You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Very strange, was this maybe due to the old implementation in which the figure size of datashader was given by the value of the coordinates/transformed coordinates? I think this has now been fixed. Also a way to test for that is to make random points with bound values (like points with coordinates in [0, 1]).
To get a feeling for when rendering with
datashader
is faster thanmatplotlib
, we prepared a notebook contrasting the two: https://github.com/scverse/spatialdata-notebooks/blob/main/notebooks/examples/speed_up_illustration.ipynbHowever, in doing so we found that rendering points is not really sped up for some reason.
Why is that?
cc @Sonja-Stockhaus
The text was updated successfully, but these errors were encountered: