OGC
®
Some Statistics (Sep 2019)
• 12 205 processing CPU hours / month
consumed solely by users
• Products
– Generated: 8872 Published: 7796 Downloaded: 10749
• Overall 251 selected users (121 organisations)
– Carrying out projects on the platform via the early
adopters programme to use data processing services,
publish results and provide feedback to improve the platform
• 1545 registered users (96 countries)
– To search for EO data acquisitions, shared results
from processing jobs, and public information layers
OGC
®
API driven
• Data Discovery
– OGC OpenSearch
– Geo & Time Extensions
– EO Extensions
• Data Packaging
– OGC OWS Context
• Application Packaging
– OGC OWS Context + T13/14
• Data Processing Execution
– WPS 2.0 API
OGC
®
Data Discovery API
• Earth Observation Catalogues from a Portal or a Jupyter
• Accessing OGC OpenSearch API directly from Python
and explore catalogue contents as Panda/Geopanda data
structures
OGC
®
• Invoke on-demand data processing services from
authorized application Portals or a Jupyter Notebooks
with OGC WPS 2.0 API
• Analyse and exploit data results
On-demand Data Processing API
OGC
®
Systematic Data Processing API
• Invoke systematic data processing services from
authorized application Portals or a Jupyter Notebooks
• Analyse and exploit data results
OGC
®
EO Application Development
Implement an EO application using your IDE
on your machine using the client APIs
Example shown:
PyCharm IDE with EO application to process
Sentinel-1 GRD data for sigma0 calculation
using SNAP
OGC
®
EO Application Version Control
Use a software repository like GitHub or
GitLab to host the EO application code and
files → versioning and well tracked
releases
Our Sentinel-1 sigma0 SNAP application is
is hosted by GitLab
OGC
®
EO Application build process
Continuous Integration/Deployment
environment to build, package and
dockerize the EO application release(s)
Our Sentinel-1 sigma0 SNAP application is
now built, packaged and dockerized
OGC
®
EO Application - Package
The build, package and dockerize process
produces an Application package with:
- A docker image
- Its associated OWS-Context
document
The docker image is accessible on a
docker-hub
OGC
®
EO Application Exploitation - Docker
To consume the EO Application docker
image:
- pull the docker image with the EO
Application from the docker-hub
- run the docker image in a container
OGC
®
EO Application Exploitation - Deploy
On TEPs, the Application Package is
deployed and the EO Application exposed
as a Web Processing Service (WPS 2.0
API)
OGC
®
EO Application exploitation on a TEP
The deployed Application Package as a
Web Processing Service (WPS 2.0 API) on
a TEP is exploited using Cloud resources
(e.g. DIAS)
OGC
®
EO Application Exploitation on a Notebook
Consume the EO application via WPS API
2.0, from a Jupyter Notebook or desktop
application client, to analyse and exploit
data results
OGC
®
Takeaway Messages
• Users benefit from fast access to EO data,
storage capacity and processing resources
offered by platform-based solutions
• A hosted processing platform is a
partnership that needs the support
of scientist/developer to offer operational
services providing value added information
to the community
• Platform e-collaboration and reproducible
knowledge promote innovation and
response capacity
OGC
®
Platform for Earth Sciences Communities
• to share their findings, streamline their
creation of new data products and
make these accessible, interoperable
• communities remain owners of their
created assets, and decide how to share
these on the platforms, for other users to
find and reuse without a platform lock-in
• to document their developments as
reproducible experiments
• with FAIR guiding principles to make
data findable, accessible, interoperable
and reusable