Hi there,
As you might have seen through the issue notification that I have added a fix. Here is a bit of explanation on the issue.
There was an issue when a tweet did not have specific gps coordinates but instead a bounding box of coordinates. Tweetinvi was only using the exact coordinates to match the tracked location. This has been fixed with the new code I checked in yesterday.
But in addition to this issue of Tweetinvi, Twitter is returning some tweets that are not located in the location you entered. I therefore created a post on the twitter forum to inform the developers of the Twitter stream API and get some answers from them.
I will keep you up to date as soon as I have some news from the Twitter Team.
Cheers,
Linvi
As you might have seen through the issue notification that I have added a fix. Here is a bit of explanation on the issue.
There was an issue when a tweet did not have specific gps coordinates but instead a bounding box of coordinates. Tweetinvi was only using the exact coordinates to match the tracked location. This has been fixed with the new code I checked in yesterday.
But in addition to this issue of Tweetinvi, Twitter is returning some tweets that are not located in the location you entered. I therefore created a post on the twitter forum to inform the developers of the Twitter stream API and get some answers from them.
I will keep you up to date as soon as I have some news from the Twitter Team.
Cheers,
Linvi