Some metrics: I just reran some tests to compare results for both the polling search api + geocode and the steaming api statuses/filter + locations using San Francisco as the geolocation.
Basically, the polling search api+geocode returns approximately 30x more results than the steaming api statuses/filter + locations within the same test period for the same geolocation. The parameters used for the search api+geocode were: 37.736784, -122.44709, 40km The parameters used for the steaming api statuses/filter + locations were: -122.901549008664,37.3773810096865,-121.992630991336,38.0961869903135 which correspond to the bounding box around 37.736784, -122.44709, 40km. Why is there such huge difference and can we expect the streaming API to eventually match what the search API produces for geolocalized searches? Thanks, Colin On Feb 10, 5:32 pm, Colin Surprenant <colin.surpren...@gmail.com> wrote: > Hi, > > I have been running some tests to gather tweets from users within a > geo area using both the search API (with the geocode parameter) and > the streaming API (with the statuses/filter method & locations > parameter). > > I have noticed that the streaming API returns far less tweets for an > equivalent area expressed either as a latlong+radius for the search > API or as a bounding box for the streaming API. > > Is this normal or should we expect a similar result set with both > methods? > > In the doc it says that the streaming API will only return tweets that > are created using the Geotagging API (and within the bounding box) but > the search API will preferentially use the Geotagging API, but will > fall back to the Twitter profile location. > > Can this explain why I see much more results with the search API? > > Thanks, > Colin -- 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
