Adopt minDistance for the portable Q5 cross-platform queries#40
Merged
Merged
Conversation
Q5 in the portable and th3index-portable query sets aggregates each licence group's trips into a tgeompoint array and calls minDistance(tgeompoint[], tgeompoint[]) for the exact set-set spatial minimum distance, matching the PG-native query set. The kernel uses each trip's STBox as a sound lower-bound prefilter and computes the per-pair distance with liblwgeom's segment-pair sweep, so the answer is identical to the aggregated geometry-collection form across PostgreSQL/MobilityDB, DuckDB/MobilityDuck and Spark/MobilitySpark.
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
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.
Q5 in the portable and th3index-portable query sets aggregates each licence group's trips into a tgeompoint array and calls minDistance(tgeompoint[], tgeompoint[]) for the exact set-set spatial minimum distance, matching the PG-native query set. The kernel uses each trip's STBox as a sound lower-bound prefilter and computes the per-pair distance with liblwgeom's segment-pair sweep, so the answer is identical to the aggregated geometry-collection form across PostgreSQL/MobilityDB, DuckDB/MobilityDuck and Spark/MobilitySpark.