I agree with Chris and Martin. If we plan to roll our own set of geometry interfaces, then all we need is the desired architecture. We can fill that in over time as we need things, complete with tests. I'll see if I can lay hands on ISO 19107 to see what the layout looks like.
Joe On Dec 14, 2012, at 12:19 PM, "Mattmann, Chris A (388J)" <[email protected]> wrote: > Hey Martin, > > On 12/14/12 12:57 AM, "Martin Desruisseaux" > <[email protected]> wrote: > >> Hello Chris >> >> The dependency injection mechanism would have prevented any JTS >> dependency declaration in SIS. But anyway, I think we need a SIS >> implementation if we can provide a real 3D library. But the fact that 2 >> Ph.D students worked on that with mitigated success suggests that the >> difficulty is not to be underestimated. > > Yep agreed. And yes, I know to write a fully featured, amazing one is a > huge investment. But, that's the point of Apache, and SIS, and projects, > we're here for the long haul :) > >> >> But if the goal is to provide the minimal infrastructure needed for >> supporting SIS-32, then a possible approach is to identify the minimal >> set of geometric objects needed, write this minimal set in a way that >> "looks like" ISO 19107, then use them until a real ISO 19107 support is >> available... > > +1, this makes total sense and is the way to go. Instead of considering > how we can have our own "JTS" library in SIS today, let's consider the > necessary baby steps to eventually getting there :) And writing the > minimal set of geometric objects, incrementally, object by object, with > tests, and functions, etc., seems to be the best approach. > > Cheers, > Chris > >> >> Martin >> >> >> Le 14/12/12 15:29, Mattmann, Chris A (388J) a écrit : >>> The big thing at Apache is to not introduce "surprises" downstream, >>> e.g., >>> the need to download an LGPL library in order to do something >>> interesting, >>> while obfuscating it with APIs as part of the core ALv2 library. So I >>> would not be in favor of any JTS dependency, even optional. >>> >>> I realize this is limiting in some fashion as JTS is fairly feature rich >>> geometry library. But one of the goals of SIS is to provide a fully ALv2 >>> compatible, "no surprises" and feature rich package which means, unless >>> JTS relicenses itself as ALv2 (which there have been some discussions >>> regarding), then we can't use it in SIS. >>> >>> I am committed to helping with some alternative, so whatever we want to >>> do >>> as a community, even going all the way to rolling our own, let's simply >>> do >>> it, move forward, and deliver something awesome! >> >
