> For the complete documentation index, see [llms.txt](https://technical.geometrygym.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://technical.geometrygym.com/rhino-grasshopper/structuralanalysis/geometry-gym-model/common-attributes/1d-elements-curve.md).

# 1D Elements (Curve)

## Curve Elements

A curve element can take the nature of many different elements in reality such as a structural beam, cable or structural link. However for Geometry Gym they are generally stored within a single 'curve element' list with attributed defined

Structural analysis programs generally define the nature of a curve element in one of two ways:

* Define its type within attributes of a beam element
* Define it as a completely separate element with different

If the program defines these elements separately then the plug-in will generally have separate create element creation components for each. For example **`ggGSACreateBeam`**, **`ggGSACreateCable`**, **`ggGSACreateLink.`** If not than a member type will be defined in the beam attributes of the component.

### Beam Elements

**`gg###CreateBeam`**

#### Property

#### Node Node or Centreline

#### Orientation

#### Angle

#### Attributes

###

### Link Elements

Link elements work in a similar way to beam elements however, do not have any physical representation and typically provide a rigid connection between 2 nodes.

### Cable Elements

## Working with Curve Elements

Create a simple beam

## Curve Element Utilities

### Decompose Beam

**`gg###DecomposeBeam`**

The decompose beam component allow you to deconstruct the attributes of a curve element. By inputting the beam element you can explode out the property, centre line, node points, orientation, Name and ID of the element to be used down stream.

This is extremely helpful when importing a model.


---

# 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://technical.geometrygym.com/rhino-grasshopper/structuralanalysis/geometry-gym-model/common-attributes/1d-elements-curve.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.