Looks like my city’s map (Long Beach, California) was synced a couple of days ago, and with that sync, suddenly several streets are showing up as incomplete that I’ve definitely completed. Here’s an example. Is it just a matter of waiting for everything to sync up again?
My profile link :Robb B. - CityStrides
The icon next to the date on the city page (just under its name & next to the street count and distance) will spin while the city is actively syncing. After that’s done spinning, there’s nothing else to wait for.
There’s a large queue right now, but I put all the nodes created in the last update through for reprocessing. It seems like it might be just that data.
I’m reviewing the city sync code to figure out how this can happen … I’m not spotting anything yet, though 
Update: It actually looks like there are 6 legit unfinished nodes:
Yeah, but I’ve walked all six of those nodes, several years ago. My LifeMap GPS track comes within 20 feet of each one of those six nodes.
The attached image is a screenshot of my LifeMap showing that I’ve hit those nodes
I dug into the data more, finding all the activities that completed the other nodes and then manually checking nearby nodes for those. I found one activity that would return those 6 nodes.
The issue is that an optimization I added to the processing that occurs after a city sync isn’t working as expected. There are some cases where matching activities are excluded from the query.
This also explains what’s going on in Vancouver progress now inaccurate … which is good and bad 
I’m pausing city syncs until I get this sorted out.
