-
-
Notifications
You must be signed in to change notification settings - Fork 36
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
Splitting multipolygons by 180th meridian #90
Splitting multipolygons by 180th meridian #90
Conversation
This looks great! And thanks for adding I ended up removing flags in favor of GUC variables. Furthermore, based on input from @Komzpa in #79 (review), I figured it was best to always split the PostGIS types (including the raw WKB). Could you update the PR to not include the boolean flag, and always split? |
Updated. |
Thank you for the contribution! |
@zachasme I'm also going to add aggregate versions of geometry/geography functions. Now that they don't have a second argument no C code is required to pass it. |
Interesting, I have not yet worked with aggregate functions. Would that be similar to |
Yes, similar to
This allows to apply
Aggregate functions could be added for |
Adds
h3_cells_to_multi_polygon_wkb
function (and PostGIS wrappers) that allows to split multipoligons returned bycellsToLinkedMultiPolygon
by 180th meridian.Standalone tool using the same algorithm: https://github.com/konturio/h3-split
I noticed that a boolean flag has been removed for
h3_cell_to_boundary_wkb
, but WKB version ofh3_cells_to_multi_polygon
also greatly simplifies the interface, so maybe it's better to keep the flag in case the user doesn't need to split?Non-convex polygon with holes:
Polygon at North Pole: