Welcome to the GeoGit project, exploring the use of distributed management of spatial data. GeoGit draws inspiration from Git, but adapts its core concepts to handle versioning of geospatial data. Users are able to import raw geospatial data (currently from Shapefiles, PostGIS or SpatiaLite) in to a repository where every change to the data is tracked. These changes can be viewed in a history, reverted to older versions, branched in to sandboxed areas, merged back in, and pushed to remote repositories. GeoGit is written in Java, available under the BSD License.

For background reading see these two papers on the spatial distributed versioning Concept and Implementation..

Project Lead: Gabriel Roldan

License: all source code is licensed under the BSD New License, except for the GeoServer plugin which is available under the GPL 2.0 License.

Status: A 0.1 version has been released and it is available for download, with a full commandline interface to import data and work with repositories. A web API and user interface is slated for 0.2.

Version 0.1.0 from SourceForge. Documentation available for download and online.

Unzip the geogit-cli-app-0.1.0.zip to an applications directory, and then add the unzipped geogit/bin/ folder to your PATH.

See the QuickStart guide for an introduction to GeoGit. Additional information available at the full Manual.

If you want to get involved in the development of GeoGit, build GeoGit yourself or know more about the technical details behind GeoGit, check the developers section.

Everyone is invited to participate in GeoGit and help in its development.

Discussion takes place on our geogit google group. Please join and introduce yourself, we'd love to help, and to figure out ways for you to get involved.

There is also a GeoGit IRC channel on freenode (#geogit).

Participation is encouraged using the github fork and pull request workflow:

• Include test case demonstrating functionality
• Contributions are expected to pass all tests and not break the build
• Include proper license headers on your contributed files

More information on this workflow and how to remotely collaborate in a project like GeoGit can be found at the GitHub help page

Issues to help out on are at our issue tracker.

Before contributing code, read the developers section for technical details about how to build and develop GeoGit.

For those who can't code help on documentation is always appreciated, all docs can be found at https://github.com/opengeo/GeoGit/tree/master/doc/ and contributed to by editing in ReStructuredText and using standard GitHub workflows.

Our build is actively monitored using hudson.