[MapProxy] Mapproxy hangs on reprojection?
Anne Blankert
anne.blankert at geodan.nl
Fri Sep 24 20:10:18 EDT 2010
Hello list,
At Foss4G I was very impressed with the presented featureset of MapProxy.
I am now playing with mapProxy and at first sight it works great.
However, one of the announced features that I thought could be very
interesting, is the possibility to reproject. I would like to use that
to combine services that support different SRSs
Now I have the following setup:
* Windows Vista (happened to be pre-installed on my laptop)
* Python 2.6
* the virtual environment from
http://bitbucket.org/ianb/virtualenv/raw/1.4.8/virtualenv.py
* MapProxy0.8.4
the following lines in my services.yaml
...
- dnk:
md:
title: De nieuwe kaart - http://www.nieuwekaart.nl
param:
srs: ['EPSG:4326', 'EPSG:900913']
tile_size: [256, 256]
sources:
- type: cache_wms
supported_srs: ['EPSG:4326']
req:
url: http://webservice.nieuwekaart.nl/cgi-bin/nkn?
layers: nieuwekaart
transparent: 'true'
Now if I start the service with:
paster serve etc/develop.ini --reload
The service completely hangs after 1 getCapabilities request + 4 GetMap
epsg:900913 requests.
The 4 tiles are reprojected correctly, but no longer transparent.
I have to completely kill the command box that I used to run the virtual
environment in before I can use mapproxy again.
To verify that MapProxy is really requesting epsg:4326, I used a network
sniffer (wireshark) and saw the following request header for the remote
server:
GET
/cgi-bin/nkn?styles=&format=image%2Fpng&height=1184&bbox=4.87449645996,52.3735032015,4.92530822754,52.4045134766&transparent=true&layers=nieuwekaart&service=WMS&srs=EPSG%3A4326&request=GetMap&width=1940&version=1.1.1
HTTP/1.1
Accept-Encoding: identity
Host: webservice.nieuwekaart.nl
Connection: close
User-Agent: MapProxy-0.8.5
Questions:
* Is the hang a problem caused by me, my machine, Vista in general,
virtualenv, Python or MapProxy?
* it seems that layer-transparancy is lost if reprojected. Is that true?
* the request header shows escaped request parameters, shouldn't they be
unescaped?
* the request header claims I am using MapProxy version 0.8.5 instead of
0.8.4
Anne
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/mapproxy/attachments/20100925/7af24abb/attachment.html
More information about the MapProxy
mailing list