> 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/general-faq/examples-how-to-ensure-accurate-georeferencing-of-trajectories-and-pointclouds.md).

# Examples: How to ensure accurate Georeferencing of Trajectories and Pointclouds

There are a few steps within the post processing workflow where you will be prompted to select some form of [georeferencing](https://docs.phoenixlidar.com/common-terms-and-definitions#georeferencing) ([datum](https://docs.phoenixlidar.com/common-terms-and-definitions#datum), [epoch](https://docs.phoenixlidar.com/common-terms-and-definitions#epoch), [horizontal](https://docs.phoenixlidar.com/common-terms-and-definitions#horizontal-datum) [CRS](https://docs.phoenixlidar.com/common-terms-and-definitions#coordinate-reference-system-crs), [Vertical](https://docs.phoenixlidar.com/common-terms-and-definitions#vertical-datum) [CRS](https://docs.phoenixlidar.com/common-terms-and-definitions#coordinate-reference-system-crs), etc.).

It is critical to the absolute accuracy of your post processed data products that this information is correct.

These steps include:

**Project File - Spatial Explorer / LiDARMill**

* Project CRS 
  * Datum and epoch
* Import GCPs 
  * Horizontal CRS, Vertical CRS, Epoch

**Trajectory Processing - Inertial Explorer / Navlab**

* Input Refined Reference Station Coordinates during trajectory processing
  * Position, Datum, and Epoch
* Output trajectory
  * Datum

**LiDAR Export - Spatial Explorer / LiDARMill**

* Export LAS/LAZ 
  * Horizontal CRS, Vertical CRS, Epoch