Australian Police Warn That Apple Maps Could Get Someone Killed
First time accepted submitter jsherring writes "Police in Victoria, Australia warn that Apple's glitch-filled Maps app could get someone killed, after motorists looking for the Victorian city of Mildura were instead guided to a wilderness area. Relying on Apple Maps to navigate through rural Australia seems rather foolish but it has become common practice to rely on GPS navigation. Besides reverting to google maps, perhaps Apple should provide strong warnings to use other navigation sources if navigating to remote locations."
As much as I enjoy a good old apple bashing, anyone who trust their gps without checking the plausibility of the route is an utter fool.
iLost? *ducks*
Apple would be leading us out of the wilderness, not into it!
Wasn't Apple using Open Street Maps?
The article notes that Apple used various data sources, but explains that there's no reason to think the data sources are at fault here.
Open Street Map correctly locates Mildura: http://osm.org/go/uHcWMmj-?m
Oh my... Now I can't stop picturing a naughty Siri giving me turn by turn navigation in the middle of nowhere.
"Take the next right."
[Stops and scratches head upon seeing it's a dirt road.]
"For real. Get onto that dirt road."
[Proceeds and drives a few miles.]
"At the next kangaroo, turn left."
[WTF?!?]
Before there is too much stupidity, if you've never been to Australia, please realise:
1. It's huge. Really huge. I live in one out of two of the closer-together cities in Australia, and they're about 800kms apart. In the other direction, the next major city is 2,500kms away.
2. It's mostly empty (in terms of civilization). Think of driving through rural Utah or Arizona, which are quite similar to the Australian bush.
3. It's mostly flat and full of similar looking landscape.
4. National parks and non-national park areas often look quite similar.
5. There's usually only one or two ways to get around in the country.
6. Mildura is a small town in the middle of bloody nowhere. If I was driving there from here I'd expect to pass through a handful of tiny settlements on the way.
So if you are relying on your GPS to get you somewhere outside a major city, it's actually quite plausible and reasonable that you might not have much idea that you're being led off in the wrong direction until you (don't) get there.
It's also quite plausible that you can die - it has happened before. People get lost, they run out of fuel, they don't have water, the temperature easily gets up into the 40-50C range and - dead.
Read Pynchon.
People managed to navigate without all this garbage.
And if their maps wrongly placed their destination in completely the wrong place, they'd be equally screwed.
What's your point?
Read Pynchon.
If you are trying to get to a residential area, and instead take a dirt road into a wilderness area, while blindly following your GPS, and you get eaten by a crocodile, you deserve the Darwin award you're about to get.
The problem is that in Australia you sometimes do have to take dirt roads through wildnerness areas to get to residential areas. Sometimes for hundreds of kilometres.
http://michaelsmith.id.au
for those that do care ... no crocs ... just emus, kangaroos, snakes, etc ...
pretty damn difficult to die there except from exposure to the heat
i.e. Pretty easy to die there from exposure to the heat.
The root cause of this, and many of the other errors in city location observed throughout Australia, is actually quite simple and I don't know why Apple haven't fixed it yet. It was a bit of a facepalm moment when I realised what was actually going on with the Australian maps on iOS6.
Basically there are two problems:
1. Apple Maps is marking the centre of local government areas (analogous to a county, for American readers) as a point location, rather than a name for a large area of land (i.e. it's treating them as locations you can navigate to); and
2. In the case that a search query matches both a local government area name, AND a town name ... it preferences the local government area (which as mentioned, is being mapped as an exact point roughly in the middle of the area, generally in the middle of nowhere)
For example, follow the Hume Highway south from Sydney a little way and you will see a point marked as Wingecaribee, east of the highway, roughly in the vicinity of where the town of Moss Vale is (though, as noted, the GUI chooses to display Wingecaribee prominently, but doesn't mark Moss Vale or any other towns at all, unless you zoom in really close). The point marked as Wingecaribee is just a random spot in rugged forested terrain. Nothing's actually there. This is simply the centre of the Wingecaribee Shire. But there is no actual town called Wingecaribee so apart from looking weird, this doesn't hurt anything.
BUT ... keep following the highway south and you will soon come to the next shire, Goulburn Shire. Again, the centre of this local government area is marked as a point, called "Goulburn" and again, it's not anywhere near anything. It's in the middle of some random farmer's field somewhere. BUT THIS TIME, we have a problem, because within Goulburn Shire, there is actually also a town called Goulburn. But if you search for 'Goulburn', you are directed to the centre of the Goulburn Shire, NOT the town. This is completely retarded, as noone ever searches for things by local government area name in Australia (many people don't even know the name of their LGA ... they aren't as prominently known as counties in the US), and even if they did, wouldn't want to be directed to some arbitrary point near the middle of it with no regard for whether there's anything there.
This is what has happened in TFA too. There is a Mildura local government area. Within that, there is also a city called Mildura. But the city isn't marked; only the centre of the LGA. Which as stated, is in the middle of bloody nowhere.
Basically whoever processed the Australian mapping data has interpreted LGA (shire, county etc.) names as locality (town, city) names. And has given them prominence in both display and search results over actual localities. Should be simple to fix, surely. The data is there - it's just being used incorrectly.
Its exactly this.
The Apple apologists are suggesting that you shouldn't trust a map application, but should somehow magically trust other map sources.
The flaw in this thinking is that if a popular mapping company was selling paper maps at local gas stations that sent you in the wrong direction into the middle of nowhere, then we would also expect a government office to come forth and announce the serious risks associated with trusting that particular paper map.
On top of this, the iPhone maps are now different than the one they used to provide.. the old one was of much better quality. So a person may have come to trust the maps built into their iPhone because they were of good quality, but now suddenly they arent of good quality even though its the same damn iPhone. That "upgrade" was actually a full-blown downgrade.
So yes, we expect the government to announce the risks associated with trusting Apple's maps, because not only are they no longer good maps, Apple after the fact went and edited everyones existing maps to be of much worse quality.
"His name was James Damore."
Isn't Darwin further up north?
not according to Apple
---
Oh yeah, Siri should just come on every 5 minutes while navigating and say "Just to let you know, I have no idea where I'm going."