My wife and I will be cycling around France during September and October. We've planned a 2600km route using cycle.travel but I cannot determine how to extract day long sections of the route for use each day. The "Split Route" feature in the web tool isn't what we want since that divide up the entire route a priori. We don't know how far we'll ride each day, so want to simply split out the section of the route for the next day, say 100km section. Then the next day, go back to the original full route, take our current position and split out the next 100km. And so on throughout the trip.
We want the short GPX tracks so that we can load it into Komoot for the day's ride. We've found using the cycle.travel iPhone app to be much more power hungry since it provides "turn-by-turn" guidance and hence keeps the GPS system always active, whereas Komoot only activates the GPS when the app is on-screen. The turn by turn feature is nice in a complex environment like a city but when we're riding in the country-side we don't need it and would like to save the power.
Any advice on how best to do this would be appreciated.
Comments
Ivars, adding a viapoint at your daily destination, clicking on it, selecting 'more' in the dialogue box then choosing 'delete before' will remove the portion of the route already travelled but leave the remainder.
I'm sorry, I don't understand your 'short' gpx question. CT allows downloading of different formats. Maybe try different ones? While I have Komoot I don't use it. And don't trust it.
Given the recent ability to add photos as Markers on the CT app and given your location I'd stick with CT, pack a powerbank and enjoy the ability to add special photos to my route that I'll have for evermore.
Hi HobbesOnTour. Your viapoint suggestion solved my problem.
First, let me explain what I meant by "short GPX". What I meant was a GPX track just for the next day versus the entire route. Typically we would want to create a GPX track that extends about only to our expected destination for the day (with some buffer in case we want to keep riding).
Using via points solves the problem. I need three steps:
1. Make a copy of the entire route, rename the copy as Day XX.
2. Add two via points to Day XX. One at the day's starting location and one at where we expect to end the day.
3. Select the start via point and "Delete Before" and then select the finish via point and "Delete After". Now the route is just the portion of the overall route that matches are expected ride for the day. Export this as a GPX file for Komoot.
I had missed the Delete Before/After features, so thanks for pointing them out.
I agree with you regarding not trusting Komoot for the route finding, but we're only using it due to the power savings. We camp most of the time, so the less we need to charge power banks and phones the better. We do have a solar panel to charge a phone/power bank during the day, but it needs sunny weather and can't fully satisfy our charging needs if we have high usage of the phones.
We used CT a few years ago on a 4 month Europe trip and loved it. This was before the App existed. We'll experiment with the App this trip, but our local experiments have shown that it still uses a lot more power than something like Komoot (but Komoot isn't providing turn-by-turn navigation). Which we use will likely depend on the complexity of the navigation.
For what it’s worth, I find that on my iPhone, loading a route into the c.t app and turning the screen off (using the side button) uses about 1% of phone battery per mile while still providing spoken directions. So a 50-mile route, which is more or less what I do in a day (depending on hills!), will use half the battery. I’ve just added an option to the Android app to turn background navigation off even though you have a route open, and will look at adding this to the iOS app too.