The name of a BC data event. The name must be the same name as used in the GIS 1d_bc and 2d_bc layers. It may contain spaces and other characters, but must not contain any commas. It is not case sensitive.
As of Build 2005-05-AN, the name of a group of boundaries can be used for RAFTS (.loc and .tot files) and WBNM (via the .ts1 file format) hydrographs. For example, if “N1|Local” is the boundary Name in a 1d_bc or 2d_bc layer, then the group is interpreted as the text to the right of the | symbol (ie. Local), and the text to the left is the ID (ie. N1) of the time-series data in the file containing the hydrographs. In this example, TUFLOW:
Searches for an entry “Local” in the Name column of the BC database.
Extracts the hydrograph for node N1 from Q100.ts1.
Using this approach the size of the BC Database .csv file can be reduced from several hundred lines for large hydrologic models to a couple of lines.
n/a
Source
The file from which to extract the BC data. Acceptable formats are:
Blank – if left blank, the BC data is assumed constant over time at the value specified under the Column 2 (Value) column (see Column 2 keyword below).
Comma delimited (.csv) files. Must have a .csv extension.
TUFLOW .ts1 time-series boundary data format (incorporated in Build 2003 06 AE).
RAFTS-XP .tot and .loc files. As of Build 2003-09-AA, both 12 and 16 field output is supported.
WBNM _Meta.out files.
ESTRY fixed field file containing boundary condition. Must be a .eef, .ebc or .ecf extension.
TUFLOW fixed field file containing boundary condition. Must be a .tbc or .tef extension.
