[Script] WME Validator v2025.02.26 (+ PLACES BETA)

[porubcan]

new check proposal:

check description: street name contains only space / non-breaking space (alt+0160) / blank space (alt+255)
What is the problem: in old Cartouche many editors used non-breaking space or blank space as a street name just to distinguish between newly pawed roads and already finished unnamed roads in unnamed streets layer.
How to fix: use correct street name or check “no street” checkbox instead
Severity: warning
Countries: any country

[berestovskyy]

23.01.2014 v0.5.3:

• NEW for ALL: ‘Street name with spaces only’
• UPD ‘More than 25 letters street name’: for drivables roads only (still excluding Ramps)
• few checks enabled/localized for CZ and Slovakia
• ‘Settings->About->Available checks’ button now shows enabled/disabled checks
  for the current (i.e. map top left corner) country

[fmondini]

@berestovskyy

I’d really appreciate wiki/forum references for the following checks:

@fmondini

• Incorrect Freeway lock level
• Incorrect Major Highway lock level
• Incorrect Minor Highway lock level

Official guidelines and/or wiki on the lock level are not ready (yet). If you absolutely need a link to a reference please temporarily use http://docs.wme-tools.com/ for all, at least until the rewrite of the documentation will be done by our local champs.

@berestovskyy

EDIT: please note you have lots of roads with “dir.”, so I mark ‘Street name with a dot’ as a beta check. Please let me know if I shall add “dir.” as an exception.

Sorry, I forgot to mention that the only road type that can have dots in the name is “Ramp” (because we use TTS abbreviations) and it must be one-way. All other road types must be checked.

If you want you can add a more strict check on the abbreviation, but it’s not a small list (see here).
But I do not know if it’s worth it.

[sketch]

Perhaps directional words should be excluded from the city name check…

[houstonmg]

if I turn off the script. does not need to be on every time I press a new permalink.
MG

[berestovskyy]

@fmondini

If you absolutely need a link to a reference please temporarily use http://docs.wme-tools.com/ for all

Validator localize links, problems and how-tos. For instance, hover you mouse over the “New road” note in France (permalink) and in Slovakia (permalink). In France you get localized description and link:
“Création de segment incomplète ville et nom de rue non renseigné wiki”
In Slovakia you get the default:
“Each segment must minimally have the Country and State information wiki”

While it’s OK to have the default message for “New roads”, IMO some checks (like abbreviations and locks) always must provide local information, so editors know what should be locked and how to abbreviate streets.

@fmondini

If you want you can add a more strict check on the abbreviation, but it’s not a small list (see here).

Apparently you have lots of abbreviations with dots, so I’m not sure if you need this ‘Street name with a dot’ check at all :lol: Maybe it’s better to implement ‘Incorrectly abbreviated street name’ like in other countries?

@sketch

Perhaps directional words should be excluded from the city name check…

Please have a look at Might be incorrect city name explained (forum post). This i case #10 Add/remove word. It has a limit: 10 segments. If you would have more than 10 ‘West Memphis’ segments, they would completely disappear from the report.

I’m not sure if we shall add directional words in all languages. I’d rather to lower the limit mentioned above…

@houstonmg

if I turn off the script. does not need to be on every time I press a new permalink.

Thanks, will be fixed.

[TonyTorrent]

@AlanOfTheBerg

This has been well documented in a few different forum discussions, which the Validator author provided links to earlier in this thread.

Thanks Alan, that’s all I needed to know. I don’t always have the time to read all of the threads and posts, that’s why I started out with the comment that it might have been brought up before.

[AlanOfTheBerg]

@TonyTorrent

@AlanOfTheBerg

This has been well documented in a few different forum discussions, which the Validator author provided links to earlier in this thread.

Thanks Alan, that’s all I needed to know. I don’t always have the time to read all of the threads and posts, that’s why I started out with the comment that it might have been brought up before.

Discovered I believe I was wrong. It got sent to me via PM. He provided two links to threads about 2-part/3-part loops.

[fmondini]

@berestovskyy

Validator localize links, problems and how-tos. For instance, hover you mouse over the “New road” note in France (permalink) and in Slovakia (permalink). In France you get localized description and link:
“Création de segment incomplète ville et nom de rue non renseigné wiki”
In Slovakia you get the default:
“Each segment must minimally have the Country and State information wiki”

While it’s OK to have the default message for “New roads”, IMO some checks (like abbreviations and locks) always must provide local information, so editors know what should be locked and how to abbreviate streets.

Ok, if I understand correctly what you need is an italian translation of the brief message for the hover text AND a link to the wiki.

If this is the case, here is the translation:

• Incorrect Freeway lock level
  Autostrada: Livello di blocco insufficiente, deve essere almeno 5
• Incorrect Major Highway lock level
  Superstrada: Livello di blocco insufficiente, deve essere almeno 5
• Incorrect Minor Highway lock level
  SS/SR: Livello di blocco insufficiente, deve essere almeno 4
• Street name contains a dot
  Il nome della strada non può contenere un punto
  For the wiki link use http://docs.wme-tools.com/ for all.

@berestovskyy

@fmondini

If you want you can add a more strict check on the abbreviation, but it’s not a small list (see here).

Apparently you have lots of abbreviations with dots, so I’m not sure if you need this ‘Street name with a dot’ check at all :lol:

No, sorry, my fault, the list I linked contain the TTS abbreviations; forget it, it’s deprecated.
Generally, the rule is: street names (all types except Ramps) cannot contain a dot.
Ramps can have it, but only if the word is: “Dir.”, “dir.”, “Var.” and “var.”

Thank you for your patience and forgive me for the confusion, can happen when things are done in a hurry.

“There’s never time to do it right, but there’s always time to do it over.”

[sketch]

@berestovskyy

@sketch

Perhaps directional words should be excluded from the city name check…

Please have a look at Might be incorrect city name explained (forum post). This i case #10 Add/remove word. It has a limit: 10 segments. If you would have more than 10 ‘West Memphis’ segments, they would completely disappear from the report.

I’m not sure if we shall add directional words in all languages. I’d rather to lower the limit mentioned above…

I understand. I guess I got the report because I was zoomed pretty far out so it was only grabbing a couple West Memphis freeway segments at the time. Sort of a weird thing, but it’s not a big deal.

[GinBook]

@porubcan

berestovskyy, would it be possible to include SK (Slovakia) and CZ (Czech Republic) into those country specific checks?

12. BETA Lowercase street name (SK only, not for CZ)
13. BETA: Lowercase street name (with exceptions) (CZ only, exceptions: náměstí; nám.; nábřeží)
14. BETA: Two-way Freeway segment
15. City name on Railroad
16. Less than 3 letters long street name
17. More than 25 letters street name (ramps excl.)
18. No lock on Freeway
19. No lock on Major Highway
20. No lock on Minor Highway

thank you very much for great help and maybe just small suggestion - separate checks in the complete list into groups, e.g.:

• checks not adjacted to other scripts:
  A. checks vallid for all countries
  B. country specific checks
• checks using other scripts
  C. checks vallid for all countries
  D. country specific checks

this will allow better overview of all checks with separate numbering for each group so no need to renumber the list and if someone will reffer to check A13 it will be clear regardless of current version.

than you.

Hi berestovskyy

50. BETA: Lowercase … (CZ only, exceptions: náměstí; nám.; nábřeží) add třída; tř.; nábř.

than you.

[berestovskyy]

@GinBook

50. BETA: Lowercase … (CZ only, exceptions: náměstí; nám.; nábřeží) add třída; tř.; nábř.

Sorry for a delay. Sure, will be added in the next version (~ Monday).

[levin]

Another suggested check: U-turn at roundabout entrance

When a road is entering a roundabout, there must not be a u-turn on the node connecting to the round-about. The driver must make a full round around the roundabout instead of a U-turn just ahead of it.

For example, The marked U-turn should not be allowed:

[berestovskyy]

28.01.2014 v0.5.5:

• fixed ‘Available checks’ crash
• fixed ‘Show report’ crash (for some countries)

28.01.2014 v0.5.4:

• NEW for ALL ‘U-turn at roundabout entrance’
• NEW for FR, GF, NC, RE ‘SLOW: Missing street name accents’
• UPD ‘Lowercase street name (with exceptions)’: added SK and CZ exceptions
• UPD ‘Less than 3 letters long street name’: Ramps are excluded
• DISABLED for SK: ‘Lowercase street name’
• UPD: ‘Street name with a dot’: Ramps are excluded
• now you can localize check titles
• some translations for Italy
• Validator is disabled in LayerSwitcher due to auto-enabling on permalink click

One hundred of checks!
Thanks everyone for your ideas and contribution!

[davidg666]

Thanks for all the work so far! Something I’ve noticed in one of the country-specific checks you made for Ireland: this segment here reports “Incorrect Major Highway name” because of the fada (accent) in its name. The correct name is “N62 Cúchulainn”, but if that’s changed to “N62 Cuchulainn” (removing the accent on the first ‘u’) then Validator doesn’t think it’s incorrect any more.

Irish placenames use similar (but not all the same) characters as English placenames; as well as the usual [a-zA-Z] characters, fadas (accents) on vowels are also valid: [áéíóúÁÉÍÓÚ].

++David \ davidg666

[BellHouse]

@berestovskyy

• Validator is disabled in LayerSwitcher due to auto-enabling on permalink click

Sorry to see that, I really liked this feature!

I never left-click the permalink button, but just copy the link instead (right click permalink, then select copy link). Following this procedure, the LayerSwitcher entry was perfect. Any chance to get it back (maybe optionally)?

[berestovskyy]

@BellHouse

@berestovskyy

• Validator is disabled in LayerSwitcher due to auto-enabling on permalink click

Sorry to see that, I really liked this feature!

WME was re-enabling Validator once you clicked a permalink. The issues was reported here: forum link

WME beta uses new permalink layer param format and it works fine. So once this new format will be released in prod WME, Validator will appear in LayerSwitcher again

Meanwhile you can click Validator title to switch it on/off:

[berestovskyy]

29.01.2014 v0.5.6:

• new WME beta compatibility
• UPD for Ireland ‘Incorrect Highway name’ (accents)

[kentsmith9]

@AlanOfTheBerg

@TonyTorrent

Emmons Circle is the horseshoe with both ends connecting to Wolcott Hill Street.

Emmons Circle needs to be split into two segments. No two segments should have the same end points. It causes all sorts of routing problems, and misidentification of the actual route requested on URs, etc. It also causes issues with inability to locate the correct location when starting on that type of road.

This has been well documented in a few different forum discussions, which the Validator author provided links to earlier in this thread.

There may be some confusion between the different types of “same connections”. Let me clarify:

• Loop Roads: One Segment. End-nodes A and B connect to themselves. Routing issues identified and fixes exist in many scripts. Covered in Wiki
• Routing to Same Segment: One Segment. I found a strange routing problem when you start and end navigation on the same single segment. I fully documented it in the forums under Same Segment Routing Problems.
• Parallel Segments: Two Segments. Also called Horseshoe Roads. This situation is like two resistors in parallel. The end nodes A of both segments connect together and the end nodes B of both segments connect together. A real example is here. I also posed this question in the forum under “Same Connections” cause routing issues?

@berestovskyy

34. Same endpoints drivable segments
    What is the problem? Two drivable segments share the same two endpoints: forum reference
    How to fix? Split the segment. You might also remove one of the segments if they are identical: instructions
    Severity: warning
    Countries: any country
    

This entry is referring to the Parallel Segments/Horseshoe Rd example. The forum reference for 34 actually links to my forum entry that was asking anyone to actually confirm there are problems with this configuration in routing, but there was nothing conclusive. I did point out the other problem with routing to the same segment in that thread, so maybe people got confused what was actually a problem. There were comments this was a known issue with Cartouche, but not necessarily the current WME.

Today I sent a message to the Waze team on that specific issue. I will report back what they say relative to this issue. If anyone has any current routing issues they know about or can find any forum threads showing this is still a problem then let us know and we can add it to the Wiki best practices.

If there are no routing issues that we can still find today I realize this particular warning will help identify segments that lay on top of each other, but these Horseshoe roads are so widespread in suburban neighborhoods I think it will invite unnecessary editing to add a junction. Also if we do leave this in we need to be sure the “remove unnecessary junction nodes” option does suggest removing them. LOL

[berestovskyy]

Thanks!
Let me know when you get an answer.

IMO for the Parallel Segments we can create more precise and reliable check, so I’ll disable ‘Same endpoints drivable segments’ for now.