Skip to content

Project Status

Thomas Monfre edited this page Nov 11, 2018 · 10 revisions

As of November 16th, 2018, Project Pine Beetle will not be under active development. It is intended to be under active development again starting January 3rd, 2019.

Implemented: Fall, 2018

  • Database in MongoDB Developed
  • Historical data (1986-2018) uploaded to DB
  • Pipeline constructed for uploading Survey123 data to DB
  • Frontend framework developed
  • Data retrieval from DB implemented
  • Data handling in frontend implemented
  • User selection tools implemented
  • Rudimentary data visualization in map form implemented
  • Rudimentary data wrangling implemented
  • Aoki-Ayres Model implemented to run in R through JavaScript
  • Model updating process implemented
  • Expected Implementations: Winter, 2019
  • Given completed data processing on frontend, begin constructing data visualizations as per Aoki-Ayres specification

Next Steps

Data Visualization


After progress in developing the back-end and feeding data to the front-end, we anticipate future terms will be tasked with visualization data on the front-end. This will likely include some process of choosing and implementing a Javascript library specifically for data visualization. Future teams will be tasked with created dynamic and interactive graphs, charts, and diagrams. User interaction with selection menus and/or physical aspects of the graph itself will adjust what content is being visualized.

Model Integration Future teams will also have to integrate the predictive model(s) into the front-end. A significant part of this will be determining how to run and call the statistical model on the back-end and send that data to the front-end without having to refresh the page. Teams will have to look into different frameworks and perhaps do some refactoring of code on the front-end to accomplish this. Furthermore, future teams will be tasked with getting the model that calculates/updates coefficients running. They will have to make a plan for the frequency of running this model and come up with a way to automatically update the coefficients used in the other model.

Map Visualizations Future terms will also be tasked with visualizing data on the Esri map that is currently embedded on the front-end. Teams should consider using the Esri library of functions to put data points on the map and add functionality based on user clicks. Teams will specifically be tasked with making the map interactive with other data visualizations on the screen. For example, when a user clicks one data point, other graphs and charts adjust based on the interaction.

Design Front-End Lastly, future teams should have a full design team do through the entire design process. This includes user research, testing, iteration, and more. The goal will be to design a beautiful and functional front-end that fits the needs of the target audience.

Future Directions

This product illustrates the threats facing communities in a visual manner. It is well suited to visualize any epidemic or spreading threat. It could be generalized and implemented for visualizing risk of forest fires, spread of disease, genetic diversity, or any threat that is predictable, has the potential to propagate outward, and displays a set of observable qualities indicating risk.

Clone this wiki locally