Bedrock and surficial geology offline
With survey vintage stated.
Industries · Resource · Whitepaper
The camp is the constraint.
Mineral exploration is a logistics problem with a geology problem inside it. The bedrock question is answered by data; the reason programs fail is camp supply, crew rotation, access in a thaw and a medical distance measured in flying hours.
01 / Problem statement
What actually goes wrong.
An exploration program has a geological objective and three logistical constraints that decide whether it is met.
Access is seasonal and reversible. A winter road, a frozen crossing or a dry creek bed is a route for part of the year and an obstacle for the rest. A route computed in February is wrong in May.
Camp supply is depletable state. Fuel, food, water, drill consumables and power are inventories with burn rates, not a packing list. Running a camp on a spreadsheet updated when somebody has signal is how programs stop.
Crew rotation is a scheduling and comms problem. Fly-in fly-out rotation means the party composition changes while the camp continues, and the handover has to survive the fact that nobody involved had a connection at the same time.
02 / Mechanism
How NavTrax addresses each one.
Each entry names the mechanism rather than the benefit, so it can be evaluated rather than believed.
- Geology layers with vintage
- Bedrock, surficial geology, mineral occurrence and seismic hazard, each carrying its custodian and survey vintage, so a 1970s map is not read as current.
- Seasonal access as a routing constraint
- Winter road and crossing viability is an attribute on the network, so a route is computed for the season it will be driven in.
- Camp inventory as depletable state
- Fuel, water, food and consumables tracked with burn rates and reorder points, synced over whatever channel exists, including a satellite digest.
- Rotation-safe handover
- Trip and camp state are operations in a durable log with causal ordering, so an outgoing and incoming crew who were never online together still converge on one truth.
- Capability-matched medical planning
- Facilities distinguished by capability, with flying weather and the window, in the contingency plan before it is needed.
- Air-gapped option
- For programs on a network policy that forbids cloud egress, the platform runs with no external connectivity and syncs by signed bundle.
03 / Capabilities
In the field, this is what you have.
Seasonal route computation
Winter roads and crossings as season-dependent attributes.
Camp inventory with burn rates
Depletable state, not a list.
Sample and observation capture
Structured, offline, tied to position and to the geological layer.
Rotation handover that converges
Causally ordered operations, no lost edits between crews.
Remote medical planning
Capability-matched, weather-aware, pre-planned.
04 / Reference
| Risk | Mechanism | Works offline |
|---|---|---|
| Seasonal access misjudged | Season-attributed routing | Yes |
| Camp fuel or water depletion | Inventory with burn rates and reorder points | Yes |
| Lost handover between rotations | Durable op log with causal ordering | Yes |
| Stale geological interpretation | Survey vintage on every layer | Yes |
| Medical delay | Capability-matched contingency plan | Yes |
| Cloud policy prohibition | Air-gapped bundle sync | Yes |
05 / Process
Traced, node by node.
Geology is the objective. Logistics is the risk.
Industry modules and custom workflows are Elite. Air-gapped deployment is Enterprise.