Hello, As far as I can see from my testing, terms seem to be ignored. Here is the twitter processor configuration: ---twitter endpoint: filter endpointterms to filter on: kmeans,kmeanlocations to filter on: -124.476284,32.172870,-59.437227,48.862583 ---
Date: Wed, 21 Oct 2015 16:09:02 -0400 Subject: Re: Filtering GetTwitter with both terms and locations From: [email protected] To: [email protected] >From looking at the processor code it looks like it adds both the terms and >locations to the filter endpoint and should be able to filter on both. The >processor leverages the Hosebird Client [1] so it could be possible that >library is not working as expected. Is there a specific example of terms that aren't working? or they never work in conjunction with locations? [1] https://github.com/twitter/hbc On Wed, Oct 21, 2015 at 3:03 PM, David Klim <[email protected]> wrote: Hello, I am trying to get data from Twitter filter endpoint using a both location (bounding box ) and terms to filter on. The data I get is not being filtered by terms at all. Is there any known problem with the feature? Not sure if the processor behaves as I expect. Thanks a lot!
