User:PesachZ/SyncScratch View history

VisualWikitext
m (Copying text of wiki page for coparison with the "Template:Lock Standard State" page)
m (Copying text of wiki page for coparison with the "Minnesota/Special roads/Main" page)
Line 1: Line 1:
<noinclude>
<!-- This page is only transcluded into (displayed on) the main page for this state. See more detailed instructions below. --><noinclude>{{:USA/CommonState/ReturnPurge|{{SubPage2}}}}<br/></noinclude><!--
{{Documentation}}
------ DO NOT MODIFY ABOVE THIS LINE -------- DO NOT MODIFY ABOVE THIS LINE ------>  
</noinclude>
=== Ramsey County Lettered Roads ===
<includeonly>{{#switch: {{uc:{{{1|}}}{{{st|}}}{{{ST|}}}{{{St|}}}{{{sT|}}}}}
The Ramsey County lettered roads are a special situation.  They do not get abbreviated with the letter.  For example County J should not be named CR-J or CH-J.
| NH
| VT
| MA
| RI
| CT
| ME
| NEW ENGLAND<!-- per Regional SM HO discussion with OrbitC on 2/11/16 https://www.waze.com/forum/viewtopic.php?f=945&t=177664&p=1328584#p1328582 -->
| NJ
| DE
| PA
| NORTHEAST = {{Locking Standard<!-- per Regional SM Hangout discussion with OrbitC https://www.waze.com/forum/viewtopic.php?f=569&t=177663 -->
    |title=Statewide
    |Fwy=5
    |Ramp=Highest rank of connected segments
    |MH=3
    |mH=3
    |PS=1 (Auto)
    |Street=1 (Auto)
    |Private=1 (Auto)
    |note={{Red|Do Not Mass Edit just to update locks to these standards}}, these can adjusted as you find while editing other aspects of the segments such as FC, speed limits, naming, etc.


Some segments still warrant higher locks and care should be taken when setting segment lock to these standards to look for and protect these special setups with higher locks. Some examples; segments which are part of [[Detour Prevention Mechanisms/USA|BDP]], [[Uturn prevention|U-turn prevention]], or using [[Glossary#mDL|micro-doglegs]], or other complex intersection setups.}}
These roads have a long history. They were laid out by Ramsey County on unincorporated land north of St Paul before most of the cities we know today were created. [http://www.historicmapworks.com/Map/US/487761/Index+Map+001/Ramsey+County+1931/Minnesota/ See a historical 1931 map here].  As cities incorporated land, many of them kept these names even though they were no longer county owned and maintained roads.  As far as Ramsey County is concerned, if it is a county owned road, it will have a #. For example County J is Ramsey County 1.  All the official blue 5-sided Ramsey county sign's only have the numbered routes.  Nowhere is there a letter on a blue shield sign (in Ramsey County).  So that's why we don't abbreviate them.  CR- should eventually make the white county sign, and CH- should eventually make the blue county sign, The lettered roads never appear on a blue or white sign, so they do not get the CR- or CH- abbreviation.  Also some of these are not even county owned roads so they don't get upgraded to primary street by default either.  For example, [https://www.waze.com/editor/?env=usa&lon=-93.13445&lat=45.03588&layers=5&zoom=9 County D at this link] is a city road maintained by the cities of Roseville and Shoreview who have decided to leave the road named as County Rd D.  It is not a Ramsey County owned or maintained road and has no white or blue county highway signs.  So it is named "County D" to match the street signs and is classed as a street classification.  It is not upgraded to a primary street because it is not a real "County Road."
| NY = {{Locking Standard <!-- https://www.waze.com/forum/viewtopic.php?f=569&t=177663 -->
    |title=NYC Only
    |Fwy=5|Ramp=Highest rank of connected segment|MH=5|mH=4|PS=3|Street=1 (Auto)
    |title2=Everywhere Else
    |MH2=3|mH2=3|PS2=1 (Auto)|Street=1 (Auto)|Private=1 (Auto)
    |note={{Red|Do Not Mass Edit just to update locks to these standards}}, these can adjusted as you find while editing other aspects of the segments such as FC, speed limits, naming, etc.


Some segments still warrant higher locks and care should be taken when setting segment lock to these standards to look for and protect these special setups with higher locks. Some examples; segments which are part of [[Detour Prevention Mechanisms/USA|BDP]], [[Uturn prevention|U-turn prevention]], or using [[Glossary#mDL|micro-doglegs]], or other complex intersection setups.}}<!--A/p wiki-->
One bit of trivia since it is often asked, where are the missing letters?  County A was where Larpenter Ave is today and County G was where Highway 96 is today.
| TX = {{Locking Standard
  |lede=In Texas we have a set minimum standard for locking roads based on segment type. Any road of a certain segment type must be locked '''at least''' to the rank (level) in the chart below. Roads may be locked higher for protection and special situations (areas with construction, tricky design, frequent mistakes, imaging inaccuracies, and the like), but should not be locked lower. If you find a road locked to a higher level than its minimum, please leave it locked no lower than that level when you have finished editing.
  |title=Lock Level
  |Fwy=5
  |Ramp=4
  |MH=4
  |mH=3
  |PS=2
  |Private=2
  |Street=Automatic (1)}}


| CA = {{Locking Standard
=== Other drivable roads ===
  |title=Metro Areas
 
  |title2=Rural
==== Dirt Road / 4X4 Trail[[File:Service road.png|200px|Service road.png]] ====
  |Fwy=5
 
  |Ramp=5
{{mbox
  |MH=3
| type = important
  |MH2=2
| text = Minnesota has different interpretations of Dirt Roads than many other locations. Even veteran editors need to pay attention to this section!
  |mH=2
  |PS=2
  |Street=1}}
| UT = {{Locking Standard <!-- Per Jemay, 2015-11-19. Temporary lowering from 54-4/3-3/2-2 to 4H322 per herrchin/AoTB/Bretmcvey 2016-06-01-->
  |caption=Utah locking standard
  |title=Statewide
  |Fwy=4
  |Ramp=Highest rank of connected segments
  |MH=3
  |mH=2
  |PS=2
  |Street=1
  |lede=In {{RootPage2}} we have a set minimum standard for locking roads based on segment type. Any road of a certain segment type must be locked '''at least''' to the rank (level) in the chart below. Roads may be locked higher for protection and special situations (areas with construction, tricky design, frequent mistakes, imaging inaccuracies, and the like), but should not be locked lower.
  }}
| NV = {{Locking Standard <!-- As per State Forum discussions, SuperDave1426, 2015-01-28 -->
  |title=Urban Areas
  |title2=Rural Areas
  |Fwy=5|Fwy2=4
  |Ramp=5|Ramp2=4
  |MH=3
  |mH=2
  |PS=2
  |Street=Automatic (1)
  |Private=Automatic (1)
  |PLR=Automatic (1)
  }}
| CO = {{Locking Standard <!-- per Random sample from the map - 2015-11-25 -->
  |Fwy=5|Ramp=Highest Rank of Connected Segment|MH=3|mH=2|PS=2|Street=1}}
| NM
| SOUTHWEST = {{Locking Standard <!-- per Jemay - 2015-11-25 -->
  |Fwy=5|Ramp=4|MH=4|mH=3|PS=2|Street=1
  |lede=Actual locks used may be more or less than values in the table, depending on area circumstance. Please consult RC, SM, or appropriate AM for guidance.
}}
}}
| AZ = {{Locking Standard <!-- per nnote - 2017-01-25 -->
  |Fwy=4|Ramp=4|MH=4|mH=3|PS=2|Street=1}}




| MO = {{Locking Standard <!-- a/p BlueTiger68 MO SM -->
[[File:MNdirtrd.jpg|300px|left]]In the state of {{RootPage2}}, most unpaved roads are considered [[Road_types/USA#Dirt_Road_.2F_4X4_Trail|dirt roads]].  Knowing this will help you create the correct road levels. Undrivable roads should not be mapped, should be restricted, or should be listed as a trail instead and not be connected to any functional roads.  Even though 4x4 is in the title, we will only use dirt roads for standard gravel or dirt roads that most vehicles can drive on.  Keep in mind that because of the way Waze handles dirt roads, we will not use the dirt road class in the city limits of any town.  Any in-town gravel roads will be streets.
  |title=Statewide|Fwy=4|Ramp=4|MH=3|mH=3|PS=2|Street=1}}
 
Because most likely people in {{RootPage2}} feel a gravel road is a dirt road, we will use Dirt Road for both examples.  Please be aware of any of these dirt roads that are minimum maintenance roads as these roads should have [[Scheduled_restrictions#Segments|restrictions]] in place for winter months.
 
[[File:Dirtroad.PNG|300px|right]]
 
The reason the dirt roads classification is important is because a user can decide to not be sent on dirt roads or to only be sent on dirt roads for short distances in the settings of the Waze App. 
 
Keep in mind that if the person does allow for dirt roads, Waze will treat the road as a Primary Street so do not try to make an exception to well maintained dirt roads as a street or you will cause the driver to be directed on undesirable roads. Yes, that's right, a dirt road can be seen as a higher priority than a street! This is very important in rural areas where the Street Category should only be used on very short road segments that are paved.  In towns, the Dirt Road Category should be rarely used and an unpaved road should be considered a street or a private road.
 
==== Parking Lot Road[[File:Service road.png|200px|Service road.png]] ====
 
[[File:Parklotrhmmn.png|right|300px]]
Parking lots roads are essential to navigating users to the proper destinations.  It also helps to properly exit a parking lot.  Follow these examples to creating parking lots correctly. Click the image to the right to see a well-designed parking lot section.
 
* Simple is best. Do not map every lane
* Map the main entrances from the roads outside the parking lot
* Map lanes that run along storefronts
* Map lanes that run along main roads outside the parking area
* Map primary lanes that serve to get people from one area of the lot to another
 
For for information about mapping parking lots, follow this [[Best_map_editing_practice#Parking_Lots|article]]


| KS = {{Locking Standard <!-- KC-guardrail KS SM -->
==== Private Road[[File:Service road.png|200px|Service road.png]] ====
  |title=Statewide|Fwy=4|Ramp=4|MH=3|mH=3|PS=2|Street=1}}


| MN = {{Locking Standard
[[File:Pi gated-community1.jpg|right|300px|Pi gated-community1.jpg]]
    |title=Urban<ref>This includes any city over [http://www.city-data.com/city/Minnesota.html 6,000 people]</ref>|Fwy=5|Ramp=Highest rank of connected segments|MH=4|mH=3|PS=2<ref>Increase lock level to 3 if [[House_numbers|House Numbering]] is correct</ref>|Street=1<ref>Increase lock level to 2 if [[House_numbers|House Numbering]] is correct</ref>
    |title2=Rural<ref>This includes any area considered a township or a small town</ref>|Fwy2=5|Ramp2=Highest rank of connected segments|MH2=3|mH2=2|PS2=2|Street2=1<ref>Increase lock level to 2 if [[House_numbers|House Numbering]] is correct</ref>
|lede=In {{RootPage2}} we have a set minimum standard for [[Best_map_editing_practice#Locking_Segments|locking roads]] based on the segment type. Any road of a certain segment type must be locked to '''at least''' the [[Your_Rank_and_Points#Map_Editing_Rank|rank (level)]] in the chart below. Roads may be locked higher for protection and special situations (areas with construction, tricky design, frequent mistakes, imaging inaccuracies, and the like), but should not be locked lower.


A great time to implement these locks is while performing the [[Functional_Classification|FC Upgrade]] of an area. Lock the roads based on the type after they've been set to [[Road_types/USA#Quick_reference_chart|FC standards]].
Private Roads should follow the Wiki Example on [[Private_road#Private_Road|Private Roads]].  Please be very limited on using this for [[Driveways|driveways]] as, for the most part, these should not be mapped at all. 
 
Keep in mind that on the Waze App, a private road will look like a street. Nothing looks more off than a bunch of streets connected to a dirt road. 
 
If you are adding a private road for a private housing section, make sure house numbering is correct or there is a place point or area within a private road section. This area will still be able to be navigated to the correct destination as long as it has a proper address to navigate to. Pay attention to [[Private_Installations#Problem_Definition|this article]] for more information.
 
In the case of very long driveways, it may helpful to a driver to see the driveway mapped on the client app or even necessary for Waze to determine how to reach the destination. In those cases it may be prudent to add a road. See the article on [[Driveways]] for more information.
 
==== Alleyways[[File:Service road.png|200px|Service road.png]] ====
 
Avoid drawing alleyways unless it is considered a street by the general public.  Most alleyways should not be used to direct traffic and will cause unneeded [[Node_penalties#Junction_penalties|nodes]] in the road that can cause roads connected to the alleyways to be less desirable. Most alleyways that would be mapped will use the Private Road classification.
 
[[File:Pizzalola.png|300px|left]]
 
This is a good example of where alleyways will be mapped.  This is in South Minneapolis at the corner of Xerxes Ave S and W 56th St.  It is also the location of Pizzeria Lola.  The parking at this location is on the side of the Cavé Vin building.  It is a one-directional section and the only way to leave is through an alleyway. In this case, you would create the section as a Private Road and you only map out what is needed to enter the parking lot and exit; however, you would not need to map any other section of that alleyway.
 
==== Roundabouts [[Image:Round.png |50px]] ====
 
{{RootPage2}} has been adding [[Road_types/USA#Roundabouts|roundabouts]] in many locations throughout the state.  It is important to note that most roundabouts should only have three to four connections or it will sound confusing to a driver.  Following this [https://www.waze.com/editor/?env=usa&lon=-93.94724&lat=44.16858&layers=2981&zoom=4 Example] will give proper turn information and roundabout icons on the screen.  If you would use multiple-point access, it instead will say the exit number such as, "At the Roundabout, take the 3rd exit".
[[File:Roundabouts.png|400px|right]]
This is an indication of what a user of Waze should see on an upcoming Roundabout.  It is clear at showing the direction of the turn.  It also will verbally say what is referenced on the signage such as "At the Roundabout, Continue Straight" or "turn left". This is the {{RootPage2}} Standard for creating and editing Roundabouts.
 
 
 
[[File:Roundboutmn2.png|400px|left]]
 
This is how it looks when more than four exit points occur.  It does not give clear guidance to the driver on what way to go aside from the highlighted road ahead. This should be avoided, Only add multiple connections per side if the signs clearly mark Exit numbers (Commonly seen on signs showing 5 or more exit points).
 
 
 
Roundabouts will use the same functional class of the main route traveling through the roundabout.  Follow [[Creating_and_Editing_a_roundabout#Road_type|This Article]] for more information.
 
If at all possible, drive through a roundabout after it has been created or updated.  Verify that it seems to give correct information.
 
==== HOT & Hov Roads/Lanes ====
[[Image:Hovmn.png|right]]
High Occupancy Toll or High-occupancy Vehicle roads are not yet handled 100% by Waze as of yet, but we will still map these out to prepare for that time.
 
These roadways have the following features:
* These lanes/roads allow both toll traffic and HOV traffic to traverse the same lanes.
* There are no toll plazas or booths for paying by cash. All tolls are paid electronically to maintain traffic speed.
* Entrances and exits to the HOT lanes are limited to help maintain high speeds.
* There are no entrance/exit combinations where the toll fare rules don't apply.
* Tolls are discounted or waived for users that meet High Occupancy Vehicle (HOV) requirements. These requirements may change based on time of day.
 
To avoid traffic from entering this section, all entrance ramps will be will be restricted as in [[Carpool,_HOV,_Transit_lanes#Example_configurations|this article]]. From there, nothing will be restricted so if a user decides to take this route, he or she will be directed correctly.
 
This will all be changing shortly as we find a better way to develop these roads.
 
==== Bus or Cab Only Lanes[[File:Service road.png|200px|Service road.png]] ====
 
When a road or lane is designated for bus or cab use only, mark that road segment(s) as a '''Private Road''' to prevent the Waze router from using that segment(s) for general traffic, since the majority of the users will not be able to use that lane. It is also advisable to set the turn restrictions to prevent turns into that segment(s), but permit turns exiting the segment.
 
If a road is one-way but allows bus or cab traffic to flow the other direction, leave the road as one-way with the normal flow of traffic. There is no need to create a second road traveling the opposite direction for the bus and cab-only traffic.
 
==== Emergency Vehicle and DOT Service Roads [[File:Service road.png|200px|Service road.png]] ====
 
[[File:Emergency.jpg|right|300px|Emergency.jpg]] "Emergency and Authorized Vehicles Only" and DOT Service Roads are to be treated as Non-drivable roads. These are found primarily through the median of divided highways to connect opposite direction lanes. In most cases, these should not be mapped at all. If mapped, they should not be connected to any drivable road, with properties set to road type Private Road, and lock the segment at as high a rank as possible, up to rank 5. {{clear}}
 
=== Non-drivable roads ===
 
==== Railroad [[File:Service road.png|200px|Service road.png]] ====
 
[[File:RailroadTracksVanishingPoint.jpg|right|300px|RoadPicN11.jpg]]
 
 
Railroads are not yet added to the map, but these can be added to prepare the maps for when it is.  Mapping the tracks allows Waze to recognize spurious speed data from people Wazing on the train and prevent it from corrupting speed data for the adjacent road.
 
 
 
 
{{mbox
| type = important
| text = Please notice that railroads have changed from previous interpretations of railroad mapping.  Even veteran editors need to pay attention to this section!
}}
 
 
* Elevation will be set to the same elevation standards as a drivable road. When tracks junction a road on the ground, the Elevation should be set to Ground.
* If the railroad crosses a segment of road, it should be connected to the road to so the historical data for the rail crossing will be more accurate.
* Always select "None" for the city name. This avoids [[Smudged_city#Overview|city smudging]].
* Set railroad to 2-way directionality and Restrict turns ''to'' and ''from'' the railroad segments.
* Follow the [http://fragis.fra.dot.gov/Apps/GISFRASafety/ Federal DOT Railroad GIS] to verify the owner of the rail line to help on naming of the segment. Use the acronyms under RROWNER1 to help on naming.
* Name each segment using the rail owner name acronyms or abbreviations railroad.  For example, Twin Cities & Western Railroad uses TCWR. We would name this section TCW Railroad.  We leave off the R in the acronym because it would be redundant to say, Twin Cities & Western Railroad Railroad.
* Canadian Pacific uses the acronym CPRS, but it is more know as CP, so it will be called CP Railroad
*Do not map every piece of parallel track, such as in sidings or yards, or industrial spurs that don't cross any roads. Your work may otherwise be seen as clutter, much like mapping every parking lot row.
* Lock all railroads to a Level 2
* Keep segment lengths under 10,000 meters (32,808 Ft) – the longer the segment length, the more sluggish the editor is to respond to changes.
* Read [[Road_types/USA#Railroad|this section]] for more information about railroads.
 
==== Runway/Taxiway[[File:Service road.png|200px|Service road.png]] ====
[[File:Aelrwmn.png|right|250px]]
We will map all airports runways such:
 
* These roads will not connect to any drivable sections
* The runways will not be connected to each other
* Always select "None" for the city name. This avoids [[Smudged_city#Overview|city smudging]].
* Using [http://en.wikipedia.org/wiki/List_of_airports_in_Minnesota this article] we will find the airport code.  We will use the [http://en.wikipedia.org/wiki/International_Air_Transport_Association IATA] code unless the airport does not have one, then we will revert to the [http://en.wikipedia.org/wiki/International_Civil_Aviation_Organization ICAO] code.
* After finding the code, we will use [http://www.airnav.com/airports/ this] to find the runway numbers for the airport.
* Most of the time, you will see the number of the runway at the beginning and end of each runway from the aerial views.
* Name each runway as such: [Airport Code] Runway [x-x] ... for example, in the image to the right, you will see the runways for Albert Lea Municipal Airport.  The IATA code for this airport is AEL and it has two runways including Runway 5/23 & Runway 17/35 so one will be named "AEL Runway 5-23" and the other AEL Runway 17-35".
 
Please follow this Wiki article on [[Runway#Runway.2FTaxiway|Runways]] for information about how to set runways correctly.  These roads should be locked to the same standard as Airport Area itself.
 
==== Ferry [[File:Service road.png|200px|Service road.png]] ====
 
{{mbox
| type = warning
| text = The Ferry Road type is not to be used at this time. '''Do not use the Ferry Road type for any purpose.''' See [[ferries]] page for more information on how to map ferries.
}}
}}


| WV = {{Locking Standard  <!-- 2015-07-06, stephenr1966, as discussed within state -->
==== Walking Trails [[File:Service road.png|200px|Service road.png]] ====
  |caption=West Virginia Locking Rank Standard Guideline
 
  |Fwy=5|Ramp=4|MH=3|mH=2|PS=1
[[File:RoadPicN9.jpg|right|300px|RoadPicN9.jpg]]
  |lede=Actual locks used may be more or less than values in the table below, depending on area circumstance
 
    Please consult RC, SM, or appropriate AM for guidance
Because Waze currently only supports navigation for drivers and not walkers or bikers at all, we will not be drawing any of these types of roads.  Please delete any of these types of roads that you find.  If you find automatically set URs claiming a road is indicated to be be present, Please fill out the form located [//docs.google.com/forms/d/e/1FAIpQLSekzNg6aMKuxgz2fASws5Cjzadho9BLVKpHsZluWJgL446EyQ/viewform?c=0&w=1&usp=send_form Here] and choose Second Set of Eyes so a high level editor can check out the situation.
    }}
 
| VA = {{Locking Standard
==== Pedestrian Boardwalks [[File:Service road.png|200px|Service road.png]] ====
  |caption=Virginia Locking Rank Standard Guideline
 
  |title=Urban|Fwy=5|MH=4|mH=3|PS=2
Because Waze currently only supports navigation for drivers and not walkers or bikers at all, we will not be drawing any of these types of roads.  Please delete any of these types of roads that you find.  If you find automatically set URs claiming a road is indicated to be be present, Please fill out the form located [//docs.google.com/forms/d/e/1FAIpQLSekzNg6aMKuxgz2fASws5Cjzadho9BLVKpHsZluWJgL446EyQ/viewform?c=0&w=1 Here] and choose Second Set of Eyes so a high level editor can check out the situation.
  |title2=Rural|MH2=3|mH2=2|PS2=1
 
  |lede=Actual locks used may be more or less than values in the table below, depending on area circumstance
==== Stairway [[File:Service road.png|200px|Service road.png]] ====
    Please consult RC, SM, or appropriate AM for guidance
 
    }}
Stairways will not be added to Waze maps in Minnesota at all.  Please delete any of these sections that you find added to the map
| WASHDC = {{Locking Standard
 
  |caption=Washington, DC Locking Rank Standard Guideline
 
  |Fwy=5|MH=4|mH=3|PS=2
== Speed Limits ==
  |lede=Actual locks used may be more or less than values in the table below, depending on area circumstance
 
    Please consult RC, SM, or appropriate AM for guidance
Minnesota primarily follows the USA Speed Limits wiki: [[Speed_limits/USA | USA Speed Limits Wiki]] with some clarifications
    }}
 
| SOUTHERN = {{Locking Standard
=== Ramp Speed Limits ===
  |caption=Standard for locking roads in the southeast region:
For ramps that are for accelerating to a road with a higher speed limit, use the higher speed limit of the destination road that the ramp goes to.
  |Fwy=5|Ramp=5|MH=5|mH=4|PS=3
 
  |lede=
For ramps that go from a higher speed limit to a lower speed limit such as a freeway off ramp, do not place any speed limit on the ramp.
    There are some cases that do not adhere to this standard, such as military base gates (6), and any theme park type areas in Orlando (5/6).
 
  }}
For ramps where the start and end have the same speed limit, keep the same speed limit on the ramp.
| PR
 
| VI
Do not use advisory speed limits that are black text on yellow signs.
| AS
 
| GUAM
=== Other Minnesota Specific Speed Limit details ===
| NMI
 
| TERRITORIES = {{Locking Standard|title=Statewide|Fwy=5|Ramp=4|MH=4|mH=3|PS=2|Street=1}}<!-- Per nnote, RC-->
The MN state laws for default unposted speed limits statewide are;
| OK = {{Locking Standard|title=Statewide|Fwy=5|Ramp=Highest rank of connected segment|MH=4|mH=3|PS=2|Street=1}}
*Alleyways and mobile home parks <b>10 mph</b> unless otherwise posted.
| MD = {{Locking Standard <!-- a/p Kodi, nzahn1 SMs -->
*Urban residential roads <b>30 mph</b> unless otherwise posted.
  |title=Urban
*Rural roads <b>55 mph</b> unless otherwise posted.
  |title2=Rural
 
  |Fwy=5|Fwy2=4
Check with your Area or State Managers for clarification if needed.
  |Ramp=5|Ramp2=4
  |MH=3|MH2=2
  |mH=2
  |PS=2
  }}
| MIDATLANTIC = {{Locking Standard
  |title=Two-Way
  |Fwy=5
  |Ramp=4
  |MH=4
  |mH=3
  |PS=2
  |Street=1
  |title2=One-Way
  |PS2=3
  |Street2=2}}


| MI = {{Locking Standard
  |caption=Michigan locking standard
  |title=Urban
  |title2=Rural
  |Fwy=5
  |Ramp=Highest rank of connected segment
  |MH=3
  |mH=2|mH2=3
  |PS=2
  }}


| WI = {{Locking Standard
  |title=Statewide
  |Fwy=5|Ramp=Highest rank of connected segment|MH=3|mH=2|PS=2|Street=1
  |note=These are minimums and, for protection, certain segments may be set at higher lock levels.  In these cases, please contact the last editor or a {{RootPage2}} SM before editing the segments.  Once changes have been made and verified, the locks should be returned to their elevated levels, unless standard levels are approved by a {{RootPage2}} SM}}<!-- per GHO KB_Steveo, 2015-12-26 -->
| KY = {{Locking Standard
    |title=Statewide
    |Fwy=5|MH=4|mH=3|PS=2
    |note=These are minimums and, for protection, certain segments may be at higher lock levels. Locks should be applied after the segments are correct. Remember you are putting your name on it, make sure it is correct.}}
| NC = {{Locking Standard
    |title=Statewide
    |Fwy=5|MH=4|mH=3|PS=2
    |note=Certain areas may be locked higher than the above minimums. Please do not lower locks unless approved by the RC or a {{RootPage2}} SM.}}
| SC = {{Locking Standard
    |title=Statewide
    |Fwy=5|MH=4|mH=3|PS=2
    |note=Certain areas may be locked higher than the above minimums. Please do not lower locks unless approved by the RC or a {{RootPage2}} SM.}} <!-- a/p crazycaveman SC SM -->
| TN = {{Locking Standard
    |title=Statewide
    |Fwy=5|MH=4|mH=3|PS=2}}
| ND = {{Locking Standard <!-- As per bretmcvey 2016-04-26 -->
    |title=Statewide
    |Fwy=4
    |Ramp=4
    |MH=3
    |mH=3
    |PS=2
    |Street=1}}
| WY = {{Locking Standard <!-- Preliminary proposal subject to discussion and approval - TheChrisK, 2015-12-18 -->
  |title=Statewide
  |Fwy=4
  |Ramp=4
  |MH=3
  |mH=2
  |PS=2
  |Street=1
  |note=Certain roads may be locked higher than the above minimums. Please do not lower locks unless approved by the RC or a {{RootPage2}} SM.}}
| AK = {{Locking Standard
<!--per HO discussion with AlanOfTheBerg and AK state manager-->
|title=Statewide|Fwy=4|Ramp=4|MH=3|mH=2|PS=2|Street=1|PLR=2{{ref|PLR}}|append={{note|PLR|1}}This rule should primarily apply to LARGE parking lots such as shopping malls/centers/plazas, tourist attractions/sports/music venues, large office buildings and schools/colleges.}}
| OR = {{Locking Standard <!--As confirmed by AlanOfTheBerg-->
  |title=Statewide
    |Fwy=4
    |Ramp=4
    |MH=3
    |mH=2
    |PS=2
    |Street=1}}
|lede=In {{RootPage2}} we have a set minimum standard for [[Best_map_editing_practice#Locking_Segments|locking roads]] based on the segment type. Any road of a certain segment type must be locked to '''at least''' the [[Your_Rank_and_Points#Map_Editing_Rank|rank (level)]] in the chart below. Roads may be locked higher for protection and special situations (areas with construction, tricky design, frequent mistakes, imaging inaccuracies, and the like), but should not be locked lower.


A great time to implement these locks is while performing the [[Functional_Classification|FC Upgrade]] of an area. Lock the roads based on the type after they've been set to [[Road_types/USA#Quick_reference_chart|FC standards]].<!--A/p wiki-->
<!---- DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ----
| = {{Mbox|type=critical|text={{Red|Error: The Lock Standard State template requires a state/province abbreviation or other equivalent; none was supplied, so no locking scheme can be generated}}}}
-------------------------------------------------------------------------------------
| {{Mbox|type=critical|text={{Red|The Lock Standard State template cannot display the locking scheme because it does not recognize the state/province/region specified: {{{1|}}}{{{st|}}}{{{ST|}}}{{{St|}}}{{{sT|}}}}}}}
---- This page is only transcluded into (displayed on) the main page for this state.
}}</includeonly>
---- It directly follows the common guidelines applicable to all states. When this
---- page is present (even if blanked), it displaces any optional code that might be
---- in that section.
---- If the original optional code from the main page for this section is still
---- desired, it can be restored by adding the following code to the first line
---- between the "DO NOT MODIFY" lines on this page:
----  {{:USA/CommonState/Special roads|optional}}
----
-------------------------------------------------------------------------------------
---- If there will be a full page for this section, use code similar to the wording
---- below to provide a hyperlink to that page. When creating the full page, use the
---- link on the talk page to ensure the preload data is provided to help with
---- formatting the page. Don't just use the red link from this section once it is
---- saved.
----
See [[{{BasePage2}}/Special roads]] for guidance in {{RootPage2}} that may not be universal to all other states.
----
-------------------------------------------------------------------------------------
---- This section has three possible purposes:
---- 1. It is only providing a hyperlink to the full page for this section.
---- 2. It is only providing some unique guidance for this state that differs from
---- other states.
---- 3. It is intentionally wiping out the general optional content for this section
---- for this state.
------------------------------------------------------------------------------------>

Revision as of 04:00, 16 February 2017

 Press here to return to the SyncScratch section to see your changes 


Ramsey County Lettered Roads

The Ramsey County lettered roads are a special situation. They do not get abbreviated with the letter. For example County J should not be named CR-J or CH-J.

These roads have a long history. They were laid out by Ramsey County on unincorporated land north of St Paul before most of the cities we know today were created. See a historical 1931 map here. As cities incorporated land, many of them kept these names even though they were no longer county owned and maintained roads. As far as Ramsey County is concerned, if it is a county owned road, it will have a #. For example County J is Ramsey County 1. All the official blue 5-sided Ramsey county sign's only have the numbered routes. Nowhere is there a letter on a blue shield sign (in Ramsey County). So that's why we don't abbreviate them. CR- should eventually make the white county sign, and CH- should eventually make the blue county sign, The lettered roads never appear on a blue or white sign, so they do not get the CR- or CH- abbreviation. Also some of these are not even county owned roads so they don't get upgraded to primary street by default either. For example, County D at this link is a city road maintained by the cities of Roseville and Shoreview who have decided to leave the road named as County Rd D. It is not a Ramsey County owned or maintained road and has no white or blue county highway signs. So it is named "County D" to match the street signs and is classed as a street classification. It is not upgraded to a primary street because it is not a real "County Road."

One bit of trivia since it is often asked, where are the missing letters? County A was where Larpenter Ave is today and County G was where Highway 96 is today.

Other drivable roads

Dirt Road / 4X4 TrailService road.png

 Minnesota has different interpretations of Dirt Roads than many other locations. Even veteran editors need to pay attention to this section!


In the state of PesachZ, most unpaved roads are considered dirt roads. Knowing this will help you create the correct road levels. Undrivable roads should not be mapped, should be restricted, or should be listed as a trail instead and not be connected to any functional roads. Even though 4x4 is in the title, we will only use dirt roads for standard gravel or dirt roads that most vehicles can drive on. Keep in mind that because of the way Waze handles dirt roads, we will not use the dirt road class in the city limits of any town. Any in-town gravel roads will be streets.

Because most likely people in PesachZ feel a gravel road is a dirt road, we will use Dirt Road for both examples. Please be aware of any of these dirt roads that are minimum maintenance roads as these roads should have restrictions in place for winter months.

The reason the dirt roads classification is important is because a user can decide to not be sent on dirt roads or to only be sent on dirt roads for short distances in the settings of the Waze App.

Keep in mind that if the person does allow for dirt roads, Waze will treat the road as a Primary Street so do not try to make an exception to well maintained dirt roads as a street or you will cause the driver to be directed on undesirable roads. Yes, that's right, a dirt road can be seen as a higher priority than a street! This is very important in rural areas where the Street Category should only be used on very short road segments that are paved. In towns, the Dirt Road Category should be rarely used and an unpaved road should be considered a street or a private road.

Parking Lot RoadService road.png

Parking lots roads are essential to navigating users to the proper destinations. It also helps to properly exit a parking lot. Follow these examples to creating parking lots correctly. Click the image to the right to see a well-designed parking lot section.

  • Simple is best. Do not map every lane
  • Map the main entrances from the roads outside the parking lot
  • Map lanes that run along storefronts
  • Map lanes that run along main roads outside the parking area
  • Map primary lanes that serve to get people from one area of the lot to another

For for information about mapping parking lots, follow this article

Private RoadService road.png

Pi gated-community1.jpg
Pi gated-community1.jpg

Private Roads should follow the Wiki Example on Private Roads. Please be very limited on using this for driveways as, for the most part, these should not be mapped at all.

Keep in mind that on the Waze App, a private road will look like a street. Nothing looks more off than a bunch of streets connected to a dirt road.

If you are adding a private road for a private housing section, make sure house numbering is correct or there is a place point or area within a private road section. This area will still be able to be navigated to the correct destination as long as it has a proper address to navigate to. Pay attention to this article for more information.

In the case of very long driveways, it may helpful to a driver to see the driveway mapped on the client app or even necessary for Waze to determine how to reach the destination. In those cases it may be prudent to add a road. See the article on Driveways for more information.

AlleywaysService road.png

Avoid drawing alleyways unless it is considered a street by the general public. Most alleyways should not be used to direct traffic and will cause unneeded nodes in the road that can cause roads connected to the alleyways to be less desirable. Most alleyways that would be mapped will use the Private Road classification.

This is a good example of where alleyways will be mapped. This is in South Minneapolis at the corner of Xerxes Ave S and W 56th St. It is also the location of Pizzeria Lola. The parking at this location is on the side of the Cavé Vin building. It is a one-directional section and the only way to leave is through an alleyway. In this case, you would create the section as a Private Road and you only map out what is needed to enter the parking lot and exit; however, you would not need to map any other section of that alleyway.

Roundabouts

PesachZ has been adding roundabouts in many locations throughout the state. It is important to note that most roundabouts should only have three to four connections or it will sound confusing to a driver. Following this Example will give proper turn information and roundabout icons on the screen. If you would use multiple-point access, it instead will say the exit number such as, "At the Roundabout, take the 3rd exit".

This is an indication of what a user of Waze should see on an upcoming Roundabout. It is clear at showing the direction of the turn. It also will verbally say what is referenced on the signage such as "At the Roundabout, Continue Straight" or "turn left". This is the PesachZ Standard for creating and editing Roundabouts.


This is how it looks when more than four exit points occur. It does not give clear guidance to the driver on what way to go aside from the highlighted road ahead. This should be avoided, Only add multiple connections per side if the signs clearly mark Exit numbers (Commonly seen on signs showing 5 or more exit points).


Roundabouts will use the same functional class of the main route traveling through the roundabout. Follow This Article for more information.

If at all possible, drive through a roundabout after it has been created or updated. Verify that it seems to give correct information.

HOT & Hov Roads/Lanes

High Occupancy Toll or High-occupancy Vehicle roads are not yet handled 100% by Waze as of yet, but we will still map these out to prepare for that time.

These roadways have the following features:

  • These lanes/roads allow both toll traffic and HOV traffic to traverse the same lanes.
  • There are no toll plazas or booths for paying by cash. All tolls are paid electronically to maintain traffic speed.
  • Entrances and exits to the HOT lanes are limited to help maintain high speeds.
  • There are no entrance/exit combinations where the toll fare rules don't apply.
  • Tolls are discounted or waived for users that meet High Occupancy Vehicle (HOV) requirements. These requirements may change based on time of day.

To avoid traffic from entering this section, all entrance ramps will be will be restricted as in this article. From there, nothing will be restricted so if a user decides to take this route, he or she will be directed correctly.

This will all be changing shortly as we find a better way to develop these roads.

Bus or Cab Only LanesService road.png

When a road or lane is designated for bus or cab use only, mark that road segment(s) as a Private Road to prevent the Waze router from using that segment(s) for general traffic, since the majority of the users will not be able to use that lane. It is also advisable to set the turn restrictions to prevent turns into that segment(s), but permit turns exiting the segment.

If a road is one-way but allows bus or cab traffic to flow the other direction, leave the road as one-way with the normal flow of traffic. There is no need to create a second road traveling the opposite direction for the bus and cab-only traffic.

Emergency Vehicle and DOT Service Roads Service road.png

Emergency.jpg
Emergency.jpg

"Emergency and Authorized Vehicles Only" and DOT Service Roads are to be treated as Non-drivable roads. These are found primarily through the median of divided highways to connect opposite direction lanes. In most cases, these should not be mapped at all. If mapped, they should not be connected to any drivable road, with properties set to road type Private Road, and lock the segment at as high a rank as possible, up to rank 5.

Non-drivable roads

Railroad Service road.png

RoadPicN11.jpg
RoadPicN11.jpg


Railroads are not yet added to the map, but these can be added to prepare the maps for when it is. Mapping the tracks allows Waze to recognize spurious speed data from people Wazing on the train and prevent it from corrupting speed data for the adjacent road.



Please notice that railroads have changed from previous interpretations of railroad mapping. Even veteran editors need to pay attention to this section!


  • Elevation will be set to the same elevation standards as a drivable road. When tracks junction a road on the ground, the Elevation should be set to Ground.
  • If the railroad crosses a segment of road, it should be connected to the road to so the historical data for the rail crossing will be more accurate.
  • Always select "None" for the city name. This avoids city smudging.
  • Set railroad to 2-way directionality and Restrict turns to and from the railroad segments.
  • Follow the Federal DOT Railroad GIS to verify the owner of the rail line to help on naming of the segment. Use the acronyms under RROWNER1 to help on naming.
  • Name each segment using the rail owner name acronyms or abbreviations railroad. For example, Twin Cities & Western Railroad uses TCWR. We would name this section TCW Railroad. We leave off the R in the acronym because it would be redundant to say, Twin Cities & Western Railroad Railroad.
  • Canadian Pacific uses the acronym CPRS, but it is more know as CP, so it will be called CP Railroad
  • Do not map every piece of parallel track, such as in sidings or yards, or industrial spurs that don't cross any roads. Your work may otherwise be seen as clutter, much like mapping every parking lot row.
  • Lock all railroads to a Level 2
  • Keep segment lengths under 10,000 meters (32,808 Ft) – the longer the segment length, the more sluggish the editor is to respond to changes.
  • Read this section for more information about railroads.

Runway/TaxiwayService road.png

We will map all airports runways such:

  • These roads will not connect to any drivable sections
  • The runways will not be connected to each other
  • Always select "None" for the city name. This avoids city smudging.
  • Using this article we will find the airport code. We will use the IATA code unless the airport does not have one, then we will revert to the ICAO code.
  • After finding the code, we will use this to find the runway numbers for the airport.
  • Most of the time, you will see the number of the runway at the beginning and end of each runway from the aerial views.
  • Name each runway as such: [Airport Code] Runway [x-x] ... for example, in the image to the right, you will see the runways for Albert Lea Municipal Airport. The IATA code for this airport is AEL and it has two runways including Runway 5/23 & Runway 17/35 so one will be named "AEL Runway 5-23" and the other AEL Runway 17-35".

Please follow this Wiki article on Runways for information about how to set runways correctly. These roads should be locked to the same standard as Airport Area itself.

Ferry Service road.png

 The Ferry Road type is not to be used at this time. Do not use the Ferry Road type for any purpose. See ferries page for more information on how to map ferries.

Walking Trails Service road.png

RoadPicN9.jpg
RoadPicN9.jpg

Because Waze currently only supports navigation for drivers and not walkers or bikers at all, we will not be drawing any of these types of roads. Please delete any of these types of roads that you find. If you find automatically set URs claiming a road is indicated to be be present, Please fill out the form located Here and choose Second Set of Eyes so a high level editor can check out the situation.

Pedestrian Boardwalks Service road.png

Because Waze currently only supports navigation for drivers and not walkers or bikers at all, we will not be drawing any of these types of roads. Please delete any of these types of roads that you find. If you find automatically set URs claiming a road is indicated to be be present, Please fill out the form located Here and choose Second Set of Eyes so a high level editor can check out the situation.

Stairway Service road.png

Stairways will not be added to Waze maps in Minnesota at all. Please delete any of these sections that you find added to the map


Speed Limits

Minnesota primarily follows the USA Speed Limits wiki: USA Speed Limits Wiki with some clarifications

Ramp Speed Limits

For ramps that are for accelerating to a road with a higher speed limit, use the higher speed limit of the destination road that the ramp goes to.

For ramps that go from a higher speed limit to a lower speed limit such as a freeway off ramp, do not place any speed limit on the ramp.

For ramps where the start and end have the same speed limit, keep the same speed limit on the ramp.

Do not use advisory speed limits that are black text on yellow signs.

Other Minnesota Specific Speed Limit details

The MN state laws for default unposted speed limits statewide are;

  • Alleyways and mobile home parks 10 mph unless otherwise posted.
  • Urban residential roads 30 mph unless otherwise posted.
  • Rural roads 55 mph unless otherwise posted.

Check with your Area or State Managers for clarification if needed.



Retrieved from "https://beta.waze.com/wiki/Mauritius/index.php?title=User:PesachZ/SyncScratch&oldid=151009"