Update reader configuration with human-readable long names

[djhoese]

We currently have a description field in the reader YAML files, but these are not standardized. Descriptions may also be long sentences or paragraphs (at least commonly in other software/file formats). Maybe we should add a long_name or short_name attribute to the reader so that GUI applications (like SIFT) can have a pretty name to show a novice user:

abi_l1b -> GOES-R ABI Level 1b
viirs_edr_active_fires -> JPSS VIIRS EDR - Active Fires

[djhoese]

Would it make sense to have a separate parameter for types of satellite supported like polar versus geo versus both?

[sfinkens]

Good idea! Since all the descriptions are one liners at the moment, we could use them but strip the Reader for ... and ... reader parts.
Not sure about the supported type of satellite. For which reader would you specify both?

[djhoese]

Ah sorry, should have been clearer. There are some readers which are algorithm software readers like clavrx or geocat so they support multiple sensors including polar-orbiting and geostationary.

[sfinkens]

Ok I see, then a geo/leo/both tag makes sense!