Add import well path from OSDU

content/Wells-and-Completions/WellPaths.md

@@ -14,75 +14,23 @@ ResInsight also supports creation of your own user-defined well paths. See [Crea
 ## Ascii Well Paths
 
 The command **File -> Import -> Well Data -> Import Well Paths From File** will read the well paths in the selected file, and create one entry for each well path under the {{< image-in-text src="images/3d-main-window/WellCollection.png" >}} **Wells** item in the **Project Tree**. 
-
-The supported ASCII format is quite flexible but the main requirements are: 
-
-- Each data line must contain four numbers: X Y TVD(MSL) MD(RKB) separated with white-space.
-- Lines starting with `"--" or "#"` is considered to be comment lines
-- A line starting with none-number-characters are used as a well name after the following rules:
-  - If the line contains a pair of : ```  "'", "`", "´", "’" or "‘" ``` the text between the quotation marks is used as a well name.
-  - If the line contains the case insensitive string "name" with an optional ":" after then the rest of the line is used as a well name. 
-  - If there are no quotes or "name"'s, the complete line is used as a well name.
-  - If there are several consecutive name-like lines, only the last one will be used 
-- If a well name is found, a new well is created and the following data points are added to it.
-
-#### Example 1:
-```txt
-WELLNAME: WELL1
-6507.1	725	2542	2590
-6523.5	757	2549	2626.6
-6523.5	760	2559	2637.1
--999
-WELLNAME: WELL2
-550.7 1020.2  2410   2410
-551   1004.1  2422.2 2430.2
-555.2  993.9  2425   2441.6
--999
-```
-
-#### Example 2:
-```txt
-X Y TVD(MSL) MD(RKB)
-Name Well_1
-6507.1	725	2542	2542
-6523.5	757	2549	2578.6
-6523.5	760	2559	2589.1
-
--- A Comment new well
-This is not its name
-Name Well_2
-550.7	1020.2	2410	2520
-551	1004.1	2422.2	2540.2
-# a comment inside the data 
-555.2	993.9	2425	2551.6
-
-3Q AHB-J
-5507.0	4638.5	0.0	0.0
-5507	4638.5	1628.6	1628.6
-```
 
-### Well Path Files are Referenced
-The well path data is not copied into the ResInsight project as such. The project file only stores the file path, and the next time you open the project, ResInsight will try to read the well data from the file again.  
-
-{{% notice info %}}
-If the well path file is changed and you would like a running ResInsight to update accordingly, you will need to delete all the well paths that emerge from that file, and import it again.
-{{% /notice %}}
+## Importing well paths from OSDU
 
-## Importing well paths from SSI-Hub
+Well path trajectories can be downloaded from an OSDU cloud service. When storing the project file, the reference to the OSDU trajectory is stored. This will ensure that authentication and access is checked before the trajectory is downloaded.
 
-SSI-Hub is an Equinor internal webservice. In order to import well paths from SSI-Hub, a project file must be present and stored to file. All imported well paths from the web service will be stored relative to this project file location. If no project file exists, the menu item is disabled.
+Download of OSDU trajectories will not work if the project is used on a server, as the user is required to authenticate before download of data.
 
-The command **File -> Import -> Well Data -> Import Well Paths From SSI-hub** launches a wizard to guide you through the process of selecting the well paths you need.
+The command **File -> Import -> Well Data -> Import Well Paths From OSDU** launches a wizard to guide you through the process of selecting the well paths you need.
 Having completed the wizard, the imported wells are accessible as Items under the {{< image-in-text src="images/3d-main-window/WellCollection.png" >}} **Wells** item in the **Project Tree**.
 
-The well path data is not copied into the ResInsight project as such, but is stored in files in a directory called *ProjectFileName_wellpaths* in the same directory as your project file.   
+[OSDU Cloud Service]({{< relref "cloudservices" >}})
 
 {{% notice info %}}
-<strong>Access to web service: </strong>
-If you are an Equinor employee, make sure you have access to "EDM Landmark" and "EDM Compass".
+<strong>Access to Cloud Data </strong>
+Make sure you have access to "OSDU - Base acces" and "Linux Exclusion Conditional Access".
 {{% /notice %}}
 
-
 ## Well Path Visualization
 
 All the imported well paths are available below the {{< image-in-text src="images/3d-main-window/WellCollection.png" >}} **Wells** item in the **Project Tree**. 
@@ -127,3 +75,51 @@ These can be visualised in the 3D View and Well Log Plots on a [Well Log Track](
 ![]({{< relref "" >}}images/3d-main-window/CasignDesign3D.png) 
 
 ![]({{< relref "" >}}images/3d-main-window/CasignDesignPlot.png)
+
+
+## Ascii Well Paths File Format
+The supported ASCII format is quite flexible but the main requirements are: 
+
+- Each data line must contain four numbers: X Y TVD(MSL) MD(RKB) separated with white-space.
+- Lines starting with `"--" or "#"` is considered to be comment lines
+- A line starting with none-number-characters are used as a well name after the following rules:
+  - If the line contains a pair of : ```  "'", "`", "´", "’" or "‘" ``` the text between the quotation marks is used as a well name.
+  - If the line contains the case insensitive string "name" with an optional ":" after then the rest of the line is used as a well name. 
+  - If there are no quotes or "name"'s, the complete line is used as a well name.
+  - If there are several consecutive name-like lines, only the last one will be used 
+- If a well name is found, a new well is created and the following data points are added to it.
+
+#### Example 1:
+```txt
+WELLNAME: WELL1
+6507.1	725	2542	2590
+6523.5	757	2549	2626.6
+6523.5	760	2559	2637.1
+-999
+WELLNAME: WELL2
+550.7 1020.2  2410   2410
+551   1004.1  2422.2 2430.2
+555.2  993.9  2425   2441.6
+-999
+```
+
+#### Example 2:
+```txt
+X Y TVD(MSL) MD(RKB)
+Name Well_1
+6507.1	725	2542	2542
+6523.5	757	2549	2578.6
+6523.5	760	2559	2589.1
+
+-- A Comment new well
+This is not its name
+Name Well_2
+550.7	1020.2	2410	2520
+551	1004.1	2422.2	2540.2
+# a comment inside the data 
+555.2	993.9	2425	2551.6
+
+3Q AHB-J
+5507.0	4638.5	0.0	0.0
+5507	4638.5	1628.6	1628.6
+```

content/misc/ProjectFile.md

@@ -28,7 +28,3 @@ Editing the **Project File** is one effective way to replace source cases and ot
 </ReferencedExternalFiles>
 ```
 
-
-### The Cache Directory
-
-Statistics calculations, octave generated property sets, and SSI-hub imported well paths are saved to a folder named _`<ProjectFileName>_cache`_ in the same directory as the project file. If you need to move your project, make sure you move this folder along. If you do not, the calculations or well path import needs to be done again.