(Created page with "== Community == The Waze 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...") |
No edit summary |
||
Line 1: | Line 1: | ||
== Community == | == Community == | ||
The Waze | The Waze 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 | * [https://www.waze.com/forum/viewforum.php?f=582 West Virginia Section of the Waze Forum] | ||
* The Mid Atlantic | * [https://www.waze.com/forum/viewforum.php?f=946 The Mid-Atlantic Region Forum] | ||
* The USA | * [https://www.waze.com/forum/viewforum.php?f=129 The USA Section of the Waze Forum] | ||
* | * [https://www.waze.com/forum/viewforum.php?f=622 US Unlock and Update Requests Forum] | ||
''Area Managers for West Virginia can be found in the table below.'' | ''[[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 | ''New editors should consider checking into the [[Mentoring/Formal|Formal Mentoring Program]] available at no charge.'' | ||
=== Waze West Virginia Google Hangout (GHO) === | === Waze West Virginia Google Hangout (GHO) === | ||
We | We 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 [https://www.waze.com/forum/memberlist.php?mode=viewprofile&u=16973197 Stephen] and/or [https://www.waze.com/forum/memberlist.php?mode=viewprofile&u=16946130 Todd-Roadtechie] with your email address so that we can invite you to the hangout. | |||
=== West Virginia User Report Management Response Timeline === | === West Virginia User Report Management Response Timeline === | ||
Line 22: | Line 24: | ||
'''Day 0''' | '''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 | 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 '''"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 4+''' | ||
Line 30: | Line 32: | ||
'''Day 8+''' | '''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. | 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''' | '''Shared Ownership''' | ||
Line 38: | Line 40: | ||
'''Notes''' | '''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 4+ day followup / reminder has shown remarkable improvement in reporter response everywhere that it has been implemented. | 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 === | === Downlock Requests === | ||
Line 59: | Line 61: | ||
* City = Closest City the request is being requested. Such as Morgantown, Huntington, etc. | * 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. | * Reason = Whatever Reason for the request. Examples include Speed Limits (SL), Elevation, Geometry, etc. | ||
* Say Please! | |||
===== Formatting the Permalink (PL) ===== | ===== Formatting the Permalink (PL) ===== | ||
Line 64: | Line 67: | ||
# Before copying a PL hover over the "chain link" icon and press the "Shift" key. This will eliminate the layers in your 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. | # Delete all the information, starting with the "&" after the segment ID. For example, ...&segments=1234567&... Delete everything after the last number in segments. | ||
# Example: | # Finished Example: | ||
Dnlock L5-L2, Huntington, SLs, Elevation, https://www.waze.com/editor/?env=usa&lon=-82.42197&lat=38.39253&zoom=5&segments=65476746 | Dnlock L5-L2, Huntington, SLs, Elevation, https://www.waze.com/editor/?env=usa&lon=-82.42197&lat=38.39253&zoom=5&segments=65476746 | ||
=== Uplock === | === 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. | 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) |
Revision as of 21:27, 22 April 2016
Community
The Waze 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 of the Waze Forum
- The Mid-Atlantic Region Forum
- The USA Section of the Waze Forum
- US Unlock and Update Requests Forum
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.
Waze West Virginia Google Hangout (GHO)
We 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 Stephen and/or Todd-Roadtechie with your email address so that we can invite you to the hangout.
West Virginia User Report Management Response Timeline
(NOTE: all day values are relative to the date the FIRST editor response is sent to the reporter)
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 "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+
Polite reminders should be sent to reporters who have not responded to the initial at any time, provided at least four full days have elapsed since the initial response was sent
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
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 describe above, provided they adhere the minimum time spacing guidance between responses. All editors are explicitly encouraged to attempt resolving 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 4+ day followup / reminder has shown remarkable improvement in reporter response everywhere that it has been implemented. 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.
Downlock Requests
Definitions
Downlock (or Down-Lock): Term used to describe the process of adjusting the Segment Lock level in WME down to match the regional standards, or the Rank of an editor to allow them to edit the segment(s).
Uplock (or Up-Lock): Term used to describe the process of adjusting Segment Lock levels up in WME. Often to its prior Segment Lock level before it was Down-Locked to match the Rank of an editor to allow them to edit the segment(s).
Permalink (or PL): A URL aka browser link (http://...) that shows the map with the same view as the user who created the Permalink (PL). Location, zoom, layers, and selected segments will be the same. You can find the icon for the Permalink in the lower right corner of the WME screen (two chains linked together). When the mouse is hovered over the icon, press Control-C to copy the Permalink to the clipboard (or right-click it and choose copy). You can then paste the PL into an e-mail or forum message so others can access what you are seeing.
Request Format
A downlock request can made in the West Virginia Google Hangout. The request itself shall be constructed as follows:
Dnlock Lx-Ly, "City", "Reason", PL
- Lx = Current Lock Level
- Ly = Proposed Lock Level
- 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, https://www.waze.com/editor/?env=usa&lon=-82.42197&lat=38.39253&zoom=5&segments=65476746
Uplock Requests
Upon finishing your editing, create another PL with the segments needed to Uplock to the 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.