Where I live there's a disused pedestrian/cycling bridge over a river, with no paved road whatsoever leading to it on one side. There's a mud "road" there which I wouldn't risk driving on in anything other than a tank or a tractor (my farmer neighbor does drive his tractor there and across water, so there's that). The bridge has never been made for use by vehicles other than bicycles since its inception.
Nevertheless, when trying for navigation guidance to the street on the other bank of the river, many map applications insisted I could drive right across that disused bridge. Until recently, only OpenStreetMap and Google Maps presented the correct information. Apple Maps, TomTom, and Sygic all insisted I had to drive right across mud and the disused bridge (that would not be suitable for a car anyway).
These maps also reported there had been a street in the other part of the town where there was only barely a boundary between two fields.
I've been reporting this via Apple Maps feedback, complete with photos, for three years straight with no response whatsoever. I think one of my feedbacks just had been closed. Then a year ago Apple Maps got refreshed and their data sources got better, at least now they don't show roads where there are none.
Google Maps used to navigate me in the wrong directions on one-way streets months, if not years, after the changes had been made. They also seem to choose the shittiest routes ever when driving from any A to B, like the narrowest unmaintained countryside roads with steep gradients, and ETA seems to be drugs-induced fiction, like their information on speed limits and the actual speed attainable on those roads is waaaay off.
OSMAnd and OSM data in general is way better, I only wish it was recalculating the routes faster. Oh, and live traffic information.
I'm glad at least there's some movement to have some accountability about that clusterfuck. But then again, whom am I kidding, that won't move the needle in ad sales so nobody's giving a shit.
Nevertheless, when trying for navigation guidance to the street on the other bank of the river, many map applications insisted I could drive right across that disused bridge. Until recently, only OpenStreetMap and Google Maps presented the correct information. Apple Maps, TomTom, and Sygic all insisted I had to drive right across mud and the disused bridge (that would not be suitable for a car anyway).
These maps also reported there had been a street in the other part of the town where there was only barely a boundary between two fields.
I've been reporting this via Apple Maps feedback, complete with photos, for three years straight with no response whatsoever. I think one of my feedbacks just had been closed. Then a year ago Apple Maps got refreshed and their data sources got better, at least now they don't show roads where there are none.
Google Maps used to navigate me in the wrong directions on one-way streets months, if not years, after the changes had been made. They also seem to choose the shittiest routes ever when driving from any A to B, like the narrowest unmaintained countryside roads with steep gradients, and ETA seems to be drugs-induced fiction, like their information on speed limits and the actual speed attainable on those roads is waaaay off.
OSMAnd and OSM data in general is way better, I only wish it was recalculating the routes faster. Oh, and live traffic information.
I'm glad at least there's some movement to have some accountability about that clusterfuck. But then again, whom am I kidding, that won't move the needle in ad sales so nobody's giving a shit.