Open jorgenherje opened 12 months ago
I believe this was discussed offline, and that we ended up point this towards the sumo-uploader? Coordinate system (which should be synched with SMDA) is included in metadata for all data objects produced by fmu-dataio
but perhaps not embedded into the vds
object that is stored in Sumo (?)
That's true - I believe it was mentioned in the #sumo-oneseismic
channel in slack. I do not recall whether it was the Sumo case or VDS-slice which returned empty string when trying to fetch the coordinate system info as of now.
The main goal is to ensure some way to verify consistency when working with multiple services. VDS-slice of course reads from SUMO, as I understand? So the coordinate systems should basically be equal for all data within a case?
The wish is to have control of coordinate systems, and have control of data to make them comparable in space?
1) Data from various services are to be used together 2) Data across cases/ensembles are to be visualized together.
Example of workflow:
In ´Webviz´ it is developed a module to show a seismic fence, i.e. an intersection in a seismic cube. The cutting is done by providing a polyline, a set of (x, y)-coordinates, to slice in a seismic cube. In the front-end code the polyline is generated by sampling along a well path.
The seismic fence is generated by use of vds-slice. The polyline provided to ´vds-slice´ is generated by use of well trajectory from ´smda´ and utility functionality of esv-intersection. The final visualization is done using ´esv-intersection´.
An issue can be to ensure control of coordinates in the various services, and ensure that the well, resulting points in created polyline and the seismic cube are equivalent.