api - What's wrong with my Twitter stream bounding boxes? -

given url, should see tweets around london, right?

http://stream.twitter.com/1/statuses/filter.json?locations=51.23,-0.28,51.68,0.25

but nothing happens :(

i tried different areas couldn't nothing @ all, although i'm trying areas given in doc, neither using curl / post.

when add keyword track parameter, ton of tweets -- doesn't mean location works (location bounding boxes logical ors w/ other filtering params).

http://stream.twitter.com/1/statuses/filter.json?track=royalwedding&locations=51.23,-0.28,51.68,0.25

thanks !

in experience streaming api, have found there's surprisingly small amount of geotagged tweets. and, it's possible locations restrictive. when add keyword parameter, state, you're getting or'd results both searches -- twitter can perform multiple streaming queries on same connection.

if try

http://stream.twitter.com/1/statuses/filter.json\?locations\=-180,-90,180,90 

you sorts of responses back.

edit: oops, also, have longitude , latitude backwards. longitude comes first in api. url works:

 http://stream.twitter.com/1/statuses/filter.json\?locations\=-0.28,51.23,0.25,51.68