No doube operator error, and the first time I followed a route with the app (as a trial, it was a circular route from home) just a few miles to go I noticed that there were 'reroute' 'ingore' options on the screen (being familiar with the location I assumed I'd taken an alternative route for the last few miles). I chose 'reroute' and all seemed good until I finished my ride and saved the journey as only the section from the reroute point was saved and the earlier section of the route was lost. Of course, being in an area I knew I could have chosen either option, and losing the route did not matter, but I am curious as to what I did wrong.
Comments
Scorbutico, if you can share the routes - the original and the 'saved' one, we might be able to throw some light on the matter.
The easiest way to share is to make sure the route is not private, copy the URL and paste it here.
It looks like you went off course, CT rerouted you to get to the destination and then offered you a chance to save the variation?
If you have the original route and the variation, saving both in the one folder, then displaying the folder as a map (my journeys) you'll see the difference.
If you don't have the original (deleted?) then I strongly doubt that CT deletes a planned route when we go off course. It's more likely to be user error, I'm afraid. Perhaps replicate the error on a short 'around the block' ride and pay closer attention to the instructions?
This is all I have left: https://cycle.travel/map/journey/917907 I obviously saved it over the original planned route, no doubt streaming eyes from the bitter cold weather didn't help. I will try again.
‘Reroute’ takes your current location and restarts the route there to get you back on your planned route.
So if you have a route with via points A,B,C,D,E,F, and you go off course somewhere between C and D (let’s call your off-route location Z), then it’ll create a route Z,D,E,F.
If you then save this then it’ll overwrite your previous route (i.e. the ABCDEF route).
I think this goes back to the thread about recording an activity – because that’s not something c.t does, I hadn’t envisaged that people might save their route at the end of riding it. But if this is genuinely something people are doing then I guess I could alter the app, either so that ‘Reroute’ actually changes the route to ABCZDEF, or that it flashes up a warning saying ‘The route was re-routed, do you really want to save?’.
Richard
Seems to me that IF you do want to develop a feature in the app to "save simple data about my ride including the route as ridden", then ABCZDEF would be the version needed.
(For completeness: It still might not be exactly the route as ridden, as the app would create its own optimum route from C to Z, whereas the actual route taken may have been different, esp if the reroute occurs some distance after the via point C. But IMO that caveat would rarely be material, so should be accepted in order to avoid further bloating the development task. In any case, couldn't a user wanting "perfection" use the website to do a post-ride edit of the "saved as ridden" route to add via points between C and Z to record even more exactly what they actually did?)
I had not realised what the impact of reroute option was but understand now where I went wrong. Perhaps it's just me but I save all my rides even the ones that I do regularly.