[
https://issues.apache.org/jira/browse/CALCITE-1861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17203746#comment-17203746
]
Julian Hyde commented on CALCITE-1861:
--------------------------------------
[~jnh5y] wrote:
{code:java}
Lemme know if there's anything that'd make JTS or SFCurve a fit for Calcite!
{code}
I think JTS is already a good fit for Calcite. The license was unsuitable when
we first evaluated it, but the license has since changed.
The main thing keeping us on ESRI is inertia. If we see significant usage of
Calcite's geospatial functions, and incoming contributions, we will seriously
consider switching. I have logged CALCITE-4294 to track.
> Spatial index, based on Hilbert space-filling curve
> ---------------------------------------------------
>
> Key: CALCITE-1861
> URL: https://issues.apache.org/jira/browse/CALCITE-1861
> Project: Calcite
> Issue Type: Improvement
> Components: spatial
> Reporter: Atri Sharma
> Assignee: Julian Hyde
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.26.0
>
> Time Spent: 2h 50m
> Remaining Estimate: 0h
>
> Many Calcite users, like Phoenix and Flink can benefit from support of
> Spatial indexes.
> See:
> http://revenant.ca/www/postgis/workshop/indexing.html
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
