Hi all,
I hacked the SetBand() method so as to report the new medata in
DERIVED_SUBDATASETS mdd. Now if I gdal info a S1 dataset I get :
$ gdalinfo -nogcp -mdd DERIVED_SUBDATASETS
s1a-s6-slc-vv-20150619t195043-20150619t195101-006447-00887d-001.tiff
Driver: GTiff/GeoTIFF
Files: s1a-s6-slc-vv-
Wilfried,
>
> I'd like to use overviews for building image pyramids with a scale
> reduction of 2 for photogrammetric applications. While
> GDALDataset::BuildOverviews allows for the specification of "overview
> decimation factors" as integers only, GDAL seems to interpret these
> factors as hint
>
> Even, I think the AddBand() method is obviously not the right place to
> do that, but I do not get how tweak the GetMetadata() /
> GetMetadataDomainList().
Hum I'm not sure how to better explain. I almost coded it ;-)
> As far as I can tell from the code, datasets
> never directly declare ne
Le 06/07/2016 à 10:26, Even Rouault a écrit :
Even, I think the AddBand() method is obviously not the right place to
do that, but I do not get how tweak the GetMetadata() /
GetMetadataDomainList().
Hum I'm not sure how to better explain. I almost coded it ;-)
Sorry, it is my first time coding in
Le 06/07/2016 à 10:26, Even Rouault a écrit :
Even, I think the AddBand() method is obviously not the right place to
>do that, but I do not get how tweak the GetMetadata() /
>GetMetadataDomainList().
Hum I'm not sure how to better explain. I almost coded it;-)
I figured it out (or at least I fi
Le mercredi 06 juillet 2016 11:28:24, Julien Michel a écrit :
> Le 06/07/2016 à 10:26, Even Rouault a écrit :
> >> Even, I think the AddBand() method is obviously not the right place to
> >>
> >> >do that, but I do not get how tweak the GetMetadata() /
> >> >GetMetadataDomainList().
> >
> > Hum I
Dear Even,
I'm not referring to a specific interpolation method. However, for
checking GDAL's behaviour, nearest-neighbor interpolation is surely the
easiest way. And yes, it may seem arbitrary whether to select only even
rows/columns or only odd rows/columns of the base image when
downsampling by
Le mercredi 06 juillet 2016 12:52:15, Wilfried Karel a écrit :
> Dear Even,
>
> I'm not referring to a specific interpolation method. However, for
> checking GDAL's behaviour, nearest-neighbor interpolation is surely the
> easiest way.
I guess the effect is the most distracting with nearest neigh
Dear Even,
On 06.07.2016 13:45, Even Rouault wrote:
> Le mercredi 06 juillet 2016 12:52:15, Wilfried Karel a écrit :
>> Dear Even,
>>
>> I'm not referring to a specific interpolation method. However, for
>> checking GDAL's behaviour, nearest-neighbor interpolation is surely the
>> easiest way.
>
Hi,
The explicit feedback has been modest, but positive so far, so :
Motion 1: GDAL/OGR 1.11.5 RC1 is promoted to be the official 1.11.5 final
release.
Motion 2: GDAL/OGR 2.0.3 RC2 is promoted to be the official 2.0.3 final release.
Motion 3: GDAL/OGR 2.1.1 RC1 is promoted to be the official 2
You were right (what a surprise !). I pushed the new
GetMetadataDomainList() / GetMetadata() methods to gdaldataset, as well
as the fix for geotiff (and some other fixes).
Now works like a charm even with subdatasets.
Regards,
Julien
Le 06/07/2016 à 11:49, Even Rouault a écrit :
Le mercred
Hi Even,
has this improvement also being backported on previous versions (as an
instance 2.1.x, 2.0.x)?
Cheers,
Daniele
On Tue, May 10, 2016 at 3:29 PM, Even Rouault
wrote:
> Le mardi 10 mai 2016 09:22:19, jramm a écrit :
> > Hi
> > I have made changes to FillEmptyTiles so that if nodata is set
Thank you, Jürgen! This is exactly what I was looking for.
Thank you,
Chris
-Original Message-
From: gdal-dev [mailto:gdal-dev-boun...@lists.osgeo.org] On Behalf Of Jürgen
E. Fischer
Sent: Saturday, July 2, 2016 2:27 PM
To: gdal-dev@lists.osgeo.org
Subject: Re: [gdal-dev] Test Windows Bu
> Yes, with interpolation methods that take into account more than a
> single pixel of the source image, this effect will not be that obvious.
> But that doesn't resolve the problem if one is interested in more than
> just visualization, but e.g. in deriving positions from the image
> content, as
Daniele,
> has this improvement also being backported on previous versions (as an
> instance 2.1.x, 2.0.x)?
No, trunk only.
You could as well use the SPARSE_OK=TRUE creation option to avoid writting
blocks at all. Provided that your reader knows how to deal with tile/strips
with a 0 byte count
Hi Even,
thanks I'm already using the SPARSE_OK=TRUE to create an empty tiff
and afterwards warp input files on that with SKIP_NOSOURCE=YES.
I have already updated the ImageIO-EXT's TIFFImageReader to deal with
tile/strip with zero byte count.
Final question:
Starting from which GDAL version, SPAR
Le mercredi 06 juillet 2016 16:17:32, Daniele Romagnoli a écrit :
> Hi Even,
> thanks I'm already using the SPARSE_OK=TRUE to create an empty tiff
> and afterwards warp input files on that with SKIP_NOSOURCE=YES.
> I have already updated the ImageIO-EXT's TIFFImageReader to deal with
> tile/strip w
Hi, Jürgen. Do you happen to know of similar tests for the output
executables and libraries?
Thank you,
Chris
-Original Message-
From: Christopher McGeorge [mailto:cmcgeo...@surgeforward.com]
Sent: Wednesday, July 6, 2016 7:38 AM
To: 'Jürgen E. Fischer'
Cc: gdal-dev@lists.osgeo.org
Sub
Dear developers, I thought people on this list might find my latest little
tool entertaining and/or useful:
https://github.com/daleroberts/tv
... and thank you for the great subsampling feature in GDAL 2. I've used it
on a couple of different projects and it's fantastic.
_
I'm in need of "max" resampling in gdaladdo, to preserve the highest points
in elevation raster overviews. I've found that gdalwarp supports "-r max",
but gdaladdo doesn't.
Can I achieve what I need (with prebuilt GDAL binaries)? (How?)
Will future versions of gdaladdo support "-r max"? (When?)
20 matches
Mail list logo