Road names/City names: Difference between revisions Discussion View history

Revision as of 02:14, 14 November 2016

To keep city names from sprawling over too wide an area in the Waze app, in WME and LiveMap, editors follow standards of placing the city name on segment details only within the boundaries of the city polygon. That means many addresses on the map are in these “no city” areas, particularly in rural regions.

The search problem

An editor can create a Residential Point Place (RPP) in the correct location with an accurate address, but Waze may not route to the RPP if the city is not on a nearby segment. It will turn up under the "more results" tab in the app, but will be listed without a city and thus unlikely to be chosen.

Waze search defaults to best match of search terms, whether they're entered in search fully or selected from the autofill results. If the Wazer enters or selects a postal address and there is none on the Waze segment, W first to Google backup data that matches and will route to that pin. That’s not always optimal, especially in rural areas or other locations where the destination is some distance from the named road.

There are sometimes multiple city names in use for an area — a municipality or a Census Designated Place (CDP), in addition to the postal address.

But because many Wazers will search for a location by its postal address, U.S. management has established an editing standard to include the city designated by the U.S. Postal Service as an alternate on segments having no name, or a conflicting name, in the City field.

For example, these images show a discrepancy between Waze RPP and Google coordinates, and where the Waze app puts the search result. The example shown in the images is 10020 SW Grabhorn Rd, Beaverton, OR.

The city has now been added to the segment off the main road closest to the RPP. NOTE: In order to add an alternate city to an unnamed road segment, it’s necessary to put the street name of the address in the primary position, and then save, to get the option to add an alternate. The street name can be deleted from the primary after the alternate is in place.

The improved navigation result can be seen in the final screenshot from the app.

There are other standards in place for other purposes requiring adding other street data in the the alternate. The addition of the USPS data does not change any other standards but is in addition to anything existing already on those affected segments.

Identifying the correct postal city

Editors should use official USPS tools to check the city. If you know the ZIP Code, the city can be looked up here, or entering a city believed to be correct can be verified:

https://tools.usps.com/go/ZipLookupAction_input

Every Door Direct Mail, a mapping tool from USPS, produces a map with ZIP Code boundaries:

https://eddm.usps.com/eddm/customer/routeSearch.action

TIGERWeb is an online service of the U.S. Census Bureau:

https://tigerweb.geo.census.gov/tigerweb/

@@ Line 1: / Line 1: @@
-To keep city names from sprawling over too wide an area in the Waze app, in WME and LiveMap, editors follow standards of placing the city name on segment details only within the boundaries of the city polygon.
+To keep city names from sprawling over too wide an area in the Waze app, in WME and LiveMap, editors follow standards of placing the city name on segment details only within the boundaries of the city polygon. That means many addresses on the map are in these “no city” areas, particularly in rural regions.
-However, many addresses on the map are in these “no city” areas, particularly in rural regions. A search for these addresses are visible under the "more results" tab in the app, but they will be listed without a city and thus are unlikely to be chosen.
+== The search problem ==
+An editor can create a Residential Point Place (RPP) in the correct location with an accurate address, but Waze may not route to the RPP if the city is not on a nearby segment. It will turn up under the "more results" tab in the app, but will be listed without a city and thus unlikely to be chosen.
-Waze search tries to find a match. If the Wazer enters or selects a postal address in search, Waze will default first to Google backup data that matches and will route to that pin. That’s not always optimal, especially in rural areas or other locations where the destination is some distance from the named road.
+Waze search defaults to best match of search terms, whether they're entered in search fully or selected from the autofill results.  If the Wazer enters or selects a postal address and there is none on the Waze segment, W first to Google backup data that matches and will route to that pin. That’s not always optimal, especially in rural areas or other locations where the destination is some distance from the named road.
-== The search problem ==
-An editor can create a Residential Point Place (RPP) in the correct location, but to get Waze to return the RPP as a result, the search criteria must match with the data on a nearby segment.
 [[File:WMEvsGmaps.png|left|180px|WME vs. Google Maps]]
 There are sometimes multiple city names in use for an area — a municipality or a Census Designated Place (CDP), in addition to the postal address.
-But because many Wazers will search for a location by its postal address, Waze editing standard in the U.S. is to include the city designated by the U.S. Postal Service as an alternate on segments having no name, or a conflicting name, in the City field.
+But because many Wazers will search for a location by its postal address, U.S. management has established an editing standard to include the city designated by the U.S. Postal Service as an alternate on segments having no name, or a conflicting name, in the City field.
 For example, these images show a discrepancy between Waze RPP and Google coordinates, and where the Waze app puts the search result. The example shown in the images is 10020 SW Grabhorn Rd, Beaverton, OR.