mHealth specification
  • Introduction
  • Directory structure
    • Overview of directory structure
  • File types
    • Quick view of supported file types
  • sensor Data
    • Filename convention
    • File format
    • Sensor types
    • Data types
  • event Data
    • Filename convention
    • File format
    • Event types
  • annotation Data
    • Filename convention
    • File format
  • feature Data
    • Filename convention
    • File format
Powered by GitBook
On this page
  • File format
  • Columns
  • HEADER_TIME_STAMP, START_TIME, STOP_TIME format
  • Other columns' format
  1. annotation Data

File format

Store formatted annotations from a predefined or user defined annotation set.

File format

In csv format, separated by ,, no white space.

HEADER_TIME_STAMP,START_TIME,STOP_TIME,LABEL_NAME
2015-01-05 15:23:00.244,2015-01-05 15:20:00.244,2015-01-05 15:21:00.244,Walking

Columns

COLUMN_NAME

POSITION

Value type

Values

Required

HEADER_TIME_STAMP

1

String

e.g. 2015-01-05 15:23:00.244

Yes

START_TIME

2

String

e.g. 2015-01-05 15:23:00.244

Yes

STOP_TIME

3

String

e.g. 2015-01-05 15:23:00.244

Yes

LABEL_NAME

4

String

e.g. Walking

Yes

CONFIDENCE

5

0-1

e.g. 0.5

No

PARTICIPANT_ID

last

String

e.g. SPADES_1

No

Should be locally unique among the annotation set.

0 means random guess, 1 means for sure.

HEADER_TIME_STAMP, START_TIME, STOP_TIME format

  2. YYYY-MM-DD HH:mm:ss.SSS

Other columns' format

  1. No white space.

  2. If value is not available, use "" empty string instead.

PreviousFilename conventionNextFilename convention

Last updated 6 years ago

In local time zone, meaning the time zone where event happens. Time zone can be identified through .

filename convention