Hi Colin,

You hit the nail on the head with this observation:

> 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.

The Search API is greedy with those location fields on user's
profiles. It's not likely this behavior will be emulated in the
Streaming API with the bright side that you can be more confident in
the location accuracy in matches on the Streaming API.


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