Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

odata_attributesdata type
to be
removed
target STAC extension
STAC Counterpart
collection levelitem levelasset level
NotesOData ICD definitionSTAC definitionExample STAC
Example Odata
areaOfInterestStringAttributeXregionnamemandatoryoptionalnacan be set as a keyword at collection levelCLMS specificA human-readable name of the relevant region.
global
beginningDateTimeDateTimeOffsetAttribute
STAC core attributestart_datetimenamandatory nabeginning of the interval that the data is valid. RFC beginning of interval start or end of second?CLMS specificThe first or start date and time for the resource, in UTC. It is formatted as date-time according to RFC 3339, section 5.6.2025-06-21T00:00:00.000000Z2025-06-21T00:00:00.000000Z
cellIDIntegerAttribute?gridcodenaoptionalnaNew grid variants may need to be added to the extension.CLMS specificCLMS specific
1300000000033
ChecksumStringAttribute
filechecksumnanamandatory
Represents the known checksums for the product’s physical data, providing a unique value for supporting download integrity check. At least MD5 checksum is mandatory.Provides a way to specify file checksums (e.g. BLAKE2, MD5, SHA1, SHA2, SHA3). The hashes are self-identifying hashes as described in the Multihash specification and must be encoded as hexadecimal (base 16) string with lowercase letters.

collectionNameStringAttributeXnananananacan be set as a keyword at collection levelCLMS specificCLMS specificTO BE REMOVEDCLMS
componentStringAttributeXnananananacan be set as a keyword at collection levelCLMS specificCLMS specific
bio-geophysical
consolidationPeriodIntegerAttributeXnananananacan be set as a keyword at collection levelCLMS specificCLMS specific
6
ContentDate:EndDateTimeOffsetAttribute
STAC core attributeend_timenamandatoryna
nominal endThe last or end date and time for the resource, in UTC. It is formatted as date-time according to RFC 3339, section 5.6.2025-06-30T23:59:59.999999Z2025-06-30T23:59:59.999999Z
ContentDate:StartDateTimeOffsetAttribute
STAC core attributestart_datetimenamandatoryna
nominal startThe first or start date and time for the resource, in UTC. It is formatted as date-time according to RFC 3339, section 5.6.2025-06-21T00:00:00.000000Z2025-06-21T00:00:00.000000Z
ContentLengthIntegerAttribute
filesizenanamandatory

Actual size in bytes (B) of the downloadable product package

The file size, specified in bytes.27516224122751622412
ContentTypeStringAttribute
STAC core attributetypenanamandatory
The Mime type of the productMedia type of the asset. See the common media types in the best practice doc for commonly used asset types.image/tiff; application=geotiff; profile=cloud-optimizedapplication/netcdf
datasetAliasStringAttributeX




can be set as a keyword at collection levelCLMS specificCLMS specific
wl-lakes_global_vector_daily
datasetIdentifierStringAttribute
STAC core attributecollectionmandatorynana
CLMS specific

The id of the STAC Collection this Item references to with the collection relation type in the links array.

wl-lakes_global_vector_daily_v2wl-lakes_global_vector_daily_v2
datasetShortNameStringAttributeX




can be set as a keyword at collection levelCLMS specificCLMS specific
lwl
datasetVersionIntegerAttribute
versionversionmandatorynanait should be included in the collection nameCLMS specificVersion of the context this fields is used in (e.g. Asset or Collection).
2
endingDateTimeDateTimeOffsetAttribute
STAC core attributeend_timenamandatoryna
CLMS specificThe last or end date and time for the resource, in UTC. It is formatted as date-time according to RFC 3339, section 5.6.2025-06-30T23:59:59.999999Z2025-06-30T23:59:59.999999Z
EvictionDateDateTimeOffsetAttribute
timestampsexpiresnamandatoryna

Date when the data file will be removed from the Interface Delivery Point.

Date and time the corresponding data (see below) expires (is not valid any longer), in UTC.9999-12-31T23:59:59.999999Z9999-12-31T23:59:59.999999Z
fileFormatStringAttributeX




it should be included in the collection nameCLMS specificCLMS specific
geojson
gridLabelStringAttribute
STAC core attributegsdmandatorynanaRequired for all rasters
minimum nominal grid spacing for a collection
CLMS specificThe nominal Ground Sample Distance for the data, as measured in meters on the ground. There are many definitions of GSD. The value of this field should be related to the spatial resolution at the sensor, rather than the pixel size of images after orthorectification, pansharpening, or scaling. The GSD of a sensor can vary depending on geometry (off-nadir / grazing angle) and wavelength, so it is at the discretion of the implementer to decide which value most accurately represents the GSD. For example, Landsat8 optical and short-wave IR bands are all 30 meters, but the panchromatic band is 15 meters. The gsd should be 30 meters in this case because that is the nominal spatial resolution at the sensor.300300m
IdStringAttributeX




UUID

It is a universally unique identifier (UUID). The Id is a local identifier for the product instance within the Data Access, assigned during the product ingestion.

NA
c46db475-d910-431f-8f36-d12bf3a93e7f
instrumentShortNameStringAttribute
STAC core attributeinstrumentsmandatorymandatorynaCan be array of strings.name of the InstrumentAn array of all the sensors used in the creation of the data. For example, data from the Landsat-8 platform is collected with the OLI sensor as well as the TIRS sensor, but the data is distributed together so would be specified as ['oli', 'tirs']VEGETATIONVEGETATION
metricGridSpacingIntegerAttribute
STAC core attributegsdmandatorymandatoryna
CLMS specificThe nominal Ground Sample Distance for the data, as measured in meters on the ground. There are many definitions of GSD. The value of this field should be related to the spatial resolution at the sensor, rather than the pixel size of images after orthorectification, pansharpening, or scaling. The GSD of a sensor can vary depending on geometry (off-nadir / grazing angle) and wavelength, so it is at the discretion of the implementer to decide which value most accurately represents the GSD. For example, Landsat8 optical and short-wave IR bands are all 30 meters, but the panchromatic band is 15 meters. The gsd should be 30 meters in this case because that is the nominal spatial resolution at the sensor.10001000
missionShortNameStringAttributeXnanananana
CLMS specificCLMS specificNOT TO BE USEDSPOT4,SPOT5,PROBAV
ModificationDateDateTimeOffsetAttribute
STAC core attributeupdatednamandatorynamodification of metadata in OData/STAC cataloguea and not the modification of data/assets itself

Date when the product metadata was last modified.

Date and time the corresponding STAC entity or Asset (see below) was updated last, in UTC.2025-07-02T10:08:46.236018Z2025-07-02T10:08:46.236018Z
NameStringAttribute
STAC core attributeidnamandatorynaproduct name unique within a Collection,Data file nameIt is important that an Item identifier is unique within a Collection, and that the Collection identifier in turn is unique globally. Then the two can be combined to give a globally unique identifier. Items are strongly recommended to have Collections, and not having one makes it more difficult to be used in the wider STAC ecosystem. If an Item does not have a Collection, then the Item identifier should be unique within its root Catalog or root Collection.c_gls_NDVI300_202506210000_GLOBE_OLCI_V2.0.1_ncc_gls_NDVI300_202506210000_GLOBE_OLCI_V2.0.1_nc
nominalDateDateTimeOffsetAttribute
STAC core attributedatetimenamandatoryna
CLMS specific2025-06-21T00:00:00.000000Z2025-06-21T00:00:00.000000ZOnlineStringAttributeXnanananana

Indication of current online presence.

TRUEOriginDateDateTimeOffsetAttributeSTAC core attributecreatednamandatorynaWhen generated by the CLMS producer

Date and time of the product at the source (e.g. Publication date time on the PRIP). Time is in UTC

2025-07-02T09:30:01.282075Z2025-07-02T09:30:01.282075ZThis is likely the acquisition (in the case of single camera type captures) or the 'nominal' or representative time in the case of assets that are combined together. Though time can be a complex thing to capture, for this purpose keep in mind the STAC spec is primarily searching for data, so use whatever single date and time is most useful for a user to search for. STAC content extensions may further specify the meaning of the main datetime field, and many will also add more datetime fields. All times in STAC metadata should be in Coordinated Universal Time (UTC). If there's clearly no meaningful single 'nominal' time, it is allowed to use null instead. In this case it is required to specify a temporal interval with the fields start_datetime and end_datetime from common metadata.2025-06-21T00:00:00.000000Z2025-06-21T00:00:00.000000Z
OnlineStringAttributeXnanananana

Indication of current online presence.

na
TRUE
OriginDateDateTimeOffsetAttribute
STAC core attributecreatednamandatorynaWhen generated by the CLMS producer

Date and time of the product at the source (e.g. Publication date time on the PRIP). Time is in UTC

Creation date and time of the corresponding STAC entity or Asset (see below), in UTC.2025-07-02T09:30:01.282075Z2025-07-02T09:30:01.282075Z
platformAcronymStringAttribute
STAC core attributeconstellationmandatorymandatoryna
CLMS specificThe name of a logical collection of one or more platforms that have similar payloads and have their orbits arranged in a way to increase the temporal resolution of acquisitions of data with similar geometric and radiometric characteristics. This field allows users to search for related data sets without the need to specify which specific platform the data came from, for example, from either of the Sentinel-2 satellites. Examples include landsat-8 (Landsat-8, a constellation consisting of a single platform), sentinel-2 (Sentinel-2), rapideye (operated by Planet Labs), and modis (NASA EOS satellites Aqua and Terra). In the case of modis, this is technically referring to a pair of sensors on two different satellites, whose data is combined into a series of related products.Sentinel-2 or multimissionSentinel-2
platformShortNameplatformAcronymStringAttribute
STAC core attributeconstellationplatformmandatorymandatorynaCLMS specificSentinel-2 or multimissionSentinel-2
name of the PlatformThe unique name of the specific platform the instrument is attached to. For satellites this would be the name of the satellite, whereas for drones this would be a unique name for the drone. Examples include landsat-8 (Landsat-8), sentinel-2a and sentinel-2b (Sentinel-2), terra and aqua (part of NASA EOS, carrying the MODIS instruments), mycorp-uav-034 (hypothetical drone name), and worldview02 (Maxar/DigitalGlobe WorldView-2).platformShortNameStringAttributeSTAC core attributeplatformmandatorymandatorynaname of the PlatformSentinel-2A or multimissionSenitnel-2A
processingCenterStringAttribute
processingfacilitynamandatorynana
name of the Procesing CentreThe name of the facility that produced the data. For example, Copernicus S1 Core Ground Segment - DPA for product of Sentinel-1 satellites.name of the Procesing Centre
VITO
productVersionStringAttribute
processingversionnamandatoryna
CLMS specificThe version of the primary processing software or processing chain that produced the data. For example, this could be the processing baseline for the Sentinel missions.
v3.0.1
PublicationDateDateTimeOffsetAttribute
timestampspublishednamandatoryna
Publication date and time of the product (time at which the product becomes accessible for retrieval to the client within the DA).

Date and time the corresponding data (see below) was published the first time, in UTC.


2025-07-02T10:08:46.236018Z
S3PathStringAttribute
STAC core attributehrefnanamandatory
S3 path in the CDSE repositoryS3 path in the CDSE repository
/eodata/CLMS/bio-geophysical/vegetation_indices/ndvi_global_300m_10daily_v2/2025/06/21/c_gls_NDVI300_202506210000_GLOBE_OLCI_V2.0.1_nc
swiSubParameterStringAttribute?





CLMS specificCLMS specific
CI
temporalRepeatRateStringAttributeX




can be set as a keyword at collection levelCLMS specificCLMS specific
10daily
vppSeasonStringAttribute?





CLMS specificCLMS specific
S2
vppSubParameterStringAttribute?





CLMS specificCLMS specific
TPROD
wlBasinNameStringAttribute?





CLMS specificCLMS specific
Mackenzie River
wlLakeNameStringAttribute?





CLMS specificCLMS specific
athabasca
wlRiverNameStringAttribute?





CLMS specificCLMS specific
Ya-lu-cang-bu-jiang

...