Relationship

Hive plot

Positions network nodes on attribute-defined axes and connects their links.

  • Diagram
  • Relationship
  • Structure

What it answers

How do connections relate to node attributes?

Shape
Nodes on radial axes with curved links
What it shows
Between-type links and attribute-based structure.

Example

The question

How are links spread between suppliers, factories and customers?

Supply links on three axes (hive plot)

Supply links on three axes (hive plot)Three axes for suppliers, factories and customers; each dot is one, placed further out the more orders it handles, and curves join linked pairs. Links spread evenly with no single dominant hub.SuppliersFactoriesCustomersNodes sit on three axes,further out = more orders;curves are supply links
Supply links on three axes (hive plot)Three axes for suppliers, factories and customers; each dot is one, placed further out the more orders it handles, and curves join linked pairs. Links spread evenly with no single dominant hub.SuppliersFactoriesCustomers
Three axes for suppliers, factories and customers; each dot is one, placed further out the more orders it handles, and curves join linked pairs. Links spread evenly with no single dominant hub.

Illustrative data. It belongs to no company.

When to use it

Use it when

Comparing networks with explicit attribute-based layout.

Avoid it when

When axis assignment has no analytical meaning.

How to read it

Read each radial axis definition and position before following links.

Note

Specify axis assignment and position rules.

The data you need

Layout
Two linked tables
Fields
Edges: Source,Target; Nodes: NodeID,AxisGroup,Position
One row is
One relationship in the edge table; one axis assignment and position per node. What is the grain?
Rules
Every edge endpoint must exist in Nodes. Define how attributes determine axis and position.
Optional
Separate Nodes table: NodeID,Label,Type. Include isolated nodes there.
Preparation
Resolve node identities and endpoint joins; define direction and duplicate/self-link handling. Aggregate weights only under a stated relationship or flow definition.
Units
Unweighted links encode presence. Weights need a unit; flow shares divide by stated source, destination or network totals, not an assumed common denominator.
Example of the input layout: Two linked tablesTwo linked tables, joined by a shared key column.KeyValueABCKeyDetailABC
Two linked tables, joined by a shared key column.

Worked example

NodeA is on Input axis at 1; B on Output at 2; edgeA-B joins them. Position comes from supplied attributes, not simulated distance.

Nodes: NodeIDAxisGroupPosition
AInput1
BOutput2
Edges: SourceTarget
AB