ENH: extending the basic spatial join about dask-geopandas HOT 5 OPEN

Supporting a left join
... when doing a left join, geopandas.sjoin preserves the rows of the left dataframe that don't match with a geometry of the right dataframe. But so if we do this multiple times, it means that rows of the left dataframe can end up in multiple output partitions

One way to "relatively easy" do this, is to always do at least one "left join" for each partition of the left dataframe, and then inner joins for any additional sjoin calls for that same partition. (unfortunately, this would still give potentially duplicated rows)

from dask-geopandas.

Hello! What's the priority on this feature request? I'm interested in performing left joins (a left outer join) with this library.

from dask-geopandas.

@alxmrs we don't really have a capacity to work on dask-geopandas beyond maintenance these days. I'd be happy to review a PR if someone wants to give it a go but it is unlikely that any of us will try to implement left joins anytime soon.

from dask-geopandas.

from dask-geopandas.

Sure, if you have anything to discuss leave it in this issue.

from dask-geopandas.