Closed ManuelPopp closed 2 months ago
This may have been fixed by https://github.com/geopandas/dask-geopandas/pull/307. Can yo try installing geopandas from GitHub and reporting whether you still see the error?
I ran
pip install git+https://github.com/geopandas/geopandas.git
Successfully installed geopandas-1.0.1+18.g3d0ff15
Which alone did not resolve the error. However, combined with
pip install git+https://github.com/geopandas/dask-geopandas
Successfully installed dask-geopandas-0.4.1+3.g069f0c1
it seems the issue is gone! Thank you for the quick response to this issue!
Hey there,
I ran into some issues/weird behaviour.
The issue
I get a
ValueError
when runningsjoin
with twodask_geopandas.expr.GeoDataFrame
s. THere are no tuples involved. I also checked the data types. Everything seems fine, but it does not run.The code I run is as follows (full version at the end):
Here,
coordinates
andpolygons
are twodask_geopandas.expr.GeoDataFrame
s. I can share example data if required.This is what I get when I print out the data type, crs, and
.head()
of the input data sets:What I tried/found out
The error does not occur, if I apply
.compute()
to the input variables before runningsjoin
. This is even the case when I turn the computedGeoPandas.GeoDataFrame
s back intodask_GeoPandas
, i.e., into the samedask_geopandas.expr.GeoDataFrame
as before.While this workaround may be suitable for small data sets (then, however, the question would be: Why use dask in the first place?), computing some intermediate output will take quite a long time for a huge data set.
Environment
Full code