[MapProxy] Reprojecting on the fly using an epsg file with tiles cached in EPSG:23031

[Fabrellas Bertran, Isabel]

I installed pyproj-1.8.8-py2.7. Today I have upgraded to
pyproj-1.8.9-py2.7 and I get the same results.

If I comment out the 25831 and 23031 entries in my custom EPSs file, I
get an error: 
...
srs = _SRS(srs_code)
File "c:\mapproxy_venv\Lib\site-packages\mapproxy\srs.py", line 150, in
__init
 raise ex 
RuntimeError: no options found in 'init' file
...

The test I made previously in MapProxy 1.0.0 was in a Unix installation.
Today I have installed Mapproxy 1.0.0 in Windows and I get the same
results as with MapProxy 1.1.0.


Isabel Fabrellas Bertran
Unitat de SIG - Web
Ext. 3283


-----Missatge original-----
De: Oliver Tonnhofer [mailto:olt at omniscale.de] 
Enviat: lunes, 25 de julio de 2011 18:38
Per a: Fabrellas Bertran, Isabel
A/c: mapproxy at lists.osgeo.org
Tema: Re: [MapProxy] Reprojecting on the fly using an epsg file with
tiles cached in EPSG:23031


On 25.07.2011, at 14:38, Fabrellas Bertran, Isabel wrote:

> In MapProxy 1.1.0, we have 3 layers, one cached in EPSG:23031, one in
> EPSG:4326 and one in EPSG:900913. There is a reference to an epsg file
> in the configuration file.
> When accessed from an OpenLayers visor in EPSG:25831, the first layer
> doesn't project correctly to EPSG:25831, there is a horizontal
> difference near 80 metres and a vertical difference of 130 metres.The
> other layers project correctly.

Ok, so reproduction works, but it uses wrong transformation parameters?

> I tested it previously in MapProxy 1.0.0, and the 3 layers project
> correctly to EPSG:25831.

I don't remember any changes for that. Did you install/upgraded pyproj?

You can comment out the 25831 and 23031 entries in your custom EPSs file
and see if it still accepts the SRS. In that case it is not using your
EPSG file.

Regards,
Oliver

-- 
Oliver Tonnhofer    | Omniscale GmbH & Co KG    | http://omniscale.de
http://mapproxy.org | https://bitbucket.org/olt | @oltonn