Anything, but random
Random lines in the cloud

Anything, but random

The way I have been drawing lines to test this new feature has been random. Usually, though a seismic interpreter will pick random or arbitrary lines to better understand the geology in the 3D seismic dataset.

At Osokey we want to utilise seismic in the cloud, so the ability to generate a seismic section based on a chosen path through a 3D seismic survey is a step closer to business as usual. In the video below I pick a path through a survey that is formed from three SEG-Y files. During ingestion into the cloud these were automatically merged into one survey outline polygon. Once the path is completed this triggers the creation of the random line and it can be opened in the seismic viewer. (Note: the video has no sound.)

This approach is directly accessing the SEG-Y data stored on cloud object-based storage. We have not transformed the seismic data into a different format to use it in the cloud. To enable this functionality you need to index the SEG-Y data that is added to your seismic data lake. We have been through a few different iterations, but have settled on a compact representation of the SEG-Y trace headers that enables the look-up of the relevant byte location to access a particular trace within the SEG-Y volume. In the above video we transform the map x,y coordinates into inline,crossline coordinates and then find the relevant bytes to extract the traces required to construct the random line.

This is a completely serverless implementation - there are no permanent servers managed by Osokey. This type of architecture makes for a very cost effective cloud implementation by only paying when something is happening, e.g. a user needing to look at a random line.

Same approach for horizon extraction coming up?

To view or add a comment, sign in

More articles by James S.

  • Multi-cloud Seismic Viewer

    Microsoft Azure have announced the general availability of Python support in Azure Functions, so it prompted me to look…

    3 Comments
  • Are duplicate files muddying your data lake?

    Osokey recently helped perform a bulk ingestion of 592,921 SEG-D files to Amazon S3 object storage using an AWS…

    9 Comments
  • .LAS events

    To develop and implement Osokey's cloud architecture it was important to think in terms of events. I recently worked…

    5 Comments
  • Seismic in the cloud: serverless, permissions and data duplication

    Serverless - where are the servers? My very simplistic view of cloud is that there are a number of different services…

    3 Comments
  • Seismic 2019 Tech-Byte delivered

    My Tech-Byte is over and so is Seismic 2019. It was great to engage in discussions about seismic data, cloud computing…

    2 Comments
  • Are you ingesting SEG-Y into the cloud?

    At Osokey we take the following approach to ingesting SEG-Y data into the Amazon Web Services (AWS) cloud. From…

    4 Comments
  • Using SEG-Y data in cloud

    I was really pleased to see that Equinor and partners in the Volve field have approved the data for sharing. In the…

    8 Comments

Others also viewed

Explore content categories