The graph of the storm, and its ontology

One graph of Storm Charles: who decided and warned what, when, what was reported, where it was read, and which agent keeps which dataset. Kept by incident.graph@web-summit.dinis. Built from the incident's JSON files by tools/graph-build.mjs, never by hand. Not a warning service: the graph records what the authorities decided and warned and when we read it; follow IPMA and ANEPC.

Files

File	What
ontology.json	the eight kinds of thing and eight relations below; the builder refuses anything else
storm.json	the graph: `nodes[]` and `edges[]` (one per line), `counts`, `built_from` (each input file with its sha256). Lisbon, the decisions and everything else
storm-elsewhere.json	the rest of the graph, same shape: the warnings in force in the other districts, and those districts; its edges point into `storm.json`
tables/timeline.json	the lead-time line: every warning and decision with a time known to the minute, in order, with the hours between them and before the red warnings start
tables/decisions.json	decisions and issued warnings: by whom, what, when, status, what each followed
tables/warnings.json	warnings: issued, in force (type, level, area, start, end), and the history of when each was first seen
tables/signals.json	the timeline, one row per signal, with its publisher
tables/sources.json	every URL read, its publisher, how often it is cited
tables/actors.json	bodies, operators, the organiser, outlets
ref/ipma-areas.json	IPMA's warning areas by code (names and coordinates), from IPMA's own list
queries.json	the worked SQL queries of the query page

The ontology on one page

Every node and every edge carries four things: label (fact, evidence or hypothesis), source (an https URL), read (the UTC time it was read) and origin (the file and place it was built from).

Kind of thing	What it is	Built from
Actor	someone who decides, warns or reports; `kind` is `body` (an authority, the government, a municipality), `operator` (transport, a venue, schools), `organiser` (Web Summit) or `outlet` (press and public social platforms)	`decisions/graph.json` nodes; outlets from the hosts of cited URLs
Decision	something an actor decided, or has not yet announced (`status`)	`decisions/graph.json` edges
Warning	a warning from a body that warns: `issued`, `in_force`, or `cap` (IPMA's own message, with the time IPMA sent it)	IPMA's and ANEPC's edges; `weather/warnings.json`; `weather/cap.json`
Signal	a row of the timeline: something published, said or observed	`signals.json`
Source	a URL that was read	`decisions/sources.json`; any other cited URL; the pages covering the storm (`research/weather-sites/sites.json`)
Place	where a warning applies: an IPMA area, mainland Portugal	`weather/warnings.json`; `ref/ipma-areas.json`
Dataset	a JSON file of the incident	the files under the incident's `data/`
Agent	an agent or desk that reads sources and keeps datasets	`data/keys.json`; `read_by` in the datasets

Relation	From, to	Meaning
`decides`	Actor, Decision	the actor made (or owes) the decision
`warns`	Actor, Warning	the body issued the warning
`reports`	Actor, Signal or Decision or Warning	the actor published it
`cites`	Decision or Warning or Signal, Source	it was read at this URL, or is corroborated by it
`precedes`	Decision or Warning, Decision or Warning	time order between two linked items, with `lead_minutes` when both times are known to the minute. Order, not cause
`affects`	Decision or Warning, Actor	whom the decision touches
`located-in`	Warning or Place, Place	a warning's area; a district in the mainland
`produced-by`	Dataset or Source, Agent or Actor	who keeps a dataset; whose channel a source is

Labels. A fact was read on the channel of the body that decides or warns. Evidence is reported by others, with its source. A hypothesis is our analysis, with its reasons, never stated as fact. A derived item takes the label of the item it came from; an outlet, a place, a dataset or an agent is a fact about the file or URL that names it.

Not in the graph: people. No private person is a node; journalists and officials are not modelled here. Forecast values and observations stay in weather/*.json: the graph links the dataset, not each number.

One hand-kept list: own_channels in the ontology (seven hosts that are plainly an actor's own, two that are never outlets). Everything else is derived.

Build

node tools/graph-build.mjs            # writes storm.json and tables/*.json
node tools/graph-build.mjs --check    # exits 1 if they are not what the inputs give
node tools/graph-build.mjs --out DIR  # writes DIR/data/graph/... only; no tracked file is touched (the build: --out _site)

The output has no clock in it: the same inputs give the same bytes; as_of is the newest time in the inputs. In storm.json a node is short (a name of at most 140 characters); the long text is in the tables, joined by id. Each file stays under 256 KB (the builder stops if one would not).

Use it

Query it in the browser (SQL, no server, eight worked questions): the query page.
See it: the graph page (3D, on the engine of web-summit.sgit.ai's Universe, and as a list).
Read it as an agent: fetch storm.json; follow origin back to the file each item came from, and source to where it was read.