Added by jgarnett, last edited by jgarnett on Jun 19, 2008  (view change)

Labels

 
(None)

GeoAPI is an official OGC project capturing standards as normal Java interfaces. This is great especially if you do not have time or money to figure out the standards on your own. The GeoAPI process results in interfaces that are well documented, and often the result of collaboration between vendors (or even between GeoTools and other open source projects).

Relationship with GeoTools

GeoTools is all about implementing spatial solutions, and we do our very best to follow a don't invent here policy (rather than get off topic).

We make use of the Java Topology Suite to represent "Simple" Geometry, and the GeoAPI project to represent everything else. We have been forced to define some interfaces of our own (we are pragmatic and do not wait for a standard) we will switch to GeoAPI interfaces the moment they are ready. Well actually several moments after they are ready – we are usually stuck on time and/or money.

GeoTools stands on the shoulders of giants. On occasion they kick us down, but that is why we have maven to track the dependencies. Please use maven, life is too short to get class cast exceptions.

Historic Relationship with GeoAPI:

  • 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
  • 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.
You are Here
<< >>

External Links: