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] 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] 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