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 [2020/10/01 10:54] mahmsakr |
teaching:projh402 [2020/10/01 11:05] mahmsakr |
||
|---|---|---|---|
| Line 34: | Line 34: | ||
| MobilityDB is engineered as an extension of PostgreSQL. MS Azure supports distributed PostgreSQL databases using [[Citus|https://www.citusdata.com/]]. We have made successful tests for integrating MobilityDB and Citus on a local cluster. The goal of this project is to repeat this work on MS Azureintegrate 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. MS Azure supports distributed PostgreSQL databases using [[Citus|https://www.citusdata.com/]]. We have made successful tests for integrating MobilityDB and Citus on a local cluster. The goal of this project is to repeat this work on MS Azureintegrate 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. | ||
| ==== Map-matching as a Service ==== | ==== Map-matching as a Service ==== | ||
| + | When GPS tracks typically contain errors, because the GPS receiver | ||
| ==== Geospatial Trajectory Data Cleaning ==== | ==== Geospatial Trajectory Data Cleaning ==== | ||