Apologies, I had a few weeks going overseas for holidays (and did a lot of GPS tracking on the way!)
I like your suggestion of moving the nodes slightly! I have written a quick script which will take overlapping nodes and shift them all radially around their current location by less than 1 meter. That way they are close enough for navigation but far apart for humans to understand, and no data is lost. In the spirit of this import, it only operates on selected nodes, which forces the mapper to run the validate and screen the overlapping nodes before actually shifting them using the script. Script is below. https://gitlab.com/dionmoult/osm-nsw-address-import/blob/master/src/displace_overlapping_nodes.js Updated OSM file with the shifted nodes are here: https://gitlab.com/dionmoult/osm-nsw-address-import/blob/master/review/EPPING-1.osm If there are no more issues I will upload in 2 weeks. Dion Moult ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On July 8, 2018 5:50 PM, Martin Koppenhoefer <[email protected]> wrote: > > > sent from a phone > > > On 8. Jul 2018, at 08:29, Dion Moult [email protected] wrote: > > > > 2. don't leave the nodes in the same position. This action has the effect > > of intentionally creating messy data for humans. (it would be good for > > navigator software, though! But OSM is humans first!) > > if you move these nodes slightly (e.g. < 1m) it won’t make a difference for > navigation software, but will make the situation easier to understand for > mappers > > Cheers, > Martin _______________________________________________ Imports mailing list [email protected] https://lists.openstreetmap.org/listinfo/imports
