Bug report #12694
Incorrect reading of OziExplorer .map raster projection file
Status: | Closed | ||
---|---|---|---|
Priority: | Normal | ||
Assignee: | - | ||
Category: | Rasters | ||
Affected QGIS version: | 2.8.1 | Regression?: | No |
Operating System: | Easy fix?: | No | |
Pull Request or Patch supplied: | No | Resolution: | fixed/implemented |
Crashes QGIS or corrupts data: | No | Copied to github as #: | 20800 |
Description
In our office we were loading a .png raster image that had an associated .JPR and .map georeferencing files. When loading this layer in QGIS Desktop 2.8.1 the image appears to land down near the equator in the incorrect position. When testing the exact same set of .png, .JPR and .map file using QGIS 2.6.0 the raster image is placed in it's real world coordinates. I've copied the output in the metadata from each version of QGIS for your comparison. I've also attached a copy of the raster files for your review.
Cheers!
David Mancini
QGIS 2.8.0
Driver
GDAL provider
VRT
Virtual Raster
Dataset Description
Band 1
Dimensions
X: 1607 Y: 2136 Bands: 1
Origin
324018,5.48999e+06
Pixel Size
30.0263,-30.0263
No Data Value
127
Data Type
Byte - Eight bit unsigned integer
Pyramid overviews
Layer Spatial Reference System
+proj=utm +zone=14 +datum=WGS84 +units=m +no_defs
Layer Extent (layer original source projection)
0.0000000000000000,-2136.0000000000000000 : 1607.0000000000000000,0.0000000000000000
Band
Band 1
Band No
1
No Stats
No stats collected yet
QGIS 2.6.0
Driver
GDAL provider
VRT
Virtual Raster
Dataset Description
Band 1
Dimensions
X: 1607 Y: 2136 Bands: 1
Origin
324018,5.48999e+06
Pixel Size
30.0263,-30.0263
No Data Value
127
Data Type
Byte - Eight bit unsigned integer
Pyramid overviews
Layer Spatial Reference System
+proj=utm +zone=14 +datum=WGS84 +units=m +no_defs
Layer Extent (layer original source projection)
324018.3895008852123283,5425853.8244448192417622 : 372270.7000576654099859,5489990.0629944661632180
Band
Band 1
Band No
1
No Stats
No stats collected yet
History
#1 Updated by Nyall Dawson over 9 years ago
- Resolution set to fixed/implemented
- Status changed from Open to Closed
Already fixed in master and will be fixed in 2.8.2