Add optional bounding_region arg to geocode function

[robe]

This is again both a precision and time savings.

Often times for regional geocodes where everyone is assuming we are talking about Boston or a specific neighborhood, they just give you an address with no city or zip and often times even no state.

This optional arg will allow you to pass in a bounding region which could be as simple as a bounding box or as complex as a neighborhood and immediately reject all results that do not intersect the region.

This should save both time in that we can skip a whole bunch of zip, county etc checks and also achieve better results since I won't be getting stuff in Lexington, MA when all I care about is Boston, MA.

[mikepease]

This sounds like a great feature to me! Most of my data is the Twin Cities metro area. If I could pass in a polygon of the boundaries of the metro, or of Minneapolis, or of some other known territory, that would be great. I think that would really help in validating my geocodes. I look forward to this!

[robe]

done at r7620