Difference between revisions of "Editing locations in the location catalog"

From InfoEx Help Information
Jump to navigation Jump to search
(Related documents)
(Functionality tested by)
Line 57: Line 57:
  
 
==Functionality tested by==
 
==Functionality tested by==
* Dec. 22: Pascal Haegeli
+
* Dec. 22, 2013: Pascal Haegeli
  
 
[[Category:Super User]][[Category:Operation Administrator]][[Category:Locations]][[Category:Software Issues]][[Category:Version 3.4.0]]
 
[[Category:Super User]][[Category:Operation Administrator]][[Category:Locations]][[Category:Software Issues]][[Category:Version 3.4.0]]

Revision as of 11:28, 2 January 2014

REQUIREMENTS
Permission Operation Administrator or higher
Connectivity Online only

This document describes how to edit locations in the location catalog of your operation.

Background

The ability to edit locations and delete obsolete location from your from the location tree of an operation should allow users to main a clean catalog of relevant location at all time. However, please note that the editing locations affects all observations that have ever been associated with the given location. For example, if you change the location of a weather site, all associated historic observations will be moved to the new location. Similarly, when you change the name of a ski run, all of the associate historic avalanche observation will then be associated with the new name of the ski run.

We recommend the following guidelines for the maintenance of your location catalog:

  • Editing is appropriate for minor changes in the attributes (e.g., fixing of typos, name changes, minor adjustments of their geometries) of location that still represent the same piece of terrain. This approach will ensure that that time series (e.g., long-time observations at a weather site with a changing name) will be maintained.
  • If the geometry of a location changes considerable, it would be better to delete the location and create a new location under the same name. This approach will ensure that all observations associated with this location are displayed at their appropriate locations.

Step-by-step description

1.
Fig. 1: Administration menu for operation administrator
Select 'Location Catalog' from the administration menu (cog wheel) in the top left corner of the screen (Fig. 1).
2.
Fig. 2: Location catalog screen
This will get you to the location catalog screen of the application (Fig. 2). The location catalog screen shows your location hierarchy tree on the right and a Google Earth map on the right.
NOTE Please note that depending on your connectivity and the size of your location catalog, it might take a while to start Google Earth and load your entire location catalog. Once the catalog has been downloaded, the location are drawn one-by-one. A progress bar will indicate the number of location that have been added to the map already. You are advised to wait until the entire catalog is drawn before proceeding to the next step.
3. Expand the location hierarchy tree on the right as required by clicking on the little plus (+) signs left of locations that contain other locations and navigate to the location you would like to edit. The locations are sorted by location type first and location name second.

Alternatively you can search your location catalog by clicking on the ButtonSearch.png button at the top of the location tree.

4.
Fig. 3: Location map in editing mode
Right click on the the location you want to edit. This will open a small menu with an edit option. To have access to this menu item, you need to be either an operation administrator or a super user. Select the edit option. This will replace the location tree with a location form filled with the information of the location to be edited and the map section will change from viewing to editing mode (Fig. 3).
NOTE Depending on the complexity of your location (i.e., number of points), it might take a while load your location in editing mode. You might even get an error message from Google Chrome informing you that the application is taking long to respond. Click on 'Wait for application' to continue.
ISSUE The drawing tools of the InfoEx application are currently unable to deal with geometries with more than 150 points. If you are trying to edit a location with more than 150 points, you will get an warning message from the application. The map will still go to editing mode, but the to be edited geometry will will shown without the circles in the corner points as shown in Fig. 3. See below for the available options for editing locations large number of corner points.
JIRA: - (Dec. 22, 2013)
5. Edit any of the information in the fields at the top of the pop-up window:
  • Name (required):
    Full name of the location
  • Abbreviation (required):
    Abbreviation to be used for the location in the tabular InfoEx reports.
  • Description (optional):
    Detailed description of the location
  • External ID (only accessible to super users):
    The external ID of a location is required if your operation submits their observations from an external database system via the API (see How to submit observation to the InfoEx via the CAAML 3.0.3 API for more information). The external ID is also required for locations that already existed in the legacy CAAML driven InfoEx and have historic observation associated with them.
  • Elevation (weather site only):
    Elevation of weather site in meters. When you create a new weather site, its elevation will automatically be extracted from the digital elevation model (DEM) of Google Earth. You can, however, overwrite the automatically created value.
NOTE Since locations are primarily referred to by name in the InfoEx system, it is not advisable to create multiple location of the same type with the same name. However, the system currently does not explicitly check for it.
6. If necessary, modify the geometry of the location.
7. Click on Update to commit the changes to the InfoEx system. This will submit the changes to the InfoEx database and change the mode of the location catalog back to viewing.

Related documents

Functionality tested by

  • Dec. 22, 2013: Pascal Haegeli