[
https://issues.apache.org/jira/browse/CALCITE-1968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16141961#comment-16141961
]
Julian Hyde edited comment on CALCITE-1968 at 8/25/17 8:57 PM:
---------------------------------------------------------------
Work in progress: https://github.com/julianhyde/calcite/tree/1968-spatial
was (Author: julianhyde):
Work in progress: https://github.com/julianhyde/calcite/tree/1861-spatial
> Support OpenGIS Simple Feature Access SQL
> -----------------------------------------
>
> Key: CALCITE-1968
> URL: https://issues.apache.org/jira/browse/CALCITE-1968
> Project: Calcite
> Issue Type: Bug
> Reporter: Julian Hyde
> Assignee: Julian Hyde
>
> Support [OpenGIS Simple Feature Access
> SQL|http://www.opengeospatial.org/standards/sfs]. This is standard core
> functionality for spatial/geographical/geometry data, implemented by PostGIS
> and others.
> It basically consists of a {{GEOMETRY}} data type and about 150 functions
> whose names start with 'ST_', for example {{ST_GeomFromText}} and
> {{ST_Distance}}. [H2 GIS|http://www.h2gis.org/docs/dev/functions/] has a good
> reference. (Look for the functions labeled 'OpenGIS 1.2.1'.)
> Adds a {{SqlConformance.allowGeometry()}} method to allow people to
> enable/disable this functionality.
> First commit will probably add a dozen or so functions, backed by a library
> such as [ESRI Geometry API|https://github.com/Esri/geometry-api-java]. I'd
> appreciate help implementing the rest.
> Spatial indexes are covered by CALCITE-1861 and are out of scope of this
> case. So with this feature, spatial queries will work, but predicates will be
> applied row-by-row.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
