OilfieldToolsNet/ResInsight
4
0
Fork 0
mirror of https://github.com/OPM/ResInsight.git synced 2024-12-29 10:21:54 -06:00
Code Issues Packages Projects Releases Wiki Activity

User Doc : Well Paths

Browse Source
This commit is contained in:
Jacob Støren 2013-10-24 14:45:14 +02:00
parent 2d8ca974f9
commit 11b9c40607
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
Documentation/UsersGuide/WellPaths.md
View File

@ -41,7 +41,7 @@ The supported ascii format is quite flexible but the main requirements are:
5297.4 4938.5 3632.4 1998.387 5297.4 4938.5 3632.4 1998.387
The trajectory data is not copied into the ResInsight project as such. The project file only stores the file patht, and the next time you open the project, ResInsight will try to read the well data from the file again. The trajectory 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.
### Importing from SSI-Hub (Internal Statoil web-service) ### Importing from SSI-Hub (Internal Statoil web-service)
@ -49,7 +49,7 @@ The command **File -> Import -> Import Well Paths From SSI-hub** launch a wizard
After completing the wizard, the wells imported are accessible as Items under the ![](images/WellCollection.png) **Wells** item in the **Project Tree**. After completing the wizard, the wells imported are accessible as Items under the ![](images/WellCollection.png) **Wells** item in the **Project Tree**.
The trajectory data is not copied into the ResInsight project as such. The trajectory 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.
### Well Trajectory visualization ### Well Trajectory visualization

0
TestModels/Documenetation_wellpaths/fields.json Normal file
View File