Naming and Referencing Grids

The format of the standard grid file name is:

			
   <proj><gfi>.<mv>g

The project code is a name of up to four letters used to associate grids in a project. The grid file identifier, <gfi> is a one to four letter code, usually a horizon name, used to identify grids that are physically related to each other in 3D space. For example, in the modelling of a coal deposit, the grid file identifier normally corresponds to the name of a seam. The mapping variable name, <mv> is a two letter code indicating which variable (or value) is being modelled by the grid for the horizon.

See the Mapfiles information for a list of standard mapping variables.

Example file names

abch.srg abch.sfg abctopo.tpg

When referencing a grid, only the distinguishing components of that grid name need to be specified. The default project name and grid file identifier (horizon) are used if these portions are omitted from the grid name.

If a specific grid is to be referenced, and the default horizon does not point to that grid, then the grid may be referenced by specifying <gfi>.<mv>.

For example;

h.sr h.sf topo.tp

Note
If the project name does not point to the required grid, then the name must be specified in full.
It is still possible and acceptable in some situations to create grids where the grid file identifier is longer than four characters.
Don't use solely numeric horizon names, which will become the grid file identifier <gfi> (for example, 10, 20, 30 and 40) or begin them with a number (for example, 1U, 1L, 2, 3U, 3L). In such situations, Grid Calc interprets any grid that starts with a number as a grid at that particular RL level (that is, a flat grid at that elevation) and also, if any other text then follows the numeric, this will possibly create errors in Grid Calc.
Ensure your horizon and therefore, potentially your subsequent grid file identifier <gfi> do not share the same name or abbreviation as your project code, as it will be automatically 'removed' by Grid Calc when referencing grids. for example, abcabc.sfg - Grid Calc will 'remove' the project code 'abc' twice in this situation and as a result, the required grid will not be found by Grid Calc, even though it does exist.
Think ahead and consider your deposit's stratigraphy and complexity before deciding on the nomenclature system. For example, this situation has been seen where the two major seams in a deposit were called Upper (U) and Lower (L). These seams subsequently split and the child splits were called Upper-Upper (UU) and Upper-Lower (UL). This naming system continued right through the deposit which contained up the three splitting levels, resulting in seams called Upper-Upper-Upper-Upper (UUUU) and Upper-Upper-Upper-Lower (UUUL)! This obviously became very confusing when discussing the stratigraphy on-site and this system was also highly susceptible to typographical errors.
Think about the names of your horizons in conjunction with your project code. When grids are created, the resultant grid is named in the format: <proj><gfi>.<mv>g. Therefore, this combination of two groups of independent text (the project code and grid file identifier) appearing together can form certain undesirable or inappropriate words or strings of text.