Develop an analysis pipeline

[gaurav]

The goal for this issue is to construct an internal analysis pipeline so that calculated raster layers can be provided to the user. This involves (copied from @DanRosauer's notes from our meeting last weekend - see the "Map of Life - Meeting Notes" Google document for further information):

• a Python process (e.g. “process.py”) to pre-compute a presence matrix in the PostgreSQL db summarising the species ranges stored in MoL to a predetermined grid or grids
• data queryable to feed into python analysis algortrhims (which will ultimately run on the cloud backend
• analysis results and metadata written to postgres tables
• then, we draw that, possibly as a single image which is mapped on top of the Google Map, bypassing Windshaft tiling (unless that is useful for some reason).

This is a high-priority task, since it is necessary to make it possible for the Jetz lab to work directly on Map of Life.

Future goals include replacing the sparse matrix with (1) a precomputed intersection of MoL polygons, and later (2) calculating it regularly as new data is added to MoL.

[gaurav]

Further information about this task:

1. We do not have to worry about ingesting rasters at this point, only in allowing rasters to be generated by analysis programs internally and stored in the database.
2. Quad id are unique to a grid, so cell 1201 in grid 360x114 will always point to the same lat/long coordinates. It might be easier to map quad ids to lat/long and render them using information about the grid, or to have a table mapping quad ids to polygons directly, which can then just be rendered by Windshaft. That's something we'll know more about as the polygon-ingest/Windshaft code comes together this week.
3. @DanRosauer's suggestion is to have a table mapping values/results from an analysis to a 'theme' (the analysis class being executed) and 'analysis' (the specific instance of an analysis with the parameters used to execute the analysis).

[gaurav]

Is this going to be made redundant by our work on Google's Earth Engine?