Geographic information – Geospatial API for features — Part 2: Coordinate Reference Systems by Reference
Introduction: OGC API standards define modular API building blocks to spatially enable Web APIs in a consistent way. The OpenAPI specification is used to define the API building blocks. The OGC API family of standards is organized by resource type. This document extends the fundamental API building blocks for interacting with features. The spatial data community uses the term 'feature' for things in the real world that are of interest. For those not familiar with the term 'feature,' the explanations on Spatial Things, Features and Geometry in the W3C/OGC Spatial Data on the Web Best Practice document[6] provide more detail. OGC API Features provides API building blocks to create, modify and query features on the Web. OGC API Features is comprised of multiple parts, each of them is a separate standard. This document extends the core capabilities specified in OGC API — Features — Part 1: Core (ISO 19168-1) with the ability to use coordinate reference system identifiers other than the defaults defined in the core. By default, every API implementing this document will provide access to a single dataset. Rather than sharing the data as a complete dataset, the OGC API Features standards offer direct, fine-grained access to the data at the feature (object) level. The API building blocks specified in this document are consistent with the architecture of the Web. In particular, the API design is guided by the IETF HTTP/HTTPS RFCs, the W3C Data on the Web Best Practices, the W3C/OGC Spatial Data on
Scope: This document specifies an extension to the Geospatial API for Features — Part 1: Core standard that defines the behaviour of a server that supports the ability to present geometry valued properties in a response document in one from a list of supported Coordinates Reference Systems (CRS). Each supported CRS is specified by reference using a uniform resource identifier (URI). This document specifies: — how, for each offered feature collection, a server advertises the list of supported CRS identifiers; — how the coordinates of geometry valued feature properties can be accessed in one of the supported CRSs; — how features can be accessed from the server using a bounding box specified in one of the supported CRSs; and — how a server can declare the CRS used to present feature resources.