After each batch of city updates (all of my 20 cities around Stockholm update the same day)
I just check the city listing to see if any of my completed cities are not 100% anymore. E.g today one of them had gone down to 99.77% due to an extension for one street.
But then more by chance I noticed that one city, Solna kommun, was still listed as 100%, but street count said 352 of 353 streets. Going to the city details I find one incomplete street, correct, due to an extension of that street.
So why did the percentage not drop for Solna?
This is pretty stressful, given all my recent work was towards fixing exactly this issue.
Is it possible that this percentage value has been incorrect for a bit? I’m wondering if this is a new issue, or if it’s something that happened earlier & won’t be auto-corrected - more of that convo is in Percentages incorrect - #11 by JamesChevalier
Either way, I’d like to hear about cases where the city percentage is correct … a city update occurs … and the percentage ends up wrong. I want to make sure this is fully fixed.
I can definitely see that this missing street was introduced four days ago, in Changeset: 139505906 | OpenStreetMap
So before that, Solna was a correct 100%
I also noticed that your percentage did not decrease, even with the city update I pushed through. This might help me figure out what’s causing the issue - I suspect that only ‘touched’ accounts are being processed & it’s not picking up accounts as being touched for some reason.
Hmm, makes me think… this was Solna, where I have not run at all since last update. But for ”Södermalms stadsdelsområde” which had the same scenario, someone extended a street a bit, this showed up correctly as 99.73%. But here I had actually run a small part of that city since last update (not to catch nodes, as I was already at 100%, just passing through a corner)
Yeah, I’ve fixed a number of bugs in the last couple hours … Waiting on some background jobs to finish, so I can deploy the fixes.
I think the most glaring issue, in your case, is that (this is a little complicated) the old version was too lax on updating percentages around new streets:
new streets were created
these did not immediately affect percentages, with the logic that no node data existed yet
new nodes were created/processed
any created completed streets resulted in percentages being updated
anyone how hadn’t completed the new streets would now have incorrect percentages
It’ll be a bit more ‘jittery’ if you’re watching your stats intensely while a city is being updated, but the new version (being released shortly) will forcefully update people’s stats after a new street is created … and then re-adjust stats for whoever completed the new streets already.
RE: notifications, the system doesn’t re-notify for milestones - so if you were at and a new street was created, dropping your %, and then the new nodes are processed which sees you’ve completed them, bringing you back to , you will not be notified again for the
My profile link : Hans Westerback - CityStrides
Is it possible that this percentage value has been incorrect for a bit? I’m wondering if this is a new issue, or if it’s something that happened earlier & won’t be auto-corrected - more of that convo is in 
and a new street was created, dropping your %, and then the new nodes are processed which sees you’ve completed them, bringing you back to 
at least that’s what I’m seeing