The web planner needs some love & development?
-
For me the core functionality of MRA is the web-based routeplanner. This is why I've become a gold member, and as many of you, I am now managing hundreds of routes and tracks with it.
The only use I personally have for the MRA app is as a gateway between my Android nav-phone (running Kurviger, Locus, OSMand etc) and my MRA routes archive. I don't want or need one integrated "MRA experience", I want to be able to pick the best point solution for every job and tie it together with GPX. So it hurts a bit to see so much of MRA dev effort go into the app, where it has to compete with 10s of other/better products.
Guys, you have a UNIQUE property in the planner, which is the only fully featured route planner that includes so many routing engines, layers, Google Streetview integration etc.
How about spending some love & care & dev resources on this?
Some areas that are really starting to hurt:
- showing and managing multiple routes in a folder (must be the #1 request here over the past few years, "a la Basecamp"), in order to plan longer trips
- reliably handling big GPX files, KML conversion etc (too many random error messages when importing GPX from non-MRA sources, ACT, TET)
- functions to manage multiple tracks, segments and POIs in one GPX file (see gpx.studio for inspiration) - also on import & export
- reliably handling big routes, instead of just giving up; remove the 200 waypoint restriction
I understand that this is a community forum, so I don't expect any formal follow-up by MRA.
However, I would really love to see a backlog for the next-gen route planner!@Peter-3b Personally I'm reasonably happy with the route planner at present. I would prefer that the Nav app gets fully sorted with regard to battery drain and car play for when I use the car. I much prefer on my bike to use the app over and above any other nav app because it's the only one that shows correctly the shaping points and via points I create in the planner. However, as you say, there are areas in the planner that could be enhanced, mainly your suggestion regarding "showing and managing multiple routes in a folder".
The way I like to plan a tour is to start with the complete round trip with all cities etc so I can ensure it is achievable in X days and mileage is within reason. Then I plan separately each day based on that and tweak it depending on bookable hotels etc. It would be great for me if I could split my big rough round trip into sections representing each day, but then when I plan those days in detail it gets fed back into the "master" big round trip. Hope that makes sense!!
-
@Drabslab said in The web planner needs some love & development?:
I think it is about time to stop tinkering with the navigation app and do a last big effort on solving the bugs (battery drain?) and then concentrate on the planning tool
I would be happy to respond to this. But I am well aware that a critical opinion on this forum (about Next, for example) is quickly punished and that would not promote the good atmosphere here.
Corjan has responded and I will wait and see.
It is striking and very positive that many upvotes were given by mostly users who are not very active here.@Jack-van-Tilburg said in The web planner needs some love & development?:
But I am well aware that a critical opinion on this forum (about Next, for example) is quickly punished and that would not promote the good atmosphere here.
I think this is not very true. I think opinions are mostly welcomed and used as input beyond what I have ever seen on any other public software forum. That does not mean though that everyone has to agree with everything
Especially your input, very generously given, is valued by me and many.
On topic and in general:
Yes I think we should not forget that the webplanner as it is, already is the best tool out there. Yes, a lot can be improved to make it even better. But of course it is best to finish the app first before drawing attention elsewhere. I agree that a feature freeze on the app would be good, because else it will never be finished. I think the deployment of the greatly overhauled CP/AA functionality will soon show how finished the app can be. Then developer attention will only be needed for bug fixing, and time will be available for the planner development.I can't wait for the exciting things to come!
-
@Drabslab said in The web planner needs some love & development?:
I think it is about time to stop tinkering with the navigation app and do a last big effort on solving the bugs (battery drain?) and then concentrate on the planning tool
I would be happy to respond to this. But I am well aware that a critical opinion on this forum (about Next, for example) is quickly punished and that would not promote the good atmosphere here.
Corjan has responded and I will wait and see.
It is striking and very positive that many upvotes were given by mostly users who are not very active here.That's not true @Jack, everyone is allowed to share their opinion here.
This is approximately the same as when the MyRoute app was launched in 2013/2014, when there were 1001 questions/ideas to adjust the planner, and a lot of things were realized. And as Corjan indicates, MRA is a small company with 4 programmer hands. There are plenty of ideas and plans and the company makes its choices, which I think we should respect.
Let's just keep an eye on the forum and when the time comes, there will be an announcement on the forum. -
@Peter-3b Personally I'm reasonably happy with the route planner at present. I would prefer that the Nav app gets fully sorted with regard to battery drain and car play for when I use the car. I much prefer on my bike to use the app over and above any other nav app because it's the only one that shows correctly the shaping points and via points I create in the planner. However, as you say, there are areas in the planner that could be enhanced, mainly your suggestion regarding "showing and managing multiple routes in a folder".
The way I like to plan a tour is to start with the complete round trip with all cities etc so I can ensure it is achievable in X days and mileage is within reason. Then I plan separately each day based on that and tweak it depending on bookable hotels etc. It would be great for me if I could split my big rough round trip into sections representing each day, but then when I plan those days in detail it gets fed back into the "master" big round trip. Hope that makes sense!!
@Stephen-Rowland I appreciated your comments on route planning. My process is very similar, starting with an overall route (7-10+days), identifying interesting roads and scenery. Then the hard work of breaking down individual day rides with reasonable timelines and a decent destination when the day is done. At the end, I often 're-build' the entire route by stringing together the daily routes for future planning purposes.
I agree with others that the Route Planner is the application that is most important to me. My Garmin loads the files I create in MRA, and I use it on the bike and in the car. I really don't use a phone or tablet for serious navigation. I realize that my situation may be different than the typical MRA customer. I live in a very large and diverse country, and my wife and I are both retired. So we enjoy long trips that require a lot of up-front planning.
But I'm content to wait for new feature development, The product continues to evolve. It was better than any of the alternatives that I tried back when I decided to become a lifetime member. I do look forward to more features in the Route Planner. I've suggested a few, and gotten positive responses from the team. You only get that level of interaction from a small, dedicated company. I feel lucky to be their customer!
-
@Jack-van-Tilburg said in The web planner needs some love & development?:
But I am well aware that a critical opinion on this forum (about Next, for example) is quickly punished and that would not promote the good atmosphere here.
I think this is not very true. I think opinions are mostly welcomed and used as input beyond what I have ever seen on any other public software forum. That does not mean though that everyone has to agree with everything
Especially your input, very generously given, is valued by me and many.
On topic and in general:
Yes I think we should not forget that the webplanner as it is, already is the best tool out there. Yes, a lot can be improved to make it even better. But of course it is best to finish the app first before drawing attention elsewhere. I agree that a feature freeze on the app would be good, because else it will never be finished. I think the deployment of the greatly overhauled CP/AA functionality will soon show how finished the app can be. Then developer attention will only be needed for bug fixing, and time will be available for the planner development.I can't wait for the exciting things to come!
Yes I think we should not forget that the webplanner as it is, already is the best tool out there.
Indeed!
MRA is a small company with 4 programmer hands.
pffff, they ony need to type faster
but let us please give them the time to analyse well. That eventually leads to better development and less bugs.
I agree that a feature freeze on the app would be good, because else it will never be finished.
I can only agree to this and I think that several people here notice a kind of feature creep leading to the typical never ending programming story.
Then developer attention will only be needed for bug fixing,
you are very optimistic here. I was once involved in "correcting a situation" and discovered that nothing was progressing because the developers spent 90% (not a typing mistake) on correcting bugs.
and time will be available for the planner development.
I see that slightly different.
I agree that planner and navigator are two distinct animals with their own purpose and scope, and overlap between the two should too a large extend be avoided.
However, it makes no sense to e.g. improve the planners POI handling, and not making sure immediately (in the same sprint or how is this called these days) that the navigator can exploit these new planning features.
Corjan has responded and I will wait and see.
Me too
-
When I think back to last spring when MyRoute-app exited beta and compare to today's product, what a huge improvement. I look forward to future versions but I wish we could fix some of the long outstanding issues. Ex. Battery usage, Navigation falling behind (possibly related) and general readability of the Here maps.
-
When I think back to last spring when MyRoute-app exited beta and compare to today's product, what a huge improvement. I look forward to future versions but I wish we could fix some of the long outstanding issues. Ex. Battery usage, Navigation falling behind (possibly related) and general readability of the Here maps.
@Doug-Robinson
Very true, and the outstanding issues are beyond the direct influence of MRA. That does not make it less annoying but we have to put responsibility where it belongs.
-
@Stephen-Rowland I appreciated your comments on route planning. My process is very similar, starting with an overall route (7-10+days), identifying interesting roads and scenery. Then the hard work of breaking down individual day rides with reasonable timelines and a decent destination when the day is done. At the end, I often 're-build' the entire route by stringing together the daily routes for future planning purposes.
I agree with others that the Route Planner is the application that is most important to me. My Garmin loads the files I create in MRA, and I use it on the bike and in the car. I really don't use a phone or tablet for serious navigation. I realize that my situation may be different than the typical MRA customer. I live in a very large and diverse country, and my wife and I are both retired. So we enjoy long trips that require a lot of up-front planning.
But I'm content to wait for new feature development, The product continues to evolve. It was better than any of the alternatives that I tried back when I decided to become a lifetime member. I do look forward to more features in the Route Planner. I've suggested a few, and gotten positive responses from the team. You only get that level of interaction from a small, dedicated company. I feel lucky to be their customer!
@Don-Stauffer I like and respect your reply. MRA was certainly the best Route Planner I tried before committing to a lifetime gold membership
-
Yes I think we should not forget that the webplanner as it is, already is the best tool out there.
Indeed!
MRA is a small company with 4 programmer hands.
pffff, they ony need to type faster
but let us please give them the time to analyse well. That eventually leads to better development and less bugs.
I agree that a feature freeze on the app would be good, because else it will never be finished.
I can only agree to this and I think that several people here notice a kind of feature creep leading to the typical never ending programming story.
Then developer attention will only be needed for bug fixing,
you are very optimistic here. I was once involved in "correcting a situation" and discovered that nothing was progressing because the developers spent 90% (not a typing mistake) on correcting bugs.
and time will be available for the planner development.
I see that slightly different.
I agree that planner and navigator are two distinct animals with their own purpose and scope, and overlap between the two should too a large extend be avoided.
However, it makes no sense to e.g. improve the planners POI handling, and not making sure immediately (in the same sprint or how is this called these days) that the navigator can exploit these new planning features.
Corjan has responded and I will wait and see.
Me too
@Drabslab said in The web planner needs some love & development?:
I was once involved in "correcting a situation" and discovered that nothing was progressing because the developers spent 90% (not a typing mistake) on correcting bugs.
You would think if 90% of capacity is spent on bugs, that that would lead to less bugs to spent capacity on...
-
Just to add my 2 pennies:
- the planner is what brought me here
- the nav app is what keeps me completely hooked
I need both.
But I don't need perfection from the planner. It works well enough for nearly all my uses. I've not found anything close to beating it. So that's a 9.5/10 stars from me.
I do need near-perfection from the nav app. It's what's happening live on the road, and it's not only disconcerting when it doesn't behave, but it can take the shine off a ride for a few minutes whilst you stop (with mates in tow, questioning your sanity) and work out what's happened. Right now it's a 8/10 stars for me, and thus needs the main focus for, say, another 2-3 months.
Considering the app has only been live for 9 months, and it's complexity and integration, it's bloody good.
We just need HERE to pull their finger out and fix the battery drain, plus some online/offline stability, and that will be an easy 9.5/10 for the app.
-
@Drabslab said in The web planner needs some love & development?:
I was once involved in "correcting a situation" and discovered that nothing was progressing because the developers spent 90% (not a typing mistake) on correcting bugs.
You would think if 90% of capacity is spent on bugs, that that would lead to less bugs to spent capacity on...
@Con-Hennekens indeed, but they managed to create a new bug for more or less every bug they solved (consequence of totally wrong internal organization, lack of testing ...) so they kept busy chasing their own tail, leading to some drastic management interference, and me be awarded the very "interesting" job of keeping the angry customers at bay and solving the issues.
-
@Con-Hennekens indeed, but they managed to create a new bug for more or less every bug they solved (consequence of totally wrong internal organization, lack of testing ...) so they kept busy chasing their own tail, leading to some drastic management interference, and me be awarded the very "interesting" job of keeping the angry customers at bay and solving the issues.
@Drabslab, That's a thankful job... I hope you give the MRA team a bit more credit
-
@Richard-18 Maybe 500 would be reasonable? The underlying theme is multi-day trips. To plan those I often make a separate overview route covering the entire trip, just to get a feel for distances and time, etc -- and this is where I would run up to the 200 limit. The choice to recalculate the entire route on every click gets very tedious too, though, in this scenario, see below.
The current web planner is excellent for planning (a) single day routes, (b) on asphalt. You can of course put a bunch of day-trips in a folder and if you don't mind the work (add route -> add route -> add route...) show them at the same time, but that's about as far as MRA goes in supporting multi-day trips.
My ideal for a successor would be a planner that would support multiple segments that can be linked into a trip. With an overview of the entire trip (with insight into distances and times per segment), and with the possibility to drill down and edit into the individual segments. And flexible export and import options, eg, map to individual GPX files, to GPX tracks or GPX segments.
While we're at it: maybe allow mixing in offroad segments, so I can find a home for my TET and ACT tracks and bind them into my trips.
Side note: currently every route gets fully recomputed whenever you open it or edit it. I think the scalability of MRA would be much improved if they would cache route computations (routes are viewed much more often than edited) and don't open an entire trip in edit mode. In terms of resources, it would become much "cheaper" to work with multiple segments and >5.000 km trips. (And to show an entire folder of routes on the map, so I can see "where I and others have been".)
Well apologies for a lot of text in response to your simple question. Hope this helps.
Cheers, -PeterHi @Peter-3b
I do agree with a lot of what you are saying,
I also find the 200 waypoint limit very frustrating when trying to plan multi-day trips.Often I plan/ride 500 mile (800km) routes on small non-motorway roads & will have 150+ waypoints for a day, so for a multi-day trip of 10-16 days I can be looking at a trip with several thousand points.
For those that say only 50 points are sufficient for 1 day, that is your choice/preference, some of us prefer a lot more points as we plan far more detailed routes.
IMO there should be no limit on the number of points unless there is a very sound technical reason to impose such a limit, like when importing tracks with 10's or 100's of thousands of points.You can of course put a bunch of day-trips in a folder and if you don't mind the work (add route -> add route -> add route...)
I agree the "> add route > add route" is painful especially as this action is not cached / saved & if you exit the route you have to go back & "> add route > add route" all over again.
I get round this by having multiple browser tabs open for MRA but this sometimes leads to instabilities in the browser/mra site.show them at the same time, but that's about as far as MRA goes in supporting multi-day trips.
MRA does allow for prepend / appending the shown routes using the + symbol in the Routes tab after a route has been added.
Unfortunately with detailed routes you soon hit the 200 point limit when you append multiple days. Trying to get an overview of your whole trip & its total mileage is not possible when MRA then randomly removes points.
And yes I want to know the total mileage of a trip as tyre ware & maintenance stops should be planned ( & yes again a new tyre is fitted before a trip)I understand MRA is a small team & only so much can be done & only so fast, the above is just some pain points I experience with the planner & which I work around.
For planning group trips with multiple riders all using different navigation systems, TomTom, Garmin, MRA, Calimoto...... there is no other app/planner that comes close to being able to successfully create & transfer a route to each of the group & for them then to be able to navigate the days ride. -
I am a bit surprised at the number of required route points mentioned here.
I am going to the North Cape this summer and have now planned a route to the north and one to the south. Together more than 6000 kilometers. But no more than 110 waypoints. And that includes shaping points and points along the way for sightseeing and/or overnight stays.
And yes.....I also have day trips in Europe that mainly take very small roads where extra waypoints are needed to carry out the chosen route exactly as I wish. But even there I never reach the number of 100 route points. -
Hi @Peter-3b
I do agree with a lot of what you are saying,
I also find the 200 waypoint limit very frustrating when trying to plan multi-day trips.Often I plan/ride 500 mile (800km) routes on small non-motorway roads & will have 150+ waypoints for a day, so for a multi-day trip of 10-16 days I can be looking at a trip with several thousand points.
For those that say only 50 points are sufficient for 1 day, that is your choice/preference, some of us prefer a lot more points as we plan far more detailed routes.
IMO there should be no limit on the number of points unless there is a very sound technical reason to impose such a limit, like when importing tracks with 10's or 100's of thousands of points.You can of course put a bunch of day-trips in a folder and if you don't mind the work (add route -> add route -> add route...)
I agree the "> add route > add route" is painful especially as this action is not cached / saved & if you exit the route you have to go back & "> add route > add route" all over again.
I get round this by having multiple browser tabs open for MRA but this sometimes leads to instabilities in the browser/mra site.show them at the same time, but that's about as far as MRA goes in supporting multi-day trips.
MRA does allow for prepend / appending the shown routes using the + symbol in the Routes tab after a route has been added.
Unfortunately with detailed routes you soon hit the 200 point limit when you append multiple days. Trying to get an overview of your whole trip & its total mileage is not possible when MRA then randomly removes points.
And yes I want to know the total mileage of a trip as tyre ware & maintenance stops should be planned ( & yes again a new tyre is fitted before a trip)I understand MRA is a small team & only so much can be done & only so fast, the above is just some pain points I experience with the planner & which I work around.
For planning group trips with multiple riders all using different navigation systems, TomTom, Garmin, MRA, Calimoto...... there is no other app/planner that comes close to being able to successfully create & transfer a route to each of the group & for them then to be able to navigate the days ride.@Brian-McG, I can only imagine that such an exorbitant number of waypoints would lead to an incredibly slow route calculation. I think the problem is in the method, not in the tools.
-
I am a bit surprised at the number of required route points mentioned here.
I am going to the North Cape this summer and have now planned a route to the north and one to the south. Together more than 6000 kilometers. But no more than 110 waypoints. And that includes shaping points and points along the way for sightseeing and/or overnight stays.
And yes.....I also have day trips in Europe that mainly take very small roads where extra waypoints are needed to carry out the chosen route exactly as I wish. But even there I never reach the number of 100 route points.I suppose you mean 100 routepoints per day? otherwise you have a point every 60 km, and that can hardly be seen as a route?
-
@Drabslab said in The web planner needs some love & development?:
... otherwise you have a point every 60 km, and that can hardly be seen as a route?
A route only needs 2 points.
But I can understand why people add superfluous points to a route - it's a distrust of the routing engine to follow the exact same route when actually on the journey.
In my case that distrust originally came from automatic re-routing due to:
- closed roads, and
- traffic
Now that I understand that aspect of the app / routing engine, my routes have a lot less points - 17 over 280 miles for a medium complexity route (start, end, two places to visit on the way, petrol, food, and certain roads I wanted to go down)
You have the option to disable that auto re-routing of course, if you don't like it, or don't trust it.
-
I suppose you mean 100 routepoints per day? otherwise you have a point every 60 km, and that can hardly be seen as a route?
@Drabslab said in The web planner needs some love & development?:
I suppose you mean 100 routepoints per day
In the sense of my day routes in Europe I indeed mean 100 waypoints.
But I very rarely (or never) reach that number. -
@Drabslab said in The web planner needs some love & development?:
... otherwise you have a point every 60 km, and that can hardly be seen as a route?
A route only needs 2 points.
But I can understand why people add superfluous points to a route - it's a distrust of the routing engine to follow the exact same route when actually on the journey.
In my case that distrust originally came from automatic re-routing due to:
- closed roads, and
- traffic
Now that I understand that aspect of the app / routing engine, my routes have a lot less points - 17 over 280 miles for a medium complexity route (start, end, two places to visit on the way, petrol, food, and certain roads I wanted to go down)
You have the option to disable that auto re-routing of course, if you don't like it, or don't trust it.
@richtea999 said in The web planner needs some love & development?:
Now that I understand that aspect of the app / routing engine, my routes have a lot less points
I am not using the app but my old trusted Rider400. The app cooks my phone and I hope that the rider keeps functioning until the battery drain is resolved.
and I rarely follow the route calculated by the planner.
I start with a begin and endpoint, a few POI underway that i want to visit, and then I start tinkering putting waypoints left and right to force the route over a green michelin road, or to avoid the centre of a village...
-
@Drabslab said in The web planner needs some love & development?:
I suppose you mean 100 routepoints per day
In the sense of my day routes in Europe I indeed mean 100 waypoints.
But I very rarely (or never) reach that number.@Jack-van-Tilburg said in The web planner needs some love & development?:
I indeed mean 100 waypoints. But I very rarely (or never) reach that number.
same for me













