work-in-progress
This page lists software packages that implement approved or draft OGC API Features standards. Draft standards are only added once they have a tagged version. Currently the following parts are covered:
Two types of software packages are distinguished:
-
Server implementations are software products that can be used to set up APIs that implement OGC API Features conformance classes.
-
Client implementations are software products that connect to APIs implementing OGC API Features conformance classes to use the feature data.
If you have a server or client implementation of OGC API Features, we welcome a pull request to update this page to add or update an entry for the product. You may add a link to a sub-page with more details in the servers and clients folders of this repository and you may add a link to the associated entry in the OGC Product Database. Please include a contact email address so that we may later contact you in case of page updates or questions.
If you have a server product, please consider to register it in the OGC Product Database and test it for compliance, too.
The columns for each part list the conformance classes of the standard that are implemented by the server implementation. The conformance classes available in a specific API that is provided using the implementation will be listed in the Conformance Declaration resource of the API.
| Product | Part 1 | Part 2 | Part 3 | OGC Product Database | Contact email |
|---|---|---|---|---|---|
|
|
|
portele [at] interactive-instruments.de |
||
|
|
|
pvretano [at] cubewerx.com |
||
please consult the product documentation for details |
|||||
please consult the product documentation for details |
|||||
please consult the product documentation for details |
|||||
|
|
- |
- |
||
please consult the product documentation for details |
|||||
please consult the product documentation for details |
|||||
GNOSIS Map Server |
please consult the product documentation for details |
||||
TerraNexus OGC API Server |
please consult the product documentation for details |
||||
|
|
- |
|||
The columns for each part list the conformance classes of the standard that the client uses when connecting to an API and the API supports that conformance class.
| Product | Part 1 | Part 2 | Part 3 | OGC Product Database | Contact email |
|---|---|---|---|---|---|
|
- |
- |
- |
||
please consult the product documentation for details |
- |
||||
|
- |
- |
- |
||
| Product | Part 1 | Part 2 | Part 3 | OGC Product Database | Contact email |
|---|---|---|---|---|---|
|
- |
|
- |
||
|
- |
- |
- |
||
ArcGIS Runtime API for .NET/Android/iOS/Java/Qt (OGCFeatureCollectionTable) |
|
|
|
- |
|
|
|
- |
hellokaoto [at] gmail.com |
| Product | Part 1 | Part 2 | Part 3 | OGC Product Database | Contact email |
|---|---|---|---|---|---|
|
|
- |
- |
||
|
|
|
haoliang.yu [at] outlook.com |
||
|
- |
- |
- |
ivan [at] sanchezortega.es |
|
|
|
|
- |
michaelkeller03 [at] gmail.com |
|
|
|
- |
- |
olivia.guyot [at] camptocamp |
Since most APIs implementing OGC API Features support the GeoJSON conformance class, any client that is able to process GeoJSON feature collections and features can also use feature data provide by such APIs by directly accessing the Features resources (at the relative path collections/{collectionId}/items) as long as they can fetch all features in a single request without paging.
See the examples and descriptions for clients for more information, for example, for Leaflet, OpenLayers and Mapbox GL JS.
The SpatioTemporal Asset Catalog (STAC) specification, more precisely the STAC API specification, is based on OGC API Features. Thus STAC API is a superset of OGC API - Features - Part 1: Core, in that OGC API Features defines many of the resources that STAC uses. A STAC API should be compatible and usable with OGC API Features clients and a STAC server should also be a valid OGC API Features server.
See the STAC implementations page for implementations.