...
- The legitimate versions of the GEFID for this keyword are listed in the same line as the caption for Keyword. For an explanation about versions, see versions.
- Type of Data lists the minimum type of variable to hold the information in the field. For examples and restrictions for "Type of data", see the table of datatypes.
- Strings as in Param3 must obey the rules as stated for information fields, see special characters.
- Param4 is in between brackets. It is optional, so it may be omitted.
- Param5 is optional. The brackets around Param5 are nested within the brackets of Param4. This means that if Param4 is omitted, Param5 should be omitted as well.
- Valid examples for use of Keyword are:
- #Keyword=12, The number PI, 3.141592653589793238, 3.1415926, 98765
- #Keyword=12, The number PI, 3.141592653589793238, 3.1415926
- #Keyword=12, The number PI, 3.141592653589793238
_________________________________________________________________________________________________________________________________________
...
ANALYSISCODE
ANALYSISCODE
Anchor | ||||
---|---|---|---|---|
|
(version: 1,0,0 / 1,1,0 / 2,0,0)
#Analysiscode=Code, Release, Version, Update[, Reference]
...
Note. Via this keyword, a program can determine whether the data is suitable for analysis using this version of the program. This prevents a program designed to work out, for example, a dry critical density test from importing data from a compression test. In addition, tests which still need to be analysed using an older version, can be processed using the most suitable method.
ANALYSISTEXT
Anchor | ||||
---|---|---|---|---|
|
(version: 1,0,0 / 1,1,0 / 2,0,0)
#Analysistext=Index, Text[, Information]
...
Example: #Analysistext=129, Cohesion calculated in accordance with NEN, comments.
ANALYSISVAR
Anchor | ||||
---|---|---|---|---|
|
(version: 1,0,0 / 1,1,0 / 2,0,0)
#Analysisvar=Index, Value, Unit, Quantity
...
Example: #Analysisvar=129, 1.33,-,over-relax factor for creep.
CHILD
Anchor |
---|
...
|
...
|
(version: 1,1,0 / 2,0,0)
#CHILD= Index, Reference[, value, Unit, Quantity[, Quantity number[, Explanation]]]
...
- Child is only listed in files of tests during which other tests are performed; e.g. child is listed in GEF-CPT-Report.
- The reference item in the child keyword must hold an unique identifier as a link to the child. It is usually a name of a file. Other possibilities are objectids or a primary key in a database. The reference field may contain up to 1023 characters. This item is compulsory.
- When files are transferred between different clients, one should avoid using path names, since there is no guarantee for a unique directory structure.
- The items Value, Unit and Quantity are optional. They form a group of items. If a Value is given, the Unit and Quantity must be given as well. The reason is, that if Unit is omitted, it is impossible to know what the Value really means. Unit and Quantity are conditionally compulsory. If a value without a dimension is to be listed, e.g. merely a number, Unit is marked by '-'. For each type of value a description for Quantity can be given: e.g. a number of a scan, a depth or a date (20000419)
- The item Quantity number is optional. It allows for an automatic recognition of the type of test. If Value, Unit and Quantity are not listed, Quantity number can not be listed as well.
- The item Explanation is optional. If the Quantity number is not listed, Explanation can not be listed either.
COLUMN
Anchor |
---|
...
|
...
|
(version: 1,0,0 / 1,1,0 / 2,0,0)
#Column=Column
Column | int | A number between 1 and 250. This gives the number of columns which are in the data block. |
...
Note. For a binary file, it is assumed that #Column observations, consisting of 4-bytes floating point numbers, belonging to a scan, are stored. Also see Datatype.
...
COLUMNINFO
COLUMNINFO
Anchor | ||||
---|---|---|---|---|
|
(version: 1,0,0 / 1,1,0 / 2,0,0)
#Columninfo =Column, Unit, Quantity[, Qnumber]
...
Example: #Columninfo=3, kPa, deviator pressure, 1001.
...
COLUMNMINMAX
COLUMNMINMAX
Anchor | ||||
---|---|---|---|---|
|
(version: 1,0,0 / 1,1,0 / 2,0,0)
#Columnminmax=Column, Min, Max
...
Example: #Columnminmax=5, 0.17, 5.68.
...
COLUMNSEPARATOR
COLUMNSEPARATOR
Anchor | ||||
---|---|---|---|---|
|
(version: 1,0,0 / 1,1,0 / 2,0,0)
#Columnseparator=Char
Char | char | This is a character (to be printed in ASCII) which will be printed between each column, making it easier to import data with so-called spreadsheet programs or databases. See also Recordseparator. |
Example: #Columnseparator=;
Remark: the characters \#=+-.,DEGdeg0123456789 are not allowed as columnseparator. Furthermore Columnseparator and Recordseparator must differ.
COLUMNTEXT
Anchor |
---|
...
|
...
|
(version: 1,0,0 / 1,1,0 / 2,0,0)
#Columntext=State[, Remarks]
...
Example: #Columntext=1.
COLUMNVOID
...
COLUMNVOID
...
Anchor | ||||
---|---|---|---|---|
|
(version: 1,0,0 / 1,1,0 / 2,0,0)
#ColumnVoid=Column, Value
...
Note. Instead of using a letter of a word, it was decided to define a figure to indicate that no suitable information is present at the position, so the possibility of using the columnvoid keyword in binary data blocks was not blocked.
COMMENT
Anchor |
---|
...
|
...
|
(version: 1,0,0 / 1,1,0 / 2,0,0)
#Comment=Text
Text | string | Optional random text, not necessary for the test, rather an annotation but as a marginal note. A maximum of 1500 comment lines can be stored. Maximum 255 characters. |
...
Example: #Comment=Repeat of the test of 1995-06-25.
...
COMPANYID
COMPANYID
Anchor | ||||
---|---|---|---|---|
|
(version: 1,0,0 / 1,1,0 / 2,0,0)
#Companyid=Name, Taxcode, CountryID
...
Example: #Companyid=GEODELFT, 8000.97.476.B.01, 31.
...
DATAFORMAT
DATAFORMATo
Anchor | ||||
---|---|---|---|---|
|
(version: 1,0,0 / 1,1,0 / 2,0,0)
#Dataformat=Type
Type | string | Text stating whether the readings in the data block are stored as an ASCII or BINARY file. |
...
Note. Only ASCII and BINARY are permitted. Binary data storage can be imported and processed extremely rapidly. It is, however, system dependent. The data format default value is ASCII. Also see keyword OS.
DATATYPE
...
Anchor | ||
---|---|---|
|
...
|
(version: 1,0,0 / 1,1,0 / 2,0,0)
#Datatype=Type
Type | string | Text stating which type of numbers are stored in the data block. |
...
Type | Description | Number of bytes | Example |
byte | flag | 1 | 1 |
int2 | integer number | 2 | -30000 |
long | integer number | 4 | 2123456789 |
int4 | integer number | 4 | 2123456789 |
real4 | decimal number | 4 | -3.14159 |
float | decimal number | 4 | -3.14159 |
real8 | decimal number | 8 | 6.62×10-34 |
double | decimal number | 8 | 6.62×10-34 |
string | text | variable | Measurement |
EOH
Anchor |
---|
...
|
...
|
(version: 1,0,0 / 1,1,0 / 2,0,0)
#EOH=
Example: #EOH=
Note. This keyword has no data behind the = character which needs to be used. In addition, this keyword is completed using a Line Feed (Unix) or the Carriage Return and the Line Feed (DOS). When using binary data, no text in the data block is allowed.
...
EQUIPMENT
EQUIPMENT
Anchor | ||||
---|---|---|---|---|
|
(version: 1,0,0 / 1,1,0)
#Equipment=Text
Text | string | Text stating the name of the equipment. |
...
Example: #Equipment=TS200.
...
FILEDATE
FILEDATE
Anchor | ||||
---|---|---|---|---|
|
(version: 1,0,0 / 1,1,0 / 2,0,0)
#Filedate=Yyyy, Mm, Dd
Yyyy | int | Year, when the file was created. Y2k compliant. |
Mm | int | Month, when the file was created. |
Dd | int | Day, when the file was created. |
...
Example: #Filedate=1995,02,20.
FILEOWNER
Anchor |
---|
...
|
...
|
(version: 1,0,0 / 1,1,0 / 2,0,0)
#Fileowner=Fileowner
Fileowner | string | Text stating the owner of the file. The file owner is responsible for the quality of the file. He/she is usually the same person who performed the test. |
...
Example: #Fileowner=Lambert Smidt.
FILINGCODE
...
Anchor | ||||
---|---|---|---|---|
|
(version: 1,0,0 / 1,1,0 / 2,0,0)
#Filingcode=Code, Release, Version, Update[, Reference]
...
Example: #Filingcode=B17, 3, 0, 1, NEN888888.
FILINGTEXT
...
Anchor | ||
---|---|---|
|
...
|
(version: 1,0,0 / 1,1,0 / 2,0,0)
#Filingtext=Index, Text[, Information]
...
Example: #Filingtext=129, Archiving in Oracle table PROJECT, tablename.
...
FILINGVAR
FILINGVAR
Anchor | ||||
---|---|---|---|---|
|
(version: 1,0,0 / 1,1,0 / 2,0,0)
#Filingvar=Index, Value, Unit, Quantity
...
Example: #Filingvar=133, 0.45, -,Location of the map.
FIRSTSCAN
Anchor | ||||
---|---|---|---|---|
|
(version: 1,0,0 / 1,1,0)
#Firstscan=Rownumber
Rownumber | long | The number of the first scan containing a meaningful value. |
Example: #Firstscan=13.
GEFID
...
Anchor | ||
---|---|---|
|
...
|
(version: 1,0,0 / 1,1,0 / 2,0,0)
#GEFID=Release, Version, Update
...
Note. This keyword must be the first one to appear in the file. It must be written in capital letters. Using the first line, operation systems like Unix are able to deduce the type of file and which program or printer is needed to control the file.
LANGUAGE
Anchor |
---|
...
|
...
|
(version: 1,0,0 / 1,1,0 / 2,0,0)
#Language=Language
Language | string | Abbreviation which states the language. Maximum 2 characters. |
...
Note. This keyword can influence the program which imports and analyses a GEF file. Default value is NL .
...
LASTSCAN
LASTSCAN
Anchor | ||||
---|---|---|---|---|
|
(version: 1,0,0 / 1,1,0)
#Lastscan=Rownumber
Rownumber | long | Number of the last meaningful scan. |
...
Note. The default value is 2147483648 (=231). (Nov 2000 I) The scans following the scan number in lastscan, are not processed.
...
MEASUREMENTCODE
MEASUREMENTCODE
Anchor | ||||
---|---|---|---|---|
|
(version: 1,0,0 / 1,1,0 / 2,0,0)
#Measurementcode=Code, Release, Version, Update[, Reference]
...
Example: #Measurementcode=Cu, 3, 1, 0, 300-1-CU.
MEASUREMENTTEXT
Anchor |
---|
...
|
...
|
(version: 1,0,0 / 1,1,0 / 2,0,0)
#Measurementtext=Index, Text[, Information]
...
Example: #Measurementtext=129, Temperature measured in accordance with NEN, temp. measurement.
MEASUREMENTVAR
Anchor | ||||
---|---|---|---|---|
|
(version: 1,0,0 / 1,1,0 / 2,0,0)
#Measurementvar=Index, Value, Unit, Quantity
...
Note. Measurementvar is used to store one-time measurements which form part of a test, such as temperature outside.
OBJECTID
...
Anchor | ||
---|---|---|
|
...
|
(version: 1,0,0 / 1,1,0 / 2,0,0)
#Objectid=Value
Value | long | Reference to a number in the archive where this GEF file belongs. |
...
Note. Objectid can refer to a (primary ) key in a database.
OS
Anchor | ||
---|---|---|
|
|
(version: 1,0,0 / 1,1,0 / 2,0,0)
#Os=Type
Type | string | Text stating for which operating system the data are stored. Maximum 10 characters. |
...
In the old days most Unix's were running on the generic type Motorola processors, which use Big Endian notation. DOS was running on the generic type of Intel processors, which use Little Endian representation. In the third column of Table 6 the number 16 is written down as a long integer, in hexadecimal notation.
...
PARENT
PARENT
Anchor | ||||
---|---|---|---|---|
|
(version: 1,1,0 / 2,0,0)
#PARENT= Reference[, value, Unit, Quantity[, Quantity number[, Explanation]]]
...
- Parent is only listed in files, which report tests that are performed as part of another test; e.g. parent will appear in a dissipation test.
- The reference item in the parent keyword must hold an unique identifier as a link to the parent test. It is usually a name of a file. Other possibilities are objectids or a primary key in a database. The reference field may contain up to 1023 characters. This item is compulsory.
- When files are transferred between different clients, one should avoid using path names, since there is no guarantee for a unique directory structure.
- The items Value, Unit and Quantity are optional. They form a group of items. If a Value is given, the Unit and Quantity must be given as well. The reason is, that if Unit is omitted, it is impossible to know what the Value really means. Unit and Quantity are conditionally compulsory. If a value without a dimension is to be listed, e.g. merely a number, Unit is marked by '-'. For each type of value a description for Quantity can be given: e.g. a number of a scan, a depth or a date (20000419)
- The item Quantity number is optional. It allows for an automatic recognition of the type of test. If Value, Unit and Quantity are not listed, Quantity number can not be listed as well.
- The item Explanation is optional. If the Quantity number is not listed, Explanation can not be listed either.
PROCEDURECODE
Anchor | ||||
---|---|---|---|---|
|
(version: 1,0,0 / 1,1,0 / 2,0,0)
#Procedurecode=Code, Release, Version, Update[, Reference]
...
Example: #Procedurecode=GEF-CPT-Report, 1,0,0.
...
PROJECTID
PROJECTID
Anchor | ||||
---|---|---|---|---|
|
(version: 1,0,0 / 1,1,0 / 2,0,0)
#Projectid=Type,[ Number,[ Sub]]
...
Example: #Projectid=CO, 342770, 624.
...
PROJECTNAME
PROJECTNAME
Anchor | ||||
---|---|---|---|---|
|
(version: 1,0,0 / 1,1,0 / 2,0,0)
#Projectname=Projectname
Projectname | string | Text stating the name of the relevant project. Maximum of 255 characters. |
...
Example: #Projectname= High Speed Line.
QNMINMAX
Anchor |
---|
|
...
|
(version: 2,0,0)
#Qnminmax=Qn, Min, Max
Qn | long | The quantity number to which the information relates. |
Min | double | Minimum value in the column associated with this quantity number. |
Max | double | Maximum value in the column associated with this quantity number. |
...
Example: #Qnminmax=3019, 0.17, 5.68.
...
QNTIME
QNTIME
Anchor | ||||
---|---|---|---|---|
|
(version: 2,0,0)
#Qntime=Qn[, Timecode[, Unit]]
...
Table 7 Value of Code and Unit
Timecode | Unit |
1 | second |
2 | minute |
3 | hour |
4 | day |
5 | week |
QNVOID
Anchor | ||||
---|---|---|---|---|
|
(version: 2,0,0)
#QnVoid=Qn, Value
Qn | long | The quantity number to which the information relates. |
Value | double | The figure which shows that the value does not contain suitable information. |
...
Note. Instead of using a letter of a word, it was decided to define a figure to indicate that no suitable information is present at the position, so the possibility of using the qnvoid keyword in binary data blocks was not blocked.
RECORDSEPARATOR
Anchor |
---|
|
...
|
(version: 1,0,0 / 1,1,0 / 2,0,0)
#Recordseparator=Char
Char | char | The character used to finish a data record. A data record always consists of a fixed number of registrations (the value is given by the #column). It is the physical end of the scan. Also see Columnseparator. |
...
(Nov 2000 I) Remark: the characters \#=+-.,DEGdeg0123456789 are not allowed as columnseparator. Furthermore Columnseparator and Recordseparator must differ.
...
REPORTCODE
REPORTCODE
Anchor | ||||
---|---|---|---|---|
|
(version: 1,0,0 / 1,1,0 / 2,0,0)
#Reportcode=Code, Release, Version, Update[, Reference]
...
Example: #Reportcode=Standard, 3, 1, 0, 300-1-SDS.
REPORTDATAFORMAT
...
Anchor | ||
---|---|---|
|
...
|
(version: 1,0,0 / 1,1,0 / 2,0,0)
#Reportdataformat=Layout
Layout | string | The layout of the values to be printed sLayout consists of a series of words, separated by blanks. The number of words must be equal to the number of columns, as started in #COLUMN=. Each word consists of one letter and one or more digits. This word determines how a value is printed. The convention of the FORTRAN format identifier is used:
|
...
Example: #Reportdataformat=F7.3 F7.3 E11.4 I6.
REPORTTEXT
Anchor |
---|
...
|
...
|
(version: 1,0,0 / 1,1,0 / 2,0,0)
#Reporttext=Index, Text[, Information]
...
Example: #Reporttext=129, Section 5 is confidential, general comment.
REPORTVAR
Anchor |
---|
...
|
...
|
(version: 1,0,0 / 1,1,0 / 2,0,0)
#Reportvar=Index, Value, Unit, Quantity
...
Example: #Reportvar=17, 66, -, number of pages.
...
ROW
ROW
Anchor | ||||
---|---|---|---|---|
|
(version: 2,0,0)
#Row=Rows
Rows | long | A number between 1 and 2147483647. This gives the number of rows which are in the data block. |
Example: #Row=1495.
SCANFREQ
Anchor |
---|
...
|
...
|
(version: 1,0,0 / 1,1,0 / 2,0,0)
#Scanfreq=Value, Startrow
...
Note. The scan frequency is expressed in Hz (s-1).
SCANTIME
...
Anchor | ||
---|---|---|
|
...
|
(version: 1,0,0 / 1,1,0 / 2,0,0)
#Scantime=Value, Startrow
...
Note. The time interval is expressed in s. In the example, a reading is carried out each minute. For scanfreq and scantime, startdate and starttime are to be used. The scans in the test are thus placed in absolute form in time.
...
SETUPCODE
SETUPCODE
Anchor | ||||
---|---|---|---|---|
|
(version: 2,0,0)
#Setupcode=Code, Release, Version, Update[, Reference]
...
Example: #Setupcode=S17, 3, 0, 1, NEN888888.
SETUPTEXT
Anchor |
---|
|
...
|
(version: 2,0,0)
#Setuptext=Index, Text[, Information]
...
Example: #Setuptext=250, Removing carbonates by H2SO4, carbonate removal.
SETUPVAR
Anchor |
---|
|
...
|
(version: 2,0,0)
#Setupvar=Index, Value, Unit, Quantity
...
Example: #Setupvar=250, 45.89, g, Mass of removed carbonates.
SPECIMENCODE
...
Anchor | ||
---|---|---|
|
...
|
(version: 1,0,0 / 1,1,0 / 2,0,0)
#Specimencode=Code, Release, Version, Update[, Reference]
...
Example: #Specimencode=MN, 3, 1, 0, 300-1-Mons.
SPECIMENTEXT
Anchor | ||||
---|---|---|---|---|
|
(version: 1,0,0 / 1,1,0 / 2,0,0)
#Specimentext=Index, Text[, Information]
...
Example: #Specimentext=129, Sample fell apart during transportation, general comment.
...
SPECIMENVAR
Anchor | ||||
---|---|---|---|---|
|
(version: 1,0,0 / 1,1,0 / 2,0,0)
#Specimenvar=Index, Value, Unit, Quantity
...
Note. Specimenvar is very similar to Measurementvar as far as structure and use are concerned. The difference is that the information is specifically related to a sample with Specimenvar, while Measurementvar is concerned with quantities which are specifically related to measuring and measurement apparatus where appropriate.
STARTDATE
...
Anchor | ||
---|---|---|
|
...
|
(version: 1,0,0 / 1,1,0 / 2,0,0)
#Startdate=Yyyy, Mm, Dd
Yyyy | int | The year in which the test started. Y2k compliant. |
Mm | int | The month in which the test started. |
Dd | int | The day on which the test started. |
...
Note. Together with the start time, the start date is important for tests as a function of time.
STARTTIME
Anchor |
---|
...
|
...
|
(version: 1,0,0 / 1,1,0 / 2,0,0)
#Starttime=Hour, Min, Sec
...
Example: #Starttime=12, 35, 24.75.
STRUCTURETEXT
Anchor |
---|
...
|
...
|
(version: 1,0,0 / 1,1,0 / 2,0,0)
#Structuretext=Codeword, Parameter1[, Parameter2[, Parameter3[,,]]]
...
Example: #Structuretext=GEFID, Releasenumber, Versionnumber, Updatenumber.
STRUCTURETYPE
Anchor | ||||
---|---|---|---|---|
|
(version: 1,0,0 / 1,1,0 / 2,0,0)
#Structuretype=Codeword, Type1[, Type2[, Type3[,,]]]
...
Example: #Structuretype=GEFID, int2, int2, int2.
TESTID
Anchor |
---|
...
|
...
|
(version: 1,0,0 / 1,1,0 / 2,0,0)
#Testid=TestID
TestID | string | Text stating which test from a series of tests this file concerns. |
Example: #Testid=T13B.
...
TIMECOLUMN
TIMECOLUMN
Anchor | ||||
---|---|---|---|---|
|
(version: 1,0,0 / 1,1,0 / 2,0,0)
#Timecolumn=Column[, Timecode[, Unit]]
...
Table 8 Value of Code and Unit
Timecode | Unit |
1 | second |
2 | minute |
3 | hour |
4 | day |
5 | week |
XYID
...
Anchor | ||
---|---|---|
|
...
|
(version: 1,0,0 / 1,1,0 / 2,0,0)
#XYid=MapID, X, Y[, EpsX, EpsY]
...
The MapID code consists of the international dial code for a specific country, multiplied by 1000, followed by a number 000 .. 999.
ZID
Anchor |
---|
...
|
...
|
(version: 1,0,0 / 1,1,0 / 2,0,0)
#Zid=ReferenceID, Z[, EpsZ]
...