| But I have more troubles to understand why breaking code that use
spatial_ref for decades without any real need
Have you ever looked at the mess in the netcdf driver? Aligning with
recommendations from standards, especially on the write side, and
helping to reduce a bit code bloat (although
real need. Sorry, and I know it's not
> decided yet, but it looks so much the Linux culture of *easy breaking*.
>
> Joaquim
>
> -Original Message-
> From: Even Rouault
> Sent: Thursday, September 21, 2023 12:33 AM
> To: Joaquim Manuel Freire Luís ; gdal-dev@lis
aking*.
Joaquim
-Original Message-
From: Even Rouault
Sent: Thursday, September 21, 2023 12:33 AM
To: Joaquim Manuel Freire Luís ; gdal-dev@lists.osgeo.org
Subject: Re: [gdal-dev] Call for 4.0 ideas
Le 21/09/2023 à 01:12, Joaquim Manuel Freire Luís a écrit :
> Remove spatial_ref WK
Le 21/09/2023 à 01:12, Joaquim Manuel Freire Luís a écrit :
Remove spatial_ref WKT export in netCDF driver (GDAL 4) #4712
Would this mean all codes that use spatial_ref would be broken
yes, spatial_ref is AFAIK a GDAL specific thing that predates the
introduction of crs_wkt in the CF
32 PM
To: gdal-dev@lists.osgeo.org
Subject: [gdal-dev] Call for 4.0 ideas
Hi,
following latest discussions on RFC 95, I've drafted
https://github.com/OSGeo/gdal/issues/8440 with a few ideas. Please add yours
into it. We should focus on listing breaking changes, rather than new features
t
Hi,
following latest discussions on RFC 95, I've drafted
https://github.com/OSGeo/gdal/issues/8440 with a few ideas. Please add
yours into it. We should focus on listing breaking changes, rather than
new features that can be developed without involving breakage.
Even
--
http://www.spatialys
