Support ImageStack in dynspread

[hoxbro]

Resolves #5993

screenrecord-2023-12-11_11.56.54.mp4

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 88.39%. Comparing base (802edf7) to head (6914e3a).
Report is 1 commits behind head on main.

Additional details and impacted files

@@             Coverage Diff             @@
##             main    #6024       +/-   ##
===========================================
+ Coverage   17.43%   88.39%   +70.95%     
===========================================
  Files         323      323               
  Lines       67588    67621       +33     
===========================================
+ Hits        11784    59771    +47987     
+ Misses      55804     7850    -47954     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[jlstevens]

Glad to see that the current codepath in datashader seems to work!

Two things to note:

1. As an extra validation, I would like to see dynspread using datashade next to dynspread using ImageStack - if everything is working correctly they should basically look the same.
2. I think more work is needed to support imagestack fully in the way we are imagining. For instance, supporting the spreading of layers that are not colormixed and included to added hover information. Such layers may not be numeric (e.g. text!) but should also be spread. The way I would imagine it is as if you are spreading a i64 image (an index per unique value) and then using those values as indices back to the data.

While the first thing would be good to check before merging this PR, the second thing is a fair bit more work and can be made into a feature request and addressed in a future PR.

[droumis]

@philippjfr: "To efficiently spread multiple layers, we may have to do this in Datashader"

[hoxbro]

I will add a small test and then merge this. We can always improve functionality later.

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.