Ouch, that is pretty nasty... I'll see what can be done as merging multiple searches will degrade response times rather badly.
Thanks for the reply! On Sep 24, 4:33 pm, Taylor Singletary <taylorsinglet...@twitter.com> wrote: > 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 6:57 AM, Johannes la Poutre <jsixp...@gmail.com>wrote: > > > 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%2C... > > > I expect all resuls to originate from a geocode within 1km radius > > around the central coordinate. > > > As of a few days ago I get many results from much farther away, up to > > several tens of kilometers. > > > Is this a known issue? > > Any time to a fix? > > Or has there been an API change? > > Note: I revisited the API documentation ad could not find any recent > > changes. > > > Best, > > > Joe. > > > -- > > 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
