Summary
Currently, visualizing well paths and surfaces in ResInsight requires an Eclipse or geomechanical case to be loaded, since these objects are only rendered inside case-based 3D views. This is unnecessarily restrictive for workflows that only need to inspect well paths and/or surfaces (e.g. planning, QC, or import review) without any grid/case data.
Proposal
Add a case-less 3D view (RimDataView) that can render well paths, surfaces, and polygons without requiring an owning Eclipse/geomechanical case. The view scales and navigates using the bounding box of its own contents (well paths + surfaces) instead of a grid's bounding box.
Key points:
- New
RimDataView/RimDataViewCollection classes, modeled closely on the existing RimSeismicView/RimSeismicViewCollection case-less view pattern.
- A "New 3D View" command is available from the well path and surface collection context menus, and is also auto-created the first time a well path or surface is imported into a project with no other 3D view yet.
- Well paths get per-view visibility control (
RimWellPathInView/RimWellPathInViewCollection), following the same per-view mirroring pattern already used for polygons (RimPolygonInView) and surfaces (RimSurfaceInView), so individual well paths can be toggled on/off per view.
Motivation
- Enables lightweight visualization/QC of well paths and surfaces without needing to load a full simulation case.
- Keeps the addition well isolated from existing case-based view types (Eclipse/GeoMech/Seismic), with no behavior change for those views.
Original issue description #13807
Summary
Currently, visualizing well paths and surfaces in ResInsight requires an Eclipse or geomechanical case to be loaded, since these objects are only rendered inside case-based 3D views. This is unnecessarily restrictive for workflows that only need to inspect well paths and/or surfaces (e.g. planning, QC, or import review) without any grid/case data.
Proposal
Add a case-less 3D view (
RimDataView) that can render well paths, surfaces, and polygons without requiring an owning Eclipse/geomechanical case. The view scales and navigates using the bounding box of its own contents (well paths + surfaces) instead of a grid's bounding box.Key points:
RimDataView/RimDataViewCollectionclasses, modeled closely on the existingRimSeismicView/RimSeismicViewCollectioncase-less view pattern.RimWellPathInView/RimWellPathInViewCollection), following the same per-view mirroring pattern already used for polygons (RimPolygonInView) and surfaces (RimSurfaceInView), so individual well paths can be toggled on/off per view.Motivation
Original issue description #13807