[postgis-devel] [PostGIS] #1808: [raster] Raster importation creates gaps and corrupted data

[PostGIS]

#1808: [raster] Raster importation creates gaps and corrupted data
--------------------+-------------------------------------------------------
 Reporter:  molgor  |       Owner:  dustymugs    
     Type:  defect  |      Status:  assigned     
 Priority:  high    |   Milestone:  PostGIS 2.0.2
Component:  raster  |     Version:  2.0.x        
 Keywords:          |  
--------------------+-------------------------------------------------------

Comment(by dustymugs):

 On the postgis-users mailing list, a different user described a similar
 (same?) issue regarding gaps and corrupted data.

 [http://postgis.refractions.net/pipermail/postgis-
 users/2012-July/034710.html]

 The user was able to privately provide the raster in question for testing.
 The raster was loaded on a Linux 64-bit dev box running PostgreSQL 9.1.2
 and PostGIS trunk r10035 with the the following:

 {{{
 raster2pgsql -s 4326 -t 10x10 -I -C sft00.tif test_1808 | psql -d test
 }}}

 The output of gdalinfo on sft00.tif is

 {{{
 Driver: GTiff/GeoTIFF
 Files: sft00.tif
        sft00.tfw
        sft00.tif.aux.xml
 Size is 1760, 880
 Coordinate System is:
 GEOGCS["WGS 84",
     DATUM["WGS_1984",
         SPHEROID["WGS 84",6378137,298.257223563,
             AUTHORITY["EPSG","7030"]],
         AUTHORITY["EPSG","6326"]],
     PRIMEM["Greenwich",0],
     UNIT["degree",0.0174532925199433],
     AUTHORITY["EPSG","4326"]]
 Origin = (-180.102272599999992,89.946211599999998)
 Pixel Size = (0.204545041250000,-0.204422967727273)
 Metadata:
   AREA_OR_POINT=Area
 Image Structure Metadata:
   INTERLEAVE=BAND
 Corner Coordinates:
 Upper Left  (-180.1022726,  89.9462116) (180d 6' 8.18"W, 89d56'46.36"N)
 Lower Left  (-180.1022726, -89.9460000) (180d 6' 8.18"W, 89d56'45.60"S)
 Upper Right ( 179.8970000,  89.9462116) (179d53'49.20"E, 89d56'46.36"N)
 Lower Right ( 179.8970000, -89.9460000) (179d53'49.20"E, 89d56'45.60"S)
 Center      (  -0.1026363,   0.0001058) (  0d 6' 9.49"W,  0d 0' 0.38"N)
 Band 1 Block=1760x1 Type=Float32, ColorInterp=Gray
   Min=-78.197 Max=53.275
   Minimum=-78.197, Maximum=53.275, Mean=8.062, StdDev=22.105
   Metadata:
     STATISTICS_MAXIMUM=53.275016784668
     STATISTICS_MEAN=8.0621312493133
     STATISTICS_MINIMUM=-78.196998596191
     STATISTICS_STDDEV=22.104605706292
 }}}

 To validate that the raster loaded into PostGIS was clean, a pixel by
 pixel validation was done using compare_new.sh (attached to ticket).  Upon
 completion of the validation, the script found that every pixel value in
 PostGIS matched that of the source raster (as sampled using
 gdallocationinfo)

 As the user specified, the raster DOES look corrupted in QGIS 1.7.3 when
 loaded with DB Manager and PostGIS Raster plugin.

 The user is also running compare_new.sh (modified for PostGIS 2.0) on the
 user's machine to ensure that the comparison also completes cleanly.
 Assuming that the comparison is successful, a ticket will be filed with
 QGIS.  QGIS 1.8 should be tested as well.

-- 
Ticket URL: <http://trac.osgeo.org/postgis/ticket/1808#comment:19>
PostGIS <http://trac.osgeo.org/postgis/>
The PostGIS Trac is used for bug, enhancement & task tracking, a user and developer wiki, and a view into the subversion code repository of PostGIS project.