Pre-release. Ophiolite runs today for design partners; public source and server image publication are in preparation.

Ophiolite

Product

How it works between your applications

What happens to your work when it moves between the people and the applications on your team?

One project in the middle

Your project runs on your own server. Applications connect to it; it keeps every version and remembers who sent each one.

One project between your data and your applicationsData comes in from files, databases and uploads. Your project, on your own server, keeps every version, who sent it and which application received it (today). Your applications check for updates, get the latest version and send to the project: QGIS (today), your own code (today), OpendTect, ResInsight and more.Where datacomes fromfiles, databases,uploadsYour projecton your own serverEvery version keptWho sent each oneWhich applicationreceived ittodayYour applicationsQGIStodayYour own codetodayOpendTectResInsight
Applications with a connector check, get and send. Nothing changes in an application until a person chooses.

Three actions, and only one runs by itself

Checking for updates can run on its own. Getting the latest version and sending to the project are always a person's choice, or the choice of code a person wrote.

Check for updates, Get latest, Send to projectA changes an item (a map, here) in QGIS and chooses Send to project: the project keeps version 3 and adds version 4. B’s script checks for updates and is told that version 4 was sent by A; getting the latest version is B’s choice, and going back stays possible. A send made from an older version is refused, with two choices: look at the newer one, or save mine as a separate item. Activity then shows that B’s script received version 4 (today).A in QGISThe projectB’s scriptSend to projectversion 4version 3 is keptCheck for updates“map: version 4, sent by A”Get latestreads version 4;Go back stays possibleSend from version 3✕refused: look at the newer one,or save mine as a separate itemActivity: B’s script received version 4today
A send made from an older version is refused, never merged: you look at the newer one, or save yours as a separate item.

Which applications work with which kinds of data

Each mark comes from the qualification record of a connector. The table gives every cell in words, with what it is tested on and its limits.

Which applications work with which kinds of dataA grid of 11 applications and 13 kinds of data by direction; each filled cell carries a status mark. The table below the drawing gives every cell in words, with its limits.QGISOpendTectResInsightYour codeTyped uploadOSDU recordsPostgreSQLGeoTIFF filesLAS uploadSQLiteSection uploadWell logs · readWell logs · writeWells · readWells · writeTops and deviation · readSurfaces and grids · readSurfaces and grids · sendSurfaces and grids · writePoints and faults · readPoints and faults · writeSeismic · readSections and wavelets · readRecords · read✓*✓*✓*✓*✓*?✓*✓*✓*○✓*?✓*†?✓*?○○✓*?○✓*?✓*?✓*✓ works today · ✓* works today, with limits · ? not verified · ◐ in preparation · ○ planned · † the evidence disagrees
Marks are generated from the record; a blank cell means nothing is claimed.
ApplicationDataDirectionStatusTested onLimits
Your codeWell logsreadsworks today, with limitsPython
  • Preview (0.x) release; Windows is not yet qualified
OSDU recordsWell logsreadsworks today, with limitsOSDU Data Platform, Linux
  • Bounded Parquet fidelity
  • Not supported, not qualified: writing to OSDU
LAS file uploadWell logsreadsworks today, with limitsWeb browser, Linux
  • LAS formatting is kept only in the exact original
  • Not supported, not qualified: LAS 3
  • Not supported, not qualified: wrapped LAS with repeated curve names
  • Not supported, not qualified: automatic re-upload
OpendTectWell logswritesworks today, with limitsOpendTect Free 7.0.10, Linux
  • Float32 values and depth
  • missing endpoints absent in native log
  • gamma unit label canonicalized to API
  • Not supported, not qualified: source overwrite
  • Not supported, not qualified: resampling
  • Not supported, not qualified: automatic synchronization
  • Not supported, not qualified: Windows/macOS
Your codeWell logswritesworks today, with limitsPython
  • Preview (0.x) release; Windows is not yet qualified
Tops, survey, grid, fault and seismic uploadWellsreadsnot verifiedWeb browser
  • JSON formatting is kept only in the exact original
  • Not supported, not qualified: CRS transformation at upload
  • Not supported, not qualified: more than one well per file
PostgreSQL well headersWellsreadsworks today, with limitsPostgreSQL 16, Linux, web browser
  • Only mapped columns are read
  • Coordinates are as stored; the declared CRS is not transformed
  • Tables are read in pages of 1,000 rows inside one read-only snapshot, up to 100,000 rows and 64 MiB
  • Not supported, not qualified: change data capture
  • Not supported, not qualified: curves in SQL
  • Not supported, not qualified: schema changes without a new reviewed mapping
SQLite well locationsWellsreadsworks today, with limitsSQLite 3, Linux
  • Only mapped columns are read
  • Tables are read in pages of 1,000 rows inside one read-only snapshot, up to 100,000 rows and 64 MiB
  • Not supported, not qualified: files outside the gateway allowlist
PostgreSQL well headersWellswritesworks today, with limitsPostgreSQL 16, Linux, web browser
  • Only explicitly granted columns are written
  • Not supported, not qualified: creating or deleting rows
QGISTops and deviationreadsplannedQGISNone stated
Tops, survey, grid, fault and seismic uploadTops and deviationreadsworks today, with limitsWeb browser, Linux
  • Text formatting is kept only in the exact original
  • Not supported, not qualified: tie-in point
  • Not supported, not qualified: magnetic declination
  • Not supported, not qualified: absolute positions
QGISSurfaces and gridsreadsnot verifiedQGIS 4.2.2, macOS
  • Display styling is QGIS-side and not returned
  • A newer version is shown only when the person chooses Get latest; a check never changes the map
  • Not yet exercised in QGIS
  • Not supported, not qualified: editing in place
  • Not supported, not qualified: following the newest version automatically
  • Not supported, not qualified: editing
  • Not supported, not qualified: sending a horizon grid from QGIS
ResInsightSurfaces and gridsreadsworks today, with limits
The evidence for this cell disagrees
Technical details

The route's profile is not in the connector profile registry

ResInsight, Linux
  • Synthetic local coordinates in the pilot
  • Not supported, not qualified: writing into ResInsight
  • Not supported, not qualified: Mac qualification
Tops, survey, grid, fault and seismic uploadSurfaces and gridsreadsnot verifiedWeb browser, Linux
  • Text formatting is kept only in the exact original
  • Comment lines and number spelling are kept only in the exact original
  • Number spelling and spacing are kept only in the exact original
  • Not supported, not qualified: rotated grids
  • Not supported, not qualified: CRS transformation
  • Not supported, not qualified: interpolation
  • Not supported, not qualified: mesh editing
  • Not supported, not qualified: non-triangular faces
  • Not supported, not qualified: unit conversion
  • Not supported, not qualified: time-to-depth
  • Not supported, not qualified: inline/crossline horizons
GeoTIFF filesSurfaces and gridsreadsworks today, with limitsFile system, Linux, macOS
  • Only band 1 is read
  • Horizontal CRS conversion is limited to the qualified pair
  • Not supported, not qualified: multi-band rasters
  • Not supported, not qualified: vertical datum shifts
QGISSurfaces and gridssends to the projectnot verifiedQGIS 4.2.2, macOS
  • Styling, layer order and QGIS processing history are not sent
  • A result from a managed source, or one that changes the meaning or grid, is sent as a separate map
  • Not supported, not qualified: sending from a map opened through a connection file
  • Not supported, not qualified: merging two changes to one map
QGISSurfaces and gridswritesplannedQGISNone stated
QGISPoints and faultsreadsplannedQGISNone stated
Your codePoints and faultsreadsworks today, with limitsPython
  • Preview (0.x) release; Windows is not yet qualified
Tops, survey, grid, fault and seismic uploadPoints and faultsreadsnot verifiedWeb browser
  • Text formatting is kept only in the exact original
  • Not supported, not qualified: CRS transformation
  • Not supported, not qualified: text attributes
  • Not supported, not qualified: fault surfaces (triangulated planes)
QGISPoints and faultswritesplannedQGISNone stated
Your codeSeismicreadsworks today, with limitsPython
  • Preview (0.x) release; Windows is not yet qualified
Tops, survey, grid, fault and seismic uploadSeismicreadsnot verifiedWeb browser
  • Slice samples are converted to float64 exactly; header interpretations are recorded as decisions
  • Not supported, not qualified: SEG-Y formats other than IBM and IEEE float
  • Not supported, not qualified: little-endian or variable-length traces
  • Not supported, not qualified: irregular grids
  • Not supported, not qualified: volume export
Your codeSections and waveletsreadsworks today, with limitsPython
  • Preview (0.x) release; Windows is not yet qualified
Wavelet, rock model and seismic section uploadSections and waveletsreadsnot verifiedWeb browser
  • Text formatting is kept only in the exact original
  • The declared frequency is recorded as written; it is not checked against the samples
  • Not supported, not qualified: wavelet estimation from data
  • Not supported, not qualified: phase rotation
  • Not supported, not qualified: sample intervals outside 0.0005-0.01 s
  • Not supported, not qualified: more than 4095 samples
  • Not supported, not qualified: property grids (one rock index per cell only)
  • Not supported, not qualified: map position
  • Not supported, not qualified: more than 1,000,000 cells
  • Not supported, not qualified: 2D SEG-Y lines
  • Not supported, not qualified: depth-to-time conversion
  • Not supported, not qualified: more than 1,000,000 samples
OSDU recordsRecordsreadsworks today, with limitsOSDU Data Platform, Linux
  • Only approved kinds and fields
  • Not supported, not qualified: writing to OSDU
  • Not supported, not qualified: general raster kinds