Skip to content

Conversation

@slama0077
Copy link
Collaborator

This new pull request makes t-route compatible with hydriofabric version 3.0. Also, this includes the new routing algorithm where the lateralflow stored in nexus gets mapped to the flowpath/flowline downstream to nexus. This PR gets rid of the idea of giuh node. It also makes user to strictly use nextgen output if using Hyfeature network. This doesn't include the routing of pseudo-headwater catchments. Finally, everything is cleaned up, so this should be ready to merged after a review.

kumdonoaa and others added 18 commits October 14, 2025 16:34
…ateral

Increased the speed by about 5 times for Forcing Array Construction
…lateral of the nexus is passed to downstream flowline.

crosswaslking nexus, poi is also done

if the qlateral_input files is channel routing, then it follows old convention of routing.

added multiprocessing in reading channel routing files which helps to create lateral array 5 times faster

headwater routing needs to be done with interpolation
Removed flowpath attributes manually if the network type is NHD
… into terminal nexus

Fixed f-string formatting

descriptive dictionary variable
…etwork_bodies parameter is. But I think the better way to do this in Hyfeature implementation is to seperate the creation of lake_gage_df from the normal gage dataframe because creation of lake_gage_df should certainly depend on break_network_waterbody, and that's how NHD functions.
… updates:1)Got rid of the idea of giuh parameter\n2)If using hyfeature network only accept output from nextgen with file pattern nex-* cat-*\n3)No headwater routing for now (but the function that maps pseudo headwaters to its first nexus' downstream still exists\n4)Cleaned up a lot so should be ready to merge after some review
@slama0077 slama0077 requested a review from quinnylee November 10, 2025 21:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants