Hacker News Reader

Maybe it's just me, but I'm not sure how much better Apple could have made Maps before launching it.

I stopped trying to use Apple Maps here in Warsaw, Poland, simply because they get so many of the basics wrong.

Any official document lists my street name as Skorochód-Majewskiego. Even Nokia's new offering can find it. Apple though? Nope, not even anything in the autocomplete list. The only match occurs if you type in the full Walentego Skorochód-Majewskiego. This is true for many streets here. So on that level, their offering is useless.

There were loads of other bizarre issues at launch - loads of parks had their names written in what looked like Chinese characters. Out of sheer annoyance, I went through and marked them all, not expecting much, and sure enough, three weeks later, the names started to clear up.

And this is without going into how obscenely ridiculous it was to see Warsaw's main airport being marked with the German word "Flughafen" in its title.

Even Nokia's new offering can find it. Apple though? Nope.

Nokia owns Navteq, which is one of the premier providers of GIS data. They're actually better positioned then Apple in this space.

Nokia owns Navteq, which is one of the premier providers of GIS data. They're actually better positioned then Apple in this space.

I'm not sure that the data's to blame. For comparison, I've just given CoPilot Live a try with a couple of other streets (Korotyńskiego and Dickensa to be precise), and the UI presented them to without any difficulties.

These aren't new streets, they're on every map out there, and I'm convinced that this is a programming issue of not handling the data correctly. It's not even a case of doing cleverness with letters such as ń or ó - it's a complete failure altogether.

I was in Warsaw a couple weeks ago, and it worked fine, but I'm an English speaker, so not as sensitive to things like "Flughafen".

Firstly, Apple certainly could have provided public transit directions. Plenty of third party apps already did this (or at least claimed to), so there's no real excuse there.

Another issue is the goofy cosmetic problems with the 3D maps. Of course, you could argue that it's still "a data problem," but it's not the type of data problem that magically gets better as more users use the app.

Lastly, there are usability issues that have nothing to do with data. As another user noted, I can only view navigation either fully zoomed in (with slightly variable tilt that doesn't even work well) or fully zoomed out. The overview shows a list of all the turns, but doesn't let me click on each one to zoom in on it (like every other directions app I've seen). It doesn't show speed or any other useful statistics except for estimated duration and distance.

The old GPS app I used on my iPhone 4, which I believe was Navigon, was a far superior product even ignoring the lackluster data of Apple Maps.

Its frustrating because the old Maps did in fact let you click on the individual direction instructions to zoom into them.

Sigh, we need to stop with that annoying "maps will magically get better with usage".

No, they won't. Stop claiming that. There is no magic algorith m to fixup maps based on people being given wrong data. Even if some people will give some feedback, that requires humans to process that input and translate it into map changes. Which can take a loong time.

They will get better with that feedback. Without the feedback, there is no way to improve them. It's simply not possible for 1 company to go around the entire world mapping every business and address in any reasonable timeframe. The only way to do it is by accepting and processing feedback.

So you first argue that it won't get better with usage... But then admit that yes, it will get better because feedback gets taken into account.

Which is it?

I think their problem is much worse than just being a question of improving data quality. They seem to get data from a lot of very different sources, and those simply do not fit together.

For example, in Stockholm Apple's map still shows most buildings as lying in the middle of some street. On the other hand, only relatively few businesses seem to be located in some kind of building. There seem to be quite obvious, and systematic, errors all over the place.

Compared to the last time Google switched mapping databases, which I think was about three years ago, Apple Maps (for my town at least) has been remarkably accurate. For several months, Google Maps was putting my home address more than a mile from where I actually live (right in the middle of a major city, so a mile is a world away), and it refused to parse addresses for at least a couple of major commercial roads with unusual names. I don't think I've been able to find a single comparable problem with Apple Maps. Visual glitches don't ruin my day nearly as much as refusing to parse a business' address or placing it a mile away from where it is.

I still use Google Maps (via the web now), though, since I prefer the way it presents traffic data.