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

Compare with Current View Page History

« Previous Version 7 Next »

Element Description

The archive and distribution information main element allows data providers to provide users information of what is available for downloading when they initially looking at a collection. The end users get information such as the average downloadable file size, format, mime type, checksum, etc., an estimate of the collections entire downloadable file size, etc.

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.


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

Instrument is an optional metadata element, however, it is strongly recommended that it be provided when possible. Multiple Instruments may be listed if necessary (Cardinality: 0..*).

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

ArchiveAndDistributionInformation/ FileArchiveInformation/

Format
String
1 - 80 characters
Yes1
UMM-CommonArchiveAndDistributionInformation/ FileArchiveInformation/ FormatTypeString

Native

Supported

n/aNo0..1
UMM-CommonArchiveAndDistributionInformation/ FileArchiveInformation/ AverageFileSizeDecimal



Yes, if TotalCollectionFileSizeBeginDate is used.0..1
UMM-Common

ArchiveAndDistributionInformation/ FileArchiveInformation/ AverageFileSizeUnit

String

KB

MB

GB

TB

PB

NA


n/a

Yes, if AverageFileSize is used.
0..1
UMM-Common

ArchiveAndDistributionInformation/ FileArchiveInformation/ TotalCollectionFileSize

Decimal

No0..1Either use TotalCollectionFileSize or TotalCollectiopnFileSizeBeginDate
UMM-Common

ArchiveAndDistributionInformation/ FileArchiveInformation/ TotalCollectionFileSizeUnit

Enumeration

KB

MB

GB

TB

PB

NA

n/aYes, if TotalCollectionFileSize is used0..1
UMM-Common

ArchiveAndDistributionInformation/ FileArchiveInformation/ TotalCollectionFileSizeBeginDate

Date

No0..1Either use TotalCollectionFileSize or TotalCollectiopnFileSizeBeginDate
UMM-Common

ArchiveAndDistributionInformation/ FileArchiveInformation/ Description

Stringn/a

1 - 1024 characters


No0..1

ArchiveAndDistributionInformation/

FileDistributionInformation/Format

String
1 - 80 charactersYes1

ArchiveAndDistributionInformation/

FileDistributionInformation/ FormatType

String

Native

Supported


No0..1
UMM-Common

ArchiveAndDistributionInformation/ FileDistributionInformation/

Media
Stringn/a

1 - 80 characters


No0..1
UMM-CommonArchiveAndDistributionInformation/ FileDistributionInformation/ AverageFileSizeDecimaln/an/aYes, if TotalCollectionFileSizeBeginDate is used.0..1
UMM-Common

ArchiveAndDistributionInformation/ FileDistributionInformation/ AverageFileSizeUnit

Enumeration

KB

MB

GB

TB

PB

NA


Yes, if AverageFileSize is used.
0..1
UMM-Common

ArchiveAndDistributionInformation/ FileDistributionInformation/ TotalCollectionFileSize

Decimaln/a
No0..1Either use TotalCollectionFileSize or TotalCollectiopnFileSizeBeginDate
UMM-Common

ArchiveAndDistributionInformation/ FileDistributionInformation/ TotalCollectionFileSizeUnit

Enumeration

KB

MB

GB

TB

PB

NA

n/aYes, if TotalCollectionFileSize is used0..1
UMM-Common

ArchiveAndDistributionInformation/ FileDistributionInformation/ TotalCollectionFileSizeBeginDate

Date

No0..1Either use TotalCollectionFileSize or TotalCollectiopnFileSizeBeginDate
UMM-Common

ArchiveAndDistributionInformation/ FileDistributionInformation/ Description

Stringn/a

1 - 1024 characters


No0..1
UMM-Common

Fees

Stringn/a

1 - 255 characters


No0..1


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.
  • The specific instrument must be unique within the collection. The uniqueness is established by combining the instrument short name along with its characteristic's name.
  • The instrument short name must match with what is in the KMS.
  • If a granule has an instrument short name in it, it must match to one that is defined in the collection.
  • If removing an instrument from a collection, none of its granules can reference that instrument's short name.

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

  • Instrument Short Name
    • If no value is provided, return is: "This is a required field. Recommend providing at least one Instrument Short Name relevent to this data set. Instrument Short Name is GCMD controlled and should be selected from the following list: https://gcmdservices.gsfc.nasa.gov/static/kms/instruments/instruments.csv?ed_wiki_keywords_page"
    • If the provided value is in the incorrect hierarchy position, return is: "<provided value> is in the incorrect position of the project keyword hierarchy."
    • If the provided value does not conform to GCMD, return is: "<provided value> does not conform to GCMD."
  • Instrument Long Name
    • If no value is provided, return is: "Recommend providing at least one Instrument Long name relevent to this data set. Instrument Long Name is GCMD controlled and should be selected from the following list: https://gcmdservices.gsfc.nasa.gov/static/kms/instruments/instruments.csv?ed_wiki_keywords_page"

    • If the provided value is in the incorrect hierarchy position, return is: "<provided value> is in the incorrect position of the project keyword hierarchy."
    • If the provided value does not conform to GCMD, return is: "<provided value> does not conform to GCMD."

Dialect Mappings

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

DIF 10

Instrument is a required metadata element. At least 1 Instrument Keyword must be provided under each Platform. Multiple Instruments may be listed if necessary (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.

UMM-C ElementPathTypeUsable Valid ValuesConstraintsRequired in DIF 10?CardinalityNotes
Platforms/Instruments/ShortName/DIF/Platform/Instrument/Short_Name
StringInstrument Short_Name Keywords

KMS controlled

Yes1For each instrument provided, a short name is required.
Platforms/Instruments/LongName/DIF/Platform/Instrument/Long_NameStringInstrument Long_Name Keywords

KMS controlled

No0..1It is highly recommended that a long name be provided if one is available in KMS.
Platforms/Instruments/Technique/DIF/Platform/Instrument/TechniqueString
1 - 2048 charactersNo0..1
Platforms/Instruments/NumberOfInstruments/DIF/Platform/Instrument/NumberOfSensorsInteger
n/aNo0..1
Platforms/Instruments/Characteristics/Name/DIF/Platform/Instrument/Characteristics/NameString
1 - 80 charactersYes, if applicable1Only required if a characteristic is provided.Providing characteristics is optional.
Platforms/Instruments/Characteristics/Description/DIF/Platform/Instrument/Characteristics/DescriptionString
1 - 2048 charactersYes, if applicable1Only required if a characteristic is provided.Providing characteristics is optional.
Platforms/Instruments/Characteristics/DataType/DIF/Platform/Instrument/Characteristics/DataTypeString
1 - 80 charactersYes, if applicable1Only required if a characteristic is provided.Providing characteristics is optional.
Platforms/Instruments/Characteristics/Unit/DIF/Platform/Instrument/Characteristics/UnitString
1 - 20 charactersYes, if applicable1Only required if a characteristic is provided.Providing characteristics is optional.
Platforms/Instruments/Characteristics/Value/DIF/Platform/Instrument/Characteristics/ValueString
1 - 80 charactersYes, if applicable1Only required if a characteristic is provided.Providing characteristics is optional.
Platforms/Instruments/OperationalModes/DIF/Platform/Instrument/OperationalModeString
1 - 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

Instrument is an optional metadata element, however, it is strongly recommended that it be provided when possible. Multiple Instruments may be listed if necessary (Cardinality: 0..*).

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.

UMM-C ElementPathTypeUsable Valid ValuesConstraintsRequired in ECHO10?CardinalityNotes
Platforms/Instruments/ShortName/Collection/Platforms/Platform/Instruments/Instrument/ShortNameStringInstrument Short_Name Keywords

KMS controlled

Yes1For each instrument provided, a short name is required.
Platforms/Instruments/LongName/Collection/Platforms/Platform/Instruments/Instrument/LongNameStringInstrument Long_Name Keywords

KMS controlled

No0..1It is highly recommended that a long name be provided if one is available in KMS.
Platforms/Instruments/TechniqueCollection/Platforms/Platform/Instruments/Instrument/TechniqueString
1 - 2048 charactersNo0..1
Platforms/Instruments/NumberOfInstrumentsCollection/Platforms/Platform/Instruments/Instrument/NumberOfSensorsInteger
n/aNo0..1
Platforms/Instruments/Characteristics/Name/Collection/Platforms/Platform/Instruments/Instrument/Characteristics/Characteristic/NameString
1 - 80 charactersYes, if applicable1Only required if a characteristic is listed. Providing characteristics is optional.
Platforms/Instruments/Characteristics/Description/Collection/Platforms/Platform/Instruments/Instrument/Characteristics/Characteristic/DescriptionString
1 - 2048 charactersYes, if applicable1Only required if a characteristic is listed. Providing characteristics is optional.
Platforms/Instruments/Characteristics/DataType/Collection/Platforms/Platform/Instruments/Instrument/Characteristics/Characteristic/DataType String
1 - 80 charactersYes, if applicable1Only required if a characteristic is listed. Providing characteristics is optional.
Platforms/Instruments/Characteristics/Unit/Collection/Platforms/Platform/Instruments/Instrument/Characteristics/Characteristic/UnitString
1 - 20 charactersYes, if applicable1Only required if a characteristic is listed. Providing characteristics is optional.
Platforms/Instruments/Characteristics/Value/Collection/Platforms/Platforms/Platform/Instruments/Instrument/Characteristics/Characteristic/ValueString
1 - 80 charactersYes, if applicable1Only required if a characteristic is listed. Providing characteristics is optional.
Platforms/Instruments/OperationalModes/Collection/Platforms/Platform/Instruments/Instrument/OperationModes/OperationModeString
1 - 20 charactersNo0..*


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

Instrument is an optional metadata element, however, it is strongly recommended that it be provided when possible. Multiple Instruments may be listed if necessary (Cardinality: 0..*).

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.

UMM-C ElementPathTypeNotes
Platforms/Instruments/ShortName

/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 under the 'Short_Name' column. 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.

Platforms/Instruments/LongName

/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 under the 'Long_Name' column.
Platforms/Instruments/Technique/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.
Platforms/Instruments/NumberOfInstrumentsWhen translating to UMM-C the number of instruments is counted. The number is not translated to ISO 19115-2 MENDS
Corresponds to the UMM field Platforms/Instruments/NumberOfInstruments.

/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 elementchoosing 'instrumentInformation' indicates to CMR that the instrument characteristic elements should be mapped.
Platforms/Instruments/Characteristics/Name/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.
Platforms/Instruments/Characteristics/Description/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.
Platforms/Instruments/Characteristics/DataType/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)

Platforms/Instruments/Characteristics/Unit/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.
Platforms/Instruments/Characteristics/Value/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.
Platforms/Instruments/OperationalModes

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

gmi:MI_Metadata/gmi:acquisitionInformation/gmi:MI_AcquisitionInformation/gmi:instrument/eos:EOS_Instrument/ gmi:mountedOn xlink:href='<insert unique platform 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

<gmi:MI_Metadata>
  ...
  <gmi:acquisitionInformation>
    <gmi:MI_AcquisitionInformation>
      <gmi:instrument>

        <eos:EOS_Instrument id="dfdaa96ba-483d-4e63-86ad-5dfd0eedf496">
          <gmi:identifier>
            <gmd:MD_Identifier>
              <gmd:code>
                <gco:CharacterString>MODIS</gco:CharacterString>
              </gmd:code>
              <gmd:codeSpace>
                <gco:CharacterString>gov.nasa.esdis.umm.instrumentshortname</gco:CharacterString>
              </gmd:codeSpace>
              <gmd:description>
                <gco:CharacterString>Moderate-Resolution Imaging Spectroradiometer</gco:CharacterString>
              </gmd:description>
            </gmd:MD_Identifier>
          </gmi:identifier>
          <gmi:type>
            <gco:CharacterString>Broadband scanning radiometry</gco:CharacterString>
          </gmi:type>
          <gmi:mountedOn xlink:href="#d36bb8fb0-d827-4fd1-a2e9-5db6778abddc"/>
          <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/eosCodelists.xml#EOS_AdditionalAttributeTypeCode" codeListValue="instrumentInformation">instrumentInformation</eos:EOS_AdditionalAttributeTypeCode>
                      </eos:type>
                      <eos:name>
                        <gco:CharacterString>SwathWidth</gco:CharacterString>
                      </eos:name>
                      <eos:description>
                        <gco:CharacterString>The width of the sensor scan as the satellite moves along the ground track.</gco:CharacterString>
                      </eos:description>
                      <eos:dataType>
                        <eos:EOS_AdditionalAttributeDataTypeCode codeList="https://cdn.earthdata.nasa.gov/iso/resources/Codelist/eosCodelists.xml#EOS_AdditionalAttributeDataTypeCode" codeListValue="INT">INT</eos:EOS_AdditionalAttributeDataTypeCode>
                      </eos:dataType>
                      <eos:parameterUnitsOfMeasure>
                        <gco:CharacterString>Kilometers</gco:CharacterString>
                      </eos:parameterUnitsOfMeasure>
                    </eos:EOS_AdditionalAttributeDescription>
                  </eos:reference>
                  <eos:value>
                    <gco:CharacterString>2330</gco:CharacterString>
                  </eos:value>
                </eos:AdditionalAttribute>
              </eos:AdditionalAttributes>
            </gco:Record>
          </eos:otherProperty>
        </eos:EOS_Instrument>
      </gmi:instrument>
      <gmi:platform>
        <eos:EOS_Platform id="d36bb8fb0-d827-4fd1-a2e9-5db6778abddc">
          <gmi:identifier>
            <gmd:MD_Identifier>
              <gmd:code>
                <gco:CharacterString>Aqua</gco:CharacterString>
              </gmd:code>
              <gmd:codeSpace>
                <gco:CharacterString>gov.nasa.esdis.umm.platformshortname</gco:CharacterString>
              </gmd:codeSpace>
              <gmd:description>
                <gco:CharacterString>Earth Observing System, Aqua</gco:CharacterString>
              </gmd:description>
            </gmd:MD_Identifier>
          </gmi:identifier>
          <gmi:description>
            <gco:CharacterString>Earth Observation Satellites</gco:CharacterString>
          </gmi:description>
          <gmi:instrument xlink:href="#dfdaa96ba-483d-4e63-86ad-5dfd0eedf496"/>
        </eos:EOS_Platform>
      </gmi:platform>
    </gmi:MI_AcquisitionInformation>
  </gmi:acquisitionInformation>
</gmi:MI_Metadata>

UMM

Platforms: [
  {
    Type: "Earth Observation Satellites",
    ShortName: "Aqua",
    LongName: "Earth Observing System, Aqua",
    Instruments: [
      {
        ShortName: "MODIS",
        LongName: "Moderate-Resolution Imaging Spectroradiometer",
        Technique: "Broadband scanning radiometry", 
        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

Instrument is an optional metadata element, however, it is strongly recommended that it be provided when possible. Multiple Instruments may be listed if necessary (Cardinality: 0..*).

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.

UMM-C ElementPathTypeNotes
Platforms/Instruments/ShortName

/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 under the 'Short_Name' column. 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.


Platforms/Instruments/LongName

/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 under the 'Long_Name' column.
Platforms/Instruments/Technique/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.
Platforms/Instruments/NumberOfInstrumentsWhen translating to UMM-C the number of instruments is counted. The number is not translated to ISO 19115-2 MENDS

Corresponds to the UMM field Platforms/Instruments/NumberOfInstruments.

/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 elementchoosing 'instrumentInformation' indicates to CMR that the instrument characteristic elements should be mapped.
Platforms/Instruments/Characteristics/Name/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.
Platforms/Instruments/Characteristics/Description/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.
Platforms/Instruments/Characteristics/DataType/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)

Platforms/Instruments/Characteristics/Unit/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.
Platforms/Instruments/Characteristics/Value/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.
Platforms/Instruments/OperationalModes

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

/gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmi:acquisitionInformation/gmi:MI_AcquisitionInformation/gmi:instrument/eos:EOS_Instrument/ gmi:mountedOn xlink:href='<insert unique platform 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

<gmd:DS_Series>
<gmd:seriesMetadata>
<gmi:MI_Metadata>
  ...
  <gmi:acquisitionInformation>
    <gmi:MI_AcquisitionInformation>
      <gmi:instrument>

        <eos:EOS_Instrument id="dfdaa96ba-483d-4e63-86ad-5dfd0eedf496">
          <gmi:identifier>
            <gmd:MD_Identifier>
              <gmd:code>
                <gco:CharacterString>MODIS</gco:CharacterString>
              </gmd:code>
              <gmd:codeSpace>
                <gco:CharacterString>gov.nasa.esdis.umm.instrumentshortname</gco:CharacterString>
              </gmd:codeSpace>
              <gmd:description>
                <gco:CharacterString>Moderate-Resolution Imaging Spectroradiometer</gco:CharacterString>
              </gmd:description>
            </gmd:MD_Identifier>
          </gmi:identifier>
          <gmi:type>
            <gco:CharacterString>Broadband scanning radiometry</gco:CharacterString>
          </gmi:type>
          <gmi:mountedOn xlink:href="#d36bb8fb0-d827-4fd1-a2e9-5db6778abddc"/>
          <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/eosCodelists.xml#EOS_AdditionalAttributeTypeCode" codeListValue="instrumentInformation">instrumentInformation</eos:EOS_AdditionalAttributeTypeCode>
                      </eos:type>
                      <eos:name>
                        <gco:CharacterString>SwathWidth</gco:CharacterString>
                      </eos:name>
                      <eos:description>
                        <gco:CharacterString>The width of the sensor scan as the satellite moves along the ground track.</gco:CharacterString>
                      </eos:description>
                      <eos:dataType>
                        <eos:EOS_AdditionalAttributeDataTypeCode codeList="https://cdn.earthdata.nasa.gov/iso/resources/Codelist/eosCodelists.xml#EOS_AdditionalAttributeDataTypeCode" codeListValue="INT">INT</eos:EOS_AdditionalAttributeDataTypeCode>
                      </eos:dataType>
                      <eos:parameterUnitsOfMeasure>
                        <gco:CharacterString>Kilometers</gco:CharacterString>
                      </eos:parameterUnitsOfMeasure>
                    </eos:EOS_AdditionalAttributeDescription>
                  </eos:reference>
                  <eos:value>
                    <gco:CharacterString>2330</gco:CharacterString>
                  </eos:value>
                </eos:AdditionalAttribute>
              </eos:AdditionalAttributes>
            </gco:Record>
          </eos:otherProperty>
        </eos:EOS_Instrument>
      </gmi:instrument>

      <gmi:platform>
        <eos:EOS_Platform id="d36bb8fb0-d827-4fd1-a2e9-5db6778abddc">
          <gmi:identifier>
            <gmd:MD_Identifier>
              <gmd:code>
                <gco:CharacterString>Aqua</gco:CharacterString>
              </gmd:code>
              <gmd:codeSpace>
                <gco:CharacterString>gov.nasa.esdis.umm.platformshortname</gco:CharacterString>
              </gmd:codeSpace>
              <gmd:description>
                <gco:CharacterString>Earth Observing System, Aqua</gco:CharacterString>
              </gmd:description>
            </gmd:MD_Identifier>
          </gmi:identifier>
          <gmi:description>
            <gco:CharacterString>Earth Observation Satellites</gco:CharacterString>
          </gmi:description>
          <gmi:instrument xlink:href="#dfdaa96ba-483d-4e63-86ad-5dfd0eedf496"/>
        </eos:EOS_Platform>
      </gmi:platform>
    </gmi:MI_AcquisitionInformation>
  </gmi:acquisitionInformation>
</gmi:MI_Metadata>
</gmd:seriesMetadata>
</gmd:DS_Series>

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

Instrument is an optional metadata element, however, it is strongly recommended that it be provided when possible. Multiple Instruments may be listed if necessary (Cardinality: 0..*).

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.

UMM-C ElementPathTypeNotes
Platforms/Instruments/ShortName

/mdb:MD_Metadata/mdb:acquisitionInformation/mac:MI_AcquisitionInformation/mac:instrument/mac:MI_Instrument id="<insert unique instrument ID here>"/mac:identifier/mcc:MD_Identifier/mcc:code/gco:CharacterString

with

/mdb:MD_Metadata/mdb:acquisitionInformation/mac:MI_AcquisitionInformation/mac:instrument/mac:MI_Instrument id="<insert unique instrument ID here>"/mac:identifier/mcc:MD_Identifier/mcc: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 under the 'Short_Name' column. 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.

Platforms/Instruments/LongName

/mdb:MD_Metadata/mdb:acquisitionInformation/mac:MI_AcquisitionInformation/mac:instrument/mac:MI_Instrument id="<insert unique instrument ID here>"/mac:identifier/mcc:MD_Identifier/mcc:description/gco:CharacterString

StringCorresponds to the UMM field Platforms/Instruments/LongName. A list of valid instrument long names can be found in the KMS under the 'Long_Name' column.
Platforms/Instruments/Technique/mdb:MD_Metadata/mdb:acquisitionInformation/mac:MI_AcquisitionInformation/mac:instrument/mac:MI_Instrument id="<insert unique instrument ID here>"mac:type/gco:CharacterString StringCorresponds to the UMM field Platforms/Instruments/Technique.
Platforms/Instruments/NumberOfInstrumentsWhen translating to UMM-C the number of instruments is counted. The number is not translated to ISO 19115-2 MENDS
Corresponds to the UMM field Platforms/Instruments/NumberOfInstruments.

/mdb:MD_Metadata/mdb:acquisitionInformation/mac:MI_AcquisitionInformation/mac:instrument/mac:MI_Instrument id="<insert unique instrument ID here> "/mac: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 elementchoosing 'instrumentInformation' indicates to CMR that the instrument characteristic elements should be mapped.
Platforms/Instruments/Characteristics/Name/mdb:MD_Metadata/mdb:acquisitionInformation/mac:MI_AcquisitionInformation/mac:instrument/mac:MI_Instrument id="<insert unique instrument ID here> "/mac:otherProperty/gco:Record/eos:AdditionalAttributes/eos:AdditionalAttribute/eos:reference/eos:EOS_AdditionalAttributeDescription/ eos:name/gco:CharacterStringStringCorresponds to the UMM field Platforms/Instruments/Characteristics/Name.
Platforms/Instruments/Characteristics/Description/mdb:MD_Metadata/mdb:acquisitionInformation/mac:MI_AcquisitionInformation/mac:instrument/mac:MI_Instrument id="<insert unique instrument ID here> "/mac:otherProperty/gco:Record/eos:AdditionalAttributes/eos:AdditionalAttribute/eos:reference/eos:EOS_AdditionalAttributeDescription/ eos:description/gco:CharacterStringStringCorresponds to the UMM field Platforms/Instruments/Characteristics/Description.
Platforms/Instruments/Characteristics/DataType/mdb:MD_Metadata/mdb:acquisitionInformation/mac:MI_AcquisitionInformation/mac:instrument/mac:MI_Instrument id="<insert unique instrument ID here> "/mac: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)

Platforms/Instruments/Characteristics/Unit/mdb:MD_Metadata/mdb:acquisitionInformation/mac:MI_AcquisitionInformation/mac:instrument/mac:MI_Instrument id="<insert unique instrument ID here> "/mac:otherProperty/gco:Record/eos:AdditionalAttributes/eos:AdditionalAttribute/eos:reference/eos:EOS_AdditionalAttributeDescription/ eos:parameterUnitsOfMeasure/gco:CharacterStringStringCorresponds to the UMM field Platforms/Instruments/Characteristics/Unit.
Platforms/Instruments/Characteristics/Value/mdb:MD_Metadata/mdb:acquisitionInformation/mac:MI_AcquisitionInformation/mac:instrument/mac:MI_Instrument id="<insert unique instrument ID here> "/mac:otherProperty/gco:Record/eos:AdditionalAttributes/eos:AdditionalAttribute/eos:value/gco:CharacterStringStringCorresponds to the UMM field Platforms/Instruments/Characteristics/Value.
Platforms/Instruments/OperationalModes

/mdb:MD_Metadata/mdb:acquisitionInformation/mac:MI_AcquisitionInformation/mac:instrument/mac:MI_Instrument id="<insert unique instrument ID here> "/mac:otherProperty/gco:Record/eos:AdditionalAttributes/eos:AdditionalAttribute/eos:reference/eos:EOS_AdditionalAttributeDescription/ eos:name/gco:CharacterString="OperationalMode"

and

/mdb:MD_Metadata/mdb:acquisitionInformation/mac:MI_AcquisitionInformation/mac:instrument/mac:MI_Instrument id="<insert unique instrument ID here> "/mac: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.

/mdb:MD_Metadata/mdb:acquisitionInformation/mac:MI_AcquisitionInformation/mac:instrument/mac:MI_Instrument id="<insert unique instrument ID here>/gmi:mountedOn xlink:href='<insert unique platform 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-1

<mdb:MD_Metadata>
  ...
  <mdb:acquisitionInformation>
    <mac:MI_AcquisitionInformation>
      <mac:instrument>
        <mac:MI_Instrument id="dfdaa96ba-483d-4e63-86ad-5dfd0eedf496">
          <mac:identifier>
            <mcc:MD_Identifier>
              <mcc:code>
                <gco:CharacterString>MODIS</gco:CharacterString>
              </mcc:code>
              <mcc:codeSpace>
                <gco:CharacterString>gov.nasa.esdis.umm.instrumentshortname</gco:CharacterString>
              </mcc:codeSpace>
              <mcc:description>
                <gco:CharacterString>Moderate-Resolution Imaging Spectroradiometer</gco:CharacterString>
              </mcc:description>
            </mcc:MD_Identifier>
          </mac:identifier>
          <mac:type>
            <gco:CharacterString>Broadband scanning radiometry</gco:CharacterString>
          </mac:type>
          <mac:mountedOn xlink:href="#d36bb8fb0-d827-4fd1-a2e9-5db6778abddc"/>
          <mac: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/eosCodelists.xml#EOS_AdditionalAttributeTypeCode" codeListValue="instrumentInformation">instrumentInformation</eos:EOS_AdditionalAttributeTypeCode>
                      </eos:type>
                      <eos:name>
                        <gco:CharacterString>SwathWidth</gco:CharacterString>
                      </eos:name>
                      <eos:description>
                        <gco:CharacterString>The width of the sensor scan as the satellite moves along the ground track.</gco:CharacterString>
                      </eos:description>
                      <eos:dataType>
                        <eos:EOS_AdditionalAttributeDataTypeCode codeList="https://cdn.earthdata.nasa.gov/iso/resources/Codelist/eosCodelists.xml#EOS_AdditionalAttributeDataTypeCode" codeListValue="INT">INT</eos:EOS_AdditionalAttributeDataTypeCode>
                      </eos:dataType>
                      <eos:parameterUnitsOfMeasure>
                        <gco:CharacterString>Kilometers</gco:CharacterString>
                      </eos:parameterUnitsOfMeasure>
                    </eos:EOS_AdditionalAttributeDescription>
                  </eos:reference>
                  <eos:value>
                    <gco:CharacterString>2330</gco:CharacterString>
                  </eos:value>
                </eos:AdditionalAttribute>
              </eos:AdditionalAttributes>
            </gco:Record>
          </mac:otherProperty>
        </mac:MI_Instrument>
      </mac:instrument>
      <mac:platform>
        <mac:MI_Platform id="d36bb8fb0-d827-4fd1-a2e9-5db6778abddc">
          <mac:identifier>
            <mcc:MD_Identifier>
              <mcc:code>
                <gco:CharacterString>Aqua</gco:CharacterString>
              </mcc:code>
              <mcc:codeSpace>
                <gco:CharacterString>gov.nasa.esdis.umm.platformshortname</gco:CharacterString>
              </mcc:codeSpace>
              <mcc:description>
                <gco:CharacterString>Earth Observing System, Aqua</gco:CharacterString>
              </mcc:description>
            </mcc:MD_Identifier>
          </mac:identifier>
          <mac:description>
            <gco:CharacterString>Earth Observation Satellites</gco:CharacterString>
          </mac:description>
          <mac:instrument xlink:href="#dfdaa96ba-483d-4e63-86ad-5dfd0eedf496"/>
        </mac:MI_Platform>
      </mac:platform>
    </mac:MI_AcquisitionInformation>
  </mdb:acquisitionInformation>
</mdb:MD_Metadata>

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.13.0FutureThis element was added to the UMM-C specification.

ARC Documentation

VersionDateWhat ChangedAuthor
1.05/16/18Recommendations/priority matrix transferred from internal ARC documentation to wiki space
  • No labels