Data Format B-1 P2D Polyline / and Polygon File.
Any number of polylines /or polygons can reside in the same file. Each one begins with a single line header that is used as the "ID" of the polyline /or polygon. Next comes the data in either 2D or 3D format, the importing automatically handles either. Finally, the polyline /or polygon is finished (not necessarily "closed") by an "*" in column 1. There is no difference between polyline and polygon in a P2D file, only how the data are treated by the application reading the file.
Example
------------------------
Polyline Test
...
Data Format B-2 TB2 XYZ Gridded Data.
This format is a compact way to store regular grid X, Y, and Z data. It contains three lists, each with the number of data points as the first value in the list. The file contains a list of the X coordinates, a list of Y coordinates, and a list of the Z's.
Example
------------------------
195 Nx
...
-28.1969829
...
...
...
Data Format B-3 DX Polyline /and Polygon File.
The DX format is described by in the following outline. The vertical bar "|" indicates the actual left side of the file.
...
Loop over the number of vertical profile locations
Line 1: ID (any user defined ID)
Line 2: Xc, Yc, nPts (nPts in vertical profile)
Loop over nPts
Input Depth (Positive depths below the water surface, m)
End Loop
Loop over nPts
Input Parameter_Value (units dependent on the parameter)
End Loop
End Loop
...
Data file containing observation data (.wq,.dat) | Description |
10993 USGS_Speedy, Salinity, PPT | First line: 10993: number (N) of data points; USGS_Speedy, Name, Units: title for some meaning (here: station name, water temperature in Celsius degree). This text is only used for labeling. |
...
SE 03, Unknown (Unknown) @ 573370.8125, 3009112 | First line: Title for some meaning (here: station name, coordinate) This field is not used by EE. |
Data Format B-9 Polygon DSM Format
The "Polygon" Digital Sediment Model (DSM) format is a file that contains any number of polygons that define an area followed by a data block that contains the sediment data. The polygon ID and the data block ID's must match. The data block consists of a line for each depth (beginning at the surface or 0.0 depth) for which data exists. On each line, the user must include the depth (m), thickness (m), porosity, and then the grain size. The number of grain size classes and the associated size breaks are determined by the space-delimited data of the label line (see example). The number of grain size classes and their sizes must be the same for every sediment data block in the file. However, the size classes can vary from file to file or project to project to meet the project needs.
Example
...
Data Format B-10 Sediment Cores with Grainsize DSM Format
The "Sediment Cores with Grainsize" Digital Sediment Model (DSM) format is a file that contains any number of cores. Each core can have any number of samples at depths below the top of the core. For each core, the user must locate the core in horizontal (XY) space. The "Z" requested is the top of the core elevation (i.e. the bottom elevation at the core location).
Title Line
"Discrete" Flag: Used to determine the data file format
Loop over groupings of cores (Loop Terminated by the "END" statement)
...
Explanation of the header fields:
Table 1: Description of the data field in TVF file header
INPT | Input format: INPT = 0: The number of values and its order for each component the field in each time step is the same as grid cells. INPT = 1: The number of values each component the field in each time step can be less than the number of the grid cells but the data lines should have cell indices (NL, IC, JC) in front of data values. |
NT | Number of time steps. |
NC | Number of components. NC=1 for bathymetry, bottom roughness, barometric pressure, etc. NC=2 for wind fields (X and Y components of wind speed). |
NL | Number of grid cells. This is for QC to ensure the data matches the model grid. |
NK | number of vertical layers (NK = 1 for this version). |
ITRP | Interpolation option: ITRP = 0: no interpolation, direct field applied at each time step. ITRP = 1: linear interpolation between time steps. |
IUPD | Flag to direct EFDC on how to update the current cell value with the reading value. IUPD = 0: The cell value will be replaced by the reading value. IUPD = 1: The cell value will be added with the reading value. IUPD = 2: The cell value will be the min. of the current cell value and the reading value. IUPD = 3: The cell value will be the max. of the current cell value and the reading value. |
IDST | Specific option for data operation after interpolation IDST = 0: Cell value = field value IDST = 1: Cell value = field value multiplies cell area |
TSCL | Conversion factor to convert time values to seconds (default 86400) |
TSHF | Time offset having the same unit as time values (default 0) |
VSCL | Conversion factor to convert the field values to the same units as in EFDC (default 1) |
VSHF | Value offset having the same unit as the field values (default 0) |
NODAT | No data value. Cells having this value will not change/not be updated by reading values. |
YY | The year of the base date |
MM | The month of the base date |
DD | The day of the base date |
...
Each data block for one time step begins with the time value (in Julian days from the base date) and a number of grid cells to which the data will be applied for (should be the same as NL for INPT = 0).
For INPT = 0, the number of the data values for in each block should be NC × NL × NK values and the FORTRAN command to read the data is as follows
...
For INPT = 1, the number of the data values for in each block can vary and the FORTRAN command to read the data is as follows
...
The file header has a length of 80 bytes with the data fields are as the table bellows:
Description of the data field in a binary TVF file header
...
For INPT = 0, the number of the data values for in each block should be NC × LC × NK values and the FORTRAN command to read the data is as follows
...
For INPT = 1, the number of the data values for in each block can vary and the FORTRAN command to read the data is as follows
...