Difference between revisions of "Location catalog overview"

From InfoEx Help Information
Jump to navigation Jump to search
(Loocations types)
 
(14 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.
 
 
 
===Loocations types===
 
 
The InfoEx system currently supports the following location types:
 
The InfoEx system currently supports the following location types:
*Operation location
+
*[[Location types and symbology#OperationArea|Operation area]]
*Forecast area
+
*[[Location types and symbology#ForecastArea|Forecast area]]
*Operating zone
+
*[[Location types and symbology#OperatingZone|Operating zone]]
*Permanent closure
+
*[[Location types and symbology#PermanentClosure|Permanent closure]]
*Road
+
*[[Location types and symbology#Road|Road]]
*Rail
+
*[[Location types and symbology#Rail|Rail]]
*Route
+
*[[Location types and symbology#Route|Route]]
*Ski run
+
*[[Location types and symbology#SkiRun|Ski run]]
*Avalanche path
+
*[[Location types and symbology#ControlRoute|Control route]]
*Weather site
+
*[[Location types and symbology#AvalanchePath|Avalanche path]]
*Shot placement
+
*[[Location types and symbology#WeatherSite|Weather site]]
 +
*[[Location types and symbology#ShotPlacement|Shot placement]]
  
 
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.
 
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.
  
==Step-by-step description==
+
==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.
  
{|class="TblSteps"
+
There are currently '''two main uses''' of the location hierarchy in the InfoEx application:
|-
+
* It helps to keep your location catalog tidy
|class="StepNum" | 1.
+
* 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.  
|Description of first step.
+
 
|-
+
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="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 13: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