Page tree
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 17 Next »

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

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

<insert here>

ARC Priority Matrix

Priority CategorizationJustification

This element is categorized as highest priority when:

  • The processing level Id is not included at all.
  • 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.
  • 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 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.

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"


Dialect Mappings

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

DIF 10

SpecificationPathTypeUsable Valid ValuesConstraintsRequired in DIF 10?CardinalityNotes
DIF 10/DIF/Processing_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

DIF 10

<Processing_Level_Id>3</Processing_Level_Id>

UMM

ProcessingLevel: {
  Id: "3"
},

ECHO 10

SpecificationPathTypeConstraintsRequired in ECHO10?CardinalityNotes
ECHO 10/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/Collection/ProcessingLevelDescriptionStringn/aNo0..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."
},



ISO 19115-2 MENDS

SpecificationPathTypeNotes
ISO 19115-2 MENDS

/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

/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

ISO 19115-2 MENDS

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

UMM

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



ISO 19115-2 SMAP

SpecificationPathTypeNotes
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 SMAP

/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

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

UMM

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



UMM Migration

N/A

Future Mappings

SpecificationPathTypeNotes
ISO 19115-1

/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

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




History

UMM Versioning

VersionDateWhat Changed
1.10.0
No 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

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



  • No labels