|
ReleaseNotes
Release notes page
version 0.7.5 (released 2012-20-04)This release has some bugfixes, some new modules and it removes the geotools logs that were not wanted. version 0.7.4 (released 2012-25-03)Bugfix release. version 0.7.3 (released 2012-01-03)Upgrade of OMS3 to OMS3.1RC8 Several fixes on modules. New experimental modules. version 0.7.2 (released 2011-07-20)Several fixes on modules. New experimental modules. Best used with the Spatial Toolbox for uDig. version 0.7.1Compatibility fixes to align with the geotools/uDig/jaitools combo. version 0.7.0 (released 2011-05-16)welcomeThis is the first official release of JGrasstools. We have worked about a year prepare not only the algorithms contained in this release, but also the supporting the evolution of the OMS3 framework to gain the main objective of the JGrasstools library: the possibility to link together models in a most possible flexible way, being it along a timeline or in standalone mode, being it in complex and recursive way or in simple standalone mode. quality and testingWe put particular attention to learn from the 10 years of JGrass development, were the worst enemies were updated developer documentation and quality checks on the code. In JGrasstools, for every module that is brought into release in certified status, it is mandatory to have a documentation page (generated from the code. Check out for example the FlowDirections page) and a testcase, which also helps developers to understand the library usage of the module (look for example at the FlowDirections Testcase). a GIS implementation based on OMS3 powered by geotoolsIt is out of the scope of this announcement to explain OMS, to get informed and started on OMS3, you best visit its website. It is important to say that OMS3 is a pure Java, object-oriented modeling framework. OMS allows model construction and model application based on components. OMS3 is a collaborative project active among the U.S. Department of Agriculture and partner agencies and organizations involved with agro-environmental modeling. In OMS3 components are Plain Java Objects enriched with descriptive meta data by means of language annotations. This non-invasive approach over a modeling API minimizes dependencies on the framework. Components default to multi-threaded execution If data flows permits, components are executed in parallel, with no explicit parallel programming required. An OMS3 model scales well in current and future multi-core architectures. Every module of JGrasstools is OMS3 annotated and based on geotools raster and vector formats defined in it. contained modulesThis release contains a fraction of the original JGrass modules, which have been reviewed, enhanced and cleaned up. The library is divided in two major parts:
By selecting the above link, all the available modules get visible on the sidebar. The wiki pages are generated from the annotations in the code and are therefore kept strictly uptodate. While it doesn't make much sense to list all available modules, it might be useful to link to at least a couple of important ones, like:
usageas libraryThe JGrasstools library 0.7.0 is released in maven central. To use it in your project, have a look at this page. You can find instructions on how to use JGrasstools as library on this page. If you want to build the library yourself, here are the instructions to do so. commandline modeJGrasstools can be used through groovy scripting from commandline. This page explains how to do so. from within a GISThis release is not provided with a graphical user interface yet. Udig will soon support through the OmsBox the loading of not only JGrasstools libs but any kind of module-centric OMS3 annotated module. The proposal submitted (and accepted) to the uDig community can be reviewed here. downloadsThe 0.7.0 version of the JGrasstools can be downloaded here. support and mailinglistsVoluntary support is supplied on the main project's mailinglist. 0.7.0 developers tagThe 0.7.0 version has been tagged here. | |
► Sign in to add a comment