5 ms·
What confuses me about Apple's choice of maps here is why they didn't go with OpenStreetMap? It was the perfect opportunity to leapfrog Google and help the open
by grey-area 14y ago
What confuses me about Apple's choice of maps here is why they didn't go with OpenStreetMap? It was the perfect opportunity to leapfrog Google and help the open source community at the same time, and they would have had more control over the data - as it is they are beholden to TomTom and other providers to try to get things fixed, or will have to try to merge future map updates with their own patches. As it is they are going to see increasing controversy as people realise just how bad the maps they have bought are, and that this was changed for political reasons, not for the good of their users, and there's very little they can do about it.
They seem to have tried out OSM in the photos app (with a horrible skin), but to have used purchased data for the street maps. Perhaps they felt it wasn't good enough in some locations they tested?
In my experience OSM is superior to Google maps in many locations (even in parts of central London), and it is of course continually improving.
- vondur 14y agoI was under the impression that Apple did make use of Open Street Maps. http://www.theverge.com/2012/6/11/3078987/apple-tomtom-openstreemap-ios-6-maps-app http://www.theverge.com/2012/6/11/3078987/apple-tomtom-opens...
- grey-area 14y agoThey're not using OSM data most of the time, I suspect it's just for a small amount of data - the OSM credit is a tiny one amongst a whole load of others on their credits page for the maps app. http://gspa21.ls.apple.com/html/attribution.html http://gspa21.ls.apple.com/html/attribution.html It's not clear exactly where they get all the data, and what is used where, but simple searches like Paddington Station are not working (Paddington does, but not Paddington Station), and I'm sure they're not using the OSM vector data (in the UK at least) as it differs and is less complete than OSM in rural areas for example. It would be interesting to know just how they've put their datasets together and what they used from where, but it looks like they use tomtom map data in the UK (along with Yelp places, and perhaps Royal Mail addresses/postcodes).
- awkward 14y agoOpen Streetmaps is a great project, but it doesn't include orthophotography. Even if they were using it, it wouldn't fix the errors with missing or blurry images, cloud cover, or rubber sheeting errors.
- grey-area 14y agoOf course they'd have to get the satellite data from elsewhere (though they couldn't do much worse than the stuff they have frankly), but the vector data and POIs would have been a good start, and probably more accurate and complete than what they have, at least in some countries. They would probably always have to buy satellite imagery. I'd rather have seen more focus on getting the basics right, even if it meant they had to leave out (for example) satellite imagery in the first iteration. As it is they have broken satellite data, broken street mapping, and incomplete place names. If they had chosen to back an open project like this they could have had a team of people worldwide fixing their maps for them, rather than trying to collate and correct thousands of bug reports from around the world and push them out in revisions. I wouldn't like to be on their mapping team over the next few months :)
- rburhum 14y agoOpenstreetmap's doesnt address any of the OP's issues. Having built maps for the past 12 years, I know exactly what of each of those issues are about. The blurry images are underlying base layers that drew first and then probably the upper layer timed out when rendering the tile. The curves are caused by elevation measurements that are incorrect (measuring elevation from a satellite involves bouncing from the ground - when there are structures below, depending on the material, it may go through or bounce differently) or precision problems when generating the elevation grid (very common). The big white thing are clouds, when you buy highly expensive imagery you get them with louds (say 30% cloud blockage) and you need to comnine several images taken a different times, color correct them, and stitch them back to remove it (try to do this for one city and then think about doing it for the entire world). The routes that don't match the pins is weird, but it could be that the snapping point for the routing engine snapped to the wrong street edge (it seems very far though) or that the geocoder and the routing engine use different geocoders (that would be bad). Creating a good mapping product is difficult, but Apple will have something much better in one year.
- grey-area 14y agoThe link is to a rolling blog of images, so you might not be looking at the same images I am. Here is an example of one: http://theamazingios6maps.tumblr.com/post/31923886066/are-you-wondering-where-stratford-upon-avon http://theamazingios6maps.tumblr.com/post/31923886066/are-yo... There are a lot of problems with road map and point data (at least in the UK) which are nothing to do with the points you've raised above, though those are fair criticisms too - however the satellite data is the least of their worries, I'm sure they could buy in a better cleaned up set of satelite tiles if they're willing to spend enough money, and people expect some problems with that, but basic search and mapping is not as complete as it should be.
- smikhanov 14y agoApple will have something much better in one year It certainly will be better but I'm not holding my breath about Apple maps surpassing Google Maps any time soon. Google bought a Rasmussen brothers' company (what eventually became Google Maps) in 2004. That's eight years of product development, data collection, storage and refining -- all at Google's pace. Will Apple find some shortcut to compress this time in one-two year? Unlikely. It's very easy to underestimate the amount of pure, repetitive effort required to build products of this sort and how hard it is to "disrupt" the industries with players like Google.
- VonGuard 14y ago"It was the perfect opportunity to leapfrog Google and help the open source community" The only time Apple helps open source is when they hire the most important people in really important projects, and then they graciously allow them to continue contributing. CUPS, LLVM, it's happened a couple times. They take good care of these guys, but I always feel like their contributions to the projects after Apple are being written with one eye watching over their shoulder to make sure they dont get sued for talking to the public about some super secret project.
- pooriaazimi 14y agoFirst time I heard about CUPS! Apparently it's a kind of printing system. Thanks. http://www.cups.org/ http://www.cups.org/ http://en.wikipedia.org/wiki/CUPS http://en.wikipedia.org/wiki/CUPS
- its_so_on 14y agoyou're not alone. apparently, for many people, occasionally hearing the word "CUPS" is the closest they ever get to printing under Linux.
- emidln 14y agoI'm pretty sure that CUPS was shipping by default on some linux distros as early as 1999. I know I installed Caldera OpenLinux (2.2 or 2.3 maybe?) and Mandrake Linux (version 6 or 7 something) and both had it, detected my printers, and "just worked".
- WiseWeasel 14y agoPeople print so rarely nowadays, it's more economical to go to the FedEx office on the occasions when you need something printed out than to buy a printer and ink or toner.
- nobleach 14y agoHa, hitting http://localhost:631 http://localhost:631 and using the CUPS interface is the easiest ways to fix a few problems on Lion/Mountain Lion.
- andrewljohnson 14y agoOSM is only comparable to commercial data in Europe AFAIK, and there, only in some places. It's not surprising that densely populated areas in Europe/UK are complete and accurate in OSM.
- grey-area 14y agoIt's actually pretty good in some quite remote places, but like all mapping the coverage does vary (see examples elsewhere in this thread of remote places). Probably some countries they'd have to either fill in with commercial data, or sponsor efforts to add data to OSM. The main advantage would be that OSM has all the adding/editing/updating stuff down - that is a major operation and if Apple are trying to do it all themselves while merging inconsistent data from several sources and taking care of customer complaints they'll find themselves falling farther and farther behind people like Google who have devoted years and years of effort and a lot of money to this just to get where they are now. Perhaps Apple considered OSM as a basis and decided it was just too limited in areas that were important to them - it would be fascinating to find out about their internal tools for this and where the data came from but I suppose we'll never know.