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
+21-21Lines changed: 21 additions & 21 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -51,29 +51,29 @@ Next, set up Postman:
51
51
52
52
1. Select **Import** in Postman.
53
53
54
-
[](media/tutorial-ddms/postman-import-button.png#lightbox)
54
+
[](media/tutorial-ddms/postman-import-button.png#lightbox).
55
55
56
56
2. Paste the URL of each file into the search box.
57
57
58
-
[](media/tutorial-ddms/postman-import-search.png#lightbox)
58
+
[](media/tutorial-ddms/postman-import-search.png#lightbox)
59
59
60
60
3. In the Postman environment, update **CURRENT VALUE** with the information from your Azure Data Manager for Energy instance details
61
61
62
62
1. In Postman, in the left menu, select **Environments**, and then select **SEGYtoVDS Environment**.
63
63
64
64
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'.
65
65
66
-
[](media/how-to-convert-segy-to-vds/postman-environment-current-values.png#lightbox)
66
+
[](media/how-to-convert-segy-to-vds/postman-environment-current-values.png#lightbox)
67
67
68
68
## Step by Step Process to convert SEG-Y file to oVDS
69
69
70
70
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.
71
71
72
-
[](media/how-to-convert-segy-to-vds/postman-code-button.png#lightbox)
72
+
[](media/how-to-convert-segy-to-vds/postman-code-button.png#lightbox)
73
73
74
74
### Create a Legal Tag
75
75
76
-
[](media/how-to-convert-segy-to-vds/postman-api-create-legal-tag.png#lightbox)
76
+
[](media/how-to-convert-segy-to-vds/postman-api-create-legal-tag.png#lightbox)
77
77
78
78
### Prepare dataset files
79
79
@@ -83,39 +83,39 @@ This file contains the sample [Vector Header Mapping](https://github.com/microso
83
83
84
84
The user needs to be part of the `users.datalake.admins` group. Validate the current entitlements for the user using the following call:
85
85
86
-
[](media/how-to-convert-segy-to-vds/postman-api-get-user-groups.png#lightbox)
86
+
[](media/how-to-convert-segy-to-vds/postman-api-get-user-groups.png#lightbox)
87
87
88
88
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.
89
89
90
90
If the user isn't part of the required group, you can add the required entitlement using the following sample call:
91
91
email-id: Is the value "Id" returned from the call above.
92
92
93
-
[](media/how-to-convert-segy-to-vds/postman-api-add-user-to-admins.png#lightbox)
93
+
[](media/how-to-convert-segy-to-vds/postman-api-add-user-to-admins.png#lightbox)
94
94
95
95
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.
96
96
97
97
### Prepare Subproject
98
98
99
99
#### 1. Register Data Partition to Seismic
100
100
101
-
[](media/how-to-convert-segy-to-vds/postman-api-register-tenant.png#lightbox)
101
+
[](media/how-to-convert-segy-to-vds/postman-api-register-tenant.png#lightbox)
102
102
103
103
#### 2. Create Subproject
104
104
105
105
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.
106
106
107
-
[](media/how-to-convert-segy-to-vds/postman-api-create-subproject.png#lightbox)
107
+
[](media/how-to-convert-segy-to-vds/postman-api-create-subproject.png#lightbox)
108
108
109
109
#### 3. Create dataset
110
110
111
111
> [!NOTE]
112
112
> This step is only required if you are not using `sdutil` for uploading the seismic files.
113
113
114
-
[](media/how-to-convert-segy-to-vds/postman-api-create-dataset.png#lightbox)
114
+
[](media/how-to-convert-segy-to-vds/postman-api-create-dataset.png#lightbox)
115
115
116
116
### Upload the File
117
117
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.
119
119
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.
120
120
121
121
```yaml
@@ -143,27 +143,27 @@ azure:
143
143
144
144
##### Get the sasurl:
145
145
146
-
[](media/how-to-convert-segy-to-vds/postman-api-get-gcs-upload-url.png#lightbox)
146
+
[](media/how-to-convert-segy-to-vds/postman-api-get-gcs-upload-url.png#lightbox)
147
147
148
148
##### Upload the file:
149
149
150
150
You need to select the file to upload in the Body section of the API call.
151
151
152
-
[](media/how-to-convert-segy-to-vds/postman-api-upload-file.png#lightbox)
152
+
[](media/how-to-convert-segy-to-vds/postman-api-upload-file.png#lightbox)
153
153
154
154
155
-
[](media/how-to-convert-segy-to-vds/postman-api-upload-file-binary.png#lightbox)
155
+
[](media/how-to-convert-segy-to-vds/postman-api-upload-file-binary.png#lightbox)
156
156
157
157
##### Verify upload
158
158
159
-
[](media/how-to-convert-segy-to-vds/postman-api-verify-file-upload.png#lightbox)
159
+
[](media/how-to-convert-segy-to-vds/postman-api-verify-file-upload.png#lightbox)
160
160
161
161
#### Method 2: SDUTIL
162
162
163
163
**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).
164
164
165
165
> [!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:`.
[](media/how-to-convert-segy-to-vds/postman-api-create-headermapping.png#lightbox)
189
+
[](media/how-to-convert-segy-to-vds/postman-api-create-headermapping.png#lightbox)
190
190
191
191
### Create Storage Records
192
192
193
-
[](media/how-to-convert-segy-to-vds/postman-api-create-records.png#lightbox)
193
+
[](media/how-to-convert-segy-to-vds/postman-api-create-records.png#lightbox)
194
194
195
195
### Run Converter
196
196
@@ -202,19 +202,19 @@ Generate the Header Vector Mapping
202
202
python sdutil auth idtoken
203
203
```
204
204
205
-
[](media/how-to-convert-segy-to-vds/postman-api-start-workflow.png#lightbox)
205
+
[](media/how-to-convert-segy-to-vds/postman-api-start-workflow.png#lightbox)
206
206
207
207
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
208
208
209
-
[](media/how-to-convert-segy-to-vds/postman-api-check-workflow-status.png#lightbox)
209
+
[](media/how-to-convert-segy-to-vds/postman-api-check-workflow-status.png#lightbox)
210
210
211
211
3. You can see if the converted file is present using the following command in sdutil or in the Postman API call:
212
212
213
213
```bash
214
214
python sdutil ls sd://<data-partition-id>/<subproject>
215
215
```
216
216
217
-
[](media/how-to-convert-segy-to-vds/postman-api-verify-file-converted.png#lightbox)
217
+
[](media/how-to-convert-segy-to-vds/postman-api-verify-file-converted.png#lightbox)
218
218
219
219
4. Verify the converted files are present on the specified location in DAG Trigger or not
0 commit comments