SegY to oVDS conversion in sdstore

Introduction

For oVDS conversion, the converter supports native cloud location and sdstore as long as the location of the segy is provided in the segy_file.

The practice is for all segy/oVDS/oZGY file to be stored in the sdstore so that applications can access the seismic data via the sdms API.

All CSP should ensure the following implementation of segy-oVDS conversion in the sdstore. Here are some examples of expected implementation of the workflow from IBM, GCP, Azure.

Example working procedure - postman collection from IBM: https://community.opengroup.org/osdu/platform/pre-shipping/-/blob/main/R3-M12/IBM-M12/M12-IBM_ODI_R3_v2.0.1_SEGY-to-Open_VDS_Conversion_Collection.postman_collection.json

Example working procedure - postman collection from GCP: https://community.opengroup.org/osdu/platform/pre-shipping/-/blob/main/R3-M12/GCP-M12/OpenVDS_SSDMS_to_SSDMS_conversion_CI-CD.postman_collection.json

Status

• AWS - M16
• IBM - Working
• GCP - Working
• Azure - Added in M13

Discrepancies observed in AWS

{
    "executionContext": {
        "data-partition-id": "{{data_partition_id}}",
        "url_connection": "Region={{vdsUrlConnectionStringRegion}};AccessKeyId={{vdsUrlConnectionStringAccessKeyId}};SecretKey={{vdsUrlConnectionStringSecretAccessKey}};SessionToken={{vdsUrlConnectionStringSessionToken}};Expiration={{vdsUrlConnectionStringExpiration}}",
        "input_connection": "Region={{vdsInputConnectionStringRegion}};AccessKeyId={{vdsInputConnectionStringAccessKeyId}};SecretKey={{vdsInputConnectionStringSecretAccessKey}};SessionToken={{vdsInputConnectionStringSessionToken}};Expiration={{vdsInputConnectionStringExpiration}}",
        "segy_file": "{{fileSource}}",
        "url": ""
    }
}

You can see that the executionContext is missing several keys like :

        "work_product_id": "{{work-product-id}}",
        "file_record_id": "{{file-record-id}}",
        "persistent_id": "{{vds_id}}",
        "id_token": "{{id_token}}"

These ids are needed to correctly fetch the seismic parameters (e.g. Inline, crossline etc.) to perform the oVDS conversion. Expected implementation is observed in - IBM / GCP / Azure [M13]

{
    "executionContext": {
        "Payload": {
            "AppKey": "test-app",
            "data-partition-id": "{{data-partition-id}}"
        },
        "vds_url": "{{test_vds_url}}",
        "work_product_id": "{{work-product-id}}",
        "file_record_id": "{{file-record-id}}",
        "persistent_id": "{{vds_id}}",
        "id_token": "{{id_token}}"
    }
}