I would agree, however if this statement from the article can be proven:
The lawsuit adds that Google had previously been notified about the collapse and several attempts had been made for the route information to be updated.
Then there might be an argument that Google was negligent in not updating it’s maps. I’d agree that it’s a weak argument and that the Terms of Service likely contains a clause like “you are responsible to watch out for road conditions”. But, if the bridge has been out for a decade and multiple attempts to update Google about the collapsed bridge had been made, that may rise to the level of negligence.
I encountered this issue too. An overpass near me was demolished but Google Maps was still showing it there. I submitted an edit and included a link to the state DOT’s website about the project that clearly stated the overpass would be permanently demolished and not replaced. My edit was rejected.
I’m a local guide, although I haven’t really done much in ages. Still, one day not too long ago I was standing in a new business that wasn’t on maps yet. I added the business, photos, hours, even their phone number and it was immediately rejected.
Sometimes you can get small changes approved but change more than one or two things and it’s immediately rejected too. Doesn’t help much with saying “road isn’t here” though.
I tried to report a restaurant as closed. I was looking forward to eating there while out of town. It was empty, had a big CLOSED sign in the window, and was surrounded by construction equipment and road barriers. I took pictures of all of this and they still rejected my edit.
They did approve my addition of a river access in the middle of nowhere, though.
In fact, all drivers are always required to watch out for road conditions, regardless of whether they are using Google Maps, TomTom GPS, AAA Triptiks, the Rand McNally Road Atlas, or a sketch on the back of an envelope.
No map is going to tell you about a moose standing in the middle of the road, after all.
I would agree, however if this statement from the article can be proven:
Then there might be an argument that Google was negligent in not updating it’s maps. I’d agree that it’s a weak argument and that the Terms of Service likely contains a clause like “you are responsible to watch out for road conditions”. But, if the bridge has been out for a decade and multiple attempts to update Google about the collapsed bridge had been made, that may rise to the level of negligence.
I encountered this issue too. An overpass near me was demolished but Google Maps was still showing it there. I submitted an edit and included a link to the state DOT’s website about the project that clearly stated the overpass would be permanently demolished and not replaced. My edit was rejected.
Google’s editing algorithm is atrocious.
I’m a local guide, although I haven’t really done much in ages. Still, one day not too long ago I was standing in a new business that wasn’t on maps yet. I added the business, photos, hours, even their phone number and it was immediately rejected.
Sometimes you can get small changes approved but change more than one or two things and it’s immediately rejected too. Doesn’t help much with saying “road isn’t here” though.
I tried to report a restaurant as closed. I was looking forward to eating there while out of town. It was empty, had a big CLOSED sign in the window, and was surrounded by construction equipment and road barriers. I took pictures of all of this and they still rejected my edit.
They did approve my addition of a river access in the middle of nowhere, though.
In fact, all drivers are always required to watch out for road conditions, regardless of whether they are using Google Maps, TomTom GPS, AAA Triptiks, the Rand McNally Road Atlas, or a sketch on the back of an envelope.
No map is going to tell you about a moose standing in the middle of the road, after all.