1. Introduction¶
1.1 Scope¶
This document is part of the DestinE Platform technical baseline and complements the Onboarding process in the DestinE platform framework.
1.2 Purpose¶
This document outlines the key guidelines for furnishing the attributes pertaining to the service and data portfolio as part of the integration with the DestinE Platform Service Registry.
Guidelines are organized following the main Data Model sections:
Service Survey – detailed in Section 0
Data Portfolio – detailed in Section 1.4.3. The Data Portfolio is an entry of the Service, but due to its complexity it is treated separately from the Service Survey.
Also, this document covers some conventions that support the Service Provider during the process.
1.3 Reference Documents¶
Table 1: Reference documents.
| Ref. | Title | Reference and Version |
|---|---|---|
| [RD-1] | List of Map Projections | https://en.wikipedia.org/wiki/List_of_map _projections |
| [RD-2] | EPSG Geodetic Parameter Dataset | https://epsg.org/ |
| [RD-3] | International System of Units | https://en.wikipedia.org/wiki/International _System_of_Units |
| [RD-4] | EUROSTAT GISCO Geographical Information and Maps (NUTS) | https://ec.europa.eu/eurostat/web/nuts |
| [RD-5] | ArcGIS World Water Bodies | https://www.arcgis.com/home/item.html?i d=e750071279bf450cbd510454a80f2e63 |
| [RD-6] | Inland Waters reference ArcGIS | https://hub.arcgis.com/search?tags=inlan d%2520waters |
1.4 Service Survey¶
Any Service Provider intending to register a service in the DestinE Platform Service Registry must collect information in a format that aligns with the tables provided below.
The tables below show attributes per each element and attribute batch reflecting the Data Model and here described by the following fields.
Key name: the name of the Data Model entry
Key Description: Short description to support filling.
Key Format: the key format such as str, list, object, …
Key Label: indicating the relevance of the key
Free: free text input
Standardized: input selection from predefined options (enumerated list)
Suggested: free text optional entry
Guideline: the actual guideline supporting the provision of the single attribute.
Every key has a value that populates the Data Model implementation as a Database in the scope of the Service Registry.
Some attributes are marked bold to denote their implementation as List or Object (Table) and developed in the subsections accordingly.
1.4.1 Service General Description¶
The Tables below are aimed at gathering information on Service General Description.
Table 2: Service General Description.
| Key Name | Key Description | Key Format | Key label | Guideline |
| Name | Service Name | Str | Free | 3-20 characters |
| Description | Service description, which becomes searchable text | Str | Free | 100-1000 characters |
| Cover Image | Cover image of the service | PNG or JPEG | Free | 1600x900 pixels 72 D.P.I. Size max 150kb If the service provider has no image to place, a placeholder will be used |
| Logo | Logo representing the Service | SVG or EPS | Free | Vectorial, coloured If the service provider has no image to place, a placeholder will be used |
| Logo (monochrome) | Logo representing the Service | SVG or EPS | Free | Vectorial, monochrome white If the service provider has no image to place, |
| a placeholder will be used | ||||
| Short Description | Service short description that becomes searchable text | Str | Free | 10-100 characters |
| Service Page Link | URL pointing to the service | Str | Free | Valid URL |
| Gallery | List of gallery items | List-Object | See 1.4.1.1 If the service provider has no image to place, a placeholder will be used | |
| Video tutorials | List of video tutorials | List-Object | See 1.4.1.2 | |
| Organization Info | Organization information | List-Object | See 1.4.1.3 | |
| Category | List of service categories | Str-Enum | Standardized | Choose value from reference, see 2.3.1 |
| Primary Tag | List of “preferred” service tags that appear on the main cover page of the service (marketplace) | Str-Enum | Standardized | Choose values from reference, see 2.3.2 Maximum 3 primary tags shall be set as preference. |
| Secondary Tag | A list of service tags is shown on the service dedicated page. | Str-Enum | Standardized | Choose values from reference, see 2.3.2 No limit in the number of secondary tags. |
| Documentation | Readthedocs documentation URL relative to the service | Str | Free | Readthedocs URL obtained after service integration |
| User Availability | Indication if the service is available to DestinE free usage profile or restricted | Str-Enum | Standardized | Choose value between: Open or Restricted |
| Service Version | Version of the Service used in Production | Str | Free | Standard semantic versioning X.Y.Z. Shall reflect the deployed version on destine.eu |
| *Service Quota | List of service-related limitations | List-Object | See 1.4.1.4 | |
| *Cloud Type | Referred to the Cloud solution as per -runtime -OVH account -external infrastructure | String | Standardized | Internal use. Default is “runtime” |
| *Service Issue Date | Publication into PROD | Datetime | Free | Internal use |
| *Operational Readiness | States the service readiness level | Str | Standardized | Choose value among the following options: - alpha version (new features are added), - beta version (only bug fixing), - ops version (standard version), |
| - long-term supported version (whenever bug fixing is ensured) |
*: for internal use only, not exposed to end users.
1.4.1.1 Gallery Items¶
Object table identifying single gallery items/media files. Multiple entries are possible.
Table 3: Gallery Items.
| Key Name | Key Description | Key Format | Key label | Guideline |
| Single Item of Gallery | A single item of a service collection gallery of images | PNG or JPEG Or GIF | Suggested | 1600x900, pixels, 72 D.P.I., Size max 150kb For videos: mp4 format Note that if no items are provided, not even the cover image, a placeholder image will be used |
1.4.1.2 Tutorial¶
Object table identifying tutorials. The provisioning of tutorials is strongly suggested. If Multiple entries are possible.
Table 4: Video tutorials.
| Key Name | Key Description | Key Format | Key label | Guideline |
| Tutorial title | Title or name of the tutorial item | Str | Suggested | |
| Tutorial URL | URI pointing to the tutorial web page | Str | Suggested | For video: 1080p resolution |
| Tutorial Item Description | Caption/description of the Gallery Item | Str | Suggested | 50-200 characters |
| Tutorial Category | Tag indicating the scope and purpose of the tutorial item | Str-Enum | Suggested | Possible options: Use Cases, Step-by-step Guide, … Service Providers can propose new categories |
1.4.1.3 Organization attributes¶
Object table describing the service provider’s organization or company. Multiple entries are possible.
Table 5: Organization attributes.
| Key Name | Key Description | Key Format | Key label | Guideline |
| Organization Name | The complete legal name of the organization providing the service | Str | Free | 3-20 characters |
| Organization Type | Description of the type of the service | Str-Enum | Standardized | Choose value among the following options: Industry, Research, Public, Scientific, Commercial, Education, Other |
| Service Contact address | Organization email address for information request. Contact point | Str | Free | Service email associated with the Company providing the service. |
| Organization Logo | Logo representing the Service Organization | SVG or EPS | Suggested | Vectorial, coloured If the service provider has no image to place, a placeholder will be used |
| Organization Logo (monochrome) | Logo representing the Service Organization | SVG or EPS | Suggested | Vectorial, monochrome white If the service provider has no image to place, a placeholder will be used |
| Organization reference | URL pointing to the organization or company website | Str | Suggested | Valid URL |
1.4.1.4 Service Quota¶
Object table describing service limitations and quota.
| Key Name | Key Description | Key Format | Key label | Guideline |
| Limit on request | Quota restricting the number of requests a user can make per month. | Int | Free | Use a “per month” scale. If uneven, approximates to the larger integer |
| Concurrency Limits | Quota limiting the number of concurrent connections a user can initiate. | Int | Free | If uneven, approximates to the larger integer. Use a time scale (e.g. per month) if applicable. |
| Time-Based Access Control | Quota that restricts access to resources based on time constraints, i.e. access rights are granted or revoked after a time frame. | String | Free | Free text with unit, e.g. “30 days”, “12 hours”, … |
| Computational or Processing Limits | Limitation on the provisioning of computational resources (e.g., CPU, memory, or GPU) that the user can instance into the service. | Int | Free | If uneven, approximates to the larger integer. Use a time scale (e.g. per month) if applicable. |
| API Request or Response Size Limits | Quota limiting the size of data a user can request or send in a single API call. | Int (bytes) | Free | |
| Data Transfer Limits | Quota limiting the amount of data a user can transfer (upload/download) on the service per month. | Int (bytes) | Free | Use a “per month” scale. If uneven, approximates to the larger integer |
| Feature- Based/Custom Limits | Restricts access to specific features based on the user's plan. Free optional key value proposed as an entry | String | Free | Custom key-value set |
1.4.2 Service Interfaces Description¶
The Tables below are aimed at gathering information on Service Interfaces Description. Multiple entries are possible.
Table 6: Service Interfaces Description.
| Key Name | Key Description | Key Format | Key label | Guideline |
| Name | Interface Name | Str | Free | 3-20 characters |
| Version | Interface Version | Str | Free | Standard semantic versioning X.Y.Z. |
| Documentation | URL pointing to the interface documentation | Str | Free | Swagger for API. In the Service Readthedocs for other types. |
| Type | Endpoint archetype | Str-Enum | Standardized | Choose value among the following options: API, GUI, Catalogue, IDE, CLI, Other |
| User Availability | Indication if the interface is available to DestinE free usage profile or restricted | Str-Enum | Standardized | Choose value between options: Open or Restricted |
| Support Contact | Email of support contact | Str | Free | The service email is associated with the company providing the service. |
| Interface URL | URI of the interface exposed to end user | Str | Free | Valid URL to interface root path depending on service provider integration |
1.4.3 Tenancy Resource Description¶
The Tables below are aimed at gathering information on Service Tenancy Resource Description. Multiple entries are possible.
Table 7: Tenancy Resource Description
| Key Name | Key Description | Key Format | Key label | Guideline |
| Resource Name | The name of the resource provided by the Service Provider within the scope of the service | Str | Free | 3-20 characters |
| Resource Description | A brief description outlining the purpose and details of the resource | Str | Free | 3-20 characters |
| Terms & Conditions | A URI linking to the applicable terms and conditions for the resource | Str | Free | 3-20 characters |
| Monthly Allocation Price | The monthly price of the resource, expressed in euros (EUR), with a value greater than or equal to 0 | Int | Free | 0-1E6 range possible in EUR |
| Resource Type | The category of the resource | Str-Enum | Standardized | Following options: Quota, Datasets, or Service Feature |
| Free DestinE | A boolean flag indicating whether the resource is included in the Free DestinE tier | Bool | Standardized | If set to true, the associated price for the user is considered zero |
1.4.3.1 Tenancy Dynamic Resource Description¶
The resource is characterized by the following properties describing the time availability within the Service Offering.
Table 8: Tenancy Dynamic Resource Description
| Key Name | Key Description | Key Format | Key label | Guideline |
| Quantity max | integer number indicating the max time for which the resource is available | Int | Free | |
| Quantity min | integer number indicating the min time for which the resource is available | Int | Free | |
| Step Value | integer number indicating the configurable timestep of the resource availability | Int | Free | |
| Default Value | integer number defining the min/max time average | Int | Free | Only values above are not specified |
| Unit | enum list specifying if the availability time is hours, days, or months | Str | Free | Use units reference system |
| Updatable | boolean value indicating if the resource time range span can be updated or not | Bool | Standardized | Default is true |
1.5 Data Portfolio¶
Service “Data Portfolio” is a dedicated object table with own description, divided per element (General, Spatial, Temporal) in a well-defined data hierarchy. Any single data entry can be multiple.
The tables below show attributes per each element and attribute batch reflecting the Data Model and here described by the following fields.
Key name: the name of the Data Model entry
Key Description: Short description to support filling.
Key Format: the key format such as str, list, object, …
Key Label: indicating the relevance of the key
Free: free text input
Standardized: input selection from predefined options (enumerated list)
Suggested: free text optional entry
Guideline: the actual guideline supporting the provision of the single attribute.
Every key has a value that populates the Data Model implementation as a Database in the scope of the Service Registry.
Some attributes are marked bold to denote their implementation as List or Object (Table) and developed in the subsections accordingly.
Note. Providing Data Portfolio information is required only if the service exposes data; otherwise, this section can be omitted.
1.5.1 Data Portfolio General Description¶
The Tables below are aimed at gathering information on the Service Data Portfolio General Description.
1.5.1.1 Collection¶
A data portfolio can show different “Collections”.
Table 9: Collection
| Key Name | Key Description | Key Format | Key label | Guideline |
| Name | Collection name | Str | Free | 3-50 characters Use a full name not an ID. |
| Description | Collection description | Str | Free | 50-150 characters |
| References | URL referencing the Collection | Str | Free | Valid URL filled by the system |
| Image | Image representing the Collection | PNG or JPEG | Suggested | 1600x900 pixels 72 D.P.I. Size max 150kb It is pre-defined if the entry is known by the system. |
| Dataset | Dataset entry of a Collection | List-Object | Free | See 1.5.1.2 |
1.5.1.2 Dataset¶
Multiple entries are possible: a “Collection” can have multiple “Datasets”.
Dataset-specific attributes are provided in Section 1.5.2.
Table 10: Dataset
| Key Name | Key Description | Key Format | Key label | Guideline |
| Dataset Name | Dataset name | Str | Free | 3-50 characters Use a full name not an ID. |
| Dataset ID | Short name of the dataset | Str | Free | Name used to access data via service interfaces. It is strongly recommended to use known ID, e.g. used by primary data sources or within the literature. |
| Dataset Description of usage | Free text is provided to explain the usage of the dataset within the service | Str | Free | Small summary including the processing steps and manipulations performed |
| on data for which purpose. | ||||
| Reference | URL referencing the dataset | Str | Free | Valid URL or DOI |
| Update Frequency | High-level indication of how often the service updates the dataset | Str | Standardized | It indicates the update frequency of the dataset within the service. Choose value among options: 'daily', 'x-hourly', 'hourly', 'monthly', 'yearly', etc. |
| Processing Label | Indication if the dataset has been processed or not | Bool | Standardized | Choose value between options TRUE (if processed) or FALSE (if not) |
| Format | Format of the dataset as offered by the Service | Str | Standardized | Choose value among the allowed conventions, please see 2.1.3 The format provided here does refer to the data provided by the service (i.e. not the source data) |
| User Availability | Indication if the dataset is available to DestinE free usage profile or restricted | Str-Enum | Standardized | Choose value between options: Open or Restricted |
| Image | The cover image represents the dataset (inherited from the Collection). It appears on the web portal within the data marketplace | PNG or JPEG | Suggested | 1600x900 pixels 72 D.P.I. Size max 150kb It is pre-defined if the entry is known by the system. |
| Spatial Attributes | Pertain to characteristics related to space or spatial aspects of the data, which are essential for understanding the distribution, composition, and relationships of features on the Earth's surface or atmosphere | Object | See Section 1.5.2 | |
| Temporal Attributes | Refer to characteristics related to time or temporal aspects of the data collection process | Object | See Section 1.5.2.2 | |
| Variable | Single variable pertaining to the Dataset element | List-Object | See Section 1.5.1.3 |
1.5.1.3 Variables¶
Multiple entries are possible: a “Dataset” can have multiple “Variables”.
Table 11: Variables
| Key Name | Key Description | Key Format | Key label | Guideline |
| Name | The full name of the variable | Str | Free | Extended name of the variable, for example, “temperature”, “surface |
| pressure”, “total column ozone”, etc | ||||
| Unit | The unit of measure of the variable | Str | Free | See allowed conventions in 2.1.8 |
| Tag | A tag identifying the variable | Str-Enum | Standardized | Choose values from reference, see Section 2.3.3 If not provided, a standard set of tags will be used for each variable. |
1.5.2 Dataset-Specific Attributes¶
The following metadata set serves as a technical description for each dataset.
1.5.2.1 Spatial attributes¶
Object Table with own attributes pertaining to a “Dataset”.
Table 12: Dataset Spatial attributes.
| Key Name | Key Description | Key Format | Key label | Guideline |
| Spatial extent | Geographical extent of the dataset | Str-Enum | Standardized | Selection is based on a multi-level selection. Options in Section 2.1.5 Options like "All/Global" include all underlying levels of territorial coverage, i.e. it implicitly encompasses all subordinate or smaller geographic, administrative, or conceptual areas. Other options are nested increasingly with the level of detail upon the geographic coverage |
| Resolution | Data resolution | Str | Free | Float number expressed in units: degree or metres NA if not applicable to the dataset |
| Resolution tag | Human readable tag associated with the resolution | Str-Enum | Standardized | The selection is based on the resolution value inserted by the Service Provider. Choose value among options: Low, Medium, High or Super High, NA |
1.5.2.2 Temporal attributes¶
Object Table with own attributes pertaining to a “Dataset”.
Table 13: Dataset Temporal attributes.
| Key Name | Key Description | Key Format | Key label | Guideline |
| Start date | Start date of the dataset | Str | Free |
Formatted as "datetime +/- N days" where datetime is selected from the calendar widget as YYYY-MM-DD:HH:MM:SS in UTM
N can be 0 if the start date is fixed |
|---|---|---|---|---|
| End date | The end date of the dataset | Str | Free |
Formatted as "datetime +/- N days" where datetime is selected from the calendar widget as YYYY-MM-DD:HH:MM:SS in UTM
N can be 0 if the end date is fixed |
| Time resolution | Dataset time resolution in a human-readable format | Str | Standardized | Choose value among options: hours, days, months, etc. |
| Update frequency | Temporal information about the frequency of update of the dataset according to the service ingestion process | Str | Standardized | Choose value among options: weekly, monthly, etc. depending on service policy. |
| Last update | Temporal information about the last update of the dataset according to the service ingestion process | Str | Free | Datetime when this survey is compiled for the first time or updated. |
2. Conventions¶
In this Chapter are provided notable conventions adopted in the scope of the Service Registry “standardized” attributes.
Where possible conventions are taken from the literature.
2.1 Pre-defined attribute tables¶
Here below some known conventions used to represent the Data Portfolio entries.
2.1.1 Data Portfolio hierarchy¶
In the following we provide some known data names and descriptions that can be used as reference.
Examples of "Collections"
Copernicus Sentinels
Copernicus DEM
Marine Monitoring Service
Atmosphere Monitoring Service
Climate Change Service
Land Monitoring Service
Emergency Management Service
DestinE Climate Adaptation Digital Twins
DestinE Extreme-Weather Digital Twins
Eurostat General and regional statistics
Eurostat Economy and Finance
Eurostat Population and social conditions
Eurostat Industry, trade and services
Eurostat Agriculture, forestry, fisheries
Eurostat International trade
Eurostat Transport
Eurostat Environment and Energy
Eurostat Science, technology, digital society
Eurostat Tables on EU policy
Eurostat Cross-cutting topics
ECMWF Real-time forecasts
Example of "Datasets"
Here below a list of known examples covering the main use cases analyzed in this Data Model version.
“Destination Earth” > “DestinE Climate Adaptation Digital Twins” > “IFS-NEMO - ScenarioMIP - SSP3-7.0 - 0001” shows:
Surface Fields (sfc), Height level fields (hl), Pressure fields (pl)
“Destination Earth” > “DestinE Climate Adaptation Digital Twins” > “ICON - ScenarioMIP - SSP3-7.0 - 0001”
Surface Fields (sfc), Height level fields (hl), Pressure fields (pl)
Note: within a Data Access service, the dataset naming convention could incorporate also a part of its description or other metadata provided in the Data Model.
For instance, “High resolution Climate DT hourly Atmosphere on single levels” for the collection “IFS-NEMO - ScenarioMIP - SSP3-7.0 - 0001”.
“Copernicus Information” > “Atmosphere Monitoring Service” > “CAMS” shows:
Global greenhouse Gas Reanalysis (EGG4), Global Emissions Inventories, European Air Quality Reanalysis, Global Atmospheric Composition Forecasts, European Air Quality Forecasts, Global greenhouse Gas Reanalysis (EGG4) monthly averaged fields, Global Radiative Forcing, Global Radiative Forcing Auxiliary Variables, Global Reanalysis (EAC4) monthly averaged fields, Global Reanalysis (EAC4), Solar Radiation time-series
“Copernicus Information” > “Climate Change Service” > “ERA5” shows:
ERA5-Land hourly data from 1950 to present, ERA5 hourly data on single levels from 1940 to present, ERA5 monthly averaged data on single levels from 1940 to present, ERA5 hourly data on pressure levels from 1940 to present, ERA5 monthly averaged data on pressure levels from 1940 to present
“Copernicus Information” > “Emergency Management Service” > “EFAS”
EFAS forecasts, EFAS seasonal forecasts, EFAS re-forecasts, EFAS seasonal re-forecasts, EFAS historical simulations
“Copernicus Information” > “Land Monitoring Service” > “Bio-geophysical parameters” shows:
Burnt Areas, Vegetation Cover, Fraction of Absorbed Photosynthetically Active Radiation, Leaf-Area Index, Normalized Difference Vegetation Index, Dry-Gross Dry-Matter Productivity
2.1.2 Sensor Names and Types¶
List of known Sensor-Type combinations.
MODIS (Moderate Resolution Imaging Spectroradiometer) - Optical/Infrared Imaging Sensor
VIIRS (Visible Infrared Imaging Radiometer Suite) - Optical/Infrared Imaging Sensor
AMSR-E (Advanced Microwave Scanning Radiometer for EOS) - Microwave Radiometer
OLI (Operational Land Imager) on Landsat-8 - Optical Imaging Sensor
TIRS (Thermal Infrared Sensor) on Landsat-8 - Thermal Infrared Sensor
AVHRR (Advanced Very High-Resolution Radiometer) - Optical/Infrared Imaging Sensor
GOES Imager (Geostationary Operational Environmental Satellites) - Optical/Infrared Imaging Sensor
SAR (Synthetic Aperture Radar) - Radar Sensor
MERIS (Medium Resolution Imaging Spectrometer) - Optical Spectrometer
ASTER (Advanced Spaceborne Thermal Emission and Reflection Radiometer) - Optical/Infrared Imaging Sensor
GOME (Global Ozone Monitoring Experiment) - Ultraviolet/Visible Spectrometer
SMOS (Soil Moisture and Ocean Salinity) - Microwave Radiometer
ALI (Advanced Land Imager) on EO-1 (Earth Observing-1) - Optical Imaging Sensor
GEDI (Global Ecosystem Dynamics Investigation) - LiDAR (Light Detection and Ranging) Sensor
Sentinel-1 C-SAR (C-band Synthetic Aperture Radar) - Radar Sensor
Sentinel-2 MSI (MultiSpectral Instrument) - Optical Imaging Sensor
Sentinel-3 OLCI (Ocean and Land Colour Instrument) - Optical Imaging Sensor
Sentinel-3 SLSTR (Sea and Land Surface Temperature Radiometer) - Thermal Infrared Sensor
Sentinel-3 SRAL (SAR Radar Altimeter) – Radar Sensor
Sentinel-4 UVN (Ultraviolet Visible Near-infrared) - Spectrometer (planned for geostationary orbit)
Sentinel-5 Precursor TROPOMI (Tropospheric Monitoring Instrument) - Spectrometer
Sentinel-5 UVNS (Ultraviolet Visible Near-infrared Shortwave) - Spectrometer (planned)
Sentinel-6 Michael Freilich/Jason-CS (Radar Altimeter) - Altimetry Sensor
Meteosat Second Generation (MSG) SEVIRI - Spinning Enhanced Visible and Infrared Imager - Optical/Infrared Imaging Sensor
Meteosat Third Generation (MTG) FCI - Flexible Combined Imager - Optical/Infrared Imaging Sensor (planned)
Meteosat Third Generation (MTG) LI - Lightning Imager - Optical Sensor for Lightning Detection (planned)
MetOp Series IASI - Infrared Atmospheric Sounding Interferometer - Infrared Sounder
MetOp Series ASCAT - Advanced Scatterometer - Microwave Radar Sensor
EPS-SG Microwave Imager (MWI) - Microwave Imager - Microwave Radiometer (planned)
EPS-SG Infrared Sounder (IRS) - Infrared Sounder - Infrared Sounder (planned)
Jason-3 Poseidon-3B - Radar Altimeter - Altimetry Sensor
2.1.3 Formats¶
List of supported formats.
GeoTIFF
JPEG2000
NetCDF
HDF
GRIB
Zarr
Ascii
Shapefile
KML/KMZ
XML
BUFR
JSON
JSON-LD
Geo-JSON
CSV
YAML
JSON-Parquet
Protobuf
FITS
WMS
Binary
OBJ
STL
FBX
Collada
LAS
PNG
JPEG
Gif
MP4
SVG
PDF
2.1.4 Spatial Type¶
In the context of “Dataset”/“Spatial attributes”, the known list of “Spatial type” is the following.
surface,
2m,
10m,
100m,
total column,
tropospheric total column,
tropospheric columns,
top of canopy,
top of atmosphere,
bottom of atmosphere
2.1.5 Spatial Extent¶
In the context of “Dataset”/“Spatial attributes”, the known list of “Spatial extent” is the following.
Global
Continent
All - by selecting All, the below are automatically all selected
Africa, Europe, Asia, Oceania (including Australia and the Pacific Islands), North America, South America
Ocean
All - by selecting All, the below are automatically all selected.
Pacific Ocean, Atlantic Ocean, Indian Ocean, Southern Ocean, Arctic Ocean
Sea
All - by selecting All, the below are automatically all selected
Mediterranean Sea, Caribbean Sea, South China Sea, Bering Sea, Gulf of Mexico, Arabian Sea, Sea of Okhotsk, Sea of Japan (East Sea), North Sea, Red Sea, Baltic Sea, Black Sea, Andaman Sea, East China Sea, Hudson Bay
NUTS:
Note: if Europe is selected as a continent, as well as the global option, all NUTS are included.
All - by selecting All, the below are automatically all selected
NUTS Level based on [RD-4] please specify the NUTS by: NUTS_ID or NUTS_NAME
In Land Water: please refer to [RD-5] and [RD-6].
Custom: if any of the above apply the extent can be provided as a free-text input.
2.1.6 Projections and CRS¶
Projections and CRS are both used to reference imagery and data coordinates on the Earth globe.
The Service Provider shall provide both the Projections and CRS metadata. In particular,
Projection refers to the mathematical process of representing the three-dimensional surface of the Earth onto a two-dimensional plane for analysis and visualization purposes. Standard projections are Mercator, Universal Transverse Mercator (UTM), Lambert, or HEALPix (Hierarchical Equal Area isoLatitude Pixelization). Please refer to
CRS is a system that uniquely determines the position of a point or a geometric element (such as a line or polygon) on Earth. CRS includes a coordinate system, such as latitude and longitude or easting and northing, and a datum, which specifies the reference point and orientation of the coordinate system. A common CRS is WGS 84/EPSG 4326.
There can be two cases in providing the information about projection and CRS:
Data is referenced upon a CRS but cannot be projected; in this case, the Projection metadata is N/A
Data is referenced upon a CRS and is also projected on the Earth’s globe
Data does have CRS then the field shall be N/A.
Please refer to [RD-1] and [RD-2].
2.1.7 Time resolution¶
Known time resolutions are: “hourly”, “x-hours”, “daily”, “x-days”, “weekly”, “x-weeks”, “monthly”, “x-months”, “quarterly”, “annual”, “x-years”.
2.1.8 Units¶
Please use the International System of Units where possible [RD-3]. Also, specify the unit symbols instead of full text. Examples:
Single symbol: Kelvin → K
Combined: Kg/m2 (no * symbols if possible)
2.2 Naming conventions¶
Here below some scenarios that can be used as reference by service providers.
2.2.1 Datasets¶
Dataset Name
The general guideline for naming datasets is to use a full name as close as possible to the original data source dataset name, adding details as much representative as possible regarding the modification or processing performed.
Consider the example below.
Assume that a service delivers a dataset obtained from the following datasets: “ERA5 hourly data on single levels from 1940 to present” and “ERA5 monthly averaged data on single levels from 1940 to present”. The processing reduces the data with a variable time resolution from monthly (from 1940) to weekly (for the period closer to the present). The service provider can name the new dataset as: “ERA5 on single levels from 1940 to present monthly-to-weekly resolution.”
Dataset Description of Usage
In case the Service performs processing on a Dataset, its attribute “Description of usage” shall incorporate the information upon the dataset attributes modified by the processing chain. Here below some examples:
Format after a processing of format change
Projection/CRS after a processing of reprojection
Spatial resolution after a processing of spatial subsampling
Spatial extent after a processing of sub setting or cropping or mosaicking
Time resolution after a processing of temporal subsampling or aggregation
Temporal extent after a processing of time-series composition
Units after a processing of conversion
Compression after a processing of reducing data size (e.g. data streams)
Stack bands after a processing of color composition
···
Example of “Description of usage”: Sentinel-2 true color mosaic over France in Lambert coordinates.
2.2.2 Variables¶
Variable Name
The general guideline for naming variables is to use names as much closer as possible to the original name at the data source.
If this is not applicable, or in case the variable relates to a non-quantitative object (e.g. a 3D model), the name shall be a descriptive title, to be easily understood by users. For instance, “Wind Turbine”, “Soil PH”, etc.
2.3 Templates¶
2.3.1 Service Categories¶
Here below the enumerated list of service categories.
Data Access Management: This category focuses on controlling and managing access to data resources within an organization or system. It encompasses a range of tools, processes, and policies designed to ensure that data is accessed, used, and shared securely and efficiently.
Data Certification: This category identifies the capability of a service to verify the authenticity and integrity and track the lifecycle of digital items (data or software) through
the Collection and restitution of production traces and the certified signature of the related items.
Data Visualization: Services in this category specialize in presenting Earth Observation and DestinE data in a dynamic and immersive manner, including 2D, 3D, or 4D visual representations. Images and wind fields are projected onto a sphere, providing a contextual and spatial understanding. Additionally, numerical and categorical variables are depicted through insightful plots, offering a comprehensive view of data patterns. The service also enables the visualization of time series data evolution, supporting the seamless tracking of changes and trends over time.
Data Analysis and Modelling: This category revolves around sophisticated Earth observation data processing, employing advanced analytical techniques and modelling methodologies to extract meaningful insights and predict future trends. Data analysis involves systematically examining large datasets to uncover patterns, correlations, and anomalies, providing valuable intelligence for various applications such as environmental monitoring, disaster management, urban planning, agriculture, and more.
User Workflow: This category focuses on providing tools, platforms, and processes to facilitate the efficient and organized execution of tasks, processes, or projects by users within an organization or system. By automating, orchestrating, and optimizing the sequence of tasks and activities performed by users, this category aims to streamline user workflows, improve productivity, and enhance collaboration.