Rafael Schouten

I wondered that too, they at least need "ambiguity" comments if so

I think it can be 50x faster, for linestrings anyway

We already did this for ArchGDAL for the same reason. We only need to be consistent with GeoInterface in GeoInterface methods. The idea is to do what your saying, but...

Its probably defined in the dataset itself, but gdal passes us `:geom` in `GeoInterface.geometrycolumns` so it can be called whatever they like. GADM.jl strips that information by converting the table...

But youre not returning the ArchGDAL table... thats where the problem comes from. If you did it would work, and would be ArchGDALs problem if it didnt. From my perspective,...

A fifth options is to leverage the new metadata interface for tables, and add the column name to metadata so it propagates everywhere. But its some serious work to implement...

ConstructionBaseExtras.jl is obsolete now that we have those extensions. So probably the problem is some package (maybe even one of mine like ModelParameters.jl ?) still depending on it, even just...

What is happening here... the yank was such an obvious quick fix to just merge, and now we have chaos instead: https://github.com/yeesian/ArchGDAL.jl/actions/runs/8969588301/job/24631262216?pr=423 (is the idea that instead we just cut...

But isn't that what your change does? wont there be no version of julia where 0.4.0 can be added? If so, what version will it work on?

Ahh right there always needs to be a version change in two places, not just the one, or there is a conflict. The example link goes to the file without...