4 ms·
> OSM data can be quite terrible at times in minute ways that made it look decent but made routing nearly impossible Please do elaborate! I often spend a lot o
by lucb1e 12y ago
> OSM data can be quite terrible at times in minute ways that made it look decent but made routing nearly impossible
Please do elaborate! I often spend a lot of time just figuring out what the best practices are to map. I'd like to make the map data perfect for all uses but I don't know what kind of tags are needed when I'm mapping.
- nicky0 12y agoOne example I often run into is where dissimilar ways meet. For example a footpath that crosses a road. The path and the road should share a node. If not, then it will look fine on the rendered map but it won't be routable. (Of course, if the path is bridged over the road with no access between them then they shouldn't share a node.)
- Doctor_Fegg 12y agoGood example. Another common example is one-way streets. If you have several sections of a street with conflicting one-way markings like this: ----> . <---- . ----> then the street becomes unroutable (assuming no intersections at the .s). I found this was a fairly common issue on the entry/exit flares at roundabouts.
- ZeroGravitas 12y agoThere's various automated tools to do this: http://wiki.openstreetmap.org/wiki/Quality_assurance#Error_detection_tools http://wiki.openstreetmap.org/wiki/Quality_assurance#Error_d...