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

Evolution data #108

Closed gyachdav closed 8 years ago

gyachdav commented 8 years ago

tried http://pokedata.c4e3f8c7.svc.dockerapp.io:65014/api/pokemon/evolution/prev/name/Voltorb

Resp: { "message": "Success", "data": [ { "_id": "57c7433d7db332a41b06d7c5", "maxHP": 1646, "maxCP": 1496, "fleeRate": 0.06, "classification": "Ball Pokèmon", "name": "Electrode", ...} ] }

whereas cannon says:

Voltorb -> Electrode

trying

http://pokedata.c4e3f8c7.svc.dockerapp.io:65014/api/pokemon/evolution/next/name/Voltorb

gets me an empty resp.

Now I understand what you're trying to do here but it is counter intuitive. I would recommend to either:

  1. change the logic of this operation to find the EvolveTo

or

  1. change the name of the operation to EvolveFrom

or

  1. Have two operations: EvolveTo and EvolveFrom.

and have a better description, right now it is confusing.

jonas-he commented 8 years ago

@gyachdav indeed, theres a mistake in our logic, im looking into this.

swathi-ssunder commented 8 years ago

@jonas-he - The problem is not with the logic, but rather with the naming, as @gyachdav rightly pointed out. And this has led to the confusion in interpreting the API response. So we can change it as per the suggestions.

jonas-he commented 8 years ago

@gyachdav its fixed now. also these API calls will only return the direct next/previous evolution, not all of them.

gyachdav commented 8 years ago

LGTM