Yes I am finding it can be dependent on the input dataset dimensions - Im only reproducing with a large raster. It is perhaps a small problem anyway since apparently MapInfo will not handle files > 2GB anyway. I will try using VSIFTruncateL to initialize.
On 13 July 2016 at 15:21, Even Rouault <[email protected]> wrote: > Le mercredi 13 juillet 2016 15:41:36, jramm a écrit : > > jramm wrote > > > > > gdalwarp -of NWT_GRD -ot Float32 -t_srs EPSG:4326 test.tif test.grd > > > > > > very quickly returns > > > > Sorry this meant to read: > > > > very quickly returns: > > > > 0ERROR 1: /home/jamesramm/test.grd, band 1: IReadBlock failed at X offset > > 0, Y offset 0 > > ERROR 1: GetBlockRef failed at X block offset 0, Y block offset 0 > > I don't manage to reproduce. Might perhaps depend on the dimensions of the > input dataset and/or cache size used > > That said, it is not inconsistant that some code tries to read blocks on > the > newly created dataset. Probably that the Create() method should use > VSIFTruncateL() to set the file to the full size if filling with zeroes is > OK > for the format. Otherwise you may need to pad with more appropriate values. > That way potential IReadBlock() won't error out. > > > > > > > > > > > -- > > View this message in context: > > > http://osgeo-org.1560.x6.nabble.com/Error-in-GDALWarp-to-NWT-GRD-tp5276136 > > p5276137.html Sent from the GDAL - Dev mailing list archive at > Nabble.com. > > _______________________________________________ > > gdal-dev mailing list > > [email protected] > > http://lists.osgeo.org/mailman/listinfo/gdal-dev > > -- > Spatialys - Geospatial professional services > http://www.spatialys.com >
_______________________________________________ gdal-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/gdal-dev
