assume upper and lower are equal
Estimate cover -> anything not bare soil (i.e. rocks)
Also explanation of each input
Latitude and Longitude
Soil texture, rock content, gradient
pulled from spatial WEPP database
Slope length, cover, climate, years to run, vegetation
Only the first output table
mean annual averages for X years
Inputs (two views)
Ask user for use of browser location data
Input address -> latitude, longitude
Slope value from database is actually the slope gradient.
The rock content field has a range from 0% to 55%, not 0% to 100%.
Though, the model may clamp the value.
Confirmed that the the top and bottom gradient values are constant and the gradient input field is copied into the two middle gradient values
Mary will send the development team more information regarding the instructions for collecting and understanding the various input fields on the web app.
Add some more climate centers:
specifically the one in Ann Arbor and some near Houghton.
No strong preference for or against making the app a single page.
Mary gave the idea that we could put the latitude and longitude values on the homepage and keep separate from the inputs page.
Design Changes after meeting with Mary and Joseph and Ankitha
state and year?
select location based on region
dropdown list or from GPS location?
review climate models
climate models are forestry stations
one or two?
one or two?
HTTPBuilder packaged into the .war file
for the server
dependency in gradle build?
Another meeting with Mary soon
another paper draft
- What kind of users will we expect to use this application (possibly some examples)?
Citizen scientist, students, educators, may be by other people, forest services interested
-online database, soil texture, data not correct yet
Allow the user to modify data based on what they see in the field
-Some members need an explanation of the Disturbed WEPP Model 2.0
-app will have to query to two databases
-Are databases manipulatable?
Both are designed to be user-friendly, can be modified to our needs. We need a location, can be done using latitude and longitudes
-We will need to collect data from the user
It is a process based on hydrology model. 500 inputs go into running the model. Online interface to a WEPP model.Built for BAER team, typically forest service personnel. 7 days to decide hydrological threat after fire. Uses remote sensing data.
- What environment (at home, outside, etc... and what situations) would you expect the users to be in whilst using the app?
Students out on the field, or may be from home. Need internet or wifi on any mobile device
Can user collect data offline and then upload later on.?
Possibly offline mode.? Yes, if possible!
- Are there any requirements that you wish to outright specify?
Query the database
Be able to collect data from users(automated process to manipulate data?) feature to email scientist if there is something wrong in the database, scientist can review and make edits.
Login? Should be accessible to everyone, so probably not
Keep in mind, app could be
Allow user to gather information from phone, gps location and edit database from phone, would be beneficial for students for educational purposes
- Did you have a chance to look into licensing since the last meeting?
If not, do you want this application to be free/opensource or commercial?
yes preferably. Mary will check with her lead programmer
Can commercial entities use it to make money?
Don’t need to worry about at the moment
- Have you been added to the github page and do you want a short overview of how to use it?
She has been added, she hasn’t checked it out yet
During this meeting we discussed the results of the usability test, some last minutes changes, as well as possibly features, which were not included in our porject. Mary was pleased with the results of the usability test: she was glad that students were able to use WEPA, despite having little to no experience with erosion modeling beforehand. Though, she was confused by the risk indicator that we included on the results page. So we explained why we added it and that there was a bug with the indicator text that has been fixed.
In addition, we discussed an issue with the climate input field that Mary had discovered recently, which Joshua was able to fix before the meeting. However, fixing the issue with the climate revealed that further development was necessary to allow climates, which are not part of the default list in the WEPP Model website, to be used in WEPA. Mary understands this and looks forward to seeing the final version of WEPA being deployed with a function climate field.
Finally, we brainstormed a list of possible features for WEPA, which were not included in this project:
Forestry Managers (Expert)
Citizen Scientists (Novice)
Mary Miller (Scientist)
Professor Robert Pastel (Product Owner)
Other Michigan Tech students and faculty
Aaron Hale is surveying the damage caused to his backyard from the fire he (accidently) started. From his studies as an environmental engineer, he is aware that part of the yard could be susceptible to soil erosion. To ensure that he can prepare for any further mishaps, Aaron decides to test the soil erosion and update the MTU BAER database with his findings. He navigates to the homepage of our application to request an update to the database with his new findings. The update is then reviewed by a scientist to ensure that it is indeed accurate and the database is updated.
Lois Pearson is out on stroll near the when he decides to take a look at the hillside near his campus. After noticing that the recent fire did quite a bit of damage, he decides to check the data of the soil around the area of the fire. He navigates to the apps main page where he then inputs his location to query the database for information of the surrounding area. Unfortunately he does not quite understand the information he is seeing so he takes the info to the local soil erosion team on campus. Making the team aware that there may be a problem, the scientists can then take care to ensure that soil erosion causes minimal damage to the buildings below the hill.
WEPP explanation view
Data collection view
Database query view
Edit input parameters
Query data from database
Edit input parameters view
Input latitude, longitude, hydrological parameters
Query data from database view
Upload user data to server
The Soil Erosion Query application is to consist of forms that the user may use to query and input information from a set of soil erosion and BAER databases in a streamline manner. The application will be web based and the user will be capable of accessing this web application from many common desktop internet browsers (such as Google Chrome, Safari, Firefox, and Internet Explorer) as well as from their mobile devices. The queries and inputs will be made in a streamlined fashion allowing for more general users to make use of the application to detect the possibility of soil erosion. Once the user completes the forms (for a query or to input new data), the form will be sent off to a server and processed by our web application and the web application will then make the appropriate queries to the appropriate databases.
The application has three primary stakeholders: Mary Miller (Scientist), Forestry Managers (experts in the field of soil erosion and users of the databases), and citizen scientists (general users who may be novices when it comes to the field of soil erosion and utilizing the databases). Mary Miller needs this application to run in an efficient manner to help streamline many of the processes and procedures that users like the BAER teams and soil erosion experts currently need to perform under extremely tedious circumstances. It must be able to intelligently relay the information that the users need to see with minimal effort on the part of the user.
|#||First Name||Last Name|
|5||Mohammad||Sajib Al Serajemail@example.com|