Organisation of Databases

  • Database Naming
  • Data Sharing

Database Naming

Maptek supports database organisation facilities right from the outset. Various databases can be grouped together by an environment (for example, cold/coal) variable, which allows the use of common features such as legends and colour schemes, feature definitions etc. Each database can then be identified on a project (PROJ) code basis. These are the minimum prefix requirements for a database. The suffix (DSN) is generally user defined, although certain file types are set internally. Typically an optional database identifier is inserted after the project code: 

<PROJ><GEOLOGY>.DDH 
<PROJ><SURVEY>.PEG
Vulcan has internal secretaries that keep track of the various databases and make pick lists available. This means the user no longer has to remember the exact name or spelling of triangulations or databases!

Data Sharing

Vulcan supports file-sharing capabilities so that the geologist may access the survey database and display survey information without necessarily having the ability to alter the original survey data. Currently under Beta release is an option called "Files-layout" which allows the user to store different file types for example triangulations, in different directories. Of course, it is possible to access files across the network. In addition to this, the Unix and PC versions support binary compatible file types. This means that users on both platforms can access the same information without having to maintain multiple copies of the same databases and ensuring they are both current.

Vulcan also supports the use of logically named and formatted ASCII files. This facility is supported by the pull down menus for Vulcan formats. User definable format statements may also be specified for non-standard ASCII files.