Feature request for MRA Navigation app: report a (temporary) road block

[FrankS]

Hi everyone,

I have this feature request for the MRA Navigation app:

From time to time it happens that you get to
a) a road forbidden for cars and/or motorcycles
b) a new road block, e.g. because of road construction work
that HERE does not know as such.

In such events it would be very hepful, if I could report this new forbidden road (and specify the vehicle type) or temporary road block (and the end date of a temporary block), so that HERE and the community get informed about this information.

Looking forward to comments from the MRA development team!

Thanks
Frank

[Nick Carthew]

@FrankS You can report map errors here: https://mapfeedback.here.com/#/report

[Corjan Meijerink]

@FrankS great idea! Would enjoy something like this myself but it’s a massive feature.

Considering the development time, it would not make sense to add such a feature at this point. If all critical stuff is done and our user base has grown massively, this would make a lot of sense to add!

[richtea999]

It would be a brilliant crowd-sourced data feed for HERE (rather than MRA), so maybe you could just funnel the feedback straight through to them, and they can decide how to handle the information.

After all, it's in their interest to provide improved information to all their users, not just MRA users.

It's a win-win if they just step up.

[Teresa Wood]

@FrankS I NEED this detour function. Since I retired my Garmin (which had a detour function) and now run MRA through my Samsung android mounted on my solid as a rock SP Connect handle bar mount, I find the frequent road closures on my painstakingly planned routes hugely irritating, especially as whoever puts up the diversion signs in the UK must only have a limited number of signs at their disposal, because they frequently disappear before you are back on track. Taking waypoints out with a gloved hand on a phone, is really tricky. Its making me consider going back to a dedicated motorcycle sat nav, or forgoing my gold mra membership and finding another navigation and route planning app.

[richtea999]

@Teresa-Wood said in Feature request for MRA Navigation app: report a (temporary) road block:

Taking waypoints out with a gloved hand on a phone, is really tricky. Its making me consider going back to a dedicated motorcycle sat nav...

BarButtons or touch-sensitive gloves are cheaper, I promise. A long press on either and bingo.

Just in case you haven't enabled it, there is a 'traffic-aware' option in Navigation settings -> Functional which, assuming you have internet connectivity whilst riding, should re-route you around such problems. That's in the hands of live HERE data, not MRA themselves.

Lastly, MRA is improving month by month. It's early days yet. The first public release was only in June this year.

[Teresa Wood]

@richtea999 thanks, I've just checked and traffic aware is on. I have touch sensitive gloves. What are bar buttons? I had real trouble navigating with mra on a 2 week trip down to the black forest in June. I had preplanned all the routes and luckily installed them onto my husbands ancient tom tom so we always had a route when mra wouldn't play ball. I tried downloading the routes to use offline because of unknown data availability, but after the first stop each day I could not get it to continue route. If I removed all the way points I'd been through it just wanted to take me back to the start. I navigated around Europe for a year using mra on my old gamin in 2019. Totally reliable.

[richtea999]

@Teresa-Wood said in Feature request for MRA Navigation app: report a (temporary) road block:

@richtea999 thanks, I've just checked and traffic aware is on. I have touch sensitive gloves.

Long press on the next waypoint indicator (top right) and it will skip it.

What are bar buttons?

https://jaxeadv.com/barbuttons/

Other button sets are available, but these work quite nicely and are a sensible price.

... after the first stop each day I could not get it to continue route. If I removed all the way points I'd been through it just wanted to take me back to the start.

<teaching grandma to suck eggs mode>

MRA always taking you back to the start means you've missed the start i.e. the 'via' point indicated by a hand symbol. MRA won't let you skip 'via' points (which when you need that long press), but it will let you skip the 'shaping'/normal waypoints, i.e. the inverted raindrop symbol.

</teaching grandma to suck eggs mode>

[Con Hennekens]

@Teresa-Wood, If I understand this correctly, you navigated a multiple day route contained in one "file" in the route planner?

• just long-press the first waypoint on your path to start navigating there each day.
• stop doing multiple day routes in one, and make a separate route for each day.

[FrankS]

@Nick-Carthew Thank you for the link, will use that next time after I had encountered a road block on my tour.

[FrankS]

@Corjan-Meijerink: Thank you for your quick response. I (also working in the software application development and therefor) fully understand the need for prioritization of features in the product roadmap. Two questions regarding that roadmap: #1: is the current feature roadmap public or at least visible for beta users? #2 Does the MRA team (from time to time) organize polls or events in which the subscribers can vote for features, so that you have the input from the user community?

[Corjan Meijerink]

@FrankS thanks for asking.

1: No, it is not visible. We do not have it publicly available mainly due to consistency reasons. Roadmaps tend to be posted and become outdated creating more confusion than clarity. Personally, I am not against making it public.

2: No, we rarely have feature specific votes. It really comes down to hype about requests on the beta forum (and non-beta if relevant). Then it's up to me to schedule some time to implement. Quite often small requests can be implemented same day / week (such as a request before current release to make long route names better visible). The timing of the request, my personal approval, some free time, no real impact on work load and above all no required extended testing resulted in it being implemented almost immediately.

It's not that I'm against explicit voting or continuously sharing our roadmap. It's just that it takes time to manage and I would need to manage that. More community management, less time to code

That's my honest answer (as are all my answers on this forum hahah). The little staff we have needs to be allocated very efficiently to keep our output at the current level.

[FrankS]

This post is deleted!