> 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/analytics/iot-query/schema-overview/bronze-layer/raw-telematics-data.md). # raw\_telematics\_data schema raw\_telematics\_data holds tracking points, inputs, states, and events sent by devices. Browse the schema definition and key table descriptions for SQL analysis The **`raw_telematics_data`** schema contains four primary table types that work together to provide comprehensive device data. {% hint style="info" %} The interactive diagram of raw\_telematics\_data schema is available on **dbdiagram.io**: {% endhint %} Find raw telematics data schema details below. {% code title="raw\_telematics\_data schema" expandable="true" %} ```sql Table tracking_data_core {   device_id integer [primary key]   device_time timestampz [primary key]   platform_time timestampz   record_added_at timestampz [default: `now()`]   latitude integer   longitude integer   speed integer   altitude integer   satellites integer   event_id integer   gps_fix_type integer   hdop integer   indexes {(device_id, device_time)} } Table inputs {   event_id integer [primary key]   device_id integer [primary key]   record_added_at timestampz [default: `now()`]   device_time timestampz [primary key]   sensor_name text [primary key]   value text   indexes {(device_id, device_time)} } Table states {   event_id integer [primary key]   device_id serial [primary key]   record_added_at timestampz [default: `now()`]   device_time timestampz [primary key]   state_name text [primary key]   value text   indexes {(device_id, device_time)} } Table additional_data { device_id integer [primary key] device_time timestampz [primary key] platform_time timestampz record_added_at timestampz [default: `now()`] discrete_inputs text [primary key] discrete_outputs text [primary key] special_jsonb jsonb indexes {(device_id, discrete_inputs, discrete_outputs, device_time)} } Ref: inputs.(device_id, device_time) > tracking_data_core.(device_id, device_time) Ref: states.(device_id, device_time) > tracking_data_core.(device_id, device_time) Ref: additional_data.(device_id, device_time) > tracking_data_core.(device_id, device_time) ``` {% endcode %} ## Key tables by category Each table serves a specific purpose in capturing different aspects of device information:
tracking_data_core **Purpose**: Core location and motion data
AttributeDetails
Key fieldsdevice_id, device_time, platform_time, latitude, longitude, speed, altitude, satellites, hdop, event_id
IndexingOptimized with index on (device_id, device_time)
Special notesLocation data (latitude and longitude) uses integer format with 10⁷ precision for optimal TimescaleDB performance

Speed is also stored in integer, so you need to divide it with 100
inputs **Purpose**: Sensor readings from devices
AttributeDetails
Key fieldsinput_id, device_id, device_time, sensor_name, value
ContentAnalog readings (fuel level, temperature, voltage), calculated values (engine RPM)
Relationships
FROM raw_telematics_data.inputs AS i
JOIN raw_business_data.sensor_description AS sd
    ON i.device_id = sd.device_id AND i.sensor_name = sd.input_label
JOIN raw_telematics_data.tracking_data_core AS tdc
    ON i.device_id = tdc.device_id AND i.device_time = tdc.device_time
states **Purpose**: Device status indicators and operational modes
AttributeDetails
Key Fieldsstate_id, device_id, device_time, state_name, value
ContentOperating mode indicators (working, idle, off), component statuses (ignition, doors)
Value FormatBoolean values (1/0) or specific status codes
additional_data **Purpose**: Discrete input/output signal states and other non-standard device data
AttributeDetails
Key fieldsdevice_id, device_time, platform_time, discrete_inputs, discrete_outputs
Primary keyComposite: (device_id, discrete_inputs, discrete_outputs, device_time)
ContentEach of discrete_inputs and discrete_outputs is a bit string with one character per input or output channel (for example, "10110001"), where 1 means on and 0 means off
Special notesspecial_jsonb is a reserved column for future device data and isn't currently populated. This table feeds processed_common_data.input_change_events. See Input change events
Data in this schema is ingested directly from devices, with minimal latency (typically seconds). The schema is optimized for time-series data using TimescaleDB for efficient storage and retrieval. ## Additional information ### Data validation The database enforces data integrity through multiple mechanisms: * **CHECK constraints** validate that values fall within acceptable ranges * **Foreign keys** ensure relationships between tables remain consistent * **NOT NULL constraints** guarantee that required fields always have values * **DEFAULT values** provide fallback when data isn't explicitly provided ### Query optimization Tables are organized with specific indexing strategies: * All tables include **time-based indexes** on `record_added_at` * Foreign key columns have dedicated indexes for join performance * Frequently used column combinations have **composite indexes** * TimescaleDB provides specialized indexes for time-series queries --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://navixy.com/docs/analytics/iot-query/schema-overview/bronze-layer/raw-telematics-data.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.