eomEX+ (Earth Observation Metadata Explorer) is a very slim web catalogue based on Flask. It allows querying the EODC data archive trough a simple Web GUI as well as an API.
The back-end of eomEX+ is the EODC pycsw server (an OGC CSW server implementation).
Info
A more extensive API is provided by the EODC CSW server, located at
https://csw.eodc.eu).
Please refer to the following sites for more information on how to query CSW servers:
The eomEX+ Web GUI allows querying the EODC data archive by keywords, temporal extent and bounding box. The results are sorted by the temporal extent start date.
- Keywords
-
Keywords can be used to distinguish between Satellites (e.g. 'Sentinel-1', 'Sentinel-1A', 'Sentinel-1B', 'Sentinel-2', 'Sentinel-3'), sensor modes ('IW', 'EW', ...), product types (e.g. 'GRD', 'SLC', ...) and other parameters.
Multiple keywords are supportet, they have to be separated by comma.
If you are e.g. looking for Sentinel-1B, Ground Range Detected products, recorded in descending orbit, in HH polarisation, your query string would be "Sentinel-1B,GRD,descending,HH".
You can find an overview of all dataset specific keywords in the
keyword glossary.
- Start date
- Begin of the time period covered by the content of the dataset [YYYY-MM-DD]
- End date
- End of the time period covered by the content of the dataset [YYYY-MM-DD]
- North
- Northern-most coordinate of the limit of the dataset extent, expressed in latitude in decimal degrees (positive north).
- East
- Eastern-most coordinate of the limit of the dataset extent, expressed in longitude in decimal degrees (positive east).
- South
- Southern-most coordinate of the limit of the dataset extent, expressed in latitude in decimal degrees (positive north).
- West
- Western-most coordinate of the limit of the dataset extent, expressed in longitude in decimal degrees (positive east).
The API of eomEX can be accessed under https://eomex.eodc.eu/api. It allowes querying the EODC data archive in a similar matter as the web GUI, however, the results are returned as JSON file. This file contains a dictionary with four fields:
- filelist
- List of files containing the full path on the EODC storage
- matches
- Number of files found with a query
- nextrecord
- Position of the next record. This information is useful if the number of matches is bigger than the number of returned records. You can access the 'second page' of the results by setting the startposition parameter to the value of nextrecord.
- returned
- Number of files returned by the query
The results are sorted by the temporal extent start date.
An example querying Sentinel-1A GRD products over the area of Austria in January 2017:
https://eomex.eodc.eu/api?keywords=Sentinel-1A,GRD&maxrecords=10&tempextent_begin=2017-01-01&tempextent_end=2017-01-31&bbox=[46.3,9.4,49.02,17.2]
API reference
- keywords
-
Keywords can be used to distinguish between Satellites (e.g. 'Sentinel-1', 'Sentinel-1A', 'Sentinel-1B', 'Sentinel-2', 'Sentinel-3'), sensor modes ('IW', 'EW', ...), product types (e.g. 'GRD', 'SLC', ...) and other parameters.
Multiple keywords are supportet, they have to be separated by comma.
If you are e.g. looking for Sentinel-1B, Ground Range Detected products, recorded in descending orbit, in HH polarisation, your query string would be "Sentinel-1B,GRD,descending,HH"
...&keywords=Sentinel-1B,GRD,descending,HH
- tempextent_begin
-
Begin of the time period covered by the content of the dataset [YYYY-MM-DD]
...&tempextent_begin=2017-01-01
- tempextent_end
-
End of the time period covered by the content of the dataset [YYYY-MM-DD]
...&tempextent_end=2017-01-31
- bbox
- Bounding box of the dataset, composed as followed:
[southbound_latitude,westbound_longitude,northbound_latitude,eastbound_longitude]
...&bbox=[0,0,90,180]
- maxrecords
-
The maximum number of records to return (default is 1000). The server side maximum is set to 1000.
...&maxrecords=50
- startposition
-
Requests a slice of the result set, starting at this position (default is 0).
Please note: startposition=1 ≙ startposition=0
...&startposition=51
Sentinel-2
- cloud_coverage
- Maximum percentage of cloud coverage
This section gives an overview about satellite/dataset/product specific keywords that can be used for querying.
Sentinel
|
Parameter |
Keyword |
| Satellite |
Sentinel 1 |
Sentinel-1 |
| Sentinel 1A |
Sentinel-1A |
| Sentinel 1B |
Sentinel-1B |
| Sentinel 2 |
Sentinel-2 |
| Sentinel 3 |
Sentinel-3 |
| Orbit direction |
ascending |
ascending |
| descending |
descending |
Sentinel-1
|
Parameter |
Keyword |
| Product |
Ground Range Detected |
GRD |
| Single Look Complex |
SLC |
| Mode |
Extra Wide Swath |
EW |
| Interferometric Wide swath |
IW |
| Stripmap |
SM |
| High Resolution |
HR |
| Medium Resolution |
MR |
| Polarisation |
HH |
HH |
| VV |
VV |
| HH+HV |
HH+HV |
| VV+VH |
VV+VH |
Sentinel-2
No specific keywords given.
Sentinel-3
|
Parameter |
Keyword |
| Product |
Ocean Land Colour Instrument |
OLCI |
| Sea and Land Surface Temperature Radiometer |
SLSTR |
| Sar Radar Altimeter |
SRAL |
Sentinel-3 OLCI
|
Parameter |
Keyword |
| Resolution |
Full Resolution |
FR |
| Reduced Resolution |
RR |
Sentinel-3 SRAL
|
Parameter |
Keyword |
| Level |
Level 1 |
Level-1 |
| Level 2 |
Level-2 |
The following examples demonstrate a combination of queries by keyword, temporal and spatial extent.
-
Sentinel-1A GRDH, IW, descending orbit, 2nd of April 2016
-
https://eomex.eodc.eu/api?keywords=Sentinel-1A,GRD,HR,IW,descending&tempextent_begin=2016-04-02&tempextent_end=2016-04-02
-
Sentinel-1B GRD, Medium Resolution over Austria
-
https://eomex.eodc.eu/api?keywords=Sentinel-1B,GRD,MR&bbox=[46.3,9.4,49.02,17.2]
-
Sentinel-2 data over Iceland on February 28th, 2017
-
https://eomex.eodc.eu/api?keywords=Sentinel-2A&tempextent_begin=2017-02-28&tempextent_end=2017-02-28&bbox=[63.27,-24.78,66.9,-13.07]
-
Sentinel-3 OLCI Reduced Resolution data from Jan-Mar 2017
-
https://eomex.eodc.eu/api?keywords=Sentinel-3A,OLCI,RR&tempextent_begin=2017-01-01&tempextent_end=2017-03-31&bbox=[66,-180,90,180]
For querying large datasets with more than 1000 results (the server side limit for returned records is set to 1000), it is useful to manually set a maxrecord value and browse through the result lists using the startposition parameter.
In the following example we are looking for Sentinel 2 data recorded at the 1st of April 2017. Since there are usually > 1000 Sentinel 2 scenes available each day, it won't be possible to get a complete list of files with only one query. This is where the startposition parameter comes in handy.
Q1 shows the query as described above (we additionally set maxrecords to 5 for formatting reasons).
Q1: Sentinel 2 data in April 2017, limit to 5 results
To get to the next results, we set the startposition parameter to 6 (= the 'nextrecord' value of the result of Q1):
Q2: Sentinel 2 data in April 2017, limit to 5 results, start at position 6
To get to the following results, we could now set the startposition parameter to 11, 16, 21 and so on.
As it's name already suggests, eomEX+ is a Metadata Explorer. At the moment, data access is not a part of eomEX+. In general, data access is reserved for EODC partners, who can access the data through the EODC cloud infrastructure (e.g. through a virtual machine on OpenStack).
If you are interested in accessing our data archive, please contat us through our support request form.