Waze forum

Note ID: 54436298
I tried editing the map myself but it's locked with the above ID.
Going north on I87 trying to use 16, the map should show "Keep Right" on the place where it shows now Exit 16 which is missing from the map a mile up the road (it shows direction correctly but missing the exit notification).

FYI, we have not had an update since June 14th. There is one coming soon, just no date yet. If the edits were done around that time, that's why it is still giving bad routing.


Sent from my iPhone using Tapatalk

Can you check this out again please? For about a month now, navigation won't show I can exit at 16. Nav has me going to 17 and turning around. I tried to edit the map but being new nothin worked. I made a post in the "problem with navigation" forum for reference.

Edit: Spil,I see you participated in my other thread so thank you, but I still have the issue with exit 16 not being recognized by the app during navigation.

Can someone verify that the changes were made before the next update hits?

That's a lot of people driving an extra 30 minutes during these busy summer hours where tens of thousands drive this way to the catskills every week.

problemsny wrote:Note ID: 54436298
I tried editing the map myself but it's locked with the above ID.
Going north on I87 trying to use 16, the map should show "Keep Right" on the place where it shows now Exit 16 which is missing from the map a mile up the road (it shows direction correctly but missing the exit notification).

"Would you believe ..." that this problem has been partly fixed already? I was just working in this area last night, as a matter of fact, finishing up my work on the NY-17/I-86 corridor. In the main map, the exit is now properly labeled according to the sign: "Exit 16: US-6 / SR-17 / Harriman"; this will show in the client version with the next map update, which should happen this coming weekend.

I did say "partly fixed" ... I see where the exit is beginning far earlier than it should. I've corrected this just now, but that correction won't appear in the client until the update after next (hopefully the weekend of June 9-10).

Thank you for your feedback ... if you have any further problems in this area, let me know.

Any changes made right now won't be included in the next update anyway -- they'd be in the one after that (that's just the way it works).

Once the next update does occur (and as bigbear mentioned, we're way overdue for one ), try out the area again and see if you still have the problem. If there's still an issue, then I'll take the junction apart and rebuild it, to see if that will correct the problem there.