OSM Basics

This is a resource that summarizes a few techniques for fixing common OpenStreetMap (OSM) errors that found their way into CityStrides. It is meant as a shortcut for those unwilling to navigate the OSM learning curve for the sake of a few edits, a more detailed write-up/guide can be found here. Please keep in mind that there is no process to reflect any such changes in CityStrides yet (as of July 2020), but it is planned and edits will be reflected once it is implemented.

Signing up:

Head over to https://www.openstreetmap.org/ and create an account for yourself. To start editing navigate to the area of interest and hit “Edit” in the left top. Once all the desired edits (see below) have been made they can be uploaded by hitting “Save” in the right top corner. Keep in mind that OSM is used as a resource for many things besides CityStrides and that changes should be made in a way that reflects reality .

Private streets:

If the entire street is private, select it by clicking on it and change the “access” tags in the left panel to “private”. If only a part of a street is private, it might be necessary to split it so that the private part can be tagged appropriately. This can be done by right-clicking the node where it becomes private and selecting “Split”. The access tags on the private part can now be set as above. If there is a gate blocking access to the private part, this can be added by selecting the node and editing the feature type by selecting from the feature drop-down. Again, appropriate tags should be set for the gate. If the whole street is private, but this street is already spit into several parts, remember to set all parts of the road to ‘private’ if applicable.

Non-pedestrian roads:

If you find a street (or section) on CityStrides that is dangerous/not pedestrian accessible in real life, change the “access” tags for pedestrian/foot to “no”. Keep in mind that longer streets are often modelled as a series of shorter segments, so you may need to repeat this until the entire segment you want to edit is covered.

Did it work?

Once the edits are done and saved it’s possible to see the effect they will (eventually) have on CityStrides by finding the edited area here (https://overpass-turbo.eu/s/UZ7) and hitting run. Only streets in blue will be in CityStrides. OSM might take a few minutes to incorporate your changes to the map.


This explains why some of the obvious hiking/walking routes over here, had no nodes.
Paths missing their names on OSM is one reason, adding the tag Foot:yes to roads is another … now I know what to do once I finish running the whole city :sweat_smile:

Thanks for this, there has been a few streets that would require trespassing to be completed near me. I managed to mark the private parts of these as private now. And if overpass-link in your post is correct a lot of the changes I’ve wanted done have already been fixed. Can’t wait for all changes to be updated into CityStrides, hopefully a solution can be found soon.