Skip to content
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

Expose GDAL driver metadata #103

Open
jorisvandenbossche opened this issue May 14, 2022 · 6 comments
Open

Expose GDAL driver metadata #103

jorisvandenbossche opened this issue May 14, 2022 · 6 comments

Comments

@jorisvandenbossche
Copy link
Member

jorisvandenbossche commented May 14, 2022

Would we want something like this in fiona: Toblerity/Fiona#950 ?

It would allow to check the extension of a driver (and making the driver inference from the extension for writing more robust, cfr Toblerity/Fiona#948), the open options, whether the driver supports certain data types, etc (but it would probably be mostly copy/paste from fiona ..)

@theroggy
Copy link
Member

Sounds like it is at least somewhat linked to #81 and #71

@jorisvandenbossche
Copy link
Member Author

linked to #81

Yes, if we have this, it could indeed be used for #81. But I think it's also certainly fine to already do something about #81 without this feature (this issue is also meant for user facing API, while for the tests we can hard-code a bunch of things on the short term)

@theroggy
Copy link
Member

theroggy commented Jun 7, 2022

I wonder if it would be possible to get more driver metadata into gdal... as this metadata isn't python-specific, it would be way more elegant to have it there I think.

@jorisvandenbossche
Copy link
Member Author

jorisvandenbossche commented Jun 8, 2022

Which additional information are you thinking about? (the current GDAL metadata already exposes quite a lot: extensions, which data types are supported, whether nulls are supported, ..)

@theroggy
Copy link
Member

theroggy commented Jun 8, 2022

Which additional information are you thinking about? (the current GDAL metadata already exposes quite a lot: extensions, which data types are supported, whether nulls are supported, ..)

Ah, OK, then I misinterpreted what was in fiona. In that case, ignore my remark :-).

@jorisvandenbossche
Copy link
Member Author

I started using the GDAL driver metadata internally in #189, but without publicly exposing it for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants