I don’t see why they should be exceptions. All the lowercase ones in California are wrong and should be capitalized.
I stand corrected. I was doing edits in the SJC area and I could swear I had seen road signs that matched the lower case name in WME, but I have been unable to locate. I was likely mistaken. For now it seems like lower case names would be the exception, and ‘la’ and ‘el’ should not be added to the exception list. I think the summary from the other forum thread was “match the case of the road sign”
thanks!
I agree. Since most signs are uppercase, in Waze we would typically switch this to initial caps.
So I remove all exceptions but the “to” for the ramps, right?
For the first word of any street name, yes. Not every connector is a ramp, so road type is not a factor. If the first word is “to”, it should be lowercase.
There exists a street (deKoven Dr, Middletown, CT) which starts with two lowercase letters on the BGS. This is a name, not a word, and isn’t going to appear on a list; rather it is detectable by the pattern that that it matches ‘de’ followed immediately by a capital letter (not a space). This is the only example so far I have seen for the entire USA of a street name that is not capitalized. Some might described it as a quirk, oddity, or affectation.
02.02.2014 v0.5.9:
- 4xNEW for ALL: ‘No inward/outward connectivity at node A/B’ (warning)
(DELETED: ‘No connectivity at node A/B of drivable road’) - NEW for ALL: ‘Railroad used for comments’
- NEW for ALL: ‘Walking Trail used as a Railroad’
- NEW for ALL: ‘Unneeded name on one-way Ramp’
- UPD for US ‘Lowercase street name’ exceptions: to
- UPD for PL ‘Incorrect Railroad name’: added MPK, SKM and Tramwaje Śląskie
- fixed: in segment properties issues are grouped now, i.e. ‘Soft turns (12)’
- fixed: beta editor login
- fixed: Validator enabling/disabling
- polish translations thanks to Zniwek
For FR, GF, NC, RE, the equivalent is “TRAVAUX”.
I could have missed the discussion on this one, but how does this determine it is unnecessary? I assume the subsequent ramps or streets are named.
However, I have seen plenty of very long ramps or when they are around corners where the initial exit sign naming is not the same as either of the secondary ramp split points.
Maybe this is only important if the initial segment length is too short and when TTS reports the first name it takes longer than the drive time to the next split causing the driver to miss the turn.
If this one-way Ramp has a turn enabled to another one-way Ramp. Here is an example: permalink
Sorry, maybe the condition is not sufficient for US, so please let me know if I shall disable the check for US or add more ifs.
I don’t understand - how can I translate (localize) the Validator?
There is a roundabout in Bratislava, SK, which has just one connecting road (it is actually a dead-end or cul-de-sac road, but never mind for now) and one more junction at its opposite side (possibly created using JNF, or manually… who knows, it is nearly two years old).
Validator reports “Inconsistent roundabout direction - #49 The adjacent roundabout segments have different directions.” This is actually a false positive - both segments of the roundabout have a correct direction (anticlockwise, consistent with driving on the right-hand side). It was possibly triggered by the detail, that both segments go from node B to node A, but in such case the reported problem should be rather something like “The roundabout segments’ direction is B->A, which might be believed to possibly cause harm to the instructions”?
I was editing for some time, but I still didn’t get the idea of new check on one-way ramps. It simply does not work to my logic.
This condition brings many false positives in Germany, too. Since editors in other countries seem to have the same problem, might I suggest to only activate this condition in countries who explicitly ask for it?
I am not sure what this means by your description of “turn enabled”. Many of the one way ramps in the US will lead to other one way ramps with a turn enabled. I presume this is getting lost in the translation. 
Either way I do think we should consider disabling it in the US. I don’t know of any situation where the name in the ramp causes problems except the point I made about short ramp segments possibly. In that case maybe we do some tests to see when it is too short and then you give the warning.
Found a situation with a roundabout giving a warning "Same endpoints drivable segments." In this case assuming the reports that the routing engine has trouble with these by not starting people in the right place, a roundabout with the two segments going only opposite directions would force the routing server to only go through one way or the other. And worst case someone starting on the roundabout or ending on the roundabout can likely figure out the route in that circle.
Otherwise we have to add a node in the middle of one of the two segments on the roundabout. That seems like unnecessary work.
Please disable one-way ramps warning for CZ (or disable it globally). I think we need to discuss it and understand how it works before enabling again.
Sent from my iPhone using Tapatalk
I fail to see why that is an “unneeded name,” given the length of the ramp. I’ve seen lots of named segments of that nature out here, and have been doing it that way all along, since it helps to provide guidance to drivers making their way to the freeway.
I’d vote for that. 
I’m still not sure it’s applicable for anywhere else, though. Is there something in the Wiki that I’ve missed regarding freeway onramps?
Another question, how does the script determine when walking trail is used as railroad and when it is correct walking?
Sent from my iPhone using Tapatalk
Not to mention that the minute you do that, you create a roundabout with non-sequential segment IDs, and I’ve read that can cause problems with navigation through a roundabout. The Toolbox will specifically flag such a roundabout as one which could cause potential problems (and if you use the “redo roundabout” tool, it will (quite properly, IMO) remove the extra node you just added because there’s not actually a road attached to it).
03.02.2014 v0.5.10:
- HOTFIX: DISABLED for (almost) ALL: ‘Unneeded name on one-way Ramp’
Sorry, from now on I will announce upcoming checks. For instance, here are the checks ready to release in 0.6.0:
- NEW for ALL ‘SLOW: No connection at node A/B’: a dead-end node is 5m from another segment
- NEW for ALL ‘Too short segment’ (less than 2m long)
Here is the post about the localization/translation: forum link
Right, for the left-hand traffic, direction could be either A-B or B-A, but for right-hand traffic it’s always A-B. So Validator takes this shortcut and does not compare adjacent roundabout segments for right-hand traffic.
You might need to update Validator, since it was disabled few days ago:
22.01.2014 v0.5.2:
- UPD ‘Same endpoints drivable segments’: roundabouts are temporarily excluded
It reports Walking Trails with level -5.