Kind regards
Joel Edding
My profile link : CityStrides
Hi. Yesterday around 70 streets disappeared that I have run. And according to the map there are nodes left at places I have run several times. Can any one please help me with this?
3 Likes
It is happening everywhere because @JamesChevalier implemented the 1 node street removal from CS - I lost 3 streets from the Town of New Scotland for this same reason. The screenshot is from the boarder of New Scotland and Bethlehem, the road that was removed was West Yard Rd.
Thanks for your answer but I don’t really understand what it means. Are the missing streets going to pop back in a while without me doing anything? I live in Stockholm.
1 Like
With streets that cross a border and only have one node they are permanently removed. Unless @JamesChevalier changes the setting back. I believe that he has been presented enough evidence that the 1-node removal decision was a bad decision.
So that mean that those around 70 streets that I lost ain’t coming back? If that’s the case I kind of loosing my faith in CS and the fun with it. 
2 Likes
There is definitely something wrong with Stockholm since the update yesterday. We are three runners who were at 99 or 100% for Stockholm. Today all three of us are at 3008 out of 4256 streets, 70%.
@JamesChevalier can you see what’s wrong?
An example of a street of mine
which shows incomplete even though it is completed:
experiencing the same issue! 67 streets gone, including several where the nodes were certainly “marked” as in here
A few recent syncs caused some big RAM issues, and it looks like Stockholm is one of the four cities that are in an … odd state … that I’m trying to figure out. It’s helpful for me to see how this is playing out from your perspective, so thanks for sharing.
I’ll be working on cleaning things up (though, given the timing around the holidays, this might drag on a bit). You don’t need to do anything, it will all be handled by data reprocessing.
It’s very possible that some people are seeing a similar temporary issue, because of how data is handled during a city sync. A very large city was sent in for a sync, which queued up a lot of background work. Since all city syncing shares the same queue, this one large city’s work can affect a number of other cities if they’re syncing at the same time.
The (also temporary) single node street issue isn’t likely playing a role here. That issue doesn’t have a huge affect on most cities, and doesn’t present itself in this way (random unfinished nodes appearing when they’re definitely completed).
2 Likes
Thanks for working with solving this!
Hi,
Unfortunately the problem is not solved. Are you working on it? For an example look att the attached picture.
Kind regards
Joel
Yeah, I have a list of a few cities that I still need to clean up.
1 Like
I hope Stockholm is on that list!
Sorry, yes, that was implied.
1 Like
Stockholm is ok now, thanks!
Thanks for fixing Stockholm!
I’ve got two more that I’ll need to fix up over the next couple nights … the fix affects general activity processing, which means that people saving new activities won’t see their progress updated immediately & this causes confusion … the least worst way to handle this is to do the big reprocessing “overnight” (this kinda doesn’t actually exist when operating a global website) while there are fewer activities being save.
@hans1 I got my eyes on you. Keep up the good effort in Stockholm