search

PokemonGoers / PokeData

In this project you will scrape as much data as you can get about the *actual* sightings of Pokemons. As it turns out, players all around the world started reporting sightings of Pokemons and are logging them into a central repository (i.e. a database). We want to get this data so we can train our machine learning models. You will of course need to come up with other data sources not only for sightings but also for other relevant details that can be used later on as features for our machine learning algorithm (see Project B). Additional features could be air temperature during the given timestamp of sighting, location close to water, buildings or parks. Consult with Pokemon Go expert if you have such around you and come up with as many features as possible that describe a place, time and name of a sighted Pokemon. Another feature that you will implement is a twitter listener: You will use the twitter streaming API (https://dev.twitter.com/streaming/public) to listen on a specific topic (for example, the #foundPokemon hashtag). When a new tweet with that hashtag is written, an event will be fired in your application checking the details of the tweet, e.g. location, user, time stamp. Additionally, you will try to parse formatted text from the tweets to construct a new “seen” record that consequently will be added to the database. Some of the attributes of the record will be the Pokemon's name, location and the time stamp. Additional data sources (here is one: https://pkmngowiki.com/wiki/Pok%C3%A9mon) will also need to be integrated to give us more information about Pokemons e.g. what they are, what’s their relationship, what they can transform into, which attacks they can perform etc.
Apache License 2.0
9 stars 6 forks source link

No tweet data from the api #189

Closed mfkaptan closed 7 years ago

mfkaptan commented 7 years ago

Hi guys,

Catch-em-all here. I am trying to get tweets (with actual texts) from the api for tweet view on our app. Can anybody tell me what is the reason http://pokedata.c4e3f8c7.svc.dockerapp.io:65014/api/pokemon/sighting/source/twitter returns

{
    "message": "Success",
    "limited": false,
    "data": []
}

Also, will this result contain the text data?

Thanks, @mfkaptan

jonas-he commented 7 years ago

@mfkaptan the reason is that there are no sightings from twitter currently in our (temporary) database. There won't be any text, it would look the same like these ones http://pokedata.c4e3f8c7.svc.dockerapp.io:65014/api/pokemon/sighting

sacdallago commented 7 years ago

and now ( #190 ) the most likely source seems to be twitter :D :D :D crowd sourcing findings.

Actually. I see a huge potential here: with respect to everyone else, we have a WORKING solution to extract sightings from twitter. Today. No one else can do that. And while other services try to crack the new security measures, we can show data by crowd sourcing.

@gyachdav @goldbergtatyana

Now it would be the best time for AWS to let us use their damn services.

mfkaptan commented 7 years ago

@jonas-he Thanks for the answer. So, we won't keep any text from twitter in the database, is that correct (also no tweet data for the mobs)?

jonas-he commented 7 years ago

@mfkaptan yes that is correct. Regarding the mobs im not quite sure, please ask the hashPokemonGo team.