There is a ticket now tracking this issue in our public issue tracker
and we'll post there when a fix is deployed. The URL for the ticket
is:
http://code.google.com/p/twitter-api/issues/detail?id=1930
Thanks for bearing with us whilst we track down what happened to the
radius and get a fix deployed.
Best
@themattharris
Developer Advocate, Twitter
http://twitter.com/themattharris
On Mon, Oct 11, 2010 at 7:26 AM, Taylor Singletary
wrote:
> Hi all,
> Yes, this is still an issue. We don't have an ETA on when it will be fixed.
> Thanks,
> Taylor
>
> On Sun, Oct 10, 2010 at 6:24 PM, bella wrote:
>>
>> I'm also very interested if there is an update on this.
>>
>> For me, it doesn't matter whether there is a q parameter or not.
>> If the geocode pararemter is used, only geotagged tweets are returned.
>>
>> http://search.twitter.com/search.json?geocode=-35.28204%2C149.12858%2C50.0km
>>
>> I get the same result when using the Advanced Search form (place:
>> Canberra, radius: 50km).
>>
>> Thanks,
>> Bella
>>
>>
>> On Oct 10, 6:55 pm, "Mack D. Male" wrote:
>> > Any update on this? It is still an issue.
>> >
>> > On Oct 7, 9:46 pm, Siim Saarlo wrote:
>> >
>> > > Hi,
>> >
>> > > Search API with location restriction (geocode parameter) used to
>> > > search through tweets that were geotagged and also tweets that were
>> > > tweeted by user who had set her location in profile settings.
>> > > Seems that currently search API, when both geocode and and q
>> > > parameters are set, only goes through the geotagged tweets. Although
>> > > seems that when only geocode is set, tweets are included by user'
>> > > location field as well.
>> > > I was told (by @twitterapi) that this is temporary situation to be
>> > > fixed soon.
>> >
>> > > 1) Can anyone suggest when will it probably be fixed? is there
>> > > alternative solution until then?
>> > > 2) I would like to try out Streams API' filter method, but it is
>> > > states that this only goes through geotagged tweets. Is there any
>> > > workaround to make frequent location specific searches through
>> > > geotagged tweets and also the ones that are not geotagged?
>> >
>> > > Thank you in advance,
>> >
>> > > siim
>>
>> --
>> Twitter developer documentation and resources: http://dev.twitter.com/doc
>> API updates via Twitter: http://twitter.com/twitterapi
>> Issues/Enhancements Tracker:
>> http://code.google.com/p/twitter-api/issues/list
>> Change your membership to this group:
>> http://groups.google.com/group/twitter-development-talk
>
> --
> Twitter developer documentation and resources: http://dev.twitter.com/doc
> API updates via Twitter: http://twitter.com/twitterapi
> Issues/Enhancements Tracker:
> http://code.google.com/p/twitter-api/issues/list
> Change your membership to this group:
> http://groups.google.com/group/twitter-development-talk
>
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
