User:PesachZ/SyncScratch View history

VisualWikitext
m (Copying text of wiki page for coparison with the "Wisconsin/Special roads/Main" page)
m (Copying text of wiki page for coparison with the "Arizona/Other/Main" page)
Line 2: Line 2:
------ DO NOT MODIFY ABOVE THIS LINE -------- DO NOT MODIFY ABOVE THIS LINE ------>  
------ DO NOT MODIFY ABOVE THIS LINE -------- DO NOT MODIFY ABOVE THIS LINE ------>  


== Speed Limits ==
=== Working with URs ===


Wisconsin has no variances from the USA Speed Limits wiki: [[Speed_limits/USA | USA Speed Limits Wiki]]
{{RootPage2}} has adopted a '''72hr/5 day''' standard when dealing with User Requests.
[[Image:Request pin open-low.png|left]] Our goal is to respond to new URs within 72 hours.
{{clear}}
[[Image:Request pin open-med.png|left]] Fix the issue (if within our control), or solicit additional needed information from the reporter, and
{{clear}}
[[Image:Request pin open-high.png|left]] Resolve URs that have no response to comment in 5 days, or are completed. '''NEVER close a UR without leaving a closing comment''', even if it's something as simple as ''"No info received, closing."''


=== Speed Limit Effective-Location for Wisconsin ===
<!-- Approved by NNote, Arizona LC on 24 Nov, 2014 -->
<br />
When responding to URs, please remember the wise words of the scholar, ''brevity is the soul of wit.'' 


Speed Limits in Wisconsin change at the sign. This is important when determining where speed limit changes should be marked on the Waze map. USA guidance for states that "change at the sign" is given [[Speed_limits/USA#State_law_speed_limit_changes_at_the_sign | here]].
More than likely, the user is going to be reading your response in the Waze App, so try and keep it as short as possible, while still conveying the information, or request desired.


Where speed limits change is an important decision for clear guidance to drivers. There are many considerations for appropriately marking speed limit changes on the map. Editors, especially new editors, should be familiar with the USA Speed Limits wiki, a link to which is shown above.  
Before working with URs, you should review the [[UR|Wiki documentation on URs]] and especially the section on [[UR#The resolution process / Etiquette|etiquette]].


For example, if there is an intersection within 200 feet of the speed limit sign, then the speed-change location should be made at that intersection. If the speed-change location is within 200 feet of an existing junction node, not an intersection, then we don't add a new junction node.
=== Working with Speed Limit URs ===


Alleys in Wisconsin - max speed is <b>15 mph</b> unless posted otherwise.
When responding to a Speed Limit Update Report, or SLUR, that is invalid or incorrect, please use the following to respond:
* Not Identified (invalid information): Waze does not set speed limits based on yellow "advisory" signs or variably timed or temporary speed limits, e.g., school zones, work zones. Waze uses the maximum speed limit designated by the established, or permanent, white regulatory sign.
* Not Identified (correct speed limit already in place): The speed limit for this road segment already has a verified speed limit confirmed using either recent street view imagery or other means.


Always refer to the USA Speed Limits wiki for guidance, and check with your Area or State Managers for clarification if needed.
[[File:Checkchat.jpg|thumb|right|Getting your attention]]
=== Live Users ===


If you're editing in Arizona, we ask that you turn on the LIVE USERS layer in the editor. If you see another editor show up where you are editing, and move around you, please check WME Chat. Also, check and see if you have a Private Message (PM) in the Forum.


[https://docs.legis.wisconsin.gov/statutes/statutes/346/IX/57/ Wisconsin Legislature: 346.57]
There may be an issue with the area you're editing in, or what you are doing.
== Update Requests ==


Wisconsin is using the [[USA/Great Lakes/Test#Update Requests | Great Lakes region Update Requests Response System]]:
Never Be Unreachable!


=== Overview ===
NOTE: all day values are relative to the date the FIRST editor response is sent to the reporter.
'''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. 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
'''Shared Ownership:'''
* All editors are considered to have equal ownership of and responsibility for all URs in the Great Lakes Region.
* 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
* While strongly recommended, it is not required to send the followup message.
=== Process Chart ===
[[File:GLR_-_UR_Process_20150606.png|700px]]


<!---- 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 53: Line 44:
---- 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/Special roads|optional}}
----  {{:USA/CommonState/Other|optional}}
----
----
-------------------------------------------------------------------------------------
-------------------------------------------------------------------------------------
Line 62: Line 53:
---- saved.
---- saved.
----
----
See [[{{BasePage2}}/Special roads]] for guidance in {{RootPage2}} that may not be universal to all other states.
See [[{{BasePage2}}/Other]] for guidance in {{RootPage2}} that may not be universal to all other states.
----
----
-------------------------------------------------------------------------------------
-------------------------------------------------------------------------------------

Revision as of 13:46, 28 August 2016

 Press here to return to the SyncScratch section to see your changes 


Working with URs

PesachZ has adopted a 72hr/5 day standard when dealing with User Requests.

Our goal is to respond to new URs within 72 hours.

Fix the issue (if within our control), or solicit additional needed information from the reporter, and

Resolve URs that have no response to comment in 5 days, or are completed. NEVER close a UR without leaving a closing comment, even if it's something as simple as "No info received, closing."


When responding to URs, please remember the wise words of the scholar, brevity is the soul of wit.

More than likely, the user is going to be reading your response in the Waze App, so try and keep it as short as possible, while still conveying the information, or request desired.

Before working with URs, you should review the Wiki documentation on URs and especially the section on etiquette.

Working with Speed Limit URs

When responding to a Speed Limit Update Report, or SLUR, that is invalid or incorrect, please use the following to respond:

  • Not Identified (invalid information): Waze does not set speed limits based on yellow "advisory" signs or variably timed or temporary speed limits, e.g., school zones, work zones. Waze uses the maximum speed limit designated by the established, or permanent, white regulatory sign.
  • Not Identified (correct speed limit already in place): The speed limit for this road segment already has a verified speed limit confirmed using either recent street view imagery or other means.
Getting your attention

Live Users

If you're editing in Arizona, we ask that you turn on the LIVE USERS layer in the editor. If you see another editor show up where you are editing, and move around you, please check WME Chat. Also, check and see if you have a Private Message (PM) in the Forum.

There may be an issue with the area you're editing in, or what you are doing.

Never Be Unreachable!


Retrieved from "https://beta.waze.com/wiki/USA/index.php?title=User:PesachZ/SyncScratch&oldid=149477"