REST API v1
Since today, we have noticed that search api with geocode is returning complete random results, sometimes working sometimes simply returning the most recent tweets from around the world. Please fix this, our application is getting very negative reviews because of this, I hope something is done before its too late
try a few times, would give complete random results, at some tries is correct, but most of the times is just returning all 100 irrelevant result
I am experiencing the same bug since Sep 23.
Our app had worked fine until then.
Search by lat / lng returns sometimes random locations now.
Facing same issue and also since 23rd. It is very critical for us to get this bug fixed.
yes we are also facing same problem. we are getting random results from 23rd sep .can it be fixed quickly....?
Can you indicate some more about how the results are wrong? Can you include an example query along with some tweet ids that were returned to you in the response that did not belong?
Do you normally specify an empty q= parameter when performing these searches rather than not including the parameter at all?
Originating poster: I assume that the location you were intending in the above query was within New York.
Thanks for any additional data you can provide.
i am giving geocode of india and i am getting tweets from newyork , london ,egypt and newzealana etc.
Could this bug be related to some "string to geo" parsing on user location? For example, we are seeing some tweets with user having a location set to "old montreal" that are assigned "ottawa" as location (ie. they pop up in search results using Ottawa lat/long and they should not).
Also, our volume of results have increased a lot in the last few days (almost +50% on some geo searches using lat/long + radius). This behavior started after the downtime of the search API last week.
Yes, its always been q= empty rather than not having the parameter at all and it used to work perfectly fine.
This issue seems to have been resolved now, I no longer get random results, I'm not sure if it was figured out or not, but if it was not, its a very scary situation for our location aware app.
There seems to be a few bugs in the search by geocode and I can totally understand why, there are so many different ways location is specified in tweets that it seems like a miracle on how it works.
Please see my previous report on a bug
It seems to be back to normal.
Search by lat / lng returns correct locations now.
Thank you !
I am using twitterizer as an interface to twitter but I am seeing random returns, if search for tweets from the following location and 1 mile radius I get 12 back "38.7326611204823,-104.718933105469,1mi", many of the tweets are outside this area, but I could live with that, but when I increase the radius to 5 miles "38.7326611204823,-104.718933105469,5mi" at the same location I get 2 tweets back, and non of the original 12. I can't make sense of what is going on.
Taylor. You may check the issue using http://metaki.com
This problem exists a lot of weeks ago but no body have solution any idea?
If you have the same problem, you may check it using http://metaki.com if you find a solution please share it!! thanks!
This topic is now closed. New replies are no longer allowed.