Skip to content
No description, website, or topics provided.
Branch: master
Clone or download
cmheazel Requirement format cleanup
Cleaned up formats for requirements, recomendations, and permissions
Latest commit 790ca12 Jun 14, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
OAPI-Common Requirement format cleanup Jun 14, 2019
OAPI-Elements March 6 update Mar 6, 2019
19-xxx.html publish draft Jun 5, 2019
19-xxx.pdf publish draft Jun 5, 2019
CONTRIBUTORS.md March 6 update Mar 6, 2019
DEVELOPMENT.md March 6 update Mar 6, 2019
LICENSE March 6 update Mar 6, 2019
README.md Cleanup May 7 May 8, 2019
asciidoctor.json Create asciidoctor.json Jun 5, 2019
implementations.md March 6 update Mar 6, 2019
index.adoc Initial population Sep 12, 2018

README.md

OGC API (OAPI) Common Specification

OGC API standards define modular API building blocks to spatially enable Web APIs. The OGC API family of standards is organized by resource type. Each resource has an associated API standard. These resource-specific API standards share a common core. This OGC API Common standard specifies requirements which are shared by all OGC API standards. The OGC API Common standard is maintained on this GitHub repository.

Overview

A Web Feature Service is a standard API that represents collections of geospatial data.

GET /
GET /api
GET /collections
GET /collections

Lists the collections of data on the server that can be queried (7.11), and each describes basic information about the resource, like its id and description, as well as the spatial and temporal extents of all the data contained

GET /collections/{collectionId}/items?bbox=160.6,-55.95,-170,-25.89}

Requests all the data in the collection identified by the "collectionId" that is in the New Zealand economic zone.

Possible response formats are specific to a resource type, but typically HTML and [GeoJSON]((http://geojson.org/) are supported. The format selected for the response is determined using HTTP content negotiation.

Data is returned in pageable chunks, with each response containing a next link as many collections are quite large. The core specification supports a few basic filters, in addition to the bbox filter above, with extensions providing more advanced options. (7.13)

GET /collections/{collectionId}/items/{featureId}

Returns a single 'feature' - something in the real-world (a building, a stream, a county, etc.) that typically is described by a geometry plus other properties. This provides a stable, canonical URL to link to the 'thing'.

Using the standard

A stable draft is available. Note that the draft uses the title "Web Feature Service" or "WFS", version 3.0. This was the original title and newer editor's drafts already use the title "OGC API - Features".

A PDF version is available, too.

Those who want to just see the endpoints and responses can explore the generic OpenAPI definition on SwaggerHub:

Several implementations of the draft standard exist:

Communication

Join the mailing list or chat at https://gitter.im/opengeospatial/WFS_FES

Most all work on the specification takes place in GitHub issues, so browse there to get a good idea of what is happening, as well as past decisions.

Additional Information

Also a non-normative document, the "Users Guide", is being developed.

In addition to feedback from the initial implementations as well as discussions on GitHub and in the OGC/ISO working group, the current draft standard has been tested in a WFS 3.0 Hackathon, the OGC Testbed-14, the OGC Vector Tiles Pilot and other activities.

Feedback for the Core is collected and discussed in the GitHub issues for Part 1, Core. The current expectation is to have a stable version of the Core specification by August 2019. This version would then be the input for the next steps in the standardization process in OGC and ISO/TC 211.

Contributing

The contributor understands that any contributions, if accepted by the OGC Membership and ISO/TC 211, shall be incorporated into OGC and ISO/TC 211 Web Feature Service standards documents and that all copyright and intellectual property shall be vested to the OGC.

The WFS/FES Standards Working Group (SWG) is the group at OGC responsible for the stewardship of the standard, but is working to do as much work in public as possible.

You can’t perform that action at this time.