> For the complete documentation index, see [llms.txt](https://docs.roomle.com/rubens/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.roomle.com/rubens/content-creation/roomlescript-reference/coordinatesystems.md).
# Coordinate Systems
.png?alt=media)
(a) Left handed coordinate system\
(b) Right handed coordinate system
[wiki - Right-hand rule](https://en.wikipedia.org/wiki/Right-hand_rule)
## Input coordinate system
### Roomle Script Coordinate System
The coordinate system for the component definitions JSON and the configuration JSON is a left handed coordinate system.
```json
{
"id": "catalog_id:coordinate_system",
"geometry": "
AddPrism(1000, Vector2f[{0, 0}, {2000, 0}, {0, 1000}]);
SetObjSurface('roomle_script_test:yellow');
"
}
```
.png?alt=media)
### Plan XML Coordinate System
Left handed coordinate system
```xml
```
.png?alt=media)
#### Object position in PlanXML
Left handed coordinate system
.png?alt=media)
## Internal Roomle Core Coordinate System
### Configurator
Right handed coordinate system
.png?alt=media)
This is also the coordinate system of all the meshes generated by the Configurator
### Planner
Right handed coordinate system
.png?alt=media)
## External Mesh Coordinate System
Right handed coordinate system
```none
o Prism
v 0 0 0
v 2000 0 0
v 0 -1000 0
v 0 0 1000
v 2000 0 1000
v 0 -1000 1000
f 1 2 3
f 4 6 5
f 1 3 6
f 1 6 4
f 2 1 4
f 2 4 5
f 3 2 5
f 3 5 6
```
.png?alt=media)
## API Coordinate System
The API coordinate system is a right handed coordinate system and the same as the internal Roomle Core coordinate system.
* Configurator API
* Positions and rotations: Right handed, internal Roomle Core coordinate system
* Meshes: Right handed, internal Roomle Core coordinate system
* Planner API
* Object positions: Right handed, internal Roomle Core coordinate system
* Meshes: Right handed, internal Roomle Core coordinate system
---
# 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.roomle.com/rubens/content-creation/roomlescript-reference/coordinatesystems.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.