I have problems trying making queries as:
http://search.twitter.com/search.json?geocode=37.781157,-122.398720,1mi
The results allways:
{results:[],max_id:9449483417488384,since_id:
9449483417488384,refresh_url:?
since_id=9449483417488384q=,results_per_page:15,page:
Hello,
Since a few days it seems that search restricted by geolocation and
search radius is not working correctly anymore.
If I submit this request:
http://search.twitter.com/search.json?geocode=52.360773%2C4.871720%2C1kmrpp=100
I expect all resuls to originate from a geocode within 1km radius
We have a bug right now effecting exactly these kinds of searches. I'm not
sure how quickly it will be fixed, but I'm hoping it will be early next
week. I don't think there are any functional workarounds besides merging
multiple searches.
Sorry about the mess!
Taylor
On Fri, Sep 24, 2010 at
Dear all,
from today Search API's geocode parameter (http://apiwiki.twitter.com/
Twitter-Search-API-Method%3A-search) does not work anymore. It only
shows an error:
hash
errorCouldn't find Status with ID=2954291578/error
/hash
Example link:
Did the geocode operator stop working?
I just tried a couple of geocoded searches and got back 0 results.
Here is a search for San Francisco, CA within 15 miles.
curl
http://search.twitter.com/search.json?q=geocode%3A37.779160%2C-122.420049%2C15m
Users are complaining to me as well, so I know
