Weather anomaly baseline values are currently extracted only from the DerivedValue table. Baselines are climatologies. Recently I noticed that there are also a lot of climatological values stored in Obs. For example:
db/crmp=> select count(obs_raw.*)
from
obs_raw join meta_vars v on obs_raw.vars_id = v.vars_id
where
v.net_var_name = 'Precip_Climatology'
;
count
-------
17130
This suggests that
- we should be getting some or all baseline values from Obs
- or we should transfer these into DerivedValue
- and consider how and why it is that non-observational data is stored in Obs, a.k.a. obs_raw as in "raw observations"
Only the first item can be addressed entirely within this backend. The others require work outside of it.
As a first step, we can certainly investigate how the climatologies in the two tables compare, and whether it would be wise to obtain our baselines from both places. Potentially this could expand the weather anomaly station coverage significantly.
Weather anomaly baseline values are currently extracted only from the
DerivedValuetable. Baselines are climatologies. Recently I noticed that there are also a lot of climatological values stored inObs. For example:This suggests that
Only the first item can be addressed entirely within this backend. The others require work outside of it.
As a first step, we can certainly investigate how the climatologies in the two tables compare, and whether it would be wise to obtain our baselines from both places. Potentially this could expand the weather anomaly station coverage significantly.