> For the complete documentation index, see [llms.txt](https://docs.innova-drilling.com/introduction/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.innova-drilling.com/introduction/legacy-documentation/manuals/well-seeker-pro-1/9.0-survey-view.md).

# 9.0 - Survey View

![Figure 170: Survey View](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Finnova-engineering-how-to-guides%2F-MhXkYZ7PdExlYiiIyCZ%2F-MhXlDv3QQuFYB7SpbgW%2F0.png?generation=1629449679013611\&alt=media)

The survey view allows the user to enter survey data into survey files and is accessible by double clicking on a survey file from the database viewer (above Left). The tie-on line for the survey is not editable from the grid and can only be changed in the survey properties dialog. Enter MD INC and AZI and all other parameters will be calculated.

If an actual or planned wellbore is being viewed, **surveys are not editable** (above right).

The distance, Up Down, Left Right, TC X, TC Y, TFO HS, TFO + Azi and BR to Land columns will only be populated if a **principal plan** is present. The BR to Land column data can be overridden if the Force Landing option is selected in the Actual Wellbore Properties. The proximity calculations are performed using the scan method specified at operator level.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.innova-drilling.com/introduction/legacy-documentation/manuals/well-seeker-pro-1/9.0-survey-view.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.