Skip to content
Public repo for CAT4.0 work
Branch: master
Clone or download
cmheazel Merge pull request #21 from kalxas/renames
Switch README to OGC API Records
Latest commit 01b9b92 Jan 17, 2020
Type Name Latest commit message Commit time
Failed to load latest commit information.
core Merge branch 'master' into tomkralidis-patch-1 Aug 6, 2019
LICENSE Check in the charter plus some descriptive documentation. Jun 20, 2018

OGC API - Records

This GitHub repository contains the new revision of the OGC's Catalogue Services standard for querying geospatial metadata on the web. It is a complete rewrite of previous versions, focusing on a simple RESTful core specified as reusable OpenAPI components with responses in JSON, XML and HTML.


A Catalogue Service is a standard API for retrieving and managing metadata about geospatial data and services.

GET /collections/myCatalogue/items

Lists all the metadata records in the catalogue.

GET /collections/myCatalogue/items?bbox=160.6,-55.95,-170,-25.89

Lists all the metadata records that describe objects in the New Zealand economic zone.

The response format is determined using standard HTTP content negotiation.

Data is returned in pageable chunks, with each response containing a next link pointing to the next set of response records. The core specification supports a basic set of filters roughly analogous to the OpenSearch and OGC OpenSearch Geo ( query parameters.

GET /collections/myCatalogue/items/{recordId}

Returns a specific metadata record.

Using the standard

A draft of the OGC API - Records standard is available:

  • T.B.D.

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

  • T.B.D.

There have been several implementations of the draft standard, though they are still getting up to compliance with the first draft release:

  • T.B.D.


Join the mailing list or chat at

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 "Catalogue 4.0 User's Guide", is planned.

The current expectation is to have a stable version of the Core specification in 2019. We want to wait for sufficient implementation feedback, mature implementations including a test suite, results from OGC test beds and experience with draft extensions first.


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 standards documents and that all copyright and intellectual property shall be vested to the OGC.

The OGC API Records 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.