Remove time intersection from pairing process #10
Conversation
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.
Changelog
[Changed]
pair_from_sources: the pairing function now matches declarations to detections only according to spatial intersection. The date comparison actually contradicted the goal to describe soil occupation at the time of the detection.pair_from_sources: database objects marked for deletion are now logged alongside their deletion reason.pair_from_sources: some pairing statistics other than deletions are now logged as debug entries[Fixed]
pyproject.toml: changed ruff configuration keys to follow a deprecation warningdelete_data: If the input id list is empty, instead of sending an invalid SQL request, deletion functions now exit before attempting anything