Skip to content

Commit 3c7b905

Browse files
author
Preeti Singh
committed
remving postman ref
1 parent 5c51177 commit 3c7b905

File tree

1 file changed

+13
-11
lines changed

1 file changed

+13
-11
lines changed

articles/energy-data-services/how-to-convert-segy-to-ovds.md

Lines changed: 13 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -155,7 +155,7 @@ Follow this [tutorial](tutorial-seismic-ddms.md) to Prepare Subproject which inv
155155

156156
### Upload the File
157157

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.
159159
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.
160160

161161
```yaml
@@ -182,17 +182,19 @@ azure:
182182
#### Method 1: cURL
183183
184184
##### Get gcs url:
185+
186+
```bash
185187
cURL -X GET \
186188
-H "content-type: application/json" \
187189
-H "Authorization: Bearer <access_token>" \
188190
"https://<DNS>/seistore-svc/api/v3/dataset/tenant/<datapartition>/subproject/<vdssubprojectname>/dataset/<datasetname>"
189-
191+
```
190192

191193
**Sample Response:**
192194
Should be a string. we call it gcsstring.
193195

194196

195-
##### Get the sasurl:
197+
##### Get the SASurl:
196198

197199
Use the following `cURL` command to get a SAS upload URL:
198200

@@ -206,25 +208,25 @@ cURL -X 'GET' \
206208
**Sample Response:**
207209
```json
208210
{
209-
"access_token": "<sas token>",
211+
"access_token": "<SAS token>",
210212
"expires_in": <duration>,
211-
"token_type": "SasUrl"
213+
"token_type": "SASUrl"
212214
}
213215
```
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
215217

216218
```bash
217219
filepath="<gcsstring>"
218220
container=$(echo "$filepath" | cut -d'/' -f1)
219-
sasurl=$(echo "<sas token>" | sed "s|$container|$filepath|")
221+
SASurl=$(echo "<SAS token>" | sed "s|$container|$filepath|")
220222
```
221223

222224
##### Upload the SEG-Y file:
223225

224226
Use the following `cURL` command:
225227

226228
```bash
227-
cURL -X PUT -T "<local_file_path>" "<sas_url>" \
229+
cURL -X PUT -T "<local_file_path>" "<SAS_url>" \
228230
-H "x-ms-blob-type: BlockBlob"
229231
```
230232

@@ -445,19 +447,19 @@ cURL --request GET \
445447
}
446448
```
447449

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
449451

450452
```bash
451453
python sdutil ls sd://<data-partition-id>/vdssubprojectname
452454
```
453455

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
455457

456458
```markdown
457459
python sdutil ls sd://<data-partition-id>/vdssubprojectname/
458460
```
459461

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.
461463

462464
OSDU&reg; is a trademark of The Open Group.
463465

0 commit comments

Comments
 (0)