Oh! Never knew there were any issues with location. I use Google Maps for navigation and never had any issues.
...which is funny because the Google Map app will leverage the exact same chip within the iDevice.
As you said, spinning this as if it will improve Maps is missing the point of the data itself being poor. If Maps can get us to the wrong location "within centimeters" vs. a few feet as it does now, it's still the
wrong location. I don't need to be taken to a more accurate point when it's the WRONG location. What I'd like to see is that Apple is acquiring a source of much better location(s) data and/or talent that is proven capable of rapidly replacing poor (location) data with better data.
I continue to wonder why Apple isn't devising some kind of querying system that will plot (at least popularly-searched locations) per Apple's database against where Google and other mapping options thinks that same location is. When the results are mostly in harmony, flag that as good data in the Apple Maps database. Where the maps differ, either:
A. adjust the Apple data to go more with the mainstream (multiple sourced) location OR
B. show where other mapping services think it is along with where Apple thinks it is.
I could really only imagine Apple doing A (if that), but that does seem to be a systematic way to fix data weaknesses quickly (at the speed of computer processing).
And APP developers: I for one would gladly pay pretty well for a mapping app that would plot points from multiple mapping (data) sources on the same map (Apple Maps thinks it's here, Google thinks it's here, Garmin thinks it's here, etc). I imagine this would make it much easier to recognize the times when Apple's plot will probably take me to the wrong place as well as the times when Apple's plot is likely right.