You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@calcite.apache.org by "Julian Hyde (Jira)" <ji...@apache.org> on 2022/09/02 20:56:00 UTC

[jira] [Resolved] (CALCITE-4294) Use JTS rather than ESRI as the underlying library for geospatial (ST_) functions

     [ https://issues.apache.org/jira/browse/CALCITE-4294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Julian Hyde resolved CALCITE-4294.
----------------------------------
    Resolution: Fixed

Fixed in [250d13c5|https://github.com/apache/calcite/commit/250d13c566913ba541ddd7ac4c4443a11a1a976b]; thanks, [~bchapuis]!

> Use JTS rather than ESRI as the underlying library for geospatial (ST_) functions
> ---------------------------------------------------------------------------------
>
>                 Key: CALCITE-4294
>                 URL: https://issues.apache.org/jira/browse/CALCITE-4294
>             Project: Calcite
>          Issue Type: Bug
>          Components: spatial
>            Reporter: Julian Hyde
>            Assignee: Bertil Chapuis
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.32.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> The geospatial functions are currently implemented using the ESRI library. We should consider using JTS instead. AT the time we started work on geospatial the JTS did not have a suitable license, but this is no longer the case. I gather that JTS is a superior library.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)