Thanks for the fix Even.
> On 30 Mar 2022, at 14:21, Even Rouault wrote:
>
> Pete,
>
> ouch, confirmed, and fix queued in https://github.com/OSGeo/gdal/pull/5547 .
> And the commit you mention was indeed the culprit.
>
> Potential workarounds (besides generating the VRT on GDAL <= 3.4.0)
>
>
Thank you everyone for the responses, and Even for the bug fix.
Best regards,
Robin
On 29 March 2022 at 22:33:49, Even Rouault (even.roua...@spatialys.com) wrote:
Was a bug. Fix queued in https://github.com/OSGeo/gdal/pull/5543
Le 29/03/2022 à 22:30, Robin Wilson a écrit :
Hi,
I’ve been runn
Pete,
ouch, confirmed, and fix queued in
https://github.com/OSGeo/gdal/pull/5547 . And the commit you mention was
indeed the culprit.
Potential workarounds (besides generating the VRT on GDAL <= 3.4.0)
- if using gdalbuildvrt on a single source, you could just use
"gdal_translate sen2_20210
Hi,
I can confirm with GDAL 3.5.0dev from gisinternals and with a normal RGB
ortoimage.
gdalbuildvrt test.vrt p4433h.tif -b 2
0...10...20...30...40...50...60...70...80...90...100 - done.
ERROR 5: p4433h.tif: GDALDataset::GetRasterBand(2) - Illegal band #
With -b 1 -b 2 the command runs fine.
-
Hi,
With the release of gdal 3.4.2, gdalbuildvrt seems to have a bug when selecting
image bands. It works OK when band 1 is specified but if other band(s) in the
image are used without band 1 then it seg faults. I noticed there were some
changes around checking bands in the release notes "chan
