Feature request: switch off automatic calculation of routes in the web routeapp
-
@Drabslab I think it is a very good suggestion. Doing a large multi day route before splitting off into multiple parts can be very handy for overall route hours or km. The refresh needn't be done every single route point change and must relieve the server of some CPU time too.
@Drabslab said in Feature request: switch off automatic calculation of routes in the web routeapp:
When making a route, each waypoint introduced leads to an automatic recalculation. When seriously changing a (long) route this can be a bt annoying as the system can take quite some time to recalculate and I have to wait in front of the screen until its done;
As a user, I would like to be able to stop automatic recalculation to change many points (or their order in the route) , or to combine several exiting routes and delete all the unneeded parts of that combination, and only have it calculated once when I switch calculation back on.
@Terry-Cox-0 said in Feature request: switch off automatic calculation of routes in the web routeapp:
@Drabslab I think it is a very good suggestion. Doing a large multi day route before splitting off into multiple parts can be very handy for overall route hours or km. The refresh needn't be done every single route point change and must relieve the server of some CPU time too.
Hmm, I see that this can be a problem with large routes and many shapingpoints. However the solution would better not be to disable calculation temporarily, but to limit the recalculations to the shaping-point being created or moved, and the previous and next shaping point. That would eliminate A LOT of calculation, make every change a snap. Earlier and latter shaping points are not impacted by this recalculation anyway...
I am just an enthusiastic MRA user, and hope you will be one too!
Most motorcycle problems are caused by the nut that connects the handlebar to the saddle.
Streetpilot 2610/Zumo 660/Zumo 395/ CAT S52 + MRA app -
In my capacity as a RouteXpert I make and check 100s of routes each year and have never considered the recalculation as being a problem.
Always willing to help if I can.
Triumph Tiger 1200 XRT called Tina.
MRA Navigation Next and SilverFox B8J bar buttons.
Quadlock wireless mount for IPhone 11.
Cardo Scala Packtalk Bold.
TomTom Rider 500. (In the cupboard now) -
In my capacity as a RouteXpert I make and check 100s of routes each year and have never considered the recalculation as being a problem.
@Nick-Carthew It all comes down to one's patience
and state of mind haha! -
@Drabslab said in Feature request: switch off automatic calculation of routes in the web routeapp:
When making a route, each waypoint introduced leads to an automatic recalculation. When seriously changing a (long) route this can be a bt annoying as the system can take quite some time to recalculate and I have to wait in front of the screen until its done;
As a user, I would like to be able to stop automatic recalculation to change many points (or their order in the route) , or to combine several exiting routes and delete all the unneeded parts of that combination, and only have it calculated once when I switch calculation back on.
@Terry-Cox-0 said in Feature request: switch off automatic calculation of routes in the web routeapp:
@Drabslab I think it is a very good suggestion. Doing a large multi day route before splitting off into multiple parts can be very handy for overall route hours or km. The refresh needn't be done every single route point change and must relieve the server of some CPU time too.
Hmm, I see that this can be a problem with large routes and many shapingpoints. However the solution would better not be to disable calculation temporarily, but to limit the recalculations to the shaping-point being created or moved, and the previous and next shaping point. That would eliminate A LOT of calculation, make every change a snap. Earlier and latter shaping points are not impacted by this recalculation anyway...
@Con-Hennekens said in Feature request: switch off automatic calculation of routes in the web routeapp:
However the solution would better not be to disable calculation temporarily, but to limit the recalculations to the shaping-point being created or moved, and the previous and next shaping point. That would eliminate A LOT of calculation, make every change a snap. Earlier and latter shaping points are not impacted by this recalculation anyway...
Fully agree, optimizing the calculation algorithm to only the points that need recalcualtion would give a better effect than what I proposed
-
When making a route, each waypoint introduced leads to an automatic recalculation. When seriously changing a (long) route this can be a bt annoying as the system can take quite some time to recalculate and I have to wait in front of the screen until its done;
As a user, I would like to be able to stop automatic recalculation to change many points (or their order in the route) , or to combine several exiting routes and delete all the unneeded parts of that combination, and only have it calculated once when I switch calculation back on.
Uncalculated parts of the routes could be shown on screen by straight dotted lines (as an example).
I guess this could also save some server time?
Apologies if it's poor form here to bring back old threads, but it seemed to be the exact right search result.
New user here, and I recently imported a route started in google maps, brought it in via KML file. Some part of the process went wrong and the 50 stops were partly in the wrong order. So I thought I would shuffle in MRA rather than play with KML.
I needed to move about 20, and I was hoping this would have taken me about 90 seconds. with moving some points multiple times, it took about 5 minutes, with the millisecond lag between each move getting more and more painful to experience.
Microsoft excel has an option to switch off auto-recalculation and I went looking for a similar feature, but couldn't find one. It would be a great addition.
I do get that some people might feel that it's just a matter of throwing more processing power at the problem, but there will always be a delay, and we have different expectations of what makes a good experience. Personally I shuffle data like I'm shuffling dominoes and the merest delay feels like trying to shuffle dominoes in treacle.
When a first quick shuffle is needed, or when brainstorming a road-trip, I would applaud the ability to pause recalculation. Great suggestion.
-
Apologies if it's poor form here to bring back old threads, but it seemed to be the exact right search result.
New user here, and I recently imported a route started in google maps, brought it in via KML file. Some part of the process went wrong and the 50 stops were partly in the wrong order. So I thought I would shuffle in MRA rather than play with KML.
I needed to move about 20, and I was hoping this would have taken me about 90 seconds. with moving some points multiple times, it took about 5 minutes, with the millisecond lag between each move getting more and more painful to experience.
Microsoft excel has an option to switch off auto-recalculation and I went looking for a similar feature, but couldn't find one. It would be a great addition.
I do get that some people might feel that it's just a matter of throwing more processing power at the problem, but there will always be a delay, and we have different expectations of what makes a good experience. Personally I shuffle data like I'm shuffling dominoes and the merest delay feels like trying to shuffle dominoes in treacle.
When a first quick shuffle is needed, or when brainstorming a road-trip, I would applaud the ability to pause recalculation. Great suggestion.
@Abssorb-0 said in Feature request: switch off automatic calculation of routes in the web routeapp:
I do get that some people might feel that it's just a matter of throwing more processing power at the problem,
No problem to raise an old theread again, that is what these are there for.
to my knowledge the recalculation is done on the MRA server so you may buy a supercomputer and it would not help at all.
Unfortunately, the suggestion in this thread was (again to my knowledge) not taken on board by the developers.
-
When making a route, each waypoint introduced leads to an automatic recalculation. When seriously changing a (long) route this can be a bt annoying as the system can take quite some time to recalculate and I have to wait in front of the screen until its done;
As a user, I would like to be able to stop automatic recalculation to change many points (or their order in the route) , or to combine several exiting routes and delete all the unneeded parts of that combination, and only have it calculated once when I switch calculation back on.
Uncalculated parts of the routes could be shown on screen by straight dotted lines (as an example).
I guess this could also save some server time?
https://www.myrouteapp.com/en/social/route/6366286?mode=share
Hereâs a public route from Lands End to John OâGroats.
851 Miles, 200 hundred waypoints.
For me it takes about a second to recalculate?
Maybe this is a bit too simplistic an example, as I used the Expand function to generate them.
I have not checked all the waypoints and some will be on junctions and will cause issues.You donât stop riding when you get old, you get old when you stop riding.
-
https://www.myrouteapp.com/en/social/route/6366286?mode=share
Hereâs a public route from Lands End to John OâGroats.
851 Miles, 200 hundred waypoints.
For me it takes about a second to recalculate?
Maybe this is a bit too simplistic an example, as I used the Expand function to generate them.
I have not checked all the waypoints and some will be on junctions and will cause issues.@Steve-Lynch fair enough , but thar seems yo have little to do with the use case presented here?
It is not difficult, it is easy, it's a hobby
-
@Steve-Lynch fair enough , but thar seems yo have little to do with the use case presented here?
Sorry, I was bored this morning and I woke up at at 6am with nothing else to do!
I would have to disagree on this point if, recalculation is actually polling and recalculating every waypoint on the route.
Whilst the second route which I have now created from the first âexpandedâ route is a wildly ridiculous route, it is still as valid as any ârealâ route as it does demonstrate that 200 âfull blownâ waypoints with full addresses do actually recalculate in less than a second.
MRA donât seem to agree that it is necessary to turn recalc off so I guess my point is void, but at least it gave me something to do this morning.Ok Iâll get my coat now.
https://www.myrouteapp.com/en/social/route/6368583?mode=share
You donât stop riding when you get old, you get old when you stop riding.
-
Sorry, I was bored this morning and I woke up at at 6am with nothing else to do!
I would have to disagree on this point if, recalculation is actually polling and recalculating every waypoint on the route.
Whilst the second route which I have now created from the first âexpandedâ route is a wildly ridiculous route, it is still as valid as any ârealâ route as it does demonstrate that 200 âfull blownâ waypoints with full addresses do actually recalculate in less than a second.
MRA donât seem to agree that it is necessary to turn recalc off so I guess my point is void, but at least it gave me something to do this morning.Ok Iâll get my coat now.
https://www.myrouteapp.com/en/social/route/6368583?mode=share
my two cents.
Reducing the number of waypoints (to 40) 1sec
Change from Here to TomTom 1sec
Move waypoint 1sec
Using route Test 2
