Hi Thomas, Can you provide us with a little more information about this so we can look into it. Information like:
* the filter predicates you are sending with your request to the streaming API. * an example of a Tweet that appears to have been delivered in error. Thanks, @themattharris <https://twitter.com/intent/follow?screen_name=themattharris> Developer Advocate, Twitter On Tue, Jun 21, 2011 at 12:12 AM, Thomas Alisi <thomasal...@gmail.com>wrote: > hi all > > I am developing a data mining application for telecom italia (the biggest > tlc company in italy) and we're still refining the algorithms using a > spritzer account. > > in order to maximize the streams around a few interesting locations (uk, > spain, france, italy), our setup is using location boxes, as detailed here: > http://dev.twitter.com/pages/streaming_api_methods#locations > > but something weird happens: we are receiving status updates out of the > specified location boxes (fair enough...) from places that have the same > names as others inside our location boxes. e.g. our box coordinates focused > on UK obviously do not include US, but we are receiving tweets from > 37.1289787 -84.0832596 (namely: london, KY) > > is there some reverse geo-coding going on? > > many thanks > thomas > > -- > Twitter developer documentation and resources: https://dev.twitter.com/doc > API updates via Twitter: https://twitter.com/twitterapi > Issues/Enhancements Tracker: > https://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > https://groups.google.com/forum/#!forum/twitter-development-talk > -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
