[
https://issues.apache.org/jira/browse/CALCITE-5399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17641165#comment-17641165
]
Martin Desruisseaux commented on CALCITE-5399:
----------------------------------------------
Yes, if EPSG data are removed from PROJ4J "main" JAR file, I think that the
result is clear of licensing issue. I just wonder,
[PROJ-92|https://github.com/locationtech/proj4j/pull/92] suggests that those
CSV files were not used at all. In which case I wonder where PROJ4J takes its
data when e.g. "EPSG:3395" is requested?
The {{org.opengis}} package name conflict is indeed an orthogonal issue. Email
has been sent. With both OGC director and OSGeo board who accepted to look at
this issue, I hope that some resolution may finally be reachable.
> 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: Blocker
> Labels: pull-request-available
> Fix For: 1.33.0
>
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> 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)
