Greg Reynolds wrote:
We've been having this conversation as well about adding the Feature interfaces to GeoAPI. Currently Chris Dillard is adding some improvements to the GeoTools WFS-T
Do you mean GeoServer? GeoServer is a completely separate project from Geotools (although we all try to work together).
and we would like to see that code implement appopriate GeoAPI features instead of the currect concrete class representation.
Geotools currently uses an interface for Feature (not a concrete class), its stated intention is to match GeoAPI interfaces when they are made available.
I am not sure what GeoAPI/Martin's timeline is for defining Geometry & Feature interfaces is.
<>Could you please coordinate with Chris Dillard which interfaces you intend to add.
We are *right now* adding Metadata interfaces to Geotools, we have started dialog with GeoAPI to ensure our work will be upward compatible.
We were only exploring the various Feature APIs to prevent conflict with respect to Metadata methods.
<>Possibly we could add a subset of those interfaces if the timing would be better to do on our end?
If Chris Dillard could take this scheduling conversation to the GeoServer or Geotools email lists respectively.
My impression is:
- Martin will start a Geotools 2.2 branch on exactly this subject (Geometry & Feature) a some point in the next six months.
- GeoServer is planning a 1.2 release in early July, although plans for the next 1.3 branch should be address to Chris Holmes (or the geoserver email list).