Jonathan Moules warwickshire.gov.uk> writes:
>
>
> Hi Jukka,Good point. In fact, that's one of the reasons I want to set the
noData flag. I figure when compressing hopefully the compressor will see
that it is "noData" and will treat it differently from the way it would an
actual value (which re
Hi Jukka,
Good point. In fact, that's one of the reasons I want to set the noData
flag. I figure when compressing hopefully the compressor will see that it
is "noData" and will treat it differently from the way it would an actual
value (which results in things like your mentioned 255,255,254) so I
Jonathan Moules warwickshire.gov.uk> writes:
>
>
>
> Hi Even,
> That worked great.
> It figures that I'd tried about 6 different permutations, including a few
without "-hidenodata"; but none of them was the right one it seems.
>
>
> It's no problem recreating the tifs as they're small test t
Hi Even,
That worked great.
It figures that I'd tried about 6 different permutations, including a few
without "-hidenodata"; but none of them was the right one it seems.
It's no problem recreating the tifs as they're small test tifs that takes a
few seconds to process.
Many thanks!
Jonathan
On 3
Selon Jonathan Moules :
> Hi List,
> I have a question about setting a value as "noData" in GeoTIFFs.
>
> I'm creating a Geotiff with this two stage process (mosaicing a lot of
> tiles together):
>
> gdalbuildvrt -hidenodata -srcnodata 255 -vrtnodata 255 -input_file_list
> >> tiff_list.txt 255.v
Hi List,
I have a question about setting a value as "noData" in GeoTIFFs.
I'm creating a Geotiff with this two stage process (mosaicing a lot of
tiles together):
gdalbuildvrt -hidenodata -srcnodata 255 -vrtnodata 255 -input_file_list
>> tiff_list.txt 255.vrt
>
>
>> gdal_translate -of GTiff -co
