MapProxy grew from a simple tile server with WMS support to a powerful and flexible proxy for maps. Features like the security API, the ability to reproject tiles, support for coverages from Shapefiles or PostGIS and the various tools are just a few things that we couldn't have imagined to have in MapProxy when we were thinking about the future of MapProxy three years ago.

You will get an impression of the development by comparing the configuration options from the first open source release to the latest version.

With open source it is hard to tell how many users MapProxy gained in this time, but we do know that it is now used in countless projects – by federal or state agencies and institutions, by universities, students and hobbyists, by small, national and international companies – all around the world. We also know that there are 200 subscribers on the mailing list and that we get hundreds of downloads each month.

While most of the development, support and release management was made by Omniscale, all this would not have been possible without the support from various companies and institutions who funded large parts of the development of MapProxy.

We would like to thank:

• Blackbridge Geomatics, Canada
• Cadastral Agency of the Hanseatic City of Rostock, Germany
• Camptocamp SA, Switzerland
• Dienstleistungszentren Ländlicher Raum, Rhineland-Palatinate, Germany
• Federal Agency for Cartography and Geodesy, Germany
• GeoInformation Bremen, State Office, Germany
• Norwegian Meteorological Institute
• swisstopo, Federal Office of Topography, Switzerland
• Tike, Information Centre of the Ministry of Agriculture and Forestry, Finland
• ...

And of course, we also like to thank all contributers of MapProxy and all users that gave us valuable feedback on the mailing list, on IRC or during hands-on workshops.

The next release is coming and the list of ideas for 2.0 is growing.

On to the next three years!

The latest release is available at: http://pypi.python.org/pypi/MapProxy

To upgrade within you virtualenv:

$ pip install --upgrade --no-deps MapProxy

Updated documentation is available at: http://mapproxy.org/docs/1.5.0/

New features

Some noteworthy improvements since 1.4.0 are:

Clipping WMTS/TMS/KML requests to polygons

The security API now also supports limiting requests to polygon geometries for all tile services.

See: http://mapproxy.org/docs/1.5.0/auth.html#limited-to

Mixed image mode

The mixed image mode automatically chooses between PNG and JPEG format depending if the image has transparency or not. This is a great feature for aerial images with transparency at the image boundaries. Thanks to Thomas Bonfort for the idea.

See: http://mapproxy.org/docs/1.5.0/configuration.html#format

Caches as source for other caches

You can now use a cache as a source for another cache. You can use this to directly reproject tiles or to make changes to your grid configuration without losing your existing cache.

See: http://mapproxy.org/docs/1.5.0/configuration_examples.html#using-existing-caches and http://mapproxy.org/docs/1.5.0/configuration_examples.html#reprojecting-tiles

Changed default SRS in WMS

The WMS now supports EPSG:3857, the official EPSG code of the Webmercator projection (EPSG:900913). UTM 32/33N and Gauß-Krüger zones 3-5 were removed from the default list, since they are only usable in parts of Europe. Make sure you've configured all SRS you are using in the service configuration.

New tools

There are three new tools:

• mapproxy-util grids: debug and analyze grid configuration
• mapproxy-util wms-capabilities: get bbox and min/max_scales of existing WMS
• mapproxy-util export: export (parts) of your cache to MBTiles or a TMS directory

See: http://mapproxy.org/docs/1.5.0/mapproxy_util.html

Other features

• use_grid_names option to access Tiles/TMS/KML layers by grid name instead of EPSGXXXX
• origin option for TMS to change default origin of the /tiles service
• continue stopped/interrupted seed processes
• support min_res/max_res for tile sources

Improvements

• do not show layers with incompatible grids in WMTS/TMS demo
• make 0/0/0.kml optional for the initial KML file
• use BBOX of coverage for capabilities in seed_only layers
• ignore debug layer when loading tile layers
• simplified coverage configuration
• add reloader option to make_wsgi_app()
• add MetadataURL to WMS 1.1.1 capabilities
• improved WMTS services with custom grids (origin)
• use in_image exceptions in WMS demo client
• larger map in demo client
• always request with transparent=true in WMS demo client
• use in_image exceptions in WMS demo client

Other fixes and changes

For a complete list of changes see:

The latest release is available at: http://pypi.python.org/pypi/MapProxy

To upgrade within you virtualenv:

$ pip install --upgrade --no-deps MapProxy

Updated documentation is available at: http://mapproxy.org/docs/1.4.0/

New features

Some noteworthy improvements since 1.3.0 are:

Clipping requests to polygons

The security API now supports limiting requests to polygon geometries with the limited_to feature.

See auth API.

Demo service

The demo service now allows you to query WMS layers in all supported SRS. It now also supports WMTS if you have enabled this service.

Other improvements

• WMS 1.3.0 now supports extended layer capabilities for metadata etc.
• You can configure fallbacks for errors in tile sources. MapProxy can create an empty tile if the tile source returns a 404 not found for a tile, for example.

Note: There was a bug in the configuration loader that permitted to have an error in the layers configuration. Please make sure your configuration is valid after upgrading.

Changelog

For a complete list of changes see: http://bitbucket.org/olt/mapproxy/src/1.4.0/CHANGES.txt

The latest release is available at: http://pypi.python.org/pypi/MapProxy

To upgrade within you virtualenv:

$ pip install --upgrade --no-deps MapProxy

Updated documentation is available at: http://mapproxy.org/docs/1.3.0/

New features

Some noteworthy improvements since 1.2.0 are:

RESTful WMTS

The MapProxy WMTS now also supports the RESTful API. This service also supports custom URL templates for your service.

See WMTS configuration.

CouchDB cache backend

You can now use a CouchDB as a backend for tile caches. Each cache gets stored into a separate database and you can configure the layout of the URLs of each tile. You can also add additional metadata for each tile.

See CouchDB configuration.

mapproxy-util serve-multiapp-develop tool

The new command is similar to serve-develop but it starts a MultiMapProxy instance.

See mapproxy-util documentation.

Other features

• Mapnik source now supports Mapnik 2.

• You can limit the maximum WMS response size in pixels with max_output_pixels.

• You can configure additional SRS for which MapProxy should add bounding boxes to the WMS capabilities with the new wms.bbox_srs option.

Changelog

For a complete list of changes see: http://bitbucket.org/olt/mapproxy/src/1.3.0/CHANGES.txt

We are finally ready to announce the release of MapProxy 1.2.0. It contains major and minor improvements.

The latest release is available at: http://pypi.python.org/pypi/MapProxy

To upgrade within you virtualenv:

$ pip install --upgrade --no-deps MapProxy

Updated documentation is available at: http://mapproxy.org/docs/1.2.0/

New features

Some noteworthy improvements since 1.1.0 are:

Cache

You can use the MBTiles format for new caches and you can load existing MBTiles cache files.

The directory layout for file based caches is now configurable and you can choose a TMS compatible layout besides the default TileCache compatible one.

See cache configuration.

mapproxy-util scales tool

The new mapproxy-util scales tool helps to convert between scales and resolutions.

See mapproxy-util documentation.

Other features

• Mapnik source now supports the selection of single layers.

• You can use MultiMapProxy without Paste Deploy.

Changelog

For a more complete list see: http://bitbucket.org/olt/mapproxy/src/1.2.0/CHANGES.txt

The 1.1.1 release fixes:

• add back transparent option for mapnik/tile sources (in addition to image.transparent)
• keep alpha channel when handling image.transparent_color
• fixed combining of multiple WMS layers with transparent_color
• fixed header parsing for MapServer CGI source

The latest release is available at: http://pypi.python.org/pypi/MapProxy

To update within you virtualenv:

$ pip install --upgrade --no-deps MapProxy

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/

MapProxy 1.1.0 is the first version that is released under the Apache Software License 2.0. This replaces the old GNU AGPL License terms with a more open and liberal license.

New features

Some noteworthy improvements since 1.0.0 are:

New sources

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.

See MapServer source and Mapnik source documentation.

The tile source was extended by the arcgiscache_path and bbox parameters. 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.

See tile source documentation.

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.

WMTS

There is first support for the OGC WMTS standard. It implements KVP requests and can be used with existing caches.

See WMTS service documentation.

Improved logging

The logging was improved and unified. System information is now logged at mapproxy.system, configuration errors at mapproxy.config and all source errors under mapproxy.source.wms, etc.

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.

See deployment documentation.

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.

Cache location

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 configuration from 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.

See deployment documentation.

Changelog

For a more complete list see: http://bitbucket.org/olt/mapproxy/src/1.1.0/CHANGES.txt

The latest release is available at: http://pypi.python.org/pypi/MapProxy

To update within you virtualenv:

$ pip install -U --no-deps MapProxy

Updated documentation is available at: http://mapproxy.org/docs/1.0.0/

Upgrade notes

A bug, introduced in a previous release, prevented that the tile locks get removed. This issue is solved since 1.0.0b2 and MapProxy will remove existing lock files on the first access to the cache. This might take a while if the directory already contains a lot of lock files (probably thousands and more).

We suggest that you remove the complete lock directories by hand before upgrading:

rm -r cache_dir/*/tile_locks

New features

Some noteworthy improvements are:

mapproxy-seed

mapproxy-seed got a new, flexible configuration format (the old format is still supported). You can now define multiple seed and cleanup tasks and call each separately from the command line interface (--seed and --cleanup options).

It is now possible to reseed specific areas without triggering any cleanup.

There are also two new --summary and --interactive options that help to understand what the seed tool will do.

See: http://mapproxy.org/docs/1.0.0/seed.html

FeatureInfo XSL transformations

MapProxy now supports content aware merging of multiple HTML/XML feature responses and it supports XSL transformations. See:
http://mapproxy.org/docs/1.0.0/configuration_examples.html#featureinformation

Image manipulation

You can now make non-transparent layers transparent. Either with an opacity value, with blends the layer over the others, or with a color value that should be converted to transparent. See: http://mapproxy.org/docs/1.0.0/sources.html#image-transparent-color

Authentication

There is a new powerful authentication interface. See: http://mapproxy.org/docs/1.0.0/auth.html

Changelog

For a more complete list see: http://bitbucket.org/olt/mapproxy/src/1.0.0/CHANGES.txt

Final note

We also like to use this announcement to say thank you to the ever growing community. To everyone that helped funding the many new features and to everyone that offered help, gave feedback or talked/blogged/tweeted about MapProxy.

Thank you!

The latest release is available at: http://pypi.python.org/pypi/MapProxy

To update within you virtualenv:

$ pip install -U MapProxy

Updated documentation is available at: http://mapproxy.org/docs/0.9.1/

Some noteworthy improvements are:

Coverage support

You can limit any tile/WMS source to the actual coverage of the data. The configuration is similar to the seeding tool. You can use a simple BBOX, WKT files or OGR datasources like Shapefiles to load the boundaries of your data. Requests for data outside of the coverage will result in empty images and the source will not be requested.

See: http://mapproxy.org/docs/0.9.1/coverages.html

WMS improvements

We added lots of new features to the WMS implementation of MapProxy. Some of them:

• Nested layer groups
• WMS 1.1.0 support
• GetLegendGraphic support
• ScaleHint support
• SLD support for WMS sources

MultiMapProxy

Use multiple MapProxy configurations in a single MapProxy instance: http://mapproxy.org/docs/0.9.1/deployment.html#multimapproxy

Changelog

For a more complete list see: http://bitbucket.org/olt/mapproxy/src/0.9.1/CHANGES.txt

You now find the latest documentation of the development trunk at: http://mapproxy.org/docs/nightly/

The official documentation of the latest release is still available at the old location.