> > 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
