https://docs.ogc.org/is/18-058/18-058.html
| requirement | applicable | description |
|---|---|---|
| /req/crs/crs-uri | ❌ | {Authoritie}:{Code} is used in the request and a URN is used in the feature response. No URI is used. |
| /req/crs/fc-md-crs-list | ❌ | We don't have a collection object in this API |
| /req/crs/fc-md-storageCrs | ❌ | No spatial feature collection is stored on the server |
| /req/crs/fc-md-storageCrs-valid-value | ❌ | No storageCrs is advertised |
| /req/crs/fc-md-crs-list-global | ❌ | No spatial feature collection is advertised |
| /req/crs/fc-bbox-crs-definition | ❌ | No request with a bbox or bbox-crs are supported |
| /req/crs/fc-bbox-crs-valid-value | ❌ | No bbox-crs is supported |
| /req/crs/fc-bbox-crs-valid-defaultValue | ❌ | No bbox-crs is supported |
| /req/crs/fc-bbox-crs-action | ❌ | No bbox-crs is specified |
| /req/crs/fc-crs-definition | ❌ | No requests on a features or feature resource is available |
| /req/crs/fc-crs-valid-value | ❌ | No crs on a featues or feature resource is supported |
| /req/crs/fc-crs-default-value | ❌ | No crs on a featues or feature resource is supported |
| /req/crs/fc-crs-action | ❌ | No crs is specified |
| /req/crs/geojson | ❕ | We are subjected to this rfc7946 |
| /req/crs/ogc-crs-header | ❌ | We don't use the CRS query parameter because we need 2 CRS for our API. Using a named one like source-crs and target-crs makes it clear what the purpose is |
| /req/crs/ogc-crs-header-value | ❌ | No Content-Crs header is return in the response |
| recommendation | applicable | description |
|---|---|---|
| /rec/crs/crs-format-model | ❌ | see requirement /req/crs/crs-uri |
| /rec/crs/fc-md-coordinateEpoch | ❌ | No spatial feature collection is stored on the server |
| recommendation | applicable | description |
|---|---|---|
| /per/crs/fc-crs-action | ❌ | No features or feature resources are available |