Versions Compared

Old Version 12

changes.mady.by.user Tyler Stevens

Saved on

compared with

New Version 37

changes.mady.by.user Jeanne' le Roux

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents
stylecircle

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). 

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 varyThe 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

ModelElementTypeConstraintsRequired?Cardinality
UMM-CProcessingLevel/IdString1 - 80 charactersYes1
UMM-CProcessingLevel/DescriptionString1 - 2048 charactersNo0..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).

Lucidchart
rich-viewerfalse
autofittrue
nameCopy of Wiki Page Metadata Evaluation Workflow-1939-137e40a3
width1102
pages-to-display
id98e5dc28-3252-4209-953f-66f1378e1cf4
alignLeft
height299

Please see the expandable sections below for flowchart details.


Expand
titleGCMD Metadata QA/QC
  • 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 from KMS.
    • Check that the field length for 'ProcessingLevel/Id' is not greater than 80 characters.
Expand
titleCMR Validation

<insert here>

Expand
titleARC Metadata QA/QC

ARC Priority Matrix

Priority CategorizationJustification

Red = High Priority Finding

This element is categorized as highest priority when:

  • The processing level Processing Level Id is not included at allprovided.
  • The processing level Id is included but is empty.
  • The processing level for an EOSDIS dataset does not match an EOSDIS processing level.
  • The processing level provided is incorrect for the dataset.
  • Processing Level provided is incorrect for the dataset.
  • The Processing Level Description contains a spelling or major The processing level description contains a spelling or grammatical error.
  • The processing level description Processing Level Description incorrectly describes the processing level provided.

Yellow = Medium Priority Finding

This element is categorized as medium priority when:

  • A non-EOSDIS dataset, being re-distributed via EOSDIS, The Processing Level for an EOSDIS dataset does not match an EOSDIS processing level.
    • Note: if a justification is provided for why the EOSDIS dataset cannot be assigned an EOSDIS processing level, the recommendation will be changed to blue upon the second iteration of review. 
  • 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 descriptionProcessing Level Description.

Blue = Low Priority Finding

This element is categorized as low priority when:

  • A recommendation is made to update the processing level description Processing Level Description to match a recommended processing level Id change.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 Processing Level Description is not capitalized.
  • A recommendation is made to update a link in the processing level description Processing Level Description from 'http' to 'https'.
  • A miscellaneous inconsistency is noted in the processing level description.Processing Level Description. 

Green = No Findings/Issues

The element is provided , and follows all applicable criteria specified in the best practices section above.

ARC Automated Checks

ARC uses the pyQuARC library for automated metadata checks. Please see the pyQuARC GitHub for more information.  

Dialect Mappings

Expand
titleDIF 9

DIF 9 (Note: DIF-9 is being phased out and will no longer be supported after 2018)

Expand
titleDIF 10

DIF 10

UMM-C ElementDIF 10
Specification
PathTypeUsable Valid ValuesConstraintsRequired in DIF 10?CardinalityNotes
DIF 10/DIF/
ProcessingLevel/IdProcessing_Level_IdEnumeration

Not provided

0

1

1A

1B

1T

2

2G

2P

3

4

NA

n/aYes1

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

Section
Column
width50%

DIF 10

No Format
<Processing_Level_Id>3</Processing_Level_Id>
Column
width50%

UMM

No Format
ProcessingLevel: {
  Id: "3"
},
Expand
titleECHO 10

ECHO 10

UMM-C ElementECHO 10
Specification
PathTypeConstraintsRequired in ECHO10?CardinalityNotes
ECHO 10
ProcessingLevel/Id/Collection/ProcessingLevelIdStringn/aNo0..1Processing 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
ECHO 10
ProcessingLevel/Description/Collection/ProcessingLevelDescriptionStringn/aNo0..1


Enumeration Mapping

N/A

Example Mapping

Section
Column
width50%

ECHO 10

No Format
<ProcessingLevelId>3</ProcessingLevelId>
<ProcessingLevelDescription>Variables mapped on uniform space-time grid scales, usually with some completeness and consistency.</ProcessingLevelDescription>
Column
width50%

UMM

No Format
ProcessingLevel: {
  Id: "3",
  Description: "Variables mapped on uniform space-time grid scales, usually with some completeness and consistency."
},



Expand
titleISO 19115-2 MENDS

ISO 19115-2 MENDS

UMM-C Element

ISO 19115-2 MENDS 

Specification

Path

TypeNotes
ISO 19115-2 MENDS
ProcessingLevel/Id

/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:processingLevel/gmd:MD_Identifier/gmd:code/gco:CharacterString

and

/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:processingLevel/gmd:MD_Identifier/gmd:codeSpace/gco:CharacterString = gov.nasa.esdis.umm.processinglevelid

String

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.

ISO 19115-2 MENDS
ProcessingLevel/Description

/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:processingLevel/gmd:MD_Identifier/gmd:description/gco:CharacterString

and

/gmi:MI_Metadata/gmd:contentInfo/gmd:MD_ImageDescription/gmd:processingLevelCode/gmd:MD_Identifier/gmd:description/gco:CharacterString

StringCorresponds to the UMM field ProcessingLevel/Description.

Enumeration/Code List Mapping

N/A

Example Mapping

Section
Column
width50%

ISO 19115-2 MENDS

No Format
<gmi:MI_Metadata>
  <gmd:identificationInfo>
    <gmd:MD_DataIdentification> 
      <gmd:processingLevel> 
        <gmd:MD_Identifier>
          <gmd:code>
    	    <gco:CharacterString>3</gco:CharacterString>
          </gmd:code>
          <gmd:codeSpace>
            <gco:CharacterString>gov.nasa.esdis.umm.processinglevelid</gco:CharacterString>
          </gmd:codeSpace>
          <gmd:description>
            <gco:CharacterString>Variables mapped on uniform space-time grid scales, usually with some completeness and consistency.</gco:CharacterString>
          </gmd:description>
        </gmd:MD_Identifier>
      </gmd:processingLevel>
    </gmd:MD_DataIdentification>
  </gmd:identificationInfo>
</gmi:MI_Metadata>
Column
width50%

UMM

No Format
ProcessingLevel: {
  Id: "3",
  Description: "Variables mapped on uniform space-time grid scales, usually with some completeness and consistency."
},



Expand
titleISO 19115-2 SMAP

ISO 19115-2 SMAP

UMM-C Element


ISO 19115-2 SMAP 

Specification

Path

TypeNotes
ProcessingLevel/Id

/

ISO 19115-2 SMAP

/gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:processingLevel/gmd:MD_Identifier/gmd:code/gco:CharacterString

and

/gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:processingLevel/gmd:MD_Identifier/gmd:codeSpace/gco:CharacterString = gov.nasa.esdis.umm.processinglevelid

String

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.

ISO 19115-2 SMAPProcessingLevel/Description

/gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:processingLevel/gmd:MD_Identifier/gmd:description/gco:CharacterString

and

/gmi:MI_Metadata/gmd:contentInfo/gmd:MD_ImageDescription/gmd:processingLevelCode/gmd:MD_Identifier/gmd:description/gco:CharacterString

StringCorresponds to the UMM field ProcessingLevel/Description.

Enumeration/Code List Mapping

N/A

Example Mapping

Section
Column
width50%

ISO 19115-2 SMAP

No Format
<gmd:DS_Series>
  <gmd:seriesMetadata>
    <gmi:MI_Metadata>
      <gmd:identificationInfo>
        <gmd:MD_DataIdentification> 
          <gmd:processingLevel> 
            <gmd:MD_Identifier>
              <gmd:code>
    	        <gco:CharacterString>3</gco:CharacterString>
              </gmd:code>
              <gmd:codeSpace>
                <gco:CharacterString>gov.nasa.esdis.umm.processinglevelid</gco:CharacterString>
              </gmd:codeSpace>
              <gmd:description>
                <gco:CharacterString>Variables mapped on uniform space-time grid scales, usually with some completeness and consistency.</gco:CharacterString>
              </gmd:description>
            </gmd:MD_Identifier>
          </gmd:processingLevel>
        </gmd:MD_DataIdentification>
      </gmd:identificationInfo>
    </gmi:MI_Metadata>
  </gmd:seriesMetadata>
</gmd:DS_Series>
Column
width50%

UMM

No Format
ProcessingLevel: {
  Id: "3",
  Description: "Variables mapped on uniform space-time grid scales, usually with some completeness and consistency."
},



UMM Migration

N/A

Excerpt
hiddentrue

Future Mappings

Expand
titleISO 19115-1

ISO 19115-1

Specification
UMM-C ElementISO 19115-1 PathTypeNotes
ISO 19115-1
ProcessingLevel/Id

/mdb:MD_Metadata/mdb:identificationInfo/mri:MD_DataIdentification/mri:processingLevel/mcc:MD_Identifier/mcc:code/gco:CharacterString

and

/mdb:MD_Metadata/mdb:contentInfo/mdb:MD_ImageDescription/mdb:processingLevelCode/mcc:MD_Identifier/mcc:code/gco:CharacterString

String

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.

ISO 19115-1
ProcessingLevel/Description

/mdb:MD_Metadata/mdb:identificationInfo/mri:MD_DataIdentification/mri:processingLevel/mcc:MD_Identifier/mcc:description/gco:CharacterString

and

/mdb:MD_Metadata/mdb:contentInfo/mdb:MD_ImageDescription/mdb:processingLevelCode/mcc:MD_Identifier/mcc:description/gco:CharacterString

StringCorresponds to the
UMM field ProcessingLevel/Description.
UMM field ProcessingLevel/Description.


Example Mapping

Section
Column
width50%

ISO 19115-1

No Format
ADD EXAMPLE
Column
width50%

UMM

No Format
ProcessingLevel: {
  Id: "3",
  Description: "Variables mapped on uniform space-time grid scales, usually with some completeness and consistency."
},

History

UMM Versioning

VersionDateWhat Changed
1.15.512/3/2020No changes were made for Processing Level during the transition from version 1.15.4 to 1.15.5
1.15.49/18/2020No changes were made for Processing Level during the transition from version 1.15.3 to 1.15.4
1.15.37/1/2020No changes were made for Processing Level during the transition from version 1.15.2 to 1.15.3
1.15.25/20/2020No changes were made for Processing Level during the transition from version 1.15.1 to 1.15.2
1.15.13/25/2020No changes were made for Processing Level during the transition from version 1.15.0 to 1.15.1
1.15.02/26/2020No changes were made for Processing Level during the transition from version 1.14.0 to 1.15.0
1.14.010/21/2019No changes were made for Processing Level during the transition from version 1.13.0 to 1.14.0
1.13.004/11/2019No changes were made for Processing Level during the transition from version 1.12.0 to 1.13.0
1.12.001/22/2019No changes were made for Processing Level during the transition from version 1.11.0 to 1.12.0.
1.11.011/28/2018No changes were made for Processing Level during the transition from version 1.10.0 to 1.11.0.
1.10.005/02/2018No changes were made for Processing Level during the transition from version 1.9.0 to 1.10.0.
1.9.0

DIF Versioning

VersionDateWhat Changed
10.3May 2018Changed field from optional to required for UMM-C compliance

ARC Documentation

History

UMM Versioning

110.0
VersionDateWhat ChangedAuthor
2.No changes were made for Processing Level during the transition from version 1.9.0 to 1.10.01.9.0

ARC Documentation

06/18/2021Moved "The Processing Level for an EOSDIS dataset does not match an EOSDIS processing level" from the red to yellow prioritization category. Removed "No Processing Level Description is provided" from the ARC Priority Matrix (this was listed under the blue prioritization category). 

Jeanne' le Roux

1.005/22/2018
VersionDateWhat ChangedAuthor
1.05/22/18Recommendations/priority matrix transferred from internal ARC documentation to wiki space

Jeanne' le Roux