Skip to content

OGC API Features: Static API

Timo edited this page Oct 8, 2023 · 7 revisions

OGC API Features: Static API

The OGC API Features static API exposes the following API calls:

  • /index.json Landing Page in JSON Format
  • /api/index.json OpenAPI documentation of the OGC API Features API
  • /collections/index.json List FeatureCollections defined in the static API
  • /collections/{collectionId}/index.json List a data schema for items present in the feature collection with name {id}
  • /collections/{collectionId}/items/index.json List items included in the feature collection with identifier {id}
  • /collections/{collectionId}/items/{featureid}/index.json Return the feature with feature id {fid} in FeatureCollection {id}

API Capabilities

This API configuration allows to return the data saved in its respective coordinate reference system but does not allow for the following functions, which are usually available in an OGC API Features API:

  • Returning geodata in a different coordinate reference system
  • Execution of CQL functions for filtering data (Always all data, or the result of the CQL expression * will be returned)

Application Example

An example of the static version of OGC API Features can be found in this repository: https://github.com/Research-Squirrel-Engineers/limes

The deployment of the static API and all other files can be found in the branch gh-pages of the repository.

This static API can be accessed in QGIS using the following link :https://research-squirrel-engineers.github.io/limes/index.json

Remarks

Features of the webspace might impact the URLs given to OGC API Features Clients.

GitHub Pages and Content Negotiation

GitHub Pages, at the time of writing, does not support content negotiation. This requires the definition of most URIs to end with "index.json" Webspaces with content negotiation and the correct request header do not need the definition of "index.json" at the end of the URL and will resolve to "index.json" automatically.