[OAPIF] Server defined fields are not fetched when creating a new feature #57486
Assignees
Labels
Bug
Either a bug report, or a bug fix. Let's hope for the latter!
Comments
3nids
added
the
Bug
3nids
referenced
this issue
May 19, 2024
…es Part 4)
- Issues OPTIONS on /collections/{coll_id} and collections/{coll_id}/{feature_id}
endpoints to check server capabilities
- Add support for addFeature() through POST /collections/{coll_id} endpoint
- Add support for changeGeometryValues()/changeAttributeValues() through
PUT /collections/{coll_id}/{feature_id} endpoint.
Or through PATCH /collections/{coll_id}/{feature_id} with just the
updated subset, if available
- Add support for deleteFeatures() through
DELETE /collections/{coll_id}/{feature_id} endpoint.
- For POST/PUT/PATCH, takes into account Part 2 (CRS support) when implemented
by the server.
rouault
added a commit
to rouault/QGIS
that referenced
this issue
May 23, 2024
…fill the QGIS 'id' field, when it exists Fixes qgis#57486
rouault
added a commit
to rouault/QGIS
that referenced
this issue
May 23, 2024
…refreshed version of the feature Fixes qgis#57486
nyalldawson
pushed a commit
that referenced
this issue
May 23, 2024
…fill the QGIS 'id' field, when it exists Fixes #57486
nyalldawson
pushed a commit
that referenced
this issue
May 23, 2024
…refreshed version of the feature Fixes #57486
qgis-bot
pushed a commit
that referenced
this issue
May 23, 2024
…fill the QGIS 'id' field, when it exists Fixes #57486
qgis-bot
pushed a commit
that referenced
this issue
May 23, 2024
…refreshed version of the feature Fixes #57486
nyalldawson
pushed a commit
that referenced
this issue
May 24, 2024
…fill the QGIS 'id' field, when it exists Fixes #57486
nyalldawson
pushed a commit
that referenced
this issue
May 24, 2024
…refreshed version of the feature Fixes #57486
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What is the bug or the crash?
If you create a feature on an OAPIF layer which has some server defined default values, these values stay as defined on feature creation on QGIS side.
This is valid both for the ìd` primary key and any other field/property.
see discussion 2924f3e#r142164114
The text was updated successfully, but these errors were encountered: