reverse geocoder overwrites best street answer with worst street answer

[robe]

Case in point: SELECT * from reverse_geocode(ST_Point(-71.22484166666666, 42.303448333333336) )

Was giving a primary answer of Highland Ave even though I- 95 is closer to the point. This is because the primary answer has no name (is a ramp), and the logic is intended to pick the next best street name assuming they are unnamed. Instead it replaces the best answer with the worst that has a street

[robe]

I'm debating if this is an issue. I think I'll just dismiss. With tiger 2015 data

test_tiger=# SELECT pprint_addy(addy[1]), street[1] from reverse_geocode(ST_Point(-71.22484166666666, 42.303448333333336) ) ;
       pprint_addy        |    street
--------------------------+--------------
 I- 95, Needham, MA 02494 | Highland Ave
(1 row)

And OSM shows this:

Given it's at the cross roads of the interstate around a ramp for Highland, I think this answer is fine.