Street with two names after update

Two months ago I updated a street name in Solna kommun, https://citystrides.com/users/24151/cities/113432.
This street Tvärvägen https://citystrides.com/streets/9630906 was found in two different places, the southern one is correct, but the nortern one was not, it was really a part of Polisvägen https://citystrides.com/streets/9630786 , so I updated this in OSM, but as you can see now the same nodes are included in both these streets

Ping @JamesChevalier

Let’s see if an update fixes things up…

:thinking: it did not. I’ll have to take a closer look when I have some free time.

1 Like

@JamesChevalier I found another similar case, but this was not after any updates I did, just happened to stumble upon it: Stockholm https://citystrides.com/users/24151/cities/113349
Look at Gebersvägen https://citystrides.com/streets/17107420
All these nodes are also (wrongly) attached to the neighboring Orhemsvägen https://citystrides.com/streets/9644385
cs3

1 Like

One more example, @JamesChevalier: Nacka kommun

One street was previously included in a closeby street, Augustendalsvägen https://citystrides.com/streets/9846656
I corrected this to the real name in OSM, Ellenviksvägen
https://citystrides.com/streets/15639362
And now all nodes in this street belong to both street names, as in this picture
cs4

Another example in Wiltshire (UK) following an OSM edit I made to correct the road name.

These street links are very helpful - thanks for sharing them. I probably can’t do anything without these links.

So I think I’m seeing:

Similarly:

I’ll have to step through the city update code to see why it’s picking up nodes like that…

1 Like

Just wanted to echo the previous posts since I’m seeing the same issue in my city. I’ve been updating street names in OSM as I’ve found mistakes and sometimes they aren’t pulled into CityStrides correctly.

Here’s a few examples. For the most part I’ve only been updating the way name in OSM for these and not really messing with the nodes or much else:

This one wasn’t caused by me and I can’t quite figure it out. East 116th Street includes nodes from Hazel Dell Parkway, but only for one specific way. Looking at the way history on OSM, version 12 inexplicably changed the name to East 116th Street, but it has since been fixed. That version also says the way has 41 nodes, which matches up with what got mistakenly pulled in to CityStrides.

I’m assuming the update code is pulling in older versions of ways or something. I can’t be sure exactly obviously so hopefully these examples can help in addition to the ones already posted.

Providing additional examples to help with troubleshooting. In this case the name of the way was updated in 2019 but is still showing nodes under two streets. The section of 82nd Ave N is being included with 81st Ave N.

History of way:
image

82nd Ave N: https://citystrides.com/streets/2526456
81st Ave N: https://citystrides.com/streets/2526391

@zbrown4 I only looked at 82nd ave n, but comparing to Google maps, it seems like 82nd ave n is all over the place.

but then I looked at ArcGIS Web Application and got a different picture (map).

Unfortunately I did not find navigation, or searching, on that map very intuitive, and gave up.

But more maps at: City maps | Maple Grove, MN

maybe another is more useful? :crossed_fingers:

Yeah my city has a ton of disconnected streets across the same latitude or longitude with the same name. I think it still holds that the nodes on 82nd Ave should not be included in 81st Ave though. I’ll keep my eyes out for any clearer examples in my city though.

1 Like