I just checked in on progress from a walk, and I saw that I had finished (yay) four streets, but I knew that I had not. Looking at the map, the issue is that the street is showing up as “Mitchell Avenue” and “Mitchell Road” - I think this means there is an underlying issue with OpenStreetMap - which I am going to check. However, I am not sure how often this is happening in cities. It doesn’t really make much of a difference (for completing a given place) if all of the streets are duplicated, but it skews the totals and if it is only one or a few streets, it would be somewhat problematic for percent of city completed.
I found this issue in East Port Orchard and Port Orchard (walk on July 8) . Interestingly, the overlapping differently named roads have different lengths and nodes but cover the same area.
Screenshots with nodes for examples:
This is Mitchell Avenue Southeast in East Port Orchard.
It is decidedly an Open Street Map issue at play with these two streets. I’m not 100% sure how to correct, but I will attempt to fix this one road on Open Street Map. NOTE: I am also not sure how to identify these except for folks looking at their streets in detail (which I don’t do that often).
Hi Jess, I just checked for you and it’s indeed something funky going on with OSM.
If you search in Overpass Turbo for all ways with Mitchell you get the following:
My guess is that @JamesChevalier uses name and name_1 separately to create streets, which means multiple streets can be created from the same ways?
On the OSM side of things, I’ve noted that naming with name_. is deprecated but I’m not experienced enough to know whether we can just delete the name_1 tag here without issue. Can a more avid OSM mapper help out here?
I am pursuing this on the OSM forums - I already privately asked a person who has made a lot of edits in that area. I hope to get this one instance corrected, and I am considering how to identify other similar segments/nodes.
I deleted name_1 for those segments on OSM, and I asked for a review. I’m not sure when it will get read into City Strides to see if it corrects this issue.
NOTE - if this query is still the one in use, than it doesn’t look like name_1 is actually the issue.