Grouping of observations within tables

From InfoEx Help Information
Revision as of 16:13, 1 January 2014 by Pascal (talk | contribs)
Jump to navigation Jump to search
REQUIREMENTS
Permission All user levels
Connectivity Online only

This page describes how observations within a table may be grouped in InfoEx reports.

Background

Users can group the rows of tables according to three preferences: range; operation; and, no preference.

Step-by-step-description

1.
Fig. 1: How to access the grouping options
To access the grouping options click on the Layout button in the upper right corner of the 'Reports' page (Fig. 1).
2.
Fig. 2: Settings box for the InfoEx report
A dropdown box will appear offering selections for the layout, grouping, and table types for the report that will be produced (Fig.2). For a description of selecting tables and layout see: Specifying the tables to be included in an InfoEx report and Single page view versus individual tabs for tables.
3. Under 'Group By' select the grouping option that you prefer. The grouping options will provide output as follows:
Range:
Fig. 3:Example of a report grouped by 'Range'
This option groups the report entries in each table by the mountain range of the location.
NOTE The mountain range of the location is decided automatically by comparing the location to a baseline map of predefined mountain ranges. If the location overlaps two defined mountain ranges it will be considered to lie in both.
Operation:
Fig. 4:Example of a report grouped by 'Operation'
This option groups the report entries in each table alphabetically by the operation name.
ISSUE Currently this sorting method does not sort locations alphabetically and some unexpected ordering can occur
JIRA: - SAFE-967 ( Oct 29, 2013)
None: This option groups the report entries by their default sort order that is assigned by the InfoEx administrator.

Related documents

Customizing reports

[1] Click to watch a help video
[2] Click to watch a help video

Managing report templates

Viewing report templates

Map Layers

Charts

Functionality tested by

  • Jan. 1, 2014: Pascal Haegeli