-
Notifications
You must be signed in to change notification settings - Fork 44
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
Remove whitespace from pos when importing gml geometries #808
Comments
florianesser
added a commit
to florianesser/hale
that referenced
this issue
Apr 30, 2020
Make sure that leading and trailing whitespace is removed before splitting the value of an element bound to `java.util.List` at whitespace. The old behaviour lead to three list entries (an empty one followed by the one for each of the actual values) being created for the `pos` element value from the following snippet: ``` <gml:Point srsName="EPSG:25832" gml:id="GML-f"> <gml:pos> 540465.8278 5802259.4572 </gml:pos> </gml:Point> ``` However, the snippet above should have the same semantics as ``` <gml:Point srsName="EPSG:25832" gml:id="GML-f"> <gml:pos>540465.8278 5802259.4572</gml:pos> </gml:Point> ``` Therefore, leading and trailing whitespace is now removed before the split. halestudio#808
florianesser
added a commit
that referenced
this issue
Apr 30, 2020
Make sure that leading and trailing whitespace is removed before splitting the value of an element bound to `java.util.List` at whitespace. The old behaviour lead to three list entries (an empty one followed by the one for each of the actual values) being created for the `pos` element value from the following snippet: ``` <gml:Point srsName="EPSG:25832" gml:id="GML-f"> <gml:pos> 540465.8278 5802259.4572 </gml:pos> </gml:Point> ``` However, the snippet above should have the same semantics as ``` <gml:Point srsName="EPSG:25832" gml:id="GML-f"> <gml:pos>540465.8278 5802259.4572</gml:pos> </gml:Point> ``` Therefore, leading and trailing whitespace is now removed before the split. #808
LGTM, tested with build https://builds.wetransform.to/job/hale/job/hale~publish(master)/504/ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If source data contains geometries with pos elements structured in the following way (coordinates are provided in their own line)
hale studio reads the geometry as a 3D geometry with the first value being null:
When changing the structure in a way that the pos value is in the same line as its tags
it is correctly recognised:
There is test data available on that (test data for XPlanung 5.1 vollvektoriell FNP) in the relevant GitHub repository.
The text was updated successfully, but these errors were encountered: