Difference between revisions of "Location catalog overview"

From InfoEx Help Information
Jump to navigation Jump to search
 
(18 intermediate revisions by one other user not shown)
Line 1: Line 1:
 
__NOTOC__
 
__NOTOC__
  
The location catalog is the backbone of the geospatial InfoEx system. This document give a general overview of the location catalog functionality of the InfoEx application.  
+
The location catalog is the backbone of the geospatial InfoEx system. All observations entered into the InfoEx system need to be associated with a pre-defined location from your location catalog. This document gives a general overview of the location catalog functionality of InfoEx.  
  
==Background==
+
==Locations types==
All observation entered into the InfoEx system need to be associated with a pre-defined location from your location catalog. For certain observation types, it is possible to also specify a more detailed location in the observation entry screen.
+
The InfoEx system currently supports the following location types:
 +
*[[Location types and symbology#OperationArea|Operation area]]
 +
*[[Location types and symbology#ForecastArea|Forecast area]]
 +
*[[Location types and symbology#OperatingZone|Operating zone]]
 +
*[[Location types and symbology#PermanentClosure|Permanent closure]]
 +
*[[Location types and symbology#Road|Road]]
 +
*[[Location types and symbology#Rail|Rail]]
 +
*[[Location types and symbology#Route|Route]]
 +
*[[Location types and symbology#SkiRun|Ski run]]
 +
*[[Location types and symbology#ControlRoute|Control route]]
 +
*[[Location types and symbology#AvalanchePath|Avalanche path]]
 +
*[[Location types and symbology#WeatherSite|Weather site]]
 +
*[[Location types and symbology#ShotPlacement|Shot placement]]
  
===Loocations types===
+
See [[Location types and symbology]] for a detailed description of supported location types and the symbols used to display them on the location catalog map.
The InfoEx system currently supports the following location types
 
  
{|
+
==Location hierarchy==
|-
+
Locations entered into InfoEx are organized in a location hierarchy. The location hierarchy has a '''tree structure''' where a location can only have a single parent, but multiple children. Every location needs to be derived from a single parent location, except the operation area, which is the top parent location of a location catalog. To ensure meaningful location catalogs, there are numerous restrictions on what type of locations can be contained by other locations. See [[Location hierarchy]] for a detailed description of the supported relations.
|style="width:150px;"|''Location type''
 
|''Description''
 
|style="width:350px;"|''Supported geometries''
 
|''Symbology''
 
|-
 
|'''Operation location'''
 
|Represents main location of operation. Every operation need to have an operation location that acts as the parent for all other locations.
 
|Polygon: Yellow outline with highlight transparent white fill<br/>Point: Yellow paddle
 
|[[File:SymbologyOperationLocation.png|300px|thumb|right|Operation location symbology(polygon, point)]]
 
|-
 
|'''Forecast area'''
 
|Larger area that represents a unit for avalanche forecasting purposes. Typical spatial scales range from individuals bowls to large sections of western Canada. Typically used by ski areas, highway and railway forecasters, and public avalanche forecasting agencies.
 
|Polygon: Blue outline with highlight transparent white fill
 
|[[File:SymbologyForecastArea.png|300px|thumb|right|Forecast area symbology(polygon)]]
 
|-
 
|'''Operating zone'''
 
|Larger area that represents a unit for avalanche forecasting purposes. Typically used in mechanized and non-mechanized backcountry operations and commonly represent drainages or groups of drainages.
 
|Polygon: Red outline with highlight transparent white fill
 
|[[File:SymbologyOperatingZone.png|300px|thumb|right|Operating zone symbology(polygon)]]
 
|-
 
|'''Permanent closure'''
 
|Permanently closed area of any spatial scales. Typically used in ski areas.
 
|Polygon: Black outline with highly transparent black fill
 
|[[File:SymbologyPermanentClosure.png|300px|thumb|right|Permanent closure symbology(polygon)]]
 
|-
 
|'''Road'''
 
|A complete or continuous section of a road. Can be used for both permanent roads (e.g., highways, access roads) and seasonal roads (e.g., cat roads in a catski operation)
 
|Line: Wide white line
 
|[[File:SymbologyRoad.png|300px|thumb|right|Road symbology(line)]]
 
|-
 
|'''Rail'''
 
|A complete or continuous section of a railway line.
 
|Line: Wide black line
 
|[[File:SymbologyRail.png|300px|thumb|right|Rail symbology(line)]]
 
|-
 
|'''Route'''
 
|A complete or continuous section of route, typically an uphill ski or climbing route. Primarily used by non-mechanized backcountry operations.
 
|Line: Light green line
 
|[[File:SymbologyRoute.png|300px|thumb|right|Route symbology(line)]]
 
|-
 
|'''Ski run'''
 
|Approximate location of a ski run
 
|Polygon: Orange outline with transparent orange fill<br/>Line: Orange line<br/>Point: Red paddle with star
 
|[[File:SymbologySkiRun.png|300px|thumb|right|Ski run symbology(polygon, line, point)]]
 
|-
 
|'''Avalanche path'''
 
|Location of an avalanche path
 
|Polygon: Fuchsia outline with transparent fuchsia fill<br/>Line: Fuchsia line<br/>Point: Fuchsia paddle with star
 
|[[File:SymbologyAvalanchePath.png|300px|thumb|right|Avalanche path symbology(polygon, line, point)]]
 
|-
 
|'''Weather site'''
 
|Location of a permanent weather or snow profile observation site
 
|Point: Black and white square
 
|[[File:SymbologyWeatherSite.png|300px|thumb|right|Weather site symbology(point)]]
 
|-
 
|'''Shot placement'''
 
|Location on an avalanche path regularly used for avalanche control with explosives
 
|Point: Yellow paddle with star
 
|[[File:SymbologyShotPlacement.png|300px|thumb|right|Shot placement symbology(point)]]
 
|}
 
  
 +
There are currently '''two main uses''' of the location hierarchy in the InfoEx application:
 +
* It helps to keep your location catalog tidy
 +
* It is used in the [[Observations module]] to pull previously entered observations into the workflow. Only observations associated with locations that are direct or indirect children of the location associated with the workflow are automatically presented for review and submission to InfoEx.
  
==Step-by-step description==
+
The hierarchy in the location tree needs to be '''defined explicitly''' and is not directly derived from the geospatial information of the locations. This approach allows for a more flexible use of the location hierarchy. For example, a weather site that provides valuable observations for a forecast region can be made a child of this forecast region even if the site is not located within the forecast region.
 
 
{|class="TblSteps"
 
|-
 
|class="StepNum" | 1.
 
|Description of first step.
 
|-
 
|class="StepNum" | 2.
 
|Description of second step.
 
|-
 
|class="StepNum" | 3.
 
|...
 
|}
 
  
 
==Related documents==
 
==Related documents==
* Link to relate document 1
+
{{PagesLocations}}
* Link to relate document 2
 
 
 
==Functionality tested by==
 
* Date: Tester / Server / Application version (e.g., Oct. 11: Pascal Haegeli / QA Server / Test Version 0.28.00)
 
  
 
[[Category:Locations]]
 
[[Category:Locations]]

Latest revision as of 14:04, 23 November 2015


The location catalog is the backbone of the geospatial InfoEx system. All observations entered into the InfoEx system need to be associated with a pre-defined location from your location catalog. This document gives a general overview of the location catalog functionality of InfoEx.

Locations types

The InfoEx system currently supports the following location types:

See Location types and symbology for a detailed description of supported location types and the symbols used to display them on the location catalog map.

Location hierarchy

Locations entered into InfoEx are organized in a location hierarchy. The location hierarchy has a tree structure where a location can only have a single parent, but multiple children. Every location needs to be derived from a single parent location, except the operation area, which is the top parent location of a location catalog. To ensure meaningful location catalogs, there are numerous restrictions on what type of locations can be contained by other locations. See Location hierarchy for a detailed description of the supported relations.

There are currently two main uses of the location hierarchy in the InfoEx application:

  • It helps to keep your location catalog tidy
  • It is used in the Observations module to pull previously entered observations into the workflow. Only observations associated with locations that are direct or indirect children of the location associated with the workflow are automatically presented for review and submission to InfoEx.

The hierarchy in the location tree needs to be defined explicitly and is not directly derived from the geospatial information of the locations. This approach allows for a more flexible use of the location hierarchy. For example, a weather site that provides valuable observations for a forecast region can be made a child of this forecast region even if the site is not located within the forecast region.

Related documents