Standardize filenaming conventions related to satellite and instrument names

[djhoese]

I recently discovered that P2G has a couple different ways (at least pre-2.3 release) of naming satellites (a.k.a platforms) and instruments. This is causing weird inconsistencies with the filenames that it produces where for VIIRS from NOAA-20 we may end up with filenames using:

1. "noaa20" (viirs_sdr reader)
2. "noaa-20" (viirs_edr_active_fires reader)
3. "j01" (crefl reader)

Historically P2G has preferred lowercase non-hyphenated names (npp_viirs) but this means we have to change the default naming used by Satpy pretty often and sometimes make things unexpected for users. We even have Geo2Grid naming files with "GOES-16_ABI" instead of "goes16_abi".

I'm wondering if P2G can come up with one "rule" for how it names things that is consistent across Satpy, Polar2Grid, and Geo2Grid.

@pnuu, @adybbroe, and @mraspaud, I'm curious what you usually do and how you name things? How do you feel about hyphens and capital letters in filenames?

[pnuu]

We (FMI) use the OSCAR naming for satellite platform, and so far haven't used the instrument at all in the filenames (the files are in per-instrument directories). A typical filename is e.g. 20190404_0033_Suomi-NPP_ EPSG3035_night_microphysical.tif. Other naming schemes are in use, but that's what I generally prefer. As an operations-person, I always name the files in a way that suits either me or the user, so never use whatever the software has as a default 😁

[mraspaud]

I'm with @pnuu, we try to stick to oscar naming. For users that want something else, we any have the file pattern set manually in the operational chains, so that we don't take the risk of underlying software changing the default naming.