> 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/js-sdk-api-reference/layers/valueconfiguration.md).

# ValueConfiguration

***

Configuration for filtering and aggregating values across features.

This can be used to restrict the features considered for aggregation via the `boundary`\
and `filters` properties.

It can also be used to specify how to aggregate the values via the `aggregation` property.

## Properties

### boundary?

> `optional` **boundary**: [`GeometryFilter`](/js-sdk-api-reference/layers/geometryfilter.md)

The spatial boundary for what to count or aggregate.

***

### filters?

> `optional` **filters**: [`Filters`](/js-sdk-api-reference/layers/filters.md)

Attribute filters to determine what gets counted or aggregated.

***

### aggregation?

> `optional` **aggregation**: [`AggregationConfig`](/js-sdk-api-reference/layers/aggregationconfig.md)

Specifies how to aggregate values within each category or bin. When omitted,\
features are counted. When specified, the chosen calculation (avg, sum, etc.)\
is performed on the specified attribute.

For example, instead of counting buildings in each category, you might want\
to sum their square footage or average their assessed values.


---

# 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/js-sdk-api-reference/layers/valueconfiguration.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.