After the actuall conference was over, I attended another workshop: about mapproxy. At my work, we have done nothing regarding map caching and proxying and tiling (we have done a lot on regular web caching, though). We’re “just” generating complete images on demand via WMS as lots of our data is pretty dynamic. But there is mostly-static data. And by setting up our software differently, tiling and proxying and caching becomes possible. At the moment I can only dream about what that’ll do to the speed of our web applications... :-) So that’s why I attended this workshop: getting to know at least one of the available map proxy tools.
Ok, what’s mapproxy?
A core piece of functionality of mapproxy is that it tiles the map. In order to cache a map, it subdivides it into parts.
What are the possible input data types?
And what can come out? (Note that this means that you can theoretically take google tiles and turn them into a WMS service!)
Some comments from the hands-on-keyboard part of the workshop:
pip install MapProxyaway. Well packaged!
.inipython paste file to run the server with. Integration with standard python wsgi tools and so easy integration into web servers. Looks good.
In the end, I found it a very good workshop. Glad I attended. And the mapproxy software left a very good impression on me: I’m looking forward to using it.
My name is Reinout van Rees and I work a lot with Python (programming language) and Django (website framework). I live in The Netherlands and I'm happily married to Annie van Rees-Kooiman.
Most of my website content is in my weblog. You can keep up to date by subscribing to the automatic feeds (for instance with Google reader):