Thank you for the detailed explanation. Since Waze is owned by Google, what actual options does Apple have to bring their maps accuracy to the same level, worldwide?
Thank you, and what you're asking is fairly simple to address, in a nutshell, with the caveats that deep, dark financial posturing lies afoot and it depends on how much money Apple wants to spend.
First, there's aerial photos. Look up
MrSID and
JPEG 2000 file formats - they're key to the back end, the first is lossless and the second is lossy, but it's the ability to embed metadata in each format that makes them valuable. When I consign an aerial, I get a MrSID file as a deliverable - each pixel is scaled, down to a pixel representing a 6-inch square - not bad from around 21k feet up, and there's an anchor point to work with, and this file is generally XREF'd in as you'd reference a file in PS, FCPX, or any GIS/CAD application. They're referenced in from a server largely due to the fairly large file size - a high-res file that generally covers acres or hectares. For viewing by a client, the MrSID file is converted to a TIFF file that doesn't contain the metadata. For later processing not in house, the image file is converted to JPEG 2000 that does contain the metadata. The metadata in the image file is tied/anchored to the relevant 0,0,0 reference point. Generally, this aerial is the
only raster file we work with in a project no matter the file format. Remember this bit, the anchoring part...
Almost all of the remaining work that's relevant is vector-based and, again, tied to an anchor point (survey control points IOW). Depending on the application being used, just about any kind of output can be generated to be processed in another application. The two beasts in the room are Autodesk's AutoCAD and Bently MicroStation - they've been around for decades. Both are extensible, and extraordinarily powerful, with Bently's app actually having a built-in environment that mimics - not emulates - the entire AutoCAD command environment. The file format of choice is AutoCAD's DXF - DXF files can be opened by dozens of applications, even Adobe Illustrator, which I use to dress up a viewable image for presentations. The point here is that these files are vector-based, and DXF files and variants of them include a metadata database generally in 3D
and they can be edited and amended. The accuracy is only as only as good as the original source files, of course. Almost all of the work I get from surveyors is accurate to one-tenth of a foot (a little over an inch). (Side note: architects think in sixteenths of an inch, engineers and surveyors think in tenths of a foot - don't get in the middle of that argument...).
FWIW, I generally don't do "TL;DR". I use dictation software, it's quicker for me...
When I started seeing Google's vehicles around my project sites, several years ago now, their drivers were gathering what would be street view images and verifying street sign names. The latter bit must have been a bit of a nightmare in cities like Paris, where a street name can go for miles or one city block - ugh. What I would have done, using an example in the US but very similar elsewhere in the world with a few exceptions, is buy/lease GIS data and a county map directly from each county surveyor and pay someone to tie in that data to their "world map" - right now, they're already doing that with TomTom as the middleman and paying the vig for their work...
There's a couple of issues with all of this. A frustration that I have long held with TeleAtlas is the inaccuracy of their mapping due to not properly setting control points - control point of the base of the map (the "picture" that we see) is not aligned with the control point related to POIs and addresses, which leads to your house being around a mile down the road from where it's actually at. For Google, for Benz owners, for real estate agents and a bunch of the rest of us using devices that rely on TeleAtlas data - that's a problem (duh), and I only get that stuff fixed when I hire my Dutch translator. I've lost hair and time over this crap, and I'm not the only one. Google addressed this by hiring a bunch of drivers and investing billions - that's billions with a "B" - in high-resolution imagery satellites to take pictures of the world; Google sold those satellites to an imagery company last year with an agreement that Google will have access to products from that company.
Regarding the politicking, that's a bit of a tricky one. If Apple really wants to get a decent product in its devices, I'd approach Verizon with a bit of coin on the table. Verizon owns AOL, which owns MapQuest - believed to be the second-most widely used mapping service after Google's product. Going "open-source" here might not be an option, contractually, as AFAIK the open-source options rely partly/wholly on MapQuest data for mapping and traffic/routing (plus OSRM - "Open Source Routing Machine"). With the way Verizon is closing down some of their purchases, they might be open to selling MapQuest to Apple.
In closing this out, Apple could just throw money at base data and then overlay their own custom work on top of it, just as they've been leasing base data from providers around the world. Mercedes has told the owners of its older vehicles that last year is the end of map updates - they are TeleAtlas-based (and about as inaccurate as Apple Maps is in some areas!) - and they're starting to put HERE WeGo map data in their newer vehicles (I'm not moving on from my E63 anytime soon anyways...). Two of my largest clients are moving away from TeleAtlas as well, buying data from Verizon's MapQuest, and another one is buying direct from MS. I wouldn't be surprised if TomTom is in its second phase of panic (the first being when their nav device prices tanked after Google Maps hit the street) and considering shopping TeleAtlas around.
Apple's farming out some of this work to designers/engineers in India leads me to believe that they're serious about the next step, relinquishing direct control over this work, incorporating drones for detail work, seeing Apple vehicles on the road. Yes, their work can be very accurate. Still, IMO, they've got to cut TeleAtlas loose, at least here in the US. FWIW, I have used a TomTom nav in Europe, it was great but I'd rather have Navteq/HERE data in North America. Over and out!