> For the complete documentation index, see [llms.txt](https://developers.felt.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.felt.com/felt-style-language/style-definition-blocks/the-attributes-block.md).

# The attributes block

The attributes block contains information on how attributes will be shown both on the popup and the table. Each attribute definition can contain the following properties:

<table><thead><tr><th width="191">Field name</th><th>Description</th></tr></thead><tbody><tr><td><code>displayName</code></td><td>Optional. How this attribute will be shown in different parts of the Felt UI.</td></tr><tr><td><code>format</code></td><td>Optional. A <a href="https://numbrojs.com/">numbro</a> object that encodes how numeric fields should be shown.</td></tr></tbody></table>

{% code title="Example of an attributes block" %}

```json
"attributes": {
  "faa": {
    "displayName": "FAA Code",
    "format": {
      "mantissa": 0,
      "thousandSeparated": true
    }
  },
  "wikipedia": {"displayName": "Wikipedia"}
}
```

{% endcode %}

## The `format` object

`format` accepts any valid [numbro format object](https://numbrojs.com/format.html) — common keys include `mantissa` (decimal places), `thousandSeparated`, `average` (compact notation like `1.2M`), `output` (`"percent"`, `"currency"`), and `prefix`/`postfix`. The object is validated by numbro itself, so anything numbro accepts is valid.

Felt adds one extra key on top of numbro: `unit`, for displaying measurements. Supported values: `meter`, `kilometer`, `foot`, `mile`, `square_meter`, `hectare`, `square_kilometer`, `square_foot`, `acre`, `square_mile`, and the adaptive `auto-distance` and `auto-area`.

```json
"attributes": {
  "parcel_area": {
    "displayName": "Parcel area",
    "format": {"mantissa": 1, "unit": "auto-area"}
  }
}
```


---

# 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://developers.felt.com/felt-style-language/style-definition-blocks/the-attributes-block.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.