[
https://issues.apache.org/jira/browse/CALCITE-1861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17203270#comment-17203270
]
Jim Hughes commented on CALCITE-1861:
-------------------------------------
[~julianhyde] glad you found SFCurve! (I'm involved with SFCurve, JTS, and
GeoMesa.)
Out of curiosity, is there any reason you copied classes from SFCurve rather
than depending on it? Also, in addition to being relicensed, Martin Davis has
just finished a body of work to improve overlay operations in JTS
([http://lin-ear-th-inking.blogspot.com/2020/05/jts-overlay-next-generation.html]
[http://lin-ear-th-inking.blogspot.com/2020/06/jts-overlayng-noding-strategies.html]
[http://lin-ear-th-inking.blogspot.com/2020/06/jts-overlayng-tolerant-topology.html]
)
Lemme know if there's anything that'd make JTS or SFCurve a fit for Calcite!
> 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)
