MobilityDB MobilityDB Versions Save

Changelog

• Allow MobilityDB and MEOS to run on ARM64 architecture (by @Diviloper, @mschoema in https://github.com/MobilityDB/MobilityDB/pull/461, https://github.com/MobilityDB/MobilityDB/pull/463, https://github.com/MobilityDB/MobilityDB/pull/465, https://github.com/MobilityDB/MobilityDB/pull/469, https://github.com/MobilityDB/MobilityDB/pull/472)
• Fix bugs in ever/always spatial relationships (by @estebanzimanyi in https://github.com/MobilityDB/MobilityDB/pull/467, https://github.com/MobilityDB/MobilityDB/pull/468)
• Fix compilation issues when using Postgres 12 (by @mschoema in https://github.com/MobilityDB/MobilityDB/pull/470)

Full Changelog: https://github.com/MobilityDB/MobilityDB/compare/v1.1.0...v1.1.1

MobilityDB 1.1 Feature Highlights

MobilityDB 1.1 is a major revision with respect to the initial version 1.0. The most important change in version 1.1 was to extract the core functionality for temporal and spatiotemporal data management from MobilityDB into the Mobility Engine Open Source (MEOS) C library. In this way, the same functionality provided by MobilityDB in a database environment is available in a C program to be used, for example, in a streaming environment.

To generate the MEOS library it suffices to pass the additional parameter -DMEOS=on to cmake.

Several changes were necessary with respect to MobilityDB version 1.0 to enable the above. An important one was the definition of new data types span and spanset, which provide similar functionality to the PostgreSQL data types range and multirange but can also be used in various programming environments regardless of PostgreSQL. These are template types, which means that they are containers of other types, in a similar way as lists and arrays contains values of other types. Furthermore, a new template data type set was also added. Therefore, the types timestampset, period, and periodset in version 1.0 are replaced by the types tstzset, tstzspan, and tstzspanset in version 1.1.

MobilityDB 1.1 also includes several bugfixes and performance improvements compared to 1.0. Finally, the API of MEOS and MobilityDB was streamlined to improve usability and to facilitate the other bindings that are currently being developed.

For additional information regarding MobilityDB and MEOS, refer to the pregenerated documentation

This release candidate fixes several bugs detected in release candidate 1.

Main changes w.r.t rc1:

• Several bugfixes
• API changes: use camelCase for all SQL functions and allow calls to atGeometryTime without Z dimension
• Hide postgis and postgres functions in the meos.h library. This allows PyMEOS to be used in QGIS without crashing

First release candidate for MobilityDB 1.1

Pre-release for MobilityDB 1.1

Pre-release for MobilityDB 1.1

This release marks the first official release of MobilityDB

A non-exhaustive list of changes:

• Multiversion (PostgreSQL 10 ->14, PostGIS 2.5->3.2) and multiplatform (macOS, Windows in the future) capabilities.
• Improving the lifting infrastructure (i.e. how to "temporalize" a function, see https://github.com/MobilityDB/MobilityDB/wiki/Lifting-a-Function-in-MobilityDB).
• Considerable speed up improvements, the last one related to multidimensional tiling now optimized with a custom bit matrix data structure.
• Addition of the asMVTGeom function, used for visualizing numerous trajectories using vector tiles.