Virginia/Major roads/Main: Difference between revisions Discussion View history

Latest revision as of 02:21, 30 May 2018

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

For further information, see Road names, Road types and Virginia/Resources.

The following is intended for Virginia Specific roadways. For further information about Interstates and US Highways and other non-Virginia roadways, see Road names, Road types and Virginia/Resources.

Primary route marker
Secondary route marker

Naming

Virginia folows the road naming guidelines of the USA. The local name of a road should always be set as the primary name and the route number should be set as an alternate name; there are very few state routes in Virginia that do not have a local name.

Primary state routes have numbers in the range of 2 to 599 (and, as exceptions, 785, 895), displayed in a route marker using a shield design. Using the example above, the road should be named SR-28.

Secondary state routes are those with route numbers 600 or greater; if these roads have route markers (many do not), they use a circle design or a small rectangle instead of a shield. Using the example above, the road should be named VA-613.

Frontage roads are roads run parallel to a higher-speed, limited-access road. A frontage road is often used to provide access to private driveways, industries, farms, etc.. A list of these roads can be found here. They should be named F-###

Town Roads or T-Roads are roads that are maintained by incorporated towns on an optional basis. They should be named T-###

Road typing

Virginia follows the national guidelines for road types. VDOT Functional Classification The VDOT Functional Classification Maps have been approved for setting road type in WME based on the quick reference chart and other considerations listed below.The functional classifications are available via an interactive map that can be found here.

NEW Script to help for Functional Classification - This should be considered as a tool to help in functional classification. There are some problems with incorrect FC; some are caused by bad VDOT data, some are by conflicting rules. Please make sure to use other resources including street signs in recent SV shots (cross streets may be more current) and other FC resources. This script is currently available for R3+ editors who have Area Manager roles. (If interested in an AM position please contact one of your State Managers). Link to script is here. Thanks to MapoMagic for developing this script.

For purposes of applying the US road type guidelines, we treat only primary state routes as "numbered state highways." Primary state routes must be designated as at least Minor Highway in Waze, unless the road's functional classification requires a higher designation. (For example, primary routes 785 and 895 are road typed to reflect their future designation as freeway.)

Exception: Primary routes that solely access state facilities (parks, educational/correctional institutions, etc.) should be given a road type that matches the FC maps published by VDOT, even if that is less than Minor Highway. Many, but not all of the routes that service state institutions are SR-3##; a non-exhaustive list can be found here.

Secondary state routes, frontage roads, and town roads are always typed based solely on the FC maps

Consult the Road types page for further guidance on how to type based on functional class and road signage.

Locking

In Virginia we have a set minimum standard for locking roads based on segment type. Any road of a certain segment type must be locked at least to the rank (level) in the chart below. Roads may be locked higher for protection and special situations (areas with construction, tricky design, frequent mistakes, imaging inaccuracies, and the like), but should not be locked lower. A great time to implement these locks is while bringing the road types of an area into compliance with the current US road type standards. Lock the roads based on type after they've been set to current US road type standards and connecting roads are set up correctly and all other edits are complete for the segment.

Minimum Locking Standard

Actual locks used may be more than the table below, depending on area circumstance. Please consult RC, SM, or appropriate AM for guidance

**Locking Levels**
Freeway	5
Ramp	4
Major Highway	4
Minor Highway	3
Primary Street	2 (3 for one way PS)
Street	1 (2 for one way S)
\|-\|-\|-\|-\|-\|-\|-\|-\|-\| Railroad \|-\|-\|-\|-\|-\|-\|-\|-\|-\|	2
• • • • Ferry • • • •	5

@@ 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 ------>
-:''For further information, see [[Road names/USA]], [[Road types/USA]] and [[Virginia/Mapping resources]].''
+:''For further information, see [[Road names]], [[Road types]] and [[Virginia/Resources]].''
-In Virginia, outside cities and major towns (and a couple of urban counties), nearly every road and street is designated as a "state highway" and assigned a number for VDOT inventory purposes. However, for Waze routing, we only treat '''primary''' state highways as "numbered state highways" for purposes of applying the [[Road types/USA|road type guidelines]]. Highways marked with '''primary''' route numbers must be designated as at least "Minor Highway" in Waze, unless the road's functional classification requires a higher designation. For Virginia secondary highways, rely on the road's functional classification only.
-Primary state highways have numbers in the range of 2 to 599 (and, as exceptions, 785, 895), displayed in a route marker using a shield design. All other numbers from 600 up are secondary highways; if these roads have route markers (many do not), they use a circle design instead of a shield. See [http://www.virginiadot.org/info/resources/route-index-07012003.pdf Virginia DOT Route Index Resources] for more info.
-Our naming convention is '''SR-###''' for primary routes (SR-2 - SR-599, SR-785 and SR-895)  and '''VA-###''' for secondary routes (VA-600+). Since this update is fairly new (1/24/2015), your first priority should be making sure that ramps and roads with the route name as their primary name are correct. Correcting alt names is a secondary priority.
+:''The following is intended for Virginia Specific roadways. For further information about Interstates and US Highways and other non-Virginia roadways, see [[Road names]], [[Road types]] and [[Virginia/Resources]].''
 <gallery>
 File:Virginia 28.png|Primary route marker
 File:VA_613.PNG|Secondary route marker
 </gallery>
-==== Locking standard ====
+===Naming===
-{{Lock Standard State|VA}}
+Virginia folows the [[Road names| road naming guidelines of the USA]]. The local name of a road should always be set as the primary name and the route number should be set as an alternate name; there are very few state routes in Virginia that do not have a local name.
+'''Primary state routes''' have numbers in the range of 2 to 599 (and, as exceptions, [http://en.wikipedia.org/wiki/Interstate_785 785], [http://en.wikipedia.org/wiki/Virginia_State_Route_895 895]), displayed in a route marker using a shield design.  Using the example above, the road should be named '''SR-28'''.
+'''Secondary state routes''' are those with route numbers 600 or greater; if these roads have route markers (many do not), they use a circle design or a small rectangle instead of a shield. Using the example above, the road should be named '''VA-613'''.
+'''Frontage roads''' are roads run parallel to a higher-speed, limited-access road. A frontage road is often used to provide access to private driveways, industries, farms, etc.. A list of these roads can be found [http://www.vahighways.com/route-log/fseries.htm here.] They should be named '''F-###'''
+'''Town Roads''' or T-Roads are roads that are maintained by incorporated towns on an optional basis. They should be named '''T-###'''
+===Road typing===
+Virginia follows the [[Road types| national guidelines for road types]].
+VDOT Functional Classification
+The VDOT Functional Classification Maps have been approved for setting road type in WME based on the quick reference chart and other considerations listed below.The functional classifications are available via an interactive map that can be found [http://www.arcgis.com/home/webmap/viewer.html?webmap=3eca6c9adb6649c988d98734f85baddb here].
+'''NEW Script''' to help for '''Functional Classification''' -  This should be considered as a tool to help in functional classification.   There are some problems with incorrect FC; some are caused by bad VDOT data, some are by conflicting rules.   Please make sure to use other resources including street signs in recent SV shots (cross streets may be more current) and other FC resources.  This script is currently available for R3+ editors who have Area Manager roles.   (If interested in an AM position please contact one of your State Managers).  Link to script is [//greasyfork.org/en/scripts/21944-wme-fc-layer-beta here]. Thanks to MapoMagic for developing this script.
+[[File:VA_FC.png|center]]
+For purposes of applying the US road type guidelines, we treat only primary state routes as "numbered state highways." Primary state routes must be designated as at least [[Road types#Minor_Highway|{{Minor Highway}}]] in Waze, unless the road's functional classification requires a higher designation. (For example, primary routes '''785''' and '''895''' are road typed to reflect their future designation as freeway.)
+'''Exception''': Primary routes that solely access state facilities (parks, educational/correctional institutions, etc.) should be given a road type that matches the FC maps published by VDOT, even if that is less than Minor Highway. Many, but not all of the routes that service state institutions are '''SR-3##'''; a non-exhaustive list can be found [http://en.wikipedia.org/wiki/State_highways_serving_Virginia_state_institutions here.]
+Secondary state routes, frontage roads, and town roads are always typed based solely on the FC maps
+Consult the [[Road types]] page for further guidance on how to type based on functional class and road signage.
+===Locking===
+In Virginia we have a set minimum standard for locking roads based on segment type. Any road of a certain segment type must be locked at least to the rank (level) in the chart below. Roads may be locked higher for protection and special situations (areas with construction, tricky design, frequent mistakes, imaging inaccuracies, and the like), but should not be locked lower.
+A great time to implement these locks is while bringing the road types of an area into compliance with the current [[Road types| US road type standards.]] Lock the roads based on type after they've been set to current US road type standards and connecting roads are set up correctly and all other edits are complete for the segment.
+;Minimum Locking Standard
+Actual locks used may be more than the table below, depending on area circumstance. Please consult RC, SM, or appropriate AM for guidance
+{| border="1" style="border-collapse:collapse;margin: 1em auto 1em auto; text-align:center"
+|+ '''Locking Levels'''
+|-
+| {{Freeway}}||5
+|-
+| {{Ramp}}||4
+|-
+| {{Major Highway}}||4
+|-
+| {{Minor Highway}}||3
+|-
+| {{Primary Street}}||2 (3 for one way PS)
+|-
+| {{Street}}||1 (2 for one way S)
+|-
+| {{Railroad}}||2
+|-
+| {{Ferry}}||5
+|}
 <!--
 See [[{{BasePage2}}/Major roads]] for guidance in {{RootPage2}} that may not be universal to all other states and territories.

Search

Virginia/Major roads/Main: Difference between revisions Discussion View history

Latest revision as of 02:21, 30 May 2018

Naming

Road typing

Locking