Open jtgilbert opened 2 years ago
@joewheaton @philipbaileynar thoughts on this? I've left it unassigned, but if you agree with the above you can assign.
I do not have strong opinions about this and defer to model users.
FYI, @wally-mac here's an issue I created a while ago to document the issue with the Stream Size Limited
category in the Limited Opportunities
output. There's a few tickets for other potential improvements we've discussed as well.
@jtgilbert I think this is worth adding as it provides more accurate and nuanced outputs for the user.
@ChloeSeeborg I'm assigning this old ticket to you. Let's get rid of the 'steam size limited' category in the Q and Arc symbology for the BRAT 'limited opportunities' layer. There's no consistent way to apply it and it's not being used right now.
In ArcRAVE and QRAVE there is a
Stream Size Limited
category, but in WebRAVE there isn't. However, it does not appear that this category gets applied at all anyway. If we don't want this output category, then this is just an xml issue. I think it makes sense to use this category to maintain transparency in the process (i.e., show that a drainage area threshold is being applied because we're assuming streams above that threshold are too big to build dams on). In this case, the model logic needs updated to apply this value to stream segments with DA > DA threshold. I also think that this value should override any other limitations, because if the stream is too big to build on, stream power or anthropogenic limitations don't really matter.