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 data used by the CC are stored in the table cryospheric_commission.data2d. A detailed description of the tables can be found here.
The INSERT of the new records into cryospheric_commission.data2d could be solved by adding trigger functions to the tables length_change.length_change_data and mass_balance.mass_balance.
The text was updated successfully, but these errors were encountered:
Instead of storing the values for cumulative length changes, the values are getting calculated in the view ekk_lengthchange_cumulative and later as union with data2d.
The INSERT script of the cumulative length change data got deleted (not used anymore).
addresses issue #7 .
Establishing of an INSERT-Trigger on table length_change.length_change_data.
The trigger will check and insert new length-change data into the table cryospheric_commission.data2d.
Requirements:
Check if data already in table data2d. INSERT if not existing, UPDATE if existing but different, nothing if identical.
Perhaps additional table to store the required glaciers.
The length-change and mass-balance data of the 7 representative glaciers shown on the website of the Cryospheric Commission (CC) (e.g. https://naturwissenschaften.ch/topics/snow-glaciers-permafrost/glaciers/length_variation ) have to be updated automatically during inserting new data into the GLAMOS main tables.
The data used by the CC are stored in the table cryospheric_commission.data2d. A detailed description of the tables can be found here.
The INSERT of the new records into cryospheric_commission.data2d could be solved by adding trigger functions to the tables length_change.length_change_data and mass_balance.mass_balance.
The text was updated successfully, but these errors were encountered: