Good perspectives, thanks @hhummel. European urban runners must have ankles of steel 
I’ll add that indoor=yes tag to my local hospital and await the next CS OSM update.
2 Likes
I do not like the idea of ignoring cobblestones either. After all, one does not need to literally run every street… Walking, or hiking, is acceptable too. 
2 Likes
Good find - the next release will include an update to that query which includes all the other indoor tags (updated CityStrides Street Query - Google Sheets as well)
3 Likes
3 posts were merged into an existing topic: Removing service roads from those included in citystriders
Would this be fair to assume that you mean to remove slipways from showing up in CS lists? If so yes, I agree, I’ve found several areas in NH/Maine that have boat launches showing up as necessary to run.
1 Like
If it was me, I’d keep it… I was expecting it to extend into the water, but it doesn’t.
Oh wait, that second one does look like it has a node in the water! 
Someone has recently added Christie Lane in St Leonards NSW: Christie Lane - CityStrides. This is a former street which no longer exists and it has been added with a tag of “razed”, where “razed” means completely obliterated. I think the overpass query should be updated to exclude streets so tagged.
Interestingly, I have visited both nodes, but still have not been given credit for completing the street, not sure if this is part of this issue or something different.
Trying to take good care of my local city “Københavns Kommune”, I’ve been running the query in the Google Sheet and it returns 2665 named streets, however the refresh done at the same time in CityStrides shows 2666 streets.`
I’ve tested the query with the Overpass “date:” and “diff:” predicates to make sure that it’s not just because i have a time glitch.
Is the query in the Google sheet up to date and aligned with the CityStrides source or might there be a discraprency?