https://www.waze.com/wiki/USA/api.php?action=feedcontributions&user=DallasGrant&feedformat=atomWazeopedia - User contributions [en]2024-03-28T23:16:44ZUser contributionsMediaWiki 1.40.2https://www.waze.com/wiki/USA/index.php?title=Minnesota/Special_roads/Main&diff=126069Minnesota/Special roads/Main2015-11-14T23:12:29Z<p>DallasGrant: Rules have changed from walking trails and had to update</p>
<hr />
<div><!-- 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><!--<br />
------ DO NOT MODIFY ABOVE THIS LINE -------- DO NOT MODIFY ABOVE THIS LINE ------> <br />
=== Other drivable roads ===<br />
<br />
==== Dirt Road / 4X4 Trail[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
{{mbox<br />
| type = important<br />
| text = Minnesota has different interpretations of Dirt Roads than many other locations. Even veteran editors need to pay attention to this section!<br />
}}<br />
<br />
<br />
[[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.<br />
<br />
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.<br />
<br />
[[File:Dirtroad.PNG|300px|right]]<br />
<br />
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. <br />
<br />
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.<br />
<br />
==== Parking Lot Road[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:Parklotrhmmn.png|right|300px]]<br />
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.<br />
<br />
* Simple is best. Do not map every lane<br />
* Map the main entrances from the roads outside the parking lot<br />
* Map lanes that run along storefronts<br />
* Map lanes that run along main roads outside the parking area<br />
* Map primary lanes that serve to get people from one area of the lot to another<br />
<br />
For for information about mapping parking lots, follow this [[Best_map_editing_practice#Parking_Lots|article]]<br />
<br />
==== Private Road[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:Pi gated-community1.jpg|right|300px|Pi gated-community1.jpg]]<br />
<br />
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. <br />
<br />
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. <br />
<br />
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.<br />
<br />
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.<br />
<br />
==== Alleyways[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
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 Parking Lot class.<br />
<br />
[[File:Pizzalola.png|300px|left]]<br />
<br />
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 parking lot 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.<br />
<br />
==== Roundabouts [[Image:Round.png |50px]] ====<br />
<br />
{{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".<br />
[[File:Roundabouts.png|400px|right]]<br />
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. <br />
<br />
<br />
<br />
[[File:Roundboutmn2.png|400px|left]]<br />
<br />
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).<br />
<br />
<br />
<br />
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.<br />
<br />
If at all possible, drive through a roundabout after it has been created or updated. Verify that it seems to give correct information.<br />
<br />
==== HOT & Hov Roads/Lanes ====<br />
[[Image:Hovmn.png|right]]<br />
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.<br />
<br />
These roadways have the following features:<br />
* These lanes/roads allow both toll traffic and HOV traffic to traverse the same lanes.<br />
* There are no toll plazas or booths for paying by cash. All tolls are paid electronically to maintain traffic speed.<br />
* Entrances and exits to the HOT lanes are limited to help maintain high speeds.<br />
* There are no entrance/exit combinations where the toll fare rules don't apply.<br />
* Tolls are discounted or waived for users that meet High Occupancy Vehicle (HOV) requirements. These requirements may change based on time of day.<br />
<br />
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.<br />
<br />
This will all be changing shortly as we find a better way to develop these roads.<br />
<br />
==== Bus or Cab Only Lanes[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
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.<br />
<br />
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.<br />
<br />
==== Emergency Vehicle and DOT Service Roads [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[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}}<br />
<br />
=== Non-drivable roads ===<br />
<br />
==== Railroad [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:RailroadTracksVanishingPoint.jpg|right|300px|RoadPicN11.jpg]]<br />
<br />
<br />
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.<br />
<br />
<br />
<br />
<br />
{{mbox<br />
| type = important<br />
| text = Please notice that railroads have changed from previous interpretations of railroad mapping. Even veteran editors need to pay attention to this section!<br />
}}<br />
<br />
<br />
* 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.<br />
* 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.<br />
* Always select "None" for the city name. This avoids [[Smudged_city#Overview|city smudging]].<br />
* Set railroad to 2-way directionality and Restrict turns ''to'' and ''from'' the railroad segments.<br />
* 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. <br />
* 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.<br />
* Canadian Pacific uses the acronym CPRS, but it is more know as CP, so it will be called CP Railroad<br />
*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.<br />
* Lock all railroads to a Level 2<br />
* 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.<br />
* Read [[Road_types/USA#Railroad|this section]] for more information about railroads.<br />
<br />
==== Runway/Taxiway[[File:Service road.png|200px|Service road.png]] ====<br />
[[File:Aelrwmn.png|right|250px]]<br />
We will map all airports runways such:<br />
<br />
* These roads will not connect to any drivable sections<br />
* The runways will not be connected to each other<br />
* Always select "None" for the city name. This avoids [[Smudged_city#Overview|city smudging]].<br />
* 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.<br />
* After finding the code, we will use [http://www.airnav.com/airports/ this] to find the runway numbers for the airport.<br />
* Most of the time, you will see the number of the runway at the beginning and end of each runway from the aerial views. <br />
* 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".<br />
<br />
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.<br />
<br />
==== Ferry [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
{{mbox<br />
| type = warning<br />
| 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.<br />
}}<br />
<br />
==== Walking Trails [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:RoadPicN9.jpg|right|300px|RoadPicN9.jpg]] <br />
<br />
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 [http://goo.gl/forms/6guJu7ujqh Here] and choose Second Set of Eyes so a high level editor can check out the situation.<br />
<br />
==== Pedestrian Boardwalks [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
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 [http://goo.gl/forms/6guJu7ujqh Here] and choose Second Set of Eyes so a high level editor can check out the situation.<br />
<br />
==== Stairway [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
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<br />
<br />
<br />
<!---- DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ----<br />
-------------------------------------------------------------------------------------<br />
---- This page is only transcluded into (displayed on) the main page for this state.<br />
---- It directly follows the common guidelines applicable to all states. When this<br />
---- page is present (even if blanked), it displaces any optional code that might be<br />
---- in that section.<br />
---- If the original optional code from the main page for this section is still<br />
---- desired, it can be restored by adding the following code to the first line <br />
---- between the "DO NOT MODIFY" lines on this page:<br />
---- {{:USA/CommonState/Special roads|optional}}<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- If there will be a full page for this section, use code similar to the wording<br />
---- below to provide a hyperlink to that page. When creating the full page, use the<br />
---- link on the talk page to ensure the preload data is provided to help with<br />
---- formatting the page. Don't just use the red link from this section once it is<br />
---- saved.<br />
----<br />
See [[{{BasePage2}}/Special roads]] for guidance in {{RootPage2}} that may not be universal to all other states.<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- This section has three possible purposes:<br />
---- 1. It is only providing a hyperlink to the full page for this section.<br />
---- 2. It is only providing some unique guidance for this state that differs from<br />
---- other states.<br />
---- 3. It is intentionally wiping out the general optional content for this section<br />
---- for this state.<br />
------------------------------------------------------------------------------------></div>DallasGranthttps://www.waze.com/wiki/USA/index.php?title=Minnesota/Cities_and_towns/Main&diff=126054Minnesota/Cities and towns/Main2015-11-14T20:43:47Z<p>DallasGrant: Changing link to correct new link</p>
<hr />
<div><!-- 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><!--<br />
------ DO NOT MODIFY ABOVE THIS LINE -------- DO NOT MODIFY ABOVE THIS LINE ------> <br />
<br />
{{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. <br />
<br />
{{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. <br />
<br />
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.<br />
<br />
If you see an issue, Report It 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. <br />
<br />
[[Minnesota/Cities_and_towns#Update_City|Report Incorrect City Data]]<br />
<br />
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.<br />
<br />
<!---- DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ----<br />
-------------------------------------------------------------------------------------<br />
---- This page is only transcluded into (displayed on) the main page for this state.<br />
---- It directly follows the common guidelines applicable to all states. When this<br />
---- page is present (even if blanked), it displaces any optional code that might be<br />
---- in that section.<br />
---- If the original optional code from the main page for this section is still<br />
---- desired, it can be restored by adding the following code to the first line <br />
---- between the "DO NOT MODIFY" lines on this page:<br />
---- {{:USA/CommonState/Cities_and_towns|optional}}<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- If there will be a full page for this section, use code similar to the wording<br />
---- below to provide a hyperlink to that page. When creating the full page, use the<br />
---- link on the talk page to ensure the preload data is provided to help with<br />
---- formatting the page. Don't just use the red link from this section once it is<br />
---- saved.<br />
----<br />
See [[{{BasePage2}}/Cities and towns]] for guidance in {{RootPage2}} that may not be universal to all other states.<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- This section has three possible purposes:<br />
---- 1. It is only providing a hyperlink to the full page for this section.<br />
---- 2. It is only providing some unique guidance for this state that differs from<br />
---- other states.<br />
---- 3. It is intentionally wiping out the general optional content for this section<br />
---- for this state.<br />
------------------------------------------------------------------------------------></div>DallasGranthttps://www.waze.com/wiki/USA/index.php?title=Minnesota/Cities_and_towns&diff=126052Minnesota/Cities and towns2015-11-14T20:34:19Z<p>DallasGrant: </p>
<hr />
<div><!-- This page is only viewed directly through a link from the state's "unique portion" page. Content on this page will be viewed in its entirety.--><noinclude>{{:USA/CommonState/ReturnPurge|{{SubPage2}}}}<br/></noinclude><!--<br />
------ DO NOT MODIFY ABOVE THIS LINE -------- DO NOT MODIFY ABOVE THIS LINE ------> <br />
<br />
== Update City ==<br />
{{#widget:Iframe<br />
|url=https://docs.google.com/forms/d/1sMCT2RLGXqgCx45IASX_Q_gDEyD8jcmsoIPLlHiS2eA/viewform?c=0&w=1<br />
|width=100%<br />
|height=850<br />
|border=0<br />
}}</div>DallasGranthttps://www.waze.com/wiki/USA/index.php?title=Minnesota/Cities_and_towns&diff=126050Minnesota/Cities and towns2015-11-14T20:30:47Z<p>DallasGrant: Added MN only City Name Changes</p>
<hr />
<div><!-- This page is only viewed directly through a link from the state's "unique portion" page. Content on this page will be viewed in its entirety.--><noinclude>{{:USA/CommonState/ReturnPurge|{{SubPage2}}}}<br/></noinclude><!--<br />
------ DO NOT MODIFY ABOVE THIS LINE -------- DO NOT MODIFY ABOVE THIS LINE ------> <br />
<br />
<br />
{{#widget:Iframe<br />
|url=https://docs.google.com/forms/d/1sMCT2RLGXqgCx45IASX_Q_gDEyD8jcmsoIPLlHiS2eA/viewform?c=0&w=1<br />
|width=100%<br />
|height=850<br />
|border=0<br />
}}</div>DallasGranthttps://www.waze.com/wiki/USA/index.php?title=Minnesota/Closures/Main&diff=118285Minnesota/Closures/Main2015-09-07T15:43:28Z<p>DallasGrant: */Closures/Main*/</p>
<hr />
<div><!-- 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><!--<br />
------ DO NOT MODIFY ABOVE THIS LINE -------- DO NOT MODIFY ABOVE THIS LINE ------> <br />
When an event occurs that causes a road to be closed, it is important to know that we have a closure system in place to properly close the road and return the road to normal when the closure is over. There is no need to take the closure into your own hands using restrictions.<br />
<br />
=== Closure or Restictions? ===<br />
<br />
There will be times we will use restrictions to a road being set for closure. If the road has a [[Partial_restrictions|Scheduled Restriction]] that occurs like clockwork [[Partial_restrictions#Setting_restrictions|restricting access]] during certain times of the day or months of the year, it would be a restriction. You can also set [[Partial_restrictions#Scheduled_turn_restrictions|Turn Restrictions]] for turns that need to be restricted certain times of the day. These are all restrictions because they are standard road limitations that occur on a regular basis.<br />
<br />
On the flip side, if the road is being closed due to an event such as construction, a parade, or a natural disaster, we need to create a [[Real time closures|Closure]]. Keep reading to see if what you have needs to have a closure in place.<br />
<br />
=== When is a closure required? ===<br />
<br />
This is really dependent on a few simple requirements. First of all, does it require a direction of traffic to be impacted at all? This is important because an actual lane of traffic closed does not necessarily mean a closure is needed if traffic still goes the direction(s) it would normally travel; however, this still could be important if access from the side of the road that is closed is restricted (such as exit ramps and connecting streets). One thing to consider is that a divided highway, in most cases, needs no closures if it affects one of the sides of the highway and all traffic is moved to the other lane unless there is a significant split in the road. In a lot of cases, nothing will need to be altered to make this work.<br />
<br />
Bottom line: if the closure will restrict access to a certain direction of the road, restrict access to the road completely, or has a limited connection to a closed road it will require a closure.<br />
<br />
=== Tools ===<br />
<br />
In {{RootPage2}}, there is not a single location to find all road closing; however, we have included a series of links to multiple city, county, and state resources. [[Minnesota/Closures#Tools|These Tools]] will help find any upcoming closures throughout {{RootPage2}}. Also, check our [[Minnesota/Closures#Current_Closures|Current Closures]] to see if an anticipated closure is already being recognized.<br />
<br />
* [[Minnesota/Closures#Tools|Resourses to find upcoming closures]]<br />
* [[Minnesota/Closures#Current_Closures|Current & Upcoming Closures]]<br />
<br />
=== Report a Closure ===<br />
<br />
Is there an upcoming closure that is not listed, is Waze is trying to drive you through roads that should be closed, or do we have a closure set for a road that is now open? Let us know so we can add it to the system -- [[Minnesota/Closures#Report_Closures|Report Closures]]<br />
<br />
== Update Requests ==<br />
<br />
An Update Request (UR) is a Map Issue reported by a user from the Waze client app. It is also a layer in the Map Editor. See [[Update_Requests_in_Waze_Map_Editor|update requests]] for more information. <br />
<br />
In {{RootPage2}}, we have adopted a 1/6/15 system for response to Update Requests. We use this system based on the colors the UR icon would be based on the [[Update_Requests_in_Waze_Map_Editor#Interface_Elements|Interface Elements]]. <br />
<br />
=== Day 1 ===<br />
[[Image:Request pin open-low.png|left]][[Image:Urijmn.png||175px|right]]A yellow Update Request (UR) has been open for 0-5 days. This is the first day the editor responds. We typically want to answer a report within 24 hours, but this should be at least attempted within the first 3 days. <br />
<br />
The first thing to do is to look at the UR and try to figure out the issue that happened. It is imperative to look at everything before ultimately deciding that you don't get it. If you click on ''More Information'' you can look at the Waze provided route and what the user took to determine this issues. Check the area roads for any [[Map_Editing_Quick-start_Guide#Turn_restrictions_.28allowed_turns.29|restrictions]], [[Elevation#Road_elevation|incorrect elevation]], [[Road_names/USA|incorrect street names]], [[Geometry#Geometry|bad geometry]], etc.<br />
<br />
If you can figure out the issue, Fix it or submit an [[Minnesota#Unlock_Requests|unlock request]]!<br />
<br />
Example:<br />
[[Image:Request_pin_solved_conversation.png|left]]<br />
"''"Thank you for reporting the [general error] through the Waze app. The issue has been corrected in the system and will be updated on the map within the next few days. If you are still having issues, please go to the Waze App, then go to Settings / Advanced Settings / Data Transfer and then Refresh Area of My Map to see if that improves anything."''"<br />
[[Image:Request_pin_solved_conversation.png|left]]<br />
"''"Thank you for reporting the [general error] through the Waze app. A request has been made to fix the issues. This should be resolved within the next week or two. If you still are having issues after 2 weeks, please go to the Waze App, then go to Settings / Advanced Settings / Data Transfer and then Refresh Area of My Map to see if that improves anything."''"<br />
<br />
[[Image:Request pin open-low.png|left]][[Image:Urgemn.png||175px|right]]Sometimes the UR will give such vague information that there is no way to tell at all what causes the error at all. The best thing to do here is to request more information from the user and follow the [[Minnesota#Day_6|6]] and [[Minnesota#Day_15|15-day]] example from there.<br />
<br />
Example<br />
[[Image:Request_pin_open_conversation-low.png|left]] <br />
"''"Thank you for reporting a [general error] through the Waze app. The report was not clear on what exactly happened at [this location]. Could you please explain the issue that occurred further?"''"<br />
<br />
=== Day 6 ===<br />
[[Image:Request pin open-med.png|left]] An orange update request has been open for 6-14 days. If the reporter has not commented after 6 (to 10) days of this initial comment a message should be sent reminding the reporter that we need more information about the problem they encountered.<br />
<br />
Example<br />
[[Image:Request_pin_open_conversation-med.png|left]]<br />
"''We apologize that we have not heard back from you to explain the issue further. We will need a response to fix the issue further. This ticket will be closed in 9 days if no response occurs.''"<br />
<br />
=== Day 15 ===<br />
[[Image:Request pin open-high.png|left]] A red update request has been open for 15 days or longer. If the reporter still has not commented after 9 more days (15 days since the initial comment) a message should be sent telling the reported that we were unable to fix the problem and this report is being closed. The Update Request then needs to be closed as Not Identified. <br />
<br />
Example<br />
[[Image:Request pin-notidentified.gif|left]] <br />
"''We apologize that we still have not heard back from you about the issue. We have not found the issue and it could be that your map is giving you incorrect information. Please go to the Waze App, then go to Settings / Advanced Settings / Data Transfer and then Refresh Area of My Map to see if that improves anything. Due to no response, we are closing this ticket. You can submit another report if the issue is still present''"<br />
<br />
=== Rural Areas ===<br />
While we would like to have every inch of {{RootPage2}} covered with a network of editors, we are not currently at that level of community involvement. The 1/6/15 rule has been set as the standard for areas with [[#Area_Managers|Area Managers]] and active editors; However, in many areas, there is very little editor coverage. That being said, use good judgment in these areas as there may be Update Requests that are greater than 30 or even 60 days old. There is no penalty or negative perception to answering these, quite the opposite. Please, still take the time to send the reporter a message to see if they can remember the issue and allow them additional time to provide more information. In these areas, we will follow a 1/15/30 rule. Day 1 is the first day an editor responds. Day 15 is the warning message stating the issue will be closing in 15 days. Day 30 to close out the ticket. <br />
<br />
Example:<br />
<br />
"''Thank you for your report! I apologize for the late response, we are volunteer editors and in some areas there are not many of us. You reported a General Error near [this location] in [City], {{RootPage2}} way back on 9 Dec 14. Do you remember what issue you encountered?''"<br />
<br />
== Unlock Requests ==<br />
<br />
Sometimes, you will come to an issue with a road, but you do not have a sufficient lock level to fix the situation. [http://www.waze.com/forum/viewforum.php?f=622 Click here] if you need to setup an unlock request. Please pay attention to the top of this forum where it will give clear instructions on how to create an unlock request.<br />
<br />
If you want to check to see if there are any Unlock Requests that you can handle, [http://www.waze.com/forum/search.php?fid%5B0%5D=622&sf=titleonly&sr=topics&submit=Search&keywords={{RootPage2}} Click Here] to check all open reports for {{RootPage2}}. Anything showing the green check mark means it has been completed. <br />
<br />
<!---- DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ----<br />
-------------------------------------------------------------------------------------<br />
---- This page is only transcluded into (displayed on) the main page for this state.<br />
---- It directly follows the common guidelines applicable to all states. When this<br />
---- page is present (even if blanked), it displaces any optional code that might be<br />
---- in that section.<br />
---- If the original optional code from the main page for this section is still<br />
---- desired, it can be restored by adding the following code to the first line <br />
---- between the "DO NOT MODIFY" lines on this page:<br />
---- {{:USA/CommonState/Closures|optional}}<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- If there will be a full page for this section, use code similar to the wording<br />
---- below to provide a hyperlink to that page. When creating the full page, use the<br />
---- link on the talk page to ensure the preload data is provided to help with<br />
---- formatting the page. Don't just use the red link from this section once it is<br />
---- saved.<br />
----<br />
See [[{{BasePage2}}/Closures]] for guidance in {{RootPage2}} that may not be universal to all other states.<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- This section has three possible purposes:<br />
---- 1. It is only providing a hyperlink to the full page for this section.<br />
---- 2. It is only providing some unique guidance for this state that differs from<br />
---- other states.<br />
---- 3. It is intentionally wiping out the general optional content for this section<br />
---- for this state.<br />
------------------------------------------------------------------------------------></div>DallasGranthttps://www.waze.com/wiki/USA/index.php?title=Minnesota/Closures&diff=118283Minnesota/Closures2015-09-07T15:00:53Z<p>DallasGrant: */Closures*/</p>
<hr />
<div><!-- This page is only viewed directly through a link from the state's "unique portion" page. Content on this page will be viewed in its entirety.--><noinclude>{{:USA/CommonState/ReturnPurge|{{SubPage2}}}}<br/></noinclude><!--<br />
------ DO NOT MODIFY ABOVE THIS LINE -------- DO NOT MODIFY ABOVE THIS LINE ------> <br />
== Report Closures ==<br />
<br />
{{#widget:Iframe<br />
|url=https://docs.google.com/forms/d/19M3MlVgezUfCpQba2R7YqZH5AhEcqKeqpUNn_hQXBiw/viewform?embedded=true<br />
|width=100%<br />
|height=850<br />
|border=0<br />
}}<br />
<br />
== Current Closures ==<br />
<br />
{{#widget:Google Spreadsheet<br />
|key=106eZeRgf5cRze6338J_lPkCNwt5wF_w611XDog4VjbI<br />
|width=100%<br />
|height=300<br />
|page=false<br />
}}<br />
<br />
== Tools ==<br />
<br />
{| class="wikitable sortable"<br />
|+ Road Closure Reports<br />
! Area !! Link <br />
|-<br />
|Statewide || [http://hb.511mn.org/#roadReports/layers=allReports,roadReports,winterDriving,weatherWarnings,otherStates 511mn.org]<br />
|-<br />
|St. Paul || [http://www.stpaul.gov/index.aspx?NID=929 stpaul.gov]<br />
|-<br />
|Hennepin County || [http://www.hennepin.us/residents#transportation hennepin.us]</div>DallasGranthttps://www.waze.com/wiki/USA/index.php?title=Minnesota/Major_roads/Main&diff=117123Minnesota/Major roads/Main2015-08-22T23:20:42Z<p>DallasGrant: </p>
<hr />
<div><!-- 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><!--<br />
------ DO NOT MODIFY ABOVE THIS LINE -------- DO NOT MODIFY ABOVE THIS LINE ------> <br />
=== Functional Class ===<br />
<br />
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.<br />
<br />
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.<br />
<br />
If you have any questions about Functional Class, please use our [[Minnesota#Community|Community Resourses]] to reach out to gain further information.<br />
<br />
Below is a list of the six major road types. If you click on the button of the road type, for instance [[Road_Types_(USA)#Freeway|{{Freeway}}]], you will be directed to a Wiki section that discusses the road type further.<br />
<br />
==== Freeway [[Image:RoadBlue.png|180px]] ====<br />
<br />
A [[Road_Types_(USA)#Freeway|{{Freeway}}]] is the highest functional class of road. It is designed for higher speeds and limited to entrance and exits ramps being the only way to enter or exit this type of road. <br />
<br />
[[File:Pa-interstateMN.png|150px|left]][[File:I35mn.png|100px|right]][[File:I94fcmn.png|150px|left]]Any road with the Functional Class (FC) as Principal Arterial Interstate, colored blue on the FC map, will be considered a Freeway. All [http://en.wikipedia.org/wiki/List_of_Interstate_Highways_in_Minnesota#Minnesota_Interstates Interstate Roads] Will be freeways aside from Business Loops and Spurs (Which instead will be a Major Highway). Also, watch for some roads that are Principal Arterial - Other or Other Freeways (colored red or orange) as they could fit the profile of a Freeway. All roads that have to be entered or exited using a ramp, where 3 or more consecutive exits occur, needs to be set as a freeway. A Freeway will end at first direct connection of a road to the highway.<br />
<br />
===== Naming =====<br />
<br />
# Freeways will usually only be named the Highway number of the most prominent highway of the section. For instance, If a highway is a State Highway connected with a US highway, then it will be named the US highway. <br />
# If two of the same type connect such as a US highway and another US highway, then the road that stayed on course will be the named highway. <br />
# All highway numbering will be as follows: Interstate: I-XXX, US Highway: US-XXX, Minnesota State Highway: MN-XXX, County Highway: CH-XXX. Notice that there are no spaces between the dashes. The only exception to using the Highway Number would be if there is clear signage that the freeway is known by another name.<br />
<br />
==== Ramps [[File:Ramp.png|200px|Ramp.png]] ====<br />
<br />
A [[Road_types/USA#Ramps|{{Ramp}}]] will connect two roads together; however, it will not be used for a simple [[At-grade_connectors#Road_type|At-grade connector]] or in other words a road that doesn't have a different elevation level. There are some [[At-grade_connectors#Exceptions|exceptions]] to this rule to understand. <br />
<br />
===== Naming =====<br />
<br />
Even veteran editors need to pay attention here! Naming of an entrance and exit ramp correctly is crucial to the users of this app when being navigated around. If the name of the entrance ramp is incorrect it will confuse the experience and may confuse the driver to take the exit absurdly or miss it all together. Please follow these rules:<br />
<br />
# Only time to ever type in the word "Exit" in the ramp is when the exit is a numbered exit. The only roads that have numbered exits are exits off an Interstate with the exception of US-52.<br />
# For all Numbered exits, it will start with "Exit XX:" For example, if the Exit is number 114A then you will start the exit name as "Exit 114A:" and there will always be a colon after the exit number<br />
# For non-numbered exits, just start the exit as such, "to" For example, if the exit was to US Highway 169 Northbound, then the exit would be "to US-169 N"<br />
# All numbered highways need to be typed as such: Interstate: I-XXX, US Highway: US-XXX, Minnesota State Highway: MN-XXX, County Highway: CH-XXX, County Road: CR-XX all with no spaces between the Highway type and the number.<br />
# Include as much information in the sign as possible. For example, If the actual sign shows it will take you to County Highway 1 Eastbound and it also takes you to Riverview Rd and Old Shakopee Rd, then the ramp needs to be labeled: "to CH-1 E / Riverview Rd / Old Shakopee Rd" using the slash "/" to separate the different roads to take. Try to match the sign as close as possible.<br />
# If a road splits showing arrow marking under lanes to of which to stay on to continue your course, use ramps for each side. For example: in Burnsville, a person taking I-35 N will have the decision to take I-35W N or I-35E N. The I-35W side is a numbered exit, the other side is just a guided direction to head towards I-35E N. The one side is labeled: "Exit 88A: I-35W / Minneapolis" and the other side is just labeled: "to I-35E / St. Paul". Using ramps here will guide the driver to the right side of the highway.<br />
# For road splits that have 3 or more splits, usually paying attention to the one that splits first will guide you to how to set it up correctly, but it is often best to reach out for support to find the best solution based on the more complexity of an issue.<br />
<br />
==== Major Highway[[Image:Majorhighwayseg.png |200px]] ====<br />
<br />
A [[Road_Types_(USA)#Major_Highway|{{Major Highway}}]] is a primary route for traveling throughout the country, from one city to another, over long distances.<br />
<br />
[[File:Pa-othmnFC.png|150px|left]][[File:US 169 (MN).png|100px|right]][[File:Paother169mnfc.png|150px|left]]<br />
<br />
Any road with the Functional Class (FC) as Principal Arterial - Other (Freeways), colored red or orange on the FC map, will be a Major Highway (MH) if these roads do not fit the standard definition of a Freeway. All [http://en.wikipedia.org/wiki/List_of_U.S._Highways_in_Minnesota#U.S._Highways US Highways] (Such as US-169) will be labeled as a Major Highway regardless of what the FC map shows unless it can be labeled as a freeway.<br />
<br />
===== Naming =====<br />
# Naming of a major highway typically will be in the road number standard: US Highway: US-XXX, Minnesota State Highway: MN-XXX, County Highway: CH-XXX, County Road: CR-XXX; however, pay close attention to the way the signage really is in these areas. <br />
# In town, these highways need to be named as the street names used for house numbering. <br />
# Out of town, should be labeled the same as the street name for house numbering if looking at a 2 lane highway <br />
# and the Highway number for split direction Major highways unless signage clearly indicates it is known by another name<br />
<br />
==== Minor Highway[[Image:RoadYell.png |200px]] ====<br />
<br />
A [[Road_types/USA#Minor_Highway|{{Minor Highway}}]] is a secondary route for traveling between cities over moderately long distances.<br />
<br />
[[File:Mnfcma.png|130px|left]][[File:MN13sign.png|100px|right]][[File:Mnfcmamn13.png|130px|left]]<br />
<br />
Any road with the Functional Class (FC) as Minor Arterial, colored as green on the FC map. will be a Minor Highway (mH). Also, all [http://en.wikipedia.org/wiki/List_of_Minnesota_state_highways#List_of_highways State Highways] (such as MN-13) will be set at a minimum of a minor highway regardless of the current FC classification from the State of Minnesota unless it is a higher classification or could be considered a freeway.<br />
<br />
===== Naming =====<br />
# Naming of a minor highway typically will be in the road number standard: Minnesota State Highway: MN-XXX, County Highway: CH-XXX, County Road: CR-XXX; however, pay close attention to the way the signage really is in these areas. <br />
# In a town or city, the naming will typically be the street name unless the name of the street is Co Hwy XX where we would change it to CH-XX<br />
# Pay close attention to the name assigned for house numbering. If house numbering suggests using the wording, "State Highway XXX", we need to set the name of the road as such.<br />
<br />
==== Primary Street [[Image:Primary street.png|200px]] ====<br />
A [[Road_types/USA#Primary_Street|{{Primary Street}}]] is a road used with medium-low traffic densities which are used to bring traffic from local streets to arterials and vice versa<br />
<br />
[[File:Mnfcmc.png|130px|left]][[File:Mncr81.png|100px|right]][[File:Mnfcco.png|130px|left]]Any road with the Functional Class (FC) a Major or Minor Collector, colored as purple or yellow on FC map, will be a Primary Street (PS). Also, pay attention to any paved [http://en.wikipedia.org/wiki/County_roads_in_Minnesota#Lists_of_county_roads_in_Minnesota county road] as these will have a minimum of a Primary Street. Most frontage roads will have this category as well even if the FC map shows a lower level (but reach out for clarification for the ones that are not a county road). If you see any of these roads set as a service road, please correct this to a standard type road as Service Roads are phased out.<br />
<br />
===== Naming =====<br />
Primary streets should only be named the actual name of the street (same name as house numbering indicates). The only exceptions to this rule would be tricky intersections where a county road sign is the only prevalent name of the street.<br />
<br />
<br />
==== Street [[Image:Street.png|200px]] ====<br />
<br />
A [[Road_types/USA#Street|{{Street}}]] will be for any road in a town or city that doesn't fit in the categories above. In rural areas, this will be lightly used for paved roads that cannot be considered a County Road (a rarity in the rural areas). This will be named the same name used for house numbering.<br />
<br />
=== Lock Standards ===<br />
<br />
{{Lock Standard State|MN}}<br />
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.<br />
Additional: {{reflist}}<br />
<br />
<!---- DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ----<br />
-------------------------------------------------------------------------------------<br />
---- This page is only transcluded into (displayed on) the main page for this state.<br />
---- It directly follows the common guidelines applicable to all states. When this<br />
---- page is present (even if blanked), it displaces any optional code that might be<br />
---- in that section.<br />
---- If the original optional code from the main page for this section is still<br />
---- desired, it can be restored by adding the following code to the first line <br />
---- between the "DO NOT MODIFY" lines on this page:<br />
---- {{:USA/CommonState/Major_roads|optional}}<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- If there will be a full page for this section, use code similar to the wording<br />
---- below to provide a hyperlink to that page. When creating the full page, use the<br />
---- link on the talk page to ensure the preload data is provided to help with<br />
---- formatting the page. Don't just use the red link from this section once it is<br />
---- saved.<br />
----<br />
See [[{{BasePage2}}/Major roads]] for guidance in {{RootPage2}} that may not be universal to all other states.<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- This section has three possible purposes:<br />
---- 1. It is only providing a hyperlink to the full page for this section.<br />
---- 2. It is only providing some unique guidance for this state that differs from<br />
---- other states.<br />
---- 3. It is intentionally wiping out the general optional content for this section<br />
---- for this state.<br />
------------------------------------------------------------------------------------></div>DallasGranthttps://www.waze.com/wiki/USA/index.php?title=Minnesota/Closures&diff=103949Minnesota/Closures2015-04-16T03:19:18Z<p>DallasGrant: /* Current Closures */</p>
<hr />
<div><!-- This page is only viewed directly through a link from the state's "unique portion" page. Content on this page will be viewed in its entirety.--><noinclude>{{:USA/CommonState/ReturnPurge|{{SubPage2}}}}<br/></noinclude><!--<br />
------ DO NOT MODIFY ABOVE THIS LINE -------- DO NOT MODIFY ABOVE THIS LINE ------> <br />
<br />
== Current Closures ==<br />
<br />
{{#widget:Google Spreadsheet<br />
|key=106eZeRgf5cRze6338J_lPkCNwt5wF_w611XDog4VjbI<br />
|width=100%<br />
|height=300<br />
|page=false<br />
}}<br />
<br />
== Tools ==<br />
<br />
{| class="wikitable sortable"<br />
|+ Road Closure Reports<br />
! Area !! Link <br />
|-<br />
|Statewide || [http://hb.511mn.org/#roadReports/layers=allReports,roadReports,winterDriving,weatherWarnings,otherStates 511mn.org]<br />
|-<br />
|St. Paul || [http://www.stpaul.gov/index.aspx?NID=929 stpaul.gov]<br />
|-<br />
|Hennepin County || [http://www.hennepin.us/residents#transportation hennepin.us]</div>DallasGranthttps://www.waze.com/wiki/USA/index.php?title=Minnesota/Closures&diff=103948Minnesota/Closures2015-04-16T03:18:32Z<p>DallasGrant: */Closures*/</p>
<hr />
<div><!-- This page is only viewed directly through a link from the state's "unique portion" page. Content on this page will be viewed in its entirety.--><noinclude>{{:USA/CommonState/ReturnPurge|{{SubPage2}}}}<br/></noinclude><!--<br />
------ DO NOT MODIFY ABOVE THIS LINE -------- DO NOT MODIFY ABOVE THIS LINE ------> <br />
<br />
== Current Closures ==<br />
<br />
{{#widget:Google Spreadsheet<br />
|key=106eZeRgf5cRze6338J_lPkCNwt5wF_w611XDog4VjbI<br />
|width=100%<br />
|height=500<br />
|page=false<br />
}}<br />
<br />
== Tools ==<br />
<br />
{| class="wikitable sortable"<br />
|+ Road Closure Reports<br />
! Area !! Link <br />
|-<br />
|Statewide || [http://hb.511mn.org/#roadReports/layers=allReports,roadReports,winterDriving,weatherWarnings,otherStates 511mn.org]<br />
|-<br />
|St. Paul || [http://www.stpaul.gov/index.aspx?NID=929 stpaul.gov]<br />
|-<br />
|Hennepin County || [http://www.hennepin.us/residents#transportation hennepin.us]</div>DallasGranthttps://www.waze.com/wiki/USA/index.php?title=Minnesota/Places/Main&diff=101104Minnesota/Places/Main2015-03-27T15:29:02Z<p>DallasGrant: </p>
<hr />
<div><!-- 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><!--<br />
------ DO NOT MODIFY ABOVE THIS LINE -------- DO NOT MODIFY ABOVE THIS LINE ------> <br />
<br />
==== Locking Standard ====<br />
<br />
'''Do Not Lock''' a place if the following is not true:<br />
<br />
Places should be completed as fully as possible any time they are created or updated. At a ''minimum'', editors should:<br />
*'''Verify correct spelling''' of the name, using the guidelines below<br />
*'''Complete the address''', to help when choosing among search results in the app, and<br />
*'''Ensure the correct location''' of the Point or Stop Point, to guide drivers to the correct location. Note that this may not always be on the street side of the location.<br />
Phone numbers and opening hours are also particularly helpful to Wazers. Complete them whenever possible, using an online search, if necessary. Photos should help Wazers recognize the destination when they arrive.<br />
<br />
{| class="wikitable" style="text-align:center; margin: 1em auto 1em auto; width: 75%"<br />
|+ MINNESOTA PLACE LOCK LEVEL STANDARDS<br />
! PLACE TYPE !! LOCK LEVEL<br />
|-<br />
| Commercial Service – Primary Airports || 5<br />
|-<br />
| Military Airports || 5<br />
|-<br />
| Reliever Airports || 4<br />
|-<br />
| General Aviation Airports || 3<br />
|-<br />
| Other Public-Use Airports || 3<br />
|-<br />
| Hospitals / Urgent Care / Police &amp; Fire Dept || 4<br />
|-<br />
| National &amp; State Parks and Monuments || 4<br />
|-<br />
| Major Shopping Centers || 4<br />
|-<br />
| Gas Stations / Charging Stations || 3<br />
|-<br />
| Schools / Universities / Colleges || 3<br />
|-<br />
| Government Buildings / Consulates || 3<br />
|-<br />
| City Parks || 3<br />
|}<br />
<br />
:All Places that have complete information (to include, at a minimum, address/city, hours of operation, phone number) are to be locked at '''Level 2'''. This is to prevent loss of data due to automatic acceptance of Place Update submissions from ''Trusted Users'', or Place Update Request approvals from other editors without careful examination.<br />
<br />
:If you do not have a high enough enough rank to lock the place as indicated, please lock it as high as you can, and notify a higher rank [[#Area Managers|AM, SM, CM, or Champ]] to lock it higher.<br />
<br />
<br />
<br />
<!---- DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ----<br />
-------------------------------------------------------------------------------------<br />
---- This page is only transcluded into (displayed on) the main page for this state.<br />
---- It directly follows the common guidelines applicable to all states. When this<br />
---- page is present (even if blanked), it displaces any optional code that might be<br />
---- in that section.<br />
---- If the original optional code from the main page for this section is still<br />
---- desired, it can be restored by adding the following code to the first line <br />
---- between the "DO NOT MODIFY" lines on this page:<br />
---- {{:USA/CommonState/Places|optional}}<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- If there will be a full page for this section, use code similar to the wording<br />
---- below to provide a hyperlink to that page. When creating the full page, use the<br />
---- link on the talk page to ensure the preload data is provided to help with<br />
---- formatting the page. Don't just use the red link from this section once it is<br />
---- saved.<br />
----<br />
See [[{{BasePage2}}/Places]] for guidance in {{RootPage2}} that may not be universal to all other states.<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- This section has three possible purposes:<br />
---- 1. It is only providing a hyperlink to the full page for this section.<br />
---- 2. It is only providing some unique guidance for this state that differs from<br />
---- other states.<br />
---- 3. It is intentionally wiping out the general optional content for this section<br />
---- for this state.<br />
------------------------------------------------------------------------------------></div>DallasGranthttps://www.waze.com/wiki/USA/index.php?title=Minnesota/Places/Main&diff=101047Minnesota/Places/Main2015-03-27T06:22:18Z<p>DallasGrant: /* Locking Standard */</p>
<hr />
<div><!-- 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><!--<br />
------ DO NOT MODIFY ABOVE THIS LINE -------- DO NOT MODIFY ABOVE THIS LINE ------> <br />
<br />
==== Locking Standard ====<br />
<br />
{| class="wikitable" style="text-align:center; margin: 1em auto 1em auto; width: 75%"<br />
|+ MINNESOTA PLACE LOCK LEVEL STANDARDS<br />
! PLACE TYPE !! LOCK LEVEL<br />
|-<br />
| Commercial Service – Primary Airports || 5<br />
|-<br />
| Military Airports || 5<br />
|-<br />
| Reliever Airports || 4<br />
|-<br />
| General Aviation Airports || 3<br />
|-<br />
| Other Public-Use Airports || 3<br />
|-<br />
| Hospitals / Urgent Care / Police &amp; Fire Dept || 4<br />
|-<br />
| National &amp; State Parks and Monuments || 4<br />
|-<br />
| Religious Centers || 4<br />
|-<br />
| Major Shopping Centers || 4<br />
|-<br />
| Gas Stations / Charging Stations || 3<br />
|-<br />
| Schools / Universities / Colleges || 3<br />
|-<br />
| Government Buildings / Consulates || 3<br />
|-<br />
| City Parks || 3<br />
|}<br />
<br />
:All Places that have complete information (to include, at a minimum, address/city, hours of operation, phone number) are to be locked at '''Level 2'''. This is to prevent loss of data due to automatic acceptance of Place Update submissions from ''Trusted Users'', or Place Update Request approvals from other editors without careful examination.<br />
<br />
:If you do not have a high enough enough rank to lock the place as indicated, please lock it as high as you can, and notify a higher rank [[#Area Managers|AM, SM, CM, or Champ]] to lock it higher.<br />
<br />
<!---- DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ----<br />
-------------------------------------------------------------------------------------<br />
---- This page is only transcluded into (displayed on) the main page for this state.<br />
---- It directly follows the common guidelines applicable to all states. When this<br />
---- page is present (even if blanked), it displaces any optional code that might be<br />
---- in that section.<br />
---- If the original optional code from the main page for this section is still<br />
---- desired, it can be restored by adding the following code to the first line <br />
---- between the "DO NOT MODIFY" lines on this page:<br />
---- {{:USA/CommonState/Places|optional}}<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- If there will be a full page for this section, use code similar to the wording<br />
---- below to provide a hyperlink to that page. When creating the full page, use the<br />
---- link on the talk page to ensure the preload data is provided to help with<br />
---- formatting the page. Don't just use the red link from this section once it is<br />
---- saved.<br />
----<br />
See [[{{BasePage2}}/Places]] for guidance in {{RootPage2}} that may not be universal to all other states.<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- This section has three possible purposes:<br />
---- 1. It is only providing a hyperlink to the full page for this section.<br />
---- 2. It is only providing some unique guidance for this state that differs from<br />
---- other states.<br />
---- 3. It is intentionally wiping out the general optional content for this section<br />
---- for this state.<br />
------------------------------------------------------------------------------------></div>DallasGranthttps://www.waze.com/wiki/USA/index.php?title=Minnesota/Places/Main&diff=101046Minnesota/Places/Main2015-03-27T04:26:55Z<p>DallasGrant: Initial page creation from preload</p>
<hr />
<div><!-- 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><!--<br />
------ DO NOT MODIFY ABOVE THIS LINE -------- DO NOT MODIFY ABOVE THIS LINE ------> <br />
<br />
==== Locking Standard ====<br />
<br />
{| class="wikitable" style="text-align:center; margin: 1em auto 1em auto; width: 75%"<br />
|+ MINNESOTA PLACE LOCK LEVEL STANDARDS<br />
! PLACE TYPE !! LOCK LEVEL<br />
|-<br />
| Commercial Service – Primary Airports || 5<br />
|-<br />
| Military Airports || 5<br />
|-<br />
| Reliever Airports || 4<br />
|-<br />
| General Aviation Airports || 3<br />
|-<br />
| Other Public-Use Airports || 3<br />
|-<br />
| Hospitals / Urgent Care / Police &amp; Fire Dept || 4<br />
|-<br />
| National &amp; State Parks and Monuments || 4<br />
|-<br />
| Major Shopping Centers || 4<br />
|-<br />
| Gas Stations / Charging Stations || 3<br />
|-<br />
| Schools / Universities / Colleges || 3<br />
|-<br />
| Government Buildings / Consulates || 3<br />
|-<br />
| City Parks || 3<br />
|}<br />
<br />
:All Places that have complete information (to include, at a minimum, address/city, hours of operation, phone number) are to be locked at '''Level 2'''. This is to prevent loss of data due to automatic acceptance of Place Update submissions from ''Trusted Users'', or Place Update Request approvals from other editors without careful examination.<br />
<br />
:If you do not have a high enough enough rank to lock the place as indicated, please lock it as high as you can, and notify a higher rank [[#Area Managers|AM, SM, CM, or Champ]] to lock it higher.<br />
<br />
<!---- DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ----<br />
-------------------------------------------------------------------------------------<br />
---- This page is only transcluded into (displayed on) the main page for this state.<br />
---- It directly follows the common guidelines applicable to all states. When this<br />
---- page is present (even if blanked), it displaces any optional code that might be<br />
---- in that section.<br />
---- If the original optional code from the main page for this section is still<br />
---- desired, it can be restored by adding the following code to the first line <br />
---- between the "DO NOT MODIFY" lines on this page:<br />
---- {{:USA/CommonState/Places|optional}}<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- If there will be a full page for this section, use code similar to the wording<br />
---- below to provide a hyperlink to that page. When creating the full page, use the<br />
---- link on the talk page to ensure the preload data is provided to help with<br />
---- formatting the page. Don't just use the red link from this section once it is<br />
---- saved.<br />
----<br />
See [[{{BasePage2}}/Places]] for guidance in {{RootPage2}} that may not be universal to all other states.<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- This section has three possible purposes:<br />
---- 1. It is only providing a hyperlink to the full page for this section.<br />
---- 2. It is only providing some unique guidance for this state that differs from<br />
---- other states.<br />
---- 3. It is intentionally wiping out the general optional content for this section<br />
---- for this state.<br />
------------------------------------------------------------------------------------></div>DallasGranthttps://www.waze.com/wiki/USA/index.php?title=Minnesota/Notice/Main&diff=101043Minnesota/Notice/Main2015-03-27T02:36:22Z<p>DallasGrant: */Notice/Main*/</p>
<hr />
<div><!-- 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><!--<br />
------ DO NOT MODIFY ABOVE THIS LINE -------- DO NOT MODIFY ABOVE THIS LINE ------> <br />
<!---- DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ----<br />
-------------------------------------------------------------------------------------<br />
---- This page is only transcluded into (displayed on) the main page for this state.<br />
---- It directly follows the common guidelines applicable to all states. When this<br />
---- page is present (even if blanked), it displaces any optional code that might be<br />
---- in that section.<br />
---- If the original optional code from the main page for this section is still<br />
---- desired, it can be restored by adding the following code to the first line <br />
---- between the "DO NOT MODIFY" lines on this page:<br />
---- {{:USA/CommonState/Notice|optional}}<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- If there will be a full page for this section, use code similar to the wording<br />
---- below to provide a hyperlink to that page. When creating the full page, use the<br />
---- link on the talk page to ensure the preload data is provided to help with<br />
---- formatting the page. Don't just use the red link from this section once it is<br />
---- saved.<br />
----<br />
See [[{{BasePage2}}/Notice]] for guidance in {{RootPage2}} that may not be universal to all other states.<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- This section has three possible purposes:<br />
---- 1. It is only providing a hyperlink to the full page for this section.<br />
---- 2. It is only providing some unique guidance for this state that differs from<br />
---- other states.<br />
---- 3. It is intentionally wiping out the general optional content for this section<br />
---- for this state.<br />
------------------------------------------------------------------------------------></div>DallasGranthttps://www.waze.com/wiki/USA/index.php?title=Minnesota/Closures&diff=100569Minnesota/Closures2015-03-24T06:42:16Z<p>DallasGrant: /* Current Closures */</p>
<hr />
<div><!-- This page is only viewed directly through a link from the state's "unique portion" page. Content on this page will be viewed in its entirety.--><noinclude>{{:USA/CommonState/ReturnPurge|{{SubPage2}}}}<br/></noinclude><!--<br />
------ DO NOT MODIFY ABOVE THIS LINE -------- DO NOT MODIFY ABOVE THIS LINE ------> <br />
<br />
== Current Closures ==<br />
{| class="wikitable sortable"<br />
|-<br />
! City!! Road !! Area on Map !! Report !! Date & Time From !! Date & Time To<br />
|-<br />
|St Louis Park || Minnetonka Blvd || [https://www.waze.com/editor/?env=usa&lon=-93.34719&lat=44.94867&layers=1061&zoom=6&segments=25005119 Permalink] || [http://kstp.com/news/stories/s3734411.shtml KSTP] || 03/23/2015 0:00 || 09/01/2015 0:00<br />
|-<br />
|Florence || US-14 || [http://www.waze.com/editor/?env=usa&lon=-96.06097&lat=44.23871&layers=389&zoom=3&segments=78634181,67945044,24623859,24620162 Permalink] || [http://www.dot.state.mn.us/d8/projects/hwy14florence/ MnDot] || 05/01/2014 0:00 || 05/01/2015 0:00<br />
|-<br />
|Cambridge || MN-95 || [http://www.waze.com/editor/?env=usa&lon=-93.23860&lat=45.57219&layers=389&zoom=4&segments=24740508 Permalink] || [http://www.dot.state.mn.us/d3/newsrels/14/04/25_hwy95cambridge.html MnDot] || 05/01/2014 0:00 || 07/01/2015 0:00<br />
|-<br />
|Thomson || MN-210 || [http://www.waze.com/editor/?env=usa&lon=-92.29857&lat=46.66924&layers=389&zoom=3&segments=24421586,82257715 Permalink] || [http://www.dot.state.mn.us/d1/projects/Hwy210future/index.html MnDot] || 06/01/2012 0:00 || 06/01/2016 0:00<br />
|}<br />
<br />
== Tools ==<br />
<br />
{| class="wikitable sortable"<br />
|+ Road Closure Reports<br />
! Area !! Link <br />
|-<br />
|Statewide || [http://hb.511mn.org/#roadReports/layers=allReports,roadReports,winterDriving,weatherWarnings,otherStates 511mn.org]<br />
|-<br />
|St. Paul || [http://www.stpaul.gov/index.aspx?NID=929 stpaul.gov]<br />
|-<br />
|Hennepin County || [http://www.hennepin.us/residents#transportation hennepin.us]</div>DallasGranthttps://www.waze.com/wiki/USA/index.php?title=Minnesota/Special_roads/Main&diff=99584Minnesota/Special roads/Main2015-03-15T15:32:39Z<p>DallasGrant: /* HOT & Hov Roads/Lanes */</p>
<hr />
<div><!-- 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><!--<br />
------ DO NOT MODIFY ABOVE THIS LINE -------- DO NOT MODIFY ABOVE THIS LINE ------> <br />
=== Other drivable roads ===<br />
<br />
==== Dirt Road / 4X4 Trail[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
{{mbox<br />
| type = important<br />
| text = Minnesota has different interpretations of Dirt Roads than many other locations. Even veteran editors need to pay attention to this section!<br />
}}<br />
<br />
<br />
[[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.<br />
<br />
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.<br />
<br />
[[File:Dirtroad.PNG|300px|right]]<br />
<br />
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. <br />
<br />
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.<br />
<br />
==== Parking Lot Road[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:Parklotrhmmn.png|right|300px]]<br />
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.<br />
<br />
* Simple is best. Do not map every lane<br />
* Map the main entrances from the roads outside the parking lot<br />
* Map lanes that run along storefronts<br />
* Map lanes that run along main roads outside the parking area<br />
* Map primary lanes that serve to get people from one area of the lot to another<br />
<br />
For for information about mapping parking lots, follow this [[Best_map_editing_practice#Parking_Lots|article]]<br />
<br />
==== Private Road[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:Pi gated-community1.jpg|right|300px|Pi gated-community1.jpg]]<br />
<br />
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. <br />
<br />
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. <br />
<br />
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.<br />
<br />
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.<br />
<br />
==== Alleyways[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
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 Parking Lot class.<br />
<br />
[[File:Pizzalola.png|300px|left]]<br />
<br />
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 parking lot 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.<br />
<br />
==== Roundabouts [[Image:Round.png |50px]] ====<br />
<br />
{{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".<br />
[[File:Roundabouts.png|400px|right]]<br />
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. <br />
<br />
<br />
<br />
[[File:Roundboutmn2.png|400px|left]]<br />
<br />
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).<br />
<br />
<br />
<br />
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.<br />
<br />
If at all possible, drive through a roundabout after it has been created or updated. Verify that it seems to give correct information.<br />
<br />
==== HOT & Hov Roads/Lanes ====<br />
[[Image:Hovmn.png|right]]<br />
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.<br />
<br />
These roadways have the following features:<br />
* These lanes/roads allow both toll traffic and HOV traffic to traverse the same lanes.<br />
* There are no toll plazas or booths for paying by cash. All tolls are paid electronically to maintain traffic speed.<br />
* Entrances and exits to the HOT lanes are limited to help maintain high speeds.<br />
* There are no entrance/exit combinations where the toll fare rules don't apply.<br />
* Tolls are discounted or waived for users that meet High Occupancy Vehicle (HOV) requirements. These requirements may change based on time of day.<br />
<br />
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.<br />
<br />
This will all be changing shortly as we find a better way to develop these roads.<br />
<br />
==== Bus or Cab Only Lanes[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
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.<br />
<br />
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.<br />
<br />
==== Emergency Vehicle and DOT Service Roads [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[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}}<br />
<br />
=== Non-drivable roads ===<br />
<br />
==== Railroad [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:RailroadTracksVanishingPoint.jpg|right|300px|RoadPicN11.jpg]]<br />
<br />
<br />
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.<br />
<br />
<br />
<br />
<br />
{{mbox<br />
| type = important<br />
| text = Please notice that railroads have changed from previous interpretations of railroad mapping. Even veteran editors need to pay attention to this section!<br />
}}<br />
<br />
<br />
* 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.<br />
* 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.<br />
* Always select "None" for the city name. This avoids [[Smudged_city#Overview|city smudging]].<br />
* Set railroad to 2-way directionality and Restrict turns ''to'' and ''from'' the railroad segments.<br />
* 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. <br />
* 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.<br />
* Canadian Pacific uses the acronym CPRS, but it is more know as CP, so it will be called CP Railroad<br />
*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.<br />
* Lock all railroads to a Level 2<br />
* 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.<br />
* Read [[Road_types/USA#Railroad|this section]] for more information about railroads.<br />
<br />
==== Runway/Taxiway[[File:Service road.png|200px|Service road.png]] ====<br />
[[File:Aelrwmn.png|right|250px]]<br />
We will map all airports runways such:<br />
<br />
* These roads will not connect to any drivable sections<br />
* The runways will not be connected to each other<br />
* Always select "None" for the city name. This avoids [[Smudged_city#Overview|city smudging]].<br />
* 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.<br />
* After finding the code, we will use [http://www.airnav.com/airports/ this] to find the runway numbers for the airport.<br />
* Most of the time, you will see the number of the runway at the beginning and end of each runway from the aerial views. <br />
* 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".<br />
<br />
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.<br />
<br />
==== Ferry [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
{{mbox<br />
| type = warning<br />
| 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.<br />
}}<br />
<br />
==== Walking Trails [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:RoadPicN9.jpg|right|300px|RoadPicN9.jpg]] <br />
<br />
Even though Waze does not allow for navigating pedestrians or bikers, we will still prepare the map for when it is a function of the application. We will map out trails not only for this reason, but also to avoid speed data from being compiled if a person would leave Waze running on their phone while taking these trails. It also can be useful for a person who may use the map of Waze to recognize his or her location while taking these trails<br />
<br />
* Do not map trails that run parallel to a road unless it is more than 100 Ft from the road<br />
* Do not connect this road type to any drivable section of road<br />
* If the trail has a name, name it [Trail Name] Trail<br />
* Always select "None" for the city name. This avoids [[City smudge|city smudging]].<br />
* 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.<br />
* Use elevation standards as a standard road.<br />
<br />
==== Pedestrian Boardwalks [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:Boardwalksm.jpg|right|300px|RoadPicN10.jpg]] <br />
<br />
Pedestrian Boardwalks are not common, but they are going to be used in sections where a trail would not be appropriate. <br />
<br />
* Do not use these for a standard sidewalk. Sidewalks will not be mapped at all.<br />
* The common use for this will be for large sections that vehicles are not allowed such as an outdoor shopping area or concrete walkway away from roads<br />
* Do not connect this to any drivable road<br />
* Always select "None" for the city name. This avoids [[Smudged_city#Overview|city smudging]].<br />
<br />
==== Stairway [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:RoadPicN11.jpg|right|300px|RoadPicN11.jpg]]<br />
Stairways are very uncommon, but they will be used for any walking section that would require a person to climb a set of stairs to get to the next trail or pedestrian boardwalk. Never connect these to any drivable roads and do not add city names to this section of road. Use the same elevation standards as a road ... if no road or trail is directly underneath, it will be set for ground.<br />
<br />
<br />
<!---- DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ----<br />
-------------------------------------------------------------------------------------<br />
---- This page is only transcluded into (displayed on) the main page for this state.<br />
---- It directly follows the common guidelines applicable to all states. When this<br />
---- page is present (even if blanked), it displaces any optional code that might be<br />
---- in that section.<br />
---- If the original optional code from the main page for this section is still<br />
---- desired, it can be restored by adding the following code to the first line <br />
---- between the "DO NOT MODIFY" lines on this page:<br />
---- {{:USA/CommonState/Special roads|optional}}<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- If there will be a full page for this section, use code similar to the wording<br />
---- below to provide a hyperlink to that page. When creating the full page, use the<br />
---- link on the talk page to ensure the preload data is provided to help with<br />
---- formatting the page. Don't just use the red link from this section once it is<br />
---- saved.<br />
----<br />
See [[{{BasePage2}}/Special roads]] for guidance in {{RootPage2}} that may not be universal to all other states.<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- This section has three possible purposes:<br />
---- 1. It is only providing a hyperlink to the full page for this section.<br />
---- 2. It is only providing some unique guidance for this state that differs from<br />
---- other states.<br />
---- 3. It is intentionally wiping out the general optional content for this section<br />
---- for this state.<br />
------------------------------------------------------------------------------------></div>DallasGranthttps://www.waze.com/wiki/USA/index.php?title=File:Hovmn.png&diff=99548File:Hovmn.png2015-03-15T07:22:24Z<p>DallasGrant: </p>
<hr />
<div></div>DallasGranthttps://www.waze.com/wiki/USA/index.php?title=Minnesota/Special_roads/Main&diff=99547Minnesota/Special roads/Main2015-03-15T07:15:52Z<p>DallasGrant: /* HOT & Hov Roads/Lanes */</p>
<hr />
<div><!-- 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><!--<br />
------ DO NOT MODIFY ABOVE THIS LINE -------- DO NOT MODIFY ABOVE THIS LINE ------> <br />
=== Other drivable roads ===<br />
<br />
==== Dirt Road / 4X4 Trail[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
{{mbox<br />
| type = important<br />
| text = Minnesota has different interpretations of Dirt Roads than many other locations. Even veteran editors need to pay attention to this section!<br />
}}<br />
<br />
<br />
[[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.<br />
<br />
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.<br />
<br />
[[File:Dirtroad.PNG|300px|right]]<br />
<br />
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. <br />
<br />
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.<br />
<br />
==== Parking Lot Road[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:Parklotrhmmn.png|right|300px]]<br />
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.<br />
<br />
* Simple is best. Do not map every lane<br />
* Map the main entrances from the roads outside the parking lot<br />
* Map lanes that run along storefronts<br />
* Map lanes that run along main roads outside the parking area<br />
* Map primary lanes that serve to get people from one area of the lot to another<br />
<br />
For for information about mapping parking lots, follow this [[Best_map_editing_practice#Parking_Lots|article]]<br />
<br />
==== Private Road[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:Pi gated-community1.jpg|right|300px|Pi gated-community1.jpg]]<br />
<br />
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. <br />
<br />
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. <br />
<br />
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.<br />
<br />
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.<br />
<br />
==== Alleyways[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
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 Parking Lot class.<br />
<br />
[[File:Pizzalola.png|300px|left]]<br />
<br />
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 parking lot 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.<br />
<br />
==== Roundabouts [[Image:Round.png |50px]] ====<br />
<br />
{{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".<br />
[[File:Roundabouts.png|400px|right]]<br />
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. <br />
<br />
<br />
<br />
[[File:Roundboutmn2.png|400px|left]]<br />
<br />
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).<br />
<br />
<br />
<br />
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.<br />
<br />
If at all possible, drive through a roundabout after it has been created or updated. Verify that it seems to give correct information.<br />
<br />
==== HOT & Hov Roads/Lanes ====<br />
[[Image:I-15-express-lanes.jpg|right]]<br />
<br />
==== Bus or Cab Only Lanes[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
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.<br />
<br />
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.<br />
<br />
==== Emergency Vehicle and DOT Service Roads [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[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}}<br />
<br />
=== Non-drivable roads ===<br />
<br />
==== Railroad [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:RailroadTracksVanishingPoint.jpg|right|300px|RoadPicN11.jpg]]<br />
<br />
<br />
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.<br />
<br />
<br />
<br />
<br />
{{mbox<br />
| type = important<br />
| text = Please notice that railroads have changed from previous interpretations of railroad mapping. Even veteran editors need to pay attention to this section!<br />
}}<br />
<br />
<br />
* 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.<br />
* 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.<br />
* Always select "None" for the city name. This avoids [[Smudged_city#Overview|city smudging]].<br />
* Set railroad to 2-way directionality and Restrict turns ''to'' and ''from'' the railroad segments.<br />
* 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. <br />
* 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.<br />
* Canadian Pacific uses the acronym CPRS, but it is more know as CP, so it will be called CP Railroad<br />
*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.<br />
* Lock all railroads to a Level 2<br />
* 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.<br />
* Read [[Road_types/USA#Railroad|this section]] for more information about railroads.<br />
<br />
==== Runway/Taxiway[[File:Service road.png|200px|Service road.png]] ====<br />
[[File:Aelrwmn.png|right|250px]]<br />
We will map all airports runways such:<br />
<br />
* These roads will not connect to any drivable sections<br />
* The runways will not be connected to each other<br />
* Always select "None" for the city name. This avoids [[Smudged_city#Overview|city smudging]].<br />
* 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.<br />
* After finding the code, we will use [http://www.airnav.com/airports/ this] to find the runway numbers for the airport.<br />
* Most of the time, you will see the number of the runway at the beginning and end of each runway from the aerial views. <br />
* 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".<br />
<br />
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.<br />
<br />
==== Ferry [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
{{mbox<br />
| type = warning<br />
| 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.<br />
}}<br />
<br />
==== Walking Trails [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:RoadPicN9.jpg|right|300px|RoadPicN9.jpg]] <br />
<br />
Even though Waze does not allow for navigating pedestrians or bikers, we will still prepare the map for when it is a function of the application. We will map out trails not only for this reason, but also to avoid speed data from being compiled if a person would leave Waze running on their phone while taking these trails. It also can be useful for a person who may use the map of Waze to recognize his or her location while taking these trails<br />
<br />
* Do not map trails that run parallel to a road unless it is more than 100 Ft from the road<br />
* Do not connect this road type to any drivable section of road<br />
* If the trail has a name, name it [Trail Name] Trail<br />
* Always select "None" for the city name. This avoids [[City smudge|city smudging]].<br />
* 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.<br />
* Use elevation standards as a standard road.<br />
<br />
==== Pedestrian Boardwalks [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:Boardwalksm.jpg|right|300px|RoadPicN10.jpg]] <br />
<br />
Pedestrian Boardwalks are not common, but they are going to be used in sections where a trail would not be appropriate. <br />
<br />
* Do not use these for a standard sidewalk. Sidewalks will not be mapped at all.<br />
* The common use for this will be for large sections that vehicles are not allowed such as an outdoor shopping area or concrete walkway away from roads<br />
* Do not connect this to any drivable road<br />
* Always select "None" for the city name. This avoids [[Smudged_city#Overview|city smudging]].<br />
<br />
==== Stairway [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:RoadPicN11.jpg|right|300px|RoadPicN11.jpg]]<br />
Stairways are very uncommon, but they will be used for any walking section that would require a person to climb a set of stairs to get to the next trail or pedestrian boardwalk. Never connect these to any drivable roads and do not add city names to this section of road. Use the same elevation standards as a road ... if no road or trail is directly underneath, it will be set for ground.<br />
<br />
<br />
<!---- DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ----<br />
-------------------------------------------------------------------------------------<br />
---- This page is only transcluded into (displayed on) the main page for this state.<br />
---- It directly follows the common guidelines applicable to all states. When this<br />
---- page is present (even if blanked), it displaces any optional code that might be<br />
---- in that section.<br />
---- If the original optional code from the main page for this section is still<br />
---- desired, it can be restored by adding the following code to the first line <br />
---- between the "DO NOT MODIFY" lines on this page:<br />
---- {{:USA/CommonState/Special roads|optional}}<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- If there will be a full page for this section, use code similar to the wording<br />
---- below to provide a hyperlink to that page. When creating the full page, use the<br />
---- link on the talk page to ensure the preload data is provided to help with<br />
---- formatting the page. Don't just use the red link from this section once it is<br />
---- saved.<br />
----<br />
See [[{{BasePage2}}/Special roads]] for guidance in {{RootPage2}} that may not be universal to all other states.<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- This section has three possible purposes:<br />
---- 1. It is only providing a hyperlink to the full page for this section.<br />
---- 2. It is only providing some unique guidance for this state that differs from<br />
---- other states.<br />
---- 3. It is intentionally wiping out the general optional content for this section<br />
---- for this state.<br />
------------------------------------------------------------------------------------></div>DallasGranthttps://www.waze.com/wiki/USA/index.php?title=Minnesota/Special_roads/Main&diff=99546Minnesota/Special roads/Main2015-03-15T07:13:31Z<p>DallasGrant: /* Other drivable roads */</p>
<hr />
<div><!-- 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><!--<br />
------ DO NOT MODIFY ABOVE THIS LINE -------- DO NOT MODIFY ABOVE THIS LINE ------> <br />
=== Other drivable roads ===<br />
<br />
==== Dirt Road / 4X4 Trail[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
{{mbox<br />
| type = important<br />
| text = Minnesota has different interpretations of Dirt Roads than many other locations. Even veteran editors need to pay attention to this section!<br />
}}<br />
<br />
<br />
[[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.<br />
<br />
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.<br />
<br />
[[File:Dirtroad.PNG|300px|right]]<br />
<br />
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. <br />
<br />
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.<br />
<br />
==== Parking Lot Road[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:Parklotrhmmn.png|right|300px]]<br />
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.<br />
<br />
* Simple is best. Do not map every lane<br />
* Map the main entrances from the roads outside the parking lot<br />
* Map lanes that run along storefronts<br />
* Map lanes that run along main roads outside the parking area<br />
* Map primary lanes that serve to get people from one area of the lot to another<br />
<br />
For for information about mapping parking lots, follow this [[Best_map_editing_practice#Parking_Lots|article]]<br />
<br />
==== Private Road[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:Pi gated-community1.jpg|right|300px|Pi gated-community1.jpg]]<br />
<br />
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. <br />
<br />
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. <br />
<br />
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.<br />
<br />
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.<br />
<br />
==== Alleyways[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
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 Parking Lot class.<br />
<br />
[[File:Pizzalola.png|300px|left]]<br />
<br />
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 parking lot 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.<br />
<br />
==== Roundabouts [[Image:Round.png |50px]] ====<br />
<br />
{{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".<br />
[[File:Roundabouts.png|400px|right]]<br />
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. <br />
<br />
<br />
<br />
[[File:Roundboutmn2.png|400px|left]]<br />
<br />
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).<br />
<br />
<br />
<br />
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.<br />
<br />
If at all possible, drive through a roundabout after it has been created or updated. Verify that it seems to give correct information.<br />
<br />
==== HOT & Hov Roads/Lanes ====<br />
[[Image:I-15-express-lanes.jpg]]<br />
<br />
<br />
==== Bus or Cab Only Lanes[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
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.<br />
<br />
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.<br />
<br />
==== Emergency Vehicle and DOT Service Roads [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[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}}<br />
<br />
=== Non-drivable roads ===<br />
<br />
==== Railroad [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:RailroadTracksVanishingPoint.jpg|right|300px|RoadPicN11.jpg]]<br />
<br />
<br />
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.<br />
<br />
<br />
<br />
<br />
{{mbox<br />
| type = important<br />
| text = Please notice that railroads have changed from previous interpretations of railroad mapping. Even veteran editors need to pay attention to this section!<br />
}}<br />
<br />
<br />
* 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.<br />
* 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.<br />
* Always select "None" for the city name. This avoids [[Smudged_city#Overview|city smudging]].<br />
* Set railroad to 2-way directionality and Restrict turns ''to'' and ''from'' the railroad segments.<br />
* 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. <br />
* 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.<br />
* Canadian Pacific uses the acronym CPRS, but it is more know as CP, so it will be called CP Railroad<br />
*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.<br />
* Lock all railroads to a Level 2<br />
* 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.<br />
* Read [[Road_types/USA#Railroad|this section]] for more information about railroads.<br />
<br />
==== Runway/Taxiway[[File:Service road.png|200px|Service road.png]] ====<br />
[[File:Aelrwmn.png|right|250px]]<br />
We will map all airports runways such:<br />
<br />
* These roads will not connect to any drivable sections<br />
* The runways will not be connected to each other<br />
* Always select "None" for the city name. This avoids [[Smudged_city#Overview|city smudging]].<br />
* 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.<br />
* After finding the code, we will use [http://www.airnav.com/airports/ this] to find the runway numbers for the airport.<br />
* Most of the time, you will see the number of the runway at the beginning and end of each runway from the aerial views. <br />
* 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".<br />
<br />
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.<br />
<br />
==== Ferry [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
{{mbox<br />
| type = warning<br />
| 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.<br />
}}<br />
<br />
==== Walking Trails [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:RoadPicN9.jpg|right|300px|RoadPicN9.jpg]] <br />
<br />
Even though Waze does not allow for navigating pedestrians or bikers, we will still prepare the map for when it is a function of the application. We will map out trails not only for this reason, but also to avoid speed data from being compiled if a person would leave Waze running on their phone while taking these trails. It also can be useful for a person who may use the map of Waze to recognize his or her location while taking these trails<br />
<br />
* Do not map trails that run parallel to a road unless it is more than 100 Ft from the road<br />
* Do not connect this road type to any drivable section of road<br />
* If the trail has a name, name it [Trail Name] Trail<br />
* Always select "None" for the city name. This avoids [[City smudge|city smudging]].<br />
* 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.<br />
* Use elevation standards as a standard road.<br />
<br />
==== Pedestrian Boardwalks [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:Boardwalksm.jpg|right|300px|RoadPicN10.jpg]] <br />
<br />
Pedestrian Boardwalks are not common, but they are going to be used in sections where a trail would not be appropriate. <br />
<br />
* Do not use these for a standard sidewalk. Sidewalks will not be mapped at all.<br />
* The common use for this will be for large sections that vehicles are not allowed such as an outdoor shopping area or concrete walkway away from roads<br />
* Do not connect this to any drivable road<br />
* Always select "None" for the city name. This avoids [[Smudged_city#Overview|city smudging]].<br />
<br />
==== Stairway [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:RoadPicN11.jpg|right|300px|RoadPicN11.jpg]]<br />
Stairways are very uncommon, but they will be used for any walking section that would require a person to climb a set of stairs to get to the next trail or pedestrian boardwalk. Never connect these to any drivable roads and do not add city names to this section of road. Use the same elevation standards as a road ... if no road or trail is directly underneath, it will be set for ground.<br />
<br />
<br />
<!---- DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ----<br />
-------------------------------------------------------------------------------------<br />
---- This page is only transcluded into (displayed on) the main page for this state.<br />
---- It directly follows the common guidelines applicable to all states. When this<br />
---- page is present (even if blanked), it displaces any optional code that might be<br />
---- in that section.<br />
---- If the original optional code from the main page for this section is still<br />
---- desired, it can be restored by adding the following code to the first line <br />
---- between the "DO NOT MODIFY" lines on this page:<br />
---- {{:USA/CommonState/Special roads|optional}}<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- If there will be a full page for this section, use code similar to the wording<br />
---- below to provide a hyperlink to that page. When creating the full page, use the<br />
---- link on the talk page to ensure the preload data is provided to help with<br />
---- formatting the page. Don't just use the red link from this section once it is<br />
---- saved.<br />
----<br />
See [[{{BasePage2}}/Special roads]] for guidance in {{RootPage2}} that may not be universal to all other states.<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- This section has three possible purposes:<br />
---- 1. It is only providing a hyperlink to the full page for this section.<br />
---- 2. It is only providing some unique guidance for this state that differs from<br />
---- other states.<br />
---- 3. It is intentionally wiping out the general optional content for this section<br />
---- for this state.<br />
------------------------------------------------------------------------------------></div>DallasGranthttps://www.waze.com/wiki/USA/index.php?title=Minnesota/Special_roads/Main&diff=99545Minnesota/Special roads/Main2015-03-15T07:03:26Z<p>DallasGrant: /* Emergency Vehicle and DOT Service Roads 200px|Service road.png */</p>
<hr />
<div><!-- 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><!--<br />
------ DO NOT MODIFY ABOVE THIS LINE -------- DO NOT MODIFY ABOVE THIS LINE ------> <br />
=== Other drivable roads ===<br />
<br />
==== Dirt Road / 4X4 Trail[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
{{mbox<br />
| type = important<br />
| text = Minnesota has different interpretations of Dirt Roads than many other locations. Even veteran editors need to pay attention to this section!<br />
}}<br />
<br />
<br />
[[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.<br />
<br />
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.<br />
<br />
[[File:Dirtroad.PNG|300px|right]]<br />
<br />
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. <br />
<br />
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.<br />
<br />
==== Parking Lot Road[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:Parklotrhmmn.png|right|300px]]<br />
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.<br />
<br />
* Simple is best. Do not map every lane<br />
* Map the main entrances from the roads outside the parking lot<br />
* Map lanes that run along storefronts<br />
* Map lanes that run along main roads outside the parking area<br />
* Map primary lanes that serve to get people from one area of the lot to another<br />
<br />
For for information about mapping parking lots, follow this [[Best_map_editing_practice#Parking_Lots|article]]<br />
<br />
==== Private Road[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:Pi gated-community1.jpg|right|300px|Pi gated-community1.jpg]]<br />
<br />
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. <br />
<br />
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. <br />
<br />
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.<br />
<br />
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.<br />
<br />
==== Alleyways[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
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 Parking Lot class.<br />
<br />
[[File:Pizzalola.png|300px|left]]<br />
<br />
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 parking lot 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.<br />
<br />
==== Roundabouts [[Image:Round.png |50px]] ====<br />
<br />
{{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".<br />
[[File:Roundabouts.png|400px|right]]<br />
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. <br />
<br />
<br />
<br />
[[File:Roundboutmn2.png|400px|left]]<br />
<br />
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).<br />
<br />
<br />
<br />
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.<br />
<br />
If at all possible, drive through a roundabout after it has been created or updated. Verify that it seems to give correct information.<br />
<br />
==== Bus or Cab Only Lanes[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
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.<br />
<br />
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.<br />
<br />
==== Emergency Vehicle and DOT Service Roads [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[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}}<br />
<br />
=== Non-drivable roads ===<br />
<br />
==== Railroad [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:RailroadTracksVanishingPoint.jpg|right|300px|RoadPicN11.jpg]]<br />
<br />
<br />
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.<br />
<br />
<br />
<br />
<br />
{{mbox<br />
| type = important<br />
| text = Please notice that railroads have changed from previous interpretations of railroad mapping. Even veteran editors need to pay attention to this section!<br />
}}<br />
<br />
<br />
* 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.<br />
* 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.<br />
* Always select "None" for the city name. This avoids [[Smudged_city#Overview|city smudging]].<br />
* Set railroad to 2-way directionality and Restrict turns ''to'' and ''from'' the railroad segments.<br />
* 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. <br />
* 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.<br />
* Canadian Pacific uses the acronym CPRS, but it is more know as CP, so it will be called CP Railroad<br />
*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.<br />
* Lock all railroads to a Level 2<br />
* 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.<br />
* Read [[Road_types/USA#Railroad|this section]] for more information about railroads.<br />
<br />
==== Runway/Taxiway[[File:Service road.png|200px|Service road.png]] ====<br />
[[File:Aelrwmn.png|right|250px]]<br />
We will map all airports runways such:<br />
<br />
* These roads will not connect to any drivable sections<br />
* The runways will not be connected to each other<br />
* Always select "None" for the city name. This avoids [[Smudged_city#Overview|city smudging]].<br />
* 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.<br />
* After finding the code, we will use [http://www.airnav.com/airports/ this] to find the runway numbers for the airport.<br />
* Most of the time, you will see the number of the runway at the beginning and end of each runway from the aerial views. <br />
* 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".<br />
<br />
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.<br />
<br />
==== Ferry [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
{{mbox<br />
| type = warning<br />
| 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.<br />
}}<br />
<br />
==== Walking Trails [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:RoadPicN9.jpg|right|300px|RoadPicN9.jpg]] <br />
<br />
Even though Waze does not allow for navigating pedestrians or bikers, we will still prepare the map for when it is a function of the application. We will map out trails not only for this reason, but also to avoid speed data from being compiled if a person would leave Waze running on their phone while taking these trails. It also can be useful for a person who may use the map of Waze to recognize his or her location while taking these trails<br />
<br />
* Do not map trails that run parallel to a road unless it is more than 100 Ft from the road<br />
* Do not connect this road type to any drivable section of road<br />
* If the trail has a name, name it [Trail Name] Trail<br />
* Always select "None" for the city name. This avoids [[City smudge|city smudging]].<br />
* 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.<br />
* Use elevation standards as a standard road.<br />
<br />
==== Pedestrian Boardwalks [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:Boardwalksm.jpg|right|300px|RoadPicN10.jpg]] <br />
<br />
Pedestrian Boardwalks are not common, but they are going to be used in sections where a trail would not be appropriate. <br />
<br />
* Do not use these for a standard sidewalk. Sidewalks will not be mapped at all.<br />
* The common use for this will be for large sections that vehicles are not allowed such as an outdoor shopping area or concrete walkway away from roads<br />
* Do not connect this to any drivable road<br />
* Always select "None" for the city name. This avoids [[Smudged_city#Overview|city smudging]].<br />
<br />
==== Stairway [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:RoadPicN11.jpg|right|300px|RoadPicN11.jpg]]<br />
Stairways are very uncommon, but they will be used for any walking section that would require a person to climb a set of stairs to get to the next trail or pedestrian boardwalk. Never connect these to any drivable roads and do not add city names to this section of road. Use the same elevation standards as a road ... if no road or trail is directly underneath, it will be set for ground.<br />
<br />
<br />
<!---- DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ----<br />
-------------------------------------------------------------------------------------<br />
---- This page is only transcluded into (displayed on) the main page for this state.<br />
---- It directly follows the common guidelines applicable to all states. When this<br />
---- page is present (even if blanked), it displaces any optional code that might be<br />
---- in that section.<br />
---- If the original optional code from the main page for this section is still<br />
---- desired, it can be restored by adding the following code to the first line <br />
---- between the "DO NOT MODIFY" lines on this page:<br />
---- {{:USA/CommonState/Special roads|optional}}<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- If there will be a full page for this section, use code similar to the wording<br />
---- below to provide a hyperlink to that page. When creating the full page, use the<br />
---- link on the talk page to ensure the preload data is provided to help with<br />
---- formatting the page. Don't just use the red link from this section once it is<br />
---- saved.<br />
----<br />
See [[{{BasePage2}}/Special roads]] for guidance in {{RootPage2}} that may not be universal to all other states.<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- This section has three possible purposes:<br />
---- 1. It is only providing a hyperlink to the full page for this section.<br />
---- 2. It is only providing some unique guidance for this state that differs from<br />
---- other states.<br />
---- 3. It is intentionally wiping out the general optional content for this section<br />
---- for this state.<br />
------------------------------------------------------------------------------------></div>DallasGranthttps://www.waze.com/wiki/USA/index.php?title=Minnesota/Special_roads/Main&diff=99544Minnesota/Special roads/Main2015-03-15T07:03:05Z<p>DallasGrant: /* Emergency Vehicle and DOT Service Roads 200px|Service road.png */</p>
<hr />
<div><!-- 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><!--<br />
------ DO NOT MODIFY ABOVE THIS LINE -------- DO NOT MODIFY ABOVE THIS LINE ------> <br />
=== Other drivable roads ===<br />
<br />
==== Dirt Road / 4X4 Trail[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
{{mbox<br />
| type = important<br />
| text = Minnesota has different interpretations of Dirt Roads than many other locations. Even veteran editors need to pay attention to this section!<br />
}}<br />
<br />
<br />
[[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.<br />
<br />
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.<br />
<br />
[[File:Dirtroad.PNG|300px|right]]<br />
<br />
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. <br />
<br />
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.<br />
<br />
==== Parking Lot Road[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:Parklotrhmmn.png|right|300px]]<br />
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.<br />
<br />
* Simple is best. Do not map every lane<br />
* Map the main entrances from the roads outside the parking lot<br />
* Map lanes that run along storefronts<br />
* Map lanes that run along main roads outside the parking area<br />
* Map primary lanes that serve to get people from one area of the lot to another<br />
<br />
For for information about mapping parking lots, follow this [[Best_map_editing_practice#Parking_Lots|article]]<br />
<br />
==== Private Road[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:Pi gated-community1.jpg|right|300px|Pi gated-community1.jpg]]<br />
<br />
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. <br />
<br />
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. <br />
<br />
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.<br />
<br />
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.<br />
<br />
==== Alleyways[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
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 Parking Lot class.<br />
<br />
[[File:Pizzalola.png|300px|left]]<br />
<br />
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 parking lot 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.<br />
<br />
==== Roundabouts [[Image:Round.png |50px]] ====<br />
<br />
{{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".<br />
[[File:Roundabouts.png|400px|right]]<br />
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. <br />
<br />
<br />
<br />
[[File:Roundboutmn2.png|400px|left]]<br />
<br />
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).<br />
<br />
<br />
<br />
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.<br />
<br />
If at all possible, drive through a roundabout after it has been created or updated. Verify that it seems to give correct information.<br />
<br />
==== Bus or Cab Only Lanes[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
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.<br />
<br />
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.<br />
<br />
=== Emergency Vehicle and DOT Service Roads [[File:Service road.png|200px|Service road.png]] ===<br />
<br />
[[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}}<br />
<br />
=== Non-drivable roads ===<br />
<br />
==== Railroad [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:RailroadTracksVanishingPoint.jpg|right|300px|RoadPicN11.jpg]]<br />
<br />
<br />
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.<br />
<br />
<br />
<br />
<br />
{{mbox<br />
| type = important<br />
| text = Please notice that railroads have changed from previous interpretations of railroad mapping. Even veteran editors need to pay attention to this section!<br />
}}<br />
<br />
<br />
* 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.<br />
* 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.<br />
* Always select "None" for the city name. This avoids [[Smudged_city#Overview|city smudging]].<br />
* Set railroad to 2-way directionality and Restrict turns ''to'' and ''from'' the railroad segments.<br />
* 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. <br />
* 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.<br />
* Canadian Pacific uses the acronym CPRS, but it is more know as CP, so it will be called CP Railroad<br />
*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.<br />
* Lock all railroads to a Level 2<br />
* 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.<br />
* Read [[Road_types/USA#Railroad|this section]] for more information about railroads.<br />
<br />
==== Runway/Taxiway[[File:Service road.png|200px|Service road.png]] ====<br />
[[File:Aelrwmn.png|right|250px]]<br />
We will map all airports runways such:<br />
<br />
* These roads will not connect to any drivable sections<br />
* The runways will not be connected to each other<br />
* Always select "None" for the city name. This avoids [[Smudged_city#Overview|city smudging]].<br />
* 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.<br />
* After finding the code, we will use [http://www.airnav.com/airports/ this] to find the runway numbers for the airport.<br />
* Most of the time, you will see the number of the runway at the beginning and end of each runway from the aerial views. <br />
* 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".<br />
<br />
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.<br />
<br />
==== Ferry [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
{{mbox<br />
| type = warning<br />
| 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.<br />
}}<br />
<br />
==== Walking Trails [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:RoadPicN9.jpg|right|300px|RoadPicN9.jpg]] <br />
<br />
Even though Waze does not allow for navigating pedestrians or bikers, we will still prepare the map for when it is a function of the application. We will map out trails not only for this reason, but also to avoid speed data from being compiled if a person would leave Waze running on their phone while taking these trails. It also can be useful for a person who may use the map of Waze to recognize his or her location while taking these trails<br />
<br />
* Do not map trails that run parallel to a road unless it is more than 100 Ft from the road<br />
* Do not connect this road type to any drivable section of road<br />
* If the trail has a name, name it [Trail Name] Trail<br />
* Always select "None" for the city name. This avoids [[City smudge|city smudging]].<br />
* 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.<br />
* Use elevation standards as a standard road.<br />
<br />
==== Pedestrian Boardwalks [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:Boardwalksm.jpg|right|300px|RoadPicN10.jpg]] <br />
<br />
Pedestrian Boardwalks are not common, but they are going to be used in sections where a trail would not be appropriate. <br />
<br />
* Do not use these for a standard sidewalk. Sidewalks will not be mapped at all.<br />
* The common use for this will be for large sections that vehicles are not allowed such as an outdoor shopping area or concrete walkway away from roads<br />
* Do not connect this to any drivable road<br />
* Always select "None" for the city name. This avoids [[Smudged_city#Overview|city smudging]].<br />
<br />
==== Stairway [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:RoadPicN11.jpg|right|300px|RoadPicN11.jpg]]<br />
Stairways are very uncommon, but they will be used for any walking section that would require a person to climb a set of stairs to get to the next trail or pedestrian boardwalk. Never connect these to any drivable roads and do not add city names to this section of road. Use the same elevation standards as a road ... if no road or trail is directly underneath, it will be set for ground.<br />
<br />
<br />
<!---- DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ----<br />
-------------------------------------------------------------------------------------<br />
---- This page is only transcluded into (displayed on) the main page for this state.<br />
---- It directly follows the common guidelines applicable to all states. When this<br />
---- page is present (even if blanked), it displaces any optional code that might be<br />
---- in that section.<br />
---- If the original optional code from the main page for this section is still<br />
---- desired, it can be restored by adding the following code to the first line <br />
---- between the "DO NOT MODIFY" lines on this page:<br />
---- {{:USA/CommonState/Special roads|optional}}<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- If there will be a full page for this section, use code similar to the wording<br />
---- below to provide a hyperlink to that page. When creating the full page, use the<br />
---- link on the talk page to ensure the preload data is provided to help with<br />
---- formatting the page. Don't just use the red link from this section once it is<br />
---- saved.<br />
----<br />
See [[{{BasePage2}}/Special roads]] for guidance in {{RootPage2}} that may not be universal to all other states.<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- This section has three possible purposes:<br />
---- 1. It is only providing a hyperlink to the full page for this section.<br />
---- 2. It is only providing some unique guidance for this state that differs from<br />
---- other states.<br />
---- 3. It is intentionally wiping out the general optional content for this section<br />
---- for this state.<br />
------------------------------------------------------------------------------------></div>DallasGranthttps://www.waze.com/wiki/USA/index.php?title=Minnesota/Special_roads/Main&diff=99543Minnesota/Special roads/Main2015-03-15T07:02:40Z<p>DallasGrant: /* Other drivable roads */</p>
<hr />
<div><!-- 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><!--<br />
------ DO NOT MODIFY ABOVE THIS LINE -------- DO NOT MODIFY ABOVE THIS LINE ------> <br />
=== Other drivable roads ===<br />
<br />
==== Dirt Road / 4X4 Trail[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
{{mbox<br />
| type = important<br />
| text = Minnesota has different interpretations of Dirt Roads than many other locations. Even veteran editors need to pay attention to this section!<br />
}}<br />
<br />
<br />
[[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.<br />
<br />
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.<br />
<br />
[[File:Dirtroad.PNG|300px|right]]<br />
<br />
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. <br />
<br />
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.<br />
<br />
==== Parking Lot Road[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:Parklotrhmmn.png|right|300px]]<br />
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.<br />
<br />
* Simple is best. Do not map every lane<br />
* Map the main entrances from the roads outside the parking lot<br />
* Map lanes that run along storefronts<br />
* Map lanes that run along main roads outside the parking area<br />
* Map primary lanes that serve to get people from one area of the lot to another<br />
<br />
For for information about mapping parking lots, follow this [[Best_map_editing_practice#Parking_Lots|article]]<br />
<br />
==== Private Road[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:Pi gated-community1.jpg|right|300px|Pi gated-community1.jpg]]<br />
<br />
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. <br />
<br />
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. <br />
<br />
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.<br />
<br />
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.<br />
<br />
==== Alleyways[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
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 Parking Lot class.<br />
<br />
[[File:Pizzalola.png|300px|left]]<br />
<br />
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 parking lot 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.<br />
<br />
==== Roundabouts [[Image:Round.png |50px]] ====<br />
<br />
{{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".<br />
[[File:Roundabouts.png|400px|right]]<br />
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. <br />
<br />
<br />
<br />
[[File:Roundboutmn2.png|400px|left]]<br />
<br />
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).<br />
<br />
<br />
<br />
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.<br />
<br />
If at all possible, drive through a roundabout after it has been created or updated. Verify that it seems to give correct information.<br />
<br />
==== Bus or Cab Only Lanes[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
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.<br />
<br />
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.<br />
<br />
=== Emergency Vehicle and DOT Service Roads [[File:Service road.png|200px|Service road.png]] ===<br />
<br />
[[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}<br />
<br />
=== Non-drivable roads ===<br />
<br />
==== Railroad [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:RailroadTracksVanishingPoint.jpg|right|300px|RoadPicN11.jpg]]<br />
<br />
<br />
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.<br />
<br />
<br />
<br />
<br />
{{mbox<br />
| type = important<br />
| text = Please notice that railroads have changed from previous interpretations of railroad mapping. Even veteran editors need to pay attention to this section!<br />
}}<br />
<br />
<br />
* 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.<br />
* 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.<br />
* Always select "None" for the city name. This avoids [[Smudged_city#Overview|city smudging]].<br />
* Set railroad to 2-way directionality and Restrict turns ''to'' and ''from'' the railroad segments.<br />
* 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. <br />
* 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.<br />
* Canadian Pacific uses the acronym CPRS, but it is more know as CP, so it will be called CP Railroad<br />
*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.<br />
* Lock all railroads to a Level 2<br />
* 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.<br />
* Read [[Road_types/USA#Railroad|this section]] for more information about railroads.<br />
<br />
==== Runway/Taxiway[[File:Service road.png|200px|Service road.png]] ====<br />
[[File:Aelrwmn.png|right|250px]]<br />
We will map all airports runways such:<br />
<br />
* These roads will not connect to any drivable sections<br />
* The runways will not be connected to each other<br />
* Always select "None" for the city name. This avoids [[Smudged_city#Overview|city smudging]].<br />
* 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.<br />
* After finding the code, we will use [http://www.airnav.com/airports/ this] to find the runway numbers for the airport.<br />
* Most of the time, you will see the number of the runway at the beginning and end of each runway from the aerial views. <br />
* 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".<br />
<br />
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.<br />
<br />
==== Ferry [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
{{mbox<br />
| type = warning<br />
| 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.<br />
}}<br />
<br />
==== Walking Trails [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:RoadPicN9.jpg|right|300px|RoadPicN9.jpg]] <br />
<br />
Even though Waze does not allow for navigating pedestrians or bikers, we will still prepare the map for when it is a function of the application. We will map out trails not only for this reason, but also to avoid speed data from being compiled if a person would leave Waze running on their phone while taking these trails. It also can be useful for a person who may use the map of Waze to recognize his or her location while taking these trails<br />
<br />
* Do not map trails that run parallel to a road unless it is more than 100 Ft from the road<br />
* Do not connect this road type to any drivable section of road<br />
* If the trail has a name, name it [Trail Name] Trail<br />
* Always select "None" for the city name. This avoids [[City smudge|city smudging]].<br />
* 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.<br />
* Use elevation standards as a standard road.<br />
<br />
==== Pedestrian Boardwalks [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:Boardwalksm.jpg|right|300px|RoadPicN10.jpg]] <br />
<br />
Pedestrian Boardwalks are not common, but they are going to be used in sections where a trail would not be appropriate. <br />
<br />
* Do not use these for a standard sidewalk. Sidewalks will not be mapped at all.<br />
* The common use for this will be for large sections that vehicles are not allowed such as an outdoor shopping area or concrete walkway away from roads<br />
* Do not connect this to any drivable road<br />
* Always select "None" for the city name. This avoids [[Smudged_city#Overview|city smudging]].<br />
<br />
==== Stairway [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:RoadPicN11.jpg|right|300px|RoadPicN11.jpg]]<br />
Stairways are very uncommon, but they will be used for any walking section that would require a person to climb a set of stairs to get to the next trail or pedestrian boardwalk. Never connect these to any drivable roads and do not add city names to this section of road. Use the same elevation standards as a road ... if no road or trail is directly underneath, it will be set for ground.<br />
<br />
<br />
<!---- DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ----<br />
-------------------------------------------------------------------------------------<br />
---- This page is only transcluded into (displayed on) the main page for this state.<br />
---- It directly follows the common guidelines applicable to all states. When this<br />
---- page is present (even if blanked), it displaces any optional code that might be<br />
---- in that section.<br />
---- If the original optional code from the main page for this section is still<br />
---- desired, it can be restored by adding the following code to the first line <br />
---- between the "DO NOT MODIFY" lines on this page:<br />
---- {{:USA/CommonState/Special roads|optional}}<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- If there will be a full page for this section, use code similar to the wording<br />
---- below to provide a hyperlink to that page. When creating the full page, use the<br />
---- link on the talk page to ensure the preload data is provided to help with<br />
---- formatting the page. Don't just use the red link from this section once it is<br />
---- saved.<br />
----<br />
See [[{{BasePage2}}/Special roads]] for guidance in {{RootPage2}} that may not be universal to all other states.<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- This section has three possible purposes:<br />
---- 1. It is only providing a hyperlink to the full page for this section.<br />
---- 2. It is only providing some unique guidance for this state that differs from<br />
---- other states.<br />
---- 3. It is intentionally wiping out the general optional content for this section<br />
---- for this state.<br />
------------------------------------------------------------------------------------></div>DallasGranthttps://www.waze.com/wiki/USA/index.php?title=Minnesota/Special_roads/Main&diff=99540Minnesota/Special roads/Main2015-03-15T06:58:05Z<p>DallasGrant: /* Non-drivable roads */</p>
<hr />
<div><!-- 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><!--<br />
------ DO NOT MODIFY ABOVE THIS LINE -------- DO NOT MODIFY ABOVE THIS LINE ------> <br />
=== Other drivable roads ===<br />
<br />
==== Dirt Road / 4X4 Trail[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
{{mbox<br />
| type = important<br />
| text = Minnesota has different interpretations of Dirt Roads than many other locations. Even veteran editors need to pay attention to this section!<br />
}}<br />
<br />
<br />
[[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.<br />
<br />
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.<br />
<br />
[[File:Dirtroad.PNG|300px|right]]<br />
<br />
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. <br />
<br />
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.<br />
<br />
==== Parking Lot Road[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:Parklotrhmmn.png|right|300px]]<br />
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.<br />
<br />
* Simple is best. Do not map every lane<br />
* Map the main entrances from the roads outside the parking lot<br />
* Map lanes that run along storefronts<br />
* Map lanes that run along main roads outside the parking area<br />
* Map primary lanes that serve to get people from one area of the lot to another<br />
<br />
For for information about mapping parking lots, follow this [[Best_map_editing_practice#Parking_Lots|article]]<br />
<br />
==== Private Road[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:Pi gated-community1.jpg|right|300px|Pi gated-community1.jpg]]<br />
<br />
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. <br />
<br />
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. <br />
<br />
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.<br />
<br />
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.<br />
<br />
==== Alleyways[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
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 Parking Lot class.<br />
<br />
[[File:Pizzalola.png|300px|left]]<br />
<br />
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 parking lot 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.<br />
<br />
==== Roundabouts [[Image:Round.png |50px]] ====<br />
<br />
{{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".<br />
[[File:Roundabouts.png|400px|right]]<br />
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. <br />
<br />
<br />
<br />
[[File:Roundboutmn2.png|400px|left]]<br />
<br />
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).<br />
<br />
<br />
<br />
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.<br />
<br />
If at all possible, drive through a roundabout after it has been created or updated. Verify that it seems to give correct information.<br />
<br />
==== Bus or Cab Only Lanes[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
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.<br />
<br />
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.<br />
<br />
=== Non-drivable roads ===<br />
<br />
==== Railroad [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:RailroadTracksVanishingPoint.jpg|right|300px|RoadPicN11.jpg]]<br />
<br />
<br />
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.<br />
<br />
<br />
<br />
<br />
{{mbox<br />
| type = important<br />
| text = Please notice that railroads have changed from previous interpretations of railroad mapping. Even veteran editors need to pay attention to this section!<br />
}}<br />
<br />
<br />
* 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.<br />
* 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.<br />
* Always select "None" for the city name. This avoids [[Smudged_city#Overview|city smudging]].<br />
* Set railroad to 2-way directionality and Restrict turns ''to'' and ''from'' the railroad segments.<br />
* 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. <br />
* 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.<br />
* Canadian Pacific uses the acronym CPRS, but it is more know as CP, so it will be called CP Railroad<br />
*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.<br />
* Lock all railroads to a Level 2<br />
* 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.<br />
* Read [[Road_types/USA#Railroad|this section]] for more information about railroads.<br />
<br />
==== Runway/Taxiway[[File:Service road.png|200px|Service road.png]] ====<br />
[[File:Aelrwmn.png|right|250px]]<br />
We will map all airports runways such:<br />
<br />
* These roads will not connect to any drivable sections<br />
* The runways will not be connected to each other<br />
* Always select "None" for the city name. This avoids [[Smudged_city#Overview|city smudging]].<br />
* 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.<br />
* After finding the code, we will use [http://www.airnav.com/airports/ this] to find the runway numbers for the airport.<br />
* Most of the time, you will see the number of the runway at the beginning and end of each runway from the aerial views. <br />
* 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".<br />
<br />
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.<br />
<br />
==== Ferry [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
{{mbox<br />
| type = warning<br />
| 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.<br />
}}<br />
<br />
==== Walking Trails [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:RoadPicN9.jpg|right|300px|RoadPicN9.jpg]] <br />
<br />
Even though Waze does not allow for navigating pedestrians or bikers, we will still prepare the map for when it is a function of the application. We will map out trails not only for this reason, but also to avoid speed data from being compiled if a person would leave Waze running on their phone while taking these trails. It also can be useful for a person who may use the map of Waze to recognize his or her location while taking these trails<br />
<br />
* Do not map trails that run parallel to a road unless it is more than 100 Ft from the road<br />
* Do not connect this road type to any drivable section of road<br />
* If the trail has a name, name it [Trail Name] Trail<br />
* Always select "None" for the city name. This avoids [[City smudge|city smudging]].<br />
* 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.<br />
* Use elevation standards as a standard road.<br />
<br />
==== Pedestrian Boardwalks [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:Boardwalksm.jpg|right|300px|RoadPicN10.jpg]] <br />
<br />
Pedestrian Boardwalks are not common, but they are going to be used in sections where a trail would not be appropriate. <br />
<br />
* Do not use these for a standard sidewalk. Sidewalks will not be mapped at all.<br />
* The common use for this will be for large sections that vehicles are not allowed such as an outdoor shopping area or concrete walkway away from roads<br />
* Do not connect this to any drivable road<br />
* Always select "None" for the city name. This avoids [[Smudged_city#Overview|city smudging]].<br />
<br />
==== Stairway [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:RoadPicN11.jpg|right|300px|RoadPicN11.jpg]]<br />
Stairways are very uncommon, but they will be used for any walking section that would require a person to climb a set of stairs to get to the next trail or pedestrian boardwalk. Never connect these to any drivable roads and do not add city names to this section of road. Use the same elevation standards as a road ... if no road or trail is directly underneath, it will be set for ground.<br />
<br />
<br />
<!---- DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ----<br />
-------------------------------------------------------------------------------------<br />
---- This page is only transcluded into (displayed on) the main page for this state.<br />
---- It directly follows the common guidelines applicable to all states. When this<br />
---- page is present (even if blanked), it displaces any optional code that might be<br />
---- in that section.<br />
---- If the original optional code from the main page for this section is still<br />
---- desired, it can be restored by adding the following code to the first line <br />
---- between the "DO NOT MODIFY" lines on this page:<br />
---- {{:USA/CommonState/Special roads|optional}}<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- If there will be a full page for this section, use code similar to the wording<br />
---- below to provide a hyperlink to that page. When creating the full page, use the<br />
---- link on the talk page to ensure the preload data is provided to help with<br />
---- formatting the page. Don't just use the red link from this section once it is<br />
---- saved.<br />
----<br />
See [[{{BasePage2}}/Special roads]] for guidance in {{RootPage2}} that may not be universal to all other states.<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- This section has three possible purposes:<br />
---- 1. It is only providing a hyperlink to the full page for this section.<br />
---- 2. It is only providing some unique guidance for this state that differs from<br />
---- other states.<br />
---- 3. It is intentionally wiping out the general optional content for this section<br />
---- for this state.<br />
------------------------------------------------------------------------------------></div>DallasGranthttps://www.waze.com/wiki/USA/index.php?title=Minnesota/Special_roads/Main&diff=99539Minnesota/Special roads/Main2015-03-15T06:56:22Z<p>DallasGrant: /* Pedestrian Boardwalks 200px|Service road.png */</p>
<hr />
<div><!-- 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><!--<br />
------ DO NOT MODIFY ABOVE THIS LINE -------- DO NOT MODIFY ABOVE THIS LINE ------> <br />
=== Other drivable roads ===<br />
<br />
==== Dirt Road / 4X4 Trail[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
{{mbox<br />
| type = important<br />
| text = Minnesota has different interpretations of Dirt Roads than many other locations. Even veteran editors need to pay attention to this section!<br />
}}<br />
<br />
<br />
[[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.<br />
<br />
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.<br />
<br />
[[File:Dirtroad.PNG|300px|right]]<br />
<br />
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. <br />
<br />
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.<br />
<br />
==== Parking Lot Road[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:Parklotrhmmn.png|right|300px]]<br />
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.<br />
<br />
* Simple is best. Do not map every lane<br />
* Map the main entrances from the roads outside the parking lot<br />
* Map lanes that run along storefronts<br />
* Map lanes that run along main roads outside the parking area<br />
* Map primary lanes that serve to get people from one area of the lot to another<br />
<br />
For for information about mapping parking lots, follow this [[Best_map_editing_practice#Parking_Lots|article]]<br />
<br />
==== Private Road[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:Pi gated-community1.jpg|right|300px|Pi gated-community1.jpg]]<br />
<br />
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. <br />
<br />
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. <br />
<br />
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.<br />
<br />
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.<br />
<br />
==== Alleyways[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
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 Parking Lot class.<br />
<br />
[[File:Pizzalola.png|300px|left]]<br />
<br />
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 parking lot 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.<br />
<br />
==== Roundabouts [[Image:Round.png |50px]] ====<br />
<br />
{{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".<br />
[[File:Roundabouts.png|400px|right]]<br />
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. <br />
<br />
<br />
<br />
[[File:Roundboutmn2.png|400px|left]]<br />
<br />
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).<br />
<br />
<br />
<br />
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.<br />
<br />
If at all possible, drive through a roundabout after it has been created or updated. Verify that it seems to give correct information.<br />
<br />
==== Bus or Cab Only Lanes[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
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.<br />
<br />
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.<br />
<br />
=== Non-drivable roads ===<br />
<br />
==== Railroad [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:RailroadTracksVanishingPoint.jpg|right|300px|RoadPicN11.jpg]]<br />
<br />
<br />
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.<br />
<br />
<br />
<br />
<br />
{{mbox<br />
| type = important<br />
| text = Please notice that railroads have changed from previous interpretations of railroad mapping. Even veteran editors need to pay attention to this section!<br />
}}<br />
<br />
<br />
* 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.<br />
* 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.<br />
* Always select "None" for the city name. This avoids [[Smudged_city#Overview|city smudging]].<br />
* Set railroad to 2-way directionality and Restrict turns ''to'' and ''from'' the railroad segments.<br />
* 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. <br />
* 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.<br />
* Canadian Pacific uses the acronym CPRS, but it is more know as CP, so it will be called CP Railroad<br />
*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.<br />
* Lock all railroads to a Level 2<br />
* 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.<br />
* Read [[Road_types/USA#Railroad|this section]] for more information about railroads.<br />
<br />
==== Runway/Taxiway[[File:Service road.png|200px|Service road.png]] ====<br />
[[File:Aelrwmn.png|right|250px]]<br />
We will map all airports runways such:<br />
<br />
* These roads will not connect to any drivable sections<br />
* The runways will not be connected to each other<br />
* Always select "None" for the city name. This avoids [[Smudged_city#Overview|city smudging]].<br />
* 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.<br />
* After finding the code, we will use [http://www.airnav.com/airports/ this] to find the runway numbers for the airport.<br />
* Most of the time, you will see the number of the runway at the beginning and end of each runway from the aerial views. <br />
* 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".<br />
<br />
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.<br />
<br />
==== Walking Trails [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:RoadPicN9.jpg|right|300px|RoadPicN9.jpg]] <br />
<br />
Even though Waze does not allow for navigating pedestrians or bikers, we will still prepare the map for when it is a function of the application. We will map out trails not only for this reason, but also to avoid speed data from being compiled if a person would leave Waze running on their phone while taking these trails. It also can be useful for a person who may use the map of Waze to recognize his or her location while taking these trails<br />
<br />
* Do not map trails that run parallel to a road unless it is more than 100 Ft from the road<br />
* Do not connect this road type to any drivable section of road<br />
* If the trail has a name, name it [Trail Name] Trail<br />
* Always select "None" for the city name. This avoids [[City smudge|city smudging]].<br />
* 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.<br />
* Use elevation standards as a standard road.<br />
<br />
==== Pedestrian Boardwalks [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:Boardwalksm.jpg|right|300px|RoadPicN10.jpg]] <br />
<br />
Pedestrian Boardwalks are not common, but they are going to be used in sections where a trail would not be appropriate. <br />
<br />
* Do not use these for a standard sidewalk. Sidewalks will not be mapped at all.<br />
* The common use for this will be for large sections that vehicles are not allowed such as an outdoor shopping area or concrete walkway away from roads<br />
* Do not connect this to any drivable road<br />
* Always select "None" for the city name. This avoids [[Smudged_city#Overview|city smudging]].<br />
<br />
==== Stairway [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:RoadPicN11.jpg|right|300px|RoadPicN11.jpg]]<br />
Stairways are very uncommon, but they will be used for any walking section that would require a person to climb a set of stairs to get to the next trail or pedestrian boardwalk. Never connect these to any drivable roads and do not add city names to this section of road. Use the same elevation standards as a road ... if no road or trail is directly underneath, it will be set for ground.<br />
<br />
<br />
<!---- DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ----<br />
-------------------------------------------------------------------------------------<br />
---- This page is only transcluded into (displayed on) the main page for this state.<br />
---- It directly follows the common guidelines applicable to all states. When this<br />
---- page is present (even if blanked), it displaces any optional code that might be<br />
---- in that section.<br />
---- If the original optional code from the main page for this section is still<br />
---- desired, it can be restored by adding the following code to the first line <br />
---- between the "DO NOT MODIFY" lines on this page:<br />
---- {{:USA/CommonState/Special roads|optional}}<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- If there will be a full page for this section, use code similar to the wording<br />
---- below to provide a hyperlink to that page. When creating the full page, use the<br />
---- link on the talk page to ensure the preload data is provided to help with<br />
---- formatting the page. Don't just use the red link from this section once it is<br />
---- saved.<br />
----<br />
See [[{{BasePage2}}/Special roads]] for guidance in {{RootPage2}} that may not be universal to all other states.<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- This section has three possible purposes:<br />
---- 1. It is only providing a hyperlink to the full page for this section.<br />
---- 2. It is only providing some unique guidance for this state that differs from<br />
---- other states.<br />
---- 3. It is intentionally wiping out the general optional content for this section<br />
---- for this state.<br />
------------------------------------------------------------------------------------></div>DallasGranthttps://www.waze.com/wiki/USA/index.php?title=Minnesota/Special_roads/Main&diff=99538Minnesota/Special roads/Main2015-03-15T06:54:52Z<p>DallasGrant: /* Stairway 200px|Service road.png */</p>
<hr />
<div><!-- 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><!--<br />
------ DO NOT MODIFY ABOVE THIS LINE -------- DO NOT MODIFY ABOVE THIS LINE ------> <br />
=== Other drivable roads ===<br />
<br />
==== Dirt Road / 4X4 Trail[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
{{mbox<br />
| type = important<br />
| text = Minnesota has different interpretations of Dirt Roads than many other locations. Even veteran editors need to pay attention to this section!<br />
}}<br />
<br />
<br />
[[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.<br />
<br />
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.<br />
<br />
[[File:Dirtroad.PNG|300px|right]]<br />
<br />
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. <br />
<br />
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.<br />
<br />
==== Parking Lot Road[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:Parklotrhmmn.png|right|300px]]<br />
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.<br />
<br />
* Simple is best. Do not map every lane<br />
* Map the main entrances from the roads outside the parking lot<br />
* Map lanes that run along storefronts<br />
* Map lanes that run along main roads outside the parking area<br />
* Map primary lanes that serve to get people from one area of the lot to another<br />
<br />
For for information about mapping parking lots, follow this [[Best_map_editing_practice#Parking_Lots|article]]<br />
<br />
==== Private Road[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:Pi gated-community1.jpg|right|300px|Pi gated-community1.jpg]]<br />
<br />
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. <br />
<br />
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. <br />
<br />
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.<br />
<br />
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.<br />
<br />
==== Alleyways[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
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 Parking Lot class.<br />
<br />
[[File:Pizzalola.png|300px|left]]<br />
<br />
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 parking lot 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.<br />
<br />
==== Roundabouts [[Image:Round.png |50px]] ====<br />
<br />
{{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".<br />
[[File:Roundabouts.png|400px|right]]<br />
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. <br />
<br />
<br />
<br />
[[File:Roundboutmn2.png|400px|left]]<br />
<br />
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).<br />
<br />
<br />
<br />
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.<br />
<br />
If at all possible, drive through a roundabout after it has been created or updated. Verify that it seems to give correct information.<br />
<br />
==== Bus or Cab Only Lanes[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
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.<br />
<br />
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.<br />
<br />
=== Non-drivable roads ===<br />
<br />
==== Railroad [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:RailroadTracksVanishingPoint.jpg|right|300px|RoadPicN11.jpg]]<br />
<br />
<br />
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.<br />
<br />
<br />
<br />
<br />
{{mbox<br />
| type = important<br />
| text = Please notice that railroads have changed from previous interpretations of railroad mapping. Even veteran editors need to pay attention to this section!<br />
}}<br />
<br />
<br />
* 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.<br />
* 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.<br />
* Always select "None" for the city name. This avoids [[Smudged_city#Overview|city smudging]].<br />
* Set railroad to 2-way directionality and Restrict turns ''to'' and ''from'' the railroad segments.<br />
* 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. <br />
* 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.<br />
* Canadian Pacific uses the acronym CPRS, but it is more know as CP, so it will be called CP Railroad<br />
*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.<br />
* Lock all railroads to a Level 2<br />
* 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.<br />
* Read [[Road_types/USA#Railroad|this section]] for more information about railroads.<br />
<br />
==== Runway/Taxiway[[File:Service road.png|200px|Service road.png]] ====<br />
[[File:Aelrwmn.png|right|250px]]<br />
We will map all airports runways such:<br />
<br />
* These roads will not connect to any drivable sections<br />
* The runways will not be connected to each other<br />
* Always select "None" for the city name. This avoids [[Smudged_city#Overview|city smudging]].<br />
* 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.<br />
* After finding the code, we will use [http://www.airnav.com/airports/ this] to find the runway numbers for the airport.<br />
* Most of the time, you will see the number of the runway at the beginning and end of each runway from the aerial views. <br />
* 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".<br />
<br />
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.<br />
<br />
==== Walking Trails [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:RoadPicN9.jpg|right|300px|RoadPicN9.jpg]] <br />
<br />
Even though Waze does not allow for navigating pedestrians or bikers, we will still prepare the map for when it is a function of the application. We will map out trails not only for this reason, but also to avoid speed data from being compiled if a person would leave Waze running on their phone while taking these trails. It also can be useful for a person who may use the map of Waze to recognize his or her location while taking these trails<br />
<br />
* Do not map trails that run parallel to a road unless it is more than 100 Ft from the road<br />
* Do not connect this road type to any drivable section of road<br />
* If the trail has a name, name it [Trail Name] Trail<br />
* Always select "None" for the city name. This avoids [[City smudge|city smudging]].<br />
* 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.<br />
* Use elevation standards as a standard road.<br />
<br />
==== Pedestrian Boardwalks [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:Boardwalksm.jpg|right|300px|RoadPicN10.jpg]] <br />
<br />
Pedestrian Boardwalks are not common, but they are going to be used in sections where a trail would not be appropriate. <br />
<br />
* Do not use these for a standard sidewalk. Sidewalks will not be mapped at all.<br />
* The common use for this will be for large sections that vehicles are not allowed such as an outdoor shopping area or concrete walkway away from roads<br />
* Do not connect this to any drivable road<br />
<br />
{{clear}}<br />
<br />
==== Stairway [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:RoadPicN11.jpg|right|300px|RoadPicN11.jpg]]<br />
Stairways are very uncommon, but they will be used for any walking section that would require a person to climb a set of stairs to get to the next trail or pedestrian boardwalk. Never connect these to any drivable roads and do not add city names to this section of road. Use the same elevation standards as a road ... if no road or trail is directly underneath, it will be set for ground.<br />
<br />
<br />
<!---- DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ----<br />
-------------------------------------------------------------------------------------<br />
---- This page is only transcluded into (displayed on) the main page for this state.<br />
---- It directly follows the common guidelines applicable to all states. When this<br />
---- page is present (even if blanked), it displaces any optional code that might be<br />
---- in that section.<br />
---- If the original optional code from the main page for this section is still<br />
---- desired, it can be restored by adding the following code to the first line <br />
---- between the "DO NOT MODIFY" lines on this page:<br />
---- {{:USA/CommonState/Special roads|optional}}<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- If there will be a full page for this section, use code similar to the wording<br />
---- below to provide a hyperlink to that page. When creating the full page, use the<br />
---- link on the talk page to ensure the preload data is provided to help with<br />
---- formatting the page. Don't just use the red link from this section once it is<br />
---- saved.<br />
----<br />
See [[{{BasePage2}}/Special roads]] for guidance in {{RootPage2}} that may not be universal to all other states.<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- This section has three possible purposes:<br />
---- 1. It is only providing a hyperlink to the full page for this section.<br />
---- 2. It is only providing some unique guidance for this state that differs from<br />
---- other states.<br />
---- 3. It is intentionally wiping out the general optional content for this section<br />
---- for this state.<br />
------------------------------------------------------------------------------------></div>DallasGranthttps://www.waze.com/wiki/USA/index.php?title=Minnesota/Special_roads/Main&diff=99537Minnesota/Special roads/Main2015-03-15T06:46:40Z<p>DallasGrant: /* Runway/Taxiway200px|Service road.png */</p>
<hr />
<div><!-- 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><!--<br />
------ DO NOT MODIFY ABOVE THIS LINE -------- DO NOT MODIFY ABOVE THIS LINE ------> <br />
=== Other drivable roads ===<br />
<br />
==== Dirt Road / 4X4 Trail[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
{{mbox<br />
| type = important<br />
| text = Minnesota has different interpretations of Dirt Roads than many other locations. Even veteran editors need to pay attention to this section!<br />
}}<br />
<br />
<br />
[[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.<br />
<br />
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.<br />
<br />
[[File:Dirtroad.PNG|300px|right]]<br />
<br />
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. <br />
<br />
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.<br />
<br />
==== Parking Lot Road[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:Parklotrhmmn.png|right|300px]]<br />
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.<br />
<br />
* Simple is best. Do not map every lane<br />
* Map the main entrances from the roads outside the parking lot<br />
* Map lanes that run along storefronts<br />
* Map lanes that run along main roads outside the parking area<br />
* Map primary lanes that serve to get people from one area of the lot to another<br />
<br />
For for information about mapping parking lots, follow this [[Best_map_editing_practice#Parking_Lots|article]]<br />
<br />
==== Private Road[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:Pi gated-community1.jpg|right|300px|Pi gated-community1.jpg]]<br />
<br />
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. <br />
<br />
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. <br />
<br />
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.<br />
<br />
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.<br />
<br />
==== Alleyways[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
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 Parking Lot class.<br />
<br />
[[File:Pizzalola.png|300px|left]]<br />
<br />
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 parking lot 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.<br />
<br />
==== Roundabouts [[Image:Round.png |50px]] ====<br />
<br />
{{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".<br />
[[File:Roundabouts.png|400px|right]]<br />
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. <br />
<br />
<br />
<br />
[[File:Roundboutmn2.png|400px|left]]<br />
<br />
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).<br />
<br />
<br />
<br />
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.<br />
<br />
If at all possible, drive through a roundabout after it has been created or updated. Verify that it seems to give correct information.<br />
<br />
==== Bus or Cab Only Lanes[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
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.<br />
<br />
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.<br />
<br />
=== Non-drivable roads ===<br />
<br />
==== Railroad [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:RailroadTracksVanishingPoint.jpg|right|300px|RoadPicN11.jpg]]<br />
<br />
<br />
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.<br />
<br />
<br />
<br />
<br />
{{mbox<br />
| type = important<br />
| text = Please notice that railroads have changed from previous interpretations of railroad mapping. Even veteran editors need to pay attention to this section!<br />
}}<br />
<br />
<br />
* 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.<br />
* 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.<br />
* Always select "None" for the city name. This avoids [[Smudged_city#Overview|city smudging]].<br />
* Set railroad to 2-way directionality and Restrict turns ''to'' and ''from'' the railroad segments.<br />
* 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. <br />
* 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.<br />
* Canadian Pacific uses the acronym CPRS, but it is more know as CP, so it will be called CP Railroad<br />
*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.<br />
* Lock all railroads to a Level 2<br />
* 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.<br />
* Read [[Road_types/USA#Railroad|this section]] for more information about railroads.<br />
<br />
==== Runway/Taxiway[[File:Service road.png|200px|Service road.png]] ====<br />
[[File:Aelrwmn.png|right|250px]]<br />
We will map all airports runways such:<br />
<br />
* These roads will not connect to any drivable sections<br />
* The runways will not be connected to each other<br />
* Always select "None" for the city name. This avoids [[Smudged_city#Overview|city smudging]].<br />
* 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.<br />
* After finding the code, we will use [http://www.airnav.com/airports/ this] to find the runway numbers for the airport.<br />
* Most of the time, you will see the number of the runway at the beginning and end of each runway from the aerial views. <br />
* 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".<br />
<br />
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.<br />
<br />
==== Walking Trails [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:RoadPicN9.jpg|right|300px|RoadPicN9.jpg]] <br />
<br />
Even though Waze does not allow for navigating pedestrians or bikers, we will still prepare the map for when it is a function of the application. We will map out trails not only for this reason, but also to avoid speed data from being compiled if a person would leave Waze running on their phone while taking these trails. It also can be useful for a person who may use the map of Waze to recognize his or her location while taking these trails<br />
<br />
* Do not map trails that run parallel to a road unless it is more than 100 Ft from the road<br />
* Do not connect this road type to any drivable section of road<br />
* If the trail has a name, name it [Trail Name] Trail<br />
* Always select "None" for the city name. This avoids [[City smudge|city smudging]].<br />
* 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.<br />
* Use elevation standards as a standard road.<br />
<br />
==== Pedestrian Boardwalks [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:Boardwalksm.jpg|right|300px|RoadPicN10.jpg]] <br />
<br />
Pedestrian Boardwalks are not common, but they are going to be used in sections where a trail would not be appropriate. <br />
<br />
* Do not use these for a standard sidewalk. Sidewalks will not be mapped at all.<br />
* The common use for this will be for large sections that vehicles are not allowed such as an outdoor shopping area or concrete walkway away from roads<br />
* Do not connect this to any drivable road<br />
<br />
{{clear}}<br />
<br />
==== Stairway [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:RoadPicN11.jpg|right|300px|RoadPicN11.jpg]] {{clear}}<br />
<br />
<br />
<!---- DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ----<br />
-------------------------------------------------------------------------------------<br />
---- This page is only transcluded into (displayed on) the main page for this state.<br />
---- It directly follows the common guidelines applicable to all states. When this<br />
---- page is present (even if blanked), it displaces any optional code that might be<br />
---- in that section.<br />
---- If the original optional code from the main page for this section is still<br />
---- desired, it can be restored by adding the following code to the first line <br />
---- between the "DO NOT MODIFY" lines on this page:<br />
---- {{:USA/CommonState/Special roads|optional}}<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- If there will be a full page for this section, use code similar to the wording<br />
---- below to provide a hyperlink to that page. When creating the full page, use the<br />
---- link on the talk page to ensure the preload data is provided to help with<br />
---- formatting the page. Don't just use the red link from this section once it is<br />
---- saved.<br />
----<br />
See [[{{BasePage2}}/Special roads]] for guidance in {{RootPage2}} that may not be universal to all other states.<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- This section has three possible purposes:<br />
---- 1. It is only providing a hyperlink to the full page for this section.<br />
---- 2. It is only providing some unique guidance for this state that differs from<br />
---- other states.<br />
---- 3. It is intentionally wiping out the general optional content for this section<br />
---- for this state.<br />
------------------------------------------------------------------------------------></div>DallasGranthttps://www.waze.com/wiki/USA/index.php?title=Minnesota/Special_roads/Main&diff=99536Minnesota/Special roads/Main2015-03-15T06:39:51Z<p>DallasGrant: /* Pedestrian Boardwalks 200px|Service road.png */</p>
<hr />
<div><!-- 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><!--<br />
------ DO NOT MODIFY ABOVE THIS LINE -------- DO NOT MODIFY ABOVE THIS LINE ------> <br />
=== Other drivable roads ===<br />
<br />
==== Dirt Road / 4X4 Trail[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
{{mbox<br />
| type = important<br />
| text = Minnesota has different interpretations of Dirt Roads than many other locations. Even veteran editors need to pay attention to this section!<br />
}}<br />
<br />
<br />
[[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.<br />
<br />
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.<br />
<br />
[[File:Dirtroad.PNG|300px|right]]<br />
<br />
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. <br />
<br />
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.<br />
<br />
==== Parking Lot Road[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:Parklotrhmmn.png|right|300px]]<br />
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.<br />
<br />
* Simple is best. Do not map every lane<br />
* Map the main entrances from the roads outside the parking lot<br />
* Map lanes that run along storefronts<br />
* Map lanes that run along main roads outside the parking area<br />
* Map primary lanes that serve to get people from one area of the lot to another<br />
<br />
For for information about mapping parking lots, follow this [[Best_map_editing_practice#Parking_Lots|article]]<br />
<br />
==== Private Road[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:Pi gated-community1.jpg|right|300px|Pi gated-community1.jpg]]<br />
<br />
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. <br />
<br />
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. <br />
<br />
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.<br />
<br />
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.<br />
<br />
==== Alleyways[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
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 Parking Lot class.<br />
<br />
[[File:Pizzalola.png|300px|left]]<br />
<br />
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 parking lot 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.<br />
<br />
==== Roundabouts [[Image:Round.png |50px]] ====<br />
<br />
{{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".<br />
[[File:Roundabouts.png|400px|right]]<br />
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. <br />
<br />
<br />
<br />
[[File:Roundboutmn2.png|400px|left]]<br />
<br />
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).<br />
<br />
<br />
<br />
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.<br />
<br />
If at all possible, drive through a roundabout after it has been created or updated. Verify that it seems to give correct information.<br />
<br />
==== Bus or Cab Only Lanes[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
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.<br />
<br />
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.<br />
<br />
=== Non-drivable roads ===<br />
<br />
==== Railroad [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:RailroadTracksVanishingPoint.jpg|right|300px|RoadPicN11.jpg]]<br />
<br />
<br />
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.<br />
<br />
<br />
<br />
<br />
{{mbox<br />
| type = important<br />
| text = Please notice that railroads have changed from previous interpretations of railroad mapping. Even veteran editors need to pay attention to this section!<br />
}}<br />
<br />
<br />
* 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.<br />
* 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.<br />
* Always select "None" for the city name. This avoids [[Smudged_city#Overview|city smudging]].<br />
* Set railroad to 2-way directionality and Restrict turns ''to'' and ''from'' the railroad segments.<br />
* 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. <br />
* 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.<br />
* Canadian Pacific uses the acronym CPRS, but it is more know as CP, so it will be called CP Railroad<br />
*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.<br />
* Lock all railroads to a Level 2<br />
* 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.<br />
* Read [[Road_types/USA#Railroad|this section]] for more information about railroads.<br />
<br />
==== Runway/Taxiway[[File:Service road.png|200px|Service road.png]] ====<br />
[[File:Aelrwmn.png|right|250px]]<br />
We will map all airports runways such:<br />
<br />
* These roads will not connect to any drivable sections<br />
* The runways will not be connected to each other<br />
* 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.<br />
* After finding the code, we will use [http://www.airnav.com/airports/ this] to find the runway numbers for the airport.<br />
* Most of the time, you will see the number of the runway at the beginning and end of each runway from the aerial views. <br />
* 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".<br />
<br />
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. <br />
<br />
==== Walking Trails [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:RoadPicN9.jpg|right|300px|RoadPicN9.jpg]] <br />
<br />
Even though Waze does not allow for navigating pedestrians or bikers, we will still prepare the map for when it is a function of the application. We will map out trails not only for this reason, but also to avoid speed data from being compiled if a person would leave Waze running on their phone while taking these trails. It also can be useful for a person who may use the map of Waze to recognize his or her location while taking these trails<br />
<br />
* Do not map trails that run parallel to a road unless it is more than 100 Ft from the road<br />
* Do not connect this road type to any drivable section of road<br />
* If the trail has a name, name it [Trail Name] Trail<br />
* Always select "None" for the city name. This avoids [[City smudge|city smudging]].<br />
* 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.<br />
* Use elevation standards as a standard road.<br />
<br />
==== Pedestrian Boardwalks [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:Boardwalksm.jpg|right|300px|RoadPicN10.jpg]] <br />
<br />
Pedestrian Boardwalks are not common, but they are going to be used in sections where a trail would not be appropriate. <br />
<br />
* Do not use these for a standard sidewalk. Sidewalks will not be mapped at all.<br />
* The common use for this will be for large sections that vehicles are not allowed such as an outdoor shopping area or concrete walkway away from roads<br />
* Do not connect this to any drivable road<br />
<br />
{{clear}}<br />
<br />
==== Stairway [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:RoadPicN11.jpg|right|300px|RoadPicN11.jpg]] {{clear}}<br />
<br />
<br />
<!---- DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ----<br />
-------------------------------------------------------------------------------------<br />
---- This page is only transcluded into (displayed on) the main page for this state.<br />
---- It directly follows the common guidelines applicable to all states. When this<br />
---- page is present (even if blanked), it displaces any optional code that might be<br />
---- in that section.<br />
---- If the original optional code from the main page for this section is still<br />
---- desired, it can be restored by adding the following code to the first line <br />
---- between the "DO NOT MODIFY" lines on this page:<br />
---- {{:USA/CommonState/Special roads|optional}}<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- If there will be a full page for this section, use code similar to the wording<br />
---- below to provide a hyperlink to that page. When creating the full page, use the<br />
---- link on the talk page to ensure the preload data is provided to help with<br />
---- formatting the page. Don't just use the red link from this section once it is<br />
---- saved.<br />
----<br />
See [[{{BasePage2}}/Special roads]] for guidance in {{RootPage2}} that may not be universal to all other states.<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- This section has three possible purposes:<br />
---- 1. It is only providing a hyperlink to the full page for this section.<br />
---- 2. It is only providing some unique guidance for this state that differs from<br />
---- other states.<br />
---- 3. It is intentionally wiping out the general optional content for this section<br />
---- for this state.<br />
------------------------------------------------------------------------------------></div>DallasGranthttps://www.waze.com/wiki/USA/index.php?title=File:Boardwalksm.jpg&diff=99535File:Boardwalksm.jpg2015-03-15T06:37:42Z<p>DallasGrant: </p>
<hr />
<div></div>DallasGranthttps://www.waze.com/wiki/USA/index.php?title=Minnesota/Special_roads/Main&diff=99533Minnesota/Special roads/Main2015-03-15T05:55:33Z<p>DallasGrant: /* Railroad 200px|Service road.png */</p>
<hr />
<div><!-- 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><!--<br />
------ DO NOT MODIFY ABOVE THIS LINE -------- DO NOT MODIFY ABOVE THIS LINE ------> <br />
=== Other drivable roads ===<br />
<br />
==== Dirt Road / 4X4 Trail[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
{{mbox<br />
| type = important<br />
| text = Minnesota has different interpretations of Dirt Roads than many other locations. Even veteran editors need to pay attention to this section!<br />
}}<br />
<br />
<br />
[[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.<br />
<br />
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.<br />
<br />
[[File:Dirtroad.PNG|300px|right]]<br />
<br />
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. <br />
<br />
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.<br />
<br />
==== Parking Lot Road[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:Parklotrhmmn.png|right|300px]]<br />
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.<br />
<br />
* Simple is best. Do not map every lane<br />
* Map the main entrances from the roads outside the parking lot<br />
* Map lanes that run along storefronts<br />
* Map lanes that run along main roads outside the parking area<br />
* Map primary lanes that serve to get people from one area of the lot to another<br />
<br />
For for information about mapping parking lots, follow this [[Best_map_editing_practice#Parking_Lots|article]]<br />
<br />
==== Private Road[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:Pi gated-community1.jpg|right|300px|Pi gated-community1.jpg]]<br />
<br />
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. <br />
<br />
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. <br />
<br />
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.<br />
<br />
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.<br />
<br />
==== Alleyways[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
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 Parking Lot class.<br />
<br />
[[File:Pizzalola.png|300px|left]]<br />
<br />
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 parking lot 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.<br />
<br />
==== Roundabouts [[Image:Round.png |50px]] ====<br />
<br />
{{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".<br />
[[File:Roundabouts.png|400px|right]]<br />
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. <br />
<br />
<br />
<br />
[[File:Roundboutmn2.png|400px|left]]<br />
<br />
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).<br />
<br />
<br />
<br />
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.<br />
<br />
If at all possible, drive through a roundabout after it has been created or updated. Verify that it seems to give correct information.<br />
<br />
==== Bus or Cab Only Lanes[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
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.<br />
<br />
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.<br />
<br />
=== Non-drivable roads ===<br />
<br />
==== Railroad [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:RailroadTracksVanishingPoint.jpg|right|300px|RoadPicN11.jpg]]<br />
<br />
<br />
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.<br />
<br />
<br />
<br />
<br />
{{mbox<br />
| type = important<br />
| text = Please notice that railroads have changed from previous interpretations of railroad mapping. Even veteran editors need to pay attention to this section!<br />
}}<br />
<br />
<br />
* 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.<br />
* 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.<br />
* Always select "None" for the city name. This avoids [[Smudged_city#Overview|city smudging]].<br />
* Set railroad to 2-way directionality and Restrict turns ''to'' and ''from'' the railroad segments.<br />
* 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. <br />
* 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.<br />
* Canadian Pacific uses the acronym CPRS, but it is more know as CP, so it will be called CP Railroad<br />
*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.<br />
* Lock all railroads to a Level 2<br />
* 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.<br />
* Read [[Road_types/USA#Railroad|this section]] for more information about railroads.<br />
<br />
==== Runway/Taxiway[[File:Service road.png|200px|Service road.png]] ====<br />
[[File:Aelrwmn.png|right|250px]]<br />
We will map all airports runways such:<br />
<br />
* These roads will not connect to any drivable sections<br />
* The runways will not be connected to each other<br />
* 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.<br />
* After finding the code, we will use [http://www.airnav.com/airports/ this] to find the runway numbers for the airport.<br />
* Most of the time, you will see the number of the runway at the beginning and end of each runway from the aerial views. <br />
* 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".<br />
<br />
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. <br />
<br />
==== Walking Trails [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:RoadPicN9.jpg|right|300px|RoadPicN9.jpg]] <br />
<br />
Even though Waze does not allow for navigating pedestrians or bikers, we will still prepare the map for when it is a function of the application. We will map out trails not only for this reason, but also to avoid speed data from being compiled if a person would leave Waze running on their phone while taking these trails. It also can be useful for a person who may use the map of Waze to recognize his or her location while taking these trails<br />
<br />
* Do not map trails that run parallel to a road unless it is more than 100 Ft from the road<br />
* Do not connect this road type to any drivable section of road<br />
* If the trail has a name, name it [Trail Name] Trail<br />
* Always select "None" for the city name. This avoids [[City smudge|city smudging]].<br />
* 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.<br />
* Use elevation standards as a standard road.<br />
<br />
==== Pedestrian Boardwalks [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:RoadPicN10.jpg|right|300px|RoadPicN10.jpg]] {{clear}}<br />
<br />
==== Stairway [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:RoadPicN11.jpg|right|300px|RoadPicN11.jpg]] {{clear}}<br />
<br />
<br />
<!---- DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ----<br />
-------------------------------------------------------------------------------------<br />
---- This page is only transcluded into (displayed on) the main page for this state.<br />
---- It directly follows the common guidelines applicable to all states. When this<br />
---- page is present (even if blanked), it displaces any optional code that might be<br />
---- in that section.<br />
---- If the original optional code from the main page for this section is still<br />
---- desired, it can be restored by adding the following code to the first line <br />
---- between the "DO NOT MODIFY" lines on this page:<br />
---- {{:USA/CommonState/Special roads|optional}}<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- If there will be a full page for this section, use code similar to the wording<br />
---- below to provide a hyperlink to that page. When creating the full page, use the<br />
---- link on the talk page to ensure the preload data is provided to help with<br />
---- formatting the page. Don't just use the red link from this section once it is<br />
---- saved.<br />
----<br />
See [[{{BasePage2}}/Special roads]] for guidance in {{RootPage2}} that may not be universal to all other states.<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- This section has three possible purposes:<br />
---- 1. It is only providing a hyperlink to the full page for this section.<br />
---- 2. It is only providing some unique guidance for this state that differs from<br />
---- other states.<br />
---- 3. It is intentionally wiping out the general optional content for this section<br />
---- for this state.<br />
------------------------------------------------------------------------------------></div>DallasGranthttps://www.waze.com/wiki/USA/index.php?title=Minnesota/Special_roads/Main&diff=99532Minnesota/Special roads/Main2015-03-15T05:54:18Z<p>DallasGrant: /* Walking Trails 200px|Service road.png */</p>
<hr />
<div><!-- 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><!--<br />
------ DO NOT MODIFY ABOVE THIS LINE -------- DO NOT MODIFY ABOVE THIS LINE ------> <br />
=== Other drivable roads ===<br />
<br />
==== Dirt Road / 4X4 Trail[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
{{mbox<br />
| type = important<br />
| text = Minnesota has different interpretations of Dirt Roads than many other locations. Even veteran editors need to pay attention to this section!<br />
}}<br />
<br />
<br />
[[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.<br />
<br />
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.<br />
<br />
[[File:Dirtroad.PNG|300px|right]]<br />
<br />
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. <br />
<br />
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.<br />
<br />
==== Parking Lot Road[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:Parklotrhmmn.png|right|300px]]<br />
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.<br />
<br />
* Simple is best. Do not map every lane<br />
* Map the main entrances from the roads outside the parking lot<br />
* Map lanes that run along storefronts<br />
* Map lanes that run along main roads outside the parking area<br />
* Map primary lanes that serve to get people from one area of the lot to another<br />
<br />
For for information about mapping parking lots, follow this [[Best_map_editing_practice#Parking_Lots|article]]<br />
<br />
==== Private Road[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:Pi gated-community1.jpg|right|300px|Pi gated-community1.jpg]]<br />
<br />
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. <br />
<br />
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. <br />
<br />
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.<br />
<br />
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.<br />
<br />
==== Alleyways[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
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 Parking Lot class.<br />
<br />
[[File:Pizzalola.png|300px|left]]<br />
<br />
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 parking lot 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.<br />
<br />
==== Roundabouts [[Image:Round.png |50px]] ====<br />
<br />
{{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".<br />
[[File:Roundabouts.png|400px|right]]<br />
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. <br />
<br />
<br />
<br />
[[File:Roundboutmn2.png|400px|left]]<br />
<br />
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).<br />
<br />
<br />
<br />
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.<br />
<br />
If at all possible, drive through a roundabout after it has been created or updated. Verify that it seems to give correct information.<br />
<br />
==== Bus or Cab Only Lanes[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
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.<br />
<br />
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.<br />
<br />
=== Non-drivable roads ===<br />
<br />
==== Railroad [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:RailroadTracksVanishingPoint.jpg|right|300px|RoadPicN11.jpg]]<br />
<br />
<br />
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.<br />
<br />
<br />
<br />
<br />
{{mbox<br />
| type = important<br />
| text = Please notice that railroads have changed from previous interpretations of railroad mapping. Even veteran editors need to pay attention to this section!<br />
}}<br />
<br />
<br />
* 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.<br />
* 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.<br />
* Always select "None" for the city name. This avoids [[Smudged_city#Overview|city smudging]].<br />
* Set railroad to 2-way directionality and Restrict turns ''to'' and ''from'' the railroad segments.<br />
* 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. <br />
* 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.<br />
* Canadian Pacific uses the acronym CPRS, but it is more know as CP, so it will be called CP Railroad<br />
*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.<br />
* Lock all railroads to a Level 2<br />
* Read [[Road_types/USA#Railroad|this section]] for more information about railroads.<br />
<br />
==== Runway/Taxiway[[File:Service road.png|200px|Service road.png]] ====<br />
[[File:Aelrwmn.png|right|250px]]<br />
We will map all airports runways such:<br />
<br />
* These roads will not connect to any drivable sections<br />
* The runways will not be connected to each other<br />
* 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.<br />
* After finding the code, we will use [http://www.airnav.com/airports/ this] to find the runway numbers for the airport.<br />
* Most of the time, you will see the number of the runway at the beginning and end of each runway from the aerial views. <br />
* 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".<br />
<br />
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. <br />
<br />
==== Walking Trails [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:RoadPicN9.jpg|right|300px|RoadPicN9.jpg]] <br />
<br />
Even though Waze does not allow for navigating pedestrians or bikers, we will still prepare the map for when it is a function of the application. We will map out trails not only for this reason, but also to avoid speed data from being compiled if a person would leave Waze running on their phone while taking these trails. It also can be useful for a person who may use the map of Waze to recognize his or her location while taking these trails<br />
<br />
* Do not map trails that run parallel to a road unless it is more than 100 Ft from the road<br />
* Do not connect this road type to any drivable section of road<br />
* If the trail has a name, name it [Trail Name] Trail<br />
* Always select "None" for the city name. This avoids [[City smudge|city smudging]].<br />
* 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.<br />
* Use elevation standards as a standard road.<br />
<br />
==== Pedestrian Boardwalks [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:RoadPicN10.jpg|right|300px|RoadPicN10.jpg]] {{clear}}<br />
<br />
==== Stairway [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:RoadPicN11.jpg|right|300px|RoadPicN11.jpg]] {{clear}}<br />
<br />
<br />
<!---- DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ----<br />
-------------------------------------------------------------------------------------<br />
---- This page is only transcluded into (displayed on) the main page for this state.<br />
---- It directly follows the common guidelines applicable to all states. When this<br />
---- page is present (even if blanked), it displaces any optional code that might be<br />
---- in that section.<br />
---- If the original optional code from the main page for this section is still<br />
---- desired, it can be restored by adding the following code to the first line <br />
---- between the "DO NOT MODIFY" lines on this page:<br />
---- {{:USA/CommonState/Special roads|optional}}<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- If there will be a full page for this section, use code similar to the wording<br />
---- below to provide a hyperlink to that page. When creating the full page, use the<br />
---- link on the talk page to ensure the preload data is provided to help with<br />
---- formatting the page. Don't just use the red link from this section once it is<br />
---- saved.<br />
----<br />
See [[{{BasePage2}}/Special roads]] for guidance in {{RootPage2}} that may not be universal to all other states.<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- This section has three possible purposes:<br />
---- 1. It is only providing a hyperlink to the full page for this section.<br />
---- 2. It is only providing some unique guidance for this state that differs from<br />
---- other states.<br />
---- 3. It is intentionally wiping out the general optional content for this section<br />
---- for this state.<br />
------------------------------------------------------------------------------------></div>DallasGranthttps://www.waze.com/wiki/USA/index.php?title=Minnesota/Special_roads/Main&diff=99531Minnesota/Special roads/Main2015-03-15T05:27:45Z<p>DallasGrant: /* Pedestrian Boardwalks 200px|Service road.png */</p>
<hr />
<div><!-- 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><!--<br />
------ DO NOT MODIFY ABOVE THIS LINE -------- DO NOT MODIFY ABOVE THIS LINE ------> <br />
=== Other drivable roads ===<br />
<br />
==== Dirt Road / 4X4 Trail[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
{{mbox<br />
| type = important<br />
| text = Minnesota has different interpretations of Dirt Roads than many other locations. Even veteran editors need to pay attention to this section!<br />
}}<br />
<br />
<br />
[[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.<br />
<br />
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.<br />
<br />
[[File:Dirtroad.PNG|300px|right]]<br />
<br />
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. <br />
<br />
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.<br />
<br />
==== Parking Lot Road[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:Parklotrhmmn.png|right|300px]]<br />
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.<br />
<br />
* Simple is best. Do not map every lane<br />
* Map the main entrances from the roads outside the parking lot<br />
* Map lanes that run along storefronts<br />
* Map lanes that run along main roads outside the parking area<br />
* Map primary lanes that serve to get people from one area of the lot to another<br />
<br />
For for information about mapping parking lots, follow this [[Best_map_editing_practice#Parking_Lots|article]]<br />
<br />
==== Private Road[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:Pi gated-community1.jpg|right|300px|Pi gated-community1.jpg]]<br />
<br />
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. <br />
<br />
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. <br />
<br />
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.<br />
<br />
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.<br />
<br />
==== Alleyways[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
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 Parking Lot class.<br />
<br />
[[File:Pizzalola.png|300px|left]]<br />
<br />
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 parking lot 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.<br />
<br />
==== Roundabouts [[Image:Round.png |50px]] ====<br />
<br />
{{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".<br />
[[File:Roundabouts.png|400px|right]]<br />
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. <br />
<br />
<br />
<br />
[[File:Roundboutmn2.png|400px|left]]<br />
<br />
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).<br />
<br />
<br />
<br />
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.<br />
<br />
If at all possible, drive through a roundabout after it has been created or updated. Verify that it seems to give correct information.<br />
<br />
==== Bus or Cab Only Lanes[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
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.<br />
<br />
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.<br />
<br />
=== Non-drivable roads ===<br />
<br />
==== Railroad [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:RailroadTracksVanishingPoint.jpg|right|300px|RoadPicN11.jpg]]<br />
<br />
<br />
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.<br />
<br />
<br />
<br />
<br />
{{mbox<br />
| type = important<br />
| text = Please notice that railroads have changed from previous interpretations of railroad mapping. Even veteran editors need to pay attention to this section!<br />
}}<br />
<br />
<br />
* 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.<br />
* 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.<br />
* Always select "None" for the city name. This avoids [[Smudged_city#Overview|city smudging]].<br />
* Set railroad to 2-way directionality and Restrict turns ''to'' and ''from'' the railroad segments.<br />
* 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. <br />
* 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.<br />
* Canadian Pacific uses the acronym CPRS, but it is more know as CP, so it will be called CP Railroad<br />
*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.<br />
* Lock all railroads to a Level 2<br />
* Read [[Road_types/USA#Railroad|this section]] for more information about railroads.<br />
<br />
==== Runway/Taxiway[[File:Service road.png|200px|Service road.png]] ====<br />
[[File:Aelrwmn.png|right|250px]]<br />
We will map all airports runways such:<br />
<br />
* These roads will not connect to any drivable sections<br />
* The runways will not be connected to each other<br />
* 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.<br />
* After finding the code, we will use [http://www.airnav.com/airports/ this] to find the runway numbers for the airport.<br />
* Most of the time, you will see the number of the runway at the beginning and end of each runway from the aerial views. <br />
* 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".<br />
<br />
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. <br />
<br />
==== Walking Trails [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:RoadPicN9.jpg|right|300px|RoadPicN9.jpg]] {{clear}}<br />
<br />
==== Pedestrian Boardwalks [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:RoadPicN10.jpg|right|300px|RoadPicN10.jpg]] {{clear}}<br />
<br />
==== Stairway [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:RoadPicN11.jpg|right|300px|RoadPicN11.jpg]] {{clear}}<br />
<br />
<br />
<!---- DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ----<br />
-------------------------------------------------------------------------------------<br />
---- This page is only transcluded into (displayed on) the main page for this state.<br />
---- It directly follows the common guidelines applicable to all states. When this<br />
---- page is present (even if blanked), it displaces any optional code that might be<br />
---- in that section.<br />
---- If the original optional code from the main page for this section is still<br />
---- desired, it can be restored by adding the following code to the first line <br />
---- between the "DO NOT MODIFY" lines on this page:<br />
---- {{:USA/CommonState/Special roads|optional}}<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- If there will be a full page for this section, use code similar to the wording<br />
---- below to provide a hyperlink to that page. When creating the full page, use the<br />
---- link on the talk page to ensure the preload data is provided to help with<br />
---- formatting the page. Don't just use the red link from this section once it is<br />
---- saved.<br />
----<br />
See [[{{BasePage2}}/Special roads]] for guidance in {{RootPage2}} that may not be universal to all other states.<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- This section has three possible purposes:<br />
---- 1. It is only providing a hyperlink to the full page for this section.<br />
---- 2. It is only providing some unique guidance for this state that differs from<br />
---- other states.<br />
---- 3. It is intentionally wiping out the general optional content for this section<br />
---- for this state.<br />
------------------------------------------------------------------------------------></div>DallasGranthttps://www.waze.com/wiki/USA/index.php?title=Minnesota/Special_roads/Main&diff=99530Minnesota/Special roads/Main2015-03-15T05:27:06Z<p>DallasGrant: /* Walking Trails 200px|Service road.png */</p>
<hr />
<div><!-- 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><!--<br />
------ DO NOT MODIFY ABOVE THIS LINE -------- DO NOT MODIFY ABOVE THIS LINE ------> <br />
=== Other drivable roads ===<br />
<br />
==== Dirt Road / 4X4 Trail[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
{{mbox<br />
| type = important<br />
| text = Minnesota has different interpretations of Dirt Roads than many other locations. Even veteran editors need to pay attention to this section!<br />
}}<br />
<br />
<br />
[[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.<br />
<br />
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.<br />
<br />
[[File:Dirtroad.PNG|300px|right]]<br />
<br />
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. <br />
<br />
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.<br />
<br />
==== Parking Lot Road[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:Parklotrhmmn.png|right|300px]]<br />
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.<br />
<br />
* Simple is best. Do not map every lane<br />
* Map the main entrances from the roads outside the parking lot<br />
* Map lanes that run along storefronts<br />
* Map lanes that run along main roads outside the parking area<br />
* Map primary lanes that serve to get people from one area of the lot to another<br />
<br />
For for information about mapping parking lots, follow this [[Best_map_editing_practice#Parking_Lots|article]]<br />
<br />
==== Private Road[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:Pi gated-community1.jpg|right|300px|Pi gated-community1.jpg]]<br />
<br />
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. <br />
<br />
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. <br />
<br />
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.<br />
<br />
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.<br />
<br />
==== Alleyways[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
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 Parking Lot class.<br />
<br />
[[File:Pizzalola.png|300px|left]]<br />
<br />
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 parking lot 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.<br />
<br />
==== Roundabouts [[Image:Round.png |50px]] ====<br />
<br />
{{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".<br />
[[File:Roundabouts.png|400px|right]]<br />
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. <br />
<br />
<br />
<br />
[[File:Roundboutmn2.png|400px|left]]<br />
<br />
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).<br />
<br />
<br />
<br />
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.<br />
<br />
If at all possible, drive through a roundabout after it has been created or updated. Verify that it seems to give correct information.<br />
<br />
==== Bus or Cab Only Lanes[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
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.<br />
<br />
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.<br />
<br />
=== Non-drivable roads ===<br />
<br />
==== Railroad [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:RailroadTracksVanishingPoint.jpg|right|300px|RoadPicN11.jpg]]<br />
<br />
<br />
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.<br />
<br />
<br />
<br />
<br />
{{mbox<br />
| type = important<br />
| text = Please notice that railroads have changed from previous interpretations of railroad mapping. Even veteran editors need to pay attention to this section!<br />
}}<br />
<br />
<br />
* 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.<br />
* 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.<br />
* Always select "None" for the city name. This avoids [[Smudged_city#Overview|city smudging]].<br />
* Set railroad to 2-way directionality and Restrict turns ''to'' and ''from'' the railroad segments.<br />
* 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. <br />
* 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.<br />
* Canadian Pacific uses the acronym CPRS, but it is more know as CP, so it will be called CP Railroad<br />
*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.<br />
* Lock all railroads to a Level 2<br />
* Read [[Road_types/USA#Railroad|this section]] for more information about railroads.<br />
<br />
==== Runway/Taxiway[[File:Service road.png|200px|Service road.png]] ====<br />
[[File:Aelrwmn.png|right|250px]]<br />
We will map all airports runways such:<br />
<br />
* These roads will not connect to any drivable sections<br />
* The runways will not be connected to each other<br />
* 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.<br />
* After finding the code, we will use [http://www.airnav.com/airports/ this] to find the runway numbers for the airport.<br />
* Most of the time, you will see the number of the runway at the beginning and end of each runway from the aerial views. <br />
* 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".<br />
<br />
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. <br />
<br />
==== Walking Trails [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:RoadPicN9.jpg|right|300px|RoadPicN9.jpg]] {{clear}}<br />
<br />
==== Pedestrian Boardwalks [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:RoadPicN10.jpg|right|300px|RoadPicN10.jpg]] <br />
<br />
==== Stairway [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:RoadPicN11.jpg|right|300px|RoadPicN11.jpg]] {{clear}}<br />
<br />
<br />
<!---- DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ----<br />
-------------------------------------------------------------------------------------<br />
---- This page is only transcluded into (displayed on) the main page for this state.<br />
---- It directly follows the common guidelines applicable to all states. When this<br />
---- page is present (even if blanked), it displaces any optional code that might be<br />
---- in that section.<br />
---- If the original optional code from the main page for this section is still<br />
---- desired, it can be restored by adding the following code to the first line <br />
---- between the "DO NOT MODIFY" lines on this page:<br />
---- {{:USA/CommonState/Special roads|optional}}<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- If there will be a full page for this section, use code similar to the wording<br />
---- below to provide a hyperlink to that page. When creating the full page, use the<br />
---- link on the talk page to ensure the preload data is provided to help with<br />
---- formatting the page. Don't just use the red link from this section once it is<br />
---- saved.<br />
----<br />
See [[{{BasePage2}}/Special roads]] for guidance in {{RootPage2}} that may not be universal to all other states.<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- This section has three possible purposes:<br />
---- 1. It is only providing a hyperlink to the full page for this section.<br />
---- 2. It is only providing some unique guidance for this state that differs from<br />
---- other states.<br />
---- 3. It is intentionally wiping out the general optional content for this section<br />
---- for this state.<br />
------------------------------------------------------------------------------------></div>DallasGranthttps://www.waze.com/wiki/USA/index.php?title=Minnesota/Special_roads/Main&diff=99529Minnesota/Special roads/Main2015-03-15T05:26:21Z<p>DallasGrant: /* Non-drivable roads */</p>
<hr />
<div><!-- 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><!--<br />
------ DO NOT MODIFY ABOVE THIS LINE -------- DO NOT MODIFY ABOVE THIS LINE ------> <br />
=== Other drivable roads ===<br />
<br />
==== Dirt Road / 4X4 Trail[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
{{mbox<br />
| type = important<br />
| text = Minnesota has different interpretations of Dirt Roads than many other locations. Even veteran editors need to pay attention to this section!<br />
}}<br />
<br />
<br />
[[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.<br />
<br />
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.<br />
<br />
[[File:Dirtroad.PNG|300px|right]]<br />
<br />
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. <br />
<br />
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.<br />
<br />
==== Parking Lot Road[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:Parklotrhmmn.png|right|300px]]<br />
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.<br />
<br />
* Simple is best. Do not map every lane<br />
* Map the main entrances from the roads outside the parking lot<br />
* Map lanes that run along storefronts<br />
* Map lanes that run along main roads outside the parking area<br />
* Map primary lanes that serve to get people from one area of the lot to another<br />
<br />
For for information about mapping parking lots, follow this [[Best_map_editing_practice#Parking_Lots|article]]<br />
<br />
==== Private Road[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:Pi gated-community1.jpg|right|300px|Pi gated-community1.jpg]]<br />
<br />
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. <br />
<br />
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. <br />
<br />
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.<br />
<br />
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.<br />
<br />
==== Alleyways[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
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 Parking Lot class.<br />
<br />
[[File:Pizzalola.png|300px|left]]<br />
<br />
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 parking lot 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.<br />
<br />
==== Roundabouts [[Image:Round.png |50px]] ====<br />
<br />
{{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".<br />
[[File:Roundabouts.png|400px|right]]<br />
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. <br />
<br />
<br />
<br />
[[File:Roundboutmn2.png|400px|left]]<br />
<br />
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).<br />
<br />
<br />
<br />
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.<br />
<br />
If at all possible, drive through a roundabout after it has been created or updated. Verify that it seems to give correct information.<br />
<br />
==== Bus or Cab Only Lanes[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
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.<br />
<br />
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.<br />
<br />
=== Non-drivable roads ===<br />
<br />
==== Railroad [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:RailroadTracksVanishingPoint.jpg|right|300px|RoadPicN11.jpg]]<br />
<br />
<br />
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.<br />
<br />
<br />
<br />
<br />
{{mbox<br />
| type = important<br />
| text = Please notice that railroads have changed from previous interpretations of railroad mapping. Even veteran editors need to pay attention to this section!<br />
}}<br />
<br />
<br />
* 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.<br />
* 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.<br />
* Always select "None" for the city name. This avoids [[Smudged_city#Overview|city smudging]].<br />
* Set railroad to 2-way directionality and Restrict turns ''to'' and ''from'' the railroad segments.<br />
* 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. <br />
* 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.<br />
* Canadian Pacific uses the acronym CPRS, but it is more know as CP, so it will be called CP Railroad<br />
*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.<br />
* Lock all railroads to a Level 2<br />
* Read [[Road_types/USA#Railroad|this section]] for more information about railroads.<br />
<br />
==== Runway/Taxiway[[File:Service road.png|200px|Service road.png]] ====<br />
[[File:Aelrwmn.png|right|250px]]<br />
We will map all airports runways such:<br />
<br />
* These roads will not connect to any drivable sections<br />
* The runways will not be connected to each other<br />
* 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.<br />
* After finding the code, we will use [http://www.airnav.com/airports/ this] to find the runway numbers for the airport.<br />
* Most of the time, you will see the number of the runway at the beginning and end of each runway from the aerial views. <br />
* 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".<br />
<br />
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. <br />
<br />
==== Walking Trails [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:RoadPicN9.jpg|right|300px|RoadPicN9.jpg]]<br />
<br />
==== Pedestrian Boardwalks [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:RoadPicN10.jpg|right|300px|RoadPicN10.jpg]] <br />
<br />
==== Stairway [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:RoadPicN11.jpg|right|300px|RoadPicN11.jpg]] {{clear}}<br />
<br />
<br />
<!---- DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ----<br />
-------------------------------------------------------------------------------------<br />
---- This page is only transcluded into (displayed on) the main page for this state.<br />
---- It directly follows the common guidelines applicable to all states. When this<br />
---- page is present (even if blanked), it displaces any optional code that might be<br />
---- in that section.<br />
---- If the original optional code from the main page for this section is still<br />
---- desired, it can be restored by adding the following code to the first line <br />
---- between the "DO NOT MODIFY" lines on this page:<br />
---- {{:USA/CommonState/Special roads|optional}}<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- If there will be a full page for this section, use code similar to the wording<br />
---- below to provide a hyperlink to that page. When creating the full page, use the<br />
---- link on the talk page to ensure the preload data is provided to help with<br />
---- formatting the page. Don't just use the red link from this section once it is<br />
---- saved.<br />
----<br />
See [[{{BasePage2}}/Special roads]] for guidance in {{RootPage2}} that may not be universal to all other states.<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- This section has three possible purposes:<br />
---- 1. It is only providing a hyperlink to the full page for this section.<br />
---- 2. It is only providing some unique guidance for this state that differs from<br />
---- other states.<br />
---- 3. It is intentionally wiping out the general optional content for this section<br />
---- for this state.<br />
------------------------------------------------------------------------------------></div>DallasGranthttps://www.waze.com/wiki/USA/index.php?title=Minnesota/Special_roads/Main&diff=99528Minnesota/Special roads/Main2015-03-15T05:16:27Z<p>DallasGrant: /* Roundabouts 50px */</p>
<hr />
<div><!-- 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><!--<br />
------ DO NOT MODIFY ABOVE THIS LINE -------- DO NOT MODIFY ABOVE THIS LINE ------> <br />
=== Other drivable roads ===<br />
<br />
==== Dirt Road / 4X4 Trail[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
{{mbox<br />
| type = important<br />
| text = Minnesota has different interpretations of Dirt Roads than many other locations. Even veteran editors need to pay attention to this section!<br />
}}<br />
<br />
<br />
[[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.<br />
<br />
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.<br />
<br />
[[File:Dirtroad.PNG|300px|right]]<br />
<br />
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. <br />
<br />
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.<br />
<br />
==== Parking Lot Road[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:Parklotrhmmn.png|right|300px]]<br />
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.<br />
<br />
* Simple is best. Do not map every lane<br />
* Map the main entrances from the roads outside the parking lot<br />
* Map lanes that run along storefronts<br />
* Map lanes that run along main roads outside the parking area<br />
* Map primary lanes that serve to get people from one area of the lot to another<br />
<br />
For for information about mapping parking lots, follow this [[Best_map_editing_practice#Parking_Lots|article]]<br />
<br />
==== Private Road[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:Pi gated-community1.jpg|right|300px|Pi gated-community1.jpg]]<br />
<br />
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. <br />
<br />
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. <br />
<br />
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.<br />
<br />
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.<br />
<br />
==== Alleyways[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
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 Parking Lot class.<br />
<br />
[[File:Pizzalola.png|300px|left]]<br />
<br />
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 parking lot 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.<br />
<br />
==== Roundabouts [[Image:Round.png |50px]] ====<br />
<br />
{{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".<br />
[[File:Roundabouts.png|400px|right]]<br />
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. <br />
<br />
<br />
<br />
[[File:Roundboutmn2.png|400px|left]]<br />
<br />
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).<br />
<br />
<br />
<br />
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.<br />
<br />
If at all possible, drive through a roundabout after it has been created or updated. Verify that it seems to give correct information.<br />
<br />
==== Bus or Cab Only Lanes[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
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.<br />
<br />
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.<br />
<br />
=== Non-drivable roads ===<br />
<br />
==== Railroad [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:RailroadTracksVanishingPoint.jpg|right|300px|RoadPicN11.jpg]]<br />
<br />
<br />
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.<br />
<br />
<br />
<br />
<br />
{{mbox<br />
| type = important<br />
| text = Please notice that railroads have changed from previous interpretations of railroad mapping. Even veteran editors need to pay attention to this section!<br />
}}<br />
<br />
<br />
* 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.<br />
* 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.<br />
* Always select "None" for the city name. This avoids [[Smudged_city#Overview|city smudging]].<br />
* Set railroad to 2-way directionality and Restrict turns ''to'' and ''from'' the railroad segments.<br />
* 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. <br />
* 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.<br />
* Canadian Pacific uses the acronym CPRS, but it is more know as CP, so it will be called CP Railroad<br />
*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.<br />
* Lock all railroads to a Level 2<br />
* Read [[Road_types/USA#Railroad|this section]] for more information about railroads.<br />
<br />
==== Runway/Taxiway[[File:Service road.png|200px|Service road.png]] ====<br />
[[File:Aelrwmn.png|right|250px]]<br />
We will map all airports runways such:<br />
<br />
* These roads will not connect to any drivable sections<br />
* The runways will not be connected to each other<br />
* 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.<br />
* After finding the code, we will use [http://www.airnav.com/airports/ this] to find the runway numbers for the airport.<br />
* Most of the time, you will see the number of the runway at the beginning and end of each runway from the aerial views. <br />
* 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".<br />
<br />
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. <br />
<br />
<!---- DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ----<br />
-------------------------------------------------------------------------------------<br />
---- This page is only transcluded into (displayed on) the main page for this state.<br />
---- It directly follows the common guidelines applicable to all states. When this<br />
---- page is present (even if blanked), it displaces any optional code that might be<br />
---- in that section.<br />
---- If the original optional code from the main page for this section is still<br />
---- desired, it can be restored by adding the following code to the first line <br />
---- between the "DO NOT MODIFY" lines on this page:<br />
---- {{:USA/CommonState/Special roads|optional}}<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- If there will be a full page for this section, use code similar to the wording<br />
---- below to provide a hyperlink to that page. When creating the full page, use the<br />
---- link on the talk page to ensure the preload data is provided to help with<br />
---- formatting the page. Don't just use the red link from this section once it is<br />
---- saved.<br />
----<br />
See [[{{BasePage2}}/Special roads]] for guidance in {{RootPage2}} that may not be universal to all other states.<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- This section has three possible purposes:<br />
---- 1. It is only providing a hyperlink to the full page for this section.<br />
---- 2. It is only providing some unique guidance for this state that differs from<br />
---- other states.<br />
---- 3. It is intentionally wiping out the general optional content for this section<br />
---- for this state.<br />
------------------------------------------------------------------------------------></div>DallasGranthttps://www.waze.com/wiki/USA/index.php?title=Minnesota/Special_roads/Main&diff=99527Minnesota/Special roads/Main2015-03-15T05:07:18Z<p>DallasGrant: /* Runway/Taxiway200px|Service road.png */</p>
<hr />
<div><!-- 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><!--<br />
------ DO NOT MODIFY ABOVE THIS LINE -------- DO NOT MODIFY ABOVE THIS LINE ------> <br />
=== Other drivable roads ===<br />
<br />
==== Dirt Road / 4X4 Trail[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
{{mbox<br />
| type = important<br />
| text = Minnesota has different interpretations of Dirt Roads than many other locations. Even veteran editors need to pay attention to this section!<br />
}}<br />
<br />
<br />
[[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.<br />
<br />
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.<br />
<br />
[[File:Dirtroad.PNG|300px|right]]<br />
<br />
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. <br />
<br />
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.<br />
<br />
==== Parking Lot Road[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:Parklotrhmmn.png|right|300px]]<br />
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.<br />
<br />
* Simple is best. Do not map every lane<br />
* Map the main entrances from the roads outside the parking lot<br />
* Map lanes that run along storefronts<br />
* Map lanes that run along main roads outside the parking area<br />
* Map primary lanes that serve to get people from one area of the lot to another<br />
<br />
For for information about mapping parking lots, follow this [[Best_map_editing_practice#Parking_Lots|article]]<br />
<br />
==== Private Road[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:Pi gated-community1.jpg|right|300px|Pi gated-community1.jpg]]<br />
<br />
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. <br />
<br />
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. <br />
<br />
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.<br />
<br />
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.<br />
<br />
==== Alleyways[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
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 Parking Lot class.<br />
<br />
[[File:Pizzalola.png|300px|left]]<br />
<br />
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 parking lot 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.<br />
<br />
==== Roundabouts [[Image:Round.png |50px]] ====<br />
<br />
{{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".<br />
[[File:Roundabouts.png|400px|right]]<br />
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. <br />
<br />
<br />
<br />
[[File:Roundboutmn2.png|400px|left]]<br />
<br />
<br />
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).<br />
<br />
<br />
<br />
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.<br />
<br />
If at all possible, drive through a roundabout after it has been created or updated. Verify that it seems to give correct information.<br />
<br />
<br />
==== Bus or Cab Only Lanes[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
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.<br />
<br />
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.<br />
<br />
=== Non-drivable roads ===<br />
<br />
==== Railroad [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:RailroadTracksVanishingPoint.jpg|right|300px|RoadPicN11.jpg]]<br />
<br />
<br />
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.<br />
<br />
<br />
<br />
<br />
{{mbox<br />
| type = important<br />
| text = Please notice that railroads have changed from previous interpretations of railroad mapping. Even veteran editors need to pay attention to this section!<br />
}}<br />
<br />
<br />
* 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.<br />
* 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.<br />
* Always select "None" for the city name. This avoids [[Smudged_city#Overview|city smudging]].<br />
* Set railroad to 2-way directionality and Restrict turns ''to'' and ''from'' the railroad segments.<br />
* 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. <br />
* 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.<br />
* Canadian Pacific uses the acronym CPRS, but it is more know as CP, so it will be called CP Railroad<br />
*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.<br />
* Lock all railroads to a Level 2<br />
* Read [[Road_types/USA#Railroad|this section]] for more information about railroads.<br />
<br />
==== Runway/Taxiway[[File:Service road.png|200px|Service road.png]] ====<br />
[[File:Aelrwmn.png|right|250px]]<br />
We will map all airports runways such:<br />
<br />
* These roads will not connect to any drivable sections<br />
* The runways will not be connected to each other<br />
* 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.<br />
* After finding the code, we will use [http://www.airnav.com/airports/ this] to find the runway numbers for the airport.<br />
* Most of the time, you will see the number of the runway at the beginning and end of each runway from the aerial views. <br />
* 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".<br />
<br />
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. <br />
<br />
<!---- DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ----<br />
-------------------------------------------------------------------------------------<br />
---- This page is only transcluded into (displayed on) the main page for this state.<br />
---- It directly follows the common guidelines applicable to all states. When this<br />
---- page is present (even if blanked), it displaces any optional code that might be<br />
---- in that section.<br />
---- If the original optional code from the main page for this section is still<br />
---- desired, it can be restored by adding the following code to the first line <br />
---- between the "DO NOT MODIFY" lines on this page:<br />
---- {{:USA/CommonState/Special roads|optional}}<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- If there will be a full page for this section, use code similar to the wording<br />
---- below to provide a hyperlink to that page. When creating the full page, use the<br />
---- link on the talk page to ensure the preload data is provided to help with<br />
---- formatting the page. Don't just use the red link from this section once it is<br />
---- saved.<br />
----<br />
See [[{{BasePage2}}/Special roads]] for guidance in {{RootPage2}} that may not be universal to all other states.<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- This section has three possible purposes:<br />
---- 1. It is only providing a hyperlink to the full page for this section.<br />
---- 2. It is only providing some unique guidance for this state that differs from<br />
---- other states.<br />
---- 3. It is intentionally wiping out the general optional content for this section<br />
---- for this state.<br />
------------------------------------------------------------------------------------></div>DallasGranthttps://www.waze.com/wiki/USA/index.php?title=Minnesota/Special_roads/Main&diff=99526Minnesota/Special roads/Main2015-03-15T04:52:02Z<p>DallasGrant: /* Bus or cab only lanes200px|Service road.png */</p>
<hr />
<div><!-- 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><!--<br />
------ DO NOT MODIFY ABOVE THIS LINE -------- DO NOT MODIFY ABOVE THIS LINE ------> <br />
=== Other drivable roads ===<br />
<br />
==== Dirt Road / 4X4 Trail[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
{{mbox<br />
| type = important<br />
| text = Minnesota has different interpretations of Dirt Roads than many other locations. Even veteran editors need to pay attention to this section!<br />
}}<br />
<br />
<br />
[[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.<br />
<br />
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.<br />
<br />
[[File:Dirtroad.PNG|300px|right]]<br />
<br />
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. <br />
<br />
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.<br />
<br />
==== Parking Lot Road[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:Parklotrhmmn.png|right|300px]]<br />
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.<br />
<br />
* Simple is best. Do not map every lane<br />
* Map the main entrances from the roads outside the parking lot<br />
* Map lanes that run along storefronts<br />
* Map lanes that run along main roads outside the parking area<br />
* Map primary lanes that serve to get people from one area of the lot to another<br />
<br />
For for information about mapping parking lots, follow this [[Best_map_editing_practice#Parking_Lots|article]]<br />
<br />
==== Private Road[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:Pi gated-community1.jpg|right|300px|Pi gated-community1.jpg]]<br />
<br />
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. <br />
<br />
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. <br />
<br />
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.<br />
<br />
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.<br />
<br />
==== Alleyways[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
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 Parking Lot class.<br />
<br />
[[File:Pizzalola.png|300px|left]]<br />
<br />
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 parking lot 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.<br />
<br />
==== Roundabouts [[Image:Round.png |50px]] ====<br />
<br />
{{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".<br />
[[File:Roundabouts.png|400px|right]]<br />
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. <br />
<br />
<br />
<br />
[[File:Roundboutmn2.png|400px|left]]<br />
<br />
<br />
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).<br />
<br />
<br />
<br />
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.<br />
<br />
If at all possible, drive through a roundabout after it has been created or updated. Verify that it seems to give correct information.<br />
<br />
<br />
==== Bus or Cab Only Lanes[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
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.<br />
<br />
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.<br />
<br />
=== Non-drivable roads ===<br />
<br />
==== Railroad [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:RailroadTracksVanishingPoint.jpg|right|300px|RoadPicN11.jpg]]<br />
<br />
<br />
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.<br />
<br />
<br />
<br />
<br />
{{mbox<br />
| type = important<br />
| text = Please notice that railroads have changed from previous interpretations of railroad mapping. Even veteran editors need to pay attention to this section!<br />
}}<br />
<br />
<br />
* 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.<br />
* 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.<br />
* Always select "None" for the city name. This avoids [[Smudged_city#Overview|city smudging]].<br />
* Set railroad to 2-way directionality and Restrict turns ''to'' and ''from'' the railroad segments.<br />
* 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. <br />
* 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.<br />
* Canadian Pacific uses the acronym CPRS, but it is more know as CP, so it will be called CP Railroad<br />
*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.<br />
* Lock all railroads to a Level 2<br />
* Read [[Road_types/USA#Railroad|this section]] for more information about railroads.<br />
<br />
==== Runway/Taxiway[[File:Service road.png|200px|Service road.png]] ====<br />
[[File:Aelrwmn.png|right|250px]]<br />
We will map all airports runways such:<br />
<br />
* These roads will not connect to any drivable sections<br />
* The runways will not be connected to each other<br />
* 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<br />
* After finding the code, we will use [http://www.airnav.com/airports/ this] to find the runway numbers for the airport<br />
* Most of the time, you will see the number of the runway at the beginning and end of each runway<br />
* 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".<br />
<br />
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. <br />
<br />
<!---- DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ----<br />
-------------------------------------------------------------------------------------<br />
---- This page is only transcluded into (displayed on) the main page for this state.<br />
---- It directly follows the common guidelines applicable to all states. When this<br />
---- page is present (even if blanked), it displaces any optional code that might be<br />
---- in that section.<br />
---- If the original optional code from the main page for this section is still<br />
---- desired, it can be restored by adding the following code to the first line <br />
---- between the "DO NOT MODIFY" lines on this page:<br />
---- {{:USA/CommonState/Special roads|optional}}<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- If there will be a full page for this section, use code similar to the wording<br />
---- below to provide a hyperlink to that page. When creating the full page, use the<br />
---- link on the talk page to ensure the preload data is provided to help with<br />
---- formatting the page. Don't just use the red link from this section once it is<br />
---- saved.<br />
----<br />
See [[{{BasePage2}}/Special roads]] for guidance in {{RootPage2}} that may not be universal to all other states.<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- This section has three possible purposes:<br />
---- 1. It is only providing a hyperlink to the full page for this section.<br />
---- 2. It is only providing some unique guidance for this state that differs from<br />
---- other states.<br />
---- 3. It is intentionally wiping out the general optional content for this section<br />
---- for this state.<br />
------------------------------------------------------------------------------------></div>DallasGranthttps://www.waze.com/wiki/USA/index.php?title=Minnesota/Special_roads/Main&diff=99524Minnesota/Special roads/Main2015-03-15T04:26:00Z<p>DallasGrant: /* Bus or cab only lanes */</p>
<hr />
<div><!-- 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><!--<br />
------ DO NOT MODIFY ABOVE THIS LINE -------- DO NOT MODIFY ABOVE THIS LINE ------> <br />
=== Other drivable roads ===<br />
<br />
==== Dirt Road / 4X4 Trail[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
{{mbox<br />
| type = important<br />
| text = Minnesota has different interpretations of Dirt Roads than many other locations. Even veteran editors need to pay attention to this section!<br />
}}<br />
<br />
<br />
[[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.<br />
<br />
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.<br />
<br />
[[File:Dirtroad.PNG|300px|right]]<br />
<br />
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. <br />
<br />
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.<br />
<br />
==== Parking Lot Road[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:Parklotrhmmn.png|right|300px]]<br />
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.<br />
<br />
* Simple is best. Do not map every lane<br />
* Map the main entrances from the roads outside the parking lot<br />
* Map lanes that run along storefronts<br />
* Map lanes that run along main roads outside the parking area<br />
* Map primary lanes that serve to get people from one area of the lot to another<br />
<br />
For for information about mapping parking lots, follow this [[Best_map_editing_practice#Parking_Lots|article]]<br />
<br />
==== Private Road[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:Pi gated-community1.jpg|right|300px|Pi gated-community1.jpg]]<br />
<br />
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. <br />
<br />
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. <br />
<br />
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.<br />
<br />
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.<br />
<br />
==== Alleyways[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
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 Parking Lot class.<br />
<br />
[[File:Pizzalola.png|300px|left]]<br />
<br />
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 parking lot 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.<br />
<br />
==== Roundabouts [[Image:Round.png |50px]] ====<br />
<br />
{{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".<br />
[[File:Roundabouts.png|400px|right]]<br />
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. <br />
<br />
<br />
<br />
[[File:Roundboutmn2.png|400px|left]]<br />
<br />
<br />
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).<br />
<br />
<br />
<br />
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.<br />
<br />
If at all possible, drive through a roundabout after it has been created or updated. Verify that it seems to give correct information.<br />
<br />
<br />
==== Bus or cab only lanes[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
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.<br />
<br />
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.<br />
<br />
=== Non-drivable roads ===<br />
<br />
==== Railroad [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:RailroadTracksVanishingPoint.jpg|right|300px|RoadPicN11.jpg]]<br />
<br />
<br />
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.<br />
<br />
<br />
<br />
<br />
{{mbox<br />
| type = important<br />
| text = Please notice that railroads have changed from previous interpretations of railroad mapping. Even veteran editors need to pay attention to this section!<br />
}}<br />
<br />
<br />
* 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.<br />
* 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.<br />
* Always select "None" for the city name. This avoids [[Smudged_city#Overview|city smudging]].<br />
* Set railroad to 2-way directionality and Restrict turns ''to'' and ''from'' the railroad segments.<br />
* 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. <br />
* 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.<br />
* Canadian Pacific uses the acronym CPRS, but it is more know as CP, so it will be called CP Railroad<br />
*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.<br />
* Lock all railroads to a Level 2<br />
* Read [[Road_types/USA#Railroad|this section]] for more information about railroads.<br />
<br />
==== Runway/Taxiway[[File:Service road.png|200px|Service road.png]] ====<br />
[[File:Aelrwmn.png|right|250px]]<br />
We will map all airports runways such:<br />
<br />
* These roads will not connect to any drivable sections<br />
* The runways will not be connected to each other<br />
* 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<br />
* After finding the code, we will use [http://www.airnav.com/airports/ this] to find the runway numbers for the airport<br />
* Most of the time, you will see the number of the runway at the beginning and end of each runway<br />
* 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".<br />
<br />
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. <br />
<br />
<!---- DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ----<br />
-------------------------------------------------------------------------------------<br />
---- This page is only transcluded into (displayed on) the main page for this state.<br />
---- It directly follows the common guidelines applicable to all states. When this<br />
---- page is present (even if blanked), it displaces any optional code that might be<br />
---- in that section.<br />
---- If the original optional code from the main page for this section is still<br />
---- desired, it can be restored by adding the following code to the first line <br />
---- between the "DO NOT MODIFY" lines on this page:<br />
---- {{:USA/CommonState/Special roads|optional}}<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- If there will be a full page for this section, use code similar to the wording<br />
---- below to provide a hyperlink to that page. When creating the full page, use the<br />
---- link on the talk page to ensure the preload data is provided to help with<br />
---- formatting the page. Don't just use the red link from this section once it is<br />
---- saved.<br />
----<br />
See [[{{BasePage2}}/Special roads]] for guidance in {{RootPage2}} that may not be universal to all other states.<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- This section has three possible purposes:<br />
---- 1. It is only providing a hyperlink to the full page for this section.<br />
---- 2. It is only providing some unique guidance for this state that differs from<br />
---- other states.<br />
---- 3. It is intentionally wiping out the general optional content for this section<br />
---- for this state.<br />
------------------------------------------------------------------------------------></div>DallasGranthttps://www.waze.com/wiki/USA/index.php?title=Minnesota/Special_roads/Main&diff=99523Minnesota/Special roads/Main2015-03-15T04:25:03Z<p>DallasGrant: /* Runway/Taxiway */</p>
<hr />
<div><!-- 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><!--<br />
------ DO NOT MODIFY ABOVE THIS LINE -------- DO NOT MODIFY ABOVE THIS LINE ------> <br />
=== Other drivable roads ===<br />
<br />
==== Dirt Road / 4X4 Trail[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
{{mbox<br />
| type = important<br />
| text = Minnesota has different interpretations of Dirt Roads than many other locations. Even veteran editors need to pay attention to this section!<br />
}}<br />
<br />
<br />
[[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.<br />
<br />
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.<br />
<br />
[[File:Dirtroad.PNG|300px|right]]<br />
<br />
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. <br />
<br />
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.<br />
<br />
==== Parking Lot Road[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:Parklotrhmmn.png|right|300px]]<br />
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.<br />
<br />
* Simple is best. Do not map every lane<br />
* Map the main entrances from the roads outside the parking lot<br />
* Map lanes that run along storefronts<br />
* Map lanes that run along main roads outside the parking area<br />
* Map primary lanes that serve to get people from one area of the lot to another<br />
<br />
For for information about mapping parking lots, follow this [[Best_map_editing_practice#Parking_Lots|article]]<br />
<br />
==== Private Road[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:Pi gated-community1.jpg|right|300px|Pi gated-community1.jpg]]<br />
<br />
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. <br />
<br />
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. <br />
<br />
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.<br />
<br />
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.<br />
<br />
==== Alleyways[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
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 Parking Lot class.<br />
<br />
[[File:Pizzalola.png|300px|left]]<br />
<br />
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 parking lot 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.<br />
<br />
==== Roundabouts [[Image:Round.png |50px]] ====<br />
<br />
{{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".<br />
[[File:Roundabouts.png|400px|right]]<br />
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. <br />
<br />
<br />
<br />
[[File:Roundboutmn2.png|400px|left]]<br />
<br />
<br />
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).<br />
<br />
<br />
<br />
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.<br />
<br />
If at all possible, drive through a roundabout after it has been created or updated. Verify that it seems to give correct information.<br />
<br />
<br />
==== Bus or cab only lanes ====<br />
<br />
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.<br />
<br />
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.<br />
<br />
=== Non-drivable roads ===<br />
<br />
==== Railroad [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:RailroadTracksVanishingPoint.jpg|right|300px|RoadPicN11.jpg]]<br />
<br />
<br />
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.<br />
<br />
<br />
<br />
<br />
{{mbox<br />
| type = important<br />
| text = Please notice that railroads have changed from previous interpretations of railroad mapping. Even veteran editors need to pay attention to this section!<br />
}}<br />
<br />
<br />
* 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.<br />
* 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.<br />
* Always select "None" for the city name. This avoids [[Smudged_city#Overview|city smudging]].<br />
* Set railroad to 2-way directionality and Restrict turns ''to'' and ''from'' the railroad segments.<br />
* 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. <br />
* 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.<br />
* Canadian Pacific uses the acronym CPRS, but it is more know as CP, so it will be called CP Railroad<br />
*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.<br />
* Lock all railroads to a Level 2<br />
* Read [[Road_types/USA#Railroad|this section]] for more information about railroads.<br />
<br />
==== Runway/Taxiway[[File:Service road.png|200px|Service road.png]] ====<br />
[[File:Aelrwmn.png|right|250px]]<br />
We will map all airports runways such:<br />
<br />
* These roads will not connect to any drivable sections<br />
* The runways will not be connected to each other<br />
* 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<br />
* After finding the code, we will use [http://www.airnav.com/airports/ this] to find the runway numbers for the airport<br />
* Most of the time, you will see the number of the runway at the beginning and end of each runway<br />
* 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".<br />
<br />
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. <br />
<br />
<!---- DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ----<br />
-------------------------------------------------------------------------------------<br />
---- This page is only transcluded into (displayed on) the main page for this state.<br />
---- It directly follows the common guidelines applicable to all states. When this<br />
---- page is present (even if blanked), it displaces any optional code that might be<br />
---- in that section.<br />
---- If the original optional code from the main page for this section is still<br />
---- desired, it can be restored by adding the following code to the first line <br />
---- between the "DO NOT MODIFY" lines on this page:<br />
---- {{:USA/CommonState/Special roads|optional}}<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- If there will be a full page for this section, use code similar to the wording<br />
---- below to provide a hyperlink to that page. When creating the full page, use the<br />
---- link on the talk page to ensure the preload data is provided to help with<br />
---- formatting the page. Don't just use the red link from this section once it is<br />
---- saved.<br />
----<br />
See [[{{BasePage2}}/Special roads]] for guidance in {{RootPage2}} that may not be universal to all other states.<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- This section has three possible purposes:<br />
---- 1. It is only providing a hyperlink to the full page for this section.<br />
---- 2. It is only providing some unique guidance for this state that differs from<br />
---- other states.<br />
---- 3. It is intentionally wiping out the general optional content for this section<br />
---- for this state.<br />
------------------------------------------------------------------------------------></div>DallasGranthttps://www.waze.com/wiki/USA/index.php?title=File:Aelrwmn.png&diff=99521File:Aelrwmn.png2015-03-15T03:54:58Z<p>DallasGrant: </p>
<hr />
<div></div>DallasGranthttps://www.waze.com/wiki/USA/index.php?title=Minnesota/Special_roads/Main&diff=99519Minnesota/Special roads/Main2015-03-15T02:21:33Z<p>DallasGrant: /* Other drivable roads */</p>
<hr />
<div><!-- 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><!--<br />
------ DO NOT MODIFY ABOVE THIS LINE -------- DO NOT MODIFY ABOVE THIS LINE ------> <br />
=== Other drivable roads ===<br />
<br />
==== Dirt Road / 4X4 Trail[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
{{mbox<br />
| type = important<br />
| text = Minnesota has different interpretations of Dirt Roads than many other locations. Even veteran editors need to pay attention to this section!<br />
}}<br />
<br />
<br />
[[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.<br />
<br />
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.<br />
<br />
[[File:Dirtroad.PNG|300px|right]]<br />
<br />
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. <br />
<br />
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.<br />
<br />
==== Parking Lot Road[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:Parklotrhmmn.png|right|300px]]<br />
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.<br />
<br />
* Simple is best. Do not map every lane<br />
* Map the main entrances from the roads outside the parking lot<br />
* Map lanes that run along storefronts<br />
* Map lanes that run along main roads outside the parking area<br />
* Map primary lanes that serve to get people from one area of the lot to another<br />
<br />
For for information about mapping parking lots, follow this [[Best_map_editing_practice#Parking_Lots|article]]<br />
<br />
==== Private Road[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:Pi gated-community1.jpg|right|300px|Pi gated-community1.jpg]]<br />
<br />
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. <br />
<br />
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. <br />
<br />
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.<br />
<br />
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.<br />
<br />
==== Alleyways[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
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 Parking Lot class.<br />
<br />
[[File:Pizzalola.png|300px|left]]<br />
<br />
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 parking lot 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.<br />
<br />
==== Roundabouts [[Image:Round.png |50px]] ====<br />
<br />
{{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".<br />
[[File:Roundabouts.png|400px|right]]<br />
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. <br />
<br />
<br />
<br />
[[File:Roundboutmn2.png|400px|left]]<br />
<br />
<br />
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).<br />
<br />
<br />
<br />
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.<br />
<br />
If at all possible, drive through a roundabout after it has been created or updated. Verify that it seems to give correct information.<br />
<br />
<br />
==== Bus or cab only lanes ====<br />
<br />
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.<br />
<br />
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.<br />
<br />
=== Non-drivable roads ===<br />
<br />
==== Railroad [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:RailroadTracksVanishingPoint.jpg|right|300px|RoadPicN11.jpg]]<br />
<br />
<br />
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.<br />
<br />
<br />
<br />
<br />
{{mbox<br />
| type = important<br />
| text = Please notice that railroads have changed from previous interpretations of railroad mapping. Even veteran editors need to pay attention to this section!<br />
}}<br />
<br />
<br />
* 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.<br />
* 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.<br />
* Always select "None" for the city name. This avoids [[Smudged_city#Overview|city smudging]].<br />
* Set railroad to 2-way directionality and Restrict turns ''to'' and ''from'' the railroad segments.<br />
* 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. <br />
* 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.<br />
* Canadian Pacific uses the acronym CPRS, but it is more know as CP, so it will be called CP Railroad<br />
*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.<br />
* Lock all railroads to a Level 2<br />
* Read [[Road_types/USA#Railroad|this section]] for more information about railroads.<br />
<br />
==== Runway/Taxiway ====<br />
<br />
<br />
<br />
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. <br />
<br />
<!---- DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ----<br />
-------------------------------------------------------------------------------------<br />
---- This page is only transcluded into (displayed on) the main page for this state.<br />
---- It directly follows the common guidelines applicable to all states. When this<br />
---- page is present (even if blanked), it displaces any optional code that might be<br />
---- in that section.<br />
---- If the original optional code from the main page for this section is still<br />
---- desired, it can be restored by adding the following code to the first line <br />
---- between the "DO NOT MODIFY" lines on this page:<br />
---- {{:USA/CommonState/Special roads|optional}}<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- If there will be a full page for this section, use code similar to the wording<br />
---- below to provide a hyperlink to that page. When creating the full page, use the<br />
---- link on the talk page to ensure the preload data is provided to help with<br />
---- formatting the page. Don't just use the red link from this section once it is<br />
---- saved.<br />
----<br />
See [[{{BasePage2}}/Special roads]] for guidance in {{RootPage2}} that may not be universal to all other states.<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- This section has three possible purposes:<br />
---- 1. It is only providing a hyperlink to the full page for this section.<br />
---- 2. It is only providing some unique guidance for this state that differs from<br />
---- other states.<br />
---- 3. It is intentionally wiping out the general optional content for this section<br />
---- for this state.<br />
------------------------------------------------------------------------------------></div>DallasGranthttps://www.waze.com/wiki/USA/index.php?title=Minnesota/Special_roads/Main&diff=99518Minnesota/Special roads/Main2015-03-15T02:17:14Z<p>DallasGrant: /* Private Road200px|Service road.png */</p>
<hr />
<div><!-- 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><!--<br />
------ DO NOT MODIFY ABOVE THIS LINE -------- DO NOT MODIFY ABOVE THIS LINE ------> <br />
=== Other drivable roads ===<br />
<br />
==== Dirt Road / 4X4 Trail[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
{{mbox<br />
| type = important<br />
| text = Minnesota has different interpretations of Dirt Roads than many other locations. Even veteran editors need to pay attention to this section!<br />
}}<br />
<br />
<br />
[[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.<br />
<br />
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.<br />
<br />
[[File:Dirtroad.PNG|300px|right]]<br />
<br />
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. <br />
<br />
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.<br />
<br />
==== Parking Lot Road[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:Parklotrhmmn.png|right|300px]]<br />
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.<br />
<br />
* Simple is best. Do not map every lane<br />
* Map the main entrances from the roads outside the parking lot<br />
* Map lanes that run along storefronts<br />
* Map lanes that run along main roads outside the parking area<br />
* Map primary lanes that serve to get people from one area of the lot to another<br />
<br />
For for information about mapping parking lots, follow this [[Best_map_editing_practice#Parking_Lots|article]]<br />
<br />
==== Private Road[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:Pi gated-community1.jpg|right|300px|Pi gated-community1.jpg]]<br />
<br />
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. <br />
<br />
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. <br />
<br />
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.<br />
<br />
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.<br />
<br />
==== Alleyways[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
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 Parking Lot class.<br />
<br />
[[File:Pizzalola.png|300px|left]]<br />
<br />
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 parking lot 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.<br />
<br />
==== Roundabouts [[Image:Round.png |50px]] ====<br />
<br />
{{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".<br />
[[File:Roundabouts.png|400px|right]]<br />
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. <br />
<br />
<br />
<br />
[[File:Roundboutmn2.png|400px|left]]<br />
<br />
<br />
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).<br />
<br />
<br />
<br />
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.<br />
<br />
If at all possible, drive through a roundabout after it has been created or updated. Verify that it seems to give correct information.<br />
<br />
=== Non-drivable roads ===<br />
<br />
==== Railroad [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:RailroadTracksVanishingPoint.jpg|right|300px|RoadPicN11.jpg]]<br />
<br />
<br />
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.<br />
<br />
<br />
<br />
<br />
{{mbox<br />
| type = important<br />
| text = Please notice that railroads have changed from previous interpretations of railroad mapping. Even veteran editors need to pay attention to this section!<br />
}}<br />
<br />
<br />
* 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.<br />
* 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.<br />
* Always select "None" for the city name. This avoids [[Smudged_city#Overview|city smudging]].<br />
* Set railroad to 2-way directionality and Restrict turns ''to'' and ''from'' the railroad segments.<br />
* 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. <br />
* 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.<br />
* Canadian Pacific uses the acronym CPRS, but it is more know as CP, so it will be called CP Railroad<br />
*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.<br />
* Lock all railroads to a Level 2<br />
* Read [[Road_types/USA#Railroad|this section]] for more information about railroads.<br />
<br />
==== Runway/Taxiway ====<br />
<br />
<br />
<br />
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. <br />
<br />
<!---- DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ----<br />
-------------------------------------------------------------------------------------<br />
---- This page is only transcluded into (displayed on) the main page for this state.<br />
---- It directly follows the common guidelines applicable to all states. When this<br />
---- page is present (even if blanked), it displaces any optional code that might be<br />
---- in that section.<br />
---- If the original optional code from the main page for this section is still<br />
---- desired, it can be restored by adding the following code to the first line <br />
---- between the "DO NOT MODIFY" lines on this page:<br />
---- {{:USA/CommonState/Special roads|optional}}<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- If there will be a full page for this section, use code similar to the wording<br />
---- below to provide a hyperlink to that page. When creating the full page, use the<br />
---- link on the talk page to ensure the preload data is provided to help with<br />
---- formatting the page. Don't just use the red link from this section once it is<br />
---- saved.<br />
----<br />
See [[{{BasePage2}}/Special roads]] for guidance in {{RootPage2}} that may not be universal to all other states.<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- This section has three possible purposes:<br />
---- 1. It is only providing a hyperlink to the full page for this section.<br />
---- 2. It is only providing some unique guidance for this state that differs from<br />
---- other states.<br />
---- 3. It is intentionally wiping out the general optional content for this section<br />
---- for this state.<br />
------------------------------------------------------------------------------------></div>DallasGranthttps://www.waze.com/wiki/USA/index.php?title=Minnesota/Special_roads/Main&diff=99517Minnesota/Special roads/Main2015-03-15T02:15:58Z<p>DallasGrant: /* Runway/Taxiway */</p>
<hr />
<div><!-- 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><!--<br />
------ DO NOT MODIFY ABOVE THIS LINE -------- DO NOT MODIFY ABOVE THIS LINE ------> <br />
=== Other drivable roads ===<br />
<br />
==== Dirt Road / 4X4 Trail[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
{{mbox<br />
| type = important<br />
| text = Minnesota has different interpretations of Dirt Roads than many other locations. Even veteran editors need to pay attention to this section!<br />
}}<br />
<br />
<br />
[[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.<br />
<br />
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.<br />
<br />
[[File:Dirtroad.PNG|300px|right]]<br />
<br />
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. <br />
<br />
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.<br />
<br />
==== Parking Lot Road[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:Parklotrhmmn.png|right|300px]]<br />
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.<br />
<br />
* Simple is best. Do not map every lane<br />
* Map the main entrances from the roads outside the parking lot<br />
* Map lanes that run along storefronts<br />
* Map lanes that run along main roads outside the parking area<br />
* Map primary lanes that serve to get people from one area of the lot to another<br />
<br />
For for information about mapping parking lots, follow this [[Best_map_editing_practice#Parking_Lots|article]]<br />
<br />
==== Private Road[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:Pi gated-community1.jpg|right|300px|Pi gated-community1.jpg]]<br />
<br />
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. <br />
<br />
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. <br />
<br />
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.<br />
<br />
==== Alleyways[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
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 Parking Lot class.<br />
<br />
[[File:Pizzalola.png|300px|left]]<br />
<br />
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 parking lot 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.<br />
<br />
==== Roundabouts [[Image:Round.png |50px]] ====<br />
<br />
{{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".<br />
[[File:Roundabouts.png|400px|right]]<br />
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. <br />
<br />
<br />
<br />
[[File:Roundboutmn2.png|400px|left]]<br />
<br />
<br />
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).<br />
<br />
<br />
<br />
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.<br />
<br />
If at all possible, drive through a roundabout after it has been created or updated. Verify that it seems to give correct information.<br />
<br />
=== Non-drivable roads ===<br />
<br />
==== Railroad [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:RailroadTracksVanishingPoint.jpg|right|300px|RoadPicN11.jpg]]<br />
<br />
<br />
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.<br />
<br />
<br />
<br />
<br />
{{mbox<br />
| type = important<br />
| text = Please notice that railroads have changed from previous interpretations of railroad mapping. Even veteran editors need to pay attention to this section!<br />
}}<br />
<br />
<br />
* 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.<br />
* 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.<br />
* Always select "None" for the city name. This avoids [[Smudged_city#Overview|city smudging]].<br />
* Set railroad to 2-way directionality and Restrict turns ''to'' and ''from'' the railroad segments.<br />
* 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. <br />
* 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.<br />
* Canadian Pacific uses the acronym CPRS, but it is more know as CP, so it will be called CP Railroad<br />
*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.<br />
* Lock all railroads to a Level 2<br />
* Read [[Road_types/USA#Railroad|this section]] for more information about railroads.<br />
<br />
==== Runway/Taxiway ====<br />
<br />
<br />
<br />
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. <br />
<br />
<!---- DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ----<br />
-------------------------------------------------------------------------------------<br />
---- This page is only transcluded into (displayed on) the main page for this state.<br />
---- It directly follows the common guidelines applicable to all states. When this<br />
---- page is present (even if blanked), it displaces any optional code that might be<br />
---- in that section.<br />
---- If the original optional code from the main page for this section is still<br />
---- desired, it can be restored by adding the following code to the first line <br />
---- between the "DO NOT MODIFY" lines on this page:<br />
---- {{:USA/CommonState/Special roads|optional}}<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- If there will be a full page for this section, use code similar to the wording<br />
---- below to provide a hyperlink to that page. When creating the full page, use the<br />
---- link on the talk page to ensure the preload data is provided to help with<br />
---- formatting the page. Don't just use the red link from this section once it is<br />
---- saved.<br />
----<br />
See [[{{BasePage2}}/Special roads]] for guidance in {{RootPage2}} that may not be universal to all other states.<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- This section has three possible purposes:<br />
---- 1. It is only providing a hyperlink to the full page for this section.<br />
---- 2. It is only providing some unique guidance for this state that differs from<br />
---- other states.<br />
---- 3. It is intentionally wiping out the general optional content for this section<br />
---- for this state.<br />
------------------------------------------------------------------------------------></div>DallasGranthttps://www.waze.com/wiki/USA/index.php?title=Road_types&diff=99516Road types2015-03-15T02:15:47Z<p>DallasGrant: /* Driveways */</p>
<hr />
<div>{{mbox<br />
| type = critical<br />
| text = The contents of this page were completely revamped starting 19 April 2014, to incorporate an entirely new set of guidelines for map editing. All US editors should familiarize themselves with the contents of this page. Please see [http://www.waze.com/forum/viewtopic.php?f=276&t=85397 this topic] for details.<br />
}}<br />
{{UpdatedBanner<br />
|majorDate = 1/14/15<br />
|majorDesc = Clarify when to use PLR vs Private Road for apartment complexes, trailer parks, schools, universities, etc.<br />
|majorForum = http://www.waze.com/forum/viewtopic.php?f=276&t=124820}}<br />
<br />
'''Road types''' in the United States can be divided into three categories: public roads, other drivable roads, and non-drivable roads.<br />
<br />
Public road types in Waze are determined by the FHWA functional classification of the road and, where applicable, by the highway system to which the road belongs.<br />
<br />
{{LocalGuidance|link=Mapping resources/USA/States}}<br />
<br/><br />
== Overview ==<br />
<br />
=== Functional classification ===<br />
<br />
Functional classifications (FC) are determined using a set of criteria selected by the [[wikipedia:Federal Highway Administration|Federal Highway Administration]] (FHWA). These criteria include not only the physical attributes of the road but also efficiency of travel, number of access points, speed limits, route spacing, actual usage, and continuity. This can lead to quite different classifications for roads that appear similar. For example, a six-lane divided road in an urbanized area may be a Collector (Primary Street); a two-lane road through the middle of a town may be a principal arterial (Major Highway).<br />
<br />
Functional classification is a national standard, but functional classification maps are published by state departments of transportation. Links to functional classification maps for each state can be found on [[National resources/USA/Functional classification|the USA functional classification page]].<br />
<br />
=== Highway systems ===<br />
<br />
The '''[[wikipedia:Interstate Highway System|Interstate Highway System]]''' (formally, the Dwight D. Eisenhower National System of Interstate and Defense Highways) is a nationwide network of freeways designated by Congress and administered by the FHWA and [[wikipedia:American Association of State Highway and Transportation Officials|AASHTO]], a nationwide organization of state departments of transportation with governmental support. The system facilitates high-speed travel throughout the nation.<br />
<br />
The [[wikipedia:United States Numbered Highways|United States Numbered Highways]], or '''U.S. Highways''', system is a nationwide integrated network of roads also desginated by Congress and administered by the FHWA and AASHTO. While many of the routes in this system have been superseded by the Interstate Highway System, they remain important as direct links between regions not served by the new system, and as alternatives to Interstate travel in the case of heavy traffic or incident.<br />
<br />
Each of the fifty states (along with the District of Columbia and some of the United States's overseas territories) has a numbered '''[[wikipedia:state highway|state highway]] system'''. These systems are designated and administered by their respective state legislatures and departments of transportation as statewide networks of important travel links between cities and communities of those states. The roads in these systems, while of lesser national importance, are nevertheless essential for travel within the state.<br />
<br />
In addition to their state highway systems, some states designate [[wikipedia:County highway|county routes]] which are important for travel within a county. These routes serve important functions in a short-distance capacity.<br />
<br />
=== Importance of road types ===<br />
<br />
Road types are important for both routing and map display:<br />
# When planning a route, major roads will sometimes get priority over smaller roads.<br />
#* For longer routes, some lower road types will often be ignored outright in favor of higher-type roads.<br />
#* Since freeways are given the highest priority of all, having other high-type roads is necessary to provide viable alternatives to the routing server in case freeways are clogged with traffic.<br />
# When viewing the map, more important roads should appear at the far zoom levels. Without proper types, the zoomed out display can be misleading.<br />
<br />
The {{Freeway}} and {{Ramp}} road types each have their own special rules. The {{Major Highway}}, {{Minor Highway}}, and {{Primary Street}} types are designated using a set of minimum criteria, as explained [[#Highways|below]].<br />
<br />
Occasionally, if deemed necessary for proper routing, a particular road's type may be set higher than as prescribed in these rules. If a road has a '''higher''' type than set forth in these rules, there may be a reason for it. In rare cases, a particular road may require a '''lower''' type than as prescribed in these rules. Contact your regional coordinator before lowering the type of any road past the bounds of the rules.<br />
<br />
Special rules are used to determine the road types of [[Creating and Editing a roundabout#Road type|roundabouts]] and [[At-grade connectors#How to label the connector type|at-grade connectors]].<br />
<br />
Road types do not affect naming. See [[Road Naming (USA)]].<br />
<br />
=== Before editing ===<br />
Be sure that you are completely familiar with the articles on:<br />
* [[Waze Map Editor|The Waze Map Editor]]<br />
* [[Creating and editing road segments]]<br />
* [[Junction Style Guide]]<br />
* [[Creating and Editing a roundabout]]<br />
* [[At-grade connectors]]<br />
<br />
== Public roads ==<br />
Public roads are those who can be driven by anyone. Naturally, they are by far the most important roads on the Waze map.<br />
<br />
<br />
{{mbox | type = warning | text = <div style="font-size:smaller">Public roads are designated by a series of '''minimum criteria'''.<br />
<br />
If a road meets '''any one''' criterion for a type, the road must be '''at least''' that type.<br />
<br />
For example,<br />
* a county highway (Waze: at least primary street) that is classified as a principal arterial (Waze: at least major highway) would be classified in Waze as a {{Major Highway}}.<br />
* a state highway (Waze: at least minor highway) that is classified as a major collector (Waze: at least primary street) would be classified in Waze as a {{Minor Highway}}.<br />
* a locally maintained road (Waze: at least street) that is classified as an other arterial (Waze: at least minor highway) would be classified in Waze as a {{Minor Highway}}.<br />
<br />
If a road meets the criteria for multiple types, the highest of those types must be used, to satisfy every "at least" rule.</div>}}<br />
<br />
<br />
=== Highways [[Image:RoadBlue.png|180px]][[Image:Majorhighwayseg.png |150px]][[Image:RoadYell.png |150px]] ===<br />
<br />
A '''highway''' is an arterial road.<br />
<br />
Highways roads are the backbone of the traffic network. They serve a dual purpose:<br />
*to carry traffic over long distances, from one city to another, and<br />
*to carry traffic from collector roads to freeways, where applicable.<br />
<br />
Several systems of numbered highways exist in the United States:<br />
*the Interstate Highway System<br />
*the United States Numbered Highways<br />
*various [[wikipedia:Numbered_highways_in_the_United_States#State_highways_and_other_similar_systems|State Highway systems]]<br />
*various County (or Parish) Highway systems, in some states<br />
<br />
Waze's definition of "highways" includes all these, but it also includes other roads that are not necessarily a part of any numbered highway system. In other words, think of the dictionary definition of "highway" ("a main road, esp. one connecting major towns or cities") rather than the legal definition of the term.<br />
<br />
Waze distinguishes three classes of highway: {{Freeway}}, {{Major Highway}}, and {{Minor Highway}}.<br />
<br />
<br />
==== Freeway [[Image:RoadBlue.png|180px]] ====<br />
[[Image:RoadPicN.jpg|right|400px]]<br />
<br />
A '''freeway''' is a highway designed for high speed traffic, with fully controlled access over entrance to, and exit from, the highway.<br />
<br />
Freeway is the highest functional class of road.<br />
<br />
<br />
The following roads shall be classified as {{Freeway}}:<br />
*All '''Interstate Highways'''.<br />
**This includes all roads classified in FHWA's functional classification as '''Interstates'''.<br />
**This includes three-digit Interstate spurs and loops (e.g., I-610; I-585).<br />
**This includes the [[wikipedia:List of gaps in Interstate Highways#At-grade intersections and traffic lights|few grade-intersected, undivided, and/or narrow portions of the Interstate Highway System]].<br />
**This does ''not'' include Interstate Business Loops and Business Spurs (e.g., I-69 Business Loop), unless they meet the standards for Other Freeways and Expressways defined below.<br />
*Roads classified in FHWA's functional classification as '''Other Freeways and Expressways''' which meet the criteria of a [[wikipedia:controlled-access highway|controlled-access highway]]:<br />
**No at-grade crossings.<br />
**No at-grade intersections.<br />
**No direct property access.<br />
**No stop lights (except sometimes on ramps).<br />
**No stop signs.<br />
**Except at the beginning or end of the controlled-access roadway, connected to other roads exclusively by [[Limited Access Interchange Style Guide|interchanges]]:<br />
***Entrance via ramps only, typically with acceleration zones.<br />
***Exit via ramps only, typically with deceleration zones.<br />
***Note: Many freeways continue as non-controlled-access roadways; the road should be set as Freeway until the point at which access becomes non-controlled.<br />
**Note: Some states refer to this class as '''Other Freeways'''. In these states, every road in this class is a Freeway.<br />
<br />
For information on how to best layout freeways and their junctions, please review the section on [[Junction_Style_Guide#Highway.2FFreeway_Junctions|freeways]] in the [[Junction Style Guide]]. For specific guidelines in other countries refer to [[How_to_label_and_name_roads|this page for more information]].<br />
<br />
====Major Highway[[Image:Majorhighwayseg.png |200px]]====<br />
[[Image:Maj-hwy.jpg|thumb|right|450px|A partially-limited-access roadway, or "expressway". Note the interchange to the left and the at-grade intersection to the right.]]<br />
<br />
'''Principal arterials''' are the primary routes for traveling throughout the country, from one city to another, over long distances. Many principal arterials are freeways or expressways, but many others are not.<br />
<br />
As a nationwide system, the United States Numbered Highways, or '''U.S. Highways''', system provides a direct links between regions not served by the Interstate Highway System, and as alternatives to Interstate travel in the case of heavy traffic or incident.<br />
<br />
<br />
The following roads are to be classified, at minimum, as {{Major Highway}}:<br />
*Roads classified in FHWA's functional classification as '''Principal Arterials''' or '''Other Principal Arterials'''.<br />
*Roads classified in FHWA's functional classifications as '''Other Freeways and Expressways''' ''which do not meet the criteria for Freeway''.<br />
**This includes partially-limited-access roadways (or "expressways"). These are roads that have a lot of the characteristics of freeways, but also have occasional at-grade intersections with other roads.<br />
**Note: Every partially-limited-access roadway is a Major Highway; this does not mean that every Major Highway must be partially-limited-access.<br />
**Note: "Expressway" is used as a shorthand term for partially-limited-access roads. This does not mean every road ''named'' "Expressway" is a Major Highway.<br />
**Note: Some states refer to this class as '''Other Freeways'''. In these states, every road in this class is a Freeway.<br />
*Roads in the '''United States Numbered Highways''' system (US Highways).<br />
**This includes Alternate (ALT), Bypass (BYP), Connector (CONN), Truck, and Scenic US Highways.<br />
**This does ''not'' include Business, Spur, and Loop US Highways.<br />
*Business routes (Spurs and Loops) in the Interstate Highway System (e.g., I-69 Business Loop).<br />
<br />
====Minor Highway[[Image:RoadYell.png |200px]]====<br />
<br />
'''Minor arterials''' (or '''other arterials''') are secondary routes for traveling between cities over moderately long distances. Minor or other arterials are classified in Waze as Minor Highways.<br />
<br />
Each of the fifty states (along with the District of Columbia and some of the United States's overseas territories) has a numbered '''state highway system'''. Roads in these systems are designated and selected by their respective State Departments of Transportation as part of statewide networks of important travel links between cities and communities of those states. These roads, while of lesser national importance, are nevertheless essential for travel within the state.<br />
<br />
<br />
The following roads are to be classified, at minimum, as {{Minor Highway}}:<br />
*Roads classified in FHWA's functional classification as '''Minor Arterials''' or '''Other Arterials'''.<br />
*Signed, numbered routes in '''state, D.C., and territorial highway systems'''.<br />
**This includes Alternate (ALT), Bypass (BYP), Connector (CONN), Truck, and Scenic state highways.<br />
**This includes Spur state highways when they are used to connect state highways with other state highways, US Highways, or Interstates; i.e., Spur highways which are used like Connector (CONN) highways.<br />
**This does ''not'' include Business (BUS), Loop, and other Spur state highways.<br />
*Business (BUS), Loop, and Spur US Highways.<br />
<br />
Note: Not every state highway system is the same. Some state systems may be overinclusive, whether because of differing standards or because of political corruption and pork barrel spending; as such, your state may make exceptions where some lesser state highways are better represented by the Primary Street type. Contact your regional coordinator before making these decisions.<br />
<br />
<br />
==== Ramps [[File:Ramp.png|200px|Ramp.png]] ====<br />
<br />
[[File:RoadPicN2.jpg|right|300px|RoadPicN2.jpg]] [[File:HBlue.png|right|300px|HBlue.png]]<br />
<br />
The following are to be classified as {{Ramp}}.<br />
<br />
*Roads which connect roadways to other roadways as part of an [[Limited Access Interchange Style Guide|interchange]]. This includes all freeway exits and entrances.<br />
*Roads connecting freeways and highways with [[Rest areas]], parking areas, and service plazas (e.g., "Exit to Service Area").<br />
*Jughandles.<br />
*Median U-turn Intersection (MUTI) and "Michigan left" segments.<br />
*J-turn (RCUT/"Superstreet") segments.<br />
*Displaced Left Turn (DLT) left turn segments.<br />
<br />
The following are '''not''' to be classified as {{Ramp}}.<br />
<br />
*[[At-grade connectors]], unless they fit into one of the exceptions (see article).<br />
*Turn lanes.<br />
<br />
Ramp names do not appear on the client application map, but do appear in the text for routing directions. Entrance and exit ramps often contain a lot of text which is duplicative of roads already in the area, so this text is suppressed until the user actually needs it. This is also the reason for using the ramp type for named MUTI and jughandle segments—the text is needed for effective navigation instructions but would needlessly clutter the ramp.<br />
<br />
Information on how to lay out ramps and set the proper angles from the main road can be found in the [[Junction Style Guide]]. {{clear}}<br />
<br />
===Streets[[Image:Primary street.png|150px]][[Image:Street.png|150px]][[Image:Service road.png|150px]]===<br />
<br />
The Street types are for local and short-distance travel. Street types are used at the beginning and end of long routes as well.<br />
<br />
<br />
====Primary Street [[Image:Primary street.png|200px]]====<br />
<br />
'''Collectors''' are roads used with medium-low traffic densities which are used to bring traffic from local streets to arterials and vice versa. Collectors are classified in Waze as Primary Streets.<br />
<br />
Some states designate [[wikipedia:County highway|county routes]] which are important for travel within a county. These routes serve important functions in a short-distance capacity.<br />
<br />
<br />
The following roads are to be classified, at minimum, as {{Primary Street}}:<br />
*Roads classified in FHWA's functional classification as '''Major Collectors''' or '''Minor Collectors''' and paved with a hard surface.<br />
*Signed, numbered '''county routes''' (and, in Louisiana, parish routes) paved with a hard surface.<br />
*Business (BUS) and Loop state highways, and Spur state highways which are not used as connectors, paved with a hard surface.<br />
*'''[[wikipedia:Frontage road|Frontage road]]s''' which serve as the means of access between freeways/expressways and surface streets, if not otherwise classified.<br />
**Some functional classification maps are not produced in high enough detail to determine the class of frontage roads. On maps that are produced in high detail, frontage roads are almost universally classified as Major Collectors or higher.<br />
<br />
<br />
Unpaved roads – including gravel, macadam, and dirt roads – are considered on a regional basis. Check your [[Mapping resources/USA|state page]] or contact your regional coordinator.<br />
<br />
Note: Some states or counties may designate county routes differently than others. Check your state's page for possible exceptions to this rule.<br />
{{clear}}<br />
<br />
<br />
As stated above, [[wikipedia:Frontage road|frontage road]]s should generally be set to at least {{Primary Street}}, if not marked as a higher type on a functional class map.<br />
<br />
Many frontage roads are used as "feeder roads" or "access roads", often the primary or only means of entering and exiting a freeway. Setting these to the "street" type, as has been done in the past, has the potential to invalidate good routes which use freeways and major/minor highways. To ensure that routing works, always use at least "primary street" for frontage roads that are used in this way. It may be desirable to set the entire frontage road to the same type to achieve a more contiguous map appearance.<br />
{{clear}}<br />
<br />
<br />
====Street [[Image:Street.png|200px]]====<br />
[[Image:RoadPicN4.jpg|right|400px]]<br />
<br />
*Any road for public travel which does not meet the criteria for any other type shall be classified as a {{Street}}. Shown as "local roads" in some functional classification maps; not shown at all in others.<br />
{{clear}}<br />
<br />
<br />
====Service Road [[Image:Service road.png|200px]]====<br />
<br />
{{mbox<br />
| type = warning<br />
| text = The Service Road type is deprecated. '''Do not use the Service Road type for any purpose.'''<br />
}}<br />
{{clear}}<br />
<br />
=== {{Anchor|FC cross reference}}Quick reference chart ===<br />
<br />
Refer to this chart to determine the road type of a given paved public road based on the functional class.<br />
<br />
To use this chart, first determine the functional class of a road, and whether it is a signed, numbered highway in a particular highway system.<br />
<br />
Where the column for the road's highway system and the row for the road's functional class meet, you will find the proper road type for that particular road.<br />
<br />
A number of examples are given below the chart.<br />
<br />
<br />
<div style="font-size:smaller"><br />
{| border="1" style="border-collapse:collapse; text-align:center"<br />
! scope="row" rowspan="2" colspan="2"| <br />
! colspan="8"| <big>Highway Systems</big><br />
|-<br />
! Interstate<br />
! Interstate Business Loop/Spur<br />
! US Hwy (incl. some [[wikipedia:special routes|special routes]])<br />
! US Hwy BUS, SPUR, LOOP<br />
! State Hwy (incl. some special routes)<br />
! State Hwy BUS, SPUR{{ref label|a|a}}, LOOP<br />
! County Route<br />
! Locally-maintained<br />
|-<br />
|<br />
| ''example''<br />
| I-10 E<br />
| I-94 Business<br />
| US-190<br />
| US-460 Business<br />
| SR-23<br />
| SR-400 Loop<br />
| CR-15<br />
| Robertson St<br />
|- <br />
! scope="row" rowspan="8" style="width:28px"| <big>F<br>u<br>n<br>c<br>t<br>i<br>o<br>n<br>a<br>l<br> <br>C<br>l<br>a<br>s<br>s</big><!-- Temp placeholder --><br />
| '''Interstate'''{{ref label|b|b}}||{{Freeway|Fw}}||n/a||n/a||n/a||n/a||n/a||n/a||n/a<br />
|- <br />
| '''Other Freeway'''{{ref label|c|c}}||n/a||{{Freeway|Fw}}||{{Freeway|Fw}}||{{Freeway|Fw}}||{{Freeway|Fw}}||{{Freeway|Fw}}||{{Freeway|Fw}}||{{Freeway|Fw}}<br />
|- <br />
| '''Other Expressway'''{{ref label|d|d}}||n/a||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Major Highway|Major}}<br />
|- <br />
| '''Other Principal Arterial'''{{ref label|e|e}}||n/a||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Major Highway|Major}}<br />
|- <br />
| '''Minor Arterial'''{{ref label|f|f}}||n/a||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Minor Highway|Minor}}||{{Minor Highway|Minor}}||{{Minor Highway|Minor}}||{{Minor Highway|Minor}}||{{Minor Highway|Minor}}<br />
|- <br />
| '''Major Collector'''||n/a||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Minor Highway|Minor}}||{{Minor Highway|Minor}}||{{Primary Street|PS}}||{{Primary Street|PS}}||{{Primary Street|PS}}<br />
|- <br />
| '''Minor Collector'''||n/a||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Minor Highway|Minor}}||{{Minor Highway|Minor}}||{{Primary Street|PS}}||{{Primary Street|PS}}||{{Primary Street|PS}}<br />
|- <br />
| '''Local/not mapped'''||n/a||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Minor Highway|Minor}}||{{Minor Highway|Minor}}||{{Primary Street|PS}}||{{Primary Street|PS}}||{{Street}}<br />
|}<br />
{{note|a|a}} When a state highway "SPUR" route is used to connect a state highway with another state highway, a US highway, or an Interstate (i.e., when it is used as a connector/CONN route), use the first state highway column.<br />
<br />
{{note|b|b}} Also known as '''Principal Arterial - Interstate'''.<br />
<br />
{{note|c|c}} Also known as '''Principal Arterial - Freeway'''.<br />
<br />
{{note|d|d}} Also known as '''Principal Arterial - Expressway'''.<br />
<br />
{{note|e|e}} Also known as '''Principal Arterial'''.<br />
<br />
{{note|f|f}} Also known as '''Other Arterial'''.<br />
<br />
<br />
For example,<br />
* An Interstate Business Loop classified as a Minor Arterial is a {{Major Highway}}.<br />
* A US Highway classified as a Minor Arterial is a {{Major Highway}}.<br />
* A US Highway Spur route classified as a Minor Arterial is a {{Minor Highway}}.<br />
* A State Highway classified as an Other Freeway is a {{Freeway}}.<br />
* A State Highway classified as a Collector is a {{Minor Highway}}.<br />
* A County Route classified as a Minor Arterial is a {{Minor Highway}}.<br />
* A County Route classified as a Collector is a {{Primary Street}}<br />
* A locally-maintained road classified as an Other Principal Arterial is a {{Major Highway}}.<br />
* A locally-maintained road classified as a Collector is a {{Primary Street}}.<br />
<br />
<br />
{| border="1" style="border-collapse:collapse;margin: 1em auto 1em auto; text-align:center"<br />
|+ '''Legend'''<br />
|- <br />
| {{Freeway|Fw}}||{{Freeway}}<br />
|-<br />
| {{Major Highway|Major}}||{{Major Highway}}<br />
|- <br />
| {{Minor Highway|Minor}}||{{Minor Highway}}<br />
|- <br />
| {{Primary Street|PS}}||{{Primary Street}}<br />
|-<br />
| {{Street|Street}}||{{Street}}<br />
|}<br />
</div><br />
<br />
== Other drivable roads ==<br />
<br />
<br />
=== {{anchor|Dirt}}Dirt Road / 4X4 Trail[[File:Service road.png|200px|Service road.png]] ===<br />
<br />
[[File:RoadPicN6.jpg|right|300px|RoadPicN6.jpg]]<br />
<br />
Generally, a road that is not paved.<br />
<br />
Roads of the "Dirt Road / 4X4 Trail" type will not be used if the user has selected the "Don't allow" option in the client, and segments longer than 300m will be avoided if the user has selected "Avoid long ones".<br />
<br />
In some areas of the country, improved unpaved roads (gravel, macadam, etc.) are set to this type. In other areas, improved unpaved roads, and possibly certain dirt roads, will be set to other types, as if they were paved. Check your [[Mapping resources/USA|state page]] or contact your regional coordinator for further guidance. {{clear}}<br />
<br />
=== Parking Lot Road[[File:Service road.png|200px|Service road.png]] ===<br />
<br />
[[File:RoadPicN7.jpg|right|300px|RoadPicN7.jpg]] Parking lots, along with other publicly accessible roads such as '''alleys''' that should not be used for traffic routing unless directly at the start or end point of a route.<br />
<br />
*Do not map the rows within parking lots because it clutters the map. See this additional page for [[Best map editing practice#Parking Lots|more details on how to map parking lots]].<br />
<br />
{{mbox|type=caution|text=This section was updated {{As of |2015|01|14|df=us|lc=yes}} to clarify when to use PLR vs Private Roads.}}<br />
<br />
*Use Parking Lot road type for all [[Best map editing practice#Parking Lots|necessary segments]] in the Parking Lot.<br />
*Parking Lot road type should be used inside Apartment Complexes, Trailer Parks, Schools, and Universities unless it meets the criteria for Private Road found in the next section below.<br />
*Parking Lot roads have a [[Routing penalties|transition penalty]] when exiting the Parking Lot road segment. This should prevent Waze from routing you through a Parking Lot or an alley as a shortcut.<br />
*The proper use of parking lot roads can also help to avoid automated traffic jam reports as well as Map Problems related to Wazers driving in unmapped parking lots. Draw in the drivable portions of the parking lot that are near streets and other roadways. This will prevent the Waze routing server from assuming you must be on the main road when in fact you are stopped in the parking lot.<br />
<br />
[http://www.waze.com/forum/viewtopic.php?f=10&t=13825&start=20#p117202 Additional information on this topic can be reviewed in the forums.] {{clear}}<br />
<br />
Information on mapping a parking lot landmark "place" is covered [[Places#Parking Lot|here]].<br />
<br />
=== Private Road[[File:Service road.png|200px|Service road.png]] ===<br />
<br />
[[File:Pi gated-community1.jpg|right|300px|Pi gated-community1.jpg]]Private roads are useful for the following situations:<br />
<br />
*Gated communities with controlled access<br />
*Schools and Universities (gates / guard)<br />
*Businesses with controlled access (gates / guard)<br />
<br />
However, using private roads in some of these situations may require more complex mapping as covered in the article [[Private Installations]]. Be sure to read through that article before setting a whole neighborhood to all private roads.<br />
<br />
As with Parking-Lot Roads, a route over a Private Road will incur a [[Routing penalties|transition penalty]] upon leaving it for another road type. This transition penalty keeps Waze from routing Wazers through a private area as a shortcut. Unlike Parking-Lot Roads, however, Private Roads do not suppress automated traffic-jam detection. <br />
<br />
{{As of|2014|8}} the Waze client displays Private Roads identically to public roads. Since this may change in future releases, never use the Private Road type for unrestricted public roads. Do not use the Private Road type as a workaround to force Waze to avoid slow public roads, for example those with rough patches or construction. In special cases, however, the Private Road type may be used for a public street that is legally and enforceably signed for local traffic only.<br />
{{clear}}<br />
<br />
== Non-drivable roads ==<br />
<br />
'''Your car should not be here!'''<br />
<br />
*These may be useful for points of reference when navigating such as seeing on a map where a turn is in relation to a railroad crossing.<br />
*When Waze users travel on a non-vehicle route such as a bicyclist or mass-transit rider, marking these routes can be useful to explain the GPS traces that result.<br />
*If a base map scan has non-drivable routes on it, it is important to mark these to prevent traffic routing onto them.<br />
*Non-drivable road type of Walking Trail, Pedestrian Boardwalk, Stairway and Runway/Taxiway should '''not have any type of junction with a drivable road'''. Because of the way the routing engine uses a [[Routing penalties|penalty system]], Waze '''will''' route users to drive on these "Non-drivable" road types if they are connected to drivable roads. When crossing a drivable road, the non-drivable road should be bridged across without a junction between them and set at a different Elevation.<br />
* ''It is OK to junction drivable roads with the Railroad type.'' See specific details in the Railroad section later on this page.<br />
*{{Red|Walking Trails, and other non-drivable road type which are visible in the app, can cause significant routing issues.}} If a walking trail (even when not connected to any other drivable segment) is closest to the latitude and longitude of the search result, the routing server will route you to the spot on the segment closest to that walking trail.<br/><br/>In the sketch below, if you assume the Place target is a latitude and longitude returned by a Google search result, you would think that the actual destination would be the parking lot segment because it is the closest reachable/connected segment to the target. But it won't be. The actual destination will be where the green spot is, because the closest segment to the latitude and longitude is the walking trail, and the closest Waze can route to the walking trail is to where the green spot is.<br />
<br />
[[File:Walking trail dest.png|center|Walking trail dest.png]]<br />
<br />
{{clear}}<br />
<br />
<br />
<br />
=== Emergency Vehicle and DOT Service Roads [[File:Service road.png|200px|Service road.png]] ===<br />
<br />
[[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. 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}}<br />
<br />
=== Walking Trails [[File:Service road.png|200px|Service road.png]] ===<br />
<br />
[[File:RoadPicN9.jpg|right|300px|RoadPicN9.jpg]] Also bike trails. These have an ability to alter routing as discussed above, so be cautious when and where they are mapped. {{clear}}<br />
<br />
<br />
<br />
=== Pedestrian Boardwalks [[File:Service road.png|200px|Service road.png]] ===<br />
<br />
[[File:RoadPicN10.jpg|right|300px|RoadPicN10.jpg]] {{clear}}<br />
<br />
<br />
<br />
=== Stairway [[File:Service road.png|200px|Service road.png]] ===<br />
<br />
[[File:RoadPicN11.jpg|right|300px|RoadPicN11.jpg]] {{clear}}<br />
<br />
<br />
<br />
=== Railroad [[File:Service road.png|200px|Service road.png]] ===<br />
<br />
[[File:RailroadTracksVanishingPoint.jpg|right|300px|RoadPicN11.jpg]]<br />
The "Railroad" road type serves two purposes in Waze. First, it provides drivers with visual orientation relative to railroad and light-rail tracks. More importantly, in the common case where passenger-carrying tracks lie parallel with roads, 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.{{clear}}<br />
<br />
{{mbox<br />
| type = important<br />
| text = The guidelines below which allow junctioning of railroads to drivable segments is new as of October 24, 2014.<br />
#There is no need to make mass railroad changes immediately.<br />
#Railroad junctions are expected to be made gradually over time. <br />
#There is to be no massive railroad updating project.<br />
}}<br />
<br />
<br />
Use the following guidelines when '''mapping''' railroad segments:<br />
* By default, enter "Railroad" for the street name of every railroad segment. (See more below on Naming railroad segments.)<br />
* Always select "None" for the city name. This avoids [[City smudge|city smudging]].<br />
* Lock the segment at L2.<br />
* Set the elevation just as you would a drivable segment. When tracks junction a road on the ground, the Elevation should be set to Ground.<br />
* Create junctions between drivable roads and railroads.{{ref label|rr|rr}}<br />
* Set railroad to 2-way directionality<br />
* Restrict turns ''to and from'' the railroad segments.<br />
* When mapping railroad tracks, focus on those near drivable roads.<br />
* Map rail yards simply, with one railroad segment along either edge of the yard's tracks.<br />
* Map industrial spurs only if they cross drivable roads.<br />
* 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.<br />
* Multiple parallel lines at crossings:<br />
** At most crossings, there should be only one railroad segment mapped and no more than two parallel railroads mapped at any crossing.<br />
** Parallel lines are to be at least 5m apart<br />
** In general, there is no reason to have multiple lines mapped. When not at a crossing, even four parallel lines can be easily mapped as a single railroad segment in Waze.<br />
* Keep segment lengths under 10,000 meters – the longer the segment length, the more sluggish the editor is to respond to changes.<br />
* {{Red|Do not map railroads using a drivable road type}} (streets, primary streets, etc.); it could be a hazard to human life if drivers were routed to them.<br />
<br />
<small>{{note|rr|rr}} ''Note: The routing server will properly account for delays at railroad crossings through a segment without a junction. However, with a junction, the historical data for the rail crossing will be more accurate.''</small><br />
<br />
<br />
Use the following guidelines when '''naming''' railroad segments:<br />
* For commercially-controlled right-of-ways, rather than apply the default "Railroad" name, you may optionally use the owner's full legal name spelled out without acronyms or abbreviations (e.g. "New Orleans Public Belt Railroad"). Some owners' names incorporate what appear to be or once were acronyms but are actually part of the legal name (e.g., "BNSF Railway", "CSX Railroad").<br />
** In case of uncertain ownership, do not guess. Use the default "Railroad" name.<br />
** Do not name a railroad segment for a passenger operator that uses it, regardless of how many passengers or how little freight it may carry, unless you are absolutely certain that the passenger operator owns the track. For example, do not name a segment "Amtrak" unless Amtrak actually owns the track ([http://en.wikipedia.org/wiki/Amtrak#Trains_and_tracks it usually does not], except in the [http://en.wikipedia.org/wiki/Northeast_Corridor|Northeast Corridor] and in a few other areas).<br />
** Do not apply "fallen flags" (former owners that no longer exist due to bankruptcy or merger) in the alternate field.<br />
** Keep in mind that should the name of the owner change, due to bankruptcy, merger, or other business decision, you or another editor will need to come back and fix all now-incorrect segments. Railroads can change names often; for example, BNSF Railway has been known by that name only since 2005, and its previous name was in use for only eight years. <br />
* For urban rapid transit and light rail systems, rather than apply the default "Railroad" name, you may optionally use the name of the transit authority and the name of the line, separated by a hyphen (e.g., "MBTA - Green Line", "RTA - Riverfront Streetcar").<br />
** If a system has only one line, of course, use its name alone (e.g., "Detroit People Mover").<br />
** If multiple lines share the same track or run on parallel tracks, include all lines (e.g., "Metro Rail - Red/Purple Lines").<br />
** However, if a rapid transit system is so complex that including all line names would lead to an absurd result on some railroad segments, use the name of the system alone (e.g., "BART", "MTA") throughout the system.<br />
* Federal DOT Railroad GIS: http://fragis.fra.dot.gov/Apps/GISFRASafety/<br />
<br />
<br />
<br />
'''Waze - Support'''<br />
<br />
'''Railroads should be labeled as such in the editor. For the time being they won't make it to the client indeed, but in the future we might want to use them for display purposes.'''<br />
<br />
'''The "railroad" road type in the editor is under "non drivable" so it should not cause any issue to the routing.'''<br />
<br />
For specific recommendations in other countries outside the United States, please see the [[Road types and names|entry for the country in question here]]. {{clear}}<br />
<br />
=== Runway/Taxiway[[File:Service road.png|200px|Service road.png]] ===<br />
<br />
Airport runways and private airstrips may be mapped using the Runway/Taxiway road type. The Runway/Taxiway type is for display only and must never connect to drivable road segments. If a drivable road and a runway cross, set the [[elevation]] of the road below that of the runway and ensure there is no connection. Draw each runway as a single segment and lock it to prevent lower-ranking editors from attaching a road. Do not form junctions where runways cross each other.<br />
<br />
Name each runway using the airport identifier, the word ''Runway'', and the runway designations with the lower number first (e.g., "SMF Runway 16R-34L".) The preferred airport identifier is the [http://en.wikipedia.org/wiki/International_Air_Transport_Association_airport_code IATA] [http://en.wikipedia.org/wiki/List_of_airports 3-letter code], for example "SFO", "LAX", "JFK", etc. If the airport in question is not included in that list, use the [http://en.wikipedia.org/wiki/International_Civil_Aviation_Organization_airport_code ICAO] [http://en.wikipedia.org/wiki/International_Civil_Aviation_Organization_airport_code#Prefixes 4-letter code] instead. If the airport is not included in that list use the [http://www.faa.gov/air_traffic/publications/atpubs/lid/lidhme.htm FAA identifier]. For the "City" field of runway segments, check "None" to avoid any chance of [[City smudge|city smudging]]. {{clear}} <br />
<br />
[[File:Fly-inCommunity.png|right|250px]]<br />
Despite its title, the Runway/Taxiway road type should never be used for an aircraft taxiway because it would render the same as a runway and confuse the display. Taxiways not intended for frequent access by street vehicles should not be mapped at all with any road type. Taxiways that commonly serve street vehicles as well as aircraft, for example at [http://www.waze.com/editor/?zoom=5&lat=38.68054&lon=-120.98836&env=usa&layers=389 fly-in communities], may be mapped as Streets provided they remain disconnected from any runway.<br />
{{clear}}<br />
<br />
=== Ferry [[File:Service road.png|200px|Service road.png]] ===<br />
<br />
{{mbox<br />
| type = warning<br />
| 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.<br />
}}<br />
{{clear}}<br />
<br />
== Roundabouts [[Image:Round.png |50px]] ==<br />
{{clear}}<br />
[[Image:RoadPicN8.jpg |right|300px]] <br />
<br />
Roundabouts have few principals:<br />
<br />
The first one, each node on the roundabout can only be connected to no more than one segment.<br />
<br />
Each connection has a spectrum that exists in order to notify the Client on how to define the message (Go straight, exit through the 2nd / 3rd / 4th exit).<br />
{{clear}}<br />
<br />
[[Image:Round2.png |right|200px]]<br />
<br />
The system will include the radius border from the center and notify the user accordingly.<br />
<br />
For more information on when to create a Roundabout or a loop instead, please review the [[Junction Style Guide]].<br/><br />
For information on what type of road to set a Roundabout to, please review [[Creating_and_Editing_a_roundabout#Road_Type|Creating and Editing a Roundabout]]<br />
{{clear}}<br />
<br />
<br />
== Special case roads not covered ==<br />
There are a number of other types of roadways and lane types which are not directly covered with the current options above. In some cases there are plans to add some of these special cases, but in the mean time the following guidelines are the best that can be done with the current settings.<br />
<br />
<br />
=== Bus or cab only lanes ===<br />
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.<br />
<br />
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.<br />
<br />
<br />
=== Driveways ===<br />
Most urban communities have very short driveways between the named road they live on and the garage or carport on their property. In general these very short segments should not be mapped because they have no name, would clutter the map in the client app, take a lot of time to draw, and would greatly increase the overall size of the Waze mapping database with very little return.<br />
<br />
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.<br />
<br />
== See Also ==<br />
[[Road names/USA]]<br><br />
[[Junction Style Guide]]<br><br />
[[How to label and name roads (United Kingdom)]]<br><br />
<br />
[[Category:USA]]<br />
[[Category:Review redirects]]<br />
[[Category:Style Guides]]</div>DallasGranthttps://www.waze.com/wiki/USA/index.php?title=Minnesota/Special_roads/Main&diff=99510Minnesota/Special roads/Main2015-03-15T01:53:27Z<p>DallasGrant: /* Parking Lot Road200px|Service road.png */</p>
<hr />
<div><!-- 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><!--<br />
------ DO NOT MODIFY ABOVE THIS LINE -------- DO NOT MODIFY ABOVE THIS LINE ------> <br />
=== Other drivable roads ===<br />
<br />
==== Dirt Road / 4X4 Trail[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
{{mbox<br />
| type = important<br />
| text = Minnesota has different interpretations of Dirt Roads than many other locations. Even veteran editors need to pay attention to this section!<br />
}}<br />
<br />
<br />
[[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.<br />
<br />
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.<br />
<br />
[[File:Dirtroad.PNG|300px|right]]<br />
<br />
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. <br />
<br />
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.<br />
<br />
==== Parking Lot Road[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:Parklotrhmmn.png|right|300px]]<br />
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.<br />
<br />
* Simple is best. Do not map every lane<br />
* Map the main entrances from the roads outside the parking lot<br />
* Map lanes that run along storefronts<br />
* Map lanes that run along main roads outside the parking area<br />
* Map primary lanes that serve to get people from one area of the lot to another<br />
<br />
For for information about mapping parking lots, follow this [[Best_map_editing_practice#Parking_Lots|article]]<br />
<br />
==== Private Road[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:Pi gated-community1.jpg|right|300px|Pi gated-community1.jpg]]<br />
<br />
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. <br />
<br />
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. <br />
<br />
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.<br />
<br />
==== Alleyways[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
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 Parking Lot class.<br />
<br />
[[File:Pizzalola.png|300px|left]]<br />
<br />
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 parking lot 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.<br />
<br />
==== Roundabouts [[Image:Round.png |50px]] ====<br />
<br />
{{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".<br />
[[File:Roundabouts.png|400px|right]]<br />
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. <br />
<br />
<br />
<br />
[[File:Roundboutmn2.png|400px|left]]<br />
<br />
<br />
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).<br />
<br />
<br />
<br />
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.<br />
<br />
If at all possible, drive through a roundabout after it has been created or updated. Verify that it seems to give correct information.<br />
<br />
=== Non-drivable roads ===<br />
<br />
==== Railroad [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:RailroadTracksVanishingPoint.jpg|right|300px|RoadPicN11.jpg]]<br />
<br />
<br />
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.<br />
<br />
<br />
<br />
<br />
{{mbox<br />
| type = important<br />
| text = Please notice that railroads have changed from previous interpretations of railroad mapping. Even veteran editors need to pay attention to this section!<br />
}}<br />
<br />
<br />
* 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.<br />
* 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.<br />
* Always select "None" for the city name. This avoids [[Smudged_city#Overview|city smudging]].<br />
* Set railroad to 2-way directionality and Restrict turns ''to'' and ''from'' the railroad segments.<br />
* 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. <br />
* 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.<br />
* Canadian Pacific uses the acronym CPRS, but it is more know as CP, so it will be called CP Railroad<br />
*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.<br />
* Lock all railroads to a Level 2<br />
* Read [[Road_types/USA#Railroad|this section]] for more information about railroads.<br />
<br />
==== Runway/Taxiway ====<br />
<br />
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. <br />
<br />
<!---- DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ----<br />
-------------------------------------------------------------------------------------<br />
---- This page is only transcluded into (displayed on) the main page for this state.<br />
---- It directly follows the common guidelines applicable to all states. When this<br />
---- page is present (even if blanked), it displaces any optional code that might be<br />
---- in that section.<br />
---- If the original optional code from the main page for this section is still<br />
---- desired, it can be restored by adding the following code to the first line <br />
---- between the "DO NOT MODIFY" lines on this page:<br />
---- {{:USA/CommonState/Special roads|optional}}<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- If there will be a full page for this section, use code similar to the wording<br />
---- below to provide a hyperlink to that page. When creating the full page, use the<br />
---- link on the talk page to ensure the preload data is provided to help with<br />
---- formatting the page. Don't just use the red link from this section once it is<br />
---- saved.<br />
----<br />
See [[{{BasePage2}}/Special roads]] for guidance in {{RootPage2}} that may not be universal to all other states.<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- This section has three possible purposes:<br />
---- 1. It is only providing a hyperlink to the full page for this section.<br />
---- 2. It is only providing some unique guidance for this state that differs from<br />
---- other states.<br />
---- 3. It is intentionally wiping out the general optional content for this section<br />
---- for this state.<br />
------------------------------------------------------------------------------------></div>DallasGranthttps://www.waze.com/wiki/USA/index.php?title=Minnesota/Special_roads/Main&diff=99507Minnesota/Special roads/Main2015-03-14T23:56:06Z<p>DallasGrant: /* Parking Lot Road200px|Service road.png */</p>
<hr />
<div><!-- 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><!--<br />
------ DO NOT MODIFY ABOVE THIS LINE -------- DO NOT MODIFY ABOVE THIS LINE ------> <br />
=== Other drivable roads ===<br />
<br />
==== Dirt Road / 4X4 Trail[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
{{mbox<br />
| type = important<br />
| text = Minnesota has different interpretations of Dirt Roads than many other locations. Even veteran editors need to pay attention to this section!<br />
}}<br />
<br />
<br />
[[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.<br />
<br />
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.<br />
<br />
[[File:Dirtroad.PNG|300px|right]]<br />
<br />
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. <br />
<br />
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.<br />
<br />
==== Parking Lot Road[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:Parklotrhmmn.png|right|300px]]<br />
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.<br />
<br />
* Simple is best. Do not map every lane<br />
* Map the main entrances from the roads outside the parking lot<br />
* Map lanes that run along storefronts<br />
* Map lanes that run along main roads outside the parking area<br />
* Map primary lanes that serve to get people from one area of the lot to another<br />
<br />
For for information about mapping parking lots, follow this [[Best_map_editing_practice#Parking_Lots|article]]<br />
<br />
==== Private Road[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:Pi gated-community1.jpg|right|300px|Pi gated-community1.jpg]]<br />
<br />
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. <br />
<br />
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. <br />
<br />
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.<br />
<br />
==== Alleyways[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
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 Parking Lot class.<br />
<br />
[[File:Pizzalola.png|300px|left]]<br />
<br />
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 parking lot 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.<br />
<br />
==== Roundabouts [[Image:Round.png |50px]] ====<br />
<br />
{{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".<br />
[[File:Roundabouts.png|400px|right]]<br />
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. <br />
<br />
<br />
<br />
[[File:Roundboutmn2.png|400px|left]]<br />
<br />
<br />
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).<br />
<br />
<br />
<br />
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.<br />
<br />
If at all possible, drive through a roundabout after it has been created or updated. Verify that it seems to give correct information.<br />
<br />
=== Non-drivable roads ===<br />
<br />
==== Railroad [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:RailroadTracksVanishingPoint.jpg|right|300px|RoadPicN11.jpg]]<br />
<br />
<br />
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.<br />
<br />
<br />
<br />
<br />
{{mbox<br />
| type = important<br />
| text = Please notice that railroads have changed from previous interpretations of railroad mapping. Even veteran editors need to pay attention to this section!<br />
}}<br />
<br />
<br />
* 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.<br />
* 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.<br />
* Always select "None" for the city name. This avoids [[Smudged_city#Overview|city smudging]].<br />
* Set railroad to 2-way directionality and Restrict turns ''to'' and ''from'' the railroad segments.<br />
* 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. <br />
* 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.<br />
* Canadian Pacific uses the acronym CPRS, but it is more know as CP, so it will be called CP Railroad<br />
*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.<br />
* Lock all railroads to a Level 2<br />
* Read [[Road_types/USA#Railroad|this section]] for more information about railroads.<br />
<br />
==== Runway/Taxiway ====<br />
<br />
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. <br />
<br />
<!---- DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ----<br />
-------------------------------------------------------------------------------------<br />
---- This page is only transcluded into (displayed on) the main page for this state.<br />
---- It directly follows the common guidelines applicable to all states. When this<br />
---- page is present (even if blanked), it displaces any optional code that might be<br />
---- in that section.<br />
---- If the original optional code from the main page for this section is still<br />
---- desired, it can be restored by adding the following code to the first line <br />
---- between the "DO NOT MODIFY" lines on this page:<br />
---- {{:USA/CommonState/Special roads|optional}}<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- If there will be a full page for this section, use code similar to the wording<br />
---- below to provide a hyperlink to that page. When creating the full page, use the<br />
---- link on the talk page to ensure the preload data is provided to help with<br />
---- formatting the page. Don't just use the red link from this section once it is<br />
---- saved.<br />
----<br />
See [[{{BasePage2}}/Special roads]] for guidance in {{RootPage2}} that may not be universal to all other states.<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- This section has three possible purposes:<br />
---- 1. It is only providing a hyperlink to the full page for this section.<br />
---- 2. It is only providing some unique guidance for this state that differs from<br />
---- other states.<br />
---- 3. It is intentionally wiping out the general optional content for this section<br />
---- for this state.<br />
------------------------------------------------------------------------------------></div>DallasGranthttps://www.waze.com/wiki/USA/index.php?title=File:Parklotrhmmn.png&diff=99502File:Parklotrhmmn.png2015-03-14T23:42:13Z<p>DallasGrant: </p>
<hr />
<div></div>DallasGranthttps://www.waze.com/wiki/USA/index.php?title=Minnesota/Special_roads/Main&diff=99472Minnesota/Special roads/Main2015-03-14T20:04:11Z<p>DallasGrant: /* Parking Lot Road200px|Service road.png */</p>
<hr />
<div><!-- 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><!--<br />
------ DO NOT MODIFY ABOVE THIS LINE -------- DO NOT MODIFY ABOVE THIS LINE ------> <br />
=== Other drivable roads ===<br />
<br />
==== Dirt Road / 4X4 Trail[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
{{mbox<br />
| type = important<br />
| text = Minnesota has different interpretations of Dirt Roads than many other locations. Even veteran editors need to pay attention to this section!<br />
}}<br />
<br />
<br />
[[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.<br />
<br />
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.<br />
<br />
[[File:Dirtroad.PNG|300px|right]]<br />
<br />
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. <br />
<br />
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.<br />
<br />
==== Parking Lot Road[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:RoadPicN7.jpg|right|300px|RoadPicN7.jpg]]<br />
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.<br />
<br />
* Simple is best.<br />
<br />
==== Private Road[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:Pi gated-community1.jpg|right|300px|Pi gated-community1.jpg]]<br />
<br />
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. <br />
<br />
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. <br />
<br />
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.<br />
<br />
==== Alleyways[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
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 Parking Lot class.<br />
<br />
[[File:Pizzalola.png|300px|left]]<br />
<br />
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 parking lot 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.<br />
<br />
==== Roundabouts [[Image:Round.png |50px]] ====<br />
<br />
{{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".<br />
[[File:Roundabouts.png|400px|right]]<br />
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. <br />
<br />
<br />
<br />
[[File:Roundboutmn2.png|400px|left]]<br />
<br />
<br />
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).<br />
<br />
<br />
<br />
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.<br />
<br />
If at all possible, drive through a roundabout after it has been created or updated. Verify that it seems to give correct information.<br />
<br />
=== Non-drivable roads ===<br />
<br />
==== Railroad [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:RailroadTracksVanishingPoint.jpg|right|300px|RoadPicN11.jpg]]<br />
<br />
<br />
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.<br />
<br />
<br />
<br />
<br />
{{mbox<br />
| type = important<br />
| text = Please notice that railroads have changed from previous interpretations of railroad mapping. Even veteran editors need to pay attention to this section!<br />
}}<br />
<br />
<br />
* 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.<br />
* 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.<br />
* Always select "None" for the city name. This avoids [[Smudged_city#Overview|city smudging]].<br />
* Set railroad to 2-way directionality and Restrict turns ''to'' and ''from'' the railroad segments.<br />
* 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. <br />
* 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.<br />
* Canadian Pacific uses the acronym CPRS, but it is more know as CP, so it will be called CP Railroad<br />
*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.<br />
* Lock all railroads to a Level 2<br />
* Read [[Road_types/USA#Railroad|this section]] for more information about railroads.<br />
<br />
==== Runway/Taxiway ====<br />
<br />
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. <br />
<br />
<!---- DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ----<br />
-------------------------------------------------------------------------------------<br />
---- This page is only transcluded into (displayed on) the main page for this state.<br />
---- It directly follows the common guidelines applicable to all states. When this<br />
---- page is present (even if blanked), it displaces any optional code that might be<br />
---- in that section.<br />
---- If the original optional code from the main page for this section is still<br />
---- desired, it can be restored by adding the following code to the first line <br />
---- between the "DO NOT MODIFY" lines on this page:<br />
---- {{:USA/CommonState/Special roads|optional}}<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- If there will be a full page for this section, use code similar to the wording<br />
---- below to provide a hyperlink to that page. When creating the full page, use the<br />
---- link on the talk page to ensure the preload data is provided to help with<br />
---- formatting the page. Don't just use the red link from this section once it is<br />
---- saved.<br />
----<br />
See [[{{BasePage2}}/Special roads]] for guidance in {{RootPage2}} that may not be universal to all other states.<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- This section has three possible purposes:<br />
---- 1. It is only providing a hyperlink to the full page for this section.<br />
---- 2. It is only providing some unique guidance for this state that differs from<br />
---- other states.<br />
---- 3. It is intentionally wiping out the general optional content for this section<br />
---- for this state.<br />
------------------------------------------------------------------------------------></div>DallasGranthttps://www.waze.com/wiki/USA/index.php?title=Minnesota/Special_roads/Main&diff=99471Minnesota/Special roads/Main2015-03-14T19:53:58Z<p>DallasGrant: </p>
<hr />
<div><!-- 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><!--<br />
------ DO NOT MODIFY ABOVE THIS LINE -------- DO NOT MODIFY ABOVE THIS LINE ------> <br />
=== Other drivable roads ===<br />
<br />
==== Dirt Road / 4X4 Trail[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
{{mbox<br />
| type = important<br />
| text = Minnesota has different interpretations of Dirt Roads than many other locations. Even veteran editors need to pay attention to this section!<br />
}}<br />
<br />
<br />
[[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.<br />
<br />
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.<br />
<br />
[[File:Dirtroad.PNG|300px|right]]<br />
<br />
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. <br />
<br />
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.<br />
<br />
==== Parking Lot Road[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:RoadPicN7.jpg|right|300px|RoadPicN7.jpg]]<br />
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.<br />
<br />
* <br />
<br />
<br />
<br />
==== Private Road[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:Pi gated-community1.jpg|right|300px|Pi gated-community1.jpg]]<br />
<br />
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. <br />
<br />
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. <br />
<br />
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.<br />
<br />
==== Alleyways[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
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 Parking Lot class.<br />
<br />
[[File:Pizzalola.png|300px|left]]<br />
<br />
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 parking lot 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.<br />
<br />
==== Roundabouts [[Image:Round.png |50px]] ====<br />
<br />
{{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".<br />
[[File:Roundabouts.png|400px|right]]<br />
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. <br />
<br />
<br />
<br />
[[File:Roundboutmn2.png|400px|left]]<br />
<br />
<br />
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).<br />
<br />
<br />
<br />
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.<br />
<br />
If at all possible, drive through a roundabout after it has been created or updated. Verify that it seems to give correct information.<br />
<br />
=== Non-drivable roads ===<br />
<br />
==== Railroad [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:RailroadTracksVanishingPoint.jpg|right|300px|RoadPicN11.jpg]]<br />
<br />
<br />
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.<br />
<br />
<br />
<br />
<br />
{{mbox<br />
| type = important<br />
| text = Please notice that railroads have changed from previous interpretations of railroad mapping. Even veteran editors need to pay attention to this section!<br />
}}<br />
<br />
<br />
* 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.<br />
* 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.<br />
* Always select "None" for the city name. This avoids [[Smudged_city#Overview|city smudging]].<br />
* Set railroad to 2-way directionality and Restrict turns ''to'' and ''from'' the railroad segments.<br />
* 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. <br />
* 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.<br />
* Canadian Pacific uses the acronym CPRS, but it is more know as CP, so it will be called CP Railroad<br />
*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.<br />
* Lock all railroads to a Level 2<br />
* Read [[Road_types/USA#Railroad|this section]] for more information about railroads.<br />
<br />
==== Runway/Taxiway ====<br />
<br />
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. <br />
<br />
<!---- DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ----<br />
-------------------------------------------------------------------------------------<br />
---- This page is only transcluded into (displayed on) the main page for this state.<br />
---- It directly follows the common guidelines applicable to all states. When this<br />
---- page is present (even if blanked), it displaces any optional code that might be<br />
---- in that section.<br />
---- If the original optional code from the main page for this section is still<br />
---- desired, it can be restored by adding the following code to the first line <br />
---- between the "DO NOT MODIFY" lines on this page:<br />
---- {{:USA/CommonState/Special roads|optional}}<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- If there will be a full page for this section, use code similar to the wording<br />
---- below to provide a hyperlink to that page. When creating the full page, use the<br />
---- link on the talk page to ensure the preload data is provided to help with<br />
---- formatting the page. Don't just use the red link from this section once it is<br />
---- saved.<br />
----<br />
See [[{{BasePage2}}/Special roads]] for guidance in {{RootPage2}} that may not be universal to all other states.<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- This section has three possible purposes:<br />
---- 1. It is only providing a hyperlink to the full page for this section.<br />
---- 2. It is only providing some unique guidance for this state that differs from<br />
---- other states.<br />
---- 3. It is intentionally wiping out the general optional content for this section<br />
---- for this state.<br />
------------------------------------------------------------------------------------></div>DallasGranthttps://www.waze.com/wiki/USA/index.php?title=Minnesota/Special_roads/Main&diff=99422Minnesota/Special roads/Main2015-03-14T06:57:43Z<p>DallasGrant: </p>
<hr />
<div><!-- 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><!--<br />
------ DO NOT MODIFY ABOVE THIS LINE -------- DO NOT MODIFY ABOVE THIS LINE ------> <br />
=== Other drivable roads ===<br />
<br />
==== Dirt Road / 4X4 Trail[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
{{mbox<br />
| type = important<br />
| text = Minnesota has different interpretations of Dirt Roads than many other locations. Even veteran editors need to pay attention to this section!<br />
}}<br />
<br />
<br />
[[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.<br />
<br />
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.<br />
<br />
[[File:Dirtroad.PNG|300px|right]]<br />
<br />
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. <br />
<br />
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.<br />
<br />
==== Private Road[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:Pi gated-community1.jpg|right|300px|Pi gated-community1.jpg]]<br />
<br />
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. <br />
<br />
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. <br />
<br />
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.<br />
<br />
==== Alleyways[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
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 Parking Lot class.<br />
<br />
[[File:Pizzalola.png|300px|left]]<br />
<br />
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 parking lot 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.<br />
<br />
==== Roundabouts [[Image:Round.png |50px]] ====<br />
<br />
{{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".<br />
[[File:Roundabouts.png|400px|right]]<br />
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. <br />
<br />
<br />
<br />
[[File:Roundboutmn2.png|400px|left]]<br />
<br />
<br />
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).<br />
<br />
<br />
<br />
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.<br />
<br />
If at all possible, drive through a roundabout after it has been created or updated. Verify that it seems to give correct information.<br />
<br />
=== Non-drivable roads ===<br />
<br />
==== Railroad [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:RailroadTracksVanishingPoint.jpg|right|300px|RoadPicN11.jpg]]<br />
<br />
<br />
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.<br />
<br />
<br />
<br />
<br />
{{mbox<br />
| type = important<br />
| text = Please notice that railroads have changed from previous interpretations of railroad mapping. Even veteran editors need to pay attention to this section!<br />
}}<br />
<br />
<br />
* 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.<br />
* 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.<br />
* Always select "None" for the city name. This avoids [[Smudged_city#Overview|city smudging]].<br />
* Set railroad to 2-way directionality and Restrict turns ''to'' and ''from'' the railroad segments.<br />
* 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. <br />
* 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.<br />
* Canadian Pacific uses the acronym CPRS, but it is more know as CP, so it will be called CP Railroad<br />
*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.<br />
* Lock all railroads to a Level 2<br />
* Read [[Road_types/USA#Railroad|this section]] for more information about railroads.<br />
<br />
==== Runway/Taxiway ====<br />
<br />
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. <br />
<br />
<!---- DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ----<br />
-------------------------------------------------------------------------------------<br />
---- This page is only transcluded into (displayed on) the main page for this state.<br />
---- It directly follows the common guidelines applicable to all states. When this<br />
---- page is present (even if blanked), it displaces any optional code that might be<br />
---- in that section.<br />
---- If the original optional code from the main page for this section is still<br />
---- desired, it can be restored by adding the following code to the first line <br />
---- between the "DO NOT MODIFY" lines on this page:<br />
---- {{:USA/CommonState/Special roads|optional}}<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- If there will be a full page for this section, use code similar to the wording<br />
---- below to provide a hyperlink to that page. When creating the full page, use the<br />
---- link on the talk page to ensure the preload data is provided to help with<br />
---- formatting the page. Don't just use the red link from this section once it is<br />
---- saved.<br />
----<br />
See [[{{BasePage2}}/Special roads]] for guidance in {{RootPage2}} that may not be universal to all other states.<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- This section has three possible purposes:<br />
---- 1. It is only providing a hyperlink to the full page for this section.<br />
---- 2. It is only providing some unique guidance for this state that differs from<br />
---- other states.<br />
---- 3. It is intentionally wiping out the general optional content for this section<br />
---- for this state.<br />
------------------------------------------------------------------------------------></div>DallasGranthttps://www.waze.com/wiki/USA/index.php?title=File:Pizzalola.png&diff=99421File:Pizzalola.png2015-03-14T06:42:22Z<p>DallasGrant: </p>
<hr />
<div></div>DallasGranthttps://www.waze.com/wiki/USA/index.php?title=Minnesota/Special_roads/Main&diff=99412Minnesota/Special roads/Main2015-03-14T01:48:56Z<p>DallasGrant: </p>
<hr />
<div><!-- 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><!--<br />
------ DO NOT MODIFY ABOVE THIS LINE -------- DO NOT MODIFY ABOVE THIS LINE ------> <br />
=== Other drivable roads ===<br />
<br />
==== Dirt Road / 4X4 Trail[[File:Service road.png|200px|Service road.png]] ====<br />
{{mbox<br />
| type = important<br />
| text = Minnesota has different interpretations of Dirt Roads than many other locations. Even veteran editors need to pay attention to this section!<br />
}}<br />
[[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.<br />
<br />
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.<br />
<br />
[[File:Dirtroad.PNG|300px|right]]<br />
<br />
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. <br />
<br />
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.<br />
<br />
==== Private Road[[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:Pi gated-community1.jpg|right|300px|Pi gated-community1.jpg]]<br />
<br />
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. <br />
<br />
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. <br />
<br />
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<br />
<br />
==== Alleyways ====<br />
<br />
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 ne mapped will use the Parking Lot class.<br />
<br />
==== Roundabouts [[Image:Round.png |50px]] ====<br />
<br />
{{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".<br />
[[File:Roundabouts.png|400px|right]]<br />
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. <br />
<br />
<br />
<br />
[[File:Roundboutmn2.png|400px|left]]<br />
<br />
<br />
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).<br />
<br />
<br />
<br />
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.<br />
<br />
If at all possible, drive through a roundabout after it has been created or updated. Verify that it seems to give correct information.<br />
<br />
=== Non-drivable roads ===<br />
<br />
==== Railroad [[File:Service road.png|200px|Service road.png]] ====<br />
<br />
[[File:RailroadTracksVanishingPoint.jpg|right|300px|RoadPicN11.jpg]]<br />
<br />
<br />
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.<br />
<br />
<br />
<br />
<br />
{{mbox<br />
| type = important<br />
| text = Please notice that railroads have changed from previous interpretations of railroad mapping. Even veteran editors need to pay attention to this section!<br />
}}<br />
<br />
<br />
* 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.<br />
* 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.<br />
* Always select "None" for the city name. This avoids [[Smudged_city#Overview|city smudging]].<br />
* Set railroad to 2-way directionality and Restrict turns ''to'' and ''from'' the railroad segments.<br />
* 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. <br />
* 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.<br />
* Canadian Pacific uses the acronym CPRS, but it is more know as CP, so it will be called CP Railroad<br />
*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.<br />
* Lock all railroads to a Level 2<br />
* Read [[Road_types/USA#Railroad|this section]] for more information about railroads.<br />
<br />
==== Runway/Taxiway ====<br />
<br />
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. <br />
<br />
<!---- DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ----<br />
-------------------------------------------------------------------------------------<br />
---- This page is only transcluded into (displayed on) the main page for this state.<br />
---- It directly follows the common guidelines applicable to all states. When this<br />
---- page is present (even if blanked), it displaces any optional code that might be<br />
---- in that section.<br />
---- If the original optional code from the main page for this section is still<br />
---- desired, it can be restored by adding the following code to the first line <br />
---- between the "DO NOT MODIFY" lines on this page:<br />
---- {{:USA/CommonState/Special roads|optional}}<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- If there will be a full page for this section, use code similar to the wording<br />
---- below to provide a hyperlink to that page. When creating the full page, use the<br />
---- link on the talk page to ensure the preload data is provided to help with<br />
---- formatting the page. Don't just use the red link from this section once it is<br />
---- saved.<br />
----<br />
See [[{{BasePage2}}/Special roads]] for guidance in {{RootPage2}} that may not be universal to all other states.<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- This section has three possible purposes:<br />
---- 1. It is only providing a hyperlink to the full page for this section.<br />
---- 2. It is only providing some unique guidance for this state that differs from<br />
---- other states.<br />
---- 3. It is intentionally wiping out the general optional content for this section<br />
---- for this state.<br />
------------------------------------------------------------------------------------></div>DallasGrant