Use multisurface and multicurve for GML 3.2 and WFS 2.0 #14471
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ahocevar
force-pushed
the
gml32-multisurface-multicurve
branch
from
88c4aaa
to
460086c
Compare
|
📦 Preview the website for this branch here: https://deploy-preview-14471--ol-site.netlify.app/. |
tschaub
approved these changes
Feb 1, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
WFS GetFeature requests with
Intersectsfilter currently fail whenversion: '2.0.0'is used. This is because WFS 2.0 uses GML 3.2 as format, whereMultiPolygonandMultiLineStringare deprecated in favor ofMultiSurfaceandMultiCurve.GML 3.2 already uses
MultiSurfaceandMultiCurveby default when an instance ofol/format/GML32is created. With this pull request, the same defaults are applied when the prototype is used by other formats, e.g. WFS.