TheTechIdea OilGas - User guide Developer guide →

Field QC and mapping suggestions

Field-wide QC

wellbore-config qc <environment.json> <source> [--out folder] [--max N] checks every well of a data source and reports:

--out writes qc-wells.csv, qc-issues.csv and qc-report.html (with your trademark footnote). The tool exits 1 when it finds an error, so it can run in a pipeline. Wells are read one at a time and not kept, so large fields do not need large memory. From code: FieldQc.Run(source, new FieldQcOptions { Progress = ..., Cancellation = ..., Validator = ... }).

Mapping suggestions

For the values the coverage report could not resolve - code values, units, curve mnemonics, stratigraphic names - the setup proposes mappings: wellbore-config setup suggest <environment.json> <source> lists them, each with the setup accept ... command that applies it; the setup app puts the best one in the "Resolve with" box and lists the top three. Nothing is applied until you accept it, and an accepted suggestion is written exactly like a mapping you type yourself.

Suggestions come from comparing the value with the environment's own lists (the code catalogues, unit symbols and their spellings, the curve families' mnemonics, the stratigraphic chart and your lexicon): equal once case and separators are ignored, a prefix (GR_EDTC -> GR), contained (HCAL -> CAL), or close in spelling. A slash is kept, because in a unit it means "per": us/ft (microseconds per foot) is not usft (the US survey foot). Vendor mnemonics with no spelling in common (ZDEN for density, AT90 for deep resistivity) are not found this way; a further suggester - for example a language model - can be plugged in (IMappingSuggester), and its proposals are listed with its name and are likewise never applied without confirmation.