WME Validator Localization Package for NY (& rest of USA)

Moderators: delilush, orbitc, PhantomSoul

WME Validator Localization Package for NY (& rest of USA)

Postby PesachZ » Fri Oct 09, 2015 2:44 am

Over the past couple of weeks I've been working with several other editors; xanderb, tythesly, dsfargeg, and timbones to develop this localization package to customize Validator for our guidelines and preferences in NYC, NYS, and the rest of the country.

The package can be downloaded from Greasyfork here j.mp/NYvalidator
You must have WME Validator installed for this to function.

This script is still young and may contain errors, and false positives. If you see it highlighting anything which should not be highlighted (ie it is mapped corectly), please reach out to the authors. We will investigate and try to update this package accordingly.

The authors (tythesly, dsfargeg, and PesachZ) can be contacted via PM.

This package has been designed to not use either of the custom check slots available in Validator through the settings panel. The checks which are specific to NYS are designed so they only highlight segments in NY.
The only NYS specific check which is active everywhere by necessity due to its nature is #131 (segment state check). When editing outside NYS this check can be easily really disabled by typing
Code: Select all
!131, *
in the Reported As: field of Validators search settings (click the magnifying glass). (See screenshot)
Therefore you may keep this package installed and running always, whenever you are using Validator, without it interfering with your editing.

As always with any validator highlight, the items highlighted are meant to draw you attention to a possible problem for you to investigate. If after investigating you determine that the map is setup correctly as is, you do not need to change the map "just to make Validator happy". If this does happen please bring it to our attention, so we can fine tune the filters.

I hope using the NY Localization package, will make editing more efficient, and accurate.
[ img ]


Complete List of Checks for United States (v1.1.8)
See Settings->About->Available checks

Localization Fallback Rules:
New York State, USA → United States

82 checks are enabled for United States:

New Local Checks

  • Not New York (#131)
    The segment matched custom conditions.
    Make sure you are editing in NY and change it. If you are editing outside NY you can disable this check by entering "!131, *" (without the quotes) in the Reported As: field of Validators search settings (magnifying glass): wiki
    Current configuration for United States:
    Code: Select all
    "131.params": {
      "titleEN": "Not New York",
      "problem": "The segment is assigned to another state",
      "solutionEN": "Make sure you are editing in NY and change it. If you are editing outside NY you can disable this check by entering \"!131, *\" (without the quotes) in the Reported As: field of Validators search settings (magnifying glass)",
      "template": "${state}",
      "regexp": "!/^New York/",
    },

  • Improper Exit Naming (#132)
    This segment has an entrance / exit name which does not follow the USA standards for exit naming, or is a ramp with non entrance / exit name.
    For numbered exits use "Exit(s) ##: Name / Other Name". For entrances & unnumbered exits use "to Name / Other Name". Separate all shields and names with slashes (/) and spaces. Verify if this is supposed to be a ramp: wiki
    Current configuration for United States:
    Code: Select all
    "132.params": {
      "titleEN": "Improper Exit Naming",
      "problemEN": "This segment has an entrance / exit name which does not follow the USA standards for exit naming, or is a ramp with non entrance / exit name",
      "solutionEN": "For numbered exits use \"Exit(s) ##: Name / Other Name\". For entrances & unnumbered exits use \"to Name / Other Name\". Separate all shields and names with slashes (/) and spaces. Verify if this is supposed to be a ramp",
      "template": "${rank}#${street}",
      "regexp": "/4#(?!(Exit|to|$))|( |\\b)(To|[Ee](?!xits? [\\dA-Z-]+:)[Xx][Ii][Tt][Ss]?( [Tt][Oo])?:?|to:|TO|Exits? \\d+[\\w\\-]*( \\/ | \\- | |:[ \\w]*:))( |\\b|$)/",
    },

  • Improper City Naming (#133)
    This segment has a generated city name which is not its' proper name.
    Fill out the form to have teh city renamed, and contact your SM or RC to finalize the process: wiki
    Current configuration for United States:
    Code: Select all
    "133.params": {
      "titleEN": "Improper City Naming",
      "problemEN": "This segment has a generated city name which is not its' proper name",
      "solutionEN": "Fill out the form to have teh city renamed, and contact your SM or RC to finalize the process",
      "template": "${city}#${altCity[#]}",
      "regexp": "/(^|#)Greater [\\w -]+ Area|[\\w -]+\\(\\d+\\)(#|$)/",
    },

  • Potential Incorrect BANNER Abbreviation (#134)
    Name abbreviation may be incorrect. Alternative routes should be labeled ALT and abbreviations ALT, BUS, BYP, CONN, LOOP, SCN, SPUR, or TRUCK should be in ALL CAPS.
    Change abbreviation to ALT, BUS, BYP, CONN, LOOP, SCN, SPUR, or TRUCK in ALL CAPS.
    Current configuration for United States:
    Code: Select all
    "134.params": {
      "titleEN": "Potential Incorrect BANNER Abbreviation",
      "problemEN": "Name abbreviation may be incorrect. Alternative routes should be labeled ALT and abbreviations ALT, BUS, BYP, CONN, LOOP, SCN, SPUR, or TRUCK should be in ALL CAPS",
      "solutionEN": "Change abbreviation to ALT, BUS, BYP, CONN, LOOP, SCN, SPUR, or TRUCK in ALL CAPS",
      "template": "${street}#{altStreet[#]}",
      "regexp": "/!?[0-9].+(Alt|Bus(iness)?|Byp|Conn?|L(oo)?p|Scn|Spu?r|Truck)\\b/",
    },

  • NYS Minimum Lock Levels (#136)
    NYC has higher locking levels than the rest of NYS. Ferries and RR should be locked as well.
    Lock the segment to at least; PS>=3, mH>=4, MH>=5, FW>=5, Ramp>=highest connection, Ferry>=5, RR>=2: wiki
    Current configuration for United States:
    Code: Select all
    "136.params": {
      "titleEN": "NYS Minimum Lock Levels",
      "problemEN": "NYC has higher locking levels than the rest of NYS. Ferries and RR should be locked as well",
      "solutionEN": "Lock the segment to at least; PS>=3, mH>=4, MH>=5, FW>=5, Ramp>=highest connection, Ferry>=5, RR>=2",
      "template": "${state}:${city}#${type}:${lock}",
      "regexp": "/^New York:((New York|Manhattan|Queens|Brooklyn|Bronx|Staten Island)#(6:[1-4]|7:[1-3]|2:[12])|.*#(15:[1-4]|18:1))/",
    },

  • Improper Cardinal Usage (#137)
    This check is also compatible with Nebraska state roads usage.
    This name contains a cardinal direction (NEWS) which does not match wiki guidelines.
    If this cardinal should be spoken as a direction by TTS, make sure it has space on either side of it. If this cardinal should be spoken by TTS as a letter, follow it with a period. All cardinals should be capitalized: wiki
    Current configuration for United States:
    Code: Select all
    "137.params": {
      "titleEN": "Improper Cardinal Usage",
      "problemEN": "This name contains a cardinal direction (NEWS) which does not match wiki guidelines",
      "solutionEN": "If this cardinal should be spoken as a direction by TTS, make sure it has space on either side of it. If this cardinal should be spoken by TTS as a letter, follow it with a period. All cardinals should be capitalized",
      "template": "${street} ${altStreet[#]}",
      "regexp": "/(^| )([NEWS]?[news][NEWS]?|[\"']?(([ns]|N(?!-\\d{1,3}\\b)|S(?!-\\d{1,2}[A-Z]\\b))[EeWw]?|[EeWw])['\":;-]|[\"']([NnSs][EeWw]?|[EeWw])['\":-]?)(\\b|\\d| |$)/",
    },

  • Incorrect Hwy Name Prefix (#138)
    NY follows national guidelines for hwy naming prefixes (I-##, US-##, CR-##, FS-##), and uses NY-## for state routes.
    Rename the Street or Alt Street: wiki
    Current configuration for United States:
    Code: Select all
    "138.params": {
      "titleEN": "Incorrect Hwy Name Prefix",
      "problemEN": "NY follows national guidelines for hwy naming prefixes (I-##, US-##, CR-##, FS-##), and uses NY-## for state routes",
      "solutionEN": "Rename the Street or Alt Street",
      "template": "${state}:${street}#${altStreet[#]}",
      "regexp": "/^New York:.*\\b((([Uu]\\.? ?( S|S(?!-\\d)[- ]|S\\.|s\\.?)|[Nn](?! \\d)(ew )?(y|Y- |[Yy]ork)? ?|[Ss]tate |[Ss] ?[RrHh]|[Cc]o(unty)? ?|[Rr]o?u?[Tt]e?|[Ff](s|S(?!-\\d)|[Rr]))([Ss][Pp][Uu][Rr]|[Rr]((ou)?(te)?|(oa)?d)|[Hh]((igh)?[Ww]a?[Yy])?)?|Ny|NY=|I- |[Cc]([HhrSs]|R(?!-\\d))|([Ii]|[NnCcUu][YyRrSs])[ =])[- ]{0,2}\\d+|([Uu] ?[Ss][- ]?)?([Hh](igh)?[Ww]a?[Yy] )?[Ff] ?([Ss] ?|[Ss]? ?[Rr])(oa)?d? )/",
    },
    Edited 2015-10-10

  • Bad TTS Street name (#139)
    Streets that start with St and Dr result in TTS reading Street or Drive.
    Add a period after St or Dr at the beginning of the street name: wiki
    Current configuration for United States:
    Code: Select all
    "139.params": {
      "titleEN": "Bad TTS Street name",
      "problemEN": "Streets that start with St and Dr result in TTS reading Street or Drive",
      "solutionEN": "Add a period after St or Dr at the beginning of the street name",
      "template": "${street}#${altStreet[#]}",
      "regexp": "/((^|#|(\\/|[NEWS]|Rue|Place)\\s)(St|Dr)|(Jr|Rev)) /",
    },

Modified Existing Checks

  • Incorrectly abbreviated street name (#171)
    Updated to no longer flag N. cardinals, and checks against the recommended abbreviations in the wiki.
    The street name has incorrect abbreviation, or character.
    Check upper/lower case, a space before/after the abbreviation and the accordance with the abbreviation table. Remove any comma (,), backslash (\), or semicolon (;): wiki
    Current configuration for United States:
    Code: Select all
    "171.params": {
      "regexp": "/((?!(\\bPhila|\\bPenna|.(\\bWash|\\bCmdr|\\bProf|\\bPres)|..(Adm|\\bSte|\\bCpl|\\bMaj|\\bSgt|\\bRe[vc]|\\bR\\.R|\\bGov|\\bGen|\\bHon|\\bCpl)|...(\\bSt|\\b[JSD]r|\\bLt|\\bFt)|...(#| )[NEWSR])).{5}\\.|(?!(hila|enna|(\\bWash|\\bCmdr|\\bProf|\\bPres)|.(\\bAdm|\\bSte|\\bCpl|\\bMaj|\\bSgt|\\bRe[vc]|\\bR\\.R|\\bGov|\\bGen|\\bHon|\\bCpl)|..(\\bSt|\\b[JSD]r|\\bLt|\\bFt)|..(#| )[NEWSR])).{4}\\.|(?!(ila|nna|(ash|mdr|rof|res)|(\\bAdm|\\bSte|\\bCpl|\\bMaj|\\bSgt|\\bRe[vc]|\\bR\\.R|\\bGov|\\bGen|\\bHon|\\bCpl)|.(\\bSt|\\b[JSD]r|\\bLt|\\bFt)|.(#| )[NEWSR])).{3}\\.|(?!(la|na|(sh|dr|of|es)|(dm|te|pl|aj|gt|e[vc]|\\.R|ov|en|on|pl)|(\\bSt|\\b[JSD]r|\\bLt|\\bFt)|(#| )[NEWSR])).{2}\\.|(#|^)[^NEWSR]?\\.)|(((?!\\bO).|#|^)'(?![sl]\\b)|(?!\\bNat).{3}'l|(#|^).{0,2}'l)|(Dr|St)\\.(#|$)|,|;|\\\\|((?!\\.( |#|$|R))\\..|(?!\\.( .|#.|$|R\\.))\\..{2}|\\.R(#|$|\\.R))|[Ee]x(p|w)y|Tunl|Long Is\\b|Brg/",
      "problemEN": "The street name has incorrect abbreviation, or character",
      "solutionEN": "Check upper/lower case, a space before/after the abbreviation and the accordance with the abbreviation table. Remove any comma (,), backslash (\\), or semicolon (;)",
    },
    Edited 2015-10-10

  • No lock on Freeway (#150)
    The Freeway segment should be locked at least to Lvl 5.
    Lock the segment.
    Current configuration for United States:
    Code: Select all
    "150.params": {
      "n": 5,
    },

  • No lock on Major Highway (#151)
    The Major Highway segment should be locked at least to Lvl 4.
    Lock the segment.
    Current configuration for United States:
    Code: Select all
    "151.params": {
      "n": 4,
    },

  • No lock on Minor Highway (#152)
    The Minor Highway segment should be locked at least to Lvl 3.
    Lock the segment.
    Current configuration for United States:
    Code: Select all
    "152.params": {
      "n": 3,
    },

  • No lock on Primary Street (#154)
    The Primary Street segment should be locked at least to Lvl 2.
    Lock the segment.
    Current configuration for United States:
    Code: Select all
    "154.params": {
      "n": 2,
    },

  • No lock on Ramp (#153)
    Ramps generally connect to Freeways, so they should be locked to Lvl 5. If not connected to a freeway, verify that this meets the criteria to be a ramp.
    Lock the segment, change it to a non-ramp type, or just verify it should be a ramp: wiki
    Current configuration for United States:
    Code: Select all
    "153.params": {
      "n": 5,
      "problemEN": "Ramps generally connect to Freeways, so they should be locked to Lvl 5. If not connected to a freeway, verify that this meets the criteria to be a ramp",
      "solutionEN": "Lock the segment, change it to a non-ramp type, or just verify it should be a ramp",
    },

Other Default Checks Enabled in the USA

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

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

  • 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
    Current configuration for United States:
    Code: Select all
    "101.params": {
      "regexp": "/(^|\\b)closed(\\b|$)/i",
    },

  • 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

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

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

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

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

  • Self connectivity (#43)
    The segment is connected back to itself: wiki
    Split the segment into THREE pieces: wiki

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

  • 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
    Current configuration for United States:
    Code: Select all
    "175.params": {
      "regexp": "/^[\\s\\.]*$/",
    },


  • Lowercase city name (#190)
    The city name starts with a lowercase letter.
    Use this form to rename the city: forum
    Current configuration for United States:
    Code: Select all
    "190.params": {
      "regexp": "/^[a-zа-яёіїєґ]/",
    },

  • Lowercase street name (#170)
    The street name starts with a lowercase word.
    Correct lettercase in the street name.
    Current configuration for United States:
    Code: Select all
    "170.params": {
      "regexp": "/^(?!to [^a-z])((S|N|W|E)(E|W)? )?[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

  • 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.
    Current configuration for United States:
    Code: Select all
    "173.params": {
      "regexp": "/([^\\s]\\.[^\\s0-9-][^\\s0-9\\.])|([0-9][^\\s0-9]+\\.[^0-9-])/",
    },

  • 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

  • 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

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

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

  • 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

  • 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

  • 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

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

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

  • 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

  • Obsolete CONST ZN marker (#117)
    The segment is marked with obsolete CONST ZN suffix.
    Change CONST ZN to (closed): wiki

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

  • 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

  • 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

  • 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

  • Too short segment (#109)
    The drivable non-terminal segment is less than 5m 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
    Current configuration for United States:
    Code: Select all
    "109.params": {
      "n": 5,
    },

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

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

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

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

  • ██ WME Toolbox: Roundabout which may cause issues (#1)
    Junction IDs of the roundabout segments are not consecutive.
    Redo the roundabout: wiki

  • 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

  • Empty alternate street (#34)
    Alternate street name is empty.
    Remove empty alternate street name.

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

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


  • 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
    Current configuration for United States:
    Code: Select all
    "193.params": {
      "regexp": "/([^\\s]\\.[^\\s0-9-][^\\s0-9\\.])|([0-9][^\\s0-9]+\\.[^0-9-])/",
    },

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

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

  • 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

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

  • 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

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

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

  • Unneeded spaces in city name (#192)
    Leading/trailing/double space in the city name.
    Use this form to rename the city: forum
    Current configuration for United States:
    Code: Select all
    "192.params": {
      "regexp": "/^\\s|\\s$|\\s\\s/",
    },

  • Unneeded spaces in street name (#172)
    Leading/trailing/double space in the street name.
    Remove unneeded spaces from the street name.
    Current configuration for United States:
    Code: Select all
    "172.params": {
      "regexp": "/^\\s|\\s$|\\s\\s/",
    },

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

  • ██ WME Toolbox: Simple segment (#2)
    The segment has unneeded geometry nodes: wiki
    Simplify segment geometry by hovering mouse pointer and pressing "d" key: wiki

34 checks are disabled for United States:

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

  • 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: 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 (#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": "",
    },

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

  • 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 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\\. :\"'(/)-]+$/",
    },

  • 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

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

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

  • 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

  • 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

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

  • 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,
    },

  • 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
Last edited by PesachZ on Mon Oct 12, 2015 5:14 pm, edited 3 times in total.
PesachZ
Wiki Master
Wiki Master
 
Posts: 4511
Joined: Mon Jul 01, 2013 12:51 am
Location: NY, USA (also NJ sometimes) {GC}
Has thanked: 1998 times
Been thanked: 2361 times

Re: WME Validator Localization Package for NY (& rest of USA

Postby kentsmith9 » Fri Oct 09, 2015 2:48 am

This is outstanding. I think we should do more to educate on the use of customizations for Validator.

We should link this to the NY State template too.
USA: Now Idaho; previously California (Northern, SF/SJ)

[ img ][ img ][ img ][ img ][ img ][ img ]
PLEASE READ: Waze Map Editor (Start Here) | Editing Quick-start | Best Practices | Junctions
kentsmith9
Waze Global Champs
Waze Global Champs
 
Posts: 5681
Joined: Mon Apr 23, 2012 3:33 pm
Location: Boise ID and SF/SJ Bay Area of Northern California
Has thanked: 1574 times
Been thanked: 1785 times

Re: WME Validator Localization Package for NY (& rest of USA

Postby PesachZ » Fri Oct 09, 2015 2:51 am

kentsmith9 wrote:This is outstanding. I think we should do more to educate on the use of customizations for Validator.

We should link this to the NY State template too.

you mean post it in the wiki like this? Or something else?
PesachZ
Wiki Master
Wiki Master
 
Posts: 4511
Joined: Mon Jul 01, 2013 12:51 am
Location: NY, USA (also NJ sometimes) {GC}
Has thanked: 1998 times
Been thanked: 2361 times

Re: WME Validator Localization Package for NY (& rest of USA

Postby orbitc » Fri Oct 09, 2015 2:55 am

Nice work guys.
Regional Coordinator for Northeast & New England
•Tier1 •USA Coordinator •Global Champ & Mentor
•iOS & WME ßeta Tester •Beacon, CCP & Wiki Master
•Master Raiders •Localization •Content Raider

[ img ]

USA | MapRaid!
orbitc
Master Raider
Master Raider
 
Posts: 6495
Joined: Mon Jun 25, 2012 1:51 pm
Location: USA
Has thanked: 2585 times
Been thanked: 6570 times

Re: WME Validator Localization Package for NY (& rest of USA

Postby bz2012 » Fri Oct 09, 2015 10:14 am

Problem: despite
2015-10-09_050754.png
(11.67 KiB) Downloaded 5909 times


I am getting:
2015-10-09_050715.png
(18.06 KiB) Downloaded 5908 times

when I select a segment.

Additional note: after I added the 'disable' code, Validator stopped 'highlighting' all the segments as not NY, so it has some effect, but it doesn't disable the message when a segment in the New Orleans area is selected.
State Manager, Louisiana
bz2012
Map Raider
Map Raider
 
Posts: 1595
Joined: Wed Nov 23, 2011 4:32 pm
Location: Baton Rouge, La
Has thanked: 1909 times
Been thanked: 310 times

Re: WME Validator Localization Package for NY (& rest of USA

Postby kentsmith9 » Fri Oct 09, 2015 4:08 pm

PesachZ wrote:
kentsmith9 wrote:This is outstanding. I think we should do more to educate on the use of customizations for Validator.

We should link this to the NY State template too.

you mean post it in the wiki like this? Or something else?

Works for me.

I haven't tried it out yet, but did you say this will work fine for all states? Is it easy enough for users to make adjustments for differences in states, or do you have to make such changes?
USA: Now Idaho; previously California (Northern, SF/SJ)

[ img ][ img ][ img ][ img ][ img ][ img ]
PLEASE READ: Waze Map Editor (Start Here) | Editing Quick-start | Best Practices | Junctions
kentsmith9
Waze Global Champs
Waze Global Champs
 
Posts: 5681
Joined: Mon Apr 23, 2012 3:33 pm
Location: Boise ID and SF/SJ Bay Area of Northern California
Has thanked: 1574 times
Been thanked: 1785 times

Re: WME Validator Localization Package for NY (& rest of USA

Postby PesachZ » Sun Oct 11, 2015 10:11 am

kentsmith9 wrote:
PesachZ wrote:
kentsmith9 wrote:This is outstanding. I think we should do more to educate on the use of customizations for Validator.

We should link this to the NY State template too.

you mean post it in the wiki like this? Or something else?

Works for me.

I haven't tried it out yet, but did you say this will work fine for all states? Is it easy enough for users to make adjustments for differences in states, or do you have to make such changes?

Except for check #131 the rest of the checks should follow national guidance not subject to local variation, and therefore be relevant anywhere in the country. If changes are needed you can edit the script locally on your machine, but for changes to be pushed to everyone (and mistakes fixed), one of the authors will have to make the updates.

As mentioned above by bz2012 you can disable the highlight on the map for #131 using the exclude method, BUT apparently it still shows p when clicking on a segment (and I assume it may show up in reports as well). :(
bz2012 wrote:Problem: despite
2015-10-09_050754.png


I am getting:
2015-10-09_050715.png

when I select a segment.

Additional note: after I added the 'disable' code, Validator stopped 'highlighting' all the segments as not NY, so it has some effect, but it doesn't disable the message when a segment in the New Orleans area is selected.

There is the option if you primarily edit outside NY to disable check #131 in the script itself by commenting out the code. Or if you don't mind seeing it in the left panel, but not being highlighted on the map you can leave it as is.

To fully disable check #131 in the script, you will have to update the script locally on your machine and enclose the check in comment codes (/*...*/). It should then look like this.
Code: Select all
/*
  //  #131 ##Check that all segments have NY as state. This check is active everywhere.
  "131.enabled": true,
  "131.params": {
    "titleEN": "Not New York",
    "problemEN": "The segment is assigned to another state",
    "solutionEN": "Make sure you are editing in NY and change it. If you are editing outside NY you can disable this check by entering \"!131, *\" (without the quotes) in the Reported As: field of Validators search settings (magnifying glass)",
    "template": "${state}",
    "regexp": "!/^New York/"
  },
*/

Alternatively you can add in your state to the code, so it won't flag in your state(s) or NY.
To add in your state(s) modify just the line that says regexp to include your state(s) Exactly as they appear in WME. You will have to enclose the state names in parenthesis, and place a pipe (|) between each name like this.
Code: Select all
"regexp": "!/^(New York|YOUR STATE|ANOTHER STATE)/"
PesachZ
Wiki Master
Wiki Master
 
Posts: 4511
Joined: Mon Jul 01, 2013 12:51 am
Location: NY, USA (also NJ sometimes) {GC}
Has thanked: 1998 times
Been thanked: 2361 times

Re: WME Validator Localization Package for NY (& rest of USA

Postby kentsmith9 » Sun Oct 11, 2015 6:59 pm

PesachZ wrote:Alternatively you can add in your state to the code, so it won't flag in your state(s) or NY.
To add in your state(s) modify just the line that says regexp to include your state(s) Exactly as they appear in WME. You will have to enclose the state names in parenthesis, and place a pipe (|) between each name like this.
Code: Select all
"regexp": "!/^(New York|YOUR STATE|ANOTHER STATE)/"

I have not used any of the customization code for the Validator, so can 131 be set up to only run on the states that are listed for 131, so if your state is not listed this entry does not execute? Or is it an all or nothing setup?

If we can, then the script can be used by any state editor who runs it without having to know anything about editing the script.
USA: Now Idaho; previously California (Northern, SF/SJ)

[ img ][ img ][ img ][ img ][ img ][ img ]
PLEASE READ: Waze Map Editor (Start Here) | Editing Quick-start | Best Practices | Junctions
kentsmith9
Waze Global Champs
Waze Global Champs
 
Posts: 5681
Joined: Mon Apr 23, 2012 3:33 pm
Location: Boise ID and SF/SJ Bay Area of Northern California
Has thanked: 1574 times
Been thanked: 1785 times

Re: WME Validator Localization Package for NY (& rest of USA

Postby PesachZ » Sun Oct 11, 2015 7:03 pm

Duplicate
Last edited by PesachZ on Sun Oct 11, 2015 7:05 pm, edited 1 time in total.
PesachZ
Wiki Master
Wiki Master
 
Posts: 4511
Joined: Mon Jul 01, 2013 12:51 am
Location: NY, USA (also NJ sometimes) {GC}
Has thanked: 1998 times
Been thanked: 2361 times

Re: WME Validator Localization Package for NY (& rest of USA

Postby PesachZ » Sun Oct 11, 2015 7:05 pm

kentsmith9 wrote:
PesachZ wrote:Alternatively you can add in your state to the code, so it won't flag in your state(s) or NY.
To add in your state(s) modify just the line that says regexp to include your state(s) Exactly as they appear in WME. You will have to enclose the state names in parenthesis, and place a pipe (|) between each name like this.
Code: Select all
"regexp": "!/^(New York|YOUR STATE|ANOTHER STATE)/"

I have not used any of the customization code for the Validator, so can 131 be set up to only run on the states that are listed for 131, so if your state is not listed this entry does not execute? Or is it an all or nothing setup?

If we can, then the script can be used by any state editor who runs it without having to know anything about editing the script.

The problem is this check looks at the state field and highlights any segment not using state. I know of no other way to verify current state location to filter the search.
It's designed to find segments mistakenly using the wrong state (common near borders). If we restrict it to segments listed as in the state it would never run on the segments listed with wrong state, which is what it's looking for.
PesachZ
Wiki Master
Wiki Master
 
Posts: 4511
Joined: Mon Jul 01, 2013 12:51 am
Location: NY, USA (also NJ sometimes) {GC}
Has thanked: 1998 times
Been thanked: 2361 times

Next

Return to New York

Who is online

Users browsing this forum: YourEvilTwinFTW