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
VisualMap is only applying correctly for the first progressivly rendered block (until datapoint 1000). Afterwards visualMap seems to be apllied randomly. Issue becomes more clear when moving the handle on the visualMap component to filter data. (also shows up on the internal progressiveThreshold of 100000 if not set)
The text was updated successfully, but these errors were encountered:
MatthiasMert
changed the title
[BUG] visualMap not applying correctly for scatterGl when progressive and progressiveThreshold is set
[BUG] visualMap not applying correctly for scatterGL with progressiveRandering
May 3, 2024
MatthiasMert
changed the title
[BUG] visualMap not applying correctly for scatterGL with progressiveRandering
[BUG] visualMap not applying correctly for scatterGL with progressive Rendering
May 3, 2024
Default progressive value is 100000. Workaround is to not change it, or to make it bigger than data size.
Revision
Yes, there is a bug with visualMap.
When both progressiveThreshold and progressive values are larger than data size (5000), then visualMap works fine.
When both progressiveThreshold and progressive values are smaller than data size (5000), then visualMap works correctly for the first progressive number of points (1000), the other points are randomly colored.
Just wanted to document the very strange behaviour of scatterGL + visualMap + progressive rendering
Example:
VisualMap is only applying correctly for the first progressivly rendered block (until datapoint 1000). Afterwards visualMap seems to be apllied randomly. Issue becomes more clear when moving the handle on the visualMap component to filter data. (also shows up on the internal progressiveThreshold of 100000 if not set)
The text was updated successfully, but these errors were encountered: