New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
More complete Twitter Ingestion #194
Comments
I think we can strike |
Sounds good to me @ruebot! |
Example:
|
All of the
|
|
@SamFritz can we add a item for our August 22nd agenda to discuss how we should pull out these ...unless @lintool knows of some Scala tricks with json off the top of his head. |
As for "place":
{
"country_code": "US",
"url": "https://api.twitter.com/1.1/geo/id/67b98f17fdcf20be.json",
"country": "United States",
"place_type": "city",
"bounding_box": {
"type": "Polygon",
"coordinates": [
[
[
-71.191421,
42.227797
],
[
-71.191421,
42.399542
],
[
-70.986004,
42.399542
],
[
-70.986004,
42.227797
]
]
]
},
"full_name": "Boston, MA",
"attributes": {},
"id": "67b98f17fdcf20be",
"name": "Boston"
},
"geo":
{
"type": "Point",
"coordinates": [
42.33887,
-71.08839
]
}
|
Good idea. My basic instincts suggest we either use classes, or just accept tuples. The coordinates thing seems complicated though and could just be a quagmire of nested Objects if we go the class route. |
Threaded from #192
Going through the twitter ingestion script, it might be nice to include a few other things if possible from the api. Retweet_count for instance. Possibly things like "location" and "in_reply_to" depending on how far we want to go with that and ethical considerations.
Here's a short list from my perspective and maybe we can check the things we want to include, and then we can fix things all together:
retweeted (true / false)This is just a rough list of possible candidates. Not necessarily suggesting we should ingest them all or even one. Just think it's worth looking at while we fix TweetUtils.
The text was updated successfully, but these errors were encountered: