Table of Contents | ||
---|---|---|
|
Element Description
The Temporal Extent element describes when data were acquired or collected.
Best Practices
Dates provided in CMR metadata should comply with the ISO 8601 Standard, which is an International Standard for the representation of dates and times.
There are three options in the UMM for describing the temporal extent of data: Single Date Time, Range Date Time and Periodic Date Time.
Using different temporal extent representations between collection and granule level metadata are allowed, as long as it makes logical sense. For example, Single Date Time could be used to describe temporal coverage at the granule level, whereas a Range Date Time may be used to describe temporal coverage at the collection level. It is important that the temporal extent at the collection level be in sync with the temporal extent provided in associated granule level metadata files.
Single Date Time
The Single Date Time element should be used if data were captured instantaneously (i.e. a single time stamp sufficiently describes the temporal extent of the data). For example, if a data file contains an image that was taken by a camera, the time stamp associated with the time the image was taken would be listed as the Single Date Time in the granule level metadata. Single Date Time may also be used in the collection level metadata if appropriate. If the exact time of data capture is known, it is strongly recommended that the time be included in the Single Date Time. If the exact time of data collection is unknown, it is okay to just provide a date. Multiple Single Date Times may be provided if necessary (cardinality 0..*).
Examples:
SingleDateTime: 2018-11-11T14:53:32Z
SingleDateTime: 2017-04-14T05:26:22Z
Range Date Time
The Range Date Time element should be used when a continuous time range is appropriate to describe the temporal extent of data. Range Date Time is composed of two sub-elements: Beginning Date Time and Ending Date Time, which describe the start and end time of a data file or a collection.
For completed data sets:
- It is required that an Ending Date Time be provided. The 'EndingDateTime' element should specify the ending date and time of the last available granule in the collection. In addition:
- The ‘Ends at Present Flag' element should be set to “false”. Setting the ‘Ends at Present Flag’ element to “false” tells the CMR that the ending time for the collection is in the past. Note: Ends at Present Flag is an optional element.
- The Collection Progress element should be set to “COMPLETE”
If data collection is ongoing,
- An Ending Date Time does not need to be provided. In addition:
- The ‘Ends at Present Flag’ element should be set to “true.” Setting the ‘Ends at Present Flag’ element to “true” tells the CMR that the ending time for the collection is present day, and thus eliminates the need to specify the Ending Date Time of the collection. This also eliminates the need to update the Ending Date Time in the metadata each time new data gets added to the collection.
- The Collection Progress element should be set to “ACTIVE”
Multiple RangeDateTimes may be provided if necessary (cardinality 0..*). It is recommended that multiple RangeDateTimes be used if there is a significant temporal gap present in the data.
Examples:
A satellite collected data from May 1, 2004 to February 10, 2008. A data product derived from this satellite provides monthly global averages of surface temperature. A monthly global average for February 2008 was not included in the data set since only 10 days of data were available in February.
RangeDateTime for the collection: | RangeDateTime for the first granule in the collection: |
---|---|
BeginningDateTime: 2004-05-01T00:00:00Z EndingDateTime: 2008-01-31T23:59:59Z | BeginningDateTime: 2004-05-01T00:00:00Z EndingDateTime: 2004-05-31T23:59:59Z |
Radar measurements were taken from a plane. One flight occurred each day from August 20, 2018 to August 31, 2018.
RangeDateTime for the collection: | RangeDateTime for the first granule in the collection: | RangeDateTime for the last granule in the collection: |
---|---|---|
BeginningDateTime: 2018-08-20T12:34:00Z EndingDateTime: 2018-08-31T10:01:02Z | BeginningDateTime: 2018-08-20T12:34:00Z EndingDateTime: 2018-08-20T16:50:52Z | BeginningDateTime: 2018-08-31T06:18:21Z EndingDateTime: 2018-08-31T10:01:02Z |
Periodic Date Time
For data that is collected in regular reoccurring intervals, the temporal extent can be described as a Periodic Date Time. Periodic Date Time is described via the below sub-elements. If Periodic Date Time is provided, all sub-elements are required:
Name: The name given to the recurring time period.
StartDate: The date (day and time) of the first occurrence of this regularly occurring period. This is when data collections begins for the entire collection. This also identifies the day of the month and time of the day when data collection starts for each reoccurring cycle.
EndDate: The date (day and time) of the last occurrence of this regularly occurring period. This is when data collection ends for the entire collection.
DurationUnit: The unit for the regularly reoccurring data collection period. In combination with DurationValue, this describes the length of time that data gets collected. This value must be selected from a controlled vocabulary list maintained in the UMM-Common schema. Options include: DAY, MONTH, YEAR
DurationValue: The number of DurationUnits comprising the regularly reoccurring data collection period. Together, DurationValue and DurationUnit describe the length of time that data gets collected.
PeriodCycleDurationUnit: The duration unit of one full cycle. The full cycle includes both the active data collection period as well as an inactive period. This value must be selected from a controlled vocabulary list maintained in the UMM-Common schema. Options include: DAY, MONTH, YEAR
PeriodCycleDurationValue: The number of CycleDurationUnits comprising one full cycle. Together, CycleDurationValue and CycleDurationUnit describe the length of a full cycle which includes both the active data collection period as well as an inactive period.
Examples:
Data for a field campaign are collected in December, January and February of each year. Data collection started in December 2013 and ended in February 2017.
Name: Winter_FieldCampaign
StartDate: 2013-12-01T00:00:00Z
EndDate: 2017-02-28T23:59:59Z
DurationUnit: MONTH
DurationValue: 3
PeriodCycleDurationUnit: YEAR
PeriodCycleDurationValue: 1
A sensor collected data every morning from 5 AM to 6 AM UTC.
Name: AM_Sensor_Daily
StartDate: 2000-04-01T05:00:00Z
EndDate: 2010-09-04T06:00:00Z
DurationUnit: DAY
DurationValue: 0.0417
PeriodCycleDurationUnit: DAY
PeriodCycleDurationValue: 1
For paleoclimate or geologic data, temporal coverage can be described via the Paleo Temporal Coverage elements. Paleo Temporal Coverage should be used to describe time frames earlier than 0001-01-01 (yyyy-mm-dd). Please see the Paleo Temporal Coverage wiki page for details.
Element Specification
Model | Element | Type | Constraints | Required? | Cardinality | Notes |
---|---|---|---|---|---|---|
UMM-Common | TemporalExtent/PrecisionOfSeconds | Integer | n/a | No | 0..1 | The precision (position in number of places to right of decimal point) of seconds used in measurement. |
UMM-Common | TemporalExtent/EndsAtPresentFlag | Boolean | n/a | No | 0..1 | Setting the Ends At Present Flag to 'True' indicates that a data collection currently ends at the present date. Setting the Ends at Present flag to 'True' eliminates the need to continuously update the Range Ending Time for collections where granules are continuously being added to the collection inventory. |
Choice of:
(1) SingleDateTime
If SingleDateTime is selected, the cardinality is 1..*
Model | Element | Type | Constraints | Required? | Cardinality | Notes |
---|---|---|---|---|---|---|
UMM-Common | TemporalExtent/SingleDateTime | dateTime | n/a | Yes, if applicable | 1 | Dates must comply with the ISO 8601 Standard. |
(2) RangeDateTime
If RangeDateTime is selected, the cardinality is 1..*
Model | Element | Type | Constraints | Required? | Cardinality | Notes |
---|---|---|---|---|---|---|
UMM-Common | TemporalExtent/RangeDateTime/BeginningDateTime | dateTime | n/a | Yes, if applicable | 1 | Dates must comply with the ISO 8601 Standard. |
UMM-Common | TemporalExtent/RangeDateTime/EndingDateTime | dateTime | n/a | No | 0..1 | An EndingDateTime must be provided at the collection level if the collection is complete. |
(3) PeriodicDateTime
If PeriodicDateTime is selected, the cardinality is 1..*
Model | Element | Type | Usable Valid Values | Constraints | Required? | Cardinality | Notes |
---|---|---|---|---|---|---|---|
UMM-Common | TemporalExtent/PeriodicDateTime/Name | String | n/a | 1 - 30 characters | Yes, if applicable | 1 | |
UMM-Common | TemporalExtent/PeriodicDateTime/StartDate | dateTime | n/a | n/a | Yes, if applicable | 1 | Dates must comply with the ISO 8601 Standard. |
UMM-Common | TemporalExtent/PeriodicDateTime/EndDate | dateTime | n/a | n/a | Yes, if applicable | 1 | Dates must comply with the ISO 8601 Standard. |
UMM-Common | TemporalExtent/PeriodicDateTime/DurationUnit | Enumeration | DAY MONTH YEAR | n/a | Yes, if applicable | 1 | |
UMM-Common | TemporalExtent/PeriodicDateTime/DurationValue | Integer | n/a | n/a | Yes, if applicable | 1 | |
UMM-Common | TemporalExtent/PeriodicDateTime/PeriodCycleDurationUnit | Enumeration | DAY MONTH YEAR | n/a | Yes, if applicable | 1 | |
UMM-Common | TemporalExtent/PeriodicDateTime/PeriodCycleDurationValue | Integer | n/a | n/a | Yes, if applicable | 1 |
Value needed for translations:
N/A
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).
Lucidchart rich-viewer true autofit true name Copy of Wiki Page Metadata Evaluation Workflow-1939-672ea43a width 1102 id 98e5dc28-3252-4209-953f-66f1378e1cf4 align Left height 299
Please see the expandable sections below for flowchart details.
Expand | ||
---|---|---|
| ||
Expand | ||
---|---|---|
| ||
Expand | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
ARC Automated Checks
|
Dialect Mappings
Expand | ||
---|---|---|
| ||
DIF 9 DIF 9 (Note: DIF-9 is being phased out and will no longer be supported after 2018) |
Expand | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
DIF 10
Choice of: (1) Single_DateTime If Single_DateTime is selected, the cardinality is 1..*
(2) Range_DateTime If Range_DateTime is selected, the cardinality is 1..*
(3) Periodic_DateTime If Periodic_DateTime is selected, the cardinality is 1..*
Value needed for translations: The following value is used to translate older versions of DIF (e.g. DIF 9, DIF 10.1) to the most current version of DIF (DIF10.3) if no valid value is provided in the older version of the record. Not provided - This value is auto-populated to any DateTime fields if no valid value is provided in the DateTime field at time of conversion to DIF 10.3. This value should not be used by metadata providers. Enumeration Mapping
Example Mapping
|
Expand | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ECHO 10
Choice of: (1) SingleDateTime If SingleDateTime is selected, the cardinality is 1..*
(2) RangeDateTime If RangeDateTime is selected, the cardinality is 1..*
(3) PeriodicDateTime If PeriodicDateTime is selected, the cardinality is 1..*
Enumeration Mapping
Example Mapping
|
Expand | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ISO 19115-2 MENDS
Enumeration/Code List Mapping
Example Mapping
|
Expand | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ISO 19115-2 SMAP
Enumeration/Code List Mapping
Example Mapping
|
UMM Migration
UMM Version 1.9.0 | Translation Direction | UMM Version 1.10.0 |
---|---|---|
PLANNED | ↔ | PLANNED |
IN WORK | ↔ | ACTIVE |
COMPLETE | ↔ | COMPLETE |
NOT APPLICABLE | ↔ | NOT APPLICABLE |
NOT PROVIDED | ↔ | NOT PROVIDED |
Any other value | → | NOT PROVIDED |
Future Mappings
Expand | ||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||
ISO 19115-1
|
History
UMM Versioning
Version | Date | What Changed |
---|---|---|
1.10.0 | Changes would be tracked here | |
1.9.0 |
ARC Documentation
Version | Date | What Changed | Author |
---|---|---|---|
1.0 | 8/17/18 | Recommendations/priority matrix transferred from internal ARC documentation to wiki space |