[postgis-devel] PostGIS 3 and MobilityDB
Esteban Zimanyi
esteban.zimanyi at ulb.be
Sat Jul 10 05:36:31 PDT 2021
Dear Paul
Since you mention geodetic functions, we implemented a year ago some
geography functions to be submitted as PR to PostGIS but we haven't had
time to do it. These functions are geography_closestpoint,
geography_shortestline, geography_line_substring,
geography_line_interpolate_point, and geography_line_locate_point. You can
find these functions at the following address
https://github.com/MobilityDB/MobilityDB/blob/develop/point/src/geography_functions.c
It may be useful to have such functionality in PostGIS.
Regards
Esteban
On Fri, Jul 9, 2021 at 5:54 PM Paul Ramsey <pramsey at cleverelephant.ca>
wrote:
> I really wonder whether just copying over the liblwgeom functions they
> really really need into their own code base isn't the most straight-forward
> thing. Once that's done the only real point-of-integration is the
> serialization, and that only changes once every 10 years, so... keeping an
> eye on the postgis serialization code to watch for changes once a year is a
> relatively small price to pay.
>
> Everything else is just "useful functionality that happens to be in
> postgis", and can probably just be copied across and given a new function
> name prefix to avoid collisions. At that point they are stuck maintaining
> their copy, but it's not like postgis is some massively churning code base
> at this point. Core lwgeom stuff changes infrequently at most. You might
> see some re-writes in geodetic from me, but that wouldn't invalidate the
> current code if they had a working copy.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20210710/79b83030/attachment-0001.html>
More information about the postgis-devel
mailing list