The Great Suggestion List
Our users generate most of the feature ideas that drive MyRoute-app forwards. In this specific thread, we'll summarize suggestions put forward on the forum. A suggestion might have multiple interpretations, as such, all relevant interpretations will be linked here. Participants are encouraged to discuss suggestions within their respective threads. This thread should be used only for the discussion of the list itself, its' structure and possibly its' level of accuracy.
Last updated on the 11th of march, 2020.
- Show routes in map view of the library (ErikB)
- Sorting and filtering on events (MTC-TET Club)
- Remove unaccepted passed events automatically (MTC-TET Club)
- Change download directory (max auger)
- Adding multiple routes at once in the view of one route (Alan bowen)(Lisi Mayr)
- Add waypoint with GPS coordinates (Frenator)
- More advanced event editor (Guzzist)
- Show and possibly edit times for each waypoint (Royzee)(Tim Goodman)
- Add geo-tagged images to routes and tracks (ErikB)
- Blog feature for events and groups with privacy settings (MTC-TET Club)
- POI Name and icon editing (Guzzist)
- Show height profile of a route (Lisi Mayr)
- Flowchart route with decision waypoints (Dan Howell)
- Search routes based on destination (Con Hennekens)
- Collaborative route editing (Dan Howell)
- Download entire route library
- User profile and MRA profile integrated as one
- Live route calculation while dragging waypoints (Christian Schrenk)
- Rework POI's and Favorites to share behaviors (Drabslab)
- Save as Co-pilot .trp format (Mark Davies)
- Control where a waypoint is inserted on the route (Jeffrey Kogler)
- POI visibility on higher altitudes (Ron Cook)
- E-mail notifications on events (Guzzist)
- Save as editable text document (Brian Liechty)
- View speed limits (Will Brooks)
- change color of routeline (Will Brooks)
Guzzist last edited by
...really really perfect! That's what I mentioned.
Thank you verry much
@Guzzist Thank you. You're welcome
In the nearby future I'll start communicating about the progress of these features, which ones will be selected for development and which won't. We're also positively brainstorming with the team about ways to involve the community in selecting features in an appropriate manner.
MTC-TET Club last edited by
Greets ErikB & MTC-TET
Idon't know whether the following qualifies as "discussion of the list itself, its' structure and possibly its' level of accuracy" as I am basically adding to the list but I have the following additional requests:
A download option for all our routes in one go, respecting the folder structure, as backup
Integration of our MRA account and profile, and the forum account and profile with options to decide what we want to make public and what not
Adding your suggestions to the list.
Edit: additionally I believe @Guzzist made a similar suggestion regarding downloading all his routes.
Drabslab last edited by Drabslab
My suggestions have been allowed. Snif, this is a very emotional moment, snif
If I am allowed an extra comment/ suggestion (a big one) then in general I would to see a better integration of all services.
For instance, to be able to store all favorites only applicable to a x days trip in the routefolder of that trip, to connect a blog post with a specific trip, to integrate blogs with the forum etc...
Most certainly, I miss a few of the original (or current) intentions of having all these different features, and there may be very good reasons not to do all this (not in the least because it is a heap of work), but I can't help but mentioning it.
The risk of all these feature requests,although probably all improving things, is that when implementd on a case by case absis it may lead to "spaghetti" code and a totally incoherent site.
So probably, MRA should take a step back, ask for all suggestions related to a specific subject, and implement in an organised way.
I think discussing the order of implementation and suggestions as to do it are fine here, don't worry about making a new thread
What you're talking about is something we're already doing behind the scenes, called Web 2.0. Web 2.0. is a future feature update that aims to connect all features within a new (though recognizable and highly familiar) shell. Once MRA Video is out of the way the first few major content updates will definitely be tailored towards the core of MRA: creating, finding and sharing routes.
I don't know what to expect from MRA video, but this kind of IT related specification/interface/feature development stuff really gets me going
Will Brooks last edited by
Can I add a couple of other suggestions which I've previously raised on the "old" topics/forums
Add speed limit data for roads. This is already available and open source from OpenStreetMap data
Being able to change the colour and transparency of the route line (solid black isn't always the most helpful!)
@Will-Brooks Hi Will, you may definitely suggest those! However, please do so in seperate threads as that will allow discussion on those subjects to happen in a structured manner. If someone else raises a similar suggestion, I'll then forward them that specific thread. This is to avoid having a conversation about detail here in the comments on the suggestion list.
Guzzist last edited by
@Timo-Martosatiman-MRA please can you add this to "great suggestion list" :
At MRA Navigation App, especialy the only one used map is really a pain!
It is possible in MRA to create routes for driving, cycling, or by foot. And for this purpose you can use maps which fits best for: OpenCyleMap or OpenTopoMap (both as Gold Member). With this, you can use small paths or gravel roads to do route planning.
But then, if you will use the route in MRA Navigation App, the App is only using HERE Map and will not show your route if ther is no big street! Ok, directing the driver by message is one thing - but simply showing current position on map and route is the other thing. Because this is essentially, it mußt be developed soon! Otherwise App is senseless for cyclists and pedestrians.
May do it for Gold Memers only - but do it.
Ruediger Hoffner last edited by
Hi, suggestions are made and i probalby inserted more suggestions which from my point of view make sense. However when looking at the releases for MyRouteApp-Navigation, the last release with new features was on October/19.
These are 6 months without any new functionality and no announcements only a suggestion list.
To get a better communication between the development team and the users it would be good to have more information about what is planned for the next release.
It would also be a good thing even for you to start a Beta program for your App where we can participate and give you immediately feedback. I know this is possible to with Android-Apps on Google Play.
What do you think MRA-Team?
I am not part of the MRA team but to give them credit: it is not correct that there have been no announcements.
In fact, the big announcement was called MRA Video which was scheduled for release end last year (a bit too optimistic as it seems ) but is "upcoming.
Next to that some refactoring has been urgently done to go round some Google price hike, and there has been a substantial amount of bug fixing as well.
In addition, they invented recently the great suggestion list that several forum members have contributed to, and for which the voting (and decision) wil be finalized/has finalized? very soon. Involving users in a decision making process takes time, you need to collect the idea's, make a first list, have a first voting round to downsize that huge list, then a final vote to determine the next iteration of the software...
We just have to wait a few more days/weeks for the outcome of that final voting and have the first roadmap.
In any case: if you open a new post with title: "great suggestion list: topic title" and then some content explaining what you mean then you will undoubtedly get soem reaction from other users, and make it easy for MRA to find all suggestions.
Steve Lynch last edited by
I would like to add a suggestion to impliment the "Offroad" functionality in MRA into the Navigation App
Using the "Offroad" functionality in MRA, it simply draws a straight line between the waypoints rather than plotting the route via actual roads.
This would allow actual plotting of the UK's Ordanance Survey "Green Lanes" or Byways Open to All Traffic which very often unclearly or incorrectly marked on the actual trail.
For other countries where there are vast open spaces that can be legally ridden anywhere this would be great for those users as they could share there gnarliest (or not) trails with others.
speedup100 last edited by
Unlike the original Tyre a favorite cannot be left permanently showing on the general map template, presumably because each map generated in MRA is a stand alone item. A favorite can only be added as a waypoint, it would be a good feature if a favorite could be added permanently as is the case with POI's. To me there is a difference between a favorite and a POI, a favorite can be someone's address personal to you, a POI is more of a general interest. The difference in the visual image of the icons is the important significance.
Peter 3b last edited by
Suggestion: add a "export as link to GPX".
Rationale: exporting through USB is so very 2005, but all currently available alternatives require the use of intermediate storage.
Current "export as a link" links to the interactive MRA webapp. While I understand the viral value this has for MRA (as a company), as a user I would like to be able to drop a link directly into other apps.
This is what URLs were invented for, right?
BJ last edited by BJ
Suggestion: change the route-type of an existing or imported route.
When you start making a new route you have to choose what type this route is (Driving, Cycling, By foot). I use MRA for preparing running-routes as well and when you (accidentally) select a different type it is not possible to modify this later on.
This also goes when using imported Route-tracks: when choosing to use the track as a route you don't have the possibility to select what type of route it is.
You can change this afterwards in the route-information
or via the 3 dots behind the route in your route library