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
While trying to translate addresses for Spokane county I found that 2043 nodes were being dropped before making it to the xml. They are all nodes that are very close to one another. It's been confirmed that after moving the points away from each other ogr2osm will output the points normally.
Confirmed with custom translation and default translation.
This is designed behavior in mergePoints() function. commenting out mergePoints() in main will output all points but also removes roundingDigits funcationality.
A --no-merge option would be nice for this use case. Maybe as an option with help=suppress_help option since people shouldn't unknowingly import points that will be nearly impossible to work with in GUIs.
While trying to translate addresses for Spokane county I found that 2043 nodes were being dropped before making it to the xml. They are all nodes that are very close to one another. It's been confirmed that after moving the points away from each other ogr2osm will output the points normally.
Confirmed with custom translation and default translation.
Source:
spokane_co_addresses.geojson.gz
XML output:
spokane_co_addresses_fake_version.osm.gz
The text was updated successfully, but these errors were encountered: