equinor / equinor/interpretation-models

Model Domain vs Attribute

Open
#14 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
1
Forks
0
PR merge metrics
No merged PRs in 30d

Description

Align the representation of domain and attribute (currently in the interpretation level) with OSDU.

Potentially save z_domain as a restricted list - use the same list as OSDU, something like (depth, time, other) or (tvd, tvdss, twt, ..., other) - and have attribute as a separate item

Define based on that model if attribute should be in the InterpretationRecrod level or if it should go down to GriddedInterpretationRecord (i.e. if it also applies to polygons, point sets, faults or not)

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.