Feature Suggestion - expand POI features

[Guzzist]

In MRA, I love possibility to upload own file (gpx) of POI.
But you are not using full functionality of common agreed functions of POI. Please can you develop to use full set of possibilities of POI.

• Unfortunately, there is only one fix Icon for all POI, given by MRA.
• Unfortunately, there is only a Name possible for a POI - nothing more, no description, no address, no URL

In common rules for POI, there are a lot more of data fields allowed:

• Position
• Name
• Description
• Address
• Phone
• URL
• Icon
• ...

I would like to keep my Information about POI like Hotels and others in MRA as well as in Navi device. But solution by Waypoint is not sufficient because restriction of amount of WP in Navi device. Amount of POI is not restricted because of different data Format.

[ptrdvrs]

Yes, that is what I missing with the own POI database.

[HABVEN aka MrMRA]

Hi,

POIs are on the roadmap, point 1.9.
Adding the POI manager. Allows members to create, share and edit Point Of Interest maps. Also allows multi-route exporting.

We have asked with the RouteXperts community whether it is possible to deal with this earlier

[Drabslab]

@Hans-van-de-Ven-MRA-Master Hai, it is indeed on the roadmap but it also seems that developments are on-going which are not on the roadmap (and that is putting the roadmap as a whole in question.

Anyway, considering that officially the roadmap is on step 1.3 and POI are step 1.9 with an average 3 months per step, this is still a long way of. We need to be patient (I know, I am not good at that either ) , a development team is generally always to small, and it always works on urgent issues popping up and ruining the planning

[HABVEN aka MrMRA]

@Drabslab
Hi Drabslab, What developments are going on that are not in the roadmap?

[Drabslab]

@Hans-van-de-Ven-MRA-Master

Hoi Hans,

The new MRA academy for instance (unless it has been there "always" and I never noticed what would not surprise me to be honest). OK, you could say that this is a new development and does not require much developing but the team must have spent time on it?

And is MRA not working on Apple carplay something? If that is on the roadmap then I missed that completely (again, would not surprise me ). Here you could say that the roadmap is only for the routeplanner and carplay is more related to the navigation tool which is not in scope. But that is also costing resources?

I am not trying to be negative here, both the above examples (if indeed doen aside the roadmap) are very good developments but having a roadmap should mean that you (try to) stick to it, and add new things when needed, reschedule when required... (My former colleagues would laught their socks of reading this coming from me

[HABVEN aka MrMRA]

@Drabslab
Hello Drabslab,

I can assure you that the developers are not concerned with the points you mentioned, but are only concerned with the roadmap and bug fixing.

[dannygroeneveld]

@Hans-van-de-Ven-MRA-Master Please see my suggestion to developers (my seperate post of today) to include the POIPocket system into the MRA system. Working together with POIPocket developers can speed up the MRA development process and will deliver POI management functions (web-based and in the app).