[MapProxy] incorrect latlong boundary?
olt at omniscale.de
Wed Nov 30 10:11:50 EST 2011
On 30.11.2011, at 15:57, Mark Volz wrote:
> I would like to make sure that mapproxy Is not caching outside of my county boundary of which is 430000, 97000, 5700000, 270000 in county coordinates. ArcCatalog reports a LatLong Bounding Box of: -180, -85.051, 180, 85.051, which is far beyond the borders. I am wondering if Mapproxy is caching outside of the county boundarys, or if Mapproxy is caching the correct area, and since ESPG 4326 is disabled, ArcCatalog / Mapproxy is reporting the wrong boundary box extent.
> Let me know if something appears incorrect in my grid settings.
> base: GLOBAL_GEODETIC
> res_factor: 'sqrt2'
> tile_size: [512, 512]
> srs: 'EPSG:103749'
> bbox: [430000, 97000, 5700000, 270000]
> bbox_srs: 'EPSG:103749'
> res: [1000, 512, 256, 128, 64, 32, 16, 8, 4, 2, 1, .5]
Does you cache use both grids? MapProxy will use the largest grid for the BBOX in the capabilities and global_geodetic is world wide. You should use the coverage feature for you source, if you want to limit the requests to some boundaries. MapProxy won't cache any tiles for requests that are outside of the configured coverage, even if they are inside the grid.
Oliver Tonnhofer | Omniscale GmbH & Co KG | http://omniscale.de
http://mapproxy.org | https://bitbucket.org/olt | @oltonn
More information about the MapProxy