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 10, 2026, 10:20 PM

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.

Street Direction Change Requests (2019 - 2025)

9a6i-gcns

Fields catalogued

Understood

Checked, no match

Nobody has looked

Every field decided — Every field carries a verdict — which does not mean every field is understood.

Every field in this dataset

Covered and uncovered alike, in the order the publisher lists them. A field with no verdict is one nobody has looked at yet.

Field	Type	What we know	Meaning	How it was decided	Shared term
borough Borough	Text	Understood	place.borough Borough	value_domain_read	borough
type_of_request Type of Request	Text	Understood	category.classification Publisher classification	dictionary_read The change request type.	—
location Location	Text	Checked, no match	—	dictionary_read The street for the change request and the street names of the two closest intersections	—
request_status Request Status	Text	Understood	category.status Workflow status	dictionary_read The condition of the change request.	—
request_date Request Date	Calendar date	Understood	time.period.month Month	value_profile The date the request was received.	—
requested_by Requested by:	Text	Checked, no match	—	dictionary_read Identifies whether an individual or an organization made the street directional change request.	—