You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fix OSM→OSW conversion when OSM Way contains consecutive duplicate nodes
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
Copy file name to clipboardExpand all lines: CHANGELOG.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,8 @@
1
1
# Change log
2
2
3
+
### 0.3.4
4
+
- 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.
5
+
3
6
### 0.3.3
4
7
- Fix OSM→OSW export classification so canonical OSM tags are used for semantic recognition and `ext:*` tags are preserved as extensions instead of being treated as feature-defining tags.
5
8
- Fix closed ext-only ways such as `ext:demolished:building=yes` to emit polygon output without falling through to point geometry construction.
0 commit comments