CRUD

specdraftimplproposal

Create, replace, update and delete features.

Scope

Limitations

Only feature types from an SQL feature provider with dialect PGIS, sourced from a single table and with auto-incrementing primary keys are supported. See also issue #411.

Conformance Classes

The module is based on the specifications of the conformance classes "Create/Replace/Delete" and "Features" from the Draft OGC API - Features - Part 4: Create, Replace, Update and Delete. The implementation will change as the draft will evolve during the standardization process.

Operations

Resource	Path	Methods	Media Types	Description
Features, Feature	collections/{collectionId}/items, collections/{collectionId}/items/{featureId}	DELETE, PATCH, POST, PUT		Create, Replace, Update and Delete features.

Path Parameters

Name	Resources	Description
collectionId	Features, Feature	The identifier of the feature collection.

Query Parameters

Name	Resources	Description
schema	Feature	This option can be used to return features with a different schema. The only supported value is receivables, the response is the schema of the features that has to be met when creating or replacing a feature. Diese Option kann verwendet werden, um Features in einem anderen Schema zurückzugeben. Der einzige unterstützte Wert ist receivables. Die Antwort ist dann in dem Schema, das beim Erstellen oder Ersetzen eines Features verwendet werden muss.

Configuration

Options

Name	Default	Description	Type	Since
buildingBlock		Always CRUD or (deprecated) TRANSACTIONAL.	string	v2.0
extensionType		Deprecated See buildingBlock.	string	v2.0
enabled	false	Enable the building block?	boolean	v2.0
optimisticLockingLastModified	false	Option to enable support for conditional processing of PUT, PATCH, and DELETE requests, based on the time when the feature was last updated. Such requests must include an If-Unmodified-Since header, otherwise they will be rejected. A feature will only be changed, if the feature was not changed since the timestamp in the header (or if no last modification time is known for the feature). The setting is ignored, if optimisticLockingETag is enabled.	boolean	v3.5
optimisticLockingETag	false	Option to enable support for conditional processing of PUT, PATCH, and DELETE requests, based on a strong Entity Tag (ETag) of the feature. Such requests must include an If-Match header, otherwise they will be rejected. A feature will only be changed, if the feature matches the Etag(s) in the header.	boolean	v3.5

Examples

- buildingBlock: CRUD
  enabled: true