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).
Best Practices
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 vary. The 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."
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?
Metadata Validation and QA/QC
All metadata entering the CMR goes through the below process to ensure metadata quality requirements are met. All records undergo CMR validation before entering the system. The process of QA/QC is slightly different for NASA and non-NASA data providers. Non-NASA providers include interagency and international data providers and are referred to as the International Directory Network (IDN).
Please see the expandable sections below for flowchart details.
Manual Review
Identify errors, discrepancies or omissions.
Automated Review
Check that the field has been populated.
Check that the field is populated with a valid value.
Check that the field length for 'ProcessingLevel/Id' is not greater than 80 characters.
Note: if a justification is provided for why the EOSDIS dataset cannot be assigned an EOSDIS processing level, the recommendation will be changed to yellow upon the second iteration of review.
The processing level provided is incorrect for the dataset.
The processing level description contains a spelling or grammatical error.
The processing level description incorrectly describes the processing level provided.
This element is categorized as medium priority when:
A non-EOSDIS dataset, being re-distributed via EOSDIS, does not match an EOSDIS processing level.
A recommendation is made to improve the syntax of the processing level description.
This element is categorized as low priority when:
A recommendation is made to update the processing level description to match a recommended processing level Id change.
The processing level description provided is vague to the point where it does not help discern between the assigned processing level and another processing level.
The first letter of the processing level description is not capitalized.
A recommendation is made to update a link in the processing level description from 'http' to 'https'.
A miscellaneous inconsistency is noted in the processing level description.
No processing level description is provided.
The element is provided and follows all applicable criteria specified in the best practices section above.
ARC Automated Checks
If a value is not provided, return is: "Provide a processing level Id for this dataset. This is a required field."
If the provided value is "1," return is: " '1' is not a valid Processing Level ID; please choose either '1A' or '1B'."
The ProcessingLevelId is an invalid value. The ProcessingLevelId should be chosen from a list of NASA EOSDIS appoved values: <schema listed here>.
If an appropriate value is provided, return is "OK."
DialectMappings
DIF 9(Note: DIF-9 is being phased out and will no longer be supported after 2018)
DIF 10
UMM-C Element
DIF 10 Path
Type
Usable Valid Values
Constraints
Required in DIF 10?
Cardinality
Notes
ProcessingLevel/Id
Processing_Level_Id
Enumeration
Not provided
0
1
1A
1B
1T
2
2G
2P
3
4
NA
n/a
Yes
1
The DIF 10 enumeration includes values that fall outside of the EOSDIS processing level scheme. While these options are available, adherence to the EOSDIS processing levels is still strongly recommended.
Enumeration Mapping
N/A
Example Mapping
DIF 10
<Processing_Level_Id>3</Processing_Level_Id>
UMM
ProcessingLevel: {
Id: "3"
},
ECHO 10
UMM-C Element
ECHO 10 Path
Type
Constraints
Required in ECHO10?
Cardinality
Notes
ProcessingLevel/Id
/Collection/ProcessingLevelId
String
n/a
No
0..1
Processing Level Id is not controlled in ECHO10. Therefore it is strongly encouraged that one of the EOSDIS processing levels be provided: 0, 1A, 1B, 2, 3, 4
ProcessingLevel/Description
/Collection/ProcessingLevelDescription
String
n/a
No
0..1
Enumeration Mapping
N/A
Example Mapping
ECHO 10
<ProcessingLevelId>3</ProcessingLevelId>
<ProcessingLevelDescription>Variables mapped on uniform space-time grid scales, usually with some completeness and consistency.</ProcessingLevelDescription>
UMM
ProcessingLevel: {
Id: "3",
Description: "Variables mapped on uniform space-time grid scales, usually with some completeness and consistency."
},
The first path to the left is where the processing level Id should be provided. It is recommended that an EOSDIS processing level be assigned if possible.
The value of "gov.nasa.esdis.umm.processinglevelid" should be provided in the gmd:codeSpace field so that CMR can properly parse out the processing level Id.
The first path to the left is where the processing level Id should be provided. It is recommended that an EOSDIS processing level be assigned if possible.
The value of "gov.nasa.esdis.umm.processinglevelid" should be provided in the gmd:codeSpace field so that CMR can properly parse out the processing level Id.