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
What is happening?
The max value in the histogram changes (going lower) even though a 'higher' max value is still in view.
What should happen?
In this case, the max value is 1 and the histogram should keep the x-axis on 1 the entire time because that geometry is still in view.
Steps to Reproduce
I can set you up with the data/map offline.
Device/Browser/Airship-Version
Version 76.0.3809.100 (Official Build) (64-bit)
cartoframes version in develop as of Sept 11
Extra information
Nope, let me know how I can help. Thanks!
The text was updated successfully, but these errors were encountered:
I'm pretty sure this is due to the global vs. viewport aggregations and the values that VL returns. @elenatorro and I had this discussion when we were working on the globalHistogram expression.
For numeric values, we're using the sample values from the metadata, as we're doing in other global expressions such as GlobalQuantiles. As we've discussed, we'll talk about it during this cycle.
What is happening?
The max value in the histogram changes (going lower) even though a 'higher' max value is still in view.
What should happen?
In this case, the max value is 1 and the histogram should keep the x-axis on 1 the entire time because that geometry is still in view.
Steps to Reproduce
I can set you up with the data/map offline.
Device/Browser/Airship-Version
Version 76.0.3809.100 (Official Build) (64-bit)
cartoframes version in develop as of Sept 11
Extra information
Nope, let me know how I can help. Thanks!
The text was updated successfully, but these errors were encountered: