Loading…
Loading…
56,681 columns in the coverage ledger · read from /api/field-coverage on citytap-prod · source last observed Oct 10, 2026, 9:56 AM
3,026 datasets, 56,681 catalogued fields, 36,243 of them still unread. Every band below is a share of that, worst first. Open one to see its datasets.
How the city is doing at keeping its data current, by the city's own definitions, plus how far our mirror trails the source.
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.
A meaning was established for this field.
Somebody investigated and ruled the candidate meaning out. A result, not a gap.
Somebody investigated and the evidence did not settle it.
No verdict exists for this field yet.
We have not fetched their columns. That is a harvest gap, not an analysis gap — there is nothing to investigate until the fields arrive.
| Band | Datasets | Fields | Decided | Understood | In the web | |
|---|---|---|---|---|---|---|
| No field list yet | 603 | 0 | 0 — | 0 | 0 | See every dataset |
| Nothing read yet | 743 | 11,664 | 0 0.0% | 0 | 0 | See every dataset |
| Under half read | 1,308 | 26,920 | 5,056 18.8% | 2,584 | 588 | See every dataset |
| Half read | 241 | 4,975 | 3,108 62.5% | 1,233 | 178 | See every dataset |
| Most read | 92 | 12,017 | 11,169 92.9% | 582 | 52 | See every dataset |
| Every field decided | 39 | 1,105 | 1,105 100.0% | 88 | 5 | See every dataset |
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.
| Shared term | Datasets | Fields | Read | |
|---|---|---|---|---|
| borough | 555 | 632 | 632 100.0% | See every dataset |
| bin | 354 | 355 | 3 0.8% | See every dataset |
| council_district | 293 | 295 | 295 100.0% | See every dataset |
| zip | 197 | 199 | 199 100.0% | See every dataset |
| bbl | 193 | 205 | 205 100.0% | See every dataset |
| community_district | 190 | 207 | 207 100.0% | See every dataset |
| nta | 109 | 123 | 123 100.0% | See every dataset |
| agency | 48 | 50 | 49 98.0% | See every dataset |
| precinct | 41 | 41 | 41 100.0% | See every dataset |
| census_tract | 40 | 40 | 40 100.0% | See every dataset |
| school_district | 31 | 31 | 31 100.0% | See every dataset |
| month | 11 | 11 | 0 0.0% | See every dataset |
Gaps in the data behind this page
Source last observed Oct 10, 2026, 9:00 AM.
36,243 of the 56,681 columns in the coverage ledger have never been analysed.
36,243 / 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
1,677 of the 3,026 datasets in the catalog declare no update cadence.
1,677 / 3,026
Source: /api/scorecard
Check it yourself: /api/scorecard#/no_regular_updates
311 of the 3,026 datasets in the catalog are overdue against the cadence they declare.
311 / 3,026
Source: /api/scorecard
Check it yourself: /api/scorecard#/overdue_catalog
These pages state their own gaps: /datasets, /freshness, /scorecard, /scorecard/fields, /analyses, /ontology, /graph, /alerts, any topic page under /domains.