Opened 13 years ago
Last modified 13 years ago
#3504 new bug
Zoom to full or layer extent fails after OTF transformation
Reported by: | gsherman | Owned by: | mhugent |
---|---|---|---|
Priority: | major: does not work as expected | Milestone: | Version 1.7.0 |
Component: | Projection Support | Version: | Trunk |
Keywords: | Cc: | ||
Must Fix for Release: | Yes | Platform: | All |
Platform Version: | Awaiting user input: | no |
Description
Load a layer (e.g. alaska.shp from the sample data set). Turn on OTF transformation and choose NAD27 as the target coordinate system. Once set, click on Zoom full or zoom to layer extent. It doesn't work. Using the zoom to point plugin and putting -150, 60 and zooming shows the data is there and reprojected to NAD27 geographic.
This problem has been confirmed in HEAD on Windows, Mac, and Ubuntu.
Change History (9)
comment:1 by , 13 years ago
comment:2 by , 13 years ago
Yes, I'm sure. It works on both 1.5 and 1.6 on OS X. It also works on 1.6 on Windows with the standalone installer. I don't have earlier versions for other platforms to test.
comment:3 by , 13 years ago
Owner: | changed from | to
---|
comment:4 by , 13 years ago
The change in r15131 may not be the root cause. Projection is not getting set when loading a layer (e.g. from the alaska sample set). If you load the layer, set the projection to Alaska Albers NAD27 then reproject to geographic the zoom full works.
comment:5 by , 13 years ago
comment:6 by , 13 years ago
Component: | Build/Install → Projection Support |
---|
Are you sure that worked with 1.6? landice works, alaska or airports does not. Looks like it's a problem with extents crossing the dateline. I think we don't have a way to express that a bounding box for a latlong crs is including the dateline instead of excluding it.