[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.1
Component:  raster  |     Version:  2.0.x        
 Keywords:          |  
--------------------+-------------------------------------------------------

Comment(by dustymugs):

 I updated the fill_1808.py script to populate the test raster with psuedo-
 random floating point values between 0 and 100.  I also wrote a pixel-for-
 pixel comparison script to validate that what is loaded into PostGIS with
 raster2pgsql matches that of the source test raster.  The comparison
 script requires the latest revision of postgis-trunk due to a bug I found
 in 2.0.

 Due to the massive size of the source test raster, I had my initial
 comparisons only checking every N pixels (113 or some other prime number).
 All those tests ran fine.  I'm running a final test checking every pixel.

-- 
Ticket URL: <http://trac.osgeo.org/postgis/ticket/1808#comment:16>
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.