> 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/xamarin/measurement.md).

# Measurement

- [PDF measurement library for Xamarin](https://docs.apryse.com/xamarin/measurement/measurement.md): Learn how to create measurement annotations using the UI. Get started with this step-by-step guide. Enhance your data analysis today! The Apryse Xamarin SDK streamlines secure, serverless document pro
- [Measurement](https://docs.apryse.com/xamarin/measurement/measurement-tools.md): Learn how to customize PDF measurement tools in Android and iOS using Apryse SDK. Create distance, perimeter, and area annotations with precision. Find out more here! The Apryse Xamarin SDK streamline
- [Samples for measuring PDFs in Xamarin](https://docs.apryse.com/xamarin/measurement/samples.md): Discover Xamarin.Android and Xamarin.iOS showcase sample apps demonstrating SDK features. Explore the measurement demo in the Annotation section. Start building with Xamarin today! The Apryse Xamarin
- [API for PDF Measurement in Xamarin](https://docs.apryse.com/xamarin/measurement/apis.md): Discover utility classes for measurement in Xamarin.Android and Xamarin.iOS using C#. Learn about Distance, Perimeter, and Area tools with pdftron.PDF.Tools. Optimize your app development now! The Apr


---

# 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/xamarin/measurement.md?ask=<question>&goal=<user_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.
