|Not San Francisco|
Vector Support in Maply
I've had support for vector data in WhirlyGlobe since 1.0. With version 2.2 it's gotten much better, specifically for map display. The important bit was the MaplyQuadPagingLayer and the MaplyPagingDelegate protocol.
It works like this. You provide an object that supports the MaplyPagingDelegate protocol, start up a MaplyQuadPagingLayer and wait for the callbacks. When it's time to load a tile, you load your data, convert it to a displayable form and then hand it over. The system cleans it up for you when it's no longer needed.
Now we can treat vector data like we do image tiles. If only we had a good data source...
A few months ago OpenStreetMap began providing vector data tiles experimentally. Mike Migurski was the driving force behind it, and he explains it better than I.
The short of it is, we've got vector data chopped up into individual tiles, with some basic cartographic choices made at the various levels. The server responds much like an image tile server, but it returns GeoJSON.
That's great, but how well does it all work?
Base Map + Vector Overlay
There are two sorts of vector maps we might want to display with Maply. The first is comprised of vector data overlaid on an image base map.
That's the easier case. It's a subset of the full vector features, including roads, labels, and buildings. More importantly, the polygons are fairly simple. Which leads to the next question: How about everything?
Pure Vector Map
An entirely vector based map is the goal, at least from a technical standpoint. With pure vector on one end and pure image on the other, we'd like to dial in the appropriate mix for a given app. The OSM data is there, so how well does it work?
It works well. Quite well indeed. That's the big innovation from a few months ago: WhirlyGlobe-Maply 2.2 can handle the weird polygons it gets from the server. The tessellation is working well even for complex polygons with holes.
Room For Improvement
Nothing's perfect, of course; that would be creepy. There are a few areas that could be better, in no particular order, they are:
- Parsing GeoJSON is just slow. It needs to be faster.
- A binary vector data cache would make things appear much faster. For some cases it would be a big improvement.
- The vector data is coming in tiny little chunks. This is messing with the drawing optimization. There are ways to fix this.
- Place names are dominating the display in cities. For a real app, I'd suggest making some cartographic choices.
- It needs more styles. I've broken out a few of the feature types, but more is better.
Even so, this is usable as is. Go check out the code, all open source, and give it a try.
I build out serious toolkit functionality with serious apps. On the WhirlyGlobe side I've had some great clients who did some really ambitious things. There's been some interest on the Maply side, but so far nothing really big. The toolkit is ready (more than ready) so as soon as I reel those clients in, we should have some interesting results.
In the mean time Maply vectors are pretty stable. Go give the OSM example a look and feel free to use it in your own apps.