Context Navigation

Changes between Initial Version and Version 1 of Ticket #4747, comment 6

-              initial
+              v1
 And all this only to load the data of a single day before analyzing every couple of trips in the data set, synchronizing the two trips to obtain 2 trips of 4K + 4K synchronized points and
 * call  4K + 4K times the function ST_Distance for each couple of trips.
 As you can imagine, for such kind of manipulations we really need to access directly the liblwgeom library. The situation is much more challenging for aviation data obtained from, e.g.,
 https://developer.laminardata.aero/
+As you can imagine, for such kind of manipulations we really need to access directly the liblwgeom library. The situation is much more challenging for analyzing aviation data obtained from, e.g.,
+https://developer.laminardata.aero/ since in this case we need to do the computations using the PostGIS geography type and its associated functions.
 For these reasons we really need to collaborate with you in order to connect as efficiently as possible MobilityDB and PostGIS. Indeed, the overall philosophy of MobilityDB is take care of the temporal aspects and completely delegate the spatial manipulation to PostGIS. Our role is then to understand at which timestamps the current value of a spatial function may change and call PostGIS to compute the function at those timestamps.