# Simple features

Builder supports simple features stored as geometry or geography in cloud data warehouses. These simple features are defined as a standard which specifies digital storage of geographical data, usually point, line or polygon, storing both spatial and non-spatial features.

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

This table shows the current type of simple features (`geometry` or `geography`) supported on each data warehouse:

|                | **Geography**  | **Geometry**  |
| -------------- | -------------- | ------------- |
| **BigQuery**   | ✅              | Not Supported |
| **CARTO DW**   | ✅              | Not Supported |
| **Redshift**   | Not Supported  | ✅             |
| **Snowflake**  | ✅              | Not Supported |
| **PostgreSQL** | Not Supported  | ✅             |
| **Databricks** | ✅ WKB Binaries | Not Supported |
| **Oracle**     | Not Supported  | ✅             |

{% hint style="info" %}
When working with simple features in Builder, ensure that your spatial column contains only a single type of geometry—either points, lines, or polygons. Mixing different geometry types within the same spatial column is not supported. To handle multiple geometry types, use separate sources for each type.
{% endhint %}

{% hint style="warning" %}
**GEOMETRYCOLLECTION is not supported**

If your data contains GEOMETRYCOLLECTION geometry types, you'll need to convert them to individual geometry components before visualization. Use the ST\_Dump function in your SQL query to explode geometry collections.
{% endhint %}

## Visualizing simple features

Builder ensures performance experience when rendering simple features on a map as data is loaded progressively via vector tiles. The data for these tiles is extracted by pushing down SQL queries to the data warehouse, and they are requested as you zoom in and out or pan the map.

Note these queries in Builder are cached. To understand more how caching works and different methods to keep your data fleshed, check this link in our [documentation](/carto-user-manual/maps/data-sources/managing-data-freshness.md).

Find more information about performance consideration for this data source type in [this section](/carto-user-manual/maps/performance-considerations.md).


---

# 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/carto-user-manual/maps/data-sources/simple-features.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.