Reference Data Sets

The follow items describe the reference data layers that are used to computed geocodes within the TAMU Geocoder.

---

Reference Data Sources

Boundary Solutions 2012 National Parcel File

2010 US Census Bureau TIGER/Line Files

Edges

Places

Cities

Consolidated Cities

Zip Code Tabulation Area (ZCTA)

County Sub Regions

Counties

States

2008 US Census Bureau TIGER/Line Files

Edges

Places

Cities

Consolidated Cities

Zip Code Tabulation Area (ZCTA)

County Sub Regions

Counties

States

2005 US Census Bureau TIGER/Line Files

Edges

2000 US Census Bureau Cartographic Boundary Files

Places

Cities

Zip Code Tabulation Area (ZCTA)

Counties

Los Angeles County Assessor’s Parcel Files

USPS Tiger/ZIP + 4 Files

If you have other reference data sets you would like to use for and/or contribute to the geocoding process on this site, we can incorporate them. Please contact us for more information.

Reference Feature Geometry

Including this option in either the batch processing or API will result in the geometry of the reference feature used for interpolation being returned along with the geocode result. This option is only appliable when using the API in verbose mode, or when the optional reference feature fields are selected in a batch process. It is not recomended that this option be selected unless you have a specirfic need for the underlying reference feature geometry.

You can always return to the site and easily get the reference feature geometry for any specific geocode of interest.

Why not to include the reference feature geometry as output

Geometry format	The geometry of the reference feature will be reported in OGC GML
Geometry text size	OGC GML is extremely verbose. This means that there will be a lot text returned if the geometry is a complex object such as a ZIP code, city or state
CSV files in batch mode (and TSV)	CSV files may become unusable due to the amount of text returned for a GML geometry
Access database files in batch mode (mdb and accdb)	Access data files may grow beyond the maximum file size of 2GB and become unusable due to the amount of text returned for a GML geometry