New answers tagged

1

Put the proj4 string between quotes. Now the string gets split at parsing and GDAL thinks that the +ellps is a name of the source file.


2

Using the EPSG works: gdalwarp -t_srs EPSG:4269 RipBuf100_09.tif RipB uf100WGS_09.tif Creating output file that is 55104P x 24192L. Processing input file RipBuf100_09.tif. Using internal nodata values (e.g. -2.14748e+009) for image RipBuf100_09.tif. Copying nodata values from source RipBuf100_09.tif to destination ...


1

shot in the dark, but maybe use the EPSG instead of the actual CRS label


2

you can use gdalbuildvrt instead of gdalmerge to create a virtual raster template (xml file) that will behave like a merged raster. then you can run gdal_translate with the -projwin option for your set of 256*256 tiles. For most of my applications, I would create a single output per face then use gdalbuildvrt for virtual tiles. Note that if you create one ...


5

You have now a better way to do. Since RFC 59.1 : GDAL/OGR utilities as a library, you can use gdalwarp from Python directly without using any call to the command line utility but using really the function from Python. This solution is a bit "on the edge" as you need at the moment to use the latest GDAL version (version 2.1, in fact the master/trunk ...



Top 50 recent answers are included