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

PostGIS trac at osgeo.org
Thu May 10 10:08:30 PDT 2012


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

Comment(by dustymugs):

 So, I created a test raster of the same characteristics as your source
 raster using the following.

 {{{
 gs -q -dNOPAUSE -sDEVICE=tiffgray -g28368x19839 -sOutputFile=temp.tif -c
 showpage quit

 create contents of temp.tifw
 --
 0.002424431085498
 0
 0
 -0.002424431085498
 -128.603699283545
 53.625756173363
 --

 gdal_translate -ot Float32 -a_srs EPSG:4326 -a_nodata -32767 temp.tif
 1808.tif
 }}}

 I imported the raster 1808.tif into a test database using...

 {{{
 raster2pgsql -s 4326 -t 256x256 -I -C 1808.tif test_1808 | psql -U
 postgres -d test
 }}}

 I did not use the -N flag as your source raster already had a NODATA value
 as per the gdalinfo output.

 Visualizing the imported raster against the source raster in QGIS shows no
 problems.  I'll see about striping the test raster to see if there is any
 tearing or gaps as you're seeing.

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


More information about the postgis-devel mailing list