[MapProxy] reproduction from wms to tiles

Jaak Laineste jaak at nutiteq.com
Mon Jan 30 16:49:32 EST 2012


Greets,

 I would need to convert WMS in local  projection to the "web map tiles API" which is in EPSG:900913, so they could be consumed in Potlach2. I have already WMS conversion from 4326 to the same, and this works. Now I added another WMS map source with similar pattern, and with local projection instead of 4326, then WMS requests started to have completely wrong and defunct coordinate ranges. So it looks like 4326 (in source wms) ->900913 (in tiles API) works, but 3301->900913 reprojection does not.

The functioning layer name is maaamet_orto, the one which does not work properly is maaamet_reljeef here:

layers:
 - name: maaamet_orto
   sources: [maaamet_orto_cache]
 - name: maaamet_reljeef
   sources: [maaamet_reljeef_cache]
caches:
 maaamet_orto_cache:
   grids: [global_mercator_osm]
   sources: [maaamet_ortofoto_wms]
 maaamet_reljeef_cache:
   grids: [global_mercator_osm]
   sources: [maaamet_reljeef_wms]
sources:
 maaamet_ortofoto_wms:
   type: wms
   supported_srs: ['EPSG:4326']
 maaamet_reljeef_wms:
   type: wms
   supported_srs: ['EPSG:3301']
grids:
 global_mercator_osm:
   base: GLOBAL_MERCATOR
   num_levels: 19

 The resulting wrong WMS URL example - SRS here is correct, but bbox numbers
certainly not: http://kaart.maaamet.ee/wms/fotokaart?layers=reljeef&width=1024&version=1.1.1&bbox=-74125583.3418,5327739.45256,-74021330.5857,5432021.63481&service=WMS&format=image%2Fjpeg&styles=&srs=EPSG%3A3301&request=GetMap&height=1024

--
JaakL
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/mapproxy/attachments/20120130/6f694f7a/attachment-0001.html


More information about the MapProxy mailing list