Flow diagrams show relationships. They require a Flow Relational Model, which is just a mechanism used to define relationships within the data. Because of this dependency, Flow Diagram visualizations will only appear as an option off of Flow Relational Models.
Examples above show a Sankey Diagram (left) and a Chord Diagram (right).
There are two different types of Flow Diagram visualizations available in edgeSuite.
Sankey Diagrams show a horizontal flow through different Attributes, which are presented as separate columns of values. The size of each node in a column is scaled proportionally based on aggregated values defined in the underlying Flow Relational Model.
Chord Diagrams show a radial summary of values from all the Attributes, and highlight interconnectivity between those different values. The nodes along the outer radius are also scaled proportionally, based on aggregated values defined in the underlying Flow Relational Model.
Flow Diagram configuration is broken out into the following steps:
A symbolic name used to represent this Visualization. This is the name that will show up in choosers when adding a Visualization to a page.
This determines the type of Flow Diagram that will be rendered. Options are:
This determines whether an end user will be able to change the Diagram Type. Options are:
This determines whether or not to show default Tooltips on the nodes.
This determines whether or not to show default Tooltips on the links between nodes.
The Renderer step is broken out into two parts. The top section shows the attributes that have been related to one another in the Flow Relational Model. From here, you can adjust the colors of the values for each of the attributes, as well as the display name of the attribute itself.
This is the name of the attribute as defined in the relational model.
This property defaults to the raw attribute name, but it can be altered. It is used to display a different name that it will be more readable when presented.
This property sets a color scheme for each attribute. The values for an attribute will iterate through the colors defined in the color palette. If there are more unique values then colors, then the renderer will wrap and start over reusing colors in the same palette.
See Color Palettes for additional information.
The renderer only affects how elements are displayed. Since reordering the attributes affects aggregated counts, it must be done inside the relational model itself.
The bottom section on the Renderer Step contains global text renderers that affect all attributes.
Labels affect how individual values are rendered within the Visualizations.
Determines the font color of all labels. Selecting a color is done via the color input field. Clicking anywhere within the color input field will open the Color Picker.
Determines the font size of all labels.
Determines font style for all labels
For Chord Visualizations, labels will be hidden based on available space. For very dense data, users might not see any labels at all.
The Sankey Header Option section determines whether column headers will appear. If enabled, this section also determines what the headers will look like.
This determines whether or not Attribute Names are shown.
Determines the color of header values. See Color Picker.
Determines the font size of header values.
Determines the font style of header values.
Shows a preview of what the end Flow Diagram will look like.
Sample data can be found in edgeCore folder under data National Parks