The file starts with three comment rows, followed by a blank row. This is followed by the entry for the time unit (+ blank row), the model type (+ blank row) and the scale (+ empty row). After the node coordinates and element incidences, the various data types are entered in any order. The individual data types are each summarised in a data block. Each data block consists of a data identification row, the data rows, and ends with a final blank row. There must be no other blank rows in a data block. A data identifier (upper or lower case) is specified for each data type and must be entered in the first four columns of the data identifier line. A permissible identifier consists of a combination of 4 letters or numbers (an underscore is also permitted). This data identifier can be extended (for commentary purposes) over the entire row .

The following graphic shows the structure of a mesh file:

 

LineComment row

LineComment row

LineComment row

LineBlank row or INUMx, CRS=EPSG:25832 (Coordinate system)

LineZEITeinheit (Time unit)

LineBlank row

LineHORIzontal model (Model type)

LineBlank row

LineMASSstab (Scale data)

Line... (scale data)

LineBlank row

LineKOORdinaten (data identification row)

Line... (coordinate data)

...

Blank row

ELEMents (data identification row)

... (data)

...

Blank row

TRANsmissivities (data identification row)

... (data)

...

Blank row

POTEntial (data identification row)

... (data)

Blank row

If a coordinate system is defined in the model, this is displayed in the 4th line after INUMx.

 

Format description:

The geometric data types (node and element incidences) and all attributes are saved in the *.net and *.3d files during modelling in SPRING. The user should NOT manually edit the node and element incidences, as this can lead to significant errors in the FE mesh.

Should it nevertheless be necessary to edit the attributes in the model file manually, the following standard format applies to almost all attributes:

Columns 1 - 14: Value assignment using the following possible formats

• A maximum of 14-digit real number as a floating point number, e.g. "14.99" or "-1.234"

• Exponential format: e.g. "1.e-7" or "-2.5e+10"

 

The values must always have a decimal point.

 

Columns 15 - 16: Special characters:

• For some attributes, it is possible to set a special character in column 15 or 16 (e.g. F, /, *), which influences the processing of the values. These characters are explained in the individual data types.

 

Column 17 – 79:

 

• Node or element integer numbers in the format I6, the number is followed by a comma or a hyphen for a number sequence from .... to

• The element or node integer numbers are entered in the I6 FORTRAN format as long as no number equals or exceeds a million. To manage larger numbers, the keyword NUM with a decimal place appended must be entered in the fourth line of the *.net file. INUM values less than six are ignored. The following fixed formats are then changed from I6 to I/NUM

 

Column 80:

• If the value assignment to a data type extends over more than one row, a "+" can be set in column 80 to connect the rows.

 

Each attribute block must end with a blank row.

 

Comment rows can also be inserted between the individual data blocks. These begin with a 'C' and three blank spaces ('C '). Comment rows are ignored during the model checks.

Some types of data (e.g. flooding or van Genuchten parameters) are saved in a particular format. As this is done automatically in SPRING, the user does not have to edit this.

 

 

3D file *.3d