> For the complete documentation index, see [llms.txt](https://guardian.hedera.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guardian.hedera.com/docs/develop/guardian/workspace/schemas/schema-fields-reference.md).

# Schema Fields Reference

Schema fields define the data a document can collect and validate. Select a type from the field picker or drag it into the schema.

### Simple types

| Field type       | Use it for                                             |
| ---------------- | ------------------------------------------------------ |
| **Number**       | Numeric values, including decimals.                    |
| **Integer**      | Whole numbers, including negative values.              |
| **String**       | Plain text.                                            |
| **Boolean**      | A `true` or `false` value.                             |
| **Date**         | A calendar date.                                       |
| **Time**         | A time of day.                                         |
| **DateTime**     | A date and time together.                              |
| **Duration**     | A period, such as `P1D` or `P2W`.                      |
| **URL**          | A web address.                                         |
| **URI**          | A resource identifier, including IPFS links.           |
| **Email**        | An email address.                                      |
| **Image**        | An uploaded image.                                     |
| **File**         | An uploaded file.                                      |
| **Enum**         | One value from a defined list.                         |
| **Help Text**    | Instructions or guidance within a form.                |
| **GeoJSON**      | Geographic points, lines, and polygons.                |
| **Sentinel Hub** | Geographic raster-imagery coordinates and date ranges. |
| **Table**        | CSV-based tabular data.                                |
| **Rich Text**    | Formatted long-form text.                              |

### Geographic types

Use these fields for standardized location values:

| Field type         | Use it for               |
| ------------------ | ------------------------ |
| **Continent**      | A continent.             |
| **Country**        | An ISO 3166 country.     |
| **State/Province** | An ISO 3166 subdivision. |

Geographic fields can be linked into a cascading group. Selecting a parent filters compatible child values.

### Units of measure

| Field type  | Use it for                           |
| ----------- | ------------------------------------ |
| **Prefix**  | A fixed unit before a numeric value. |
| **Postfix** | A fixed unit after a numeric value.  |

### Hedera and schema types

| Field type     | Use it for                                 |
| -------------- | ------------------------------------------ |
| **Account**    | A Hedera account reference.                |
| **Sub-schema** | A nested object defined by another schema. |

### Configure a field

For each field, define its name, description, and type. You can also:

* Mark the field as required, hidden, or optional.
* Allow multiple answers when the field accepts a list.
* Set default, suggested, and test values.
* Map the field to an IWA dMRV property.

Use **Conditions** to show fields based on other answers. Use **Repeatable links** for repeating related data.

{% hint style="info" %}
Choose the most specific field type available. It improves validation and data consistency.
{% 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://guardian.hedera.com/docs/develop/guardian/workspace/schemas/schema-fields-reference.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.