-
-
Notifications
You must be signed in to change notification settings - Fork 99
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use targed gml namespace if boundedBy/geometry is in gml namespace #1550
Conversation
Another test should be done checking whether the generated GML 3.1 (from GML 3.2 Blob store) is schema valid. |
The fix seems to be reasonable to fix the output to be valid XML again. Currently, I can not estimate what output will appear for GML3.2 blob data after the fix is applied. If the endpoint only shows GML3.2, or can be changed to, as supported output format in the capabilities, another approach may be to force GML3.2 output in the case of BLOB storage. |
The description of this PR shall be extended with the information how it behaves with the fix (paste the GML output here) for the different GML versions. |
The PR ensures that the namespace for GML that matches the WFS GetFeature request is set in the response. Delimitation:
|
Open tasks:
|
…ions in blob mode
Fixes #1548
Please also see this issue for description of the bug.
The problem is that in Blob mode the namespace of the GML version of the original features is used (e.g. GML 3.2). This namespace is also used partly to write the response body although another GML version is expected (e.g. GML 3.1) leading to the documented exception.
This PR ensures that the targed GML namespace is used to write boundedBy and first geometry element if the geometry is in GML namespace preventing the mixing of GML versions.