> For the complete documentation index, see [llms.txt](https://help.felt.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.felt.com/upload-anything/data-sources/stac.md).

# STAC

Connect a SpatioTemporal Asset Catalog (STAC) or STAC API to Felt. Configure credentials for the catalog and its linked assets.

{% hint style="success" %}
Available on the Business and Enterprise plans. [Compare plans](https://felt.com/pricing#compare)
{% endhint %}

A SpatioTemporal Asset Catalog (STAC) describes geospatial files, such as satellite imagery. Connect a static catalog in JSON or a dynamic STAC API to find those files and add them to maps. Felt streams Cloud Optimized GeoTIFF (COG) assets without copying them. See the [STAC specification](https://stacspec.org/en) and [Stream large rasters](/upload-anything/stream-large-rasters.md).

## Connect STAC

Follow the steps in [Add a source](/upload-anything/data-sources/add-a-source.md#connect-a-source), select **STAC**, and in **Connection**, enter the **URL** of your STAC catalog or API. If the catalog or its assets are private, add [credentials](#credentials):

* If the catalog or API needs authentication, select a type in **API authentication** and fill in its fields.
* If the assets need their own credentials, click **Add credential** in **Asset credentials**, select an **Asset authentication** type, and fill in its fields. Repeat for each set of credentials.

## Credentials

A STAC source can have one credential for the catalog or API and any number of credentials for the assets its [items](https://github.com/radiantearth/stac-spec/blob/master/item-spec/item-spec.md) link to. For example, a public STAC API can point to private assets in Amazon S3. API authentication and asset authentication offer the same types. Felt doesn't match asset credentials to buckets: for each asset, it tries the asset credentials in turn and uses the first one that works.

| Type                     | Use it for                                                         | What to enter                                                                                                                                                                      |
| ------------------------ | ------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| None (public)            | A catalog or assets that need no credentials. This is the default. | Nothing                                                                                                                                                                            |
| AWS Assume Role          | Assets in Amazon S3                                                | A Role ARN and a Role session name. Set up the role as for [an Amazon S3 source](/upload-anything/data-sources/amazon-s3.md#credentials).                                          |
| Azure Connection String  | Assets in Azure Blob Storage                                       | A connection string with a Read and List SAS. See [Azure Blob Storage credentials](/upload-anything/data-sources/azure-blob-storage.md#credentials).                               |
| Custom Headers           | A catalog or server that takes a header, such as a bearer token    | A Header name and a Value for each header, such as `Authorization` and `Bearer {YOUR_AUTH_TOKEN}`. Felt adds them to every request and hides the value after you save.             |
| GCP Service Account JSON | Assets in Google Cloud Storage                                     | The JSON key for a service account with the Storage Object Viewer role. See [Google Cloud Storage credentials](/upload-anything/data-sources/google-cloud-storage.md#credentials). |


---

# 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://help.felt.com/upload-anything/data-sources/stac.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.