> For the complete documentation index, see [llms.txt](https://docs.phoenixlidar.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.phoenixlidar.com/hardware-and-interfaces/gnss/orientation-and-offsets.md). # Orientation and Offsets In order to produce accurate data, the rover needs to know the position and orientation of all attached sensors. These sensors include the IMU as well as a combination of one or multiple GNSS antennas, LiDAR sensors and cameras. In this section, the terms offset and translation will be used as synonyms. However, the terms rotation and orientation are not the same; a sequence of rotations around different axes leads to an orientation. For every orientation, there is an infinite number of sets of rotations that leads to that orientation. Generally, a sensor will be mounted, translated, and then rotated relative to the IMU. When the terms “translation” and “rotation” are used together, they form a “transform”. The system’s frame of reference is the IMU (which is why the reference point in the IMU is named the “center of navigation”). The offsets for all sensors are specified as offsets from the IMU to the sensor, not the other way around (sensor to IMU). However, the axis definitions used differ by sensor type. The rotations for all sensors are specified using different conventions depending on the sensor type. When mounting the rover to a vehicle, it is important to have an idea of the vehicle’s forward and up directions. While some vehicles, e.g. multirotors, don’t enforce a forward-direction, navigation systems do, so even a multirotor needs to be flown like a fixed-wing aircraft (aside from takeoff and landing). --- # 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://docs.phoenixlidar.com/hardware-and-interfaces/gnss/orientation-and-offsets.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.