> For the complete documentation index, see [llms.txt](https://docs.apryse.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.apryse.com/ios/measurement.md). # Measurement - [Measurement Library for iOS](https://docs.apryse.com/ios/measurement/measurement.md): Learn how to create measurement annotations using the UI. Follow these steps to get started and enhance your data analysis. Perfect for beginners! The Apryse iOS SDK streamlines secure document proces - [Customize the PDF Measurement Tool on iOS](https://docs.apryse.com/ios/measurement/measurement-tools-i.md): Learn how to use PDF documents for precise measurements with line, polyline, and polygon annotations. Discover how the Apryse iOS SDK simplifies creating and modifying annotations with built-in tools - [Sample code for measurement tool on iOS](https://docs.apryse.com/ios/measurement/samples.md): Discover a sneak peek of the upcoming iOS measurement sample. Stay tuned for the latest updates and insights. #iOS #MeasurementSample #ComingSoon The Apryse iOS SDK streamlines secure document process - [API to measure area, distance & perimeter on iOS](https://docs.apryse.com/ios/measurement/apis.md): Discover utility classes for measurement on this page. Learn about Distance, PTRulerCreate, Perimeter, PTPerimeterCreate, and Area PTAreaCreate. Optimize your SEO now! The Apryse iOS SDK streamlines s --- # 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.apryse.com/ios/measurement.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.