Earth Observation Applications Pilot
The goal of the pilot is to evaluate the maturity of the Earth Observation Applications-to-the-Data specifications that has been developed over the last two years as part of various OGC Innovation Program (IP) initiatives in a real-world environment. ‘Real-world’ includes integration of the architecture in an environment requiring authenticated user identity, access controls and billing for resources consumed.
The pilot consists of two parts that are executed in parallel. The first part will define the exact requirements of application developers in terms of data discovery, data loading, data processing, and result delivery. These requirements will define the implementation evaluation and performance criteria. The requirements gathering will be executed at the kickoff meeting workshop. App developers will explain their approach and requirements to platform providers, including aspects such as finding data, working with data, making processes available, and result handling. App developers get informed what is available from platform providers in terms of data and existing processes and corresponding interfaces, processing environments, user identity and authentication, including the possibility to use an existing identity (depending on Identity Provider), quoting options, and billing mechanisms.
The second part invites earth observation platform operators to implement the OGC Earth Observation Applications Pilot architecture as it has been defined in previous IP initiatives. The implementation shall take Part 1 results into account. In essence, this requires implementing two Web API endpoints to allow the registration, deployment and execution of new processes on the platform. Meanwhile, application developers implement their cases to provide test cases for the architecture.
The Goal of Part 2 is for Platform Providers to develop the necessary user infrastructure and ADES/EMS services to allow app developers to deploy their apps, and to allow consumers to obtain quotes and execute processes, with associated billing. Simultaneously, app developers implement and deliver their Earth observation applications. In detail, this part includes the development and deployment of EMS/ADES on platforms, the development and deployment of apps, the registration of apps on enterprise platforms, and testing apps as single entities and as part of workflows. All evaluation results will be recorded and made available in a final report together with a description of future work items.
The overall goal of both parts is to achieve a solid understanding of the suitability of the current architecture. This includes better understanding which elements of the envisioned architecture work, and which parts require what type of modification. In this context, the questions shall be answered regarding what works and what does not, including:
- Discovery and loading of available data
- Discovery and invocation of existing services
- Development and deployment of user defined services
- Usage of external data
- Making results available
- Advertisement of new processes, discovery for consumers
- Enforcement of access controls across platform boundaries (federated/delegated access)
It is expected that the pilot will identify several missing/sub-optimal elements. As is currently hard to predict what form, functionality, or architectural design will require modifications, it is expected that participants have some flexibility during the course of the project in terms of evaluation and analysis. Aspects that cannot be addressed or need further review shall be recorded in a future work definition. Some expected potential issues have been captured in the call for participation. The call for participation further defines the pilot architecture and planned component interactions in full detail.
In addition to the implementations and reports, participants will produce a short video that can be used in outreach activities on a royalty-free basis. The video will illustrate the initial challenge(s) and developed solutions.