M19 Azure incorrect Inline range for OpenVDS file created from segy-to-vds-conversion DAG

When using the segy-to-vds-conversion DAG to convert segy to openvds data, the openvds file has the wrong inline count. The converted openvds file's inline range is 9985 to 10031, however, the expected inline range is 9985 to 10369.

The steps used to upload the segy file to seismic ddms are here: M19-Azure-Upload-Segy-File-SDUTIL-Michael.txt The steps used to convert the segy file to OpenVDS are here: M19-Azure-Segy-To-OpenVDS_SDDMS-Conversion-Michael.txt

To check the inline range of an openvds file, you can use the VDSInfo utility that is apart o the OpenVDS windows binaries. These binaries can be downloaded from https://bluware.jfrog.io/ui/native/Releases-OpenVDSPlus.

To use VDSInfo to check an openvds file in Seismic DDMS run the following command:

VDSInfo --connection "sdauthorityurl={{SEISMIC_DDMS_URL}};sdapikey={{SD_API_KEY}};sdtoken={{ACCESS_TOKEN}}" {{SD_PATH}}

Below is an excerpt of using VDSInfo to check the inline range of the OpenVDS file generated from the segy-to-vds-conversion DAG:

C:\Users\Michael\openvds\openvds+-3.1.4-win\openvds+-3.1.4\bin\msvc_140>VDSInfo --connection "sdauthorityurl=https://osdu-ship.msft-osdu-test.org/seistore-svc/api/v3;sdapikey=placeholder;sdtoken=..." sd://opendes/michaelm19/openvds/attempt4/test_vds_id_999822905641 ... "axisDescriptors" : [ { "coordinateMax" : 4500.0, "coordinateMin" : 0.0, "name" : "Sample", "numSamples" : 1126, "unit" : "ms" }, { "coordinateMax" : 2536.0, "coordinateMin" : 1932.0, "name" : "Crossline", "numSamples" : 303, "unit" : "unitless" }, { "coordinateMax" : 10031.0, "coordinateMin" : 9985.0, "name" : "Inline", "numSamples" : 24, "unit" : "unitless" } ], ... The full output of VDSInfo can be found here: VDSInfoOutput.txt