MRA 5.0.1-430 Limit of 1000 POIs

[Corjan Meijerink]

The route you opened “zahn” apparently has more than 1000 POIs loaded from most likely one of your own POI groups.

You probably enabled a POI group by default for all your routes in your account

[Hubert Thoring]

In the web planning I have always activated the POIs of the Alpine passes, and closures ...

The route tooth has been created directly in the MRA app directly...

I would say that no user is aware of what MRA is in the file ...

How should the user behave?

[Corjan Meijerink]

@Hubert-Thoring if you disable those POI groups, the warning will for sure disappear.

I don’t see why you’d need all those POIs loaded all the time You enabled the POI groups to be enabled for all your routes so you are aware you did that.

Especially because of that we added this setting. Users were unaware of the fact that always showing 10.000 POIs would cause some issues with performance Then they get mad at our app while they were kinda abusing a feature which in their defense is wasn’t smart of us. Hence we now limit the POIs

[Hubert Thoring]

Okay, thank you, I understand that now, that should be explained again for all users.

I was not aware of that at all, I will take a closer look at it tomorrow and then check the settings.

Thank you very much, and good night with a relaxed dream of the best MRA app it already is

——- D ——-

Okay danke das verstehe ich jetzt, das sollte dann auch noch einmal besser für alle User erklärt werden.

Mir war das überhaupt nicht bewusst , ich schaue mir das morgen mal genauer an und werde dann die Einstellungen überprüfen.

Vielen Dank, und gute Nacht mit einem entspannten Traum von der besten MRA App die sie jetzt schon ist

[Con Hennekens]

@Corjan-Meijerink, while I totally understand your desire to limit the amount of POI shown, I typically load a geocaching pocketquery which also has a limit of 1000 geocaches as default POI category. Hence I ALWAYS get this message when starting a route. That's a bit unlucky. Is it really stressful for the app to up the limit to let's say 1250 or 1500? For my specific case even upping to 1001 would suffice

[white.mouse]

@Con-Hennekens; Another (simple) solution is to limit your pocketquery to 999! I got mine limited at 500. That's more than I can do in a daytime!

[Con Hennekens]

@white.mouse, I know how pocket queries work I don't usually load them for a single day, but to have them at hand whenever I am driving around What I was hoping for, is a little headroom for more than just one POI. Often it is not the only category you want to have enabled. And yeah, my newer phones don't seem to have any problem handling multiple 1000s of POI. But yeah, if nothing can be done about it, I will need to adjust some PQ indeed.

[Hubert Thoring]

Can you please explain to me in this context what No. 3.) does exactly ...?

• Im Profil anzeigen
• Does that mean the profile will then automatically be displayed in every route?

[Hubert Thoring]

What do I do if I have no control over the number of POIs in a file I download from the web?

For example, road closures... Link to select a POI file

There appear to be more than 1000 points of interest there...

This is displayed in BasCamp! So it's not 1000 POIs, but a mix...

I reduced it to 106 POIs in BaseCamp, but the message in the MRA still appears! ?

[Hubert Thoring]

@Corjan-Meijerink : Please explain what happens in the background of the app!

1.) What does the message "The POI limit of 1000 has been reached" actually do in the background of the app?

My setup: I've selected two POI files, "Alpine Passes" and "Road Closures." What does the app do with them then?

• Are POIs truncated?
• What is still displayed?
• What is still there and what isn't?

This message is quite confusing for me and I'm sure for many other users as well.

• Is it just a message that indirectly says if you have performance issues with the app on your phone, it's your own fault if you want to see so many POIs?

In the past, I never had the problem that my old iPhone XR, now 7 years old, couldn't process the POIs; there was no performance issue!