Changes between Initial Version and Version 1 of Ticket #3458


Ignore:
Timestamp:
Mar 4, 2010, 4:23:44 PM (14 years ago)
Author:
warmerdam
Comment:

Can you provide a gdalinfo report for the input file so I can try and construct something structurally similar to test?

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #3458

    • Property Status new → assigned
    • Property Component default → Algorithms

  • Ticket #3458 – Description

    initial v1  
    11gdalwarp is generating output that has large black rectangles that should not be there when given a large input file (a bluemarble octant).  The rectangles move around depending on the output file format and depending on the value passed to the "-wm" option.  If I use "-wm 1024" or greater the problem goes away (the input file is 1.3GB).  The warp command I am using is:
    22
    3 gdalwarp -rn -te -4000000 -3000000 0 3000000 -t_srs '+proj=gnom +lon_0=-90.0 +lat_0=58 +a=5500000 +b=5500000' -tr 2000 2000 -co 'TILED=YES' zz-src.tif zz.tif
     3{{{
     4gdalwarp -rn -te -4000000 -3000000 0 3000000 \
     5  -t_srs '+proj=gnom  +lon_0=-90.0 +lat_0=58 +a=5500000 +b=5500000' \
     6  -tr 2000 2000 -co 'TILED=YES' zz-src.tif zz.tif
     7}}}
    48
    59The same error happens with other projections, and without the TILED=YES option.  Valgrind doesn't report any errors.