From Wazeopedia
no edit summary
== Community ==
The Waze forum Forum is a great place to find answers to previously asked questions and also a place to ask new ones. Below are links to the forums specific to West Virginia.
* [ West Virginia section Section of the Waze forumForum]* [ The Mid -Atlantic region forumRegion Forum]* [ The USA section Section of the Waze Forum]* The USA segment unlock requests[ US Unlock and Update Requests Forum]
''[[Area_Manager|Area Managers ]] for West Virginia can be found in [[West_Virginia#Area_Managers|the table below]].''
''New editors should consider checking into the formal mentoring program [[Mentoring/Formal|Formal Mentoring Program]] available at no charge.''
=== Waze West Virginia Google Hangout (GHO) ===
We've have created a Google Hangout (GHO) just for West Virginia. The GHO is where you can go to interact and chat with fellow editors along with the Area and State Managers. It will give you good insight into the best practices and policies in regard to map editing plus give an easy, convenient way for editors to stay in touch, ask questions (any questions, we all started at Rank #1 at some point), request downlocks or review of your work, etc.  If you are editing in WV and have not already been invited, please send a PM to [ Stephenr1966Stephen] and/or [ roadtechieTodd-Roadtechie] with your email address so that we can invite you to the hangout.
=== West Virginia User Report Management Response Timeline ===
'''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'''"Solved'''". If more information from the reporter is required to make progress towards closure, a response should be sent to the reporter containing the information needed for resolution.
'''Day 4+'''
'''Day 8+'''
URs may be noted as closed due to lack of reporter response at any time, provided at least four full days have elapsed since the followup message was sent. These need to be marked as '''"Not Identified"''' and a brief comment sent.
'''Shared Ownership'''
The ideal timeline for UR response is when responses are sent as early as the minimum required time spacing between messages permits; experience has reliably shown that UR response rates are much higher when editors are able to send responses promptly. The 4+ day followup / reminder has shown remarkable improvement in reporter response everywhere that it has been implemented. The script [[Scripts#URComments|URComments]] streamlines the process of responding to a UR and provides comments based on the UR type and can be edited prior to sending to fit your needs.
=== Downlock Requests ===
* City = Closest City the request is being requested. Such as Morgantown, Huntington, etc.
* Reason = Whatever Reason for the request. Examples include Speed Limits (SL), Elevation, Geometry, etc.
* Say Please!
===== Formatting the Permalink (PL) =====
# Before copying a PL hover over the "chain link" icon and press the "Shift" key. This will eliminate the layers in your PL.
# Delete all the information, starting with the "&" after the segment ID. For example, ...&segments=1234567&... Delete everything after the last number in segments.
# Finished Example:
Dnlock L5-L2, Huntington, SLs, Elevation,
=== Uplock Requests ===
Upon finishing your editing, create another PL with the segments needed to Uplock to the [[West_Virginia#Minimum_Lock_Standard|Minimum Lock Standard]]. Use the format '''Uplock L2-L5 "PL"''' . This is done because the person performing the dnlock or uplock may be using a mobile device and it is difficult to select the correct segments. Also, if you add a junction node for a speed limit or PLR, for example, it will create new segment IDs and those will not be the same as the original dnlock request.
--[[User:Markr4468|Markr4468]] ([[User talk:Markr4468|talk]]) 21:27, 22 April 2016 (UTC)