You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/energy-data-services/how-to-convert-segy-to-ovds.md
+13-11Lines changed: 13 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -155,7 +155,7 @@ Follow this [tutorial](tutorial-seismic-ddms.md) to Prepare Subproject which inv
155
155
156
156
### Upload the File
157
157
158
-
There are two ways to upload a SEGY file. One option is to use the sasurl through cURL call. You need to setup cURL on your OS.
158
+
There are two ways to upload a SEGY file. One option is to use the SASurl through cURL call. You need to setup cURL on your OS.
159
159
The second method is to use [SDUTIL](https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-sdutil/-/tags/azure-stable). To log in to your instance for ADME via the tool you need to generate a refresh token for the instance. See [How to generate auth token](how-to-generate-auth-token.md). Alternatively, you can modify the code of SDUTIL to use client credentials instead to log in. If you haven't already, you need to setup SDUTIL.Check this guide for setting up [SDUTIL](tutorial-seismic-ddms-sdutil.md) Download the codebase and edit the `config.yaml` at the root. Replace the contents of this config file with the following yaml.
Use the following `cURL` command to get a SAS upload URL:
198
200
@@ -206,25 +208,25 @@ cURL -X 'GET' \
206
208
**Sample Response:**
207
209
```json
208
210
{
209
-
"access_token": "<sas token>",
211
+
"access_token": "<SAS token>",
210
212
"expires_in": <duration>,
211
-
"token_type": "SasUrl"
213
+
"token_type": "SASUrl"
212
214
}
213
215
```
214
-
#### Modify sas url. Replace container name in sas url with filepath i.e gcsstring
216
+
#### Modify SAS url. Replace container name in SAS url with filepath i.e gcsstring
215
217
216
218
```bash
217
219
filepath="<gcsstring>"
218
220
container=$(echo "$filepath"| cut -d'/' -f1)
219
-
sasurl=$(echo "<sas token>" | sed "s|$container|$filepath|")
221
+
SASurl=$(echo "<SAS token>"| sed "s|$container|$filepath|")
220
222
```
221
223
222
224
##### Upload the SEG-Y file:
223
225
224
226
Use the following `cURL` command:
225
227
226
228
```bash
227
-
cURL -X PUT -T "<local_file_path>" "<sas_url>" \
229
+
cURL -X PUT -T "<local_file_path>""<SAS_url>" \
228
230
-H "x-ms-blob-type: BlockBlob"
229
231
```
230
232
@@ -445,19 +447,19 @@ cURL --request GET \
445
447
}
446
448
```
447
449
448
-
3. You can see if the converted file is present using the following command in sdutil or in the cURL API call:
450
+
1. You can see if the converted file is present using the following command in sdutil
449
451
450
452
```bash
451
453
python sdutil ls sd://<data-partition-id>/vdssubprojectname
452
454
```
453
455
454
-
4. Verify the converted files are present on the specified location in DAG Trigger or not
456
+
2. Verify the converted files are present on the specified location in DAG Trigger or not
455
457
456
458
```markdown
457
459
python sdutil ls sd://<data-partition-id>/vdssubprojectname/
458
460
```
459
461
460
-
5. If you would like to download and inspect your VDS files, don't use the `cp` command as it will not work. The VDS conversion results in multiple files, therefore the `cp` command won't be able to download all of them in one command. Use either the [SEGYExport](https://osdu.pages.opengroup.org/platform/domain-data-mgmt-services/seismic/open-vds/tools/SEGYExport/README.html) or [VDSCopy](https://osdu.pages.opengroup.org/platform/domain-data-mgmt-services/seismic/open-vds/tools/VDSCopy/README.html) tool instead. These tools use a series of REST calls accessing a [naming scheme](https://osdu.pages.opengroup.org/platform/domain-data-mgmt-services/seismic/open-vds/connection.html) to retrieve information about all the resulting VDS files.
462
+
3. If you would like to download and inspect your VDS files, don't use the `cp` command as it will not work. The VDS conversion results in multiple files, therefore the `cp` command won't be able to download all of them in one command. Use either the [SEGYExport](https://osdu.pages.opengroup.org/platform/domain-data-mgmt-services/seismic/open-vds/tools/SEGYExport/README.html) or [VDSCopy](https://osdu.pages.opengroup.org/platform/domain-data-mgmt-services/seismic/open-vds/tools/VDSCopy/README.html) tool instead. These tools use a series of REST calls accessing a [naming scheme](https://osdu.pages.opengroup.org/platform/domain-data-mgmt-services/seismic/open-vds/connection.html) to retrieve information about all the resulting VDS files.
0 commit comments