Area Managers for West Virginia can be found in the table below. New editors should consider checking into the formal mentoring program available at no charge. This channel is where you can go to interact and chat with fellow editors along with your 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 and get Peer-to-Peer Mentoring. You can join easily with this link.
If they are successful, they should comment as such in the UR and mark it "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. These need to be marked as "Not Identified" and a brief comment sent. Shared Ownership All editors are considered to have equal ownership of and responsibility for all URs in West Virginia. All editors, regardless if they have worked the UR previously, may send any of the responses described above, provided they adhere to the minimum time spacing guidance between responses.
All editors are explicitly encouraged to attempt to resolve URs at any point during their lifecycle, even if others happen to be actively working it at the same time. Notes 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 script 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.
Cities and towns One of the most common errors when editing the maps is when an editor creates a road and does not confirm the road by setting the city and road name or stating it has none. Duplicate cities can be caused by incorrectly named segments and should be corrected following the guidelines in the duplicate cities article.
Most segments should have an elevation of Ground unless they pass over another segment, waterway, or natural feature. Drivable and non-drivable segments are handled the same way with elevation. Definitions Segment travels over another segment also known as Overpass Segment travels over a river or body of water Segment artificially elevated to pass over ground level objects and natural features.
Tunnel A tunnel is any road segment that is underground and thus the GPS reception is inconsistent. Implementation Elevation of overlapping segments should be set relative to each other, with the lowest segment as Ground unless that segment is a tunnel. Also the pavement type may change Asphalt to Concrete for example. No need to elevate segments over every small creek or box culvert. Only elevate over significant waterways or natural features. Tunneled segments shall have lower elevation, relative to ground and Tunnel should be checked.
Only segments that are actually underground should have the negative elevation. The use of common sense is paramount in using True Elevation. If you use the Bridge tool to join segments, be aware that it raises the elevation of the joined segment.
Lower the joined segment as appropriate. Note for WV, speed limits change at the sign; consult the Wiki for guidance on when to create a new junction for the Speed Limit change.