You don't understand the point. Google is using other companies' data too. Open google maps in your browser, try scrolling around various parts of the world and look at the lower right-hand corner. You'll see copyrights of various global and local companies and agencies, who provided the data. But in addition to all the data they buy, they also have 7000 people working full-time in house. Which is around 6900 more than Apple has.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Apple Issues Statement Over Day 1 'Maps' Glitches, Maps Team Reportedly Under Lockdown to Fix Issues
- Thread starter MacRumors
- Start date
- Sort by reaction score
You don't understand the point. Google is using other companies' data too. Open google maps in your browser, try scrolling around various parts of the world and look at the lower right-hand corner. You'll see copyrights of various global and local companies and agencies, who provided the data. But in addition to all the data they buy, they also have 7000 people working full-time in house. Which is around 6900 more than Apple has.
Which is a useless figure since we do not know the amount of people working outside Apple in comparison. I think it safe to say that the people who drives cars and flying planes are out sourced and not working for Apple for example.
These images taken from this forum post compare the same maps from the TomTom app and Apple Maps... (click on images for full size)
It seems that Apple's implementation of the data is at fault. The labels have poor spelling and are incorrectly placed or totally missing.
Mainly the wrong maps in a large part of the world and the rather slow rate this got fixed during the beta (although one could make an argument on the beta would be for fixing the app itself).
Also the misplacement of virtually everything around me looks like something that will take a long time to straighten out.
The fact that there are no clear way to really interact (help improve) the maps/data other that from the app itself.
That Apple has limited resources, something international Siri users have experienced (and still experience).
The fact that even huge international cities like New York and Tokyo is so poorly represented in the app also makes me fear for this in smaller countries/areas.
That Google is in full speed here - and it really takes an effort to make even a small dent.
That Maps seems to be limited to IOS only and doesn't attract people on other platforms to participate in making it better.
But the point is, you don't know the number of people working outside Google either. Which can be (and most likely is) 10x as many as working outside Apple.
Exactly, neither of us know, which make the 7000 figure useless since we have nothing to compare it with. We do know that Google have their own staff driving cars and flying planes though, as it was mentioned in the article.
On this point, I am fully on board with you.
There is a difference between "bitching" about something and posting comments related to a legitimate discussion about the shortcomings of a very prominent part of Apple's latest IOS offerings.
Personally, I'm a fan of MOST Apple products. But I am NOT blind to the things that they do that, in my opinion, fall far short of the standards that not only I, but THEY profess to adhere to. And from my experiences and those of plenty of others, this integrated part of IOS6 is a mess.
It's a signature component of their latest IOS, something that they actively touted as a major advancement, something that they actively promoted.
Talking about its' shortcomings (real or imagined!) in a Forum dedicated to discussing THEIR response to the high volume of criticism of their Map App doesn't strike me as "bitching".
Further - if people don't complain (which isn't necc. bitching) Apple won't do anything about it.
Anyway, criticism is not bitching and is quite apt to promote change. Without criticism, no one would ever know what is at fault and what needs fixing. Feedback, discussion, criticism, they promote healthy change.
There absolutely is a difference. But when you clearly state that it doesn't work for you and the alternatives don't work for you and you don't believe it can be fixed, that's bitching.
At that point you have to wait for a fix, eat it, or switch. How is the discussion progressing I'd you've already decided that you don't believe it'll be fixed?
Can stand whining you shut your ear-hole - works for me.
But this is a perfect example of why things aren't black and white. Build quality of the iPhone is miles above anything WP7/8 or Android related, so that weighs in. Other functions in IOS that people use and like. The apps they downloaded and paid for. Why even be angry about people thinking of switching - you will get your iPhone 5 faster, you should be rejoicing.
Seriously - it's unhealthy to be so much in love with a product that you get an emotional response if people criticize it.
Personally, I never said that.
But to your point, it really depends on the individual user and their needs, doesn't it?
I mean, if you use the integrated Map App every day many times a day and its use is critical to your use of the iPhone, then you have to consider your alternatives, including switching.
On the other hand, if you use it once and a while, or it works great in the areas you frequent, then that seems like a pretty extreme reaction.
But detailing and discussing the perceived shortcomings of ANY part of the OS seems to me to be a part of what this Forum is all about. For some people and in some cases, it will appear to be nothing but "bitching". But in some cases and for others of us, it's part of a healthy dialogue. And it doesn't need to be "personal" on either side...
I recommend you do your own analysis of your home area. I went to the TomTom web site for my home location (Southern California) and compared to my phone it appears to be the same (did not check every street). I also went to Wombourn, England (from your post, not familiar with that area) to check the accuracy of this post and if you do so you will see that as you zoom around you will notice that the poster gives an image that does not show about 50% of the information. My guess at looking at the site is that Apple tends to show more street information instead of maybe "city name" information. But again I am not familiar with that area. But I am familiar with my own area which is extremely accurate. I recommend everyone here do the same instead just relying whats others are saying about their area and assuming it is the same in every other area. I ask my daughter to test her area in Miami Florida since she has a TomTom in each of her cars to see if Miami is working the same or not.These images taken from this forum post compare the same maps from the TomTom app and Apple Maps... (click on images for full size)
It seems that Apple's implementation of the data is at fault. The labels have poor spelling and are incorrectly placed or totally missing.
This also ties into the method of gathering data - the StreetView approach rely on a rather large number of people and (although not fully comparable) C3's way of doing this (for 3D) is more effective. So the number of people say nothing about what can be done.
I live a few miles from Wombourne (not Wombourn) and I'm very familiar with the area.
The information on the maps local to me is abysmal. Wombourne is a large country village and is lucky enough to be labeled, even if it is spelt wrong. Five miles away is the city of Wolverhampton (population 250,000), though you wouldn't know it because the Apple map doesn't acknowledge it exists.
I live in the West Midlands, which is 2nd largest conurbation in the UK and the majority of towns in the area are not labeled, no matter how close you zoom in or out. Dudley is shown, though it is placed seven miles away from where it really is in a different county. The village of Himley (shown on the image) is in the wrong place. There are countless errors on the map and I spent an hour last night submitting reports for missing town names and incorrect labels, though I've barely scratched the surface.
I'm pleased your local maps are fully featured and accurate but I would appreciate it if you could bring yourself to accept that many of us are not so lucky and our maps are not fit for purpose.
I can certainly except you and others are having problems. But it seems like most on this thread believe that the problems are universal. Meaning that every part of the world has the exact same problem and I am here to say that at least in my area it is not true. And my "guess" is that I am not not the isolated area but more of a majority. To me it is more like the Verizon vs. ATT arguments that you can use ATT unless you want to make a call then you better get Verizon. Which is obvious more about location then about ATT. Just my 2 cents.......I live a few miles from Wombourne (not Wombourn) and I'm very familiar with the area.
The information on the maps local to me is abysmal. Wombourne is a large country village and is lucky enough to be labeled, even if it is spelt wrong. Five miles away is the city of Wolverhampton (population 250,000), though you wouldn't know it because the Apple map doesn't acknowledge it exists.
I live in the West Midlands, which is 2nd largest conurbation in the UK and the majority of towns in the area are not labeled, no matter how close you zoom in or out. Dudley is shown, though it is placed seven miles away from where it really is in a different county. The village of Himley (shown on the image) is in the wrong place. There are countless errors on the map and I spent an hour last night submitting reports for missing town names and incorrect labels, though I've barely scratched the surface.
I'm pleased your local maps are fully featured and accurate but I would appreciate it if you could bring yourself to accept that many of us are not so lucky and our maps are not fit for purpose.
It's not the same all over the wold - but Your statement about this being only a problem for the minority is a bit of a stretch.
You live in California, the home of Apple. It was bound to work there and it's not a big surprise to hear the rest of the USA has fairly accurate data.
The reports from the UK are very poor, it's so bad it's even made headline news on many of our TV channels and newspapers and I've heard similar reports from other countries. The app itself looks like it has promise but without accurate mapping data it's going to struggle to be accepted.
Based on map data being sourced from different places for different countries?
Why couldn't someone just download the MapQuest app? It even gives users on the iPhone 4 turn by turn voice directions. I get the "outrage" kind of about Maps sucking, but its not the app its the breakdown in quality testing at Apple that should concern people. Hopefully its just a one time thing and we don't start getting crap updates or programs from them anymore then was usual.
First, I did not give a "percentage" when I said a majority. And I did say it was a guess because I did not know. But even if 10% of the people had a problem it would be a serious problem. However, those that say it can not be fixed in a reasonable amount of time just might be wrong. As we all know it is using the TomTom Database and based on reports the TomTom Database is fine in some of the problem areas so it should mean a software problem and not a Database problem. So I believe that a software problem can be easier to fix then simply the data is just not available for that area. However, areas where the data is simply not available then my guess is it may be a very long time before you get service. Kind of like when will LTE come to my town. It may never come there.
For my turn-by-turn, I'm sticking with Motion-X.
I intentionally went off course the other day, and it took me 2 miles traveling at 25mph before it was able to get a connection and "reroute" me to my destination.
It also said that I was still 1.1 miles from my destination although I was at the end pin on my route...
Not responsive enough for me.
I intentionally went off course the other day, and it took me 2 miles traveling at 25mph before it was able to get a connection and "reroute" me to my destination.
It also said that I was still 1.1 miles from my destination although I was at the end pin on my route...
Not responsive enough for me.