language en

RESEO - REmote SEnsing Ontology

Release 2021-09-24T23:59:59

This version:
https://w3id.org/reseo/1.0
Latest version:
https://w3id.org/reseo
Previous version:
0.1
Revision:
1.0
Issued on:
published
Authors:
Khaos Research Group, University of Málaga
Publisher:
Expert Systems with Applications
Imported Ontologies:
aemet.owl
geosparql
gml
sf
core
time
Download serialization:
JSON-LD RDF/XML N-Triples TTL
License:
https://opensource.org/licenses/MIT
Visualization:
Visualize with WebVowl
Cite as:
Aldana-Martín, J. F., García-Nieto, J., Roldan-Garcia, M. D. M., & Aldana-Montes, J. F. (2021). Semantic modelling of Earth Observation remote sensing [Computer software]. doi: https://doi.org/10.1016/j.eswa.2021.115838
DOI:
https://doi.org/10.1016/j.eswa.2021.115838
Incompatible with:
http://khaos.uma.es/green-senti/reseo/0.1

published

Abstract

Earth Observation (EO) based on Remote Sensing (RS) is gaining importance nowadays, since it offers a well-grounded technological framework for the development of advanced applications in multiple domains, such as climate change, precision agriculture, smart urbanism, safety, and many others. This promotes the continuous generation of data-driven software facilities oriented to advanced processing, analysis and visualization, which often offer enhanced computing capabilities. Nevertheless, the development of knowledge-driven approaches is still an open challenge in remote sensing, besides they provide human experts with domain knowledge representation, support for data standardization and semantic integration of sources, which indeed enhance the construction of advanced on-top applications. To this end, the use of ontologies and web semantic technologies have shown high success in knowledge representation in many fields, in which the Earth Observation is not an exception. However, as argued by the research community, there is large room for improvement in the specific case of remote sensing, where ontologies that consider the special nature and structure of different satellital and airborne data products are demanded. This article addresses, in first instance, part of this need by proposing a semantic model for the consolidation, integration, reasoning and linking of data (and meta-data), in the context of satellital remote sensing products for EO. With this objective, an OWL ontology has been developed and an RDF repository has been generated to allow advanced SPARQL querying. Although the proposal has been designed to consider remote sensing data products in general, the current study is mainly focused on the Sentinel 2 satellite mission from the Copernicus Programme of the European Space Agency (ESA). Four different use cases are showcased to check potentials of the proposed semantic model in terms of ontology integration, federated querying, data analysis and reasoning.

Introduction back to ToC

The development of new sensors and the growing ease of access to data generated with remote sensing techniques are pushing data-driven research and the development of new innovative algorithms for its analysis. In this context, Earth Observation's satellite systems are continuously generating a great quantity of data, which are nowadays essential for applications in diverse areas, such as: climate change monitoring (Plummer, Lecomte, & Doherty, 2017), precision agriculture (Weiss, Jacob, & Duveiller, 2020), smart urban design (Reba & Seto, 2020), and many others. This promotes the continuous generation of data-driven software facilities oriented to advanced processing, analysis and visualization, which often offer enhanced computing capabilities. However, while promising, such new-generation applications still require the symbolic representation of scenes and objects in images, as well as the setting of threshold values of computed vegetation indexes for the generation of knowledge rule systems (Belgiu, Drǎguţ, & Strobl, 2014). In this regard, the development of knowledge-driven deductive methods represents an important research line in remote sensing (Arvor et al., 2019, Chen, et al., 2016), as they complement inductive data-driven techniques to make them more actionable. A significant example in this direction is GEOBIA (Geographic Object-Based Image Analysis) (Blaschke, et al., 2014) that allows to set objects in satellite images (based on grouping pixels according to common features) to classify them. GEOBIA enables the representation of complex spatial topological and non-topological relationships. However, as argued in the literature (Arvor et al., 2019) and (Belgiu et al., 2014), GEOBIA rules are usually highly biased to specific scenarios and hence, they are rarely suited to be generalized.

In this sense, the development of general knowledge-driven approaches constitutes an open challenge in remote sensing, besides they provide human experts with domain knowledge representation, support for data standardization and semantic integration of multiple sources, such as multi-spectral (and hyper-spectral) data from various satellites and linked open data (meteorological, plant phenotype, etc.). Therefore, there is a clear need of studying integration aspects of existing ontologies in the context of remote sensing (Arvor et al., 2019), as well as to show the potentials of such integration for feeding advanced analysis. To this end, the use of ontologies and web semantic technologies has shown high success in many fields. In the specific domain of remote sensing, there are several distinct attempts of ontologies, although they still constitute local prototypes that illustrate the potential in their use (Andrés et al., 2017, Arvor et al., 2019).

On the basis of this necessity, this article proposes a semantic model for the consolidation, integration, reasoning and linking of data (and meta-data), in the context of satellital remote sensing products for EO. With this objective, an OWL (Web Ontology Language) (Group, 2012) ontology has been developed and an RDF repository has been generated to allow advanced SPARQL querying. The proposed ontology, called RESEO (REmote SEnsing Ontology), has been designed to consider remote sensing data and meta-data products in general, including satellite constellations, unmanned aerial vehicles (UAVs), airborne, etc. For the sake of better understanding, the current study is mainly focused on the Sentinel 2 satellite mission of the Copernicus Programme of the European Space Agency (ESA), due to the growing popularity it is exhibiting among the scientific community since its launch in 2015 (Pahlevan, Sarkar, Franz, Balasubramanian, & He, 2017).

Namespace declarations

Table 1: Namespaces used in the document
reseo<https://w3id.org/reseo>
ns<http://creativecommons.org/ns>
owl<http://www.w3.org/2002/07/owl>
xsd<http://www.w3.org/2001/XMLSchema>
swrl<http://www.w3.org/2003/11/swrl>
swrlb<http://www.w3.org/2003/11/swrlb>
skos<http://www.w3.org/2004/02/skos/core>
rdfs<http://www.w3.org/2000/01/rdf-schema>
ssn<http://purl.oclc.org/NET/ssnx/ssn>
swrla<http://swrl.stanford.edu/ontologies/3.3/swrla.owl>
geosparql<http://www.opengis.net/ont/geosparql>
rdf<http://www.w3.org/1999/02/22-rdf-syntax-ns>
terms<http://purl.org/dc/terms>
xml<http://www.w3.org/XML/1998/namespace>
oboe-core<http://ecoinformatics.org/oboe/oboe.1.2/oboe-core.owl>
bibo<http://purl.org/ontology/bibo>
time<http://www.w3.org/2006/time>
vann<http://purl.org/vocab/vann>
reseo<http://khaos.uma.es/green-senti/reseo>
ontology<http://aemet.linkeddata.es/ontology>
dc<http://purl.org/dc/elements/1.1>

RESEO - REmote SEnsin Ontology: Overview back to ToC

This ontology has the following classes and properties.

Classes

Object Properties

Data Properties

Annotation Properties

RESEO - REmote SEnsin Ontology: Description back to ToC

A number of classes have been integrated from other external ontologies, although a set of new generic ones have been designed to be inherited from. This allows the ontology to be easily expanded by adding new Scene, DataSource or Product types depending on the specific end user's case of study. For simplicity, a selection of the most important classes of RESEO are detailed as follows:

- Product. This class defines the data products received from the remote sensing devices, i.e., EO satellites and UAVs. Each Product has associated a timestamp given from the owl-TIME ontology of type time:GeneralDateTimeDescription.5 The Product class is modelled in this version with two subclasses, Sentinel2Product and Landsat8Product which correspond to the data sources worked at the moment in the semantic model, although it can be easily extended with more of them. A set of main object properties of the Product class are: hasDataSource, hasDate, hasProduct, and hasScene. Regarding data properties, they are mostly defined for the subclasses of Product, since they cover specific aspects of the contextual use cases where they are used.
- Data Source. It represents a data provider for a Product. In its current state, this class has the subclass Satellite, which in turn has other two subclasses: Sentinel2 and Landsat8. However, depending on the application, it could be extended with new hierarchies of subclasses to define different sources, such as: other EO satellites (MODIS, WorldView) and UAV products. DataSource includes two main object properties, hasDataSource and isDataSourceOf. It is worth noting that DataSource can also be used as linking element with other external ontologies, since it could cover sources of data in general, but focused on contextualizing with the remote sensing domain of knowledge. In this regard, the subclass Satellite has the object property processedBy with range NDVIProcessing, which is in turn linked with classes Procedure and Observation from the SSN ontology. NDVIProcessing has the data property formula to define how the NDVI is calculated for each satellite. In this regard, a subclass of satellite is Sentinel2, which is connected to MSI, being this last a subclass of Sensor (also taken from SSN).
- Scene. A Scene defines a region of interest with a specific location in the Earth. A scene is contained inside one or more products, which could be captured from different remote sensing devices (Sentinel 2, Landsat 8, UAVs, etc.), although referring to the same specific location and preferably to similar (or close) time instants. Scene is modelled as a subclass of the geosparql:Geometry class of the GeoSPARQL ontology. Object properties defined for Scene are: hasNearestStation hasScene and isSceneOf. Data properties of this class are defined in geosparql:Geometry. The property hasNearestStation is used as linking element with the AEMET.owl ontology that incorporates meteorological data. In this way, the Scene allows to integrate different sensing data referring to a specific location, for a given time period and including the specific climatic conditions, e.g., the imagery products of Sentinel 2 and Landsat 8 capturing the area of the Strait of Gibraltar, and including maximum and minimum temperatures during the first week of August.
- Snapshot. A Snapshot represents the results of an analysis of a Product, over a concrete Scene of interest. The object properties of this class, namely: hasProduct, isProductOf and isSceneOf. Among the data properties, it is worth mentioning those referring to vegetation indexes, such as EVI or NDVI, which are computed with different combination of spectral bands, depending on the remote sensing devices involved in the specific Scene (e.g., Sentinel 2, Landsat 8, etc.). The remaining indexes (SAVI, NSDI, etc.) are defined in this class by following similar schemes of data properties as done with EVI and NDVI. In this sense, NDVI is linked with the OBOE class Characteristic and with the SWEET ontology by means of the property hasCharacteristic. Another interesting property is the cloud cover percentage in sensed images, which is often used as a threshold to select an specific product, or discard it, for the analysis.
- Entity. This class has been reused from the OBOE ontology to model in RESEO those subclasses related to land-cover classification, in the current version: BareSoil, Building, Vegetation and Water. These classes are indeed subclasses of FeatureOfInterest from the SSN ontology. They are used as consequent elements in reasoning rules to perform ontology classification of remote sensing imagery.

Cross-reference for RESEO - REmote SEnsin Ontology classes, object properties and data properties back to ToC

This section provides details for each class and property defined by RESEO - REmote SEnsin Ontology.

Classes

Band 1c back to ToC or Class ToC

IRI: https://w3id.org/reseo#Band01

has super-classes
Raster Image c

Band 10c back to ToC or Class ToC

IRI: https://w3id.org/reseo#Band10

has super-classes
Raster Image c

Band 11c back to ToC or Class ToC

IRI: https://w3id.org/reseo#Band11

has super-classes
Raster Image c

Band 12c back to ToC or Class ToC

IRI: https://w3id.org/reseo#Band12

has super-classes
Raster Image c

Band 2c back to ToC or Class ToC

IRI: https://w3id.org/reseo#Band02

has super-classes
Raster Image c

Band 3c back to ToC or Class ToC

IRI: https://w3id.org/reseo#Band03

has super-classes
Raster Image c

Band 4c back to ToC or Class ToC

IRI: https://w3id.org/reseo#Band04

has super-classes
Raster Image c

Band 5c back to ToC or Class ToC

IRI: https://w3id.org/reseo#Band05

has super-classes
Raster Image c

Band 6c back to ToC or Class ToC

IRI: https://w3id.org/reseo#Band06

has super-classes
Raster Image c

Band 7c back to ToC or Class ToC

IRI: https://w3id.org/reseo#Band07

has super-classes
Raster Image c

Band 8c back to ToC or Class ToC

IRI: https://w3id.org/reseo#Band08

has super-classes
Raster Image c

Band 8Ac back to ToC or Class ToC

IRI: https://w3id.org/reseo#Band8A

has super-classes
Raster Image c

Band 9c back to ToC or Class ToC

IRI: https://w3id.org/reseo#Band09

has super-classes
Raster Image c

Bare Soilc back to ToC or Class ToC

IRI: https://w3id.org/reseo#BareSoil

has super-classes
entity c, feature of interest

Buildingc back to ToC or Class ToC

IRI: https://w3id.org/reseo#Building

has super-classes
entity c, feature of interest

Data sourcec back to ToC or Class ToC

IRI: https://w3id.org/reseo#DataSource

has sub-classes
Satellite c
is in domain of
is data source of op
is in range of
has data source op
is disjoint with
Product c, Scene c, Snapshot c

Landsat 8c back to ToC or Class ToC

IRI: https://w3id.org/reseo#Landsat8

has super-classes
Satellite c

Landsat 8 productc back to ToC or Class ToC

IRI: https://w3id.org/reseo#Landsat8Product

has super-classes
Product c
is in domain of
Cloud cover dp, Cloud cover land dp, Collection category dp, Collection number dp, Data Type dp, Date acquired dp, Datum dp, File date dp, Image quality OLI dp, Image quality TIRS dp, Landsat 8 product properties dp, Landsat product ID dp, Landsat scene ID dp, Map projection dp, Orientation dp, Origin dp, Output format dp, Station identifier dp, UTM zone dp

MSIc back to ToC or Class ToC

IRI: https://w3id.org/reseo#MSI

has super-classes
sensor

NDVIc back to ToC or Class ToC

IRI: https://w3id.org/reseo#NDVI

has super-classes
Raster Image c

NDVI Processingc back to ToC or Class ToC

IRI: https://w3id.org/reseo#NDVIProcessing

has super-classes
thing c
is in domain of
formula dp
is in range of
processed by op

Pixelc back to ToC or Class ToC

IRI: https://w3id.org/reseo#Pixel

has super-classes
thing c
is in domain of
column dp, has value op, row dp

Pixel Valuec back to ToC or Class ToC

IRI: https://w3id.org/reseo#PixelValue

has super-classes
thing c
is in domain of
part of raster image op, value dp
is in range of
has value op

Productc back to ToC or Class ToC

IRI: https://w3id.org/reseo#Product

is equivalent to
(has data source op some Data source c) and (has data source op only Data source c)
(has date op some general date time description c) and (has date op only general date time description c)
has sub-classes
Landsat 8 product c, Sentinel 2 product c
is in domain of
has data source op, has date op, has scene op, is product of op
is in range of
has product op, is data source of op, is date of op, is scene of op, part of product op
is disjoint with
Data source c, Scene c, Snapshot c

Raster Imagec back to ToC or Class ToC

IRI: https://w3id.org/reseo#RasterImage

has super-classes
thing c
has sub-classes
Band 1 c, Band 10 c, Band 11 c, Band 12 c, Band 2 c, Band 3 c, Band 4 c, Band 5 c, Band 6 c, Band 7 c, Band 8 c, Band 8A c, Band 9 c, NDVI c
is in domain of
part of product op
is in range of
part of raster image op

Satellitec back to ToC or Class ToC

IRI: https://w3id.org/reseo#Satellite

has super-classes
Data source c
has sub-classes
Landsat 8 c, Sentinel 2 c
is in domain of
has sensor op, processed by op

Scenec back to ToC or Class ToC

IRI: https://w3id.org/reseo#Scene

has super-classes
geometry
is in domain of
has nearest station op, is scene of op
is in range of
has scene op
is disjoint with
Data source c, Product c, Snapshot c

Sentinel 2c back to ToC or Class ToC

IRI: https://w3id.org/reseo#Sentinel2

has super-classes
Satellite c

Snapshotc back to ToC or Class ToC

IRI: https://w3id.org/reseo#Snapshot

is equivalent to
(has product op some Product c) and (has product op only Product c)
(has scene op some Scene c) and (has scene op only Scene c)
has super-classes
characteristic c
is in domain of
Cloud cover percentage dp, EVI dp, Image EVI dp, Image MOISTURE dp, Image NDSI dp, Image NDVI dp, Image TC dp, MOISTURE dp, NDSI dp, NDVI dp, Snapshot properties dp, TC dp, has product op
is in range of
is product of op, is scene of op
is disjoint with
Data source c, Product c, Scene c

Vegetationc back to ToC or Class ToC

IRI: https://w3id.org/reseo#Vegetation

has super-classes
entity c, feature of interest

Waterc back to ToC or Class ToC

IRI: https://w3id.org/reseo#Water

has super-classes
entity c, feature of interest

Object Properties

has data sourceop back to ToC or Object Property ToC

IRI: https://w3id.org/reseo#hasDataSource

Something (usually a product) has data source
has domain
Product c
has range
Data source c
is inverse of
is data source of op

has dateop back to ToC or Object Property ToC

IRI: https://w3id.org/reseo#hasDate

Something (usually a product) has date

has characteristics: functional

has domain
Product c
has range
general date time description c
is inverse of
is date of op

has nearest stationop back to ToC or Object Property ToC

IRI: https://w3id.org/reseo#hasNearestStation

has domain
Scene c
has range
weather station

has productop back to ToC or Object Property ToC

IRI: https://w3id.org/reseo#hasProduct

Something (usually a snapshot) has product
has domain
Snapshot c
has range
Product c
is inverse of
is product of op

has sceneop back to ToC or Object Property ToC

IRI: https://w3id.org/reseo#hasScene

Something (usually a product) has scene
has domain
spatial object
Product c
has range
Scene c
is inverse of
is scene of op

has sensorop back to ToC or Object Property ToC

IRI: https://w3id.org/reseo#hasSensor

has super-properties
top object property
has domain
Satellite c
has range
sensor

has valueop back to ToC or Object Property ToC

IRI: https://w3id.org/reseo#hasValue

has super-properties
top object property
has domain
Pixel c
has range
Pixel Value c

is data source ofop back to ToC or Object Property ToC

IRI: https://w3id.org/reseo#isDataSourceOf

Is data source of something (usually a product)
has domain
Data source c
has range
Product c
is inverse of
has data source op

is date ofop back to ToC or Object Property ToC

IRI: https://w3id.org/reseo#isDateOf

Is date of something (usually a product)

has characteristics: inverse functional

has domain
general date time description c
has range
Product c
is inverse of
has date op

is product ofop back to ToC or Object Property ToC

IRI: https://w3id.org/reseo#isProductOf

Is product of something (usually a snapshot)
has domain
Product c
has range
Snapshot c
is inverse of
has product op

is scene ofop back to ToC or Object Property ToC

IRI: https://w3id.org/reseo#isSceneOf

Is scene of something (usually a product)
has domain
Scene c
has range
Product c
Snapshot c
is inverse of
has scene op

observed in intervalop back to ToC or Object Property ToC

IRI: http://aemet.linkeddata.es/ontology/observedInInterval

part of productop back to ToC or Object Property ToC

IRI: https://w3id.org/reseo#partOfProduct

has super-properties
top object property
has domain
Raster Image c
has range
Product c

part of raster imageop back to ToC or Object Property ToC

IRI: https://w3id.org/reseo#partOfRasterImage

has super-properties
top object property
has domain
Pixel Value c
has range
Raster Image c

processed byop back to ToC or Object Property ToC

IRI: https://w3id.org/reseo#processedBy

has super-properties
top object property
has domain
Satellite c
has range
NDVI Processing c

Data Properties

Bare soil percentagedp back to ToC or Data Property ToC

IRI: https://w3id.org/reseo#baresoilpercentage

Bare soil percentage Example: 35.747452

has characteristics: functional

has super-properties
Sentinel 2 product properties dp
has domain
Sentinel 2 product c
has range
decimal

Begin positiondp back to ToC or Data Property ToC

IRI: https://w3id.org/reseo#beginposition

Acquisition start date time, i.e. time of the oldest data within the product. Format standard: YYYY-MM-DD hh:mm Example: 2018-06-28 10:56

has characteristics: functional

has super-properties
Sentinel 2 product properties dp
has domain
Sentinel 2 product c
has range
date time

Cloud coverdp back to ToC or Data Property ToC

IRI: https://w3id.org/reseo#cloudcover

Cloud coverage (percent) of a WRS scene. Values: 0.00 - 100.00 -1 = Cloud cover not calculated or assessed
has super-properties
Landsat 8 product properties dp
has domain
Landsat 8 product c
has range
decimal

Cloud cover landdp back to ToC or Data Property ToC

IRI: https://w3id.org/reseo#cloudcoverland

All sensors = Cloud coverage over land (percent) assigned to a WRS scene. Values: -1 = Cloud cover land not calculated or assessed.
has super-properties
Landsat 8 product properties dp
has domain
Landsat 8 product c
has range
decimal

Cloud cover percentagedp back to ToC or Data Property ToC

IRI: https://w3id.org/reseo#cloudcoverpercentage

Cloud cover percentage. Example: 3.8478

has characteristics: functional

has super-properties
Snapshot properties dp
has domain
Snapshot c
has range
decimal

Collection categorydp back to ToC or Data Property ToC

IRI: https://w3id.org/reseo#collectioncategory

Landsat Collection 1 is organized by a tiered inventory structure to indicate the quality and level of processing of the data. Values: T1 = Tier 1 is the highest available quality and processing level. This category is suitable for time-series analysis across the different Landsat sensors. T2 = Tier 2 scenes contain significant cloud cover and have insufficient ground control to generate precision and terrain corrected products. RT = Real-Time indicates initial processing with additional processing required to achieve Tier 1 or Tier 2.
has super-properties
Landsat 8 product properties dp
has domain
Landsat 8 product c
has range
string

Collection numberdp back to ToC or Data Property ToC

IRI: https://w3id.org/reseo#collectionnumber

has super-properties
Landsat 8 product properties dp
has domain
Landsat 8 product c
has range
decimal

columndp back to ToC or Data Property ToC

IRI: https://w3id.org/reseo#column

has super-properties
top data property
has domain
Pixel c
has range
integer

Data take sensing startdp back to ToC or Data Property ToC

IRI: https://w3id.org/reseo#datatakesensingstart

Datatake start date time, i.e time of the oldest data within the datatake. Format standard: YYYY-MM-DDThh:mm:ss.mmmZ Example: 2018-06-28T10:56:19.024Z

has characteristics: functional

has super-properties
Sentinel 2 product properties dp
has domain
Sentinel 2 product c
has range
date time

Data Typedp back to ToC or Data Property ToC

IRI: https://w3id.org/reseo#datatype

Data type identifier string used to create the L-1 product. Values: L1G = L1G Data L1GT = L1Gt Data L1T = L1T Data
has super-properties
Landsat 8 product properties dp
has domain
Landsat 8 product c
has range
string

Datatake identifierdp back to ToC or Data Property ToC

IRI: https://w3id.org/reseo#s2datatakeid

The file name provided by ESA for the continuous acquisition of an image from a SENTINEL-2 satellite in a given MSI imaging mode or a "datatake". Format: GMMM_YYYYMMDDTHHMMSS_Affffff_Nxx.yy G = Datatake Identifier MMM = Mission ID: S2A or S2B YYYYMMDDTHHMMSS = Acquisition Start Date and Time Affffff = Absolute Orbit Number Nxx.yy = Vendor Software Version Example: GS2A_20180603T110041_015392_N02.06

has characteristics: functional

has super-properties
Sentinel 2 product properties dp
has domain
Sentinel 2 product c
has range
string

Date acquireddp back to ToC or Data Property ToC

IRI: https://w3id.org/reseo#dateacquired

Year, month and day that this scene was imaged. Format: YYYY/MM/DD
has super-properties
Landsat 8 product properties dp
has domain
Landsat 8 product c
has range
date time

Datumdp back to ToC or Data Property ToC

IRI: https://w3id.org/reseo#datum

Datum used in creating the image. Values: WGS84 = World Geodetic System 1984
has super-properties
Landsat 8 product properties dp
has domain
Landsat 8 product c
has range
string

End positiondp back to ToC or Data Property ToC

IRI: https://w3id.org/reseo#endposition

Acquisition end date time, i.e. time of the most recent data within the product. Format standard: YYYY-MM-DDThh:mm:ss.mmmZ Example: 2018-06-28T10:56:19.024Z

has characteristics: functional

has super-properties
Sentinel 2 product properties dp
has domain
Sentinel 2 product c
has range
date time

EVIdp back to ToC or Data Property ToC

IRI: https://w3id.org/reseo#evi

EVI (Enhaced vegetation index) Calculation for Sentinel 2 product: 2.5 * (B08 - B04) / ((B08 + 6 * B04 - 7.5 * B02) + 1) This value is the mean of the calculated image Example: 0.27742198

has characteristics: functional

has super-properties
Snapshot properties dp
has domain
Snapshot c
has range
decimal

File datedp back to ToC or Data Property ToC

IRI: https://w3id.org/reseo#filedate

has super-properties
Landsat 8 product properties dp
has domain
Landsat 8 product c
has range
string

Filenamedp back to ToC or Data Property ToC

IRI: https://w3id.org/reseo#filename

Package file name, with extension ‘.SAFE’. Example: S2B_MSIL2A_20180628T105619_N0208_R094_T30SUF_20180628T151421.SAFE

has characteristics: functional

has super-properties
Sentinel 2 product properties dp
has domain
Sentinel 2 product c
has range
string

Footprintdp back to ToC or Data Property ToC

IRI: https://w3id.org/reseo#footprint

Boundaries of the frame in a simplified form.The coordinates shall be declared in a counter-clockwise order. Example: POLYGON ((-5.248379903953922 37.02527578563511,-4.014302538465313 37.042247242200354,-4.001451962964202 36.05254100905861,-5.219917191699283 36.03616769808406,-5.248379903953922 37.02527578563511))

has characteristics: functional

has super-properties
Landsat 8 product properties dp, Sentinel 2 product properties dp
has domain
Sentinel 2 product c
has range
string

Formatdp back to ToC or Data Property ToC

IRI: https://w3id.org/reseo#productformat

Format of the product Example: SAFE

has characteristics: functional

has super-properties
Sentinel 2 product properties dp
has domain
Sentinel 2 product c
has range
string

formuladp back to ToC or Data Property ToC

IRI: https://w3id.org/reseo#formula

has super-properties
top data property
has domain
NDVI Processing c
has range
string

GML footprintdp back to ToC or Data Property ToC

IRI: https://w3id.org/reseo#gmlfootprint

Boundaries of the frame. In addition to the constraints imposed by the GML type for linear rings, the coordinates shall be declared in a counter-clockwise order. Example: <gml:Polygon srsName="http://www.opengis.net/gml/srs/epsg.xml#4326" xmlns:gml="http://www.opengis.net/gml"> <gml:outerBoundaryIs> <gml:LinearRing> <gml:coordinates>37.02527578563511,-5.248379903953922 37.042247242200354,-4.014302538465313 36.05254100905861,-4.001451962964202 36.03616769808406,-5.219917191699283 37.02527578563511,-5.248379903953922</gml:coordinates> </gml:LinearRing> </gml:outerBoundaryIs> </gml:Polygon>

has characteristics: functional

has super-properties
Sentinel 2 product properties dp
has domain
Sentinel 2 product c
has range
string

High proba clouds percentagedp back to ToC or Data Property ToC

IRI: https://w3id.org/reseo#highprobacloudspercentage

High proba clouds percentage Example: 0.232073

has characteristics: functional

has super-properties
Sentinel 2 product properties dp
has domain
Sentinel 2 product c
has range
decimal

Identifierdp back to ToC or Data Property ToC

IRI: https://w3id.org/reseo#identifier

Identifier Example: S2A_MSIL1C_20180603T110041_N0206_R094_T30SUF_20180603T130559

has characteristics: functional

has super-properties
Sentinel 2 product properties dp
has domain
Sentinel 2 product c
has range
string

Image EVIdp back to ToC or Data Property ToC

IRI: https://w3id.org/reseo#evi_image

Image with the value of EVI for each pixel
has super-properties
Snapshot properties dp
has domain
Snapshot c
has range
any u r i

Image MOISTUREdp back to ToC or Data Property ToC

IRI: https://w3id.org/reseo#moisture_image

Image with the value of MOISTURE for each pixel
has super-properties
Snapshot properties dp
has domain
Snapshot c
has range
any u r i

Image NDSIdp back to ToC or Data Property ToC

IRI: https://w3id.org/reseo#ndsi_image

Image with the value of NDSI for each pixel
has super-properties
Snapshot properties dp
has domain
Snapshot c
has range
any u r i

Image NDVIdp back to ToC or Data Property ToC

IRI: https://w3id.org/reseo#ndvi_image

Image with the value of NDVI for each pixel
has super-properties
Snapshot properties dp
has domain
Snapshot c
has range
any u r i

Image quality OLIdp back to ToC or Data Property ToC

IRI: https://w3id.org/reseo#imagequalityoli

Composite image quality for the bands. For Landsat 8 or 9, if scene is OLI or OLI_TIRS combined, value will reflect OLI quality score. If TIRS, the TIRS quality score will be used Values: 9 = Best 0 = Worst -1 = Image quality not calculated or assessed
has super-properties
Landsat 8 product properties dp
has domain
Landsat 8 product c
has range
decimal

Image quality TIRSdp back to ToC or Data Property ToC

IRI: https://w3id.org/reseo#imagequalitytirs

Composite image quality for the bands. For Landsat 8 or 9, if scene is OLI or OLI_TIRS combined, value will reflect OLI quality score. If TIRS, the TIRS quality score will be used Values: 9 = Best 0 = Worst -1 = Image quality not calculated or assessed
has super-properties
Landsat 8 product properties dp
has domain
Landsat 8 product c
has range
decimal

Image TCdp back to ToC or Data Property ToC

IRI: https://w3id.org/reseo#true_color_image

Image with the value of TC for each pixel
has super-properties
Snapshot properties dp
has domain
Snapshot c
has range
any u r i

Ingestion datedp back to ToC or Data Property ToC

IRI: https://w3id.org/reseo#ingestiondate

Represents the time when the product is indexed in the DHuS Service databases. Time is in UTC. Format standard: YYYY-MM-DD hh:mm Example: 2018-06-28 16:38

has characteristics: functional

has super-properties
Sentinel 2 product properties dp
has domain
Sentinel 2 product c
has range
date time

Instrument namedp back to ToC or Data Property ToC

IRI: https://w3id.org/reseo#instrumentname

The instrument name used for acquiring the data. Example: Multi-Spectral Instrument

has characteristics: functional

has super-properties
Sentinel 2 product properties dp
has domain
Sentinel 2 product c
has range
string

Instrument short namedp back to ToC or Data Property ToC

IRI: https://w3id.org/reseo#instrumentshortname

The short name of the instrument used for acquiring the data. Example: MSI

has characteristics: functional

has super-properties
Sentinel 2 product properties dp
has domain
Sentinel 2 product c
has range
string

Landsat 8 product propertiesdp back to ToC or Data Property ToC

IRI: https://w3id.org/reseo#landsat8ProductProperties

Landsat product IDdp back to ToC or Data Property ToC

IRI: https://w3id.org/reseo#landsatproductid

The naming convention of each L7 ETM+ Collection 1 Level-1 image is based on acquisition and processing parameters. Format: LXSS_LLLL_PPPRRR_YYYYMMDD_yyyymmdd_CC_TX L = Landsat X = Sensor (E = Enhanced Thematic Mapper Plus) SS = Satellite (07 = Landsat 7) LLLL = Processing Correction Level (L1TP = precision and terrain, L1GT = systematic terrain, L1GS = systematic) PPP = WRS Path RRR = WRS Row YYYYMMDD = Acquisition Date expressed in Year, Month, Day yyyymmdd = Processing Date expressed in Year, Month, Day CC = Collection Number (01) TX = Collection Category (RT = Real Time, T1 = Tier 1, T2 = Tier 2) Example: LE07_L1TP_029030_20140715_20140805_02_T1
has super-properties
Landsat 8 product properties dp
has domain
Landsat 8 product c
has range
string

Landsat scene IDdp back to ToC or Data Property ToC

IRI: https://w3id.org/reseo#landsatsceneid

Landsat scene identifier. Format: LXSPPPRRRYYYYDDDGSIVV L = Landsat X = Sensor (T = TIRS, O = OLI, C = OLI_TIRS) S = Satellite PPP = WRS Path RRR = WRS Row YYYY = Year of Acquisition DDD = Day of Acquisition Year GSI = Ground Station Identifier VV = Version Example: LC82010342019039LGN00
has super-properties
Landsat 8 product properties dp
has domain
Landsat 8 product c
has range
string

Low proba clouds percentagedp back to ToC or Data Property ToC

IRI: https://w3id.org/reseo#lowprobacloudspercentage

Low proba clouds percentage Example: 1.868199

has characteristics: functional

has super-properties
Sentinel 2 product properties dp
has domain
Sentinel 2 product c
has range
decimal

Map projectiondp back to ToC or Data Property ToC

IRI: https://w3id.org/reseo#mapprojection

L0Ra map projection selectively applied to HDTs based on geographic location. Used for processed archive data. Values: HOM = Hotine Oblique Mercator UTM = Universal Transverse Mercator
has super-properties
Landsat 8 product properties dp
has domain
Landsat 8 product c
has range
string

Medium proba clouds percentagedp back to ToC or Data Property ToC

IRI: https://w3id.org/reseo#mediumprobacloudspercentage

Medium proba clouds percentage Example: 0.577722

has characteristics: functional

has super-properties
Sentinel 2 product properties dp
has domain
Sentinel 2 product c
has range
decimal

MOISTUREdp back to ToC or Data Property ToC

IRI: https://w3id.org/reseo#moisture

GVMI (Global Vegetation Moisture Index) Calculation for Sentinel 2 product: (B8A - B11) / (B8A + B11) This value is the mean of the calculated image Example: -0.02705707

has characteristics: functional

has super-properties
Snapshot properties dp
has domain
Snapshot c
has range
decimal

NDSIdp back to ToC or Data Property ToC

IRI: https://w3id.org/reseo#ndsi

NDSI (Normalized Difference Snow Index) Calculation for Sentinel 2 product: (B03 - B11) / (B03 + B11) This value is the mean of the calculated image Example: 0.0

has characteristics: functional

has super-properties
Snapshot properties dp
has domain
Snapshot c
has range
decimal

NDVIdp back to ToC or Data Property ToC

IRI: https://w3id.org/reseo#ndvi

NDVI (Normalized Difference Vegetation Index) Calculation for Sentinel 2 product: (B08 - B04) / (B08 + B04) This value is the mean of the calculated image Example: 0.14262335

has characteristics: functional

has super-properties
Snapshot properties dp
has domain
Snapshot c
has range
decimal

Not vegetated percentagedp back to ToC or Data Property ToC

IRI: https://w3id.org/reseo#notvegetatedpercentage

Percentage of area non vegetated Example: 33.812419

has characteristics: functional

has super-properties
Sentinel 2 product properties dp
has domain
Sentinel 2 product c
has range
decimal

Orbit directiondp back to ToC or Data Property ToC

IRI: https://w3id.org/reseo#orbitdirection

Orbit direccion while taking he product Can be either 'ASCENDING' or 'DESCENDING' Example: 'ASCENDING'

has characteristics: functional

has super-properties
Sentinel 2 product properties dp
has domain
Sentinel 2 product c
has range
string

Orbit numberdp back to ToC or Data Property ToC

IRI: https://w3id.org/reseo#orbitnumber

Absolute orbit number to which the oldest data unit of the product refers Example: 5525

has characteristics: functional

has super-properties
Sentinel 2 product properties dp
has domain
Sentinel 2 product c
has range
integer

Ordered tile identifierdp back to ToC or Data Property ToC

IRI: https://w3id.org/reseo#hv_order_titleid

Tile identifier to order tiles horizontally. Example: SF30U

has characteristics: functional

has super-properties
Sentinel 2 product properties dp
has domain
Sentinel 2 product c
has range
string

Orientationdp back to ToC or Data Property ToC

IRI: https://w3id.org/reseo#orientation

Orientation used in creating the image. Values: NOMINAL = Nominal Path NORTH_UP = North Up TRUE_NORTH = True North USER = User
has super-properties
Landsat 8 product properties dp
has domain
Landsat 8 product c
has range
string

Origindp back to ToC or Data Property ToC

IRI: https://w3id.org/reseo#origin

Origin of the image Values: Example: "Image courtesy of the U.S. Geological Survey"
has super-properties
Landsat 8 product properties dp
has domain
Landsat 8 product c
has range
string

Output formatdp back to ToC or Data Property ToC

IRI: https://w3id.org/reseo#outputformat

Output format of the image. Values: GEOTIFF = Geostationary Earth Orbit Tagged Image File Format
has super-properties
Landsat 8 product properties dp
has domain
Landsat 8 product c
has range
string

Platform namedp back to ToC or Data Property ToC

IRI: https://w3id.org/reseo#platformname

The mission full name of the platform. This name is not a perfect identifier. Example:Sentinel-2

has characteristics: functional

has super-properties
Sentinel 2 product properties dp
has domain
Sentinel 2 product c
has range
string

Platform NSSDC identifierdp back to ToC or Data Property ToC

IRI: https://w3id.org/reseo#platformidentifier

Univocally identifies the platform. The exact syntax and lexical space of this identifier is defined by the World Data Center for Satellite Information (WDC-SI), which depends on the NASA’s National Space Science Data Center. For each platform, the exact identifier is available from the mission name at the address: http://nssdc.gsfc.nasa.gov/nmc/sc-query.html. Example: 2015-028A

has characteristics: functional

has super-properties
Sentinel 2 product properties dp
has domain
Sentinel 2 product c
has range
string

Platform serial identifierdp back to ToC or Data Property ToC

IRI: https://w3id.org/reseo#platformserialidentifier

The platform serial identifier is the sequence number of the platform among the mission Example: Sentinel-2A

has characteristics: functional

has super-properties
Sentinel 2 product properties dp
has domain
Sentinel 2 product c
has range
string

Processing baselinedp back to ToC or Data Property ToC

IRI: https://w3id.org/reseo#processingbaseline

The processing baseline Example: 2.08

has characteristics: functional

has super-properties
Sentinel 2 product properties dp
has domain
Sentinel 2 product c
has range
decimal

Processing leveldp back to ToC or Data Property ToC

IRI: https://w3id.org/reseo#processinglevel

The level of the last processing Example: Level-2A

has characteristics: functional

has super-properties
Sentinel 2 product properties dp
has domain
Sentinel 2 product c
has range
string

Product typedp back to ToC or Data Property ToC

IRI: https://w3id.org/reseo#producttype

Product type Example: S2MSI2A

has characteristics: functional

has super-properties
Sentinel 2 product properties dp
has domain
Sentinel 2 product c
has range
string

Relative orbit numberdp back to ToC or Data Property ToC

IRI: https://w3id.org/reseo#relativeorbitnumber

Relative orbit number to which the oldest data unit of the product refers Example: 94

has characteristics: functional

has super-properties
Sentinel 2 product properties dp
has domain
Sentinel 2 product c
has range
integer

rowdp back to ToC or Data Property ToC

IRI: https://w3id.org/reseo#row

has super-properties
top data property
has domain
Pixel c
has range
integer

Sensor operational modedp back to ToC or Data Property ToC

IRI: https://w3id.org/reseo#sensoroperationalmode

Sensor mode Example: INS-NOBS

has characteristics: functional

has super-properties
Sentinel 2 product properties dp
has domain
Sentinel 2 product c
has range
string

Sizedp back to ToC or Data Property ToC

IRI: https://w3id.org/reseo#size

Size of the product Example: 634.50 MB

has characteristics: functional

has super-properties
Sentinel 2 product properties dp
has domain
Sentinel 2 product c
has range
string

Snapshot propertiesdp back to ToC or Data Property ToC

IRI: https://w3id.org/reseo#SnapshotProperties

has sub-properties
Cloud cover percentage dp, EVI dp, Image EVI dp, Image MOISTURE dp, Image NDSI dp, Image NDVI dp, Image TC dp, MOISTURE dp, NDSI dp, NDVI dp, TC dp
has domain
Snapshot c

Snow ice percentagedp back to ToC or Data Property ToC

IRI: https://w3id.org/reseo#snowicepercentage

Percentage of snow ice Example: 0.00018899999999999999

has characteristics: functional

has super-properties
Sentinel 2 product properties dp
has domain
Sentinel 2 product c
has range
decimal

Station IDdp back to ToC or Data Property ToC

IRI: https://w3id.org/reseo#stationID

has domain
weather station
has range
string

Station identifierdp back to ToC or Data Property ToC

IRI: https://w3id.org/reseo#stationid

Original ground receiving station to which this data was downlinked. All data received from ground stations are archived at the USGS EROS unless otherwise noted. Maps showing these stations can be found at https://landsat.usgs.gov/about_ground_stations.php. Values: AAA = North America receiving site unknown AA0 = North America receiving site unknown ABG = Awutu Bawjiase, Ghana ABN = Abuja, Nigeria AGS = Poker Flats, Alaska, USA ASA = Alice Springs, Australia ASK = Astana, Kazakhstan ASN = Alice Springs, Australia ATG = Atlanta, Georgia, USA (test site) AWE = Aswan, Egypt BIK = Bishkek, Kyrgyzstan BJC = Beijing, China BKT = Bangkok, Thailand BOC = Bogatá, Colombia CBA = Canberra, Australia CHM = Chetumal, Mexico CLT = Chung-Li, Taiwan CNB = Cuiabá, Brazil COA = Còrdoba, Argentina CPE = Cotopaxi, Ecuador CUB = Cuiabá, Brazil DJK = Daejeon, Korea DKI = Parepare, Indonesia DUB = Dubai, United Arab Emirates DVU = Dunaivtsi, Ukraine DWA = Darwin, Australia EDC = Sioux Falls, South Dakota, USA (aka LGS) EV1 = Eagle Vision 1 EV3 = Eagle Vision 3 EV4 = Eagle Vision 4 FAK = Fairbanks, Alaska, USA FFF = Foreign (non-North American) Receiving Site FUI = Fucino, Italy GDS = Goldstone, California, USA GLC = Gilmore Creek, Alaska, USA GMD = Greenbelt, Maryland, USA GNC = Gatineau, Canada HAJ = Hatoyama, Japan HCA = Datron testing in California, USA HIJ = Hiroshima, Japan HCV = Ho Chi Minh City, Vietnam HLV = Hoa Lac, Vietnam HNV = Hanoi, Vietnam HOA = Hobart, Australia IKR = Irkutsk, Russia ISP = Islamabad, Pakistan IVC = Inuvik, Canada JSA = Hartebeesthoek, South Africa (aka Johannesburg) KHC = KaShi, China KIS = Kiruna, Sweden KLM = Kuala Lumpur, Malaysia KMC = Kunming, China KUJ = Kumamoto, Japan LBG = Libreville, Gabon LGN = Landsat Ground Network (Landsat 8) LGS = Sioux Falls, South Dakota, USA (aka EDC) LUZ = Lusaka, Zambia MCM = Mexico City, Mexico MGR = Magadan, Russia MGS = McMurdo, Antarctica MLK = Malindi, Kenya MOR = Moscow, Russia MPF = Montpelier, France MPS = Maspalomas, Spain MTI = Matera, Italy NOK = Norman, Oklahoma, USA NPA = North Pole, Alaska, USA NP1 = North Pole, Alaska, USA NP2 = North Pole, Alaska, USA NP3 = North Pole, Alaska, USA NP4 = North Pole, Alaska, USA NP5 = North Pole, Alaska, USA NRK = Nairobi, Kenya NSG = Neustrelitz, Germany NSN = Neustrelitz, Germany NWN = Noordwijk, Netherlands OHA = O’Higgins, Antarctica PAC = Prince Albert, Canada PFS = Poker Flats, Alaska, USA PF1 = Poker Flats, Alaska, USA PF2 = Poker Flats, Alaska, USA PUC = Punto Arenas, Chile RPI = Rumpin, Indonesia RSA = Riyadh, Saudi Arabia SAC = Santiago, Chile SEK = Seoul, South, Korea SGI = Shadnagar, India SGP = Singapore SGS = Svalbard, Norway SG1 = Svalbard, Norway SNC = SanYa, China SRT = Si Racha, Thailand TFT = Taipei, Taiwan (fix Location) TGS = Transportable Ground Station TMT = Taipei, Taiwan (mobile location) TOF = Toulouse, France UHI = Honolulu, Hawaii, USA ULK = Ulsan, South Korea ULM = Ulan Bator, Mongolia UPR = Mayagüez, Puerto Rico WPS = Wallops Island, Virginia, USA XX0 = Receiving station unknown XXX = Receiving station unknown
has super-properties
Landsat 8 product properties dp
has domain
Landsat 8 product c
has range
string

Summarydp back to ToC or Data Property ToC

IRI: https://w3id.org/reseo#summary

Summary of the product. Includes date, instrument, sensor mode, satellite and size Example: Date: 2017-09-26T10:58:11.026Z, Instrument: MSI, Mode: , Satellite: Sentinel-2, Size: 699.32 MB

has characteristics: functional

has super-properties
Sentinel 2 product properties dp
has domain
Sentinel 2 product c
has range
string

TCdp back to ToC or Data Property ToC

IRI: https://w3id.org/reseo#true_color

TC (True Color) Calculated using B04 as red value, B03 as green value and B02 as blue value for each pixel This value is the mean of the calculated image Example: 56.023668417104275

has characteristics: functional

has super-properties
Snapshot properties dp
has domain
Snapshot c
has range
decimal

Tile identifierdp back to ToC or Data Property ToC

IRI: https://w3id.org/reseo#tileid

Extract tile identifier (MGRS encoded). If more than one tile is present in the user product, first one is selected. Example: 30SUF

has characteristics: functional

has super-properties
Sentinel 2 product properties dp
has domain
Sentinel 2 product c
has range
string

Titledp back to ToC or Data Property ToC

IRI: https://w3id.org/reseo#title

Title Example: S2A_MSIL2A_20170628T105651_N0205_R094_T30SUF_20170628T110445

has characteristics: functional

has super-properties
Sentinel 2 product properties dp
has domain
Sentinel 2 product c
has range
string

Unclassified percentagedp back to ToC or Data Property ToC

IRI: https://w3id.org/reseo#unclassifiedpercentage

Unclassified percentage Example: 0.377401

has characteristics: functional

has super-properties
Sentinel 2 product properties dp
has domain
Sentinel 2 product c
has range
decimal

UTM zonedp back to ToC or Data Property ToC

IRI: https://w3id.org/reseo#utmzone

UTM (Universal Transverse Mercator) zone number in a map projection. A negative zone indicates that the false northing needs to be applied to the northing coordinate and a positive zone indicates that the false northing has been applied. Values: Negative Zone = Indicates that the false northing needs to be applied. Positive Zone = Indicates that the false northing has been applied.
has super-properties
Landsat 8 product properties dp
has domain
Landsat 8 product c
has range
string

UUIDdp back to ToC or Data Property ToC

IRI: https://w3id.org/reseo#uuid

Universally unique identifier Example: 20f35b69-4eb1-49f1-be5f-b55cec37ea66

has characteristics: functional

has super-properties
Sentinel 2 product properties dp
has domain
Sentinel 2 product c
has range
string

valuedp back to ToC or Data Property ToC

IRI: https://w3id.org/reseo#value

has super-properties
top data property
has domain
Pixel Value c
has range
double

Vegetation percentagedp back to ToC or Data Property ToC

IRI: https://w3id.org/reseo#vegetationpercentage

Percentage of vegetation Example: 10.589334000000001

has characteristics: functional

has super-properties
Sentinel 2 product properties dp
has domain
Sentinel 2 product c
has range
decimal

Water percentagedp back to ToC or Data Property ToC

IRI: https://w3id.org/reseo#waterpercentage

Water of percentage Example: 15.87375

has characteristics: functional

has super-properties
Sentinel 2 product properties dp
has domain
Sentinel 2 product c
has range
decimal

Annotation Properties

bibliographic citationap back to ToC or Annotation Property ToC

IRI: http://purl.org/dc/terms/bibliographicCitation

creatorap back to ToC or Annotation Property ToC

IRI: http://purl.org/dc/elements/1.1/creator

doiap back to ToC or Annotation Property ToC

IRI: http://purl.org/ontology/bibo/doi

is rule enabledap back to ToC or Annotation Property ToC

IRI: http://swrl.stanford.edu/ontologies/3.3/swrla.owl#isRuleEnabled

issuedap back to ToC or Annotation Property ToC

IRI: http://purl.org/dc/terms/issued

preferred namespace prefixap back to ToC or Annotation Property ToC

IRI: http://purl.org/vocab/vann/preferredNamespacePrefix

preferred namespace uriap back to ToC or Annotation Property ToC

IRI: http://purl.org/vocab/vann/preferredNamespaceUri

publisherap back to ToC or Annotation Property ToC

IRI: http://purl.org/dc/terms/publisher

rightsap back to ToC or Annotation Property ToC

IRI: http://purl.org/dc/terms/rights

statusap back to ToC or Annotation Property ToC

IRI: http://purl.org/ontology/bibo/status

Legend back to ToC

c: Classes
op: Object Properties
dp: Data Properties

Acknowledgments back to ToC

The authors would like to thank Silvio Peroni for developing LODE, a Live OWL Documentation Environment, which is used for representing the Cross Referencing Section of this document and Daniel Garijo for developing Widoco, the program used to create the template used in this documentation.