For some time GeoWebCache has taken shape, what began as a scholarship for a Google Summer of Code has evolved into a functional product. But time has come for a new kid in the neighborhood, calledMapProxy and has some pretty interesting features.
Technologically MapProxy development is written in Python that allows deployed in what is called a "virtual environment" to isolate your development environment from the rest of your system. Also brings a simple web server for development and production use must go to either FastCGI WSGI , Python standard for deploying web applications. The deployment is therefore more or less similar to TileCache.
MapProxy not only exposed as a server TMS or WMS-C, and this is also the biggest difference, is exposed as a normal WMS server . That is, from the origins to define and that will be storing cached on disk, as well as tiles MapProxy services may also address requests that fall outside the boundaries of the grid. To this end comprise reproyectará if necessary and the image to the size required and reference system.
This opens interesting scenarios, such as using our caches with fat clients likegvSIG and not just pulling existing WMS services but also of others who were served only by TMS. That is, to put it simply, we can set up a WMS for OpenStreetMap . Of course, a source and OSM did not look great in the intermediate zones between resolutions of the cache because the labels and linear elements are distorted enough
No comments:
Post a Comment