So today, let’s pull together a roundup of all the mapping options for your iPhone development, shall we?
1) First off, you’re no doubt aware from posts like this that much of the Maps.app functionality is exposed to any developer through MapKit.framework in OS 3.0 — and for earlier versions you can do more or less the same working with iphone-google-maps-component as we mentioned ages ago. However, if you’re actually planning on making any money off it, the terms of service may very well be an issue, as discussed here. We’ll have to see how that works out.
2) As an alternative to Google, there’s VirtualEarthKit for Microsoft Virtual Earth, also discussed previously here. Unless there’s some specific reason to prefer this, it would seem the path of least resistance has definitely tilted toward 1) with the imminent MapKit.framework now, though.
3) There’s the commercial/free ad-supported option of mapNinja which we mentioned when released a couple months ago, which looks interesting but again probably superseded by official SDK developments.
4) The apparently most popular current option is the BSD-licensed route-me library which, yet again, we mentioned earlier, and can use a variety of sources.
5) And finally, one we actually have not posted about before! Yes, you were starting to wonder why a post with nothing but rehashes, weren’t you? Well, this one looks particularly interesting; the great folks at CloudMade, who wrap assorted useful functionality around OpenStreetMap, now have an iPhone Maps Library!
The iPhone Maps Library lets you build interactive mapping applications for the iPhone. With this API you can
- Build applications that give users a rich mapping experience on the iPhone
- Benefit from our tile servers which deliver mobile optimized maps to your users
- Easily integrate with the iPhone’s location API to show your user’s position in real time
Just like our other APIs, we don’t want to restrict the uses of this API – you are free to create applications that use our maps in any way you like, as long as they comply with the terms of the iPhone SDK agreement. What’s more, this library is open source – so you are free to extend and re-use it as you want.
Well, that’s excellent, isn’t it? The reasonably friendly LGPL for the source license, can’t beat the CC-by-SA data license anywhere, and their API appears to have good documentation, examples, and most important of all, other people have already selected it to do cool stuff with; the apparently well-regarded Trails and OffMaps are reportedly both using the CloudMade library.
So there you go; as long as you’re targeting 2.x users, we’d say that CloudMade deserves to be at the top of your short list for implementation options, and depending on licensing terms, probably even if 3.0 dependence is OK.
‘Course, what we really want to do is get our own topo maps onto the device — come now, if you’re on a ROAD, how much do you really need a map for, after all? — so whenever we get around to seriously comparing libraries, pretty much our only criterion is “so how do we swap our own local tile provider in here then?” which the existence of OffMaps seems to indicate makes the CloudMade stuff the leading candidate for that too!
Continue Reading →