User:PesachZ/SyncScratch View history

m (Copying text of wiki page for coparison with the "Maryland/Community/Main" page)
m (Copying text of wiki page for coparison with the "Virginia/Major roads/Main" page)
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 ------>  
==Update Requests==
:''For further information, see [[Road names/USA]], [[Road types/USA]] and [[Virginia/Resources]].''


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. {{RootPage2}} has a policy of shared UR management. This means that URs are open to all editors and that there is no "ownership" implied when posting the initial comment. However, it is courteous to allow new editors or editors you don't have an informal agreement with an extra day or two to respond to reporter comments and/or post reminders. Effective UR conversations are usually achieved with a single point of contact for the reporter, but other editors can step in if a UR with reporter comments begins to sit idle or if they think another editor needs help. Please be respectful to other editors and reporters while working URs; it is usually best to send a message to the editor rather than chatting with them through a UR. (Most reporters don't care about the chat, they just want it fixed and not be bothered with multiple responses). Typically, an editor should be given some time to respond to the reporter's comments (since real life has a way to occasionally get in the way to prevent editing time on some days).
:''The following is intended for Virginia Specific roadways. For further information about Interstates and US Highways and other non-Virginia roadways, see [[Road names/USA]], [[Road types/USA]] and [[Virginia/Resources]].''
<gallery>
File:Virginia 28.png|Primary route marker
File:VA_613.PNG|Secondary route marker
</gallery>
===Naming===
Virginia folows the [[Road Names (USA) | 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.


In {{RootPage2}} we have adopted at 0/4/4 system for response to Update Requests. 0/4/4 is the short way of explaining the following.
'''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'''.
==== Standard URs ====
===== Day 0 =====
The first editor who is able to respond to UR should attempt to resolve the UR. If they are successful, they should comment as such in the UR and mark it closed. If more information from the reporter is required to make progress towards closure, a query should be sent to the reporter requesting the information needed for resolution


===== Day 4+ =====
'''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'''.
Polite reminders should be sent to a reporter who has never responded to a query, provided at least three full days have elapsed since the initial response was sent. (You can send reminder at 00:01 Eastern Standard (or Daylight when applicable) Time on the fourth day).


Example
'''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-###'''


"''If no further information is provided we will be unable to fix the issue you encountered and this report will be closed soon''"
'''Town Roads''' or T-Roads are roads that are maintained by incorporated towns on an optional basis. They should be named '''T-###'''


===== Second Day 4+ =====
===Road typing===
URs may be noted as closed due to lack of reporter response, provided at least three full days have elapsed since the followup message was sent (You can close at 00:01 Eastern Standard (or Daylight when applicable) Time on the fourth day since the reminder was sent)
Virginia follows the [[Road Types (USA) | 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]. Alternatively, [http://arcg.is/1FxkS9x maps] have been made to match WME colors.


Example
'''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.


"''This report is being closed due to lack of information, please submit another report if the issue continues. Happy Wazing!''"
[[File:VA_FC.png|center]]


==== Speed Limit URs ====
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 (USA) #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.)
The first user able to respond to a Speed Limit ("SL") UR must evaluate the UR for its applicability to the nearest segment.
If the nearest segment to a SL UR has a Verified SL supported by recent Streetview ("SV") imagery (or other means) OR the speed limit cannot be added due to Waze USA policy (roundabouts, ramps, etc) it should be marked as "NOT IDENTIFIED" and a reply should be sent to the submitter explaining the reason for closing the UR. Examples:
* "''This speed limit report is being closed because it was on a road segment with an already verified speed limit confirmed using recent street view imagery or other means. If you believe this speed limit is incorrect, please reply in the Waze Map Editor, or at [email].''"
* "''This speed limit report is being closed because it was on a road segment that does not have a legally enforceable speed limit. Only speed limits posted on black and white regulatory signs are added to the app. ''"
<br />
If the SL UR occurs on a road segment with an unverified SL or a SL without recent SV imagery, request confirmation from the user on the SL sign and its location. Examples:
* "''Can you please confirm your speed limit report on [road name]? We have a speed limit of [existing SL], did you see a different speed limit posted on a regulatory black and white sign?''"
* "''Can you please confirm your speed limit report on [road name]? We don't have any information on speed limits for this road.''"
<br />
'''SL URs should be revisited after only 1-2 days, and closed after only 3-4 days without a response. Use the closing comment to direct the user on proper SL reporting. Example:'''<br />
"''We have not been able to verify your speed limit report. Please only submit SL reports for roads with incorrect or missing speed limits.  If you would like to see speed limits at all times while using the app, please go to Settings > Speedometer > Show speed limit.''"


'''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 (USA)]] 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 (USA) | 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.
If a different locking standard for the midatlantic region is desired, please develop it at {{:USA/Mid Atlantic/Locking standard}}.  If state-specific guidance for {{BasePage2}} is desired, please develop it at [[{{BasePage2}}/Locking standard]].
-->
<!---- DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ----
<!---- DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ----
-------------------------------------------------------------------------------------
-------------------------------------------------------------------------------------
Line 47: Line 76:
---- desired, it can be restored by adding the following code to the first line  
---- desired, it can be restored by adding the following code to the first line  
---- between the "DO NOT MODIFY" lines on this page:
---- between the "DO NOT MODIFY" lines on this page:
----  {{:USA/CommonState/Community|optional}}
----  {{:USA/CommonState/Major_roads|optional}}
----
----
-------------------------------------------------------------------------------------
-------------------------------------------------------------------------------------
Line 56: Line 85:
---- saved.
---- saved.
----
----
See [[{{BasePage2}}/Community]] for guidance in {{RootPage2}} that may not be universal to all other states.
<!--  this is a comment  --><!--
    If this section grows too long, move most of it to the following page
    and uncomment the paragraph:
--><!--
See [[{{BasePage2}}/Major roads]] for guidance in {{RootPage2}} that may not be universal to all other states.
-->
<!--
----
----
-------------------------------------------------------------------------------------
-------------------------------------------------------------------------------------

Revision as of 17:17, 2 September 2016


For further information, see Road names/USA, Road types/USA 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/USA, Road types/USA and Virginia/Resources.

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. Alternatively, maps have been made to match WME colors.

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 (USA) 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