I don't care about the maps thing, it's really not that bad.
Please stop...PLEASE stop with these 'it's not that bad' or 'it works for me' or 'Google had years to perfect their map app' posts. What utter nonsense!
Glad you don't think it's that bad.
Glad it works for you.
And who cares how long Google has been working on their map app?
The fact remains that Apple replaced a highly functional and mostly accurate map application with a piece of junk- and integrated it into the OS.
That integration creates a whole other level of issues. For example, when you click on an address in your address book, the MapApp will open and show you where that is. If the data is incorrect, you will get an incorrect location. And if you try to navigate from there to another place, you will be relying on the accuracy of the two locations and all of the points in between. And this has the potential to make the original bad data (if it is bad) worse.
Additionally, developers use Apple's maps and MapKit as the framework that they build on. That will compound the problem. And MapKit is used as the framework for a variety of applications, including 'Geofencing' and things like that.
Lots of people have posted, "Well, just download the Google Map website on Safari and use that instead".
But it's not that simple, particularly if you are using a built in function like Address Book, and even more so if you are a developer. You're essentially "forced" to use MapKit, and you build your data and actions on top of that.
If developers wanted to use Google Maps instead for example, it would mean that Google would have to provide a framework for it to them to use, that developers would have to explicitly use that framework instead of MapKit and that Apple would have to approve apps using that framework.
It would also mean that developers who have built built apps on top of MapKit for about 4 years now would have to learn that new framework and port their apps all over again. (I recognize that this isn't EXACTLY how it works, so sophisticated developers, please don't slam the post because it simplifies things to the degree that it does.)
The point is that the potential problems with the current MapApp in IOS6 go way beyond not being able to find an accurate location for your neighborhood Starbucks!

It's clear to me that Apple was more interested in having "Superman" fly through the skyscrapers of New York City for their propaganda presentation than actually having a functional application that can accurately get you where you need to go.
And all you have to do to understand just how bad the Apple Map App is is to realize that the head of the most highly capitalized company on the planet had to come out and post a letter, sincere or otherwise, apologizing for a sub par product.
All you have to do is read the comments posted by many people on this website and many others documenting an embarrassing array of errors, inconsistencies and poor execution.
And all you have to do is read the comments made by people who write about this stuff for a living to recognize that EVEN APPLE thinks this is a bad product.
And it really does make you wonder whether anyone actually looked at the nuts and bolts of the product before it was released, particularly since many developers who had access to the betas complained about the Map App right from the start, or whether the PR machine simply drowned out any chatter that was inconsistent with what they wanted to hear.
And in the LONG run, that's more of the problem- if hubris is what caused this, THAT is more of an issue than a lousy Map App.