We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
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
Recent geopandas (since at lease 0.9) uses pygeos.STRTree as the spatial index if pygeos is installed, or else continues to use rtree.index.Index.
pygeos.STRTree
rtree.index.Index
snkit currently uses the .nearest functionality from the rtree.index.Index.
.nearest
As a workaround, if a recent geopandas and pygeos are installed, we can force compatibility by doing:
import geopandas as gpd gpd._compat.USE_PYGEOS = False import snkit
It looks like future pygeos - https://github.com/pygeos/pygeos/blob/b74773d5a7abbcfdf645ebd52b1ca4836a3fee80/pygeos/strtree.py#L180 - will have some variant of nearest and there's some discussion about the spatial index API compatibility going forward in geopands - geopandas/geopandas#1344
nearest
The text was updated successfully, but these errors were encountered:
Closed by 9a1a7dc
Sorry, something went wrong.
No branches or pull requests
Recent geopandas (since at lease 0.9) uses
pygeos.STRTree
as the spatial index if pygeos is installed, or else continues to usertree.index.Index
.snkit currently uses the
.nearest
functionality from thertree.index.Index
.As a workaround, if a recent geopandas and pygeos are installed, we can force compatibility by doing:
It looks like future pygeos - https://github.com/pygeos/pygeos/blob/b74773d5a7abbcfdf645ebd52b1ca4836a3fee80/pygeos/strtree.py#L180 - will have some variant of
nearest
and there's some discussion about the spatial index API compatibility going forward in geopands - geopandas/geopandas#1344The text was updated successfully, but these errors were encountered: