Skip to content

Commit a156a12

Browse files
author
Divya Prakash Sivakumar
committed
Resolved comments
1 parent 66ca1fb commit a156a12

File tree

5 files changed

+40
-40
lines changed

5 files changed

+40
-40
lines changed

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

Lines changed: 21 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -51,29 +51,29 @@ Next, set up Postman:
5151

5252
1. Select **Import** in Postman.
5353

54-
[![Screenshot that shows the import button in Postman](media/tutorial-ddms/postman-import-button.png)](media/tutorial-ddms/postman-import-button.png#lightbox)
54+
[![Screenshot that shows the import button in Postman.](media/tutorial-ddms/postman-import-button.png)](media/tutorial-ddms/postman-import-button.png#lightbox).
5555

5656
2. Paste the URL of each file into the search box.
5757

58-
[![Screenshot that shows importing collection and environment files in Postman via URL](media/tutorial-ddms/postman-import-search.png)](media/tutorial-ddms/postman-import-search.png#lightbox)
58+
[![Screenshot that shows importing collection and environment files in Postman via URL.](media/tutorial-ddms/postman-import-search.png)](media/tutorial-ddms/postman-import-search.png#lightbox)
5959

6060
3. In the Postman environment, update **CURRENT VALUE** with the information from your Azure Data Manager for Energy instance details
6161

6262
1. In Postman, in the left menu, select **Environments**, and then select **SEGYtoVDS Environment**.
6363

6464
2. In the **CURRENT VALUE** column, enter the information that's described in the table in 'Get your Azure Data Manager for Energy instance details'.
6565

66-
[![Screenshot that shows where to enter current values in SEGYtoVDS environment](media/how-to-convert-segy-to-vds/postman-environment-current-values.png)](media/how-to-convert-segy-to-vds/postman-environment-current-values.png#lightbox)
66+
[![Screenshot that shows where to enter current values in SEGYtoVDS environment.](media/how-to-convert-segy-to-vds/postman-environment-current-values.png)](media/how-to-convert-segy-to-vds/postman-environment-current-values.png#lightbox)
6767

6868
## Step by Step Process to convert SEG-Y file to oVDS
6969

7070
The Postman collection provided has all of the sample calls to serve as a guide. You can also retrieve the equivalent cURL command for a Postman call by clicking the **Code** button.
7171

72-
[![Screenshot that shows the Code button in Postman](media/how-to-convert-segy-to-vds/postman-code-button.png)](media/how-to-convert-segy-to-vds/postman-code-button.png#lightbox)
72+
[![Screenshot that shows the Code button in Postman.](media/how-to-convert-segy-to-vds/postman-code-button.png)](media/how-to-convert-segy-to-vds/postman-code-button.png#lightbox)
7373

7474
### Create a Legal Tag
7575

76-
[![Screenshot of creating Legal Tag](media/how-to-convert-segy-to-vds/postman-api-create-legal-tag.png)](media/how-to-convert-segy-to-vds/postman-api-create-legal-tag.png#lightbox)
76+
[![Screenshot of creating Legal Tag.](media/how-to-convert-segy-to-vds/postman-api-create-legal-tag.png)](media/how-to-convert-segy-to-vds/postman-api-create-legal-tag.png#lightbox)
7777

7878
### Prepare dataset files
7979

@@ -83,39 +83,39 @@ This file contains the sample [Vector Header Mapping](https://github.com/microso
8383

8484
The user needs to be part of the `users.datalake.admins` group. Validate the current entitlements for the user using the following call:
8585

86-
[![Screenshot that shows the API call to get user groups in Postman](media/how-to-convert-segy-to-vds/postman-api-get-user-groups.png)](media/how-to-convert-segy-to-vds/postman-api-get-user-groups.png#lightbox)
86+
[![Screenshot that shows the API call to get user groups in Postman.](media/how-to-convert-segy-to-vds/postman-api-get-user-groups.png)](media/how-to-convert-segy-to-vds/postman-api-get-user-groups.png#lightbox)
8787

8888
Later in this tutorial, you need at least one `owner` and at least one `viewer`. These user groups look like `data.default.owners` and `data.default.viewers`. Make sure to note one of each in your list.
8989

9090
If the user isn't part of the required group, you can add the required entitlement using the following sample call:
9191
email-id: Is the value "Id" returned from the call above.
9292

93-
[![Screenshot that shows the API call to get register a user as an admin in Postman](media/how-to-convert-segy-to-vds/postman-api-add-user-to-admins.png)](media/how-to-convert-segy-to-vds/postman-api-add-user-to-admins.png#lightbox)
93+
[![Screenshot that shows the API call to get register a user as an admin in Postman.](media/how-to-convert-segy-to-vds/postman-api-add-user-to-admins.png)](media/how-to-convert-segy-to-vds/postman-api-add-user-to-admins.png#lightbox)
9494

9595
If you haven't yet created entitlements groups, follow the directions as outlined in [How to manage users](how-to-manage-users.md). If you would like to see what groups you have, use [Get entitlements groups for a given user](how-to-manage-users.md#get-entitlements-groups-for-a-given-user). Data access isolation is achieved with this dedicated ACL (access control list) per object within a given data partition.
9696

9797
### Prepare Subproject
9898

9999
#### 1. Register Data Partition to Seismic
100100

101-
[![Screenshot that shows the API call to register a data partition as a seismic tenant in Postman](media/how-to-convert-segy-to-vds/postman-api-register-tenant.png)](media/how-to-convert-segy-to-vds/postman-api-register-tenant.png#lightbox)
101+
[![Screenshot that shows the API call to register a data partition as a seismic tenant in Postman.](media/how-to-convert-segy-to-vds/postman-api-register-tenant.png)](media/how-to-convert-segy-to-vds/postman-api-register-tenant.png#lightbox)
102102

103103
#### 2. Create Subproject
104104

105105
Use your previously created entitlement groups that you would like to add as ACL (Access Control List) admins and viewers. Data partition entitlements don't necessarily translate to the subprojects within it, so it is important to be explicit about the ACLs for each subproject, regardless of what data partition it is in.
106106

107-
[![Screenshot that shows the API call to create a seismic subproject in Postman](media/how-to-convert-segy-to-vds/postman-api-create-subproject.png)](media/how-to-convert-segy-to-vds/postman-api-create-subproject.png#lightbox)
107+
[![Screenshot that shows the API call to create a seismic subproject in Postman.](media/how-to-convert-segy-to-vds/postman-api-create-subproject.png)](media/how-to-convert-segy-to-vds/postman-api-create-subproject.png#lightbox)
108108

109109
#### 3. Create dataset
110110

111111
> [!NOTE]
112112
> This step is only required if you are not using `sdutil` for uploading the seismic files.
113113
114-
[![Screenshot that shows the API call to create a seismic dataset in Postman](media/how-to-convert-segy-to-vds/postman-api-create-dataset.png)](media/how-to-convert-segy-to-vds/postman-api-create-dataset.png#lightbox)
114+
[![Screenshot that shows the API call to create a seismic dataset in Postman.](media/how-to-convert-segy-to-vds/postman-api-create-dataset.png)](media/how-to-convert-segy-to-vds/postman-api-create-dataset.png#lightbox)
115115

116116
### Upload the File
117117

118-
There are two ways to upload a SEGY file. One option is use the sasurl through Postman / curl call. You need to download Postman or setup Curl on your OS.
118+
There are two ways to upload a SEGY file. One option is to use the sasurl through Postman / curl call. You need to download Postman or setup Curl on your OS.
119119
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 login to your instance for ADME via the tool you need to generate a refresh token for the instance. See [How to generate a refresh token](how-to-generate-refresh-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. Download the codebase and edit the `config.yaml` at the root. Replace the contents of this config file with the following yaml.
120120

121121
```yaml
@@ -143,27 +143,27 @@ azure:
143143
144144
##### Get the sasurl:
145145
146-
[![Screenshot that shows the API call to get a GCS upload URL in Postman](media/how-to-convert-segy-to-vds/postman-api-get-gcs-upload-url.png)](media/how-to-convert-segy-to-vds/postman-api-get-gcs-upload-url.png#lightbox)
146+
[![Screenshot that shows the API call to get a GCS upload URL in Postman.](media/how-to-convert-segy-to-vds/postman-api-get-gcs-upload-url.png)](media/how-to-convert-segy-to-vds/postman-api-get-gcs-upload-url.png#lightbox)
147147
148148
##### Upload the file:
149149
150150
You need to select the file to upload in the Body section of the API call.
151151
152-
[![Screenshot that shows the API call to upload a file in Postman](media/how-to-convert-segy-to-vds/postman-api-upload-file.png)](media/how-to-convert-segy-to-vds/postman-api-upload-file.png#lightbox)
152+
[![Screenshot that shows the API call to upload a file in Postman.](media/how-to-convert-segy-to-vds/postman-api-upload-file.png)](media/how-to-convert-segy-to-vds/postman-api-upload-file.png#lightbox)
153153
154154
155-
[![Screenshot that shows the API call to upload a file binary in Postman](media/how-to-convert-segy-to-vds/postman-api-upload-file-binary.png)](media/how-to-convert-segy-to-vds/postman-api-upload-file-binary.png#lightbox)
155+
[![Screenshot that shows the API call to upload a file binary in Postman.](media/how-to-convert-segy-to-vds/postman-api-upload-file-binary.png)](media/how-to-convert-segy-to-vds/postman-api-upload-file-binary.png#lightbox)
156156
157157
##### Verify upload
158158
159-
[![Screenshot that shows the API call to verify a file binary is uploaded in Postman](media/how-to-convert-segy-to-vds/postman-api-verify-file-upload.png)](media/how-to-convert-segy-to-vds/postman-api-verify-file-upload.png#lightbox)
159+
[![Screenshot that shows the API call to verify a file binary is uploaded in Postman.](media/how-to-convert-segy-to-vds/postman-api-verify-file-upload.png)](media/how-to-convert-segy-to-vds/postman-api-verify-file-upload.png#lightbox)
160160
161161
#### Method 2: SDUTIL
162162
163163
**sdutil** is an OSDU desktop utility to access seismic service. We use it to upload/download files. Use the azure-stable tag from [SDUTIL](https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-sdutil/-/tags/azure-stable).
164164
165165
> [!NOTE]
166-
> when running `python sdutil config init`, you don't need to enter anything when prompted with `Insert the azure (azureGlabEnv) application key:`.
166+
> When running `python sdutil config init`, you don't need to enter anything when prompted with `Insert the azure (azureGlabEnv) application key:`.
167167

168168
```bash
169169
python sdutil config init
@@ -186,11 +186,11 @@ python sdutil cp ST10010ZC11_PZ_PSDM_KIRCH_FULL_T.MIG_FIN.POST_STACK.3D.JS-01753
186186

187187
Generate the Header Vector Mapping
188188

189-
[![Screenshot that shows the API call to create header vector mapping in Postman](media/how-to-convert-segy-to-vds/postman-api-create-headermapping.png)](media/how-to-convert-segy-to-vds/postman-api-create-headermapping.png#lightbox)
189+
[![Screenshot that shows the API call to create header vector mapping in Postman.](media/how-to-convert-segy-to-vds/postman-api-create-headermapping.png)](media/how-to-convert-segy-to-vds/postman-api-create-headermapping.png#lightbox)
190190

191191
### Create Storage Records
192192

193-
[![Screenshot that shows the API call to create storage records in Postman](media/how-to-convert-segy-to-vds/postman-api-create-records.png)](media/how-to-convert-segy-to-vds/postman-api-create-records.png#lightbox)
193+
[![Screenshot that shows the API call to create storage records in Postman.](media/how-to-convert-segy-to-vds/postman-api-create-records.png)](media/how-to-convert-segy-to-vds/postman-api-create-records.png#lightbox)
194194

195195
### Run Converter
196196

@@ -202,19 +202,19 @@ Generate the Header Vector Mapping
202202
python sdutil auth idtoken
203203
```
204204

205-
[![Screenshot that shows the API call to start the conversion workflow in Postman](media/how-to-convert-segy-to-vds/postman-api-start-workflow.png)](media/how-to-convert-segy-to-vds/postman-api-start-workflow.png#lightbox)
205+
[![Screenshot that shows the API call to start the conversion workflow in Postman.](media/how-to-convert-segy-to-vds/postman-api-start-workflow.png)](media/how-to-convert-segy-to-vds/postman-api-start-workflow.png#lightbox)
206206

207207
2. Let the DAG run to the `succeeded` state. You can check the status using the workflow status call. The run ID is in the response of the above call
208208

209-
[![Screenshot that shows the API call to check the conversion workflow's status in Postman](media/how-to-convert-segy-to-vds/postman-api-check-workflow-status.png)](media/how-to-convert-segy-to-vds/postman-api-check-workflow-status.png#lightbox)
209+
[![Screenshot that shows the API call to check the conversion workflow's status in Postman.](media/how-to-convert-segy-to-vds/postman-api-check-workflow-status.png)](media/how-to-convert-segy-to-vds/postman-api-check-workflow-status.png#lightbox)
210210

211211
3. You can see if the converted file is present using the following command in sdutil or in the Postman API call:
212212

213213
```bash
214214
python sdutil ls sd://<data-partition-id>/<subproject>
215215
```
216216

217-
[![Screenshot that shows the API call to check if the file has been converted](media/how-to-convert-segy-to-vds/postman-api-verify-file-converted.png)](media/how-to-convert-segy-to-vds/postman-api-verify-file-converted.png#lightbox)
217+
[![Screenshot that shows the API call to check if the file has been converted.](media/how-to-convert-segy-to-vds/postman-api-verify-file-converted.png)](media/how-to-convert-segy-to-vds/postman-api-verify-file-converted.png#lightbox)
218218

219219
4. Verify the converted files are present on the specified location in DAG Trigger or not
220220

0 commit comments

Comments
 (0)