There is one particularly odd area in which multiple flow line features fall within a single catchment in the reference layer. They are then "oddly" grouped in the reconciled/divides layer.
Looking at the map, the assignment does make sense, but seems to contradict the incoming data.
Edited
Designs
Child items
...
Show closed items
Linked items
0
Link issues together to show that they're related.
Learn more.
6747170 and 6745232 are both marked Catchment: N in the burn line event table. This indicates that those lines will not have catchments created for them.
So, from a catchment perspective, they don't exist and no land-area will ever route to them.
If you search the divides for a member_COMID that includes those two orphan flow lines, you won't find any.
So, should we just drop little orphan networks like these when we start the process? They really aren't adding anything.
Looking more closely at the flow direction issue -- this can be fixed. This is a case where the flowline is being replaced by a burn line but, because the no-catchment flowlines connect to it, the direction is not being checked. Definitely a bug. I'll get this taken care of with an update to the enhd attributes. Going to have some fairly far-reaching impacts, but I'm glad we caught this.
I was wrong about the solution here. There's a much lighter hand approach. I'm now just culling flowlines that don't need to be included in prep nhd prior to generating the regional reference gpkgs. Merge request incoming and I'll work on getting the regional files updated tomorrow.