> For the complete documentation index, see [llms.txt](https://docs.carto.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.carto.com/data-and-analysis/analytics-toolbox-for-redshift/key-concepts.md).

# Key concepts

There are a few concepts that are repeated throughout the different Analytics Toolbox modules and functions, and that are unique to geospatial analytics. In this section of our documentation you will find some articles to introduce you to some of those key concepts.

* **Tilesets:** tilesets are a method to progressively load data for the visualization of large-scale datasets in a map. The [tiler](/data-and-analysis/analytics-toolbox-for-redshift/sql-reference/tiler.md) module allows you to create tilesets out of your data.\
  \
  Learn more about tilesets in the following [subsection](/data-and-analysis/analytics-toolbox-for-redshift/key-concepts/tilesets.md).

<figure><img src="/files/QCw2XcyxwS08XD8y9y4K" alt=""><figcaption></figcaption></figure>

* **Spatial Indexes:** spatial indexes are systems that provide a relationship between geospatial data and a hierarchical grid systems, represented by geospatial indexes. There are huge performance and scalability benefits of aggregating data using spatial indexes. The most common spatial indexes libraries are [Quadbin](/data-and-analysis/analytics-toolbox-for-redshift/sql-reference/quadbin.md), H3, and [S2](/data-and-analysis/analytics-toolbox-for-redshift/sql-reference/s2.md), which CARTO supports with different modules in the Analytics Toolbox.\
  \
  Learn more about spatial indexes in the following [subsection](/data-and-analysis/analytics-toolbox-for-redshift/key-concepts/spatial-indexes.md).

<figure><img src="/files/KHjYoSyovCdUAXArnb6I" alt=""><figcaption></figcaption></figure>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.carto.com/data-and-analysis/analytics-toolbox-for-redshift/key-concepts.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.