ogcapi-features
ogcapi-features copied to clipboard
An open standard for querying geospatial information on the web.
I looked through the spec and could not find clear guidance on this, so I'm filing this ticket. The semantics of a PUT or PATCH allow the entity to be...
See, for example, https://sookocheff.com/post/api/optimistic-locking-in-a-rest-api/. This should be quite useful for some scenarios. Of course, it should be a separate conformance class.
To address comments by @cportele in issue 515.
Meeting 2022-05-23: This topic is not specific to geospatial, so the current thinking is that we should not add much in the OGC API standards, but we should provide links...
Meeting 2021-11-08: * It is two years (part 1) or one year (part 2) since the publication of v1.0.0 and both of the standards have seen some changes to clarify...
The publication date of 18-058r1 is wrong . 
Most recently, I've been working extensively with the OGC API Features and I noticed that there is no way for a web client to dynamically determine the ID column of...
[Recommendation 2](https://docs.ogc.org/DRAFTS/20-002.html#feature-representations) of Part 4 specifies that the schema that should be retrieved from the `/collections/{collectionId}/schema` endpoint is the schema of a **feature**. The example and requirements that follow [Recommendation...
Hi, in my organisation there is a need to get unique values for a specific property from an OGC API Features collection. Is this already supported in OGC API Features,...
It might be a good idea to, in each part of a multi-part standard, include an "Other parts" section that points to the other parts of the standard. For example,...