The Address Range relationship file often lists several address ranges for each edge. Which address ranges should I use to geocode addresses?
In many cases, the most-inclusive address ranges (found in the All Lines shapefiles) may cover the available address ranges for an edge. However, the Census Bureau advises data users to use all of the available address ranges to geo-reference/geocode addresses for the best possible results. A single pair of left- and right-side address range may not always provide complete address range coverage. The address ranges in the TIGER/Line Shapefiles may be separate because of ZIP Code differences or to establish gaps created by out-of-sequence addresses located elsewhere. Some address ranges may include embedded alphanumeric characters or hyphens that make them distinct from the other address ranges. Only using one of the available address ranges will significantly lower the overall address match success rate.
Related Questions
- The Address Range relationship file often lists several address ranges for each edge. Which address ranges should I use to geocode addresses?
- Can SeekData geocode my Puerto Rican address data when some addresses contain KM and HM markers?
- Why is the CMEM heap buffer address not within my specified range of CMEM physical addresses?
