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 |
|---|
Saves name, CRS, and units. Optional initials are recorded as ingest sign-off in the build report. Sign-off is not required to build a provisional model. Error-level QC still blocks modeling until the source is fixed.
Drafted automatically from the logs - review before modeling. Every lithology code must map to a unit.
| Unit | Name | Lithology | Codes (comma-sep) | Color | Contam. |
|---|
After ingest, correlations are generated automatically when lithology is sufficient. Build Model always regenerates from current code and observations, then reapplies reviewer edits. Use regenerate only to preview a fresh automatic interpretation without building.
One action: Subgeo checks that the logs are structurally valid, regenerates the automatic interpretation from current observations and code, reapplies your edits, and builds a provisional explicit-layer model. Previously generated layers are not reused just because they were saved. Acceptance signs off a revision; it does not freeze future builds. There is no legacy U# fallback.
Build Model generates a proposal automatically when lithology is sufficient. Inspect layers here after the 3D preview exists.
Questionable memberships and uncorrelated occurrences. Leave uncorrelated is valid. A proposed layer is a machine interpretation, not an accepted engineering fact. A hole with a lithology log still has stratigraphy even if it is uncorrelated.
Filled = members of the selected layer. Outline = other holes.