Previously, unneeded nodes were reported for those used for change of elevation and road type also. I haven’t re-tested.
I don’t get this. Why would you ever traverse the lower segment just to turn around? Why not have a single segment with the restriction? It doesn’t go anywhere else, so regardless of whether it is one or two segments, the routing effect is identical. Or else I’m not getting it…
If Waze thinks the destination is closer to the segment with restrictions than any other segment, it will override the segment restrictions. This is just like any turn restriction.
The only thing this segment restriction does is affect travel along the whole segment, so having two parts is unnecessary.
As for me, I like having a node at the gate. It makes it easier to find the point of access control between the public side and the private side even though there might be no reason to drive up to the gate when it is closed and it makes an “unneeded” node.
There are two buildings on the inside of the gate that are accessible at all times from inside the park (it’s a very large park with roads throughout that doesn’t close completely at night - just the smaller gates close at night). Access to these buildings shouldn’t be restricted, only passage through the gate should be restricted.
I agree that restricting one single segment would have the same effect on routing because the restriction just imposes a routing penalty and there’s no other way to the part of this road that remains accessible, however it feels wrong to mark a bit of road as time-restricted when it isn’t.
++David \ davidg666
Are you sure? In tests I did a little while ago, Waze acted as if the restricted roads didn’t exist at all…
(behaviour may have changed since, without warning, as it often does)
Things change all the time, so I very well could be wrong. In fact, that’d be great in this case!
^ (here, in response to Alan/Timbones)
Consider someone going to one of the buildings near the gate, after the gate is closed. If Waze doesn’t ignore restricted roads entirely, having the restriction on the whole segment would make Waze indifferent to which direction it came into the segment, and would be just as likely to send you through the closed gate as it would be to send you through the complex (the “possible” way). If Waze does ignore restricted roads entirely, it’ll send you to R806 instead of North Rd (inside the complex), which is unhelpful because those buildings are inside the fence.
Here’s another example. What we have here is a road with a locked gate in the middle, to which only the residents have a key. Each end of the road is accessible to everybody, but only key holders can pass through.
If the central section isn’t on the map, and any of the residents start driving through the gate with Waze running, Map Problems will result. OK, they can be deleted, but better to avoid them in the first place - besides an editor not knowing the situation might react to the Map Problem by creating an unrestricted link.
With the central section in but restricted, non-residents never get routed along the road past the gate. Neither do residents, which isn’t ideal, but at least they know the area and can make their own decision to ignore the Waze route when they want.
So in my view, Validator should be detecting that the restrictions are different each side of the node, and not flagging it for removal.
Works exactly as if that segment were set as Private Rd. So, I guess it’s one way or the other…
On this occasion, the “private road” penalty is not (or has not been at some time in the past) sufficient to stop through routing - passing through the gate saves a good ten minutes on some journeys, which is of course why the residents are so keen to keep their gate locked.
Please update the FAQ. In particular, it should not use the word flashing.
OK, here here is yet another example of where Validator is incorrectly saying “remove a node” because it isn’t recognising restrictions. The northern part of Church St is a pedestrian precinct during the day only. Time restriction closes it 10:00-16:30. There is no junction at the change, just a gate which is closed 10:00-16:30, open at other times.
Now as it happens, Church St also goes 1-way at this point, so Validator wasn’t complaining. But I’ve temporarily made it 2-way, and immediately Validator says get rid of the node, which would incorrectly apply the time restriction to the whole road.
Done:
- UPD ‘Unneeded node A/B’ for segment/turn restrictions
- keyboard shortcut to toggle Validator on/off: Shift+W
- Spanish localization has started
- FAQ and forum post updated
Anything else for the next version?
Hi
WME validator 0.6.1 makes some script unusable on Firefox 27:
- WME Color Highlight 1.8
- WME House Number Helper 0.4.5
- WME route checker 1.0
- WME Hide Landmarks 1.0
Could you find a way to fix this? I’d like to use your script and these others 
Sure, no problem.
I guess those first 3 scripts have the common issue: they all have fixed WME startup time encoded (setTimeout), which is not always enough as you can see.
Yours Hide Landmarks have another issue, please check the PM.
Thanks a lot. Now fixed for WME hidelandmarks
For Belgium #31 and #33 are irrelevant, because our citynames are fixed, we can’t really make such mistakes in the cityname.
And because we have citynames that are used more than once, we use abbreviations to distinguish them: pe ‘Laeken / Laken (Bru.)’ is colouring completely blue, and that doesn’t need to be changed
NM, clearing cache resolved the issue.
I still receive this warning for segments with very distinct paths, often with one being much longer than the other. I think Kent is correct. It matters when the geometry of one segment is completely overlapped by the geometry of other segments. If the segments are several meters apart, then one cannot hide the other.
A segment which has a geometry point at least 5 m from any point along any other segment cannot be hidden by that segment.
07.02.2014 v0.6.2:
- Validator makes a 1 sec pause on startup to allow other scripts to start first
- Improved startup time (esp. for Firefox users)
- NEW keyboard shortcut to toggle Validator on/off: Shift+W
- UPD ‘Unneeded node A/B’ for segment/turn restrictions
- ENABLED few checks for Spain
- Spanish localization has started
Edit:
It was enabled back in 0.5.8. At the moment this check does not report roundabouts.
1 Like