I’m trying to build routes today and they are not saving completely - only the first few portions of the route will be saved. I’ve tried 3 times now, and on the last try I clicked on save repeatedly and waited a reasonable delay before clicking on view, but it still did not capture the entire route I’d built.
Is this a known issue? Is there a limit to the number of steps in a custom route?
Regarding some enhancement requests (sorry if duplicates):
Optimize route to capture most nodes (e.g. provide a distance and the route is built automatically)
Live tracking in the CityStrides map - see the nodes get eaten up pacman style in real time
This issue is new to me & I haven’t been able to reproduce it … There aren’t any limits to steps in a route (that I’m aware of)
When you click “Save”, if the “Visit” button is visible then everything has happened on the server - no need to wait for anything (there are many things in CityStrides that do involve background jobs, but route creation isn’t one of them)
I haven’t been able to figure out a path in the code that allows the route to be displayed in the browser prior to clicking the “Save” button and then allows something different to be saved in the database.
Did you keep any of the bad routes that you’d be able to share links to? (it’s ok if they’re private, I’d be looking at it through the database not the website)
If you’d like automatic route generation, then you should upvote Automatically Generate Routes … that thread has gone through some lifetimes it was initially shot down by the community, but I’m hearing more requests for it lately
Similarly, Live Trace or Pacman covers the live tracing idea … but that idea is basically a dead-end as a website:
I’m pretty sure the main issue I need to overcome is the fact that CityStrides is a website, and websites do not retain GPS tracking when they go into the background or when the phone is locked. So the tracked GPS lines would include straight lines during that background/locked time.
Although, you’re asking for something slightly different in that it’s individual nodes marked incomplete/complete as you pass them … since I don’t need to retain GPS info to accomplish that (just some browser storage that collects completed node IDs maybe) this might be possible