Loading request...
User describes frustration with detection systems that don't provide an indicator of successful detection, leading to unnecessary stops. They suggest improving the feedback mechanism and timing to prevent cyclists from stopping when detection has already occurred and a green light is imminent.
Great video - well timed (hurr), and a clear explanation of how the system works. :) I’m glad you mentioned the energy conservation at 12:15 . I’m Dutch and there are still some traffic lights where they HAVE implemented the detection system, but seemingly a bit poorly so, with no indicator it registered you, and so you approach the light… stop.. and as you reach to push the button, the light turns green. You’d think that sensing you is a good thing, but at that point you realise: “oh, it senses me, the button has become redundant, but I’m still pressing it AND I had to stop. WHY? If you’re going to make me stop, might as well not have the overly complicated sensor.” It’s actually MORE annoying, especially when you know what’s going to happen. (And no, I’m not going ‘Wielrenner’ speeds ) And if people know there’s a sensor that will just make them stop for a second or two, they’re more likely to ignore the red, thinking it’ll be fine because it will turn green in a second anyway and run the red light. (Similar to that Granville bridge example) This is frustrating, especially if you have it several times in a row, or for instance, after a bridge, where you just spent a lot of energy getting up it, and then get to waste it all for what feels like a needless red just down on the opposite side. Don’t get me wrong, especially after watching videos like yours and NJB, I’ve come to realise how much effort we’ve actually put in our systems here.. but it wouldn’t be very Dutch of me not to complain about it.