-
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
docs(blog): ibis, duckdb and lonboard for overture maps #10143
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. |
Bug fix release is scheduled for monday if everything goes as planned! |
Thanks @Maxxen that would be awesome. If you are interested in being part of the blog too, I'd be happy to get include a paragraph or something related to the duckdb geoparquet support that you added and list you as a co-author. At the moment is a very rough draft, but I'll leave the invitation open in case you are interested. |
``` | ||
|
||
## Motivation | ||
|
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'd start with a sentence intro about what Overture Maps is. Like
Overture Maps is a project to build map data products on top of a variety of sources, like OpenStreetMap.
(not sure that's the best one-liner description of what Overture Maps is, any zingers @jwass ?)
plants_CA = plants.filter(_.bbox.xmin.between(-118.6, -117.9), | ||
_.bbox.ymin.between(34.5, 35.3))[_.names.primary, _.geometry] |
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.
Nit: I'd suggest using standard black/ruff code formatting for all Python code blocks
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.
Good catch, I'll fix this.
and that's how you can visualize ~7 million points from the comfort of | ||
your laptop. | ||
|
||
Note: I got the ~7M by adding the number of points in power_lines and minor_lines. I'm not sure if plotting the lines that connect these points add points to this. |
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.
It is more effort for the GPU to render lines than to render points, but a line isn't rendered as a collection of points.
It might be clearer to say 7 million coordinates
rather than points.
Co-authored-by: Kyle Barron <[email protected]>
duckdb 1.1.1 is going out on Monday, I'll revisit changes, cleanup code and update text accordingly once the release is out. |
…ject#10072) Co-authored-by: Phillip Cloud <[email protected]>
Co-authored-by: Phillip Cloud <[email protected]>
## Description of changes Simplifying the previous implementation from `sge.Case(ifs...)` per ibis-project#10060 (comment).
Co-authored-by: Guilherme Martins Crocetti <[email protected]>
Oh no, I have no clue what git shenanigans happen that this got so messed up. I will close this in favor of a new one. |
closing in favor of #10215 Apologies for the mess, no clue what happened. |
This is still a draft, there are a few comments and things to decide
to_parquet
geoparquet files, there is a PR open to fix this Fix data race when writing GeoParquet duckdb/duckdb#13962, not sure if there will be a bug fix release or if we will encourage downloading the nightly when it goes out.html
file gets huge to host.