The ‘expand’ function
-
The ‘expand’ function is really useful for a number of reasons. I was wondering though if it might be improved by offering what I’d call ‘expand 2’?
Imagine an A to B route, from Calais to Rome, a distance of 1,000 miles. Naturally, this will only have two waypoints being: A at Calais and B at Rome.
Now imagine (for example only) that the rider would like to break their journey up into 10 days of 100 miles distance each. Expanding the number of waypoints to 12 does not space the 10 intermediate points equally between A and B.
My idea for ‘expand 2’ would be to allow the rider to chose the spacing of the intermediate points. For example, the question asked by MyRoute would be:
“Insert waypoint every xxx miles”, xxx being the gap the rider wanted. The rider would then have a suitably divided route.
The rider could then use the ‘split’ function to break the route up into its 10 sections, one for each day.
Where I think this might be useful is where:
A. A rider, as is sometimes the case, cannot get to grips with A to B distances. We see this in lots of forums, where people say, “Tell me Calais to Rome” but with no clear idea as to how far that might be or how to break it up into sensible chunks.
B. When a rider is sent a copy of a route (sometimes of several thousand miles) but it’s not broken up at all. Inserting a point every say, 250 or 500 miles, might help the rider imagine it better.
C. Having the 250 or 500 mile points pop-up in a different colour, might be nice, too.
Richard
-
@Richard-18 I like the idea, but I'm not sure 'distance' is the best measure to space the points. Obviously, there's a huge difference in driving 500 miles on the highway/motorway vs driving 500 miles on secondary, twisty roads. So I would imagine estimated driving time, not distance, would be the way to go. E.g. plan a stop every 5 hours of driving (assuming 5 hours + stops make a full driving day).
-
@Herko-ter-Horst @Richard-18 I think it's a cool idea too! But why not both? Driving a car or camper (if that functionality is added in the future) is less tiring than riding a motorcycle. I see both options, deviding a route based on distance or time, as a great addition.
-
@Richard-18 Your basic idea is good and has been requested in the past. Maybe it could, in one form or another be taken on board when the planner is updated.
But Herko is right in his reaction.
and in addition, when travelling, you may want to do a day of highway to cover a lot of distance but in general, that is a boring day.
For long stretches, I usually put in start and ending point, and then enter intermediate waypoints of places i want to visit and add the amount of time i want to stay there.
then put on michelin to select green roads, and check with the satelite ovrlays if those green roads are truly green
then I look at the list of waypoints to select days of maximum 300 km (or introduce a stretch of highway when needed)
i cut this long route in pieces of maximum 300 km and then optuimize the individual routes so i get a max of 350km secondary roads a day
That makes a holiday, a relaxed affair and not a race form one point to the next.
-
Thank you everyone.
Indeed, I used distance (as a heathen Englishman, I used miles) as an example only. It would work well with time as the medium to divide by, too.
But maybe not so well, as eight hours riding without stops, is a lot further than eight hours duration with lots of stops. That is another common mistake people new to riding longer distances make. I see this a lot when people say “But Google says it’s X hours from Calais to Rome”…. Indeed it is, if you go nonstop down the motorway but much longer if you ride every D road and stop to take pictures every 10 minutes.
I sometimes use the ‘split route’ function in Kurviger, where you can subdivide a single route between several types of road. As an example, for the 1,000 miles of Calais to Rome, I might ask Kurviger to give me Calais to Metz by motorway, then (in the same single route) to give me Metz to Rome via non-motorway. It will do it, giving me mileages and estimated (best case) times. Being able to quickly subdivide the Metz to Rome route, by using MyRoute (which I’ll be using to fine tune Kurviger’s idea of a ‘good route’, which often does not exactly match my own ideas) either by mileage or time or both, would be good.
-
@Richard-18 said in The ‘expand’ function:
I sometimes use the ‘split route’ function in Kurviger, where you can subdivide a single route between several types of road. As an example, for the 1,000 miles of Calais to Rome, I might ask Kurviger to give me Calais to Metz by motorway, then (in the same single route) to give me Metz to Rome via non-motorway. It will do it, giving me mileages and estimated (best case) times. Being able to quickly subdivide the Metz to Rome route, by using MyRoute (which I’ll be using to fine tune Kurviger’s idea of a ‘good route’, which often does not exactly match my own ideas) either by mileage or time or both, would be good.
That is exactly what i tried to explain above
-
@Drabslab said in The ‘expand’ function:
@Richard-18 said in The ‘expand’ function:
I sometimes use the ‘split route’ function in Kurviger, where you can subdivide a single route between several types of road. As an example, for the 1,000 miles of Calais to Rome, I might ask Kurviger to give me Calais to Metz by motorway, then (in the same single route) to give me Metz to Rome via non-motorway. It will do it, giving me mileages and estimated (best case) times. Being able to quickly subdivide the Metz to Rome route, by using MyRoute (which I’ll be using to fine tune Kurviger’s idea of a ‘good route’, which often does not exactly match my own ideas) either by mileage or time or both, would be good.
That is exactly what i tried to explain above
Indeed
-
Preparing a holiday is fun, and a whole year process.
When I read about a nice destination somewhere near a point when I may end up during a future holiday, I already bookmark it in the routeplanner as POI.
Its just fun to connect those dots for makign a holiday trip
-
Moved from [App] Suggestions and Discussion by
Corjan Meijerink
