Experimented with a style highlighting footways tagged with footway=sidewalk
and footway=crossing
Play with the Pedestrian QA style
The mapping of sidewalks as separate ways seems to be more of an issue in US than in other places. This style of mapping increases visual noise on the map especially if the sidewalk or crossing tags are missing.
Discussion
Comment from augxcgrwxo on 11 December 2015 at 13:26
Is it an issue? I thought that now it is the recommended way of mapping sidewalks.
Comment from SomeoneElse on 11 December 2015 at 15:11
@ksetdekov It depends on location, really. In many places in the world for pedestrian routing it makes no sense to map separate sidewalks and crossings because there are no explicit crossings - you’re allowed to cross anywhere.
Where it gets complicated is where there are multiple sets of users, for example (1) pedestrians, who can and do cross anywhere (for whom sidewalk=none/left/right/both on the road is the best tagging) and (2) wheelchair and mobility scooter users who have to navigate by dropped kerbs, which may be at junctions or may not, and don’t necessarily match any marked crossings that might exist. I’ve not seen a good solution that addresses both groups of users, but I do know (because I regularly use OSM data for pedestrian routing) that mapping sidewalks as separate ways, if done badly, can break pedestrian routing for everyone.
Comment from Omnific on 11 December 2015 at 20:45
I recommend tagging sidewalks as separate ways only if there is space between the sidewalk and the road. If the sidewalk is directly next to the road, then it should be tagged using the sidewalk tags on the road. This keeps visual noise down, but also ensures that the ways are more or less spatially accurate.