Installation#
This tutorial guides you to the MapProxy installation process on Unix systems. For Windows refer to Installation on Windows.
This tutorial was created and tested with Debian and Ubuntu, if you’re installing MapProxy on a different system you might need to change some package names.
MapProxy is registered at the Python Package Index (PyPI). If you have Python 2.7.9 or higher, you can install MapProxy with:
sudo python -m pip install MapProxy
This is really, easy but we recommend to install MapProxy into a virtual Python environment. A virtualenv is a self-contained Python installation where you can install arbitrary Python packages without affecting the system installation. You also don’t need root permissions for the installation.
Read about virtualenv if you want to know more about the benefits.
Create a new virtual environment#
virtualenv is available as python-virtualenv on most Linux systems. You can also install Virtualenv from source.
To create a new environment with the name mapproxy call:
virtualenv --system-site-packages mapproxy
You should now have a Python installation under mapproxy/bin/python.
Note
Virtualenv will use your Python system packages (like python-imaging or python-yaml) only when the virtualenv was created with the --system-site-packages option.
You need to either prefix all commands with mapproxy/bin, set your PATH variable to include the bin directory or activate the virtualenv with:
source mapproxy/bin/activate
This will change the PATH for your current session.
Install Dependencies#
MapProxy is written in Python, thus you will need a working Python installation. MapProxy works with Python 3.8 or higher, which should already be installed with most Linux distributions.
MapProxy requires a few third-party libraries that are required to run. There are different ways to install each dependency. Read Dependency details for a list of all required and optional dependencies.
Installation#
On a Debian or Ubuntu system, you need to install the following packages:
sudo apt-get install python3-pil python3-yaml python3-pyproj
To get all optional packages:
sudo apt-get install libgeos-dev python3-lxml libgdal-dev python3-dev python3-shapely
Dependency details#
pyproj or libproj#
MapProxy uses the PROJ C library for all coordinate transformation tasks. MapProxy can directly use the C library or via the pyproj Python package. The internal API of PROJ was updated with PROJ >=5. The old PROJ 4 API is now deprecated and will be removed from future PROJ releases. MapProxy only supports the new API via pyproj and it is therefore recommended to use a recent pyproj version.
Changed in version 1.13: Support for new PROJ API via pyproj.
Pillow#
Pillow, the successor of the Python Image Library (PIL), is used for the image processing and it is included in most distributions as python-pil or python-imaging. Please make sure that you have Pillow installed as MapProxy is no longer compatible with the original PIL. The version of python-imaging should be >=3.1.
You can install a new version of Pillow from source with:
sudo apt-get install build-essential python-dev libjpeg-dev \
zlib1g-dev libfreetype6-dev
pip install Pillow
YAML#
MapProxy uses YAML for the configuration parsing. It is available as python-yaml, but you can also install it as a Python package with pip install PyYAML.
Shapely and GEOS (optional)#
You will need Shapely to use the coverage feature of MapProxy. Shapely offers Python bindings for the GEOS library. You need Shapely (python-shapely) and GEOS (libgeos-dev). You can install Shapely as a Python package with pip install Shapely if you system does not provide a recent (>= 1.8) version of Shapely.
GDAL (optional)#
The coverage feature allows you to read geometries from OGR datasources (Shapefiles, PostGIS, etc.). This package is optional and only required for OGR datasource support (BBOX, WKT and GeoJSON coverages are supported natively). OGR is part of GDAL (libgdal-dev).
lxml (optional)#
lxml is used for more advanced WMS FeatureInformation operations like XSL transformation or the concatenation of multiple XML/HTML documents. It is available as python-lxml.
Install MapProxy#
Your virtual environment should contain pip, a tool to install Python packages.
To install you need to call:
pip install MapProxy
You specify the release version of MapProxy. E.g.:
pip install MapProxy==1.10.0
or to get the latest 1.10.0 version:
pip install "MapProxy>=1.10.0,<=1.10.99"
To check if the MapProxy was successfully installed, you can call the mapproxy-util command.
mapproxy-util --version
Note
pip will download packages from the Python Package Index and therefore require full internet access. You need to set the https_proxy environment variable if you only have access to the internet via an HTTP proxy. See Access sources through HTTP proxy for more information.
Create a configuration#
To create a new set of configuration files for MapProxy call:
mapproxy-util create -t base-config mymapproxy
This will create a mymapproxy directory with a minimal example configuration (mapproxy.yaml and seed.yaml) and two full example configuration files (full_example.yaml and full_seed_example.yaml).
Refer to the configuration documentation for more information. With the default configuration the cached data will be placed in the cache_data subdirectory.
Start the test server#
To start a test server:
cd mymapproxy
mapproxy-util serve-develop mapproxy.yaml
There is already a test layer configured that obtains data from the Omniscale OpenStreetMap WMS. Feel free to use this service for testing.
MapProxy comes with a demo service that lists all configured WMS and TMS layers. You can access that service at http://localhost:8080/demo/
Upgrade#
You can upgrade MapProxy with pip in combination with a version number or with the --upgrade option.
Use the --no-deps option to avoid upgrading the dependencies.
To upgrade to version 1.x.y:
pip install 'MapProxy==1.x.y'
To upgrade to the latest release:
pip install --upgrade --no-deps MapProxy
To upgrade to the current development version:
pip install --upgrade --no-deps https://github.com/mapproxy/mapproxy/tarball/master
Changes#
New releases of MapProxy are backwards compatible with older configuration files. MapProxy will issue warnings on start-up if a behavior will change in the next releases. You are advised to upgrade in single release steps (e.g. 1.9.0 to 1.10.0 to 1.11.0) and to check the output of mapproxy-util serve-develop for any warnings. You should also refer to the Changes Log of each release to see if there is anything to pay attention for.
If you upgrade from 0.8, please read the old migration documentation.