Closed
Description
When a join_by_location
if ran on the result of a previous join_by_location
and column_prefixes=""
, the result will typically be wrong.
Root cause is the column spatial_relation
that is being added by the first join_by_location
being "reused" by the second join_by_location
, leading to wrong results.
Solution:
- As first bugfix I'll use a different temp column name which will avoid the column from being reused: BUG: fix wrong results returned by join by location if ran on result of join by location #476
- On longer term (but not backwards compatibel), I'll remove the undocumented column being added to the output.
Activity
join_by_location
#503