The web planner needs some love & development?
-
@Brian-McG it looks to me like the planner took the shortest route while the navigation chose what may be the fastest route. I think car routing can select shortest or fastest routing.
-
Just to add my two cents to an already lengthy discussion...
I'm a simple guy. I like simple tools. The navigator is very important to me. I no longer have to fool around with my Garmin, gpx files, Kurviger, Osmand, etc., etc... wow, so much better for me. My phone runs fine, although I would be happy to cook it anyway. (I pay a few dollars a month to Google to replace it if that happens... or if it falls off the bike and bounces along the ground... etc.
The one thing about the app that is less than ideal is that it is often a bit behind me... it's less than ideal to know where I >was< than where I am about to be. And I recognize that the issue may be with an outside provider.
Our pals at MRA have a great product as well as a business that they need to run profitably. I want them to be profitable, so they are here tomorrow as well as today.
So I think all of this input is good, but once given, I might suggest that we have the confidence in our MRA friends to make the best decisions and trade-offs to keep their product attractive, their user base growing, and their company profitable!
Vinnie
-
I thought about adding a long reply explaining why its fine for some use cases to only require a few points but that there are other occasions, like when planning routes for large groups where multiple different "engines"/navigation devices will be used, then more points are required.... etc etc etc...
But this just made me laugh .....
The planned route above takes what I would say is the expected logical path between points 1 & 2,
click the Navigate button & ....
the route/path is re-calculated 
I understand that different engines/routing algorithms can calculate different paths & there is probably a perfectly logical reason for the difference in this case. I do not expect a fix.
I just thought it was hilarious that within the same app it can display one path & then on the next screen show a different path
& this is why I prefer to use more points to "constrain" the engines/algorithms to the path I want to take.So for a route similar to the above, where there are different possible paths that the engine/algorithms might choose, I would normally place an additional point somewhere between 1 & 2 to prevent the strange path the engines sometimes decide to take.
This simple control of the engines/algorithms obviously uses more points
@Brian-McG, I can only say my simulation does not show the same problem. Could it be caused by traffic jam?
@RetiredWingMan said in The web planner needs some love & development?:
it looks to me like the planner took the shortest route while the navigation chose what may be the fastest route.
If you choose the navigation option "Shortest route", that option will be stored with the route, and replicated to MRA Navigation, which will also show "Shortest" at the route optimisation. Exactly to prevent what you are suggesting
-
Hi all,
I completely agree with Peter here, in that the browser based planner is why I bought into the MRA system (and yes, I find 200 points limiting when I want to build an overview of a tour).
I would love to see some more active development in this area. Whilst making the app a slick proposition is no doubt enticing, for me the heart of MRA is in it's ability to plan complex routes and visualise them before riding.
I made a suggestion (ability to add temporary waypoints / mid-way through a route) back in Oct 23 which was well received, but has not yet been implemented.
Being a continual user of the planner, I have other suggestions, which I'm happy to put some serious work into defining, provided I can see that they'll go somewhere and in a reasonable timeframe.
So ... does anyone have info on the web redevelopment project timescales, and specifically on whether this involves a re-work of the planner to make it even more productive and easier / more pleasant to use ?
Thanks, Jem
-
Hi all,
I completely agree with Peter here, in that the browser based planner is why I bought into the MRA system (and yes, I find 200 points limiting when I want to build an overview of a tour).
I would love to see some more active development in this area. Whilst making the app a slick proposition is no doubt enticing, for me the heart of MRA is in it's ability to plan complex routes and visualise them before riding.
I made a suggestion (ability to add temporary waypoints / mid-way through a route) back in Oct 23 which was well received, but has not yet been implemented.
Being a continual user of the planner, I have other suggestions, which I'm happy to put some serious work into defining, provided I can see that they'll go somewhere and in a reasonable timeframe.
So ... does anyone have info on the web redevelopment project timescales, and specifically on whether this involves a re-work of the planner to make it even more productive and easier / more pleasant to use ?
Thanks, Jem
@Jem-Cotton said in The web planner needs some love & development?:
I would love to see some more active development in this area. Whilst making the app a slick proposition is no doubt enticing, for me the heart of MRA is in it's ability to plan complex routes and visualise them before riding.
I completely agree with that.
The best navigator still cannot make anything out of an incorrectly and bad planned route. -
@Jem-Cotton said in The web planner needs some love & development?:
I would love to see some more active development in this area. Whilst making the app a slick proposition is no doubt enticing, for me the heart of MRA is in it's ability to plan complex routes and visualise them before riding.
I completely agree with that.
The best navigator still cannot make anything out of an incorrectly and bad planned route.@Jem-Cotton said in The web planner needs some love & development?:
So ... does anyone have info on the web redevelopment project timescales
Yes
@Corjan-Meijerink said in I'm very happy with MRA but......:
When the big 4.1.0 update is released for the app we will prioritise the coming months
-
@Jem-Cotton said in The web planner needs some love & development?:
I would love to see some more active development in this area. Whilst making the app a slick proposition is no doubt enticing, for me the heart of MRA is in it's ability to plan complex routes and visualise them before riding.
I completely agree with that.
The best navigator still cannot make anything out of an incorrectly and bad planned route.@Jack-van-Tilburg said in The web planner needs some love & development?:
The best navigator still cannot make anything out of an incorrectly and bad planned route.
Correct, for me it is all about expanding and integrating the MRA ecosystem
We have seen a long process to improve the navigator, and maybe that process was TOO long putting to much time on trivial(?) things (while still struggling with core shortcomings (battery issue)). Maybe it was the only way possible considering that the previous navigator was outdated in many aspects.
I would not like to see that this would be followed up by an equally long cycle for the planner.
Instead, I am hoping for shorter sprints tackling one subject (POI, multi-map, ...) to the extend relevant in all parts of the eco system. This will prevent that one part grows totally outdated compared to the rest, and will give the users something new to play with very often.
It is not difficult, it is easy, it's a hobby
-
@Jack-van-Tilburg said in The web planner needs some love & development?:
The best navigator still cannot make anything out of an incorrectly and bad planned route.
Correct, for me it is all about expanding and integrating the MRA ecosystem
We have seen a long process to improve the navigator, and maybe that process was TOO long putting to much time on trivial(?) things (while still struggling with core shortcomings (battery issue)). Maybe it was the only way possible considering that the previous navigator was outdated in many aspects.
I would not like to see that this would be followed up by an equally long cycle for the planner.
Instead, I am hoping for shorter sprints tackling one subject (POI, multi-map, ...) to the extend relevant in all parts of the eco system. This will prevent that one part grows totally outdated compared to the rest, and will give the users something new to play with very often.
@Drabslab said in The web planner needs some love & development?:
the eco system
Yes, yes... who thinks all that is important?
Isn't it so that the Planner is now also used by a lot of users with navigation devices other than MRA Navigation?
And of course I understand that it seems fantastic that the Planner and MRA Navigation fit together well in a eco system. But they already do that in a way now, don't they? In a very useful way, right?
And of course I now create beautiful routes with the Planner and am happy with the functions it offers. But there are many points that could be more beautiful, more intuitive and more convenient.
If I had a choice then I would go to pick the low-hanging fruit.But my biggest wish?
Make a plan and stick to the plan. -
@Drabslab said in The web planner needs some love & development?:
the eco system
Yes, yes... who thinks all that is important?
Isn't it so that the Planner is now also used by a lot of users with navigation devices other than MRA Navigation?
And of course I understand that it seems fantastic that the Planner and MRA Navigation fit together well in a eco system. But they already do that in a way now, don't they? In a very useful way, right?
And of course I now create beautiful routes with the Planner and am happy with the functions it offers. But there are many points that could be more beautiful, more intuitive and more convenient.
If I had a choice then I would go to pick the low-hanging fruit.But my biggest wish?
Make a plan and stick to the plan.TS here. I sure hit a nerve, I guess.
Totally agree that a more agile approach would be desirable.
But like Jack, I'm not sure that "integrating the MRA ecosystem" would be the best direction of travel. For me the GPX ecosystem is key. See my initial reply at the top of this thread. We need to support a variety of devices, tools & apps and better GPX support is the way to do that.
Let's not forget that this is where MRA was first successful: a tool that let you plan routes which you could then export to Garmin, Tomtom, etc.
(For comparison, take a look at gpx.studio, which I think was hacked together by a brilliant student to map his own "extreme running" - but which already has so much more depth in GPX handling than the MRA planner has today.)
-
@Peter-3b said in The web planner needs some love & development?:
I sure hit a nerve
Not just with @Drabslab and me I think.
With 26 upvotes for your opening post it is the most highly rated post ever in my guess. -
@Drabslab said in The web planner needs some love & development?:
the eco system
Yes, yes... who thinks all that is important?
Isn't it so that the Planner is now also used by a lot of users with navigation devices other than MRA Navigation?
And of course I understand that it seems fantastic that the Planner and MRA Navigation fit together well in a eco system. But they already do that in a way now, don't they? In a very useful way, right?
And of course I now create beautiful routes with the Planner and am happy with the functions it offers. But there are many points that could be more beautiful, more intuitive and more convenient.
If I had a choice then I would go to pick the low-hanging fruit.But my biggest wish?
Make a plan and stick to the plan.@Jack-van-Tilburg said in The web planner needs some love & development?:
Make a plan and stick to the plan.
YES
I think we all mean more or less the same... with different words
@Peter-3b said in The web planner needs some love & development?:
We need to support a variety of devices, tools & apps and better GPX support is the way to do that.
which are all part of the eco system in my book
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
