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


Ignore:
Timestamp:
08/26/20 02:18:51 (4 years ago)
Author:
ezimanyi

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #4747, comment 6

    v3 v4  
    2121* call  4K + 4K times the function ST_Distance for each couple of trips.
    2222As 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.,
    23 https://developer.laminardata.aero/ since in this case we need to do the computations using the PostGIS geography type and its associated functions.
     23https://developer.laminardata.aero/ since in this case we need to do the computations using the PostGIS geography type and its associated functions. For this case we needed to implement the functions ST_ClosestPoint, ST_ShortestLine, ST_LineSubstring, ST_LineInterpolatePoint, and ST_LineLocatePointfunctions for geography
     24https://github.com/MobilityDB/MobilityDB/blob/develop/point/src/geography_functions.c
     25and we plan to submit a PR to PostGIS soon.
     26
    2427
    2528For 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.