You are here: Other topics > Procedures > Geological database > Database Mapper
GEOVIA Surpac

Mapping a database

Surpac database tree

The structure of the Surpac database is similar to the structure of any other database, except that the tables are split into mandatory and optional tables. These folders represent a view of the database and Surpac 'knows' only about the tables and fields that are defined in the Surpac database. Every other object in the database you are mapping is ignored.

The mandatory tables required by Surpac are the collar and survey tables. Within the folders for these tables are a list of the mandatory fields that are required for the table and two subfolders. The subfolders are for Optional Fields and Indexes. Within the Optional Fields subfolder, you can map to fields of the collar and survey tables that are not mandatory.

Note: You must map any tables that have an asterisk (*) next to their name. Any fields that have an asterisk next to their name are mandatory fields that you must either map to a stored field or leave as a calculated field. Only positional fields, like x, y, z, x_from, y_from, z_from, or hole_path can be calculated fields (Surpac uses hole_path to determine which algorithm to use for calculating hole position: 'linear', 'curved', or 'vertical').

The optional tables allow you to map any other tables in the database that you want to use in Surpac. There are five subfolders under the optional tables folder. The translation subfolder allows you to map a translation table that translates numeric codes. The styles subfolder allows you to map to a table that contains stored drawing styles. The Interval, Point, and Discrete tables allow you to map to data tables in the database.

Indexes

For geological database functions to work correctly, the indexes in the Indexes subfolders of Collar and Survey must be mapped from the source database to the .ddb file. When the hole_id and depth fields are mapped, these indexes are also mapped. Surpac requires these indexes to display and work with the data at a reasonable speed, and to ensure that there is a unique hole_id field for each drillhole.

You can also map other indexes that you want to be able to use within Surpac.