On Thu, Oct 29, 2020 at 3:15 PM Even Rouault
wrote:
> Sean,
>
> > In rasterio's tests I have noticed a change in the order of coordinates
> in
> > the interior rings of polygons extracted by GDAL's polygonizer and a
> change
> > in the number of polygons extracted, but no other issues. I don't
Hi all,
I am using gdal_translate to read a VRT file made up of COGs stored in S3.
This works great when downsampling using nearest neighbour (GDAL 2.4.2):
$ time gdal_translate /vsis3/bucket/mosaic.vrt /tmp/out.tiff -projwin
-9177335.364031402 5305341.259217514 -9174889.379126277
On 2020-10-29 5:55 a.m., Even Rouault wrote:
Hi,
Having heard about no critical ([1]) issues regarding RC1
Motion:
Adopt GDAL 3.2.0 RC1 as final 3.2.0 release
+1
Works well on Windows.
The documentation build now throws 27 Doxygen warnings (with Doxygen
1.8.20).
-jeff
--
Jeff
Sean,
> In rasterio's tests I have noticed a change in the order of coordinates in
> the interior rings of polygons extracted by GDAL's polygonizer and a change
> in the number of polygons extracted, but no other issues. I don't think
> these need to hold up the release.
Hum, changes in the
Hi Even,
On Thu, Oct 29, 2020 at 2:55 AM Even Rouault
wrote:
> Hi,
>
> Having heard about no critical ([1]) issues regarding RC1
>
> Motion:
>
> Adopt GDAL 3.2.0 RC1 as final 3.2.0 release
>
> Starting with my +1
>
> Even
>
> [1] The only regression I'm aware of currently is regarding the
>
+1
Daniel
On 2020-10-29 04:55, Even Rouault wrote:
Hi,
Having heard about no critical ([1]) issues regarding RC1
Motion:
Adopt GDAL 3.2.0 RC1 as final 3.2.0 release
Starting with my +1
Even
[1] The only regression I'm aware of currently is regarding the possibility to
open raw LERC1
+1
Norman
On Thu, Oct 29, 2020 at 4:39 AM jratike80 <
jukka.rahko...@maanmittauslaitos.fi> wrote:
> +1
>
> -Jukka Rahkonen-
>
>
> Even Rouault-2 wrote
> > Hi,
> >
> > Having heard about no critical ([1]) issues regarding RC1
> >
> > Motion:
> >
> > Adopt GDAL 3.2.0 RC1 as final 3.2.0 release
>
+1
-Jukka Rahkonen-
Even Rouault-2 wrote
> Hi,
>
> Having heard about no critical ([1]) issues regarding RC1
>
> Motion:
>
> Adopt GDAL 3.2.0 RC1 as final 3.2.0 release
>
> Starting with my +1
>
> Even
>
> [1] The only regression I'm aware of currently is regarding the
> possibility to
>
+1
Mateusz
On Thu, 29 Oct 2020 at 09:55, Even Rouault wrote:
>
> Motion:
> Adopt GDAL 3.2.0 RC1 as final 3.2.0 release
>
> Starting with my +1
--
Mateusz Loskot, http://mateusz.loskot.net
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
Hi,
Having heard about no critical ([1]) issues regarding RC1
Motion:
Adopt GDAL 3.2.0 RC1 as final 3.2.0 release
Starting with my +1
Even
[1] The only regression I'm aware of currently is regarding the possibility to
open raw LERC1 files in the MRF driver that is broken. See
Hi,
But you did not find out what is special in the spatial reference of your
source image and why GDAL 3.0.2 did not find it while 2.4.1 had no problem.
First step would be to run gdalinfo with 2.4.1 and 3.0.2 and compare the
reports.
-Jukka Rahkonen-
Laurynas Gedminas wrote
> OK, so the
11 matches
Mail list logo