Not only these days. In general calculating is fast enough. But from time to time calculating a new route after moving, adding or deleting a waypoint takes forever. Pressing F5 most of times solves this issue for that moment.

@wilfried-Baars hoi Wilfried. Heb je toevallig te ver ingezoomed op je Chrome pagina

@Nick-Carthew I get that, but if MRA wants to be THE BEST, then it should be as user friendly as possible. And coming from the IT background creating systems for Wall St. users I am big on cllarity. No one should be wondering what any message means. And it is such a small change... I think Corjan should take it into account.

Thank you for confirming.

@Guzzist Aha, that is so from the beginning. Poi are exported/ transfers with the connector, but not imported. Maybe it will be possible within web 2.0

@M-PRP Prestaties die je ziet zijn van de tracklogs die je in het betreffende land hebt gestart. Als je geen tracklogs hebt gestart in het betreffende land dan is die rit ook niet opgenomen in je prestaties. Overigens wordt de website dit jaar helemaal vernieuwd. Het is nog niet bekend wat er van de oude website mee gaat naar het nieuwe Routelab. Dat is nog even afwachten.

Wel een interessante constatering Zou natuurlijk mooi zijn als dit met Web 2.0 kan worden meegenomen/opgelost

Ik kan de Michelin kaart en de fietskaart alleen via routeplanner op het scherm krijgen Ligt dit aan een instellingsfout?

Yes, thank you! I didn't know that OSM didn't support long distances...

Just noticed…..You fixed it

@Makro To start with the easiest question: no, if you deselect a POI, it does not disappear from your own POI list. The options you are given—adding it as a POI and/or as a waypoint—allow you to choose whether to see both or just one of them. You can then place the created waypoint on the route line (for example, if the POI point is far away from the road) while leaving the original POI point in its original location. After placing the POIs in your route, you can deselect your own library. Only the POIs that have been placed in your route will then be visible. This is especially useful if your own list contains more than 2,000 POIs, as there is a limitation in the navigation app: it displays a maximum of 2,000.

Wouldn't it be neat if having found an exceptional* route blockage the app could display it in red, indicating to the user why the route is not as direct as expected. The user would be informed, rather than confused. Not sure if it's feasible, but it would certainly have helped me in the past! Example: [image: combi.jpg] *closed road, serious jam, etc.

thank you - it was a friends route. I should have checked it

You can report it here: https://mapfeedback.here.com/#/report

@Rolf-Engelsman, change your base map to OpenSTreetMap, and your transport method to bicycle: [image: 0d6eb088-149a-4c69-a396-7b55330554cf-image.png]

I just opened maps.google op my pc and searched for Ugarit ruins. Right clicked on the red droplet and copied the coordinates to the clipbord. Opened a new route in the web routeplanner and copied the coordinates in the search box. In all the mapsets the coordinates were correct. But looking at the picture you posted, the coordinates showed are N and E notation (h ddd° mm' ss.s"). If you can not change the "degrees, minutes, seconds" notation into decimal on your phone, you have to convert them: N 35° 35' 19.2"E 035° 44' 05.9" or 35° 35' 19.2" N and 035° 44' 05.9" E. [image: coordinates javawa.JPG] Only in Dutch https://www.javawa.nl/coords.html

Bedankt voor de update @white.mouse. Ervaar hier helaas nog steeds precies hetzelfde. De oplossing werkt gelukkig ook nog steeds Edit: Getest met Safari op macOS Tahoe 26.1

Mmm, interesting. After a refresh, it now works again for me as well, although the blue lines from Street View only re-appeared after first clicking somewhere to actually go into Street View. Weird, but glad it works again.

Thank you for this derivation and explanation

I'm already looking forward to it when the new WebPlaner appears as an update, some ideas on the subject of POIs are already available and are waiting to surprise us with the ideas in the implementation Some patience is still required, but that will definitely be worth the wait. VG