The map failure is just another example of where apple's design principle cannot be blindly applied to every product. Apple's top-down approach on software design is expected to fail on Maps. Maps put hard requirement on data, bottom data, nothing to do with your leader's vision. Apple's way out of this is not to engage user input to add missing data or correct data errors --OSM tried that for years, the most accurate data still comes from semi-professional survey-er.
Look at other companies that does map, google map started out using Tele Atlas, NavTeq serves yahoo, bing and mapquest. Let's face it, spatial data cost money to collect and even more costly to update/maintain. Nevteq and Tele Atlas are gigantic companies for serving basic spatial data for a reason.
I guess apple didn't do sufficient data QA before saying, "hell yeah we are going with OSM where every big player is going with commercial data."
Without a solid baseline data, any fancy pants software development would just evaporate in air.
I have to say though, the GUI for apple map and functionality has very high usability. Apple just need to adapt a different mindset when dealing with data-dependent applications.
(disclaimer: I am a PhD student in Geography with CS background, did my share of processing spatial data for the last 8 years)
sorry, just saying that I actually work in the field, not just a bystander saying apple is evil. I would be very happy if OSM in the end works(which I believe it will, just need at least a couple of more years); I would also be happy if apple map were able to fix the problem--which, as I pointed out, is the under-emphasized data issue.
> I guess apple didn't do sufficient data QA before saying
Do you have this on good authority? (seeing your disclaimer and all) Because the way I understood it, they have all the data from TomTom and that seems to work fine - so it seems the problem is definitely not the data but what they are doing with it...? In this case some people in here stated it is an issue with search priorities, the phone suggests a different destination with a very similar name.
Look at other companies that does map, google map started out using Tele Atlas, NavTeq serves yahoo, bing and mapquest. Let's face it, spatial data cost money to collect and even more costly to update/maintain. Nevteq and Tele Atlas are gigantic companies for serving basic spatial data for a reason.
I guess apple didn't do sufficient data QA before saying, "hell yeah we are going with OSM where every big player is going with commercial data."
Without a solid baseline data, any fancy pants software development would just evaporate in air.
I have to say though, the GUI for apple map and functionality has very high usability. Apple just need to adapt a different mindset when dealing with data-dependent applications.
(disclaimer: I am a PhD student in Geography with CS background, did my share of processing spatial data for the last 8 years)