I’ve only just realised that after mapping MEPs since February 2019 :!:, 3 years later it is still not available for most users. I can’t access it on my iPhone as I don’t have access to the RBS and Android users can’t access it at all AFAIK. Also not sure whether it will ever be available for the increasing number of CarPlay/AA users.
I came across one example today where mapping MEPs for the benefit of future-proofing causes an issue now. When there are two exits from a roundabout ideally you want the entry point being at the welcome sign before the roundabout so that the user can make the choice as to which one they take, rather than having the decision made for them by the main entry point.
Just raising as I think editors should be aware of potential issues with adding MEPs before they are usable in app.
Its worse than this (or at least used to be unless a fix has been applied) In Android, Waze ignores the Default or Main entry point, it chooses which entry point it thinks is the shortest route. So for example, if you have a place with the Main entry on the west side, and the HGV entry on the east side…if you start you’re journey from the east, then its likely that Waze on Android will choose the HGV entry as its the shorter route. I’ve found that MEPs cause more problems, and often changing to one entry point at the main entrance solves the issue.
Actually looks like that bug has been fixed, I’ve done some tests. I think its still a problem if there are multiple points but none is set as “Main”. Waze will just choose the closest one.
MEPs do now seem to be listed in the Android Beta app in the search results as below, I’ve not noticed this before…maybe I’ve just always defaulted to the top result.
(and yes there is a Hooters in Nottingham, not sure why Gate 5 has been shunted below Hooters in the results)
