> For the complete documentation index, see [llms.txt](https://docs.openbrim.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openbrim.org/templates/retaining-wall-workflow/external-references-rw/imported-data-rw.md).

# Imported Data \[RW]

Data that was authored in another system and brought into the project: a survey surface exported from a civil design package, for example.

This is a different kind of reference from the rest of **External References**. The Project 3D, Project Objects and Project Analysis Results items point at another OpenBrIM project and stay linked to it, so the master model remains the source of truth. Imported data is brought in once: the project keeps its own copy along with the file it came from, so it travels with the project and does not depend on the machine it was imported on.

**Digital Terrain Model**

* The existing ground surface, imported from a LandXML TIN. It is what a vertical clearance is measured up from, so a **Clearance Zone** under **Geometric Criteria** normally names the terrain as its floor.
* Set the project's geographic coordinate system before importing a surface, or the imported points cannot be placed. The coordinate system and the background map are both view settings, reached from the Project Site window rather than modelled as objects.


---

# 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.openbrim.org/templates/retaining-wall-workflow/external-references-rw/imported-data-rw.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.