Closed joewheaton closed 6 years ago
@joewheaton Let's try to get some feedback on final workflow early next week.
@joewheaton and I talked today (5/10/18) and attempted to determine what the BRAT app should allow the user to do. We agreed that the main thing the app should do is address the same questions that the BRAT capacity model assesses:
On the human-beaver conflict potential side of things we also discussed that the app should allow users to add location data (“drop a point”) in areas of known beaver conflict and in areas where there is infrastructure constraints. - NW: Would this be field or desktop or both? WM: I think both
We also talked about how the app could help make determinations regarding the NHD stream network misalignment and when it is worth making modifications to the NHD Network based on if the misalignment actually affect dam building material preferences or slope calculations (i.e., if the stream is offset but within that offsite the vegetation class does not change nor do the elevation values significantly change it is not worth re-digitizing the stream segment. - NW: I could see this being part of the desktop portion of the workflow. Basically just a field in the attribute table that could be flagged WM: I agree!
Joe, thought that it would be useful to have a BRAT calculator that would allow the user to run a simple inference system and get a capacity output “in the field.” -NW: Yup, should be OK
@webernick79 I hope this is useful information. We also talked about trying to have a catch up call tomorrow late afternoon with @bangen, @joewheaton and you and I. Are you available?
This is good feedback. I'm available tomorrow, just let me know the time.
Wally and I have a meeting from 10 to 11 am PST tomorrow morning. I'm available after that.
Joe and I have a meeting that will probably last until 2:30 MST so how about 3:00 MST?
@webernick79 I ask Kristen Wilson (our TNC contact) for locations data and where we should test the app and she provided a kmz file (below as a zipfile). She identified 250-600 m reaches of stream that are within walking distance of the field station where we are staying. She put notes in the location names to indicate why these reaches might work well.
BRAT model validation locations Sagehen.zip
I think the task for @bangen to use this kmz to select stream segments (and the associated 30 and 100 m buffers) from the BRAT output and provide them to @webernick79 so he can produce the sample dataset for the workshop. Note: Joe and I discussed earlier today that the 30 and 100 meter buffers are the polygons that the user will interact with.
This seems very doable.
@joewheaton and I talked today (5/10/18) and Joe stated that for the TNC BRAT project TNC staff, forest service personnel and citizen scientists will only be responsible for data capture and this data capture can occur as field, desktop or a combination between field and desktop interpretations. We (the ETAL lab) is responsible for model calibration, verification and validation based on the data that they provide us.
This conversation has run its course....
From @webernick79:
Some more ideas for validation workflow. These are just concept what could work and are not meant to be finished products
This example shows how Arc Explorer and Survey123 work together to allow offline data collection: https://www.youtube.com/watch?v=26rqpWeay-o , this makes use of a vector tile package as a basemap, and is brought into Arc Explorer using a the mobile map package, which also launches survey 123 to record validation observations.
The survey 123 data would then be available in as a layer in ArcOnline. This can be used in a web map or app, here’s an app example: https://www.youtube.com/watch?v=ieZPHtKUPxk
Let’s chat about limitations of this approach and others soon and decide where to go. If this is a route we consider I would need to start getting final layers to develop Basemaps and validation layers etc…..