You can add a mask band to the tiff but unfortunately aside from
gdalwarp and mapserver I don't think there is any other way to read it.
see http://docs.oam.osgeo.org/storage/creating.html
Thanks Brian! I've not used masks in gdal before. From my initial
testing I think I can use that recipe f
matt,
jpeg is a lossy format. the nodata is ignored because those pixels are
no longer the same value as the nodata value.
You can add a mask band to the tiff but unfortunately aside from
gdalwarp and mapserver I don't think there is any other way to read it.
see http://docs.oam.osgeo.org/storag
Hello,
When I convert with gdal_translate and use jpeg compression in geotiff
format there is artifacting on the edges. It looks like nodata is being
ignored. Is there any way to avoid this? (and still use jpeg or
equivalent space-saving compression)
see attached.
--
matt wilkie
-
Then, to keep consistency, the fact that hdf5imagedataset isn't consistent
with the hdf5dataset is a defect, right?
May I summarize the conclusions and update the ticket?
thanks for your patience Antonio
2011/6/16 Antonio Valentino
> Hi Alex,
>
> Il giorno Thu, 16 Jun 2011 11:51:48 -0300
> Alex
Hi Alex,
Il giorno Thu, 16 Jun 2011 11:51:48 -0300
Alex Mantaut ha scritto:
> Antonio,
>Ok, I understand the asociation between the raster band
> and the metadata, but if you have to explicitally ask for the raster
> band in order to get the metadata there is an inconsistency between
Antonio,
Ok, I understand the asociation between the raster band and the
metadata, but if you have to explicitally ask for the raster band in order
to get the metadata there is an inconsistency between the interface to get
metadata from hdf5dataset and hdf5imagedataset... In hdf5dataset
Hi Alex,
Il giorno Thu, 16 Jun 2011 10:05:42 -0300
Alex Mantaut ha scritto:
> Hi Antonio,
>
> For what I discussed with Frank it seemed that the expected behavior
> was to get the only the data asociated to that subdataset (plus some
> aditional data from root and the other groups) I wasn't sur
Hi Antonio,
For what I discussed with Frank it seemed that the expected behavior was to
get the only the data asociated to that subdataset (plus some aditional data
from root and the other groups) I wasn't sure untill you confirmated...
Well, right now when I open a specific subdataset it gets on
