Structuring Your Data

The structure of the data is very much dependent on the application for which Vulcan is intended. However, a general set of rules are outlined below to assist you in defining the required structure:

  1. Determine the most basic unit of data in the system above point locations. For example, digitised contour data would usually involve designating each contour string as the basic unit. This unit then becomes the object in the data structure.
  2. Layers are then defined as collections of related objects. A layer might contain all contour strings on one hand and all the subcrop seam limits on another. Alternatively, it is possible to structure the name of a layer and use wildcard characters ('*' and '%') to group layers.

    For example with surveying data one might decide to put each day's surveying into a separate layer, i.e.

    SV.931109   (Survey on 9Nov93) SV.931112   (Survey on 12Nov93) SV.931223   (Survey on 12Dec93)

    In this way several selection choices are available:

    SV*         Loads all Survey layers SV.93*      Loads all 1993 Survey layers SV.9311*    Loads all Nov. 1993 layers

    Another example for geological modelling might be for the seam 'MTA':

    MTA.GEOL    Geology, e.g washouts MTA.CROP    Outcrop limit line MTA.MASK    Masking polygon to show horizon extent
  3. A design database may then be defined as a collection of similar or related layers.

    Using the previous example, this may be a file containing all geological data such as contours, subcrops, washout zones etc., each in a separate layer. Alternatively, each file may correspond to a specific geographical area and contain either all geological data or all mine site buildings.

The following is an example of how files, layers and objects may be constructed at an active mine site. As mine sites will generally hold coordinate data concerning several fields of activity, the example assumes the following:

  1. There is geological data used for exploration and evaluation.
  2. There is cadastral data for lease boundaries, road and rail connections.
  3. There is data relating to mine site buildings and facilities.
  4. There is data relating to open pit design.

Example - Data Structure at Mine Site

Activity

Object

Layer

File

A

Usually a bounding polygon defining seam or ore body limits and contour lines.

Specific types of geological data.

A compound of all layers thus the file contains all geological data. There may be several of these files representing several time periods.

B

Each different road, rail link or property/boundary lease.

Specific types of survey data.

Division into files may depend on various legal requirements. For example, it may be decided to maintain a file for all disputed lease areas. These areas may be deleted or added from a more general file.

C

For buildings, each individual building could be considered an object. For facilities, the objects may be service bays, conveyor belts.

The basis of use of the buildings. For facilities the layer could group parts of the facility, for example workshop, ore crusher.

Site buildings could be maintained as one file, facilities where more detail is required may have a separate file for each facility.

D

Toes and crests for pit design.

Each pit design, blast block and road layout.

Geology, Survey, Mine design.

Related topics