-
Notifications
You must be signed in to change notification settings - Fork 44
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.
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
Create Dask GeoDataFrame from wkt string #208
Comments
For the case of x / y columns, we have an example in the docs like:
We should probably add For now, I think the best work-around is the
We need to pass That's probably also the reason why |
Thanks! I think having a function Coming back to the workaround. I'm now calculating it like this:
UPDATE:
|
Hi @jorisvandenbossche, I'm pretty new to dask-geopandas. A few weeks back, I had a similar requirement and I basically ended up creating my own I used the same approach implemented in |
None of the examples in this ticket worked for me, and it took me way too long to figure out that it was because of dask-expr and its "query planning". To get these examples to work, you need to disable query planning:
See: #284 |
I'm trying to load geometries from wkt.strings stored in a
dask.Dataframe
. I tried both in nativedask
anddask_geopandas
, but the libraries seem not to be able to deal with wkt strings. Since thedask_geopandas
community is probably more familiar with this type of issue, I thought I could better raise it here.Please find below a toy script with some things I've tried.
What would be the suggested work around? Or should a functionality to load from wkt strings become available in
dask_geopandas
?The text was updated successfully, but these errors were encountered: