Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Some ACSPO SST AWIPS filenames not compatible with other AWIPS naming conventions #659

Closed
kathys opened this issue Dec 1, 2023 · 0 comments · Fixed by #660
Closed

Some ACSPO SST AWIPS filenames not compatible with other AWIPS naming conventions #659

kathys opened this issue Dec 1, 2023 · 0 comments · Fixed by #660
Assignees
Labels

Comments

@kathys
Copy link
Collaborator

kathys commented Dec 1, 2023

Douglas Schumacher noticed that for both Metop and SNPP satellites, the output file ACSPO SST AWIPS file naming conventions were not following the same standards as other products names. Specifically, it is the satellite names that are different.

Examples:
SSEC_AII_MetOpB_avhrr_sst_Pacific_TD03_20231130_2038.nc, and SSEC_AII_NPP_viirs_sst_Pacific_TR01_20231130_2213.nc .

The Metop sat name should be metopb and NPP should be npp.

Dave already figure out where the problem is:

I'm missing entries for metopa/b/c with no hyphen and npp -> npp here:

_PLATFORM_ALIASES = {
"suomi-npp": "npp",
"snpp": "npp",
"n20": "noaa20",
"n21": "noaa21",
"n22": "noaa22",
"n23": "noaa23",
"noaa-18": "noaa18",
"noaa-19": "noaa19",
"noaa-20": "noaa20",
"noaa-21": "noaa21",
"noaa-22": "noaa22",
"noaa-23": "noaa23",
"jpss-1": "noaa20",
"jpss-2": "noaa21",
"jpss-3": "noaa22",
"jpss-4": "noaa23",
"j1": "noaa20",
"j2": "noaa21",
"j3": "noaa22",
"j4": "noaa23",
"fy-3b": "fy3b",
"fy-3c": "fy3c",
"fy-3d": "fy3d",
"eos-aqua": "aqua",
"eos-terra": "terra",
"aqua": "aqua",
"terra": "terra",
"gcom-w1": "gcom-w1",
"metop-a": "metopa",
"metop-b": "metopb",
"metop-c": "metopc",
}

.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants