ogcapi-code-sprint-2021-07's Introduction

July 2021 OGC API Virtual Code Sprint

This Github repository is for the July 2021 OGC API Virtual Code Sprint.

About the Code Sprint

The Open Geospatial Consortium (OGC) invites software developers to the July 2021 OGC API Virtual Code Sprint, to be held from July 21st to July 23rd , 2021. The code sprint will begin at 07:00am EDT on the first day, and end at 05:30pm EDT on the last day.

A pre-event webinar, lasting up to one hour, will take place on July 14th at 09:00am EDT. The webinar will set out the scope of the code sprint and provide an overview of the candidate standards.

The July 2021 OGC API Virtual Code Sprint will focus on the following draft OGC API specifications:

The draft OGC API - Processes specification defines an interface that enables the execution of geospatial computing processes and the retrieval of metadata describing their purpose and functionality. Typically, these processes execute well-defined algorithms that ingest vector and/or coverage data to produce new datasets.
The draft OGC API - Records specification defines an interface that enables discovery and access to metadata records about resources such as features, coverages, tiles / maps, models, assets, services or widgets. The draft specification enables the discovery of geospatial resources by standardizing the way collections of descriptive information about the resources (metadata) are exposed and accessed.
The draft OGC API - Coverages specification defines an interface that enables access to coverages that are modeled according to the Coverage Implementation Schema (CIS) 1.1. Coverages are represented by some binary or ASCII serialization, specified by some data (encoding) format. Arguably the most popular type of coverage is that of a gridded coverage. Gridded coverages have a grid as their domain set describing the direct positions in multi-dimensional coordinate space, depending on the type of grid. Satellite imagery is typically modeled as a gridded coverage, for example.

ogcapi-code-sprint-2021-07's People

Contributors

Stargazers

Watchers

ogcapi-code-sprint-2021-07's Issues

How to support propagation of Exceptions up a workflow

The proposed Workflows extension of OGC API - Processes needs to include support for propagation of errors up a service chain.

For example, in a 10 step workflow, if an error occurs at step 5, the process at step 5 needs to be able to notify the processes at step 1, 2, 3 and 4 that an error occurred (e.g. in case a roll back is needed).

Some of the research questions will include:

How should the Exception class be modelled (i.e. profiling of the Exception class from OGC API - Common)?
How will the process at step 5 notify the processes up the chain and also the client that triggered the workflow?