30.11.2012 Views

Automotive User Interfaces and Interactive Vehicular Applications

Automotive User Interfaces and Interactive Vehicular Applications

Automotive User Interfaces and Interactive Vehicular Applications

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Motivation<br />

• The mobility context strongly affects which information is relevant for a user.<br />

• It can be used to adapt the way information is presented, e.g., in a car.<br />

• It also can be used to calculate the carbon footprint of a user.<br />

• Or can make suggestions for a more economic or ecologic way to work.<br />

Approach<br />

Bus schedule<br />

Maps<br />

GPS<br />

Accelerometer Compass<br />

Result<br />

Figure 1: Visualization of a trace using Google Earth.<br />

Correct determination of transportation means is<br />

depicted in green, incorrect results depicted in red.<br />

The recognition of the railway line in parallel to the<br />

highway is confused with driving by car.<br />

Findings<br />

Daniel Christoph Christian<br />

Daniel Braun, Christoph Endres, Christian Müller<br />

Divide Traces<br />

into sections<br />

(~30 m length)<br />

Additional Information<br />

We identified some areas with suboptimal recognition rates:<br />

• Train rides can be confused with riding a car. (Figure 1)<br />

• The recognition of walking is challenged by the inherent inaccuracy of the<br />

GPS signal. (Figure 2)<br />

• Traffic jams are sometimes confused with walking. (Figure 3)<br />

This work was funded by the<br />

German Federal Ministry<br />

of Education <strong>and</strong> Research<br />

Why using Low-Level Data?<br />

• Low-Level GPS Data are provided by every smartphone <strong>and</strong> navigation system<br />

• The data can be used everywhere, because need road maps etc are not necessary<br />

• The analysis of these data is easy <strong>and</strong> fast (realtime)<br />

function calculateSpeed(){<br />

…<br />

}<br />

function calculateAcceleration(){<br />

….<br />

}<br />

function contextHeuristic(){<br />

----<br />

}<br />

Figure 2: Visualization of a trace with afoot parts.<br />

Incorrect (red) results are caused by inaccuracy of the<br />

GPS signal.<br />

Conclusion<br />

Mobility Contexts<br />

Different means of<br />

transportation :<br />

• car<br />

• train<br />

• afoot<br />

• etc<br />

Different situations:<br />

• urban traffic<br />

• highways<br />

• traffic jams<br />

• etc<br />

Figure 3: Visualization of a trip on the highway. Red<br />

parts are caused by traffic jams which are confused with<br />

walking.<br />

• The use of low level GPS data as only source is not sufficient for<br />

recognizing the mobility context of a user.<br />

• It is necessary to connect the low level data with other information, such as<br />

street maps, schedules or additional sensordata (e.g., accelerometer) to<br />

obtain more reliable results.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!