> For the complete documentation index, see [llms.txt](https://gitbook.saf.guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gitbook.saf.guide/structural-analysis-elements/structuralstorey.md).
# StructuralStorey
## Storey, Floor levels...
StructuralStorey object describes definition of floor levels/storeys in structural model.
### Specification in the excel
| Name of the column header | Type of data | Value example or enum definition | Required value | Description |
| ------------------------- | ------------ | :----------------------------------: | -------------- | ------------------------------------------------------------------------------------------------------------------------ |
| Name | String | FL1 | yes | Human readable unique name of the Arbitrary definition |
| Height level \[m] | Double | -2.000 | yes | Height level \[m] or \[m] of the floor.
Zero height level refers to horizontal plane of GCS (mostly XY plane).
|
| Id | String | 39f238a5-01d0-45cf-a2eb-958170fd4f39 | no | Unique attribute designation |
---
# 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://gitbook.saf.guide/structural-analysis-elements/structuralstorey.md?ask=&goal=
```
`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.