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

changed pokemonicon storage and response to be buffer #116

Closed samitsv closed 8 years ago

samitsv commented 8 years ago
sacdallago commented 8 years ago

One question: what is the outcome now of calling that route? Do I still need to interpret the data somehow?

When I was dealing with images, I just piped them as the response. If the request was succesful you'd get http://cell.dallago.us/api/maps/573c87c182a9e1ae1e37d08e. On the other hand if there was a not found you get a http://cell.dallago.us/api/maps/kdf . Notice that although the 404 is a page in my case, the status of the request is also 404, so it is actually consistent (pipe = 200, error = 404/500)

samitsv commented 8 years ago

@sacdallago now i changed the api to directly provide the requester the image. For example,

/api/pokemon/id/140/icon

will return a gif image, no decoding required if the pokemonid doesnt exist then it will return

{"message":"Failure. No pokemon icon with this id exists!"}