> 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/developers/paramml-developer-guide/core-objects/3d-geometric-objects/point.md).
# Point
To describe a point, its position in space is indicated by its X, Y, and Z values.
**Syntax:**
```
```
| **Name and Type Attributes** | **Label** | **Mandatory** | **Default Description and Value Attributes** | **Other Attributes** |
| ---------------------------- | --------- | ------------- | ---------------------------------------------------------------------------------- | ------------------------ |
| N="C" | Chamfer | No | D="Chamfer: length of the chamfer." V="0" | UT="Length" UC="Section" |
| N="R" | Radius | No | D="Radius: radius of the curve." V="0" | UT="Length" UC="Section" |
| N=" AlignTB " | AlignTB | No | D="AlignTB: Break transversely for alignment cross-Section? \[Yes=1/No=0] ." V="0" | UT="None" UC="Section" |
**Example:**
```xml
```
When using "R" and "C" parameters, ensure that all of them arranges the points in a specific order. To create a curved path between two points, the "radius" parameter should be added, and for a beveled edge, the "Chamfer" parameter should be added.
A line object has been added to reference the points with X=0 and Y=0.  To view this example in the library, see ()
**Example:**
```xml
```
 To view this example in the library, see ()
**Example:**
```xml
```
 To view this example in the library, see ()
---
# 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/developers/paramml-developer-guide/core-objects/3d-geometric-objects/point.md?ask=&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.