Tool foundation
Telemetry CSV Data-Quality Inspector
Inspect the structure of a telemetry CSV locally before you use it to form an interpretation. No upload, account, database or external API.
Local browser tool · Version 1.0
Inspect the structure before you interpret the trace
Select a telemetry CSV. The file stays in your browser. LapProtocol checks the structure before you interpret the data.
No upload. The file is read locally and is not sent to a server.
Processed locally · no account · no database · browser inspection limit: 25 MB
No file selected.
Selected file
Unknown
Inspection result
Structural readout
Time and sampling
Timestamp inspection
- Time column
- Unknown
- Recorded start
- Unknown
- Recorded end
- Unknown
- Recorded span
- Unknown
- Duplicate timestamps
- Unknown
- Large gaps
- Unknown
- Largest positive step
- Unknown
- Unreadable time values
- Unknown
How gaps are screened
The tool uses the file's own positive time steps. It does not assume a universal motorsport sampling interval.
Channel inventory
What is present in the header?
Flags are prompts to check, not fault findings.
Read this before using the result
A structurally readable CSV is not necessarily accurate telemetry. This inspector cannot confirm sensor calibration, installation, units, channel meaning, alignment quality or vehicle condition. A constant channel can be legitimate, and a populated channel can still be wrong.
Before you interpret the trace
Data structure is the first question, not the final answer
A telemetry file can contain thousands of values and still leave important questions unresolved. A missing channel, duplicated timestamp, flat-lined field or unexplained time gap can change what a comparison is able to support. This inspector gives you a quick structural readout before you move from the file to a lap-comparison question.
What the inspector checks
- Header and channel inventory
- Rows, blank cells and basic file information
- Likely time columns, including ambiguity where more than one is plausible
- Repeated timestamps and contextual large time gaps
- Numeric, text, mixed and empty columns
- Basic minimum and maximum ranges for fully numeric channels
- Constant and near-constant channel flags
What it cannot check
- Sensor calibration, installation or channel accuracy
- Whether a channel name means what the logger documentation says it means
- Whether the car is safe, fast, slow or correctly set up
- Whether a setup change worked
- Whether two laps are comparable for a particular question
- Whether a value is physically plausible for a specific vehicle
Why telemetry data can mislead
A populated channel is not automatically a trustworthy measurement. Timing, synchronization, filtering, installation, units, configuration and missing context all matter. A constant channel may be legitimate, or it may be a field that was not recording. The result here is therefore an inspection prompt, not a verdict. Keep the source, units and limitations beside the question you are asking.
For the next step, use LapProtocol'stelemetry data-quality checklist to decide whether two laps are comparable enough for a defined question. Then use thetwo-lap telemetry method to locate where time changed without turning a delta into proof of cause.
The wider method remains the same: plan a useful question in thestructured track-test workflow, keep the observation separate from the possible explanation, and retain the limitations through validation. LapProtocol's methodology explains the evidence and safety boundary behind that sequence.