What's next, and templates

When data lands in a project, Workspace shows What’s next under the report: how to open it in QGIS, how to read it in your own scripts, who can see it, and how to invite a colleague. Every sentence about QGIS comes from the deployment’s record of what QGIS opens, one line per kind of data, so a kind QGIS cannot show yet says so.

A template is a table with the right columns for one kind of data, one example row and (in Excel) a sheet that explains each column. A filled template is added with no question about its columns: the example row is skipped and your rows land.

In Workspace

1. Add data > Download a template. Choose the kind (wells, well tops, deviation surveys, points or time-depth pairs) and CSV or Excel, then metres or feet. Wells and points also ask for the coordinate system, by its name; wells ask what the depths are measured from (kelly bushing, ground level, mean sea level or not known).
2. Fill the rows below the example row, in any spreadsheet program, and save. Keep the header and the sheet names.
3. Drop the file on Add data and choose Say what it holds. The layout is recognised (“Matches Ophiolite’s standard layout.”), the example row is skipped (“The example row is skipped.”) and the result says what was added.
4. What’s next appears under the result:
   • Open in QGIS: the steps to add the project’s layer, with the address to paste (Copy address; the exact QGIS menus are under Technical details). Maps open through the QGIS plug-in: see Open your project in QGIS.
   • Read it in Python: the command and the Python line for each item, under Technical details, with your own access key. A seismic volume is read in slices; an item that cannot be sent to a script says so.
   • Share with the project: who can see each item, and Share to change it (New data and who can see it).
   • Invite a colleague: an organization owner invites; everyone else is told to ask one.

An empty project shows Get started with the template list and Start from the NLOG sample (a project administrator): 2,222 well headers and one gamma-ray log from NLOG.NL, in the Dutch national grid, depths in metres. Pressing it again adds nothing twice.

In Python

Download the well-tops template in metres. It holds the header and one example row:

template = client.template("well-tops", "csv", length="m")
path = template.save()          # well-tops-template.csv
print(open(path).read())

Fill your rows below the example row:

import csv

with open(path, "a", newline="") as table:
    rows = csv.writer(table)
    rows.writerow(["TM-2", "North Sea Supergroup", 0.0, "", "Composite log"])
    rows.writerow(["TM-2", "Chalk Group", 1012.5, "", "Composite log"])

Add it. The example row is skipped; each well in the table becomes one set of tops:

from ophiolite.imports import result_lines

tops = client.imports.from_table(path, "well-tops", {"well": "Well", "name": "Top name", "md": "Measured depth (m)"},
                                 declarations={"depth_unit": "m"})
print("\n".join(result_lines(tops["run"], tops["preview"])))

Read it back the way What’s next shows it, into a folder of your own:

first = tops["run"]["units"][0]
got = client.exchange("work").get(first["asset_id"], output="data/TM-2 tops")
print(got)

client.templates() lists the kinds, units and formats the deployment serves. client.start_sample() adds the NLOG sample (a project administrator) and steps its wells to the end; the same command_id returns the same run.

On the command line

ophiolite templates
ophiolite template well-tops --format xlsx --length m
ophiolite template wells --crs EPSG:28992 --reference KB --output wells.csv
ophiolite import table well-tops-template.csv --target well-tops --map "well=Well,name=Top name,md=Measured depth (m)" --declare depth_unit=m
ophiolite get --item ITEM --output "data/TM-2 tops"
ophiolite sample start

template writes TARGET-template.FORMAT unless --output names another file. sample start prints the sample’s statement, the log’s result and the number of wells added; when the wells are not all added it exits with the conflict code, and running it again finishes them.

What QGIS opens

What’s next names, for each kind you added, whether QGIS shows it as a map layer, through your map connection, or not yet. That list is the deployment’s record, held to the program’s record and the connector support on every site build, so the card never says more than has been checked.