Open kasra-keshavarz opened 1 year ago
Just an extra note, this issue is addressed outside of the MESH
's source code, in the relevant workflow mesfhlow
where the islands are dealt with in the setup process: the longest branch of river segments is extracted using the functionalities in Hydrant
and the islands are put in between the found segments.
Adding this note just for the sake of completeness and possibly guidance for future visitors.
Problem statement
MESH v.1813
seems to have an issue in reading validRank
andNext
values when "islands" are placed at the end of theRank
list in a vector-based setup. Please note that even if "islands" are placed at the end of theRank
list, bothRank
andNext
lists are still valid. However,MESH v.1813
apparently "does a sanity check to compare the last draining outlet against the number of Rank, the ordering creates this disconnect", and therefore, cannot fully comprehend the network setup.An "island" is defined as a sub-basin without any immediate downstream segment and drains to the outside of the modelling domain; non-contributing areas could be an example of an "island."
The typical "Remarks" printed by
MESH v.1813
when "islands" become problematic are as follows:And the following error is raised:
Example of problematic
Rank
andNext
with "islands"The following gives an example of
Rank
andNext
created using MESH-Scripts workflow (commit e8fcba5) applied on the St. Mary and Milk geo-fabric.Rank
:Next
:Relevant Issue
This issue could be resolved outside of
MESH
by bringing the "islands" in between the river segments of the longest branch of rivers in a network. This is explained in an issue inMESH-Scripts
workflow repository.If I can help further, please let me know. Thanks.