Really? It was still in there I thought. Who is PHSanders? They reverted the stuff that was added in.
It was not there last night, but today is is. PHSanders is Waze’s pseudonym for me when they did a conversion to the wiki. I have removed the second redundant location of RPPs.
I will be proposing some modification to the Places page in that forum.
- adding in the part about the <50 m for new RPP if there was a HN anchor
- adding a brief RPP section to the part above the table of contents for the Places page to be consistent with area places and point places.
Haha. Silly wiki.
Agree with that.
Would it be better to just provide the link to the RPP info in the places page on the HN page?
Sure, I was just listing the changes to the Places page here since somewhat related. Having a cross reference is fine that way only have to update one when something changes.
I just took a look on my computer at this again, and it seems that the RPP section is already referenced in the HN places, or were you thinking to have a more direct reference?
I was thinking more of having a link from one page to the other, just so it only has to be updated in one location if (or when) it changes.
In the guidance here in the House Numbers in WME section, I think think the statement that “additionally ensure the RPP’s city name is listed a primary or alternate city name on a nearby segment.” needs some clarification. The street and city name have to be paired as a primary (or alternate) selection - be an exact match. For the address on First St, Anytown, you can’t just have First St , CensusDesigatedPlace with Maple Rd, Anytown nearby. You actually need First St, Anytown.
So I would change it to “additionally ensure the RPP’s street name and city name are listed the primary or an alternate pairing on a nearby segment.”
This occurs twice. Once in If an address is on an unnamed road segment and once in If the correct stop point for a house/business is on another road segment (differently named segment) away from its properly labeled segment in Waze
Agreed. I have made the updates live on the page now
Hi folks. Thanks for the informative discussion about HNs. I have a question about HN interpolation.
First, thank you for the pyramid diagram on address searching priorities. Very helpful from an editor troubleshooting URs!
Now, let me say that I wish Waze HN interpolation would override google’s. That’s because as editors we have control over it. But I know that’s another story…
My post here is regarding a behavior of Waze HN interpolation that is actually different from what is documented on WO. I have a case here where there is no Google addressing (so Waze HNs are the only data source), and Waze interpolation is working quite well - and EVEN over neighboring segments. When I read the wiki (WO), it implies that it won’t work for even numbers on a segment unless two even numbers are already mapped on same segment, and generally on opposite sides of the point in question. But in my case, it is interpolating correctly when I have only one even at the far end of one segment, and one even at the opposite far end of a neighboring segment.
706 and 754 are mapped (on consecutive segments). Try searching for 726, 736, 746, etc. It works!
Am I misinterpreting?
Thanks for your insights!
Waze can always change programming, but the interpolation and extrapolation was a direct answer to a question that I brought up at a Regional Meetup in 2017. Nzahn1 drafted the posting and had it verified by staff.
Searches are made to be fuzzy, but have you used the Debug mode to see if the search thinks it is Waze or Google as the source?
Well, Red Pine Dr doesn’t exist in GMaps, so I assumed it couldn’t be the source.
https://goo.gl/maps/RoqSG28HXUq
I don’t have a beta installed on my phone. (I prefer to do troubleshooting at the editor, not while I’m driving 
)
Thanks for the quick response
I think you’re right, kndcajun. I saw the same thing recently. HN interpolation works along several consecutive segments with the same name if two are mapped at each end of the sequence. By the way, remember to abbreviate the street name
Good catch ~Kartografer. Thanks
Thanks kndcajun for finding a test bed for interpolation. We’ll see how long it lasts before Google “catches up” and adds the road name.
I’m seeing the same thing that you found in my testing; I tested several even numbers in between the two endpoint HNs (706 and 754), and Waze is resolving the HN using linear interpolation. When testing numbers below 706 (such as 700 ed Pine Dr) or above 754 (such as 800 Red Pine Dr), Waze’s stop point is the same as for 706 and 754, respectively. So, I conclude Waze is not “extrapolating” past the min or max. Interestingly, Waze will only “find” addresses that are within 100 of the min/max range – so for instance, 854 Red Pine Dr resolves to the same spot as 754, but Waze doesn’t find 856 or 900 Red Pine Dr, or 600 Red Pine Dr.
Oooh, good stuff. Thanks dfortney
https://wazeopedia.waze.com/wiki/USA/House_Numbers_in_WME
cite from the House Number page:
Looking for clarification of the above statement. My interpretation of this guidance is to not use House Numbers on Private Road segments. Is that accurate? If so - why should there be no HN on PR?
Also noting that if you have a Private Road that is unnamed … WME will not allow you to select that segment and press the H-key to even invoke the house number interface.
It is referring to a case such as driveways or where you would want the navigation to end where the RPP is rather than on the street where a HN would be. Here is an example: https://www.waze.com/en-US/editor/?env=usa&lon=-82.21216&lat=41.22979&zoom=5&segments=505551611. Of you had HNs for 17375 and 17405, then the stop point would be on the street, rather than way back where the houses are.
Yes, that’s what it’s about, but the wording is confusing, since we can have named PLRs and PRs with legitimate house numbers used on them. It’s really not about road type at all, but rather the use of unnamed segments. We should change this to read:
[quote]
If the destination is located on an unnamed non-public road, such as a driveway or access road (private road, parking lot road, etc.), delete the Waze House Number and replace with a Residential Place Point (RPP).[/url]
The next bullet point talks about differently named roads.
Perfect - thanks for the quick reply and clarification.
Was there ever a time when a house number could have been added to an unnamed road?
I don’t know, but I don’t think so. It’s not possible now to add a HN to an unnamed road, and it’s not possible to unname a road that has a HN. Should we clarify that the HN is to be removed from the parent road?
I believe there was a time in the dark ages when a HN could be added to an unnamed road. I have seen them pop up from time to time.