US Address Geocoder: Census Bureau Lookup
Pricing
Pay per usage
Go to Apify Store
US Address Geocoder: Census Bureau Lookup
Geocode US street addresses to coordinates and standardised components via the official US Census Bureau geocoder. No login, no proxy, no browser.
Pricing
Pay per usage
Rating
0.0
(0)
Developer
Naimur Hasan
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
5 days ago
Last modified
Categories
Share
US Address Geocoder
Geocodes US street addresses to coordinates and standardised components through the official US Census Bureau geocoder. No login, no proxy, no browser, no API key.
Input
| Field | Type | Notes |
|---|---|---|
addresses | array | Required. One-line US addresses, e.g. 1600 Pennsylvania Ave NW, Washington, DC. |
Output
One row per match: inputAddress, matchedAddress, latitude,
longitude, fromAddress, toAddress, preDirection, streetName,
suffixType, suffixDirection, city, state, zip, tigerLineId,
tigerLineSide.
Notes
- The API returns coordinates as
xandy, wherexis longitude andyis latitude. Reading them positionally in the wrong order is the classic way to land every US address in the Indian Ocean, so they are named explicitly here. inputAddressis kept next tomatchedAddressso you can see what the geocoder decided you meant. The match is standardised and uppercased, and it is not always the address you submitted.- An address can return more than one candidate match, so the row count can exceed the number submitted. Unmatched addresses are logged and skipped; the run only fails if nothing matched at all.
- Coverage is US-only, and
fromAddress/toAddressdescribe the block range the match sits in, not the building — this is street-segment interpolation, not rooftop accuracy. - The underlying TIGER data lags reality, so newer and corporate addresses can
legitimately return no match while the street around them geocodes fine —
1 Apple Park Way, Cupertino, CAis one such miss. Treat a no-match as "not in this dataset", not as "not a real address".
