251
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 21 Sep 2023
251 points (90.1% liked)
World News
32365 readers
301 users here now
News from around the world!
Rules:
-
Please only post links to actual news sources, no tabloid sites, etc
-
No NSFW content
-
No hate speech, bigotry, propaganda, etc
founded 5 years ago
MODERATORS
https://maps.app.goo.gl/jmYi6euT36iMbMqq7
Think this is the bridge in question which appears fine on Google Street view.
I thought so! You can actually see that the most recent Street view (May, 2023) has barriers, but how can someone miss the gaping hole, even without signs? The driver would have still needed to drive through the overgrowth :/
This is what they would have seen as they approached the bridge:
Yes, barriers should have been put there, but being a low-speed residential area, the driver shouldn't have missed it. Really strange story, especially putting blame on Google.
EDIT: Barriers were put there, but vandals destroyed them, and they had to be removed ahead of this accident. SOURCE
If he was driving at night in the rain I could imagine that looking like a big dark reflective puddle and not realizing it's a gaping hole until you're too close to stop.
September 30, 2022 in Hickory, NC it rained 5 inches. That is a shit load of rain. It doesn't say when he was driving home, but from 5 PM to 7 PM, it rained 1.7 inches, the peak of the storm. Driving through a wooded, unlit area in a torrential downpour... I'd wager you're right.
Article also says he drowned. In this little creek:
Yeah, it was raining hard.
This is the actual scene.
The overgrowth would have been visible ahead of the bridge, even in rain. I wonder if any dashcam was on board and if speed was also a factor.
He wasn't found until the next morning, so that's not a great indicator of what it would have looked like as he was driving. A few comments up is a picture showing the approach he came from is not nearly as overgrown, also.
The photo showing the actual vehicle in the water clearly shows overgrowth from the day the accident happened. He would have to have driven through it.
It's odd that he was found so late, TBH.
No doubt there were other factors at play, but you can't blame Google for bad weather and poor road visibility, though.
The story here is that the city of Hickory had a responsibility to put barriers and signs up, which they did not. The family is likely going after Google because $$$$$$$$$$$$$$$$$, but they have no case.
But shifting the blame wholly onto the driver is also not reasonable. People thinking "lol, Darwin" damned well know that driving at night in a dark, rural area, you're still going to be driving a decent speed and you might not see something coming. There are classes of problems you have to expect, like wildlife or other vehicles... but there are also classes of things you should not have to worry about, like the map not being updated about a destroyed bridge after 10 years despite having been notified repeatedly.
The city of Hickory bears most of the blame, of course. But the fact that Google does not pay attention when users notify them about dangerous road conditions in their maps is a serious problem, and deserves some responsibility. They can't say "we didn't know" when they actively, aggressively choose not to listen.
Of course, safety measures should have been put in place. The problem is that the family seems to be putting blame on everyone else, and that's also not reasonable.
Yes, but...
"The barricades were removed after being vandalized and were missing at the time of Paxson’s wreck." (source)
Really awful circumstances. If the vandals were caught, I'd have them face an involuntary manslaughter charge.
EDIT: Also, this particular bridge was on a private road that had no "ownership". It actually was NOT the city's responsibility and the developer of that road apparently dissolved... this just keeps getting worse and worse for the family.
Having mapped for Google for years, that's just how it is. Missing roads, incorrect routes, addresses that don't exist, closures that aren't reflected on the map... all normal stuff for every digital mapping service.
The reality is, Google does not bear any responsibility for what happens during the use of the product. No navigation app/company does. It's always in their TOS.
The very nature of maps is that they are ever-changing, and never 100% accurate.
Yes, McDonalds coffee is kept at far hotter temperatures then other resteraunts to extend the life of the coffee. Yes, they did know that it had already caused serious burns from spills.
Still, that woman should have known that coffee is hot and not asked for the cost of her medical bills to be paid by McDonalds when she required multiple skin graft surgeries to heal the third degree burns to her genial area. I mean, come on, how could McDonalds by liable for that?
That's not comparable at all. McDonald's basically sold an unsafe food, so they were liable. Food companies, restaurants, etc. are held to a certain standard for what they service.
Other than being inaccurate (every map ever made is inaccurate), can you explain how Google is responsible for a driver's skill or ability to pay attention to where they are going?
There have been some wild cases of people using in-car navigation and driving off dead ends, into water, etc. We laugh and call them idiots. What else can you do?
I'm probably just old, but there's more than one case of an Internet map telling folks to turn somewhere that there was no where to go because the maps aren't updated. I also used to used the old fashioned paper maps before MapQuest and while those were usually fine, they also don't help in cases of road closures or construction changes.
Whoever's responsibile for the road itself (local municipality or state) should have had it blocked off.
Again, as someone who grew up using paper maps, this is such a bizarre statement. It's cool that map companies offer things like speed trap warnings, but I frequently get warnings about stuff and there's nothing there. You still can't fully trust what the system is telling you. It's just a tool.
"Image capture 2012" This is why it shows still intact. The bridge washed out after this street view was taken.