Terrible navigation

[DorKul]

I finally was able to connect to the Waze server, and tried to post a permalink of the problematic area. However, I can't figure out how to do that. I see the link at the bottom right corner (marked "SuperPermalink") but when I click on it, it just re-shows me the same map (without my route marked on it) - how do I paste this map onto a thread in the forum? Since I couldn't figure this out, I just made a snapshot of the map and I'm attaching it here.

Capture.PNG (97.39 KiB) Viewed 265 times

As you can see from the map, I was driving west on Richmond Avenue, and my destination was Briarpark 3600. When I was standing at the corner of Richmond & Briarpark, in the left turn lane (which is NOT restricted), the Waze navigator was telling me to continue straight until I hit Beltway 8, then turn left, drive south until Westpark Drive, and turn left again at Briarpark. This is neither shorter nor faster than the route I took instead, which was to simply turn left at the corner of Richmond & Briarpark.
Even then, after recalculating, the Waze navigator still did not realize that I was only a few yards away from my destination, and instead recommended that I continue straight on Briarpark, drive past my destination until I hit Westpark, drive around the block just south of Westpark, and then come pack up Briarpark to finally enter my destination. I don't really know how GPS navigators work, but from the user's point of view - this just makes me feel that Waze isn't reliable.

[xteejx]

You can right click that link and copy it onto here. It would make it easier for editors to look at the problem directly.

Using Tapatalk

[AlanOfTheBerg]

I finally was able to connect to the Waze server, and tried to post a permalink of the problematic area. However, I can't figure out how to do that. I see the link at the bottom right corner (marked "SuperPermalink") but when I click on it, it just re-shows me the same map (without my route marked on it)

Copy the hyperlink? Pretty basic stuff. Also, totally covered in the manual.

[foxitrot]

I finally was able to connect to the Waze server, and tried to post a permalink of the problematic area. However, I can't figure out how to do that. I see the link at the bottom right corner (marked "SuperPermalink") but when I click on it, it just re-shows me the same map (without my route marked on it)

Copy the hyperlink? Pretty basic stuff. Also, totally covered in the manual.

I believe the confusion came from the fact, that the "permalinked" copy of the Cartouche editor's page did not contain the user's drive.

According to the screenshot, reaching Richmond Ave+Briarpark, Houston should be not a problem for a versed editor. Hopefully, DorKul will learn his lesson and remember (how) to copy a permalink of area being described into forum (to ease the attempts to locate it).

BTW, the last steps of his route are against the one-way-road's direction? But it still does not explain the recommended route.

[foxitrot]

When I was standing at the corner of Richmond & Briarpark, in the left turn lane (which is NOT restricted), the Waze navigator was telling me to continue straight until I hit Beltway 8, then turn left, drive south until Westpark Drive, and turn left again at Briarpark. This is neither shorter nor faster than the route I took instead, which was to simply turn left at the corner of Richmond & Briarpark.
Even then, after recalculating, the Waze navigator still did not realize that I was only a few yards away from my destination, and instead recommended that I continue straight on Briarpark, drive past my destination until I hit Westpark, drive around the block just south of Westpark, and then come pack up Briarpark to finally enter my destination.

Attempts with LiveMap show pretty weird routings from Richmond Ave towards the destination nearby Briarpark Dr., possibly caused by a red arrow, which disables this turn right. If the right turn is allowed, fixing the red arrow should correct it.

BTW, the last steps of his route are against the one-way-road's direction?

This might need a fix as well?

...from the user's point of view - this just makes me feel that Waze isn't reliable.

I agree, often But in this case I believe the map (editor) is the culprit.