-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
reviewed API against OGC API Feature P2 CRS
- Loading branch information
1 parent
25bb8a8
commit 57c5e76
Showing
1 changed file
with
38 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,38 @@ | ||
# OGC API - Features - Part 2: Coordinate Reference Systems by Reference | ||
|
||
<https://docs.ogc.org/is/18-058/18-058.html> | ||
|
||
## Requirements | ||
|
||
| requirement | applicable | description | | ||
| --- | --- | --- | | ||
| /req/crs/crs-uri | :x: | {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 | :x: | We don't have a `collection` object in this API | | ||
| /req/crs/fc-md-storageCrs | :x: | No spatial feature collection is stored on the server | | ||
| /req/crs/fc-md-storageCrs-valid-value | :x: | No storageCrs is advertised | | ||
| /req/crs/fc-md-crs-list-global | :x: | No spatial feature collection is advertised | | ||
| /req/crs/fc-bbox-crs-definition | :x: | No request with a bbox or bbox-crs are supported | | ||
| /req/crs/fc-bbox-crs-valid-value | :x: | No bbox-crs is supported | | ||
| /req/crs/fc-bbox-crs-valid-defaultValue | :x: | No bbox-crs is supported | | ||
| /req/crs/fc-bbox-crs-action | :x: | No bbox-crs is specified | | ||
| /req/crs/fc-crs-definition | :x: | No requests on a features or feature resource is available | | ||
| /req/crs/fc-crs-valid-value | :x: | No crs on a featues or feature resource is supported | | ||
| /req/crs/fc-crs-default-value | :x: | No crs on a featues or feature resource is supported | | ||
| /req/crs/fc-crs-action | :x: | No crs is specified | | ||
| /req/crs/geojson | :grey_exclamation: | We are subjected to this rfc7946 | | ||
| /req/crs/ogc-crs-header | :x: | 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 | :x: | No `Content-Crs` header is return in the response | | ||
|
||
## Recommendations | ||
|
||
| recommendation | applicable | description | | ||
| --- | --- | --- | | ||
| /rec/crs/crs-format-model | :x: | see requirement `/req/crs/crs-uri` | | ||
| /rec/crs/fc-md-coordinateEpoch | :x: | No spatial feature collection is stored on the server | | ||
| | ||
|
||
## Permission | ||
|
||
| recommendation | applicable | description | | ||
| --- | --- | --- | | ||
| /per/crs/fc-crs-action | :x: | Np features or feature resources are available | |