Waze: outsmarting traffic together
https://www.waze.com/forum/
Maybe just edit it to redirect to the Junction Style Guide page?sketch wrote:As an aside, wow, that Wiki article could use some work! Lots of what-not-to-do screenshots and no corresponding how-to-do-it-right screenshots, just brief bits of text that even I have a hard time understanding.
WMECH does already highlight streets with alternate names. It doesn't, of course, do any checking of the names, but you didn't ask for that. Yet.BellHouse wrote:Is there a way to highlight segments which carry an alternate street name? I'm thinking of configuring something with the new RegExp feature, but I would not know which variable to use (something like ${alt_street}).
You are correct, sketch. In fact, it would/could erroneously highlight any junction/segment for which there exists a right-turn at-grade connector. If it is possible to look back one segment and find a "sister" segment which junctions the same segment for which the right turn is enabled, then it could ignore the first. However, I feel this type of check may be fraught with all number of exceptions that we can't think of at this time.sketch wrote:Wait, I have a problem with the "no right turn" check. Wouldn't it call for erroneous enabling of turns like the right turn from this segment?
In the thread quotes by CBenson, please supply either GIS link to city/county website showing lowercase usage or photograph of street signs showing lowercase.j4m35ch3w wrote:Hi berestovskyy,
Thanks for the fast fix!
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'
This should not be a global option. We catch lots of new/bad editors by being able to see the red roads at very wide zoom levels.pvaladares wrote:My suggestion is to add set City and Street default fields to 'None'.
Nope, I wish it was that simple.PesachZ wrote:Are you in WME Beta? Validator is broken in the latest beta.AlanOfTheBerg wrote:Sheesh, I can't even get Validator to load at all. The only line in the console on load is "WME Validator v1.1.8: login AlanOfTheBerg". Win7/Chrome 46.0.2490.71 m. Ideas?
I knew that it wasn't working in beta.