Node hunter suddenly started showing complete nodes as incomplete

CityStrides Profile Link

Message

Hi,

Before launching into the topic, I just want to say:

  • sorry if this has been answered before, I looked the forums but couldn’t find this exact issue
  • I love this site, I stumbled on it by chance and within 30 mins I was a paid up supporter. Within a few days I was already updating open street map.

All of a sudden, node hunter is showing nodes as incomplete which were previously complete, eg see on the map below. Note:

  • Actual road and city progress is still exactly correct. Eg all the cities I completed previously (including one in the picture below) are still correctly showing 100%
  • It occurs across multiple suburbs I’ve been in (all in Sydney), not just a single suburb

I can’t see any obvious pattern as to why just certain nodes are showing up. Really appreciate any help to resolve this. Thanks very much.

N.B. if the solution is to completely resync my account from Strava, I already had deleted a bunch of old jagged activities on CityStrides. I guess those deleted activities would get re-sync’d if I have to do this. Is there any place on City Strides where I can see a list of my deleted activities? Just so I can refer to that if I have to delete them again. It would be even nicer if they could even stay deleted upon a re-sync but that’s a pretty niche feature I guess.

You might like to check out these threads, one Sydney specific and the other more general info around why sometimes nodes show as red when they’ve been completed.

In general, it seems to be an issue with city syncs. Sometimes this is persistent (ie a sync that didn’t work correctly), while sometimes it is a temporary issue while a city is in the process of being synced. The latter might be particulary relevant to you right now (see first thread linked).

PS If you navigate to the Sydney city page, you can see (via the spinning icon) that the sync Mel requested is, indeed, underway. Sydney is so huge it can take a long time (days, not hours) to sync.

Thanks for explaining! I didn’t consider it might be linked to the Sydney-wide sync which is occurring.

I’ll monitor Sydney’s sync and wait until it is complete, hope that solves it!