Map grid property to standard names (e.g. porosity)

[jcrivenaes]

Could you elaborate on use case and eventual what standard names should be?

[anders-kiaer]

The use case was brought up by @HansKallekleiv, and is typically to co-visualize some property (porosity, depth, ...) from RMS and Eclipse. The challenge today is that the properties have different names in the different tools (e.g. PORO, porosity - sometimes also indicating if it is effective or total, sometimes you need to refer to the manual to know...)

[perolavsvendsen]

Is this data.content? Assume for now that grid properties are exported 1 property per file. Perhaps just define the most common properties? porosity, permeability, etc.?

• [ ] Discuss/refine this. @HansKallekleiv @anders-kiaer @jcrivenaes

[jcrivenaes]

• porosity
• permeability ... anisotropy?
• water_saturation [Water saturation]
• oil_saturation
• gas_saturation
• zone (check SMDA)
• facies
• ntg
• hcpv
• stoiip/stooip
• giip
• hc_thickness ?
• ...

Avoid depth as default?

[perolavsvendsen]

Agree that "depth" should be avoided as default. Already polluting the stored data in Sumo. The combination of white-listing content and having a default quickly leads to using depth for everything that is not in the list. Example from current implementation on Snorre is that RFT-data is tagged with content: depth.

277

[jcrivenaes]

Yes we should probably let content be a mandatory field instead