How about you try again with a point that actually makes sense, you fucking cock gobbler. The issue at hand has nothing to do with proper programming.It's called proper programming. The question of people's stupidity is besides the point, it's about the quality of service from a product people paid for. Dumbass.
apple cut off its nose to spite its face with those maps, pretty unreal they'd deploy something that is so astonishingly shitty. Wait until it's done before releasing it.
http://theamazingios6maps.tumblr.com/
I've been on iOS 6 beta for a while and only used the new Maps a little bit. The only problem I had was that it couldn't find a hospital that had just been built in my city. Really, it was only operating for a few days at that point. Maps need constant updating, so that's 100% understandable.Mapping isn't just drawing some lines and calling it a day. There's a lot of back end GIS data that goes into making them functional and accurate. Which is ultimately the problem with Apple Maps. Google has spent the last eight years creating their mapping program, and have been very meticulous about it. Primarily because Google is first and foremost a search company. As a result, Google Maps is the best and most accurate map product available to consumers.
Apple is first and foremost a hardware design company. They don't have any experience in mapping and search and they're basically starting from scratch. What they've come up with is okay but far from perfect. It will be a very long time before it is perfect, if it ever does. Unfortunately Apple has escalated their war with Google to the detriment of their users, by offering an inferior product. Hopefully Google develops their own proper apps map to replace it.
Mapping isn't just drawing some lines and calling it a day. There's a lot of back end GIS data that goes into making them functional and accurate. Which is ultimately the problem with Apple Maps. Google has spent the last eight years creating their mapping program, and have been very meticulous about it. Primarily because Google is first and foremost a search company. As a result, Google Maps is the best and most accurate map product available to consumers.
Apple is first and foremost a hardware design company. They don't have any experience in mapping and search and they're basically starting from scratch. What they've come up with is okay but far from perfect. It will be a very long time before it is perfect, if it ever does. Unfortunately Apple has escalated their war with Google to the detriment of their users, by offering an inferior product. Hopefully Google develops their own proper apps map to replace it.
While it's their first attempt, Apple has been working on this for 5 years. Since 2007. They bought 2 mapping companies and are using TomTom data along with theirs. That's pretty long time.
you have no idea how much work it is to correct geospatial data.
See above. After how many years, Google maps still hasn't got it right.
You know, Google Maps and iOS 6 Maps tries to direct you to a point that you can reach by car (by default). You shouldn't expect it to put a waypoint directly on the monument in the middle of the grass and pedestrian walkways.
For instance, when I put in an address in Google Maps, it often positions the arrow approximately where it thinks that number would be along the road. It can only attempt this if the database shows which end the numbering starts at. If Google's database doesn't know where the numbers start and end, the waypoint is directly in the middle of the road (length-wise).
One big reason: Google has 1,100 full time employees and 6,000 contractors working on its mapping products. Those 7,000 people do all sorts of granular work.
...
Excluding its retail army, Apple only has 13,000 employees in total.
Is it really ready to increase that number by 53%?
Well, that doesn't explain why Google positioned Buckingham Palace so far away from where it is actually located.
How about you try again with a point that actually makes sense, you fucking cock gobbler. The issue at hand has nothing to do with proper programming.
Returning "London, Ontario," in a search for London originating in North America is not buggy in the slightest.Yo cumdumpster, so a product that is buggy as hell has to do with what then?
While it's their first attempt, Apple has been working on this for 5 years. Since 2007. They bought 2 mapping companies and are using TomTom data along with theirs. That's pretty long time.
In keeping with Google's more-data-is-better-data mantra, the maps team, largely driven by Street View, is publishing more imagery data every two weeks than Google possessed total in 2006.
you have no idea how much work it is to correct geospatial data.
Returning "London, Ontario," in a search for London originating in North America is not buggy in the slightest.
Seriously, people are complaining about "London" returning London, Ontario, rather than London, England? Well guess what, you morons, if you want to search for the London NOT in this continent, how about you learn how to refine your fucking searches.
The stupidity is strong within you.
Why b/c you're expected to swim across the Atlantic Ocean like Google?