feat(parity): stboxes / splitNStboxes / splitEachNStboxes — multi-entry bbox emitters#127
Open
estebanzimanyi wants to merge 1 commit intomainfrom
Open
feat(parity): stboxes / splitNStboxes / splitEachNStboxes — multi-entry bbox emitters#127estebanzimanyi wants to merge 1 commit intomainfrom
estebanzimanyi wants to merge 1 commit intomainfrom
Conversation
…ry bbox emitters Adds the multi-entry bbox emitter family that's required to build R-tree-style indexes on temporal trajectories or geometry collections in DuckDB: - stboxes(<spatial>) → LIST(STBOX) — one stbox per sequence. - splitNStboxes(<spatial>, n) → LIST(STBOX) — exactly n stboxes, distributed by element count. - splitEachNStboxes(<spatial>, n) → LIST(STBOX) — each stbox covers n consecutive instants/elements of the input. Each registered for tgeometry / tgeography / tgeompoint / tgeogpoint (temporal) and bare geometry / geography (non-temporal). 15 overloads total. Wraps the MEOS exports tgeo_stboxes / tgeo_split_n_stboxes / tgeo_split_each_n_stboxes for the temporal forms and geo_stboxes / geo_split_n_stboxes / geo_split_each_n_stboxes for the bare-geometry forms. User motivation: multi-entry indexes on temporal data (R-tree, GIST-style) need to break long trajectories into bbox shards so that bounding-box overlap predicates can prune efficiently before falling through to the per-instant calculation. The three emitters are the canonical way to produce those shards. Smoke test test/sql/parity/060b_stboxes_emitters.test exercises all three emitters across tgeompoint / tgeometry / tgeography / bare geometry with deterministic len() and hasX/hasT/SRID accessor assertions — timezone-neutral.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Adds the multi-entry bbox emitter family — required to build R-tree-style indexes on temporal trajectories or geometry collections in DuckDB:
Each registered for tgeometry / tgeography / tgeompoint / tgeogpoint (temporal) and bare geometry / geography (non-temporal). 15 overloads total.
Why
Multi-entry indexes on temporal data (R-tree, GIST-style) need to break long trajectories into bbox shards so that bounding-box overlap predicates can prune efficiently before falling through to per-instant calculation. The three emitters are the canonical way to produce those shards. Without them, indexing a long trajectory degrades to O(n) per query — these emitters are essential.
Test plan
Depends on