OGC seeks Public Comment on v1.1 of OGC API – Environment Data Retrieval Standard

The OGC API – EDR Standard makes it easier to efficiently access a wide range of geospatial or spatiotemporal data through a uniform, well-defined, simple Web interface.

The Open Geospatial Consortium (OGC) seeks public comment on the candidate Version 1.1 of the OGC API – Environmental Data Retrieval (EDR) Standard. Comments are due by February 27, 2023.

The OGC API – EDR Standard provides a family of lightweight query interfaces to access spatiotemporal data resources by requesting data at a Position, within an Area, along a Trajectory, or through a Corridor. An API compliant with the OGC API – EDR Standard will return only the data needed by the user or client, reducing data transfer time and costs.

The OGC API – EDR Standard makes it easier to efficiently access a wide range of geospatial ‘big data’ through a uniform, well-defined, simple Web interface that shields the user from the complexities of data storage. An example use case of the Standard could be to retrieve, say, weather forecasts for a local area from a much larger national or global forecast dataset – though many other types of data can be accessed through the API.

By defining a small set of query patterns (and no requirement to implement all of them), OGC API – EDR helps to simplify the design and performance-tuning of systems, making it easier to build robust, scalable infrastructures.

Version 1.1 of the OGC API – EDR Standard brings the following improvements:

1. The optional use of HTTP POST as well as the HTTP GET verb. This will allow longer queries, such as when specifying a complicated, detailed area with very many points. The query payload is also encrypted and therefore more secure.
2. Custom dimensions are allowed. As well as the usual 4 dimensions of space and time, (x,y,z,t), other dimensions could be offered by a data collection, such as frequency. The dimensions could also be categorical: that is, not necessarily continuous like space and time. For example, a list of wave or frequency bands, or any enumerated type. A meteorological example would be to allow data retrieval from individual ensemble members.

To learn more about how the family of OGC API Standards work together to provide modular “building blocks for location” that address both simple and the most complex use-cases, visit ogcapi.org.

OGC Members interested in staying up to date on the progress of this standard, or contributing to its development, are encouraged to join the Standards Working Group via the OGC Portal.

The candidate OGC API – Environmental Data Retrieval v1.1 standard is available for review and comment on the OGC Portal. Comments are due by February 27, 2023, and should be submitted via the method outlined on the OGC API – Environmental Data Retrieval v1.1 Standard’s public comment request page.

 

Category: Announcement

This entry was posted on Friday, January 27th, 2023 at 11:41 am. You can follow any responses to this entry through the RSS 2.0 feed. Both comments and pings are currently closed.