I recently noticed that two cities (linked below) have several streets which list 0 nodes for me. Clicking “show” on those streets doesn’t show me anything, clicking “go” links me to the page of the street (as expected), which shows several other users did manage to complete these streets. Since the streets don’t have any nodes, I cannot complete them.
I am assuming the missing nodes are a bug, or an issue caused by some update, but I am not sure what to make of the “empty” streets. Is this an issue on my end? I tried to look on the forum, but didn’t find any issue that seemed to match mine.
Interesting! I’d guess it was a bug in a past city sync - nothing you’re doing wrong. I just queued the cities up for a sync, but it’ll take a while for it to make its way through the queue.
I think I have a similar problem. In the last 2 weeks I have lost 3 cities from 100% complete. I have searched my uncompleted cities and I can only find 2 that have been recently relegated to <100%. Both of these cities now have uncompleted streets with 0 nodes. Both these cities have not been updated since November 2025, so I am unsure how they could have changed.
Both cities have synced by now. Brussels city is fine after the sync, but Elsene is still showing two streets of 0km with 1 node (each). I have passed by both of these nodes, but citystrides still marks them as incomplete. Both streets also seem to be at the border of the city, which may be part of the issue?
As a sidenote, three other people who completed this city are now at the exact same completion percentage as I am, which makes me think this issue also applies to them.
Hi, I have the same issue in New Westminster, British Columbia.
There are no nodes on Dyke Road. I wonder if the problem is that Dyke Road (Richmond) turns into South Dyke Road (New Westminster) and it has something to do with that transition?
For New Westminster, let’s see if the queued sync sorts things out. When the text “queued for sync” on that city’s page is updated to a date, let me know if the issue with Dyke Road still persists. This might take some days.
That’s the fix, here. There was a time where single-node streets were rejected, apparently in a way that left lingering zero-node street records hanging around … another sync will fix these up.
It seems the case where no-nodes streets were introduced is relatively recent. Perhaps sometime in the past year, judging by the users that were able to complete some of those streets before they became zero-node.
It also seems this is related to streets in the edge of the city/area.
For instance, Carnide, nested in Lisboa, has 5 zero-node streets, but they do not exist as zero-node in superset of Lisboa. I didn’t confirm, but my guess is that other nested cities likely also have zero-node streets. I have also noted that the superset city (Lisboa) has a more recent update date (March 2026) than the nested city (Carnide, November 2025).
Yeah, there was a minute - around the time I switched from Overpass to a local dataset - that I couldn’t figure out how to keep around single-node streets … super common when Way records aren’t properly snapped to city borders … I’ve since figured that out, so the next sync will fix those up.
There are ~6k cities with streets like this.
I could bulk delete the zero-node streets, which would be recreated in the next sync. That’s more manual effort, and I’m trying to stay focused on the serious performance issues around syncing right now.
… another sync will fix these up.