missing projection alert
Bernhard Reiter
bernhard at intevation.de
Thu Jan 20 09:54:26 CET 2005
On Thu, Jan 20, 2005 at 12:12:20AM +0100, Bernhard Reiter wrote:
> On Tue, Dec 28, 2004 at 03:25:09PM -0500, Russell Nelson wrote:
> > I have more confidence that the second patch (mainwindow.py) is
> > correct. If you have a layer whose LatLonBoundingBox returns values
> > which are not legitimate latitude or longitudes, the status bar gets a
> > message asking you to correct the projection. If you load a UTM map,
> > you'll get this message.
>
> Finally could check this patch out.
>
> Please commit, it seems fine overall.
> One one question:
> Could left=-180 be a valid value?
> Maybe we should use <= and >= instead of < and > in the comparision.
The more I think about it, I think it should indeep allow equality.
Two more thoughts:
As my test layer was your test.jpg called test,
I think that added double quotation marks in the string
could be a tiny improvements. I did read
Select Layer test and ...
And I thought, uh that is a nice menu function. ;)
Do we actually want to allow working on unprojected layers?
It might be that it breaks other assumtions within Thuban
for the lat-long boundaries.
If we have a clear no here, then we could throw an exception
when setting the layer and have other code handle giving out
a message.
Anyway:
Russel feel free to commit.
Let me know if you want me do it, if you don't have time.
Bernhard R.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://www.intevation.de/pipermail/thuban-devel/attachments/20050120/db311dd6/attachment.bin
More information about the Thuban-devel
mailing list
This site is hosted by Intevation GmbH (Datenschutzerklärung und Impressum | Privacy Policy and Imprint)