Subgeoby OAR Scanning
Drop in whatever you have - we read DIGGS (.xml), Excel boring logs (.xlsx), multi-sheet gINT-style workbooks, CSV tables in any common layout (collars, lithology, surveys, SPT), Leapfrog export zips, and store PDFs for the record. Project details, coordinate system, units, and stratigraphy are worked out from the data - you just review and confirm.
DIGGS (.xml), Excel logs, gINT-style workbooks, CSV tables, Leapfrog zips. PDFs are stored for record.
CSV/XYZ points (East, North, Elev in project CRS meters) - bathymetry or topo survey. Constrains the top of the model between boreholes; surveyed collars are always honored exactly.
Detects what every file is, proposes the schema mapping, and drafts a stratigraphy.
Everything below was pulled from the uploads where possible. Edit anything that's wrong; it's saved when you confirm.
North up, project grid meters. Amber = QC flags on that hole.
| Hole | East | North | Elev | TD | Intvls | Cover | Flags |
|---|
Confirming saves the project details, signs off the ingest review (stamped into the build report), and builds the model. Re-ingesting new data resets the sign-off.
Drafted automatically from the logs - review before modeling. Every lithology code must map to a unit.
| Unit | Name | Lithology | Codes (comma-sep) | Color | Contam. |
|---|
Per-contact Ordinary Kriging with uncertainty, stratigraphic ordering enforced, optional surface constraint, watertight unit solids, leave-one-out cross-validation, then all exports are generated in one pass.