If set to true, MapProxy will request neighboring tiles from the source even if only one tile is requested from the cache. bulk_meta_tiles Enables meta-tile handling for caches with tile sources. Tiled sources are still requested tile by tile, but you can configure MapProxy to load multiple tiles in bulk with bulk_meta_tiles. With a tile size of 256x256 this will result in 1024x1024 requests to the source. A meta_size of will request 16 tiles in one pass. meta_size defines how large a meta-tile is. New in version 1.10.0: bulk_meta_tiles meta_size MapProxy does not make a single request for every tile it needs, but it will request a large meta-tile that consist of multiple tiles. If you have num_levels and res_factor: The resolutions will be multiplied by res_factor for up to num_levels levels. If you have max_res and res_factor: The resolutions will be multiplied by res_factor until larger then max_res. With resolutions from 1000 to 10 and 6 levels you would get 1000, 398, 158, 63, 25, 10 (rounded here for readability). The resolutions will be logarithmical, so you will get a constant factor between each resolution. If you have max_res and num_levels: The resolutions will be distributed between min_res and max_res, both resolutions included. If min_res is set then this value will be used for the first level, otherwise MapProxy will use the resolution that is needed for a single tile ( tile_size) that contains the whole bbox. 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.
0 kommentar(er)
