Add data

Adding data is one step for every kind Ophiolite reads: a well log, tops, a deviation survey, a grid, a mesh, points, faults, seismic, a well location, a wavelet, a model or seismic section, and a GeoTIFF surface. The file is read first. You see what it states and where each value comes from, and you answer only what it leaves open. Anything you leave alone is added as Not stated; nothing is guessed. Each file is a private file of the project until you share it.

The kinds this deployment reads, with their limits, are listed on File kinds. The Workspace names them under the drop area (“You can add: …”).

In the Workspace

1. Open Connect → Add files, or drop a file on the empty Data table or on the project’s first step. Drop files or a folder on “Drop files or a folder here”, press Choose files (a .zip file is opened as a folder) or Choose a folder, or press Add from an address and give an https:// link to one file. The deployment fetches the address; your browser does not, and the address is kept without its query string.
2. The read report opens. For one file: what the file states (Item, Value, Where it comes from), what was read (for a well log, its rows, curves and depth range), and under Needs your decision each value the file leaves open, preselected Not stated. A suggestion is offered as Use …; nothing is kept until you press it. For several files the report lists each file and asks each kind’s questions once.
3. When a well log’s header names a wellbore of the project, the report says so: “The file names the well … It matches the wellbore … in this project.” Press Link it, or Not this one. Nothing is linked by name alone.
4. Fill in Source attribution (required), Who may be given access and Well context notes, tick that you have permission to keep the file, make results from it and share it within this audience, and press Add this file (or Add n files). The report says what became of each file, as in Upload a folder.

A file that cannot be added says why in the read report, and nothing is sent: “The file does not state a coordinate system. Choose one to add it.” for a GeoTIFF without one, “A table (4 columns, 12 rows). This release cannot add tables yet.” for a table no reader takes (Show the columns this release reads lists what the table kinds read), and “No reader recognises this file. It looks like a web page, not a data file.” for an address that returned a page. A project set to Require complete context asks every open value before it adds the file.

In Python

from ophiolite import Client

client = Client.from_configuration("configuration.json")
log, grid = "TUM-02.las", "top-chalk.asc"   # a file, a folder, a .zip file or an https:// address

report = client.upload(log, attribution="Source: NLOG.NL", audience=[], rights_confirmed=True, link_wellbore=True)
print(report.label, report.counts)    # Finished {'added': 1, 'already-here': 0, ...}

link_wellbore=True links the file to the one wellbore of the project whose name its header names; without it, the report’s item carries the proposal and nothing is linked.

A file whose kind cannot be added without an answer (a grid that does not state its coordinate system) waits as “Needs your decision”. Say what it leaves open, per kind; a value you do not give is added as “Not stated”:

report = client.upload(grid, attribution="Source: NLOG.NL", audience=[], rights_confirmed=True,
                       declare={"esri-ascii-grid/1": {"crs": "EPSG:28992"}})
print(report.items[0]["declared"])    # {'crs': 'EPSG:28992'}

A declaration the kind does not take is refused before anything is sent, naming what it takes.

From the command line

ophiolite upload TUM-02.las --attribution "Source: NLOG.NL" --rights-confirmed --associate-matches
ophiolite upload "https://www.nlog.nl/brh-web/rest/brh/logdocument/<id>" --attribution "Source: NLOG.NL" --rights-confirmed

The command exits 0 when every file was added or is already here, 4 when any was not (the report is still written with --report), and 1 when it was refused before anything was sent.