GeoEvent Twitter Connector - Input and Bounding Box (Location)

[AllenScully]

Working in Server and GEP 10.4.1 - 

We have a working stream service, respecting the keywords we want it to look for - all good with a bit of work and trouble-shooting along the way.  What is still not working is the 'Locations' values I'm entering - essentially a bounding box with Xmin, Ymin, Xmax, Ymax lon/lat entered in.  No format I have tried makes an impact on the extent of the tweets were receiving.  

Reading through some other GeoNet entries related to this, I understand this is not a fool proof way to limit your feed, but should have some effect.  Just not seeing that at all unfortunately.  

Here's what should be defining our area of interest, and the format I'm entering it in (says it should be lon/lat pair):

-112.0,31.0,-110.0,32.0.

Anyone have any tips?

Thanks - 

Allen

[ChrisBeyett]

Hi Allen, 

I've also had trouble getting the Twitter API to conform perfectly to the Location X/Y pairs that I've set in the connector. However I think that this is a product of the API itself as I get the same general results from an search outside of the GeoEvent Server application. However what you could do it create an exact bounding box polygon of your Tweet area and use it as a geofence within GeoEvent Server. You could then specify the INSIDE or WITHIN spatial parameter and have all Tweets that fall outside of the polygon ignored. 

I run the same workflow and a USA boundary polygon when using the Twitter Connector for USA-only Tweets. 

- Chris

[AllenScully]

Thanks Chris -

That's what I ended up doing, and it works well so far.  Plus I got to learn a bit about geofences. 

Allen