|
|
|
The first example
is a portion of an OBE log file, showing timestamps, OBE ID (B420 in this
case) and the start of the data fields.
The first 11 lines are followed by the start of a snapshot appearing
in the log file at the time it is transmitted.
|
|
Note that the Data
Environment does not include all OBE
log files; it includes all log files for one day chosen for each of the three
data sets.
|
|
|
|
The second example
is a portion of a trajectory file, created by Noblis by extracting the
second-by-second position records from the log file, and adding X-Y values
corresponding to the given latitude/longitude values. The data environment contains trajectory
files for all vehicles on all days.
|
|
|
|
The sample map was
created by (1) running the Trajectory Plotter program , reading part of a
trajectory file to create a KML file, and (2) inputting the KML file to
Google Earth. Within Google Earth
there is pan and zoom capability to look at trajectories in detail.
|
|
|
|
The data
environment also contains files with all snapshot data extracted from the OBE
log files (including duplicates and snapshots not received by RSEs) and files
listing all snapshot generation, RSE acquisition and transmission, and Probe
Segment Number (PSN) change events.
|
|
|
|
Documentation for
these files is included in the data environment.
|
|
|
|
|
|
|
