`fmu-dataio` data requests

[anders-kiaer]

This is not a webviz issue per se, but a placeholder/container for data/feature requests to fmu-dataio project:

• [x] Parent grid: https://github.com/equinor/fmu-dataio/issues/278
• [ ] FIPNUM vs region/zone mapping: https://github.com/equinor/fmu-dataio/issues/532
  • Use case: Compare geo vs res volumes.
  • Use case: Easier/more discipline-agnostic filters in frontend (for pure res.data derived from UNSMRY).
  • Open question: Should it be stored on REAL, ensemble or case level?
• [ ] Blocked/modelled well logs: https://github.com/equinor/fmu-dataio/issues/372
  • Use case: QC blocked/modelled well logs with observed/measured well logs.
  • Use case: Statistical analysis of modelled well logs.
• [ ] Well uuid / alias mapping
  • Use case: Compare Eclipse simulated production data with official production data.
• [ ] Richer ensemble metadata https://github.com/equinor/fmu-dataio/issues/299
  • Use case: Give user possibility to load RESTART data and know which parameters (from RESTART ensemble) where used for a prediction run.
  • Use case: Help user in understanding which ensembles makes sense to compare for selected modules (e.g. iter-0, ..., iter-X within same AHM run).
  • Use case: Get explicit metadata on ensemble type (is it scenario based sensitivity run, or stochastic, or restart from another ensemble)
• [ ] Observations
• [ ] Common "latest & greatest" Drogon case with fmu-dataio
  • Use case: Webviz can run non-mandatory integration tests towards the case, and give feedback upstream and/or adjust upfront in Webviz accordingly. Also might shorten feedback loop between webviz and fmu-dataio.
• [ ] Stratigraphy/zone depth order/info/definition
  • Use case: order of zones visualized in well completions need info of which zone to be placed where from top to bottom row. (ref. #761)

[anders-kiaer]

Actions from meeting Sep 23rd:

• [ ] SUMO make data.geometry metadata searchable (introduced in https://github.com/equinor/fmu-dataio/pull/677).