User:Tonestertm/HouseNumbers in depth View history

(Created page with "Place Holder")
 
No edit summary
Line 1: Line 1:
Place Holder
Place Holder
Your comment about moving the number closer to the street indicates that you may have some confusion about how House Numbers work in Waze; they do not function in the same way that Google address pins do.
Waze House Numbers have two parts: the Number point and the Stop Point.
The Number point belongs directly centered over the building with that address. Waze does not route to the Waze Number Point.
Waze will route to either the Waze Stop Point, or the Google pin, according to the trust level--there is a prioritized system of "trust" when searching for an address in the client app:
Confirmed Waze House Numbers
Google Address Pins
Unconfirmed Waze House Numbers (if there is no matching Google pin)
(Most of) Waze's House Numbers were originally imported from an outside source, and these numbers, untouched, are "unconfirmed". You may have noticed that many of them do not line up well with the buildings and streets in the Waze map. In addition, the address point from the source usually sits approximately in the center of the property, rather than on the main building on the property. This is also usually the case with Google address pins. If a Google pin is chosen, Waze routes to the closest it can "physically" get to the pin on the nearest routable road.
So, how does an Unconfirmed House Number get Confirmed and become the first choice for routing, instead of third? By handling it and Saving, in the House Number editing window. This occurs because Waze reasons that if an editor has taken the time to open the House Number window and handle a given House Number, then the information left behind is likely to be correct, or confirmed.
Confirmation can be accomplished by adjusting the Number Point, the Stop Point, or both, and then Saving. It can even be accomplished by picking up one of these points, moving it away and then putting it right back where it was, then Saving. The important thing is, that it got handled and Saved.
This is why, when House Numbers reappeared in the editor, it seemed that moving the Number Point closer to the street, as we must do with Google pins, made addresses work properly--they were being handled, increasing their trust level. It wasn't that moving them closer to the street made the Waze HNs work better. Waze Stop Points are on the Street, by design, so they do not cause misroutes to nearby streets, the way that Google pins do, when they sit in the middle of the property.
So, something to keep in mind as you work HNs in the future. Number Point centered on the building, Stop Point moved to where Waze should route; the important thing is that something gets handled ("nudged" or "bumped") and Saved. This causes Waze to use a House Number instead of a Google pin.
You can tell if a HN has been previously confirmed by clicking on it. A confirmed HN will cause a "Last edited by..." popup in the upper left of the HN window.

Revision as of 09:42, 8 January 2015

Place Holder Your comment about moving the number closer to the street indicates that you may have some confusion about how House Numbers work in Waze; they do not function in the same way that Google address pins do.

Waze House Numbers have two parts: the Number point and the Stop Point. The Number point belongs directly centered over the building with that address. Waze does not route to the Waze Number Point.

Waze will route to either the Waze Stop Point, or the Google pin, according to the trust level--there is a prioritized system of "trust" when searching for an address in the client app: Confirmed Waze House Numbers Google Address Pins Unconfirmed Waze House Numbers (if there is no matching Google pin)

(Most of) Waze's House Numbers were originally imported from an outside source, and these numbers, untouched, are "unconfirmed". You may have noticed that many of them do not line up well with the buildings and streets in the Waze map. In addition, the address point from the source usually sits approximately in the center of the property, rather than on the main building on the property. This is also usually the case with Google address pins. If a Google pin is chosen, Waze routes to the closest it can "physically" get to the pin on the nearest routable road.

So, how does an Unconfirmed House Number get Confirmed and become the first choice for routing, instead of third? By handling it and Saving, in the House Number editing window. This occurs because Waze reasons that if an editor has taken the time to open the House Number window and handle a given House Number, then the information left behind is likely to be correct, or confirmed.

Confirmation can be accomplished by adjusting the Number Point, the Stop Point, or both, and then Saving. It can even be accomplished by picking up one of these points, moving it away and then putting it right back where it was, then Saving. The important thing is, that it got handled and Saved.

This is why, when House Numbers reappeared in the editor, it seemed that moving the Number Point closer to the street, as we must do with Google pins, made addresses work properly--they were being handled, increasing their trust level. It wasn't that moving them closer to the street made the Waze HNs work better. Waze Stop Points are on the Street, by design, so they do not cause misroutes to nearby streets, the way that Google pins do, when they sit in the middle of the property.

So, something to keep in mind as you work HNs in the future. Number Point centered on the building, Stop Point moved to where Waze should route; the important thing is that something gets handled ("nudged" or "bumped") and Saved. This causes Waze to use a House Number instead of a Google pin.

You can tell if a HN has been previously confirmed by clicking on it. A confirmed HN will cause a "Last edited by..." popup in the upper left of the HN window.