Rule of thumb when thinking routing: Don’t count on motor vehicle routing on highway=track, highway=road and highway=service, implementation of these tags vary greatly in routing software
For pedestrian routing, don’t count on restrictions for highway=primary, highway=trunk, highway=motorway and highway=*_link to be set correctly, if routing/non-routing is vital in surrounding of such roads, tag access on them so routing software can override Priority between streets, sidewalks, and walkways are something that needs to be sorted out in each routing application, if you encounter problems, best is to open a ticket or issue with the routing provider. Aun Johnsen > On Nov 3, 2016, at 10:00, talk-requ...@openstreetmap.org wrote: > > Another issue with routing software might be the kind of OSM object on > which a highway tag is put. Highway=pedestrian areas (and other highway > areas, but pedestrian are the most common) could be tagged on > multipolygons, but last time I checked this there were no routers > evaluating them (not even for routing along the edges, hence leaving gaps > for pedestrian routing). > > Cheers, > Martin _______________________________________________ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
