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/01 11:17] ezimanyi [Projects in Mobility Databases] |
teaching:projh402 [2020/10/01 11:21] ezimanyi [Projects in Mobility Databases] |
||
|---|---|---|---|
| Line 11: | Line 11: | ||
| Towards filling this gap, our group is building the [[https://github.com/MobilityDB/MobilityDB|MobilityDB]] system. It builds on PostGIS, which is a spatial database extension of PostgreSQL. MobilityDB extends the type system of PostgreSQL and PostGIS with ADTs for representing moving object data. It defines, for instance, the tgeompoint type for representing a time dependant geometry point. MobilityDB types are well integrated into the platform, to achieve maximal reusability, hence a mainstream development. For instance, the tgeompoint type builds on the PostGIS geometry(point) type. Similarly MobilityDB builds on existing operations, indexing, and optimization framework. | Towards filling this gap, our group is building the [[https://github.com/MobilityDB/MobilityDB|MobilityDB]] system. It builds on PostGIS, which is a spatial database extension of PostgreSQL. MobilityDB extends the type system of PostgreSQL and PostGIS with ADTs for representing moving object data. It defines, for instance, the tgeompoint type for representing a time dependant geometry point. MobilityDB types are well integrated into the platform, to achieve maximal reusability, hence a mainstream development. For instance, the tgeompoint type builds on the PostGIS geometry(point) type. Similarly MobilityDB builds on existing operations, indexing, and optimization framework. | ||
| - | MobilityDB supports SQL as query interface. Currently it is quite rich in terms of types and functions. It is incubated as community project in OSGeo [[OSGeo|https://www.osgeo.org/projects/mobilitydb/]], which certifies high technical quality. | + | MobilityDB supports SQL as query interface. Currently it is quite rich in terms of types and functions. It is incubated as community project in OSGeo [[https://www.osgeo.org/projects/mobilitydb/|OSGeo]], which certifies high technical quality. |
| The following project ideas contribute to different parts of MobilityDB. They all constitute innovative development, mixing both research and development. They hence will help developing the student skills in: | The following project ideas contribute to different parts of MobilityDB. They all constitute innovative development, mixing both research and development. They hence will help developing the student skills in: | ||
| Line 18: | Line 18: | ||
| * Understanding the architecture of extensible databases, in this case PostgreSQL. | * Understanding the architecture of extensible databases, in this case PostgreSQL. | ||
| * Writing open source software. | * Writing open source software. | ||
| + | |||
| ==== Visualization Moving Objects on the Web ==== | ==== Visualization Moving Objects on the Web ==== | ||
| + | |||
| + | <TBD> | ||
| + | |||
| ==== Implementing TSBS on MobilityDB ==== | ==== Implementing TSBS on MobilityDB ==== | ||
| which includes devising a spatio-temporal bucket function equivalent to time_bucket from TimescaleDB. | which includes devising a spatio-temporal bucket function equivalent to time_bucket from TimescaleDB. | ||
| + | |||
| + | <TBD> | ||
| + | |||
| ==== Distributed Moving Object Database on Amazon AWS ==== | ==== Distributed Moving Object Database on Amazon AWS ==== | ||
| Line 28: | Line 35: | ||
| MobilityDB is engineered as an extension of PostgreSQL. AWS supports PostgreSQL databases in Amazon RDS for PostgreSQL and in Amazon Aurora. The goal of this project is to integrate MobilityDB with these products. The key outcomes are a comprehensive assessment of which MOD API can/cannot be distributed, and an assessment of the performance gain. These outcomes should serve as a base for a thesis project to achieve effective integration. | MobilityDB is engineered as an extension of PostgreSQL. AWS supports PostgreSQL databases in Amazon RDS for PostgreSQL and in Amazon Aurora. The goal of this project is to integrate MobilityDB with these products. The key outcomes are a comprehensive assessment of which MOD API can/cannot be distributed, and an assessment of the performance gain. These outcomes should serve as a base for a thesis project to achieve effective integration. | ||
| + | |||
| ==== Distributed Moving Object Database on MS Azure ==== | ==== Distributed Moving Object Database on MS Azure ==== | ||
| Line 35: | Line 43: | ||
| ==== Map-matching as a Service ==== | ==== Map-matching as a Service ==== | ||
| When GPS tracks typically contain errors, because the GPS receiver | When GPS tracks typically contain errors, because the GPS receiver | ||
| + | |||
| ==== Geospatial Trajectory Data Cleaning ==== | ==== Geospatial Trajectory Data Cleaning ==== | ||
| + | |||
| ==== Geospatial Trajectory Similarity Measure ==== | ==== Geospatial Trajectory Similarity Measure ==== | ||
| + | |||
| ==== Spatiotemporal k-Nearest Neighbour (kNN) Queries ==== | ==== Spatiotemporal k-Nearest Neighbour (kNN) Queries ==== | ||
| + | |||