Page History

Element Description

The platform elements enable the specification of platforms used to collect the data available in the dataset. Platforms provided in CMR metadata must be chosen from a controlled keyword hierarchy maintained in the Keyword Management System (KMS). A list of valid platform keywords can be found here: https://gcmdservicesgcmd.gsfcearthdata.nasa.gov/statickms/kmsconcepts/platformsconcept_scheme/platforms.?format=csv?

Optionally, attributes specific to the platform (such as equator crossing time, inclination angle, orbital period, 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

Platform keywords are important for the discovery of data. All relevant platforms should be listed for each dataset. It is preferred that more specific platform keyword terms be chosen from the KMS when available. For example, if data were collected from the NASA DC-8 aircraft, it is preferred that "NASA DC-8" be listed as the platform as opposed to the more generic "AIRCRAFT" keyword. If a particular platform 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 platform keywords. Platform 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 platform short name specified in the KMS should not be provided in the platform 'long name' field in the metadata. When listing platforms, a platform short name will always be required. While platform long names are not required, it is highly encouraged that long names be provided if one is listed in the KMS. Many platform short 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. Platform keywords are not case sensitive.

It is recommended that platform keywords be assigned in a consistent manner. For example, if data for several collections were collected by the "LANDSAT-8" satellite, it is recommended that the metadata for all of those collections list "LANDSAT-8" as the platform short name. Providing "LANDSAT-8" as the platform in some records, but the more generic "LANDSAT" as the platform 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 a platform for a dataset, "Not Applicable" is an accepted value.     

Examples (ShortName > LongName):

Terra > Earth Observing System, Terra (AM-1)

METOP-A > Meteorological Operational Satellite - A

VIC-LSM > Variable Infiltration Capacity (VIC) Land Surface Model

MESONET > Mesoscale Meteorological Network

BE-200 > Beechcraft King Air BE-200

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 value is given. This is needed partly because the CMR still allows a non UMM compliant record to be ingested with warnings.

NOT PROVIDED  - DIF 10 records found to be missing platforms by software will be automatically assigned a value of "Not Provided". It should then be confirmed whether a platform 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.

Dialect Mappings

Dialect Mappings

Example Mapping

<Platform>
  <Type>Earth Observation Satellites</Type>
  <Short_Name>ICESat</Short_Name>
  <Long_Name>Ice, Cloud and Land Elevation Satellite</LongName>
  <Characteristics>
    <Name>OrbitInclination</Name>
    <Description>The angle between the orbit plane and the Earth's equatorial plane.</Description>
    <DataType>FLOAT</DataType>
    <Unit>Degrees</Unit>
    <Value>94.0</Value>
  </Characteristics>
............
</Platform>

Platforms: [
  {
    Type: "Earth Observation Satellites",
    ShortName: "ICESat",
    LongName: "Ice, Cloud and Land Elevation Satellite",
    Characteristics: [
      {
        Name: "OrbitInclination",
        Description: "The

<Platform>
  <Type>Earth Observation Satellites</Type>
  <Short_Name>ICESat</Short_Name>
  <Long_Name>Ice, Cloud and Land Elevation Satellite</LongName>
  <Characteristics>
    <Name>OrbitInclination</Name>
    <Description>The angle between the orbit plane and the Earth's equatorial plane.</Description>",
    <DataType>FLOAT</DataType>
    DataType: "FLOAT",
     <Unit>Degrees</Unit>
    <Value>94.0</Value>
  </Characteristics>
............
</Platform>

Platforms: [
  {
    Type: "Earth Observation Satellites",
    ShortName: "ICESat",
    LongName: "Ice, Cloud and Land Elevation Satellite",
    Characteristics: [
      {
        Name: "OrbitInclination",
        Description: "The angle between the orbit plane and the Earth's equatorial plane.",
        DataType: "FLOAT",
        Unit: "Degrees",
        Value: "94.0"
      }
    ]
    .............
  }
]

Unit: "Degrees",
        Value: "94.0"
      }
    ]
    .............
  }
]