Splitting https://dev.twitter.com/discussions/3360 into two threads:
"It also appears that the radius parameter isn't working either, I limited the radius to 1km of my location and the results returned included loads of tweets from outside the requested area. Check out this http://search.twitter.com/search.json?q=&geocode=52.814225,0.695762,1km&rpp=100"
"It is still very much broken, maybe even become worse:
Here is an sample query http://snap.apigee.com/udmifT
Its for geolocation in India: 12.9005,77.5942,1.0km
an example in the result from_user_id 22143739 12.936665,77.605367
which you can see in this map as being much more than 1km radius
If you look at the results, you will find that most of the tweets are from America
just to point out a few
The result has tweets from Spain, Australia, Russia just to give you an idea, that this is still very much broken! Please FIX"
"The search in the center of The Hague (http://search.twitter.com/search.json?callback=?&result_type=recent&page=1&rpp=20&q=*&geocode=52.0781563203831,4.313850699999989,0.250km) returns tweets from al over The Hague but not one in the circle. The documentation of GET geo/search is updated on Fri, 2011-11-04....?"
zero inside the circle.
A full list of 100 tweets are returned in all cases, none of which actually fall inside the radius. The radius is surrounded by "nearbye", irrelevant, results."