quote: So Google's ability to partner with local collectors and providers of regional data in relation to it's mapping service is constrained by it's strategic business function.
quote: As well as the data collectors collecting data from regional sources there are also specialist sectoral sources of data (Yelp is an example) who collect data about a particular topic and which are also a threat to Google's core business and who are thus also unlikely to enter into any agreements to share user data for use in Google's maps.
quote: That works very well on the whole but it is weakest precisely in those areas where entities other than Google own the best data.
quote: So Apple can partner with Yandex the Russian search engine to supply local data for Apple's maps in Russia and let Yandex collect local data because neither Apple nor Yandex are threatened by that data sharing. In contrast Yandex would be very threatened if it had to share it's data with Google.
quote: If that were true, then why is the Google Maps API far and away the most widely used in the world?
quote: it is Google users who submit corrections or amendments to Google maps. In many respects it is like a wiki.
quote: Except Yelp also uses the Google Maps API on all their listings.
quote: Surely the same problem applies to Apple and it's partners? If a company that's not Google has mapping data for a particular area, what says theyre going to go to Apple?
quote: From a technical standpoint, this is probably Apple's biggest weakness. Having to deal with dozens of different mapping companies, each with their own little fiefdoms responsible for mapping various little pieces of the world. This also causes problems with each company supplying it's data in different formats - some vector, some bitmap, some at one scale, some at another scale. All of these have to be converted to a universal format that the Apple maps API can recognise. These are the likely causes of many of the stranger errors being seen on Apple Maps.