- Exportación genérica o de fabricante
- .csv
.csv · Exportación genérica o de fabricante
Analyse telemetry exported to CSV
CSV is the universal route: if your logger is not on the list, it can almost certainly export CSV. Wild Telemetry detects which column is which channel and in what unit, and when the CSV comes from Race Studio or MoTeC i2 it also recovers the vendor's exact lap times.
- Format at a glance
Format at a glance
| Extension | .csv |
|---|---|
| Source | Any logger that can export |
| Columns | Alias match then fuzzy similarity |
| Units | Name suffix first, value range second |
| Lap boundaries | Exact when the header carries beacon markers |
| Conflicts | Highest confidence wins, with a warning |
How does it know which column is which?
First by exact match against a per-channel alias dictionary, and failing that by fuzzy similarity above a threshold. The unit is inferred from the column-name suffix first and only then from value ranges, which is the right order: a name is a declaration, a range is a guess.
When two columns compete for the same canonical channel the higher-confidence match wins and a warning is emitted. Warnings reach the interface: import quality is shown, never swallowed.
- The product
- FUJI
What you get when you open a session.
What it does not do
- A missing required field is zero-filled so the session still opens. That is a deliberate decision, and it is recorded as a warning.
- A CSV with no beacon markers cannot give exact lap times: boundaries are estimated from the telemetry itself.
Have .csv files?
Tell us which logger you run and we will say whether we can open your files before you install anything. Answered by hand.