Difference between revisions of "Terrain management"
Jump to navigation
Jump to search
(→Mandatory fields) |
(→All supported fields) |
||
| Line 28: | Line 28: | ||
{|class="TblObsFields" | {|class="TblObsFields" | ||
[https://c.ymcdn.com/sites/www.avalancheassociation.ca/resource/resmgr/infoex/2016/InfoEx_Terrain_Management_Up.pdf] Click to read a guidance document. | [https://c.ymcdn.com/sites/www.avalancheassociation.ca/resource/resmgr/infoex/2016/InfoEx_Terrain_Management_Up.pdf] Click to read a guidance document. | ||
| + | The rose for Asp/Elev Travelled was mandatory for season 16/17 but changed to non-mandatory for 17/18 | ||
|} | |} | ||
Latest revision as of 10:46, 10 November 2017
| REQUIREMENTS | |
| Permission | All users |
| Connectivity | Online and offline |
Terrain management helps communicate how subscribers are managing avalanche problems through terrain management.
Mandatory fields
Mandatory fields are highlighted with a red outline and label. Incorrectly completed mandatory fields will result in a validation error on submission.
| Name | Mandatory | Comment |
| Locations | Always | Location of observation; needs to be single or combinations of locations down to ski run and avalanche path level. |
| Date | Always | Date of observation |
All supported fields
[1] Click to read a guidance document. The rose for Asp/Elev Travelled was mandatory for season 16/17 but changed to non-mandatory for 17/18Special functionalities
None
Related documents
Other observation types
- Weather observations
- Field summaries
- Avalanche observations
- Avalanche summaries
- Snow Profiles
- Terrain management
- General messages
- Avalanche control (additional subscription required)
Related functionality
- Difference between observations and assessments
- Entering and submitting observations overview
- Customizing observation entry forms
Functionality tested by
- Jan. 2, 2014: Pascal Haegeli
