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.

I get the same result when using the Advanced Search form (place:
Canberra, radius: 50km).


On Oct 10, 6:55 pm, "Mack D. Male" <master...@gmail.com> wrote:
> Any update on this? It is still an issue.
> On Oct 7, 9:46 pm, Siim Saarlo <siim.saa...@gmail.com> 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: 

Reply via email to