Step-by-Step Tutorial: Creating Custom Reports in gINT

gINT is a robust relational database application used by geotechnical and geoenvironmental engineers to store, manage, and report subsurface data. Developed by Bentley Systems, it moves beyond simple drafting tools by serving as a single source of truth for borehole logs, lab testing, in-situ tests, and 2D/3D visualization.

Advanced borehole data management requires mastering gINT’s database structure, automation capabilities, and integration extensions. 🗄️ 1. Master the Core gINT File System Architecture

Advanced management starts with understanding how gINT splits data, formatting, and structures into a discrete file set:

Data Templates (.gdt): Define the structural blueprint (tables and fields) of your database.

Project Files (.gpj): Store the actual, project-specific subsurface data (borehole depths, coordinates, lithology).

Library Files (.glb): Contain global configuration data like report templates, symbols, drop-down lookup lists, and calculated expressions.

Pro-Tip: Always maintain a standardized company library (.glb) separate from project data to ensure consistent report formatting across different project teams. ⚙️ 2. Establish Data Integrity with Database Validation

Advanced users leverage gINT’s relational structure to enforce data compliance and eliminate transcription errors:

Required Fields & Defaults: Configure critical fields (such as Hole ID, Coordinate System, or Total Depth) as mandatory to prevent incomplete entries.

Lookup Tables: Restrict data entry for soil classifications or drilling methods to strict dropdown pick-lists. This standardizes lithology descriptions across multiple field loggers.

Component Description Models: Transition from paragraph-format entries to component-based systems. This breaks soil descriptors down into verified, standardized data points (e.g., primary component, secondary component, consistency). 🔄 3. Automate Data Entry and Interoperability

Manual data entry can create major human errors. Advanced gINT users utilize automated import and export workflows: gINT Logs – Datgel