Page History

Table of Contents

style	circle

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

Justification
This element is categorized as highest priority when: The element processing level Id is not included at all. The element 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: The processing level of a dataset originating outside of EOSDIS A non-EOSDIS dataset, being re-distributed via EOSDIS, does not match an EOSDIS processing level. EOSDIS may re-distribute data from other data providers and the standard EOSDIS processing levels may not apply. 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	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

title	DIF 9

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

Expand

title	DIF 10

DIF 10

Specification

Path

Type

Usable Valid Values

Constraints

Required in DIF 10?

Cardinality

Notes

DIF 10

/DIF/Entry_TitleStringProcessing_Level_Id

Enumeration

Not provided

0

1

1A

1B

1T

2

2G

2P

3

4

NA

n/a

Yes

1

DIF 10 Entry_Title is a string. The Entry_Title and Version Id must be unique for a providerThe 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

width	50%

DIF 10

No Format
<Entry_Title>Aquarius Official Release Level 3 Sea Surface Salinity Smoothed Standard Mapped Image Monthly Data V4.0</Entry_Title><Processing_Level_Id>3</Processing_Level_Id>

Column

width	50%

UMM

No Format
"EntryTitle" ProcessingLevel: "Aquarius{ Official ReleaseId: Level 3 Sea Surface Salinity Smoothed Standard Mapped Image Monthly Data V4.0""3" },

The DataSetId element and the LongName element may be identical in ECHO 10.

Expand

title	ECHO 10

ECHO 10

Specification	Path	Type	Constraints	Required in ECHO10?	Cardinality	Notes
ECHO 10	/Collection/

DataSetId

ProcessingLevelId

String

Yes

1

n/a	No	0..1	Processing level 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/ProcessingLevelDescription	String	n/a	No	0..1

Enumeration Mapping

N/A

Example Mapping

Section

Column

width	50%

ECHO 10

No Format

<DataSetId>Aquarius Official Release Level 3 Sea Surface Salinity Smoothed Standard Mapped Image Monthly Data V4.0</DataSetId><ProcessingLevelId>3</ProcessingLevelId>
<ProcessingLevelDescription>...</ProcessingLevelDescription>

Column

width	50%

UMM

No Format
"EntryTitle" : "Aquarius Official Release Level 3 Sea Surface Salinity Smoothed Standard Mapped Image Monthly Data V4.0",

Expand

title	ISO 19115-2 MENDS

ISO 19115-2 MENDS

Specification

Path

Type

Notes

ISO 19115-2 MENDS

/gmi:MI_Metadata/gmd:fileIdentifier/gco:CharacterString

/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:title/gco:CharacterString

String

The first path specified to the left is optional in ISO.

The second path specified to the left is required in ISO.

Enumeration/Code List Mapping

N/A

Example Mapping

Section

Column

width	50%

ISO 19115-2 MENDS

No Format

<gmi:MI_Metadata>
	<gmd:fileIdentifier>
    	<gco:CharacterString>Aquarius Official Release Level 3 Sea Surface Salinity Smoothed Standard Mapped Image Monthly Data V4.0</gco:CharacterString>
	</gmd:fileIdentifier>
</gmi:MI_Metadata>


<gmi:MI_Metadata>
	<gmd:identificationInfo>
		<gmd:MD_DataIdentification>
			<gmd:citation>
			<gmd:CI_Citation>
				<gmd:title>
					<gco:CharacterString>Aquarius Official Release Level 3 Sea Surface Salinity Smoothed Standard Mapped Image Monthly Data V4.0</gco:CharacterString>
    			</gmd:title>
			</gmd:CI_Citation>
			</gmd:citation>
		</gmd:MD_DataIdentification>
	</gmd:identificationInfo>
</gmi:MI_Metadata>

Column

width	50%

UMM

No Format
"EntryTitle" : "Aquarius Official Release Level 3 Sea Surface Salinity Smoothed Standard Mapped Image Monthly Data V4.0",

Expand

title	ISO 19115-2 SMAP

ISO 19115-2 SMAP

Specification

Path

Type

Notes

ISO 19115-2 SMAP

/gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/ gmd:aggregationInfo/gmd:MD_AggregateInformation/gmd:aggregateDataSetIdentifier/gmd:MD_Identifier/ gmd:code/gco:CharacterString

with

/gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/ gmd:citation/gmd:CI_Citation/gmd:title/gco:CharacterString='DataSetId'

String

Adding gco:CharacterString='DataSetId' helps CMR identify the identifier provided within the aggregate information section as the Entry Title.

Enumeration/Code List Mapping

N/A

Example Mapping

Section

Column

width	50%

ISO 19115-2 SMAP

No Format

<gmd:DS_Series>
 <gmd:seriesMetadata>
  <gmi:MI_Metadata>
	<gmd:identificationInfo>
		<gmd:MD_DataIdentification>
			<gmd:citation>
				<gmd:CI_Citation>
					<gmd:title>
						<gco:CharacterString>DataSetId</gco:CharacterString>
    				</gmd:title>
				</gmd:CI_Citation>
			</gmd:citation>
			<gmd:aggregationInfo>
				<gmd:MD_AggregateInformation>
					<gmd:aggregateDataSetIdentifier>
						<gmd:MD_Identifier>
							<gmd:code>
								<gco:CharacterString>Aquarius Official Release Level 3 Sea Surface Salinity Smoothed Standard Mapped Image Monthly Data V4.0</gco:CharacterString>
							</gmd:code>
						</gmd:MD_Identifier>
					</gmd:aggregateDataSetIdentifier>
				</gmd:MD_AggregateInformation>
			</gmd:aggregationInfo>
		</gmd:MD_DataIdentification>
	</gmd:identificationInfo>
  </gmi:MI_Metadata>
 </gmd:seriesMetadata>
</gmd:DS_Series>

Column

width	50%

UMM

No Format
"EntryTitle" : "Aquarius Official Release Level 3 Sea Surface Salinity Smoothed Standard Mapped Image Monthly Data V4.0",

UMM Migration

N/A

Future Mappings

Expand

title	ISO 19115-1

Specification

Path

Type

Notes

ISO 19115-1

/mdb:MD_Metadata/mdb:metadataIdentifier/mcc:MD_Identifier/mcc:code/gco:CharacterString

/mdb:MD_Metadata/mdb:identificationInfo/mri:MD_DataIdentification/mri:citation/cit:CI_Citation/cit:title/gco:CharacterString

String

The first path specified to the left is optional in ISO. The CMR will write the value into this path for export to ISO, but it will not read the value from this path.

The second path specified to the left is required in ISO. The CMR will read and write the value in this path.

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

Page tree

Versions Compared

Old Version 2

New Version 3

Key

Element Description

Element Specification

ARC Priority Matrix

Dialect Mappings

UMM Migration

Future Mappings

History

UMM Versioning

ARC Documentation