Street Decoding inconsistently fails

[qwo]

Example inputted as text to the service

150 Granby St 
fails no bus stop location

111 Granby St
Thanks your closest stop is ... 

Yeah, it definitely does that right now. I feel pretty certain this relates to how OpenStreetMap would search for the information, which means we may need to do some finagling with the input strings to get things done.

[qwo]

ive been looking at this for a bit and i stubbed out the where.Geocoder service. So your boundingbox + distance and all logic is solid!

OSM never returns the "right" granby st for specific POIs which is confusing to me and a bummer.

it is paginated by 10 results maybe we should ask for more but none of them are within the HR region.

[qwo]

mmm this feature might be too problematic with OSM where im going to take a look at another decoder strategy or maybe delay this feature.

It does sounds like a core feature so im gonna dig into this more.

[qwo]

bah OSM doesn't even have a relative hit on a major street might have to adopt an alternative

http://nominatim.openstreetmap.org/search/150%20granby%20st?format=json&addressdetails=1&country=us