Timbones wrote:I've missed something somewhere - 1) how can there be house numbers that weren't put in by an editor, and 2) why should "nudging" them be necessary?
Some countries (maybe all, but definitely the USA) have House Numbers imported into WME, however even when they are correct they are handled differently by the server than HNs which were touched by editor. So say for example there is a corner house at the intersection of C ave. and 1st st. The address is actually 123 C ave., but the location of the imported HN is closer to the segment of 1st st. than it is to the segment of C ave. Since this HN was never touched in WME, a search for this address will prefer a matching Google result over the Waze HN. (In the USA it seems our imported HNs came from Google and usually in the same location). If I touch the HN in WME, the Waze HN will now be preferred over a matching Google result.
The practical implication in this case. A destination to a Waze HN always ends on the named segment for the HN, so even though this HN is closer to 1st st, the destination will be the closest point on C ave. to the HN location. If the search returns a Google result, the destination will be to the closest segment to the HN location which in this case would be around the corner on C ave.
Once I touch the HN in WME, even if I just move it a few pixels (even closer to 1st st), it will now be preferred over the Google result, and the destination will be on C ave.
This issue primarily shows itself for corner houses, and for areas where the HN and Google pins are closer to a back alley or nearby street, than to the street the destination is meant to be on.