-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
aixm:ElevatedPoint not handled by CreateGeometryFromGML #11582
Comments
I don't replicate that.
outputs
|
You must use "km" and not "[km]". The bracket in "[nmi_i]" are just for this unit. Cf https://ext.eurocontrol.int/aixm_confluence/display/ACG/Arc+by+Centre+Point#ArcbyCentrePoint-Unitsofmeasurement So all in all, I don't see any bug |
I am curious about one detail. I read that "(case sensitive) values shall be used for gml:radius in AIXM/GML data sets" However, in the test data I see also Is it true that within the same AIXM/GML file the kilometers must be km in one place, and KM in another? |
Thank you very much for the explanation and the example. It really works the way you showed. However, I was using it differently in Java through the Java bindings, and the conversion worked correctly only when the srsName was specified in the inner element. But your way is better, so I will use it. Thanks! I have a different question, can you tell me, why ElevatedPoint doesn't work but other like ElevatedCurve or ElavatedSurface work?
|
It looks like it is sufficient to modify the gml2ogrgeometry.cpp file and add ElevatedPoint to the condition:
This adjustment is sufficient for my needs.
In some cases, it would be helpful if the Z coordinate (elevation) were correctly parsed for ElevatedPoint (and other elevated geometries). However, this is a separate issue and falls outside the current scope. It is more of a suggestion for future functionality enhancements. |
What is the bug?
It should be solved by #4807 (I wrote my comment there but nobody noticed).
It works if the srsName is set directly on the CircleByCenterPoint element (returns a POLYGON). It also works if the srsName is defined on some parent GML elements, but not on all.
However, if the srsName is only defined on the root element (Surface), it doesn't work (returns a CURVEPOLYGON).
Is there any workaround? When processing large files, modifying the XML to insert the correct srsName for child elements is inconvenient.
PS: It is strange that when I replace nmi_i with m, km, or nm, it doesn't work (regardless of the presence of srsName) — it returns a CURVEPOLYGON. According to the comments at #4807 and #3118, it should work.
Steps to reproduce the issue
See #4807
Versions and provenance
GDAL 3.11.0 (build from master branch)
Additional context
No response
The text was updated successfully, but these errors were encountered: