Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

ENH: optimize export_by_location with e.g. intersects is False #548

Open
theroggy opened this issue Jul 29, 2024 · 0 comments · May be fixed by #606
Open

ENH: optimize export_by_location with e.g. intersects is False #548

theroggy opened this issue Jul 29, 2024 · 0 comments · May be fixed by #606
Assignees
@KriWay-LV

Comments

@theroggy
Copy link
Collaborator

theroggy commented Jul 29, 2024 •
edited
Loading

Now, relate is used for almost all spatial relations, which isn't very optimized. Using the specialized function for all 'simple' queries should be faster.

12 minutes for this is slow:

        ortho_not_available_path = Path(
            "X:/Monitoring/OrthoSeg/_varia/roi_ofw/mask_ofw_2024_2024-07-23.gpkg"
        )
        gfo.export_by_location(
            input_to_select_from_path=percelen_path,
            input_to_compare_with_path=ortho_not_available_path,
            output_path=output_path,
            spatial_relations_query="intersects is False",
        )
@theroggy theroggy changed the title ENH: optimize export_by_location with intersects is False ENH: optimize export_by_location with e.g. intersects is False Oct 23, 2024
@KriWay-LV KriWay-LV linked a pull request Dec 19, 2024 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@KriWay-LV KriWay-LV

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

ENH: optimize export_by_location with e.g. intersects is False KriWay-LV/geofileops
2 participants
@theroggy @KriWay-LV