equinor / equinor/interpretation-models
Calculating extent_points
Open
- Dominant language
- Python
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
_extent_points_ are an extra attribute which we might only need when we ingest to OSDU. Since this requires a bit of thought, and and the easiest way of calculating extents accounting for rotation would be to derive it from the bulk data, we are not adding it for the MVP. We may add it in the future, so should we remove the column for now or keep it (and will have 'nulls' everywhere?)
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.