Closed philipbaileynar closed 2 months ago
@philipbaileynar, @joewheaton, @lauren-herbine: Here are the projects that have completed the updated confinement tool: 07020005 05140201 05040003 08010100 07050002 05010003 07080105 06010207 10270101
Note that confinement is calculated along the level path, which is much longer than we were previously using. There is a separate layer (confiment_ratio_segmented) that calculates confinement on the 300m segmented flowlines that were previously used, however this is not exposed in the business logic.
Thanks @KellyMWhitehead. @lauren-herbine please download and have a look at these. I have just downloaded and we'll dig in. There are some bigger segmentation issues we're going to have to deal with. Lets not forget that Gary O'Brian and I did a big sensitivity analysis of confinement on segmentation length. 500 m is what we came up with ;). I will take a look and see if I can't figure out what's going on/wrong.
@KellyMWhitehead I am noticing that not all flowlines have confinement calculated for them (specifically mainstem Mississippi). Do you have any ideas as to why this might be happening? I looked at 08010100
Edit: also happening in other HUCs (here is 10270101):
blue drawn line is a flowline but does not have confinement calculated for it. Could this have to do with FCode selection? A quick perusal doesn't point to this... the channels we are missing are main channels
Super old issue that refers to Kelly's initial version of a Riverscapes compliant version of confinement. Now we have Jordan's new implement that is a different model. Closing because it refers to a deprecated model.
Now that VBET is stable it's time to revisit confinement.