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

["Bertil Chapuis (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CALCITE-4294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17612050#comment-17612050 ] 

Bertil Chapuis commented on CALCITE-4294:
-----------------------------------------

[~dsmiley] [~julianhyde] Given the popularity of JTS and Proj4j, the main problem I see is that other projects may include different versions in their classpath. Something we should also consider is that more advanced functions such as `ST_AsMVT` may require additional dependencies. Finally, it may be nice to have a schema factory dedicated to creating schemas with spatial features. Notice that in postgres, you don't have spatial features without explicitly creating an extension (`CREATE EXTENSION postgis;`)

> 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)