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

2025-07-24 Thread Erik Schnetter via gdal-dev
error not being transmitted up to > the caller > > Even > > Le 19/07/2025 à 17:44, Erik Schnetter via gdal-dev a écrit : >> I am using GDAL to create a multidimensional zarr file that is sozip >> compressed. I see this error when creating the file: >> >> ERROR

[gdal-dev] Errors while creating sozip zarr file

2025-07-19 Thread Erik Schnetter via gdal-dev
I am using GDAL to create a multidimensional zarr file that is sozip compressed. I see this error when creating the file: ERROR 1: dish_positions..zarr/zarr.json already exists in ZIP file ERROR 8: Open file /vsizip/data/fengine_init_pathfinder/cx66_dish_positions..zarr.zip/dish_

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

2025-06-24 Thread Erik Schnetter via gdal-dev
t what Eric said, here’s the ‘getfield’ function (This code was > taken from ArchGDAL so we are talking of the same thing) > > https://github.com/GenericMappingTools/GMT.jl/blob/master/src/gdal.jl#L2161 > > From: gdal-dev <mailto:gdal-dev-boun...@lists.osgeo.org>> On Behalf

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

2025-06-24 Thread Erik Schnetter via gdal-dev
The Julia wrapper (ArchGDAL.jl) for `getfield` calls `OGR_FD_GetFieldDefn` and several related function (to get the type of the field etc.). Are these possibly expensive operations in GDAL? Any C function in GDAL can easily be called from Julia. Which C function would get all fields at once? I

Re: [gdal-dev] CSharp bindings queued for removal (was Re: GDAL CSharp bindings maintainers/contributors listening... ?)

2025-01-31 Thread Erik Schnetter via gdal-dev
For what it's worth, the Julia bindings to GDAL live in an independent repository at https://github.com/JuliaGeo/GDAL.jl and are based on the current GDAL C bindings. There is quite a bit of low-level wrangling necessary to make this work, and GDAL.jl uses Julia-specific tools for this. This is

[gdal-dev] Motion: adopt RFC 100: Add support for the float16 data type

2024-11-07 Thread Erik Schnetter via gdal-dev
I move to adopt RFC 100 (adding support for the float16 data type). The pull request for RFC 100 is here: https://github.com/OSGeo/gdal/pull/10146 . A candidate implementation is here: https://github.com/OSGeo/gdal/pull/11180 . I vote +1. -erik ___ g

[gdal-dev] Call for discussion on RFC 100: Adding Float16 support to GDAL

2024-11-05 Thread Erik Schnetter via gdal-dev
I am interested in GDAL supporting float16 values. My RFC 100 can be viewed here: https://github.com/OSGeo/gdal/issues/10144 . I have also created a candidate implementation that is available at https://github.com/OSGeo/gdal/pull/11180 . I am looking for last comments before I will ask for a vo

[gdal-dev] Adding float16 support to GDAL

2024-06-06 Thread Erik Schnetter via gdal-dev
I am interested in GDAL supporting float16 values (i.e. IEEE 16-bit floating point values) natively. If this suggestion succeeds I will most likely be able to provide such an implementation. I have prepared a draft RFC for this, available as a pull request at