Fix OSM→OSW conversion when OSM Way contains consecutive duplicate nodes#49
Merged
Conversation
https://dev.azure.com/TDEI-UW/TDEI/_workitems/edit/3286 **PR Title** Fix OSM→OSW conversion when OSM Way contains consecutive duplicate nodes **PR Summary** - Fix OSM→OSW conversion when OSM Way contains consecutive duplicate nodes (bug 3286). Instead of generating an invalid 0 length geometry, the segment is ignored. - Tested on file attached to dev board bug: osm.b8106236-b919-4e50-b956-99399635c0bb.xml - Added a new unit test
anuj-vindago
approved these changes
Apr 16, 2026
sujata-m
approved these changes
Apr 16, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
https://dev.azure.com/TDEI-UW/TDEI/_workitems/edit/3286
PR Title
Fix OSM→OSW conversion when OSM Way contains consecutive duplicate nodes
PR Summary
Fix OSM→OSW conversion when OSM Way contains consecutive duplicate nodes (bug 3286). Instead of generating an invalid 0 length geometry, the segment is ignored.
Tested on file attached to dev board bug: osm.b8106236-b919-4e50-b956-99399635c0bb.xml
Added a new unit test