-
Notifications
You must be signed in to change notification settings - Fork 27
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
introduce a vector dataset writer #315
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just leaving some thoughts while it's a draft, thank you for digging into it!
Seems like some tests are still failing on mac and windows, maybe I have to remove some drivers from the test and rewrite the test a bit. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I really appreciate the effort here.
In case it's lost among the comments: just wanted to make it clear that I think a single write
function that "does the right thing" (i.e. writes to file the way a GDAL user would like to) is my preferred approach here. I haven't seen a compelling reason to have separate writerasters
and writevectors
function.
I just removed the |
I just got the tests on windows to pass. The failing tests on mac look unrelated. |
yeesian/ArchGDAL.jl#315 (comment) ``` ERROR: LoadError: LoadError: InitError: could not load library "/Users/runner/.julia/artifacts/525a7050baaa2b0732225f4528525dfb3cfed1df/lib/libproj.25.dylib" dlopen(/Users/runner/.julia/artifacts/525a7050baaa2b0732225f4528525dfb3cfed1df/lib/libproj.25.dylib, 1): Library not loaded: @rpath/libcurl.4.dylib Referenced from: /Users/runner/.julia/artifacts/525a7050baaa2b0732225f4528525dfb3cfed1df/lib/libproj.25.9.0.1.dylib Reason: Incompatible library version: libproj.25.dylib requires version 13.0.0 or later, but libcurl.4.dylib provides version 12.0.0 ```
Ok next round. I improved the GPKG workaround, restored the old definition of |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you so much, this is looking close to ready for merge!
I still have some reservations about the approach for GPKG but I might be convinced that this is a strict improvement over the current state of things and just need some time to develop confidence in the correctness of the GPKG workaround (via comparison with other compatibly-licensed GDAL packages).
I just switched the default of |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM once the remaining comments are addressed.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you so much for pushing through on this!
Has been a pleasure! Thanks for the comments and let's see where this takes us :) |
Hi! Here comes the vector dataset writer. It still is far from perfect and needs tests, but you can already take a look.