The GeoAPI project consists of a standardized part (geoapi) and an experimental part (geoapi-pending). As these two parts are mutually exclusive, users must take care not to mix them in the same project. This separation is guaranteed for all projects that depend only on the Maven central repository (including the final versions of Apache SIS), as the geoapi-pending module is never deployed on this central repository. By contrast, certain SIS development branches may depend on geoapi-pending.

GeoAPI modules are:

• geoapi — includes interfaces covered by the GeoAPI standard of the OGC. The final versions of Apache SIS depend on this module.

• geoapi-pending — contains a copy of all interfaces in the geoapi module (not a dependence) with additions that have not yet been approved as an OGC standard. Some additions appear in interfaces normally defined by the geoapi module, hence the need to copy them. Apache SIS’s development branches depend on this module, but this dependence becomes a dependence on the geoapi standard module when the development branches are merged to the main branch.

• geoapi-conformance — includes a JUnit test suite that developers may use to test their implementations.

• geoapi-examples — includes examples of relatively simple implementations. These examples are placed in the public domain in order to encourage users to copy and adapt them to their needs if Apache SIS services are unsuitable.