The Engine Behind Every Number in GeoMaster.
DataEngine reads your survey, log and well files, maps every column to a standard mnemonic and unit for you to confirm, and computes trajectories, plans and distance to plan by minimum curvature. One engine, so the same input always gives the same answer.
How It Behaves
Built So You Can Trust the Numbers
Proposes, Never Decides
When you import a file, DataEngine proposes a mnemonic and a unit for every column, with a confidence and the reason. You confirm or override before anything is stored. If a file declares no unit, it asks rather than guessing.
One Unit Authority
Every conversion in GeoMaster goes through one unit engine. Values are stored in a canonical unit per dimension and converted to your display units, so feet and metres never mix silently.
Every Value Has a Source
Each value records where it came from: read from your file, entered by hand, or calculated. Derived values, such as azimuths completed from your corrections, are marked as calculated.
Contracts on Every Calculation
Each calculation declares the inputs it needs and the outputs it produces. Inputs are validated before it runs, so a missing correction or a bad datum is reported, not computed around.
From File to Calculation
What Happens When You Import a File
Nothing is stored until you confirm it, and values are read once and converted from that same copy.
Read
Detects the format from the file content, finds the header row, and in a workbook lists every sheet so you can pick the one with the data.
Detect
Matches each column header against the mnemonic registry and its aliases, and reads the unit from the file or the header text.
Confirm
You see the raw header, sample values and the proposal for each column. Anything uncertain is flagged for you to decide.
Validate and Convert
Values are checked against the schema rules and converted once to canonical units, from the same parsed copy of your file.
Calculate
Trajectories, plans and offsets are computed from the stored data and recalculated whenever the inputs change.
Formats and Objects
What You Can Import Today
Format
How It Is Read
CSV, TSV, TXT
Delimited text, with the header row found automatically; comment lines and title rows above the table are skipped
LAS
Well log files, detected from the ~V, ~W, ~C and ~A sections rather than the file extension
XLSX, XLSM, XLS
Excel workbooks, with every sheet listed so a cover sheet or well information page is not mistaken for the data
Object
What It Carries
Survey
Measured depth, inclination and one azimuth: grid, true or magnetic
Survey head
North reference, magnetic declination, grid convergence, vertical section azimuth and tie-in
Well header
Well identity, surface location and depth datum (KB)
Well plan
Planned stations, built into a full plan trajectory
Logs
Depth-indexed curves such as GR and resistivity, mapped to registry mnemonics
Formation tops
Tops by measured depth for each well
Re-importing a Survey
Choose what happens to the stations already stored. Sets in different depth units are refused rather than matched, so a survey is never silently doubled.
Replace
The new file is the survey. Stations not in it are removed.
Append
The new file adds stations only. An overlap with stored stations is refused, not guessed at.
Merge
Stations are matched by measured depth: matches are updated, new ones inserted, nothing removed.
Survey and Trajectory
Calculations in the App Today
Each one runs on the stored data and reruns when a survey, plan or correction changes.
Minimum Curvature Trajectory
Positions every survey station by the minimum curvature method, from the tie-in point you set, with KB and surface coordinates taken from the well header.
Well Plan
Builds a full plan from planned stations: positions, tool face, build and turn rates and absolute coordinates, on the same method as the actual well.
Distance to Plan
Densifies the plan along its curvature and finds the nearest plan point for each survey station, then splits the offset into high side (+ below plan) and lateral (+ left, looking downhole), the same sign convention as Landmark COMPASS.
Bit Projection
Projects the bit beyond the last survey station by extrapolating the inclination and azimuth trend, and adds it as a projected station, never as a survey.
Depth References on Logs
Interpolates the trajectory onto a log so every curve sample has TVD, TVDSS, northing, easting and vertical section.
Azimuth Completion
Whichever azimuth your survey arrives in, the others are derived and added as calculated values wherever the corrections allow.
North References
A survey arrives with exactly one azimuth. Positions are grid-referenced, so DataEngine checks you have the corrections it needs before it calculates.
Survey Arrives As
Needs
Grid azimuth
Nothing: positions are already grid-referenced
True azimuth
Grid convergence, to derive grid
Magnetic azimuth
Magnetic declination and grid convergence, to derive true and then grid
Every Station Gets
The trajectory output for each survey station, in your display units.
The free survey calculator runs a line-for-line port of this code, checked against DataEngine on 12 test surveys and 2,544 values, so the numbers on this site match the app.
The Registry
One Vocabulary for Well Data
Every mnemonic has a name, a category, a physical dimension and a canonical unit, plus the aliases service companies use for it, such as DEPT and DPTH for measured depth.
786
mnemonics in the registry
40
mnemonic categories, from survey to well control
26
unit dimensions, from length to slowness
437
automated tests
Already in the Engine
Built and Tested, Coming to the App
These run in DataEngine with their own tests, but have no app screens yet. LookAhead is still in development.
Surfaces and Grids
Readers for 21 surface and fault formats, plus interpolation (bilinear or inverse distance), dip and azimuth maps, isopach as TVT or TST, contours, Z statistics and well-to-surface intersections.
Geosteering Cross-Section
Surface profiles along the well path in vertical section against TVD or TVDSS, with every formation entry and exit the well makes.
Azimuthal Images
Assembles sector curves (4, 8 or 16 sectors) into an image, fits sinusoids to picked points for apparent and true dip, and picks dips automatically by harmonic fit.
Drilling Analytics
Drilling mode classification, MSE, ECD, d-exponent and Dc-exponent, mud window, mud gas ratios, trip detection, bit run performance and kick detection with a confidence score.
LookAhead Steering Solve
From the projected bit, a reaction window at the current tendency, then a curve-and-hold solution to a target TVD, vertical section and azimuth.
Surface Formats DataEngine Reads
DataEngine FAQ
How the engine handles your data.
DataEngine is the calculation and data standardisation engine inside GeoMaster. It reads imported files, maps columns to standard mnemonics and units, validates them, and computes trajectories, plans and distance to plan. It is part of GeoMaster, not a separate product.
No. On import it proposes a mnemonic and unit for each column with a confidence and a reason, and you confirm or override before anything is stored. If a unit cannot be read from the file, you are asked to supply it.
Minimum curvature, from the tie-in you set. Azimuths are brought to grid north for positions, using the magnetic declination and grid convergence in the survey head.
Yes. The survey calculator on this site is a line-for-line port of DataEngine trajectory code, checked against DataEngine output on 12 test surveys (2,544 values) every time either changes.
Not yet. The readers and calculations are built and tested in DataEngine, but the app screens for surfaces, images and drilling analytics are still to come. Today you can import surveys, survey heads, well headers, plans, logs and formation tops.
CSV, TSV and TXT, LAS, and Excel workbooks (XLSX, XLSM and XLS). WITSML 1.4.1.1 data comes in through the WITSML connection, and WITSML XML files can be imported too.
Learn more
Import Your First Survey
Start free, import a survey and see every station positioned by minimum curvature.