>> Shaun Kolomeitz wrote: >> > could push beyond 1GB/s. Currently to process (mosaic) an 80GB image it >> > takes several days to complete. This is also on 32bit hardware, and I >> >> Shaun, > >> I suspect that there is a gross issue with how the warping is being done, >> and that it could be sped up substantially. On my two year old consumer >> grade desktop I'm able to warp/reproject around 30GB/hour with gdalwarp.
>My numbers for warping single images or small mosaics with cubic spline option >show about 12 GB/hour. However, I have tried sometimes to warp tens of gigabytes >of imagery through .vrt file to a BigTIFF and that process progressed very very >slow. I need to admit that I used ER Mapper and ERDAS Imagine and never bothered >to investigate further what was going wrong when building mosaic with gdal. I >have lot of imagery easily available and I volunteer for testing is somebody has >suggestions for better gdalwarp parameters or has new program versions to try. >-Jukka Rahkonen- Hi Folks, Here's the gdal command (gdal 1.6.2) I used to merge ~3500 1 meter NAIP quarter quads (uncompressed geotiff TIFF) in 3 UTM projections into one Bigtiff Image in the USGS Albers projection. It took about 15 hours ( on a 3 year old Intel Core2 Duo 64 bit Centos 5.3 Linux box with 6GB RAM) and created an uncompressed, tiled, bigtiff file of 485 GB. About 32 GB/hr. gdalwarp -t_srs "+proj=aea +lat_1=29.5 +lat_2=45.5 +lat_0=23.0 +lon_0=-96 +x_0=0 +y_0=0 +ellps=GRS80 +datum=NAD83 +units=m no_defs <>" -wo "SKIP_NOSOURCE" --config "GDAL_CACHEMAX=500" -wm=5000 -co "TILED=YES" */*.tif /biggis/albers/nc_naip2008.tif In the above command, -t_srs "+proj=aea +lat_1=29.5 +lat_2=45.5 +lat_0=23.0 +lon_0=-96 +x_0=0 +y_0=0 +ellps=GRS80 +datum=NAD83 +units=m no_defs <>" indicates the target projection, -wo "SKIP_NOSOURCE" don't write in areas for which there is no data for the current file, --config "GDAL_CACHEMAX=500" set the cache memory at 500MB ( set this close to the maximum input file size), -wm=5000 set the warp memory to 5000MB , -co "TILED=YES" create a tiled tiff as output, */*.tif, use all of the tiffs in all of the subdirectories as input files ( in this case there was one directory for each of the 3 utm zones) , /biggis/albers/nc_naip2008.tif, the output file name and location. Hmm, I may have to do this again, I didn't include the -rcs option. Doug Doug Newcomb USFWS Raleigh, NC 919-856-4520 ext. 14 [email protected] --------------------------------------------------------------------------------------------------------- The opinions I express are my own and are not representative of the official policy of the U.S.Fish and Wildlife Service or Dept. of the Interior. Life is too short for undocumented, proprietary data formats. Jukka Rahkonen <jukka.rahko...@m mmtike.fi> To Sent by: [email protected] gdal-dev-bounces@ cc lists.osgeo.org Subject [gdal-dev] Re: CUDA PyCUDA and GDAL 11/19/2009 03:08 AM Frank Warmerdam <warmerdam <at> pobox.com> writes: _______________________________________________ gdal-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/gdal-dev
<<inline: graycol.gif>>
<<inline: pic18467.gif>>
<<inline: ecblank.gif>>
_______________________________________________ gdal-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/gdal-dev
