Zum Hauptinhalt springen

GGU-BORELOG: "Horizons" button: Input using SEP abbreviations

SEP stands for SchichtenErfassungsProgramm.

The SEP program, Version 2 of which is implemented in GGU-BORELOG, was developed by LBEG (Landesamt für Bergbau, Energie und Geologie, formerly: Niedersächsisches Landesamt für Bodenforschung, NLfB) in Hannover and allows the acquisition of data collected in field investigations. The SEP 2 program includes a set of abbreviations that can also be selected for use in the GGU-BORELOG program for entering strata using abbreviations. If you have the GGU-STRATIG program (graphical presentation of stratigraphic logs), as well as GGU-BORELOG, you can achieve the highest possible compatibility between the data sets of both programs by exclusively using the SEP 2 abbreviations.

For a detailed study of the SEP 2 abbreviations please see the SEP 2 manual, available from the LBEG. After bore or sounding input, GGU-BORELOG allows saving in a SEP 2 compatible format, if you have used the SEP 2 abbreviations. You can thus achieve a high degree of compatibility to other applications. Loading of files created with the SEP 2 program is also supported.

The abbreviations defined by LBEG for the "Engineering geology" subset are included in the "SEPKURZ-e.TXT" file, which is included with the program. The existing SEP 2 abbreviations can be viewed, printed and, if necessary, modified in the menu item "Edit/SEP abbreviations" together with the long texts and short texts, and the code numbers for controlling soil column hatching.

If files created using modified SEP 2 abbreviations are forwarded to third parties, compatibility with the receiver's programs cannot be guaranteed, because the modified abbreviations are not available and cannot therefore be interpreted.

If data forwarding is required, e.g. at the client’s request, it is better to work with the original SEP 2 file (for transfer to the SEP 2 program) or to send the modified "SEPKURZ-e.txt" file with the data (for transfer to GGU-BORELOG and GGU-STRATIG).

A SEP 2 abbreviation line consists of seven input areas :

  • Depth

  • Stratigraphy (age)

  • Petrography (main soil types + accessory soil types + characteristics if necessary)

  • Genesis (origin)

  • Colours

  • Supplements

  • Samples

These input areas are each separated by a " / ".

In the petrography field, the main and accessory soil types are separated by a " ; ".

Several abbreviations within a field are separated by commas " , ".

Depth / Stratigraphy / Petrography (main) ; Petrography (accessory) / Genesis /
Colours / Supplements / Samples

The SEP 2 program allows an abbreviation line length of 256 characters. GGU-BORELOG also allows this line length. If the number of abbreviation characters goes above a value of 60, the input window will scroll horizontally to the left. With the [Pos1] key you can return to the beginning of the line. With the [End] key you can move to the end of the abbreviation line.

The abbreviation area Petrography includes the SEP 2 abbreviations for main soil types and accessory soil types. in addition, abbreviations for properties can be entered in any position in the petrography field, e.g. information on grain roundness for a fine gravel fraction or on lime content. The abbreviations and corresponding long texts can be found under "Edit/SEP abbreviations" by pressing the dialog box button "Petrographic properties".

In the abbreviation line, the main soil type and accessory soil types are separated by a semicolon. This separation is important if the data entered in GGU-BORELOG are to be graphically displayed in GGU-STRATIG. In GGU-STRATIG, everything before the semicolon is treated as the main soil type during long text allocation. Everything after the semicolon is treated as accessory soil types. The assignment of the long texts to the 3 long text lines A1, A2 and B in GGU-STRATIG is done accordingly. If only 1 main soil type and 1 accessory soil type with a small batch are present, enter the "#" character as a placeholder for the non-existent 2nd main soil type, so that the graphical representation of the soil signatures and colours of the soil types is interpreted correctly when your file is transferred to GGU-STRATIG (see Section Data exchange with GGU-STRATIG). The placeholders can also be used if, for example, you wish to describe a fill, but the explanatory soil types are not to be displayed (e.g.: 2,35// A,#,#,#; mS, fs2, u4// bn).

Quality information is noted by a number associated with the corresponding abbreviation. They are allocated as follows: "1" = "very slight", "2" = "slight", "4" ="strong", "5" = "very strong". It is not necessary to enter the "3" = "middle".

  • Example:
    The following horizon is to be entered:
    Horizon base = 2.35 m
    Medium sand, slightly fine-sandy, very silty, brown, soil group SU*,
    stratigraphy, genesis and samples not present
    The abbreviation line is:
    2.35// mS, #; fs2, u4// bn/ SaU2
    After pressing the "Interpret" button all input will be converted to long texts.

If an input is not required in an area, simply leave the area empty - in the above example: stratigraphy and genesis. The slash to the next area follows directly.

Unnecessary fields at the end of the abbreviation line are simply left blank - in the above example: no samples. The line ends after the soil group abbreviation.

For colour input, two colours can also be combined. For example:

  • gero ==> yellowred (ge = yellow; ro = red)

  • dbn ==> dark brown (d = dark; bn = brown)

If an "=" is entered after the colour abbreviation, the long text will be supplemented with "ish". For example:

  • ge= ==> yellowish

  • ro= ==> reddish

If an abbreviation from a different input area is to be used in any of the areas, the area designation

  • S: for Stratigraphy

  • P: for Petrography

  • G: for Genesis

  • F: for Colours

  • Z: for Supplements

must be entered. For example:

  • 2.35// mS, #; fs2, u4, F:bn/// SaU2
    The colour brown (bn) will thus be interpreted into the "Petrography" area.

Free text can be entered into any area. The free text must be entered in apostrophe's. For example:

  • 2.35//'Construction rubble', mS, #; fs2, u4// bn/SaU2
    The free text Construction rubble will thus be interpreted into the "Petrography" area.

If you would like to have the long text in brackets, simply enter these at the desired position in the abbreviation line. For example:

  • 2.35//'Construction rubble', (mS, #); fs2, u4// bn/SaU2
    Medium sand, in long text, will then be placed in brackets.

Using the Supplements field in the SEP 2 abbreviation line it is possible to record the soil group, the consistencies or the drilling progress in the corresponding fields of the bore log form. The allocations are defined by the column names in the "SEPKURZ.txt" file (also see menu item "Edit/SEP abbreviations", dialog box button "Supplements"). It is also possible to combine a number of abbreviations, e.g. "kos2-kos3" for consistencies "soft to firm".

In the supplements field abbreviations are also provided for describing groundwater conditions. The depth information is entered in brackets following the abbreviation. Additional descriptions, e.g. the date, are entered in single quotation marks and follow after the depth data and a space or comma.

The brackets containing the depth data must immediately follow the groundwater abbreviation, without a space.

The decimal separator for depth input must be a point, not a comma.

Example:

  • 2.35// 'Building waste', mS, #; fs2, u4// bn/ SaU2, bv3-bv4, gws(2.66,'30.07.22')
    This means that in the DIN 4022 form, for example, the soil group in column "2h" is entered as "SU*", "medium - difficult to drill" is entered in column "2d" and "GW risen to (2.66, 30.07.22)" in column "3".

Input of samples and their designations follows at the end of the abbreviation line. After the final supplement input enter a " / " and begin with the depth from which the sample was taken.

It is important that the sample depth information is entered using a decimal point, not a comma.

You can then enter the field designation in brackets. For the type of sample, the SEP abbreviations are available once again, which you can view or supplement in "Edit / SEP abbreviations", button "Samples". The sample type (e.g. special sample) must also be placed in brackets and be separated from the sample designation by a comma. If a further sample has been taken from the same horizon, separate the entries with a " ; " and enter the depth, number and type in the same sequence.

  • For example the entry
    ....... / 1.2 (Gl 1) , (bp1) ; 1.4 (Gl 2) , (so)
    means very poor quality bore sample (= bp1) at a depth of 1.2 m in glass 1 and a special sample (= so) at a depth of 1.4 m in glass 2

The sample base level is entered in the format shown above. If the top and bottom of the sample need to be displayed, the appropriate check box must first be activated under "Edit/SEP abbreviations", dialog box button "Preferences". Depth input then follows the example below:

  • ......./ 1.0-1.2 (Gl 1), (kp)
    This allows both depths to be used in the form.

The SEP 2 program is much more consequential than the DIN 4022. The genetic expressions topsoil, boulder clay, fill, etc., e.g., are thrown into one pot with purely petrographic expressions (e.g. sand, gravel, etc.) in DIN 4022. If you would like to enter these genetic expressions in the first position in the long text line, using GGU-BORELOG (e.g. to 1.2 m fill, sand, silty), you must enter the following abbreviation line:

  • 1,2// G:y, S, u

Where "G:" stands for the genetic abbreviation subset and the "y" is the SEP 2 abbreviation for fill from this subset. In principle, it also imaginable to enter the "y" abbreviation, together with the long text "fill" into the petrography subset. This procedure may be pragmatic, as you can do without input of the "G:", you will, however, lose compatibility to the SEP 2 program. The functionality of the GGU-BORELOG program will not be restricted in any way. You can also create a completely different set of abbreviations with completely different long texts.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.