You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sis.apache.org by Ryan McKinley <ry...@gmail.com> on 2012/03/05 21:09:52 UTC
spatial4j at SIS?
Hello-
We have been working for a while to build better spatial support into
Lucene. While integrating with lucene, we separated out the core
spatial code from the lucene specific stuff. Since the code has
compile/test dependencies on JTS, we hosted it at github. See:
https://spatial4j.com/
The code itself is ASL, but we want to enable complex polygon support
for people who choose to include the LGPL library JTS. In time, there
may be pure ASL polygon solutions.
>From previous discussions, my believe this is a non-starter for SIS.
Is this accurate? Or should we investigate how this code can work
together?
Thanks
Ryan
Re: spatial4j at SIS?
Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
Hi Ryan,
I'd be interested in your guys spatial4j. The biggest issue unfortunately for me is
that as a preference for downstream users, I don't think SIS should include any
dependencies (even optional) on projects with the LGPL license.
Is there any way that the works of spatial4j could be replaced by ALv2
code?
Cheers,
Chris
On Mar 5, 2012, at 12:09 PM, Ryan McKinley wrote:
> Hello-
>
> We have been working for a while to build better spatial support into
> Lucene. While integrating with lucene, we separated out the core
> spatial code from the lucene specific stuff. Since the code has
> compile/test dependencies on JTS, we hosted it at github. See:
> https://spatial4j.com/
>
> The code itself is ASL, but we want to enable complex polygon support
> for people who choose to include the LGPL library JTS. In time, there
> may be pure ASL polygon solutions.
>
> From previous discussions, my believe this is a non-starter for SIS.
> Is this accurate? Or should we investigate how this code can work
> together?
>
> Thanks
> Ryan
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.a.mattmann@nasa.gov
WWW: http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Re: spatial4j at SIS?
Posted by Greg Reddin <gr...@gmail.com>.
On Mon, Mar 5, 2012 at 2:09 PM, Ryan McKinley <ry...@gmail.com> wrote:
> From previous discussions, my believe this is a non-starter for SIS.
> Is this accurate? Or should we investigate how this code can work
> together?
I must be missing something because I'm not seeing this. It sounds
like you are saying you'd need to include an optional dependency on an
LGPL library, correct? I don't see that as a showstopper. Am I wrong?
Greg
Re: spatial4j at SIS?
Posted by Joe White <wh...@gmail.com>.
Chris,
Sure. I have a few spare cycles that I can put some thought into. I'll be in touch.
Joe
On Mar 5, 2012, at 5:24 PM, Mattmann, Chris A (388J) wrote:
> Hey Joe,
>
> No worries, happy to have help and yes, happy to do it, a step at a time. Right now, the near term
> goal is to update the SIS website with a fresh design for our 0.2-incubating release. In fact, it's not
> a blocker in my mind and if I don't see any updates by the end of the week, I'll roll a 0.2-incubating release
> candidate with the fixes already present and save the website update for later.
>
> Then in 0.3-incubating, we've got a set of JIRA issues to work on that I think will add great value. I also
> tagged the SIS CLI as a Google Sumer of Code project. Do you think you could help cruft some JIRA issues
> and ideas for the first parts of polygon support and other features that you think would be completable in
> a summer by a GSoC student? Or any other SIS features that you think we should tackle next?
>
> Cheers,
> Chris
>
> On Mar 5, 2012, at 2:04 PM, Joe White wrote:
>
>> Trust me, Chris, I'm not arguing with the goals. It's just a lot of work. Taken in pieces, it's not so bad, but in toto, it's a lot. I look forward to helping out any way I can. There's only one way to eat an elephant… One bite at a time.
>>
>> Joe
>>
>> On Mar 5, 2012, at 5:01 PM, Mattmann, Chris A (388J) wrote:
>>
>>> Hi Joe,
>>>
>>> Well that's the goal, for when Patrick and I started the project with Sean and Paul. I'd seen enough
>>> of the LGPL libraries out there for spatial and set out to grow up an ALv2 version, so that downstream
>>> users who expect the type of legal framework and quality that the ASF provides would find no surprises.
>>> I don't think those goals have changed in the least.
>>>
>>> I'm really supportive of what Ryan is doing with spatial4j. If there is any way that we can join the communities
>>> here, that would be awesome, I would just strongly advocate for not doing it in a way that includes any LGPL
>>> components, even optionally.
>>>
>>> Cheers,
>>> Chris
>>>
>>> On Mar 5, 2012, at 1:55 PM, Joe White wrote:
>>>
>>>> That definitely sounds like you are advocating writing a complete projection engine, as well as geospatial raster and vector support with AL licensing. That would be pretty ambitious, although not as bad when taking a (much) longer view.
>>>>
>>>> Joe
>>>>
>>>> On Mar 5, 2012, at 4:50 PM, Adam Estrada wrote:
>>>>
>>>>> Chris,
>>>>>
>>>>> Optional support today means that it could potentially be deprecated in
>>>>> later releases, right? The same is true with including GDAL and Proj4. Both
>>>>> of them are very liberally licensed but have to buckle down because of EPSG
>>>>> support. Thoughts on that?
>>>>>
>>>>> Adam
>>>>>
>>>>> On Mon, Mar 5, 2012 at 4:47 PM, Mattmann, Chris A (388J) <
>>>>> chris.a.mattmann@jpl.nasa.gov> wrote:
>>>>>
>>>>>> Hi Greg,
>>>>>>
>>>>>> On Mar 5, 2012, at 1:33 PM, Greg Reddin wrote:
>>>>>>
>>>>>>> On Mon, Mar 5, 2012 at 3:17 PM, Adam Estrada <es...@gmail.com>
>>>>>> wrote:
>>>>>>>> http://www.apache.org/legal/resolved.html From there it looks like
>>>>>> LGPL is
>>>>>>>> a definite no no...Does this mean that it can't be included as an option
>>>>>>>> when being built?
>>>>>>>
>>>>>>> I think it is a definite no no for "inclusion" in a project, meaning
>>>>>>> we can't include any LGPL wok in SIS. But I think we are talking about
>>>>>>> an optional dependency here. See the following blurb from the
>>>>>>> above-linked page:
>>>>>>>
>>>>>>> "Can Apache projects rely on components whose licensing affects the
>>>>>>> Apache product?
>>>>>>> Apache projects cannot distribute any such components. However, if the
>>>>>>> component is only needed for optional features, a project can provide
>>>>>>> the user with instructions on how to obtain and install the
>>>>>>> non-included work. Optional means that the component is not required
>>>>>>> for standard use of the product or for the product to achieve a
>>>>>>> desirable level of quality. The question to ask yourself in this
>>>>>>> situation is:
>>>>>>>
>>>>>>> Will the majority of users want to use my product without adding the
>>>>>>> optional components?"
>>>>>>>
>>>>>>> So, if I understand everything correctly, I don't see this as a
>>>>>>> roadblock. It is possible that I don't understand it correctly though
>>>>>>> :-)
>>>>>>
>>>>>> Unfortunately I do see it as a roadblock. The goal of SIS was to write
>>>>>> a pure ALv2 licensed (or compatible) spatial library and toolkit, which
>>>>>> in my mind does *not* include any dependencies (even optional) on
>>>>>> LGPL components.
>>>>>>
>>>>>> As I understand it, in this case, JTS is providing the polygon support.
>>>>>> Polygon support is something we'd really like to support in SIS, so
>>>>>> to me, this dependency (though optional in e.g., Lucene) is a core
>>>>>> feature of SIS and something most of the eventual users of the system
>>>>>> would want.
>>>>>>
>>>>>> Cheers,
>>>>>> Chris
>>>>>>
>>>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>>> Chris Mattmann, Ph.D.
>>>>>> Senior Computer Scientist
>>>>>> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
>>>>>> Office: 171-266B, Mailstop: 171-246
>>>>>> Email: chris.a.mattmann@nasa.gov
>>>>>> WWW: http://sunset.usc.edu/~mattmann/
>>>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>>> Adjunct Assistant Professor, Computer Science Department
>>>>>> University of Southern California, Los Angeles, CA 90089 USA
>>>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>>>
>>>>>>
>>>>
>>>
>>>
>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>> Chris Mattmann, Ph.D.
>>> Senior Computer Scientist
>>> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
>>> Office: 171-266B, Mailstop: 171-246
>>> Email: chris.a.mattmann@nasa.gov
>>> WWW: http://sunset.usc.edu/~mattmann/
>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>> Adjunct Assistant Professor, Computer Science Department
>>> University of Southern California, Los Angeles, CA 90089 USA
>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>
>>
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Chris Mattmann, Ph.D.
> Senior Computer Scientist
> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> Office: 171-266B, Mailstop: 171-246
> Email: chris.a.mattmann@nasa.gov
> WWW: http://sunset.usc.edu/~mattmann/
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Adjunct Assistant Professor, Computer Science Department
> University of Southern California, Los Angeles, CA 90089 USA
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
Re: spatial4j at SIS?
Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
Hi Joe,
It would be great to get them in JIRA b/c then they will appear here:
http://s.apache.org/gsoc2012tasks
Be sure to "label" or "tag" them in JIRA with the tag: "gsoc2012"
Cheers,
Chris
On Mar 9, 2012, at 6:31 AM, Joe White wrote:
> Chris,
> After giving it some thought, I think there are a certain number of basic features that could conceivably be completed by a GSoC student. Would you like them in Jira, or just in an email?
> Joe
> On Mar 5, 2012, at 5:24 PM, Mattmann, Chris A (388J) wrote:
>
>> Hey Joe,
>>
>> No worries, happy to have help and yes, happy to do it, a step at a time. Right now, the near term
>> goal is to update the SIS website with a fresh design for our 0.2-incubating release. In fact, it's not
>> a blocker in my mind and if I don't see any updates by the end of the week, I'll roll a 0.2-incubating release
>> candidate with the fixes already present and save the website update for later.
>>
>> Then in 0.3-incubating, we've got a set of JIRA issues to work on that I think will add great value. I also
>> tagged the SIS CLI as a Google Sumer of Code project. Do you think you could help cruft some JIRA issues
>> and ideas for the first parts of polygon support and other features that you think would be completable in
>> a summer by a GSoC student? Or any other SIS features that you think we should tackle next?
>>
>> Cheers,
>> Chris
>>
>> On Mar 5, 2012, at 2:04 PM, Joe White wrote:
>>
>>> Trust me, Chris, I'm not arguing with the goals. It's just a lot of work. Taken in pieces, it's not so bad, but in toto, it's a lot. I look forward to helping out any way I can. There's only one way to eat an elephant… One bite at a time.
>>>
>>> Joe
>>>
>>> On Mar 5, 2012, at 5:01 PM, Mattmann, Chris A (388J) wrote:
>>>
>>>> Hi Joe,
>>>>
>>>> Well that's the goal, for when Patrick and I started the project with Sean and Paul. I'd seen enough
>>>> of the LGPL libraries out there for spatial and set out to grow up an ALv2 version, so that downstream
>>>> users who expect the type of legal framework and quality that the ASF provides would find no surprises.
>>>> I don't think those goals have changed in the least.
>>>>
>>>> I'm really supportive of what Ryan is doing with spatial4j. If there is any way that we can join the communities
>>>> here, that would be awesome, I would just strongly advocate for not doing it in a way that includes any LGPL
>>>> components, even optionally.
>>>>
>>>> Cheers,
>>>> Chris
>>>>
>>>> On Mar 5, 2012, at 1:55 PM, Joe White wrote:
>>>>
>>>>> That definitely sounds like you are advocating writing a complete projection engine, as well as geospatial raster and vector support with AL licensing. That would be pretty ambitious, although not as bad when taking a (much) longer view.
>>>>>
>>>>> Joe
>>>>>
>>>>> On Mar 5, 2012, at 4:50 PM, Adam Estrada wrote:
>>>>>
>>>>>> Chris,
>>>>>>
>>>>>> Optional support today means that it could potentially be deprecated in
>>>>>> later releases, right? The same is true with including GDAL and Proj4. Both
>>>>>> of them are very liberally licensed but have to buckle down because of EPSG
>>>>>> support. Thoughts on that?
>>>>>>
>>>>>> Adam
>>>>>>
>>>>>> On Mon, Mar 5, 2012 at 4:47 PM, Mattmann, Chris A (388J) <
>>>>>> chris.a.mattmann@jpl.nasa.gov> wrote:
>>>>>>
>>>>>>> Hi Greg,
>>>>>>>
>>>>>>> On Mar 5, 2012, at 1:33 PM, Greg Reddin wrote:
>>>>>>>
>>>>>>>> On Mon, Mar 5, 2012 at 3:17 PM, Adam Estrada <es...@gmail.com>
>>>>>>> wrote:
>>>>>>>>> http://www.apache.org/legal/resolved.html From there it looks like
>>>>>>> LGPL is
>>>>>>>>> a definite no no...Does this mean that it can't be included as an option
>>>>>>>>> when being built?
>>>>>>>>
>>>>>>>> I think it is a definite no no for "inclusion" in a project, meaning
>>>>>>>> we can't include any LGPL wok in SIS. But I think we are talking about
>>>>>>>> an optional dependency here. See the following blurb from the
>>>>>>>> above-linked page:
>>>>>>>>
>>>>>>>> "Can Apache projects rely on components whose licensing affects the
>>>>>>>> Apache product?
>>>>>>>> Apache projects cannot distribute any such components. However, if the
>>>>>>>> component is only needed for optional features, a project can provide
>>>>>>>> the user with instructions on how to obtain and install the
>>>>>>>> non-included work. Optional means that the component is not required
>>>>>>>> for standard use of the product or for the product to achieve a
>>>>>>>> desirable level of quality. The question to ask yourself in this
>>>>>>>> situation is:
>>>>>>>>
>>>>>>>> Will the majority of users want to use my product without adding the
>>>>>>>> optional components?"
>>>>>>>>
>>>>>>>> So, if I understand everything correctly, I don't see this as a
>>>>>>>> roadblock. It is possible that I don't understand it correctly though
>>>>>>>> :-)
>>>>>>>
>>>>>>> Unfortunately I do see it as a roadblock. The goal of SIS was to write
>>>>>>> a pure ALv2 licensed (or compatible) spatial library and toolkit, which
>>>>>>> in my mind does *not* include any dependencies (even optional) on
>>>>>>> LGPL components.
>>>>>>>
>>>>>>> As I understand it, in this case, JTS is providing the polygon support.
>>>>>>> Polygon support is something we'd really like to support in SIS, so
>>>>>>> to me, this dependency (though optional in e.g., Lucene) is a core
>>>>>>> feature of SIS and something most of the eventual users of the system
>>>>>>> would want.
>>>>>>>
>>>>>>> Cheers,
>>>>>>> Chris
>>>>>>>
>>>>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>>>> Chris Mattmann, Ph.D.
>>>>>>> Senior Computer Scientist
>>>>>>> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
>>>>>>> Office: 171-266B, Mailstop: 171-246
>>>>>>> Email: chris.a.mattmann@nasa.gov
>>>>>>> WWW: http://sunset.usc.edu/~mattmann/
>>>>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>>>> Adjunct Assistant Professor, Computer Science Department
>>>>>>> University of Southern California, Los Angeles, CA 90089 USA
>>>>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>>>>
>>>>>>>
>>>>>
>>>>
>>>>
>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>> Chris Mattmann, Ph.D.
>>>> Senior Computer Scientist
>>>> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
>>>> Office: 171-266B, Mailstop: 171-246
>>>> Email: chris.a.mattmann@nasa.gov
>>>> WWW: http://sunset.usc.edu/~mattmann/
>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>> Adjunct Assistant Professor, Computer Science Department
>>>> University of Southern California, Los Angeles, CA 90089 USA
>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>
>>>
>>
>>
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> Chris Mattmann, Ph.D.
>> Senior Computer Scientist
>> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
>> Office: 171-266B, Mailstop: 171-246
>> Email: chris.a.mattmann@nasa.gov
>> WWW: http://sunset.usc.edu/~mattmann/
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> Adjunct Assistant Professor, Computer Science Department
>> University of Southern California, Los Angeles, CA 90089 USA
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>
>
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.a.mattmann@nasa.gov
WWW: http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Re: spatial4j at SIS?
Posted by Joe White <wh...@gmail.com>.
Chris,
After giving it some thought, I think there are a certain number of basic features that could conceivably be completed by a GSoC student. Would you like them in Jira, or just in an email?
Joe
On Mar 5, 2012, at 5:24 PM, Mattmann, Chris A (388J) wrote:
> Hey Joe,
>
> No worries, happy to have help and yes, happy to do it, a step at a time. Right now, the near term
> goal is to update the SIS website with a fresh design for our 0.2-incubating release. In fact, it's not
> a blocker in my mind and if I don't see any updates by the end of the week, I'll roll a 0.2-incubating release
> candidate with the fixes already present and save the website update for later.
>
> Then in 0.3-incubating, we've got a set of JIRA issues to work on that I think will add great value. I also
> tagged the SIS CLI as a Google Sumer of Code project. Do you think you could help cruft some JIRA issues
> and ideas for the first parts of polygon support and other features that you think would be completable in
> a summer by a GSoC student? Or any other SIS features that you think we should tackle next?
>
> Cheers,
> Chris
>
> On Mar 5, 2012, at 2:04 PM, Joe White wrote:
>
>> Trust me, Chris, I'm not arguing with the goals. It's just a lot of work. Taken in pieces, it's not so bad, but in toto, it's a lot. I look forward to helping out any way I can. There's only one way to eat an elephant… One bite at a time.
>>
>> Joe
>>
>> On Mar 5, 2012, at 5:01 PM, Mattmann, Chris A (388J) wrote:
>>
>>> Hi Joe,
>>>
>>> Well that's the goal, for when Patrick and I started the project with Sean and Paul. I'd seen enough
>>> of the LGPL libraries out there for spatial and set out to grow up an ALv2 version, so that downstream
>>> users who expect the type of legal framework and quality that the ASF provides would find no surprises.
>>> I don't think those goals have changed in the least.
>>>
>>> I'm really supportive of what Ryan is doing with spatial4j. If there is any way that we can join the communities
>>> here, that would be awesome, I would just strongly advocate for not doing it in a way that includes any LGPL
>>> components, even optionally.
>>>
>>> Cheers,
>>> Chris
>>>
>>> On Mar 5, 2012, at 1:55 PM, Joe White wrote:
>>>
>>>> That definitely sounds like you are advocating writing a complete projection engine, as well as geospatial raster and vector support with AL licensing. That would be pretty ambitious, although not as bad when taking a (much) longer view.
>>>>
>>>> Joe
>>>>
>>>> On Mar 5, 2012, at 4:50 PM, Adam Estrada wrote:
>>>>
>>>>> Chris,
>>>>>
>>>>> Optional support today means that it could potentially be deprecated in
>>>>> later releases, right? The same is true with including GDAL and Proj4. Both
>>>>> of them are very liberally licensed but have to buckle down because of EPSG
>>>>> support. Thoughts on that?
>>>>>
>>>>> Adam
>>>>>
>>>>> On Mon, Mar 5, 2012 at 4:47 PM, Mattmann, Chris A (388J) <
>>>>> chris.a.mattmann@jpl.nasa.gov> wrote:
>>>>>
>>>>>> Hi Greg,
>>>>>>
>>>>>> On Mar 5, 2012, at 1:33 PM, Greg Reddin wrote:
>>>>>>
>>>>>>> On Mon, Mar 5, 2012 at 3:17 PM, Adam Estrada <es...@gmail.com>
>>>>>> wrote:
>>>>>>>> http://www.apache.org/legal/resolved.html From there it looks like
>>>>>> LGPL is
>>>>>>>> a definite no no...Does this mean that it can't be included as an option
>>>>>>>> when being built?
>>>>>>>
>>>>>>> I think it is a definite no no for "inclusion" in a project, meaning
>>>>>>> we can't include any LGPL wok in SIS. But I think we are talking about
>>>>>>> an optional dependency here. See the following blurb from the
>>>>>>> above-linked page:
>>>>>>>
>>>>>>> "Can Apache projects rely on components whose licensing affects the
>>>>>>> Apache product?
>>>>>>> Apache projects cannot distribute any such components. However, if the
>>>>>>> component is only needed for optional features, a project can provide
>>>>>>> the user with instructions on how to obtain and install the
>>>>>>> non-included work. Optional means that the component is not required
>>>>>>> for standard use of the product or for the product to achieve a
>>>>>>> desirable level of quality. The question to ask yourself in this
>>>>>>> situation is:
>>>>>>>
>>>>>>> Will the majority of users want to use my product without adding the
>>>>>>> optional components?"
>>>>>>>
>>>>>>> So, if I understand everything correctly, I don't see this as a
>>>>>>> roadblock. It is possible that I don't understand it correctly though
>>>>>>> :-)
>>>>>>
>>>>>> Unfortunately I do see it as a roadblock. The goal of SIS was to write
>>>>>> a pure ALv2 licensed (or compatible) spatial library and toolkit, which
>>>>>> in my mind does *not* include any dependencies (even optional) on
>>>>>> LGPL components.
>>>>>>
>>>>>> As I understand it, in this case, JTS is providing the polygon support.
>>>>>> Polygon support is something we'd really like to support in SIS, so
>>>>>> to me, this dependency (though optional in e.g., Lucene) is a core
>>>>>> feature of SIS and something most of the eventual users of the system
>>>>>> would want.
>>>>>>
>>>>>> Cheers,
>>>>>> Chris
>>>>>>
>>>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>>> Chris Mattmann, Ph.D.
>>>>>> Senior Computer Scientist
>>>>>> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
>>>>>> Office: 171-266B, Mailstop: 171-246
>>>>>> Email: chris.a.mattmann@nasa.gov
>>>>>> WWW: http://sunset.usc.edu/~mattmann/
>>>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>>> Adjunct Assistant Professor, Computer Science Department
>>>>>> University of Southern California, Los Angeles, CA 90089 USA
>>>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>>>
>>>>>>
>>>>
>>>
>>>
>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>> Chris Mattmann, Ph.D.
>>> Senior Computer Scientist
>>> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
>>> Office: 171-266B, Mailstop: 171-246
>>> Email: chris.a.mattmann@nasa.gov
>>> WWW: http://sunset.usc.edu/~mattmann/
>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>> Adjunct Assistant Professor, Computer Science Department
>>> University of Southern California, Los Angeles, CA 90089 USA
>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>
>>
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Chris Mattmann, Ph.D.
> Senior Computer Scientist
> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> Office: 171-266B, Mailstop: 171-246
> Email: chris.a.mattmann@nasa.gov
> WWW: http://sunset.usc.edu/~mattmann/
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Adjunct Assistant Professor, Computer Science Department
> University of Southern California, Los Angeles, CA 90089 USA
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
Re: spatial4j at SIS?
Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
Hey Joe,
No worries, happy to have help and yes, happy to do it, a step at a time. Right now, the near term
goal is to update the SIS website with a fresh design for our 0.2-incubating release. In fact, it's not
a blocker in my mind and if I don't see any updates by the end of the week, I'll roll a 0.2-incubating release
candidate with the fixes already present and save the website update for later.
Then in 0.3-incubating, we've got a set of JIRA issues to work on that I think will add great value. I also
tagged the SIS CLI as a Google Sumer of Code project. Do you think you could help cruft some JIRA issues
and ideas for the first parts of polygon support and other features that you think would be completable in
a summer by a GSoC student? Or any other SIS features that you think we should tackle next?
Cheers,
Chris
On Mar 5, 2012, at 2:04 PM, Joe White wrote:
> Trust me, Chris, I'm not arguing with the goals. It's just a lot of work. Taken in pieces, it's not so bad, but in toto, it's a lot. I look forward to helping out any way I can. There's only one way to eat an elephant… One bite at a time.
>
> Joe
>
> On Mar 5, 2012, at 5:01 PM, Mattmann, Chris A (388J) wrote:
>
>> Hi Joe,
>>
>> Well that's the goal, for when Patrick and I started the project with Sean and Paul. I'd seen enough
>> of the LGPL libraries out there for spatial and set out to grow up an ALv2 version, so that downstream
>> users who expect the type of legal framework and quality that the ASF provides would find no surprises.
>> I don't think those goals have changed in the least.
>>
>> I'm really supportive of what Ryan is doing with spatial4j. If there is any way that we can join the communities
>> here, that would be awesome, I would just strongly advocate for not doing it in a way that includes any LGPL
>> components, even optionally.
>>
>> Cheers,
>> Chris
>>
>> On Mar 5, 2012, at 1:55 PM, Joe White wrote:
>>
>>> That definitely sounds like you are advocating writing a complete projection engine, as well as geospatial raster and vector support with AL licensing. That would be pretty ambitious, although not as bad when taking a (much) longer view.
>>>
>>> Joe
>>>
>>> On Mar 5, 2012, at 4:50 PM, Adam Estrada wrote:
>>>
>>>> Chris,
>>>>
>>>> Optional support today means that it could potentially be deprecated in
>>>> later releases, right? The same is true with including GDAL and Proj4. Both
>>>> of them are very liberally licensed but have to buckle down because of EPSG
>>>> support. Thoughts on that?
>>>>
>>>> Adam
>>>>
>>>> On Mon, Mar 5, 2012 at 4:47 PM, Mattmann, Chris A (388J) <
>>>> chris.a.mattmann@jpl.nasa.gov> wrote:
>>>>
>>>>> Hi Greg,
>>>>>
>>>>> On Mar 5, 2012, at 1:33 PM, Greg Reddin wrote:
>>>>>
>>>>>> On Mon, Mar 5, 2012 at 3:17 PM, Adam Estrada <es...@gmail.com>
>>>>> wrote:
>>>>>>> http://www.apache.org/legal/resolved.html From there it looks like
>>>>> LGPL is
>>>>>>> a definite no no...Does this mean that it can't be included as an option
>>>>>>> when being built?
>>>>>>
>>>>>> I think it is a definite no no for "inclusion" in a project, meaning
>>>>>> we can't include any LGPL wok in SIS. But I think we are talking about
>>>>>> an optional dependency here. See the following blurb from the
>>>>>> above-linked page:
>>>>>>
>>>>>> "Can Apache projects rely on components whose licensing affects the
>>>>>> Apache product?
>>>>>> Apache projects cannot distribute any such components. However, if the
>>>>>> component is only needed for optional features, a project can provide
>>>>>> the user with instructions on how to obtain and install the
>>>>>> non-included work. Optional means that the component is not required
>>>>>> for standard use of the product or for the product to achieve a
>>>>>> desirable level of quality. The question to ask yourself in this
>>>>>> situation is:
>>>>>>
>>>>>> Will the majority of users want to use my product without adding the
>>>>>> optional components?"
>>>>>>
>>>>>> So, if I understand everything correctly, I don't see this as a
>>>>>> roadblock. It is possible that I don't understand it correctly though
>>>>>> :-)
>>>>>
>>>>> Unfortunately I do see it as a roadblock. The goal of SIS was to write
>>>>> a pure ALv2 licensed (or compatible) spatial library and toolkit, which
>>>>> in my mind does *not* include any dependencies (even optional) on
>>>>> LGPL components.
>>>>>
>>>>> As I understand it, in this case, JTS is providing the polygon support.
>>>>> Polygon support is something we'd really like to support in SIS, so
>>>>> to me, this dependency (though optional in e.g., Lucene) is a core
>>>>> feature of SIS and something most of the eventual users of the system
>>>>> would want.
>>>>>
>>>>> Cheers,
>>>>> Chris
>>>>>
>>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>> Chris Mattmann, Ph.D.
>>>>> Senior Computer Scientist
>>>>> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
>>>>> Office: 171-266B, Mailstop: 171-246
>>>>> Email: chris.a.mattmann@nasa.gov
>>>>> WWW: http://sunset.usc.edu/~mattmann/
>>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>> Adjunct Assistant Professor, Computer Science Department
>>>>> University of Southern California, Los Angeles, CA 90089 USA
>>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>>
>>>>>
>>>
>>
>>
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> Chris Mattmann, Ph.D.
>> Senior Computer Scientist
>> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
>> Office: 171-266B, Mailstop: 171-246
>> Email: chris.a.mattmann@nasa.gov
>> WWW: http://sunset.usc.edu/~mattmann/
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> Adjunct Assistant Professor, Computer Science Department
>> University of Southern California, Los Angeles, CA 90089 USA
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>
>
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.a.mattmann@nasa.gov
WWW: http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Re: spatial4j at SIS?
Posted by Joe White <wh...@gmail.com>.
Trust me, Chris, I'm not arguing with the goals. It's just a lot of work. Taken in pieces, it's not so bad, but in toto, it's a lot. I look forward to helping out any way I can. There's only one way to eat an elephant… One bite at a time.
Joe
On Mar 5, 2012, at 5:01 PM, Mattmann, Chris A (388J) wrote:
> Hi Joe,
>
> Well that's the goal, for when Patrick and I started the project with Sean and Paul. I'd seen enough
> of the LGPL libraries out there for spatial and set out to grow up an ALv2 version, so that downstream
> users who expect the type of legal framework and quality that the ASF provides would find no surprises.
> I don't think those goals have changed in the least.
>
> I'm really supportive of what Ryan is doing with spatial4j. If there is any way that we can join the communities
> here, that would be awesome, I would just strongly advocate for not doing it in a way that includes any LGPL
> components, even optionally.
>
> Cheers,
> Chris
>
> On Mar 5, 2012, at 1:55 PM, Joe White wrote:
>
>> That definitely sounds like you are advocating writing a complete projection engine, as well as geospatial raster and vector support with AL licensing. That would be pretty ambitious, although not as bad when taking a (much) longer view.
>>
>> Joe
>>
>> On Mar 5, 2012, at 4:50 PM, Adam Estrada wrote:
>>
>>> Chris,
>>>
>>> Optional support today means that it could potentially be deprecated in
>>> later releases, right? The same is true with including GDAL and Proj4. Both
>>> of them are very liberally licensed but have to buckle down because of EPSG
>>> support. Thoughts on that?
>>>
>>> Adam
>>>
>>> On Mon, Mar 5, 2012 at 4:47 PM, Mattmann, Chris A (388J) <
>>> chris.a.mattmann@jpl.nasa.gov> wrote:
>>>
>>>> Hi Greg,
>>>>
>>>> On Mar 5, 2012, at 1:33 PM, Greg Reddin wrote:
>>>>
>>>>> On Mon, Mar 5, 2012 at 3:17 PM, Adam Estrada <es...@gmail.com>
>>>> wrote:
>>>>>> http://www.apache.org/legal/resolved.html From there it looks like
>>>> LGPL is
>>>>>> a definite no no...Does this mean that it can't be included as an option
>>>>>> when being built?
>>>>>
>>>>> I think it is a definite no no for "inclusion" in a project, meaning
>>>>> we can't include any LGPL wok in SIS. But I think we are talking about
>>>>> an optional dependency here. See the following blurb from the
>>>>> above-linked page:
>>>>>
>>>>> "Can Apache projects rely on components whose licensing affects the
>>>>> Apache product?
>>>>> Apache projects cannot distribute any such components. However, if the
>>>>> component is only needed for optional features, a project can provide
>>>>> the user with instructions on how to obtain and install the
>>>>> non-included work. Optional means that the component is not required
>>>>> for standard use of the product or for the product to achieve a
>>>>> desirable level of quality. The question to ask yourself in this
>>>>> situation is:
>>>>>
>>>>> Will the majority of users want to use my product without adding the
>>>>> optional components?"
>>>>>
>>>>> So, if I understand everything correctly, I don't see this as a
>>>>> roadblock. It is possible that I don't understand it correctly though
>>>>> :-)
>>>>
>>>> Unfortunately I do see it as a roadblock. The goal of SIS was to write
>>>> a pure ALv2 licensed (or compatible) spatial library and toolkit, which
>>>> in my mind does *not* include any dependencies (even optional) on
>>>> LGPL components.
>>>>
>>>> As I understand it, in this case, JTS is providing the polygon support.
>>>> Polygon support is something we'd really like to support in SIS, so
>>>> to me, this dependency (though optional in e.g., Lucene) is a core
>>>> feature of SIS and something most of the eventual users of the system
>>>> would want.
>>>>
>>>> Cheers,
>>>> Chris
>>>>
>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>> Chris Mattmann, Ph.D.
>>>> Senior Computer Scientist
>>>> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
>>>> Office: 171-266B, Mailstop: 171-246
>>>> Email: chris.a.mattmann@nasa.gov
>>>> WWW: http://sunset.usc.edu/~mattmann/
>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>> Adjunct Assistant Professor, Computer Science Department
>>>> University of Southern California, Los Angeles, CA 90089 USA
>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>
>>>>
>>
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Chris Mattmann, Ph.D.
> Senior Computer Scientist
> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> Office: 171-266B, Mailstop: 171-246
> Email: chris.a.mattmann@nasa.gov
> WWW: http://sunset.usc.edu/~mattmann/
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Adjunct Assistant Professor, Computer Science Department
> University of Southern California, Los Angeles, CA 90089 USA
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
Re: spatial4j at SIS?
Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
Hi Joe,
Well that's the goal, for when Patrick and I started the project with Sean and Paul. I'd seen enough
of the LGPL libraries out there for spatial and set out to grow up an ALv2 version, so that downstream
users who expect the type of legal framework and quality that the ASF provides would find no surprises.
I don't think those goals have changed in the least.
I'm really supportive of what Ryan is doing with spatial4j. If there is any way that we can join the communities
here, that would be awesome, I would just strongly advocate for not doing it in a way that includes any LGPL
components, even optionally.
Cheers,
Chris
On Mar 5, 2012, at 1:55 PM, Joe White wrote:
> That definitely sounds like you are advocating writing a complete projection engine, as well as geospatial raster and vector support with AL licensing. That would be pretty ambitious, although not as bad when taking a (much) longer view.
>
> Joe
>
> On Mar 5, 2012, at 4:50 PM, Adam Estrada wrote:
>
>> Chris,
>>
>> Optional support today means that it could potentially be deprecated in
>> later releases, right? The same is true with including GDAL and Proj4. Both
>> of them are very liberally licensed but have to buckle down because of EPSG
>> support. Thoughts on that?
>>
>> Adam
>>
>> On Mon, Mar 5, 2012 at 4:47 PM, Mattmann, Chris A (388J) <
>> chris.a.mattmann@jpl.nasa.gov> wrote:
>>
>>> Hi Greg,
>>>
>>> On Mar 5, 2012, at 1:33 PM, Greg Reddin wrote:
>>>
>>>> On Mon, Mar 5, 2012 at 3:17 PM, Adam Estrada <es...@gmail.com>
>>> wrote:
>>>>> http://www.apache.org/legal/resolved.html From there it looks like
>>> LGPL is
>>>>> a definite no no...Does this mean that it can't be included as an option
>>>>> when being built?
>>>>
>>>> I think it is a definite no no for "inclusion" in a project, meaning
>>>> we can't include any LGPL wok in SIS. But I think we are talking about
>>>> an optional dependency here. See the following blurb from the
>>>> above-linked page:
>>>>
>>>> "Can Apache projects rely on components whose licensing affects the
>>>> Apache product?
>>>> Apache projects cannot distribute any such components. However, if the
>>>> component is only needed for optional features, a project can provide
>>>> the user with instructions on how to obtain and install the
>>>> non-included work. Optional means that the component is not required
>>>> for standard use of the product or for the product to achieve a
>>>> desirable level of quality. The question to ask yourself in this
>>>> situation is:
>>>>
>>>> Will the majority of users want to use my product without adding the
>>>> optional components?"
>>>>
>>>> So, if I understand everything correctly, I don't see this as a
>>>> roadblock. It is possible that I don't understand it correctly though
>>>> :-)
>>>
>>> Unfortunately I do see it as a roadblock. The goal of SIS was to write
>>> a pure ALv2 licensed (or compatible) spatial library and toolkit, which
>>> in my mind does *not* include any dependencies (even optional) on
>>> LGPL components.
>>>
>>> As I understand it, in this case, JTS is providing the polygon support.
>>> Polygon support is something we'd really like to support in SIS, so
>>> to me, this dependency (though optional in e.g., Lucene) is a core
>>> feature of SIS and something most of the eventual users of the system
>>> would want.
>>>
>>> Cheers,
>>> Chris
>>>
>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>> Chris Mattmann, Ph.D.
>>> Senior Computer Scientist
>>> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
>>> Office: 171-266B, Mailstop: 171-246
>>> Email: chris.a.mattmann@nasa.gov
>>> WWW: http://sunset.usc.edu/~mattmann/
>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>> Adjunct Assistant Professor, Computer Science Department
>>> University of Southern California, Los Angeles, CA 90089 USA
>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>
>>>
>
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.a.mattmann@nasa.gov
WWW: http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Re: spatial4j at SIS?
Posted by Joe White <wh...@gmail.com>.
That definitely sounds like you are advocating writing a complete projection engine, as well as geospatial raster and vector support with AL licensing. That would be pretty ambitious, although not as bad when taking a (much) longer view.
Joe
On Mar 5, 2012, at 4:50 PM, Adam Estrada wrote:
> Chris,
>
> Optional support today means that it could potentially be deprecated in
> later releases, right? The same is true with including GDAL and Proj4. Both
> of them are very liberally licensed but have to buckle down because of EPSG
> support. Thoughts on that?
>
> Adam
>
> On Mon, Mar 5, 2012 at 4:47 PM, Mattmann, Chris A (388J) <
> chris.a.mattmann@jpl.nasa.gov> wrote:
>
>> Hi Greg,
>>
>> On Mar 5, 2012, at 1:33 PM, Greg Reddin wrote:
>>
>>> On Mon, Mar 5, 2012 at 3:17 PM, Adam Estrada <es...@gmail.com>
>> wrote:
>>>> http://www.apache.org/legal/resolved.html From there it looks like
>> LGPL is
>>>> a definite no no...Does this mean that it can't be included as an option
>>>> when being built?
>>>
>>> I think it is a definite no no for "inclusion" in a project, meaning
>>> we can't include any LGPL wok in SIS. But I think we are talking about
>>> an optional dependency here. See the following blurb from the
>>> above-linked page:
>>>
>>> "Can Apache projects rely on components whose licensing affects the
>>> Apache product?
>>> Apache projects cannot distribute any such components. However, if the
>>> component is only needed for optional features, a project can provide
>>> the user with instructions on how to obtain and install the
>>> non-included work. Optional means that the component is not required
>>> for standard use of the product or for the product to achieve a
>>> desirable level of quality. The question to ask yourself in this
>>> situation is:
>>>
>>> Will the majority of users want to use my product without adding the
>>> optional components?"
>>>
>>> So, if I understand everything correctly, I don't see this as a
>>> roadblock. It is possible that I don't understand it correctly though
>>> :-)
>>
>> Unfortunately I do see it as a roadblock. The goal of SIS was to write
>> a pure ALv2 licensed (or compatible) spatial library and toolkit, which
>> in my mind does *not* include any dependencies (even optional) on
>> LGPL components.
>>
>> As I understand it, in this case, JTS is providing the polygon support.
>> Polygon support is something we'd really like to support in SIS, so
>> to me, this dependency (though optional in e.g., Lucene) is a core
>> feature of SIS and something most of the eventual users of the system
>> would want.
>>
>> Cheers,
>> Chris
>>
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> Chris Mattmann, Ph.D.
>> Senior Computer Scientist
>> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
>> Office: 171-266B, Mailstop: 171-246
>> Email: chris.a.mattmann@nasa.gov
>> WWW: http://sunset.usc.edu/~mattmann/
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> Adjunct Assistant Professor, Computer Science Department
>> University of Southern California, Los Angeles, CA 90089 USA
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>
>>
Re: spatial4j at SIS?
Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
Hi Adam,
It's not really about deprecation -- it's about the legal framework of Apache and
the fact that it's not what the goals of the project are/were. Goals can evolve that's fine
but that wasn't my goal when we set about on this effort.
See: http://wiki.apache.org/incubator/SpatialProposal for the rationale.
Cheers,
Chris
On Mar 5, 2012, at 1:50 PM, Adam Estrada wrote:
> Chris,
>
> Optional support today means that it could potentially be deprecated in
> later releases, right? The same is true with including GDAL and Proj4. Both
> of them are very liberally licensed but have to buckle down because of EPSG
> support. Thoughts on that?
>
> Adam
>
> On Mon, Mar 5, 2012 at 4:47 PM, Mattmann, Chris A (388J) <
> chris.a.mattmann@jpl.nasa.gov> wrote:
>
>> Hi Greg,
>>
>> On Mar 5, 2012, at 1:33 PM, Greg Reddin wrote:
>>
>>> On Mon, Mar 5, 2012 at 3:17 PM, Adam Estrada <es...@gmail.com>
>> wrote:
>>>> http://www.apache.org/legal/resolved.html From there it looks like
>> LGPL is
>>>> a definite no no...Does this mean that it can't be included as an option
>>>> when being built?
>>>
>>> I think it is a definite no no for "inclusion" in a project, meaning
>>> we can't include any LGPL wok in SIS. But I think we are talking about
>>> an optional dependency here. See the following blurb from the
>>> above-linked page:
>>>
>>> "Can Apache projects rely on components whose licensing affects the
>>> Apache product?
>>> Apache projects cannot distribute any such components. However, if the
>>> component is only needed for optional features, a project can provide
>>> the user with instructions on how to obtain and install the
>>> non-included work. Optional means that the component is not required
>>> for standard use of the product or for the product to achieve a
>>> desirable level of quality. The question to ask yourself in this
>>> situation is:
>>>
>>> Will the majority of users want to use my product without adding the
>>> optional components?"
>>>
>>> So, if I understand everything correctly, I don't see this as a
>>> roadblock. It is possible that I don't understand it correctly though
>>> :-)
>>
>> Unfortunately I do see it as a roadblock. The goal of SIS was to write
>> a pure ALv2 licensed (or compatible) spatial library and toolkit, which
>> in my mind does *not* include any dependencies (even optional) on
>> LGPL components.
>>
>> As I understand it, in this case, JTS is providing the polygon support.
>> Polygon support is something we'd really like to support in SIS, so
>> to me, this dependency (though optional in e.g., Lucene) is a core
>> feature of SIS and something most of the eventual users of the system
>> would want.
>>
>> Cheers,
>> Chris
>>
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> Chris Mattmann, Ph.D.
>> Senior Computer Scientist
>> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
>> Office: 171-266B, Mailstop: 171-246
>> Email: chris.a.mattmann@nasa.gov
>> WWW: http://sunset.usc.edu/~mattmann/
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> Adjunct Assistant Professor, Computer Science Department
>> University of Southern California, Los Angeles, CA 90089 USA
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>
>>
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.a.mattmann@nasa.gov
WWW: http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Re: spatial4j at SIS?
Posted by Adam Estrada <es...@gmail.com>.
Chris,
Optional support today means that it could potentially be deprecated in
later releases, right? The same is true with including GDAL and Proj4. Both
of them are very liberally licensed but have to buckle down because of EPSG
support. Thoughts on that?
Adam
On Mon, Mar 5, 2012 at 4:47 PM, Mattmann, Chris A (388J) <
chris.a.mattmann@jpl.nasa.gov> wrote:
> Hi Greg,
>
> On Mar 5, 2012, at 1:33 PM, Greg Reddin wrote:
>
> > On Mon, Mar 5, 2012 at 3:17 PM, Adam Estrada <es...@gmail.com>
> wrote:
> >> http://www.apache.org/legal/resolved.html From there it looks like
> LGPL is
> >> a definite no no...Does this mean that it can't be included as an option
> >> when being built?
> >
> > I think it is a definite no no for "inclusion" in a project, meaning
> > we can't include any LGPL wok in SIS. But I think we are talking about
> > an optional dependency here. See the following blurb from the
> > above-linked page:
> >
> > "Can Apache projects rely on components whose licensing affects the
> > Apache product?
> > Apache projects cannot distribute any such components. However, if the
> > component is only needed for optional features, a project can provide
> > the user with instructions on how to obtain and install the
> > non-included work. Optional means that the component is not required
> > for standard use of the product or for the product to achieve a
> > desirable level of quality. The question to ask yourself in this
> > situation is:
> >
> > Will the majority of users want to use my product without adding the
> > optional components?"
> >
> > So, if I understand everything correctly, I don't see this as a
> > roadblock. It is possible that I don't understand it correctly though
> > :-)
>
> Unfortunately I do see it as a roadblock. The goal of SIS was to write
> a pure ALv2 licensed (or compatible) spatial library and toolkit, which
> in my mind does *not* include any dependencies (even optional) on
> LGPL components.
>
> As I understand it, in this case, JTS is providing the polygon support.
> Polygon support is something we'd really like to support in SIS, so
> to me, this dependency (though optional in e.g., Lucene) is a core
> feature of SIS and something most of the eventual users of the system
> would want.
>
> Cheers,
> Chris
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Chris Mattmann, Ph.D.
> Senior Computer Scientist
> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> Office: 171-266B, Mailstop: 171-246
> Email: chris.a.mattmann@nasa.gov
> WWW: http://sunset.usc.edu/~mattmann/
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Adjunct Assistant Professor, Computer Science Department
> University of Southern California, Los Angeles, CA 90089 USA
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
>
Re: spatial4j at SIS?
Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
Hi Ryan,
On Mar 5, 2012, at 3:27 PM, Ryan McKinley wrote:
> On Mon, Mar 5, 2012 at 3:09 PM, Mattmann, Chris A (388J)
> <ch...@jpl.nasa.gov> wrote:
>> Hi Ryan,
>>
>> On Mar 5, 2012, at 2:57 PM, Ryan McKinley wrote:
>>
>>> On Mon, Mar 5, 2012 at 2:34 PM, Mattmann, Chris A (388J)
>>> <ch...@jpl.nasa.gov> wrote:
>>>> Hey Ryan,
>>>>
>>>> On Mar 5, 2012, at 2:27 PM, Ryan McKinley wrote:
>>>>
>>>>>>
>>>>>> Unfortunately I do see it as a roadblock. The goal of SIS was to write
>>>>>> a pure ALv2 licensed (or compatible) spatial library and toolkit, which
>>>>>> in my mind does *not* include any dependencies (even optional) on
>>>>>> LGPL components.
>>>>>>
>>>>>
>>>>> Got it, this was my understanding. The goal of SIS is to build an ASL
>>>>> version of JTS -- that's a great goal, just not one I have any
>>>>> energy/time to contribute towards.
>>>>
>>>> No worries. I appreciate you reaching out. Is there a way to have everything
>>>> in spatial4j that doesn't rely on the LGPL code here?
>>>>
>>>
>>> possible, but it makes testing overly complicated. I want/need the
>>> JTS implementations to be 1st class test citizens. (This is actually
>>> the biggest reason this is not directly in the lucene)
>>
>> Gotcha.
>>
>>>
>>>
>>>>>
>>>>>
>>>>>> Is there any way that the works of spatial4j could be replaced by ALv2 code?
>>>>>
>>>>> The code in spatial4j is all ASL. If there were a viable ASL polygon
>>>>> library, we could use that too.
>>>>
>>>> How can you have an ALv2 licensed library that has dependencies on LGPL upstream
>>>> components? Doesn't the LGPL and its viral nature [1] spill into your code?
>>>>
>>>
>>> You may be confusing LGPL with GPL.
>>>
>>> "Applications which link to LGPL libraries need not be released under the LGPL"
>>> http://www.gnu.org/licenses/lgpl-java.html
>>>
>>> The key thing they want to make sure is that you don't bundle your own
>>> version of the .jar file (section 6)
>>
>> Well that's the FSF's interpretation, and *not* Apache's. See this:
>>
>> (search for LGPL)
>>
>> http://www.apache.org/legal/resolved.html
>>
>> Which licenses may NOT be included within Apache products?
>>
>> • Binary Code License (BCL)
>> • Special exceptions to the GNU GPL (e.g. GNU Classpath)
>> • GNU GPL 1, 2, 3
>> • GNU LGPL 2, 2.1, 3
>> • Affero GPL 3
>> • NPL 1.0/NPL 1.1
>> • QPL
>> • Sleepycat License
>> • Microsoft Limited Public License
>>
>> GNU LGPL
>> The LGPL is ineligible primarily due to the restrictions it places on larger works, violating the third license criterion. Therefore, LGPL-licensed works must not be included in Apache products.
>> Special exceptions to the GNU GPL
>> Some copyright holders have licensed their works under the GPL with special exceptions. Although these exceptions may appear to be addressing the restrictions disallowed by the ASF's first and second license criteria, the exceptions may only apply to software not "derived from or based on" the covered work. This references terms defined in the GPL that include works that "use" or "contain" the work.
>>
>> This is also the GPL and ALv2 compatible, just for reference:
>>
>> http://www.apache.org/licenses/GPL-compatibility.html
>>
>> You may find other interpretations in mailing lists, or from
>> other folks, or via mail archives, but my preference would be
>> taking the explicit understanding from the Legal resolved
>> page above.
>>
>> Cheers,
>> Chris
>>
>
> Cool -- I have no intention of debating this... or asking legal, or whatever.
>
> It is very clear that you can not *distribute* lgpl files. The
> statement Greg pointed to earlier from the same page implies that you
> can compile/test with LGPL dependencies:
It may imply it but I'm not sure it does any more than that.
> [..snip..]
>
> "Will the majority of users want to use my product without adding the
> optional components?
Precisely.
>
> - - - - - - -
>
> That said, I totally respect the choice not to want an external JTS
> compile/test dependency.
Yep and that's the basic point. Thanks for respecting it and for understanding.
And for saying we have good goals!
We'll get there....
Cheers,
Chris
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.a.mattmann@nasa.gov
WWW: http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Re: spatial4j at SIS?
Posted by Ryan McKinley <ry...@gmail.com>.
On Mon, Mar 5, 2012 at 3:09 PM, Mattmann, Chris A (388J)
<ch...@jpl.nasa.gov> wrote:
> Hi Ryan,
>
> On Mar 5, 2012, at 2:57 PM, Ryan McKinley wrote:
>
>> On Mon, Mar 5, 2012 at 2:34 PM, Mattmann, Chris A (388J)
>> <ch...@jpl.nasa.gov> wrote:
>>> Hey Ryan,
>>>
>>> On Mar 5, 2012, at 2:27 PM, Ryan McKinley wrote:
>>>
>>>>>
>>>>> Unfortunately I do see it as a roadblock. The goal of SIS was to write
>>>>> a pure ALv2 licensed (or compatible) spatial library and toolkit, which
>>>>> in my mind does *not* include any dependencies (even optional) on
>>>>> LGPL components.
>>>>>
>>>>
>>>> Got it, this was my understanding. The goal of SIS is to build an ASL
>>>> version of JTS -- that's a great goal, just not one I have any
>>>> energy/time to contribute towards.
>>>
>>> No worries. I appreciate you reaching out. Is there a way to have everything
>>> in spatial4j that doesn't rely on the LGPL code here?
>>>
>>
>> possible, but it makes testing overly complicated. I want/need the
>> JTS implementations to be 1st class test citizens. (This is actually
>> the biggest reason this is not directly in the lucene)
>
> Gotcha.
>
>>
>>
>>>>
>>>>
>>>>> Is there any way that the works of spatial4j could be replaced by ALv2 code?
>>>>
>>>> The code in spatial4j is all ASL. If there were a viable ASL polygon
>>>> library, we could use that too.
>>>
>>> How can you have an ALv2 licensed library that has dependencies on LGPL upstream
>>> components? Doesn't the LGPL and its viral nature [1] spill into your code?
>>>
>>
>> You may be confusing LGPL with GPL.
>>
>> "Applications which link to LGPL libraries need not be released under the LGPL"
>> http://www.gnu.org/licenses/lgpl-java.html
>>
>> The key thing they want to make sure is that you don't bundle your own
>> version of the .jar file (section 6)
>
> Well that's the FSF's interpretation, and *not* Apache's. See this:
>
> (search for LGPL)
>
> http://www.apache.org/legal/resolved.html
>
> Which licenses may NOT be included within Apache products?
>
> • Binary Code License (BCL)
> • Special exceptions to the GNU GPL (e.g. GNU Classpath)
> • GNU GPL 1, 2, 3
> • GNU LGPL 2, 2.1, 3
> • Affero GPL 3
> • NPL 1.0/NPL 1.1
> • QPL
> • Sleepycat License
> • Microsoft Limited Public License
>
> GNU LGPL
> The LGPL is ineligible primarily due to the restrictions it places on larger works, violating the third license criterion. Therefore, LGPL-licensed works must not be included in Apache products.
> Special exceptions to the GNU GPL
> Some copyright holders have licensed their works under the GPL with special exceptions. Although these exceptions may appear to be addressing the restrictions disallowed by the ASF's first and second license criteria, the exceptions may only apply to software not "derived from or based on" the covered work. This references terms defined in the GPL that include works that "use" or "contain" the work.
>
> This is also the GPL and ALv2 compatible, just for reference:
>
> http://www.apache.org/licenses/GPL-compatibility.html
>
> You may find other interpretations in mailing lists, or from
> other folks, or via mail archives, but my preference would be
> taking the explicit understanding from the Legal resolved
> page above.
>
> Cheers,
> Chris
>
Cool -- I have no intention of debating this... or asking legal, or whatever.
It is very clear that you can not *distribute* lgpl files. The
statement Greg pointed to earlier from the same page implies that you
can compile/test with LGPL dependencies:
Apache projects cannot distribute any such components. However, if the
component is only needed for optional features, a project can provide
the user with instructions on how to obtain and install the
non-included work. Optional means that the component is not required
for standard use of the product or for the product to achieve a
desirable level of quality. The question to ask yourself in this
situation is:
"Will the majority of users want to use my product without adding the
optional components?
- - - - - - -
That said, I totally respect the choice not to want an external JTS
compile/test dependency.
ryan
Re: spatial4j at SIS?
Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
Hi Ryan,
On Mar 5, 2012, at 2:57 PM, Ryan McKinley wrote:
> On Mon, Mar 5, 2012 at 2:34 PM, Mattmann, Chris A (388J)
> <ch...@jpl.nasa.gov> wrote:
>> Hey Ryan,
>>
>> On Mar 5, 2012, at 2:27 PM, Ryan McKinley wrote:
>>
>>>>
>>>> Unfortunately I do see it as a roadblock. The goal of SIS was to write
>>>> a pure ALv2 licensed (or compatible) spatial library and toolkit, which
>>>> in my mind does *not* include any dependencies (even optional) on
>>>> LGPL components.
>>>>
>>>
>>> Got it, this was my understanding. The goal of SIS is to build an ASL
>>> version of JTS -- that's a great goal, just not one I have any
>>> energy/time to contribute towards.
>>
>> No worries. I appreciate you reaching out. Is there a way to have everything
>> in spatial4j that doesn't rely on the LGPL code here?
>>
>
> possible, but it makes testing overly complicated. I want/need the
> JTS implementations to be 1st class test citizens. (This is actually
> the biggest reason this is not directly in the lucene)
Gotcha.
>
>
>>>
>>>
>>>> Is there any way that the works of spatial4j could be replaced by ALv2 code?
>>>
>>> The code in spatial4j is all ASL. If there were a viable ASL polygon
>>> library, we could use that too.
>>
>> How can you have an ALv2 licensed library that has dependencies on LGPL upstream
>> components? Doesn't the LGPL and its viral nature [1] spill into your code?
>>
>
> You may be confusing LGPL with GPL.
>
> "Applications which link to LGPL libraries need not be released under the LGPL"
> http://www.gnu.org/licenses/lgpl-java.html
>
> The key thing they want to make sure is that you don't bundle your own
> version of the .jar file (section 6)
Well that's the FSF's interpretation, and *not* Apache's. See this:
(search for LGPL)
http://www.apache.org/legal/resolved.html
Which licenses may NOT be included within Apache products?
• Binary Code License (BCL)
• Special exceptions to the GNU GPL (e.g. GNU Classpath)
• GNU GPL 1, 2, 3
• GNU LGPL 2, 2.1, 3
• Affero GPL 3
• NPL 1.0/NPL 1.1
• QPL
• Sleepycat License
• Microsoft Limited Public License
GNU LGPL
The LGPL is ineligible primarily due to the restrictions it places on larger works, violating the third license criterion. Therefore, LGPL-licensed works must not be included in Apache products.
Special exceptions to the GNU GPL
Some copyright holders have licensed their works under the GPL with special exceptions. Although these exceptions may appear to be addressing the restrictions disallowed by the ASF's first and second license criteria, the exceptions may only apply to software not "derived from or based on" the covered work. This references terms defined in the GPL that include works that "use" or "contain" the work.
This is also the GPL and ALv2 compatible, just for reference:
http://www.apache.org/licenses/GPL-compatibility.html
You may find other interpretations in mailing lists, or from
other folks, or via mail archives, but my preference would be
taking the explicit understanding from the Legal resolved
page above.
Cheers,
Chris
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.a.mattmann@nasa.gov
WWW: http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Re: spatial4j at SIS?
Posted by Ryan McKinley <ry...@gmail.com>.
On Mon, Mar 5, 2012 at 2:34 PM, Mattmann, Chris A (388J)
<ch...@jpl.nasa.gov> wrote:
> Hey Ryan,
>
> On Mar 5, 2012, at 2:27 PM, Ryan McKinley wrote:
>
>>>
>>> Unfortunately I do see it as a roadblock. The goal of SIS was to write
>>> a pure ALv2 licensed (or compatible) spatial library and toolkit, which
>>> in my mind does *not* include any dependencies (even optional) on
>>> LGPL components.
>>>
>>
>> Got it, this was my understanding. The goal of SIS is to build an ASL
>> version of JTS -- that's a great goal, just not one I have any
>> energy/time to contribute towards.
>
> No worries. I appreciate you reaching out. Is there a way to have everything
> in spatial4j that doesn't rely on the LGPL code here?
>
possible, but it makes testing overly complicated. I want/need the
JTS implementations to be 1st class test citizens. (This is actually
the biggest reason this is not directly in the lucene)
>>
>>
>>> Is there any way that the works of spatial4j could be replaced by ALv2 code?
>>
>> The code in spatial4j is all ASL. If there were a viable ASL polygon
>> library, we could use that too.
>
> How can you have an ALv2 licensed library that has dependencies on LGPL upstream
> components? Doesn't the LGPL and its viral nature [1] spill into your code?
>
You may be confusing LGPL with GPL.
"Applications which link to LGPL libraries need not be released under the LGPL"
http://www.gnu.org/licenses/lgpl-java.html
The key thing they want to make sure is that you don't bundle your own
version of the .jar file (section 6)
Re: spatial4j at SIS?
Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
oops, forgot [1]:
http://en.wikipedia.org/wiki/Copyleft
I guess it depends on a lot of things (the LGPL version, any reciprocity
added by the JTS folks, etc, etc.), which I haven't looked at.
Cheers,
Chris
On Mar 5, 2012, at 2:34 PM, Mattmann, Chris A (388J) wrote:
> Hey Ryan,
>
> On Mar 5, 2012, at 2:27 PM, Ryan McKinley wrote:
>
>>>
>>> Unfortunately I do see it as a roadblock. The goal of SIS was to write
>>> a pure ALv2 licensed (or compatible) spatial library and toolkit, which
>>> in my mind does *not* include any dependencies (even optional) on
>>> LGPL components.
>>>
>>
>> Got it, this was my understanding. The goal of SIS is to build an ASL
>> version of JTS -- that's a great goal, just not one I have any
>> energy/time to contribute towards.
>
> No worries. I appreciate you reaching out. Is there a way to have everything
> in spatial4j that doesn't rely on the LGPL code here?
>
>>
>>
>>> Is there any way that the works of spatial4j could be replaced by ALv2 code?
>>
>> The code in spatial4j is all ASL. If there were a viable ASL polygon
>> library, we could use that too.
>
> How can you have an ALv2 licensed library that has dependencies on LGPL upstream
> components? Doesn't the LGPL and its viral nature [1] spill into your code?
>
>>
>> It looks like github is an appropriate place for the spatial4j development.
>
> Would be great to reach some sort of compromise, and like I said, I'm totally
> supportive of what you guys are trying to do. If we can't, I wish you the best
> and hopefully we can build an ALv2 licensed polygon support capability
> that you guys could leverage, and perhaps help merge the communities
> then.
>
> Thanks!
>
> Cheers,
> Chris
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Chris Mattmann, Ph.D.
> Senior Computer Scientist
> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> Office: 171-266B, Mailstop: 171-246
> Email: chris.a.mattmann@nasa.gov
> WWW: http://sunset.usc.edu/~mattmann/
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Adjunct Assistant Professor, Computer Science Department
> University of Southern California, Los Angeles, CA 90089 USA
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.a.mattmann@nasa.gov
WWW: http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Re: spatial4j at SIS?
Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
Hey Ryan,
On Mar 5, 2012, at 2:27 PM, Ryan McKinley wrote:
>>
>> Unfortunately I do see it as a roadblock. The goal of SIS was to write
>> a pure ALv2 licensed (or compatible) spatial library and toolkit, which
>> in my mind does *not* include any dependencies (even optional) on
>> LGPL components.
>>
>
> Got it, this was my understanding. The goal of SIS is to build an ASL
> version of JTS -- that's a great goal, just not one I have any
> energy/time to contribute towards.
No worries. I appreciate you reaching out. Is there a way to have everything
in spatial4j that doesn't rely on the LGPL code here?
>
>
>> Is there any way that the works of spatial4j could be replaced by ALv2 code?
>
> The code in spatial4j is all ASL. If there were a viable ASL polygon
> library, we could use that too.
How can you have an ALv2 licensed library that has dependencies on LGPL upstream
components? Doesn't the LGPL and its viral nature [1] spill into your code?
>
> It looks like github is an appropriate place for the spatial4j development.
Would be great to reach some sort of compromise, and like I said, I'm totally
supportive of what you guys are trying to do. If we can't, I wish you the best
and hopefully we can build an ALv2 licensed polygon support capability
that you guys could leverage, and perhaps help merge the communities
then.
Thanks!
Cheers,
Chris
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.a.mattmann@nasa.gov
WWW: http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Re: spatial4j at SIS?
Posted by Ryan McKinley <ry...@gmail.com>.
>
> Unfortunately I do see it as a roadblock. The goal of SIS was to write
> a pure ALv2 licensed (or compatible) spatial library and toolkit, which
> in my mind does *not* include any dependencies (even optional) on
> LGPL components.
>
Got it, this was my understanding. The goal of SIS is to build an ASL
version of JTS -- that's a great goal, just not one I have any
energy/time to contribute towards.
> Is there any way that the works of spatial4j could be replaced by ALv2 code?
The code in spatial4j is all ASL. If there were a viable ASL polygon
library, we could use that too.
It looks like github is an appropriate place for the spatial4j development.
Thanks
Ryan
Re: spatial4j at SIS?
Posted by Greg Reddin <gr...@gmail.com>.
On Mon, Mar 5, 2012 at 3:47 PM, Mattmann, Chris A (388J)
<ch...@jpl.nasa.gov> wrote:
> Unfortunately I do see it as a roadblock. The goal of SIS was to write
> a pure ALv2 licensed (or compatible) spatial library and toolkit, which
> in my mind does *not* include any dependencies (even optional) on
> LGPL components.
>
> As I understand it, in this case, JTS is providing the polygon support.
> Polygon support is something we'd really like to support in SIS, so
> to me, this dependency (though optional in e.g., Lucene) is a core
> feature of SIS and something most of the eventual users of the system
> would want.
Makes sense. Thanks for clarifying.
Greg
Re: spatial4j at SIS?
Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
Hi Greg,
On Mar 5, 2012, at 1:33 PM, Greg Reddin wrote:
> On Mon, Mar 5, 2012 at 3:17 PM, Adam Estrada <es...@gmail.com> wrote:
>> http://www.apache.org/legal/resolved.html From there it looks like LGPL is
>> a definite no no...Does this mean that it can't be included as an option
>> when being built?
>
> I think it is a definite no no for "inclusion" in a project, meaning
> we can't include any LGPL wok in SIS. But I think we are talking about
> an optional dependency here. See the following blurb from the
> above-linked page:
>
> "Can Apache projects rely on components whose licensing affects the
> Apache product?
> Apache projects cannot distribute any such components. However, if the
> component is only needed for optional features, a project can provide
> the user with instructions on how to obtain and install the
> non-included work. Optional means that the component is not required
> for standard use of the product or for the product to achieve a
> desirable level of quality. The question to ask yourself in this
> situation is:
>
> Will the majority of users want to use my product without adding the
> optional components?"
>
> So, if I understand everything correctly, I don't see this as a
> roadblock. It is possible that I don't understand it correctly though
> :-)
Unfortunately I do see it as a roadblock. The goal of SIS was to write
a pure ALv2 licensed (or compatible) spatial library and toolkit, which
in my mind does *not* include any dependencies (even optional) on
LGPL components.
As I understand it, in this case, JTS is providing the polygon support.
Polygon support is something we'd really like to support in SIS, so
to me, this dependency (though optional in e.g., Lucene) is a core
feature of SIS and something most of the eventual users of the system
would want.
Cheers,
Chris
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.a.mattmann@nasa.gov
WWW: http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Re: spatial4j at SIS?
Posted by Greg Reddin <gr...@gmail.com>.
On Mon, Mar 5, 2012 at 3:17 PM, Adam Estrada <es...@gmail.com> wrote:
> http://www.apache.org/legal/resolved.html From there it looks like LGPL is
> a definite no no...Does this mean that it can't be included as an option
> when being built?
I think it is a definite no no for "inclusion" in a project, meaning
we can't include any LGPL wok in SIS. But I think we are talking about
an optional dependency here. See the following blurb from the
above-linked page:
"Can Apache projects rely on components whose licensing affects the
Apache product?
Apache projects cannot distribute any such components. However, if the
component is only needed for optional features, a project can provide
the user with instructions on how to obtain and install the
non-included work. Optional means that the component is not required
for standard use of the product or for the product to achieve a
desirable level of quality. The question to ask yourself in this
situation is:
Will the majority of users want to use my product without adding the
optional components?"
So, if I understand everything correctly, I don't see this as a
roadblock. It is possible that I don't understand it correctly though
:-)
Greg
Re: spatial4j at SIS?
Posted by Joe White <wh...@gmail.com>.
According to the Apache documentation Adam pointed to, then JTS is a no-no. I'm not sure how the optionality (if that is a word), modifies this. I would probably read it as "the binaries that can be downloaded can't have it, but here are instructions on how to include it if you want to build it yourself", much the same way that GDAL does with other GPL libraries, like it's support for PDF using popplr. Any thoughts?
Joe
On Mar 5, 2012, at 4:17 PM, Adam Estrada wrote:
> http://www.apache.org/legal/resolved.html From there it looks like LGPL is
> a definite no no...Does this mean that it can't be included as an option
> when being built?
>
> Adam
>
> On Mon, Mar 5, 2012 at 4:09 PM, Joe White <wh...@gmail.com> wrote:
>
>> I think this would be a great addition to SIS. I did a cursory search on
>> JTS and Maven and didn't turn up anything other than a feature request from
>> 2008 asking for JTS to be added to iBiblio as a Maven repo. There may be
>> some additional ugliness getting it and Maven working together, but it
>> shouldn't be too bad, and there is already a request out there for it.
>>
>> Joe
>>
>> On Mar 5, 2012, at 3:30 PM, Adam Estrada wrote:
>>
>>> Hi Ryan! I for one would love to see this integrated in to SIS. The fact
>>> that JTS is "optional" is a huge benefit for those who
>>> could potentially need its capabilities. And yes...in time, there will be
>>> an Apache version that resides in trunk but for now I like that there is
>>> optional support for it. How do you propose that it gets built? Can JTS
>>> install/build through Maven? I honestly have not looked through the JTS
>>> sources.
>>>
>>> Adam
>>>
>>> On Mon, Mar 5, 2012 at 3:09 PM, Ryan McKinley <ry...@gmail.com> wrote:
>>>
>>>> Hello-
>>>>
>>>> We have been working for a while to build better spatial support into
>>>> Lucene. While integrating with lucene, we separated out the core
>>>> spatial code from the lucene specific stuff. Since the code has
>>>> compile/test dependencies on JTS, we hosted it at github. See:
>>>> https://spatial4j.com/
>>>>
>>>> The code itself is ASL, but we want to enable complex polygon support
>>>> for people who choose to include the LGPL library JTS. In time, there
>>>> may be pure ASL polygon solutions.
>>>>
>>>> From previous discussions, my believe this is a non-starter for SIS.
>>>> Is this accurate? Or should we investigate how this code can work
>>>> together?
>>>>
>>>> Thanks
>>>> Ryan
>>>>
>>
>>
Re: spatial4j at SIS?
Posted by Adam Estrada <es...@gmail.com>.
http://www.apache.org/legal/resolved.html From there it looks like LGPL is
a definite no no...Does this mean that it can't be included as an option
when being built?
Adam
On Mon, Mar 5, 2012 at 4:09 PM, Joe White <wh...@gmail.com> wrote:
> I think this would be a great addition to SIS. I did a cursory search on
> JTS and Maven and didn't turn up anything other than a feature request from
> 2008 asking for JTS to be added to iBiblio as a Maven repo. There may be
> some additional ugliness getting it and Maven working together, but it
> shouldn't be too bad, and there is already a request out there for it.
>
> Joe
>
> On Mar 5, 2012, at 3:30 PM, Adam Estrada wrote:
>
> > Hi Ryan! I for one would love to see this integrated in to SIS. The fact
> > that JTS is "optional" is a huge benefit for those who
> > could potentially need its capabilities. And yes...in time, there will be
> > an Apache version that resides in trunk but for now I like that there is
> > optional support for it. How do you propose that it gets built? Can JTS
> > install/build through Maven? I honestly have not looked through the JTS
> > sources.
> >
> > Adam
> >
> > On Mon, Mar 5, 2012 at 3:09 PM, Ryan McKinley <ry...@gmail.com> wrote:
> >
> >> Hello-
> >>
> >> We have been working for a while to build better spatial support into
> >> Lucene. While integrating with lucene, we separated out the core
> >> spatial code from the lucene specific stuff. Since the code has
> >> compile/test dependencies on JTS, we hosted it at github. See:
> >> https://spatial4j.com/
> >>
> >> The code itself is ASL, but we want to enable complex polygon support
> >> for people who choose to include the LGPL library JTS. In time, there
> >> may be pure ASL polygon solutions.
> >>
> >> From previous discussions, my believe this is a non-starter for SIS.
> >> Is this accurate? Or should we investigate how this code can work
> >> together?
> >>
> >> Thanks
> >> Ryan
> >>
>
>
Re: spatial4j at SIS?
Posted by Joe White <wh...@gmail.com>.
I think this would be a great addition to SIS. I did a cursory search on JTS and Maven and didn't turn up anything other than a feature request from 2008 asking for JTS to be added to iBiblio as a Maven repo. There may be some additional ugliness getting it and Maven working together, but it shouldn't be too bad, and there is already a request out there for it.
Joe
On Mar 5, 2012, at 3:30 PM, Adam Estrada wrote:
> Hi Ryan! I for one would love to see this integrated in to SIS. The fact
> that JTS is "optional" is a huge benefit for those who
> could potentially need its capabilities. And yes...in time, there will be
> an Apache version that resides in trunk but for now I like that there is
> optional support for it. How do you propose that it gets built? Can JTS
> install/build through Maven? I honestly have not looked through the JTS
> sources.
>
> Adam
>
> On Mon, Mar 5, 2012 at 3:09 PM, Ryan McKinley <ry...@gmail.com> wrote:
>
>> Hello-
>>
>> We have been working for a while to build better spatial support into
>> Lucene. While integrating with lucene, we separated out the core
>> spatial code from the lucene specific stuff. Since the code has
>> compile/test dependencies on JTS, we hosted it at github. See:
>> https://spatial4j.com/
>>
>> The code itself is ASL, but we want to enable complex polygon support
>> for people who choose to include the LGPL library JTS. In time, there
>> may be pure ASL polygon solutions.
>>
>> From previous discussions, my believe this is a non-starter for SIS.
>> Is this accurate? Or should we investigate how this code can work
>> together?
>>
>> Thanks
>> Ryan
>>
Re: spatial4j at SIS?
Posted by Adam Estrada <es...@gmail.com>.
Hi Ryan! I for one would love to see this integrated in to SIS. The fact
that JTS is "optional" is a huge benefit for those who
could potentially need its capabilities. And yes...in time, there will be
an Apache version that resides in trunk but for now I like that there is
optional support for it. How do you propose that it gets built? Can JTS
install/build through Maven? I honestly have not looked through the JTS
sources.
Adam
On Mon, Mar 5, 2012 at 3:09 PM, Ryan McKinley <ry...@gmail.com> wrote:
> Hello-
>
> We have been working for a while to build better spatial support into
> Lucene. While integrating with lucene, we separated out the core
> spatial code from the lucene specific stuff. Since the code has
> compile/test dependencies on JTS, we hosted it at github. See:
> https://spatial4j.com/
>
> The code itself is ASL, but we want to enable complex polygon support
> for people who choose to include the LGPL library JTS. In time, there
> may be pure ASL polygon solutions.
>
> From previous discussions, my believe this is a non-starter for SIS.
> Is this accurate? Or should we investigate how this code can work
> together?
>
> Thanks
> Ryan
>