pyprojection problem

Bram de Greve bram.degreve at gmail.com
Fri Jan 25 17:03:25 CET 2008


Didrik Pinte wrote:
> And here is a workaround/patch :
>
> Line 789 and following of Thuban/UI/projdialog.py
>
>         params = ["proj=tmerc",
>                   "lat_0=" + str(self.__latitude.GetValue()),
>                   "lon_0=" + str(self.__longitude.GetValue()),
>                   "x_0="   + str(self.__falseEast.GetValue()),
>                   "y_0="   + str(self.__falseNorth.GetValue()),
>                   "k="     + str(self.__scale.GetValue())]
>         params.extend(ProjPanel.GetParameters(self))
>         return params
>
> Adding a str() to each access to parameters solved the problem ...
>
> Is this acceptable ? There is no way to have strange encoding problem
> with those parameters (lat_0, etc.).
>   
ProjPanel.GetParameters(self) can't do any funny things?

I would suggest to move over the patch to Model/proj.py, as that seems
to be a wrapper around pyprojection.
I believe we're OK when you replace line 78 by:

        BaseProjection.__init__(self, map(str, params))

NOT TESTED ;)

> Didrik
>
> _______________________________________________
> Thuban-devel mailing list
> Thuban-devel at intevation.de
> https://intevation.de/mailman/listinfo/thuban-devel
>   




More information about the Thuban-devel mailing list

This site is hosted by Intevation GmbH (Datenschutzerklärung und Impressum | Privacy Policy and Imprint)