[postgis-devel] PostGIS 3 and MobilityDB

[Esteban Zimanyi]

Alas this would not be a solution for at least two reasons
* This would require a HUGE work to change all over the MobilityDB code
<liblwgeom_function> -> <librttopo_function>
* Not all liblwgeom functions are implemented in librttopo, for example the
azimuth_pt_pt function that I have used in the examples of this thread.



On Sat, Jul 3, 2021, 10:17 Sebastiaan Couwenberg <sebastic at xs4all.nl> wrote:

> On 7/3/21 9:49 AM, Esteban Zimanyi wrote:
> > We will closely follow any futur change in liblwgeom's public API and
> > perform any required adaptation in MobilityDB code.
>
> Is rttopo [0] not a suitable alternative to lwgeom?
>
> spatialite already uses it instead of lwgeom.
>
> [0] https://git.osgeo.org/gitea/rttopo/librttopo
>
> Kind Regards,
>
> Bas
>
> --
>  GPG Key ID: 4096R/6750F10AE88D4AF1
> Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1
> _______________________________________________
> postgis-devel mailing list
> postgis-devel at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/postgis-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20210705/35a8ef3c/attachment.html>