> ## 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. # About resource types > Learn about the different resource types in CDF including assets, time series, events, files, 3D models, sequences, labels, and more. This page describes asset-centric resource types. For data modeling, see [Data modeling](/api-reference/concepts/20230101/data-modeling) and the [Data modeling guides](/cdf/dm/). A resource is an individual data entity with a unique identifier. This article introduces the different **resource types** you can interact with using the Cognite API. ## Assets The [assets](/api-reference/concepts/20230101/assets) resource type stores **digital representations** of objects or groups of **objects from the physical world**. Assets are organized in **hierarchies**. For example, a **water pump** asset can be part of a **subsystem** asset on an **oil platform** asset. Assets **connect related data from different sources** and are core to identifying all the data relevant to an entity (**contextualization**) in Cognite Data Fusion. All other resource types, for example, time series, events, and files should be connected to **at least one** asset, and each asset can be connected to many resources and resource types. [Learn more](/api-reference/concepts/20230101/assets) about assets. ## Time series The [time series](/api-reference/concepts/20230101/time-series) resource type stores a series of **data points** in **time order**. Examples of a time series are the temperature of a water pump asset, the monthly precipitation in a location, and the daily average number of manufacturing defects. For datapoint operations (insert, retrieve, query), see [Time series and datapoints](/api-reference/concepts/20230101/time-series-data). [Learn more](/api-reference/concepts/20230101/time-series) about time series metadata. ## Events The [events](/api-reference/concepts/20230101/events) resource type stores information that happens over **a period**. Events have a **start time** and an **end time** and can be related to **multiple assets**. For example, an event can describe two hours of maintenance on a water pump and associated pipes or a future period for when the pump is scheduled for inspection. [Learn more](/api-reference/concepts/20230101/events) about events. ## Files The [files](/api-reference/concepts/20230101/files) resource type stores documents that contain information related to **one or more assets**. For example, a file can contain a P\&ID diagram that shows how many assets are connected. For file upload and download operations, see [File content](/api-reference/concepts/20230101/file-content). [Learn more](/api-reference/concepts/20230101/files) about file metadata. ## 3D models The [3D models](/api-reference/concepts/20230101/3d-models) resource type stores files that offer **visual** and **geometrical data** and **context** to assets. For example, you can connect a pump asset with a 3D model of the plant floor where it's placed. Seeing asset data rendered in 3D helps you find the sensor data you are interested in faster. [Learn more](/api-reference/concepts/20230101/3d-models) about 3D models. ## Sequences The [Sequences](/api-reference/concepts/20230101/sequences) resource type stores a series of rows indexed by row number. Each row has one or more columns with either string or numeric data. Examples of sequences are performance curves and various types of logs, for example, depth logs in drilling. [Learn more](/api-reference/concepts/20230101/sequences) about sequences. ## Labels With [labels](/api-reference/concepts/20230101/labels), you can create a predefined set of **managed terms** that you can use to annotate and group **assets**. You can organize the labels in a way that makes sense in your business and use them to make it easier to find what you want. For example, you can create a label called *pump* and apply it to all asset resources that represent pumps and then filter assets to see only pumps. [Learn more](/api-reference/concepts/20230101/labels) about labels. ## Relationships The [Relationships](/api-reference/concepts/20230101/relationships) resource type represents connections between resource objects in Cognite Data Fusion (CDF). Each relationship is between a source and a target object and is defined by a **relationship type** and the **external IDs** and **resource types** of the source and target objects. Optionally, a relationship can be time-constrained with a start and end time. [Learn more](/api-reference/concepts/20230101/relationships) about relationships. ## RAW The [RAW](/api-reference/concepts/20230101/raw) resource type is the staging area in CDF. You can ingest data in its original form into RAW resource type to reduce source system queries for the same data for different use cases and minimize the data extractors' logic. This makes it easy to re-run transformations on data in the cloud. [Learn more](/api-reference/concepts/20230101/raw) about CDF RAW. ## Entity matching Different sources of industrial data can use different naming standards when they refer to the same entity. With [Entity matching](/api-reference/concepts/20230101/entity-matching), you can match entities like time series, files, and sequences from different source systems to assets. With the mapped information, you can build applications where users, for example, can click a component in a 3D model to see all the related time series data or ask for all the pressure readings along a flow line. [Learn more](/dev/concepts/resource_types/entity_matching) about entity matching. ## Geospatial The [Geospatial](/api-reference/concepts/20230101/geospatial) resource type represents data with a geospatial nature. This data, called *features* in Geographic Information System (GIS) terminology, are grouped into *feature types* that share several properties, such as name, type, and value, and have more than one spatial representation stored in configurable properties. Feature types are user-defined, and the CDF geospatial resource type doesn't come with pre-configured schemas to enable flexibility for modeling the client domain. [Learn more](/dev/concepts/resource_types/geospatial) about geospatial data.