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
There are multiple ways (some still to be implemented) to subset/query a SpatialData object. Some of these methods are living outside this repo. We need to port them here and use a more consistent syntax (for instance always sdata.query.query_method).
Currently, the bounding_box_query doesn't automatically filter for elements within the target coordinate system. I think we should add that. We could just add a call to filter_by_coordinate_system to the beginning of the query. Thoughts?
Another point to consider, as observed in #443 (comment), is that query functions that appear only as methods of SpatialData maybe be a bit hidden in the docs.
Modules and functions of modules are better (or we can also put an explicit link to those methods in the docs).
Activity
[-]refactoring query functions[/-][+]Refactoring query functions[/+]kevinyamauchi commentedon Apr 13, 2023
Currently, the
bounding_box_querydoesn't automatically filter for elements within the target coordinate system. I think we should add that. We could just add a call tofilter_by_coordinate_systemto the beginning of the query. Thoughts?LucaMarconato commentedon Jan 9, 2024
Also:
SpatialData.subset()LucaMarconato commentedon Feb 1, 2024
Another point to consider, as observed in #443 (comment), is that query functions that appear only as methods of
SpatialDatamaybe be a bit hidden in the docs.