berestovskyy wrote: Ok, how about that:
2. No right* turn (for any drivable road)
* for the right-hand traffic
Report/highlight the segment if at the node:
a) there is an up to 85° right turn
a1) and either this segment OR that right turn segment is longer than 300m (~1000 ft)
b) and that right turn segment is also drivable and non-private
c) and that right turn segment is not marked as closed
d) and the connectivity between those two segments is possible (road directions), but not enabled

Would that new a1) condition be sufficient to detect connectors and other possible exceptions?

berestovskyy wrote:

sketch wrote:check out Street View on the service road at Aurora and Orion here — to prohibit drivers from cutting through the neighborhood when exiting the Interstate.

Wow, very nice and rare example. I just wondering how can we detect such a situation... A turn from a Ramp/Highway to the regular street or lower? Any ideas?

Although the map is perfectly correct, there are few possibilities to suppress the warning in Validator at the moment:
1. Add a 24/7 time based turn restriction from highway to the street.

2. Make an exiting piece of the screet one way.

3. Make the screet private.

I know it's ugly but a tempory solution. So, shall I exclude inward connectivities warnings for the turns from highways/ramps to streets/parking lots/dirts?

j4m35ch3w wrote:On a side note, is there any chance you can allow street names (in the US) that start with "de", "de la", "del", "el" and "la" to not trigger the #170 rule? There are a number of streets in San Diego that start with those and they are 'correct'.

Examples:
https://www.waze.com/editor/?zoom=7&lat ... ts=6953500
https://www.waze.com/editor/?zoom=5&lat ... ts=7077112
https://www.waze.com/editor/?zoom=5&lat ... ts=7013094
https://www.waze.com/editor/?zoom=4&lat ... ts=7077129
https://www.waze.com/editor/?zoom=5&lat ... ts=7094876

Many thanks!
- James

Haydenray wrote:I am not finding the "Udate extensions now" button in Chrome.

berestovskyy wrote:For US Country Managers (and not only)

BellHouse wrote:There are some nice instructions in this post.

BellHouse wrote:Maybe we are talking about different checks, but this piece of code works fine for me just now:

Code: Select all

  "130.enabled": true,
  "130.severity": "warning",
  "130.params": {
    "titleEN": "Segment with alternative name",
    "solutionEN": "Delete the alternative name(s)",
    "problemEN": "The segment has at least one alternative name",
    "template": "${altStreet[0]}",
    "regexp": "^.+$"
  },

(I left away the localized parameters in my example)

If you put this into a localization script, the severity setting will only become active if you set WME to the correct language (so it won't if WME is set to English). On an english WME the same custom check will be a note, so one might call that part a bug, yes.

"130.enabled": true,
"130.severity": "warning",
"130.params": {
  "titleEN": "Missing directional on Freeway",
  "problemEN": "The Freeway segment is missing a directional (NSEW)",
  "solutionEN": "Add the directional for the signed direction of travel",
  "template": "${length}:${type}:${street}",
    "regexp": "/^[1-9][0-9]{1,9}:3:.*(?! [SNEW]$)..$/",
  },