Hi Scott,

This is a problem with CityStrides and how it interprets OSM data, as well as how OSM default access is set. 

All navigable streets and paths, including sidewalks and footpaths, are defined as "highways" in OSM. They are further specified with a tag, e.g. 14th Street is tagged "highway=secondary", as a "secondary road", in that it is an urban arterial road with higher posted speed limit than the nearby residential roads. However, by default, it is assumed pedestrians have legal access to secondary roads—and actually, to all roads except "motorways" (freeways à la Deerfoot Trail). This is a worldwide OSM default with no consensus on how to modify it across jurisdictions (see https://wiki.openstreetmap.org/wiki/OSM_tags_for_routing/Access_restrictions) for more discussion).

CityStrides assumes that any road (other than a "motorway") allows legal access to pedestrians, and doesn't seem to exclude roads that are further tagged with "expressway=yes", "dual_carriageway=yes" and the like (Anderson Road north of this note of yours is tagged as such).

That said in Calgary all roads are *de jure* not accessible to pedestrians whatsoever, so if we're going off legal accessibility it would make the CityStrides app entirely redundant and useless.

At this point the only workable workaround is to tag road segments with "foot=no" tags. I've done this for the segments in and around the intersection of Anderson Rd and 14th St, and otherwise you can do this yourself wherever you encounter roads with no de facto pedestrian access. After CityStrides updates with the most recent OSM data the affected road segments' nodes should disappear from your app.