Public comment requested: OGC API - Processes - Part 1: Core
The draft OGC API - Processes Standard specifies a Web API that enables the execution of computing processes and the retrieval of metadata describing their purpose and functionality. For example, these processes could combine raster, vector, coverage and/or point cloud data with well-defined algorithms to produce new raster, vector, coverage and/or point cloud information.
The draft OGC API - Processes Standard builds on the Web Processing Service (WPS) 2.0 standard and defines the processing standards to communicate in a RESTful manner using JSON encodings. This API is a newer and more modern way of programming and interacting with resources over the web while allowing better integration into existing software packages.
In many cases, location data, including data from sensors, must be processed before the information can be effectively used. OGC API - Processes, just like the OGC WPS Interface Standard, provides a standard interface that simplifies the task of making simple or complex computational geospatial processing services accessible via web services. Such services include well-known processes found in GIS software as well as specialized processes for 2D/3D/4D modeling and simulation. The API also makes it easy for developers to implement microservices that can handle location data.
The draft OGC API - Processes Standard provides a similarly robust, interoperable, and versatile protocol for process execution across the Web. OGC API - Processes supports both immediate processing for computational tasks that take little time and asynchronous processing for more complex and time-consuming tasks.
As with other OGC APIs, OGC API - Processes consists of optional parts that each provide extra functionality. This specification, Part 1: Core, is intended to be a minimal useful API for the execution of processes from the geospatial domain. There are no constraints on the types of processes that can be published through the API. Examples of processes that have been demonstrated during the development of the draft API standard include routing, contour generation, buffering, coverage processing and several others. The API is therefore expected to be applicable to several domains.
Comments can be submitted to a dedicated email reflector for a thirty day period ending on the "Close request date" listed above, Comments received will be consolidated and reviewed by OGC members for incorporation into the document. Please submit your comments using the following link: requests [at] lists.opengeospatial.org (Click here to submit comments) The link provided above should include a standard template in the message body. If the preloaded message body does not work properly using your mail client, please refer to the following template for the message body: Comments Template