JGrass 1.0 starts in 2004 from the collaboration of the C.U.D.A.M. of the University of Trento and the I.C.E.N.S. of Kingston
the aim is to expand GRASS with a usability such to get it out of the academic environment to the average user
it gets born basically as a java GUI to GRASS released under GPL
the project encounters difficulties to expand and build up a community, in part because of the java-choice, which was criticised to be non-GPL
the major sponsor is the C.U.D.A.M. through projects
JGrass choses a precise direction: the protection and modeling of the territory
JGrass 1.0 – environmental modeling? So what? ...it gets filled up with tools developed at the University of Trento, department of hydrology and hydraulic, Faculty of Engineering hydro-geomorphologic models that work on raster basis
JGrass 1.0 – definition of environmental attributes rainfall data drainage direction network extraction total contributing area rescaled distances and hydrologic attributes slope, curvatures and geo-morphologic attributes
JGrass 1.0 – Peakflow: the hydrologic model in JGrass
first thing was adding native support for GRASS rasters in read/write mode and a udig service was created for the GRASS workspace
GRASSDB : folder that holds all the locations LOCATION : holds the information of the used projection, holds all the mapsets MAPSET : the user space inside which the active working region is defined PERMANENT : particular mapset used to hold location informations ACTIVE REGION : the region definition (boundaries and resolution) inside which most GRASS commands apply
GRASS saves a PROJ_INFO file in the PERMANENT mapset, but that file can't be built without GRASS functions. So for now there is the need to create a PROJ_INFO.WKT in the same folder. If that file is not present, the user is asked to chose a projection.
Reprojection on the fly is not possible. A GRASS workspace has a predefined projection and all the maps are consistent with that. So at the moment if you are working with a GRASS workspace, that one ist the first to be dragged into the project, in order to define the projection of the map.
uDig doesn't support dragging folders into the catalog, so if you want to drag the GRASS location into the catalog , you first need to create an empty file with .jgrass extention. Drag that and the magic is done.
GRASS doesn't support alpha as a persistent value. JGrass does it by putting the alpha as a comment into GRASS's colorfile.