[
https://issues.apache.org/jira/browse/CALCITE-4294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584026#comment-17584026
]
Julian Hyde commented on CALCITE-4294:
--------------------------------------
No urgency (enjoy FOSS4G!) and don't worry about producing a detailed list of
differences. A rough list will suffice. People who need the full picture can
look at the difference in the tests.
I suspect most of the changes either won't be noticed by our users or will be
seen as improvements. If changes to a particular ST_ function are breaking,
people can log a bug, revert to Calcite 1.31, and we can add logic to that
particular function to restore the old behavior in 1.33.
> 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
> Fix For: 1.32.0
>
>
> 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)
