What is wrong with the restrictive framework on Twitter?

Question

Given this URL, I 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, but I could not get anything, although I tried the areas indicated in the document, nor using cURL / POST.

When I add the keyword track parameter, I get a ton of tweets, but that doesn’t mean that the location works (the bounding boxes of the location are logical OR with other filtering options).

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

Thanks!

Answer 1

In my experience with the Streaming API, I have found that there are a surprisingly small number of tags with geotags. And perhaps your locations are too restrictive. But when you add a keyword parameter, as you say, you get OR'd results for both searches - Twitter does this, so you can execute multiple streaming requests on the same connection.

If you try

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

You get answers to all kinds of answers.

EDIT: oops, also, you have your longitude and latitude back. longitude comes first in their API. This url works:

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