LucaMarconato

Hi @spatts14, it should now be addressed in `main`, but we haven't made a release of the code yet. Please `pip` install from GitHub and let us know if it...

Thanks for reporting. It seems to be related to https://github.com/scverse/spatialdata-plot/issues/375. @timtreis any take?

One idea would be to let the user decide to load the points in-memory, and if this is done, the points would stay loaded in-memory. This is a separate topic...

Hi @Rafael-Silva-Oliveira, I think you can achieve this by using [join_spatialelement_table()](https://spatialdata.scverse.org/en/latest/api/operations.html#spatialdata.join_spatialelement_table) followed by a call of `pd.merge()` (using the `instance_key` column from the joined table and the index from the...

@EliHei2 gonna meet and brainstorm on this next monday.

While I see the argument in favor, I think we should keep only `DaskDataFrame` for the moment, for the following reasons: * the xenium points fit in memory but loading...

@gtca in `postdata` everything is lazy by default right? If I remember correctly if the user load something then it persists in memory, is it correct?

I see the speed improvements but I think that 1.88 seconds is too slow, especially with datasets that can have many more points (like MERSCOPE, [see zulip message](https://imagesc.zulipchat.com/#narrow/stream/325775-scverse-.2B-ome-.28private.29/topic/points.20.28performance.29/near/323251681); there are...

> Hi Lea, > I had this same issue. I learned that spatialdata 0.3.0 is the release version. > match_sdata_to_table is currently in the dev version. > The new release...

@bellenger-l, please can you open one separate issue for the other problems you are reporting? I give a quick answer here, but please let's follow up in separate GitHub issues....