# Analytics Toolbox Overview

The CARTO Analytics Toolbox is a suite of functions and procedures to easily enhance the geospatial capabilities available in the different leading cloud data warehouses.

It is currently available for Google BigQuery, Snowflake, Redshift, Databricks and PostgreSQL. Oracle connections are supported for workflows and visualization, but the Analytics Toolbox is not yet available for Oracle.

The Analytics Toolbox contains more than 100 advanced spatial functions, grouped in different modules.

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2Fgit-blob-2838917c104298eb01d675f3ee7baa13bb15ca64%2FCARTO3%20Analytics%20Toolbox%20-%20022023.png?alt=media" alt=""><figcaption></figcaption></figure>

## How does it work <a href="#how-does-it-work" id="how-does-it-work"></a>

Technically speaking, the CARTO Analytics Toolbox is a set of SQL UDFs and Stored Procedures that run natively within each data warehouse, leveraging their computational power and scalability and avoiding the need for time consuming ETL processes.

The functions can be executed directly from the CARTO Workspace or in your cloud data warehouse console and APIs, using SQL commands.

Here’s an example of a query that returns the compact H3 cells for a given region, using Analytics Toolbox functions such as `H3_POLYFILL()` or `H3_COMPACT()` from our H3 module.

Check the documentation for each data warehouse (listed below) for a complete SQL reference, guides, and examples.

```sql
WITH q AS (
  SELECT `carto-un`.carto.H3_COMPACT(
  `carto-un`.carto.H3_POLYFILL(geom,11)) as h3
  FROM `carto-do-public-data.carto.geography_usa_censustract_2019`
  WHERE geoid='36061009900'
) 

SELECT h3 FROM q, UNNEST(h3) as h3
```

{% embed url="<https://clausa.app.carto.com/map/a3417075-1cee-4d06-9dcc-8f350c4abb7d?bearing=270>" %}

{% hint style="info" %}
Some Analytics Toolbox modules (e.g., Location Data Services) require an **AT Gateway** to connect your data warehouse to CARTO's APIs. The gateway deployment differs depending on whether you use CARTO SaaS or Self-Hosted. See [Analytics Toolbox Gateway](https://docs.carto.com/data-and-analysis/analytics-toolbox-gateway) for details.
{% endhint %}

## Supported Data Warehouses <a href="#supported-data-warehouses" id="supported-data-warehouses"></a>

### **Google BigQuery**

Unlock advanced geospatial within Google Cloud. Find more information, guides, and examples here:

* [Analytics Toolbox for BigQuery](https://docs.carto.com/data-and-analysis/analytics-toolbox-for-bigquery)

### **Snowflake**

Get your Snowflake geospatial capabilities to the next level, no matter what cloud you use. Find more information, guides, and examples here:

* [Analytics Toolbox for Snowflake](https://docs.carto.com/data-and-analysis/analytics-toolbox-for-snowflake)

### **Amazon Redshift**

Combine the power of Redshift with the geospatial capabilities of CARTO. Find more information, guides, and examples here:

* [Analytics Toolbox for Redshift](https://docs.carto.com/data-and-analysis/analytics-toolbox-for-redshift)

### **Databricks**

Use CARTO Analytics Toolbox natively in Databricks. Find more information, guides, and examples here:

* [Analytics Toolbox for Databricks](https://docs.carto.com/data-and-analysis/analytics-toolbox-for-databricks)

### **PostgreSQL**

Combine PostGIS with the CARTO Analytics Toolbox in your own PostgreSQL instance. Find more information, guides, and examples here:

* [Analytics Toolbox for PostgreSQL](https://docs.carto.com/data-and-analysis/analytics-toolbox-for-postgresql)


---

# Agent Instructions: 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:

```
GET https://docs.carto.com/data-and-analysis/analytics-toolbox-overview.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.