Tree Map

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.

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 5/20/2019 12:00 PM and the rollup unit is Days and the rollup period is 7, then the data from 5/13/2019 12:00 PM to 5/20/2019 PM 12:00 PM will be combined into a rollup value and presented as a rectangle for each facility with valid data.

In the example above, 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.

Property Inheritance

Property Inheritance

Property inheritance is a widely used concept in Canvas. The application supports an explicit relationship between screens, objects, and controls, where certain property values, such as SiteService and facility tags, 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 SiteService and facility. Depending on how you have your screens, objects, and controls set up, the SiteService and facility may come from any one of the following sources:

• from itself — indicated by selecting <Self> and then explicitly configuring the property
• inherited from the screen — indicated by selecting Screen, which is always present as a sender
• inherited from another control — indicated by selecting the Name of the sending control

Broadcasting

Screens and objects support an additional notification option to broadcast their SiteService and facility selection changes to other open screens running in the Canvas or Canvas View application. If configured, a <Broadcast> option is available to source the screen's SiteService and facility 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:

Related Topics