Repository navigation
Datashader support for points and shapes - #244
Conversation
basic shapes datashader rendering
|
@Sonja-Stockhaus recently we introduced datashader support in In particular, you may find it useful to reuse the code in https://github.com/scverse/spatialdata/blob/b8fbc5c4ce7643455768a94665496ea4987294dd/src/spatialdata/_core/operations/rasterize.py#L604. Technically, I would consider isolating the code used to compute Please let me know what you think about this. Also, if you prefer to merge this PR as it is and then eventually reuse the components from |
Thanks for the heads up! I think fo now it would be best to finish and merge this PR and then do the refactoring later, since it's already so big. |
|
Your message comes at the right time 😊 I just made a new release 10 minutes ago! I agree, let's rather merge this and refactor later. |
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #244 +/- ##
=======================================
Coverage ? 80.19%
=======================================
Files ? 11
Lines ? 1737
Branches ? 0
=======================================
Hits ? 1393
Misses ? 344
Partials ? 0
🚀 New features to boost your workflow:
|
|
@Sonja-Stockhaus is this ready for review? |
timtreis
left a comment
There was a problem hiding this comment.
Already looks fairly good! Can we also add examples to your speed improvement notebook to show these?
| cmap=color_vector[0][:-2], | ||
| color_key=color_key, | ||
| min_alpha=np.min([150, render_params.alpha * 255]), | ||
| ) # TODO: choose other value than 150 for min_alpha (here and below)? |
There was a problem hiding this comment.
Why a different one? Is 150 bad?
There was a problem hiding this comment.
Not necessarily, but it's an arbitrary value that I chose to make everything better visible...
Work from @Sonja-Stockhaus and @ckmah.