The new Waze Wiki, aka Wazeopedia, is now live at Wazeopedia.waze.com! While this legacy wiki will remain accessible for the time being, it is no longer updated by the community. For the most up-to-date guidance, please visit your local Wazeopedia.

Please do not make any more updates to these legacy wiki pages, all future updates should be made in your country's local Wazeopedia.

Clock over a larger globe

Difference between revisions of "Utah/Special roads/Main"

From waze
Jump to: navigation, search
(Special_roads/Main)
(Special_roads/Main: Updated Dirt Roads and Pvt Roads)
Line 1: Line 1:
 
<!-- 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><!--
 
<!-- 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><!--
 
------ DO NOT MODIFY ABOVE THIS LINE -------- DO NOT MODIFY ABOVE THIS LINE ------>  
 
------ DO NOT MODIFY ABOVE THIS LINE -------- DO NOT MODIFY ABOVE THIS LINE ------>  
==== Railroads ====
+
=== Railroads ===
 
+
When mapping Railroad/Light Rail tracks, please keep the [[Road_types/USA#Railroad|following information]] in mind:
+
  
 +
{{Collapsible section top}}
 +
When mapping Railroad/Light Rail tracks, please keep the [[Road_types/USA#Railroad|following information]] in mind (from the Railroad wiki page):
 +
{{Collapsible section content}}
 
Use the following guidelines when '''mapping''' railroad segments:
 
Use the following guidelines when '''mapping''' railroad segments:
* By default, enter "Railroad" for the street name of every railroad segment. (See more below on Naming railroad segments.)
+
* If you do not know the owner of the railroad tracks, enter "Railroad" for the street name of every railroad segment.
 
* Always select "None" for the city name. This avoids [[City smudge|city smudging]].
 
* Always select "None" for the city name. This avoids [[City smudge|city smudging]].
 
* Lock the segment at L2.
 
* Lock the segment at L2.
Line 26: Line 27:
  
 
<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>
 
<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>
 +
{{Collapsible section bottom}}
  
==== Walking Trails ====
+
=== Walking Trails ===
  
 
They should only be used in rare cases. Walking Trails may have strange side effects on nearby routing. Never use the Walking Trail road type for ordinary hiking paths or bike paths. Most hiking and bicycling paths should not be on the map at all.
 
They should only be used in rare cases. Walking Trails may have strange side effects on nearby routing. Never use the Walking Trail road type for ordinary hiking paths or bike paths. Most hiking and bicycling paths should not be on the map at all.
  
The WME lists the Walking Trail road type as non-drivable. However, as of May 2015, Walking Trails are fully routable and even support Waze House Numbers. Waze treats them in some ways like "Dirt road / 4X4 Trail" but displays them differently. Historically, editors have disconnected Walking Trails to make sure Waze doesn't route drivers over them. This doesn't always work as desired. If a disconnected Walking Trail comes closer to a destination than any other road, Waze may route drivers to a location nearer to the Walking Trail than to the destination. This problem can be severe for Walking Trails passing close to many destinations in a dense neighborhood. Connected or not, the Walking Trail type should never be used where effects on local routing are not desired.
+
The WME lists the Walking Trail road type as non-drivable. Historically, editors have disconnected Walking Trails to make sure Waze doesn't route drivers over them. This doesn't always work as desired. If a disconnected Walking Trail comes closer to a destination than any other road, Waze may route drivers to a location nearer to the Walking Trail than to the destination. This problem can be severe for Walking Trails passing close to many destinations in a dense neighborhood. Connected or not, the Walking Trail type should never be used where effects on local routing are not desired.
 +
 
 +
 
 +
===Dirt Roads 4x4===
 +
 
 +
{{Collapsible section top}}
 +
Utah follows the following functional classification for Gravel and Dirt Road /4x4 trails.
 +
{{Collapsible section content}}
 +
 
 +
{| style="border: 1px solid black; border-spacing: 0; margin: 1em auto;"
 +
|+ {{Street|Gravel Roads}}
 +
|-
 +
! colspan="3" style="border: 1px solid black; padding: 5px; background: #C0C0C0;" | Functional Classification
 +
|-
 +
| style="border: 1px solid black; padding: 5px;" | Minor Arterial {{Minor Highway}}
 +
|-
 +
| style="border: 1px solid black; padding: 5px;" | Minor Collector {{Primary Street}}
 +
|-
 +
| style="border: 1px solid black; padding: 5px;" | Local/Not Mapped {{Street}}
 +
|-
 +
| colspan="3" style="border: 1px solid black; text-align: center;" |
 +
[[File:USFS-level3a.jpg|300x250px|frameless|center]]
 +
|}
 +
 
 +
 
 +
{| style="border: 1px solid black; border-spacing: 0; margin: 1em auto;"
 +
|+ {{Dirt}}
 +
|-
 +
! colspan="3" style="border: 1px solid black; padding: 5px; background: #8B4513;" | Functional Classification
 +
|-
 +
| style="border: 1px solid black; padding: 5px;" | Minor Arterial {{Dirt}}
 +
|-
 +
| style="border: 1px solid black; padding: 5px;" | Minor Collector {{Dirt}}
 +
|-
 +
| style="border: 1px solid black; padding: 5px;" | Local/Not Mapped {{Dirt}}
 +
|-
 +
| colspan="3" style="border: 1px solid black; text-align: center;" |
 +
[[File:USFS-level2b.jpg|300x250px|frameless|center]]
 +
|}
 +
{{Collapsible section bottom}}
 +
 
 +
Images demonstrated above can not cover all scenarios for mapping maintenance level to Waze road type. These types of roads may undergo variation in quality over seasons additionally depending on the climate (rain/snow). Particularly, some gravel roads may have qualities that are closer to Dirt Road / 4x4 Trail than street. Editors with local experience or potential Street View images may help in this determination.
 +
 
 +
 
 +
=== Driveways / Private Roads ===
 +
 
 +
 
 +
{{mbox
 +
|type= important
 +
|text= Please follow the following guidelines for Private Driveways. Wiki standard can be found here. [[Driveways]]}}
  
==== Dirt Roads ====
 
  
[[Road types/USA#Dirt|Dirt Roads]] - In Utah consideration as to the frequency of use and maintenance levels must be considered in determining whether or not to use this type.
+
'''Mapping rural diveways'''
 +
* If an address/location cannot be reasonably guided to without a private drive, it can be added.
 +
* Single house at the end of a 1mi (1609m) private drive, and that's the only house, it probably isn't needed.
 +
* If it's 5 houses at the end of a single shared 1/4mi (402m) long private drive, it probably is needed.
 +
* If it's a house at the end of a 500m (1640 ft) long private drive which is right up against another street from which you cannot access the address (stop point will be on the segment closest), then a private drive is probably needed.  
  
  

Revision as of 10:57, 24 January 2016



Railroads

When mapping Railroad/Light Rail tracks, please keep the following information in mind (from the Railroad wiki page):

Use the following guidelines when mapping railroad segments:

  • If you do not know the owner of the railroad tracks, enter "Railroad" for the street name of every railroad segment.
  • Always select "None" for the city name. This avoids city smudging.
  • Lock the segment at L2.
  • Do not map railroads below ground, as they do not serve any of the three purposes outlined above. This is especially true in urban areas where underground rail lines are common, and their appearance on the map would be confusing to drivers.
  • 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.
  • Create junctions between drivable roads and railroads.[rr]
  • Set railroad to 2-way directionality
  • Restrict turns to and from the railroad segments.
  • When mapping railroad tracks, focus on those near drivable roads.
  • Map rail yards simply, with one railroad segment along either edge of the yard's tracks.
  • Map industrial spurs only if they cross drivable roads.
  • 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.
  • Multiple parallel lines at crossings:
    • At most crossings, there should be only one railroad segment mapped and no more than two parallel railroads mapped at any crossing.
    • Parallel lines are to be at least 5m apart
    • 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.
  • Keep segment lengths under 10,000 meters – the longer the segment length, the more sluggish the editor is to respond to changes.
  • 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.

^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.

Walking Trails

They should only be used in rare cases. Walking Trails may have strange side effects on nearby routing. Never use the Walking Trail road type for ordinary hiking paths or bike paths. Most hiking and bicycling paths should not be on the map at all.

The WME lists the Walking Trail road type as non-drivable. Historically, editors have disconnected Walking Trails to make sure Waze doesn't route drivers over them. This doesn't always work as desired. If a disconnected Walking Trail comes closer to a destination than any other road, Waze may route drivers to a location nearer to the Walking Trail than to the destination. This problem can be severe for Walking Trails passing close to many destinations in a dense neighborhood. Connected or not, the Walking Trail type should never be used where effects on local routing are not desired.


Dirt Roads 4x4

Utah follows the following functional classification for Gravel and Dirt Road /4x4 trails.

 Gravel Roads 
Functional Classification
Minor Arterial  Minor Highway 
Minor Collector  Primary Street 
Local/Not Mapped  Street 
USFS-level3a.jpg


 Dirt Road / 4X4 Trail 
Functional Classification
Minor Arterial  Dirt Road / 4X4 Trail 
Minor Collector  Dirt Road / 4X4 Trail 
Local/Not Mapped  Dirt Road / 4X4 Trail 
USFS-level2b.jpg

Images demonstrated above can not cover all scenarios for mapping maintenance level to Waze road type. These types of roads may undergo variation in quality over seasons additionally depending on the climate (rain/snow). Particularly, some gravel roads may have qualities that are closer to Dirt Road / 4x4 Trail than street. Editors with local experience or potential Street View images may help in this determination.


Driveways / Private Roads

Please follow the following guidelines for Private Driveways. Wiki standard can be found here. Driveways


Mapping rural diveways

  • If an address/location cannot be reasonably guided to without a private drive, it can be added.
  • Single house at the end of a 1mi (1609m) private drive, and that's the only house, it probably isn't needed.
  • If it's 5 houses at the end of a single shared 1/4mi (402m) long private drive, it probably is needed.
  • If it's a house at the end of a 500m (1640 ft) long private drive which is right up against another street from which you cannot access the address (stop point will be on the segment closest), then a private drive is probably needed.