Table of Contents | ||
---|---|---|
|
Element Description
An identifier indicating the level at which the data in the collection are processed, ranging from level 0 (raw instrument data at full resolution) to level 4 (model output or analysis results). The value of Processing Level Id is chosen from a controlled vocabulary.
Best Practices
Issue: need to reconcile processing level enums and decide on best practices
Current enums:
MMT: Not Provided, 0, 1, 1A, 1B, 1C, 1T, 2, 2G, 2P, 3, 4, NA
UMM: https://git.earthdata.nasa.gov/projects/EMFD/repos/unified-metadata-model/browse/collection/v1.10/umm-c-json-schema.json#57 ← enum is not referenced in the UMM-C schema
DIF10: https://git.earthdata.nasa.gov/projects/EMFD/repos/dif-schemas/browse/10.x/UmmCommon_1.3.xsd#432 (same as MMT minus 1C)
ECHO10: no enumeration listed in schema
EOSDIS Processing level Ids: https://science.nasa.gov/earth-science/earth-science-data/data-processing-levels-for-eosdis-data-products/ ← Currently all processing levels in CMR are being humanized to these values. Is this correct?
Some datasets will not fit within the EOSDIS processing level scheme, or the enumerations provided in MMT. (example, ALOS PALSAR level 1.1 and 1.5 data). We should provide guidance to metadata authors on what to do in these cases. If values are getting humanized then we need to provide a mapping table.
It is recommended that the processing level align with the EOSDIS data processing levels if at all possible. The EOSDIS data processing levels are: 0, 1A, 1B, 2, 3, 4. Please see the EOSDIS Data Processing Levels policy page for a more detailed description of each of the processing levels. It is recommended that processing levels be assigned in a consistent manner for all datasets from a data provider. A processing level Id is required.
The processing level description is an optional field used to provide details on the processing level. Ideally the description should be a brief summary which aids the user in understanding the degree to which the source data has been processed. The level of detail provided in the description may varyThe description may range from very generic (e.g. "Model derived") to more specific (e.g. "Radiometrically calibrated and orthorectified using ground control points and SRTM digital elevation model (DEM) data to correct for relief displacement. Data is provided in digital numbers."
Examples:
Id: "4"
Description: "This data product is model derived."
Id: "1B"
Description: "Radiometrically calibrated and orthorectified using ground control points and SRTM digital elevation model (DEM) data to correct for relief displacement. Data has been converted from digital numbers to top of atmosphere (TOA) reflectance."Examples:
Element Specification
Model | Element | Type | Constraints | Required? | Cardinality |
---|---|---|---|---|---|
UMM-C | ProcessingLevel/Id | String | 1 - 80 characters | Yes | 1 |
UMM-C | ProcessingLevel/Description | String | 1 - 2048 characters | No | 0..1 |
Any values needed for translations?
ARC Priority Matrix
Priority Categorization | Justification | ||
---|---|---|---|
This element is categorized as highest priority when:
| |||
This element is categorized as medium priority when:
| |||
This element is categorized as low priority when:
| |||
The element is provided, and follows all applicable criteria specified in the best practices section above | Not applicable | The element is provided, and is a formal title for the dataset (i.e. it is not the same as the short name and is free of grammatical and content errors). |
Dialect Mappings
Expand | ||
---|---|---|
| ||
DIF 9 (Note: DIF-9 is being phased out and will no longer be supported after 2018) |
Expand | ||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||
DIF 10
Enumeration Mapping N/A Example Mapping
|
Expand | ||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||
ECHO 10
Yes | 1 | The DataSetId element and the LongName element may be identical in ECHO 10.
Enumeration Mapping N/A Example Mapping
|
Expand | ||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||
ISO 19115-2 MENDS
Enumeration/Code List Mapping N/A Example Mapping
|
Expand | ||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||
ISO 19115-2 SMAP
Enumeration/Code List Mapping N/A Example Mapping
|
UMM Migration
N/A
Future Mappings
Expand | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
|
History
UMM Versioning
Version | Date | What Changed |
---|---|---|
1.10.0 | No changes were made for Entry Title during the transition from version 1.9.0 to 1.10.0 | |
1.9.0 |
ARC Documentation
Version | Date | What Changed | Author |
---|---|---|---|
1.0 | 4/6/18 | Recommendations/priority matrix transferred from internal ARC documentation to wiki space |