Tiger edge.shp is not the best source for geocoding.

[Troy-Yang]

Just note here: I read the Tiger data specification and it mentioned the best source for geocoding is the "addrfeat.shp" file instead of "Edge.shp".

I got some news from @lonvia "The address range data didn't exist when Tiger support was implemented, so that would count as feature request (i.e. somebody needs to program it)"

[netsgnut]

Stumbled upon this issue from osm-search/Nominatim#335. Just wanted to add a note here as well.

From the quoted relevant PDF (emphasis added for clarity).

To get the best geocoding match results in ArcGIS, the Census Bureau advises data users to use the Address Range Feature Shapefile (ADDRFEAT.shp) to geo-reference/geocode addresses. Address ranges in the MAF/TIGER database may be separated into multiple address ranges on the same edge because of ZIP Code differences or to establish gaps created by address anomalies located elsewhere. Some address ranges may also include embedded alphanumeric characters or hyphens that make them distinct from the other address ranges on the same edge side. The ADDRFEAT.shp contains all of the address range to edge and street name relationships for a county to increase the number of potential geocoding matches. In comparison, the most inclusive address range in the All Line shapefile (EDGES.shp) can also be used for geocoding but a single pair of left- and right-side address ranges and the primary street name on the edge may not always provide complete address range coverage.