Here is some stuff we are working on:
- Catalog — New catalog interfaces.
- Display Package
- Feature Model — consistent Feature Model based on ISO 19109
- GridCoverage — Grid coverage interfaces derived from ISO 19123 specification.
- New package for Styles
- Repository Organization
Links to current interfaces:
Welcome to GeoAPI development, this project has a bit of a formal process to go through for adoption of new interfaces:
- Jump on the email list and talk to us, we can help confirm you are working against a useful specification
- Starting Research
- create a branch for your creation (say "dublincore")
- create the set of interfaces in your svn branch
- mark up the interface with annotations refering to the specification (their is a javadoc based audit)
- Interoptability test:
- merge changes onto trunk and make a snapshot jar
- Provided evidence of two commercial or one open source implementation
- this is the only QA we can do for an interface only project.
- Review Process
- Write up a request for change that can be presented to the OGC GeoAPI working group
- Create a stable branch 2.X.X of all work ready for review
- Standards Conformance: Wait for a review from the GeoAPI Working group, and respond/revise as required
- Release
- Tag 2.X.0 release of all work approved by the working group
- Release the new version of GeoAPI
How to compile the stable release and/or trunk
When an interface needs to be revised, it is modified (in your branch or on trunk). The interface or changes
will move to a stable release once approved by OGC.
Examples of such interfaces are org.opengis.coverage.Coverage and org.opengis.feature.FeatureCollection. Interfaces with those names exist in both 2.0.x and trunk, which leads to an apparent conflict. Actually, it is a conflict only if the developer tries to compile with these two directories in the same project. Please don't ![]()
Instructions for Java 1.4 users
The script to1.4xml in the root of the source tree can be used to create 1.4 compatable code from the base geoapi classes. Usage:
- run the to1.4.xml script (default target)
- the directory dist/src will be created under the root of the source tree which contains the 1.4 compatable code.