Battlecard: "Just use intersects"
Respond when a stakeholder or teammate wants a one-size-fits-all spatial join predicate.
A reviewer wants to use intersects for every spatial join because it returns more matches. Just use intersects. It catches everything, and missing a match is worse than overthinking predicates. Intersects is useful when any overlap counts. Here we are assigning one owner, so a broad predicate can create duplicates at boundaries. I will use the predicate that matches the ownership rule and send exceptions to a tie-break table. The response validates the concern about missing matches, then reframes the issue as ownership correctness. It explains the failure mode and offers a controlled exception path. Boundary duplicates Wrong ownership Unreviewed…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in