Sure GeoTools strives to be an implementation of most things geospatial. We tried for a bit to provide user interface widgets as well .. but did not have enough volunteer time for that.
We are not really interested in defining interfaces ... so whenever a GeoAPI interface is available we try and make use of it. We also make use of GeoAPI for collaboration with other open source and proprietary projects. GeoTools is sometimes used to explore implementation alternatives; the results of which are pushed back into GeoAPI (and the specifications that it implements). GeoAPI has a formal process (and review by a working group) so our changes are not simply accepted; indeed it is much better if they are the result of compromise with more than one implementation. You ask a lot of specific questions about process ... the real answer (and stress you will find) is volunteer time. Occasionally we are paid to work on GeoAPI (you can see this in the recent update of GeoAPI metadata - bringing it in line with recent ISO19115 work). We used GeoTools as a sample implementation to make sure the API changes were sane; the result will be available at the end of the month. The other way things work is when GeoTools runs out of steam. The current GridCoverage interface is based on an old OGC specification that has been deprecated (it only suppors 2D coverages). Now OGC tells us to use some ISO specification that I have not even scene yet. One of the Google Summer of Code students is going to take a run at creating N-Dimensional Coverage interfaces - when they do this we will start by looking at the GeoAPI interfaces, aligning them with the ISO coverage specification and asking the student to implement in GeoTools. For your specific question - not yet. We have looked at (and fixed the holes) in the GeoAPI FeatureModel. The interfaces as they stand are complete (although we will strip out some of the generics stuff before it is released). GeoTools will transition to this new model over the course of the summer by all indication. Actually we will transition to a subclass called SimpleFeature (where attributes are not duplicated and all appear in the same order). Our specific transition strategy is to set up the following: 1) org.opengis.feature.Feature 2) org.opengis.feature.simple.SimpleFeature extends Feature 3) org.geotools.feature.Feature extends SimpleFeature 4) org.geotools.feature.DefaultFeature implements Feature, SimpleFeature So if your are code consuming features for display #1 is good. If you are code that would like to only work with simple content (say creating features from a shapefile) then you could make use of #2. The last two options are available for backwards compatibility. Cheers, Jody > I'm wondering what the relationship is between GeoTools and the > GeoAPI. I know that GeoTools provides an implementation of at least > portions of the GeoAPI, but I was hoping to get some more of the details. > > When may a GeoTools interface that corresponds to a GeoAPI interface > contain significant additions or changes? Are these additions and > changes integrated back into the GeoAPI interface at some point? What > process is used to do this? > > Are all changes in a GeoAPI interface integrated into the > corresponding GeoTools API at some point? What process governs this? > > If I implement code to use the GeoAPI Feature interface, will I be > able pass it an object that implements the GeoTools Feature interface? > > Thanks, > > The Sunburned Surveyor > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------- > 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/ > ------------------------------------------------------------------------ > > _______________________________________________ > Geotools-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/geotools-devel > ------------------------------------------------------------------------- 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/ _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
