# General FAQ

- [Accuracy Standards & Quantification](/general-faq/accuracy-standards-and-quantification.md): The common criteria used to evaluate the accuracy of a dataset or system and Phoenix LiDAR's standardized post processing methods for making statements about data quality.
- [Precision](/general-faq/accuracy-standards-and-quantification/precision.md)
- [Relative Accuracy](/general-faq/accuracy-standards-and-quantification/relative-accuracy.md)
- [Absolute Accuracy](/general-faq/accuracy-standards-and-quantification/absolute-accuracy.md)
- [Further Considerations](/general-faq/accuracy-standards-and-quantification/further-considerations.md)
- [Mapping Terms and Definitions](/general-faq/common-terms-and-definitions.md)
- [Abbreviations](/general-faq/abbreviations.md)
- [Examples: How to ensure accurate Georeferencing of Trajectories and Pointclouds](/general-faq/examples-how-to-ensure-accurate-georeferencing-of-trajectories-and-pointclouds.md)
- [Example 1: Static Datum](/general-faq/examples-how-to-ensure-accurate-georeferencing-of-trajectories-and-pointclouds/example-1-static-datum.md)
- [Example 2: Dynamic Datum](/general-faq/examples-how-to-ensure-accurate-georeferencing-of-trajectories-and-pointclouds/example-2-dynamic-datum.md)
- [Clock bias adjustment](/general-faq/clock-bias-adjustment.md): Timing offsets or clock biases between the navigation system and LiDAR scanner can produce incorrect georeferencing of point clouds, often resulting in a "wavy" pattern between scanlines.
- [General FAQs](/general-faq/frequently-asked-questions.md): General: Frequently Asked Questions