> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cognite.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Manage locations

> Define location filters to help users find and select data related to specific physical locations, improving 3D experiences and natural language search results.

Each CDF project contains a **system default** location filter. It doesn't match any physical location and isn't linked to a 3D scene. Data from asset-centric and/or core data models are displayed without any filtering, and the system default location only shows singular 3D models.

We strongly recommend [configuring additional location filters](/cdf/locations/guides) to match your organization's physical location structure. You can create a **hierarchy** of location filters.

Depending on how your data is stored and structured, you can use **data sets**, and **prefixes** to define location filters:

* **Data set filters** work with asset hierarchies built with dedicated resource types and where the data is grouped into [data sets](/cdf/data_governance/concepts/datasets). A data set is a container for data objects with metadata about the data it contains.

* **Prefix filters** work with asset hierarchies built with dedicated resource types. They let you filter the search results to data objects where the external ID starts with a specific string.

## Limitations

We recommend not creating more than 100 location filters per CDF project. If you need to increase this number, contact [Cognite support](https://cognite.zendesk.com/hc/en-us/requests/new).