How to read connector support
Qualify support per application version, data type and direction.
| Question | Why it matters |
|---|---|
| Can it read, write or both? | A consumer is not automatically a source. |
| Which scientific types? | A scalar map does not preserve an entire reservoir model. |
| Snapshot or continuous publication? | Repeated manual exports are not a persistent live binding. |
| What detects source changes? | Polling and callbacks have different timing and visibility. |
| What survives conversion? | Units, nulls, axes, precision and coordinate claims need evidence. |
| What can be edited natively? | Transferring values does not recreate proprietary solver state. |
| What access is checked? | Source access does not automatically authorize a destination copy. |
Current QGIS pilot
Section titled “Current QGIS pilot”One-way scalar-map consumption, follow/pin and local contours are qualified with synthetic PORO data on Mac QGIS 4.2.2. That source remains in unknown/local coordinates. Commit-driven scalar-map notifications now reach the bridge through gRPC; QGIS uses HTTP long polling.
A separate public USGS elevation fixture qualifies bounded horizontal raster conversion from EPSG:4326 to EPSG:3857 and display in a different QGIS project CRS. It does not qualify ResInsight CRS autodiscovery, datum/vertical changes, arbitrary reservoir write-back or OSDU raster support.
Coordinate behavior and limits · Data contract · API reference.
Extension status
Section titled “Extension status”A public connector SDK and certified compatibility catalogue remain planned. This page describes the qualification contract, not a stable SDK API.