3

Follow up to How can I programmatically identify missing sidewalks in OpenStreetMap data?. I've noticed that a number of streets and roads in a region I'm interested in are missing pedestrian access when they have sidewalks, and this is affecting pedestrian Mapbox directions.

How can I find ways in Overpass Turbo that are missing this access parameter?

raphael
  • 3,407
  • 23
  • 61

1 Answers1

5

See the Overpass API language guide, specifically the section about negation.

Not sure what tags Mapbox directions is looking for. Here is an example query for retrieving various roads missing a sidewalk=* key:

[out:json][timeout:25];
way["highway"~"primary|secondary|tertiary|residential|unclassified|service"]["sidewalk"!~"."]({{bbox}});
out body;
>;
out skel qt;

You can view the result on overpass turbo.

scai
  • 6,120
  • 16
  • 28
  • Thanks for the example. I changed it to find missing foot access. There are still a number of streets in my area that are failing. http://overpass-turbo.eu/s/eEV – raphael Feb 27 '16 at 16:31
  • It shouldn't be necessary to add a foot tag to every way. Usually foot access should be the default for most highway classes except for motorway. See the implicit default values. It might be possible that Mapbox directions uses slightly different defaults, though. Still, adding foot to every way seems wrong. – scai Feb 27 '16 at 17:37
  • Hmm... I didn't know about the defaults. Thanks for sharing. It seems there is a divergence, since the road that wasn't working with Mapbox directions was tagged highway=trunk which should have default ped access=yes – raphael Feb 28 '16 at 03:37
  • Personally I can't understand why trunk has default foot access. Every trunk road (in Germany) that I know doesn't have foot access. But this might be different from country to country. Maybe Mapbox decided to change this default which seems reasonable to me. – scai Feb 28 '16 at 08:41