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  **Wells** item in the **Project Tree**.
The supported ascii format is quite flexible but the main requirements are:
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)
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  **Wells** item in the **Project Tree**.
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.
All the imported well trajectories are available below the  **Wells** item in the **Project Tree**.
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
- **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.
