> 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/android/measurement.md). # Measurement - [Measurement Library for Android](https://docs.apryse.com/android/measurement/measurement.md): Discover how to create measurement annotations using the UI. Learn how to get started with this essential feature for tracking and analyzing data effectively. The Apryse Android SDK streamlines secure - [Add PDF Measurement Tools in Android](https://docs.apryse.com/android/measurement/measurement-a.md): Learn how to create and edit measurement annotations in PDFs using the DocumentActivity and PdfViewCtrlTabHostFragment2 components. Find out how to configure ToolManager and use different measurement - [Sample of measurement tool in Android](https://docs.apryse.com/android/measurement/samples.md): Discover the features of the SDK with a measurement demo in the sample app showcase. Explore the Annotation section to see it in action! The Apryse Android SDK streamlines secure document processing a - [API to measure area, distance & perimeter in Android](https://docs.apryse.com/android/measurement/apis.md): Discover utility classes for measurement on this page. Learn about Distance Ruler, Perimeter, and Area Measurement tools. Optimize your measurements efficiently. The Apryse Android SDK streamlines sec --- # 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/android/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.