The Tree Map is a CygNet-aware tool that can be used to display historical or real-time data as a set of relatively-sized and colored rectangles. Each rectangle has an area proportional to its numerical value. Several other configuration properties are supported, including: configurable date ranges, both relative and absolute; background, low range color, and high range color; display mode (best fit or vertically stacked); filtering to show only top or bottom items; and historical rollup values.
Note: The Tree Map will not display a rectangle for negative, zero, and non-numeric values. These unsupported values are converted to a value of 0.0 prior to being added to the Tree Map, removing them from the control’s display, but not from the underlying data collection. See Filter type for more information.
Historical rollups
The Tree Map supports the display of current values with historical rollups. With this type of rollup you need to designate that the Value type is Historical, configure the rollup properties (Rollup period, Rollup type, Rollup unit, and Top of subunit), and configure either a Start date and time or a Relative start date and time. For example, if the start date is 1/8/2024 12:00 PM and the rollup unit is Days and the rollup period is 7, then the data from 1/1/2024 12:00 PM to 1/8/2024 PM 12:00 PM will be combined into a rollup value and presented as a rectangle for each facility with valid data.
Tree Map Example
In the example below, both Tree Maps are receiving facilities from the Tag Chooser for meters in the selected division (LA), which is filtered by facility type (gas meter). The first Tree Map is filtered to display only the bottom 5 gas meters; the second Tree Map is displaying all gas meters in the division. In each Tree Map a gas meter has been selected and its values passed to the CygNet Grid below.
|
Sample Tree Maps driven by facilities selected in the Tag Chooser |
Property Inheritance
Property Inheritance
Property inheritance, or sending and receiving, is a widely used concept in Canvas. The application supports an explicit relationship between screens, objects, and controls, where certain property values, such as facilities and SiteService details, are passed from one element to another via an inheritance framework. Screens, objects, and controls can be configured as property senders or property receivers and provide configuration options where you can explicitly define the source of the facility and SiteService. Depending on how you have your screens, objects, and controls configured, the facility and SiteService may be received from any one of the following sources:
- from itself — indicated by selecting <Self> and then explicitly configuring the property
- received from the screen — indicated by selecting Screen, which is always present as a sender
- received from another control — indicated by selecting the Name of the sending control.
Broadcasting
Screens and objects support an additional notification option to broadcast their facility and SiteService selection changes to other open screens. If configured, a <Broadcast> option is available to source the screen's facility and SiteService properties from another open screen.
For example, a Text Tool can be configured to get its facility from the screen and the screen can be configured to get its facility from a Tag Chooser. Or Screen_A might source its facility from Screen_B, which gets its facility from a Tag Chooser.
Receiver or Sender
The Tree Map control supports property inheritance as a receiver and sender of its facility:
| Receive from | Send to | ||
|---|---|---|---|
| SiteService | Facility | SiteService | Facility |
| none | screen other controls |
none | screen other controls |
