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
The planned implementation of the min/max value for each variable is to determine these values for each root region. However, this min/max values won't be updated for the subdivisions of the root region, which can have different range of values, for instance if the root region includes mountains and the subdivisions only plains.
This task is to decide that this working is ok (or not) for Karl.
The text was updated successfully, but these errors were encountered:
I realized that this has much more implication for the user experience. It can be confusing for him that if he change of regions, the variable legend colormap range value changes too. This definitely asks for clarification by Karl before implementing this feature.
A simple solution (to implement on the supercomputer side) would be first to have different, fixed, range values for north and south hemisphere, and for start and end of the season. This would make 4 range values per variable.
The range of values will be sent in the root region file.
This also implies that there would be different legends per variable per region. This point is to clarify on the way we want it to work on the web-app side.
The planned implementation of the min/max value for each variable is to determine these values for each root region. However, this min/max values won't be updated for the subdivisions of the root region, which can have different range of values, for instance if the root region includes mountains and the subdivisions only plains.
This task is to decide that this working is ok (or not) for Karl.
The text was updated successfully, but these errors were encountered: