Suggestions
-
Plaats random 'suggesties' in losse topics, zo kunnen we ze taggen en later nog eens bekijken. Ook houden we zo de discussies 'on topic' per suggestie! hou er rekening mee dat we tot 1 juni 2023 een strakke planning hebben. Maar daarna is er weer van alles mogelijk, dus hou je vooral niet in!
Place random 'suggestions' in seperate topics, that way we can tag them and keep them marked for later use. That way, every suggestion has it's own 'on topic' discussion! keep in mind that we have a tight schedule until June 1, 2023. But after that, anything is possible again, so don't hold back!EDIT 05/09 by Timo:
Locked topic and edited rules so that suggestions are posted in seperate topics.“People don’t take trips, trips take people.” – John Steinbeck
-
Plaats random 'suggesties' in losse topics, zo kunnen we ze taggen en later nog eens bekijken. Ook houden we zo de discussies 'on topic' per suggestie! hou er rekening mee dat we tot 1 juni 2023 een strakke planning hebben. Maar daarna is er weer van alles mogelijk, dus hou je vooral niet in! Place random 'suggestions' in seperate topics, that way we can tag them and keep them marked for later use. That way, every suggestion has it's own 'on topic' discussion! keep in mind that we have a tight schedule until June 1, 2023. But after that, anything is possible again, so don't hold back!
EDIT 05/09 by Timo:
Locked topic and edited rules so that suggestions are posted in seperate topics.@Michel-van-Hagen-MRA-Founder
Top, gaan we doen -
Plaats random 'suggesties' in losse topics, zo kunnen we ze taggen en later nog eens bekijken. Ook houden we zo de discussies 'on topic' per suggestie! hou er rekening mee dat we tot 1 juni 2023 een strakke planning hebben. Maar daarna is er weer van alles mogelijk, dus hou je vooral niet in! Place random 'suggestions' in seperate topics, that way we can tag them and keep them marked for later use. That way, every suggestion has it's own 'on topic' discussion! keep in mind that we have a tight schedule until June 1, 2023. But after that, anything is possible again, so don't hold back!
EDIT 05/09 by Timo:
Locked topic and edited rules so that suggestions are posted in seperate topics.@Michel-van-Hagen-MRA-Founder Niet zozeer random: maar ik zou in de eerste versie van februari toch al wel verwachten dat de nieuwe nav functie ook goed omgaat met "offroad" routepunten. De huidige app kan dat niet en dat is toch echt praktisch zeker wel een gemis. Hier komen op het forum zeer veel berichten van binnen.
Manks bu'j te bange.
-
Plaats random 'suggesties' in losse topics, zo kunnen we ze taggen en later nog eens bekijken. Ook houden we zo de discussies 'on topic' per suggestie! hou er rekening mee dat we tot 1 juni 2023 een strakke planning hebben. Maar daarna is er weer van alles mogelijk, dus hou je vooral niet in! Place random 'suggestions' in seperate topics, that way we can tag them and keep them marked for later use. That way, every suggestion has it's own 'on topic' discussion! keep in mind that we have a tight schedule until June 1, 2023. But after that, anything is possible again, so don't hold back!
EDIT 05/09 by Timo:
Locked topic and edited rules so that suggestions are posted in seperate topics.Please ensure that the scaling when approaching Roundabouts shows the full roundabout that allows the user to see every exit regardless of how big or small the roundabout is.
I look forward to seeing how this develops and based on my experience with MyRoute-App Mobile, which is awesome by the way, I am confident that the MRA Devs are going to give us something very special indeed.
-
Zoals in mijn introductie post gemeld zou het mooi zijn als de app rekening kan houden met he5 soort voertuig en dan met name de lengte, hoogte en het gewicht ervan. (Camper, caravan oid)
-
In complement to route options like curvy, extra curvy etc can we include an option to minimize routing through villages, towns and industrial estates?
-
One of the things that annoyed me during the navigation is the name of the street/road I am riding on (displayed on the blue background at the right top of the screen.) Sometimes the name of the road is like a chapter of the book, and all of it is displayed covering almost a1/3 of the screen.
Maybe you can abbreviate the name of the roads in the future release. Couple of lines will do, with the ellipsis at the end. If someone wants to see the whole thing, the click on the name will open the whole description for few seconds.Another thing is skipping formation/via points. It is not very intuitive; it takes some pussyfooting to get it to work.
Now I know I am pushing it. I would love to hear the voice announcement of the via/formation point I am approaching, if the description is entered during route design. There might be a checkmark or something enabling this functionality. It would be great to hear: "Calabash Seafood Hut ahead..."
Last thing (for now,) the gas pump icon at the top left of the screen. Currently, the distance displayed under the icon is unreliable at best. It would be nice if one could click on the icon, and the list of the nearest gas station would be displayed with a direction arrow and approximate distance to it.
-
The old navigation app was a bit fiddly in the landscape orientation. Would love to see better support for it in this version.
-
Would love to have a big button on the screen to skip only one waypoint. Current skip feature asks the number of waypoints to skip, which is quite difficult to use with gloves on. Also that UI doesn’t work when the screen orientation is landscape.
Great if it gave some kind of visual (and/or voice) feedback about the next waypoint after skipping.
-
Plaats random 'suggesties' in losse topics, zo kunnen we ze taggen en later nog eens bekijken. Ook houden we zo de discussies 'on topic' per suggestie! hou er rekening mee dat we tot 1 juni 2023 een strakke planning hebben. Maar daarna is er weer van alles mogelijk, dus hou je vooral niet in! Place random 'suggestions' in seperate topics, that way we can tag them and keep them marked for later use. That way, every suggestion has it's own 'on topic' discussion! keep in mind that we have a tight schedule until June 1, 2023. But after that, anything is possible again, so don't hold back!
EDIT 05/09 by Timo:
Locked topic and edited rules so that suggestions are posted in seperate topics.@Michel-van-Hagen-MRA-Founder weet wat je zegt met "hou je niet in"
...Als ik gebruikmaak van Waze en er is voor mij ergens op de route een incident, dan zorgt Waze er voor dat ik er probleemloos omheen kan navigeren in de kortst mogelijke tijd. Ik hoef dat niet zelf aan te geven. Waze heeft natuurlijk een vreselijk groot marktaandeel in de categorie van-deur-tot-deur navigatie. En als Waze-gebruiker deel je je locatie. Als er voor je op jouw route 100 Waze-gebruikers stilstaan (b.v. op de autosnelweg), dan kan het haast niet anders dan dat er iets moet zijn gebeurd waardoor het verkeer niet verder kan.
Waze leidt mij er dan keurig omheen (mits er uiteraard uitwijkroutes mogelijk zijn).Dit integreren is een megaklus, maar ik mocht mij niet inhouden
-
I've made suggestions about hiding shaping points in the General Discussion forum...
My comments there...
@Tim-Thompson said in Hide shaping points:
It might be nice to be able to turn/off or filter the shaping points from view - especially in MRA Navigation. If you have to import a route (via GPX or otherwise), you might have to have a fair number of shaping points to faithfully recreate the desired route. However, once the shaping points have done their job, one doesn't necessarily need to see them - especially when navigating.
@Tim-Thompson said in Hide shaping points:
I'm aware that waypoints can be colored. However, that's not what I'm after. I would like to be able to make the shaping points disappear. In most cases I don't need to see them while navigating. I would rather not see distance to next shaping point (this can be annoying - especially when you have to have many shaping points whose only purpose is to get the app to faithfully plot the intended route). Instead I would like to only see distance to the next turn or stop. Either make all shaping points visible/invisible as a whole, or maybe - like being able to set their colors - be able to set the visibility of waypoints individually.
I think it would also be helpful the be able to hide the shaping points in the route editors - so that the route display can be decluttered and the important things can better be brought into focus.
-
Plaats random 'suggesties' in losse topics, zo kunnen we ze taggen en later nog eens bekijken. Ook houden we zo de discussies 'on topic' per suggestie! hou er rekening mee dat we tot 1 juni 2023 een strakke planning hebben. Maar daarna is er weer van alles mogelijk, dus hou je vooral niet in! Place random 'suggestions' in seperate topics, that way we can tag them and keep them marked for later use. That way, every suggestion has it's own 'on topic' discussion! keep in mind that we have a tight schedule until June 1, 2023. But after that, anything is possible again, so don't hold back!
EDIT 05/09 by Timo:
Locked topic and edited rules so that suggestions are posted in seperate topics.@Michel-van-Hagen-MRA-Founder
You may wish to consider the use-ability of this app by a rider base of over 75000 members worldwide - the Iron Butt Association. There appears to be a great opportunity at this stage to reach out to that organisation regarding what may support their riders completing their rides and rallies. -
@Michel-van-Hagen-MRA-Founder
You may wish to consider the use-ability of this app by a rider base of over 75000 members worldwide - the Iron Butt Association. There appears to be a great opportunity at this stage to reach out to that organisation regarding what may support their riders completing their rides and rallies.@TJ189 As an organiser of a long distance rally and a member of the Iron Butt Association, I agree. I have used a variety of different GPS solutions and none quite fit the purpose. It would be fantastic to have an app that was responsive to the needs that we have.
-
It would be really useful to see others in your touring group as dots on the navigation screen so you can see if someone is falling behind or maybe went down.
-
I surely hope that my 2 main frustrations will be addressed:
-
Selecting the waypoint to skip to is an inhumanitary task. Make the waypoint selectable from the screen instead of having to next, next, next, next, next, next, next, next, next, next, next, next, next, next, next, until WP 88 or so...
-
The option "start from nearest waypoint" does not stick. after loading a route, or restarting the app it defaults back to "start from beginning". This should be a systemwide option that sticks to what you tell it to do.
-
-
Plaats random 'suggesties' in losse topics, zo kunnen we ze taggen en later nog eens bekijken. Ook houden we zo de discussies 'on topic' per suggestie! hou er rekening mee dat we tot 1 juni 2023 een strakke planning hebben. Maar daarna is er weer van alles mogelijk, dus hou je vooral niet in! Place random 'suggestions' in seperate topics, that way we can tag them and keep them marked for later use. That way, every suggestion has it's own 'on topic' discussion! keep in mind that we have a tight schedule until June 1, 2023. But after that, anything is possible again, so don't hold back!
EDIT 05/09 by Timo:
Locked topic and edited rules so that suggestions are posted in seperate topics.@Michel-van-Hagen-MRA-Founder
There are already some good suggestions and ideas listed here.
Here is my contribution:
Focus the development on motorbike navigation for the time being. The programmers will certainly take into account the needs of all the different methods of transport in the internal structures.
Leave many settings to the user. I am thinking here of something like a "Config page" with True/False switches. Possibly with a basic and expert mode.One detail: in addition to the texts that a via/shaping point can contain, optionally send an acoustic signal - with N kilometres (or minutes) advance. Of course, a separate WAV file would also be possible...
Otherwise, I am looking forward to the further development of the NAV software. The new mobile app gives rise to great hopes.
Peter
-
De enige manier (die ik op dit moment zie) waarop Next voor mijn gebruiksscenario's bruikbaar gaat zijn, is als de navigatie primair op basis van de in MRA Routeplanner (of andere software) uitgerekende route (gerepresenteerd in GPX als de track) plaats gaat vinden, zonder dat de app zelf gaat rekenen aan hoe de route moet gaan lopen.
Als er van die route afgeweken wordt, zou het standaardgedrag m.i. moeten zijn om via de snelste weg terug te worden gestuurd naar de route (dit is dus dynamisch o.b.v. hoe ver je van de route afwijkt). Aangezien de route niet is berekend o.b.v. routepunten in deze situatie, is het overslaan van routepunten hierbij niet relevant.
Routepunten (met name via-punten) zijn interessant voor stops e.d. dus zichtbaarheid/hoorbaarheid hiervan is belangrijk, ook als ze niet primair voor navigatie gebruikt worden. Hoe meer mogelijkheden er zijn om die zichtbaarheid/hoorbaarheid in te kunnen stellen (dus evt. ook uit te kunnen schakelen), hoe beter in mijn optiek.
M.b.t. het halverwege starten van een route: het zou mooi zijn als je bij het openen van de route c.q. het starten van de navigatie, gevraagd wordt of je naar het startpunt, of naar het dichtstbijzijnde punt wilt rijden. Naar het dichtstbijzijnde punt is uiteraard gelijk als van de route afwijken en kan dus op dezelfde manier afgehandeld worden (via de snelste weg naar de dichtstbijzijnde plek op de route).
Daarnaast zou het mooi zijn om op elk gewenst moment via de snelste weg naar een te kiezen routepunt te kunnen rijden, waarbij de geplande route dus wordt genegeerd.
English:
The only way I can currently see Next being suitable for my use cases, is when navigation is primarily based on the route as it has been calculated by MRA Routeplanner (or other software) (currently represented in GPX as the track), without the app recalculating what the route should be.When deviations from this route occur, the standard behaviour should be to direct the user back to the route by the fastest route (this should be dynamically calculated on the fly). As the route is not primarily based on waypoints, skipping them becomes irrelevant in this scenario.
Waypoints (in particular via points) are still very relevant even when they are not used as the primary means of navigation, as they denote stops or other important points on the route, so they should be visible/audible during navigation. The more options users have to fine-tune the visibility/audibility of waypoints (to the point of turning them off completely), the better, in my opinion.
With regards to starting halfway along the route, it would be nice if the app would ask the user whether they want to start at the beginning of route or at the nearest location on the route. This should then be handled in the same way as a deviation from the route, i.e. direct the user to the nearest location on the route in the fastest way.
It would also be very nice to be able to drive to any route point in the fastest way at any time the user desires, ignoring the planned route.
-
De enige manier (die ik op dit moment zie) waarop Next voor mijn gebruiksscenario's bruikbaar gaat zijn, is als de navigatie primair op basis van de in MRA Routeplanner (of andere software) uitgerekende route (gerepresenteerd in GPX als de track) plaats gaat vinden, zonder dat de app zelf gaat rekenen aan hoe de route moet gaan lopen.
Als er van die route afgeweken wordt, zou het standaardgedrag m.i. moeten zijn om via de snelste weg terug te worden gestuurd naar de route (dit is dus dynamisch o.b.v. hoe ver je van de route afwijkt). Aangezien de route niet is berekend o.b.v. routepunten in deze situatie, is het overslaan van routepunten hierbij niet relevant.
Routepunten (met name via-punten) zijn interessant voor stops e.d. dus zichtbaarheid/hoorbaarheid hiervan is belangrijk, ook als ze niet primair voor navigatie gebruikt worden. Hoe meer mogelijkheden er zijn om die zichtbaarheid/hoorbaarheid in te kunnen stellen (dus evt. ook uit te kunnen schakelen), hoe beter in mijn optiek.
M.b.t. het halverwege starten van een route: het zou mooi zijn als je bij het openen van de route c.q. het starten van de navigatie, gevraagd wordt of je naar het startpunt, of naar het dichtstbijzijnde punt wilt rijden. Naar het dichtstbijzijnde punt is uiteraard gelijk als van de route afwijken en kan dus op dezelfde manier afgehandeld worden (via de snelste weg naar de dichtstbijzijnde plek op de route).
Daarnaast zou het mooi zijn om op elk gewenst moment via de snelste weg naar een te kiezen routepunt te kunnen rijden, waarbij de geplande route dus wordt genegeerd.
English:
The only way I can currently see Next being suitable for my use cases, is when navigation is primarily based on the route as it has been calculated by MRA Routeplanner (or other software) (currently represented in GPX as the track), without the app recalculating what the route should be.When deviations from this route occur, the standard behaviour should be to direct the user back to the route by the fastest route (this should be dynamically calculated on the fly). As the route is not primarily based on waypoints, skipping them becomes irrelevant in this scenario.
Waypoints (in particular via points) are still very relevant even when they are not used as the primary means of navigation, as they denote stops or other important points on the route, so they should be visible/audible during navigation. The more options users have to fine-tune the visibility/audibility of waypoints (to the point of turning them off completely), the better, in my opinion.
With regards to starting halfway along the route, it would be nice if the app would ask the user whether they want to start at the beginning of route or at the nearest location on the route. This should then be handled in the same way as a deviation from the route, i.e. direct the user to the nearest location on the route in the fastest way.
It would also be very nice to be able to drive to any route point in the fastest way at any time the user desires, ignoring the planned route.
@Herko-ter-Horst Eigenlijk dus navigeren op basis van een track i.p.v. routepunten die je naar de app stuurt... toch? Pas dan weet je dat er geen extra berekeningen plaatsvinden. Gewoon de lijn volgen maar dan wel turn-by-turn.
-
If you want to know how Navigation or Next can be improved, I might suggest you look at the competition. Right now, when it comes to identifying actual worthy competition, I might suggest looking at Scenic. Do a head to head comparison identifying the strengths and weaknesses of each. When done, maybe areas where MRA Navigation/Next can be improved will be illuminated.
One area that MRA Navigation scores a point is that it's available on both iOS and Android. However, if the Scenic website holds true, that advantage won't be long lived. They are supposed to be delivering an Android version of Scenic soon.
-
If you want to know how Navigation or Next can be improved, I might suggest you look at the competition. Right now, when it comes to identifying actual worthy competition, I might suggest looking at Scenic. Do a head to head comparison identifying the strengths and weaknesses of each. When done, maybe areas where MRA Navigation/Next can be improved will be illuminated.
One area that MRA Navigation scores a point is that it's available on both iOS and Android. However, if the Scenic website holds true, that advantage won't be long lived. They are supposed to be delivering an Android version of Scenic soon.
-In- en uitschakelbare functie voor automatisch herberekenen van de route.
-Mogelijkheid om bij een obstakel in de route een alternatieve routedeel te berekenen. Liefst met een keuze ten aanzien van de lengte van het alteratief.-Switchable automatic route recalculation function.
-Possibility to calculate an alternative route section in the event of an obstacle in the route. Preferably with a choice regarding the length of the alternative.
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
