I started today with Knime in combination with Twitter. I successful connected the API to Twitter and I'm able to search for keywords as retreiving the result (including the user info).
I configured my Search Node to retreive GeoLocation information from the tweet. I saw in the release notes that this was fixed in version 3.01 (Bug 6053).
I did many tests with tweets that have geolocation enabled only I don't see any GeoLocation information in Knime.
Any idea's? Do I mis some configuration?
Hi just tried a similar setup and I was able to retrieve the GeoLocation (Latitude, Longitude, Country) for some of the Tweets (tried with query: #holidays). Of course not all Tweets have a Geo Location, but some have.
Not sure what is wrong with your workflow, but doesn't seem to be a bug to me (using the latest KNIME + updates).
Anything more you can share to help solving your issue?
Thanks for your reply Marco.
I did some more testing with larger sets of Twitter data (tweets). Found out that of 2000 tweest only 10 tweest had Geo Locations information. So I seems to work... but the result really depends on the tweet / user settings.
Indeed, it is optional for the users to turn on Geo Tagging, hence the fact that some Tweets have while others do not have an associated Geo Location.
I am trying to use the twitter search node with a query using "near" statement, for example, i am trying to run it with the following query:
"CRM near:"Canada" within:15mi"
But it is giving me the following error:
"ERROR Twitter Search 2:1 Execute failed: 400:The request was invalid. An accompanying error message will explain why. This is the status code will be returned during version 1.0 rate limiting(https://dev.twitter.com/pages/rate-limiting). In API v1.1, a request without authentication is considered invalid and you will get this response.
message - near parameter is invalid.
code - 44"
Any idea of what is happening? I run the same query directly from Twitter's search and it worked
Thank you Marco for your help, it really helped me a lot!!
the reason this doesn't wok is explained the the Twitter API documentation:
Geolocalization: The search operator “near” isn’t available in API, but there is a more precise way to restrict your query by a given location using the geocodeparameter specified with the template “latitude,longitude,radius”, for example, “37.781157,-122.398720,1mi”. When conducting geo searches, the search API will first attempt to find tweets which have lat/long within the queried geocode, and in case of not having success, it will attempt to find tweets created by users whose profile location can be reverse geocoded into a lat/long within the queried geocode, meaning that is possible to receive tweets which do not include lat/long information.