Rail Crossing Warnings Are Sought for Mapping Apps
nytimes.com
nytimes.com
Sure, we could add warnings for potentially dangerous railroad crossings (e.g. those that do not have a signal installation), and other dangerous places, but how to ensure that people do not rely even more on their systems and after a crash argue that their system did not warn them of this particular situation?
I know a street segment that is constantly blocked by trucks which blindly followed the GPS to a bridge they can't pass and turning around is almost impossible, although multiple signs warned them. Now and then a truck takes down the roof of the bridge, although a HUGE sign says it will be too low. Before the prevalence of the GPS, this almost never happened AFAIK, and the drivers always blame the GPS.
What about people driving off cliffs, into lakes, or as stated in the article, along blocked streets. If a guy puts up a sign that this street is closed, it is closed and you need to follow, no matter what your GPS tells you. The sign or any legal representative is the normative authority and you must obey - the GPS is merely assisting you.
Drivers need to pay attention - and they might have to learn to do it despite having an assisting device giving them directions.
I certainly remember multiple accidents, both in the news and happening to people I know, and seeing damage done to local bridges before GPS was common.
What I meant: Truck drivers are driving down a 3 km long street, where it is clearly stated that they are not allowed to go and at then end of that street is very old, wooden bridge with a roof. Almost never trucks went down there until a few years ago, the roof had not been repaired in ages.
Since the prevalence of GPS that street is regularly blocked by trucks stuck at a dead end. The roof was taken down around a year ago by a large truck ignoring at least 5 signs he is supposed to look out for (multiple max weight, max height, etc.).
There are numerous compilation videos on youtube [1] about this bridge from a local, and it's not a matter of people following the GPS blindly each time, it's just inattentive drivers who don't pay attention to what is in their immediate vicinity. Watch the video linked and see how many warnings and alerts have been made for the bridge, and how often people keep skinning off the tops of trucks and RVs on it. It has a sensor to warn drivers in advance if their vehicle is too tall, signs everywhere, and I imagine there must be a fair amount of debris from the numerous accidents it has.
It's not just a matter of technology leading people astray, it is people not really being aware of their surroundings period. The warning from a GPS map might be nice and help, but I personally have a hard time believing that they'll pay attention to that any more than they would the multiple warnings in real life.
I don't think it was a situation where the driver couldn't get past the crossing. I think they are saying he parked his truck across the rails when it broke down. Had the GPS warned him, "hey this is a railroad crossing" he might not have chosen that spot.
IMHO, that's a stretch. If you are too out of your wits to notice a railroad crossing - you shouldn't be driving at all.
I think they are saying he parked his truck across the rails when it broke down
The article isn't really clear on the events, but I'm interpreting it a different way. "he would have been less likely to misinterpret the visual cues and mistakenly turn onto the railroad tracks"
It sounds like he was driving along the main road, when the GPS instructed him something like "turn left", and displayed a junction with a 90º left turn: he turned left 10 yards too early, onto the railway track, rather than 10 yards later, onto the road running alongside. He had abandoned it on the tracks with the headlights and hazard lights on and the driver’s door open.
It suggests that rather than breaking down, once on the tracks, he was stuck (maybe "beached" on the rails), and couldn't get the truck off the track.I think considering to rely on a external model (e.g. from an online database) _only_ is close to building suicide machines. At least for the coming years.
And also, I think this is a far fetched argument related to OP.
How do we ensure drivers pay attention?
Its enough to keep me aware. I use the GPS, but I don't trust on it blindly and no one should. IMHO.
I find them very useful for navigating through an unfamiliar area, but I mostly see the screen in my peripheral vision because I'm paying more attention to the road and signs, etc. I can see when a turn is coming up because the brightly colored line indicating my path on the screen bends, and I complete the turn having never looked directly at the device. I do look at it occasionally when going straight to have a sense of the next road name, distance until next turn, etc.
Try this if you haven't already, because I found looking at the device too often was disorienting (especially in traffic circles or complex intersections) because the display lags slightly behind your actual position.
You are absolutely right about situational awareness though. That's always top priority and any device that interferes with it should be disabled or repositioned in your field of vision.
This is not a new problem.
1) Its ridiculous... the gps is a guide, not a dictator, and you're still responsible for where you put your vehicle. If the guy was reading a map, he'd have had the same problem.
However, 2) With autonomous vehicles coming, potential places for a vehicle to get stuck should be on the maps...
Edit: Oh right I forgot self driving cars
Interestingly I would have considered the "driver attempt to take car on rails" an uncommon occurrence but just yesterday someone posted a video on the Palo Alto FB page of a Prius turning onto the tracks, then (luckily) backing out and proceeding, to take the actual right turn they thought they were making. Yikes!
I think the convergence of drivers getting worse and self driving systems getting better is going to make this happen very soon.
(E.G. if there is a bridge near by that was built to avoid that issue, send me to it)