nobody owns america's addresses

Problem statement

An address point — a street address tied to a coordinate — is foundational data for emergency dispatch, mail, elections, broadband mapping, disaster response, and the census, yet the United States has no complete, authoritative, public national address dataset. Addresses are assigned by tribal and local governments (counties, cities, 911 authorities), aggregated (sometimes) at state level, and contributed (voluntarily) to the U.S. Department of Transportation's National Address Database (NAD), which began in 2015; as the FGDC/NSGIC white paper puts it, "Participation in the NAD is completely voluntary" and "not all states with address data have been able to become NAD partners. In some cases, there are policies in place that restrict data from being shared publicly." The unsolved problem is not technical — the schema exists (DOT's NAD schema, NENA's NG911 data model) and most jurisdictions have digital address points — but institutional: thousands of data owners with no mandate, uneven capacity, and in some cases a legal or cultural refusal to release data into the public domain.

Why this matters

Next Generation 911 routes emergency calls geospatially, so a missing or wrong address point is a mis-routed ambulance; the white paper lists NG911, broadband service mapping, elections, damage assessment, and pandemic vaccination siting as uses that all depend on the same layer. Because the layer is incomplete, every federal program and every company builds or buys its own — Kentucky's dispatch centers reported being "tired of fielding calls from companies in search of authoritative address points data" — duplicating effort and propagating inconsistent addresses. Rural and tribal areas, where address data are least likely to exist digitally, are precisely where emergency response and broadband funding decisions most need them.

What’s been tried and why it hasn’t worked

DOT's NAD initiative (2015–) built the national aggregation pipeline and a partner map — the "map of shame," as one state GIO called it — and by mid-2026 publishes a quarterly national release compiled from partner submissions; the FGDC Address Theme and the Geospatial Data Act of 2018 gave addresses formal status as a national data theme; and NG911 grant funding drove many states to build statewide address layers. But the white paper's three case studies show why coverage remains partial. Kentucky's GIS office documented for years that address points were the top-priority missing layer, found the locally maintained data "incomplete, outdated, and erroneous," and watched a state 911 board consultant aggregate the data without sharing it — a board member said, "This isn't a map sharing program and each PSAP only cares about their area"; the deadlock broke only in 2019–2022 when new legislation, a new administrator, federal NG911 grants, and an administrative rule tying PSAP funding to quarterly data submission were all in place. Kansas built a federated statewide layer but its NG911 data are governed by MOUs under which "the decision to share data beyond the approved users lies with each jurisdiction," so as of the paper only 81 of 105 counties had agreed to release to the NAD. Arizona succeeded through more than a year of outreach and by using broadband grants to fund rural data creation, yet "still experiences challenges with statewide aggregation and there are gaps in the data due to some local data providers that are not comfortable with sharing," plus "duplicative data sets developed independently to serve different purposes" where the authoritative source is unclear. The pattern is that success required a state-level champion, a funding lever, and a legal instrument all at once — and most states have not assembled all three.

What would unlock progress

The unlock is institutional design rather than mapping: an incentive or mandate structure that makes contribution the default (e.g., conditioning federal 911, broadband, or transportation grants on public-domain address submission, as Kentucky did with PSAP funding), model MOU/statutory language that lets jurisdictions release address points while retaining ownership, and lightweight tooling that lets a small county publish NAD-conformant data without a GIS department. Adjacent precedents worth studying: volunteer address-aggregation projects show the demand and the technical ease, and countries with a nationally governed address register (Canada's National Address Register is one) show the end state — but each depends on a mandate or convening authority the U.S. lacks. A conformance-and-feedback loop ("more eyes on the data with a feedback mechanism, the better the data would become for all users," as Arizona found) turns contribution from a cost into a service.

Entry points for student teams

A GIS/software team could pick one non-contributing county or tribe and build the pipeline that converts its existing address records into the NAD schema, measures conformance, and returns an error report — a working prototype of the "publish without a GIS department" tool. A policy team could inventory the legal barriers state by state (which statutes or MOUs put address points outside the public domain, and what language the contributing states used to get past them) and draft model legislation or grant conditions. A data team could quantify the gap — compare NAD coverage against Census housing-unit counts by county to map where the missing addresses are and who is affected. Relevant skills: GIS, public administration and law, data engineering, civic technology.