I tried to navigate to 295 Ann St in the city today and it took me to just outside all hallows school instead of 1km down the st further into the city. I’ve had similar issues with house numbers in Everton Hills, the gap, newfarm, tennerife, Hawthorne and more so it’s all over Brisbane.
The issue also happens no matter my platform, android auto or on the app.
How are you navigating to these locations, simply typing in the address bar, finding the result and tapping go? Or are these planned drives you’ve planned elsewhere like your calendar or the live map? Were the drives started automatically when you opened Waze?
Keen to get as much information as possible to try and isolate what’s going on.
Interesting situation. Waze finds house numbers in three ways:
directly entered into Waze
from Google Maps
interpolation - it will guess the location using known address points e.g if there is a 310 and a 240 then it knows 295 must be somewhere between those two.
Sometimes the addresses coming from Google maps can cause issues but that doesn’t seem to the problem in this case.
I have just checked the address in Google Maps, our Waze LiveMap and also in the app (I run iOS) and everything is where it should be. Routing works as expected.
Did you type in the address (295 Ann St) or did you search for a place name (Government Centre)?
