Sunburned Surveyor wrote: > I've decided to take an incremental approach to the development of the > package. This first release will only include support for waypoint > entities, not for routes or tracks. That sounds fine; release early release often. > elements associated with a waypoint, but it needs some more work. (I > need to research some JDOM stuff before I can complete this > full-feature class.) > Just a note: I have used both DOM and JDOM now and find both similarity strange and tricky. JDOM has not really been brought up to speed with Java 5 collections yet; so I am finding it less useful in day to day work. > Here are my questions: > > I currently have no plans to integrate the GeoTools Feature Model into > my code. I'll be reading the Waypoint Observation GML 2 files directly > into OpenJUMP. With this in mind, does my code really have a place in > GeoTools? What if no other developer will plan to implement GeoTools > feature support for GPX using my low-level code? (I must honestly > admit that I don't plan on this. > Depends what your goals are; not all spatial data is features (we have a WMS module that does not work with features for example). As such its documentation requirements are greater but such is life. > GeoTools have room for low-level i/o code, or should it only contain > code that directly relates to the GeoTools feature model? > As module maintainer you get to decide what it is you are working on; you may find yourself flooded with questions along the lines of "How do I draw waypoints?" and "How do I ready a GPX file?". If you have those kind of questions answer in the wiki you can at least answer people with a URL. > It is important that I answer this question now, before my first release. If > the other GeoTools programmer's feel that my code doesn't belong, then I want > to rename my packages. I'm currently using a org.geotools.gpx2 prefix on all > of my packages. > Landon; GeoTools is not really a democracy - as module maintainer you are making code available for others to use (and you are dictator for your module). We have documented a few hard and fast requirements which you are aware of (OSGeo (c), LGPL etc...). And a few requirements for including your work in the official download (user guide page and test coverage). Beyond that you are on your own ... and that is a good thing :-)
For work that builds on top of the core GeoTools library (or does something different) they generally show up as "extensions" (rather than "plugins"). Jody ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
