Hi Javier,
the difference between 3.9.2 and 3.11 that explains what you see is :
https://github.com/OSGeo/gdal/commit/a4aa0b50154b0558e2677a31dde416452ac07c97
: "OGRSpatialReference::importFromEPSG(): tries with ESRI when it looks
like an ESRI code, but with a warning when that succeeds"
The
Hi
I would like to understand why do I have different behaviour recognizing a
WKT between GDAL 3.9.2 and 3.11.1, both using PROJ 9.5.0 (using C++)
There is a clear mistake in the WKT bellow: EPSG:102641 . It should be
ESRI. But the source of the data was wrong, and we worked with that for a
long
Hi all,
I implemented a plugin raster format that produces raster of random values
using the all the distributions that are offered by the standard library's
random header. It is different from other random raster functionality in e.g.
ArcGIS or QGIS because it does not store the data on file b
"Small Language Mode"
LOL
On Fri, 4 Jul 2025 at 12:21, Even Rouault via gdal-dev <
gdal-dev@lists.osgeo.org> wrote:
> Hi Michael,
>
> I guess this is finally the perfect use case we were waiting for to find a
> good reason to embed a Small Language Model within GDAL to figure out what
> are the c
Thanks Even! Amazing, I don't think this is a rare case either, there's a
lot of data in files "like this" that I keep encountering.
Another few lines in the NetCDF behemoth, I'll keep reading (and update my
AI subscriptions).
Cheers, Mike
On Fri, Jul 4, 2025 at 8:21 PM Even Rouault
wrote:
>
Hi Michael,
I guess this is finally the perfect use case we were waiting for to find
a good reason to embed a Small Language Model within GDAL to figure out
what are the columns and lines axis. In the meantime, the boring
https://github.com/OSGeo/gdal/pull/12700 will fix it
Even
Le 04/07/2