Minnesota/Cities and towns/Main: Difference between revisions View history

VisualWikitext
(*/Cities_and_towns/Main*/)
(updated link to city fix/remove form)
 
(6 intermediate revisions by 2 users not shown)
Line 2: Line 2:
------ DO NOT MODIFY ABOVE THIS LINE -------- DO NOT MODIFY ABOVE THIS LINE ------>  
------ DO NOT MODIFY ABOVE THIS LINE -------- DO NOT MODIFY ABOVE THIS LINE ------>  


{{RootPage2}} bases cities and towns on standard city line boundaries and not USPS standards. Where the city limits end, another city or township will begin.  
=== Overview / History ===
'''As of April 2018, {{RootPage2}} will begin to adopt new standards for primary segment city names''' that better aligns with regional & national standards. This is to maintain consistency on the map and provide the best experience for users searching rural addresses.  


{{RootPage2}} does show townships throughout the state. Keep in mind that many of these are named incorrectly. All township names should be [Township] Twp. It should not end in the full word Township or be called Greater [Township] Area.  
In {{RootPage2}}, when one incorporated city ends, another city or township will begin. Those living outside city limits in township areas may describe where they live by its actual township ("The Smiths live in Dahlgren Township over by the golf course") but in reality, this part of the vernacular doesn't have much bearing on how we drivers search for, navigate to, or provide directions for an actual address. ("It's at the Smith's house on 12034 Dahlgren Rd in Carver).  


If we see an error with a city, town, or township name, DO NOT correct the issue in the map itself. Correcting it in the map either will give you errors when you attempt or it will smudge cities. Even if you update every street in the township, the incorrect city name will still exist and will show both names on the live map.
Previous statewide guidance included some version of using the township name in the "City" field on the primary segment where corporate city limits ended, either as "[Township Name] Twp" or, simply, "[Township Name]" (""Dahlgren Twp"" or ""Dahlgren,"" as an example). Postal cities may have been added as additional alternates to applicable segments, but may not have been consistently addressed.  


If you see an issue, post it [http://www.waze.com/forum/viewtopic.php?f=259&t=128895 Here] and we will submit a report to fix the city name. Keep in mind that this is a very time-consuming process and averagely takes 2-3 months to show correctly on the editing map and another 1-2 months after that before the live map will see it.
=== Adding City Names to Segments in MN ===
In an effort to provide a consistent experience, clean labeling in the editor, and better ease of navigation for drivers, {{RootPage2}} will be adopting a standard similar to the rest of the Plains Region and much of the rest of the US:
* '''Inside city limits:''' use the actual city name on the primary segment name.
* '''Outside city limits:''' check [no city] on the primary segment name. Add the postal city with the primary road name and any additional alternates as alternates. For example:
** Primary: Main St W, [no city]
** Alt 1: Main St W, Carver
** '''Delete/ Do Not Use''': Main St W, Dahlgren Twp
** '''Delete/ Do Not Use''': Main St W, Dahlgren Township
** '''Delete/ Do Not Use''': Main St W, Greater Dahlgren Area


We currently are running an experiment with adding residential addressing as a place point using the USPS city as opposed to the township or city it is actually located.  We are verifying the negative implications of this and seeing if the positives outweigh the negatives.  If you see this on the map, please do not delete it or follow suit as this is an isolated test.


== Lock Standards ==
=== Correcting Errors / Removing Old Cities ===
If you an issue with a city name, particularly a duplicate city or improperly named township, please request its removal using  [https://docs.google.com/forms/d/e/1FAIpQLSd4CVeM2SNVCXQc04ufeOnXRgIMyAVcRKSrIKScrgbJLPJCkw/viewform this form]


{{Lock Standard State|MN}}
Please also bring the issue to the attention of your SM or RC, who can provide a second look at the issue as well as potentially help expedite response to your form submission.  Please DO NOT simply try to correct the issue on the map, which may cause additional errors or smudges in the city layer.


Note: Before locking these roads to these standards, you must verify that the [[Road_Naming_(USA)#Road_naming|name of the road]], [[Road_direction#Road_Direction|direction of the road]], and [[Turn_arrow#Turn_restrictions_.28allowed_turns.29|turn functionality]] is correct.  If this information is not correct, it should not be locked unless we are having issues with editors in the area.  The only exception here is Freeways due to the routing priority. Refer to [[Minnesota#Unlock_Requests|Unlock Requests]] if you need a section of road altered or unlocked to correct an issue.
<!---- [[Minnesota/Cities_and_towns#Update_City|Report Incorrect City Data]] -->
 
Additional: {{reflist}}
 
== Functional Class ==
 
You will hear the phrase Functional Class or FC a lot when it comes to the standard for [[Road_Types_(USA)#Importance_of_road_types|road types]].  According to the [http://www.fhwa.dot.gov/planning/processes/statewide/related/highway_functional_classifications/fcauab.pdf US Federal Highway Administration],  The concept of functional classification defines the role that a particular roadway segment plays in serving the flow of traffic through the network. Waze has its own interpretation of this system, but it utilizes the state's functional class map to help determine the road type to use.
 
Check out our [[Minnesota#Mapping_resources|Mapping Resources]] for knowledge on how to use the state's map system to find Functional Classifications Standards in Minnesota.  From that knowledge, use [[Road_types/USA#Quick_reference_chart|this chart]] to determine how the road should be classified using the Waze Standard. Minnesota follows this chart completely aside from [[Minnesota#Dirt_Roads|dirt or gravel]] roads in rural areas. This exception will be changed as soon as an unpaved road option exists in Waze.
 
If you have any questions about Functional Class, please use our [[Minnesota#Community|Community Resourses]] to reach out to gain further information.


<!---- DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ----
<!---- DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ----

Latest revision as of 19:40, 22 April 2018

 Press here to return to the Cities and towns section to see your changes 


Overview / History

As of April 2018, Minnesota will begin to adopt new standards for primary segment city names that better aligns with regional & national standards. This is to maintain consistency on the map and provide the best experience for users searching rural addresses.

In Minnesota, when one incorporated city ends, another city or township will begin. Those living outside city limits in township areas may describe where they live by its actual township ("The Smiths live in Dahlgren Township over by the golf course") but in reality, this part of the vernacular doesn't have much bearing on how we drivers search for, navigate to, or provide directions for an actual address. ("It's at the Smith's house on 12034 Dahlgren Rd in Carver).

Previous statewide guidance included some version of using the township name in the "City" field on the primary segment where corporate city limits ended, either as "[Township Name] Twp" or, simply, "[Township Name]" (""Dahlgren Twp"" or ""Dahlgren,"" as an example). Postal cities may have been added as additional alternates to applicable segments, but may not have been consistently addressed.

Adding City Names to Segments in MN

In an effort to provide a consistent experience, clean labeling in the editor, and better ease of navigation for drivers, Minnesota will be adopting a standard similar to the rest of the Plains Region and much of the rest of the US:

  • Inside city limits: use the actual city name on the primary segment name.
  • Outside city limits: check [no city] on the primary segment name. Add the postal city with the primary road name and any additional alternates as alternates. For example:
    • Primary: Main St W, [no city]
    • Alt 1: Main St W, Carver
    • Delete/ Do Not Use: Main St W, Dahlgren Twp
    • Delete/ Do Not Use: Main St W, Dahlgren Township
    • Delete/ Do Not Use: Main St W, Greater Dahlgren Area


Correcting Errors / Removing Old Cities

If you an issue with a city name, particularly a duplicate city or improperly named township, please request its removal using this form

Please also bring the issue to the attention of your SM or RC, who can provide a second look at the issue as well as potentially help expedite response to your form submission. Please DO NOT simply try to correct the issue on the map, which may cause additional errors or smudges in the city layer.


Retrieved from "https://beta.waze.com/wiki/Mauritius/index.php?title=Minnesota/Cities_and_towns/Main&oldid=164128"