point source files
1,634 views
Skip to first unread message
Shannon
Nov 10, 2012, 2:35:52 PM11/10/12
to arc...@googlegroups.com
Hi,
Does anyone have any insight into formatting point source files? Does the dataset for a point source have to cover the same timeframe as the weather data set?
Shannon
sck
Nov 13, 2012, 10:00:38 AM11/13/12
to ArcSWAT
Shannon,
I had significant difficulty working with point source files when I
wanted to add them to some of the subbasins but not all of them. I
ended up having to edit one of the SWAT input files manually to make
it work correctly. The SWAT support staff helped me edit the file. Are
you adding point sources to ALL of your subbasins, or just some of
them? Did you add a point source file to subbasin 18? Did you add a
point source file to subbasin 8 but not subbasin 18?
I had significant difficulty working with point source files when I
wanted to add them to some of the subbasins but not all of them. I
ended up having to edit one of the SWAT input files manually to make
it work correctly. The SWAT support staff helped me edit the file. Are
you adding point sources to ALL of your subbasins, or just some of
them? Did you add a point source file to subbasin 18? Did you add a
point source file to subbasin 8 but not subbasin 18?
Shannon
Nov 14, 2012, 10:06:34 AM11/14/12
to arc...@googlegroups.com
I used the add point source to all susbbasins option in the watershed delineation part and then imported data to subbasin 8, but not 18.
sck
Nov 14, 2012, 10:34:14 AM11/14/12
to ArcSWAT
Here is a blurb I wrote to myself to remind me of this issue: I had
difficulty adding a daily point source file to some subbasins.
Specifically, when a daily point source file was applied to a subbasin
with a number between 1 to 9, the SWAT interface wrote the fig.fig
file as if all the subbasins that were multiples of 10 plus the
subbasin number would also be expecting a daily point source file (for
example: if subbasin 2 were assigned a daily point source file, then
the fig.fig file indicated that subbasin 12, 22, 32, etc. also
required a point source file). The SWAT setup would run without error,
but during the model simulation, an error would occur at the first
subbasin incorrectly labeled as needing a daily point source file (in
the example above, an error would occur indicating an end-of-file
error during the read of file 12p.dat). One option to solve the
problem would have been to add a point source file to all the
subbasins, filling the parameter values with zeros when no point
source was actually in the subbasin. This idea was rejected due to the
extra work in loading all the point source files and the additional
computational processing that would be required for the program to
sort through the point sources that needed further inclusion and which
could be ignored. Although not recommended, with the help of Nancy
Sammons (USDA, Computer Assistant, SWAT Development Team), I manually
edited the fig.fig.
Also note, this did not work: Write Input Tables→Write Configuration
File (.fig) will rewrite the fig.fig file, but the changes made using
the Edit SWAT Input tab to add a daily point source file to a subbasin
will not be included in the fig.fig file (the default constant zero
loading will be written to the fig.fig file instead).
I had over 100 subbasins so it made sense for me to edit the fig.fig
file. If you have only a few subbasins that are multiples, you could
maybe try entering a point source file for subbasin 18 that has all
zeros. If you find another solution to this issue, please let me know.
difficulty adding a daily point source file to some subbasins.
Specifically, when a daily point source file was applied to a subbasin
with a number between 1 to 9, the SWAT interface wrote the fig.fig
file as if all the subbasins that were multiples of 10 plus the
subbasin number would also be expecting a daily point source file (for
example: if subbasin 2 were assigned a daily point source file, then
the fig.fig file indicated that subbasin 12, 22, 32, etc. also
required a point source file). The SWAT setup would run without error,
but during the model simulation, an error would occur at the first
subbasin incorrectly labeled as needing a daily point source file (in
the example above, an error would occur indicating an end-of-file
error during the read of file 12p.dat). One option to solve the
problem would have been to add a point source file to all the
subbasins, filling the parameter values with zeros when no point
source was actually in the subbasin. This idea was rejected due to the
extra work in loading all the point source files and the additional
computational processing that would be required for the program to
sort through the point sources that needed further inclusion and which
could be ignored. Although not recommended, with the help of Nancy
Sammons (USDA, Computer Assistant, SWAT Development Team), I manually
edited the fig.fig.
Also note, this did not work: Write Input Tables→Write Configuration
File (.fig) will rewrite the fig.fig file, but the changes made using
the Edit SWAT Input tab to add a daily point source file to a subbasin
will not be included in the fig.fig file (the default constant zero
loading will be written to the fig.fig file instead).
I had over 100 subbasins so it made sense for me to edit the fig.fig
file. If you have only a few subbasins that are multiples, you could
maybe try entering a point source file for subbasin 18 that has all
zeros. If you find another solution to this issue, please let me know.
sck
Nov 14, 2012, 10:39:29 AM11/14/12
to ArcSWAT
I should mention that I was using:
ArcSWAT: ArcSWAT_install_2009_10.1_Beta3
with
SWAT Executables: rev. 510, February 14, 2012
ArcSWAT: ArcSWAT_install_2009_10.1_Beta3
with
SWAT Executables: rev. 510, February 14, 2012
sck
Nov 14, 2012, 10:42:55 AM11/14/12
to ArcSWAT
And yes, the date range for the point source files, in the versions I
was using, did have to be the same in the point source files as in the
weather data files.
was using, did have to be the same in the point source files as in the
weather data files.
Muhammad Shahid Iqbal
Jan 15, 2016, 5:51:18 AM1/15/16
to ArcSWAT
Hi I am also facing the same problem as Shannon mentioned. could you please tell me did you overcome this problem or still not/
Joy
Oct 26, 2016, 5:48:52 PM10/26/16
to ArcSWAT
Hi Shahid,
I have the same error when trying to add point source inputs (daily). Have you find a solution to the problem? Any ideas are appreciated. Thanks.
Joy
Shuvra Bijukshe
Jun 24, 2022, 9:59:52 AM6/24/22
to ArcSWAT
Hello All,
Do anyone has file format to upload point source?
Best
Shuvra
0 new messages