Skip to content

Resolve "Data loading - Allow user to provide welllog ID and writing bulk data to that welllog id"

Niall McDaid requested to merge 22-write-bulk-data-to-existing-well-log into main

Closes #22 (closed)

General code restructuring:

  • Add WellboreRecord class to and associated tests (almost identical to how WellLogRecord is set up).
  • Restructure commands: I have added ingest as a top level command and moved fileload ingest --> ingest wellbore

Add ingest data command (to complete this ticket):

  1. Retrieve well log and associated wellbore records using OSDU client.
  2. Extract the info required for validation of the user-provided LAS file from these records - well name from wellbore record, curve IDs from well log record.
  3. Validate the LAS file (containing the data to be ingested) - well name in LAS file must match well name associate with wellbore and check curves in LAS file all exist in the existing well log record.
  4. If validation passes, extract data from the LAS file and write it to existing well log record.

Note: Like before with testing the ingest wellbore (previously fileload ingest), I've found it difficult to write unit tests for the ingest data command (as it may fall under the umbrella of integration tests). The individual components have been unit tested though and the command has been manually tested by me.

Edited by Greg Harris

Merge request reports