LGPL is cat X - it wouldn’t be something Apache Sedona should distribute or
depend on
https://www.apache.org/legal/resolved.html#optional
On Thu, Feb 11, 2021 at 11:59 PM Jia Yu wrote:
> OSGeos LocationTech owns GeoTools. I am thinking whether I should have my
> wrapper on Maven Central to
OSGeos LocationTech owns GeoTools. I am thinking whether I should have my
wrapper on Maven Central to bring those Sedona required GeoTools jars to
Maven Central. Since it is LGPL, it might be OK to do so.
On Thu, Feb 11, 2021 at 5:18 PM Felix Cheung wrote:
> Who owns or manages GeoTools if it
Who owns or manages GeoTools if it is LGPL?
On Thu, Feb 11, 2021 at 12:01 PM Jia Yu wrote:
> Pawel,
>
> Python-adapter module is always being used by users. But it does not come
> with GeoTools. To use it, users have to (1) compile the source code of
> Python-adapter, or (2) add GeoTools
Pawel,
Python-adapter module is always being used by users. But it does not come
with GeoTools. To use it, users have to (1) compile the source code of
Python-adapter, or (2) add GeoTools coordiantes from OSGEO repo via
config(""), or (3) download and copy GeoTools jars to SPARK_HOME/jars/
The
I think that we can make it work on Databricks without any changes.
After creating a cluster on Databricks, the user can install the geotools
packages and provide the osego *(or any other repo) explicitly.*
As you can see in the picture:
[image: image.png]
I can provide the details on how to
Hi folks,
As you can see from the recent discussion in the mailing list
<[Bug][Python] Missing Java class>, in Sedona 1.0.0, because those LGPL
GeoTools jars are not on Maven Central (only in OSGEO repo), Databricks
cannot get GeoTools jars.
I believe this will cause lots of trouble to our
