Viewing a saved revision (read-only)
Hh_QypAbjff6duuUTo9e2
Created from react-d3-starter template
Language Influence Edges — Force-Directed Graph
An interactive, responsive force-directed network visualization of a directed "influenced by" graph between programming/formal languages, built with React + D3.
1. Datasets
data/influence_edges.csv
| Property | Value |
|---|---|
| Path (runtime) | /data/influence_edges.csv |
| Size (bytes) | 78,242 |
| Rows (records, excluding header) | 1,000 |
| Format | CSV, header is the first record; some cells may be quoted and contain embedded newlines, so the header must be parsed with a real CSV parser (D3 csv() is used). |
| Apparent subject | Directed edges of the form language ← influenced_by, i.e. "language was influenced by influenced_by". |
Columns
| Column | Parsed type (observed) | Missing | Distinct | Tentative meaning | Munzner class |
|---|---|---|---|---|---|
language |
string | 0 | 358 | Display name of the influenced (target) language. | Nominal (identifier / label) |
language_id |
string | 0 | 360 | Canonical identifier for the language entity. Looks like a URL slug (/en/cplusplus) or a legacy key (/wikipedia/fr_id/1711). |
Nominal (identifier) |
influenced_by |
string | 0 | 233 | Display name of the influencing (source) language. | Nominal (identifier / label) |
influenced_by_id |
string | 0 | 234 | Canonical identifier for the influenced_by entity. Same shape as language_id. |
Nominal (identifier) |
Grain. One row = one directed influence edge: influenced_by → language
(i.e. language depends on / was influenced by influenced_by). A single
language appears in many rows (one per incoming influence). The pair
(language_id, influenced_by_id) is the edge key; it is unique in the sample
inspected.
Cardinality observations (from the supplied profiles).
languagenames: 358 distinct, butlanguage_id: 360 distinct.influenced_bynames: 233 distinct, butinfluenced_by_id: 234 distinct.
These two mismatches mean that name and id are not 1:1:
- A single name can map to two ids (e.g. two language variants share a display name but have different canonical keys), and/or
- A single id can map to more than one name (aliasing / redirects).
Because of this, the visualization treats *_id as the entity key and
* (name) as the display label, resolving the label from the id by picking
the most frequent name observed for that id. This is a documented,
deterministic assumption — not a claim that name and id are equivalent keys.
Parsing assumptions.
- No numeric or temporal fields exist; every column is a string.
- No missing values were reported (missing count 0 for all four columns).
- Empty strings, if any, would be dropped as invalid nodes.
- No date/time, geographic coordinates, or geographic identifiers are present.
- Ordinal and quantitative encodings are therefore not applicable.
Relationships and join keys (verified vs. assumed)
- Self-relationship (intra-dataset). The dataset encodes a directed graph
whose node set is the union of
language_idvalues andinfluenced_by_idvalues. An edge(language_id, influenced_by_id)connects the two nodes; direction is influenced_by → language (source influences target). - Join key candidate (verified shape, unverified semantics).
language_idandinfluenced_by_idshare the same string shape (/en/<slug>or/wikipedia/<locale>_id/<number>). They can be used as node keys within this single dataset because they union into one node namespace. This is an assumption within this dataset only. No other dataset is present, so no cross-dataset joins are attempted or claimed. - Caveat.
language/language_idandinfluenced_by/influenced_by_idare not independent columns to be joined blindly; they are the two halves of one edge. Joining them to each other would produce garbage. They are only combined after reducing each id to the node namespace of the graph.
2. Visualization
Chosen visualization type
A force-directed directed graph (node-link diagram) rendered on a single SVG, with an interactive hover highlight that isolates a node's in-neighbors and out-neighbors.
Why this type
- The data is a directed relation between two nominal entities; a node-link layout is the canonical, defensible encoding for relational nominal data.
- A force layout surfaces hubs (languages that influenced many others) and bridges without hand-tuned coordinates.
- Hover isolation gives immediate, unambiguous reading of an individual node's neighborhood — the single most useful interaction for a 300+ node graph.
Mappings
| Data field | Role | Encoding |
|---|---|---|
node id (from language_id ∪ influenced_by_id) |
entity | force-simulation node identity; stable across renders |
| node label (most-common observed name for that id) | label | text node, faded until hover |
edge (influenced_by_id → language_id) |
relation | SVG line from source to target |
| in-degree (count of incoming influence edges) | quantitative attribute | node radius via scaleSqrt; node color via sequential scale |
| hovered node's incident edges | interaction state | opacity 1 while others fade to 0.06 |
Interactions
- Hover a node — dims all unrelated edges/nodes; highlights the hovered node, its direct neighbors, and the connecting edges. A small label appears under the hovered node showing its display name and edge count.
- Hover away — restores the full graph.
- Resize — the
ResizeObserverhook re-runs the layout in the new viewport so the graph re-centers and re-scales without distortion.
Rationale for decisions
scaleSqrton radius is used so area, not radius, is proportional to in-degree — the standard perceptual correction.- Node opacity is kept low by default so dense regions remain readable; hover is the primary reading mechanism rather than tooltips stacked on a busy plot.
- Direction is encoded geometrically, not with arrowheads, because arrowheads clutter a graph with thousands of crossings; the direction convention (influenced_by → language) is documented here and in a caption.
3. Files
index.html— page shell and import map (React + D3 from CDN). Unchanged.index.jsx— mounts<App />. Unchanged.App.jsx— loads the CSV, builds the graph, drives the viz.viz.js— D3 render entry point (force simulation + hover).useContainerDimensions.js— tracks container size. Unchanged.styles.css— page and graph styles.README.md— this file.
Removed: renderCircles.js and data.csv (starter-placeholder files no
longer used; the visualization loads /data/influence_edges.csv at runtime).