Difference between revisions of "Location catalog overview"
m (Pascal moved page Location catalog to Location catalog overview: Better title) |
|||
| (8 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. All | + | 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== | ==Locations types== | ||
| Line 13: | Line 13: | ||
*[[Location types and symbology#Route|Route]] | *[[Location types and symbology#Route|Route]] | ||
*[[Location types and symbology#SkiRun|Ski run]] | *[[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#AvalanchePath|Avalanche path]] | ||
*[[Location types and symbology#WeatherSite|Weather site]] | *[[Location types and symbology#WeatherSite|Weather site]] | ||
| Line 20: | Line 21: | ||
==Location hierarchy== | ==Location hierarchy== | ||
| − | Locations entered into | + | 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: | There are currently '''two main uses''' of the location hierarchy in the InfoEx application: | ||
* It helps to keep your location catalog tidy | * It helps to keep your location catalog tidy | ||
| − | * It is used in the [[ | + | * 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 | + | 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 | + | ==Related documents== |
| − | + | {{PagesLocations}} | |
| − | |||
| − | |||
| − | |||
| − | |||
[[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:
- Operation area
- Forecast area
- Operating zone
- Permanent closure
- Road
- Rail
- Route
- Ski run
- Control route
- Avalanche path
- Weather site
- 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.
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
- Location catalog overview
- Location types and symbology
- Location hierarchy
- Adding locations to the location catalog
- Editing locations in the location catalog
- Deleting locations from the location catalog
- Changing the hierarchy among your locations
- Searching for a location in the location catalog
- Viewing photos
- Downloading your location catalog as a KML file
