User:ShadowMasterCM

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 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:

• Validator
• Toolbox
• Tampermonkey

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 should open for TamperMonkey, and on there is a listing of User Script 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

Tips & Suggestions

• PermaLinks

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.

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

It is very likely that several people may click on any PermaLinks [PL's] that you share in any communication platform.

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'.

• Layer Data

There are however a few nuances about using PLs, specifically relating to the 'layers' data included in the default PL from WME.

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

The editor learning from or assisting you, 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.

Anyone editor that clicks a default PL including layers, has the 'layers' settings changed in their local browser.

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 preferences is not only a waste of productive editing time, it simply gets frustrating after a while.

Toolbox upgrades the default 'blue' colored PL creation icon, by adding multiple 'red' colored icons, used to create various types of PL's. Hover your mouse over each icon and a brief description of what type of PL will be created will appear.

The PL icon farthest to the right, is the standard PL creation icon, used by most editors. However, Toolbox also offers the ability to toggle the 'layers' data on or off from the default PL, by simply pressing the 'Shift' key.

The default PL in WME looks like this:

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

The toolbox PL [excluding the layers data] 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 'high speed' cable/ dsl connections.

When requesting assistance from such an editor, a PL created with out 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 bandwidth on their cellular data plan. Obviously we don't want to be a nuisance to the very people helping us!

Taking the mobile aspect one tip further, in regards to smaller device screens. It is often difficult to select a PL from between other comments. It is easier to click the PL when it is sent separate from your actual request for assistance, because it will place it in its own text 'bubble' on the other editors screen.

So try to follow this simple procedure when sharing a PL:

• 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 and send that 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

Standard Responses:

Standard Responses [SR's] are used when working with Update Requests [UR's] in the Waze Map Editor [WME].

These SR's are intended to offer general guidance to help editor's effectively communicate with Waze reporters in a productive manner. Please remember to keep this excellent guidance in mind when ever working with UR's.

There are also scripts available like UR Comments that can automate the process of replying to UR's.

Please feel free to modify any of these to fit your specific situations.

Greeting

When to use: Used to start the conversation with a Waze app user, in the UR that contains "No comments yet", as well as those UR's with little detail about the issue.

• Thanks for the report! Can you provide specific information about this error?

Reminder

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.

• 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.

No Response/ Closing

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'.

• No recent activity - No new information - Closing 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!

Address Request

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.

• Can I ask what your destination address was? I would like to try to replicate this error.

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.

Issue Solved

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.

• 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!

Restrictions [Weight/Height/Width/Vehicle Type]

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.

• 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! Please 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.

No Solution/ Closing

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!