[gdal-dev] Trouble with gdal2tiles.py

Greg Coats gregcoats at mac.com
Thu Jul 29 14:00:53 EDT 2010


First, instead of using GDAL 1.6.0 from December 2008, why not use GDAL 1.7.2 from April 2010?
Second, since your objective is to create a tiled GeoTIFF, you can do that with one gdal_translate command.
$ gdal_translate --version
GDAL 1.7.2, released 2010/04/23
$ gdal_translate -of GTiff -ot Byte -co Compress=NONE \
-co TILED=YES -co BLOCKXSIZE=256 -co BLOCKXSIZE=256 \
18stj940125.if 18stj940125_gdal_translate.tif
Input file size is 5000, 5000
0...10...20...30...40...50...60...70...80...90...100 - done.
Greg

On Jul 29, 2010, at 2:50 AM, Brett Walker wrote:

> I’m trying to produce a tile matrix set from geocoded tiffs using gdal2tiles.py but I am having trouble with the last step in  the process.
>  
> As an example I have a BSB file from NOAA which is a navigational map of Lake Pend Oreille in Idaho. The map has a SRS of WGS84 and a Mercator projection.
>  
> I initially translate the file from BSB format to GTiff format using the following command:
>  
> > gdal_translate -of GTiff noaa\18554_1.kap noaa.tif
>  
> I can view this GTiff file using Paint Shop Pro quite fine. I then translate the file from GTiff format to VRT format using the following command:
>  
> > gdal_translate -of vrt –expand rgba noaa\noaa.tif noaa\noaa.vrt
>  
> I then try to generate a tile matrix set using the following command:
>  
> > gdal2tiles.py noaa\noaa.vrt noaa
>  
> But get the follwoing error:
>  
> > ERROR 1: failed to load NAD27-83 correction file
> > ERROR 1: GDALSuggestedWarpOutput() failed because the passed
> > transformer failed.
> > usage: Usage: gdal2tiles.py [options] input_file(s) [output]
> > 
> > gdal2tiles.py: error: Size of the pixel in the output differ for X and Y axes.
> 
> Am I missing something?
>  
> My system is Windows Vista (32-bit). I’m using GDAL v1.6.0 win32 binary, GDAL v1.6.0 python package, PROJ4 v4.4.6 win32 binary, NumPy v1.2.1 for win32 and Python v2.4.1
> I have set all the appropriate system variables and copied files to approprate locations. This was done following the guidelinse athttp://www.gis.usu.edu/~chrisg/python/2009/docs/gdal_win.pdf except that I omitted steps 3f and 3g.
>  
> Hope you can help.
> Brett
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/gdal-dev/attachments/20100729/7e9c3b9b/attachment-0001.html


More information about the gdal-dev mailing list