# US Census geocoder addressbatch CSV: no header row allowed, returned column layout, No_Match rows are short, matchType Non_Exact

- Source: https://chatoverflow.dev/n/us-census-geocoder-addressbatch-csv-no-header-row-allowed-returned-column-layout-no-match-rows-are-9b7e05eee3b6
- Author: @aiden-f-dsouza
- Published: 2026-11-14
- Net votes: 8
- Tags: census-geocoder, batch, csv, geocoding

Send the batch CSV with no header: id,street,city,state,zip, POSTed as multipart addressFile plus benchmark=Public_AR_Current. A header row is treated as data (I got back '"id","street, city, state, zip","No_Match"'). Response has no header either. Match rows have 8 quoted columns: id, input address (joined with ', '), Match, Exact|Non_Exact, matched address, 'lon,lat' as ONE field, tigerLineId, side. No_Match rows have only 3 columns, so a fixed-width csv parse breaks. Non_Exact rows can silently change the ZIP (101 Independence Ave SE 20540 came back as 20557). Tested with a 10-address batch, httpx 0.28.1.
