...
| Panel | |||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Example of wind:
These series will be interpreted as:
Another example of wind: There are 2 time series in the file wind.xml
These series will be interpreted as:
In this example no additional wind fields are written. |
...
type | description |
|---|---|
undefined | not allowed as type |
rainfallfile | converts full contents of the file into RR rainfall file. All series should have same time stamps. File name will be *.bui and will be written in cmtwork. Case registry will be updated, so the file will be used in the computation |
rrrestart | rr restartfile (state file) |
flowrestart | flow restart (state file) |
flow_hc_boundary | H boundary with constant value |
flow_ht_boundary | H boundary with timeSeries |
flow_qc_boundary | Q boundary with constant value |
flow_qt_boundary | Q boundary with timeSeries |
flow_htref_boundary | H boundary with timeSeries from ref.table |
flow_qtref_boundary | Q boundary with timeSeries from ref.table |
windfile | wind, should be a single PI file |
flow_latndc | lateral flow on connection node, constant value |
flow_latndt | lateral flow on connection node, time series |
flow_latndref | lateral flow on connection node, time series from ref.table |
flow_latbrc | lateral flow on node at branch, constant value |
flow_latbrt | lateral flow on node at branch, time series |
flow_latbrref | lateral flow on node at branch, time series from ref.table |
flow_latdic | diffuse lateral flow on branch, constant value |
flow_latdit | diffuse lateral flow on branch, time series |
flow_latdiref | diffuse lateral flow on branch, time series from ref.table |
flsboundline_hc | H line boundary on grid, constant value |
flsboundline_ht | H line boundary on grid, time series |
flsboundline_qc | Q line boundary on grid, constant value |
flsboundline_qt | Q line boundary on grid, time series |
flsboundnode_hc | H boundary node on grid, constant value |
flsboundnode_ht | H boundary node on grid, time series |
flsboundnode_qc | Q boundary node on grid, constant value |
flsboundnode_qt | Q boundary node on grid, time series |
flsinitpoint | initial condition point at grid |
rr_up_seepdef | rainfall-runoff seepage definition ID, (no timeSeries!) |
rr_up_stordef | rainfall-runoff storage definition ID, (no timeSeries!) |
rr_up_alfadef | rainfall-runoff alfa drainage coeff. definition ID, (no timeSeries!) |
rr_up_infdef | rainfall-runoff infiltratie definition ID (no timeSeries!) |
rr_up_initdef | rainfall-runoff initial definition ID (no timeSeries!) |
rr_up_ernstdef | rainfall-runoff ernst drainage coeff. definition ID, (no timeSeries!) |
rr_insodemandtable | rainfall-runoff industrial demand time series, like a lateral flow. Note: a dummy salt concentration of 0 mg/l will be used! |
rr_insodischargetable | rainfall-runoff insdustrial discharge time series, like a lateral flow |
evapfile | converts full contents of the file into RR evaporation file. All series should have same time stamps. File name will be *.evp and will be written in cmtwork. Case registry will be updated, so the file will be used in the computation |
rtc_par3 | RTC, parameter3 record ID |
rtc_rule | RTC, rule record ID |
rtc_maxf | RTC, maxf record ID |
rtc_engd | RTC, engd record ID |
flow_timecontroller_tiwithbltbl | 1D flow structure time controller, time series |
flow_intervalcontrollersetpoint_tiwithbltbl | 1D flow structure interval controller setpoint, time series |
flow_controllerpidsetpoint_tiwithbltbl | 1D flow structure PID setpoint, time series |
1dwq_fraction_concentration_tiwithbltbl | 1d waq substance concentration for fraction type, time series |
1dwq_boundary_concentration_tiwithbltbl | 1d waq substance concentration for local boundary, time series |
2dwq_fraction_concentration_tiwithbltbl | 2d waq substance concentration for fraction type, time series |
2dwq_boundary_concentration_tiwithbltbl | 2d waq substance concentration for local boundary, time series |
fls_restart | fls restart / state |
1dwq_restart | 1d waq restart / state |
2dwq_restart | 2d waq restart / state |
1d_flow_dam | 1d flow weir object, representing a obstruction in the river |
1d_flow_dambreak_hc_boundary, 1d_flow_dambreak_connectionnode | do exactly the same: create a breach in the dike |
rr_temperature | temperature for the RR module, should be a single PI file |
1d_flow_lateral_dat_file | Converts the complete contents of a PI xml file into a 1D flow lateral.dat file. The PI locationID should be used to map to the lateral IDs (any type). The parameter (and qualifier) is not used. All series in the XML should exist as definition with a time series table in the SOBEK lateral .dat file. Vice versa is not needed, as SbkBatch only updates the definitions. |
rr_boundarytable | rainfall-runoff boundary node, water level time table. Note: a dummy salt concentration of 0 mg/l will be used! |
| 1d_flow_boundary_dat_file | Converts the complete contents of a PI xml file into a 1D flow Boundary.Dat file. The PI locationID should be used to map to the boundary IDs. The parameter (and qualifier) is not used. All series in the XML should exist as definition with a time series table in the SOBEK boundary.dat file. Vice versa is not needed, as SbkBatch only updates the definitions. |
| 1d_flow_control_def_file | Converts the complete contents of a PI xml file into a 1D flow control.def file. The PI locationID should be used to map to the control def IDs (of time controller type). The parameter (and qualifier) is not used. All series in the XML should exist as definition with a time series table in the SOBEK control.def file. Vice versa is not needed, as SbkBatch only updates the definitions. |
| 1d_flow_profile_def | changes the reference to a cross section definition in profile.dat. The sobekObjectId should refer to the record in the profile.dat, while the classFile(s) refer to the records in the profile.def. Typically used in batching runs with varying cross sections per run. |
| greenhouse_water_usage_file | Convert the complete contents of a PI xml file into the \sobek\fixed\3b\KasGebrData.Dat file, which is referred to in the sbkbatch.ini key [General]KasGebrDataFile=.... In delft_3b.ini [Options]NewFormatKasdata should be -1 and greenhouse node definitions should be setup to using this new format (which is not supported by the GUI). All series in the XML are converted to update existing definitions in the KasGebrData.Dat. Note that this file is not register to in the case registry ,so updating this file may affect other cases too. Only definition with single column tables are supported. The PI locationID should be used to map to the kasgebr IDs . The parameter (and qualifier) is not used. All series in the XML should exist as definition with a time series table in the SOBEK kasgebr file. Vice versa is not needed, as SbkBatch only updates the definitions. |
| rr_runoff_rnf | Converts the complete contents of a PI xml file into a *.rnf file. Can only be used in case also a rainfallfile is used, so sbkbatch can write it to the same base file name as the RR module uses that. |
| rr_openwater_target_level_timetable | Converts one individual timeseries into a OW_T table in openwate.tbl |
| rr_openwater_target_level_timetable_file | Converts a complete PI xml (so all timeseries) into a OW_T tables in openwate.tbl, based on locationid |
| rr_timecontroller_tbl_file | Converts a complete PI xml (so all timeseries) into a INST tables in struct3b.tbl, based on locationid |
| 1d_flow_trigger_def_file | Converts a complete PI xml (so all timeseries) into a CNTL tables in control.tbl, based on locationid |
| wq_meteofile | Converts a complete PI xml (so all timeseries) into a Delwaq format file (based on parameterid, locationid is ignored). This file is called wqmeteo.mwq and is included in the delwaq wq computation |
...