First deliverable: A demo for creating scenarios

[davemfish]

We're planning to prepare a demo for the San Antonio group.

The demo should include the UI & backend necessary for one of us to walk through creating new LULC scenarios and seeing the outcome of that scenario-generation process. It doesn't need to include running invest models. And it doesn't need to run in the cloud.

We estimated that this would be ready in early July. At the time we discussed it, I think that was ~6 weeks away?

[davemfish]

Anne may try to get us on their regular San Antonio call scheduled for July 14th. But we're not locked into that yet.

[phargogh]

Backend things to complete

This list is assuming that we're still going to be doing wallpapering

• [x] #20
• [x] #26
• [x] #22
• [ ] #23
• [ ] #25
• [ ] #24

For later, not critical for demo:

• [ ] would be nice if we backed up up the database (later on: disaster recovery plan)
• [ ] Set up cron job for whole-disk snapshots
• [x] Cataloging patterns - If users will be creating patterns and descriptions, make it possible to browser other people's patterns. Need a backend way to store, retrieve a listing of these patterns, specifically (name of pattern, ID of pattern, URL for where the patterned LULC is stored, bbox of pattern, maybe a colorized thumbnail of pixel values (related: can GCS handle many concurrent requests to a big GTiff, or are prerendered thumnails preferable?)

[dcdenu4]

Is it worth keeping this issue around?

[davemfish]

Seems more useful to make new issues for outstanding items.

[dcdenu4]

I agree, I'll make an issue for some of the backend things mentioned in that todo list and then close this issue.

[dcdenu4]

Created issue #60 to capture the backend todo tasks for future work.