as mentioned above, the source files came from 2009 TIGER web site: www2.census.gov/cgi-bin/shap...unty=47051
There were two files that I was looking at:
1. Address Ranges Relationship File (addr.dbf)
2. Feature Names Relationship File (featname.dbf).
I have not worked really deeply with TIGER data for about 10 years, but if I had to guess, edges.dbf does not necessarily represent the source of truth for geocoding - it represents the information needed to draw the line segments (and potentially the primary road name). So there is a potential for mutliple street/address ranges to be associated with one edge segment.
Some notes from looking census.gov/geo/www/tiger...RSHP09.pdf
Excerpt From page: 4-15:
• Address ranges in the TIGER/Line Shapefiles may be associated with one or more of the street names
that belong to an edge. Caution: Address range overlap conflicts may occur if the address ranges are
associated with some street names or route numbers that were not intended for use in locating
addresses. A route number may traverse several streets with similar house numbers but different
common names that are used for mail delivery. .
Excerpt From page: 4-17:
Geocoding—To get the best match results, the Census Bureau advises data users to use all of the
available address ranges to geo-reference/geocode addresses. A single pair of left- and right-side address
ranges may not always provide complete address range coverage. This limitation is also true for the most
inclusive address ranges as well. The address ranges in the TIGER/Line Shapefiles may be separated
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.
4.2 Address Range-Feature Name Relationships
Address range-to-feature name relationship information is available by county in the following relationship
Address Range-Feature Name Relationship File
The Address Range-Feature Name Relationship File contains a record for each address range-linear feature
name relationship. The purpose of this relationship file is to identify all street names associated with each
address range. An edge can have several feature names; an address range located on an edge can be
associated with one or any combination of the available feature names (an address range can be linked to
multiple feature names). The address range is identified by the address range identifier (ARID) attribute,
which can be used to link to the Address Ranges Relationship File. The linear feature name is identified by
the linear feature identifier (LINEARID) attribute that relates the address range back to the Feature Names
Relationship File (see Figure 5)
Based on Figure 5 relationships - to get full address ranges, you should have the following joins: edges to addr on TLID, addr to addrfn on ARID, and addrfn to featname on LINEARID. Once you have all those relationships established (as per TIGER documentation) you would end up with the correct set of address ranges and names - as described previously, for TLID 614844025 there are 8 unique address records