Idea for a yellow (warning) check:
Freeway segment connected to non-freeway/ramp segment
Per the wiki, freeways may only be:
This would highlight any time a freeway segment is connected to anything that is not a ramp or another freeway segment. This may only apply to the US, and I’m not sure how this would work in a localization pack.
So do I but that is the first result that came up on the search instead of the site itself.
In the US at least, Freeways can start and stop without ramps. I know of several interstates (I-27 in Texas, for example) that just start from a surface street and end into a surface street without any fanfare.
The same thing occurs in Canada - large sections of the Trans-Canada Highway near me have controlled access (ramps/interchanges) for major roads and direct connections for minor roads.
Oh yes, forgot about that. There’s remote interstates in the US that have at grade intersections for farms and such.
Great script, works fine and very useful!
“#74 The drivable roundabout node A has more than one segment connected”
Hi berestovskyy, please take a look of this situation concerning “Rule #74: The drivable roundabout node A has more than one segment connected”. The script reports roundabout nodes with multiple connections, but I don’t think there is another way to do this. Or there it is? Thanks.
https://www.waze.com/editor/?lon=27.2494&lat=42.6989&zoom=7&layers=429&env=row&segments=252358268
Wow, that is a hard roundabout-hybrid.
Ok, here is another roundabout, more “normal”, but the issue the same.
https://www.waze.com/editor/?lon=26.66914&lat=42.64698&zoom=7&layers=421&env=row
I don’t quite understand why E773 is continuing through the roundabout? This is not visible in the sat pic, nor in GMaps, nor in OSM.
Satelite picture is old, the other mapping services too. Take a look at Street View. But I am just raising attention to a particular type of roundabout and the issue it causes with validator rule #74.
OK, I see. But the constellation I see in StreetView is not a roundabout, but a major road with 2 half-circle extensions. There’s no roundabout sign to be seen.
I think the solution is to simply remove the roundabout status of these segments.
No worries, I guess I can fix #74 for such cases.
To get the roundabout instruction to work correctly on this roundabout, I had to not have the segments connect at the same point.
Hamburger roundabouts are a special case. I believe there’s a good discussion about them in the UK forums. IIRC one solution is to have the “meat” connect to the segments outside of the RB if turns from inside onto the RB aren’t allowed.
I do not consider traffic circles (e.g., Washington Circle to be roundabouts. They are circular roads controlled by traffic lights. In a real roundabout, traffic does not stop and roads do not cross. However, I do somewhat see how instructions to enter and exit the circle could be useful.
Certainly there is a difference between many circular intersections and a true roundabout (DC has both). (And I don’t think a hamburger roundabout can function as a true roundabout.) I agree the question becomes are the instructions to “take the X exit” more clear than a series of turn/keep instructions through the intersection. At Washington Circle users seem to expect a “at the roundabout take the 4th exit at Pennsylvania Ave NW” instruction rather than a “stay to the right at Pennsylvania Ave NW” instruction.
The question of roundabout versus traffic circle has been discussed a number of times before. Since Waze doesn’t have a separate traffic circle equivalent to roundabout, they are all roundabouts. This is also consistent with user expectations due to users not knowing (and not caring) about the difference between the two, and common experience across other GPS and mapping systems.
I have to admit I’m one of the ignorant masses who had no clue that there was a difference between the two - until I read this and Googled for the explanation. We learn something new every day. Thanks!
Validator is no longer highlighting issues on the map for me. If I click a problem segment, it does give me the list of things wrong with it, but there’s no color coding anymore.
I have tried disabling all other scripts. I have made sure that the highlight issues on the map option is enabled.
The script is obviously not dead, because it does display issues on the highlighted segment.
Windows 7, Chrome 34.0.1847.137 m (current version), Tampermonkey is loading Validator 0.9.9