This is the purpose of the "(Stop) Point" in the new Places system. If
the parking lot is correctly mapped, and
the Place is correctly mapped, with the Point placed on/near the closest parking lot segment, as long as you're navigating to the Place
and not the Address
(as described by Sketch, above) navigation should be flawless, no matter which direction you're coming from.
That is, of course, assuming you've chosen the Waze search result....
(Might be nice if there were something in the auto-complete results showing from which provider each result came... off to the beta forum I go....
Agreed about wanting to know where the search result came from. I remember a ticket where the problem came from bad address information in Yelp...
I'm going to use a specific example about the larger issue.https://www.waze.com/editor/?lon=-88.38 ... 88&env=usa
I had "Bistro Wasabi" with a house marker, like 4550 Algonquin road. (I haven't touched 4550 yet, because I don't know offhand what business it is, and it makes for a clearer example in this discussion.)
4550 has the end point. Reading your comments above, it sounds like Bistro Wasabi (4590) should have an end point for the Places marker, and I should be able to move it to the parking lot segment, which I cannot do with 4550.
Am I understanding correctly? If so, how to I get an end-point for the Places marker?
(And right now, the reason for the marker being at the edge of the building is to prevent routing to the service alley, which was the original reason for adding the address.)