> 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/data-acquisition-and-uav-piloting/navigation-and-alignment-techniques/real-time-and-post-processing-differences.md).
# Real-Time and Post-Processing Differences
## Alignment During Post Processing
Alignment in post-processing softwares is essentially the same as with the real-time INS. A notable difference is that post-processing softwares can process in the forward time direction (moving forward through the data, as it was collected in real-time) AND in the reverse time direction (moving backwards through the data, opposite to how it was collected in real-time). Forward and reverse processing solutions can then be combined, and their combined result is better than if just one processing direction was used. Thus you will notice on the flight plan diagram shown above that there are kinematic alignment maneuvers performed at the beginning and end of the flight:
This ensures both processing directions have a proper kinematic alignment maneuver at the "beginning" of processing, however the real-time INS solution does not improve with the addition of an alignment maneuver at the end of the flight.
## Forward and Reverse Processing
The larger implication of forward/reverse processing capabilities is that all INS initialization processes (static period, alignment, figure eights) should be performed at the beginning and at the end of the flight, thus missions begin to take on a symmetrical pattern:
1. Static period
2. Kinematic alignment
3. Figure eights
4. Mapping mission
5. Figure eights
6. Kinematic alignment
7. Static period.
---
# 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/data-acquisition-and-uav-piloting/navigation-and-alignment-techniques/real-time-and-post-processing-differences.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.