Presentation of ST-Toolkit: a Framework for trajectory Data warehousing short paper published in AGILE 2011, Utrecht 20th April 2011.

1. ST-Toolkit: a Framework for Trajectory Data Warehousing Authors AGILE 2011 Utrecht – 20/04/2011 Simone Campora Jose Fernandes De Macedo Laura Spinsanti

3. Why Trajectory Data Warehousing The motivation behind Trajectory Data Warehouses (TrDWs) is to transform raw moving objects' trajectories to valuable information that can be exploited for decision-making purposes in ubiquitous applications, such as location-based services, traffic control management, etc using an OLAP (or STOLAP) fashion.

5. Related Work Spatio-Temporal DBMS Secondo (Güting et al .) Hermes (Pelekis et al .) Trajectory Data Warehouses Università di Venezia (Orlando et al .)

6. Why Trajectory Data Warehousing Solution Comparison

8. Trajectory Extraction

11. Generic Data Warehouse Architecture

12. Example: Data Warehouse Design First Step Data are Streamed From Raw Datasets into Primary Memory Second Step Java Objects are Buffered and Istantiated Asychronously Sent to the RDBMS Third Step Java Objects are Persisted into RDBM and properly Indexed Fourth Step The MultiDimensional Model is istantiated from RDBMS data sources + DW Metedata Definitions

16. Presence Measure Validation Presence Measure: Problem: how to aggregates the number of trajectories within a hierarchical fully-geometric dimension avoiding the double-counting problem ?

17. Some Experiments Presence Measure: understanding the problem 1 1 1 1 0 1 1

18. Presence Measure Validation Solution : define an aggregation algorithm that can use spatial operators! Our application can define SQL injections for spatial-aggregates : String sqlExpression = "case when get_trj_space_area_intersections(trdw_episode_facts.geom) > 0 then ceil(1/get_trj_space_area_intersections(trdw_episode_facts.geom)) else 0 end "; Measure presence = new VirtualMeasure(“Trj Presence Measure", factTable, “presence", sqlExpression);

19. Presence Measure Validation Results on 260 Trajectories subset Milano – Arese: 2 Milano – Assago: 2 Milano – Bollate: 1 Milano – Bresso: 2 Milano – Buccinasco: 2 Milano - Cesano Boscone: 6 Milano – Cormano: 2 Milano – Corsico: 2 Milano - Cusano Milanino: 2 Milano – Gaggiano: 2 Milano - Locate di Triulzi: 2 Milano – Milano: 186 Milano – Novate: 2 Milano – Opera: 2 Milano – Pero: 2 Milano - Peschiera Borromeo: 2 Milano – Rho: 14 Milano – Rozzano: 2 Milano - San Donato Milanese: 1 Milano - San Giuliano Milanese: 6 Milano – Segrate: 2 Milano - Settimo Milanese: 8 Milano - Trezzano Rosa: 4 Milano - Zibido San Giacomo: 2 Monza and Brianza – Mezzano: 2 Milano: 258 Monza and Brianza: 2 Lombardia: 260

21. Thanks for your attention Any Question? Suggestions? Comments? For more information: http://st-toolkit.sourceforge.net/ Thanks for the attention