Element Description
The Temporal Extent element describes when the data for a granule 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.
The Data Product Development Guide for Data Producers offers the following guidance about time:
"The CF Conventions represent time as an integer or float, with the units attribute set to the time
unit since an epochal time, represented as YYYY-MM-DDThh:mm:ss (e.g., “seconds since 1993-01-
01T00:00:00Z”). Unless there is a strongly justifiable reason not to do so, use the UTC Time Zone
instead of alternative time zones.The date-time information in the file should adhere to the following guidelines (detailed in [26], Rec.
3.11):• Adopt the ISO 8601 standard [51] [52] for date-time information representation.
• If describing time intervals, the start time should appear before the end time.
• Date-time fields representing the temporal extent of a file’s data should appear before any
other date-time field in the file name.• All date-time fields should have the same format."
There are two options in the UMM at the granule level for describing the temporal extent of data: Range Date Time and Single 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.
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.
Examples:
BeginningDateTime: 2020-11-01T00:00:00Z
EndingDateTime: 2020-11-30T23:59:99Z
Element Specification
Choice of:
(1) SingleDateTime
If SingleDateTime is selected, the cardinality is 1..*
Model | Element | Type | Constraints | Required? | Cardinality | Notes |
---|---|---|---|---|---|---|
UMM-G | TemporalExtent/SingleDateTime | string | 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-G | TemporalExtent/RangeDateTime/BeginningDateTime | string | n/a | Yes, if applicable | 1 | Dates must comply with the ISO 8601 Standard. |
UMM-G | TemporalExtent/RangeDateTime/EndingDateTime | string | n/a | No | 0..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.
Dialect Mappings
ECHO 10
UMM Migration
None
History
UMM Versioning
Version | Date | What Changed |
---|---|---|
1.6.6 | 2024-05-01 | No changes were made for Temporal Extents during the transition from version 1.6.5 to 1.6.6. |
1.6.5 | 2023-08-23 | No changes were made for Temporal Extents during the transition from version 1.6.4 to 1.6.5. |
1.6.4 | 2021-10-06 | No changes were made for Temporal Extents during the transition from version 1.6.3 to 1.6.4. |
1.6.3 | 2021-05-03 | No changes were made for Temporal Extents during the transition from version 1.6.2 to 1.6.3. |
1.6.2 | 2021-04-21 | No changes were made for Temporal Extents during the transition from version 1.6.1 to 1.6.2. |
1.6.1 | 2020-06-05 | No changes were made for Temporal Extents during the transition from version 1.6 to 1.6.1. |
1.6 | 2019-11-04 | No changes were made for Temporal Extents during the transition from version 1.5 to 1.6. |
1.5 | 2019-01-30 | No changes were made for Temporal Extents during the transition from version 1.4 to 1.5 |
1.4 | 2018-08-01 | The UMM-G temporal EndingDateTime was made optional. |
ARC Documentation
Version | Date | What Changed | Author |
---|---|---|---|
1.0 | 2024-08-17 | Recommendations/priority matrix created in the wiki space |