
If you supply a list with resolution values in res then MapProxy will use this list and will ignore all other options. We describe the process MapProxy uses to build the list of all cache resolutions. There are multiple options that influence the resolutions MapProxy will use for caching: res, res_factor, min_res, max_res, num_levels and also bbox and tile_size. MapProxy is unable to fetch the tile if the cache has no sources, or if all sources are either seed_only or limited to a different resolution ( min_res/ max_res). To trigger the rescaling behaviour, a tile needs to be missing in the cache and MapProxy needs to be unable to fetch the tile from the source. It will start in the lowest zoom level for upscale_tiles, so that tiles in the next (higher) zoom levels can be created by upscaling the already creates tiles.Ī transparent tile is returned if no tile is found within the configured upscale_tiles or downscale_tiles range. It will start with the highest zoom level for downscale_tiles, so that tiles in the next (lower) zoom levels can be created by downscaling the already created tiles. Mapproxy-seed will seed each level independently for caches with upscale_tiles or downscale_tiles. You can use downscale_tiles to fill a cache for a source that only provides data for higher resolutions. It is therefore not recommended to use downscale_tiles values larger then one. A larger WMS request can quickly accumulate thousands of tiles required for downscaling. Downscaling from two levels below requires 16 tiles, three levels below requires 64, etc. Typically, a single tile can be downscaled from four tiles of the next zoom level. Note that the number of tiles growth exponentialy. The value configures by how many zoom levels MapProxy can search for a proper tile. MapProxy will scale down tiles from one or more zoom levels below (with higher resolutions) if you set downscale_tiles to 1 or higher. upscale_tiles allows you to provide responses for 10cm requests in all areas, allways returning the best available data. where you have an arial image cache of 20cm, with some areas also in 10cm resolution.

This also works with partially seeded caches, eg. You can use upscale_tiles if you want to provide tiles or WMS responses in a higher resolution then your available cache. MapProxy will scale up tiles from one or more zoom levels above (with lower resolutions) if you set upscale_tiles to 1 or higher. MapProxy is able to create missing tiles by rescaling tiles from zoom levels below or above. 1 feature_list : - url : http : // example. gml format : text / xml subtype = gml / 3.2. shp format : application / octet - stream - url : http : // example. xml type : ISO19115 : 2003 format : application / xml data : - url : http : // example. xml type : INSPIRE format : application / xml - url : http : // example. org / name : HKU1234 value : Some value metadata : - url : http : // example. jpg width : 100 height : 100 format : image / jpeg identifier : - url : http : // example. They mostly explain themselves, or can be looked-up in the MapProxy docs.Layers : - name : md_layer title : WMS layer with extended capabilities sources : md : abstract : Some abstract keyword_list : - vocabulary : Name of the vocabulary keywords : - vocabulary : Name of another vocabulary keywords : - keywords : attribution : title : My attribution title url : http : // example. #next are some global configuration options for MapProxy.

If you get this wrong, you might very well get an all-blue world. #The google mercator srs is used (also called EPSG:900913), and the origin of the tiles is north-west). In this example it is used for the osm_tiles source.

#this srs and origin specify a grid that can be used elsewhere in the configuration. Grid: osm_grid #the grid to use for the osm tiles. These will be downloaded upon request (if not already cached) and served by MapProxy #the osm_tiles source refers to the tiles. Sources: #here you set what source data (defined below) you want to cache #setup the cache for the open streetmap tiles. Sources: #this layer should use the osm_cache (defined below) as it's source. You can add many, but let's stick to osm data here. #sets up which layers you want to make available using the services above. The data is licensed as Creative Commons Attribution-Share Alike 2.0 # metadata used in capabilities documentsĪbstract: This is the fantastic MapProxy.Įmail: service is intended for private and evaluation use only. MapProxy reprojects the source data very well to these projections. #srs sets the coordinate reference systems as which you want to make your data available.
#SOURCES MAPPROXY HOW TO#
#sets up how to make the source data available
