You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit ccf1ea0
Browse filesBrowse the repository at this point in the historyBrowse files
test: drop the "c" region case from the interleaved-regions join fixture
Region "c" was added to _make_interleaved_regions_sdata with no matching
spatial element in the SpatialData object at all, and right_exclusive was
marked xfail(strict=True) for not surfacing its row as excluded.
That state (a table declaring a region absent from the SpatialData object)
already triggers a UserWarning at SpatialData construction/subset time
(validate_table_in_spatialdata), and whether join_spatialelement_table
should be expected to handle it, and how, given the "b3" case is still
correctly handled and the mostly working state of the codebase, is a
design question, not a clear-cut bug. Dropping the case and the xfail here;
a follow-up documents the actual behavior instead.
# generalization to all the join types of the bug reported in https://github.com/scverse/spatialdata/issues/1162
1087
1070
# covering all `how` values of `join_spatialelement_table`, crossed with all values of `match_rows`, and checking
0 commit comments