Hello Tim

Tim Swanson a écrit :
> My first question involves the status of the relationship between the
> GeoAPI and GeoTools.

Very close indeed. There is a bit of history:

* GeoAPI has been funded in 2002 by the same guy (James McGill) who
   funded GeoTools. The aim at that time was to provide common API for
   independant projects like GeoTools and OpenJump, so we could exchange
   code more easily.

* Later on, the Open Geospatial consortium started a project with
   similar goal. The project name was "GO-1" (for "Geospatial Object")
   and was leaded by Polexis, a former USA compagny.

* Givin the similarity between GO-1 and GeoAPI goals, we got in touch
   each other and managed to merge the two projects.

* Polexis produces the following specification, which became an official
   OGC specification. It was based on GeoAPI 2.0, released in same time:
   http://www.opengeospatial.org/standards/go

* Later, Polexis has been bough by Sys Technology, which seems to have
   different priorities. Their investment in GeoAPI / GO-1 stopped.

* About one year ago, GO-1 / GeoAPI working group at OGC has been
   disolved du to lack of activity.

* GeoTools contributor took over the GeoAPI project. We are for now
   the main contributor.

* We asked to OGC to recreate a new GeoAPI working group. They agree,
   the only thing missing is to find volunter time. For now there is
   Geomatys, but we need at least 3 other guys from other compagnies
   (would you be interrested?)

* In the main time, we released GeoAPI milestone as we release GeoTools.
   GeoAPI 2.1 for GeoTools 2.4, and GeoAPI 2.2 will be for GeoTools 2.5.
   But only GeoAPI 2.0 is "OGC official". GeoAPI 2.1 and 2.2 should be
   understood as milestone only. In order to get a new "OGC official"
   GeoAPI, we need to recreate the above-mentioned GeoAPI working group
   and get GeoAPI voted at OGC.

* GeoAPI 2.2-SNAPSHOT is the most up-to-date version and still in
   active development (mostly javadoc fixes at this time). The
   Javadoc page is automatically regenerated every 24 hours.

* GeoTools 2.5-SNAPSHOT on trunk is aligned on GeoAPI 2.2-SNAPSHOT.


> Second, which version of the GeoAPI should I be using. The GeoTools
> 2.5M2 download contains two jars: geoapi-2.2-M2.jar and
> geoapi-2.2-SNAPSHOT.jar. Which is more recent (I'm guessing SNAPSHOT)?
> Which should I use? The GeoTools 2.4 download uses GeoAPI 2.1.

2.2-SNAPSHOT is more recent. I suggest those, especially since we switched very 
recently (yesterday actually!) from the legacy JSR-108 to JSR-275 for units 
management.


> How do these jars relate to the release builds offered by the GeoAPI
> itself?

They are absolutly identical.


> (Also, is there a mailing list for the GeoAPI?)

Yes.

Home page, which charter and stuff like that:
http://geoapi.sourceforge.net/

GeoAPI 2.2-SNAPSHOT javadoc (generated every days):
http://geoapi.sourceforge.net/snapshot/javadoc/index.html

Mailing lists:
http://geoapi.sourceforge.net/geoapi/mail-lists.html

Issues tracker:
http://jira.codehaus.org/browse/GEO

        Regards,

                Martin

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Geotools-gt2-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users

Reply via email to