Preparing Borehole Databases for Cross-Section Software

Knowledge Center

Preparing Borehole Databases for Cross-Section Software

Workflow diagram showing preparation of borehole databases for geological cross-section software.

Written by

GAEA Technologies

in

,
Share the knowledge

Introduction

Geological cross-section software has become an essential tool for engineers and geologists working in geotechnical investigations, hydrogeology, environmental consulting, mining exploration, and infrastructure planning. Modern software platforms allow professionals to transform borehole logs into digital cross-sections, fence diagrams, and three-dimensional subsurface models.

However, the accuracy of these visualizations depends entirely on the quality and structure of the borehole data used as input. Poorly organized borehole databases can lead to incorrect layer correlations, distorted cross-sections, and misleading geological interpretations.

Preparing borehole data correctly before importing it into cross-section software is therefore one of the most important steps in subsurface modeling. Engineers and geologists must ensure that borehole logs are structured consistently, lithology descriptions are standardized, and spatial coordinates are accurate.

A well-organized borehole database allows geological software to interpret stratigraphy correctly and produce reliable visualizations of subsurface conditions.

This article explains how borehole databases should be structured, the common data issues that affect cross-section software, and the best practices for preparing borehole datasets for geological modeling.

Why Borehole Database Structure Matters

Cross-section software relies on structured datasets to reconstruct subsurface geology. Unlike geologists, software programs cannot interpret ambiguous data or resolve inconsistencies in borehole logs.

Instead, software algorithms rely on clearly defined fields such as:

  • borehole coordinates
  • ground elevation
  • lithology intervals
  • layer identifiers

If these fields are inconsistent or incomplete, the software may misinterpret the data.

For example, if two boreholes describe the same geological material using slightly different terminology, the software may treat them as separate layers rather than correlating them.

Similarly, if depth intervals overlap or contain gaps, the resulting cross-sections may display unrealistic geological structures.

A properly structured borehole database ensures that geological software can correctly interpret the relationships between boreholes and geological layers.

Core Components of a Borehole Database

Most geological software platforms require borehole data to be organized into several key tables. While the exact format may vary between programs, the fundamental structure remains similar.

Borehole Collar Table

The collar table contains general information about each borehole location.

Typical fields include:

  • borehole ID
  • easting coordinate
  • northing coordinate
  • ground surface elevation
  • drilling date
  • project name

This information allows cross-section software to position boreholes accurately in space.

Even small coordinate errors can distort cross-section geometry, especially when boreholes are projected onto section lines.

Lithology Interval Table

The lithology interval table records the geological materials encountered in each borehole.

Typical fields include:

  • borehole ID
  • from depth
  • to depth
  • lithology description
  • soil classification

These intervals define the vertical sequence of geological layers.

Cross-section software uses this information to reconstruct stratigraphy between boreholes.

If the intervals are incorrect or inconsistent, the resulting cross-sections may contain errors.

Sample and Laboratory Data

Many boreholes include samples that are analyzed in laboratories to determine soil properties.

Laboratory datasets may include:

  • grain size distribution
  • moisture content
  • Atterberg limits
  • shear strength
  • permeability

While these datasets may not directly affect cross-section geometry, they provide valuable information for geotechnical analysis.

Standardizing Lithology Descriptions

One of the most common problems in borehole databases is inconsistent lithology descriptions.

During field logging, geologists often use detailed descriptions to characterize soil materials. For example, similar materials may be recorded as:

  • fine sand
  • silty sand
  • sand with silt
  • sandy silt

Although these descriptions may be accurate, they can create problems when importing data into cross-section software.

The software may treat each description as a separate geological unit.

To avoid this issue, many organizations standardize lithology descriptions into simplified categories such as:

  • clay
  • silt
  • sand
  • gravel
  • bedrock

Detailed descriptions can still be preserved in separate fields, but standardized categories improve correlation between boreholes.

Checking Depth Intervals

Depth intervals must be carefully reviewed before importing borehole data into cross-section software.

Several common errors can occur during data entry:

  • overlapping intervals
  • gaps between intervals
  • incorrect depth values

For example:

From DepthTo DepthLithology
0.02.0Clay
2.04.5Sand
4.36.0Gravel

In this example, the sand and gravel layers overlap between depths of 4.3 and 4.5 meters.

These errors can cause software to misinterpret geological boundaries.

Each lithology interval should begin exactly where the previous interval ends.

Ensuring continuous intervals improves the reliability of cross-section interpretation.

Converting Depth to Elevation

Some geological modeling software uses elevation values instead of depth measurements.

In these systems, lithology intervals must be converted from depth below ground surface to absolute elevation.

The conversion formula is:

Elevation = Ground Elevation − Depth

For example:

BoreholeGround ElevationDepthElevation
BH01102 m5 m97 m

Using elevation values allows software to position geological layers correctly relative to topography.

This is particularly important when constructing cross-sections across uneven terrain.

Managing Missing Geological Layers

Subsurface geology often includes layers that appear in some boreholes but not others.

This may occur due to:

  • pinch-outs
  • erosion
  • depositional variability

Cross-section software may struggle to interpret these missing layers.

For example, if one borehole contains three sand layers and another contains only two, the software may incorrectly connect the layers.

Proper database preparation can help manage these situations.

Maintaining consistent stratigraphic order and clearly identifying missing units improves correlation accuracy.

Borehole Naming Conventions

Consistent borehole naming is essential for managing borehole databases.

Small differences in borehole IDs can create major problems during data import.

For example:

  • BH01
  • BH-01
  • Borehole-01

These identifiers may refer to the same borehole but will be treated as different entries by software.

Establishing standardized naming conventions prevents these errors.

Quality Control Procedures

Before importing borehole data into cross-section software, it is important to perform quality control checks.

Recommended checks include:

  • verifying borehole coordinates
  • reviewing lithology descriptions
  • confirming interval continuity
  • checking ground elevations
  • identifying duplicate records

Automated scripts or spreadsheet formulas can help identify these issues quickly.

Quality control ensures that the database is reliable before it is used for geological modeling.

Integrating Borehole Databases with Geological Software

Once the database has been cleaned and standardized, it can be imported into geological modeling software.

These tools can then generate visualizations such as:

  • geological cross-sections
  • fence diagrams
  • stratigraphic models
  • volumetric calculations

The quality of these visualizations depends directly on the quality of the borehole database.

Well-structured datasets allow software to generate realistic representations of subsurface geology.

Automation and Data Management Systems

As datasets grow larger, many organizations are adopting automated data management systems.

These systems can perform tasks such as:

  • standardizing lithology descriptions
  • detecting depth interval errors
  • validating coordinates
  • generating cross-sections

Automation reduces the risk of human error and improves efficiency when working with large borehole datasets.

Best Practices for Preparing Borehole Databases

Several best practices can help ensure that borehole databases are ready for cross-section software.

First, standardize lithology descriptions using consistent categories.

Second, verify borehole coordinates and ground elevations.

Third, ensure that depth intervals are continuous and non-overlapping.

Fourth, maintain consistent borehole naming conventions.

Finally, perform quality control checks before importing data into modeling software.

Following these practices significantly improves the reliability of geological interpretations.

Conclusion

Preparing borehole databases for cross-section software is a critical step in subsurface modeling. Even the most advanced geological software cannot produce reliable models if the underlying data is inconsistent or poorly structured.

By organizing borehole logs into structured databases, standardizing lithology descriptions, verifying spatial coordinates, and performing quality control checks, engineers and geologists can ensure that cross-section software interprets subsurface data correctly.

Well-prepared borehole databases form the foundation of accurate geological cross-sections, fence diagrams, and three-dimensional subsurface models.

Investing time in proper data preparation ultimately leads to more reliable geological interpretations and better engineering decisions.

Learn more about our Solutions

1 / ?