{"id":14,"date":"2012-12-05T16:27:19","date_gmt":"2012-12-06T00:27:19","guid":{"rendered":"https:\/\/blogs.ubc.ca\/dynamicavalanche\/?page_id=14"},"modified":"2012-12-07T10:31:21","modified_gmt":"2012-12-07T18:31:21","slug":"methodology","status":"publish","type":"page","link":"https:\/\/blogs.ubc.ca\/dynamicavalanche\/methodology\/","title":{"rendered":"Methodology"},"content":{"rendered":"

Avalanche hazard is a continuously varying phenomenon depending on recent weather trends and taking into account terrain and snowpack history. For this reason it was decided that an automated GIS tool to update hazard level in real time would be most useful. This was accomplished using a Python script for ArcGIS. The basic function of the script is highlighted below, and the full code can be seen here<\/a>.<\/p>\n

\"\"

General algorithm used by python script for updating avalanche hazard in ArcGIS.<\/p><\/div>\n

Fundamental\u00a0to the measurement of avalanche hazard is a multi-criteria evaluation (MCE) that takes into account what is necessary to cause an\u00a0avalanche\u00a0as well as some potential perturbing\u00a0factors such as precipitation and wind loading. Without access to historic data at a particular weather station the current model only considers immediate conditions reported at an hourly interval. A time history of precipitation is available from either 6:00 or 18:00, but is by no means\u00a0adequate\u00a0in developing the full weather picture. The diagram below outlines the factors used in constructing the MCE and a first take at the weight given to each factor. Brown elements are inputs from either the weather station or GIS model. Green are the variables considered and for each 30m by 30m cell in the GIS grid are given a value between 0 and 1 based. The areas under consideration are those that are above\u00a0tree line\u00a0or in an avalanche path, only a limited number of which were digitized from satellite imagery. Simple linear, normal and stepwise functions were used to assign the value. These variables are then scaled according to a weighting scheme shown to arrive at a final avalanche hazard score 0 to 100. These values are all preliminary and are subject to the critique of avalanche professionals.<\/p>\n

\"\"

Overview of the multi-criteria evaluation (MCE) used in evaluating avalanche hazard.<\/p><\/div>\n

All of which is performed within ArcGIS. Requisite to scoring process is the weight given to each of variables as shown in the MCE above. The maximum of 30 for precipitation rate and aspect (which is derived from wind rate) is an incremental scale. At this point in time an arbitrary stepwise scale is used as presented below.<\/p>\n\n\n\n\n\n<\/colgroup>\n\n\n\n\n\n\n\n\n\n
Precipitation Rate (100 * km\/hr)<\/strong><\/td>\n\u00a0<\/strong><\/td>\n\u00a0<\/strong><\/td>\nWind Rate (km\/hr)<\/strong><\/td>\n\u00a0<\/strong><\/td>\n<\/tr>\n
Low<\/strong><\/td>\nHigh<\/strong><\/td>\nScore<\/strong><\/td>\n\u00a0<\/strong><\/td>\nLow<\/strong><\/td>\nHigh<\/strong><\/td>\nScore<\/strong><\/td>\n<\/tr>\n
0<\/td>\n0<\/td>\n0<\/td>\n<\/td>\n0<\/td>\n0<\/td>\n2<\/td>\n<\/tr>\n
0<\/td>\n20<\/td>\n6<\/td>\n<\/td>\n0<\/td>\n5<\/td>\n6<\/td>\n<\/tr>\n
20<\/td>\n40<\/td>\n12<\/td>\n<\/td>\n5<\/td>\n10<\/td>\n12<\/td>\n<\/tr>\n
40<\/td>\n60<\/td>\n16<\/td>\n<\/td>\n10<\/td>\n15<\/td>\n16<\/td>\n<\/tr>\n
60<\/td>\n80<\/td>\n24<\/td>\n<\/td>\n15<\/td>\n20<\/td>\n24<\/td>\n<\/tr>\n
80<\/td>\nabove<\/td>\n30<\/td>\n<\/td>\n20<\/td>\nabove<\/td>\n30<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n","protected":false},"excerpt":{"rendered":"

Avalanche hazard is a continuously varying phenomenon depending on recent weather trends and taking into account terrain and snowpack history. For this reason it was decided that an automated GIS tool to update hazard level in real time would be most useful. This was accomplished using a Python script for ArcGIS. The basic function of […]<\/p>\n","protected":false},"author":15189,"featured_media":0,"parent":0,"menu_order":2,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-14","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/blogs.ubc.ca\/dynamicavalanche\/wp-json\/wp\/v2\/pages\/14","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blogs.ubc.ca\/dynamicavalanche\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/blogs.ubc.ca\/dynamicavalanche\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.ubc.ca\/dynamicavalanche\/wp-json\/wp\/v2\/users\/15189"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.ubc.ca\/dynamicavalanche\/wp-json\/wp\/v2\/comments?post=14"}],"version-history":[{"count":11,"href":"https:\/\/blogs.ubc.ca\/dynamicavalanche\/wp-json\/wp\/v2\/pages\/14\/revisions"}],"predecessor-version":[{"id":80,"href":"https:\/\/blogs.ubc.ca\/dynamicavalanche\/wp-json\/wp\/v2\/pages\/14\/revisions\/80"}],"wp:attachment":[{"href":"https:\/\/blogs.ubc.ca\/dynamicavalanche\/wp-json\/wp\/v2\/media?parent=14"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}