features for realy long trips
-
Hi, would it be a good idea to split the route in a way that you set a limit for the distance you want to ride? I somehow miss this. You can set manually points but it’s kind of a guess work as the scale is hidden by some info on the map on my device. Thomas
-
I just got a swell idea (I think... ). Designate specific "split points" as a new kind of waypoint. Call it a "super VIA" or something. When you start a route, you answer a question like: "Which part you want to navigate today?".
Problem though is, for multi-day routes, you will soon cross the limit of 200 waypoints...
-
Thanks. Spiting function is nice and I know it, but it seems to me that you have not planned really long trips in a roll forward manner. My problem is not splitting, i can do that, but then I have again individual day trips ... What I suggested is to have a complete new functionality which allows a better management of such long trips. One feature missing is e.g. that you can "group" day trips together. Perhaps you need to manage that in a complete different way. One issue is the 200 waypoint limit for sure, I most likely talking about thousands of waypoints..... I don't have a solution, I wanted to launch a discussion.
-
Thanks. Spiting function is nice and I know it, but it seems to me that you have not planned really long trips in a roll forward manner. My problem is not splitting, i can do that, but then I have again individual day trips ... What I suggested is to have a complete new functionality which allows a better management of such long trips. One feature missing is e.g. that you can "group" day trips together. Perhaps you need to manage that in a complete different way. One issue is the 200 waypoint limit for sure, I most likely talking about thousands of waypoints..... I don't have a solution, I wanted to launch a discussion.
Hi @Robert-Laudensack not sure if this will be of help but I do fairly long trips but nothing as huge as your impressive 6 weeks.
I do similar to you & start with an outline to get an idea of the distances which enables me to choose destination / night stops. I will use up pretty much all of the 200 points creating the outline.Once the route outline is roughly done I then split it into the individual days & these are all stored in the same folder within MRA so they are grouped together
In the same folder I will create an Overview route which is made up of the individual days as described in this thread
As the Overview route contains a view of the individual days it is automatically updated when I edit each of the individual days route & I can see the whole trip
I agree more than 200 points would be nice & it has been requested many times but I believe it maybe kept at this limit for performance reasonsBlackView BV7100, Android 12
Normaly navigate Routes in Offline mode with Offline Maps -
Hi @Robert-Laudensack not sure if this will be of help but I do fairly long trips but nothing as huge as your impressive 6 weeks.
I do similar to you & start with an outline to get an idea of the distances which enables me to choose destination / night stops. I will use up pretty much all of the 200 points creating the outline.Once the route outline is roughly done I then split it into the individual days & these are all stored in the same folder within MRA so they are grouped together
In the same folder I will create an Overview route which is made up of the individual days as described in this thread
As the Overview route contains a view of the individual days it is automatically updated when I edit each of the individual days route & I can see the whole trip
I agree more than 200 points would be nice & it has been requested many times but I believe it maybe kept at this limit for performance reasons@Brian-McG I agree with your method. I plan a long trip setting the basic route and plan the stops for each day, then split into days and plan each day separately in detail. Routes, stops, special attractions, lunch, possible detours, and finally the stop for the night. It's much easier planning each day in detail. The next day can be reviewed in the evening to see if any changes are required. 200 waypoints is more than enough for a full day's travel.
2010 GL1800 Goldwing using Samsung Galaxy S20 5G Android 13.
-
@Brian-McG I agree with your method. I plan a long trip setting the basic route and plan the stops for each day, then split into days and plan each day separately in detail. Routes, stops, special attractions, lunch, possible detours, and finally the stop for the night. It's much easier planning each day in detail. The next day can be reviewed in the evening to see if any changes are required. 200 waypoints is more than enough for a full day's travel.
@RetiredWingMan I agree 200 points is about sufficient for a long single day but I find 200 is totally insufficient to do even the rough outline for my relatively short/long trips of 14-20 days
An outline of a trip of @Robert-Laudensack length with only 200 points is going to be extremely rough to the point it stops giving useful information& I lied a little about my method above
because for a 20 day trip that means only 10 points for each day it is only possible to create a very very rough outline,
I am forced to first split the trip into the outward & return legs so that this doubles the number of points I have for the rough outline stageThe fact that the 200 point limit keeps getting brought up in posts should be a sign to the developers that it is an issue
I understand that a limit is desirable for performance reasons & that allowing users to simple "Expand" the number of points in a route to 1000's could be a problem but maybe the total number of points & the expand function could have different upper limits
PC, network, server performance is always improving/increasing but the MRA point limit stays the sameBlackView BV7100, Android 12
Normaly navigate Routes in Offline mode with Offline Maps -
@RetiredWingMan I agree 200 points is about sufficient for a long single day but I find 200 is totally insufficient to do even the rough outline for my relatively short/long trips of 14-20 days
An outline of a trip of @Robert-Laudensack length with only 200 points is going to be extremely rough to the point it stops giving useful information& I lied a little about my method above
because for a 20 day trip that means only 10 points for each day it is only possible to create a very very rough outline,
I am forced to first split the trip into the outward & return legs so that this doubles the number of points I have for the rough outline stageThe fact that the 200 point limit keeps getting brought up in posts should be a sign to the developers that it is an issue
I understand that a limit is desirable for performance reasons & that allowing users to simple "Expand" the number of points in a route to 1000's could be a problem but maybe the total number of points & the expand function could have different upper limits
PC, network, server performance is always improving/increasing but the MRA point limit stays the same@Brian-McG this topic is expanding to something where I think you've all lost the meaning of MRA.
It's designed for diving routes and U het the impression where a very small group of users is trying to turn it in to something that it's not.
By design a Max of 200 waypoints should give you an estimate of the length of your routes. The conclusion is that' it's not designed to plot your very long journey in one single route
For most of the users it's already a hard job to navigate a one day route without deciding from the route. Therefore MRA must be able to help you out with that and rest assured it is.
Let's dat for the discussion that a route with 1000 waypoints would be granted by the Devs and in dayt 6 you would encounter a problem on the route du you would have to deviate. The amount of time that it would MRA to find a new route door that deviation is that long that I.'m sure no one would want that.
So I would advise you to really plan your trips one day at a time and have fun creating those long trips at home. What could be the advantage to have it all in one route.
In my opinion niet a good idea.
By the way of you need 200 waypoints for one route you might need to learn a bit more about planning your route. Whit an average of 5 k per waypoint your route would be a 1000 k. How are you gonna do that in one day. Don't dat by motorway because in that case you might need Max 40 waypointsHonda Goldwing GL1500,
Honda Silverwing GL 650
DMD2 T865X 8 inch Android tablet using MRA next for navigation
Garmin XT sold
Samsung S24FE mounted on a Quadlock and using Android Auto in my car -
@Brian-McG this topic is expanding to something where I think you've all lost the meaning of MRA.
It's designed for diving routes and U het the impression where a very small group of users is trying to turn it in to something that it's not.
By design a Max of 200 waypoints should give you an estimate of the length of your routes. The conclusion is that' it's not designed to plot your very long journey in one single route
For most of the users it's already a hard job to navigate a one day route without deciding from the route. Therefore MRA must be able to help you out with that and rest assured it is.
Let's dat for the discussion that a route with 1000 waypoints would be granted by the Devs and in dayt 6 you would encounter a problem on the route du you would have to deviate. The amount of time that it would MRA to find a new route door that deviation is that long that I.'m sure no one would want that.
So I would advise you to really plan your trips one day at a time and have fun creating those long trips at home. What could be the advantage to have it all in one route.
In my opinion niet a good idea.
By the way of you need 200 waypoints for one route you might need to learn a bit more about planning your route. Whit an average of 5 k per waypoint your route would be a 1000 k. How are you gonna do that in one day. Don't dat by motorway because in that case you might need Max 40 waypoints@Marinus-van-Deudekom I don't think you have read & understood my post, I already split my trips into individual days as you suggest
Often my routes when riding alone a days route will be of the order of 500 miles (800km) with no motorway & yes I often use nearly the 200 points per day because the routes use a lot of minor roads
Simpler routes that I organise for groups will obviously be a lot shorter & can normally be constrained with around 100 points
but this thread is NOT about short single days it is about LONG initial planning of tripsBlackView BV7100, Android 12
Normaly navigate Routes in Offline mode with Offline Maps -
@Marinus-van-Deudekom I don't think you have read & understood my post, I already split my trips into individual days as you suggest
Often my routes when riding alone a days route will be of the order of 500 miles (800km) with no motorway & yes I often use nearly the 200 points per day because the routes use a lot of minor roads
Simpler routes that I organise for groups will obviously be a lot shorter & can normally be constrained with around 100 points
but this thread is NOT about short single days it is about LONG initial planning of trips@Brian-McG I did read your comment but my point had to do with the current Max of waypoints by design.
If you are able to drive a 800 km route in one day not using motorways I'll solute you, respect. Given an average of about 40 km/h including stops etc in not motorways it would take you about 20 hours to finish that. Even with an average of 50km/h it would take you 16 hours. Riding my GoldWing that's even to much for me
-
I do think this is a sensible discussion. Planning multiple days in one route would really help preventing going over the same roads over and over, even in case do not do long distance trips, but drive multiple days around a single hotel. By segmenting routes into days, you could prevent the web-planner as well as Navigation to handle more than 200 routepoints on each single day. As @Marinus-van-Deudekom says the tool is not really fit for this, but given the big overhaul of the web-planner it would be a pity if we did not give this any thought. "what not is could be"
In my view the bigger problem would be to fit this into the in-app planner, since that one is based completely on the HERE SDK where the web-planner is not (and will not be as far as I know).
