As a developer, I find this hard to believe. I’m not saying it is trivial to program. But adding a parameter to a method or an attribute to an object? Meh. Even if it is buried under ten layers of function calls, there’s usually an object with misc data used throughout the levels. Most frameworks support it easily.
I’m not disagreeing with you, well not exactly. But Waze has known the lat/lon-only setup for routing has been a problem for a long time, and users have often requested the street name be taken into account in determining the correct stop-point. To date, Waze has either been unwilling or unable to make the changes.
Alan, do you know if this is already in bugzilla (I did not search yet)? Maybe we could get a bunch of us champs to vote for it to move it up? I waste a lot of time editing Google maps to fix this lame Waze issue, and in some cases I actually make the Google map data wrong by moving the house address pin too far away from the house just to get it away from the back street.
I’m having some issues where businesses (either POI or address lookup) show on a major street, but the businesses themselves are only accessible through parking lots that are not directly accessible from the street the address is on, you have to go to a side street or sometimes to a parallel street to get to the businesses.
Normally mapping parking lots solves these issues, but now I’m starting to run into issues where I have a couple of businesses that are physically closer to the major street than to any point in the parking lot, and Google won’t approve me moving the business pin locations closer to the parking lot so that Waze can route appropriately. I agree with Google not approving me messing up their maps so that Waze can route, and I already feel awkward moving house pins when they aren’t in bad positions to begin with. Waze needs to find a better way to resolve these issues.
Waze already has the fix: internal house numbers. I don’t think it makes sense for this to be in bugzilla.
Beg to disagree. Let them run a scrum for fixes and decide between implementing house numbers now and implementing an interim (and possibly not so interim) fix for the address lookup logic. Plus, they need a fire lit either way.
I’m pretty sure that adding bug in bugzilla doesn’t really result in any fires being lit.
That was Kent’s point… to have a bunch of champs make complaints, in the (perhaps vain?) hope that it might actually elicit a response.
Well rather than wait another year for internal house numbers to be implemented I went ahead and created a bug report with a proposal for fix this in the mean time. https://bugs.waze.com/show_bug.cgi?id=6291
Those with voting rights are welcome to vote on it to get some higher visibility. I have been told that the dev team does actually pay attention to our votes, but they find very few vote on any entries. Also note that after creating a bug, you separately have to vote for it.
another wazer with the same problem…PeoPle Please
What problem exactly? And have you read ALL the house number documentation?
Jumping on the bandwagon here. I’m new to San Antonio, and new to Waze (since March for both). The first time I used Waze to map to my apartment, it took me to the neighborhood behind my complex. I had to use google maps to find my way back, because it took me pretty deep into the neighborhood. Yay! Exploring more areas, no major peeve, I was amuse more than anything. So I submitted a map error, and kept driving to my apt with waze up, along the route that would actually take me home. No change. So I did some researching through the forums and the wiki. I submitted an address change, created a point/area for my apt complex, with the entrance on the street where you have to enter from. A few weeks went by. Same routing issue. I read some more, and discovered the google maps issue. Well, google always routes me correctly, but waze doesn’t. Nonetheless, I submitted a correction to google maps moving the location point of the address to the street you have to enter on. It’s been 2 weeks since google has responded, and approved my change request. Last night, waze again routed me out of my way, to take me the wrong way to the neighborhood behind my complex. sigh
TL;DR : same problem, no changes despite correcting google maps too (and google routes correctly)
Have you routing to saved the location in the app (a search entry with a star) or are you routing to a history entry (a search entry with a clock)? If so these are saved as coordinates and will not change when the map (either the waze map or the Google map) is updated. Are you still routed the wrong way to the neighborhood behind your complex if you do a new search for the address and select the entry with the tear drop pin?
A Star search entry is a Favorite. ninsianna, you need to be using the search entry with a pin marker. Those are live search results. Other icons are saved/stored locations and will not reflect location changes.
Is there any estimate on when Waze will start using it’s own HNs and stop points FIRST before looking to Google SECOND if it can’t find it internally? I think this will clear up a few issues with HNs in Waze?
My understanding is that when autofill results are generated, they are generated from the Google database and this is unlikely to change in the near future. However, if there is an exact match in the waze HNs to a selected autofill result, then waze will route to the waze stop point for that address.
If you complete the search, then waze first parses the search to determine if it is for an address or for a POI. If it is for an address, then my understanding is that waze does look to its own HNs first. However, it only looks to those HNs that have been added or modified by an editor. If it finds such a waze HN match it uses it first before looking to Google addresses. If there is not a perfect match, there may be results from both waze and Google shown on the waze tab.
It’s unfortunate the auto complete doesn’t look internal first, that would make sense.
I think the exact match has a flaw, in my other post about Quail Crossing vs Quail Xing, Waze still won’t recognize my Waze pin in auto complete even though the address, street name, town is EXACT except the suffix.
On the topic of HNs that have been imported but not touched by an editor, don’t these imported HNs have a stop point on the actual street? If Waze imported HNs for internal use why would they not then refer to them if they are searched?
Yes. I believe the stop point is simply closest point on the street to the house pin.
I’m assuming that they have more trust in the Google data than the data that they imported.
Thx good stuff
Isn’t part of the issue here that postcode areas cover what can be a large area, even at the lowest level of granularity. Consequently Waze thinks my home location is 200 yards away from where it actually is, and whenever I pull up it thinks the journey is still in progress. Is there a way I can ‘fix’ the location and override it, for a favoured location? Or have I missed the blindingly obvious somewhere?