-
Notifications
You must be signed in to change notification settings - Fork 16
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 opening vector datasets with GDALOpenEx #82
Comments
Loam relies on It looks like GDAL has built-in support for read-only GDB access, for vector data only, but not raster data. Does that satisfy your use-case? There is also a read-write GDB driver available for GDAL, but it requires an external library, so it would be necessary to create a custom build of If you need raster data, it seems like you're out of luck, unfortunately -- GDAL doesn't support reading or writing raster data in GDB files. I hope that helps! |
Thanks for the quick response. Yeah I'm looking for read-only vector data with GDB files. Would this question be more appropriate for |
Just one more question, in case I do manage to build |
If all you're looking for is read-only vector data, I think OpenFileGDB driver should already be compiled into If you haven't tried using a GDB file yet, an easy way to test would be to clone the repo, check out the
You might need to pass the location of your custom In general most of the Loam functionality uses GDAL API functions pretty directly, so if you would expect something to work using |
Ok, I did try using a zipped gdb archive and encountered this error:
Thanks again for responsiveness. |
I also tried |
Oh, I see what's going on -- Loam wraps the I would expect Loam to exhibit the same behavior as
But
This is the second request that I've had for wrappers for the OGR API, so that makes me want to prioritize it. Could you give me some more information about what you would want to do with the dataset once it has been opened? Wrapping Secondly, I think that either way, a |
I want to open a gdal file get field definitions, iterate through records, render on a map. I'm not sure about other tools but opening the file from C API works well with zipped gdb or shp files. Just want to clarify, will writing my own worker for gdal-js work for my use case. Or if you want I could take a look into implementing wrapper in loam (although I'll need some guidance for that). Thanks |
Hmm, interesting. Which C API function are you using to do that, and what version of GDAL are you using?
If you're comfortable writing C and you only need to do that one thing, then the gdal-js path might be easiest. You'd need to:
|
I'm using Thanks for the instructions, I'll check out how to add those functions. |
Ah, okay, you might not need to add any new functions to |
I'll create a PR with some additional functions needed for working with vector features. Can you give me a permission to push to a branch? |
I'd suggest creating a fork -- then you'll be able to push to a branch on the forked repo and make a PR to the upstream repo from your forked copy. Looking forward to seeing it! |
I'd like to know if there are any plans to support reading/writing GDB files?
Also are there some limitations that would prevent implementing this functionality?
The text was updated successfully, but these errors were encountered: