[OSM-talk] Mapnik+OSM and TileCache
mikel_maron at yahoo.com
Sun Nov 26 16:41:30 GMT 2006
Nice work Chris
Looks like this demo auto-resizes in IE correctly .. can this solve the problem with OSM index-new.html?
(sorry if this is already discussed, I missed some of that thread earlier)
Also, am I correct understanding that the WMS-C spec itself can not support GoogleLike schemes,
because the origin is in the upper-left, while WMS-C specifies that the origin is the lower-left?
Anything we can do on that, to extend the spec for this?
----- Original Message ----
From: Christopher Schmidt <crschmidt at metacarta.com>
To: talk at lists.openstreetmap.org
Sent: Sunday, November 26, 2006 3:28:20 PM
Subject: [OSM-talk] Mapnik+OSM and TileCache
After a heck of a lot of hacking last night, I finally got OSM rendering
via mapnik. After some more playing, I added a mapnik layer to
Just-in-time (cache as you drag) OSM, based on the 11-20-06 planet.
Questions that I have been asked:
* Can it do mercator? Yes, absolutely. It only doesn't because the
existing caches for the other 7 layers are not Mercator.
* Is it WMS? TileCache can take requests in either TMS or WMS formats,
but it simply parses these requests down to the appropriate TileID.
* Does it have any additional dependancies? Nope. Once you have Mapnik
installed, the only additional dependancy is TileCache, which is
pure-python BSD licensed code.
* How are the tiles stored on disk? Because of the limitations of the
ext3 filesystem, tiles are split up into multiple subdirectories, but
these directories are regular, and very similar to the 'GoogleLike'
(zoom) (x0, x1, x2) (y0, y1, y2)
It's also possible (simple) to write your own file caching plugin,
that (for example) stores tiles on multiple servers, or use the
memcached memory caching plugin for faster access and distributed
The Mapnik layer should be in the next release of TileCache, sometime in
the next two weeks.
talk mailing list
talk at openstreetmap.org
More information about the talk