One of the cool things about building a map on top of quality Open Source products is the ease with which one can extend the possible uses of your software. <\/p>\n
GDAL 1.5 has gained the ability to read a WMS-C style remote tile cache directly: this means that any tool which uses GDAL as an image provider can read remote tile caches directly. The one that matters the most to me is MapServer: MapServer has the ability to load up a simple config file — http:\/\/openaerialmap.org\/static\/gdal_wms.xml — and use that in a mapfile: Using With MapServer<\/a>.<\/p>\n Not running the bleeding edge GDAL? That’s fine: Instead, you can use the WMS that’s hosted by the OAM project: Using With WMS<\/a>. This means that any WMS client — including those fancy schmancy ESRI tools that speak WMS. (There are at least some of them, I think.)<\/p>\n Your application only speaks in WorldWind? Well, we can take care of that for you: With a WorldWind<\/a> metadata file, you should be up and running in no time. (In my experience, unfortunately, this is true in ossimPlanet<\/a>, which has no problem with the file, but WorldWind itself seems a bit touchy about it once you zoom past the first couple levels. But I can only do so much.)<\/p>\n Using the new plugin-friendly TileCache that I rewrote last night, I was able to add support for the Mobile GMaps<\/a> client — Using With MGMaps<\/a> — in just 20 minutes. Similarly, a user reported success using the tiles with Maemo Mapper<\/a>.<\/p>\n Of course, it can be used with OSM — either as a tile backdrop, or in the OSM editing application (JOSM): Using With OSM<\/a> — due to the above plus TileCache’s TMS support.<\/p>\n