You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
TopoToolbox/libtopotoolbox#167 introduced some changes to the flow routing API that will break things here. The main change is to flow_routing_targets, which became flow_routing_d8_edgelist and now accepts an additional parameter. Renaming and fixing this interface is fairly straightforward, but we also need to distinguish between the topologically sorted list of nodes and the source vertices for the edge list on the Python side of things. The node list contains every node in the FlowObject, which is every node in the DEM. The edge list now only contains valid edges: there are no placeholder edges from sinks/outlets to the fictitious -1 node. Functions like drainagebasins and flow_accumulation now expect the edge list rather than the topologically sorted list of nodes.
The text was updated successfully, but these errors were encountered:
TopoToolbox/libtopotoolbox#167 introduced some changes to the flow routing API that will break things here. The main change is to
flow_routing_targets
, which becameflow_routing_d8_edgelist
and now accepts an additional parameter. Renaming and fixing this interface is fairly straightforward, but we also need to distinguish between the topologically sorted list of nodes and the source vertices for the edge list on the Python side of things. The node list contains every node in the FlowObject, which is every node in the DEM. The edge list now only contains valid edges: there are no placeholder edges from sinks/outlets to the fictitious -1 node. Functions likedrainagebasins
andflow_accumulation
now expect the edge list rather than the topologically sorted list of nodes.The text was updated successfully, but these errors were encountered: