test(integration): coordinate mapper parity, a pure divergence catalog - #1238
Draft
james-willis wants to merge 1 commit into
Draft
test(integration): coordinate mapper parity, a pure divergence catalog#1238james-willis wants to merge 1 commit into
james-willis wants to merge 1 commit into
Conversation
RS_RasterToWorldCoordX/Y and RS_WorldToRasterCoordX/Y, one module per function. Every case xfails: SedonaDB treats pixel coordinates as 0-based where Sedona Spark (following PostGIS, and SedonaDB's own RS_PixelAs* functions) is 1-based, so results sit exactly one pixel apart everywhere, extrapolation included (apache#1235). The geometry-returning combined forms wait on a harness geometry-compare path.
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.
Probe-first coverage for RS_RasterToWorldCoordX/Y and RS_WorldToRasterCoordX/Y, one module per function — and every case is a cataloged xfail: SedonaDB maps pixel coordinates 0-based where Sedona Spark (following PostGIS, and consistent with SedonaDB's own 1-based RS_PixelAs*) is 1-based, so every result sits exactly one pixel apart, extrapolation outside the grid included. #1235 tracks the decision (align to 1-based, or document 0-basing loudly); when it resolves these xfails flip to anchored passing tests.
6 xfailed, nothing passes by design; CI runs the parity lane.