> 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-databricks/reference/legacy.md).
# Legacy (Deprecated)
{% hint style="danger" %}
**This documentation is for the legacy JAR-based Analytics Toolbox.** These functions require cluster-based installation with Apache Sedona and are not available in the SQL Warehouse approach.
For new installations, please use the [SQL Warehouse installation](/data-and-analysis/analytics-toolbox-for-databricks/getting-access/sql-warehouse.md) which provides LDS functions via Unity Catalog.
{% endhint %}
The CARTO Analytics Toolbox's functions are organized in modules based on the functionality they offer. On this page you will find the full list with direct links to their definition.
| Module | Function or Procedure |
| ------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| lds | GEOCODE\_TABLE
GEOCODE\_REVERSE\_TABLE
CREATE\_ISOLINES
CREATE\_ROUTES
GEOCODE
GEOCODE\_REVERSE
ISOLINE
GET\_LDS\_QUOTA\_INFO
CREATE\_ROUTING\_MATRIX
|
| tiler | CREATE\_VECTOR\_TILESET
CREATE\_POINT\_AGG\_TILESET
CREATE\_H3\_AGG\_TILESET
CREATE\_QUADBIN\_AGG\_TILESET
|
### Apache Sedona
The CARTO Analytics Toolbox for Databricks includes [Apache Sedona](https://sedona.apache.org/1.5.1/) and makes all functions from "Sedona with Apache Spark" available in your Databricks all-purpose compute cluster.
The current version included is `1.5.1` and you can find the complete reference [here](https://sedona.apache.org/1.5.1/api/sql/Overview/).
All functions should be used with the prefix `sedona_` , for example:
```sql
SELECT sedona_ST_Point(double(1.2345), 2.3456)
-- OUTPUT: POINT (1.2345 2.3456)
```
---
# 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://docs.carto.com/data-and-analysis/analytics-toolbox-for-databricks/reference/legacy.md?ask=&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.