I am having an issue with the streaming API where it is returning me tweets outside of the bounding box.
It can be seen from this map of tweet locations, the dotted box is the boundary I passed to the API, but as you can see tweets have been captured from states that overlap this bounding box.
HOWEVER, tweets are not being returned for populous areas outside of the bounding box, but then within the states. This screenshot shows Philadelphia, which is devoid of tweets in the down-town area.
Can anyone shed some light on why I am seeing this behaviour?
This is the exact URL I am capturing on the stream
Replies
Thanks, I've reported Streaming results returned outside of specified bounding box
Is there any word on this? I am noticing it as well.
This is pretty noticeable. I have a bounding box consisting of a 1 KM offset from a given point. When I get tweets back, they're almost never actually inside this bounding box. Some are up to 500 KM away from the original point.
Hello, any progress on the resolution of the issue? It is quite blocking for some applications, as it seems that in addition of results outside of the box being returned, some results inside it do not show up...
Thanks
how to get bound box of location like New Delhi
I'm facing the same problems.... Any progress on this? Is there a work-around?
I am facing the same problem
I see that this problem was reported almost a year ago and yet I am still getting tweets outside of the locations bounding box as of today. Whats going on ?
Some observations.
I set my boundary to the campus of UIUC(Champaign, IL). Although I get markers out of bound,
they are never outside of Illinois(excluding St.Louis).
http://imgur.com/j1InFru
I haven't tried it yet but I think the most basic workaround is filtering tweets with this library(if tweets are used in the front end).
https://github.com/tparkin/Google-Maps-Point-in-Polygon
Bounding box around Tampa, Florida gives me Tweets from all over Florida. Very annoying.
Can anybody pls help me how to use streaming API to get Tweets with geolocations(lat longs) in any given bounding area..
I'm having this same issue.
Trying to get my android app to give me tweets from an area. It's for a class. If anyone could help i would appreciate it. :/
Ditto, please help. I have been playing with this for a while and the results are far from impressive. If anyone finds anything please let me know :)
I usually implement my own filter when consuming the streaming data if I want precise bounding box limits.
@sylvestrends Can you offer any links to examples, tutorials, or personal code examples that could assist in getting these bounding boxes to work correctly? I notice that i am in fact getting all the tweets from a certain area, but additionally i'm also getting tweets from outside the box. Assuming i could just do a second filter over the results of the first, i could get rid of anything outside of my box manually. I just have no understanding of how to go about this. Thanks.
The main thing you want to do is extract the geo origin of the incoming tweet, then do a point-in-rectangle test of that tweet's point and the target area's bounding rectangle.
Here's the python code I use once I extract the tweet's location as (long,lat) point:
bbox
is a list containing [long, lat, long, lat] where SW corner is first, NE corner is second, if I recall correctly =)@sylvestrends Thank you, that is very helpful. I'll give this a shot and see if i can construct this in Java and get it to actually work. :)
I'm just also hoping that i am not losing tweets that are actually being returned within my box. If that is the case, this second filtering would be pointless. The only way i can really test this though is to tweet from within my box myself, and so far, every test i do myself is returned. Hoping this works, thanks again for your help!
Good luck with your efforts!
Pythonistas can use my Twitter-Streamer utility (https://github.com/inactivist/twitter-streamer#location-based-searching) to test the streaming API's bounding box search functions from the command line.
Any news on this issue ?