I’ve been going to HA3 6AS, which is a series of houses on Kenton Lane. However, waze thinks it is Kingfisher Close, which is a road just off Kenton Lane. How can I fix this?
Simply, you cant.
Waze does not maintain a postcode database and uses Google for all postcode searches. Because the problem lies with Google data, there’s nothing we can do about this, other than suggest you avoid using postcodes in searches.
If you’re going to a specific set of addresses on Kenton Ln, you could add house numbers in the editor. Waze will then use that house number data to more accurately direct you. If the exact house number isn’t added to the map, Waze will interpolate between adjacent registered house numbers to get you as close as it can. Have a read of the wiki about this.
There is a workaround for problematic postcodes, which is to define a place with the postcode as its name - since the Waze app just appears to do a basic text search for locations, it doesn’t know or care that you’ve entered a postcode and instantly passes that onto Google to handle, so if there happens to be a place defined within the Waze data with a name match to that postcode, that’s the result which will be prioritised now that Waze results appear ahead of Google ones.
Not suggesting for an instant that we should start defining places for every single postcode - not that we need to given that many of them do seem to return reasonable results from Google - but it can be a handy trick to keep in your back pocket when all else fails…