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.
It would be really nice if this could be fixed. This problem seems to occur only for pokemon 19-22 - but of course I did not check all of them ;) Maybe you can do some selected checks, and also see if any other field might be shifted/wrong somehow.
PS: I found a not-documented field Next Evolution Requirements in some of the pokemon, which sounds interesting :)
@AlexanderLill - Thanks for the observation.
There was indeed a problem with the description and I fixed it in the database as well as the json file. Refer #174.
Also checked the description for all other pokemons and they seem fine.
swathi-ssunder
commented
8 years ago 
AlexanderLill
Hello everybody,
call me crazy, but I think I just found a strange issue: As far as I see the descriptions are somehow shifted starting at pokemon 20: Raticate.
It starts with 19: Rattata not even having a
descriptionfield: http://pokedata.c4e3f8c7.svc.dockerapp.io:65014/api/pokemon/id/19And then goes on with pokemon 20-22 having the description of the pokemon right before them: http://pokedata.c4e3f8c7.svc.dockerapp.io:65014/api/pokemon/id/20 http://pokedata.c4e3f8c7.svc.dockerapp.io:65014/api/pokemon/id/21 http://pokedata.c4e3f8c7.svc.dockerapp.io:65014/api/pokemon/id/22
It seems to be alright again at pokemon 23: http://pokedata.c4e3f8c7.svc.dockerapp.io:65014/api/pokemon/id/23
It would be really nice if this could be fixed. This problem seems to occur only for pokemon 19-22 - but of course I did not check all of them ;) Maybe you can do some selected checks, and also see if any other field might be shifted/wrong somehow.
PS: I found a not-documented field
Next Evolution Requirementsin some of the pokemon, which sounds interesting :)@PokemonGoers/catch-em-all