There are two main reasons as to why you would want to proxy the WMTS basemap, these areiShare v6 and later uses MapProxy to create and display cached map data, for example aerial or historic maps. MapProxy may also be useful in other circumstances, for example:

1. You may have to provide a customer API Key in the URL for each request, as in the case with the OS Maps API. If this were to be used directly in iShare, the key would have to be transferred to the client which could expose it to misuse.

2. Proxying the basemap through MapProxy allows us to also query it directly with WMS which then means that it should work seamlessly with printing.

Configuration

MapProxy uses a YAML configuration file to define the service - this file will normally be stored with the MapProxy application, for example at D:/mapproxy/mapproxy.yaml. Full documentation on configuring the YAML file are at: https://mapproxy.org/docs/latest/configuration.html, and a sample YAML file is attached to this page.

Configuration of MapProxy layers in Studio is covered in this section: BaseMaps Details .

The YAML file can be edited in a text editor such as Notepad++. The following are the main sections of the YAML file which need to be configured for each layer.

• Layers: the layers that are available in the service

• Caches: where the cache is stored

• Sources: where the source files are stored

• Grid: the Coordinate Reference System used in the layer, and the scales/resolutions available.

The YAML file itself will normally be stored with the MapProxy application, for example at D:/mapproxy/mapproxy.yaml.

...

• .

Layers

This section defines one or more layers to be served by MapProxy. Each layer should have:

...