[MapProxy] New MapProxy 1.5.0 and yaml

[A.Pirard.Papou]

Hi,

I asked for help twice to know how to determine if a python package is 
installed.
No answer but I finally found out and I can start real work now.

problem #1
My problem was that, somehow, PyYAML==3.10 was installed out of aptitude 
control.
When installing the 1.x.0 DEB, python-yaml-3.09 was installed on top and 
played havoc with 3.10.
pip uninstall  is undocumented (!), but it did uninstall 3.10, which put 
an end to war.
Conclusion: one should never mix two installation systems.
Either mapproxy should install DEBs (they are very strongly managing 
conflicts and requirements)
or pip and other installers should install python or other stuff by 
constructing temporary DEBs.

problem #2
Well, now to the 1.5.0 config problem (1.4.0 uses the same config nicely):

mapproxy.service.wmts - WARNING - grid 'global_geodetic_sqrt2' is not 
compatible with WMTS, skipping for layer 'osm'

Same message for another layer.
Many Google hits for this message, but none seems to apply.

I fear that if maxproxy

  * believes that WMTS is used while it is not
  * does not understand the grid used by the cache

it could destroy something and I returned to 1.4.0.

Config (part of):

layers:
   - name: osm
     title: Omniscale OSM WMS - osm.omniscale.net
     sources: [osm_cache]
caches:
   osm_cache:
     grids: [GLOBAL_MERCATOR, global_geodetic_sqrt2]
     sources: [osm_wms]
sources:
   osm_wms:
     type: wms
     req:
       url: http://osm.omniscale.net/proxy/service?
       layers: osm
grids:
   global_geodetic_sqrt2:
     base: GLOBAL_GEODETIC
     res_factor: 'sqrt2'

TIA,
Cheers,

André.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapproxy/attachments/20130315/9ab44efe/attachment.html>