Difference between revisions of "Persistent weak layer overview"
(→Tagging observations with Operation PWLs) |
(→Viewing PWL information) |
||
Line 50: | Line 50: | ||
* '''Snowpack Description'''<br/>The ''PWL'' column lists the [[Definitions#OperationPWL|Operation PWLs]] currently being tracked in the [[Snowpack module]] for the given location. | * '''Snowpack Description'''<br/>The ''PWL'' column lists the [[Definitions#OperationPWL|Operation PWLs]] currently being tracked in the [[Snowpack module]] for the given location. | ||
* '''Persistent Weak Layers'''<br/>This table presents the PWL assessments completed in the [[Snowpack module]]. The '(O)' addition to the PWL name in the ''PWL'' column indicates that the label is an [[Definitions#OperationPWL|Operation PWL]] and not a [[Definitions#CommunityPWL|Community PWL]]. | * '''Persistent Weak Layers'''<br/>This table presents the PWL assessments completed in the [[Snowpack module]]. The '(O)' addition to the PWL name in the ''PWL'' column indicates that the label is an [[Definitions#OperationPWL|Operation PWL]] and not a [[Definitions#CommunityPWL|Community PWL]]. | ||
− | * ''' | + | * '''Snow Profiles'''<br/>The ''PWL'' column lists the [[Definitions#OperationPWL|Operation PWLs]] that have been observed in the reported observation. |
− | |||
To make it easier and more efficient for users to scan the InfoEx report with respect to PWLs, we are intending to add avalanche problem/PWL filtering functionality. This would allow you to create a report that would only include observations and assessment related to a specific avalanche problem and/or PWL. | To make it easier and more efficient for users to scan the InfoEx report with respect to PWLs, we are intending to add avalanche problem/PWL filtering functionality. This would allow you to create a report that would only include observations and assessment related to a specific avalanche problem and/or PWL. |
Latest revision as of 15:54, 9 November 2017
REQUIREMENTS | |
Permission | Operation administrator and higher |
Connectivity | Online and partial offline |
This document describes the purpose and use of persistent weak layers (PWL) in the InfoEx system.
Background
An in depth understanding of the current condition of PWLs is critical for avalanche forecasting. InfoEx provides tools for submitting relevant observations, keeping track of the condition of PWLs in your local area(s) and efficiently exchanging this information. The following sections provide a brief overview of the PWL functionality in InfoEx.
Managing PWLs
InfoEx requires users to explicitly define PWLs. This allows PWLs to be tracked more easily and offers opportunities for advanced queries. InfoEx supports two different types of PWLs.
ISSUE | Community PWLs can be defined and managed, however custom reports cannot currently be manipulated using community PWLs so the community PWLs are currently of limited value. JIRA: -540 (Mar.29, 2017) |
Operation PWLs
Operation PWLs are defined by an operation and represents locally observed PWLs in the snowpack. Operation PWLs are managed by operations, which have full control over the characteristics of these PWLs.
See the following documents about managing Operation PWLs:
- Creating a new operation PWL
- Modifying the baseline information of an existing operation PWL
- Deleting an existing operation PWL
Community PWLs
Since PWLs often exhibit significant spatial variability and might be buried on a range of days, individual operations might create their Operation PWLs differently. Community PWLs provide a mechanism for linking operation controlled Operation PWLs that relate to the same PWL in nature. This grouping of Operation PWLs allows for more meaningful queries. For example, the community PWL functionality will allow users to more efficiently get a comprehensive picture on the assessments of a PWL that covers a large area and effectively visualize the associated observed avalanche activity.
ISSUE | Community PWLs can be defined and managed, however custom reports cannot currently be manipulated using community PWLs so the community PWLs are currently of limited value. JIRA: -540 (Mar.29, 2017) |
See the following documents about managing Community PWLs:
- Creating a new community PWL
- Modifying the information for an existing community PWL
- Deleting an existing community PWL
NOTE | At this point any user with Submission Moderator permissions can manage Community PWLs. However, once the necessary filtering functionality has been implemented, the idea is that Avalanche Canada would be taking the lead in managing the Community PWLs as they are in the best position to assess large scale patterns. However, operators always have the ability to unlink their Operation PWLs from a specific Community PWL if they disagree with the grouping. |
Reporting PWL observation and assessments
InfoEx offers a number of options for highlighting PWL-relevant observations and assessing the local condition of their Operation PWLs.
Tagging observations with Operation PWLs
To highlight relevant observations, InfoEx users can tag observations of the following types with Operation PWLs:
- Avalanche Observations
Avalanche observations can be tagged with a single Operation PWL under the failure plane section of the observation entry form to indicate the failure plane of the avalanche. - Snow Profiles
Snow profiles can be tagged with multiple Operation PWLs in the observation details section to indicate which PWLs have been observed in the reported observation.
Assessing Operation PWLs
InfoEx users can track the condition of Operation PWLs and indicate how they relate to the current avalanche problems using the functionality of the following workflow modules:
- Snowpack module
The snowpack workflow module allows users to keep track of the current conditions of their Operation PWLs in their region(s). Click here for more information on the functionality of this workflow module. - Hazard assessment module
The hazard assessment module allows users to identify and characterize the present avalanche problems and associate them with Operation PWLs if necessary. Click here for more information on the functionality of this workflow module.
Viewing PWL information
Information on PWLs is presented in the following tables of the InfoEx reports:
- Avalanche Observations
The PWL column shows which Operation PWLs have been identified as the failure planes of the reported avalanches. - Avalanche Problem
The Failure Plane column indicates which Operation PWLs have been linked to existing avalanche problems in the Hazard assessment module for the given location. - Avalanche Hazard
The Av Problems column lists the avalanche problems contributing to the current avalanche hazard recorded in the Hazard assessment module for the given location. Problems associated with PWLs have the name of the Operation PWL attached to the avalanche problem label in brackets. - Snowpack Description
The PWL column lists the Operation PWLs currently being tracked in the Snowpack module for the given location. - Persistent Weak Layers
This table presents the PWL assessments completed in the Snowpack module. The '(O)' addition to the PWL name in the PWL column indicates that the label is an Operation PWL and not a Community PWL. - Snow Profiles
The PWL column lists the Operation PWLs that have been observed in the reported observation.
To make it easier and more efficient for users to scan the InfoEx report with respect to PWLs, we are intending to add avalanche problem/PWL filtering functionality. This would allow you to create a report that would only include observations and assessment related to a specific avalanche problem and/or PWL.
NOTE | The avalanche problem/PWL filtering functionality for taking full advantage of PWL information in the InfoEx report has not been implemented yet! |
Related documents
Operation PWLs
- Creating a new operation PWL
- Modifying the baseline information of an existing operation PWL
- Deleting an existing operation PWL
Community PWLs
- Creating a new community PWL
- Modifying the information for an existing community PWL
- Deleting an existing community PWL
Assessing PWLs
Functionality tested
- n/a