We mentioned the open source MapProxy a few times since 2010, including the 1.0.0 release about a year ago. Less than two weeks ago, MapProxy 1.3.0 was released. Anyone with an interest in tile caching might be interested in reading this previous story named FOSS4G 2011: What about a Tiling Shootout?
Amongst the new features for the 1.3.0 release: "
While the presentation was on its first day in Denver, Peter Batty starts by exposing the overall success of the 2011 edition (and the slow Wifi network at the conference Hotel...) as well as the force of the open source community. In his opening ceremony, he has compiled the registration and the FOSS4G 2011 had more than 900 attendees with almost half of the crowd from the USA, around 150 Europeans and Japan as the only Asian country represented.
Secondly, Arnulf Christl presents, by showing OSGeo/FOSS4G geek T-shirt, the diversity of OSGeo around the world. Thirdly, Paul Ramsey, with his unique sense of humour, speaks about the Open source business model in his own language as it can be defines by each corporation and organisation that is working in FOSS4G as long as it keeps code alive.
Afterward, technical and academic session were exposing what’s hot in terms of geospatial open source software. Presentations on Map tiling and the new trend as managing map tiles in a database such SQLite with MapProxy. At the same time, the Apache module called geocache, renamed MapCache, was presenting its benchmark as well as its integration in the MapServer stack. In the Geonetwork presentation, the newest 2.8 geodata catalog release now separates the client and server product, the interface of metadata editor has been improved and a tool to add shapefile on-the-fly as a layer has been developed. With a strong presence of ESRI a the FOSS4G, the City and County of Denver showed that using OpenLayers in combination with ArcGIS Server is quite effective and how their contribution to the AgsjsAdapter.js to support the ArcGIS tiles version 10 was beneficial.
A discussion on the WFS-Transactional versus the REST/geoJson has been helpful to understand the performance implementation of this OGC standard with GeoServer/MapFish and to raise issue on the gml format as a WFS lack of documentation and fully compliant readers in the market.
This open source collaboration project with partners organisation, such as Quebec National Public Health Institute, has been helpful to first responders and emergency manager to actually open the used of geodata in real life-saving situation.
The MapProxy project is pleased to announce the 1.0.0 release of MapProxy.
MapProxy is a tile cache solution, but also offers many new and innovative features like full support for any WMS clients.
MapProxy is actively developed and supported, it was released as Open Source in March 2010 under the GNU AGPL License 3.0, runs on Unix/Linux and Windows and is easy to install and to configure.
More information can be found at: http://mapproxy.org
The updated documentation: http://mapproxy.org/docs/1.0.0/
Here are some of the features that where added in the last year:
MapProxy comes with an advanced seeding tool that allows you to create, update and remove tiles for specific areas. You can use Shapefiles and other sources to define the geometries of these areas. The seed tool is also multithreaded and optimized to work with WMS services with large datasets. MapProxy also handles "empty" tiles (e.g. blue ocean) to save disk space.
MapProxy supports nested layer groups and each layer or layer group can be cached or cascaded. Cached layers can be 10-100 times faster. You can combine layers from different servers and make opaque layers transparent. It also supports GetLegendGraphics and GetFeatureInfo requests. Feature info responses can be transformed with XSLT scripts. You can mix all WMS versions, image formats and SRS: MapProxy will translate, convert and reproject on-the-fly if necessary.
There is also a new interface that allows the integration of fine-grained user authorization.
You can find more information about all features in the updated documentation
You can join our mailing list if you have any questions:
From the blog entry: "The new features since the last release are numerous, including a new disk quota module for automatic managing of tile storage. The disk quota prevents runaway disk usage, removes the need for manual truncation operations, and allows for multiple policies for determining how to remove tiles from the cache.
Also, GeoWebCache can now serve tiles from an ArcGIS Server tile cache, allowing a preexisting tile cache to be easily migrated to a fully standards-compliant web mapping stack without the need for re-creation. You now also have the ability to configure the service metadata for the capabilities document.