Skip to main content
Location filters stay available. Filters that select asset-centric resources depend on resource types that are deprecated. See Deprecated and retired features and Data modeling status for CDF projects.
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 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. 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.
Last modified on October 15, 2026