> 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/global-library.md).

# Global Library

Add curated public datasets from Felt's Global Library. Find boundaries, demographics, flood risk, roads, and more.

The Global Library has curated public datasets you can add to any map. Click **Data sources** in the center of the toolbar at the top of the map, open **Global Library**, and search by keyword, such as `flood` or `ZIP`.

## Add a Global Library layer to a map

1. On the map, click **Data sources** in the toolbar.
2. Click **Global Library** in the dialog's sidebar.
3. Browse by topic, or search for a dataset.
4. Select a dataset to preview it in the **Map**, **Table**, and **Metadata** tabs.
5. Click **Add to map**. The layer appears on the map and in the legend.

## What's in the Global Library

The Global Library's datasets are grouped by topic:

| Topic              | Examples                                                                                                           |
| ------------------ | ------------------------------------------------------------------------------------------------------------------ |
| Boundaries         | Countries, states and provinces, and US counties, cities, ZIP codes, census geographies, and legislative districts |
| Climate            | Riverine flood risk, coastal flood risk, and drought risk                                                          |
| Demographics       | Population density, income, poverty, age, and more, for US states, counties, and census tracts                     |
| General            | Roads, buildings (North America and Europe), land use, water bodies, bathymetry, elevation, and time zones         |
| Infrastructure     | Airports, power plants, EV charging stations, and US public schools                                                |
| Nature and science | Parks, US wilderness areas, land cover, volcanoes, and plant hardiness zones                                       |

Each dataset's card shows its coverage, provider, and date. Select a dataset and open its **Metadata** tab to see its type, feature and attribute counts, last update, and description. Many datasets come from third parties with their own attribution requirements. See [Third-party attributions](/legal/third-party-attributions.md).

Some datasets people often look for aren't in the Global Library, such as parcels, points of interest, wind, wildfire, and Geographic Area Coordination Center (GACC) boundaries. For those, upload your own data or connect a source. See [Upload files](/upload-anything/files.md) and [Data sources](/upload-anything/data-sources.md).

## How Global Library layers behave on a map

A Global Library layer on your map is your own copy. Your changes to it don't affect the Global Library or other maps.

* Refreshing: Felt updates the Global Library on its own schedule. A layer on your map can't be refreshed or made live. To get a newer version, add the dataset again.
* Storage: adding a Global Library layer doesn't count toward your workspace's storage. Editing its features or attributes makes a full copy of its data, which does count. See [Plan usage](/plans-and-billing/plan-usage.md).


---

# 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/global-library.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.