There was a US discussion in the last couple of months about whether there are proper places to not have first letter upper case on real streets. I don’t remember the thread or the outcome at this time, but this needs examination. Ramps starting with “to” should definitely be an exception for this check, at least in the US.
Entrance ramps here in France just start with the name of the road they are leading to, without the “to”.
And I can’t think of any example where a segment could/should start with a lower case.
I agree with two-way freeway as a warning, and two-way ramp as a note, for the US.
I agree to this. Ramps starting with “to” should be excluded outright; other roads starting with a lowercase should be considered a “note”, I think, rather than a “warning”. We decided in that thread that, although it’s rare (and we couldn’t actually find any examples of it), in the case that there is a street sign that begins with a lower case letter (e.g., “da Gama Rd”), it should be reproduced as it is on the sign. If the sign is in ALL CAPS, then capitalize the first letter.
Alan, what do you think about a note/warning for “Greater * Area”?
I agree with all your recommendations.
Just stopping by to say THANK YOU !
This is a great script 
I’m looking forward to the updates after some good comments and suggestions here.
21.01.2014 0.5.1:
- NEW for ALL ‘Lowercase city name’
- NEW for US: ‘Lowercase street name (with exceptions)’
- NEW for FR, GF, NC, RE ‘Lowercase street name’
- NEW for IL, US ‘Two-way Ramp segment’
- NEW for IL, US ‘Two-way Freeway segment’
- UPD ‘Unneeded node A/B’: total length is up to 10km
- UPD ‘Might be incorrect city name’: same names
- UPD ‘Might be incorrect city name’: De Witt vs Dewitt
- ENABLED for AT, CH, DE ‘City name on Freeway’
- setting ‘WME: Two-way segments’ is off by default
- popup when settings are reset to their defaults
- popup with a changelog
- started adaptations for RTL languages
- started Israel localization
- other changes
To me it doesn’t matter since it doesn’t show up on the map now, only in the reports. The main thing I’m worried about is if the wrong city name will give problems to people trying to get to an address where there’s identical names. If it won’t cause a problem for them, then I’m fine with it.
One thing I have noticed in the past couple of days is that the color indicators aren’t flashing any more. That doesn’t bother me, but when I zoom in they tend to disappear until I zoom out then back in. I don’t know if that’s a problem with the validator or not, I just thought I’d mention it.
Also, since I’m mentioning things, I also have the “Toolbox” installed, but if I run that while I’m running the validator I’m unable to make any changes on the map. I’ve tried uninstalling/reinstalling both scripts, but I have the same problem. For now I have the toolbox turned off. Any ideas on that?
Is it why the how to fix show a link to a forum topic with a form to fill
Via Tapatalk
It was discussed here: page 7 and we decided to leave them. Let me know if I shall exclude roundabouts for you country.
Hover your mouse over any segment. If it is not selectable, it’s a WME bug. I’m experiencing that too time to time with/without Validator enabled. I just move the map a bit and it’s turn to normal.
Can’t reproduce 
Could you please give step-by-step instructions?
I was involved in that conversation, and with all due respect to the others who commented on it, I remain unconvinced that currently there’s any real probability of someone being routed down the wrong way in a raoundabout that only has two roads going to it (which is the only thing that triggers this particular alert in the Validator). CBenson gaven an example during that discussion of a toll road where toll was one way but not the other (on two one-way roads) and so people with “avoid toll” set would be routed down the wrong way street because it had the lower penalty. Since I’ve never seen a roundabout where it was toll in only one segment, I fail to see how the segment going the wrong way, which has a higher penalty than going the segment the correct way, is going to be the route that the navigator selects. Maybe there was a problem with it at one time, but I haven’t seen anybody cite anything current where someone has been routed the wrong direction on a roundabout.
The “add roundabout” function in WME doesn’t create an extra, third empty junction node and the Toolbox “redo roundabout” function doesn’t do it, either.
Adding a third node by way of the usual trick (connect a blank road and delete it) results in a roundabout which no longer has sequential segment ID numbers, and that has been demonstrated to cause routing problems occasionally. Fixing that with the Toolbox “Redo Roundabout” tool properly removes the extraneous extra node because, well, there ain’t no road there.
I really think that this decision to have a two-road roundabout flagged with that “same segment” warning needs to be rethought. As it stands, I feel this same-segment warning on two-road roundabouts is going to encourage editors using the validator to create more problems on roundabouts than the alert is trying to solve.
berestovskyy, could you please enable this checks for the IT country?
- BETA: Lowercase street name
- BETA: Two-way Freeway segment
- City name on named Ramp
- City name on Freeway
- Incorrect Freeway lock level
Must be at least 5 - Incorrect Major Highway lock level
Must be at least 5 - Incorrect Minor Highway lock level
Must be at least 4
…and maybe add a new alert for “Street name contains a dot”?
Done.
I’d really appreciate wiki/forum references for the following checks:
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.
There’s a form for that.
https://docs.google.com/forms/d/1jP38BrXfr9VUAk1V1D34MUZCuWPuuFr8LTrVNhR4W_8/viewform
berestovskyy, would it be possible to include SK (Slovakia) and CZ (Czech Republic) into those country specific checks?
- BETA Lowercase street name (SK only, not for CZ)
- BETA: Lowercase street name (with exceptions) (CZ only, exceptions: náměstí; nám.; nábřeží)
- BETA: Two-way Freeway segment
- City name on Railroad
- Less than 3 letters long street name
- More than 25 letters street name (ramps excl.)
- No lock on Freeway
- No lock on Major Highway
- 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.
22.01.2014 v0.5.2:
- NEW for Italy: ‘Street name with a dot’
- UPD ‘Same endpoints drivable segments’: roundabouts are temporarily excluded
- support for RTL languages
- bunch of checks enabled/disabled for Israel
- few checks enabled for Italy
- other minor changes
Sure, done. I just made a release, so these changes will be released tomorrow.
At the moment the checks are sorted just like in a report: more severe issues come first and sorted alphabetically. The number does not correlate with the check, it’s not a check ID.
There are lots of checks indeed, but I’d rather to implement a filter inside the script to show enabled/disabled checks for the current country…
All I do is enable the extensions in Google Chrome. I just tried it again and I can highlight the streets, but I can’t click on the arrows, move the nodes, or make edits to the street information. Others I’ve talked to haven’t had this problem, and I’ve checked to make sure everything is up to date, including Chrome.
The toolbox does have some features in it that I like, but the validator works better for me. I guess I’ll just have to leave the toolbox off. Thanks for checking on it.
A quick question, although I’m sure it’s been addressed before. There are some roads that are “horseshoe” roads with the starting and ending points connecting to the same road. Is there any way to change it so an option of “Allow” or “Accept” is possible? In the area I live in, there’s a ton of these and the only way to keep them from showing up in the reports is to put in a phantom road. If it is removed later, then there’s an extra node that needs to be fixed. If we can look at these and say it’s allowed, that would help a lot.
Here’s a permalink to one I’m talking about:
https://www.waze.com/editor/?zoom=5&lat=43.33792&lon=-75.74697&env=usa&segments=34087937
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 must be some errors in Javascript console… No other ideas, sorry