Difference between revisions of "Terrain management"
Jump to navigation
Jump to search
(→Mandatory fields) |
|||
Line 8: | Line 8: | ||
==<span class="TextRed">Mandatory fields</span>== | ==<span class="TextRed">Mandatory fields</span>== | ||
Mandatory field are highlighted with a red outline and label. Incorrectly completed mandatory field will result in a validation error on submission. | Mandatory field are highlighted with a red outline and label. Incorrectly completed mandatory field will result in a validation error on submission. | ||
− | + | ||
{|class="TblObsFields" | {|class="TblObsFields" |
Revision as of 10:28, 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 |
Location | Always | Location of observation; needs to be single or combinations of operation area, forecast areas or operating zones. |
Date | Always | Date of observation |
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