Apple Maps and the city it couldn't find
On a December morning in 2012, Victoria state police in Australia issued a formal public warning against using a piece of software on an iPhone. Drivers following Apple Maps directions to Mildura — a city of 60,000 people on the Murray River — were being deposited instead in the Murray Sunset National Park, a 1,900-square-mile expanse of scrubland with no water, no phone reception, and temperatures that regularly reach 115°F. Several had been stranded for up to 24 hours. When police tried to reach Apple about the problem, the company did not return their calls.
Apple had placed Mildura 44 miles from its actual location. Police called the error “potentially life-threatening.” This was three months after Apple Maps had launched.
The app appeared on September 19, 2012, bundled with iOS 6, and replaced Google Maps as the iPhone’s default navigation service — a position Google had held since the original iPhone in 2007. Apple’s contract with Google hadn’t included voice turn-by-turn directions, which Android had offered since 2009. So Apple built its own mapping stack from scratch, pulling together a series of acquisitions: Placebase (2009), Poly9 (2010), and C3 Technologies (2011). It launched iOS 6 and, on the same day, pulled the Google Maps app from the App Store.
The errors surfaced within hours. London searches sent users to London, Ontario. Paddington Station vanished from central London. Helsinki’s main railway station rendered as a public park. In Wales, Pontypridd appeared six miles northeast of its actual position. Bridges in Tacoma and elsewhere warped in satellite view as though they’d melted into the water below — artifacts of a 3D compositing algorithm that couldn’t distinguish a road surface from its reflection.
Within nine days, Apple’s CEO had seen enough. On September 28, Tim Cook published an open letter that was, by Silicon Valley standards, genuinely unusual. “We are extremely sorry for the frustration this has caused our customers,” he wrote, then recommended that iOS users download Bing, MapQuest, and Waze — Apple’s CEO, on Apple’s letterhead, directing customers to competitors. The company had not done anything quite like it since Steve Jobs apologized for overcharging early iPhone buyers in 2007.
The internal reckoning was quieter but sharper. Scott Forstall, the senior vice president for iOS, had reportedly refused to sign the apology letter. He left Apple in October 2012. Richard Williamson, who had led the mapping team, was replaced by Eddy Cue the following month.
What Apple Maps made visible was something the mapping industry already understood: a geographic database is not software you can iterate toward correctness on a quarterly release cycle. Google had spent seven years building street-level datasets, correcting billions of business listings, and absorbing user-filed corrections at planetary scale. Apple’s problem wasn’t a quality shortfall — it was a time-and-scale problem, and no acquisition could compress those years into months.
The Mildura error was corrected within weeks. The broader reconstruction — dataset by dataset, acquisition by acquisition — took years before professional reviewers stopped recommending alternatives by default. By then, Apple had learned what every cartographer since Ptolemy already knew: no one gets the coordinates right on the first pass.
Sources
- Apple Maps — Wikipedia — launch date, acquisitions (Placebase, Poly9, C3 Technologies), specific errors at launch, Scott Forstall and Richard Williamson departures.
- Apple Maps flaw could be deadly, warn Australian police — CNN — Mildura mislocation, stranded drivers, police warning details.
- Tim Cook apologizes for Apple Maps — TechCrunch — full text of Cook’s September 28, 2012 letter and recommended competitors.
- Apple’s mapping goes in the wrong direction — The Globe and Mail — specific launch errors: London Ontario redirect, Paddington Station, Helsinki station.