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

# Measurement

- [Measurement Library for UWP](https://docs.apryse.com/uwp/measurement/measurement.md): Learn how to create measurement annotations using the UI. Get started with this step-by-step guide for optimizing your website's performance. The Apryse uwp SDK streamlines secure document processing.
- [Adding measurement tools to viewer in UWP](https://docs.apryse.com/uwp/measurement/measurement-a.md): Measure Distance, Perimeter, and Area accurately with our tools. Set scale for precise measurements in PDFs. Customize units and get instant feedback. The Apryse uwp SDK streamlines secure document pr
- [Sample of measurement tool in UWP](https://docs.apryse.com/uwp/measurement/samples.md): Discover the ViewerControl Sample app showcasing SDK features in a single drag-and-drop control. Explore measurement tools in the annotation toolbar. The Apryse uwp SDK streamlines secure document pro
- [API to measure area, distance & perimeter in UWP](https://docs.apryse.com/uwp/measurement/apis.md): Discover utility classes for measurement on this page. Learn about Distance Ruler, Perimeter, and Area Measurement tools. Enhance your understanding now! The Apryse uwp SDK streamlines secure document


---

# 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/uwp/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.
