Early-stage · two-person project

An open-data API for U.S. addresses.
Still early.

FastOpenData is a one-person project building a single clean API over U.S. geographic, demographic, and address data. One call geocodes an address, resolves it to its 2020 Census tract, and returns that tract's attributes along with its county's, state's, and PUMA's. The demo page runs it live, no account needed.

POST /structured_geocode — real, working today
# One address in, its tract's attributes out
curl -G https://fastopendata.com/address_data \
  -H "Authorization: Bearer $TOKEN" \
  --data-urlencode "street=350 5th Ave" \
  --data-urlencode "city=New York" \
  --data-urlencode "state=NY"

Response · actual shape
{
  "place_id": 127365481,
  "licence": "Data © OpenStreetMap contributors, ODbL 1.0",
  "osm_type": "way",
  "lat": 40.7484, "lon": -73.9857,
  "display_name": "350, 5th Avenue, Manhattan, New York, NY",
  "category": "building",
  "importance": 0.71
  // /structured_geocode returns this much: a thin pass-through
  // of Nominatim. /address_data goes on to the tract attributes.
}
v0.0.1
Alpha, pre-release
881
Attributes per address (tract, county, state, PUMA)
1
Person building it
8+
Datasets in the ETL pipeline
Where things actually stand

What's real today, and what's next.

Address lookups work end to end today. The schema, the dashboard, and anything resembling a product around them do not.

Live today

Address → tract → attributes.

Send a street, city and state; the address is geocoded, resolved to the 2020 Census tract that contains it, and returned with that tract's attributes plus its county's, state's and PUMA's. Geocode-only and tract-only endpoints exist too, for callers who want one step rather than all three.

Live, with caveats

881 columns, unevenly populated.

The columns come out of the ETL pipeline in this repo — Census ACS/PUMS, FEMA's National Risk Index, NCES schools, USDA rural–urban codes, CJARS, and more. Coverage is uneven: some columns are complete, some are null for most tracts, and several describe the surrounding PUMA rather than the tract itself. The response names which geography each one came from.

Not built

A schema endpoint, batch lookups, a dashboard.

There is no /fields endpoint describing the columns, no batch endpoint, and no account dashboard. The data catalog and pricing pages on this site are drafts, labeled as such.

Data catalog

Real ingestion code. Not a live catalog yet.

These are the actual datasets the ETL pipeline in this repo ingests. Several are already joined into address lookups; others are ingested but not yet exposed as columns. There is no endpoint that tells you which is which — that is the missing /fields endpoint.

See the planned field catalog

Early, and built in the open.

This is a two-person project, developed in public. If you want to see where it's headed or follow along as it grows, the source is the most honest place to look.