|
|
| (13 intermediate revisions by 3 users not shown) |
| Line 1: |
Line 1: |
| − | Information about duplicate city names in the USA.
| + | {{TopLine}} |
| | + | <languages /><translate> |
| | | | |
| − | == Duplicate City Name Error == | + | ==WMEBR Filter== <!--T:1--> |
| | | | |
| − | <p>WME will prevent you from adding a city name to a segment if | + | <!--T:2--> |
| − | any segments in your state have the same city name, and they are more than a
| + | <i>WMEBR Filter</i> is a [[Scripts|script]] to filter the [[Place update request|PURs]] results on the [https://wmebr.info WMEBR website] to only show what we can handle.<br /> |
| − | 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 [[City_smudges | City Smudges]] in WME and the client.</p>
| |
| | | | |
| − | == Waze’s Original Solution ==
| + | <!--T:3--> |
| − | | + | * [https://www.waze.com/forum/viewtopic.php?f=819&t=263628&hilit=wmebr+filter+script Forum page] |
| − | <p>Waze resolved duplicate city names when they launched the | + | * [https://greasyfork.org/fr/scripts/370855-wmebr-filter Greasy Fork page] |
| − | map three ways.
| + | <br /> |
| − | # 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>.
| + | </translate> |
| − | #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>.
| + | __NOTOC__ |
| − | #Waze dumped the city name altogether, which is one reason you see gaps in the Cities layer and roads with no city name.</p>
| + | {{Bottomline}} |
| − | | |
| − | <p>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.</p>
| |
| − | | |
| − | == Better Scheme for Removing Duplication == | |
| − | | |
| − | <p>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 <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.</p>
| |
| − | | |
| − | <p>The simplest scheme is to resolve conflicts in this order:</p>
| |
| − | | |
| − | <p>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.</p>
| |
| − | | |
| − | <p>2. If a well-known city and a lesser-known city conflict, the most well-known keeps the unadorned name.</p>
| |
| − | | |
| − | <p>3. If all else is equal, choose one to keep the original name, and add the minimum clear suffix to alter the others.</p> | |
| − | | |
| − | == Changing an Entire City Name ==
| |
| − | | |
| − | <p>Using mass editing tools to change a city name on all segments
| |
| − | is strongly discouraged. The mass editing tools can lead to errors and loss of
| |
| − | data. The correct procedure is to contact your Region Coordinator with the old
| |
| − | city name, new city name and a permalink of the center of the area. 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. Merging two cities should also be handled the same way.</p>
| |
| − | | |
| − | == Cities Layer Purpose ==
| |
| − | | |
| − | <p>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. </p>
| |
| − | | |
| − | === City Polygon Creation and Updating ===
| |
| − | | |
| − | <p>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.
| |
| − | </p>
| |
| − | | |
| − | <p>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.</p>
| |
| − | | |
| − | === City Polygon Removal ===
| |
| − | | |
| − | <p>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. Your Regional Coordinator can request that
| |
| − | Waze remove these polygons.</p>
| |
