[
https://issues.apache.org/jira/browse/CALCITE-2758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Hyde resolved CALCITE-2758.
----------------------------------
Fix Version/s: 1.32.0
Resolution: Duplicate
> Replace ESRI based Geofunctions with LocationTech (JTS + proj4j)
> -----------------------------------------------------------------
>
> Key: CALCITE-2758
> URL: https://issues.apache.org/jira/browse/CALCITE-2758
> Project: Calcite
> Issue Type: Improvement
> Components: core
> Affects Versions: 1.17.0
> Reporter: Jonathan Mayer
> Priority: Minor
> Fix For: 1.32.0
>
>
> I will be working on this functionality outside the calcite repo ( for now).
> The project's current location is [https://github.com/jonrmayer/geofunctions]
>
> It is intended to be a like-for-like replacement of the existing
> calcite-core/runtime/GeoFunctions.java file.
>
> With some minor edits to calcite-master pom /calcite-core pom - it is
> feasible to drop this in as a replacement - adding the calcite imports etc to
> the top of the file.
>
> Tests however will be a problem - eg. spatial.iq will no longer be relevant.
> ESRI outputs geometries to JSON whereas JTS outputs WKT - this will need to
> be rewritten.
>
> My current plan is to focus on implementing as many functions as possible
> with basic tests and then to improve on the (very) basic Maven testing before
> letting anyone know that I am reasonably happy.
>
> I should imagine that spatial.iq will have to wait a fair while - I will need
> it to test Geometry Collections for eg ST_DWithin/ST_Collect etc and hope
> that the maven test are enough from a confidence perspective.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
