Duplicate cities: Difference between revisions Discussion View history

m (prep for merger with smudged cities)
(Adding clarity on the effect of a WME city name change.)
Tag: national guidance change
 
(43 intermediate revisions by 4 users not shown)
Line 1: Line 1:
<!--#REDIRECT [[Fixing_"smudged"_cities]]-->
Information about duplicate city names in the USA.
[[Image:DupeCity1.jpg|300px|right]]There are a couple of reasons why there may be duplicated city names on the map. This article covers the different conditions for the duplications and how to deal with it.
{{Clear}}


== Missing state name ==
== Duplicate City Name Error ==
In the United States, road segments have a field for the State name. There are times when this field is blank, other, or a different state than reality. In all three of these cases, because the city name is connected with a different state than the surrounding road segments, the Waze database assumes this is a different city so creates a separate color for the [[Layer#Cities|city layer]].


It helps to see the problem area by turning off all [[layers]] except for Cities and Road name. Next [[Map_Editor_Interface_and_Controls#Zoom_Control|zoom]] into the city name that does not appear to be in the center of the city area.
WME will prevent you from adding a city name to a segment if any segments in your state have the same city name, and they are more than a few miles away. The error message <b>“The highlighted road is too far from the city it was added to”</b> will be displayed when you save. This is done to prevent elongated [[Smudged city| City Smudges]] in WME and the client.
[[Image:DupeCity2.jpg|500px]]
{{Clear}}
Notice two things in the image:


1. The purple area directly above the selected street is pointing out the Waze system thinks this city is not the same as the surrounding area.
== Waze’s Original Solution to Prevent Duplication ==


2. In the edit areas on the left you can see the drop down box for the state is showing a blank is currently selected when it should be California.
Waze resolved duplicate city names when they launched the map three ways.
# When a small town was surrounded by a larger township of the same name, the smaller town was identified as <b>Foocity</b> and the larger municipality got the name <b>Greater Foocity Area</b>. Sometimes this happened even if the names didn't match.
# When the towns were separated by some distance, Waze appended a counting number behind the name. So you might see <b>Foocity (2)</b> and <b>Foocity (3)</b> on the map in addition to <b>Foocity</b>.
# Waze dumped the city name altogether, which is one reason you see gaps in the Cities layer and roads with no city name.


For each of the segments near the different colored city polygon, select each segment individually and correct the state name and press Apply. Then save changes.
None of these are elegant solutions. Each state will need to decide on a local solution if they want to clear duplicate names from their state, as there are a wide variety of municipal configurations in the USA.


You will not immediately see the city layer change. You have to wait for the next map update.
== Better Scheme for Removing Duplication ==


== Typographical error ==
As long as the city name differs by one character, you will not get the error message. But we don’t recommend kludgey fixes. The best way to clear duplication is to find something unique, but accurate, that identifies a municipality.
Sometimes the duplicated error is because there is a spelling error in one of the two entries.  
* Examples
** If a borough and a township share the same name, rename the township segments to read <b>Foocity Twp</b>.
** In Pennsylvania, we have several instances of three or more townships sharing the same name. So we append the county name to the township name, <b>Foocity, Countyname</b>, since that is how they are uniquely identified to the state government.


It helps to see the problem area by turning off all [[layers]] except for Cities and Road name. Next [[Map_Editor_Interface_and_Controls#Zoom_Control|zoom]] into the city name that does not appear to be in the center of the city area.
The simplest scheme is to resolve conflicts in this order:


Select the road closest to the incorrectly spelled city name and if that road name is actually incorrect update the name and select Apply. Also check some of the surrounding street segments to confirm if they are spelled correctly. Save changes.
1. If a postal area or CDP (Census Designated Place as found on the [http://www.census.gov/geo/maps-data/maps/2010tract.html Census Tract Maps]) and a city conflict, append something to the city name, since CDPs and Postal areas don’t have any other common appellation.
 
2. If a well-known city and a lesser-known city conflict, the most well-known keeps the unadorned name.
 
3. If all else is equal, choose one to keep the original name, and add the minimum clear suffix to alter the others.
 
== Changing or Merging an Entire City Name ==
 
Using mass editing tools to change a city name on all segments is strongly discouraged - mass editing tools can lead to errors and loss of data. Instead, to rename an entire city to a new name that is not used elsewhere in the state, contact a local State Manager and an editor of rank {{Rank|cityrename}}, who will be able to rename it. This change will affect all existing road segments and places to update to the new city name. If this cannot be done or a merge is requested, the correct procedure is to fill out the [[Forms#Cities_Form|Cities Form]] and follow up with your Regional Coordinator or Assistant Regional Coordinator with the request. The coordinator will then ask Waze to make the correction in their database. A side benefit is any polygon with the old city name will be removed at the same time.
 
== Cities Layer ==
=== Purpose ===
Currently, the cities layer in WME is only used to display the city name and polygon on the client and provide a location for client
warnings. It is also believed to be used when you  search for a city in WME. Some users have speculated that this layer will be used for native address search, but this has never been confirmed by Waze.
 
=== City Polygon Creation and Updating ===
 
Many of the city polygons were created by Waze at the original map import. They were not visible to editors in early versions of WME.
 
Waze runs a server process regularly that looks for new roads or road segments with changed city names. If the city name is new, a polygon will be created to cover all the segments with the same name. If a polygon with that name exists, Waze will sometimes expand or contract the polygon to match the new road locations. Experience has shown that many of the older polygons resist changes and remain the same shape, no matter what city name you apply to the roads. Waze has never explained this.
 
=== City Name and Polygon Removal ===
Waze runs a server process periodically that removes city polygons if there are no road segments with that name. Experience has shown that many of the older polygons are not removed by this process. Also, the old city name can remain on the map, even if the polygon is gone. Your Regional Coordinator can request that Waze remove these polygons and ghost names. The process is the same as [[Duplicate_cities#Changing_or_Merging_an_Entire_City_Name | Changing a City Name]].
 
[[Category:Waze operations]]

Latest revision as of 12:30, 28 March 2019

Information about duplicate city names in the USA.

Duplicate City Name Error

WME will prevent you from adding a city name to a segment if any segments in your state have the same city name, and they are more than a few miles away. The error message “The highlighted road is too far from the city it was added to” will be displayed when you save. This is done to prevent elongated City Smudges in WME and the client.

Waze’s Original Solution to Prevent Duplication

Waze resolved duplicate city names when they launched the map three ways.

  1. When a small town was surrounded by a larger township of the same name, the smaller town was identified as Foocity and the larger municipality got the name Greater Foocity Area. Sometimes this happened even if the names didn't match.
  2. When the towns were separated by some distance, Waze appended a counting number behind the name. So you might see Foocity (2) and Foocity (3) on the map in addition to Foocity.
  3. Waze dumped the city name altogether, which is one reason you see gaps in the Cities layer and roads with no city name.

None of these are elegant solutions. Each state will need to decide on a local solution if they want to clear duplicate names from their state, as there are a wide variety of municipal configurations in the USA.

Better Scheme for Removing Duplication

As long as the city name differs by one character, you will not get the error message. But we don’t recommend kludgey fixes. The best way to clear duplication is to find something unique, but accurate, that identifies a municipality.

  • Examples
    • If a borough and a township share the same name, rename the township segments to read Foocity Twp.
    • In Pennsylvania, we have several instances of three or more townships sharing the same name. So we append the county name to the township name, Foocity, Countyname, since that is how they are uniquely identified to the state government.

The simplest scheme is to resolve conflicts in this order:

1. If a postal area or CDP (Census Designated Place as found on the Census Tract Maps) and a city conflict, append something to the city name, since CDPs and Postal areas don’t have any other common appellation.

2. If a well-known city and a lesser-known city conflict, the most well-known keeps the unadorned name.

3. If all else is equal, choose one to keep the original name, and add the minimum clear suffix to alter the others.

Changing or Merging an Entire City Name

Using mass editing tools to change a city name on all segments is strongly discouraged - mass editing tools can lead to errors and loss of data. Instead, to rename an entire city to a new name that is not used elsewhere in the state, contact a local State Manager and an editor of rank a CM, who will be able to rename it. This change will affect all existing road segments and places to update to the new city name. If this cannot be done or a merge is requested, the correct procedure is to fill out the Cities Form and follow up with your Regional Coordinator or Assistant Regional Coordinator with the request. The coordinator will then ask Waze to make the correction in their database. A side benefit is any polygon with the old city name will be removed at the same time.

Cities Layer

Purpose

Currently, the cities layer in WME is only used to display the city name and polygon on the client and provide a location for client warnings. It is also believed to be used when you search for a city in WME. Some users have speculated that this layer will be used for native address search, but this has never been confirmed by Waze.

City Polygon Creation and Updating

Many of the city polygons were created by Waze at the original map import. They were not visible to editors in early versions of WME.

Waze runs a server process regularly that looks for new roads or road segments with changed city names. If the city name is new, a polygon will be created to cover all the segments with the same name. If a polygon with that name exists, Waze will sometimes expand or contract the polygon to match the new road locations. Experience has shown that many of the older polygons resist changes and remain the same shape, no matter what city name you apply to the roads. Waze has never explained this.

City Name and Polygon Removal

Waze runs a server process periodically that removes city polygons if there are no road segments with that name. Experience has shown that many of the older polygons are not removed by this process. Also, the old city name can remain on the map, even if the polygon is gone. Your Regional Coordinator can request that Waze remove these polygons and ghost names. The process is the same as Changing a City Name.