I believe there may be an issue with the way completion is being calculated for some cities.
Several cities that were previously marked by CityStrides as 100% completed in Hard Mode, with a completion date already recorded, are now showing additional streets as incomplete.
Examples:
Badalona (Spain): 12 streets reported as missing.
Montgat (Spain): 5 streets reported as missing.
In both cases:
Node Hunter does not identify any missing nodes.
Show displays the streets, but no missing nodes appear.
My recorded runs are clearly visible on those streets (blue route line).
The affected streets are shown as 0-node streets.
These do not appear to be new streets or recent map updates.
This is not limited to Badalona and Montgat. I am seeing the same issue in multiple cities, including cities that were already completed in Hard Mode and cities that were only missing a handful of streets.
What makes this confusing is that the streets are clearly covered by my activities, yet they are still being counted as incomplete. Since no missing nodes can be identified through either Show or Node Hunter, this appears to be a data or completion-calculation issue rather than missing coverage.
Could you please investigate whether there is a known issue affecting city completion statistics?
It looks like the city sync back in November 2025 left a number of 0 node streets. There’s a node count under each street name in the list, and I’m seeing a lot of “0 nodes” entries.
If you click the ‘Show’ button for the streets, nothing will be displayed on the map … although a lot of times it’s much simpler/clearer to click the ‘Go’ button. That will take you to a new page that zooms the map to exactly focus on the full street. You’ll also see there’s nothing displayed on the map here.
In some cases, where there are multiple streets in a city that share the same name, using the ‘Go’ button will help clarify that because it will zoom the map to show each street.
The next city sync will clear all this up … Sydney is currently syncing, and is taking a long time to finish, though, so it might take some time for these to sync if you queue them up now.
One point I’m still unclear about is your comment “if you queue them up now”. Does this mean there is an action that I need to perform to queue these cities for a new sync?
If so, could you please explain how to do that? Or will the affected cities be re-synced automatically as part of the next city sync process?
I just want to make sure I’m not missing any action required on my side.
Cities around the world are automatically/constantly synced. Each minute, code checks to see if the system can handle more work & if so, it queues up a batch of cities.
It’s a first-in-first-out situation that only looks to cities that have someone running there (have completed at least one street in the city).
Supporters have the ability to push cities to the front of the queue. That’s available in the menu on each city page, up next to the city name. This gets your sync running faster, rather than waiting in line based on its last sync date.