Back to the Main Page → Back to Motive Documentation → Back to Data Export
Captured tracking data can be exported in Comma Separated Values (CSV) format. This file format uses comma delimiters to separate multiple values in each row, and it can be imported by spreadsheet software or a programming script. Depending on which data export options are enabled, exported CSV files can contain marker data, rigid body data, and/or skeleton data. CSV export options are listed in the following chart:
Global: Defines the bone segment position and orientation in respect to the global coordinate system. The global coordinate system is the origin of the ground plane which was set with a calibration square during Calibration process.
Local: Defines the bone segment position and orientation in respect to the coordinate system of the parent segment. Note that the hip of the skeleton is always the top-most parent of the segment hierarchy. Local coordinate axes can be set to visible from Application Settings or display properties of assets in Project Pane. The Bone segment rotation values in the Local coordinate space can be used to roughly represent the joint angles; however, for precise analysis, joint angles should be computed through a biomechanical analysis software using the exported capture data (C3D).
Adds a column of Marker quality values after each rigid body marker data.
The quality stats display the reliability of associated marker data. Errors per marker lists average displacement between detected markers and expected marker locations within corresponding assets. Marker Quality values rate how well camera rays converged when the respective marker was reconstructed. The value varies from 0 (unstable marker) to 1 (accurate marker).
When the header is disabled, this information will be excluded from the CSV files. Instead, the file will have frame IDs in the first column, time data on the second column, and the corresponding mocap data in the remaining columns.
TIP: Occlusion in the marker data
When there is an occlusion in a marker, the CSV file will contain blank cells. This can interfere when running a script to process the CSV data. It is recommended to optimize the system setup to reduce occlusions. To omit unnecessary frame ranges with frequent marker occlusions, select the frame range with the most complete tracking results. Another solution to this is to use Fill Gaps to interpolate missing trajectories in post-processing.
For Takes containing force plates (AMTI or Bertec) or data acquisition (NI-DAQ) devices, additional CSV files will be exported for each connected device. For example, if you have two force plates and a NI-DAQ device in the setup, total 4 CSV files will be saved when you export the tracking data from Motive. Each of the exported CSV files will contain basic properties and settings at its header, including device information and sample counts. Also, mocap frame rate to device sampling rate ratio is included since force plate and analog data are sampled at higher sampling rates.