Difference between revisions of "Snowpack observations"

From InfoEx Help Information
Jump to navigation Jump to search
(Related documents)
(All supported fields)
Line 29: Line 29:
 
==All supported fields==
 
==All supported fields==
 
{|class="TblObsFields"
 
{|class="TblObsFields"
|-
+
Insert Link to Best Practice Document
|class="Header"|Name
 
|class="Header"|Mandatory
 
|class="Header"|Comment
 
|-
 
|class="Name"|To be completed
 
|class="Mandatory"|
 
|
 
 
|}
 
|}
 
{{Note|The aspect-elevation rose diagram user control for entering general aspect and elevation information for the snowpack observations has not been implemented yet.}}
 
  
 
==Special functionality==
 
==Special functionality==

Revision as of 10:02, 23 September 2016

REQUIREMENTS
Permission All users
Connectivity Online and offline

This observation type refers to snowpack observations as described in OGRS section 2. While the current version of the InfoEx application does not have explicit entry forms for snow profile observations like in SnowPro or other snow profile applications, the comments field of the snowpack observation type allows users to describe the main characteristics observed in their snow profile and their test results in free-text format.

NOTE The old InfoEx had an observation type call Snowpack Structure that was used for both the general description of the local snowpack structure and the description of snow profile observations. In the new InfoEx, these two observation types are separated more clearly. While snow profile observations are entered into the snowpack observation type, general descriptions of the snowpack structure are entered into the snowpack workflow module.
Fig. 1: Default format of snowpack observation entry form

Mandatory fields

Mandatory field are highlighted with a red outline and label. Incorrectly completed mandatory field will result in a validation error on submission.

NOTE If you cannot see the highlighted field in the favourite section of your observation entry form, open all of the sections at the bottom to find the field that is causing the issue.
Name Mandatory Comment
Location Always Location of observation; needs to be a single locations of any type.
Date Always Date of observation

All supported fields

Insert Link to Best Practice Document

Special functionality

In addition to associating snowpack observations with a predefined location from your location catalog, it is also possible to drop a pin on a Google Earth map to indicate exactly where the observation was taken. See Providing the exact location of an avalanche or snowpack observation for more information on how to drop a pin.

NOTE The map layer for viewing snowpack observations in the map view of the InfoEx report has not been implemented yet.

Related documents

Other observation types

Related functionality

Functionality tested by

  • Jan. 2, 2014: Pascal Haegeli