Skip to content
Dana edited this page Jul 5, 2021 · 26 revisions

This wiki is for documenting the MoMoCapture app that is being developed in the fourMs Lab at University of Oslo. It was originally developed for MusicLab events, but is also used for other data collection procedures.

Recorded Data

The recorded data are packaged into a zip-file with two CSV files:

  • deviceID.deviceMotion.csv
  • deviceID.geoLocation.csv

These are described more below.

Inertial Data

The CSV file containing motion data consists of columns with the following variables:

  • timestamp: the epoch timestamp that is returned from the device. It can be converted online or in your programming language of choice.
  • time: a time marker from the device (in milliseconds), which resets to zero when the hardware initializes and is incremented over time (it might be more precise than the timestamp).
  • x: accelerometer data in the X direction
  • y: accelerometer data in the Y direction
  • z: accelerometer data in the Z direction
  • alpha: rotation in the Z direction
  • beta: rotation in the X direction
  • gamma: rotation in the Y direction

The specification of the inertial sensor readings is documented in the W3C DeviceOrientation Event Specification, and can be seen in the image below.

Orientation

The iOS 13 version does not have the rotation information (alpha, beta, gamma). So for this OS, the orientation information (also alpha, beta, gamma) is sent in an additional file following the official documentation.

The Geolocation Data

The CSV file containing GPS data consists of the following columns:

  • time: the epoch timestamp. It can be converted online or in your programming language of choice.
  • lat: the GPS latitude, ranging from 0 to 90 (in decimal degrees). It can be converted online.
  • long: the GPS longitude, ranging from 0 to 180 (in decimal degrees).
  • accuracy: the accuracy of the GPS measurement (in meters) (more information on this value here).

Questionnaires

If the form contains a question with the text 'userID' the app will put the userID in this field and disable the field for editing. It is recommended to use this feature as this is the only way to match pre/post questionnaire and the data.

Clone this wiki locally