Use the spherical XYZ index for nearest-point queries - #17
Open
asinghvi17 wants to merge 1 commit into
Open
asinghvi17 wants to merge 1 commit into
asinghvi17 wants to merge 1 commit into
Conversation
asinghvi17
added this pull request to stack #18
September 20, 2026 20:23
This branch has not been deployed
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.
Spherical point lookups now use their lazy XYZ index for
Nearqueries. Previously every spherical nearest-point query scanned the entire lookup, even when an index was configured.The existing branch-and-bound traversal now compares angular point distances and a conservative angular bound derived from each node’s XYZ box.
tree=nothingremains an exhaustive reference path, and ties still select the lowest index. Radius cancels from nearest ordering. General spherical nearest-line/polygon distance remains dependent on upstream GeometryOps support.Validation: 816 nearest-point assertions cover all three tree algorithms, Float32 and Float64 inputs, random queries, dateline/pole/near-antipodal cases, duplicate-point ties, and lower-bound checks. The existing spherical and planar selector test files also pass.