[gdal-dev] gdalwarp on a .vrt: Using internal nodata values (eg 0) for image (?)

2015-06-11 Thread Ari Simmons
I am experimenting with using 'gdalwarp' on a .vrt (first time), but I'm not sure what I'm doing wrong. I've been running this: >> gdalwarp -s_srs EPSG:4326 -t_srs EPSG:3857 -r bilinear -of VRT merged.vrt srtm_merged_3857.vrt and it processes fast (far far *too fast* for this global file) and ret

Re: [gdal-dev] gdalwarp on a .vrt: Using internal nodata values (eg 0) for image (?)

2015-06-11 Thread Ari Simmons
One notably huge difference is that there is a huge jump in pixel size (from 0.0008323 to 205.686440189378940)... ah, duh. Unit change. On Thu, Jun 11, 2015 at 2:26 PM, Ari Simmons wrote: > I am experimenting with using 'gdalwarp' on a .vrt (first time), but I'm > not sure what I'm doin

Re: [gdal-dev] gdalwarp on a .vrt: Using internal nodata values (eg 0) for image (?)

2015-06-11 Thread Eli Adam
On Thu, Jun 11, 2015 at 2:38 PM, Ari Simmons wrote: > One notably huge difference is that there is a huge jump in pixel size (from > 0.0008323 to 205.686440189378940)... > > ah, duh. Unit change. > > On Thu, Jun 11, 2015 at 2:26 PM, Ari Simmons wrote: >> >> I am experimenting with using '

Re: [gdal-dev] gdalwarp on a .vrt: Using internal nodata values (eg 0) for image (?)

2015-06-12 Thread Ari Simmons
Do you mean gdal_translate -te -13813007 5569641 -13809113 5572598 srtm_merged_3857.vrt my_subwindow.tif --config GDAL_CACHEMAX 800 ? On Thu, Jun 11, 2015 at 3:08 PM, Eli Adam wrote: > On Thu, Jun 11, 2015 at 2:38 PM, Ari Simmons > wrote: > > One notably huge difference is that there is a hu

Re: [gdal-dev] gdalwarp on a .vrt: Using internal nodata values (eg 0) for image (?)

2015-06-12 Thread Eli Adam
On Fri, Jun 12, 2015 at 11:25 AM, Ari Simmons wrote: > Do you mean > > gdal_translate -te -13813007 5569641 -13809113 5572598 > srtm_merged_3857.vrt my_subwindow.tif --config GDAL_CACHEMAX 800 > > ? Oops, I made a bad typo by omitting -projwin: gdal_translate -projwin -13813007 5569641 -1380911