TheTechIdea OilGas - User guide Developer guide →

Exports: LAS 3.0, OSDU and WITSML 2.1

LAS 3.0

LasWriter.Write(model, set, new LasWriteOptions { Version = "3.0" }) writes LAS 3.0 to the CWLS "LAS 3.0 File Structure Specifications" (Release 3.00, 2000): ~Version (VERS 3.0, WRAP NO, DLM COMMA), ~Well with STRT / STOP / STEP first (STEP 0 when the sampling is not exactly constant) and every required line - NULL, COMP, WELL, FLD, LOC, SRVC, CTRY (the two-letter country code), DATE, a latitude / longitude set, and PROV / UWI / LIC for Canada or STAT / CNTY / API for the USA - then the tops and inclinometry section sets and the log data (~Log_Parameter, ~Log_Definition, ~Log_Data | Log_Definition) last. Numbers always carry a decimal place, values containing a comma are quoted, and characters the specification reserves are replaced.

Las3Checker.Check(text) checks any LAS 3.0 file against those structure rules (the checks LAS Certify lists) and returns the violations. LAS 2.0 output is unchanged.

OSDU

wellbore-config export-osdu <environment.json> <source> <records.json> (or OsduExport.Records(model)) writes each well as OSDU records: a master-data--Wellbore (with the depth datum as a vertical measurement), a work-product-component--WellboreTrajectory when there is a survey, and a work-product-component--WellLog per log set with its curves. Depths are in metres; units are UnitOfMeasure references (percent-encoded: g/cm3 is g%2Fcm3). The records need your deployment's settings:

"osdu": { "dataPartition": "opendes", "viewers": [ "data.default.viewers@opendes.yourcompany.com" ],
          "owners": [ "data.default.owners@opendes.yourcompany.com" ], "legalTags": [ "opendes-yourcompany-public-1" ] }

Without them the export warns. Every record validates against the official OSDU schemas (Wellbore 1.5.1, WellboreTrajectory 1.4.0, WellLog 1.5.0); the build checks this on each change.

WITSML 2.1

wellbore-config export-witsml <environment.json> <source> <folder> (or Witsml21Export.Export(model)) writes the well as WITSML 2.1 data objects - the current Energistics version (2.0 is no longer recommended for implementation): Well, Wellbore, Trajectory with its stations (azimuth reference from the header's survey north), and per log set a Log whose ChannelSet carries the channels. Each channel references its property kind from the Energistics property kind dictionary (gamma ray, bulk density, neutron porosity, resistivity, acoustic slowness, caliper, spontaneous potential, photoelectric factor, porosity, water saturation, shale volume fraction, temperature - by the curve's mnemonic after your mnemonic aliases; others: the dictionary's root "property") and the logging company (the header's service company). Units are Energistics unit symbols; v/v is m3/m3 and a unit outside the Energistics list is written as an extension (custom:pu).

The channel values are written as a LAS 3.0 file next to the log, which the channel set references (FileUri): the schema requires the data inline or by reference, and the inline JSON layout is not specified by the standard, so the reference to a standard LAS 3.0 file is used. UUIDs are derived from the well, so exporting again gives the same identifiers.

Every exported object validates against the official Energistics WITSML 2.1 and common 2.3 schemas, and every property kind against the Energistics dictionary; the build checks this on each change (the schemas are fetched for the check, not stored here - Energistics Product License Agreement).