Category: Geotechnical Data Management
Engineering projects generate large volumes of subsurface data including borehole logs, laboratory testing results, and groundwater monitoring records. Managing these datasets efficiently requires structured engineering databases and standardized workflows.
This section of the GAEA Knowledge Center explores best practices for organizing and managing geotechnical investigation data.
Start Here:
Posts
-
Standard vs Modified Proctor Test: Differences and Compaction Curve Examples
Standard and modified Proctor tests establish laboratory relationships between water content and dry density at specified compactive efforts. Their results are often used as reference values for earthwork control. The important difference is the prescribed test effort and procedure, not simply whether one test produces a larger density number. The project specification determines which reference…
-
Geotechnical Data Migration Readiness Checklist: What to Prepare Before You Start
A geotechnical data migration begins well before the first import. The most useful early work is establishing what your organization owns, what it needs to preserve and how people will use the information afterward. Without that preparation, a straightforward transfer can become a succession of questions about missing files, unfamiliar codes and report differences. This…
-
Sieve Analysis Calculations: Percent Passing and Grain-Size Distribution
Sieve analysis calculations convert the masses retained on a series of sieves into a particle-size distribution. The basic arithmetic is simple: calculate cumulative retained mass, express it as a percentage of the appropriate total dry mass, and subtract that percentage from 100 to obtain percent passing. Reliable results still depend on specimen preparation, the applicable…
-
How to Run a Geotechnical Data Migration Pilot: Samples, Checks and Acceptance Criteria
A geotechnical data migration pilot is a controlled test of whether selected information can move into a new environment and remain useful. It should answer practical questions before the full archive is converted: are relationships preserved, are important values interpreted correctly, and can users produce the outputs they need? A pilot is most valuable when…
-
How to Verify a Data Migration: Record Counts, Units, Coordinates and Exceptions
A successful import message confirms that a process finished; it does not establish that the resulting information is complete, correctly related or suitable for engineering use. Verification provides the evidence needed to answer those questions. For geotechnical data, that evidence must address both individual values and the context that gives them meaning. A borehole record…
-
What Does Geotechnical Data Migration Cost? Scope, Timing and Deliverables
Geotechnical data migration cost is difficult to estimate from a project count alone. Ten consistent databases may require less investigation than one heavily customized archive with unclear field meanings and missing dependencies. A useful budget therefore starts with the work needed to preserve meaning, verify results and support the intended destination workflow. This guide explains…
-
A Complete Geotechnical Workflow for Infrastructure Projects: WinLoG, GDMS and WinFence
See how WinLoG, GDMS and WinFence can support a connected geotechnical workflow from field records to testing and subsurface interpretation.
-
Why Legacy Geotechnical Data Is Becoming a Migration Risk
A geotechnical archive can look secure while becoming progressively harder to use. Project databases still exist, finished borehole logs are stored as PDFs, and an experienced team member knows where to find the original files. Yet none of those conditions guarantees that the information can be moved reliably into another system. Legacy geotechnical data migration…
-
From gINT to WinLoG and GaeaSynergy: A Practical Migration Plan
A gINT migration plan should begin with the work your organization needs to continue: producing dependable borehole logs, finding historical information, checking test results, and delivering consistent project outputs. Moving records into a new database is one part of that work. Preserving their meaning and making the new workflow usable are equally important. For teams…
-
What to Preserve When Migrating Historical Borehole Projects
Historical borehole projects are valuable because they connect observations to a particular place, depth, investigation, and method. When those projects move into a new system, preserving a list of boreholes and their final logs is only the beginning. The relationships and context behind the records determine how confidently the information can be reused. Migrating historical…