[Script] WME Validator 0.9.8 (BETA) / 15.04.2014

Discussion for the unofficial, community-developed addons, extensions and scripts built for the Waze Map Editor.

The official index of these tools is the Community Plugins, Extensions and Tools wiki page.

Moderators: krankyd, Unholy

Forum rules
Discussion for the unofficial, community-developed addons, extensions and scripts built for the Waze Map Editor.

DO NOT START a new thread unless it is about a new idea. Keep discussion of existing tools within the main thread for that tool.

The official index of these tools is the Community Plugins, Extensions and Tools wiki page.

Re: [Script] WME Validator 0.4.4 (BETA) / 09.01.2014

Postby berestovskyy » Thu Jan 09, 2014 12:47 pm

Hi!
Validator v0.4.4 just published. I tried to address all of the reported issues/suggestions:
- New filter options: "Exclude Streets and Service Roads" and "Exclude Other drivable and Non-drivable".
- Ghost highlighting of turns and Toolbox fixed.
- All filter options are saved across sessions, but the settings - just "Enable sounds" and "Highlight issues".
- Validator still reports, but does not highlight WCH highlighted segments anymore.
- Since I guess nobody is using "Exclude highways", the option has been removed.
berestovskyy
Beta tester
Beta tester
 
Posts: 827
Joined: Fri Jul 15, 2011 1:50 pm
Has thanked: 165 times
Been thanked: 394 times

WME Validator Localization Packages

Postby berestovskyy » Thu Jan 09, 2014 2:08 pm

Validator Localization Packages

What is localization package?
Localization package is a script that tunes Validator up for your country. The script can enable/disable checks, set params and exceptions, translate user interface and messages.

There are two types of localization packages:
1. Built-in or default packages (come bundled with Validator).

2. External or user packages (the subject of this document):
a) user packages with params and translations
b) user packages just with params

User packages have higher priority, so they can override default options.


How to create a localization package?
1. Position WME over your country.

2. Switch WME to your language to get options and translations
or switch WME to "English" to get a package just with options.

3. Make sure any previous version of your script is ENABLED.

4. Prepare your country ISO Alpha-2 country code: list of codes (example: ES)

5. In Validator click Settings->About->(magic wand) and answer the questions if any.

6. The generated package is a Greasemonkey/Tampermonkey script ready for installation.
Copy and paste it into a new .user.js file or directly paste into the Greasemonkey/Tampermonkey.
Example filename: Validator-Spain.user.js


How to tune up/translate the package?
1. Open the .user.js file in a text editor. You can create a Google document and share the file among few editors/translators.

2. Search (Ctrl+F) for string "TODO:" and translate/check the marked strings. Please also remove the "TODO" marker. Example:
Code: Select all
"report.link.forum": "TODO: forum", -> "report.link.forum": "foro",


3. To enable a check, add/change the following line:
Code: Select all
"101.enabled": true,

To disable the check:
Code: Select all
"101.enabled": false,


4. For some checks you can also set params. Have a look at the complete list of validations for the list of params and their description: forum link

For example, to create a custom check 'Street name with a dot (excluding Ramps)', add the following lines:
Code: Select all
"130.enabled": true,
"130.severity": "warning",
"130.params": {
    "titleEN": "Street name with a dot",
    "problemEN": "There is a dot in the street name (excluding Ramps)",
    "solutionEN": "Expand the abbreviation or remove the dot",
    "template": "${type}:${street}",
    "regexp": "D/^[^4][0-9]?:.*\\./",
},

*Note: use D at the beginning of RegExp to enable debugging on JS console.
*Note: do not forget to escape backslashes in strings, i.e. use "\\" instead of "\".


How to install the package?
The Wizard generates Greasemonkey/Tampermonkey script ready for installation.
You can copy and paste it directly into the Greasemonkey/Tampermonkey.

To add the script in Chrome/Tampermonkey:
Install Tampermonkey for Chrome: Web Store
a) copy your script to the clipboard (Ctrl+C)
b) click Tampermonkey icon in Chrome
c) from the drop-down menu select "Add a new script"
d) in the script editor select all (Ctrl+A) and paste your script instead (Ctrl+V)
e) click "Save" (not "Save to disc")

To add the script in Firefox/Greasemonkey:
Install Greasemonkey for Firefox: Add-Ons
a) copy your script to the clipboard (Ctrl+C)
b) click Greasemonkey icon in Firefox
c) from the drop-down menu select "New user script"
d) click "Use script from clipboard" button
e) click "Save"

Reload the page, click Tampermonkey/Greasemonkey icon and make sure your script is there.


How to distribute the package?
The generated package is a Greasemonkey/Tampermonkey script ready for installation. There are two ways to distribute your localization package:

1. Your local community maintain/distribute the package. Let me know when your package is ready, so I put a link to your package on the Validator main page.
So you need two scripts installed: "Validator" and "Validator for your country".

2. Alternatively, on your request I can import the whole package back into the Validator. So your package becomes a default built-in package bundled with Validator.


How to update the package?
1. It is OK if Validator version does not match your localization pack version. In case your localization package miss a string or an option, Validator will use english strings/default options instead.

2. Make sure the previous version of your script is installed and enabled, so you see your translations.

3. In Validator click Settings->About->Wizard, answer the questions if any and generate updated localization pack.

Note that all your translations will be preserved in this updated script and all new/changed strings will be marked with "TODO".

See "How to create a localization package?" section above for more details.
Last edited by berestovskyy on Tue Apr 08, 2014 7:57 pm, edited 8 times in total.
berestovskyy
Beta tester
Beta tester
 
Posts: 827
Joined: Fri Jul 15, 2011 1:50 pm
Has thanked: 165 times
Been thanked: 394 times

Re: [Script] WME Validator 0.4.4 (BETA) / 09.01.2014

Postby berestovskyy » Thu Jan 09, 2014 6:12 pm

BellHouse wrote:If so, I would suggest to move that checkbox to the front page of the Validator. In basemap areas the flashing segments can be quite annoying. ;)

Done, will be available in the next release.

SuperDave1426 wrote:I'd like to request an option to turn that off.

It's disabled for US.

SuperDave1426 wrote:An additional note, not related to the above: I've got some interchanges that look like this:

It's a beta check, just ignore it at the moment.
berestovskyy
Beta tester
Beta tester
 
Posts: 827
Joined: Fri Jul 15, 2011 1:50 pm
Has thanked: 165 times
Been thanked: 394 times

Re: [Script] WME Validator 0.4.4 (BETA) / 09.01.2014

Postby berestovskyy » Thu Jan 09, 2014 8:45 pm

SuperDave1426 wrote:It would be nice if there were an option under settings that was something along the lines of

[ ] Report freeway segments locked under rank ____

Where you can check the option in the beginning, and put the numeric value you want to know about at the end of the line like that. Or something similar. :-)

An option just for one of dozens of checks is too much for the user interface :lol:

But I got your idea, so instead I propose a global "Strict mode" switch. It will simply switch on/off some checks. For instance, there are already two very similar checks:
1. "Incorrect lock level/The Freeway segment is not locked to Lvl 5"
2. "No lock on Freeway/The Freeway is not locked"

So the first check might be active for US in a strict mode, while the latter might be activated in non-strict mode, like this:

1. "Incorrect lock level/The Freeway segment is not locked to Lvl 5"
Countries (strict mode): US, AU, BE...
Countries (non-strict mode): AU, BE... (no US here)

2. "No lock on Freeway/The Freeway is not locked"
Countries (strict mode): BN, MY, SG
Countries (non-strict mode): US, BN, MY, SG... (US is here)
berestovskyy
Beta tester
Beta tester
 
Posts: 827
Joined: Fri Jul 15, 2011 1:50 pm
Has thanked: 165 times
Been thanked: 394 times

Re: [Script] WME Validator 0.4.4 (BETA) / 09.01.2014

Postby berestovskyy » Thu Jan 09, 2014 8:51 pm

arbaot wrote:there is a typo in the report
Filter: duplicate segments, non-drivables and streets, non-editable segments and mjnor issues are excluded from this report.

Thanks!
Please force update the script, it's fixed in the latest 0.4.4
berestovskyy
Beta tester
Beta tester
 
Posts: 827
Joined: Fri Jul 15, 2011 1:50 pm
Has thanked: 165 times
Been thanked: 394 times

Re: [Script] WME Validator 0.4.4 (BETA) / 09.01.2014

Postby berestovskyy » Thu Jan 09, 2014 9:27 pm

AlanOfTheBerg wrote:Unless they are local light-rail stuff.

If there is a list of non-local railroads, we can add them as a condition, i.e.
Code: Select all
IF there is a city name
  AND street name is one of the list OR contains one of the keywords
THEN report the railroad segment
berestovskyy
Beta tester
Beta tester
 
Posts: 827
Joined: Fri Jul 15, 2011 1:50 pm
Has thanked: 165 times
Been thanked: 394 times

Re: [Script] WME Validator 0.4.5 (BETA) / 10.01.2014

Postby berestovskyy » Fri Jan 10, 2014 12:37 pm

10.01.2014 v0.4.5:
- fixed "Street name with no space before/after" for "Dr.-Herbert"
- to switch highlighting on/off just click on the "Validator" title
- fixed CSS styles for links
- removed "Zoom" and "Step" advanced options
- other minor changes
berestovskyy
Beta tester
Beta tester
 
Posts: 827
Joined: Fri Jul 15, 2011 1:50 pm
Has thanked: 165 times
Been thanked: 394 times

Re: [Script] WME Validator 0.4.5 (BETA) / 10.01.2014

Postby berestovskyy » Fri Jan 10, 2014 5:32 pm

ditchi56 wrote:When I try, I get a message: "Sorry, You cannot use WME Validator over here. Please check the forum thread for more information."

Sorry, at the moment Validator is being reviewed by the UK country managers. I hope it will be available soon for every editor in UK. Follow the thread for the announcement.

Thanks!
berestovskyy
Beta tester
Beta tester
 
Posts: 827
Joined: Fri Jul 15, 2011 1:50 pm
Has thanked: 165 times
Been thanked: 394 times

Re: [Script] WME Validator 0.4.5 (BETA) / 10.01.2014

Postby berestovskyy » Fri Jan 10, 2014 8:48 pm

arbaot wrote:I think check for WMETB: Simple segment shouldn't ignore roundabout segments

It's a segment highlighted by WME Toolbox (WMETB). If WME Toolbox does not highlight roundabouts, there is nothing I can do about at the moment. You should report the issue in the corresponding Toolbox thread.

If Toolbox is highlighting simple roundabout segment, but Validator does not report/highlight it - please give me a permalink to check the issue.
berestovskyy
Beta tester
Beta tester
 
Posts: 827
Joined: Fri Jul 15, 2011 1:50 pm
Has thanked: 165 times
Been thanked: 394 times

Complete List of Checks

Postby berestovskyy » Sat Jan 11, 2014 7:31 am

Complete List of Checks for v0.9.8
See Settings->About->Available checks

Localization Fallback Rules:
Argentina (AR) → Spain (ES)
Netherlands (NL) → Belgium (BE)
Luxembourg (LU) → Belgium (BE)
Chile (CL) → Spain (ES)

There are 112 checks available:

  • User-defined custom check (green) (#128)
    Some of the segment properties matched against the user-defined regular expression (see Settings→Custom): link
    Solve the issue.
    For countries: *

  • User-defined custom check (blue) (#129)
    Some of the segment properties matched against the user-defined regular expression (see Settings→Custom): link
    Solve the issue.
    For countries: *

  • Closed road (only available in the report) (#101)
    The segment is marked as closed: wiki
    If the construction is done, restore the segment connectivity and remove the suffix: wiki
    For countries: !ES, *
    Params to configure in localization pack:
    • regexp - {string} regular expression to match closed road. Default is "/(^|\\b)closed(\\b|$)/i"

  • No connectivity on roundabout (slow) (#50)
    The drivable roundabout segment has no connectivity with adjacent roundabout segment.
    Enable a turn to the adjacent segment or redo the roundabout: wiki
    For countries: *

  • No inward connectivity (#45)
    The drivable non-private segment has no single inward turn enabled.
    Select an adjacent segment and enable at least one turn to the segment: wiki
    For countries: *

  • No outward connectivity (#44)
    The drivable segment has no single outward turn enabled.
    Enable at least one outward turn from the segment: wiki
    For countries: *

  • Node A: Multiple outgoing segments at roundabout (#87)
    The drivable roundabout node A has more than one outgoing segment connected: wiki
    Redo the roundabout: wiki
    For countries: *

  • Node A: No connection (slow) (#107)
    The node A of the drivable segment is within 5m from another drivable segment but not connected by a junction.
    Drag the node A to the nearby segment so that it touches or move it a bit further away.
    For countries: *

  • Node A: Overlapping segments (slow) (#118)
    The segment is overlapping with the adjacent segment at node A.
    Spread the segments at 2° or delete unneeded geometry point or delete the duplicate segment at node A.
    For countries: *

  • Node B: No connection (slow) (#108)
    The node B of the drivable segment is within 5m from another drivable segment but not connected by a junction.
    Drag the node B to the nearby segment so that it touches or move it a bit further away.
    For countries: *

  • Node B: Overlapping segments (slow) (#119)
    The segment is overlapping with the adjacent segment at node B.
    Spread the segments at 2° or delete unneeded geometry point or delete the duplicate segment at node B.
    For countries: *

  • Self connectivity (#43)
    The segment is connected back to itself: wiki
    Split the segment into THREE pieces: wiki
    For countries: !DE, *

  • Two-way drivable roundabout segment (#48)
    The drivable roundabout segment is bidirectional.
    Redo the roundabout: wiki
    For countries: *

  • City name on named Ramp (#57)
    City name on the named Ramp may affect search results: forum
    In the address properties check the 'None' box next to the city name and then click 'Apply': wiki
    For countries: FR, IL, IT, PL, ES

  • Custom check (#130)
    The segment matched custom conditions.
    Solve the issue.
    For countries: DE
    Params to configure in localization pack:
    • template - {string} expandable template. Default is "${street}"
    • regexp - {string} regular expression to match the template. Default is "!/.+/"
    • titleEN - {string} English title. Default is ""
    • problemEN - {string} English problem description. Default is ""
    • solutionEN - {string} English solution instructions. Default is ""

  • Custom check (#131)
    The segment matched custom conditions.
    Solve the issue.
    For countries: !*
    Params to configure in localization pack:
    • template - {string} expandable template. Default is "${street}"
    • regexp - {string} regular expression to match the template. Default is "!/.+/"
    • titleEN - {string} English title. Default is ""
    • problemEN - {string} English problem description. Default is ""
    • solutionEN - {string} English solution instructions. Default is ""

  • Custom check (#132)
    The segment matched custom conditions.
    Solve the issue.
    For countries: !*
    Params to configure in localization pack:
    • template - {string} expandable template. Default is "${street}"
    • regexp - {string} regular expression to match the template. Default is "!/.+/"
    • titleEN - {string} English title. Default is ""
    • problemEN - {string} English problem description. Default is ""
    • solutionEN - {string} English solution instructions. Default is ""

  • Custom check (#133)
    The segment matched custom conditions.
    Solve the issue.
    For countries: !*
    Params to configure in localization pack:
    • template - {string} expandable template. Default is "${street}"
    • regexp - {string} regular expression to match the template. Default is "!/.+/"
    • titleEN - {string} English title. Default is ""
    • problemEN - {string} English problem description. Default is ""
    • solutionEN - {string} English solution instructions. Default is ""

  • Custom check (#134)
    The segment matched custom conditions.
    Solve the issue.
    For countries: !*
    Params to configure in localization pack:
    • template - {string} expandable template. Default is "${street}"
    • regexp - {string} regular expression to match the template. Default is "!/.+/"
    • titleEN - {string} English title. Default is ""
    • problemEN - {string} English problem description. Default is ""
    • solutionEN - {string} English solution instructions. Default is ""

  • Dead-end U-turn (#77)
    The drivable dead-end road has a U-turn enabled: wiki
    Disable U-turn.
    For countries: !IL, !RU, *

  • Empty street name (#175)
    The street name has only space characters or a dot.
    In the address properties check the 'None' box next to the street name, click 'Apply' OR set a proper street name: wiki
    For countries: *

  • Incorrect Freeway name (#160)
    The Freeway segment has incorrect street name.
    Rename the segment in accordance with the guidelines.
    For countries: BE, !NL, !LU, IE
    Params to configure in localization pack:
    • regexp - {string} regular expression to match incorrect Freeway name. Default is "!/^[AS][0-9]{1,2}/"

  • Incorrect Major Highway name (#161)
    The Major Highway segment has incorrect street name.
    Rename the segment in accordance with the guidelines.
    For countries: NL, IE, PL
    Params to configure in localization pack:
    • regexp - {string} regular expression to match incorrect Major Highway name. Default is "!/^[AS][0-9]{1,2}/"

  • Incorrect Minor Highway name (#162)
    The Minor Highway segment has incorrect street name.
    Rename the segment in accordance with the guidelines.
    For countries: NL, IE, PL
    Params to configure in localization pack:
    • regexp - {string} regular expression to match incorrect Minor Highway name. Default is "!/^[AS][0-9]{1,2}/"

  • Incorrect Primary Street name (#164)
    The Primary Street segment has incorrect street name.
    Rename the segment in accordance with the guidelines.
    For countries: !*
    Params to configure in localization pack:
    • regexp - {string} regular expression to match incorrect Primary Street name. Default is "!/^[AS][0-9]{1,2}/"

  • Incorrect Ramp name (#163)
    The Ramp segment has incorrect street name.
    Rename the segment in accordance with the guidelines.
    For countries: BE, FR, IT, PL
    Params to configure in localization pack:
    • regexp - {string} regular expression to match incorrect Ramp name. Default is "!/^[AS][0-9]{1,2}/"

  • Incorrectly abbreviated city name (#191)
    The city name has incorrect abbreviation.
    Use this form to rename the city: forum
    For countries: !*
    Params to configure in localization pack:
    • regexp - {string} regular expression to match incorrect abbreviations. Default is "/\\./"

  • Incorrectly abbreviated street name (#171)
    The street name has incorrect abbreviation.
    Check upper/lower case, a space before/after the abbreviation and the accordance with the abbreviation table.
    For countries: BE, FR, IL, PL, US
    Params to configure in localization pack:
    • regexp - {string} regular expression to match incorrect abbreviations. Default is "/\\.$/"

  • Incorrectly named street (#169)
    The street named incorrectly, illegal chars or words used.
    Rename the segment in accordance with the guidelines.
    For countries: AR, PL
    Params to configure in localization pack:
    • regexp - {string} regular expression to match incorrect street name. Default is "!/^[a-zA-Z0-9\\. :\"'(/)-]+$/"

  • Lowercase city name (#190)
    The city name starts with a lowercase letter.
    Use this form to rename the city: forum
    For countries: !IL, !RU, *
    Params to configure in localization pack:
    • regexp - {string} regular expression to match a lowercase city name. Default is "/^[a-z]/"

  • Lowercase street name (#170)
    The street name starts with a lowercase word.
    Correct lettercase in the street name.
    For countries: CL, CZ, FR, IT, SK, ES, US
    Params to configure in localization pack:
    • regexp - {string} regular expression to match a lowercase name. Default is "/^[a-z]/"

  • Might be incorrect city name (only available in the report) (#24)
    The segment might have incorrect city name: wiki
    Consider suggested city name and use this form to rename the city: forum
    For countries: *

  • Must be a Freeway (#70)
    This segment must be a Freeway.
    Set the road type to Freeway or change the road name.
    For countries: IE

  • Must be a Major Highway (#71)
    This segment must be a Major Highway.
    Set the road type to Major Highway or change the road name.
    For countries: NL, IE

  • Must be a Minor Highway (#72)
    This segment must be a Minor Highway.
    Set the road type to Minor Highway or change the road name.
    For countries: NL, IE

  • No space before/after street abbreviation (#173)
    No space before ('1943r.') or after ('st.Jan') an abbreviation in the street name.
    Add a space before/after the abbreviation.
    For countries: !FR, !DE, !IL, !ES, *

  • Node A: Multiple segments connected at roundabout (#74)
    The drivable roundabout node A has more than one segment connected: wiki
    Redo the roundabout: wiki
    For countries: *

  • Node A: No inward connectivity of drivable road (slow) (#46)
    The drivable non-private segment has no single inward turn enabled at node A.
    Select an adjacent segment and enable at least one turn to the segment at node A: wiki
    For countries: *

  • Node A: No outward connectivity of drivable road (slow) (#102)
    The drivable segment has no single outward turn enabled at node A.
    Enable at least one outward turn from the segment at node A: wiki
    For countries: *

  • Node A: Non-drivable connected to drivable (slow) (#114)
    The non-drivable segment makes a junction with a drivable at node A: wiki
    Disconnect node A from all of the drivable segments.
    For countries: !ES, *

  • Node A: Too sharp turn (slow) (#120)
    The drivable segment has a very acute turn at node A.
    Disable the sharp turn at node A or spread the segments at 30°.
    For countries: *

  • Node A: Unconfirmed turn on primary road (#201)
    The primary segment has an unconfirmed (soft) turn at node A: wiki
    Click the turn indicated with a purple question mark to confirm it. Note: you may need to make the segment 'Two-way' in order to see those turns: wiki
    For countries: *

  • Node B: No inward connectivity of drivable road (slow) (#47)
    The drivable non-private segment has no single inward turn enabled at node B.
    Select an adjacent segment and enable at least one turn to the segment at node B: wiki
    For countries: *

  • Node B: No outward connectivity of drivable road (slow) (#103)
    The drivable segment has no single outward turn enabled at node B.
    Enable at least one outward turn from the segment at node B: wiki
    For countries: *

  • Node B: Non-drivable connected to drivable (slow) (#115)
    The non-drivable segment makes a junction with a drivable at node B: wiki
    Disconnect node B from all of the drivable segments.
    For countries: !ES, *

  • Node B: Too sharp turn (slow) (#121)
    The drivable segment has a very acute turn at node B.
    Disable the sharp turn at node B or spread the segments at 30°.
    For countries: *

  • Node B: Unconfirmed turn on primary road (#301)
    The primary segment has an unconfirmed (soft) turn at node B: wiki
    Click the turn indicated with a purple question mark to confirm it. Note: you may need to make the segment 'Two-way' in order to see those turns: wiki
    For countries: *

  • Obsolete CONST ZN marker (#117)
    The segment is marked with obsolete CONST ZN suffix.
    Change CONST ZN to (closed): wiki
    For countries: !ES, *

  • Out of range elevation (#116)
    The segment elevation is out of range.
    Correct the elevation.
    For countries: *

  • Same endpoints drivable segments (slow) (#78)
    Two drivable segments share the same two endpoints: forum
    Split the segment. You might also remove one of the segments if they are identical: wiki
    For countries: !DE, *

  • Street name on roundabout (#29)
    In Waze, we do not name roundabout segments: wiki
    In the address properties check the 'None' box next to the street name, click 'Apply' and then add 'Junction' landmark to name the roundabout: wiki
    For countries: *

  • Street name on two-way Ramp (#28)
    If Ramp is unnamed, the name of a subsequent road will propagate backwards: wiki
    In the address properties check the 'None' box next to the street name and then click 'Apply': wiki
    For countries: *

  • Street name spelling mistake (#174)
    The is a spelling mistake in the street name.
    Add/correct the mistake, check accented letters.
    For countries: FR
    Params to configure in localization pack:
    • regexp - {string} regular expression to match spelling mistakes. Default is "/(^|\\b)(accross|cemetary|fourty|foward|goverment|independant|liason|pavillion|portugese|posession|prefered|shcool|wat|wich)($|\\b)/i"

  • Street name with a dot (#95)
    There is a dot in the street name (excluding Ramps).
    Expand the abbreviation or remove the dot.
    For countries: IT

  • Too long Ramp name (#112)
    The Ramp name is more than ${n} letters long.
    Shorten the Ramp name.
    For countries: !AU, !US, *
    Params to configure in localization pack:
    • n - {number} maximum Ramp name length. Default is 55

  • Too short segment (#109)
    The drivable non-terminal segment is less than ${n}m long so it is hard to see it on the map and it can cause routing problems: wiki
    Increase the length, or remove the segment, or join it with one of the adjacent segments: wiki
    For countries: *
    Params to configure in localization pack:
    • n - {number} minimum segment length. Default is 5

  • Too short U-turn connector (slow) (#79)
    The length of the segment is less than 15m long so U-turn is not possible here: wiki
    Increase the length of the segment.
    For countries: *

  • Two-way Freeway segment (#90)
    Most of the Freeways are split into two one-way roads, so this two-way segment might be a mistake.
    Check Freeway direction.
    For countries: AT, CZ, DE, IL, IT, SK, ES, CH, US

  • Two-way Ramp segment (#91)
    Most of the Ramps are one-way roads, so this two-way segment might be a mistake.
    Check Ramp direction.
    For countries: IL

  • U-turn at roundabout entrance (slow) (#99)
    The roundabout entrance segment has a U-turn enabled: wiki
    Disable U-turn.
    For countries: *

  • Unknown direction of drivable road (#25)
    'Unknown' road direction will not prevent routing on the road: wiki
    Set the road direction.
    For countries: *

  • Unterminated drivable road (#35)
    Waze will not route from the unterminated segment.
    Move the segment a bit so the terminating node will be added automatically.
    For countries: *

  • ██ WME Toolbox: Roundabout which may cause issues (#1)
    Junction IDs of the roundabout segments are not consecutive.
    Redo the roundabout: wiki
    For countries: !IL, !UK, *

  • City name on Freeway (#59)
    City name on the Freeway may cause a city smudge: wiki
    In the address properties check the 'None' box next to the city name and then click 'Apply': wiki
    For countries: AU, AT, CL, FR, DE, IL, IT, PL, ES, CH

  • City name on Railroad (#27)
    City name on the Railroad may cause a city smudge: wiki
    In the address properties check the 'None' box next to the city name and then click 'Apply': wiki
    For countries: AU, BG, CZ, FR, IL, PL, SK, ES, US

  • Empty alternate street (#34)
    Alternate street name is empty.
    Remove empty alternate street name.
    For countries: *

  • Expired segment restriction (slow) (#38)
    The segment has an expired restriction: wiki
    Click 'Edit restrictions' and delete the expired restriction.
    For countries: *

  • Expired turn restriction (slow) (#39)
    The segment has a turn with an expired restriction: wiki
    Click clock icon next to the yellow arrow and delete the expired restriction.
    For countries: *

  • Incorrect Freeway elevation (#110)
    The elevation of the Freeway segment is not a ground: wiki
    Set the Freeway elevation to ground.
    For countries: AT, DE, CH

  • Incorrect Parking Lot Road name (#166)
    The Parking Lot Road segment has incorrect street name.
    Rename the segment in accordance with the guidelines.
    For countries: !*
    Params to configure in localization pack:
    • regexp - {string} regular expression to match incorrect Parking Lot Road name. Default is "!/^[AS][0-9]{1,2}/"

  • Incorrect Railroad name (#167)
    The Railroad segment has incorrect street name.
    Rename the segment in accordance with the guidelines.
    For countries: PL
    Params to configure in localization pack:
    • regexp - {string} regular expression to match incorrect Railroad name. Default is "!/^[AS][0-9]{1,2}/"

  • Incorrect Street name (#165)
    The Street segment has incorrect street name.
    Rename the segment in accordance with the guidelines.
    For countries: !*
    Params to configure in localization pack:
    • regexp - {string} regular expression to match incorrect Street name. Default is "!/^[AS][0-9]{1,2}/"

  • No city name on Freeway (#69)
    The Freeway has no city name set.
    Set the city name.
    For countries: BN, MY, SG

  • No lock on Freeway (#150)
    The Freeway segment should be locked at least to Lvl ${n}.
    Lock the segment.
    For countries: AU, AT, BE, BN, CZ, DE, IT, MY, SG, SK, CH, US
    Params to configure in localization pack:
    • n - {number} minimum lock level. Default is 5

  • No lock on Major Highway (#151)
    The Major Highway segment should be locked at least to Lvl ${n}.
    Lock the segment.
    For countries: AU, BE, BN, CZ, IT, MY, SG, SK
    Params to configure in localization pack:
    • n - {number} minimum lock level. Default is 4

  • No lock on Minor Highway (#152)
    The Minor Highway segment should be locked at least to Lvl ${n}.
    Lock the segment.
    For countries: AU, BE, BN, CZ, IT, MY, SG, SK
    Params to configure in localization pack:
    • n - {number} minimum lock level. Default is 3

  • No lock on Primary Street (#154)
    The Primary Street segment should be locked at least to Lvl ${n}.
    Lock the segment.
    For countries: BE
    Params to configure in localization pack:
    • n - {number} minimum lock level. Default is 2

  • No lock on Ramp (#153)
    The Ramp segment should be locked at least to Lvl ${n}.
    Lock the segment.
    For countries: !*
    Params to configure in localization pack:
    • n - {number} minimum lock level. Default is 4

  • No space before/after city abbreviation (#193)
    No space before ('1943r.') or after ('st.Jan') an abbreviation in the city name.
    Use this form to rename the city: forum
    For countries: !FR, !IL, !ES, *

  • No state name selected (#106)
    The segment has no state name selected.
    Select a state for the segment and apply the changes: wiki
    For countries: US

  • Node A: Reverse connectivity of drivable road (#41)
    There is a turn which goes against the directionality of the segment at node A: wiki
    Make the segment 'Two-way', restrict all the turns at node A and then make the segment 'One way (A→B)' again.
    For countries: *

  • Node A: Unconfirmed turn on minor road (#200)
    The minor drivable segment has an unconfirmed (soft) turn at node A: wiki
    Click the turn indicated with a purple question mark to confirm it. Note: you may need to make the segment 'Two-way' in order to see those turns: wiki
    For countries: !CL, !IL, !UK, *

  • Node A: Unneeded (slow) (#36)
    Adjacent segments at node A are identical: wiki
    Select node A and press Delete key to join the segments: wiki
    For countries: *

  • Node B: Reverse connectivity of drivable road (#42)
    There is a turn which goes against the directionality of the segment at node B: wiki
    Make the segment 'Two-way', restrict all the turns at node B and then make the segment 'One way (B→A)' again.
    For countries: *

  • Node B: Unconfirmed turn on minor road (#300)
    The minor drivable segment has an unconfirmed (soft) turn at node B: wiki
    Click the turn indicated with a purple question mark to confirm it. Note: you may need to make the segment 'Two-way' in order to see those turns: wiki
    For countries: !CL, !IL, !UK, *

  • Node B: Unneeded (slow) (#37)
    Adjacent segments at node B are identical: wiki
    Select node B and press Delete key to join the segments: wiki
    For countries: *

  • Railroad used for comments (#104)
    The Railroad segment is probably used as a map comment: forum
    Remove the comment as Railroads will be added to the client display.
    For countries: *

  • Too long street name (#52)
    The name of the drivable segment is more than ${n} letters long and it is not a Ramp.
    Consider an abbreviation for the street name.
    For countries: CZ, IL, PL, SK
    Params to configure in localization pack:
    • n - {number} maximum street name length. Default is 25

  • Too short street name (#73)
    The street name is less than ${n} letters long and it is not a highway.
    Correct the street name.
    For countries: BN, CZ, MY, PL, SG, SK, ES
    Params to configure in localization pack:
    • n - {number} minimum street name length. Default is 3

  • Unconfirmed road (#23)
    Each segment must minimally have the Country and State information: wiki
    Confirm the road by updating its details: wiki
    For countries: *

  • Unneeded spaces in city name (#192)
    Leading/trailing/double space in the city name.
    Use this form to rename the city: forum
    For countries: *

  • Unneeded spaces in street name (#172)
    Leading/trailing/double space in the street name.
    Remove unneeded spaces from the street name.
    For countries: *

  • Walking Trail instead of a Railroad (#105)
    The Walking Trail segment with elevation -5 is probably used instead of a Railroad: forum
    Change road type to Railroad as Railroads will be added to the client display.
    For countries: CZ, PL

  • ██ WME Color Highlights: Editor lock (#13)
    The segment is highlighted by WME Color Highlights. It is not a problem: wiki
    For countries: *

  • ██ WME Color Highlights: Filter by city (#20)
    The segment is highlighted by WME Color Highlights. It is not a problem: wiki
    For countries: *

  • ██ WME Color Highlights: Filter by city (alt. city) (#21)
    The segment is highlighted by WME Color Highlights. It is not a problem: wiki
    For countries: *

  • ██ WME Color Highlights: Filter by editor (#22)
    The segment is highlighted by WME Color Highlights. It is not a problem: wiki
    For countries: *

  • ██ WME Color Highlights: No city (#17)
    The segment is highlighted by WME Color Highlights. It is not a problem: wiki
    For countries: *

  • ██ WME Color Highlights: No name (#19)
    The segment is highlighted by WME Color Highlights. It is not a problem: wiki
    For countries: *

  • ██ WME Color Highlights: Recently edited (#15)
    The segment is highlighted by WME Color Highlights. It is not a problem: wiki
    For countries: *

  • ██ WME Color Highlights: Road rank (#16)
    The segment is highlighted by WME Color Highlights. It is not a problem: wiki
    For countries: *

  • ██ WME Color Highlights: Time restriction / Highlighted road type (#18)
    The segment is highlighted by WME Color Highlights. It is not a problem: wiki
    For countries: *

  • ██ WME Color Highlights: Toll road / One way road (#14)
    The segment is highlighted by WME Color Highlights. It is not a problem: wiki
    For countries: *

  • ██ WME Toolbox: House numbers (#8)
    The segment is highlighted by WME Toolbox. It is not a problem: wiki
    For countries: *

  • ██ WME Toolbox: Lvl 2 lock (#3)
    The segment is highlighted by WME Toolbox. It is not a problem: wiki
    For countries: *

  • ██ WME Toolbox: Lvl 3 lock (#4)
    The segment is highlighted by WME Toolbox. It is not a problem: wiki
    For countries: *

  • ██ WME Toolbox: Lvl 4 lock (#5)
    The segment is highlighted by WME Toolbox. It is not a problem: wiki
    For countries: *

  • ██ WME Toolbox: Lvl 5 lock (#6)
    The segment is highlighted by WME Toolbox. It is not a problem: wiki
    For countries: *

  • ██ WME Toolbox: Lvl 6 lock (#7)
    The segment is highlighted by WME Toolbox. It is not a problem: wiki
    For countries: *

  • ██ WME Toolbox: Segment with time restrictions (#9)
    The segment is highlighted by WME Toolbox. It is not a problem: wiki
    For countries: *

  • ██ WME Toolbox: Simple segment (#2)
    The segment has unneeded geometry nodes: wiki
    Simplify segment geometry by hovering mouse pointer and pressing "d" key: wiki
    For countries: *
Last edited by berestovskyy on Sat Apr 19, 2014 7:52 am, edited 21 times in total.
berestovskyy
Beta tester
Beta tester
 
Posts: 827
Joined: Fri Jul 15, 2011 1:50 pm
Has thanked: 165 times
Been thanked: 394 times

PreviousNext

Return to Addons, Extensions, and Scripts

Who is online

Users browsing this forum: AndyPot2