We are finally ready to announce the release of MapProxy 1.1.0. It contains lots of major and minor improvements.
The latest release is available at: http://pypi.python.org/pypi/MapProxy
To update within you virtualenv:
$ pip install --upgrade --no-deps MapProxy
Updated documentation is available at: http://mapproxy.org/docs/1.1.0/
Some noteworthy improvements since 1.0.0 are:
There are two new sources that directly integrate Mapserver and Mapnik into MapProxy. There is no need to setup an extra WMS server for these map services.
The tile source was extended by the
arcgiscache_path allows the integration of existing ArcGIS
tile caches (L09/R05397fb1/C0012d687) and the
bbox parameter is useful
for WMS-C services that expect a fixed parameter order.
Tagged WMS Sources
You can tag WMS source names with layer names. It is no longer required to specify a WMS source multiple times, for each layer combination you use. You can now define a WMS once without any layers and then tag the source name with the layers you need.
sources: wms1: type: wms req: url: http://example.org/service? caches: mycache1: sources: ['wms1:lyr1,lyr2'] grids: [mygrid] mycache2: sources: ['wms1:lyr3,lyr4'] grids: [mygrid]
See WMS documentation.
Configurable Image Formats
Image formats are now much more flexible. You can now create custom image formats and modify them for each source or cache individually. The configuration of paletted PNGs or the JPEG quality is no longer a global option.
See image options.
There is now also support for integer images, e.g. for DEMs.
There is first support for the OGC WMTS standard. It implements KVP requests and can be used with existing caches.
The logging was improved and unified. System information is now logged at
mapproxy.system, configuration errors at
mapproxy.config and all
source errors under
All requests that MapProxy makes are now logged to
mapproxy.source.request. The request log format changed and it now
contains the complete URL (easy to copy&paste), the size and the duration
of the request. The log contains also requests to non-HTTP sources like
Mapnik or Mapserver.
Improved configuration loading
The configuration loading is now more robust. You shouldn't see any stack traces when your configuration contains any syntax errors. The MapProxy and the seed configurations are now validated and you should see detailed information about missing or unknown options.
The default location of the cache will change with the next release (1.2). The
current default is
../var/cache_dir which is appropriate for the
paster create, but not for the configuration from
mapproxy-util create (see below). You should configure
globals.cache.base_dir with your cache directory. Until then you will get
a FutureWarning during startup.
New mapproxy-util command line tool
There is a new mapproxy-util command that replaces the paster command for running the development server. You can now start a test server with:
mapproxy-util serve-develop mapproxy.yaml
Paster (PasteDeploy/PasteScript) is no longer a requirement, but it is still supported.
For a more complete list see: http://bitbucket.org/olt/mapproxy/src/1.1.0/CHANGES.txt