Green Dene Green Dene - CityStrides
Combe Lane (the northernmost bit) Combe Lane - CityStrides
appear to the same road.
Before the latest CS import I had renamed the “incorrect” bit of Combe Lane to Green Dene but it seems CS is now picking up both.
I checked OSM and as far as I can see my edit to Green Dene is still the one in use.
@JamesChevalier, I’m seeing a similar issue to the one mentioned above.
Can you fix this? Also-Is there any way that supporters can self-fix this similar to the ‘sync’ feature you’ve recently implemented?
Interesting - the example in the parent post looks (now; not sure what it looked like in 2023) Green Dene & Combe Lane are two separate streets that appear as expected in CityStrides.
In your example, it looks like Network Drive should have been removed in a past city update.
Overall, a sync is the fix here … or at least should be … The code should see that Network Drive does not appear in the request for streets in Burlington, MA and it should remove it from CityStrides.
I just started a sync (previous was December 2nd), and it looks like it has removed the street. Let’s see if it comes back (the sync is not complete yet) 
Similar issue:
I renamed part of this street to its correct name in OSM:
However the overlapping nodes now represent bot streets in CS. The city has synced multiple times since.
Fixed, thanks!
I can only guess that the code responsible for removing nodes that no longer exist in OSM is flakey … I was able to manually remove those few extra nodes, though.
I’m in the middle of some stuff right now, but I should review that to see if I can figure out why those nodes weren’t removed by the city update code…