Changes between Version 2 and Version 3 of Ticket #4747, comment 6


Ignore:
Timestamp:
08/26/20 01:55:58 (4 years ago)
Author:
ezimanyi

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #4747, comment 6

    v2 v3  
    2323https://developer.laminardata.aero/ since in this case we need to do the computations using the PostGIS geography type and its associated functions.
    2424
    25 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.
     25For 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 efficiently understand at which timestamps the current value of a spatial function may change and call PostGIS to compute the function at those timestamps.