OGC API - Features - implementation of Part 4 in QGIS server: Create, Replace, Update and Delete

[swiss-knight]

Feature description

Hi,

I have created a small QGIS server project to serve PostGIS data.

I can see the data very well in my web browser and I can get all the features.

But I'm wondering if CRUD operations can be "enable" in my QGIS server project?

Currently I can notice "only" those classes under the /conformance end point

QGIS Server
Conformance Classes
http://www.opengis.net/spec/ogcapi-features-1/1.0/conf/core
http://www.opengis.net/spec/ogcapi-features-1/1.0/conf/oas30
http://www.opengis.net/spec/ogcapi-features-1/1.0/conf/html
http://www.opengis.net/spec/ogcapi-features-1/1.0/conf/geojson

whereas, from the exact same QGIS server project, when using the exact same WFS/OAPIF configuration in the project properties, the CRUD operations are both enabled:

and available when using the WFS endpoint:

<Operations>
  <Operation>Query</Operation>
  <Operation>Insert</Operation>
  <Operation>Update</Operation>
  <Operation>Delete</Operation>
</Operations>

But I can only 'edit' (update, insert, delete) features using the WFS endpoint, not the OAPIF one.

Thanks.

Additional context

No response

[maltaesousa]

But I can only 'edit' (update, insert, delete) features using the WFS endpoint, not the OAPIF one.

Thanks.

Additional context

No response

Hi @swiss-knight , I've made a small project that allows to create a polygon with OAPIF:
https://gitlab.com/geogirafe/qgis-oapif-demo

It's with a geopackage but I've tried with PostGIS and it also works.

Also it looks like the /conformance endpoint is not really up to date with what QGIS Server can really do.

[elpaso]

OAPIF editing is supported even if not exposed in conformance. Moved to a bug.

The fact is that when it was implemented, the OAPIF was still a draft and some classes were missing or not yet finalized, now it is time for an update.