> For the complete documentation index, see [llms.txt](https://enercalc.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://enercalc.com/docs/e3d-user-manual/interface/toc175916526/input-data/toc161393915.md).

# Line Loads

How to enter member line loads in a spreadsheet using Tables Line Loads.

Tables > Line Loads prompts you with the following dialog.

![](https://560001759-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWNe8U6EBBBdUJHdb2X9G%2Fuploads%2Fgit-blob-518410eccad654442c1529a5f589bce920baedf8%2FFASTFR~1_img156.png?alt=media)

It allows you to enter member line loads in a spreadsheet. Each line load includes the member ID, the load coordinate system, direction, start and end magnitudes, and the start and end distances. The load is a force in the local or global X, Y, Z directions. The load distances are the ratio of load start and end locations (measured from the start of the member) to the member length. The member ID must be valid (defined).

An empty row is allowed if all rows below it are empty. Selected rows (whole row must be selected) may be cut by clicking the button “Cut Selected Rows”.


---

# 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://enercalc.com/docs/e3d-user-manual/interface/toc175916526/input-data/toc161393915.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.
