[Script] WME Validator 1.1.20 / 03.11.2016

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: Unholy, bextein

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.

drivable segment has a very acute turn

Postby dbraughlr » Thu Mar 13, 2014 2:34 pm

A bowtie U-turn is not too sharp. These turns probably can be detected as a turn from a one-way street to a one-way street with the same or similar name.

Spreading the nodes can lead to an incorrect "stay right" instruction for traffic continuing straight through the intersection or missing road reports for drivers making the U-turn.
dbraughlr
 
Posts: 569
Joined: Tue Aug 13, 2013 2:24 am
Has thanked: 164 times
Been thanked: 98 times

Dogbone roundabouts

Postby ditchi56 » Fri May 30, 2014 8:57 am

Can you devise a way of stopping Validator complaining about junctions like this?

Or alternatively a better way of mapping it, but routing and instructions are fine this way?
ditchi56
Country Manager
Country Manager
 
Posts: 5002
Joined: Tue May 29, 2012 12:35 pm
Has thanked: 1131 times
Been thanked: 2097 times

Custom Checks Examples

Postby berestovskyy » Wed Apr 09, 2014 9:28 pm

Custom Checks Examples
Custom check is a powerful tool of WME Validator to highlight very specific map issues, not covered with built-in validations.

To set up a custom check in Validator click Settings->custom. There are two checks: green and blue. Each check has two fields: template and regular expression (RegExp).

Hover your mouse over the template field to get a tooltip with available variables. Validator substitutes those variables with segment's data and then tries to match that string over the RegExp. If the expanded template string matches the RegExp - Validator highlights the segment.

Template Variables
Most of the variables are self-explanatory.
Note: empty address fields expand to empty streets, i.e. if you set "None" next to city name, then template "#${city}#" for this segment will be expanded to "##"

Road type: variable ${typeRank} expands to:
1 for Runways
2 for Railroads
...
14 for Major Highways
15 for Freeways

Road direction: variable ${direction} expands to:
0 for Unknown direction
1 for A->B
2 for B->A
3 for Two-way segments


Regular Expressions (RegExp)
Regular expressions are patterns used to match character combinations in your expanded template. See the detailed description of regular expressions on MDN: link

Validator provides the following two extensions for regular expressions:
Debug RegExp. To debug your RegExp add letter D at the very beginning: D/^[a-z]/
Validator will print debug information to the JavaScript console (Ctrl+Shift+J), so you can see how template variables expand for the segments on the map.

Negate RegExp. Sometimes it's much easier to create a RegExp for a normal condition and then just negate the result. To do so, add an exclamation mark at the very beginning: !/ (St|Ave)$/


Easy Examples
To highlight streets with word North
Template: ${street}
RegExp: /North/

To highlight invalid (null) elevations
Template: ${elevation}
RegExp: /null/

To highlight segments with no state assigned
Template: ${state}
RexExp: /^$/

To highlight segments with a U-turn
Template: ${Uturn}
RexExp: /1/


Medium Examples
To highlight Ramps with non-ground elevation:
Template: ${typeRank}:${elevation}
RegExp: /12:[^0]/

To highlight Freeways which do not start with letter A
Template: ${typeRank}:${street}
RegExp: /15:[^A]/

To highlight streets named "U-Turn" in LA
Template: ${state}:${street}
RegExp: /Louisiana:U-Turn/

To highlight dead-end U-turns
Template: ${deadEnd}:${Uturn}
RegExp: /1:1/

To highlight the opposite: missing dead-end U-turns
Template: ${deadEnd}:${Uturn}
RegExp: /1:0/

New! To highlight Freeways or Major Highways in format 'Axx', 'Ixx' etc
Template: ${typeRank}:${street}
RegExp: /^(15|14):[a-z][0-9]/i

New! To search for segments shorter than 17m:
Template: ${length}
RegExp: /^([0-9]|1[0-6])$/

New! To mark dead-ends without U-turn:
Template: A${deadEndA}:${UturnA}:B${deadEndB}:${UturnB}
RegExp: /A1:0|B1:0/

New! To highlight more than 100m long unnamed drivable streets:
Template: ${drivable}:${street}:${length}
RegExp: /1::...+/


Advanced Examples
To highlight street name which ends in Cntr, or Exd etc (any case variant)
Template: ${street}
RegExp: / (Cntr|Exd|La|Plc|Rvr|Tnpk|Wy)$/i

To highlight segments that have an alt street specified but no city
Template: @@${altCity[0]}##${altStreet[0]}@@${altCity[1]}##${altStreet[1]}
RegExp: /@@##[^@]/

To highlight invalid abbreviations for Australian roads
Template: ${street}
RegExp: !/ (Ave|Blvd|Cl|Cres|Cct|Ct|Dr|Way|Line|Ln|Mtwy|Pde|Pl|Rd|St)$|^$/

To highlight lowercase street names for US (except S, N, W, E and to)
Template: ${street}
RegExp: /^(?!(to) [^a-z])((S|N|W|E) )?[a-z]/

New! To highlight Freeways with no cardinal direction (NSEW)
Template: ${type}:${street}
RegExp: !/^[^3]| [NSEW]$/

New! City name abbreviation 'snt' should be lowercase and at the very beginning
Template: ${city}
RegExp: /(^|[ (])(?!^snt )[Ss][Nn][Tt]([ )]|$)/

New! To highlight segments if primary street name and one of the alt. names are the same
Template: #${street}#${altStreet[#]}#
RegExp: /(#.+)(?=#).*\1#/


See more examples in the "WME Validator localization for US" forum thread.
Last edited by berestovskyy on Fri Aug 08, 2014 11:34 pm, edited 15 times in total.
berestovskyy
 
Posts: 839
Joined: Fri Jul 15, 2011 1:50 pm
Has thanked: 259 times
Been thanked: 713 times

Complete List of Checks

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

Complete List of Checks for v1.1.1
See Settings->About->Available checks

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

There are 117 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:
    Code: Select all
    "101.params": {
      // {string} regular expression to match closed road
      "regexp": "/(^|\\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: ES, FR, IL, IT, PL

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

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

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

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

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

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

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

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

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

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

  • 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, IE, !LU, !NL
    Params to configure in localization pack:
    Code: Select all
    "160.params": {
      // {string} regular expression to match incorrect Freeway name
      "regexp": "!/^[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: IE, NL, PL
    Params to configure in localization pack:
    Code: Select all
    "161.params": {
      // {string} regular expression to match incorrect Major Highway name
      "regexp": "!/^[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: IE, NL, PL
    Params to configure in localization pack:
    Code: Select all
    "162.params": {
      // {string} regular expression to match incorrect Minor Highway name
      "regexp": "!/^[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:
    Code: Select all
    "164.params": {
      // {string} regular expression to match incorrect Primary Street name
      "regexp": "!/^[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:
    Code: Select all
    "163.params": {
      // {string} regular expression to match incorrect Ramp name
      "regexp": "!/^[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:
    Code: Select all
    "191.params": {
      // {string} regular expression to match incorrect abbreviations
      "regexp": "/\\./",
    },

  • 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:
    Code: Select all
    "171.params": {
      // {string} regular expression to match incorrect abbreviations
      "regexp": "/\\.$/",
    },

  • 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:
    Code: Select all
    "169.params": {
      // {string} regular expression to match incorrect street name
      "regexp": "!/^[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:
    Code: Select all
    "190.params": {
      // {string} regular expression to match a lowercase city name
      "regexp": "/^[a-zа-яёіїєґ]/",
    },

  • Lowercase street name (#170)
    The street name starts with a lowercase word.
    Correct lettercase in the street name.
    For countries: CL, CZ, ES, FR, IT, SK, US
    Params to configure in localization pack:
    Code: Select all
    "170.params": {
      // {string} regular expression to match a lowercase name
      "regexp": "/^[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: IE, NL

  • 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: IE, NL

  • 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: !DE, !ES, !FR, !IL, *

  • 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, !IL, *

  • 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, !IL, *

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

  • 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:
    Code: Select all
    "174.params": {
      // {string} regular expression to match spelling mistakes
      "regexp": "/(^|\\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:
    Code: Select all
    "112.params": {
      // {number} maximum Ramp name length
      "n": 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:
    Code: Select all
    "109.params": {
      // {number} minimum segment length
      "n": 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, CH, CZ, DE, ES, IL, IT, SK, 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: !*

  • 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: AT, AU, CH, CL, DE, ES, FR, IL, IT, PL

  • 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, ES, FR, IL, PL, SK, 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, CH, DE

  • 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:
    Code: Select all
    "166.params": {
      // {string} regular expression to match incorrect Parking Lot Road name
      "regexp": "!/^[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:
    Code: Select all
    "167.params": {
      // {string} regular expression to match incorrect Railroad name
      "regexp": "!/^[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:
    Code: Select all
    "165.params": {
      // {string} regular expression to match incorrect Street name
      "regexp": "!/^[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: AR, AT, AU, BE, BN, CH, CL, CZ, DE, IT, MY, SG, SK, US
    Params to configure in localization pack:
    Code: Select all
    "150.params": {
      // {number} minimum lock level
      "n": 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:
    Code: Select all
    "151.params": {
      // {number} minimum lock level
      "n": 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:
    Code: Select all
    "152.params": {
      // {number} minimum lock level
      "n": 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:
    Code: Select all
    "154.params": {
      // {number} minimum lock level
      "n": 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:
    Code: Select all
    "153.params": {
      // {number} minimum lock level
      "n": 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: !ES, !FR, !IL, *

  • 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: !IL, *

  • 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: !IL, *

  • 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, PL, SK
    Params to configure in localization pack:
    Code: Select all
    "52.params": {
      // {number} maximum street name length
      "n": 30,
    },

  • 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, ES, MY, PL, SG, SK
    Params to configure in localization pack:
    Code: Select all
    "73.params": {
      // {number} minimum street name length
      "n": 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 Sun Apr 27, 2014 3:28 pm, edited 22 times in total.
berestovskyy
 
Posts: 839
Joined: Fri Jul 15, 2011 1:50 pm
Has thanked: 259 times
Been thanked: 713 times

Bug fix request

Postby ditchi56 » Sat May 17, 2014 10:21 am

Bug fix request:

For error 114 "The non-drivable segment makes a junction with a drivable at node A" the Wiki link needs to change from:
https://wiki.waze.com/wiki/Road_Types_% ... n-drivable
to
https://wiki.waze.com/wiki/Road_Types_% ... able_roads

Many thanks for this invaluable script.
ditchi56
Country Manager
Country Manager
 
Posts: 5002
Joined: Tue May 29, 2012 12:35 pm
Has thanked: 1131 times
Been thanked: 2097 times

arbitrary rules are seen as gospel by majority of editors

Postby dbraughlr » Mon Feb 03, 2014 6:14 pm

sketch wrote:Remember that a lot of the checks in Validator are not necessarily wrong, they're just things that might need a look.
...
I'll reiterate the point I made, that many of these are just checks. Not everything needs action.


In practice, you are mistaken. There are many editors that expect the Validator to give their area a clean bill of health. Come to chat and talk to them. Editors have been deleting the loops flagged with "Same endpoints drivable segments" error. I recommended installing the updated Validator instead.

Any arbitrary "rules" like this should be turned off by default, clearly marked as informational when turned on, and marked with green or some color never used for errors.
Last edited by dbraughlr on Mon Feb 03, 2014 6:18 pm, edited 2 times in total.
dbraughlr
 
Posts: 569
Joined: Tue Aug 13, 2013 2:24 am
Has thanked: 164 times
Been thanked: 98 times

"Might be Incorrect City Name" Check Explained

Postby berestovskyy » Sat Jan 11, 2014 1:36 pm

"Might be Incorrect City Name" Check Explained
The check looks for two similar city names and reports BOTH of them with a special LIMIT assigned to each of the cities.

If number of the city segments exceeds the LIMIT, the Validator DOES NOT report the city segments.

The check recognizes the following cases:

  1. City name is too short - the city name is 1 or 2 letter long, please check if it is correct.
    There is no limit for this case.

  2. Expand the abbreviation - there are two similar cities around and one of them has an abbreviation.
    Example: "Poreba Wlk." vs "Poreba Wielka"
    Limits: 1000 and 10

  3. Complete short name - the city name is 1 or 2 letter long and it is a beginning of another city name.
    Example: "Kr" vs "Kraków"
    Limits: 1000 and 0

  4. Complete city name - one city name starts with another city name.
    Example: "Cheseaux" vs "Cheseaux-sur-Lausanne"
    Limits: 1000 and 10

  5. Correct letter case - the city names have different letter cases.
    Example: "kraków" vs "Kraków"
    Limits: 1000 and 10

  6. Check word order - the city names have different word order.
    Example: "Wielka Poręba" vs "Poręba Wielka"
    Limits: 1000 and 1000

  7. Check abbreviations - the city names have different abbreviations.
    Example: "Poręba Wlk." vs "Poręba Wiel."
    Limits: 1000 and 1000

  8. Add/remove county name - one of the cities has a county name in brackets or after a comma.
    Example: "Forel" vs "Forel (Lavaux)" OR "Forel" vs "Forel, Lavaux"
    Limits: 1000 and 10

  9. Check county name - city names are identical, but have different county names in brackets or after a comma.
    Example: "City (county1)" vs "City (county2)" OR "City, county1" vs "City, county2"
    Limits: 1000 and 1000

  10. Add/remove a word - one city name has an extra word in comparison with another.
    Example: "Amsterdam" vs "Amsterdam Zuidoost"
    Limits: 10 and 10

  11. Add county code - one city name has an extra 2-letter word in comparison with another.
    Example: "Renens" vs "Renens VD"
    Limits: 1000 and 10

  12. Identical names, but different city IDs - city names are identical, but have different internal city IDs.
    Example: "Syracuse (ID: 14696)" vs "Syracuse (ID: 53882)"
    Limits: 50 and 50

  13. Add/remove a space - one city name has a space, while another does not.
    Example: "De Witt" vs "Dewitt"
    Limits: 10 and 1000

  14. Check the number - city names contain different numbers.
    Example: "Строитель снт (Волжский)" vs "Строитель 2 снт (Среднеахтубинский р-н)"
    Limits: 1 and 1

The rename a city please use this form: forum post

Real World Example #1:
Report source: Lausanne (CH)
(permalinks are removed for the sake of brevity)

Bussigny - consider this city name: Bussigny-près-Lausanne [complete city name]
Chemin de Bellevue, Bussigny 146025417...

Carrouge (VD) - consider this city name: Carrouge VD [add county code]
Chemin de la Louchyre, Carrouge (VD) 149237200...

Cheseaux - consider this city name: Cheseaux-sur-Lausanne [complete city name]
No Street, Cheseaux 205419380

Colombier (VD) - consider this city name: Colombier VD [add county code]
No Street, Colombier (VD) 233568439...

Ecublens - consider this city name: Ecublens VD [add county code]
Chemin de la Forêt, Ecublens 144397102...

Forel - consider this city name: Forel (Lavaux) [add county name]
Route de Vevey, Forel 148818565...

Mézières (VD) - consider this city name: Mézières VD [add county code]
Chemin des Grottes, Mézières (VD) 149032735...

Vernand - consider this city name: Vernand-Dessous [complete city name]
Chemin du Stand, Vernand 151495416...


Real World Example #2:
Report source: Syracuse (US)
(permalinks are removed for the sake of brevity)

De - consider this city name: De Witt [complete short name]
No Street, De 72390902

De Witt - consider this city name: De Witt [same names 37530/56539]
Erie canal path, De Witt 75720153...

Dewitt - consider this city name: De Witt [add space]
Buffington Rd, Dewitt 34826253...

Greater Manlius Area - consider this city name: Greater Manlius Area [same names 38045/48105]
Medical Center Dr, Greater Manlius Area 69902463...

S - consider this city name: Syracuse [complete short name]
Overflow Lot, S 73135147

Syracuse - consider this city name: Syracuse [same names 14696/53882]
Audubon Pkwy, Syracuse 71544420...


Real World Example #3:
Report source: Київ (UA)
(permalinks are removed for the sake of brevity)

Білогородка - consider this city name: Білогородка (Києво-Святошинський) [add county name]
No Street, Білогородка 141798742...

Вишневе - consider this city name: Вишневе (Києво-Святошинський) [add county name]
Київська вулиця, Вишневе 141672076...

Петрівське - consider this city name: Петрівське (Вишневе) [add county name]
No Street, Петрівське 207331188...

The rename a city please use this form: forum post

See also: Fixing "smudged" cities (wiki)
Last edited by berestovskyy on Sun Apr 27, 2014 6:14 am, edited 5 times in total.
berestovskyy
 
Posts: 839
Joined: Fri Jul 15, 2011 1:50 pm
Has thanked: 259 times
Been thanked: 713 times

[Script] WME Validator 1.1.6 / 06.01.2015

Postby SiewMeng98 » Fri Mar 06, 2015 6:58 am

It is the 15th day of our Chinese New Year and I would like to take this opportunity to thank the Development Team and those behind the scene that have put in so much effort and hard work to conjure up this 'WME Validator" Script for all those out there who are using it.

Do keep up the good work and Kudos to the team.
SiewMeng98
Map Raider
Map Raider
 
Posts: 70
Joined: Sat Aug 02, 2014 5:28 pm
Has thanked: 25 times
Been thanked: 71 times

[Script] WME Validator 1.1.4 / 07.11.2014

Postby SiewMeng98 » Sat Dec 20, 2014 9:54 am

Despite having several bugs which can be resolved over time - Let's take this opportunity to thank every one on the team who have given us this magnificent tool to enhance our editing (by showing the errors).

Thanks for all the effort put in by the Great Team behind this - Merry Christmas and a Happry New Year Ahead.
SiewMeng98
Map Raider
Map Raider
 
Posts: 70
Joined: Sat Aug 02, 2014 5:28 pm
Has thanked: 25 times
Been thanked: 71 times

[Script] WME Validator 1.1.4 / 07.11.2014

Postby SiewMeng98 » Sat Dec 06, 2014 4:43 am

In Malaysia most of us is facing the same problem - shows an unneeded node but when we click on the segment it returns to normal.
SiewMeng98
Map Raider
Map Raider
 
Posts: 70
Joined: Sat Aug 02, 2014 5:28 pm
Has thanked: 25 times
Been thanked: 71 times

PreviousNext

Return to Addons, Extensions, and Scripts

Who is online

Users browsing this forum: No registered users