Loading…

Coverage

56,681 of 56,681 columns decided — 100.0% · 12,642 bound (22.3%) · 0 still unread

Bound: 12,642; 22.3%; a concept was found and asserted for the column.
Refused: 32,953; 58.1%; the column was read and no concept fits. A verdict, not a gap.
Insufficient: 11,086; 19.6%; read, but the evidence did not settle it.
Unanalysed: 0; 0.0%; 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 11, 2026, 1:21 AM

Where the unread columns are

3,026 datasets, 56,681 catalogued fields, 0 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

603 of the 3,026 datasets in the catalog list no columns at all.

Source last observed Oct 11, 2026, 1:21 AM.

Where each note comes from

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 nta. Clear

Datasets with the most fields left to read

Showing 101–109 of 109
Dataset	Fields	Decided	Understood	Shared terms
2010 Census Tracts (water areas included) ht7m-2uh6	12	12 100%	4	2	See every field
Pedestrian Zone Shapefile (Tabular) kcrr-myj9	12	12 100%	4	2	See every field
Verified Locations for NYC City-Funded Social Service Contracts FY2018 (Location) 29km-avyc	11	11 100%	7	5	See every field
Hyperlocal Temperature Monitoring qdq3-9eqn	10	10 100%	6	2	See every field
Emergency Food Supply Gap 4kc9-zrs2	9	9 100%	1	1	See every field
NYC Climate Budgeting Report: Resiliency Exposure Forecast - Outdoor Heat 95zn-7w5f	8	8 100%	2	1	See every field
CPI_Zones sidw-jf8y	8	8 100%	3	2	See every field
NYC Climate Budgeting Report: Resiliency Exposure Inventory dpq6-sy7w	7	7 100%	3	1	See every field
New York City Population By Neighborhood Tabulation Areas swpk-hqdp	6	6 100%	3	2	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.