waze.com

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

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)

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

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

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

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!

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.

Complete List of Checks for v2018.09.15
See Settings->About->Available checks

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

There are 124 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: *
  


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


• BETA: No public connection for public segment (slow) (#202)
  The public segement is not connected to any other public segment.
  Verify if the segment is meant to be a public accessible segment, or it should be changed to a private segment.
  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: PL, IT, IL, FR, ES
  


• Custom check (#130)
  The segment matched custom conditions.
  Solve the issue.
  For countries: ES
  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: ES
  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: ES
  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: !RU, !IL
  


• 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: !NL, !LU, IE, BE
  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: PL, NL, IE
  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: PL, NL, IE
  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: PL, IT, FR, BE
  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: US, PL, !IL, FR, BE
  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: PL, AR
  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: !RU, !IL, *
  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: US, SK, IT, FR, ES, CZ, CL
  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: 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: !IL, !FR, !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: !NL, !IL, !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: !NL, !IL, !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: wiki
  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: !IL, *
  


• 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: !US, !AU, *
  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: !IL, *
  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: US, SK, IT, IL, ES, DE, CZ, CH, AT
  


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


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


• 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: US, SK, PL, IL, FR, ES, CZ, BG, AU
  


• 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: DE, CH, AT
  


• 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: SG, MY, BN
  


• No lock on Freeway (#150)
  The Freeway segment should be locked at least to Lvl ${n}.
  Lock the segment.
  For countries: US, SK, SG, NL, MY, IT, DE, CZ, CL, CH, BN, BE, AU, AT, AR
  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: SK, SG, NL, MY, IT, CZ, BN, BE, AU
  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: SK, SG, NL, MY, IT, CZ, BN, BE, AU
  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: NL, CZ, 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: NL, CZ
  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: !IL, !FR, !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: !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: !UK, !IL, !CL, *
  


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


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


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


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


• Segment has no speed limit set from A to B (#212)
  Segment has no speed limit set from A to B.
  Verify the speed limit on the segment and set it: wiki
  For countries: *
  


• Segment has no speed limit set from B to A (#213)
  Segment has no speed limit set from B to A.
  Verify the speed limit on the segment and set it: wiki
  For countries: *
  


• Segment has possibly wrong speed limit from A to B (#214)
  Segment has a speed limit that seems to be incorrect.
  Verify the speed limit on the segment and correct it if needed.
  For countries: *
  Params to configure in localization pack:
  

  Code: Select all

  "214.params": {
  // {string} regular expression to match valid speed limits
  "regexp": "/^.+[05]$/",
},




• Segment has possibly wrong speed limit from B to A (#215)
  Segment has a speed limit that seems to be incorrect.
  Verify the speed limit on the segment and correct it if needed.
  For countries: *
  Params to configure in localization pack:
  

  Code: Select all

  "215.params": {
  // {string} regular expression to match valid speed limits
  "regexp": "/^.+[05]$/",
},




• Segment has unverified speed limits from A to B (#210)
  Segment has speed limit set from A to B that is unverified.
  Verify the speed limit on the segment and confirm or correct it: wiki
  For countries: *
  


• Segment has unverified speed limits from B to A (#211)
  Segment has speed limit set from B to A that is unverified.
  Verify the speed limit on the segment and confirm or correct it: wiki
  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: SK, PL, CZ
  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: SK, SG, PL, MY, ES, CZ, BN
  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: PL, CZ
  


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

"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)

12.01.2014 v0.4.6:
- UK is globally enabled
- new BETA check: "Too short U-turn connector", please report any false positives
Currently for H-shaped crossings only.
Few examples: No Street, Berlin 147432364 197852405 197613043 153911044 145487292

- new check: "Same endpoints drivable segments"
For more details see: forum thread
Out of two Validator reports segment with lower road type or the longer one.
Few examples: No Street, Berlin 233522715 201957332 161565780 161565783 148585447

- updated "Unneeded node A/B" checks
Now it takes into account "Same endpoints drivable segments"
Now it checks if the total length of the adjacent segments is less than 1km

- fixed "Incorrect highway name" check for NL
- few optimizations for lot's of highlighted segments
- other minor changes

davidg666 wrote:Would you consider adding country-specific checks for Ireland?

Sure, let's do it!

davidg666 wrote:Only motorways (name begins with Mn or Mnn (eg M6, M18 or M50)) should have Freeway type.

Shall we check if a Mnn road is Motorway, if a Motorway is named Mnn or both?

davidg666 wrote:Names in parentheses after city names *are* valid (for example "Blackwater (Wexford)").

Sure, Validator reports incorrect city name only if it sees "Blackwater (Wexford)" and "Blackwater" names during the same map scan. You can use "Clear report" button to clear the city cache.

Please give me a permalink if you have a problem with this check.

davidg666 wrote:Cardinal direction indicators on motorways (such as the 'N' in "M7 N") are never in parentheses.

So, Motorways are either 'Mxx' or 'Mxx[space]<N, S, W or E>'
Majors are 'Nxx' or 'Nxx[space]<local name, i.e. letters, digits, spaces or dots>'
Minos are 'Rxxx' or 'Rxxx[space]<local name, i.e. letters, digits, spaces or dots>'
Right?