[
https://issues.apache.org/jira/browse/CALCITE-5399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17638793#comment-17638793
]
Julian Hyde commented on CALCITE-5399:
--------------------------------------
It seems to me that there is a good short-term solution and a better long-term
solution. The short-term solution is, as I described, to make Proj4j an
optional dependency. It doesn't seem that reflection is needed just yet. But
there should be a clear entry point so that if the user tries to use
ProjectionTransform in any way (e.g. if they call the ST_Transform function)
the user should get a clear error message about what has gone wrong and what
they need to do.
A better long term solution is to let a library such as SIS or Proj4j be the
switch that controls whether the advanced functionality is available.
I logged [PROJ4J-90|https://github.com/locationtech/proj4j/issues/90], with two
suggestions: (1) that Proj4j factors out the data set and operates at reduced
functionality if it is not present, (2) Proj4j implements GeoAPI interfaces, as
[~desruisseaux] suggested above. Either of those would allow Calcite to offer
Proj4j functionality to users while also getting the necessary consent.
> Proj4j license is not compatible with Apache
> --------------------------------------------
>
> Key: CALCITE-5399
> URL: https://issues.apache.org/jira/browse/CALCITE-5399
> Project: Calcite
> Issue Type: Bug
> Components: core
> Affects Versions: 1.32.0
> Reporter: Bertil Chapuis
> Assignee: Bertil Chapuis
> Priority: Major
> Fix For: 1.33.0
>
>
> As explained by [~desruisseaux] in [1], despite being released with an Apache
> compatible license, Proj4j is a problematic dependency. The EPSG codes used
> by Proj4j come with restrictive terms of use [2] and we should find an
> alternative.
> [1] [https://lists.apache.org/thread/2g6j1jx7q5l1sx4mfp1w29obgnvrnvq5]
> [2] [https://epsg.org/terms-of-use.html]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
