Skip to content

Home

Jump to bottom
Chris Little edited this page Dec 5, 2024 · 214 revisions

Working Group Sign Up

While the Environmental Data Retrieval API Standards Working Group (EDR SWG) is being conducted as an open process, taking part in activities of the SWG other than contributing through github issues, requires membership in the SWG.

Meetings

Members of the OGC can also access recordings of the meetings, stored in the OGC Portal in the EDR API project folder.

Next

Last

Older meetings

Progress

The WG had a virtual Hackathon/Sprint in March 2020. It was organized using another GitHub repo. The final report is also on the OGC Portal.

OGC Architecture Board Review was held on Tuesday 28 July 2020.

The draft standard was released by OGC for public comment on 27 August 2020. The comment period closed on 28 September 2020.

A number of example implementations are available and details of them can be found here.

A second virtual Hackathon/Sprint was held 9-10 November 2020. It was organized using another GitHub repo. There was a public Webinar beforehand on Wednesday 4 November 2020.

The OGC Technical Committee on the 11 December 2020 voted to hold an electronic vote of all its Technical Members to recommend the current specification as a full standard. There are several comments on the proposed standard. The vote concluded on the 8 March 2021: quorum achieved, 23 YES votes, 4 NO votes, 8 Abstain. The candidate standard was considered by the OGC Planning Committee on 30 March 2021.

In the Planning Committee, there was: a comprehensive discussion; agreement to not change the name of the standard; recognition that there may be need for a more generic spatio-temporal data retrieval API in the future as part of the OGC API suite; and the standard was Approved with No Objections To Unanimous Consent. As of 28 April 2021, the standard is being edited for formal publication.

The OGC API-EDR Standard was published on 13 September 2021

A formal draft Conformance Test Suite was developed and was publicly available from Dec 2022 using the open source test suite generator TeamEngine.

All versions and parts of the Standard conform to the OGC Web API guidelines. See the completed checklists.

A formal Corrigendum, V1.0.1, was approved and published in 2022. Further corrections have been identified, but was issued with V1.1 rather than create a V1.0.2.

The backward compatible V1.1 was approved 9 June 2023 and published, having had a Public Comment period at the end of 2022 and early 2023. It supports HTTP POST as well as GET, and also categorical and custom dimensions as well as the usual spatial and temporal dimensions.

OGC API-EDR Part 2: Publish-Subscribe Workflow to support the Pub/Sub pattern was published 23 September 2024.

Work has started on V1.2 with minor improvements, a Part 3 to support restrictive profiles and probably a Part 4 to support requests for Aggregation of data or Summary Statistics. Data-stream responses are a possibility for future work.

FAQ

Frequently Asked Questions pages are being established and will help define some Best Practices.

Outreach

As well as past presentations and hackathons, future opportunities to present the EDR API and the other OGC APIs are being listed here.

During 8-10 February 2021, there was a presentation and demo at the ECMWF virtual Workshop on Weather and Climate in the Cloud.

OGC API-EDR people, implementations and server-side data were involved in the joint OGC-OSGeo-ApacheSF Sprint 2021 held virtually from 17 to 19 February 2021. They intended to work on these topics.

There will be OGC API Sprints/Hackathons in May and June 2021, focusing on Maps/Styles/Tiles and Coverages/Processes/Routes/GeoPose respectively. These may be an opportunity to explore the interoperability of the EDR API with these proposed APIs.

There will probably be an OGC API Sprint/Hackathon focusing on the EDR API in September 2021.

There will also be a Moving Features Summit in either June or September 2021. As the trajectory query used in the EDR API uses the same logical definition, it may be a good opportunity to explore interoperability of these standards.

Future Work

Future Work placeholder

Home

Repo

Issues

FAQs

Portal

Examples

Implementations

OAB-Review

Compliance-to-OGC-Web-API-Guidelines

Clone this wiki locally