Re: [Gdal-dev] GDAL "ignores" explicitly defined nodata value

2009-10-01 Thread orbiter_postmuch
Bump to avoid the issue from remaining unsolved. - Using 1.6.0 on Vista. All answers must be in DOS batch file format. -- View this message in context: http://n2.nabble.com/GDAL-ignores-explicitly-defined-nodata-value-tp3720196p3753058.html Sent from the GDAL - Dev mailing list archive at N

[Gdal-dev] GDAL "ignores" explicitly defined nodata value

2009-09-27 Thread orbiter_postmuch
NOTE-Since people' responses come through the mailing list only, expect a line of new topics in a row by me to flood (by "flood" I mean 4 topics in a row by the same author) the forum. After successfully building the .vrt and translating it to .img, I opened the file and found that the white (nod

[Gdal-dev] (Frustrated)Errors when mosaicking geotiff files

2009-09-26 Thread orbiter_postmuch
NOTE-Revised message I am trying to mosaick 318 tiffs in WGS84 projection, but have not succeeded. Here is what I want to do: 1.Mosaick files together using a batch file that uses delayed expansion to accept wildcards (*.tif) 2.Save as file where <-format-> allows sizes larger than 4GB. When I

[Gdal-dev] Mosaicking MOD44W landmask (318 geotiffs)

2009-09-24 Thread orbiter_postmuch
After nabble decides to crash, I have to post this message all again. I tried this script to mosaick the 318 tiffs: @echo off :: initial version, 2005-Nov-17, matt wilkie :: this script is public domain if [%1]==[] ( echo. echo -={ gdal_wildmerge }=- Allow gdal_merge to accep