| API
|
Advanced Programming Interface. Specific Computing interface allowing a programmatic access to the mCube functions
|
| Application Package
|
The set of files needed for the integration of a new processing service on mCube.
|
| Asset
|
A 'spatiotemporal asset' is any file that represents information about the earth captured in a certain space and time. Single bands and groups of bands are referred to as assets. Several assets can be derived from a single EO data product. They are pre-defined in mCube and can be used directly (Select Asset) or combined ad-hoc by the user (Combine Assets) within the Titiler widget.
|
| Band Combination
|
A service providing the possibility to perform RGB band combinations from user defined bands of single or multiple EO data products.
|
| Charter
|
International Charter for Space and Major Disaster a non-binding charter which provides space satellite data in the event of major disasters.
|
| Charter Mapper Processing Environment by ESA (ESA Charter Mapper)
|
An extension of the operational workflow management system COS-2 that will be operated as a portfolio of on-line EO processing Services.
|
| Cloud Optimized GeoTIFF (COG)
|
A Cloud Optimized GeoTIFF (COG) is a regular GeoTIFF file, aimed at being hosted on a HTTP file server, with an internal organization that enables more efficient workflows on the cloud. It does this by leveraging the ability of clients issuing HTTP GET range requests to ask for just the parts of a file they need.
|
| Common Band Name (CBN)
|
Common Band Names (CBN) classes refer to common band ranges derived from multispectral bands of several popular instruments.
|
| COS-2
|
Charter Operational System 2nd generation, on-online system developed by the Agency in order to better support the different users and provide more reliable and secure operation.
|
| Dataset
|
Abstract concept to define a Data Item that conveys core business data, usually as a product file with metadata. In mCube EO data or auxiliary data shall typically be datasets in the system taking place as entry in the catalogue with a physical product file in the storage.
|
| Data Item
|
Abstract concept to define any information item in the system and stored as an entry in the catalogue of the system. All acquisition notifications become Data Items in mCube taking place as entries in the catalogue shared as data references for most of the components like API, Data Pipelines, Workspaces, Production Center.
|
| Data Pipeline
|
Abstract concept to define a processing chain that is triggered by an event of a Data Item (e.g. new activation in the catalogue) and that then executes a workflow defining execution steps including long processing jobs, catalogue updates or API calls.
|
| Data Processing Scenarios
|
Written Data Processing outlines framed by a set of rules based on the Disaster type and the Sensor type defining a sequence of Thematic Processing to be applied to new Acquisitions notified to mCube.
|
| Data Processing Pipelines Application
|
Abstract concept to define a thematic data processor algorithm that is applied to a data pipeline
|
| Disaster Workspace
|
Workspace in the scope of a disaster. It contains the information related to the activation of the disaster call(s) and the related data item (Activations, Value Added Products)
|
| EO Product (or Product)
|
Satellite image coming from one of a predefined list of sensors of the mCube constellation. An EO product is notified in mCube as an acquisition providing the dataset.
|
| Geographic Information System (GIS)
|
Tools that allow users to create interactive queries (user-created searches), analyze spatial information, edit data in maps, and present the results of all these operations.
|
| Indexes
|
In Elasticsearch an index consists of one or more Documents, and a Document consists of one or more Fields. In database terminology, a Document corresponds to a table row, and a Field corresponds to a table column.
|
| Integrated Application
|
Software item that has been implemented and packaged in a way that is ready to be deployed on mCube to become a Thematic Processor. A validation step of the application package provided by the third party is necessary to have it as an Integrated Application
|
| Metadata Catalogue
|
A metadata management tool designed to help find and manage large amounts of data. In the EO it manages the collections of satellite data coming from different EO missions.
|
| Offering
|
An offering is a service associated with a Data Item. It describes a set of operations available in a web service and associated with the Data Item. For instance, a WMS offering in an Acquisition contains a GetMap operation to view a raster layer on a map as a browse of the Acquisition.
|
| On-demand service
|
A service triggered by the user after filling a form with parameters and input references.
|
| Platform as a Service (PaaS)
|
PaaS provides users with the capabilities to deploy user-created or acquired applications developed using programming languages and tools supported by the provider onto an infrastructure, typically cloud-based. The user does not manage or control the underlying infrastructure, including network, servers, operating systems, or storage, but has control over the deployed applications and possibly application hosting environment configurations.
|
| Portal
|
Front-end website containing the landing pages of mCube when connecting the main web address. The mCube Portal shall give access to all the platform functionalities via web navigation.
|
| Processing Data Item
|
This is an implementation of a Data Item specific to the Data Processing Pipeline to manage a processing as an entry in the catalogue.
|
| Processing Environment
|
Within the context of this document, a “Processing Environment” refers to an environment providing users with a set of services such as access to (i) large volume of data (EO/non-space data), (ii) computing resources (iii) processing software (e.g. toolboxes, retrieval baselines, visualization routines), and (iv) general platform capabilities (e.g. user management and access control, accounting, information portal, collaborative tools, social networks etc.). mCube thus provides a complete work environment for its users, enabling them to effectively perform data-intensive research and data exploitation by running dedicated processing software close to the data.
|
| Product segregation
|
The action of hiding a product from the list of available data relative to an Activation. This happens mainly due to quality issues.
|
| Quicklook
|
Preview of an EO Product or VAP.
|
| Raster(ization)
|
A service that produces full resolution visualization datasets for the acquisition of a call/activation.
|
| Recovery Time Objective
|
The Recovery Time Objective (RTO) is the duration of time and a service level within which a business process must be restored after a disaster in order to avoid unacceptable consequences associated with a break in continuity.
|
| Slide feature
|
A graphical effect that allows the user to move a vertical bar over an area of the map, allowing to immediately see the differences between two layers.
|
| SpatioTemporal Asset Catalog (STAC)
|
The SpatioTemporal Asset Catalog (STAC) is a standardized way to catalog and expose multi-source geospatial data through a common metadata structure which simplifies the process to expose, discover and query of “spatiotemporal” assets for data providers, developers and users.
|
| Systematic Processing Services
|
A service that is a background production triggered right after receiving an EO data notification in a workspace.
|
| Thematic Processor
|
Abstract concept to define a tool or algorithm originated from a specialized field that extracts information from an Earth Observation dataset
|
| TiTiler
|
A FastAPI that enables the dynamic creation of web map tiles from STAC, COG.
|
| Third Party Data Provider
|
Owner or operator of an Earth Observation mission under specific agreements with the Agency.
|
| Workspace
|
The full set of files related to a single activation (including intermediate results and Value Adding products).
|