[gdal-dev] "Thanks" page in our documentation

Hi, I feel we were missing a "thanks" page in our documentation. We had one in the static HTML version of the web site, prior to the migration to Sphinx, although it was already a bit outdated. Hence I'm proposing https://github.com/OSGeo/gdal/pull/10963 , partly based on the content of the p

Re: [gdal-dev] writing arrow geometry

Joris, The child name of the outer list should be “polygons”; the child name of the middle list should be “rings”; the child name of the inner list should be “vertices”. Thanks for pointing that out. Should be fixed per https://github.com/OSGeo/gdal/pull/10962 Even -- http://www.spatialys

Re: [gdal-dev] Proposed RFC 8 amendment regarding (prohibited use of) generative AI tools

Sounds good to me On Mon, 7 Oct 2024, 18:38 Even Rouault via gdal-dev, < gdal-dev@lists.osgeo.org> wrote: > Hi, > > I propose we update RFC 8 with the following changes: > https://github.com/OSGeo/gdal/pull/10958 > > Can we enforce that? No (similarly we can't prevent someone from > stealing copy

[gdal-dev] Proposed RFC 8 amendment regarding (prohibited use of) generative AI tools

Hi, I propose we update RFC 8 with the following changes: https://github.com/OSGeo/gdal/pull/10958 Can we enforce that? No (similarly we can't prevent someone from stealing copyrighted material from source code of proprietary software they have access to, or "re-license" or "forget" copyrigh

[gdal-dev] GDAL 3.9.3 release candidate available

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

Re: [gdal-dev] writing arrow geometry

Thanks Dewey! That does indeed fix it. ogr2ogr ~/fromgdal.arrows ogr/data/arrow/from_paleolimbot_geoarrow/polygon-default.ipc ## using *.arrows triggers same as -lco FORMAT=STREAM then in R nanoarrow::read_nanoarrow("~/fromgdal.arrows") >>}>> I had even toyed with the FORMAT=FILE/STREAM and

Re: [gdal-dev] gdal-dev Digest, Vol 245, Issue 7

HELP unsubscribe please On Sun, Oct 6, 2024 at 3:00 PM wrote: > Send gdal-dev mailing list submissions to > gdal-dev@lists.osgeo.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.osgeo.org/mailman/listinfo/gdal-dev > or, via email, send a message

Re: [gdal-dev] writing arrow geometry

The section about MultiPolygons at https://geoarrow.org/format.html#memory-layouts mentions: > The child name of the outer list should be “polygons”; the child name of the > middle list should be “rings”; the child name of the inner list should be > “vertices”. So this is currently phrased as a

Re: [gdal-dev] writing arrow geometry

Michael, my understanding of https://geoarrow.org/format.html#memory-layouts is that what writes OGR is supposed to be fine since they mentionned types like '|List[2]>>'|. Perhaps I've missed something or nanoarrow has stricter expectations? CC'ing Dewey Dunnington Even Le 07/10/2024 à 15:2

Re: [gdal-dev] writing arrow geometry

I realize I left out the INTERLEAVING, ie. ogr2ogr ~/fromgdal.arrow ogr/data/arrow/from_paleolimbot_geoarrow/polygon-default.ipc -lco GEOMETRY_ENCODING=GEOARROW_INTERLEAVED but still, I get these list>>}>> On Tue, Oct 8, 2024 at 12:19 AM Michael Sumner wrote: > When I investigate the schema

[gdal-dev] writing arrow geometry

When I investigate the schema in one of the test files ogr/data/arrow/from_paleolimbot_geoarrow/polygon-default.ipc I see expected listGetArrowStream and I get the same output: }>>}>> If I write a new .arrow with GDAL ogr2ogr ~/fromgdal.arrow ogr/data/arrow/from_paleolimbot_geoarrow/polygon-d

[gdal-dev] Build GDAL release/3.9 with HDF5

Hi I am trying to build GDAL from source from "release/3.9 branch". I am bit confused about the HDF5 flags i need to pass if i want to enable the HDF5 support and also build the HDF5 drivers. I am using following flags BUT i still keep getting errors shown next