Skip to content

Releases: opengeospatial/ogcapi-features

OGC API - Features - Part 1: Core, Version 1.0.0

14 Oct 20:08
Compare
Choose a tag to compare

The first published version of "OGC API - Features - Part 1: Core".

The document is published at http://docs.opengeospatial.org/is/17-069r3/17-069r3.html.

The schema documents are published in the OGC schema repository at http://schemas.opengis.net/ogcapi/features/part1/1.0/.

The home page of the OGC API Features standards on the OGC website is https://www.opengeospatial.org/standards/ogcapi-features.

OGC API - Features - Part 1: Core, Version 1.0.0-draft.2

11 Jul 10:53
Compare
Choose a tag to compare

Release candidate of "OGC API - Features - Part 1: Core".

The OGC Technical Committee has approved an electronic vote to approve release of the document as an OGC Adopted Standard.

The attached zip archive has been uploaded to the OGC pending documents. It contains:

  • the specification document (17-069r2.html)
  • the OpenAPI building blocks (folder "openapi")
  • the XML schema documents (folder "xml")

OGC API - Features - Part 1: Core, Version 1.0.0-draft.1

26 Jun 11:16
Compare
Choose a tag to compare

This is a draft release of OGC API - Features - Part 1: Core. It is mostly complete. Open actions:

  • Complete and review the Abstract Test Suite
  • Some details in the XML encoding
  • Update submitters
  • Persistent URL for examples
  • Registration of WGS 84 lon/lat/h

WFS 3.0 - Part 1: Core, 1st Draft

07 Apr 12:10
Compare
Choose a tag to compare
Pre-release

OGC Web Feature Service 3.0 - Part 1: Core, First Draft Release

This is the first draft release of Part 1 (Core) of the OGC Web Feature Service 3.0 standard after several months of discussions and testing. It will be used as input for the OGC Testbed-14 and for the next steps in the standardisation process in OGC and ISO/TC 211.

The current expectation is to have a stable version of this specification in 2019. Before finalising this specification we want to take implementation feedback into account, have mature implementations including a test suite, experience with extensions and resolve any open issues or comments.