> For the complete documentation index, see [llms.txt](https://help.besmart.software/be.smart-site-management/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.besmart.software/be.smart-site-management/site-management/section-tool.md).

# Section tool

There are three types of sections available; freehand, perpendicular and longitudinal section. It is possible to view LandXML and Inframodel surfaces, pipenetworks and points in the free and cross section. The section tool also supports geonic files. Long section supports only surfaces. 

All the sections have same measurement tools; distance, area and slope. 

The example from cross section displays all the different elements supported in the view. It is possible to query metadata from objects within the cross section. In the example a pipe metadata has been queried and displayed.

<figure><img src="/files/DbarmUiV8d0pmIXTkzM6" alt=""><figcaption><p>Example of a perpendicular section</p></figcaption></figure>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.besmart.software/be.smart-site-management/site-management/section-tool.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.