Looking over CatFIM 4.5.11.1, it is evident that the stream segments inundated in Alaska flow-based CatFIM seem to be much shorter, in general, than the CatFIM segments in other parts of the country. In the screenshots below, I've included some measured comparisons between CatFIM outputs in Alaska and CatFIM outputs in Washington State (a hydrologically-similar landscape).
Once I get the stage-based CatFIM outputs to download properly, I will add information on whether I am seeing this issue in stage-based as well.
Screenshots
Each screenshot includes a rough measurement of the flow length that seems to be inundated. The total (roughly) measured length is listed under Path Net Distance.
We've traced this back to WRDS not having stream tracing data for Alaska. We'll have to wait until they are able to get that running unless we decide to do the tracing ourselves.
Looking over CatFIM 4.5.11.1, it is evident that the stream segments inundated in Alaska flow-based CatFIM seem to be much shorter, in general, than the CatFIM segments in other parts of the country. In the screenshots below, I've included some measured comparisons between CatFIM outputs in Alaska and CatFIM outputs in Washington State (a hydrologically-similar landscape).
Once I get the stage-based CatFIM outputs to download properly, I will add information on whether I am seeing this issue in stage-based as well.
Screenshots
Each screenshot includes a rough measurement of the flow length that seems to be inundated. The total (roughly) measured length is listed under Path Net Distance.
Alaska sites:
Alaska flow-based CatFIM, LID: clta2
Alaska flow-based CatFIM, LID: suna2
Alaska flow-based CatFIM, LID: lsoa2
Alaska flow-based CatFIM, LID: apta2
In comparison, CONUS sites in Washington:
Washington flow-based CatFIM, LID: sakw1
Washington flow-based CatFIM, LID: elww1
Washington flow-based CatFIM, LID: issw1