-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support DataAPI metadata as GeoInterface name agreements #77
Comments
Yeah, I've thought about this when I implemented it in GeoDataFrames, but it's actually a bit complex.
|
Yeah namespacing is an issue. @bkamins is there a standard way of namespacing metadata for DataAPI? We could prefix it with "GeoInterface_" or something? |
We thought about it, but decided we can add a standard later after some experience with it. I understand this metadata will mostly not be accessed by the user directly, but rather programmatically via API. Is this right? Apache Arrow has the following standard: https://arrow.apache.org/docs/format/Columnar.html#extension-types.
|
Yes its mostly for programatic use.
|
I started an implementation of this in evetion/GeoDataFrames.jl#70. That being said, it does seem like GeoInterface would need to take on Tables.jl and DataAPI.jl as dependencies - is this something that we can do here? Package extensions would be pretty annoying given the need to support older versions of Julia, even if we do use an |
The next step here is to have GeoInterface natively figure this stuff out - a direct dependency on DataAPI shouldn't be too bad, it's 500 lines of function stubs and documentation. |
A package extension can work, 1.10 will be LTS very soon from what I gathered. |
How would that work, though? Just defining |
I was merely answering your
I haven't thought out the design just yet, but it would be good to document our "reserved" namespace and keys already. |
It's very cool that storing geometry column name metadata like this works:
evetion/GeoDataFrames.jl#47
I just realised it should also work in Rasters.jl, and probably lots of other places. Maybe we can we state that "crs" and "geometrycolumns" are our blessed metadata keys somewhere in the GeoInterface.jl docs, then we can use them everywhere and GeoDataFrames.jl will already be compliant.
The text was updated successfully, but these errors were encountered: