GMS:Data Set Files

From XMS Wiki - http://wikis.aquaveo.com/xms/

ASCII Data Set Files

Data sets can be stored to either ASCII or binary files. The default format is binary. Data sets can be saved in ASCII format by right clicking on the data set in the Project Explorer and selecting the Export command from the pop up menu. For both file formats, multiple data sets can be stored in a single file and both scalar and vector data sets can be saved to the same file. The file format is identical for 2D and 3D data sets.

For scalar data set files, one value is listed per vertex, cell, node, or scatter point. The points are listed sequentially in ascending order according to the ids of the nodes, points, vertices, or cells. For vector data set files, one set of XYZ vector components is listed per vertex, cell, node, or scatter point. If necessary, a set of status flags can be included in the file. If the status flag is false (0), the corresponding item (node, cell, etc.) is inactive. If status flags are not included in the file, it is assumed that all items are active.

The ASCII Data Set file format is as follows:

_{DATASET // File type identifier}

OBJTYPE type // Type of object data set is associated with

REFTIME reftime // A value corresponding to beginning date/time of dataset

BEGSCL // Beginning of scalar data set

OBJID id // Object id

ND numdata // Number of data values

NC numcells // Number of cells or elements

NAME "name" // Data set name

ACTTS time // Marks the active time step

MAPTS time // Marks the time step which is mapped as elevations

TS istat time // Time step of the following data

stat1 // Status flags

stat2

.

.

statnumcells

val1 // Scalar data values

val2

.

.

valnumdata

// Repeat TS card for each time step

ENDDS // End of data set

BEGVEC // Beginning of vector dataset

VECTYPE type // Vector at node/gridnode or element/cell

OBJID id // Object id

ND numdata // Number of data values

NC numcells // Number of cells or elements

NAME "name" // Data set name

TS istat time // Time step of the following data

stat1 // Status flags

stat2

.

.

statnumcells

vx1 vy1 vz1

vx2 vy2 vz2

.

.

vnumdata vnumdata vnumdata

// Repeat TS card for each time step

ENDDS // End of data set

// Repeat BEGSCL and BEGVEC sequences for each data set

Sample ASCII Data Set File:

_DATASET

OBJTYPE grid2d

REFTIME 945.348729

BEGSCL

ACTTS 1.00000000e+00

ND 8

NC 8

NAME "trichloroethylene"

TS 1 1.00000000e+00

0

0

0

1

1

1

1

0

0.00000000e+00

0.00000000e+00

0.00000000e+00

3.24000000e+00

4.39000000e+00

2.96000000e+00

7.48000000e+00

0.00000000e+00

ENDDS

BEGVEC

VECTYPE 0

ND 8

NC 8

NAME "velocity"

TS 1 5.00000000e+00

0

0

0

1

1

1

1

0

1.60000000e+01 1.60000000e+01 3.20000000e+01

6.40000000e+01 6.40000000e+01 1.28000000e+02

1.44000000e+02 1.44000000e+02 2.88000000e+02

1.96000000e+02 1.96000000e+02 3.92000000e+02

2.25000000e+02 2.25000000e+02 4.50000000e+02

9.21600000e+03 9.21600000e+03 1.84320000e+04

9.60400000e+03 9.60400000e+03 1.92080000e+04

9.80100000e+03 9.80100000e+03 1.96020000e+04

ENDDS

If variograms have been defined for a data set or time step of a data set within GMS, the variograms are saved in the data set file. The variogram cards are not documented.

The card types used in the scalar data set file format are as follows:

Binary Data Set Files

Data sets saved with a GMS project are saved in the binary format. The binary format is patterned after the ASCII format in that the data are grouped into "cards". However, the cards are identified by a number rather than a card title. The card ids are four byte integers. The binary format is as follows:

 1 TINs
 2 Boreholes
 3 2D meshes
 4 2D grids
 5 2D scatter points
 6 3D meshes
 7 3D grids
 8 3D scatter points

The cards in the binary data set file are as follows:

Using Vector and Scalar Data with Grids

For meshes, TINs, and scatter point sets, the order that the values are listed in the file is simply the sequential order of the node, TIN, or scatter point ids. However, vector and scalar data can also be associated with the nodes or cells of a 2D or 3D grid. T For 2D grids, data values are ordered using a row-column (I-J) priority. For 3D grids, data values are ordered using a layer-row-column (K-I-J) priority.

The following C source code examples illustrate how a 2D or 3D array of scalar values corresponding to the nodes of a grid would be written to the main portion of an ASCII scalar file.

2D Grid Example:

_{for(i=0; i<nrow; i++){}

for(j=0; j<ncol; j++){

fprintf(fp, "%f\n", scalar[i][j]);

}

}

3D Grid Example:

_{for(k=0; k<nlay; k++){}

for(i=0; i<nrow; i++){

for(j=0; j<ncol; j++){

fprintf(fp, "%f\n", scalar[k][i][j]);

}

}

}

Related Links