Closed sebastien-lenard closed 7 months ago
@MattF-NSIDC when you'll have a bit of time would you mind thinking about what could be the update of the json structure for variables?
@windnagelnsidc don't miss this part:
Other Remarks for potential info to display in the website:
- There is this additional issue that for some root regions, we have the historics and for others we don't have, or we have, but only for 5 years instead of 23 years. This info should also be somewhere.
- Additionally, for some root regions, the historics will be originate from a source called JPL and for others the historics will originate from the DAAC. This info should also be available
@MattF-NSIDC Thanks for drawing my attention to that. I'll make sure to bring it up on Tuesday.
Any time :)
Is it appropriate to think of these variables as a 2d matrix of independent variables? "Feature measured" along the top, and "statistic" along the left?
snow cover % | radiative forcing | albedo | |
---|---|---|---|
absolute | |||
anomaly (clim) | |||
anomaly (annual) |
EDIT: I see now that "snow cover days" does not have an anomaly calculation. Is that intentional? I guess it makes sense that this wouldn't have an anomaly value because it's a cumulative statistic? So the 2d matrix view falls apart. Reply: @MattF-NSIDC It's a mistake, all variables have anomalies. But we still may decide to remove the display of one anomaly but keeping the absolute value, in case of whatever problem
I'm going to add this as a topic to ask Karl for the Tuesday stake holder meeting.
Aim: have a view of how variables organize in a 'tree'. This is for helping Leslie and us, but we could have no tree at all in the website for development simplicity and rather decide of a big list of available variables.
Additionally, the current json format of variables should be updated. It might be necessary to split in two:
First draft of tree:
Remarks:
Other Remarks for potential info to display in the website: