From 11b9c406079e51062c28d27765fabeb16fd19f0a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jacob=20St=C3=B8ren?= Date: Thu, 24 Oct 2013 14:45:14 +0200 Subject: [PATCH] User Doc : Well Paths --- Documentation/UsersGuide/WellPaths.md | 4 ++-- TestModels/Documenetation_wellpaths/fields.json | 0 2 files changed, 2 insertions(+), 2 deletions(-) create mode 100644 TestModels/Documenetation_wellpaths/fields.json diff --git a/Documentation/UsersGuide/WellPaths.md b/Documentation/UsersGuide/WellPaths.md index f9b214d578..a4258f4934 100644 --- a/Documentation/UsersGuide/WellPaths.md +++ b/Documentation/UsersGuide/WellPaths.md @@ -41,7 +41,7 @@ The supported ascii format is quite flexible but the main requirements are: 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) @@ -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**. -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 _wellpaths in the same directory as your project file. ### Well Trajectory visualization diff --git a/TestModels/Documenetation_wellpaths/fields.json b/TestModels/Documenetation_wellpaths/fields.json new file mode 100644 index 0000000000..e69de29bb2