Public comment requested: OGC API - Environmental Data Retrieval

Status: 
Please note:  This Request is scheduled to close on 28 September 2020
Open Date: 
Thursday, 2020-08-27
Closing Date: 
Monday, 2020-09-28
To event remaining 4 days

The OGC API - Environmental Data Retrieval (OGC API - EDR) standard uses current web technologies and best practices to enable end-users – or anyone with web development experience – to easily identify and retrieve a subset of data from ‘big data’ stores. The idea is to save those users interested in environmental (or other) data from having to transfer and deal with datasets that inevitably contain data concerning areas or time periods that are irrelevant to their interests. In addition, as a web API, it uses a well-understood and -established mode of interaction that comes with a shallow learning curve.

The new OGC API family of standards uses the OpenAPI specification to define modular API building blocks to spatially enable Web APIs in a consistent way. The OGC API - EDR standard specifies the fundamental API building blocks required to access environmental data resources by requesting data at a Position, within an Area, or along a Trajectory, including optional time and/or vertical coordinates.

The OGC API - EDR standard is not just for accessing ‘environmental’ data but can also support more general geospatial data. The versatility of the OGC API - EDR standard makes it useful across many domains and applications. Example use cases could include: 

  1. A tower crane operator wants to know the wind speed and direction at a series of levels between the surface and 75m above from now and for the next 48 hours. The OGC API - EDR standard could be used to access the gridded weather forecast dataset and return those values to their browser in JSON.
  2. An aviator wants access to all the current aerodrome observations of visibility in a specified area. The OGC API - EDR standard could be used to access a certified METAR (METeorological Aerodrome Report) database and to return those values without the user having to decipher all the METAR content.
  3. A hydrologist would like to retrieve both observed and forecast water levels from a network of gauging stations. The OGC API - EDR standard could be used to retrieve those values by station name rather than geographical coordinates.
  4. A Public Safety Official would like to know the predicted wind speeds along several forecast typhoon tracks or in a corridor around such tracks. The OGC API - EDR standard could be used to interrogate in turn several such predictions.
  5. The OGC API - EDR standard can also be used to access data in non-real-world coordinate systems, such as for retrieving bone density from a 3D MRI scan, at a single position or along a track, or to retrieve the color or gray-scale value from a location on a digitised microscope slide.

 

Comment: 

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

Subscribe: 

You may wish to be added to the distribution list to receive comments as they are submitted


Subscribing to the the list will also allow you to view comments already received, which can be found in the List Archives.