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

The instrument elements enable the specification of instruments used to collect the data available in the dataset. Instruments provided in CMR metadata must be chosen from a controlled keyword hierarchy maintained in the Keyword Management System (KMS). A list of valid instrument keywords can be found here: https://gcmdservices.gsfc.nasa.gov/static/kms/instruments/instruments.csv?

Optionally, attributes specific to the instrument (such as swath width, revisit period, spectral range, etc.) may be specified in the characteristics elements. Please see the Characteristics wiki page for a detailed description of the characteristics sub-elements. 

Best Practices

Instrument keywords are important for the discovery of data. All relevant instruments should be listed for each dataset, and each instrument listed should be provided under its associated platform. It is preferred that more specific instrument keyword terms be chosen from the KMS when available. For example, if data were collected from the AMSR-E instrument, it is preferred that "AMSR-E" be listed as the instrument as opposed to the more generic "RADIOMETERS" keyword. If a particular instrument keyword is missing from the KMS, it is possible to put in a request to have it added. The KMS is managed by the Global Change Master Directory (GCMD) and new keyword requests may be made through the GCMD Keywords Community Forum.

In the KMS, there is a hierarchy for instrument keywords. Instrument keywords should be provided in the metadata field corresponding to the appropriate position of the keyword hierarchy, otherwise the keyword will be rendered invalid. For example, the instrument short name specified in the KMS should not be provided in the instrument 'long name' field in the metadata. When listing instruments, an instrument short name will always be required. While instrument long names are not required, it is highly encouraged that long names be provided if one is listed in the KMS. Many instrumentshort names are comprised of acronyms, so inclusion of the long name provides additional context to a user who may not be familiar with the acronym. Instrument keywords are not case sensitive.

A minimum of one instrument must be listed under each platform. Multiple instruments may be listed under a single platform if appropriate. Platform/instrument relationships are not currently validated within the KMS, so care should be taken to ensure that the correct instrument is listed under the correct platform.

It is recommended that instrument keywords be assigned in a consistent manner. For example, if data for several collections were collected by the "SMAP L-Band Radiometer" instrument, it is recommended that the metadata for all of those collections list "SMAP L-Band Radiometer" as the instrument short name. Providing "SMAP L-Band Radiometer" as the instrument in some records, but the more generic "RADIOMETERS" as the instrument in other records, results in an inconsistent experience for a user discovering data. This is especially true for users narrowing down their search results in the Earthdata Search client by using the faceted search options. 

In the case that it does not make sense to provide an instrument for a dataset, "Not Applicable" is an accepted value.     

The Instruments/Technique field is optional. It can be used to further describe the technique utilized by the instrument for data collection. For example, the technique for a laser altimeter instrument on board a satellite could read "Measures the distance of the satellite from the Earth's surface by taking a precise measurement of the time it takes a transmitted laser pulse to hit the ground and then return to the instrument." 

The Instruments/NumberOfInstruments field is optional. It can be used to indicate the number of instruments (i.e. sensors) used on the instrument while acquiring data. For example, the Terra satellite carries the ASTER instrument. The ASTER instrument is made up of 3 instrument subsystems (VNIR, SWIR, and TIR). In this example, the Instruments/NumberOfInstruments field would read "3".

The Instruments/OperationalModes field is optional and may be repeated. This field can be used to specify the mode(s) in which an instrument collects data. For example, the Sentinel-1 satellite collects data in four different modes. If a collection were to contain data acquired in all four modes, the OperationalModes field could be repeated four times and read "Stripmap (SM)", "Interferomic Wide swath (IW)", "Extra-Wide swath (EW)", "Wave (WV)"  


Examples (ShortName > LongName):

SMMR > Scanning Multichannel Microwave Radiometer

OLI > Operational Land Imager

UAVSAR > Uninhabited Aerial Vehicle Synthetic Aperture Radar

LIS > Lightning Imaging Sensor

XPOL > NOAA/ETL X-band Polarimetric Doppler Radar 


Element Specification

An unlimited amount of instrument keywords may be listed (Cardinality: 1..*)

Providing instrument characteristics is optional. An unlimited amount of instrument characteristics may be specified for a particular instrument (Cardinality: 0..*). If instrument characteristics are provided, all 5 sub-fields (Name, Description, DataType, Unit, Value) are required.

ModelElementTypeUsable Valid ValuesConstraintsRequired?CardinalityNotes
UMM-CommonPlatforms/Instruments/ShortNameStringInstrument Short_Name KeywordsKMS controlled
Yes1
UMM-CommonPlatforms/Instruments/LongNameStringInstrument Long_Name KeywordsKMS controlledNo0..1
UMM-CommonPlatforms/Instruments/TechniqueStringn/a

1 - 2048 characters


No0..1
UMM-CommonPlatforms/Instruments/NumberOfInstrumentsIntegern/an/aNo0..1
UMM-CommonPlatforms/Instruments/Characteristics/NameStringn/a

1 - 80 characters


Yes, if applicable
1Only required if a characteristic is listed. Providing characteristics is optional.
UMM-CommonPlatforms/Instruments/Characteristics/DescriptionStringn/a1 - 80 charactersYes, if applicable1Only required if a characteristic is listed. Providing characteristics is optional.
UMM-CommonPlatforms/Instruments/Characteristics/DataTypeEnumeration

STRING

FLOAT

INT

BOOLEAN

DATE

TIME

DATETIME

DATE_STRING

TIME_STRING

DATETIME_STRING

n/aYes, if applicable1Only required if a characteristic is listed. Providing characteristics is optional.
UMM-CommonPlatforms/Instruments/Characteristics/UnitStringn/a

1 - 20 characters


Yes, if applicable1Only required if a characteristic is listed. Providing characteristics is optional.
UMM-CommonPlatforms/Instruments/Characteristics/ValueStringn/a

1 - 80 characters


Yes, if applicable1Only required if a characteristic is listed. Providing characteristics is optional.
UMM-CommonPlatforms/Instruments/OperationalModesStringn/a1 - 20 charactersNo0..*

Value needed for translations:

The following value is needed by the CMR to translate older non UMM compliant records to and from the UMM and other supported specifications where non required elements are considered required but no valid is given.  This is needed partly because the CMR still allows a non UMM compliant record to be ingested with warnings.

UNDEFINED  - DIF 10 records found to be missing instruments by software will be automatically assigned a value of "Not Provided". It should then be confirmed whether an instrument can be assigned or whether "Not Applicable" should be provided. The value "Not Provided" should not be used by metadata providers. 


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
    • Verify that all pertinent keywords have been applied
    • Verify that existing facets and other controlled keyword values are consistent and suitable for the data
  • 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 value is not a duplicate
    • Check that the field length is not greater than the maximum characters allowed for each sub-element
    • Check that the field '/Instrument/NumberOfSensors' is an integer value

<>

ARC Priority Matrix

Priority CategorizationJustification

This element is categorized as highest priority when:

  • The element is not included at all.
  • The instrument short name tags are provided in the metadata but are left empty.
  • The instrument keyword does not align with the KMS.
    • The instrument keyword does not exist in KMS.
    • A keyword(s) is placed in the incorrect position of the hierarchy (e.g. the instrument short name is placed in the long name field).
    • Keywords from two different KMS hierarchies are listed in the same hierarchy in the metadata (i.e. hierarchies cannot be mixed and matched)
  • Not all relevant instruments are listed.
  • An incorrect instrument is listed.
  • An instrument is listed under the incorrect platform.
  • A recommendation is made to replace a valid instrument with a more specific/appropriate instrument keyword.
  • Please see the Characteristics wiki page for high priority issues related to the Characteristics sub-elements.

This element is categorized as medium priority when:

  • A recommendation is made to add an instrument long name when a long name exists in the KMS.
  • Instruments are provided in an inconsistent manner across related datasets.
  • Please see the Characteristics wiki page for medium priority issues related to the Characteristics sub-elements.

This element is categorized as low priority when:


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

ARC Automated Checks

<>



Dialect Mappings

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

DIF 10

An unlimited amount of instrument keywords may be listed (Cardinality: 1..*)

Providing instrument characteristics is optional. An unlimited amount of instrument characteristics may be specified for a particular instrument (Cardinality: 0..*). If instrument characteristics are provided, all 5 sub-fields (Name, Description, DataType, Unit, Value) are required.

SpecificationPathTypeConstraintsRequired in DIF 10?CardinalityNotes
DIF 10/DIF/Platform/Instrument/Short_Name
String

KMS controlled

Yes1For each instrument provided, a short name is required.
DIF 10/DIF/Platform/Instrument/Long_NameString

KMS controlled

No0..1It is highly recommended that a long name be provided if one is available in KMS.
DIF 10/DIF/Platform/Instrument/TechniqueString1 - 2048 charactersNo0..1
DIF 10/DIF/Platform/Instrument/NumberOfSensorsIntegern/aNo0..1
DIF 10/DIF/Platform/Instrument/Characteristics/NameString1 - 80 charactersNo0..1
DIF 10/DIF/Platform/Instrument/Characteristics/DescriptionString1 - 2048 charactersNo0..1
DIF 10/DIF/Platform/Instrument/Characteristics/DataTypeString1 - 80 charactersNo0..1
DIF 10/DIF/Platform/Instrument/Characteristics/UnitString1 - 80 charactersNo0..1
DIF 10/DIF/Platform/Instrument/Characteristics/ValueString1 - 80 charactersNo0..1
DIF 10/DIF/Platform/Instrument/OperationalModeString1 - 20 charactersNo0..*



Example Mapping

DIF 10

<Platform>
  <Type>Earth Observation Satellites</Type>
  <Short_Name>Aqua</Short_Name>
  <Long_Name>Earth Observing System, Aqua</LongName>
  <Instrument>
    <Short_Name>MODIS</Short_Name>
    <Long_Name>Moderate-Resolution Imaging Spectroradiometer</Long_Name>
    <Characteristics>
      <Name>SwathWidth</Name>
      <Description>The width of the sensor scan as the satellite moves along the ground track.</Description>
      <DataType>INT</DataType>
      <Unit>Kilometers</Unit>
      <Value>2330</Value>
    </Characteristics>
  </Instrument>
</Platform>

UMM

Platforms: [
  {
    Type: "Earth Observation Satellites",
    ShortName: "Aqua",
    LongName: "Earth Observing System, Aqua",
    Instruments: [
      {
        ShortName: "MODIS",
        LongName: "Moderate-Resolution Imaging Spectroradiometer",  
        Characteristics: [
          {
            Name: "SwathWidth",
            Description: "The width of the sensor scan as the satellite moves along the ground track.",
            DataType: "INT",
            Unit: "Kilometers",
            Value: "2330",
          }
        ]
      }
    ]
  }
],

ECHO 10

An unlimited amount of instrument keywords may be listed (Cardinality: 1..*)

Providing instrument characteristics is optional. An unlimited amount of instrument characteristics may be specified for a particular instrument (Cardinality: 0..*). If instrument characteristics are provided, all 5 sub-fields (Name, Description, DataType, Unit, Value) are required.

SpecificationPathTypeConstraintsRequired in ECHO10?CardinalityNotes
ECHO 10/Collection/Platforms/Platform/Instruments/Instrument/ShortNameString

KMS controlled

Yes1For each instrument provided, a short name is required.
ECHO 10/Collection/Platforms/Platform/Instruments/Instrument/LongNameStringKMS controlledNo0..1It is highly recommended that a long name be provided if one is available in KMS.
ECHO 10Collection/Platforms/Platform/Instruments/Instrument/TechniqueString
No0..1
ECHO 10Collection/Platforms/Platform/Instruments/Instrument/NumberOfSensorsInteger
No0..1
ECHO 10/Collection/Platforms/Platform/Instruments/Instrument/Characteristics/Characteristic/NameString
Yes, if applicable1Only required if a characteristic is listed. Providing characteristics is optional.
ECHO 10/Collection/Platforms/Platform/Instruments/Instrument/Characteristics/Characteristic/DescriptionString
Yes, if applicable1Only required if a characteristic is listed. Providing characteristics is optional.
ECHO 10/Collection/Platforms/Platform/Instruments/Instrument/Characteristics/Characteristic/DataType String
Yes, if applicable1Only required if a characteristic is listed. Providing characteristics is optional.
ECHO 10/Collection/Platforms/Platform/Instruments/Instrument/Characteristics/Characteristic/UnitString
Yes, if applicable1Only required if a characteristic is listed. Providing characteristics is optional.
ECHO 10/Collection/Platforms/Platforms/Platform/Instruments/Instrument/Characteristics/Characteristic/ValueString
Yes, if applicable1Only required if a characteristic is listed. Providing characteristics is optional.
ECHO 10/Collection/Platforms/Platform/Instruments/Instrument/OperationModes/OperationModeString
No0..*


Example Mapping

ECHO 10

<Platforms>
  <Platform>
    <ShortName>Aqua</ShortName>
    <LongName>Earth Observing System, Aqua</LongName>
    <Type>Earth Observation Satellites</Type>
    <Instruments>
      <Instrument>
        <ShortName>MODIS</ShortName>
        <LongName>Moderate-Resolution Imaging Spectroradiometer</LongName>    
        <Characteristics>
          <Characteristic>
            <Name>SwathWidth</Name>
            <Description>The width of the sensor scan as the satellite moves along the ground track.</Description>
            <DataType>INT</DataType>
            <Unit>Kilometers</Unit>
            <Value>2330</Value>
          </Characteristic>
        </Characteristics>
      </Instrument>
    </Instruments>
  </Platform>
</Platforms>

UMM

Platforms: [
  {
    Type: "Earth Observation Satellites",
    ShortName: "Aqua",
    LongName: "Earth Observing System, Aqua",
    Instruments: [
      {
        ShortName: "MODIS",
        LongName: "Moderate-Resolution Imaging Spectroradiometer",  
        Characteristics: [
          {
            Name: "SwathWidth",
            Description: "The width of the sensor scan as the satellite moves along the ground track.",
            DataType: "INT",
            Unit: "Kilometers",
            Value: "2330",
          }
        ]
      }
    ]
  }
],



ISO 19115-2 MENDS

An unlimited amount of instrument keywords may be listed (Cardinality: 1..*)

Providing platform characteristics is optional. An unlimited amount of platform characteristics may be specified for a particular platform (Cardinality: 0..*). If platform characteristics are provided, all 5 sub-fields should be provided (Name, Description, DataType, Unit, Value) to meet CMR requirements.

SpecificationPathTypeNotes
ISO 19115-2 MENDS

/gmi:MI_Metadata/gmi:acquisitionInformation/gmi:MI_AcquisitionInformation/gmi:instrument/eos:EOS_Instrument id="<insert unique instrument ID here>"/ gmi:identifier/gmd:MD_Identifier/gmd:code/gco:CharacterString

with

/gmi:MI_Metadata/gmi:acquisitionInformation/gmi:MI_AcquisitionInformation/gmi:instrument/eos:EOS_Instrument/ gmi:identifier/gmd:MD_Identifier/gmd:codeSpace/gco:CharacterString = gov.nasa.esdis.umm.instrumentshortname

String

Corresponds to the UMM field Platforms/Instruments/ShortName. A list of valid instrument short names can be found in the KMS. For each instrument listed the short name is required by CMR. The short name value goes in the gmd:code field. The value of " gov.nasa.esdis.umm.instrumentshortname" should be provided in gmd:CodeSpace field so that CMR can properly parse out the instrument short name.

An ID should be provided directly after "eos:EOS_Instrument" in the ISO x-path. This ID corresponds to the instrument and is used to link the instrument information to the associated platform. The ID should be unique within the metadata record.

ISO 19115-2 MENDS

/gmi:MI_Metadata/gmi:acquisitionInformation/gmi:MI_AcquisitionInformation/gmi:instrument/eos:EOS_Instrument/ gmi:identifier/gmd:MD_Identifier/gmd:description/gco:CharacterString

StringCorresponds to the UMM field Platforms/Instruments/LongName. A list of valid instrument long names can be found in the KMS.
ISO 19115-2 MENDS/gmi:MI_Metadata/gmi:acquisitionInformation/gmi:MI_AcquisitionInformation/gmi:instrument/eos:EOS_Instrument/ gmi:type/gco:CharacterString StringCorresponds to the UMM field Platforms/Instruments/Technique.
ISO 19115-2 MENDS<placeholder for mapping>
Corresponds to the UMM field Platforms/Instruments/NumberOfInstruments.
ISO 19115-2 MENDS/gmi:MI_Metadata/gmi:acquisitionInformation/gmi:MI_AcquisitionInformation/gmi:instrument/eos:EOS_Instrument/ eos:otherProperty/gco:Record/eos:AdditionalAttributes/eos:AdditionalAttribute/eos:reference/eos:EOS_AdditionalAttributeDescription/ eos:type/eos:EOS_AdditionalAttributeTypeCode codeList="https://cdn.earthdata.nasa.gov/iso/resources/Codelist/gmxCodelists.xml#EOS_AdditionalAttributeTypeCode" codeListValue="instrumentInformation"=instrumentInformationCodelistThe "instrumentInformation" codelist value must be provided so that CMR can properly identify the associated information as instrument characteristics. This codelist value does not directly map to a UMM element - choosing 'instrumentInformation' indicates to CMR that the instrument characteristic elements should be mapped.
ISO 19115-2 MENDS/gmi:MI_Metadata/gmi:acquisitionInformation/gmi:MI_AcquisitionInformation/gmi:instrument/eos:EOS_Instrument/ eos:otherProperty/gco:Record/eos:AdditionalAttributes/eos:AdditionalAttribute/eos:reference/eos:EOS_AdditionalAttributeDescription/ eos:name/gco:CharacterStringStringCorresponds to the UMM field Platforms/Instruments/Characteristics/Name.
ISO 19115-2 MENDS/gmi:MI_Metadata/gmi:acquisitionInformation/gmi:MI_AcquisitionInformation/gmi:instrument/eos:EOS_Instrument/ eos:otherProperty/gco:Record/eos:AdditionalAttributes/eos:AdditionalAttribute/eos:reference/eos:EOS_AdditionalAttributeDescription/ eos:description/gco:CharacterStringStringCorresponds to the UMM field Platforms/Instruments/Characteristics/Description.
ISO 19115-2 MENDS/gmi:MI_Metadata/gmi:acquisitionInformation/gmi:MI_AcquisitionInformation/gmi:instrument/eos:EOS_Instrument/ eos:otherProperty/gco:Record/eos:AdditionalAttributes/eos:AdditionalAttribute/eos:reference/eos:EOS_AdditionalAttributeDescription/ eos:dataType/eos:EOS_AdditionalAttributeDataTypeCode codeList="https://cdn.earthdata.nasa.gov/iso/resources/Codelist/gmxCodelists.xml#MD_DatatypeCode" codeListValue=<date type> value=<data type>Codelist

Corresponds to the UMM field Platforms/Instruments/Characteristics/DataType.

ISO codelist values (class, codelist, enumeration, codelistElement, abstractClass, aggregateClass, specifiedClass, datatypeClass, interfaceClass, unionClass, metaClass, typeClass, characterString, integer, association)

UMM enum (STRING, FLOAT, INT BOOLEAN, DATE, TIME, DATETIME, DATE_STRING, TIME_STRING, DATETIME_STRING)

ISO 19115-2 MENDS/gmi:MI_Metadata/gmi:acquisitionInformation/gmi:MI_AcquisitionInformation/gmi:instrument/eos:EOS_Instrument/ eos:otherProperty/gco:Record/eos:AdditionalAttributes/eos:AdditionalAttribute/eos:reference/eos:EOS_AdditionalAttributeDescription/ eos:parameterUnitsOfMeasure/gco:CharacterStringStringCorresponds to the UMM field Platforms/Instruments/Characteristics/Unit.
ISO 19115-2 MENDS/gmi:MI_Metadata/gmi:acquisitionInformation/gmi:MI_AcquisitionInformation/gmi:instrument/eos:EOS_Instrument/ eos:otherProperty/gco:Record/eos:AdditionalAttributes/eos:AdditionalAttribute/eos:value/gco:CharacterStringStringCorresponds to the UMM field Platforms/Instruments/Characteristics/Value.

ISO 19115-2 MENDS

/gmi:MI_Metadata/gmi:acquisitionInformation/gmi:MI_AcquisitionInformation/gmi:instrument/eos:EOS_Instrument/ eos:otherProperty/gco:Record/eos:AdditionalAttributes/eos:AdditionalAttribute/eos:reference/eos:EOS_AdditionalAttributeDescription/ eos:name/gco:CharacterString="OperationalMode"

and

/gmi:MI_Metadata/gmi:acquisitionInformation/gmi:MI_AcquisitionInformation/gmi:instrument/eos:EOS_Instrument/ eos:otherProperty/gco:Record/eos:AdditionalAttributes/eos:AdditionalAttribute/eos:value/gco:CharacterString

StringCorresponds to the UMM field Platforms/Instruments/OperationalMode. The eos:name field must read "OperationalMode" so that CMR can properly parse out the operation mode information. The actual operation mode value should be provided in the eos:value field.
ISO 19115-2 MENDSgmi:MI_Metadata/gmi:acquisitionInformation/gmi:MI_AcquisitionInformation/gmi:instrument/eos:EOS_Instrument/ gmi:mountedOn xlink:href='<insert unique ID here>'
An ID should be provided here and should match the ID provided for the associated platform. This ID should be unique within a metadata record. This will link all of the information provided on the instrument to its associated platform.


Example Mapping

ISO 19115-2 MENDS


UMM

Platforms: [
  {
    Type: "Earth Observation Satellites",
    ShortName: "Aqua",
    LongName: "Earth Observing System, Aqua",
    Instruments: [
      {
        ShortName: "MODIS",
        LongName: "Moderate-Resolution Imaging Spectroradiometer",  
        Characteristics: [
          {
            Name: "SwathWidth",
            Description: "The width of the sensor scan as the satellite moves along the ground track.",
            DataType: "INT",
            Unit: "Kilometers",
            Value: "2330",
          }
        ]
      }
    ]
  }
],



ISO 19115-2 SMAP

An unlimited amount of instrument keywords may be listed (Cardinality: 1..*)

Providing instrument characteristics is optional. An unlimited amount of instrument characteristics may be specified for a particular instrument (Cardinality: 0..*). If instrument characteristics are provided, all 5 sub-fields should be provided (Name, Description, DataType, Unit, Value) to meet CMR requirements.

SpecificationPathTypeNotes
ISO 19115-2 SMAP

/gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmi:acquisitionInformation/gmi:MI_AcquisitionInformation/gmi:instrument/eos:EOS_Instrument id="<insert unique instrument ID here>"/ gmi:identifier/gmd:MD_Identifier/gmd:code/gco:CharacterString

with

/gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmi:acquisitionInformation/gmi:MI_AcquisitionInformation/gmi:instrument/eos:EOS_Instrument/ gmi:identifier/gmd:MD_Identifier/gmd:codeSpace/gco:CharacterString = gov.nasa.esdis.umm.instrumentshortname

String

Corresponds to the UMM field Platforms/Instruments/ShortName. A list of valid instrument short names can be found in the KMS. For each instrument listed the short name is required by CMR. The short name value goes in the gmd:code field. The value of " gov.nasa.esdis.umm.instrumentshortname" should be provided in gmd:CodeSpace field so that CMR can properly parse out the instrument short name.

An ID should be provided directly after "eos:EOS_Instrument" in the ISO x-path. This ID corresponds to the instrument and is used to link the instrument information to the associated platform. The ID should be unique within the metadata record.

ISO 19115-2 SMAP

/gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmi:acquisitionInformation/gmi:MI_AcquisitionInformation/gmi:instrument/eos:EOS_Instrument/ gmi:identifier/gmd:MD_Identifier/gmd:description/gco:CharacterString

StringCorresponds to the UMM field Platforms/Instruments/LongName. A list of valid instrument long names can be found in the KMS.
ISO 19115-2 SMAP
/gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmi:acquisitionInformation/gmi:MI_AcquisitionInformation/gmi:instrument/eos:EOS_Instrument/ gmi:type/gco:CharacterStringStringCorresponds to the UMM field Platforms/Instruments/Technique.
ISO 19115-2 SMAP
<placeholder for mapping>
Corresponds to the UMM field Platforms/Instruments/NumberOfInstruments.
ISO 19115-2 SMAP
/gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmi:acquisitionInformation/gmi:MI_AcquisitionInformation/gmi:instrument/eos:EOS_Instrument/ eos:otherProperty/gco:Record/eos:AdditionalAttributes/eos:AdditionalAttribute/eos:reference/eos:EOS_AdditionalAttributeDescription/ eos:type/eos:EOS_AdditionalAttributeTypeCode codeList="https://cdn.earthdata.nasa.gov/iso/resources/Codelist/gmxCodelists.xml#EOS_AdditionalAttributeTypeCode" codeListValue="instrumentInformation"=instrumentInformationCodelistThe "instrumentInformation" codelist value must be provided so that CMR can properly identify the associated information as instrument characteristics. This codelist value does not directly map to a UMM element - choosing 'instrumentInformation' indicates to CMR that the instrument characteristic elements should be mapped.
ISO 19115-2 SMAP
/gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmi:acquisitionInformation/gmi:MI_AcquisitionInformation/gmi:instrument/eos:EOS_Instrument/ eos:otherProperty/gco:Record/eos:AdditionalAttributes/eos:AdditionalAttribute/eos:reference/eos:EOS_AdditionalAttributeDescription/ eos:name/gco:CharacterStringStringCorresponds to the UMM field Platforms/Instruments/Characteristics/Name.
ISO 19115-2 SMAP
/gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmi:acquisitionInformation/gmi:MI_AcquisitionInformation/gmi:instrument/eos:EOS_Instrument/ eos:otherProperty/gco:Record/eos:AdditionalAttributes/eos:AdditionalAttribute/eos:reference/eos:EOS_AdditionalAttributeDescription/ eos:description/gco:CharacterStringStringCorresponds to the UMM field Platforms/Instruments/Characteristics/Description.
ISO 19115-2 SMAP
/gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmi:acquisitionInformation/gmi:MI_AcquisitionInformation/gmi:instrument/eos:EOS_Instrument/ eos:otherProperty/gco:Record/eos:AdditionalAttributes/eos:AdditionalAttribute/eos:reference/eos:EOS_AdditionalAttributeDescription/ eos:dataType/eos:EOS_AdditionalAttributeDataTypeCode codeList="https://cdn.earthdata.nasa.gov/iso/resources/Codelist/gmxCodelists.xml#MD_DatatypeCode" codeListValue=<date type> value=<data type>Codelist

Corresponds to the UMM field Platforms/Instruments/Characteristics/DataType.

ISO codelist values (class, codelist, enumeration, codelistElement, abstractClass, aggregateClass, specifiedClass, datatypeClass, interfaceClass, unionClass, metaClass, typeClass, characterString, integer, association)

UMM enum (STRING, FLOAT, INT BOOLEAN, DATE, TIME, DATETIME, DATE_STRING, TIME_STRING, DATETIME_STRING)

ISO 19115-2 SMAP
/gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmi:acquisitionInformation/gmi:MI_AcquisitionInformation/gmi:instrument/eos:EOS_Instrument/ eos:otherProperty/gco:Record/eos:AdditionalAttributes/eos:AdditionalAttribute/eos:reference/eos:EOS_AdditionalAttributeDescription/ eos:parameterUnitsOfMeasure/gco:CharacterStringStringCorresponds to the UMM field Platforms/Instruments/Characteristics/Unit.
ISO 19115-2 SMAP
/gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmi:acquisitionInformation/gmi:MI_AcquisitionInformation/gmi:instrument/eos:EOS_Instrument/ eos:otherProperty/gco:Record/eos:AdditionalAttributes/eos:AdditionalAttribute/eos:value/gco:CharacterStringStringCorresponds to the UMM field Platforms/Instruments/Characteristics/Value.

ISO 19115-2 SMAP

/gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmi:acquisitionInformation/gmi:MI_AcquisitionInformation/gmi:instrument/eos:EOS_Instrument/ eos:otherProperty/gco:Record/eos:AdditionalAttributes/eos:AdditionalAttribute/eos:reference/eos:EOS_AdditionalAttributeDescription/ eos:name/gco:CharacterString="OperationalMode"

and

/gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmi:acquisitionInformation/gmi:MI_AcquisitionInformation/gmi:instrument/eos:EOS_Instrument/ eos:otherProperty/gco:Record/eos:AdditionalAttributes/eos:AdditionalAttribute/eos:value/gco:CharacterString

StringCorresponds to the UMM field Platforms/Instruments/OperationalMode. The eos:name field must read "OperationalMode" so that CMR can properly parse out the operation mode information. The actual operation mode value should be provided in the eos:value field.
ISO 19115-2 SMAP/gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmi:acquisitionInformation/gmi:MI_AcquisitionInformation/gmi:instrument/eos:EOS_Instrument/ gmi:mountedOn xlink:href='<insert unique ID here>'StringAn ID should be provided here and should match the ID provided for the associated platform. This ID should be unique within a metadata record. This will link all of the information provided on the instrument to its associated platform.


Example Mapping

ISO 19115-2 SMAP

 

UMM

Platforms: [
  {
    Type: "Earth Observation Satellites",
    ShortName: "Aqua",
    LongName: "Earth Observing System, Aqua",
    Instruments: [
      {
        ShortName: "MODIS",
        LongName: "Moderate-Resolution Imaging Spectroradiometer",  
        Characteristics: [
          {
            Name: "SwathWidth",
            Description: "The width of the sensor scan as the satellite moves along the ground track.",
            DataType: "INT",
            Unit: "Kilometers",
            Value: "2330",
          }
        ]
      }
    ]
  }
],



UMM Migration

None


Future Mappings

ISO 19115-1

An unlimited amount of platform keywords may be listed (Cardinality: 1..*)

Providing platform characteristics is optional. An unlimited amount of platform characteristics may be specified for a particular platform (Cardinality: 0..*). If platform characteristics are provided, all 5 sub-fields should be provided (Name, Description, DataType, Unit, Value) to meet CMR requirements.

SpecificationPathTypeNotes
ISO 19115-1


String

ISO 19115-1

 

UMM

Platforms: [
  {
    Type: "Earth Observation Satellites",
    ShortName: "Aqua",
    LongName: "Earth Observing System, Aqua",
    Instruments: [
      {
        ShortName: "MODIS",
        LongName: "Moderate-Resolution Imaging Spectroradiometer",  
        Characteristics: [
          {
            Name: "SwathWidth",
            Description: "The width of the sensor scan as the satellite moves along the ground track.",
            DataType: "INT",
            Unit: "Kilometers",
            Value: "2330",
          }
        ]
      }
    ]
  }
],

History

UMM Versioning

VersionDateWhat Changed
1.0.0
Initial Release

ARC Documentation

VersionDateWhat ChangedAuthor
1.05/16/18Recommendations/priority matrix transferred from internal ARC documentation to wiki spaceJeanne' le Roux

















  • No labels