Utah/Special roads/Main: Difference between revisions Discussion View history

Latest revision as of 23:29, 9 May 2017

Press here to return to the Special roads section to see your changes

Railroads

Railroads/light rail are mapped according to special guidelines in the USA. As of 2016-06-28, Railroad segments should not be named except for special, approved cases. No such cases are currently approved in Utah.

Routable Pedestrian Path (Walking Trail)

Do not map hiking or biking paths/trails. It is common for newer editors to see "missing" paths/trails on the map, and see a readily available Walking Trail segment type to choose from, but mapping trails in Utah is an error. If you have changed your editor language to US English, this becomes clearer as that segment type is then named "Routable Pedestrian Path." This segment type is routable by Waze and will cause unintended results for nearby destinations. There are rare cases where a Routable Pedestrian Path segment can be added to the map to improve routing, but all uses must be approved by a Routable Pedestrian Path expert.

Non-Routable Pedestrian Path (Pedestrian Boardwalk)

Use of this type in Utah is currently limited to one special case: Outdoor plazas where what would otherwise be a thru-road has been converted to permanent and exclusive use by pedestrians. Map the Non-Routable Pedestrian Path as you would a basic road, but do not connect the segments to actual drivable roads (leave a 10m / 33ft gap). This use case has the sole purpose of making it obvious to all editors that there is no drivable road missing from the map, so it is not necessary if the plaza is obviously not a road (ex: Main St Plaza @ Temple Square). These segments should be locked at rank 3.

Stairway

Do not use this type.

Off-road / Not maintained

Utah follows the following functional classification for Gravel and Off-road / Not maintained trails. (expandable section)

Gravel Roads
Functional Classification
Minor Arterial Minor Highway
Minor Collector Primary Street
Local/Not Mapped Street

Off-road / Not maintained
Functional Classification
Minor Arterial Off-road / Not maintained
Minor Collector Off-road / Not maintained
Local/Not Mapped Off-road / Not maintained

Images demonstrated above cannot cover all scenarios for mapping maintenance level to Waze road type. These roads may undergo variation in quality over seasons depending on the climate (rain/snow). Particularly, some gravel roads may have qualities that are closer to Off-road / Not maintained than Street. Editors with local experience and 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.
A single house at the end of a 1 mile (1609m) long private drive = it probably isn't needed.
If it's 5 houses at the end of a single shared 1/4 mile (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.

@@ 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><!--
 ------ 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:
+Railroads/light rail are mapped according to [[Road types#Railroad|special guidelines]] in the USA. As of 2016-06-28, '''Railroad segments should not be named''' except for special, approved cases. No such cases are currently approved in Utah.
-Use the following guidelines when '''mapping''' railroad segments:
+=== Routable Pedestrian Path (Walking Trail) ===
-* By default, enter "Railroad" for the street name of every railroad segment. (See more below on Naming railroad segments.)
-* Always select "None" for the city name. This avoids [[City smudge|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.{{ref label|rr|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.
-* {{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.
-<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>
+'''Do not map hiking or biking paths/trails'''. It is common for newer editors to see "missing" paths/trails on the map, and see a readily available Walking Trail segment type to choose from, but mapping trails in Utah is an error. If you have changed your editor language to '''US''' English, this becomes clearer as that segment type is then named "Routable Pedestrian Path." This segment type is [[Road types#Walking_Trails|routable by Waze and will cause unintended results]] for nearby destinations. There are rare cases where a Routable Pedestrian Path segment can be added to the map to improve routing, but all uses must be approved by a Routable Pedestrian Path expert.
-==== Walking Trails ====
+=== Non-Routable Pedestrian Path (Pedestrian Boardwalk) ===
-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.
+Use of this type in Utah is currently limited to one special case: Outdoor plazas where what would otherwise be a thru-road has been converted to permanent and exclusive use by pedestrians. Map the Non-Routable Pedestrian Path as you would a basic road, but do not connect the segments to actual drivable roads (leave a 10m / 33ft gap). This use case has the sole purpose of making it obvious to all editors that there is no drivable road missing from the map, so it is not necessary if the plaza is obviously not a road (ex: Main St Plaza @ Temple Square). These segments should be locked at rank 3.
-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.
+=== Stairway ===
-==== Dirt Roads ====
+Do not use this type.
-[[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.
+=== Off-road / Not maintained ===
+{{Collapsible section top}}
+Utah follows the following functional classification for Gravel and Off-road / Not maintained trails. (expandable section)
+{{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 cannot cover all scenarios for mapping ''maintenance level'' to Waze ''road type''. These roads may undergo variation in quality over seasons depending on the climate (rain/snow). Particularly, some gravel roads may have qualities that are closer to Off-road / Not maintained than Street. Editors with local experience and 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]]}}
+'''Mapping rural diveways'''
+* If an address/location cannot be reasonably guided to without a private drive, it can be added.
+* A single house at the end of a 1 mile (1609m) long private drive = it probably isn't needed.
+* If it's 5 houses at the end of a single shared 1/4 mile (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.

Search