I did not report a new issue. I rather tried to give you some non-technical user feedback about delayed updates at the street level while hoping that the issue is fixed now.
And I was not clear enough if you didn’t understand that the incomplete streets appeared in places I had run extensively. I am indeed talking of cities where I was at 100%.
The streets are incomplete but they only appeared in my list of incomplete streets on May 7th and that even though these streets were not updated. It always happen that the maps are improved even if the streets are not new IRL, but it’s frustrating for sure, and when it’s because of a CS-issue, it becomes one of the rare moments when I am not in love with CS anymore. In at least one case, I could have run several streets the last time I was in the area if CS had marked the streets as incomplete at the time.
Example:
This street last appeared in the city updates on April 1st, while I was in this remote area on April 6th to get back to 100% for the city. Unfortunately, this street was (wrongly) in my list of completed streets until May 7th although it must have been incomplete before (since the street was neither updated in OSM nor updated in CS in the last month).
I hope the OSM edits now appear reliably on CS with the next update. My account should be up-to-date.At least I hope so. I am not sure about other accounts.
In general, the increased update frequency is a great help because we know faster when something change in OSM.
OK, I think I’m following now. What I’m hoping is that:
City updates prior to ~May 7th left some streets incorrectly marked as complete
City updates on/after ~May 7th correctly mark those streets as incomplete
I’m going to fully re-validated all your completed streets. I think this should reduce your total number of completed streets by a little bit (streets in any of the cities that haven’t been updated since ~May 7th). After this validation is complete, I expect that further city updates will not incorrectly leave streets marked as complete.
Today, I again discovered incomplete streets in 2 different cities that do not appear in my lists of incomplete streets OR that did not lead to a corresponding drop in the city percentage (which is how I usually spot them).
Thanks for sharing the details … It seems like there are still three outstanding issues around city updates (along with my theory on why)
overall city percentage isn’t always updated - a city might be listed as 100% but there is an incomplete street
likely related to the next two issues, the street percentages are being updated, but these updates are not affecting the city percentages
complete streets marked as incomplete
maybe data is being updated … the streets are un-marked as complete … and the reprocessing isn’t re-marking it as complete
incomplete streets marked as complete
maybe nodes are being deleted … the streets are being marked as complete because of that … then the nodes are being recreated & the street is not being unmarked as complete
The nature of OSM updates (where an “update” might actually be a delete/create) and the multi-threaded processing that I have currently set up, are both working together to cause some odd data display issues.
I’ve jotted down a pile of notes around this issue, and I intend to take a closer look at the beginning of July.
The issue came back one month ago.
Good news: it’s a very specific case of a tiny town where I was the first strider, so that the CS data hadn’t been updated since 2019. Moreover, I completed the 10 streets of the “city” in a single run.
When I stored the activity, the CS update was immediately triggered and one street was updated, but remained complete for me although I now have plenty of red nodes and a percentage under 90% for this street (percentage doesn’t really matter though since I use hard mode).
I also still have 100% for the city, which is not correct as of today.
I will go back there soon and complete the street, but if you check the links before I do, you’ll be able to see the issue:
I guess you have to re-order the jobs when it’s a new city that has not been updated for a while, because otherwise, the next updates don’t fix the issue (in this case, waiting for one week would have been enough, but it doesn’t work like that).
I’ve just done a pretty large overhaul of how the city update process works. Let me know if you have any cities with incorrect stats & I’ll check if my update fixes this … similarly, please let me know if you notice the issue again.
It’s interesting because another street in the same city (probably this one: Mühlenberg - CityStrides) became incomplete on the same day while this one didn’t.
Thanks for gathering this info - I understand it can be difficult to pull together at this scale.
I think Bernau looks good now (just ran an update).
This is likely because it only reprocesses changed data … Mühlenberg likely changed in some way in that update while Am Magna Park didn’t.
Since I’m very hopeful that future city updates will behave as expected, I’m going to slowly queue up a validation job for all completed streets. That should get things back to a good state, and then I can monitor new issues from there.
