[
https://issues.apache.org/jira/browse/CALCITE-4294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17599713#comment-17599713
]
Bertil Chapuis edited comment on CALCITE-4294 at 9/2/22 9:05 PM:
-----------------------------------------------------------------
Ok, my future plan is to use calcite in baremaps to produce vector tiles.
Having JTS was a first step, but I'm interested in contributing additional
functions. Should I create one issue per function? Some of them may be quite
significant (e.g. ST_AsMVT, ST_AsMVTGeom, ST_TileEnvelope).
[https://github.com/baremaps/baremaps]
[https://demo.baremaps.com/]
was (Author: bchapuis):
Ok, my future plan is to use calcite in baremaps to produce vector tiles.
Having JTS was a first step, but I'm interested in contributing additional
functions. Should I create one issue per function? Some of them may be quite
significant (e.g. ST_AsMVT, ST_AsMVTGeom, ST_TileEnvelope).
[https://github.com/baremaps/baremaps|https://github.com/baremaps/baremaps)]
[https://demo.baremaps.com/|https://demo.baremaps.com/)]
> Use JTS rather than ESRI as the underlying library for geospatial (ST_)
> functions
> ---------------------------------------------------------------------------------
>
> Key: CALCITE-4294
> URL: https://issues.apache.org/jira/browse/CALCITE-4294
> Project: Calcite
> Issue Type: Bug
> Components: spatial
> Reporter: Julian Hyde
> Assignee: Bertil Chapuis
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.32.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The geospatial functions are currently implemented using the ESRI library. We
> should consider using JTS instead. AT the time we started work on geospatial
> the JTS did not have a suitable license, but this is no longer the case. I
> gather that JTS is a superior library.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
