Page History
Table of Contents | ||
---|---|---|
|
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://gcmdservices.gsfc.nasa.gov/static/kms/platforms/platforms.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:
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
Element Specification
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 (Name, Description, DataType, Unit, Value) are required.
Model | Element | Type | Usable Valid Values | Constraints | Required? | Cardinality |
---|---|---|---|---|---|---|
UMM-Common | Platform/Type | String | Platform Category Keywords | KMS controlled | No | 0..1 |
UMM-Common | Platform/ShortName | String | Platform Short_Name Keywords | KMS controlled | Yes | 1 |
UMM-Common | Platform/LongName | String | Platform Long_Name Keywords | KMS controlled | No | 0..1 |
UMM-Common | Platform/Characteristics/Name | String | n/a | Minimum # characters: 1 Maximum # characters: 80 | Yes | 1 |
UMM-Common | Platform/Characteristics/Description | String | n/a | Minimum # characters: 1 Maximum # characters: 2048 | Yes | 1 |
UMM-Common | Platform/Characteristics/DataType | Enumeration | STRING FLOAT INT BOOLEAN DATE TIME DATETIME DATE_STRING TIME_STRING DATETIME_STRING | n/a | Yes | 1 |
UMM-Common | Platform/Characteristics/Unit | String | n/a | Minimum # characters: 1 Maximum # characters: 20 | Yes | 1 |
UMM-Common | Platform/CCharacteristics/Value | String | n/a | Minimum # characters: 1 Maximum # characters: 80 | Yes | 1 |
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 platforms by software should use "undefined" until it can be confirmed whether "Not Applicable" or another value should be used. "Undefined" can also be used in cases where the platform is unknown. This value should not be used by metadata providers.
ARC Priority Matrix
Priority Categorization | Justification |
---|---|
This element is categorized as highest priority when:
| |
This element is categorized as medium priority when:
| |
This element is categorized as low priority when:
| |
The element is provided, and follows all applicable criteria specified in the best practices section above. |
Dialect Mappings
Expand | ||
---|---|---|
| ||
DIF 9 (Note: DIF-9 is being phased out and will no longer be supported after 2018) |
Expand | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
DIF 10 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 (Name, Description, DataType, Unit, Value) are required.
Example Mapping
|
Expand | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ECHO 10 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 (Name, Description, DataType, Unit, Value) are required.
Example Mapping
|
Expand | ||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||
ISO 19115-2 MENDS 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.
Example Mapping
|
Expand | ||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||
ISO 19115-2 SMAP 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.
Example Mapping
|
UMM Migration
None
Future Mappings
Expand | ||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||
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.
|
History
UMM Versioning
Version | Date | What Changed |
---|---|---|
1.0.0 | Initial Release |
ARC Documentation
Version | Date | What Changed | Author |
---|---|---|---|
1.0 | 5/14/18 | Recommendations/priority matrix transferred from internal ARC documentation to wiki space | Jeanne' le Roux |