Module Library Reference:File Modules:EFF_File

EVS Field File Formats and Examples

EVS Field file formats supplant the need for UCD, netCDF, Field (.fld), EVS_Geology by incorporating all of their functionality and more in a new file format with three mode options.

1)    .eff ASCII format, best if you want to be able to open the file in an editor or print it

2)    .efz GNU Zip compressed ASCII, same as .eff but in a zip archive

3)    .efb binary compressed format, the smallest & fastest format due to its binary form

Here are the tags available in an EVS field file, in the appropriate order. Note that no file will contain ALL these tags, as some are specific to the type of field (based on definition). The binary file format is undocumented and exclusively used by C Tech’s Save_EVS_Field module.

If the file is written compressed, the .efz file (and any split, extra data files) will all be compressed. The compression algorithm is compatible with the free gzip/gunzip programs or WinZip, so the user can uncompress a .efz file and get an .eff file at will. The .efb file is also compressed (hence its very small size), but uncompressing this file will not make it human-readable.

EVS Field Files

EVS Field Files consist of file tags that delineate the various sections of the file(s) and data (coordinates, nodal and/or cell data, and connectivity). The file tags are discussed below followed by portions of a few example files.

FILE TAGS:

The file tags for the ASCII file formats (shown in Bold Italics) are discussed below with a representative example. They are given in the appropriate order. If you need assistance creating software to write these file formats, please contact support@ctech.com.

 

 DATE_CREATED(optional) 7/16/2004 1:57:55 PM

The creation date of the file.

 

 EVS_FIELD_FILE_NOTES_START (optional)

 Insert your Field file notes here.

 EVS_FIELD_FILE_NOTES_END

This is the file description block. These notes are used to describe the contents of the Field file. The entire block is optional, however if you wish to use notes then both the starting and end tag are required.

 

DEFINITION Mesh+Node_Data

This is the type of field we are creating. Typically options are: 

1)    Mesh+Node_Data

2)    Mesh+Cell_Data

3)    Mesh+Node_Data+Cell_Data

4)    Mesh_Struct+Node_Data (Geology)

5)    Mesh_Unif+Node_Data (Uniform field)

 

NSPACE 3

nspace of the output field. Typically 3, but 2 in the case of geology or an image

 

NNODES 66355

Number of nodes. Not used for Mesh_Struct of Mesh_Unif

 

NDIM 2

Number of dimensions in a Mesh_Struct or Mesh_Unif

 

DIMS 41 41

The dimensions for a mesh_struct or uniform field

 

POINTS 11061.528999 12692.304504 -44.049999 11611.330994 13098.105469 11.500000

The lower left and upper right corner of a uniform field (Mesh_Unif only)

 

COORD_UNITS "ft"

Coordinate Units

 

NUM_NODE_DATA 7

Number of nodal data components

 

NUM_CELL_DATA 1

Number of cell data components

 

NCELL_SETS 5

Number of cell sets

 

NODES FILE "test_split.xyz" ROW 1 X 1 Y 2 Z 3

Nodes section is starting. If it says "NODES IN_FILE", the nodes follow (x/y/z) on the next nnodes rows, otherwise, the line will say FILE "filename" ROW 1 X 1 Y 2 Z 3, which is the file to get the coordinates, the row to start at (1 is first line of file), and the columns containing your X, Y, and Z values

 

NODE_DATA_DEF 0 "TOTHC" "log_ppm" MINMAX -3 4.592 FILE "test_split.nd" ROW 1 COLS 1

NODE_DATA_DEF specifies the definition of a nodal data component. The second word is the data component number, the third is the name, the 4th is the units, then it will either say IN_FILE (which means that it will start after a NODE_DATA_START tag) or the file information. Other options are:

1) MINMAX - two numbers follow which are the data minimum and maximum.  This behaves much like the set_min_max module.

2) If this is vector data, there will be a VECLEN 3 tag in there, and COLS will need to have 3 numbers following it (for each component of the vector)

3) NODE_DATA_START. All the node data components that are specified IN_FILE are listed in order after this tag.

 

CELL_SET_DEF 0 8120 Hex "Fill" MINMAX 1 14 FILE "test_split.conn" ROW 1

Definition of a cell set. 2nd word is cell set number, 3rd is number of cells, 4th is type, 5th is the name, then its either IN_FILE (which means they will be listed in order by cell set), or the FILE "filename" section and a row to begin reading from. Other options are:

1) MINMAX - two numbers follow which are the data minimum and maximum.  This behaves much like the cell_set_min_max module.

 

2) CELL_START. Start of all the cell set definitions that are specified IN_FILE.

 

CELL_DATA_DEF 0 "Indicator" "Discreet Unit" FILE "test_split.cd" ROW 1 COLS 1

Definition of cell data. Same options as NODE_DATA_DEF

 

CELL_DATA_START

Start of all cell data that is specified as IN_FILE

 

LAYER_NAMES "Top" "Fill" "Silt" "Clay" "Gravel" "Sand"

Allows you to specify the names associated with surfaces (layers)
 

MATERIAL_MAPPING "1|Silt" "2|Fill" "3|Clay" "4|Sand" "5|Gravel"

Allows you to specify the Material_ID and the associated material names.  Note that each number/name pair is in quotes, with the name separated from the number by the pipe "|" symbol.

 

END

Marks the end of the data section of the file. (Allows us to put a password on .eff files)

 

EVS Field File Examples:

Because EVS Field Files can contain so many different types of grids, it is beyond the scope of our help system to include every variant.

Krig_3D - EFF file representing a uniform field: The file below is an abbreviated example of writing the output of Krig_3D having kriged a uniform field (which can be volume rendered). Large sections of the data regions of this file are omitted to save space. This is represented by sections of the file with "*** omitted ***" replacing many lines of data.

DEFINITION Mesh_Unif+Node_Data

NSPACE 3

NDIM 3

DIMS 41 41 35

COORD_UNITS "ft"

NUM_NODE_DATA 7

POINTS 11281.910004 12211.149994 -29.900000 12515.890015 13259.449951 0.900000

NODE_DATA_DEF 0 "VOC" "log_ppm" IN_FILE

NODE_DATA_DEF 1 "Confidence-VOC" "linear_%" IN_FILE

NODE_DATA_DEF 2 "Uncertainty-VOC" "linear_Unc" IN_FILE

NODE_DATA_DEF 3 "Geo_Layer" "linear_" IN_FILE

NODE_DATA_DEF 4 "Elevation" "linear_ft" IN_FILE

NODE_DATA_DEF 5 "Layer Thickness" "linear_ft" IN_FILE

NODE_DATA_DEF 6 "Material_ID" "linear_" IN_FILE

NODE_DATA_START

-2.357487 34.455845 2.325005 0.000000 -29.900000 30.799999 0.000000

-3.000000 34.977974 0.000000 0.000000 -29.900000 30.799999 0.000000

-3.000000 35.603794 0.000000 0.000000 -29.900000 30.799999 0.000000

***** OMITTED *****

-3.000000 30.056839 0.000000 0.000000 0.900000 30.799999 0.000000

-3.000000 29.858747 0.000000 0.000000 0.900000 30.799999 0.000000

-3.000000 29.673925 0.000000 0.000000 0.900000 30.799999 0.000000

END

 

Krig_3D - EFF Split file representing a uniform field: The file below is a complete example of writing the output of Krig_3D having kriged a uniform field (which can be volume rendered). Note that the .EFF file is quite small, but references the data in a separate file named krig_3d_uniform_split.nd.

DEFINITION Mesh_Unif+Node_Data

NSPACE 3

NDIM 3

DIMS 41 41 35

COORD_UNITS "ft"

NUM_NODE_DATA 7

POINTS 11281.910004 12211.149994 -29.900000 12515.890015 13259.449951 0.900000

NODE_DATA_DEF 0 "VOC" "log_ppm" FILE "krig_3d_uniform_split.nd" ROW 1 COLS 1

NODE_DATA_DEF 1 "Confidence-VOC" "linear_%" FILE "krig_3d_uniform_split.nd" ROW 1 COLS 2

NODE_DATA_DEF 2 "Uncertainty-VOC" "linear_Unc" FILE "krig_3d_uniform_split.nd" ROW 1 COLS 3

NODE_DATA_DEF 3 "Geo_Layer" "linear_" FILE "krig_3d_uniform_split.nd" ROW 1 COLS 4

NODE_DATA_DEF 4 "Elevation" "linear_ft" FILE "krig_3d_uniform_split.nd" ROW 1 COLS 5

NODE_DATA_DEF 5 "Layer Thickness" "linear_ft" FILE "krig_3d_uniform_split.nd" ROW 1 COLS 6

NODE_DATA_DEF 6 "Material_ID" "linear_" FILE "krig_3d_uniform_split.nd" ROW 1 COLS 7

END

 

Large sections of the data regions of the data file krig_3d_uniform_split.nd are omitted below to save space. This is represented by sections of the file with "*** omitted ***" replacing many lines of data.

 

-2.357487 34.455845 2.325005 0.000000 -29.900000 30.799999 0.000000

-3.000000 34.977974 0.000000 0.000000 -29.900000 30.799999 0.000000

-3.000000 35.603794 0.000000 0.000000 -29.900000 30.799999 0.000000

***** OMITTED *****

-3.000000 30.056839 0.000000 0.000000 0.900000 30.799999 0.000000

-3.000000 29.858747 0.000000 0.000000 0.900000 30.799999 0.000000

-3.000000 29.673925 0.000000 0.000000 0.900000 30.799999 0.000000

 

Krig_3D_Geology & Krig_3D - EFF file representing multiple geologic layers with analyte (e.g. chemistry): The file below is an abbreviated example of writing the output of Krig_3D having kriged analyte (e.g. chemistry) data with geology input. Large sections of the data regions of this file are omitted to save space. This is represented by sections of the file with "*** omitted ***" replacing many lines of data.

NSPACE 3

NNODES 66355

COORD_UNITS "ft"

NUM_NODE_DATA 7

NCELL_SETS 5

NODES IN_FILE

11153.998856 12722.725708 2.970446

11161.871033 12715.198792 2.783408

11169.743210 12707.671875 2.594242

***** OMITTED *****

11250.848221 12865.266907 -42.575920

11248.750000 12870.909973 -42.000000

11243.389938 12870.020935 -42.474934

NODE_DATA_DEF 0 "TOTHC" "log_mg/kg" IN_FILE

NODE_DATA_DEF 1 "Confidence-TOTHC" "linear_%" IN_FILE

NODE_DATA_DEF 2 "Uncertainty-TOTHC" "linear_Unc" IN_FILE

NODE_DATA_DEF 3 "Geo_Layer" "Linear_" IN_FILE

NODE_DATA_DEF 4 "Elevation" "Linear_ft" IN_FILE

NODE_DATA_DEF 5 "Layer Thickness" "Linear_ft" IN_FILE

NODE_DATA_DEF 6 "Material_ID" "Linear_" IN_FILE

NODE_DATA_START

-0.777059 27.239126 15.861248 0.000000 2.970446 8.270601 2.000000

-0.661227 27.349216 16.503609 0.000000 2.783408 8.270658 2.000000

-0.288564 27.512394 18.822187 0.000000 2.594242 8.261375 2.000000

***** OMITTED *****

2.886921 69.551514 1.128253 4.000000 -42.575920 13.628321 4.000000

3.113943 99.999977 0.000000 4.000000 -42.000000 13.654032 4.000000

3.070153 72.869553 0.841437 4.000000 -42.474934 13.646055 4.000000

CELL_SET_DEF 0 8120 Hex "Fill" IN_FILE

CELL_SET_DEF 1 14680 Hex "Silt" IN_FILE

CELL_SET_DEF 2 6502 Hex "Clay" IN_FILE

CELL_SET_DEF 3 11284 Hex "Gravel" IN_FILE

CELL_SET_DEF 4 14412 Hex "Sand" IN_FILE

CELL_START

0 1 42 41 1681 1682 1723 1722

1 2 43 42 1682 1683 1724 1723

2 3 44 43 1683 1684 1725 1724

***** OMITTED *****

54462 54503 66349 66348 56143 56184 66353 66352

54503 54502 66350 66349 56184 56183 66354 66353

54502 54461 66347 66350 56183 56142 66351 66354

END

 

Post_samples - EFF file representing spheres: The file below is a complete example of writing the output of post_samples’ blue-black field port having read the file initial_soil_investigation_subsite.apdv. This data file has 99 samples with data that was log processed. If this file is read by Load_EVS_Field. It creates all 99 spheres colored and sized as they were in Post_samples. The tubes and any labeling are not included in the field port from which this file was created.

DEFINITION Mesh+Node_Data

NSPACE 3

NNODES 99

COORD_UNITS "units"

NUM_NODE_DATA 2

NCELL_SETS 1

NODES IN_FILE

11566.340027 12850.590027 -10.000000

11566.340027 12850.590027 -70.000000

11566.340027 12850.590027 -160.000000

11586.340027 13050.589966 -10.000000

11586.340027 13050.589966 -70.000000

11586.340027 13050.589966 -160.000000

11381.700012 12747.500000 -15.000000

11381.700012 12747.500000 -25.000000

11414.399994 12781.099976 -15.000000

11414.399994 12781.099976 -25.000000

11338.000000 12830.799988 -10.000000

11338.000000 12830.799988 -65.000000

11338.000000 12830.799988 -115.000000

11338.000000 12830.799988 -165.000000

11410.290009 12724.690002 -5.000000

11410.290009 12724.690002 -35.000000

11410.290009 12724.690002 -45.000000

11410.290009 12724.690002 -125.000000

11410.290009 12724.690002 -175.000000

11427.000000 12780.900024 -10.000000

11427.000000 12780.900024 -30.000000

11427.000000 12780.900024 -80.000000

11416.899994 12819.450012 -10.000000

11416.899994 12819.450012 -30.000000

11416.899994 12819.450012 -70.000000

11416.899994 12819.450012 -95.000000

11416.899994 12819.450012 -105.000000

11416.899994 12819.450012 -120.000000

11416.899994 12819.450012 -140.000000

11401.730011 12897.770020 -10.000000

11401.730011 12897.770020 -30.000000

11401.730011 12897.770020 -80.000000

11401.730011 12897.770020 -110.000000

11401.730011 12897.770020 -145.000000

11401.730011 12897.770020 -180.000000

11259.670013 12819.289978 -10.000000

11259.670013 12819.289978 -40.000000

11259.670013 12819.289978 -70.000000

11259.670013 12819.289978 -95.000000

11259.670013 12819.289978 -140.000000

11340.489990 12892.609985 -30.000000

11340.489990 12892.609985 -55.000000

11340.489990 12892.609985 -80.000000

11340.489990 12892.609985 -110.000000

11340.489990 12892.609985 -130.000000

11340.489990 12892.609985 -165.000000

11248.750000 12870.909973 -10.000000

11248.750000 12870.909973 -35.000000

11248.750000 12870.909973 -45.000000

11248.750000 12870.909973 -85.000000

11248.750000 12870.909973 -110.000000

11248.750000 12870.909973 -160.000000

11248.750000 12870.909973 -210.000000

11086.519997 12830.669983 -15.000000

11086.519997 12830.669983 -30.000000

11086.519997 12830.669983 -80.000000

11086.519997 12830.669983 -130.000000

11211.869995 12710.750000 -30.000000

11211.869995 12710.750000 -80.000000

11211.869995 12710.750000 -135.000000

11199.039993 12810.159973 -20.000000

11199.039993 12810.159973 -40.000000

11199.039993 12810.159973 -85.000000

11199.039993 12810.159973 -150.000000

11298.000000 12808.630005 -60.000000

11496.339996 12753.590027 -10.000000

11496.339996 12753.590027 -30.000000

11496.339996 12753.590027 -80.000000

11496.339996 12753.590027 -110.000000

11496.339996 12753.590027 -150.000000

11309.029999 12948.989990 -10.000000

11309.029999 12948.989990 -35.000000

11309.029999 12948.989990 -95.000000

11309.029999 12948.989990 -125.000000

11309.029999 12948.989990 -130.000000

11209.350006 12993.940002 -5.000000

11209.350006 12993.940002 -35.000000

11209.350006 12993.940002 -60.000000

11209.350006 12993.940002 -95.000000

11209.350006 12993.940002 -125.000000

11301.970001 13079.660034 -20.000000

11301.970001 13079.660034 -30.000000

11301.970001 13079.660034 -85.000000

11301.970001 13079.660034 -125.000000

11286.769989 13026.699951 -30.000000

11286.769989 13026.699951 -45.000000

11286.769989 13026.699951 -75.000000

11286.769989 13026.699951 -120.000000

11393.470001 12948.900024 -20.000000

11393.470001 12948.900024 -45.000000

11393.470001 12948.900024 -95.000000

11393.470001 12948.900024 -110.000000

11393.470001 12948.900024 -130.000000

11393.470001 12948.900024 -170.000000

11251.300003 12929.270020 -10.000000

11251.300003 12929.270020 -30.000000

11251.300003 12929.270020 -80.000000

11251.300003 12929.270020 -120.000000

11251.300003 12929.270020 -145.000000

NODE_DATA_DEF 0 "TOTHC" "log_mg/kg" IN_FILE

NODE_DATA_DEF 1 "" "" ID 668 IN_FILE

NODE_DATA_START

-3.000000 4.998203

-3.000000 4.998203

-3.000000 4.998203

-3.000000 4.998203

-3.000000 4.998203

-3.000000 4.998203

-3.000000 4.998203

-3.000000 4.998203

-3.000000 4.998203

-3.000000 4.998203

1.322219 4.998203

2.806180 4.998203

1.602060 4.998203

-3.000000 4.998203

-3.000000 4.998203

-3.000000 4.998203

-3.000000 4.998203

-3.000000 4.998203

-3.000000 4.998203

1.845098 4.998203

2.278754 4.998203

-3.000000 4.998203

1.296665 4.998203

-3.000000 4.998203

1.278754 4.998203

3.716003 4.998203

1.623249 4.998203

1.505150 4.998203

-3.000000 4.998203

1.707570 4.998203

-3.000000 4.998203

3.770852 4.998203

3.869232 4.998203

1.113943 4.998203

-3.000000 4.998203

2.025306 4.998203

3.434569 4.998203

3.594039 4.998203

2.454845 4.998203

-3.000000 4.998203

2.740363 4.998203

2.079181 4.998203

3.806180 4.998203

4.908485 4.998203

2.176091 4.998203

-3.000000 4.998203

3.792392 4.998203

3.362897 4.998203

4.255272 4.998203

3.699387 4.998203

3.518514 4.998203

3.301030 4.998203

3.113943 4.998203

-3.000000 4.998203

-3.000000 4.998203

-3.000000 4.998203

-3.000000 4.998203

1.361728 4.998203

-3.000000 4.998203

-3.000000 4.998203

2.000000 4.998203

1.643453 4.998203

1.732394 4.998203

1.643453 4.998203

3.556303 4.998203

-0.522879 4.998203

-3.000000 4.998203

-3.000000 4.998203

-3.000000 4.998203

-3.000000 4.998203

3.079181 4.998203

-3.000000 4.998203

2.633468 4.998203

1.505150 4.998203

-3.000000 4.998203

-3.000000 4.998203

-0.920819 4.998203

-3.000000 4.998203

-3.000000 4.998203

-3.000000 4.998203

-0.886057 4.998203

-3.000000 4.998203

-3.000000 4.998203

-3.000000 4.998203

-3.000000 4.998203

-3.000000 4.998203

-0.096910 4.998203

-3.000000 4.998203

4.000000 4.998203

2.000000 4.998203

1.602060 4.998203

1.000000 4.998203

-0.301030 4.998203

-3.000000 4.998203

1.785330 4.998203

-3.000000 4.998203

0.431364 4.998203

4.518514 4.998203

-3.000000 4.998203

CELL_SET_DEF 0 99 Point "" IN_FILE

CELL_START

0

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

61

62

63

64

65

66

67

68

69

70

71

72

73

74

75

76

77

78

79

80

81

82

83

84

85

86

87

88

89

90

91

92

93

94

95

96

97

98

END

© 1994-2015 ctech.com