Relatedly, this one is marked foot=customers in OSM and was updated in CS; it appears in the Streets list for the nested city but not the parent city - shouldn’t appear in either
You have to be careful when comparing the displayed node count and the number of nodes you’re able to count on the map. Since I’m pulling in individual Way records from OSM, and combining them based on their name in order to build the concept of a “Street”, it’s normal to have multiple nodes at intersections.
I checked the data for both your links, and all the completed node records are there, so it didn’t create the completed street for some reason. I’ve started the job to fully recheck your account.
I’ve noticed some city update failures recently that I think are playing a role here. I’m going to take a look through that code to see what’s up…
Let’s see how the next update of that city goes. Maybe the update for that parent city got a different Overpass server.
Yeah I’m not saying the nodes completed or not have anything to do with the street being done, clearly they don’t in these cases - just in case it would help diagnose what’s going on with the errors. Appreciate you looking into it!
More context if it helps - I think the errors occurred following me deleting some old activities that had GPS errors and reuploading corrected versions. The activities were the ones that originally completed at least one of those streets, Luis de Freitas Branco - but it was weird because I had re-run it later and didn’t delete that activity.
I may be in the same case, in Paris (France) : after the last city updates (since 1 or 2 month), I’ve noticed that my completion score was decreasing step by step. But after a quick look, that seems (almost) not related to streets’ updates nor creation : some nodes are reappearing as “missing” (red) in some streets that are clearly already completed. You can see on the screenshots attached that there are already previous tracks through these nodes.
Surprisingly : these streets can appear completed in the “sub-division” nested in Paris (ex : “Paris 6e Arrondissement” Paris 6e Arrondissement, Île-de-France - CityStrides) but uncompleted in the “global” city of Paris (Paris, Île-de-France - CityStrides).
Do you have any idea about this issue @JamesChevalier ?
spot-checking Route des Petits Ponts & Rue Scandicci from your first screenshot - all those nodes are marked as complete now.
Are things looking correct for you now?
In fact, in my first screenshot, streets ‘Rue Scandicci’ & ‘Route des Petits Ponts’ we indeed completed : the missing node is in ‘Avenue du général Leclerc’. You will see it better in the 2 following screenshots.
You can see that this ‘Avenue du général Leclerc’ appears completed in ‘Paris 19e arrondissement’ (which is nested in Paris) but not completed in ‘Paris’.
The fact that nobody was marked as having completed it suggests that this is tied to city update issues (I’ve since reprocessed it, which marked some people as having completed it). Avenue du Général Leclerc - CityStrides
For your own account - is it possible that you haven’t completed both sections of the street? There’s another section of it in the 14th: Avenue du Général Leclerc - CityStrides
(If you share more data, can you do so in the form of links? Those are much easier for me to work with, since it cuts out a lot of searching)
Thanks for your inspection, James !
In fact, Avenue du Général Leclerc - CityStrides was probably a bad example, due to this dual section. In addition my issue is not such that the street is not completed : it is that some nodes are re-appearing as not completed, where they were completed before. But something has actually changed after your reprocessing : the red nodes in that street have turned ‘completed’ (purple), now ! So it’s maybe juste a processing issue, at city scale ?