Line 20 in comparison view. Recommend “Addresses in an Area place or a Point place are cosmetic only and not used for address search like Residential Point Places.” vice
“Standard (not residential) Waze Place addresses” are cosmetic only, and not used for address search.
Add a section that HNs can have multiple street names and/or city names as alt names while RPP can only have one street and city name combination per RPP.
Waze HN Interpolation will be to the named road segment vice the Google map interpolation to the nearest segment even if not accessible on the named road segment. (ex last house on a court might be the street over).
removed GMM since it is gone and just said Google Maps
changed wording to residential point Places to be consistent with what you said.
For the Markers section - should we state to add a residential point Place vice a HN? The current guidance is to put PP or AP (as appropriate) but if someone searches for the address it won’t use the cosmetic address in the PP or AP.
Good question but that was where the HNs work and you could use either HN or RPP.
In the Marker section it states the anchored HN doesn’t work for routing when actual address is through many PLRs. Currently states to use AP or PP. Those options don’t work for address search since just cosmetic use of the address. So putting in a RPP would allow users searching by address to be properly routed.
What is the acceptable format for alphabetical HNs? Is it 1234A, 1234-A, 1234#A, 1234 A (with a space)? Since this is now a USA page, it’s best to clarify it.
I read through the proposed changes and the information looks good to me. The only thing to note and it may very well be personal opinion, is the lack of title casing when stating House Numbers and Residential Place Points. I’m definitely no English major but they are identified as “RPP” and “HN” so to me “residential point Places”, “residential Point Places”, and simply “house numbers” doesn’t quite look correct. Otherwise if keeping sentence case, there are still a few places to make the changes for page uniformity.
We don’t have a lot of uniformity with capitalization in the wiki. Although we seem to agree that sentence case is preferred over title case, disagreement stems from what is a proper noun and what isn’t. This was discussed somewhat in this thread but that discussion seems to have stalled. Anyhow, I think we should not capitalize any Waze objects (like place, update request, house number, etc.) and just use unambiguous language, because I don’t think they’re proper nouns. As for abbreviations, capital letters are used all the time when abbreviating common nouns.
Regardless of capitalization, we really need an update to this page, and this draft looks good! Lots of useful and important information.
Quickly read through that thread, thanks for linking it. I am good with sentence case and the initiative to come to a standardization for wiki writing. Seeing the differences from what I am used to reading triggered me to take notice. That said, I also agree this update is very much needed and the information contained needs published for the masses. Thanks to Nick and subs5 for their work here.
Its been a few days without comment, so I’m sharing this among a few additional GHOs. I think this one is pretty straight-forward, but want to make sure there aren’t any hold outs.
Great job Nick, nice update to an important topic i think an update that should go live quickly
Two Quick question on interpolation (neither of these questions should hold up the posting of this update):
Do we know if waze interpolates both sides of the street (odd/even)?
Is interpolation only on a per segment basis between house numbers?
Reading thru the suggested page update, noted this added bullet point:
* House numbers only route to road segments with names; RPPs will route to any road segment named or not.
This is quickly confirmed when testing the route after an RPP is added at the end of an unnamed private road going to the house.
I may have missed a change, but does the RPP’s “city” still have to be added as an alternate on the named address segment, whenever the primary name has a blank city (i.e. rural)?
Since I routinely add the street/city as an alternate, for out-of-city segments with an RPP, I’d never realize that, LOL. If that requirement was eliminated, it would be good to save that additional editing workload.
There are still a number of hidden mechanisms that are required for RPPs to be used, but they aren’t fully understood. For example, there is some thought that adjusting a stop point for a RPP is also required for it to be used in the app.
After I finish the HN page, maybe I can work on the Places#Residential section, or create a subpage for RPPs. For now, I’d like to keep most of the content on this page specific to HNs.
Two comments:
(1) In the search hierarchy, you have “Waze RPP or house number” at the top of the list. I suggest Waze RPP be top, then follow with Waze house number
(2) There is a growing practice to link a Google address to a place so that Wazers who search by address are led to that place without the need to add a Waze RPP. I’m not sure where this falls in the hierarchy — I’ve only seen it used in lieu of a Waze RPP.
Echo the great work and transparency this provides. I agree with these points, but for point #2, this may need to be an amendment to the Places page or just some simple text referring people back to section 5.1.1 in the USA-Places wiki when looking to link a Place Point/Area…