Skip to content

Intersection component

Jump to bottom
Knut Midtveit edited this page Apr 6, 2022 · 26 revisions

Definitions

Intersection are a vertical cut through the 3D space, the cut is defined by a polyline. Hence the geometry of intersection are defined by a series of X,Y coordinates and linear between the XY coordinates. For intersections created from well trajectories or other curving geometries the intersection is still a polyline, hence a resampling of the trajectory. In addition there is a vertical range from depth to depth for the intersection.

Intersections can be shown in 2D and in 3D. In 2D the intersection Y axis are Depth and X axis are called Abscissa. Abscissa are the length along polyline starting a 0 from one end.

User stories for Intersection in 2D

  • As geoscientist I like to digitize an arbitrary cross section (Polyline) through the model, and also select a well trajectory that define the cross section
  • As geoscientist I like to see a 3D grid parameter including grid lines for a given run/realization
  • As geoscientist I like to see the ensemble Horizons and faults across above mentioned cross sections with following options: All realizations in ensemble, Min, Max, Mean, Uncertainty envelope
  • As geoscientist I like to see the interpreted well markers and interpreted zone logs on cross section in order to validate the models
  • As geoscientist I like to see where the models do not fit to well markers or zonelogs
  • As geoscientist I like to see where the perforations are in the cross section for a well
  • As geoscientist I like to see a seismic on intersection
  • As geoscientist I like to set transparency on grid parameters and seismic and other data in order to see several data objects on the intersection.

Milestones:

Assumptions:

  • Intersection definition is done upfront in map component as polyline (series of X,Y) from a well trajectory or any other dataobject
  • In a addition to Polyline there is z min z max
  • Intersection may consist partly by digitization anywhere on map by user and partly by selecting trajectories

MS1

  • Proposal is to use vtk.js library as we belive this is advantageous compared to the Deck.GL or ESV-Intersection library. (https://equinor.github.io/esv-intersection/storybook/master/?path=/story/complete-example--intersection)

  • Link the map digitization of intersection with intersection component Draw on intersection

  • Depth line from ensemble of faulted or not faulted horizons with selected color for each Horizon with options: All realizations in ensemble, Min, Max, Mean, Uncertainty envelope

  • Well markers as circles

  • Zonelog as log.

MS2

  • Seismic cross section for one run/realization, with run selector
  • Grid properties with time slider for one run/realisation with run selector
  • MD thickmarks along well

MS3

  • Grid properties and or grid lines for a given realization

Notes on colors

  • Colors for discrete data must be mapped to name of Zone or Horizon Example: discrete logs (zonelog), discrete grid parameters (Zone paramter), structural model zone should all have same color if name is the same If name is missing the color Black shall be used If data is undefined color is 100% transparent or not shown.

Use cases discussion Feb 18 2022

  • Axes / grid

    • XYZ
    • Abscissa
    • Seismic x/inline

  • Data types

    • Well trajectories
    • Well markers
    • Surfaces
      • Cloud (single polylines)
      • Uncertainty aggregations (min, max, etc.)
    • Zones
    • Faults
    • 3D grid
      • Grid lines
      • Fault lines
      • Property
    • Seismic
      • Samples
      • Cubic interpolated

  • Readout

    • 3D grid
      • Property value
      • Cell IJK
    • Seismic
      • inline/x-line
    • Well trajectory
      • MD, TVD
    • Surfaces
      • Uncertainty
      • Aggregations (eg. P90, min, max)

  • Custom style

    • Fonts, line style, colors

  • Custom annotations

    • Overlays (screen space)
    • World space
Clone this wiki locally