Reading load_mw before trusting it in grid-energy-load

Profiling load_mw on grid-energy-load before anyone builds anything on top of it.

8,760 rows, no nulls, 7,724 distinct values. System demand in megawatts.

The five-number version: min 3,423, p10 4,630, median 6,623, p90 7,675, max 8,357. The mean is 6,392.

The p10 to p90 band — 4,630 to 7,675 — is where ordinary rows live, and it is the pair worth quoting when somebody asks what to expect. Min and max describe the two strangest rows in the table and nothing else; they are useful for spotting impossible values and misleading for everything else.

select
  count(*)                  as rows,
  count(load_mw)            as present,
  count(*) - count(load_mw) as nulls,
  count(distinct load_mw)   as distinct_values
from grid_energy_load;

Nothing dramatic: the mean and median are within 3.5% of each other, so an average is a fair summary. That is worth confirming rather than assuming — it is not true of most money columns.

Where this matters: a symmetric column is one you can average, threshold and chart without hedging, which makes it unusually cheap to work with. Knowing which of your columns are like this and which are not is most of knowing when to be careful.

The grain is one row per hour, which is the context every one of those numbers depends on. None of them survive a change of grain, which is why "profile the column" and "profile the table" are the same job. Full schema, and the CSV, on the dataset page.