Reservoir Outlet Mismatch

[Swetasree Nag]

Dear SWAT+ User Group,

I hope you are doing well.

I am currently working on a watershed model using SWAT+ Editor v3.0.8 (rev.61.0.1) and have come across a discrepancy involving automatically added reservoirs and their outlet channel connections.

In my case, I added a reservoir shapefile to the model. The SWAT+ Editor automatically assigned outflow channels for each reservoir. When I check in the Editor interface, the outlet connection (e.g., to cha33) appears to be correctly assigned (screenshot attached).

However, when I open the corresponding reservoir.con file (from the TxtInOut folder), the obj_id listed for that reservoir is different from what is shown in the Editor(screenshot attached). The mismatch between the channel displayed in the SWAT+ Editor and the one reflected in the .con file is causing confusion, and I am unsure which one is actually used in the model execution.

I have tried the following steps to troubleshoot:

• Verified that there are no duplicate reservoir entries or naming conflicts.

• Used “Save Changes” and “Write Input Files” after confirming the connections.

• Deleted the existing reservoir.con file and re-generated it.

• Cross-checked the channel IDs using QGIS attribute tables.

Despite these efforts, the mismatch remains. 
Same happened for other reservoir also.

Could you please advise if this is a known issue, or if there's something additional I need to do to ensure consistency between the SWAT+ Editor interface and the .con file output?

I would greatly appreciate your guidance.

Best regards,
Swetasree Nag

The information contained in this electronic communication is intended solely for the individual(s) or entity to which it is addressed. It may contain proprietary, confidential and/or legally privileged information. Any review, retransmission, dissemination, printing, copying or other use of, or taking any action in reliance on the contents of this information by person(s) or entities other than the intended recipient is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us by responding to this email or telephone and immediately and permanently delete all copies of this message and any attachments from your system(s). The contents of this message do not necessarily represent the views or policies of BITS Pilani.