Martijn Visser

I don't really understand. LINEARRING is a non-standard extension of WKT that several projects support. It basically is a closed LINESTRING. The `OGRwkbGeometryType` has both `wkbLineString` and `wkbLinearRing`. GDAL seems...

It seems never, based on this comment: ```cpp wkbLinearRing = 101, /**< non-standard, just for createGeometry() */ ``` From https://github.com/OSGeo/gdal/blob/v3.5.1/ogr/ogr_core.h#L401

GDAL.jl 1.4 comes with GDAL 3.5.0

Yeah although the current Tables interface for ArchGDAL is already row based, since that corresponds to GDAL's data model better.

This trick of using a MEMORY dataset seems to be needed quite often. I guess in this case it was the `"CreateGeomField"` capability? Perhaps it's good to reopen this issue...

One thing that comes to mind is to regenerate the GDAL.jl wrapper with the rewritten Clang.jl, and see what effect that has.

It only affects the tests, so I'd say no. I just tried running the GDAL Clang wrapper, and it's quite different, and smarter as well. We can probably turn off...

> But if I uncomment the #AG.getband(dataset, 1) line then GDAL crashes This works fine, it shows the band and then shows 1. ```julia band = AG.getband(dataset, 1) @show band...

Although as far as I see this usage can only really be an error, it's probably not a great user experience to get a segfault that kills the session. Reopening...

Yes I think keyword arguments would probably be the nicest looking. One thing I wonder about for keywords, does it ever become problematic, them mixing with the existing keywords? Right...