VTS Mapproxy

VTS Mapproxy is a HTTP server that converts non-VTS resources (raster or vector) to VTS resources (surface, bound layer and free layer) on the fly.

For the first time setup it is recommended to install and run mapproxy as a part of VTS Backend package or using Docker container which takes care of configuring and running the server.

• Main GitHub repository
• Build and install instructions (GitHub)
• Server configuration
• Resource definition (GitHub)
• Troubleshooting mapproxy

How it works

Once run as a binary with a configuration file or using init-script as in VTS Backend, mapproxy periodically checks for newly defined resources in resource definition file or by asking a python script. This way new resources can be defined without need to restart or shut down mapproxy.

Once it comes across a new resource, mapproxy parses its definition and if the definition is valid, it creates a generator for the resource and freezes its configuration in mapproxy’s store.

Note

Freezing configuration is meant as a failsafe in production environment, should the resource configuration file become corrupted. It also prevents user from changing some vital parameters of the resource that would result in client receiving incompatible mix of cached and fresh data.

See Troubleshooting mapproxy on how to deal with mistakes in the resource configuration.

Mapproxy serves all valid resources on following URLs (see Resource definition and Server configuration):

<server>:<port>/<reference-frame>/<resource-type>/<resource-group>/<resource-id>/