cross streets shouldn't always start with "at"

GoogleCodeExporter commented 9 years ago

What steps will reproduce the problem?
1. look at some nearby venues that have cross streets but begin with
"between/btw" or "in" 

What is the expected output? What do you see instead?
I wouldn't expect to see "at" before words like "between" or "btw" so it
says "at btw N 42nd st" or "at in east corner of parking lot"

What version of the product are you using? On what operating system?
2009-08-11

Please provide any additional information below.

Original issue reported on code.google.com by mitch.fi...@gmail.com on 24 Aug 2009 at 5:45

GoogleCodeExporter commented 9 years ago

This issue was closed by revision adb6c57bf2.

Original comment by jlapenna on 24 Aug 2009 at 4:59

Changed state: Fixed

GoogleCodeExporter commented 9 years ago

Issue 59 has been merged into this issue.

Original comment by jlapenna on 29 Aug 2009 at 6:38

GoogleCodeExporter commented 9 years ago

This issue was closed by revision adb6c57bf2.

Original comment by jlapenna on 5 Jan 2010 at 5:47

kitencx / foursquared

cross streets shouldn't always start with "at" #51