This is by design for the Search API. When a Tweet doesn't include any Geo information the Search API will instead use the location in the users profile.
The Streaming API looks only for Geo information on a Tweet and ignores the user location. If the users location is not important to you this may be a better solution. Best, @themattharris Developer Advocate, Twitter http://twitter.com/themattharris On Sun, Oct 17, 2010 at 2:41 PM, Daniel <daniel.a...@gmail.com> wrote: > the issue is still happening... You could check it at http://metaki.com > > Some times the search api query with geo params returns tweets with > the lat lon of the BIO and not the lat lon of the tweet!!! > > You may check this problem for example in Santiago de Chile, or in > Buenos Aires. > > > > > On 16 oct, 05:51, Johannes la Poutre <jsixp...@gmail.com> wrote: > > Update: the ticket is closed and @TweepsAround seems to be working > > fine again. > > > > Details:http://code.google.com/p/twitter-api/issues/detail?id=1930 > > > > Quote: > > > > Comment 3 by project member tokofu, Today (13 hours ago) > > > > We've deployed some changes which should have fixed this issue so i'm > > closing the ticket. > > > > Many thanks! > > > > On Oct 11, 9:38 pm, themattharris <thematthar...@twitter.com> wrote: > > > > > > > > > Thanks for filing the ticket on this, we'll post there when a fix is > > > deployed. Progress wise I checked in with the team today and they > > > continue to work on a fix. > > > > > To keep things connected there is another thread that was discussing > > > the issue with geocoded search here: > > > > http://groups.google.com/group/twitter-development-talk/browse_thread... > > > > > More information will be filed on the ticket here: > > > http://code.google.com/p/twitter-api/issues/detail?id=1930 > > > > > Thanks for bearing with us whilst we work out what went wrong with the > > > location index and how to resolve it. > > > > > Best, > > > @themattharris > > > > > On Oct 10, 9:29 pm, Nick <nick.fritzkow...@gmail.com> wrote: > > > > > > We are having issues with this as well and it has completely broken > > > > our system. > > > > > > We have sent many support tickets but have received no response to > > > > them. > > > > > > It looks to be breaking plain searches to not just those requested > via > > > > the API. > > > > > > Some examples of broken searches are: > > > > > >http://search.twitter.com/search?q=bigpond+near%3Aaustralia > > > > > > > http://search.twitter.com/search.json?q=bigpond&geocode=-27.766513,13... > > > > > > These were working before this issue. > > > > > > Best Regards > > > > Nick Fritzkowski > > > > > > On Oct 6, 2:42 am, Matt Harris <thematthar...@twitter.com> wrote: > > > > > > > This is a know issue which the team is working on at the moment. > I'll > > > > > post an update when a fix is deployed. > > > > > > > --- > > > > > @themattharris > > > > > Developer Advocate, Twitterhttp://twitter.com/themattharris > > > > > > > On Mon, Oct 4, 2010 at 8:36 PM, _ado <adri...@tijsseling.com> > wrote: > > > > > > For what it's worth, I'm seeing the same issue. Radius parameter > is > > > > > > completely ignored. Data returned for, for example, a 1 mile > radius > > > > > > will return results spanning 60 miles. > > > > > > > > -- > > > > > > 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
