This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | Next revision Both sides next revision | ||
|
teaching:projh402 [2021/08/31 18:47] ezimanyi [Symbolic trajectories] |
teaching:projh402 [2021/08/31 18:54] ezimanyi [Trajectory Data Warehouses] |
||
|---|---|---|---|
| Line 73: | Line 73: | ||
| ===== Trajectory Data Warehouses ===== | ===== Trajectory Data Warehouses ===== | ||
| + | Mobility data warehouses are data warehouses that keep location data for a set of moving objects. You can refer to the article [1] for more information about the subject. The project consists in building a mobility data warehouse for ship trajectories on MobilityDB | ||
| - | Symbolic trajectories enable to attach semantic information to geometric trajectories. Essentially, symbolic trajectories are just time-dependent labels representing, for example, the names of roads traversed obtained by map matching, transportation modes, speed profile, cells of a cellular network, behaviors of animals, cinemas within 2km distance, and so forth. Symbolic trajectories can be combined with geometric trajectories to obtain annotated trajectories. | + | The input data comes from the Danish Maritine Authority [2]. To download the data you must |
| + | use an FTP client (such as FileZilla) since the link Get historical AIS data does not work with | ||
| + | common Web browsers such as Chrome. Follow the instructions in Chapter 1 of | ||
| + | the MobilityDB Workshop [3] to load the data into MobilityDB. | ||
| - | The goal of this project is to explore how to implement symbolic trajectories in MobilityDB. This implementation will be based on the ttext (temporal text) data type implemented in MobilityDB and will explore how to extend it with regular expressions. This extension can be inspired from the [[https://www.postgresql.org/docs/13/functions-json.html|jsonb]] data type implemented in PostgreSQL. | + | You must implement a comprehensive data warehouse application. For this, you will perform in particular the following steps. |
| + | * Define a conceptual multidimentional schema for the application. | ||
| + | * Translate the conceptual model into a relational data warehouse. | ||
| + | * Implement the relational data warehouse in MobilityDB. | ||
| + | * Implement analytical queries based on the queries proposed in [1]. | ||
| Links: | Links: | ||
| - | * {{:teaching:symbolic_trajectories.pdf|}} | + | |
| + | [1] A. Vaisman and E. Zimányi. Mobility data warehouses. ISPRS International Journal of Geo- | ||
| + | Information, 8(4), 2019. https://www.mdpi.com/2220-9964/8/4/170. | ||
| + | [2] Danish Maritine Authority, Historical AIS data https://www.dma.dk/SikkerhedTilSoes/Sejladsinformation/AIS/Sider/default.aspx | ||
| + | [3] MobilityDB Workshop: https://github.com/MobilityDB/MobilityDB-workshop | ||