Bug#949274: pyresample autopkg tests regressed in unstable
Bas Couwenberg
sebastic at xs4all.nl
Wed Jan 22 07:39:28 GMT 2020
On 2020-01-22 08:12, Antonio Valentino wrote:
> On Sun, 19 Jan 2020 08:44:48 +0100 Matthias Klose <doko at debian.org>
> wrote:
>> - WGS_1984_Web_Mercator_Auxiliary_Sphere
>> + WGS 84 / Pseudo-Mercator
>
> I gave a very quick look to the issue and it seems that the problem has
> be triggered bu the update to gdal 3.0.3.
>
> -gdal-data 3.0.2+dfsg-1
> +gdal-data 3.0.3+dfsg-1
> -libgdal26 3.0.2+dfsg-1
> +libgdal26 3.0.3+dfsg-1
>
> rasterio could be also involved since the specific test uses rasterio
> to
> retrieve the information about the geographic projection
>
> I don't see any change in gdal data at a first look so probably the
> problem is related behavior change in gdal that is not correctly
> handled
> by pyresample or rasterio.
>
> I need to make some additional investigation.
GDAL 3 is the first to fully support PROJ 6, it now relies on PROJ and
its database for CRS data instead the data files included in gdal-data.
The test should either expect the new name or expect both.
Kind Regards,
Bas
More information about the Pkg-grass-devel
mailing list