Supported formats

Import your sessions

Send the files of your laptimer as they are: LapViz recognizes the format from the content of the file, not from its name.

Device times
The laps recorded by the laptimer are kept. On a circuit known by LapViz, the laps and sectors are also calculated from the GPS, to compare with the other drivers.
Recalculated times
The file has no laps: LapViz calculates them from the GPS track, on a circuit known by LapViz only.
  • Unipro

    Device times .uni
    UniGo and the other Unipro laptimers Channels: All the channels of the file
  • Alfano

    Device times .zip, .alf2, .csv
    Alfano laptimers Channels: GPS position and speed, RPM, rear speed, orientation, altitude Send the archive exported by the Alfano software as it is, without unzipping it: it holds the date, the driver and every lap. A lap file taken out of it (LAP_….csv) is read as one lap, dated the day it is sent.
  • Alfano CSV

    Device times .zip
    Alfano 6 sessions exported as resumen_vueltas.csv and telemetria_completa.csv Channels: GPS position and speed, RPM, rear speed, orientation, altitude Send the .zip with both files as it is, without unzipping it.
  • AiM

    Device times .xrk, .xrz, .drk
    MyChron and the other AiM loggers Channels: All the channels of the file, with the GPS channels
  • AiM CSV

    Device times .csv
    CSV export of AiM Race Studio Channels: All the channels of the export, with the GPS channels Prefer the .xrk or .xrz file of the logger: it holds every channel at its own rate. Otherwise, export the session in CSV from Race Studio.
  • LapViz

    Device times .lvz, .txt, .csv
    LapViz apps, LapViz delimited text Channels: All the channels of the file Delimited text must start with the #Format=LapViz Delimited Data header.
  • RaceBox

    Device times .csv
    RaceBox Mini and Micro, CSV export of the RaceBox app Channels: GPS position, speed and altitude, accelerations, rotation, heading Send the CSV as the app exported it, without renaming it: the exports without their first lines take their date from their name.
  • RaceChrono

    Device times .rcz, .csv
    RaceChrono app, session file or CSV export Channels: GPS position, speed, heading and altitude, satellites and accuracy, accelerations and rotation of the phone or of an external GPS, speed, engine speed, throttle and temperatures of an OBD reader In RaceChrono, export the session as a RaceChrono session file (.rcz) or in CSV. The .rcz files are read with the GPS of the phone or an external GPS, the accelerometer and gyroscope of either, and an OBD reader (speed, engine speed, throttle, coolant and intake air temperatures); what other sensors recorded is not read yet: send those files anyway, they are kept and looked at.
  • TrackAddict

    Device times .csv
    TrackAddict app: Raw CSV export, or the Log- files of the app Channels: GPS position, speed and altitude, accelerations, the OBD channels logged by the app In TrackAddict: Share, data file, Raw CSV (TrackAddict & RaceRender).
  • QStarz

    Device times .rcnx
    QStarz LT-Q6000 lap timers, session file of the QRacing software Channels: GPS position, speed, heading and altitude, accelerations
  • LapTrophy

    Recalculated times .csv
    LapTrophy app, CSV export Channels: GPS position, speed and accuracy
  • Harry's LapTimer

    Device times .kml
    Harry's LapTimer app, KML export Channels: GPS position and altitude of the exported laps, with the laps and intermediates of LapTimer Prefer the VBO export of Harry's LapTimer, sent as it is (.vbo or .zip): it holds the whole session, with the speed and the other channels. The KML export only holds the exported laps, without the speed.
  • VBO

    Recalculated times .vbo, .zip
    Racelogic VBOX, and the VBO export of RaceBox, RaceChrono, Harry's LapTimer, TrackAddict… Channels: GPS position, speed, heading and altitude, the other channels of the file
  • Off Camber Data

    Device times .csv
    RaceRender export of Off Camber Data Channels: GPS position and speed, the other columns of the file
  • RaceRender

    Recalculated times .csv
    Data exported by RaceRender (e.g. from a GoPro video) Channels: GPS position, speed, altitude
  • GoPro

    Recalculated times .mp4
    GoPro cameras with GPS Channels: GPS position, speed and altitude of the camera
  • Garmin FIT

    Recalculated times .fit
    Garmin watches and bike computers, the FIT export of sport apps Channels: GPS position, speed and altitude A watch records about one position per second, often less: lap times are less precise than with a lap timer at 10 Hz or more.
  • NMEA 0183

    Recalculated times .txt, .nmea, .log
    GPS receivers and loggers that save their raw NMEA 0183 output (RMC sentences) Channels: GPS position, speed and heading, altitude when the log has it Prefer the session file of your lap timer or app when it has one listed here: a raw NMEA log only holds the GPS position, speed and heading, and its altitude when it has GGA sentences.
  • CSV (other)

    Recalculated times .csv, .txt, .tsv
    Other CSV files with a time column and the GPS position: exports converted by a script or a tool, CSV of loggers not listed here Channels: GPS position, speed, heading and altitude when the file has them, its other columns of numbers Prefer the file of your lap timer or app when it is listed here. LapViz recognises the columns of this CSV by their names and checks the speed against the positions; when the file has no date, the session is dated the day you send it.
  • GPX

    Recalculated times .gpx
    Most GPS apps and loggers (RaceChrono, TrackAddict…) Channels: GPS position, speed and altitude Export your session to GPX or VBO when your app or laptimer has no format listed here.

Your format is not listed? Upload the file anyway: it is kept and we look at adding the format. You can also write to info@lapviz.com.

Guides per logger and app

Lap timer data analysis software, for every brand Karting and track day data analysis software compared