TILEMATRIX=%(z)s&TILEROW=%(y)s&TILECOL=%(x)s&FORMAT=image%%2Fpng Url: VERSION=1.0.0&LAYER=layername&TILEMATRIXSET=WEBMERCATOR& Here is an example of a WMTS source: sources: See the :ref:`tile source documentation ` for all possible template values. You can use x, y, z variables in the template, but MapProxy also supports the quadkey variable for Bing compatible tile service and bbox for WMS-C services. Url: You need to modify the url template parameter to match the URLs of your server. You always need to configure a cache in MapProxy to get a WMS from a tile source, since the cache is the part that does the tile stitching and reprojection. That tile server could be a WMTS, TMS or any other tile service where you can access tiles by simple HTTP requests. You can use MapProxy to create a WMS server with data from an existing tile server. You can use uncompressed TIFF as the request format, if both servers are on the same host or if they are connected with high bandwidth. This encoding is quite CPU intensive for your WMS server but reduces the amount of data than needs to be transfered between you WMS and MapProxy. You need to tell MapProxy that all overlay sources are transparent: sources:īy default MapProxy will request data in the same format it uses to cache the data, if you cache files in PNG MapProxy will request all images from the source WMS in PNG. You can also merge multiple tile sources. If the layers come from the same WMS server, then you can add them direct to the layers parameter.