(Created page with "== House Numbers vs Residential Point Places== '''When (and how) to use which''' First, lets clarify by what we mean by a “Places#Residential_point_place|Residential Poin...") |
mNo edit summary |
||
| Line 14: | Line 14: | ||
When users search in the Waze app for a destination by its street address, the address field in Public Place (PP) objects (both point and area, regardless of category) is not searched. Those fields are for display only to allow users who search by a place name to select the correct entry (such as a search for McDonald’s might return many results). Thus, we have to take a different tactic for users who search by the street address of their destination. | When users search in the Waze app for a destination by its street address, the address field in Public Place (PP) objects (both point and area, regardless of category) is not searched. Those fields are for display only to allow users who search by a place name to select the correct entry (such as a search for McDonald’s might return many results). Thus, we have to take a different tactic for users who search by the street address of their destination. | ||
The “standard” solution for these searches is the use of a HN. However, HNs have one major limitation: they must terminate on a segment of the same name as the one they were created on. Thus, a HN for 123 Main St '''must terminate at a point on Main St.''' A HN cannot terminate on an unnamed PLR segment or anywhere else. If routing directions ought to lead to a point other than the named segment, then a HN is not the right solution. | The “standard” solution for these searches is the use of a HN. However, HNs have one major limitation: they must terminate on a segment of the same name as the one they were created on. Thus, routes to a HN for 123 Main St '''must terminate at a point on Main St.''' A HN cannot terminate on an unnamed PLR segment or anywhere else. If routing directions ought to lead to a point other than the named segment, then a HN is not the right solution. | ||
Adding a RPP solves the problem because it can terminate on any segment, regardless of name. They should be used in conjunction with the named Public Place. | Adding a RPP solves the problem because it can terminate on any segment, regardless of name. They should be used in conjunction with the named Public Place. | ||
Revision as of 20:27, 29 August 2017
House Numbers vs Residential Point Places
When (and how) to use which
First, lets clarify by what we mean by a “Residential Point Place” (RPP) versus other place types, and versus the House Number (HN). The RPP is indicated in WME by a triangular point symbol, to help it stand out from the standard circular “Public Place” (PP) symbol. RPPs do not have names, details, etc – they only have an address (they do allow users to add photographs, unlike HNs).
Inserting each type
To create an RPP using the stock WME interface, first create a normal point place using any category. You only need to fill in the address field (anything else will get deleted). Then click the link for “Convert to Residential/Private (address only).” Then save your work.
Note: WME Place Interface Enhancement (PIE) allows you to add “Residence / Home” to your places menu, allowing direct insertion of an RPP onto the map.
By contrast, a House Number (HN) is created and viewed by selecting a segment, then pressing the “Edit house numbers” button in the properties pane. HNs are part of the segment, so editing is limited by the segment’s lock level.
Controlling routing for searches by address
When users search in the Waze app for a destination by its street address, the address field in Public Place (PP) objects (both point and area, regardless of category) is not searched. Those fields are for display only to allow users who search by a place name to select the correct entry (such as a search for McDonald’s might return many results). Thus, we have to take a different tactic for users who search by the street address of their destination.
The “standard” solution for these searches is the use of a HN. However, HNs have one major limitation: they must terminate on a segment of the same name as the one they were created on. Thus, routes to a HN for 123 Main St must terminate at a point on Main St. A HN cannot terminate on an unnamed PLR segment or anywhere else. If routing directions ought to lead to a point other than the named segment, then a HN is not the right solution.
Adding a RPP solves the problem because it can terminate on any segment, regardless of name. They should be used in conjunction with the named Public Place.
Examples
Example 1: Looking at this "Subway" location, it is addressed as 211 E Morris Blvd. https://www.waze.com/en-US/editor/?env=usa&lon=-83.28989&lat=36.21322&s=129498583&zoom=10 Note that there is no access from E Morris into the parking lot where Subway is located. If we relied on a HN, then users searching by “211 E Morris Blvd” will be routed to a point on E Morris Blvd, not into the parking lot via either S Hill St or S Daisy St. Using the RPP for 211 E Morris Blvd in addition to the PP for Subway, we can route all traffic to the door, whether they search by name or by address.
Example 2: Looking at this medical office "Southeast Retina," it is addressed as 2412 N John B Dennis Hwy. Note that John B Dennis Hwy is a divided highway. https://www.waze.com/en-US/editor/?env=usa&lon=-82.50838&lat=36.55516&s=129498583&zoom=8 If we use a HN here, it will route to a point on the southbound lanes, not onto the PLR segment. Thus, traffic approaching from the south (traveling northbound) will be incorrectly instructed to drive past, then make a U-turn to arrive at their destination. Using the RPP for 2412 N John B Dennis Hwy will route all traffic to turn onto the PLR and arrive at the destination correctly.