Difference between revisions of "Terrain management"
Jump to navigation
Jump to search
(→Mandatory fields) |
(→Mandatory fields) |
||
Line 18: | Line 18: | ||
|class="Name"|Locations | |class="Name"|Locations | ||
|class="Mandatory"|Always | |class="Mandatory"|Always | ||
− | |Location of observation; needs to be single or combinations of | + | |Location of observation; needs to be single or combinations of locations down to ski run and avalanche path level. |
|- | |- | ||
|class="Name"|Date | |class="Name"|Date |
Revision as of 10:32, 19 March 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 field are highlighted with a red outline and label. Incorrectly completed mandatory field 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 |
Asp/Elev Travelled | Always | Aspect/Elevation Rose: right click for a menu of quick-fill options or click on all aspects and elevation bands travelled. |
All supported fields
Insert Link to Best Practice DocumentSpecial 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