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/09/14 20:08] svsummer |
teaching:projh402 [2020/09/30 21:04] mahmsakr [Projects in Mobility Databases] |
||
|---|---|---|---|
| Line 4: | Line 4: | ||
| ===== Course objective ===== | ===== Course objective ===== | ||
| The course PROJ-H-402 is managed by Dr. Mauro Birattari. Please refer to the course description page http://iridia.ulb.ac.be/proj-h-402/index.php/Main_Page for the rules concerning the project. What follows is a list of project proposals supervised by academic members of CoDE. | The course PROJ-H-402 is managed by Dr. Mauro Birattari. Please refer to the course description page http://iridia.ulb.ac.be/proj-h-402/index.php/Main_Page for the rules concerning the project. What follows is a list of project proposals supervised by academic members of CoDE. | ||
| + | |||
| + | ===== Projects in Mobility Databases ===== | ||
| + | |||
| + | Mobility databases (MOD) are database systems that can store and manage moving object geospatial trajectory data. A moving object is an object that changes its location over time (e.g., a car driving on the road network). Using a variety of sensors, the location tracks of moving objects can be recorded in digital formats. A MOD, then, helps storing and querying such data. A couple of prototype systems have been proposed by research groups. Yet, a mainstream system is by far still missing. By mainstream we mean that the development builds on widely accepted tools, that are actively being maintained and developed. A mainstream system would exploit the functionality of these tools, and would maximize the reuse of their ecosystems. As a result, it becomes more closer to end users, and easily adopted in the industry. | ||
| + | |||
| + | Towards filling this gap, our group is building the MobilityDB system [[https://github.com/MobilityDB/MobilityDB|https://github.com/MobilityDB/MobilityDB]]. 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 [[https://www.osgeo.org/projects/mobilitydb/|https://www.osgeo.org/projects/mobilitydb/]], 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: | ||
| + | |||
| + | * Understanding the theory and the implementation of moving object databases. | ||
| + | * Understanding the architecture of extensible databases, in this case PostgreSQL. | ||
| + | * Writing open source software. | ||
| ===== Project proposals ===== | ===== Project proposals ===== | ||