§00
About
Corrections
Errors are logged here with what was wrong and what it affected. A site whose entire value is that its figures are traceable does not get to quietly fix things.
§01
How an error is handled
- If the source published it wrong, the figure stays as published and the discrepancy is noted. This site does not correct an agency’s data — that would break traceability.
- If this site introduced it, the connector is fixed, the affected records are reingested, and the change is logged below.
- If a figure is right but presented misleadingly, the presentation changes and that is logged too. Three of the five entries below are exactly that.
§02
Log
Most recent first.
| Date | Area | What was wrong |
|---|---|---|
| 2026-08-17 | Rankings | Ranks ignored each measure's direction, so “0 measures worse than national” — the best possible score — was ranked 2,296th of 2,977. Ranking now honours the direction declared with the measure. |
| 2026-08-17 | Rankings | A rank was shown without its ties, so each of the 384 hospitals holding a five-star CMS rating was told it ranked first nationally. Tie counts are now stored and always displayed. |
| 2026-08-17 | State pages | Rating statistics were computed from the 40 rows displayed rather than the whole state. Minnesota showed “40 of 40 rated, average 3.9” when the correct figures were 56 of 136 at 3.77. |
| 2026-08-17 | Geography | Land area was discarded for all 3,291 geographies because the Census API returns it as a string and the type guard rejected it. Pages showed an em dash, which read as “not published” rather than “lost in ingest”. |
| 2026-08-17 | Federal spending | USAspending keys its state layer by postal abbreviation and its county layer by FIPS. State rows matched nothing until translated, so only 1 of 56 states received a population figure. |