Skip to content

Use preferred "METimage" spelling in user-facing text - #838

Merged
djhoese merged 1 commit into
ssec:mainfrom
djhoese:fix-metimage-naming
Sep 3, 2026
Merged

djhoese merged 1 commit into
ssec:mainfrom
djhoese:fix-metimage-naming

Conversation

@djhoese

@djhoese djhoese commented Sep 2, 2026

Copy link
Copy Markdown
Member

The METImage instrument on Metop-SG is preferred to be written as "METimage". The NEWS.rst entry for the new reader was the only place using a different spelling ("MetImage").

Also drop the "A1" suffix from the summary table entry so it uses the generic "Metop-SG" platform name, matching NEWS.rst.

The lowercase "metimage" occurrences elsewhere are identifiers -- the Satpy reader name, the module and documentation filenames, and the "sensor: metimage" match key in resampling.yaml -- and are left alone.

@djhoese djhoese self-assigned this Sep 2, 2026
@coveralls

coveralls commented Sep 2, 2026 •

Copy link
Copy Markdown

Coverage Status

coverage: 83.587%. remained the same — djhoese:fix-metimage-naming into ssec:main

The METImage instrument on Metop-SG is preferred to be written as
"METimage". The NEWS.rst entry for the new reader was the only place
using a different spelling ("MetImage").

Also drop the "A1" suffix from the summary table entry so it uses the
generic "Metop-SG" platform name, matching NEWS.rst.

The lowercase "metimage" occurrences elsewhere are identifiers -- the
Satpy reader name, the module and documentation filenames, and the
"sensor: metimage" match key in resampling.yaml -- and are left alone.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QLXJ4rxrYUq3sLDvB3v7Vw
@djhoese
djhoese force-pushed the fix-metimage-naming branch from 96dab73 to 3e18282 Compare September 3, 2026 14:33
@djhoese
djhoese merged commit fbddc38 into ssec:main Sep 3, 2026
9 checks passed
@djhoese
djhoese deleted the fix-metimage-naming branch September 3, 2026 14:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants