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:mfe:is [2019/02/18 15:39] svsummer |
teaching:mfe:is [2019/04/30 15:35] ezimanyi [A Generic Similarity Measure For Symbolic Trajectories] |
||
|---|---|---|---|
| Line 18: | Line 18: | ||
| ===== Master Thesis in Collaboration with Euranova ===== | ===== Master Thesis in Collaboration with Euranova ===== | ||
| - | Our laboratory performs collaborative research with Euranova R&D (http://euranova.eu/). The list of subjects proposed for this year by Euranova can be found {{:teaching:mfe:euranova_masterthesis_2017.pdf|here}}. | + | Our laboratory performs collaborative research with Euranova R&D (http://euranova.eu/). The list of subjects proposed for this year by Euranova can be found [[https://research.euranova.eu/wp-content/uploads/proposals-thesis-2019.pdf|here]]. |
| Line 120: | Line 120: | ||
| **Status**: available | **Status**: available | ||
| + | |||
| + | |||
| + | ========================================== | ||
| + | The research in moving object databases MOD has been active since the early 2000. Many individual works have been proposed to deal with the different aspects of data modeling, indexing, operations, etc. A couple of prototypes have also been proposed, some of which are still active in terms of new releases. Yet, a mainstream system is by far still missing. Existing prototypes are merely research. 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. | ||
| + | |||
| + | In our group, we are in the course of building MobilityDB, a mainstream MOD. 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 tfloatp for representing a time dependant float, and the tgeompoint 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 tfloatp builds on the PostgreSQL doubleprecision type, and the tgeompoint build on the PostGIS geometry(point) type. Similarly MobilityDB builds on existing operations, indexing, and optimization framework. | ||
| + | |||
| + | This is all made accessible via the SQL query interface. Currently MobilityDB is quite rich in terms of types and functions. It can answer sophisticated queries in SQL. | ||
| + | |||
| + | An important, and still missing, piece of MobilityDB is Java JDBC driver, that will allow Java programs to establish connections with MobilityDB, and store and retrieve data. This thesis is about developing such a driver. As all other components of PostgreSQL, its JDBC driver is also extensible. This documentation gives a good explanation of the driver and the way it can be extended: | ||
| + | https://jdbc.postgresql.org/documentation/head/index.html | ||
| + | It is also helpful to look at the driver extension for PostGIS: | ||
| + | https://github.com/postgis/postgis-java | ||
| + | As MobilityDB build on top of PostGIS, the Java driver will need to do the same, and build on top of the PostGIS driver. Mainly the driver will need to provide Java classes to represent all the types of MobilityDB, and access the basic properties. This thesis project 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. | ||