Quite a few interesting news in this batch mode edition.
From the open source front:
From the Google front:
In the miscellaneous category:
in the maps category:
Still in my geonews catching up process, here's the open source-related geonews not shared yet.
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: "
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: