Re: [gdal-dev] dataset with no driver?

Mike, there are a number of situations where you can get a Dataset not linked to a driver. Code expecting a Dataset as input should be robust to it having a null driver. In your situation, given that small_world.tif is a multiband dataset, but AsMDArray().AsClassicDataset() returning a singl

Re: [gdal-dev] Errors while creating sozip zarr file

Erik, I don't think it is really worth sozip'ing a zipped Zarr, given that zarr is made of many relatively small files, and sozip shines with big compressed files.  Generally, even when creating a zipped (sozip or not) Zarr file, you need to make sure that your writing pattern matches chunks

Re: [gdal-dev] Understanding parquet vs adbc performance and SORT_BY_BBOX=YES

Le 20/07/2025 à 13:27, Michael Smith via gdal-dev a écrit : Using GDAL 3.11.3: I have a dataset Geometry: Point Feature Count: 15546949 in parquet format (written using gdal from oracle source). When doing a spatial query using the geoparquet driver, I see it accessing almost all the row gro

Re: [gdal-dev] Java bindings to gdal/ogr - looking for more developer documentation

ave any suggestions about this I would be happy to try it. Tom On Fri, May 30, 2025, at 5:53 PM, Even Rouault wrote: Le 30/05/2025 à 23:39, Tom Moore a écrit : > Hi Even > > I just wanted to update you and provide a record for posterity with > the results of me playing around wi

Re: [gdal-dev] ADBC driver and DuckDB on Windows

Mike, I don't remember the details but there's an issue (or at least used to be last time I tried) with the conda package libadbc-driver-manager on Windows. Le 12/07/2025 à 13:46, Michael Smith via gdal-dev a écrit : Seth, Have you tried adding https://anaconda.org/conda-forge/libadbc-drive

Re: [gdal-dev] ADBC driver and DuckDB on Windows

Seth, there has been an enhancement in *master* (not in 3.11) for being able to load libduckdb when the ADBC driver is built without libadbc-driver-manager support. So if you're not on master, this is expected Even Le 12/07/2025 à 12:45, Seth G via gdal-dev a écrit : Hi all, I'm wondering

[gdal-dev] GDAL 3.11.3 is released

Hi, Without any advanced warning, here's a 3.11.3 whose only difference with 3.11.2 is the following fix for a regression that went in 3.11.1: PG driver:  * restore string truncation that was broken in 3.11.1 Consult the release notes for the list of issues addressed:     https://github.com/

Re: [gdal-dev] Problems setting up the Windows build environment for first time

Tom, you can drop the clcache dependency if that helps. Otherwise try to create a conda env from scratch (if you didn't do that) Even Le 11/07/2025 à 02:31, Tom Moore via gdal-dev a écrit : Newbie here.  As the title says I am trying to set up a build environment. I was trying to follow the

[gdal-dev] GDAL 3.11.2 is released

Hi, On behalf of the GDAL/OGR development team, I am pleased to announce the release of the GDAL/OGR 3.11.2 bug fix version. Consult the release notes for the list of issues addressed:     https://github.com/OSGeo/gdal/blob/v3.11.2/NEWS.md The sources are available at:     https://download.o

Re: [gdal-dev] Motion: approve GDAL 3.11.2RC2 as final release

Motion passed with +1 from PSC members JavierJS, JukkaR, TamasS, NormanB, MichaelS, HowardB and me Le 09/07/2025 à 09:30, Even Rouault via gdal-dev a écrit : Hi, starting with my +1 Even -- http://www.spatialys.com My software is free, but my time generally not

[gdal-dev] Motion: approve GDAL 3.11.2RC2 as final release

Hi, starting with my +1 Even -- http://www.spatialys.com My software is free, but my time generally not. ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev

[gdal-dev] 3.11.2 RC2 available (was Re: GDAL 3.11.2 release candidate available)

A 3.11.2 RC2 with an extra bug fix for the gdallocationinfo regression that has just been reported: Pick up an archive among the following ones (by ascending size):   https://download.osgeo.org/gdal/3.11.2/gdal-3.11.2rc2.tar.xz   https://download.osgeo.org/gdal/3.11.2/gdal-3.11.2rc2.tar.gz   ht

Re: [gdal-dev] [External] : Re: Can GDAL driver be reused by GDAL python binding

Le 08/07/2025 à 23:15, Fengting Chen a écrit : Hi Even, Thanks for the helpful information. I understand that the connection pool can be stored in the driver instance and destroyed when the driver is destroyed. My question is that in the python environment, when is the individual driver cre

Re: [gdal-dev] gdallocationinfo issues, after 3.9.2

Please file a ticket, ideally with a dataset to reproduce Le 08/07/2025 à 20:55, Scott via gdal-dev a écrit : Say you have a file called raster.vrt. In that file are 15 tif's. 9 of those rasters don't have data (nodata) at the specified lon/lat: gdallocationinfo -geoloc -valonly -field_sep ","

[gdal-dev] GDAL 3.11.2 release candidate available

Hi, I have prepared a GDAL/OGR 3.11.2 release candidate (mostly triggered to fix a 3.11.0 regression regarding gdalwarp to COG) Pick up an archive among the following ones (by ascending size):   https://download.osgeo.org/gdal/3.11.2/gdal-3.11.2rc1.tar.xz   https://download.osgeo.org/gdal/3.1

Re: [gdal-dev] Clip by row / column

Hi, that should likely be a mode to add to gdal raster clip. Can you file an enhancement ticket about that? Even Le 08/07/2025 à 08:08, Stephane Goldstein via gdal-dev a écrit : Hi. I tried to use the gdal raster today to clip a raster by row and column as I used to do with gdal_translate -

Re: [gdal-dev] Can GDAL driver be reused by GDAL python binding

Hi, Connection pooling is an internal implementation driver of each driver. You have to be careful about multi-threaded use cases if you want to implement that though. The PostGISRaster driver has some connection pooling. See PostGISRasterDriver::GetConnection() Even Le 07/07/2025 à 21:18,

Re: [gdal-dev] Issues with gdalwarp 3.11.1

Thanks for raising this. Fixed per https://github.com/OSGeo/gdal/pull/12722 . As that's a rather annoying regression, I'll likely issue a 3.11.2 RC tomorrow Even Le 07/07/2025 à 18:51, Scott via gdal-dev a écrit : Using GDAL 3.11.1 on Debian 12 proj 9.1.1 and GDAL 3.11.1 on AWS Linux 2, proj

Re: [gdal-dev] Random Raster Driver

Would the next step be for me to prepare a PR based on this? yes I think so. Perhaps start small with just one distribution function, and once this initial PR is merged you can follow up with other ones -- http://www.spatialys.com My software is free, but my time generally not. __

Re: [gdal-dev] Proxy vs Real Driver in GDAL

- How to create a GDAL driver: https://gdal.org/en/stable/tutorials/raster_driver_tut.html - GDAL-GRASS plugin driver example: https://github.com/OSGeo/gdal-grass/ Le 07/07/2025 à 11:37, John Smith a écrit : Yeah I am after that kind of explanation. @Even Rouault via gdal-dev <mailto:gdal-

Re: [gdal-dev] Proxy vs Real Driver in GDAL

John, As stated in the intro, this RFC is mostly for *in-tree* drivers. If you develop an out-of-tree plugin that doesn't modify GDAL sources, then you can ignore it Even Le 07/07/2025 à 10:55, John Smith via gdal-dev a écrit : Hello Can anyone explain the concept of proxy driver and re

Re: [gdal-dev] Random Raster Driver

Alex, I am not sure if I understand your suggestion correctly. Are you suggesting to change the behaviour or VRT DerivedRasterBand in general so that its IRasterIO would only work on block boundaries? That seems quite drastic to me. No, my suggestion was to do that only when one of the rand

Re: [gdal-dev] Random Raster Driver

Alex, I'm not super familiar myself with the usage of such random rasters, but it seems to be fairly common indeed in GIS software, and could likely make sense within GDAL too. I'm wondering if instead of having a new driver, the random distribution functions could not be exposed as VRT C++

Re: [gdal-dev] strange wkt recognition

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

Re: [gdal-dev] array dim permute

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

Re: [gdal-dev] Possible to issue sqlite3_limit with "memory" OGR driver?

Jesse, Maybe you use SQL with the SQLite dialect? Otherwise we lack context to tell why you get SQLite kicking it. I don't think sqlite3_limit() would really help you here, givenit can be used to grow settings beyond the compile time default which is 1 GiB I believe ("Attempts to increase a

[gdal-dev] GDAL 3.11.1 is released

Hi, On behalf of the GDAL/OGR development team, I am pleased to announce the release of the GDAL/OGR 3.11.1 bug fix version. Consult the release notes for the list of issues addressed:     https://github.com/OSGeo/gdal/blob/v3.11.1/NEWS.md The sources are available at:     https://download.o

Re: [gdal-dev] Motion: approve GDAL 3.11.1RC2 as final release

Passed with +1 from PSC members TamasS, JukkaR, MichaelS, JavierJS and me Le 27/06/2025 à 11:00, Even Rouault via gdal-dev a écrit : Hi, starting with my +1 Even -- http://www.spatialys.com My software is free, but my time generally not. ___ gdal

Re: [gdal-dev] GDALOpenEx() not failing silently

s say Verbose error: GDAL_OF_VERBOSE_ERROR. If set, a failed attempt to open the file will lead to an error message to be reported. When it is not set (the case here) it should not need this “extra care”, no? *From:*Even Rouault *Sent:* Sunday, June 29, 2025 8:24 PM *To:* Joaquim Manuel Freire Luís ; gdal

Re: [gdal-dev] GDALOpenEx() not failing silently

Hi, you can surround the call to GDALOpenEx() with CPLPushErrorHandler(CPLQuietErrorHandler); ... GDALOpenEx() here ... CPLPopErrorHandler(); Le 29/06/2025 à 21:20, Joaquim Manuel Freire Luís via gdal-dev a écrit : Hi, Again the Julia wrapper. In it to find if a file holds a raster or a v

Re: [gdal-dev] Building GDAL from VCPKG fails with FreeXL

Martin, what error messages did you get when trying with FreeXL ? Removing the FreeXL dependency removes support for the old prior-to-Excel-2007 binary XLS format. So usually not a big deal Even Le 29/06/2025 à 02:45, Martin Chapman via gdal-dev a écrit : All, I tried to build GDAL 3.11.0

[gdal-dev] Motion: approve GDAL 3.11.1RC2 as final release

Hi, starting with my +1 Even -- http://www.spatialys.com My software is free, but my time generally not. ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev

Re: [gdal-dev] Odd date conversion from geojson file in OGR - rounding up to invalid value

Le 27/06/2025 à 00:58, Andrew C Aitchison via gdal-dev a écrit : On Thu, 26 Jun 2025, Smith, Michael ERDC-RDE-CRREL-NH CIV via gdal-dev wrote: I have a geojson file that has a date field that is: "AOI_TASKING_DATE_END": "2025-11-30T23:59:59.99Z", Gdal vector info is reporting this as:  A

Re: [gdal-dev] Odd date conversion from geojson file in OGR - rounding up to invalid value

Fixed per https://github.com/OSGeo/gdal/pull/12658 Le 26/06/2025 à 22:57, Smith, Michael ERDC-RDE-CRREL-NH CIV via gdal-dev a écrit : I have a geojson file that has a date field that is: "AOI_TASKING_DATE_END": "2025-11-30T23:59:59.99Z", Gdal vector info is reporting this as:   AOI_TASK

Re: [gdal-dev] ERDAS ECW/JPEG2000 SDK 6.1

There's a pull request at https://github.com/OSGeo/gdal/pull/11593 that should bring support for 6.0 SDK and is waiting for its release Le 26/06/2025 à 16:03, Reynolds, Scott via gdal-dev a écrit : I understand the ERDAS will be releasing version 6.1 of the ECW/JPEG2000 SDK “soon” which elimi

[gdal-dev] 3.11.1 RC2 is available (was Re: GDAL 3.11.1 release candidate available)

Hi, here's a RC2 mostly to fix a small memory leak in some excutions of gdalinfo -json that went into RC1, and with some extra bonus while we are it Sources:  - https://download.osgeo.org/gdal/3.11.1/gdal-3.11.1rc2.tar.xz  - https://download.osgeo.org/gdal/3.11.1/gdal-3.11.1rc2.tar.gz  - https

Re: [gdal-dev] Read a /vsigzip/ csv.gz all at once

Hi, I don't know anything about Julia but I'd suspect that there must be something particularly slow in the way it interacts with C. For comparison,  "time python3 swig/python/gdal-utils/osgeo_utils/samples/ogrinfo.py /vsigzip//vsicurl/https://bulk.meteostat.net/v2/hourly/2022/08554.csv.gz -

[gdal-dev] GDAL 3.11.1 release candidate available

Hi, I have prepared a GDAL/OGR 3.11.1 release candidate. Pick up an archive among the following ones (by ascending size):   https://download.osgeo.org/gdal/3.11.1/gdal-3.11.1rc1.tar.xz   https://download.osgeo.org/gdal/3.11.1/gdal-3.11.1rc1.tar.gz   https://download.osgeo.org/gdal/3.11.1/gdal31

Re: [gdal-dev] gdalinfo -stats on Int64 raster: confusing warning

Answering your 4 emails at once: What’s the purpose of including the band number in the |gdalinfo| JSON output? Since the |"bands"| key is a list, the band number is already implied by the index. Doesn’t this make the explicit band number redundant? Kind of, but not really. Given that JSON b

Re: [gdal-dev] gdal 3.11 autocompletion in zsh

Hi, I've queued fixes to make it work: https://github.com/OSGeo/gdal/pull/12615 Even Le 20/06/2025 à 08:58, Stephane Goldstein via gdal-dev a écrit : I’m running zsh on Arch Linux and I can’t get the new autocompletions for gdal 3.11 working. I added the below to my |.zshrc|. Any help is ap

Re: [gdal-dev] Note on Xerces

Hi Nicklas, Thanks for the head up. yes I'm aware that almost nobody maintains Xerces-C anymore.  Regarding the Interlis & NAS drivers, they could certainly be moved to using expat instead (with some effort...). The GMLAS driver cannot however. It strongly relies on unique capabilities of Xer

Re: [gdal-dev] Out of tree drivers

Norman, Now GDAL supports plugins, It has supported them since its early beginnings. The recent improvements were for faster loading of in-tree drivers built as plugins are there any out of tree open source drivers? https://github.com/OSGeo/gdal-grass I am looking for a template for a d

Re: [gdal-dev] [PROPOSAL] Add CADRG write support via RPFTOC/NITF drivers

Hi Patrick, It feels a bit strange that write support for CADRG is needed in 2025, but besides that, your proposal sounds solid as far as I remember the details of those formats. I guess the most interesting part will be write support for vector quantization to figure out the VQ LUT that min

Re: [gdal-dev] vat.dbf is not listed by gdalinfo

Now fixed Le 07/06/2025 à 13:58, Denis Rykov via gdal-dev a écrit : Hi, When a GeoTIFF has an associated auxiliary |*.aux.xml| file, running |gdalinfo| lists both the TIFF and the XML file: |$ gdalinfo test.tif Driver: GTiff/GeoTIFF Files: test.tif test.tif.aux.xml | However, if there's

Re: [gdal-dev] GDAL CLI Modernization Webinar June 3rd at 1400 UTC

Hi The webinar took place yesterday. We have had up to 265 attendees. For those who couldn't attend, you'll find the following artifacts: - slide deck, augmented with the content of the Q&A session during the webinar: https://download.osgeo.org/gdal/presentations/GDAL%20CLI%20Modernization.p

Re: [gdal-dev] Java bindings to gdal/ogr - looking for more developer documentation

Le 30/05/2025 à 23:39, Tom Moore a écrit : Hi Even I just wanted to update you and provide a record for posterity with the results of me playing around with gdal/java and resource management. It appears to me that Dataset objects should not be closed from Java client code.  If you do then o

Re: [gdal-dev] Java bindings to gdal/ogr - looking for more developer documentation

My program is interactive and potentially long-lived, and the user interface can be used to open layers at different times. If I miss closing a Dataset will the garbage collector eventually take care of this? If it is no longer referenced by a Java variable, yes it should in theory (depend

Re: [gdal-dev] Java bindings to gdal/ogr - looking for more developer documentation

Hi, In particular I would like to know more about object life cycles and memory management: What kind of object management is the client program responsible for? Normally none, but you may want to explicitly call .Close() on datasets to ensure the underlying file is closed at the appropriat

Re: [gdal-dev] libgdal.so.36 not found by QGIS -

Looks like an issue with your package manager (or your use of it) where the QGIS version links to an older version of GDAL (libgdal.so.36 is GDAL 3.10.x) than the one you've installed. Definitely not a upstream GDAL or QGIS issue. Sorry for not being more helpful: I'm not familiar at all with M

Re: [gdal-dev] Black artifacts with JPEG compression

Am I overlooking something in my process? No, you're just hitting a fundamental limitation of JPEG compresson Do you have any ideas on how I can get rid of the artifacts while still keeping disk usage low? Use lossy WEBP compression that fully supports transparency. -- http://www.spatialys.

Re: [gdal-dev] NODATA values in diferents bands in a DataSet

Le 21/05/2025 à 20:53, Abel Pau a écrit : Okay, thanks! So the interpretation we are aiming for is option *a)*: Each band is treated independently, and each one has its own NODATA value. The NODATA value of one band is unrelated to that of the others. That said, the question is whether this beh

Re: [gdal-dev] NODATA values in diferents bands in a DataSet

Abel, there is a subtelty: a) If bands may have invalid pixels at different locations on different bands, and that those bands have a different nodata value, then using GDALRasterBand::SetNoDataValue() is the way to go. b) If a given pixel is invalid only if its value on all bands matches

Re: [gdal-dev] raster reproject fails without error message with GCP_HOMOGRAPHY option

Mia, please file an issue at https://github.com/OSGeo/gdal/issues with the source dataset + command line to reproduce Even Le 21/05/2025 à 14:56, Schumacher, Mia via gdal-dev a écrit : Dear gdal community, I hope this is the right spot to ask questions? I am trying to use new gdal raster

Re: [gdal-dev] float16 woes on solaris

Greg, HAVE_STD_FLOAT16_T tests only the C++ part of Float16 support. Later in the log I can see: -- Performing Test HAVE__FLOAT16 -- Performing Test HAVE__FLOAT16 - Success which is this test in cmake/helpers/configure.cmake # Check whether the type `_Float16` exists, and whether type # con

Re: [gdal-dev] tmp files writing to object storage

Michael, I couldn't reproduce your error (the temp file gets deleted for me), but the creation of a temporary file on /vsis3/ was certainly a bug. I've addressed this per https://github.com/OSGeo/gdal/pull/12421 Even Le 20/05/2025 à 02:38, Michael Sumner via gdal-dev a écrit : When I write a

Re: [gdal-dev] libgdal.so.36 refers to sqlite library with full path

Maybe another library that GDAL is depending on is linked against the system sqlite3 and not your custom build ? That could be PROJ typically Le 14/05/2025 à 22:58, Fengting Chen via gdal-dev a écrit : Hi, I am trying to build GDAL 3.10.3 with sqlite 3.49.2. The build was successful on linux.

Re: [gdal-dev] RFCs

Hi Andrew, Can you be more specific about which RFCs ?  Quick grep shows RFC9 superseded per RFC83 and RFC68 superseded per RFC98. If that can help, we could potentially keep in master a mostly empty document for superseded RFCs that would contain just a link to the new RFC and a link to the

Re: [gdal-dev] GDAL 3.11.0 "Eganville" is released

Hi, quick update: - GDAL in conda-forge channel has just been updated to 3.11.0 - Docker images of 3.11.0 are available: https://github.com/OSGeo/gdal/tree/master/docker#images-of-releases Even Le 09/05/2025 à 18:34, Even Rouault via gdal-dev a écrit : Hi, On behalf of the GDAL/OGR

Re: [gdal-dev] I cannot clean overviews from GeoTIFF

Fix in https://github.com/OSGeo/gdal/pull/12351 You can workaround the issue by adding -oo IGNORE_COG_LAYOUT_BREAK=YES (actually not needed for cleaning as this doesn't break the layout, but definitely needed for adding to a COG) Le 12/05/2025 à 12:01, Javier Jimenez Shaw via gdal-dev a écrit

Re: [gdal-dev] GDAL 3.11 broke part of the Julia wrapper

Le 12/05/2025 à 01:04, Joaquim Manuel Freire Luís via gdal-dev a écrit : Hi, I’m afraid this one is not going to be easy, and I don’t know how much help I can provide to find the issue. The think is that https://github.com/OSGeo/gdal/pull/12124 (which is a very big PR) broke my Julia wrappe

Re: [gdal-dev] replacing a dataset in C++

Le 11/05/2025 à 00:20, Michael Sumner via gdal-dev a écrit : Hello, I have a question about safely re-casting a dataset to another, I want to use Multidim to re-orient an MDArray as a classic 2D raster. I was a bit surprised that this works (I just overwrite poSrcDS with the classic form): I

[gdal-dev] GDAL 3.11.0 "Eganville" is released

Hi, On behalf of the GDAL/OGR development team and community, I am pleased to announce the release of GDAL/OGR 3.11.0. GDAL/OGR is a C++ geospatial data access library for raster and vector file formats, databases and web services. It includes bindings for several languages, and a variety of

Re: [gdal-dev] Motion: approve GDAL 3.11.0RC2 as final release

Approved with +1 from PSC members JavierJS, MikeS, KurtS, HowardB, JukkaR, DanB and me. Le 07/05/2025 à 17:53, Even Rouault via gdal-dev a écrit : +1 Even -- http://www.spatialys.com My software is free, but my time generally not. ___ gdal-dev

Re: [gdal-dev] HFA (.img) driver prints Warning 1: NaN converted to INT_MAX when float raster has nan as the NoData value

: Perjantai 9. toukokuuta 2025 2.04 Vastaanottaja: Even Rouault; gdal dev Aihe: Re: [gdal-dev] HFA (.img) driver prints Warning 1: NaN converted to INT_MAX when float raster has nan as the NoData value Thank you. I can help you repro it if you want to take a look.I'm having trouble attaching a .img

Re: [gdal-dev] HFA (.img) driver prints Warning 1: NaN converted to INT_MAX when float raster has nan as the NoData value

17:51, Even Rouault wrote: Jason, It looks like something in the code asks a float64 field to be returned as a int32, and thus NaN has to be turned into something else. That's perhaps fine in the context where that happens with your file and could potentially be silenced, but access t

Re: [gdal-dev] vsicurl and --range byte-range

Joaquim, You can combine /vsisubfile/ (https://gdal.org/en/stable/user/virtual_file_systems.html#vsisubfile-portions-of-files) and /vsicurl/ /vsisubfile/${offset}_${length}/vsicurl/${url} e.g. $ gdalinfo /vsisubfile/802533_508958,/vsicurl/https://ecmwf-forecasts.s3.eu-central-1.amazonaws.c

Re: [gdal-dev] HFA (.img) driver prints Warning 1: NaN converted to INT_MAX when float raster has nan as the NoData value

Jason, It looks like something in the code asks a float64 field to be returned as a int32, and thus NaN has to be turned into something else. That's perhaps fine in the context where that happens with your file and could potentially be silenced, but access to the file would be needed to inves

Re: [gdal-dev] GDAL 3.10.3 build questions regarding to CURL and ARROW

Le 08/05/2025 à 19:15, Fengting Chen via gdal-dev a écrit : I have a couple questions regarding to building GDAL 3.10.3: 1. Error about CURL: Could NOT find CURL: Found unsuitable version "7.61.1", but required is at   least "7.68" (found /usr/lib64/libcurl.so, ) Any reason that curl 7.68

[gdal-dev] Motion: approve GDAL 3.11.0RC2 as final release

+1 Even -- http://www.spatialys.com My software is free, but my time generally not. ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev

Re: [gdal-dev] Compoundcurve to DXF

Le 07/05/2025 à 15:11, Jan Heckman via gdal-dev a écrit : Hi Jukka, You are right, excuses. My question was a bit rhetorical, though. Will you please answer the 2nd question too? I get the impression that there is no intention yet to convert curves to DXF arcs. I hope you change your mind, you

[gdal-dev] GDAL 3.11.0RC2 is available (Re: GDAL 3.11.0 release candidate available)

Hi, I've prepared a GDAL 3.11.0 RC2 Sources: -  https://download.osgeo.org/gdal/3.11.0/gdal-3.11.0rc2.tar.xz -  https://download.osgeo.org/gdal/3.11.0/gdal-3.11.0rc2.tar.gz -  https://download.osgeo.org/gdal/3.11.0/gdal3110rc2.zip Autotest suite: - https://download.osgeo.org/gdal/3.11.0/gdalau

Re: [gdal-dev] GDAL 3.11.0 release candidate available

Bas, can you give a try at https://github.com/OSGeo/gdal/pull/12275 ? Even Le 05/05/2025 à 21:02, Sebastiaan Couwenberg via gdal-dev a écrit : On 5/5/25 5:27 PM, Even Rouault via gdal-dev wrote: * Add 'gdal raster tile' (port of gdal2tiles) This seems to have caused breaka

Re: [gdal-dev] GDAL 3.11.0 release candidate available

and the release/3.11 branch has now been created.  master is open for 3.12dev -- http://www.spatialys.com My software is free, but my time generally not. ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-

[gdal-dev] GDAL 3.11.0 release candidate available

Hi, I have prepared a GDAL/OGR 3.11.0 release candidate. I'll call for a vote promoting it later this week if no serious problems are reported before. NEWS at:   https://github.com/OSGeo/gdal/blob/v3.11.0RC1/NEWS.md Pick up an archive among the following ones (by ascending size):   https://d

Re: [gdal-dev] OSX Dev Build

Andrew, check the output of "otool -L /Users/abell/gdal/build/swig/python/osgeo/_gdal.cpython-313-darwin.so" to verify that it links against the libgdal.dylib you've built. M y assumption is that it links against an older version. The SONAME of libgdal has been bumped to 37 when 3.11beta1 has

Re: [gdal-dev] [External] : Re: Build failed with "cannot deduce template arguments" error

tion easier for the compiler. Le 30/04/2025 à 05:10, Fengting Chen a écrit : I am using “c++ (GCC) 8.5.0 20210514 (Red Hat 8.5.0-18.0.6)” which is supposed to support C++17. *From: *Even Rouault *Date: *Tuesday, April 29, 2025 at 6:10 PM *To: *Fengting Chen , gdal-dev@lists.osgeo.org *Subj

Re: [gdal-dev] gdal 3.11 -dsco vs --co

Fix submitted in https://github.com/OSGeo/gdal/pull/12230 Le 30/04/2025 à 08:22, Rahkonen Jukka via gdal-dev a écrit : Hi, Your syntax with the "gdal" frontend is correct. This command is accepted: gdal vector convert -f MVT --co NAME=foo in.shp out The reason for the error may be in the com

Re: [gdal-dev] Build failed with "cannot deduce template arguments" error

Which compiler and compiler version do you use ? It is likely it is too old and doesn't fully support C++17 Le 29/04/2025 à 23:18, Fengting Chen via gdal-dev a écrit : Hi, I am trying to build GDAL from the master branch, but got the following error: [ 46%] Building CXX object alg/CMakeFil

Re: [gdal-dev] GDAL 3.11.0 "Eganville" beta1 available for testing

One point I should probably underline for packagers is the following part of NEWS.md ## New optional dependencies * [muparser](https://github.com/beltoforion/muparser) is *strongly* recommended   to be added as a build and runtime dependency, to provide nominal support for   C++ VRT expressi

Re: [gdal-dev] GDAL 3.11.0 "Eganville" beta1 available for testing

Hi, The below mentioned Docker images are available, as well as the GDAL master Conda builds that have been restored after being broken last week. This was due to the update to SWIG 4.3.1 which requires a patch on our side (work around to a SWIG upstream reported bug) This SWIG 4.3.1 issue a

Re: [gdal-dev] GDAL 3.11.0 "Eganville" beta1 available for testing

I have a few remaining warnings, which I don't claim are new in 3.11, but they don't seem like incorrect warnings at first glance. The first file may also have missing std::, resulting in calling the C function abs rather than C++ std::abs, but that's still not float? No, std::abs() is fine there

Re: [gdal-dev] Motion: ReadTheDocs Financial Support

+1 Even Le 17/04/2025 à 18:39, Howard Butler via gdal-dev a écrit : Dear PSC, GDAL and PROJ depend upon ReadTheDocs for documentation generation and hosting. RTD does not charge for open source projects to host documentation. Projects can pay $60/yr to have ads removed, which we do, but we ca

Re: [gdal-dev] GDAL 3.11.0 "Eganville" beta1 available for testing

Le 18/04/2025 à 03:47, Scott via gdal-dev a écrit : On the following page: https://gdal.org/en/latest/programs/gdal_raster_calc.html#gdal-raster-calc-subcommand Example 3 at the very bottom has: gdal_calc -i fixed, thanks -- http://www.spatialys.com My software is free, but my time

Re: [gdal-dev] GDAL 3.11.0 "Eganville" beta1 available for testing

Greg, those errors are related to the new float16 (RFC100) support. Support for that type is a bit weak with some compilers / C/C++ libraries. Can you give a try at https://github.com/OSGeo/gdal/pull/12165 ? Even Le 18/04/2025 à 01:00, Greg Troxel via gdal-dev a écrit : Even Rouault via

[gdal-dev] GDAL 3.11.0 "Eganville" beta1 available for testing

Hi, I've prepared a beta1 of GDAL 3.11.0 to get feedback from early testers, for the following next 2 weeks before the release candidate. The NEWS file is here: https://github.com/OSGeo/gdal/blob/v3.11.0beta1/NEWS.md The biggest highlight is: * RFC 104

Re: [gdal-dev] Performance Issue with VRT Pixel Function and Large Number of Source Rasters

Thanks for the quick fix Even! *My only remaining concern is that the documentation lists SkipNonContributingSources under Python Pixel Functions, even though it applies to both C++ and Python Pixel Functions. Shouldn't it be elevated to be mentioned more generically under Derived Band?*

Re: [gdal-dev] Performance Issue with VRT Pixel Function and Large Number of Source Rasters

Abdul, if you add true as a child element of the element, and apply patch https://github.com/OSGeo/gdal/commit/3dbc60b334ee022f2993dca476b08d5fed01698c , "gdal_translate -of GTiff merged.vrt OUTPUT.tif" completes in a few minutes Cf https://gdal.org/en/stable/drivers/raster/vrt.html#using

Re: [gdal-dev] STAC Geoparquet required fields - Inspecting one feature due to missing metadata items

Michael, file size isn't the issue here, it is more the symptom of the driver having to read one dataset to get on or metadata items it doesn't know, than something it really needs (getting the file size is just a side effect of opening a remote dataset) Looking at the code I presume it must

Re: [gdal-dev] Call for review on RFC 104: Adding a "gdal" front-end command line interface

Le 25/11/2024 à 10:21, Even Rouault via gdal-dev a écrit : Hi Rob, Is it worth reserving space for a future Git or Github-cli style plugin mechanism where third party tools can extend the `gdal` CLI? eg: `gdal raster from-contours` * `git foo` simply looks for internal code first

Re: [gdal-dev] GeoJSON with "id" in properties and SQLite dialect

Fix queued in https://github.com/OSGeo/gdal/pull/12104 Le 07/04/2025 à 22:43, Rahkonen Jukka via gdal-dev a écrit : Hi, I notised this question on gis.stackexchange https://gis.stackexchange.com/questions/491741/gdal-sqlite-no-such-table-when-id-in-properties I tried to make as simple as poss

[gdal-dev] GDAL 3.10.3 is released

Hi, On behalf of the GDAL/OGR development team, I am pleased to announce the release of the GDAL/OGR 3.10.3 bug fix version, likely the last one in the 3.10 series. Consult the release notes for the list of issues addressed:     https://github.com/OSGeo/gdal/blob/v3.10.3/NEWS.md The sources

Re: [gdal-dev] Motion: adopt GDAL 3.10.3RC1 as final 3.10.3 release

Motion passed with +1 from PSC members JavierJS, JukkaR and me Le 03/04/2025 à 11:25, Even Rouault via gdal-dev a écrit : Hi, Motion: adopt GDAL 3.10.3RC1 as final 3.10.3 release +1 Even -- http://www.spatialys.com My software is free, but my time generally not

Re: [gdal-dev] writing parquet to /vsiaz/ fails when chunked

The error is: URL_INFO_HEADER_OUT: PUT /bcfishpass/crossings.parquet?se=2025-04-05T05%3A19Z&sp=rwdl&sv=2022-11-02&sr=c&skoid=d80366e6-b960-4aad-b22e-879eb27768e8&sktid=8b76c303-01ec-40d5-8d9a-6c2f6d78dcd7&skt=2025-04-05T04%3A19%3A14Z&ske=2025-04-05T05%3A19%3A00Z&sks=b&skv=2022-11-02&sig=kZTkJQ0%

Re: [gdal-dev] Questions regarding phrasing in the documentation of `OCTTransformBounds`

Hi Florian, 1. Is the documentation correct that input data must be checked and not the output data, i.e. `out_xmax` etc.? No, you're right, the doc is actually incorrect. This must be the out_ variables. Fixed per https://github.com/OSGeo/gdal/commit/1a3f781304cd2856ec0438b2f773357907d7

Re: [gdal-dev] writing parquet to /vsiaz/ fails when chunked

Le 04/04/2025 à 20:40, Simon Norris via gdal-dev a écrit : Perhaps another hapless user question: Using ogr2ogr, I can write very small parquet files to /vsiaz//.parquet without issue. But with larger files (that ogr2ogr tries to write in chunks), Azure does not accept the first PUT request a

[gdal-dev] Motion: adopt GDAL 3.10.3RC1 as final 3.10.3 release

Hi, Motion: adopt GDAL 3.10.3RC1 as final 3.10.3 release +1 Even -- http://www.spatialys.com My software is free, but my time generally not. ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev

Re: [gdal-dev] Proposal for GDAL Driver: EOPF Zarr (Earth Observation Product Format)

and multi-band support. The skeleton is a starting point that will expand into a more complete EOPF driver in subsequent development stages. Thanks, Yuvraj ---- *From:* Even Rouault *Sent:* Tuesday, April 1, 2025 9:41 PM

Re: [gdal-dev] Proposal for GDAL Driver: EOPF Zarr (Earth Observation Product Format)

Hi Yuvraj, A few questions: - what is the maturity of the EOPF enhancements ? - where are they described ? (i.e. the format specification) - why not enhancing the existing Zarr driver ? - from what I can currently see in https://github.com/EOPF-Sample-Service/GDAL-ZARR-EOPF/tree/main/src,

[gdal-dev] GDAL 3.10.3 release candidate available

Hi, I have prepared a GDAL/OGR 3.10.3 release candidate. Pick up an archive among the following ones (by ascending size):   https://download.osgeo.org/gdal/3.10.3/gdal-3.10.3rc1.tar.xz   https://download.osgeo.org/gdal/3.10.3/gdal-3.10.3rc1.tar.gz   https://download.osgeo.org/gdal/3.10.3/gdal31

Re: [gdal-dev] Can we external libtiff and internal GeoTiff while building GDAL?

Can I do something to avoid the symbol clashes in Client setup while building the GDAL ? Nothing to do. GDAL automatically rename symbols when building with the internal libraries -- http://www.spatialys.com My software is free, but my time generally not. __

  1   2   3   4   5   6   7   8   9   10   >