20 likes | 130 Views
TES-MLS Combined Measurements Product Questions. MLS is working with TES to produce a combined CO product where MLS looks at the higher altitude and TES at the lower altitude. File naming convention MLS products start the filename string with "MLS-Aura”
E N D
TES-MLS Combined MeasurementsProduct Questions MLS is working with TES to produce a combined CO product where MLS looks at the higher altitude and TES at the lower altitude. • File naming convention • MLS products start the filename string with "MLS-Aura” • TES products start the filename string with “TES-Aura” • Should we now have "MLS-TES-Aura” or “TES-MLS-Aura” or something else? • Metadata • ESDT descriptor shortname (usually instrument/processing level specific) • Multiple containers in a single metadata file can be used to delineate both TES and MLS (i.e. AssociatedPlatformInstrumentSensor,…) • Granularity description (TES = global survey, MLS = multiple 24 hour time periods) • There does not seem to be metadata for instrument for MLS Level 2 products except in the local granule ID (filename) • Does the generation and delivery of both *.met and *.xml files cause any problems?
TES-MLS Combined MeasurementsProduct Questions (cont.) • Versioning • MLS is at software release version 3, ESDT v003 • TES is at software release version 12, ESDT v005 • Do we tie it to one or the other? • Do we combine the PGE version or start it at 1? • Geolocation description of TES-MLS combined product • TES looks at nadir • MLS looks at the limb • Archiving/distribution • Which DAAC ingests the new products (TES = ASDC, MLS = GSFC) • Other DAAC provide reference/access to combined product? • Generate and deliver both .met and .xml files with HDF output • Level 4 products (like GMAO) have addressed multiple instrument/platform issues. What issues have they also dealt with?