Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.siftstack.com/llms.txt

Use this file to discover all available pages before exploring further.

​
Overview

This page documents every setting available when importing a telemetry file through the Sift user interface. Settings are grouped by file type.

​
File formats supported in the UI

The Sift UI supports the following file formats for import:
  • CSV
  • Parquet
  • TDMS
  • HDF5

​
Common settings

These settings appear across multiple file types.

​
Asset and Run

​
Time settings

​
Timestamp formats

​
Channel configuration table

Shown for CSV and Parquet (Flat Dataset). Each non-timestamp column appears as one row.

​
Data types

​
CSV settings

Settings in the Upload CSV dialog.

​
CSV file requirements

Example: CSV header row

​
Parquet settings

​
Parquet file requirements

Every Parquet file must include a timestamp column, and must follow exactly one of the two supported schemas: Flat Dataset or Channel Per Row (not both). Example: Flattened Parquet Channel names A Parquet column location containing {lat, lon} imports as:
  • location.lat
  • location.lon

​
Parquet: Flat Dataset settings

​
Parquet: Channel Per Row settings

Example: Channel Per Row Parquet layout Settings used for this layout:
  • Channel Configuration: Multi
  • Name Column: channel_name
  • Data Column: value

​
Complex types modes

Applies to Flat Dataset Parquet files.

​
TDMS settings

Settings in the Upload TDMS dialog. TDMS imports use the group and Channel hierarchy embedded in the file to derive Channel names. The TDMS dialog does not expose a per-Channel configuration table. Channel-level description properties are imported and appear in the channel detail panel in the Run view. Embedded enum configurations are also imported and surfaced as enum types on the Channel.

​
Per-channel settings (REST API and Python client only)

Use TdmsDataConfig entries in the data field of TDMSConfig to select specific Channels and control how each is imported. When data is empty, Sift imports all Channels and applies the fallback method to any with missing timing information. See TDMSConfig in the protocol buffers reference for the full schema.

​
HDF5 settings

Settings in the Upload HDF5 dialog.

​
HDF5 schemas

Select the schema that matches the layout of your HDF5 file. Sift walks groups recursively for all three schemas.

​
Per-channel settings (REST API and Python client only)

Use Hdf5DataConfig entries in the data field of Hdf5Config to map specific datasets to Channels. When data is empty, Sift imports all datasets it can resolve. See Hdf5Config in the protocol buffers reference for the full schema.