We need to deploy on a production server at some point; possibly DigitalOcean & domain cafedaydream.com, possibly a Google provided server.

We need to figure out how to compress our audio analysis data into numbers that can produce a clear correspondence between visualization and audio. This is a fairly difficult problem, and very crucial to the app's usefulness, but it should be doable with measures like spectral centroids.

The entire reason we have a user login system is so people can control what they upload after they've clicked 'Allow'. Creating an interface for selecting and deleting bites might be kind of time consuming but definitely something we want to have.

We should create a warning message for collision signups, and fade the map background when the login box shows up.

At the core of our application is the way we draw heatmaps, probably the most important part of it. We need to be able to use heatmap.js on a point by point basis, perhaps overriding their time decay function for our own thing. Ideally we'll be able to control gradient, opacity, intensity, and radius of each bite; I can't figure which of these is more important, we should really have all of them.
@jennyzw and @kevinco26 are responsible for this.

If you open up the homepage at default zoom, the 'sign in with g+' and 'login' buttons are perfectly aligned. However, at different zoom levels, they become misaligned. Not a major issue but kind of annoying. See here for ideas perhaps.

The ability to listen to individual sound bites would be a big deal. Definitely something to shoot for if we have time but not a high priority.

We should have multiple ways to display the heatmap data. Ideas:

1. Real time map
2. Accelerated time lapse
3. User can choose color palette

The point of this app is to crowdsource location-sound data. As things stand, we're not going to have the chance to acquire many real users between now and ship day. However, we can certainly generate almost real data from a bunch of mp3s and locations preferably corresponding to population density, then shoot that directly into the MongoHQ datastore (or whatever we upgrade to for production). Not a huge priority but soon it will be.

Once we've compressed our audio data to core features, we need to upload this data to the Mongo server, ideally with some limitations in place to prevent abuse. There's a bit of work on both the frontend and backend required to enable this.

OperationFailure: database error: Malformed geo query: { $geoWithin: { $box: [ [ null, null ], [ null, null ] ] } }

Happens when we zoom out too much on the map - we should disable zooming out past a certain point (noone needs their map to wrap over a few times..)

Currently we can upload to the webserver but we need the webserver to save things in our datastore; a schema has been designed but stuff has to be hooked up, which might be really easy or really time consuming.. we'll see.

We should place some kind of limitation on how much users can upload so we don't run out of database storage because someone decided to spoof us with 200000 hours of generated audio.

If you log on, leave the site & come back or refresh the page, you're presented with the signin screen for a split second before we $('#loginbox').hide() it. This is a little sloppy as far as UX goes and we should address it.

Could make the entire login box only injected into the template in app.py if 'username' in session. Straightforward fix but not a priority.

See SO Q1 and SO Q2. We need to figure out how to accomplish this with a div (preferably containing an actual thing but that's optional). I'm having some issues getting the style of answer in the 2nd link to work (and ergo the style of the rest of the answers).

Currently anyone can upload stuff; let's restrict uploading to users that are logged in (have to take care of this securely somehow), and associate the sound bite they upload with their username (to support deleting later on).

I figured out how to change the color of a circle (red, green, yellow, etc) by passing in a parameter, but am not successful yet with gradients. I created a couple of gradients for testing, but when I pass the gradients (gradient1, gradient2), it does not change. Just picks up the last color in the gradient. The gradients work standing alone.

AJAX, Jinja data injection, or the likes is needed to allow the client to query our datastore for map points. Ideally we would support queries by date and location (for time based manipulations + only requesting points that are on the map area being viewed).