Difference between revisions of "Help:Specifying the default sort order of operations for the tabular InfoEx report"

From InfoEx Help Information
Jump to navigation Jump to search
(Step-by-step description)
(Related documents)
Line 73: Line 73:
  
 
==Related documents==
 
==Related documents==
* Link to relate document 1
+
* [[Help:Creating a new operation|Creating a new operation]]
* Link to relate document 2
 
  
 
==Functionality tested by==
 
==Functionality tested by==

Revision as of 16:17, 3 January 2014

REQUIREMENTS
Permission Super user
Connectivity Online only

This document describes how to specify and maintain the sort order location of an operation in the InfoEx reports.

Background

Historically, the operations in the InfoEx report were grouped by mountain range and sorted in a NW-SE direction. This resulted in a spatially meaningful report. While the new InfoEx system allows users to customize their InfoEx reports and specify any sort order, the default sort order of the classic InfoEx report is still in the NW to SE direction.

Fig. 1: Screen short of sorting zones in Google Earth (SortingZones.kml)

We have derived a coding system with five digits that allows the CAA manager of the InfoEx to specify the sort order of the report. The code consists of three parts:

  • InfoEx Region:

The first digit represent the large-scale InfoEx region. We have currently three regions defined:

    • Region 1: Coast Range, Yukon and Alaska
    • Region 2: Interior Ranges (Columbia Ranges and Rocky Mountains)
    • Region 3: Eastern Canada
InfoEx subscribers typically only belong to one of these regions.
  • Zone:
    Each InfoEx region has been divided into a number of zones that are numbered from north to south (Fig. 1). Digits two and three of the sort order represent the number of the zone (Region 1: 01 to 20; Region 2: 01 to 20; Region 3: only 01).
    Subscribers in the Whistler area, for example, have a code that starts with 116xx.
  • Local sorting:
    The last two digit of the sort order key (00 to 99) can be used to specify the small-scale sort order within an individual zone.
    In the Whistler area, for example, Whistler Heliskiing has a final code of 11610, Blackcomb Mountain 11620 and Whistler Mountain 11630 representing their relative positions from NW to SE. A new subscriber with a tenure between Whistler Heliskiing and Blackcomb Mountain could be slotted into the system with a 11615 code without having to adjust the codes of the neighbouring operations.

The combination of the three codes enables us to specify a default sort order for the InfoEx report that is flexible enough to easily accommodate new subscribers.

NOTE The sorting in the InfoEx system is done at the operation level. In other words, it is not possible to specify different sort order spots for individual locations of an operation even if they are spatially far apart. In this case, one has to choose a sort order spot for the operation that results in its location generally ending up in the right spot in the report.

Step-by-step description

Fig. 2: Saving the updated InfoExOperationsOverviewMap.kml
Fig. 3: Operation management page
Fig. 4: Operation pop-up window
1. Download the latest version of InfoExOperationsOverviewMap.kml and open the file in Google Earth. This file contains the operation areas of all InfoEx subscribers.
NOTE InfoExOperationsOverviewMap.kml needs to be maintained manually as it is currently not possible to download this information directly from the InfoEx application.
2. Add the operation area of the new subscriber operation to the InfoExOperationsOverviewMap.kml in Google Earth by dragging the label of its geometry into the 'Operation Overview Map' folder of the InfoExOperationsOverviewMap.kml file.
3. Right click on the InfoExOperationsOverviewMap.kml label in the location hierarchy in Google Earth (Fig. 2) and save the updated KML file to your local hardrive.
NOTE Ensure that you saved the file as a KML file as it is not possible to upload a KMZ to the wiki.
4. Go to File:InfoExOperationsOverviewMap.kml and click on the Upload a new version of this file link to upload the updated InfoExOperationsOverviewMap.kml to the wiki for future use.
5. Download SortingZones.kml and open the file as well in Google Earth. This file contains the labels and boundaries of the InfoEx sort order regions and zones.
NOTE You can permanently save this file in Google Earth by right clicking on its label in the location hierarchy as selecting 'Save to My Places'
6. Zoom to the operation area of the new operation and note the code of the sort region and zone the operation falls into.
7. Log into the InfoEx system with your super user account and go to the admin menu (cog wheel) in the top right concern of the application next to your user name and select 'Manage Operations'. This will get you to the Operation Management page that lists all the operations that are in the InfoEx system (Fig. 3).
8. Click on the header of the Sort Order column to sort the table by sort order.
9. Scan the table for the sort order of operations that fall into the same sort order region and zone (i.e., same first three digits) and determine how you want the new operation to fit within the order of the existing operations in this zone. Choose the last two digits of the five-digit code accordingly so that the new operation will fall into the desired location when the Sort order column is sorted numerically.
10. If you have not created the operation record yet, add the five digit sorting key when you create the operation. See Creating a new operation for more information.
11. If you have already created the operation record, click on it on the operation management table. The row will turn a pale yellow to indicate that you have selected the operation.
12. Click on the ButtonEdit.png button above the top left corner of the operation list. This will open a smaller pop-up window with the title 'Edit Operation' (Fig. 4). Enter the five-digit sorting key into the pop-up window.
13. Click on the Update button to submit the changes to the system.

Important files

Related documents

Functionality tested by

  • Jan. 3, 2013: Pascal Haegeli