Import a surface and follow its calculations

The visual pilot connects a Workspace-imported surface to QGIS and a lightweight browser View. It uses the current project backend; OSDU raster interoperability is a separate qualification gate.

Try the workflow

1. Open your private Workspace connection and select a project where you may publish.
2. Import a Float32/Float64 GeoTIFF with one band, a north-up regular grid and a declared horizontal CRS. Supply its scalar unit and confirm snapshot retention. The pilot limit is 100,000 cells and 1.5 MB. Original bytes remain downloadable.
3. Open lightweight View and enable Follow new revisions. Images render on the server. Read exact value separately retrieves a scientific cell value.
4. Run Offset scalar values from Workspace. The named operator runs in a separate server process, then publishes a revision with exact input lineage. Old revisions remain readable. This action requires compute permission and the registered source publisher’s credential.
5. Download the QGIS connection profile. It contains references, never credentials. Your administrator supplies its separate private token file and SSH tunnel.
6. In the QGIS connector choose Open connection file…, then Connect live map. Pin current snapshot creates a fixed comparison. Select the connected raster and choose Run server offset… to submit the same operator from QGIS.

Network activity, file preparation and contour generation run in the connector’s background worker. QGIS applies prepared layers on its GUI thread. The numerical operator runs on the server, not in QGIS. Rescale live colors only adjusts the color legend; it does not change scientific values or publish a revision.

Scientific meaning and ownership

The source CRS stays attached to the raster; QGIS displays it in the project CRS. This does not convert scalar units or infer a vertical datum. Unknown, rotated or unsupported source coordinate definitions are refused for this import path. See coordinate policy.

Export produces a GeoTIFF, source text, metadata and exact reference. Derived metadata records input asset/revision, operator version, parameters and parameter units. The retained original has a separately verified checksum. Customer-owned exports remain useful independently of the application.

Recovery and limits

Follow uses long HTTP waits backed by native revision notifications. A hint causes an authorized read; it is not a data payload or access grant. Slow clients may skip intermediate display updates while exact revisions remain available in history. Retry an interrupted action with the same input. The publication journal reuses its prepared request. A stale input produces a conflict instead of a silent rebase. Revocation blocks future reads, but cannot erase previously exported copies.

This is a private, loopback/SSH development pilot with provisioned credentials, not public OIDC hosting. The operator currently updates Workspace imports only. ResInsight’s existing publication path remains supported; writing arbitrary results back into native ResInsight models is not implied. Production identity, installation/upgrades, larger workloads and OSDU domain contracts remain MVP gates.