code-geek/dgf-playground

B2.2.19b: STAC: Provide a value of “Feature” in the STAC ‘type’ element and the version of STAC the Item implements in the ‘stac_version’ element. [DS + DE]

B2.2.18b STAC: Provide the id of the associated STAC Collection in the ‘collection’ element. [DS + DE]

B2.2.18a UMM: The Collection Reference identifies the collection to which the granule belongs. This is done by providing the collection's Short Name and Version Id, or the collection's Entry Title in the ‘CollectionReference’ element. [DS] More details can be found here: https://wiki.earthdata.nasa.gov/display/CMR/Collection+Reference

B2.2.17b STAC: Provide the date the Item record was created using ‘properties > created’ https://github.com/radiantearth/stac-api-spec/blob/main/stac-spec/item-spec/common-metadata.md#date-and-time [DS + DE]

B2.2.17a UMM: At least one provider date is required for granule metadata in the CMR. The ‘ProviderDates’ element presents dates associated with changes made to the granule in the database where it is stored. The Provider Dates include the date the granule was created, inserted, or updated in its database, and the date the granule metadata will be deleted from the CMR. It is highly recommended that the ‘Create’ date be included. [DS] More details can be found here: https://wi

B2.2.16b STAC: Provide a unique identifier for the file/layer/granule in the STAC Item spec ‘id’ field. [DS + DE]

B2.2.16a UMM: Provide the universal reference identifier of the granule in each metadata record using the ‘GranuleUR’ element. Typically, the Granule UR will match the granule's file name. However, other identifying information may be included. The UR must be completely unique when compared to all other data from the same provider (i.e. datasets with the same provider Id in CMR). [DS] More details can be found here: https://wiki.earthdata.nasa.gov/display/CMR/Granule+UR

B2.2.15b STAC: Provide the license using the ‘license’ element. The license should be selected from the SPDX License identifier list: https://spdx.org/licenses/. Provide “varies” if multiple licenses apply and “proprietary” for all other cases. The default value for an open license should be “CC0-1.0” unless otherwise specified. [DS + DE]

B2.2.15a UMM: Provide the license information in the ‘UseConstraints’ element. At a minimum, it is recommended that a link to the relevant license be provided in the ‘UseConstraints/LicenseURL/Linkage’ field. [DS] Additional info and other options for providing the license information can be found here: https://wiki.earthdata.nasa.gov/display/CMR/Use+Constraints Note: If a EULA identifier is available, linked it to the UMM-C under the ‘UseConstraints/EULAIdentifiersâ€�

B2.2.14b TBD: STAC: The best practice for providing the data product version using the STAC Collection spec. [DS + DE]

B2.2.13b STAC: A unique identifier for the data product should be provided in the ‘id’ element. [DS + DE]

B2.2.13a UMM: A unique identifier for the data product should be provided in the ‘ShortName’ element. This should take the form of a shortened or abbreviated name of the data product. [DS] More details on short name best practices can be found here: https://wiki.earthdata.nasa.gov/display/CMR/Short+Name

B2.2.12b STAC: Provide links to all relevant information in the Link Object -> ‘href’ and ‘rel’ elements. Provide the actual link in the ‘href’ element. The ‘ref’ element describes the relationship between the collection and the URL. More information on relationships can be found here. [DS + DE]

B2.2.12a UMM: Provide links to all relevant documentation in the collection level metadata. A complete list of relevant documentation can be found here: https://wiki.earthdata.nasa.gov/display/CMR/Related+URLs. Any documentation created in either the ‘data’ ‘code,’ or ‘information content’ activities should also be included here. Describe each URL using the guidance provided here: https://wiki.earthdata.nasa.gov/display/CMR/Related+URLs [DS]

B2.2.11a UMM: Provide the platform information using the ‘Platform’ element. Ensure all relevant platforms are listed in the metadata. [DS] More details can be found here: https://wiki.earthdata.nasa.gov/display/CMR/Platform. If applicable, it is also recommended that instruments/sensors be provided as well using the ‘Instrument’ element. More details can be found here: https://wiki.earthdata.nasa.gov/display/CMR/Instrument. The Platform name(s) must be selected from the GCMD

B2.2.10b STAC: The spatial information should be provided in the Extent Object -> Spatial Extent Object. The first bounding box always describes the overall spatial extent of the data. All subsequent bounding boxes can be used to provide a more precise description of the extent and identify clusters of data. The coordinate reference system of the values is WGS 84 longitude/latitude. [DS + DE]

B2.2.10a UMM: Determine what type of spatial extent is being described in the metadata. In the CMR, there is the option to describe the horizontal, vertical, and orbital spatial coverage of a dataset along with its coordinate system and resolution. [DS] More details on each type can be found here: https://wiki.earthdata.nasa.gov/display/CMR/Spatial+Extent For horizontal spatial extents, select an option that best describes the coverage of the data product. The four options in the CMR include: po

B2.2.9b STAC: The temporal information should be provided in the Extent Object -> Temporal Extent Object. If the data has an open range (e.g. active/ongoing collection), this can be specified by setting the start and/or end time to “null”. For example, [[2019-01-01T00:00:00Z, null]]. Timestamps should consist of a date and time in UTC and MUST be formatted according to RFC 3339, section 5.6. The temporal reference system is the Gregorian calendar. [DS + DE]

B2.2.9a UMM: Dates provided in CMR metadata should comply with the ISO 8601 Standard, which is an International Standard for the representation of dates and times. Select from one of three options in the UMM for describing the temporal extent of data: Single Date Time, Range Date Time and Periodic Date Time. More specific details on each of these options can be found here: https://wiki.earthdata.nasa.gov/display/CMR/Temporal+Extents [DS + DE]

B2.2.8b STAC: The ‘keywords’ element in the Collection specification should be used to provide science keywords. Science keywords should be selected from the GCMD science keywords list. [DS + DE]

B2.2.8a UMM: Populate science keywords using the ‘ScienceKeywords’ element. Science keywords should represent the scientific parameters being provided in the data as well as any broader conceptual terms that may aid in describing the data. [DS] The Science Keywords are chosen from a controlled keyword hierarchy. More information on science keyword best practices can be found here: https://wiki.earthdata.nasa.gov/display/CMR/Science+Keywords

B2.2.7b TBD: STAC: The best practice for providing the collection progress using the STAC Collection spec is still TBD. [DS + DE]

B2.2.7a UMM: Provide the collection production status in the ‘CollectionProgress’ element. Leverage the Collection Progress controlled vocabulary to describe the production status of the dataset. [DS] More info and the controlled vocabulary list can be found here: https://wiki.earthdata.nasa.gov/display/CMR/Collection+Progress

B2.2.6b STAC: Provide the processing level using the ‘processing:level’ element using the processing extension (https://github.com/stac-extensions/processing) for Collections. [DS + DE]

B2.2.6a UMM: Provide the data processing level in the ‘ProcessingLevel’ element. The data processing level should align with the EOSDIS data processing level whenever possible. [DS] More details on the EOSDIS data processing level can be found here: https://earthdata.nasa.gov/earth-science-data-systems-program/policies/data-information-policy/data-levels. More details on data processing level best practices can be found here: https://wiki.earthdata.nasa.gov/display/CMR/Processing+Level