User:ShadowMasterCM/So you want to edit View history

No edit summary
 
(70 intermediate revisions by the same user not shown)
Line 1: Line 1:
='''WME Extensions & Scripts:'''=


=='''WME Extensions & Scripts:'''==
Do you use any Chrome Extensions or Scripts for WME yet?
 
Extensions and Scripts are designed to work with WME, and are incredibly powerful tools, that will make your editing time far more productive. Rather than spend countless hours scrolling around looking for something to 'fix', these tools will direct your attention to various parts of WME that ''MAY'' need attention.
 
''Remember that these tools will identify items that POSSIBLY need attention. Not every issue identified is actually incorrect. It may actually be a configuration approved by Sr Editors as an exception to wiki guidance based on specific local conditions.''


Do you use any Chrome Extensions or Scripts for WME yet?
=='''Extensions'''==
 
All extensions are available at the [https://chrome.google.com/webstore/search/WME?_category=extensions Chrome Store]. Simply view these in the Chrome Store, click to install them, and then do a ''browser'' refresh [press F5] when viewing WME to load the newly installed extensions.
 
''NOTE: Remember that WME is designed for use with Chrome, so this page is about installing tools in Chrome, for use with WME. No information is available here for other browser options or tools used by them.''
 
It is highly recommend that new editors start out with the following extensions:
 
* [https://wiki.waze.com/wiki/Scripts/WME_Validator Validator]
* [https://wiki.waze.com/wiki/Scripts/WME_Toolbox Toolbox]
* [https://wiki.waze.com/wiki/Scripts/Browser_requirements#Greasemonkey_or_Tampermonkey_add-on_for_script_management TamperMonkey]


Extensions and Scripts designed to work with WME are incredibly powerful tools that will make your editing time far more productive. These tools will direct your attention to various parts of the data in WME that MAY need attention. With out these sort of tools, editors usually endlessly scroll around in WME 'looking' for something to 'fix'.


NOTE: Remember that these tools will identify items that POSSIBLY need attention. Not every issue identified is actually incorrect. It may actually be a configuration approved by Sr Editors as an exception to wiki guidance based on specific local conditions.
''TamperMonkey is a "script manager". It will allow you to install other useful scripts into WME for additional tools that you will use as you learn more about editing in WME.''


It is highly recommend that new editors start out with [https://wiki.waze.com/wiki/Scripts#WME_Validator Validator], [https://wiki.waze.com/wiki/Scripts/WME_Toolbox Toolbox] & [https://chrome.google.com/webstore/detail/tampermonkey/dhdgffkkebhmkfjojejmpbldmpobfkfo Tampermonkey*]
<small>''An additional thought about extension vs script. For those that use the Google profile login on Chrome, any extensions that you have installed at your home device, will also load into a session on any other device [re: work, school, internet cafe]. Scripts on the other hand require you to install the scripts into TamperMonkey on each separate device.''


All three are available at the [https://chrome.google.com/webstore/search/wme Chrome Store]. Simply view these in the Chrome Store, click to install them, and press F5 on your WME tab. Remember that WME is designed for use with Chrome, so this page is about installing tools in Chrome, for use with WME.  
''Toolbox for example is offered as an extension and a script. It may be easier to use the extension as you will likely have the three listed above running 90% of your time in WME.''</small>


*TamperMonkey is a "script manager". It will allow you to install other useful scripts into WME for more advanced tools that you will use as you learn more about editing in WME.
=='''Scripts'''==


Once you have TamperMonkey installed:
''Once you have TamperMonkey installed:''


Look for the TamperMonkey icon in the upper right corner of Chrome, left click the icon, then select "Get new scripts..."
Look for the TamperMonkey icon in the upper right corner of Chrome, left click the icon, then select "Get new scripts..."
A new tab should open for TamperMonkey, and on there is a listing of User Script sources. Most of the most current scripts for WME are usually found on "GreasyFork". Click on the link to GreasyFork.
 
A new tab will open for TamperMonkey, and there is a [http://tampermonkey.net/scripts.php listing of Userscript Sources]. The most current versions of WME scripts are usually found on the "GreasyFork" site. Click on the link to open another tab for GreasyFork.


Once you get to the GreasyFork page, enter 'WME' in the search box and you should see a list of [https://greasyfork.org/en/scripts/search?q=wme Scripts for WME]
Once you get to the GreasyFork page, enter 'WME' in the search box and you should see a list of [https://greasyfork.org/en/scripts/search?q=wme Scripts for WME]


NOTE: Do not feel the need to install any/ all of them, until you are working on an issue where a specific script might be useful!
''NOTE: Do not feel the need to install any/ all of them, until you are working on an issue where a specific script might be useful!''
 
One script specifically useful for editors in NY, that works with the extension ''Validator'', is [https://greasyfork.org/en/scripts/12793-wme-validator-localization-for-new-york WME Validator Localization for New York]
 
Another useful script for new editors who want to process Update Requests [UR's], is [https://greasyfork.org/en/scripts/1776-wme-ur-mp-tracking WME UR-MP tracking]. This can be a very powerful tool once you [https://www.waze.com/forum/viewtopic.php?f=819&t=125216 get familiar with it] and adjust it to your editing style.
 
='''Tips & Suggestions'''=
 
== '''PermaLinks & Unlock Requests''' ==
 
An important part about the editing community is interacting with other editors that may have knowledge about the specific issue you are currently trying to resolve. New editors will also follow along with a group discussion, trying to expand their own knowledge.
 
[https://wiki.waze.com/wiki/Permalink#Permalink PermaLinks] [PL's] are used by editors, to link directly to some bit(s) of data in WME, when asking another editor for assistance.
 
For example an editor with level 2 [L2] access needs to connect a PLR to a level 3 [L3] segment. Once you create a PL to that L3 segment, you can send it to a L3 editor and request an 'unlock'.
 
It is very likely that several editors may click on a PL that is shared in any communication platform. There are however a few nuances about using PL's that an editor needs to keep in mind.
 
=== '''Producing Useful PLs''' ===
 
*Centering Screen & Zoom Level
 
After all the segments to be included are selected, one very important step is to zoom out so you can '''see them''' all on the screen, and then '''center''' your view in WME on those selected segments.
 
Keep in mind that anything not centered and [[User:Dsfargeg/Road_Types_and_Zoom_Levels|farther out than Zoom4]] will usually fail to produce a functional PL, and will not open correctly in WME after being clicked on.
 
So save yourself some grief and remember to keep the screen at maximum of Zoom4 and centered and THEN create your PL!
 
*Layer Data
 
As an editor you might work on ''Map Problems'' [MP's] and ''Speed cameras'',  and so you will have those layers turned on in WME.
 
Editors who are assisting you, as well as other editors trying to learn from the discussion, may not have MP's locally, or there are no Speed cameras in their area, so they would not normally have those layers turned on.


One such useful script for editors in NY is [https://greasyfork.org/en/scripts/12793-wme-validator-localization-for-new-york Localization Pack for New York]
'' '''Any editor that clicks on a default PL that includes layer data, has the 'layers' settings changed in their local copy of the Waze Map Editor!''' ''


One additional script very useful for new editors, who want to process Update Requests [URs], is [https://greasyfork.org/en/scripts/1776-wme-ur-mp-tracking UR-MP Tracking]
Active editors may click on dozens of PL's during a typical editing session in WME. Having to constantly reset layers in WME to your personal preferences is not only a waste of productive editing time, it simply gets frustrating after a while.


''The default PL in WME looks like this:''


=='''Standard Responses:'''==
https://www.waze.com/editor/?env=usa&lon=-77.44210&lat=43.09923&layers=1540&zoom=5&mapProblemFilter=0&mapUpdateRequestFilter=1&venueFilter=1&update_requestsFilter=true&problemsFilter=true&lo%20...%20ueFilter=0&apProblemFilter=0&segments=33958923
<big>Standard Responses [SRs]</big> are used when working with Update Requests [URs] in the Waze Map Editor [WME].  


These SRs are intended to offer general guidance to help editor's effectively communicate with Waze reporters in a productive manner. Please remember to keep this [https://wiki.waze.com/wiki/Update_Requests_in_Waze_Map_Editor#The_resolution_process_.2F_Etiquette excellent guidance] in mind when ever working with URs.
Toolbox upgrades WMEs single default 'blue' colored PL icon, into multiple 'red' colored icons, all used to create various types of PL's. Simply hover your mouse over each red icon, and a brief description of what type of PL will be created appears.  


The red PL icon located farthest to the right, is the PL icon used most commonly by editors.


Please feel free to modify any of these to fit your specific situations.
Toolbox also offers the ability to ''toggle'' the excess layers data '''on or off''' from the default PL, by simply pressing the 'Shift' key.
<br />
=== Greeting: ===


When to use: Used to start the conversation with a reporter, in the UR that contains to little detail, as well as those URs that contain "N/A" or are "blank".
''The Toolbox PL [No Layers mode] looks like this:''


* Thanks for the report! Can you provide specific information about this error?
https://www.waze.com/editor/?env=usa&lon=-77.44210&lat=43.09923&zoom=5&lo%20...%20ueFilter=0&apProblemFilter=0&segments=33958923


=== Reminder: ===
'''NOTE:''' ''Waze recently altered the data built into PLs, and the current version of Toolbox does not completely strip away the excess layers data. Hopefully this will be corrected in a future update.''


When to use: When you have sent an initial request for additional information, and the reporter has not yet replied. The specific amount of time between the initial request and the reminder varies between regions, so check for local guidance.  
[https://greasyfork.org/en/scripts/18089-wme-simple-permalink-from-wme-keepmylayers WME Simple Permalink] is another script that will also produce a PL with all the extra layers data stripped away.


*Hi There! We would like to try to correct this issue for you, but we need more specific information about it. If it can't be corrected, then it will have to be left incomplete and this report will be closed.
''The WME Simple Permalink looks like this:''


=== No Response/ Closing: ===
https://www.waze.com/editor/?env=usa&lon=-77.44210&lat=43.09923&zoom=5&segments=33958923
When to use: After the initial request for additional info AND the reminder request have been sent, and an additional wait period has passed since the reminder was sent, THEN you should close out the UR as 'Not Identified'.


NOTE: Editors should also consider giving the entire local area one last review and see what various items can be corrected before closing this UR and leaving this specific area of the map. There may not be another editor that will review this area for weeks or months!
*Mobile Editors


*No recent activity - No new information - Closing as "Not Identified"
Often editors that are helping with 'unlock' requests, are accessing WME and the communication platform from a mobile device. They are very limited in what they can do in WME, and the typical smaller screens make doing any editing more challenging in general. They are also using cellular data, rather than 'unlimited' cable/ dsl connections.


=== Address Request: ===
When requesting assistance from such an editor, a PL created excluding the layer data is especially important. The extra map data is not needed for the unlock, so it only slows the WME page load, before the editor can actually do the unlock. That extra layer info also uses additional data on their cellular plan. Obviously we don't want to be a nuisance to the very people helping us!


When to use: Once specific routing issues have been identified by the reporter, but an editor is not able to reproduce them, knowing the exact starting/ ending address used by the reporter, is sometimes useful to the editor.  
Taking the mobile aspect one step further, it is often not possible to 'copy' a PL out of a single message 'bubble' in chat. Mobile devices usually only offer to copy the entire bubble. Some editors use mobile tools that they will paste the PL into. That extra step have to try to trim out words from the PL is an extra hassle for them.  


NOTE: For privacy reasons some reporters may not be comfortable giving you a specific address. You should respect this and consider alternative ways to resolve the issue.
=== '''Asking for the unlock''' ===


*Can I ask what your destination address was? I would like to try to replicate this error.
So after considering all the above information, what exactly do you do to use this PL you created?


=== Issue Solved: ===
Easy, go ask for an unlock!


When to use: The issue reported was properly identified, and the map data was corrected as needed...including a comment about the delay due to 'Tile Updates' is also very useful information to the reporter, who may only be a casual Waze app user.
* Describe what you want - [locked level > your level, what you want to do, location of your request]:<br />


*Appropriate data updated. This should appear in the Waze app in the next several days. Please open a new report if there are any additional issues. Thanks!
''L3 to L2, connect a PLR, Rochester''


=== Restrictions [Weight/Height/Width/Vehicle Type]: ===
* Send your request to the communication platform


When to use: When you get a report offering this sort of data, do NOT just discard it as useless. Waze wants to collect any data made available for [possible] future use, but editors also need to help the reporter understand they won't see it currently in use in the Waze app.
''Press Enter/ Send''


*Thanks for the info on the restriction(s), the appropriate data was updated. Please continue to send reports whenever you see this sort of information posted locally, so that Waze can have this information available for future use. Thanks!
* Now paste your PL as a separate message


NOTE: The current version of the Waze app does NOT use this type of data when selecting a route. Please remember to always watch for posted signage and obey local laws.
''https://www.waze.com/editor/?env=usa&lon=-77.44210&lat=43.09923&zoom=5&segments=33958923''


=== No Solution/ Closing: ===
* Send your PL
When to use: Reporter has given as much information as they can, but the actual issue is never specifically identified and corrected. We don't want the reporter to feel as tho they wasted their time sending in a UR, but we also need to acknowledge that this specific issue can not be fixed.


*All relevant MAP DATA has been reviewed, and at this time there is no obvious solution to this error. This report will be closed as "Not Identified". Please continue to report any additional issues. Thanks!
''Press Enter/ Send''


[[Category:Sample responses]]
#Stating what level the item is locked at lets other editors know if they have the ability to unlock it [it may be above their level too]
#Stating your current edit level is needed to know what level to unlock the item to
#Describing what you want to do helps open up discussions for possible learning sessions
#The location in the description tells editors if this request is in an area that they can edit
#By pressing send between sending the description and the actual PL, you create 2 separate 'bubbles' in GHO.

Latest revision as of 02:06, 4 June 2016

WME Extensions & Scripts:

Do you use any Chrome Extensions or Scripts for WME yet?

Extensions and Scripts are designed to work with WME, and are incredibly powerful tools, that will make your editing time far more productive. Rather than spend countless hours scrolling around looking for something to 'fix', these tools will direct your attention to various parts of WME that MAY need attention.

Remember that these tools will identify items that POSSIBLY need attention. Not every issue identified is actually incorrect. It may actually be a configuration approved by Sr Editors as an exception to wiki guidance based on specific local conditions.

Extensions

All extensions are available at the Chrome Store. Simply view these in the Chrome Store, click to install them, and then do a browser refresh [press F5] when viewing WME to load the newly installed extensions.

NOTE: Remember that WME is designed for use with Chrome, so this page is about installing tools in Chrome, for use with WME. No information is available here for other browser options or tools used by them.

It is highly recommend that new editors start out with the following extensions:


TamperMonkey is a "script manager". It will allow you to install other useful scripts into WME for additional tools that you will use as you learn more about editing in WME.

An additional thought about extension vs script. For those that use the Google profile login on Chrome, any extensions that you have installed at your home device, will also load into a session on any other device [re: work, school, internet cafe]. Scripts on the other hand require you to install the scripts into TamperMonkey on each separate device.

Toolbox for example is offered as an extension and a script. It may be easier to use the extension as you will likely have the three listed above running 90% of your time in WME.

Scripts

Once you have TamperMonkey installed:

Look for the TamperMonkey icon in the upper right corner of Chrome, left click the icon, then select "Get new scripts..."

A new tab will open for TamperMonkey, and there is a listing of Userscript Sources. The most current versions of WME scripts are usually found on the "GreasyFork" site. Click on the link to open another tab for GreasyFork.

Once you get to the GreasyFork page, enter 'WME' in the search box and you should see a list of Scripts for WME

NOTE: Do not feel the need to install any/ all of them, until you are working on an issue where a specific script might be useful!

One script specifically useful for editors in NY, that works with the extension Validator, is WME Validator Localization for New York

Another useful script for new editors who want to process Update Requests [UR's], is WME UR-MP tracking. This can be a very powerful tool once you get familiar with it and adjust it to your editing style.

Tips & Suggestions

PermaLinks & Unlock Requests

An important part about the editing community is interacting with other editors that may have knowledge about the specific issue you are currently trying to resolve. New editors will also follow along with a group discussion, trying to expand their own knowledge.

PermaLinks [PL's] are used by editors, to link directly to some bit(s) of data in WME, when asking another editor for assistance.

For example an editor with level 2 [L2] access needs to connect a PLR to a level 3 [L3] segment. Once you create a PL to that L3 segment, you can send it to a L3 editor and request an 'unlock'.

It is very likely that several editors may click on a PL that is shared in any communication platform. There are however a few nuances about using PL's that an editor needs to keep in mind.

Producing Useful PLs

  • Centering Screen & Zoom Level

After all the segments to be included are selected, one very important step is to zoom out so you can see them all on the screen, and then center your view in WME on those selected segments.

Keep in mind that anything not centered and farther out than Zoom4 will usually fail to produce a functional PL, and will not open correctly in WME after being clicked on.

So save yourself some grief and remember to keep the screen at maximum of Zoom4 and centered and THEN create your PL!

  • Layer Data

As an editor you might work on Map Problems [MP's] and Speed cameras, and so you will have those layers turned on in WME.

Editors who are assisting you, as well as other editors trying to learn from the discussion, may not have MP's locally, or there are no Speed cameras in their area, so they would not normally have those layers turned on.

Any editor that clicks on a default PL that includes layer data, has the 'layers' settings changed in their local copy of the Waze Map Editor!

Active editors may click on dozens of PL's during a typical editing session in WME. Having to constantly reset layers in WME to your personal preferences is not only a waste of productive editing time, it simply gets frustrating after a while.

The default PL in WME looks like this:

https://www.waze.com/editor/?env=usa&lon=-77.44210&lat=43.09923&layers=1540&zoom=5&mapProblemFilter=0&mapUpdateRequestFilter=1&venueFilter=1&update_requestsFilter=true&problemsFilter=true&lo%20...%20ueFilter=0&apProblemFilter=0&segments=33958923

Toolbox upgrades WMEs single default 'blue' colored PL icon, into multiple 'red' colored icons, all used to create various types of PL's. Simply hover your mouse over each red icon, and a brief description of what type of PL will be created appears.

The red PL icon located farthest to the right, is the PL icon used most commonly by editors.

Toolbox also offers the ability to toggle the excess layers data on or off from the default PL, by simply pressing the 'Shift' key.

The Toolbox PL [No Layers mode] looks like this:

https://www.waze.com/editor/?env=usa&lon=-77.44210&lat=43.09923&zoom=5&lo%20...%20ueFilter=0&apProblemFilter=0&segments=33958923

NOTE: Waze recently altered the data built into PLs, and the current version of Toolbox does not completely strip away the excess layers data. Hopefully this will be corrected in a future update.

WME Simple Permalink is another script that will also produce a PL with all the extra layers data stripped away.

The WME Simple Permalink looks like this:

https://www.waze.com/editor/?env=usa&lon=-77.44210&lat=43.09923&zoom=5&segments=33958923

  • Mobile Editors

Often editors that are helping with 'unlock' requests, are accessing WME and the communication platform from a mobile device. They are very limited in what they can do in WME, and the typical smaller screens make doing any editing more challenging in general. They are also using cellular data, rather than 'unlimited' cable/ dsl connections.

When requesting assistance from such an editor, a PL created excluding the layer data is especially important. The extra map data is not needed for the unlock, so it only slows the WME page load, before the editor can actually do the unlock. That extra layer info also uses additional data on their cellular plan. Obviously we don't want to be a nuisance to the very people helping us!

Taking the mobile aspect one step further, it is often not possible to 'copy' a PL out of a single message 'bubble' in chat. Mobile devices usually only offer to copy the entire bubble. Some editors use mobile tools that they will paste the PL into. That extra step have to try to trim out words from the PL is an extra hassle for them.

Asking for the unlock

So after considering all the above information, what exactly do you do to use this PL you created?

Easy, go ask for an unlock!

  • Describe what you want - [locked level > your level, what you want to do, location of your request]:

L3 to L2, connect a PLR, Rochester

  • Send your request to the communication platform

Press Enter/ Send

  • Now paste your PL as a separate message

https://www.waze.com/editor/?env=usa&lon=-77.44210&lat=43.09923&zoom=5&segments=33958923

  • Send your PL

Press Enter/ Send

  1. Stating what level the item is locked at lets other editors know if they have the ability to unlock it [it may be above their level too]
  2. Stating your current edit level is needed to know what level to unlock the item to
  3. Describing what you want to do helps open up discussions for possible learning sessions
  4. The location in the description tells editors if this request is in an area that they can edit
  5. By pressing send between sending the description and the actual PL, you create 2 separate 'bubbles' in GHO.