-
Notifications
You must be signed in to change notification settings - Fork 603
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
feat(api): add to_geo
methods for writing geospatial output
#10299
Conversation
ACTION NEEDED Ibis follows the Conventional Commits specification for release automation. The PR title and description are used as the merge commit message. Please update your PR title and description to match the specification. |
to_geo
methods for writing geospatial output
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.
That windows exception is going to be hilarious to track down. I wonder which format is causing it to barf?
Overall I think this looks good -- should probably have a docstring with a link to the DuckDB geospatial page that lists all of the output options (and their names)
DuckDB 1.1.2 was just released today (and I've merged a PR to update our lockfile to test against it). Let's see if that helps windows. |
fa590fb
to
1147168
Compare
74e8dba
to
42fa4a0
Compare
Well, it turns out that it's the WAsP format, and I don't know why it crashes, so I just |
bd252f0
to
dabd418
Compare
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.
🎉 🎉 |
Adds an experimental
to_geo
method to the duckdb backend.Closes #10296.