Hi,
I've scanned some previous posts, along with the API documentation,
but have come up empty handed. So apologies if I ask a question that
has already been asked.
Is there functionality in the API that equates to the Twitter advanced
search web site? Specifically:
- choice of language to
On Tue, Jan 26, 2010 at 1:34 PM, mapgeek mj.hu...@gmail.com wrote:
Hi,
I've scanned some previous posts, along with the API documentation,
but have come up empty handed. So apologies if I ask a question that
has already been asked.
Is there functionality in the API that equates to the
For the Search REST API any of these operators should work. Just include
them in the with your search terms in q=.
http://search.twitter.com/operators
Abraham
On Tue, Jan 26, 2010 at 13:44, M. Edward (Ed) Borasky zzn...@gmail.comwrote:
On Tue, Jan 26, 2010 at 1:34 PM, mapgeek
I believe all of the params from advanced search can be used with the
search api as well...as an example, using the search.twitter.com
advanced search form produces a url like:
For the Search *API*, the geocode (lat,long,radius) is a separate parameter
on the call, *not* part of the q= string. If you go to Advanced Search and
type near:97201 within:25mi, it will work, but if you supply that as a
query to the API it won't. You have to look up the latitude and longitude of
The location filtering does not look at the location information provided
in user profiles. It only looks at tweets that have been geotagged. So If
you have location filtering enabled, you won't get any non-geotagged tweets.
Location specification is by latitude-longitude boxes in Streaming
