Michal Migurski wrote: > I'm experimenting with a way to get at smaller areas of OSM data (generally > city-sized) for a possible update to http://tiledrawer.com, and I'm hoping to > understand how to both work within the API limitations and be able to > piecemeal together a town-sized area without requiring end-users to deal with > bzip files or osm2pgsql on their own. > > The code I'm developing is here: > > http://github.com/migurski/TileStache/blob/osm-mirror/TileStache/Goodies/Providers/MirrorOSM.py > > It's a provider class for Tilestache that mirrors OSM on a tile-by-tile basis. > > Is there any interest here in publishing the OSM API via tile-like URLs? For > example, being able to make a request like this to pull a chunk of bounded > XML cached out of the OSM API: > http://tile.openstreetmap.org/14/2627/6331.xml <---- note "xml" on the > end > > The advantages with this should be plainly obvious: a source of data that's > trivially cacheable, on the order of hours-to-days old, and available for > specific areas of the world, without the massive download and parse overhead > of OSM extracts.
Besides TRAPI you might be interested in http://wiki.openstreetmap.org/wiki/Tile_data_server http://wiki.openstreetmap.org/wiki/Tiledata2 Mitja _______________________________________________ talk mailing list [email protected] http://lists.openstreetmap.org/listinfo/talk
