Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

_________________________________________________________________________________________________________________________________________

ANALYSISCODE
Anchor
Analysiscode
Analysiscode

(version: 1,0,0 / 1,1,0 / 2,0,0)

...

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
Analysistext
Analysistext

(version: 1,0,0 / 1,1,0 / 2,0,0)

...

Example: #Analysistext=129, Cohesion calculated in accordance with NEN, comments.

 

ANALYSISVAR
Anchor
Analysisvar
Analysisvar

(version: 1,0,0 / 1,1,0 / 2,0,0)

...

Example: #Analysisvar=129, 1.33,-,over-relax factor for creep.

 

CHILD
Anchor
Child
Child

(version:  1,1,0 / 2,0,0)

...

  • 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
Column
Column

(version: 1,0,0 / 1,1,0 / 2,0,0)

...

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
Anchor
Columninfo
Columninfo

(version: 1,0,0 / 1,1,0 / 2,0,0)

...

Example: #Columninfo=3, kPa, deviator pressure, 1001.

 

COLUMNMINMAX
Anchor
Columnminmax
Columnminmax

(version: 1,0,0 / 1,1,0 / 2,0,0)

...

Example: #Columnminmax=5, 0.17, 5.68.

 

COLUMNSEPARATOR
Anchor
Columnseparator
Columnseparator

(version: 1,0,0 / 1,1,0 / 2,0,0)

...

Remark: the characters \#=+-.,DEGdeg0123456789 are not allowed as columnseparator. Furthermore Columnseparator and Recordseparator must differ.

 

COLUMNTEXT
Anchor
Columntext
Columntext

(version: 1,0,0 / 1,1,0 / 2,0,0)

...

 

Example: #Columntext=1.

 

COLUMNVOID
Anchor
Columnvoid
Columnvoid

(version: 1,0,0 / 1,1,0 / 2,0,0)

...

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
Comment
Comment

(version: 1,0,0 / 1,1,0 / 2,0,0)

...

Example: #Comment=Repeat of the test of 1995-06-25.

 

COMPANYID
Anchor
Companyid
Companyid

(version: 1,0,0 / 1,1,0 / 2,0,0)

...

Example: #Companyid=GEODELFT, 8000.97.476.B.01, 31.

 

...

DATAFORMATo
Anchor
Dataformat
Dataformat

(version: 1,0,0 / 1,1,0 / 2,0,0)

...

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
Eoh
Eoh

(version: 1,0,0 / 1,1,0 / 2,0,0)

...

Example: #Equipment=TS200.

 

FILEDATE
Anchor
Filedate
Filedate

(version: 1,0,0 / 1,1,0 / 2,0,0)

...

Example: #Filedate=1995,02,20.

 

FILEOWNER
Anchor
Fileowner
Fileowner

(version: 1,0,0 / 1,1,0 / 2,0,0)

...

Example: #Fileowner=Lambert Smidt.

 

...

 

FILINGCODE
Anchor
Filingcode
Filingcode

(version: 1,0,0 / 1,1,0 / 2,0,0)

...

Example: #Filingcode=B17, 3, 0, 1, NEN888888.

 

FILINGTEXT
Anchor
Filingtext
Filingtext

(version: 1,0,0 / 1,1,0 / 2,0,0)

...

Example: #Filingtext=129, Archiving in Oracle table PROJECT, tablename.

 

FILINGVAR
Anchor
Filingvar
Filingvar

(version: 1,0,0 / 1,1,0 / 2,0,0)

...

FIRSTSCAN

Anchor
Firstscan
Firstscan

 

(version: 1,0,0 / 1,1,0)

#Firstscan=Rownumber

...

 

Example: #Firstscan=13.

 

GEFID
Anchor
Gefid
Gefid

(version: 1,0,0 / 1,1,0 / 2,0,0)

...

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
Language
Language

(version: 1,0,0 / 1,1,0 / 2,0,0)

...

Note. The default value is 2147483648 (=231). (Nov 2000 I) The scans following the scan number in lastscan, are not processed.

 

MEASUREMENTCODE
Anchor
Measurementcode
Measurementcode

(version: 1,0,0 / 1,1,0 / 2,0,0)

...

Example: #Measurementcode=Cu, 3, 1, 0, 300-1-CU.

 

MEASUREMENTTEXT
Anchor
Measurementtext
Measurementtext

(version: 1,0,0 / 1,1,0 / 2,0,0)

...

Example: #Measurementtext=129, Temperature measured in accordance with NEN, temp. measurement.

 

MEASUREMENTVAR
Anchor
Measurementvar
Measurementvar

(version: 1,0,0 / 1,1,0 / 2,0,0)

...

Note. Measurementvar is used to store one-time measurements which form part of a test, such as temperature outside.

 

OBJECTID
Anchor
Objectid
Objectid

(version: 1,0,0 / 1,1,0 / 2,0,0)

...

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
Anchor
Parent
Parent

(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
Procedurecode
Procedurecode

(version: 1,0,0 / 1,1,0 / 2,0,0)

...

Example: #Procedurecode=GEF-CPT-Report, 1,0,0.

 

PROJECTID
Anchor
Projectid
Projectid

(version: 1,0,0 / 1,1,0 / 2,0,0)

...

Example: #Projectid=CO, 342770, 624.

 

PROJECTNAME
Anchor
Projectname
Projectname

(version: 1,0,0 / 1,1,0 / 2,0,0)

...

(Nov 2000 I) Remark: the characters \#=+-.,DEGdeg0123456789 are not allowed as columnseparator. Furthermore Columnseparator and Recordseparator must differ.

 

REPORTCODE
Anchor
Reportcode
Reportcode

(version: 1,0,0 / 1,1,0 / 2,0,0)

...

Example: #Reportcode=Standard, 3, 1, 0, 300-1-SDS.

 

 

...

REPORTDATAFORMAT
Anchor
Reportdataformat
Reportdataformat

(version: 1,0,0 / 1,1,0 / 2,0,0)

...

Example: #Reportdataformat=F7.3 F7.3 E11.4 I6.

 

 

REPORTTEXT
Anchor
Reporttext
Reporttext

(version: 1,0,0 / 1,1,0 / 2,0,0)

...

Example: #Reporttext=129, Section 5 is confidential, general comment.

 

 

REPORTVAR
Anchor
Reportvar
Reportvar

(version: 1,0,0 / 1,1,0 / 2,0,0)

...

RowslongA number between 1 and 2147483647. This gives the number of rows which are in the data block.

 

Example: #Row=1495.

 

SCANFREQ
Anchor
Scanfreq
Scanfreq

(version: 1,0,0 / 1,1,0 / 2,0,0)

...

Note. The scan frequency is expressed in Hz (s-1).

 

SCANTIME
Anchor
Scantime
Scantime

(version: 1,0,0 / 1,1,0 / 2,0,0)

...

Example: #Setupvar=250, 45.89, g, Mass of removed carbonates.

 

SPECIMENCODE
Anchor
Specimencode
Specimencode

(version: 1,0,0 / 1,1,0 / 2,0,0)

...

Example: #Specimencode=MN, 3, 1, 0, 300-1-Mons.

 

SPECIMENTEXT
Anchor
Specimentext
Specimentext

(version: 1,0,0 / 1,1,0 / 2,0,0)

...

Example: #Specimentext=129, Sample fell apart during transportation, general comment.

 

SPECIMENVAR
Anchor
Specimenvar
Specimenvar

(version: 1,0,0 / 1,1,0 / 2,0,0)

...

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
Startdate
Startdate

(version: 1,0,0 / 1,1,0 / 2,0,0)

...

Note. Together with the start time, the start date is important for tests as a function of time.

 

STARTTIME
Anchor
Starttime
Starttime

(version: 1,0,0 / 1,1,0 / 2,0,0)

...

Example: #Starttime=12, 35, 24.75.

 

STRUCTURETEXT
Anchor
Structuretext
Structuretext

(version: 1,0,0 / 1,1,0 / 2,0,0)

...

Example: #Structuretext=GEFID, Releasenumber, Versionnumber, Updatenumber.

 

STRUCTURETYPE
Anchor
Structuretype
Structuretype

(version: 1,0,0 / 1,1,0 / 2,0,0)

...

Example: #Structuretype=GEFID, int2, int2, int2.

 

TESTID
Anchor
Testid
Testid

(version: 1,0,0 / 1,1,0 / 2,0,0)

...

TestIDstringText stating which test from a series of tests this file concerns.

 

Example: #Testid=T13B.

 

TIMECOLUMN
Anchor
Timecolumn
Timecolumn

(version: 1,0,0 / 1,1,0 / 2,0,0)

...

Timecode

Unit

1

second

2

minute

3

hour

4

day

5

week

 

XYID
Anchor
Xyid
Xyid

(version: 1,0,0 / 1,1,0 / 2,0,0)

...

The MapID code consists of the international dial code for a specific country, multiplied by 1000, followed by a number 000 .. 999. 

 

ZID
Anchor
Zid
Zid

(version: 1,0,0 / 1,1,0 / 2,0,0)

...