Thanks, James… I wondered if something throttling-like might be happening behind the scenes to handle an increased load? Is membership/participation up significantly?
I’ll try the “don’t view” option next time out–although that might be tough…I’m a little astonished (and proud!) at all my purple, and love admiring it.
One workaround I’ve found for the did-I-miss-a-street before I leave the area, is to turn on an app on my phone that draws a real-time route. It’s easy to check that during the activity as well as when I get back to the car. (I’m sure there’s an iPhone equiv.)
Oh, fair, that could play a role as well… Supporters get their own queue for processing and LifeMap builds, so their build times are dramatically faster. The Status page shows their queue has a 5 second delay, and the free accounts have a 3 hour delay.
Fair. Either way, next time you see the issue send me a message and if I’m free I can take a look.
I’m not sure that I follow the options that were presented. Preferably I’d want the activity to show on my lifemap, be included in Territories, and also the streets completed (40ish) during the activity to all be readded back to my profile.
As for the speed limiter. Does that flagging of an activity with an average speed of 15mph or that any point in which 15mph is hit if even for only 2 minutes? I don’t think either is working at the moment for the person’s lifemap that I’m looking at today. They have some stuff on the interstate and highways that are clearly in a vehicle.
It’s definitely a cache issue that causes the LifeMap to update later. Usually I can see a new run pop in immediately when I’m zoomed out but it disappears when I zoom in. I have tried your workaround and avoided using the site on my phone prior to running, but it started to get a little annoying and didn’t always work.
It’s not a huge deal for me since the LifeMap usually looks right by the time I get home and I can tell if I missed something using the activity view or node hunter.
The problem seems to be limited to the reprocessing that occurs after a city sync … LifeMap & Territories seem to work fine with these, and the initial processing seems to go well.
I’m still learning what the threshold is on what kind of activities cause actual damage during that reprocessing. First, I have to do data cleanup and then I can rerun the test that failed. I’ll know more then.
It’s entirely possible that the actual issue is with another category of activities (like the 600714.79 mile activity I noticed get deleted a little while ago). If that’s the case, I’ll be able to increase the distance limit & we can all pretend this never happened.
The speed is calculated for the whole activity length_in_miles / duration_in_hours.
The system currently just stops new activities from syncing in at 15+mph. I haven’t gotten around to cleaning out activities that are too fast, yet. Right now, I just display a warning on those activities … they’ll be removed as soon I can get to it.
I just made a change in my third party cache service that I think will remove the hours-long wait. The 5 minute cache is still in place.
I might have found a way to dynamically purge the cache … So I might be able to reinstate the multi-hour cache & also force a purge at the end of every LifeMap rebuild.
That’s going into the to-do pile for now, though … let’s see if this 5 minute cache mostly resolves things.
Amazing updates and love the continued work and improvement to this awesome site!
So, for what it’s worth from just one single user…what is needed to get the missing/broken cities tracker cleaned up and updated at some point? There are now over 100 on just one tab alone now, most of which have lingered since late Spring/early summer. I realize this isn’t as big as a priority as it used to be since a lot has been added over the years for major cities/territories and now it’s just residual, smaller areas outside of those areas missing. But without the ability to track any activities at all in towns/areas not currently represented, the rest of this add-on stuff is insignificant for tracking or completion.
Just my two cents since the list only grows each time I look at it and I hesitate to add anything further at this point if what is on there isn’t processed first. Keep up the great work on here!
Adding cities can add roughly the same amount of background processing as city syncing, and I’m actively working on improving that … I really need that to be in good shape before I toss another ~hundred cities into the system … but I do have some decent progress to test, so I can look into what can be added fro that sheet.
I’m actively avoiding nested cities in that list, as well, since I’d rather effort going into expanding people’s reach.
That sheet is the list, so if you don’t add something I don’t know about it. I’d recommend ignoring the size of the list (it used to reach into the thousands).
I just noticed that my 3 journey runs in TN were removed from my map and found this post. I completed Heart of the South, Vol State, and Third Circle of Hell all on foot and was able to get them each as one Coros file. You can see the results in UltraSignup and on my Strava account. They are all over 300 miles. Any way I can get them back?
There isn’t a way right now, but I’m not opposed to allowing these types of journey runs into CityStrides. I just need to build out a way to exclude them from processing (at least post-city-sync, but potentially also direct).
I’m guessing that I’ll end up building some kind of request form that lets you share links/activity identification & an explanation. I’ll manually review these & add them to an exclusion list of some sort.
I’m also considering splitting each file in half and posting them on Strava temporarily so each file is less than 200 miles. Is there any issue with what I’m thinking of? If it’s on Strava temporarily, does it go away from citystrides once I remove it from Strava?
I might have found a way to dynamically purge the cache … So I might be able to reinstate the multi-hour cache & also force a purge at the end of every LifeMap rebuild.