This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
teaching:projh402 [2020/10/13 09:07] mahmsakr [Map-matching as a Service] |
teaching:projh402 [2020/10/22 14:18] ezimanyi [Implementing TSBS on MobilityDB] |
||
|---|---|---|---|
| Line 27: | Line 27: | ||
| However, these platforms are used for static spatial data and are unable to cope with moving objects. The goal of the project is to extend one of these platforms with spatio-temporal data types in order to be able to display animated maps. | However, these platforms are used for static spatial data and are unable to cope with moving objects. The goal of the project is to extend one of these platforms with spatio-temporal data types in order to be able to display animated maps. | ||
| - | {{ :teaching:trips2.gif?nolink |}} | + | {{:teaching:trips2.gif?direct|}} |
| + | |||
| + | Animated visualization of car trajectories | ||
| + | |||
| + | **Status**: taken | ||
| ===== Implementing TSBS on MobilityDB ===== | ===== Implementing TSBS on MobilityDB ===== | ||
| Line 35: | Line 39: | ||
| The project consists in implementing a multidimensional generalization of the time_bucket function that allows the user to partition the spatial and/or temporal domain of a table in units (or tiles) that can be used for aggregating data. Then, the project consists of performing a benchmark comparison of TimescaleDB and MobilityDB. | The project consists in implementing a multidimensional generalization of the time_bucket function that allows the user to partition the spatial and/or temporal domain of a table in units (or tiles) that can be used for aggregating data. Then, the project consists of performing a benchmark comparison of TimescaleDB and MobilityDB. | ||
| + | |||
| + | **Status**: taken | ||