> For the complete documentation index, see [llms.txt](https://navixy.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navixy.com/docs/iot-query-premium/data-access/data-schema/raw-data-layer.md).

# Raw data layer

The raw data layer of IoT Query Premium: business data copied from Business Data Repository and the telemetry your GPS devices send, before any calculation.

{% hint style="info" %}
IoT Query Premium is coming soon. This page describes how it works at release. To learn when it becomes available for your organization, [contact Navixy](https://navixy.com/en/contact?utm_source=navixy-docs\&utm_campaign=iot-query-premium).
{% endhint %}

The raw data layer stores your data as it arrives in IoT Query Premium, before Navixy calculates anything from it. It has two databases: `core_bdr` for business data and `telemetry` for what your GPS devices send. This page explains what the raw data layer contains and when to query it instead of the [transformation layer](/docs/iot-query-premium/data-access/data-schema/transformation-layer.md). It is for developers and analysts who need data at its most detailed.

## What the raw data layer contains

Each database of the raw data layer has one source:

* **`core_bdr`** is a copy of [Business Data Repository](https://app.gitbook.com/s/6RLA9o0EecKpLxHiaeR4/bdr): your workspace and its users, devices, assets, asset groups, geo objects, schedules, catalogs, and custom field definitions. Navixy copies it automatically. Each table keeps the columns of Business Data Repository, so an asset in `core_bdr.asset` has the same ID and name as in Business Data Repository.
* **`telemetry`** stores the messages of your GPS devices: time, position, speed, ignition, odometer, and sensor values. Navixy writes each message as it arrives.

Navixy calculates nothing from other rows in the raw data layer. A position in `telemetry` is the position that the device sent. The only change before Navixy writes a message is the calibration of its sensor values into their units. A trip, a stop, or a visit to a geo object doesn't exist in the raw data layer: it is a result of the transformation layer.

## When to query raw data

Query the raw data layer in these cases:

* **You need names, types, or custom fields.** Only `core_bdr` has the names of assets, devices, and geo objects. Join it to any calculated table to show names instead of IDs.
* **You need every data point.** `telemetry` has each message, while the transformation layer groups them into trips, stops, and 1-minute periods.
* **You need a value that no calculated table has**, such as a sensor that the transformation layer doesn't aggregate.
* **You define your own rules.** To detect trips with your own speed limit, or to count events that Navixy doesn't calculate, start from `telemetry`.

For totals, durations, and time in geo objects, query the transformation layer. Its tables are smaller and are already calculated, so the same question takes less time and less SQL.

## Databases of the raw data layer

* [core\_bdr database](/docs/iot-query-premium/data-access/data-schema/raw-data-layer/core-bdr.md): Find the tables of the workspaces, users, devices, assets, asset groups, geo objects, schedules, catalogs, and custom fields.
* [telemetry database](/docs/iot-query-premium/data-access/data-schema/raw-data-layer/telemetry.md): Find the columns that store positions and sensor values.


---

# 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://navixy.com/docs/iot-query-premium/data-access/data-schema/raw-data-layer.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.