Traffic Shaper Driving with mobile application

tools

Federica Santuccio

Innova S.p.a. Bilbao, 14/11/2014

What is Traffic Shaper?

• Traffic Shaper is a project funded under the European Mobility and Mobile Industry Alliance that started on 1st September 2013 until 31th August 2015.

• The total budget allocated is around 575.000 euro (funded at 70%)

Partners of teh project

• Associazione dei Comuni Italiani (ANCI) –

Umbria (coordinator)

• Innova S.p.a

• Tconnect Slovenia

• CFLI Venezia (Consorzio Formazione

Logistica Intermodale)

• Encadre

What is Traffic Shaper about?

Traffic Shaper has the objective to shape the road traffic in a centralized way by proposing alternative to routes according to different users connected.

The project aims at developing a mobile application tool based on data collected from:

• pre-existing real-time road traffic data (Tom-Tom data)

• users positions and profiles, from social network

• atmospheric and air quality data

What’s new in Traffic Shaper?

• Traffic Shaper provides a tailored solution in

moving from point A to point B by suggesting

alternative routes to the different users moving

along the same way private user

• The service intends to identify troubles related to

natural disease that may cause traffic and favour

the intervention of public security public

user

How?

Technical functioning

• Back-end system development

– System Architecture

– Data sources

– Traffic simulation

– Functionalities

– API

• Front-end system development

– Administration GUI

– Mobile APP

• Demonstrator

System architecture 1/2

Source 1 Source 2 Source n

Data source collector

User 1

User 2

User n

API

Elaboration engine

Admin GUI

DB

System architecture 2/2

• Data sources:

– GPS tracker (Dedicated device, Mobile app)

– Real time data sources (TomTom data)

– Social network (Twitter)

• Data source collector:

– it collects the traffic-road conditions data and it adapts them to our

platform's format.

• Elaboration engine

– takes as input the previous elaborated information (users routes, the

traffic road condition) and it calculates the best route for each user;

• API

– permits to exchange data between the backend and the mobile app and

the user administration GUI;

• DB interface

API

• user registration;

• user authentication;

• get route: it permits to send a user request route to the backend, in response the user receives the computed route;

• get my routes: it permits to retrieve all the user requested routes;

• insert new traffic event: it permits the user to send a geo-localized traffic event;

• track my position: it permits to send to the backend to current user positions.

Functional block diagram

Administration GUI

• View the system users list

• View user profile

• Statistical information on the user daily habits:

– preferred routes,

– most reached places,

– arrival and departure hour

• Block user account

ADMINISTRATION GUI

Mobile Application

• user registration and authentication

• route selection – the user can request a specific route inserting the start point and the

arrival point;

• route visualization – once the user request a route, the application visualizes the backend

response, i.e. the best calculated route, directly on screen as a red line

on Google Maps;

• reporting traffic condition – the user can also be “active”, helping to know where is a traffic

congestion or an accident;

• user tracker – the app sends automatically information about user’s position to the

backend. These features can be activated or deactivated by the user.

Mobile application

Mobile application

Problems encountered

• The trade-off between available data and

collection of our specific data through data

collector

• The correct methodology for route

recalculation

• Finding solutions effectively innovative and

useful for the user

Next steps

• Finalization of the methodology

– Re calculation of the routing

– Multi user management

• Sources based on pollution Data

• Mobile app finalization

• Extension to big Italian cities such as Rome (under discussion)

Demo

Download the app from:

•http://www.t-connect.it/trafficshaper/download.html

Your comments are welcome to:

Remo Pomposini

remo.pomposini@gmail.com

Thank you for your attention

Federica Santuccio

Innova S.p.a.

F.santuccio@innova-eu.net

Elaboration engine 3/3

• route elaboration engine

– it performs the simulation,

– Input: the data coming from the controller

– Output: the best path for each user.

– SUMO framework in order to perform traffic simulation.

• SUMO classic simulation: it uses the Dijkstra algorithm to find the optimal route for each

car in terms of travelling time. – This method is reliable in terms of output, i.e. it find the best route for each user

– it is very slow, it has a lot of computation;

• DuaRouter: also this methodology adopt the Dijkstra algorithm for each users, but in this

case is only performed the shortest path and not a full simulation in the time, – it lacks of important output data such as the travel time.

– The advantage of this method is the execution time that is about 70% -80% less than the first one;

• follow engine:

– it follows the user movements in order to calculate traffic in real time;

• routes interpreter:

– it converts the route elaboration engine output, in order to show it to the final user;