Loading…

Coverage

46,873 of 56,681 columns decided — 82.7% · 9,148 bound (16.1%) · 9,808 still unread

Bound: 9,148; 16.1%; a concept was found and asserted for the column.
Refused: 29,070; 51.3%; the column was read and no concept fits. A verdict, not a gap.
Insufficient: 8,655; 15.3%; read, but the evidence did not settle it.
Unanalysed: 9,808; 17.3%; nobody has read this column yet.

56,681 columns in the coverage ledger · read from /api/field-coverage on citytap-prod · source last observed Oct 10, 2026, 3:51 PM

Where the unread columns are

3,026 datasets, 56,681 catalogued fields, 9,808 of them still unread. Every band below is a share of that, worst first. Open one to see its datasets.

Gaps in the data behind this page

9,808 of the 56,681 columns in the coverage ledger have never been analysed.
603 of the 3,026 datasets in the catalog list no columns at all.

Source last observed Oct 10, 2026, 3:51 PM.

Where each note comes from

9,808 of the 56,681 columns in the coverage ledger have never been analysed.
9,808 / 56,681
Source: /api/field-coverage
Check it yourself: /api/field-coverage#/coverage/unanalysed
603 of the 3,026 datasets in the catalog list no columns at all.
603 / 3,026
Source: /api/field-coverage
Check it yourself: /api/field-coverage#/catalog/datasets_no_inventory

These pages state their own gaps: /datasets, /freshness, /scorecard, /scorecard/fields, /analyses, /ontology, /graph, /alerts, any topic page under /domains.

What we have understood

Freshness above is about the data being current. This is about the data being understood: how many of the catalogue's fields carry a meaning we can act on, which datasets are still waiting, and how far the joinable web reaches.

← Citywide scorecard

Datasets by how much of them we have read

Filtered to datasets carrying bin. Clear

Datasets with the most fields left to read

Showing 1–7 of 7
Dataset	Fields	Decided	Understood	Nobody looked	Shared terms
Forestry Work Orders bdjm-n7q4	56	17 30%	4	39	2	See every field
NYC Clean Heat Dataset (Historical) 8isn-pgv3	42	8 19%	4	34	4	See every field
ACS Community Partners 9hyh-zkx9	39	13 33%	9	26	4	See every field
Verified Locations for NYC City-Funded Social Service Contracts - Sites y9si-s7ab	40	18 45%	7	22	4	See every field
NYC Pool Inspections 3kfa-rvez	23	11 48%	6	12	3	See every field
BP Appointments - BIDS pvxf-9irb	23	11 48%	5	12	5	See every field
DOHMH Indoor Environmental Complaints 9jgj-bmct	19	9 47%	5	10	4	See every field

The web of datasets and fields

A line means a dataset carries a field tagged with a shared vocabulary term. Two datasets on the same term speak the same language about it, which is what makes a cross-dataset question possible. Sharing a term is not the same as a working join — the dataset page says whether a specific pair compiles.

Bipartite. A dimension node is a conformed-dimension family; a dataset node is a catalog dataset; an edge means that dataset carries at least one column tagged with that dimension, and names the columns that carry it.

No field list yet: We hold no columns for these at all.
Nothing read yet: We hold their columns and have decided none of them.
Under half read: Fewer than half their fields carry a verdict.
Half read: At least half their fields carry a verdict.
Most read: At least three quarters of their fields carry a verdict.
Every field decided: Every field carries a verdict — which does not mean every field is understood.

How many of an edge's tagging columns carry a method that actually read something. Zero means the edge rests entirely on carried lexical tags.

Two datasets on the same dimension node share a vocabulary, which is weaker than a join. GET /api/datasets/{fourFour}/bindings/{partner} decides whether a specific pair compiles; executing it additionally needs both marts present.