User Doc: Flip axes Well Paths

Documentation/UsersGuide/GettingStarted.md

@@ -86,6 +86,12 @@ ResInsight supports the follwing type of Eclipse input data:
 2. The case is imported, and a view of the case is created
 3. Right click the **Input Properties** in the generated **Input Case** and use the context menu to import additional Eclipse Property data files.
 
+##### Handling missing or wrong MAPAXES
+
+The X and Y grid data can be negated in order to make the Grid model appear correctly in ResInsight. This functionality is accessible in the **Property Editor** for all Case types as the toggle buttons **Flip X Axis** and **Flip Y Axis** as shown in the example below.
+ 
+![](images/Caseproperties.png)
+
 
 ### Model navigation 
 

Documentation/UsersGuide/UsersGuide.md

@@ -18,9 +18,9 @@ can also export modified cell property data sets to single Eclipse input files.
 
 - [ Getting Started ](GettingStarted.md)
 - [ Working with 3D Views ](ReservoirViews.md)
-- [ *Todo:* Well paths ]()
 - [ Multiple realizations and statistics ](CaseGroupsAndStatistics.md)
 - [ Octave Interface](OctaveInterface.md)
+- [ Well Trajectories ](WellTrajectories.md)
 
 ### Appendix
 

Documentation/UsersGuide/WellPaths.md

@@ -0,0 +1,69 @@
+## Well trajectories
+
+ResInsight can import Well trajectories from simple Ascii files. 
+In addition a Statoil specific solution to retreive Well Trajectories from their internal web service are implemented.
+
+### Ascii Well Trajectories
+
+The command **File -> Import -> Import Well Paths From File** will read the well paths in the selected file, and create one entry for each trajectory under the  ![](images/WellCollection.png) **Wells** item in the **Project Tree**. 
+
+The supported ascii format is quite flexible but the main requirements are: 
+
+1. Each data line must contain four numbers: X Y TVD MD separated with witespace.
+2. A line starting with none-number-characters are ignored, unless :
+	1. If the line contains a pair of : ', `, ´, ’ or ‘ the text between the quotation marks is used as a well name.
+	2. If the line contains the case insensitive string "name " the rest of the line is used as a well name. 
+3. If a wellname is found, a new well is created and the following datapoints ends up in it.
+
+###### Example 1:
+
+	WELLNAME: ‘WELL1’
+    4507.0	5638.5	0.0	0.0
+    4507	5638.5	4628.6	1628.6
+	4297.4	5938.5	4632.4	1998.387
+    -999
+    WELLNAME: ‘WELL2’
+	5507.0	4638.5	0.0	0.0
+    5507	4638.5	3628.6	1628.6
+    5297.4	4938.5	3632.4	1998.387
+	-999
+
+###### Example 2:
+    X Y TVD MD
+    Name Well_1
+  	5507.0	4638.5	0.0	0.0
+    5507	4638.5	3628.6	1628.6
+    5297.4	4938.5	3632.4	1998.387
+
+    Name Well_2
+  	5507.0	4638.5	0.0	0.0
+    5507	4638.5	3628.6	1628.6
+    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.  
+
+### Importing from SSI-Hub (Internal Statoil web-service)
+
+The command **File -> Import -> Import Well Paths From SSI-hub** launch a wizard to guide you through the process of selecting the well trajectories you need.
+
+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.
+
+### Well Trajectory visualization
+
+All the imported well trajectories are available below the ![](images/WellCollection.png) **Wells** item in the **Project Tree**. 
+
+![](images/WellsInTree.png)
+
+The visible wells are always shown in all the 3D Views in the complete project, so the toggles and settings controls the overall project visibility of the Well Trajectories. The **Property Editor** of the **Wells** item is shown below 
+
+![](images/WellPathCollectionProperties.png)
+
+- **Global well path visibility** This option forces the wellpaths on or off, ignoring the individual settings unless it is set to Individual.
+- **Clip Well Paths** This option hides the top of the Well Trajectories to avoid displaying the very long lines from the reservoir to the sea surface.
+- **Well Path clipping depth distance** This number is the distance from the top of the reservoir to the clipping depth.
+
+
+