> For the complete documentation index, see [llms.txt](https://help.fielddoc.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.fielddoc.org/essentials/activities/general-settings/extent.md).

# Extent

Displays the estimated footprint based on the geometry associated with this activity record.

<figure><img src="https://2238918414-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FatQfu0bk7aRHUPp2fz19%2Fuploads%2Fp7LgmjV2kmLIjRm0y8dj%2FScreenshot%202025-03-25%20at%208.28.39%E2%80%AFPM.png?alt=media&amp;token=afc30cd7-06ce-4916-bfa7-8b8d55d10309" alt="" width="563"><figcaption></figcaption></figure>

IN THIS ARTICLE

Review the FieldDoc estimated extent, convert it to different units, or enter your own value.\
Note: These inputs are for reference only and are *not* used in any additional calculations or features.

***

## Extent

This view allows you to input two types of extent:

1. **Estimated Geometric Extent** – Automatically calculated based on the dimensions (area, length, etc.) of the activity’s geometry. Many models and activity types require a unit input tied to geographic extent, so this value is useful to keep with your activity record.
2. **User-Defined Extent** – If your geometry doesn’t include a measurable extent (e.g., a point location), or if the estimate is inaccurate, you can manually enter an extent and select the appropriate unit. This will override the FieldDoc estimated extent, however the system-generated field will remain visible (you cannot delete it).

<table><thead><tr><th width="174.33984375">FieldDoc Field Name</th><th width="181">Import Field Name</th><th width="403.39453125">Description</th></tr></thead><tbody><tr><td>User Defined Extent</td><td>practice:extent</td><td>Enter in a numerical value for the activity record extent.</td></tr><tr><td>Unit</td><td>practice:extent_unit</td><td>Enter in the unit type, such as acres or linear feet.</td></tr></tbody></table>

{% hint style="warning" %}
The Extent fields are not automatically used to calculate most models. To run a model, you must enter in the unit input (which may be the extent available from this page) into the corresponding model input field and then press run.
{% endhint %}


---

# 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://help.fielddoc.org/essentials/activities/general-settings/extent.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.