08-25, 10:05–10:10 (Europe/Rome), Modulo 0
Exploitation platforms offer a cloud-based virtual work environment where expert users can access data, develop algorithms, conduct analysis close to the data and share their value-adding outcomes. We now have a complementary ecosystem of platforms, data sources and cloud services. To fully exploit the potential of these complementary resources we anticipate the need to encourage interoperation amongst the platforms, such that users of one platform may consume the services of another directly platform-to-platform.
The goal of the EO Exploitation Platform Common Architecture (EOEPCA) project is to define and agree a re-usable exploitation platform architecture by identifying a set of common building blocks that provide their services through open interfaces (e.g. OGC), to encourage interoperation and federation within this Network of Resources. We are also developing an open source Reference Implementation, to validate and refine the architecture, and to provide an implementation to the community.
The Reference Implementation comprises a set of open source components that are available on GitHub, and provided with helm charts for Kubernetes deployment. The components can be used together as an integrated platform, or individually for specific capabilities - which include:
- Application Deployment and Execution Service (ADES) - processing engine for execution of user defined applications via OGC API Processes interface
- Processor Development Environment (PDE) - integrated web tooling to develop, test and package apps for ADES execution
- Resource Catalogue - metadata catalogue for data/applications which provides OGC CSW, API Records, STAC and OpenSearch interfaces
- Data Access - standards-based access to both platform and user-owned data (OGC WCS, WMS, WMTS)
- Workspace - centralises the user’s management of owned resources through personal Resource Catalogue and Data Access services, integrated with platform S3 object storage
- Identity and Access Management - OpenID Connect (OIDC) for authentication (OIDC) and User Managed Access (UMA) for authorization, with integrations for external identity providers
We provide an introduction to each of the building blocks and the open source projects that underpin their development.
All of our work is available on GitHub (https://github.com/EOEPCA), via our website (https://eoepca.org/) and through our helm chart repository (https://eoepca.github.io/helm-charts).
Richard is an experienced (30 years) software engineer and system architect. Richard is the system architect for the ESA's EOEPCA project (EO Exploitation Platform Common Architecture), and participates in the OGC EO Exploitation Platform Domain Working Group. Richard was previously the technical architect for the Copernicus Climate Data Store (CDS), and for the renewal of the Jupiter 2 Control Centre in the Guiana Space Centre, Kourou.
Philip is an experienced software engineer, architect and consultant. Since joining Telespazio (formerly VEGA) in 1996 he has worked on many software intensive systems, for a wide range of satellite missions and applications, covering Earth Observation, Communications and Navigation.