Overview of an Insight Project

An Insight project, fundamentally, is the collection of all data (surveys, volumes, horizons, wells, faults, polygons, etc) that the team may wish to view and interpret in a single Insight instance.

Each invocation of Insight operates on a single project, so if you want to work with two objects at the same time, they must, by definition, be in the same project.

Insight projects are independent and do not share information. If one project is having problems, it is isolated from other Insight projects.

Directory Structure

Directory Structure

As Insight projects are independent, each Insight project is stored in its own directory. Therefore projects can be upgraded independently of one another.

Within the project directory, the structure has been considerably simplified. A standard project directory now contains:

  • A text file identifying the directory as an Insight project.
  • Contains information about the project CRS.
  • Provides default paths for input/output.
  • Includes location of the SQLite database.
  • Includes paths to externally referenced files.
  • The database file itself, which contains most of the smaller project data. The database may grow to be a few gigabytes for extremely large projects.
  • SQLite database.
  • The schema is not publicly available.
  • This directory is the default location for volume data.
  • Stored as .dugio.
  • High performance tile+brick format.
  • Very unlikely to change after initial import.
  • Time, phase, amplitude adjustments and metadata may vary.
  • This directory contains all of the project’s horizons (IL/CL or X/Y), each of which is itself a miniature database.
  • Stored as .dughzn (individual SQLite databases).
  • Dependencies exist between horizon databases and the main project database. .dughzn files cannot be directly moved between projects. Use Insight’s import and export features to achieve this.
  • Horizons have efficient storage and, unless they cover a very large area or include many properties, should be less than 200 Mb in size. 
  • By default, Insight tracks revisions to horizons. Horizons can get large and slow if the full history is maintained. However, clearing history can be time consuming and will block other users from accessing the horizon until complete. The performance benefit is usually worthwhile.
  • The directory for rock physics trends and probability files produced by DUG Rock and DUG Distill, prior to importing into Insight.
  • This directory stores all the imported culture data in Insight format (.dughrz)
  • The default directory into which screenshots are saved.
  • This directory contains results from wavelet extractions.
  • This directory contains results from Bayesian wavelet extractions (available on Linux platform only) and is the default location for exported wavelets or synthetic traces.
  • This directory houses all of the episodes in the Imaging tab, which contain any RMO and velocity picks that were created within the episode.


In addition, projects upgraded from previous versions of Insight will contain an "archive" directory, into which all of the flat files previously associated with the Insight project are moved.

It is important to note that once these files are imported into the Insight 4 project database, Insight will no longer reference the data in the archive directory and does not monitor it for changes.

Coordinate Reference System

A given Insight project must contain data referenced to a single cartesian (rectangular) coordinate reference system (CRS). Although you are not required to do so, providing the details of exactly which CRS is being used will enable Insight to perform conversion between coordinate systems when importing data.


An Insight session merely contains references to which project data is in the current working set, along with the state of the application when it was saved (the sizes and locations of open windows, display settings, line colours, etc).

Unlike in previous versions of Insight, sessions contain no actual data. Polygons, faults, arblines and other objects that were previously stored in the session are now first-class project objects, stored in the database and shared between sessions.

Multiple users can access the same project in their own session, which are now stored inside the project database.

Operating Systems

All Insight project data is completely independent of the operating system on which it was created, and can be used by any version of Insight for Windows, Linux, or Mac OS X simultaneously. No special consideration is required when moving users or data between operating systems.