The global +coord file was re-created by concatenating the sub-files.

Detailed timing and sub-files:

- File _1: emergency exit to CP6 (T0 to T2)
  - T0: AP started (emergency exit = 75.50;-34.50;1)
  - T1: start walking
    - Elapsed:                              00m 08s .72
    - Total time:                           00m 08s .72
    - Theoretical timestamp: T2 - 53.90 s = 1368650387.024390126
  - T2: AP stopped (CP6 = 121.80;-21.10;1)
    - Elapsed:                              00m 53s .90
    - Total time:                           01m 02s .62
    - Timestamp:                            1368650440.924390126

- File _2: CP6 to CP3 (T3 to T5)
  - T3: AP started
    - Elapsed:                              00m 34s .13
    - Total time:                           01m 36s .75
    - Theoretical timestamp:   T2 + 34.13 = 1368650475.054390126
  - T4: start walking (CP6 = 121.80;-21.10;1)
    - Elapsed:                              00m 06s .12
    - Total time:                           01m 42s .87
    - Theoretical timestamp:    T3 + 6.12 = 1368650481.174390126
                          or T5 - 67.39 s = 1368650481.531350330
  - T5: AP stopped (CP3 = 177.90;18.15;1)
    - Elapsed:                              01m 07s .39
    - Total time:                           02m 50s .26
    - Timestamp:                            1368650548.921350330
    - Theoretical timestamp:   T4 + 67.39 = 1368650548.564390126

- File _3: CP3 to CP2 (T6 to T8)
  - T6: AP started
    - Elapsed:                              00m 35s .51
    - Total time:                           03m 25s .77
    - Theoretical timestamp:   T5 + 35.51 = 1368650584.074390126
  - T7: start walking (CP3 = 177.90;18.15;1)
    - Elapsed:                              00m 06s .62
    - Total time:                           03m 32s .39
    - Theoretical timestamp:    T6 + 6.62 = 1368650590.694390126
                            or T8 - 55.27 = 1368650590.631713005
    - Note: the request sent at timestamp 1368650589.997169920 is
      considered as being sent before the operator started walking,
      therefore it was not used as the first bound for coordinate
      interpolation (a dummy request with timestamp 1368650590.694390126
      was used for the interpolation).
  - T8: AP stopped (CP2 = 160.85;78.30;1)
    - Elapsed:                              00m 55s .27
    - Total time:                           04m 27s .66
    - Timestamp:                            1368650645.901713005
    - Theoretical timestamp:   T7 + 55.27 = 1368650645.964390126

- File _4: CP2 to CP1 (T9 to T11)
  - T9: AP started
    - Elapsed:                              00m 32s .93
    - Total time:                           05m 00s .59
    - Theoretical timestamp:   T8 + 32.93 = 1368650678.894390126
  - T10: start walking (CP2 = 160.85;78.30;1)
    - Elapsed:                              00m 06s .11
    - Total time:                           05m 06s .70
    - Timestamp:                            1368650685.000436732
    - Theoretical timestamp:    T9 + 6.11 = 1368650685.004390126
  - T11: AP stopped (CP1 = 128.25;142.40;1)
    - Elapsed:                              00m 59s .75
    - Total time:                           06m 06s .45
    - Timestamp:                            1368650744.893494551
    - Theoretical timestamp:  T10 + 59.75 = 1368650744.754390126

- File _5: CP1 to CP5 (T12 to T14)
  - T12: AP started
    - Elapsed:                              00m 33s .73
    - Total time:                           06m 40s .18
    - Theoretical timestamp:  T11 + 33.73 = 1368650778.484390126
  - T13: start walking (CP1 = 128.25;142.40;1)
    - Elapsed:                              00m 06s .38
    - Total time:                           06m 46s .56
    - Timestamp:                            1368650783.968516753
    - Theoretical timestamp:   T12 + 6.38 = 1368650784.864390126
    - Note: to cope with the deviation of the timestamps, we used the
      second request in the file as departure time instead of the
      theoretical timestamp.
  - T14: AP stopped (CP5 = 72.10;122;1)
    - Elapsed:                              00m 51s .57
    - Total time:                           07m 38s .13
    - Timestamp:                            1368650835.876004579
    - Theoretical timestamp:  T13 + 51.57 = 1368650836.434390126

Please note that the timings are approximate and that it is impossible
to know exactly when the operator started the AP at the beginning of
the scenario and stopped it at the end (although normally the mobile
stops transmitting requests as soon as the AP is off, so the stop time
is a better indicator).

For example, here we consider that the timestamp of the last request of
t01, i.e. 1368650440.924390126, corresponds to T2 (walk stops), but it
is possible that this request was transmitted while the operator was
already standing still next to CP6 for a second. From this timestamp, we
extrapolate the theoretical timestamp of T1 (a request was sent at
1368650387.038010383, which is close enough, but it has been filtered
out because it was buggy). We also extrapolate the later theoretical
timestamps from T2.

In the timing above, a "real" timestamp (i.e. corresponding really to a
transmitted positioning request) is also noted for some of the requests.
For the interpolation of the coordinates, the first timestamp that
appears in the list for a given step was used, but to compute future
theoretical timestamps, previous theoretical timestamps were used.