Taco909 wrote:The comment last night was that we only need to note the beginning and ending addresses on a block, IE, for the 600 block, adding "600/601" at one end and "698/699" at the opposite end is sufficient.
I disagreed, thinking that if the driver is searching for 655, not finding it, Waze will still use the Google pin and possibly be routed to the next street over. Is this correct, or is an address range manually input sufficient?
In my (limited) testing of address interpolation, I do not think it works with Waze addresses. When it doesn't find the Waze exact
match, it uses the Google match. Google will do address interpolation and return its "best guess" based on interpolation of existing, known addresses.
Taco909 wrote:Follow-on... I have a couple of locations where the address is on a MH, but access is only via the street the next block over. If a Waze pin is present, will deleting it cause Waze to revert to the Google pin and then route the driver to the "incorrect" (in this case, correct) road if the Google pin is placed properly for that to happen?
That is how it should work, yes. If the correct stop point is NOT on the street named for the address, then Waze should not have a House Number for that address. I just added a 2nd Red Note to the Things to Remember section of the documentation: https://wiki.waze.com/wiki/House_Numbers_in_WME