Fix tile-filling polygon artifacts by upgrading to DuckDB 1.4.2 #1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
includes a fix for a bug in ST_AsMVTGeom that caused polygons crossing tile boundaries to render as full-tile rectangles
Owner
|
Thanks a lot @onlyjsmith! Merged, and the new |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
(Thanks for the great tool!)
Summary
Upgrades DuckDB Go bindings to v0.1.23 (DuckDB 1.4.2) which includes a fix for a bug in ST_AsMVTGeom that caused polygons crossing tile boundaries to render as full-tile rectangles.
Problem
Polygons that crossed tile boundaries were incorrectly rendered as rectangles filling the entire tile
(4608×4608 units including buffer). This caused:
Root Cause
DuckDB Spatial's ST_AsMVTGeom was normalizing polygon winding order before clipping to tile boundaries. Since clipping can alter winding order, this produced invalid/inverted polygons. Fixed in duckdb/duckdb-spatial#700.
AI disclosure
I had help from Claude in locating the bug and implementing the fix. I then rebuilt the binary and have confirmed that it solves the issue I was having.