Time Varying Fields
The Time Variable Data Field is a new option available in EE 10. This option allows users to specify the time or spatially varying forcings for each cell over the whole model domain. This option uses the Time Varying Field (TVF) data format designed to bridge EFDC+ and other data facilities or numerical models. By using this data format, EFDC+ can receive time varying forcings within its computational domain from external sources. The data format for a TVF file includes ASCII and binary formats described in Appendix B-26. Although the pre- and post-processing of EFDC+ Explorer can be able to read, write, and view TVF data but at this stage, the creation of TVF data should be done externally.
Temporally and spatially varying forcings can be useful in many applications, such as outlined below:
- topographic update (e.g., dredging/dumping, land reclamation)
- bottom roughness (e.g., seasonal roughness)
- vegetation (e.g., seasonal vegetation)
- groundwater/seepage
- wind (cyclones)
- barometric pressure (cyclones)
- wind shelter
- atmospheric shading
- rainfall
- evaporation
- snowfall
- snow thickness
- ice thickness
Currently, the options are implemented in EFDC+ including topography, bottom roughness, groundwater seepage, rainfall, evaporation, wind and barometric pressure.
To illustrate this approach, an example simulated the pressure changes caused by a given hurricane. Storm simulation models can export this data at high resolution and can then be imported for use in EE. Right mouse click to Pressure under External Forcing Data tab, Time Varying Fields sub-tab and then the Time Variable Data Field: Air Pressure will be displayed. If the Data Option menu is set to Not Used for pressure, then the pressure field from the external forcing for atmospheric data series will be applied. (Figure 1).
Figure 1. Time Variable Data Field form.
To create the PRESFLD file, from Time Variable Data Field form, users should click on Generate button to open Field Data Interpolation form and link all individual data series. Users may also create a list in a text or Excel file includes 4 columns are stations ID; X coordinates in UTM, Y coordinate in UTM; and the path of the data series respectively and then open this text file as shown in Figure 2 below. It is advised to ensure that individual data series files are in the format: the number of records, series name, time and value (see Appendix B-26 for an example). Users may also select whether to apply linear interpolation and whether or not to replace existing data with new data from the drop-down menus. Once these linkages are developed select Generate button.
Figure 2. Field Data Interpolation form.
Additionally, EE 10 also allows users to load the data files in ASCII or binary format. When the time varying field data is large, users also have an option to convert data from ASCII format to binary format by using Convert Time Varying Fields under Tools tab from the main form toolbar (Figure 3).
Figure 3. Convert Time Variable Data Field from ASCII to binary.
Once the field is generated, EFDC will use this field in place of the other forcings defined by the user to simulate. Users may review the forcing fields in 2DH View by selecting Forcing Fields from the 2DH View Option as shown in Figure 4.
Figure 4. 2DH View Option form.
Time Varying Field Data Formats, File Names, and Units
As described above TVF data can be saved in either ASCII or binary formats. The ASCII file format allows users to create or modify the data manually, but it requires much more disk space than a binary file format. The binary format can reduce the file size significantly and optimize the file loading, but it limits users in reading and modifying the data manually. EEMS reads the entire ASCII file into the memory so it may take a long time to load a large ASCII file. With the binary format, EEMS reads only data for one time step into the memory at a time so the performance is improved significantly. Once the data is loaded, EE allows users to switch the file format between the ASCII or binary formats and the corresponding file format will be created when the user saves the model.
The file name for the TVF data is fixed for different data type and has a general pattern of *FLD.*. The file extension for the ASCII format is *.INP, and the file extension for the binary format is *.FLD.
The following table lists the file names associated with different data types
Table 1. List of file names for several TVF data
# | File name | EFDC Variable | Descriptions and Model Units |
1 | TOPOFLD | TOPO | Bottom elevation in meters (e.g., dredging/dumping, land erosion/reclamation) |
2 | ROUGHFLD | ROUGH | Roughness height in meters (e.g., seasonal roughness) |
3 | VEGEFLD | VEGE | Vegetation (e.g., seasonal vegetation) (not yet implemented) |
4 | GWSPFLD | GWSP | Groundwater/seepage flow (inflow is positive, outflow is negative) IDST = 0: Groundwater inflow in m³/s IDST = 1: Groundwater seepage in m/s |
5 | WINDFLD | WIND | Wind speed in m/s (e.g., cyclone) |
6 | PRESFLD | PRESS | Barometric pressure in hPa (e.g., cyclone) |
7 | RAINFLD | RAIN | Rainfall (positive values in m/s) |
8 | EVAPFLD | EVAP | Evaporation (positive values in m/s) |
9 | SHELFLD | SHELT | Time varying wind shelter (not yet implemented) |
10 | SHADFLD | SHADE | Time varying sun shading (not yet implemented) |
11 | SNOWFLD | SNOW | Snow (snow depth, snowfall, …) in meters (not yet implemented) |
12 | ICEFLD | ICEFLD | Ice (thickness, temp., …) in meters (not yet implemented) |
13 | ZLJDLF | ZLJER | SEDZLJ erosion rate (factor A and power N) (not yet implemented) |