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

Production database #125

Closed sacdallago closed 8 years ago

sacdallago commented 8 years ago

Hey guys, question: if I don't define the username and password for the production database (the MLAB env vars) how will the connection string be constructed? I say this because the database will grow a lot and I'm thinking it makes more sense to move this to a private thing where we can have >500mb, but the way I set it up is sia firewall/iptables, thus the uri is something like mongo://10.12.34.56/collection rather than mongo:///user:pass@10.12.34.56/collection

jonas-he commented 8 years ago

@sacdallago Assuming your running in production mode the string will look like mongodb://undefined:undefined@10.12.34.56/collection because the code looks like this:

if (appConfig['IS_LOCAL_DB']) {
            databaseParams = config['database'];
            if (databaseParams.username.length > 0 && databaseParams.password.length > 0) {
                dbConnection += databaseParams.username + ":" + databaseParams.password + "@";
            }
            dbConnection += databaseParams.uri + ":" + databaseParams.port + "/" + databaseParams.collection;
        } else {
            databaseParams = config['shared_database'];
            /*Connection parameters for a shared database instance*/
            dbConnection += databaseParams.username + ":" + databaseParams.password + "@" + databaseParams.uri + "/" +
                databaseParams.collection;
        }
sacdallago commented 8 years ago

@jonas-he thanks, so according to the #128 this should now be fixed. I hadn't really tried, but you know after some years working with these things I can predict what might go wrong ahah

vivek-sethia commented 8 years ago

@sacdallago Since #128 is merged with develop, closing this issue.