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
.contains_properly currently takes about 550ms to run. I profiled it and saw that 250ms of that time is in the align_to_index call, which is potentially optional, especially if our API can deviate from GeoPandas in improved usability. I also saw that 150ms of the runtime is spent checking the three feature type exclusion requests, is_only_points, is_only_linestrings, or is_only_polygons. These should probably be optimized.
Minimum reproducible example
No response
Relevant log output
No response
Environment details
rapids-compose 23.04
Other/Misc.
No response
The text was updated successfully, but these errors were encountered:
Version
23.04
On which installation method(s) does this occur?
Rapids-Compose
Describe the issue
.contains_properly
currently takes about 550ms to run. I profiled it and saw that 250ms of that time is in thealign_to_index
call, which is potentially optional, especially if our API can deviate from GeoPandas in improved usability. I also saw that 150ms of the runtime is spent checking the three feature type exclusion requests,is_only_points
,is_only_linestrings
, oris_only_polygons
. These should probably be optimized.Minimum reproducible example
No response
Relevant log output
No response
Environment details
Other/Misc.
No response
The text was updated successfully, but these errors were encountered: