I've been working quitely with Jody Garnett off the mailing list. We've been exlporing opportunities for GeoTools/OpenJUMP collaborartion.
We've decided that we shouldn't let our different FeatureModels be an unsurmountable obstacle to cooperation. We are investigating other areas where we can work together. I must admit this hasn't been all ice cream and cake, and I don't agree with everything the GeoTools developers have to tell me. There is some common ground we can build on despite this, thanks to Jody's efforts. One of these areas is data access or data i/o. Jody and I are talking about designing a set of interfaces that will allow our two projects, at some point in the future, to take advantage of the same data access code. There is really no reason to have duplicate code between our projects in this regard. Our current plans are to offer up some very basic and low-level collection of primitive Java data types, Java Strings, and a geometry representation. (We are still working on how the geometry will be represented.) Our goal is to have a feature representation simple enough to allow easy conversion to the different feature models. I know not everyone on this list is realy excited about cooperation with GeoTools, but I'm taking baby steps here. Jody and I agreed today that it is impractical to expect a lot of code sharing at the present time. However, we want to define a set of interfaces that we can work towards implementing if and when our projects decide to make updates/changes to their I/O framwork for other reasons. (The idea is to make the changes for collaboration when the changes would be made for other reasons anyways, so no one feels like they are getting their bowl of cheerios peed in for another project's sake.) Here is why I am even boring you guys with all of this: Do we currently have any plans for the development of our data access or data i/o framwork? Would anyone be interested in working with me on a plan for this development, and then incorporating this plan into a design of the interfaces that I hope we can share with GeoTools in a couple of years? Is there any major problems with the data access or data I/O that I need to look at when I start work in this? I appreciate your feedback and ask that you keep your mind open to the possibilities. The Sunburned Surveyor P.S. - This doesn't mean that I am forgetting about the Deegree Project. I plan on using their code to access ESRI Shapefiles in my FeatureCache. :] ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
