AlanOfTheBerg wrote:And this isn't good enough. 1) We don't name unnamed private driveways, so 2) Waze doesn't let you set the stop point on any road other than the main named one. This is a must for remote driveways and store addresses within parking lots.
Okay, so explain how this works. In the image below, assuming the address lookup is working, and the actual building for 118 is at point C, will Waze route you to point A, being the spot on the road that the address is assigned to, or will it still follow the driveway in to point B to get you as close as possible to point C?
If so, what's the reasoning behind even having a point A? If not, does the driveway provide any type of aid to navigation other than something to snap to when driving on the driveway, and when trying to leave?
My response was *really* in reply to this:
jdeyoung wrote:since there's no point along the straight line for the client to know where to stop.
which is incorrect.
Point A will get you right to the intersection of the driveway whether it's there or not.
In this example here, unless I had driven that driveway, I never would've known it was there, and any attempt to draw in driveways like this is futile unless a Wazer is actually using them, and has put them in using the pave function.