El Miércoles, 25 de Marzo de 2009, Milo van der Linden escribió: > Mapnik could act as a wms server, but this would not be good for > performance since all rendering would be done straight from the > openstreetmap db on the fly.
You're wrong - mapnik depends on a local PostgreSQL database, not on the OSM API. > A better trick would be to implement a tile-layer in a wms image server, the > image would then take the required tiles, sticht them together in the > requested projection, cut the area that is requested and return that to the > client. If you're going to do WMS, better to do it from vector data rather than from stitching and warping tiles together. You'll ensure better place naming and consistent widths. > Caching with WMS is something that, as far as I know is not common, If > you can figure out a way of caching and write a proposal, WMS caches tend to not be efficient, so they end up not helping much. You want cached maps? Then use tiles. Cheers, -- ---------------------------------- Iván Sánchez Ortega <[email protected]> Más vale una paz relativa que una guerra ganada.- María Theresa.
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ dev mailing list [email protected] http://lists.openstreetmap.org/listinfo/dev
