Description
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.
Attachments
Issue Links
- is related to
-
CALCITE-4294 Use JTS rather than ESRI as the underlying library for geospatial (ST_) functions
- Closed