Tiger Geocoder doesn't anticipate irregular spacing in road name

[arencambre]

The tx_edges table uses I- 635 instead of the more consistent I-635.

This looks weird but works:

SELECT ST_AsEWKT(geomout) FROM geocode_intersection('N. Belt Line', 'I- 635', 'TX', 'Coppell') ORDER BY rating ASC LIMIT 1;

This looks correct but doesn't work:

SELECT ST_AsEWKT(geomout) FROM geocode_intersection('N. Belt Line', 'I-635', 'TX', 'Coppell') ORDER BY rating ASC LIMIT 1;

Seems like the geocoder needs to work around these kind of errors in the Tiger data.

[robe]

yah -- may not be that trivial as spacing is used to designate separation of elements so putting logic like this in is libel to break something else without some extensive testing. I'll push to 2.1.0 but may get to it before then.