ogcapi-features
ogcapi-features copied to clipboard
An open standard for querying geospatial information on the web.
The current draft requires that the PATCH payload is in JSON, but not on the basis that the JSON representation of the feature is GeoJSON. This is confusing. When a...
The [Prefer header for HTTP (RFC 7240)](https://www.rfc-editor.org/rfc/rfc7240.html) allows that a client can communicate a preference for handling minor issues in a request: > The "handling=strict" and "handling=lenient" preferences indicate, at...
It would be very convenient for consuming parties to get an idea of the meaning concepts/attributes in the APIs (Features/Processes etc.). I'd like to propose a generic extension on all...
OAI has released v3.2.0 and v3.1.2 of the OpenAPI Specification: https://github.com/OAI/OpenAPI-Specification/releases We need to decide whether to reference v3.1 or v3.2 in v1.1 of Features Part 1. If we stick...
Hi, have you considered implementing the [RFC9457 standard](https://www.rfc-editor.org/rfc/rfc9457.html) into the openapi schema for error responses? there is a [blog post](https://swagger.io/blog/problem-details-rfc9457-doing-api-errors-well/) talking about adopting this over on the swagger website. currenty...
In yaml, the property in isLikeOperands is called `items`, in json it is called `prefixItems` https://github.com/opengeospatial/ogcapi-features/blob/18c2e28c4199b4ce4caf7f5adcec658529cb6c6b/cql2/standard/schema/cql2.yml#L106 ```yaml isLikeOperands: type: array minItems: 2 maxItems: 2 items: oneOf: - oneOf: - $ref:...
hi there, table 11 in [the above mentioned section of the specs][1], gives `2` as the _expected number of items_ when processing the `ne_110m_populated_places_simple` data source. however, there looks like...
Hello, I would like to ask if bulk creation of features using the POST method is being/was considered. STAC Item Transactions has support for this for STAC Items. In the...
Closes #1010