[GRASS-SVN] r32772 - in grass/trunk: db/db.login display/d.barscale
display/d.colorlist display/d.colors display/d.colortable
display/d.erase display/d.extract display/d.font
display/d.fontlist display/d.geodesic display/d.graph
display/d.grid display/d.his display/d.histogram
display/d.info display/d.labels display/d.legend
display/d.linegraph display/d.measure display/d.nviz
display/d.path display/d.profile display/d.rast
display/d.rast.arrow display/d.rast.num display/d.rgb
display/d.rhumbline display/d.text.new
display/d.thematic.area display/d.title display/d.vect
display/d.vect.chart display/d.what.rast display/d.what.vect
display/d.where display/d.zoom doc/raster/r.example
doc/vector/v.example general/g.access general/g.dirseps
general/g.filename general/g.findetc general/g.findfile
general/g.gisenv general/g.gui general/g.mapset
general/g.mapsets general/g.message general/g.mkfontcap
general/g.parser general/g.pnmcomp general/g.proj
general/g.region general/g.setproj general/g.tempfile
general/g.transform general/g.version gui/tcltk/gis.m
imagery/i.atcorr imagery/i.cca imagery/i.class
imagery/i.cluster imagery/i.fft imagery/i.gensig
imagery/i.gensigset imagery/i.group imagery/i.his.rgb
imagery/i.ifft imagery/i.maxlik imagery/i.ortho.photo/menu
imagery/i.ortho.photo/photo.2image
imagery/i.ortho.photo/photo.2target
imagery/i.ortho.photo/photo.camera imagery/i.ortho.photo/photo.init
imagery/i.ortho.photo/photo.rectify imagery/i.pca
imagery/i.points imagery/i.rectify imagery/i.rgb.his
imagery/i.smap/shapiro imagery/i.target imagery/i.vpoints
imagery/i.zc lib/cairodriver lib/db/sqlp lib/htmldriver
lib/pngdriver lib/psdriver misc/m.cogo ps/ps.map
raster/r.average raster/r.basins.fill raster/r.bitpattern
raster/r.buffer raster/r.carve raster/r.cats raster/r.circle
raster/r.clump raster/r.coin raster/r.colors
raster/r.composite raster/r.compress raster/r.contour
raster/r.cost raster/r.covar raster/r.cross raster/r.describe
raster/r.digit raster/r.distance raster/r.drain
raster/r.fill.dir raster/r.flow raster/r.grow.distance
raster/r.grow2 raster/r.gwflow raster/r.his raster/r.in.arc
raster/r.in.ascii raster/r.in.bin raster/r.in.gdal
raster/r.in.gridatb raster/r.in.mat raster/r.in.poly
raster/r.in.xyz raster/r.info raster/r.kappa raster/r.lake
raster/r.le/r.le.patch raster/r.le/r.le.pixel
raster/r.le/r.le.setup raster/r.le/r.le.trace raster/r.li
raster/r.li/r.li.cwed raster/r.li/r.li.daemon
raster/r.li/r.li.dominance raster/r.li/r.li.edgedensity
raster/r.li/r.li.mpa raster/r.li/r.li.mps
raster/r.li/r.li.padcv raster/r.li/r.li.padrange
raster/r.li/r.li.padsd raster/r.li/r.li.patchdensity
raster/r.li/r.li.patchnum raster/r.li/r.li.richness
raster/r.li/r.li.setup raster/r.li/r.li.shannon
raster/r.li/r.li.shape raster/r.li/r.li.simpson raster/r.los
raster/r.median raster/r.mfilter raster/r.mfilter.fp
raster/r.mode raster/r.neighbors raster/r.null
raster/r.out.arc raster/r.out.ascii raster/r.out.bin
raster/r.out.gdal raster/r.out.gridatb raster/r.out.mat
raster/r.out.mpeg raster/r.out.png raster/r.out.pov
raster/r.out.ppm raster/r.out.ppm3 raster/r.out.tiff
raster/r.out.vrml raster/r.out.vtk raster/r.param.scale
raster/r.patch raster/r.profile raster/r.proj
raster/r.proj.seg raster/r.quant raster/r.quantile
raster/r.random raster/r.random.cells raster/r.random.surface
raster/r.reclass raster/r.recode raster/r.region
raster/r.report raster/r.resamp.interp raster/r.resamp.rst
raster/r.resamp.stats raster/r.resample raster/r.rescale
raster/r.rescale.eq raster/r.series raster/r.slope.aspect
raster/r.statistics raster/r.stats raster/r.sum raster/r.sun
raster/r.sunmask raster/r.support raster/r.support.stats
raster/r.surf.area raster/r.surf.contour
raster/r.surf.fractal raster/r.surf.gauss raster/r.surf.idw
raster/r.surf.idw2 raster/r.surf.random raster/r.terraflow
raster/r.texture raster/r.thin raster/r.timestamp
raster/r.to.rast3 raster/r.to.rast3elev raster/r.to.vect
raster/r.topidx raster/r.topmodel raster/r.transect
raster/r.volume raster/r.walk raster/r.water.outlet
raster/r.watershed/front raster/r.what raster/r.what.color
raster/simwe/r.sim.sediment raster/simwe/r.sim.water
raster/wildfire/r.ros raster/wildfire/r.spread
raster/wildfire/r.spreadpath raster3d/r3.cross.rast
raster3d/r3.gwflow raster3d/r3.in.ascii raster3d/r3.in.v5d
raster3d/r3.mkdspf raster3d/r3.out.ascii raster3d/r3.out.v5d
raster3d/r3.out.vtk raster3d/r3.showdspf raster3d/r3.stats
raster3d/r3.to.rast scripts/d.correlate
scripts/d.out.gpsdrive scripts/d.polar scripts/d.rast.edit
scripts/d.rast.leg scripts/d.shadedmap
scripts/d.vect.thematic scripts/db.dropcol
scripts/db.droptable scripts/db.in.ogr scripts/db.out.ogr
scripts/db.test scripts/g.manual scripts/g.mlist
scripts/g.mremove scripts/i.fusion.brovey
scripts/i.image.mosaic scripts/i.in.spotvgt
scripts/i.landsat.rgb scripts/i.oif scripts/i.spectral
scripts/i.tasscap scripts/m.proj scripts/r.blend
scripts/r.fillnulls scripts/r.in.aster scripts/r.in.srtm
scripts/r.in.wms scripts/r.mapcalculator scripts/r.mask
scripts/r.out.gdal scripts/r.out.xyz scripts/r.plane
scripts/r.reclass.area scripts/r.regression.line
scripts/r.shaded.relief scripts/r.tileset
scripts/r3.mapcalculator scripts/v.build.all
scripts/v.centroids scripts/v.convert.all scripts/v.db.addcol
scripts/v.db.addtable scripts/v.db.dropcol
scripts/v.db.droptable scripts/v.db.join
scripts/v.db.reconnect.all scripts/v.db.renamecol
scripts/v.db.univar scripts/v.db.update scripts/v.dissolve
scripts/v.in.e00 scripts/v.in.garmin scripts/v.in.geonames
scripts/v.in.gns scripts/v.in.gpsbabel scripts/v.in.mapgen
scripts/v.in.sites.all scripts/v.in.wfs scripts/v.rast.stats
scripts/v.report scripts/v.what.vect sites/s.in.ascii
sites/s.out.ascii vector/lidar/v.lidar.correction
vector/lidar/v.lidar.edgedetection
vector/lidar/v.lidar.growing vector/lidar/v.outlier
vector/lidar/v.surf.bspline vector/v.buffer vector/v.build
vector/v.build.polylines vector/v.category vector/v.class
vector/v.clean vector/v.convert vector/v.db.connect
vector/v.db.select vector/v.digit vector/v.distance
vector/v.drape vector/v.edit vector/v.external
vector/v.extract vector/v.extrude vector/v.generalize
vector/v.hull vector/v.in.ascii vector/v.in.db
vector/v.in.dwg vector/v.in.dxf vector/v.in.ogr
vector/v.in.region vector/v.in.sites vector/v.info
vector/v.kcv vector/v.kernel vector/v.label vector/v.label.sa
vector/v.lrs/v.lrs.create vector/v.lrs/v.lrs.label
vector/v.lrs/v.lrs.segment vector/v.lrs/v.lrs.where
vector/v.mkgrid vector/v.neighbors vector/v.net
vector/v.net.alloc vector/v.net.iso vector/v.net.path
vector/v.net.salesman vector/v.net.steiner
vector/v.net.visibility vector/v.normal vector/v.out.ascii
vector/v.out.dxf vector/v.out.ogr vector/v.out.pov
vector/v.out.svg vector/v.out.vtk vector/v.overlay
vector/v.parallel vector/v.patch vector/v.perturb
vector/v.proj vector/v.qcount vector/v.random
vector/v.reclass vector/v.sample vector/v.segment
vector/v.select vector/v.split vector/v.support
vector/v.surf.idw vector/v.surf.rst vector/v.to.db
vector/v.to.points vector/v.to.rast vector/v.to.rast3
vector/v.transform vector/v.type vector/v.univar
vector/v.vol.rst vector/v.what vector/v.what.rast
visualization/nviz visualization/nviz/src
visualization/nviz2/cmd visualization/xganim
svn_grass at osgeo.org
svn_grass at osgeo.org
Fri Aug 15 02:17:21 EDT 2008
Author: glynn
Date: 2008-08-15 02:16:42 -0400 (Fri, 15 Aug 2008)
New Revision: 32772
Added:
grass/trunk/db/db.login/db.login.html
grass/trunk/display/d.barscale/d.barscale.html
grass/trunk/display/d.colorlist/d.colorlist.html
grass/trunk/display/d.colors/d.colors.html
grass/trunk/display/d.colortable/d.colortable.html
grass/trunk/display/d.erase/d.erase.html
grass/trunk/display/d.extract/d.extract.html
grass/trunk/display/d.font/d.font.html
grass/trunk/display/d.fontlist/d.fontlist.html
grass/trunk/display/d.geodesic/d.geodesic.html
grass/trunk/display/d.graph/d.graph.html
grass/trunk/display/d.grid/d.grid.html
grass/trunk/display/d.his/d.his.html
grass/trunk/display/d.histogram/d.histogram.html
grass/trunk/display/d.info/d.info.html
grass/trunk/display/d.labels/d.labels.html
grass/trunk/display/d.legend/d.legend.html
grass/trunk/display/d.linegraph/d.linegraph.html
grass/trunk/display/d.measure/d.measure.html
grass/trunk/display/d.nviz/d.nviz.html
grass/trunk/display/d.path/d.path.html
grass/trunk/display/d.profile/d.profile.html
grass/trunk/display/d.rast.arrow/d.rast.arrow.html
grass/trunk/display/d.rast.num/d.rast.num.html
grass/trunk/display/d.rast/d.rast.html
grass/trunk/display/d.rgb/d.rgb.html
grass/trunk/display/d.rhumbline/d.rhumbline.html
grass/trunk/display/d.text.new/d.text.html
grass/trunk/display/d.thematic.area/d.thematic.area.html
grass/trunk/display/d.title/d.title.html
grass/trunk/display/d.vect.chart/d.vect.chart.html
grass/trunk/display/d.vect/d.vect.html
grass/trunk/display/d.what.rast/d.what.rast.html
grass/trunk/display/d.what.vect/d.what.vect.html
grass/trunk/display/d.where/d.where.html
grass/trunk/display/d.zoom/d.zoom.html
grass/trunk/doc/raster/r.example/r.example.html
grass/trunk/doc/vector/v.example/v.example.html
grass/trunk/general/g.access/g.access.html
grass/trunk/general/g.dirseps/g.dirseps.html
grass/trunk/general/g.filename/g.filename.html
grass/trunk/general/g.findetc/g.findetc.html
grass/trunk/general/g.findfile/g.findfile.html
grass/trunk/general/g.gisenv/g.gisenv.html
grass/trunk/general/g.gui/g.gui.html
grass/trunk/general/g.mapset/g.mapset.html
grass/trunk/general/g.mapsets/g.mapsets.html
grass/trunk/general/g.message/g.message.html
grass/trunk/general/g.mkfontcap/g.mkfontcap.html
grass/trunk/general/g.parser/g.parser.html
grass/trunk/general/g.pnmcomp/g.pnmcomp.html
grass/trunk/general/g.proj/g.proj.html
grass/trunk/general/g.region/g.region.html
grass/trunk/general/g.setproj/g.setproj.html
grass/trunk/general/g.tempfile/g.tempfile.html
grass/trunk/general/g.transform/g.transform.html
grass/trunk/general/g.version/g.version.html
grass/trunk/gui/tcltk/gis.m/gis.m.html
grass/trunk/imagery/i.atcorr/i.atcorr.html
grass/trunk/imagery/i.cca/i.cca.html
grass/trunk/imagery/i.class/i.class.html
grass/trunk/imagery/i.cluster/i.cluster.html
grass/trunk/imagery/i.fft/i.fft.html
grass/trunk/imagery/i.gensig/i.gensig.html
grass/trunk/imagery/i.gensigset/i.gensigset.html
grass/trunk/imagery/i.group/i.group.html
grass/trunk/imagery/i.his.rgb/i.his.rgb.html
grass/trunk/imagery/i.ifft/i.ifft.html
grass/trunk/imagery/i.maxlik/i.maxlik.html
grass/trunk/imagery/i.ortho.photo/menu/i.ortho.photo.html
grass/trunk/imagery/i.ortho.photo/photo.2image/photo.2image.html
grass/trunk/imagery/i.ortho.photo/photo.2target/photo.2target.html
grass/trunk/imagery/i.ortho.photo/photo.camera/photo.camera.html
grass/trunk/imagery/i.ortho.photo/photo.init/photo.init.html
grass/trunk/imagery/i.ortho.photo/photo.rectify/photo.rectify.html
grass/trunk/imagery/i.pca/i.pca.html
grass/trunk/imagery/i.points/i.points.html
grass/trunk/imagery/i.rectify/i.rectify.html
grass/trunk/imagery/i.rgb.his/i.rgb.his.html
grass/trunk/imagery/i.smap/shapiro/i.smap.html
grass/trunk/imagery/i.target/i.target.html
grass/trunk/imagery/i.vpoints/i.vpoints.html
grass/trunk/imagery/i.zc/i.zc.html
grass/trunk/lib/cairodriver/cairodriver.html
grass/trunk/lib/db/sqlp/sql.html
grass/trunk/lib/htmldriver/htmldriver.html
grass/trunk/lib/pngdriver/pngdriver.html
grass/trunk/lib/psdriver/psdriver.html
grass/trunk/misc/m.cogo/m.cogo.html
grass/trunk/ps/ps.map/ps.map.html
grass/trunk/raster/r.average/r.average.html
grass/trunk/raster/r.basins.fill/r.basins.fill.html
grass/trunk/raster/r.bitpattern/r.bitpattern.html
grass/trunk/raster/r.buffer/r.buffer.html
grass/trunk/raster/r.carve/r.carve.html
grass/trunk/raster/r.cats/r.category.html
grass/trunk/raster/r.circle/r.circle.html
grass/trunk/raster/r.clump/r.clump.html
grass/trunk/raster/r.coin/r.coin.html
grass/trunk/raster/r.colors/r.colors.html
grass/trunk/raster/r.composite/r.composite.html
grass/trunk/raster/r.compress/r.compress.html
grass/trunk/raster/r.contour/r.contour.html
grass/trunk/raster/r.cost/r.cost.html
grass/trunk/raster/r.covar/r.covar.html
grass/trunk/raster/r.cross/r.cross.html
grass/trunk/raster/r.describe/r.describe.html
grass/trunk/raster/r.digit/r.digit.html
grass/trunk/raster/r.distance/r.distance.html
grass/trunk/raster/r.drain/r.drain.html
grass/trunk/raster/r.fill.dir/r.fill.dir.html
grass/trunk/raster/r.flow/r.flow.html
grass/trunk/raster/r.grow.distance/r.grow.distance.html
grass/trunk/raster/r.grow2/r.grow.html
grass/trunk/raster/r.gwflow/r.gwflow.html
grass/trunk/raster/r.his/r.his.html
grass/trunk/raster/r.in.arc/r.in.arc.html
grass/trunk/raster/r.in.ascii/r.in.ascii.html
grass/trunk/raster/r.in.bin/r.in.bin.html
grass/trunk/raster/r.in.gdal/r.in.gdal.html
grass/trunk/raster/r.in.gridatb/r.in.gridatb.html
grass/trunk/raster/r.in.mat/r.in.mat.html
grass/trunk/raster/r.in.poly/r.in.poly.html
grass/trunk/raster/r.in.xyz/r.in.xyz.html
grass/trunk/raster/r.info/r.info.html
grass/trunk/raster/r.kappa/r.kappa.html
grass/trunk/raster/r.lake/r.lake.html
grass/trunk/raster/r.le/r.le.patch/r.le.patch.html
grass/trunk/raster/r.le/r.le.pixel/r.le.pixel.html
grass/trunk/raster/r.le/r.le.setup/r.le.setup.html
grass/trunk/raster/r.le/r.le.trace/r.le.trace.html
grass/trunk/raster/r.li/r.li.cwed/r.li.cwed.html
grass/trunk/raster/r.li/r.li.daemon/r.li.daemon.html
grass/trunk/raster/r.li/r.li.dominance/r.li.dominance.html
grass/trunk/raster/r.li/r.li.edgedensity/r.li.edgedensity.html
grass/trunk/raster/r.li/r.li.html
grass/trunk/raster/r.li/r.li.mpa/r.li.mpa.html
grass/trunk/raster/r.li/r.li.mps/r.li.mps.html
grass/trunk/raster/r.li/r.li.padcv/r.li.padcv.html
grass/trunk/raster/r.li/r.li.padrange/r.li.padrange.html
grass/trunk/raster/r.li/r.li.padsd/r.li.padsd.html
grass/trunk/raster/r.li/r.li.patchdensity/r.li.patchdensity.html
grass/trunk/raster/r.li/r.li.patchnum/r.li.patchnum.html
grass/trunk/raster/r.li/r.li.richness/r.li.richness.html
grass/trunk/raster/r.li/r.li.setup/r.li.setup.html
grass/trunk/raster/r.li/r.li.shannon/r.li.shannon.html
grass/trunk/raster/r.li/r.li.shape/r.li.shape.html
grass/trunk/raster/r.li/r.li.simpson/r.li.simpson.html
grass/trunk/raster/r.los/r.los.html
grass/trunk/raster/r.median/r.median.html
grass/trunk/raster/r.mfilter.fp/r.mfilter.fp.html
grass/trunk/raster/r.mfilter/r.mfilter.html
grass/trunk/raster/r.mode/r.mode.html
grass/trunk/raster/r.neighbors/r.neighbors.html
grass/trunk/raster/r.null/r.null.html
grass/trunk/raster/r.out.arc/r.out.arc.html
grass/trunk/raster/r.out.ascii/r.out.ascii.html
grass/trunk/raster/r.out.bin/r.out.bin.html
grass/trunk/raster/r.out.gdal/r.out.gdal.html
grass/trunk/raster/r.out.gridatb/r.out.gridatb.html
grass/trunk/raster/r.out.mat/r.out.mat.html
grass/trunk/raster/r.out.mpeg/r.out.mpeg.html
grass/trunk/raster/r.out.png/r.out.png.html
grass/trunk/raster/r.out.pov/r.out.pov.html
grass/trunk/raster/r.out.ppm/r.out.ppm.html
grass/trunk/raster/r.out.ppm3/r.out.ppm3.html
grass/trunk/raster/r.out.tiff/r.out.tiff.html
grass/trunk/raster/r.out.vrml/r.out.vrml.html
grass/trunk/raster/r.out.vtk/r.out.vtk.html
grass/trunk/raster/r.param.scale/r.param.scale.html
grass/trunk/raster/r.patch/r.patch.html
grass/trunk/raster/r.profile/r.profile.html
grass/trunk/raster/r.proj.seg/r.proj.html
grass/trunk/raster/r.proj/r.proj.html
grass/trunk/raster/r.quant/r.quant.html
grass/trunk/raster/r.quantile/r.quantile.html
grass/trunk/raster/r.random.cells/r.random.cells.html
grass/trunk/raster/r.random.surface/r.random.surface.html
grass/trunk/raster/r.random/r.random.html
grass/trunk/raster/r.reclass/r.reclass.html
grass/trunk/raster/r.recode/r.recode.html
grass/trunk/raster/r.region/r.region.html
grass/trunk/raster/r.report/r.report.html
grass/trunk/raster/r.resamp.interp/r.resamp.interp.html
grass/trunk/raster/r.resamp.rst/r.resamp.rst.html
grass/trunk/raster/r.resamp.stats/r.resamp.stats.html
grass/trunk/raster/r.resample/r.resample.html
grass/trunk/raster/r.rescale.eq/r.rescale.eq.html
grass/trunk/raster/r.rescale/r.rescale.html
grass/trunk/raster/r.series/r.series.html
grass/trunk/raster/r.slope.aspect/r.slope.aspect.html
grass/trunk/raster/r.statistics/r.statistics.html
grass/trunk/raster/r.stats/r.stats.html
grass/trunk/raster/r.sum/r.sum.html
grass/trunk/raster/r.sun/r.sun.html
grass/trunk/raster/r.sunmask/r.sunmask.html
grass/trunk/raster/r.support.stats/r.support.stats.html
grass/trunk/raster/r.support/r.support.html
grass/trunk/raster/r.surf.area/r.surf.area.html
grass/trunk/raster/r.surf.contour/r.surf.contour.html
grass/trunk/raster/r.surf.fractal/r.surf.fractal.html
grass/trunk/raster/r.surf.gauss/r.surf.gauss.html
grass/trunk/raster/r.surf.idw/r.surf.idw.html
grass/trunk/raster/r.surf.idw2/r.surf.idw2.html
grass/trunk/raster/r.surf.random/r.surf.random.html
grass/trunk/raster/r.terraflow/r.terraflow.html
grass/trunk/raster/r.texture/r.texture.html
grass/trunk/raster/r.thin/r.thin.html
grass/trunk/raster/r.timestamp/r.timestamp.html
grass/trunk/raster/r.to.rast3/r.to.rast3.html
grass/trunk/raster/r.to.rast3elev/r.to.rast3elev.html
grass/trunk/raster/r.to.vect/r.to.vect.html
grass/trunk/raster/r.topidx/r.topidx.html
grass/trunk/raster/r.topmodel/r.topmodel.html
grass/trunk/raster/r.transect/r.transect.html
grass/trunk/raster/r.volume/r.volume.html
grass/trunk/raster/r.walk/r.walk.html
grass/trunk/raster/r.water.outlet/r.water.outlet.html
grass/trunk/raster/r.watershed/front/r.watershed.html
grass/trunk/raster/r.what.color/r.what.color.html
grass/trunk/raster/r.what/r.what.html
grass/trunk/raster/simwe/r.sim.sediment/r.sim.sediment.html
grass/trunk/raster/simwe/r.sim.water/r.sim.water.html
grass/trunk/raster/wildfire/r.ros/r.ros.html
grass/trunk/raster/wildfire/r.spread/r.spread.html
grass/trunk/raster/wildfire/r.spreadpath/r.spreadpath.html
grass/trunk/raster3d/r3.cross.rast/r3.cross.rast.html
grass/trunk/raster3d/r3.gwflow/r3.gwflow.html
grass/trunk/raster3d/r3.in.ascii/r3.in.ascii.html
grass/trunk/raster3d/r3.in.v5d/r3.in.v5d.html
grass/trunk/raster3d/r3.mkdspf/r3.mkdspf.html
grass/trunk/raster3d/r3.out.ascii/r3.out.ascii.html
grass/trunk/raster3d/r3.out.v5d/r3.out.v5d.html
grass/trunk/raster3d/r3.out.vtk/r3.out.vtk.html
grass/trunk/raster3d/r3.showdspf/r3.showdspf.html
grass/trunk/raster3d/r3.stats/r3.stats.html
grass/trunk/raster3d/r3.to.rast/r3.to.rast.html
grass/trunk/scripts/d.correlate/d.correlate.html
grass/trunk/scripts/d.out.gpsdrive/d.out.gpsdrive.html
grass/trunk/scripts/d.polar/d.polar.html
grass/trunk/scripts/d.rast.edit/d.rast.edit.html
grass/trunk/scripts/d.rast.leg/d.rast.leg.html
grass/trunk/scripts/d.shadedmap/d.shadedmap.html
grass/trunk/scripts/d.vect.thematic/d.vect.thematic.html
grass/trunk/scripts/db.dropcol/db.dropcol.html
grass/trunk/scripts/db.droptable/db.droptable.html
grass/trunk/scripts/db.in.ogr/db.in.ogr.html
grass/trunk/scripts/db.out.ogr/db.out.ogr.html
grass/trunk/scripts/db.test/db.test.html
grass/trunk/scripts/g.manual/g.manual.html
grass/trunk/scripts/g.mlist/g.mlist.html
grass/trunk/scripts/g.mremove/g.mremove.html
grass/trunk/scripts/i.fusion.brovey/i.fusion.brovey.html
grass/trunk/scripts/i.image.mosaic/i.image.mosaic.html
grass/trunk/scripts/i.in.spotvgt/i.in.spotvgt.html
grass/trunk/scripts/i.landsat.rgb/i.landsat.rgb.html
grass/trunk/scripts/i.oif/i.oif.html
grass/trunk/scripts/i.spectral/i.spectral.html
grass/trunk/scripts/i.tasscap/i.tasscap.html
grass/trunk/scripts/m.proj/m.proj.html
grass/trunk/scripts/r.blend/r.blend.html
grass/trunk/scripts/r.fillnulls/r.fillnulls.html
grass/trunk/scripts/r.in.aster/r.in.aster.html
grass/trunk/scripts/r.in.srtm/r.in.srtm.html
grass/trunk/scripts/r.in.wms/r.in.wms.html
grass/trunk/scripts/r.mapcalculator/r.mapcalculator.html
grass/trunk/scripts/r.mask/r.mask.html
grass/trunk/scripts/r.out.gdal/r.out.gdal.sh.html
grass/trunk/scripts/r.out.xyz/r.out.xyz.html
grass/trunk/scripts/r.plane/r.plane.html
grass/trunk/scripts/r.reclass.area/r.reclass.area.html
grass/trunk/scripts/r.regression.line/r.regression.line.html
grass/trunk/scripts/r.shaded.relief/r.shaded.relief.html
grass/trunk/scripts/r.tileset/r.tileset.html
grass/trunk/scripts/r3.mapcalculator/r3.mapcalculator.html
grass/trunk/scripts/v.build.all/v.build.all.html
grass/trunk/scripts/v.centroids/v.centroids.html
grass/trunk/scripts/v.convert.all/v.convert.all.html
grass/trunk/scripts/v.db.addcol/v.db.addcol.html
grass/trunk/scripts/v.db.addtable/v.db.addtable.html
grass/trunk/scripts/v.db.dropcol/v.db.dropcol.html
grass/trunk/scripts/v.db.droptable/v.db.droptable.html
grass/trunk/scripts/v.db.join/v.db.join.html
grass/trunk/scripts/v.db.reconnect.all/v.db.reconnect.all.html
grass/trunk/scripts/v.db.renamecol/v.db.renamecol.html
grass/trunk/scripts/v.db.univar/v.db.univar.html
grass/trunk/scripts/v.db.update/v.db.update.html
grass/trunk/scripts/v.dissolve/v.dissolve.html
grass/trunk/scripts/v.in.e00/v.in.e00.html
grass/trunk/scripts/v.in.garmin/v.in.garmin.html
grass/trunk/scripts/v.in.geonames/v.in.geonames.html
grass/trunk/scripts/v.in.gns/v.in.gns.html
grass/trunk/scripts/v.in.gpsbabel/v.in.gpsbabel.html
grass/trunk/scripts/v.in.mapgen/v.in.mapgen.html
grass/trunk/scripts/v.in.sites.all/v.in.sites.all.html
grass/trunk/scripts/v.in.wfs/v.in.wfs.html
grass/trunk/scripts/v.rast.stats/v.rast.stats.html
grass/trunk/scripts/v.report/v.report.html
grass/trunk/scripts/v.what.vect/v.what.vect.html
grass/trunk/sites/s.in.ascii/s.in.ascii.html
grass/trunk/sites/s.out.ascii/s.out.ascii.html
grass/trunk/vector/lidar/v.lidar.correction/v.lidar.correction.html
grass/trunk/vector/lidar/v.lidar.edgedetection/v.lidar.edgedetection.html
grass/trunk/vector/lidar/v.lidar.growing/v.lidar.growing.html
grass/trunk/vector/lidar/v.outlier/v.outlier.html
grass/trunk/vector/lidar/v.surf.bspline/v.surf.bspline.html
grass/trunk/vector/v.buffer/v.buffer.html
grass/trunk/vector/v.build.polylines/v.build.polylines.html
grass/trunk/vector/v.build/v.build.html
grass/trunk/vector/v.category/v.category.html
grass/trunk/vector/v.class/v.class.html
grass/trunk/vector/v.clean/v.clean.html
grass/trunk/vector/v.convert/v.convert.html
grass/trunk/vector/v.db.connect/v.db.connect.html
grass/trunk/vector/v.db.select/v.db.select.html
grass/trunk/vector/v.digit/v.digit.html
grass/trunk/vector/v.distance/v.distance.html
grass/trunk/vector/v.drape/v.drape.html
grass/trunk/vector/v.edit/v.edit.html
grass/trunk/vector/v.external/v.external.html
grass/trunk/vector/v.extract/v.extract.html
grass/trunk/vector/v.extrude/v.extrude.html
grass/trunk/vector/v.generalize/v.generalize.html
grass/trunk/vector/v.hull/v.hull.html
grass/trunk/vector/v.in.ascii/v.in.ascii.html
grass/trunk/vector/v.in.db/v.in.db.html
grass/trunk/vector/v.in.dwg/v.in.dwg.html
grass/trunk/vector/v.in.dxf/v.in.dxf.html
grass/trunk/vector/v.in.ogr/v.in.ogr.html
grass/trunk/vector/v.in.region/v.in.region.html
grass/trunk/vector/v.in.sites/v.in.sites.html
grass/trunk/vector/v.info/v.info.html
grass/trunk/vector/v.kcv/v.kcv.html
grass/trunk/vector/v.kernel/v.kernel.html
grass/trunk/vector/v.label.sa/v.label.sa.html
grass/trunk/vector/v.label/v.label.html
grass/trunk/vector/v.lrs/v.lrs.create/v.lrs.create.html
grass/trunk/vector/v.lrs/v.lrs.label/v.lrs.label.html
grass/trunk/vector/v.lrs/v.lrs.segment/v.lrs.segment.html
grass/trunk/vector/v.lrs/v.lrs.where/v.lrs.where.html
grass/trunk/vector/v.mkgrid/v.mkgrid.html
grass/trunk/vector/v.neighbors/v.neighbors.html
grass/trunk/vector/v.net.alloc/v.net.alloc.html
grass/trunk/vector/v.net.iso/v.net.iso.html
grass/trunk/vector/v.net.path/v.net.path.html
grass/trunk/vector/v.net.salesman/v.net.salesman.html
grass/trunk/vector/v.net.steiner/v.net.steiner.html
grass/trunk/vector/v.net.visibility/v.net.visibility.html
grass/trunk/vector/v.net/v.net.html
grass/trunk/vector/v.normal/v.normal.html
grass/trunk/vector/v.out.ascii/v.out.ascii.html
grass/trunk/vector/v.out.dxf/v.out.dxf.html
grass/trunk/vector/v.out.ogr/v.out.ogr.html
grass/trunk/vector/v.out.pov/v.out.pov.html
grass/trunk/vector/v.out.svg/v.out.svg.html
grass/trunk/vector/v.out.vtk/v.out.vtk.html
grass/trunk/vector/v.overlay/v.overlay.html
grass/trunk/vector/v.parallel/v.parallel.html
grass/trunk/vector/v.patch/v.patch.html
grass/trunk/vector/v.perturb/v.perturb.html
grass/trunk/vector/v.proj/v.proj.html
grass/trunk/vector/v.qcount/v.qcount.html
grass/trunk/vector/v.random/v.random.html
grass/trunk/vector/v.reclass/v.reclass.html
grass/trunk/vector/v.sample/v.sample.html
grass/trunk/vector/v.segment/v.segment.html
grass/trunk/vector/v.select/v.select.html
grass/trunk/vector/v.split/v.split.html
grass/trunk/vector/v.support/v.support.html
grass/trunk/vector/v.surf.idw/v.surf.idw.html
grass/trunk/vector/v.surf.rst/v.surf.rst.html
grass/trunk/vector/v.to.db/v.to.db.html
grass/trunk/vector/v.to.points/v.to.points.html
grass/trunk/vector/v.to.rast/v.to.rast.html
grass/trunk/vector/v.to.rast3/v.to.rast3.html
grass/trunk/vector/v.transform/v.transform.html
grass/trunk/vector/v.type/v.type.html
grass/trunk/vector/v.univar/v.univar.html
grass/trunk/vector/v.vol.rst/v.vol.rst.html
grass/trunk/vector/v.what.rast/v.what.rast.html
grass/trunk/vector/v.what/v.what.html
grass/trunk/visualization/nviz/nviz.html
grass/trunk/visualization/nviz2/cmd/nviz_cmd.html
grass/trunk/visualization/xganim/xganim.html
Removed:
grass/trunk/db/db.login/description.html
grass/trunk/display/d.barscale/description.html
grass/trunk/display/d.colorlist/description.html
grass/trunk/display/d.colors/description.html
grass/trunk/display/d.colortable/description.html
grass/trunk/display/d.erase/description.html
grass/trunk/display/d.extract/description.html
grass/trunk/display/d.font/description.html
grass/trunk/display/d.fontlist/description.html
grass/trunk/display/d.geodesic/description.html
grass/trunk/display/d.graph/description.html
grass/trunk/display/d.grid/description.html
grass/trunk/display/d.his/description.html
grass/trunk/display/d.histogram/description.html
grass/trunk/display/d.info/description.html
grass/trunk/display/d.labels/description.html
grass/trunk/display/d.legend/description.html
grass/trunk/display/d.linegraph/description.html
grass/trunk/display/d.measure/description.html
grass/trunk/display/d.nviz/description.html
grass/trunk/display/d.path/description.html
grass/trunk/display/d.profile/description.html
grass/trunk/display/d.rast.arrow/description.html
grass/trunk/display/d.rast.num/description.html
grass/trunk/display/d.rast/description.html
grass/trunk/display/d.rgb/description.html
grass/trunk/display/d.rhumbline/description.html
grass/trunk/display/d.text.new/description.html
grass/trunk/display/d.thematic.area/description.html
grass/trunk/display/d.title/description.html
grass/trunk/display/d.vect.chart/description.html
grass/trunk/display/d.vect/description.html
grass/trunk/display/d.what.rast/description.html
grass/trunk/display/d.what.vect/description.html
grass/trunk/display/d.where/description.html
grass/trunk/display/d.zoom/description.html
grass/trunk/doc/raster/r.example/description.html
grass/trunk/doc/vector/v.example/description.html
grass/trunk/general/g.access/description.html
grass/trunk/general/g.dirseps/description.html
grass/trunk/general/g.filename/description.html
grass/trunk/general/g.findetc/description.html
grass/trunk/general/g.findfile/description.html
grass/trunk/general/g.gisenv/description.html
grass/trunk/general/g.gui/description.html
grass/trunk/general/g.mapset/description.html
grass/trunk/general/g.mapsets/description.html
grass/trunk/general/g.message/description.html
grass/trunk/general/g.mkfontcap/description.html
grass/trunk/general/g.parser/description.html
grass/trunk/general/g.pnmcomp/description.html
grass/trunk/general/g.proj/description.html
grass/trunk/general/g.region/description.html
grass/trunk/general/g.setproj/description.html
grass/trunk/general/g.tempfile/description.html
grass/trunk/general/g.transform/description.html
grass/trunk/general/g.version/description.html
grass/trunk/gui/tcltk/gis.m/description.html
grass/trunk/imagery/i.atcorr/description.html
grass/trunk/imagery/i.cca/description.html
grass/trunk/imagery/i.class/description.html
grass/trunk/imagery/i.cluster/description.html
grass/trunk/imagery/i.fft/description.html
grass/trunk/imagery/i.gensig/description.html
grass/trunk/imagery/i.gensigset/description.html
grass/trunk/imagery/i.group/description.html
grass/trunk/imagery/i.his.rgb/description.html
grass/trunk/imagery/i.ifft/description.html
grass/trunk/imagery/i.maxlik/description.html
grass/trunk/imagery/i.ortho.photo/menu/description.html
grass/trunk/imagery/i.ortho.photo/photo.2image/description.html
grass/trunk/imagery/i.ortho.photo/photo.2target/description.html
grass/trunk/imagery/i.ortho.photo/photo.camera/description.html
grass/trunk/imagery/i.ortho.photo/photo.init/description.html
grass/trunk/imagery/i.ortho.photo/photo.rectify/description.html
grass/trunk/imagery/i.pca/description.html
grass/trunk/imagery/i.points/description.html
grass/trunk/imagery/i.rectify/description.html
grass/trunk/imagery/i.rgb.his/description.html
grass/trunk/imagery/i.smap/shapiro/description.html
grass/trunk/imagery/i.target/description.html
grass/trunk/imagery/i.vpoints/description.html
grass/trunk/imagery/i.zc/description.html
grass/trunk/lib/cairodriver/description.html
grass/trunk/lib/db/sqlp/description.html
grass/trunk/lib/htmldriver/description.html
grass/trunk/lib/pngdriver/description.html
grass/trunk/lib/psdriver/description.html
grass/trunk/misc/m.cogo/description.html
grass/trunk/ps/ps.map/description.html
grass/trunk/raster/r.average/description.html
grass/trunk/raster/r.basins.fill/description.html
grass/trunk/raster/r.bitpattern/description.html
grass/trunk/raster/r.buffer/description.html
grass/trunk/raster/r.carve/description.html
grass/trunk/raster/r.cats/description.html
grass/trunk/raster/r.circle/description.html
grass/trunk/raster/r.clump/description.html
grass/trunk/raster/r.coin/description.html
grass/trunk/raster/r.colors/description.html
grass/trunk/raster/r.composite/description.html
grass/trunk/raster/r.compress/description.html
grass/trunk/raster/r.contour/description.html
grass/trunk/raster/r.cost/description.html
grass/trunk/raster/r.covar/description.html
grass/trunk/raster/r.cross/description.html
grass/trunk/raster/r.describe/description.html
grass/trunk/raster/r.digit/description.html
grass/trunk/raster/r.distance/description.html
grass/trunk/raster/r.drain/description.html
grass/trunk/raster/r.fill.dir/description.html
grass/trunk/raster/r.flow/description.html
grass/trunk/raster/r.grow.distance/description.html
grass/trunk/raster/r.grow2/description.html
grass/trunk/raster/r.gwflow/description.html
grass/trunk/raster/r.his/description.html
grass/trunk/raster/r.in.arc/description.html
grass/trunk/raster/r.in.ascii/description.html
grass/trunk/raster/r.in.bin/description.html
grass/trunk/raster/r.in.gdal/description.html
grass/trunk/raster/r.in.gridatb/description.html
grass/trunk/raster/r.in.mat/description.html
grass/trunk/raster/r.in.poly/description.html
grass/trunk/raster/r.in.xyz/description.html
grass/trunk/raster/r.info/description.html
grass/trunk/raster/r.kappa/description.html
grass/trunk/raster/r.lake/description.html
grass/trunk/raster/r.le/r.le.patch/description.html
grass/trunk/raster/r.le/r.le.pixel/description.html
grass/trunk/raster/r.le/r.le.setup/description.html
grass/trunk/raster/r.le/r.le.trace/description.html
grass/trunk/raster/r.li/description.html
grass/trunk/raster/r.li/r.li.cwed/description.html
grass/trunk/raster/r.li/r.li.daemon/description.html
grass/trunk/raster/r.li/r.li.dominance/description.html
grass/trunk/raster/r.li/r.li.edgedensity/description.html
grass/trunk/raster/r.li/r.li.mpa/description.html
grass/trunk/raster/r.li/r.li.mps/description.html
grass/trunk/raster/r.li/r.li.padcv/description.html
grass/trunk/raster/r.li/r.li.padrange/description.html
grass/trunk/raster/r.li/r.li.padsd/description.html
grass/trunk/raster/r.li/r.li.patchdensity/description.html
grass/trunk/raster/r.li/r.li.patchnum/description.html
grass/trunk/raster/r.li/r.li.richness/description.html
grass/trunk/raster/r.li/r.li.setup/description.html
grass/trunk/raster/r.li/r.li.shannon/description.html
grass/trunk/raster/r.li/r.li.shape/description.html
grass/trunk/raster/r.li/r.li.simpson/description.html
grass/trunk/raster/r.los/description.html
grass/trunk/raster/r.median/description.html
grass/trunk/raster/r.mfilter.fp/description.html
grass/trunk/raster/r.mfilter/description.html
grass/trunk/raster/r.mode/description.html
grass/trunk/raster/r.neighbors/description.html
grass/trunk/raster/r.null/description.html
grass/trunk/raster/r.out.arc/description.html
grass/trunk/raster/r.out.ascii/description.html
grass/trunk/raster/r.out.bin/description.html
grass/trunk/raster/r.out.gdal/description.html
grass/trunk/raster/r.out.gridatb/description.html
grass/trunk/raster/r.out.mat/description.html
grass/trunk/raster/r.out.mpeg/description.html
grass/trunk/raster/r.out.png/description.html
grass/trunk/raster/r.out.pov/description.html
grass/trunk/raster/r.out.ppm/description.html
grass/trunk/raster/r.out.ppm3/description.html
grass/trunk/raster/r.out.tiff/description.html
grass/trunk/raster/r.out.vrml/description.html
grass/trunk/raster/r.out.vtk/description.html
grass/trunk/raster/r.param.scale/description.html
grass/trunk/raster/r.patch/description.html
grass/trunk/raster/r.profile/description.html
grass/trunk/raster/r.proj.seg/description.html
grass/trunk/raster/r.proj/description.html
grass/trunk/raster/r.quant/description.html
grass/trunk/raster/r.quantile/description.html
grass/trunk/raster/r.random.cells/description.html
grass/trunk/raster/r.random.surface/description.html
grass/trunk/raster/r.random/description.html
grass/trunk/raster/r.reclass/description.html
grass/trunk/raster/r.recode/description.html
grass/trunk/raster/r.region/description.html
grass/trunk/raster/r.report/description.html
grass/trunk/raster/r.resamp.interp/description.html
grass/trunk/raster/r.resamp.rst/description.html
grass/trunk/raster/r.resamp.stats/description.html
grass/trunk/raster/r.resample/description.html
grass/trunk/raster/r.rescale.eq/description.html
grass/trunk/raster/r.rescale/description.html
grass/trunk/raster/r.series/description.html
grass/trunk/raster/r.slope.aspect/description.html
grass/trunk/raster/r.statistics/description.html
grass/trunk/raster/r.stats/description.html
grass/trunk/raster/r.sum/description.html
grass/trunk/raster/r.sun/description.html
grass/trunk/raster/r.sunmask/description.html
grass/trunk/raster/r.support.stats/description.html
grass/trunk/raster/r.support/description.html
grass/trunk/raster/r.surf.area/description.html
grass/trunk/raster/r.surf.contour/description.html
grass/trunk/raster/r.surf.fractal/description.html
grass/trunk/raster/r.surf.gauss/description.html
grass/trunk/raster/r.surf.idw/description.html
grass/trunk/raster/r.surf.idw2/description.html
grass/trunk/raster/r.surf.random/description.html
grass/trunk/raster/r.terraflow/description.html
grass/trunk/raster/r.texture/description.html
grass/trunk/raster/r.thin/description.html
grass/trunk/raster/r.timestamp/description.html
grass/trunk/raster/r.to.rast3/description.html
grass/trunk/raster/r.to.rast3elev/description.html
grass/trunk/raster/r.to.vect/description.html
grass/trunk/raster/r.topidx/description.html
grass/trunk/raster/r.topmodel/description.html
grass/trunk/raster/r.transect/description.html
grass/trunk/raster/r.volume/description.html
grass/trunk/raster/r.walk/description.html
grass/trunk/raster/r.water.outlet/description.html
grass/trunk/raster/r.watershed/front/description.html
grass/trunk/raster/r.what.color/description.html
grass/trunk/raster/r.what/description.html
grass/trunk/raster/simwe/r.sim.sediment/description.html
grass/trunk/raster/simwe/r.sim.water/description.html
grass/trunk/raster/wildfire/r.ros/description.html
grass/trunk/raster/wildfire/r.spread/description.html
grass/trunk/raster/wildfire/r.spreadpath/description.html
grass/trunk/raster3d/r3.cross.rast/description.html
grass/trunk/raster3d/r3.gwflow/description.html
grass/trunk/raster3d/r3.in.ascii/description.html
grass/trunk/raster3d/r3.in.v5d/description.html
grass/trunk/raster3d/r3.mkdspf/description.html
grass/trunk/raster3d/r3.out.ascii/description.html
grass/trunk/raster3d/r3.out.v5d/description.html
grass/trunk/raster3d/r3.out.vtk/description.html
grass/trunk/raster3d/r3.showdspf/description.html
grass/trunk/raster3d/r3.stats/description.html
grass/trunk/raster3d/r3.to.rast/description.html
grass/trunk/scripts/d.correlate/description.html
grass/trunk/scripts/d.out.gpsdrive/description.html
grass/trunk/scripts/d.polar/description.html
grass/trunk/scripts/d.rast.edit/description.html
grass/trunk/scripts/d.rast.leg/description.html
grass/trunk/scripts/d.shadedmap/description.html
grass/trunk/scripts/d.vect.thematic/description.html
grass/trunk/scripts/db.dropcol/description.html
grass/trunk/scripts/db.droptable/description.html
grass/trunk/scripts/db.in.ogr/description.html
grass/trunk/scripts/db.out.ogr/description.html
grass/trunk/scripts/db.test/description.html
grass/trunk/scripts/g.manual/description.html
grass/trunk/scripts/g.mlist/description.html
grass/trunk/scripts/g.mremove/description.html
grass/trunk/scripts/i.fusion.brovey/description.html
grass/trunk/scripts/i.image.mosaic/description.html
grass/trunk/scripts/i.in.spotvgt/description.html
grass/trunk/scripts/i.landsat.rgb/description.html
grass/trunk/scripts/i.oif/description.html
grass/trunk/scripts/i.spectral/description.html
grass/trunk/scripts/i.tasscap/description.html
grass/trunk/scripts/m.proj/description.html
grass/trunk/scripts/r.blend/description.html
grass/trunk/scripts/r.fillnulls/description.html
grass/trunk/scripts/r.in.aster/description.html
grass/trunk/scripts/r.in.srtm/description.html
grass/trunk/scripts/r.in.wms/description.html
grass/trunk/scripts/r.mapcalculator/description.html
grass/trunk/scripts/r.mask/description.html
grass/trunk/scripts/r.out.gdal/description.html
grass/trunk/scripts/r.out.xyz/description.html
grass/trunk/scripts/r.plane/description.html
grass/trunk/scripts/r.reclass.area/description.html
grass/trunk/scripts/r.regression.line/description.html
grass/trunk/scripts/r.shaded.relief/description.html
grass/trunk/scripts/r.tileset/description.html
grass/trunk/scripts/r3.mapcalculator/description.html
grass/trunk/scripts/v.build.all/description.html
grass/trunk/scripts/v.centroids/description.html
grass/trunk/scripts/v.convert.all/description.html
grass/trunk/scripts/v.db.addcol/description.html
grass/trunk/scripts/v.db.addtable/description.html
grass/trunk/scripts/v.db.dropcol/description.html
grass/trunk/scripts/v.db.droptable/description.html
grass/trunk/scripts/v.db.join/description.html
grass/trunk/scripts/v.db.reconnect.all/description.html
grass/trunk/scripts/v.db.renamecol/description.html
grass/trunk/scripts/v.db.univar/description.html
grass/trunk/scripts/v.db.update/description.html
grass/trunk/scripts/v.dissolve/description.html
grass/trunk/scripts/v.in.e00/description.html
grass/trunk/scripts/v.in.garmin/description.html
grass/trunk/scripts/v.in.geonames/description.html
grass/trunk/scripts/v.in.gns/description.html
grass/trunk/scripts/v.in.gpsbabel/description.html
grass/trunk/scripts/v.in.mapgen/description.html
grass/trunk/scripts/v.in.sites.all/description.html
grass/trunk/scripts/v.in.wfs/description.html
grass/trunk/scripts/v.rast.stats/description.html
grass/trunk/scripts/v.report/description.html
grass/trunk/scripts/v.what.vect/description.html
grass/trunk/sites/s.in.ascii/description.html
grass/trunk/sites/s.out.ascii/description.html
grass/trunk/vector/lidar/v.lidar.correction/description.html
grass/trunk/vector/lidar/v.lidar.edgedetection/description.html
grass/trunk/vector/lidar/v.lidar.growing/description.html
grass/trunk/vector/lidar/v.outlier/description.html
grass/trunk/vector/lidar/v.surf.bspline/description.html
grass/trunk/vector/v.buffer/description.html
grass/trunk/vector/v.build.polylines/description.html
grass/trunk/vector/v.build/description.html
grass/trunk/vector/v.category/description.html
grass/trunk/vector/v.class/description.html
grass/trunk/vector/v.clean/description.html
grass/trunk/vector/v.convert/description.html
grass/trunk/vector/v.db.connect/description.html
grass/trunk/vector/v.db.select/description.html
grass/trunk/vector/v.digit/description.html
grass/trunk/vector/v.distance/description.html
grass/trunk/vector/v.drape/description.html
grass/trunk/vector/v.edit/description.html
grass/trunk/vector/v.external/description.html
grass/trunk/vector/v.extract/description.html
grass/trunk/vector/v.extrude/description.html
grass/trunk/vector/v.generalize/description.html
grass/trunk/vector/v.hull/description.html
grass/trunk/vector/v.in.ascii/description.html
grass/trunk/vector/v.in.db/description.html
grass/trunk/vector/v.in.dwg/description.html
grass/trunk/vector/v.in.dxf/description.html
grass/trunk/vector/v.in.ogr/description.html
grass/trunk/vector/v.in.region/description.html
grass/trunk/vector/v.in.sites/description.html
grass/trunk/vector/v.info/description.html
grass/trunk/vector/v.kcv/description.html
grass/trunk/vector/v.kernel/description.html
grass/trunk/vector/v.label.sa/description.html
grass/trunk/vector/v.label/description.html
grass/trunk/vector/v.lrs/v.lrs.create/description.html
grass/trunk/vector/v.lrs/v.lrs.label/description.html
grass/trunk/vector/v.lrs/v.lrs.segment/description.html
grass/trunk/vector/v.lrs/v.lrs.where/description.html
grass/trunk/vector/v.mkgrid/description.html
grass/trunk/vector/v.neighbors/description.html
grass/trunk/vector/v.net.alloc/description.html
grass/trunk/vector/v.net.iso/description.html
grass/trunk/vector/v.net.path/description.html
grass/trunk/vector/v.net.salesman/description.html
grass/trunk/vector/v.net.steiner/description.html
grass/trunk/vector/v.net.visibility/description.html
grass/trunk/vector/v.net/description.html
grass/trunk/vector/v.normal/description.html
grass/trunk/vector/v.out.ascii/description.html
grass/trunk/vector/v.out.dxf/description.html
grass/trunk/vector/v.out.ogr/description.html
grass/trunk/vector/v.out.pov/description.html
grass/trunk/vector/v.out.svg/description.html
grass/trunk/vector/v.out.vtk/description.html
grass/trunk/vector/v.overlay/description.html
grass/trunk/vector/v.parallel/description.html
grass/trunk/vector/v.patch/description.html
grass/trunk/vector/v.perturb/description.html
grass/trunk/vector/v.proj/description.html
grass/trunk/vector/v.qcount/description.html
grass/trunk/vector/v.random/description.html
grass/trunk/vector/v.reclass/description.html
grass/trunk/vector/v.sample/description.html
grass/trunk/vector/v.segment/description.html
grass/trunk/vector/v.select/description.html
grass/trunk/vector/v.split/description.html
grass/trunk/vector/v.support/description.html
grass/trunk/vector/v.surf.idw/description.html
grass/trunk/vector/v.surf.rst/description.html
grass/trunk/vector/v.to.db/description.html
grass/trunk/vector/v.to.points/description.html
grass/trunk/vector/v.to.rast/description.html
grass/trunk/vector/v.to.rast3/description.html
grass/trunk/vector/v.transform/description.html
grass/trunk/vector/v.type/description.html
grass/trunk/vector/v.univar/description.html
grass/trunk/vector/v.vol.rst/description.html
grass/trunk/vector/v.what.rast/description.html
grass/trunk/vector/v.what/description.html
grass/trunk/visualization/nviz/description.html
grass/trunk/visualization/nviz/src/description.html
grass/trunk/visualization/nviz2/cmd/description.html
grass/trunk/visualization/xganim/description.html
Modified:
grass/trunk/gui/tcltk/gis.m/Makefile
grass/trunk/imagery/i.ortho.photo/photo.2image/Makefile
grass/trunk/imagery/i.ortho.photo/photo.2target/Makefile
grass/trunk/imagery/i.ortho.photo/photo.camera/Makefile
grass/trunk/imagery/i.ortho.photo/photo.init/Makefile
grass/trunk/imagery/i.ortho.photo/photo.rectify/Makefile
grass/trunk/lib/cairodriver/Makefile
grass/trunk/lib/db/sqlp/Makefile
grass/trunk/lib/htmldriver/Makefile
grass/trunk/lib/pngdriver/Makefile
grass/trunk/lib/psdriver/Makefile
grass/trunk/raster/r.li/Makefile
grass/trunk/raster/r.li/r.li.daemon/Makefile
grass/trunk/visualization/nviz/Makefile
grass/trunk/visualization/nviz/src/Makefile
Log:
Rename description.html -> $(PGM).html
Copied: grass/trunk/db/db.login/db.login.html (from rev 32770, grass/trunk/db/db.login/description.html)
===================================================================
--- grass/trunk/db/db.login/db.login.html (rev 0)
+++ grass/trunk/db/db.login/db.login.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,46 @@
+<h2>DESCRIPTION</h2>
+
+<em>db.login</em> sets user/password for driver/database.
+
+<h2>NOTE</h2>
+
+This is only related to SQL database backends (PostgreSQL, MySQL etc).
+The passwords are stored in a hidden file in the user account ('home'
+directory) called <em>.grasslogin6</em>. Only the file owner
+can access this file.
+
+<h2>EXAMPLES</h2>
+
+Example 1: Username specified, password will be invisibly queried interactively:
+
+<div class="code"><pre>
+db.login user=bacava
+</pre></div>
+
+<P>
+Example 2: Username and password specified (note that the command
+lines history will store the password in this way):
+
+<div class="code"><pre>
+db.login user=bacava pass=secret
+</pre></div>
+
+<P>
+Example 3: Username and empty password specified (note that the command
+lines history will store the password in this way):
+
+<div class="code"><pre>
+db.login user=bacava pass=""
+</pre></div>
+
+<h2>SEE ALSO</h2>
+<em>
+<a HREF="db.connect.html">db.connect</a>,
+<a HREF="db.test.html">db.test</a>
+</em>
+
+<h2>AUTHOR</h2>
+
+Radim Blazek
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/db/db.login/description.html
===================================================================
--- grass/trunk/db/db.login/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/db/db.login/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,46 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>db.login</em> sets user/password for driver/database.
-
-<h2>NOTE</h2>
-
-This is only related to SQL database backends (PostgreSQL, MySQL etc).
-The passwords are stored in a hidden file in the user account ('home'
-directory) called <em>.grasslogin6</em>. Only the file owner
-can access this file.
-
-<h2>EXAMPLES</h2>
-
-Example 1: Username specified, password will be invisibly queried interactively:
-
-<div class="code"><pre>
-db.login user=bacava
-</pre></div>
-
-<P>
-Example 2: Username and password specified (note that the command
-lines history will store the password in this way):
-
-<div class="code"><pre>
-db.login user=bacava pass=secret
-</pre></div>
-
-<P>
-Example 3: Username and empty password specified (note that the command
-lines history will store the password in this way):
-
-<div class="code"><pre>
-db.login user=bacava pass=""
-</pre></div>
-
-<h2>SEE ALSO</h2>
-<em>
-<a HREF="db.connect.html">db.connect</a>,
-<a HREF="db.test.html">db.test</a>
-</em>
-
-<h2>AUTHOR</h2>
-
-Radim Blazek
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/display/d.barscale/d.barscale.html (from rev 32770, grass/trunk/display/d.barscale/description.html)
===================================================================
--- grass/trunk/display/d.barscale/d.barscale.html (rev 0)
+++ grass/trunk/display/d.barscale/d.barscale.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,33 @@
+<H2>DESCRIPTION</H2>
+
+<EM>d.barscale</EM> displays a barscale on the graphics monitor using either
+the mouse or given screen coordinates. It can draw the scale in a couple of
+styles or simply draw a north arrow.
+
+
+<h2>NOTE</h2>
+
+<EM>d.barscale</EM> will not work in Lat/Lon locations as the horizontal
+scale distance changes with latitude. Try <EM>d.grid</EM> instead.
+
+<p>The -l flag will always draw a north arrow <em>and</em> a line scale
+together; it is currently not possible to draw a line scale without a north
+arrow. Instead, the -s flag can be used to draw a barscale only.</p>
+
+<H2>SEE ALSO</H2>
+
+<EM>
+<A HREF="d.graph.html">d.graph</A><br>
+<A HREF="d.grid.html">d.grid</A><br>
+<A HREF="d.legend.html">d.legend</A><br>
+<A HREF="d.measure.html">d.measure</A><br>
+<A HREF="d.where.html">d.where</A><br>
+<A HREF="g.region.html">g.region</A><br>
+</EM>
+
+
+<H2>AUTHOR</H2>
+unknown.
+
+<p>
+<i>Last changed: $Date$</i>
Deleted: grass/trunk/display/d.barscale/description.html
===================================================================
--- grass/trunk/display/d.barscale/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/display/d.barscale/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,33 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-<EM>d.barscale</EM> displays a barscale on the graphics monitor using either
-the mouse or given screen coordinates. It can draw the scale in a couple of
-styles or simply draw a north arrow.
-
-
-<h2>NOTE</h2>
-
-<EM>d.barscale</EM> will not work in Lat/Lon locations as the horizontal
-scale distance changes with latitude. Try <EM>d.grid</EM> instead.
-
-<p>The -l flag will always draw a north arrow <em>and</em> a line scale
-together; it is currently not possible to draw a line scale without a north
-arrow. Instead, the -s flag can be used to draw a barscale only.</p>
-
-<H2>SEE ALSO</H2>
-
-<EM>
-<A HREF="d.graph.html">d.graph</A><br>
-<A HREF="d.grid.html">d.grid</A><br>
-<A HREF="d.legend.html">d.legend</A><br>
-<A HREF="d.measure.html">d.measure</A><br>
-<A HREF="d.where.html">d.where</A><br>
-<A HREF="g.region.html">g.region</A><br>
-</EM>
-
-
-<H2>AUTHOR</H2>
-unknown.
-
-<p>
-<i>Last changed: $Date$</i>
Copied: grass/trunk/display/d.colorlist/d.colorlist.html (from rev 32770, grass/trunk/display/d.colorlist/description.html)
===================================================================
--- grass/trunk/display/d.colorlist/d.colorlist.html (rev 0)
+++ grass/trunk/display/d.colorlist/d.colorlist.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,15 @@
+<H2>DESCRIPTION</H2>
+
+<EM>d.colorlist</EM> report the available color names.
+The list contains all available display colors with a configurable
+separator (default is comma).
+
+<H2>SEE ALSO</H2>
+
+<EM><A HREF="d.colors.html">d.colors</A>
+
+<H2>AUTHOR</H2>
+
+Andreas Lange
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/display/d.colorlist/description.html
===================================================================
--- grass/trunk/display/d.colorlist/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/display/d.colorlist/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,15 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-<EM>d.colorlist</EM> report the available color names.
-The list contains all available display colors with a configurable
-separator (default is comma).
-
-<H2>SEE ALSO</H2>
-
-<EM><A HREF="d.colors.html">d.colors</A>
-
-<H2>AUTHOR</H2>
-
-Andreas Lange
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/display/d.colors/d.colors.html (from rev 32770, grass/trunk/display/d.colors/description.html)
===================================================================
--- grass/trunk/display/d.colors/d.colors.html (rev 0)
+++ grass/trunk/display/d.colors/d.colors.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,205 @@
+<H2>DESCRIPTION</H2>
+
+A color table file associates specific colors with the categories of a
+raster map layer. The user can change these map category color assignments
+(i.e., change the map's color table) interactively, by first displaying the
+raster map to the graphics monitor and then running the program
+<EM>d.colors</EM>.
+
+<P>
+Any color changes made using <EM>d.colors</EM> will not immediately be
+shown on the graphics display; however, any color changes saved will
+still alter the map's color table and will appear next time the raster
+map layer is redisplayed (see <EM><A HREF="d.colortable.html">d.colortable</A></EM>).
+
+<P>
+The user must first display the relevant raster map layer to the
+active frame on the graphics monitor (e.g., using
+<EM><A HREF="d.rast.html">d.rast</A></EM>) before running
+<EM>d.colors</EM>. The user can then either enter the name of the
+raster map layer whose color table is to be changed on the command
+line (e.g., by typing: <tt>d.colors map=soils</tt>), or type
+<tt>d.colors</tt> without program arguments. If the user simply types
+<tt>d.colors</tt> without program arguments on the command line,
+<EM>d.colors</EM> will ask the user to enter the name of an existing
+raster map layer using the standard GRASS interface.
+
+<P>
+In either case, the user is then presented with the <EM>d.colors</EM>
+command menu, shown below.
+<!-- This menu is the same as the category and color
+changing portion of the <EM><A HREF="d.display.html">d.display</A></EM>
+menu. -->
+The <EM>d.colors</EM> commands are listed beneath the Category
+Pointer Movement, Color Modification, Replotting Screen, and Quitting
+sections below. Commands are invoked by typing in the single-key response
+shown to the left below. (Longer descriptions of these commands appear to
+the right.) Results from invoking these commands will be reflected in the
+Category and Category Number sections of the <EM>d.colors</EM> screen. On
+the <EM>d.colors</EM> screen menu, commands appear in the right half of the
+screen, and the current status of categories appears in the left half of the
+screen.
+
+<PRE>
+CATEGORIES
+ 0 No Data
+ 1 (Category 1 description)
+ 2 (Category 2 description)
+ . ....
+ . ....
+CATEGORY NUMBER:
+ RED 0 0%
+ GREEN 0 0%
+ BLUE 0 0%
+Shift Incr: 10 3%
+CATEGORY POINTER MOVEMENT
+ D/d down (cats) Move pointer to next category
+ U/u up (cats) Move pointer to previous category
+COLOR MODIFICATIONS
+ R/r RED Increase/decrease RED intensity
+ G/g GREEN Increase/decrease GREEN intensity
+ B/b BLUE Increase/decrease BLUE intensity
+ I/i increment Increase/decrease increment
+ (of intensity shift)
+ h highlight Highlight current color
+ +/- shift colors Shift entire color table (up/down)
+ c save color Save color table
+ t toggle table Toggle to different color table
+REPLOTTING SCREEN
+ * Replot screen Replots the screen
+QUITTING
+ Q quit Quits program
+</PRE>
+
+Changing categories - The keys
+<B>"d, D, u,"</B>
+and
+<B>"U"</B>
+are used to move to a different category. The lower case letters move up,
+<B>u,</B>
+and down,
+<B>d,</B>
+the category list one category at a time. The upper case letters move 10
+categories at a time for fast movement. The cursor does wrap between the
+first and last categories. The current category is noted on the text screen
+with an arrow, and is indicated on the graphics screen by a box around the
+current color.
+
+<P>
+
+Changing colors - The color associated with the current category can be
+changed with the
+<B>"R, r, G, g, B,"</B>
+and
+<B>b</B>
+keys. The upper case letters increase the intensities of
+red
+<B>R,</B>
+green
+<B>G,</B>
+and blue
+<B>B</B>
+for the current category; the lower case letters decrease the intensities of
+these same colors for the current category. Video devices make all the
+colors of the spectrum by mixing red, green, and blue. For those
+accustomed to red, yellow, and blue being the primary colors, this can
+be confusing. For starters, yellow is made by mixing red and green. The
+intensities are listed on the text screen in as percentages.
+
+<P>
+
+Keys <B>I</B> and <B>i</B> increase and decrease the
+percentage change that each keystroke of one of the color
+keys (<EM>R, r, G, g, B, b</EM>) causes in its respective
+color. The increase increment is initially set to 10%.
+Thus, pressing the <EM>R</EM> key would will increase the
+red component of the current category by 10%.
+
+<P>
+
+Highlight - The
+<B>h</B>
+key toggles between the current category color and the current
+highlight color. This color is initially black but can be modified as
+above while in highlight mode. Blinking can be accomplished by repeatedly
+striking the
+<B>h</B>
+key. When changing to different categories using the movement keys as
+described above, while in highlight mode the category colors will be
+always left showing their actual colors. Only one category is highlighted
+at any one time.
+
+<P>
+
+Saving the current color table -
+Pressing the <B>c</B> key will save the current color table as you have
+modified it. This table will then be used next time you
+display or paint this raster map layer.
+
+<P>
+
+Color table toggle - Different types of color tables are suitable for
+different raster map layers.
+The key
+<B>t</B>
+flips between the following color tables: red, green, blue color ramp; gray
+scale; smooth changing color wave; random colors; and the saved color table.
+
+<P>
+
+Color table shift - The entire table is shifted up and down using the
+<B>+</B>
+and
+<B>-</B>
+keys.
+
+<P>
+
+Quitting the <EM>d.colors</EM> program - Pressing the
+<B>Q</B> key will cause you to quit the <EM>d.colors</EM>
+program. If colors have been modified but not saved,
+<EM>d.colors</EM> will ask:
+<PRE>
+ Colors changed
+ Save the changes? (y/n)
+</PRE>
+The user should type in <B>y</B> to save changes,
+or <B>n</B> to not save changes, before quitting the program.
+If the user types <B>n</B>, the program will ask:
+<PRE>
+ Quit anyway? (y/n)
+</PRE>
+<H2>NOTES</H2>
+
+<P>
+
+The map whose color table is to be altered with
+<EM>d.colors</EM> must already be on display in the active
+display frame on the graphics monitor before
+<EM>d.colors</EM> is run. This can be done using the
+command <em><A HREF="d.rast.html">d.rast</a> map=name</EM> (where <EM>name</EM> is a raster map
+layer whose color table the user wishes to alter).
+
+<P>
+Some color monitors may not support the full range of colors required
+to display all of the map's categories listed in the map's color table.
+However, regardless of whether the user can see the color changes he is
+effecting to a map's color table, any changes to a map's color table
+made with <EM>d.colors</EM> that are saved will appear in the map's color table.
+
+<H2>SEE ALSO</H2>
+
+<EM>
+<A HREF="d.colortable.html">d.colortable</A>,
+<A HREF="d.rast.html">d.rast</A>,
+<A HREF="r.colors.html">r.colors</A>
+</EM>
+
+<H2>AUTHOR</H2>
+
+James Westervelt, U.S. Army Construction Engineering
+Research Laboratory
+
+<p>
+<i>Last changed: $Date$</i>
+
Deleted: grass/trunk/display/d.colors/description.html
===================================================================
--- grass/trunk/display/d.colors/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/display/d.colors/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,205 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-A color table file associates specific colors with the categories of a
-raster map layer. The user can change these map category color assignments
-(i.e., change the map's color table) interactively, by first displaying the
-raster map to the graphics monitor and then running the program
-<EM>d.colors</EM>.
-
-<P>
-Any color changes made using <EM>d.colors</EM> will not immediately be
-shown on the graphics display; however, any color changes saved will
-still alter the map's color table and will appear next time the raster
-map layer is redisplayed (see <EM><A HREF="d.colortable.html">d.colortable</A></EM>).
-
-<P>
-The user must first display the relevant raster map layer to the
-active frame on the graphics monitor (e.g., using
-<EM><A HREF="d.rast.html">d.rast</A></EM>) before running
-<EM>d.colors</EM>. The user can then either enter the name of the
-raster map layer whose color table is to be changed on the command
-line (e.g., by typing: <tt>d.colors map=soils</tt>), or type
-<tt>d.colors</tt> without program arguments. If the user simply types
-<tt>d.colors</tt> without program arguments on the command line,
-<EM>d.colors</EM> will ask the user to enter the name of an existing
-raster map layer using the standard GRASS interface.
-
-<P>
-In either case, the user is then presented with the <EM>d.colors</EM>
-command menu, shown below.
-<!-- This menu is the same as the category and color
-changing portion of the <EM><A HREF="d.display.html">d.display</A></EM>
-menu. -->
-The <EM>d.colors</EM> commands are listed beneath the Category
-Pointer Movement, Color Modification, Replotting Screen, and Quitting
-sections below. Commands are invoked by typing in the single-key response
-shown to the left below. (Longer descriptions of these commands appear to
-the right.) Results from invoking these commands will be reflected in the
-Category and Category Number sections of the <EM>d.colors</EM> screen. On
-the <EM>d.colors</EM> screen menu, commands appear in the right half of the
-screen, and the current status of categories appears in the left half of the
-screen.
-
-<PRE>
-CATEGORIES
- 0 No Data
- 1 (Category 1 description)
- 2 (Category 2 description)
- . ....
- . ....
-CATEGORY NUMBER:
- RED 0 0%
- GREEN 0 0%
- BLUE 0 0%
-Shift Incr: 10 3%
-CATEGORY POINTER MOVEMENT
- D/d down (cats) Move pointer to next category
- U/u up (cats) Move pointer to previous category
-COLOR MODIFICATIONS
- R/r RED Increase/decrease RED intensity
- G/g GREEN Increase/decrease GREEN intensity
- B/b BLUE Increase/decrease BLUE intensity
- I/i increment Increase/decrease increment
- (of intensity shift)
- h highlight Highlight current color
- +/- shift colors Shift entire color table (up/down)
- c save color Save color table
- t toggle table Toggle to different color table
-REPLOTTING SCREEN
- * Replot screen Replots the screen
-QUITTING
- Q quit Quits program
-</PRE>
-
-Changing categories - The keys
-<B>"d, D, u,"</B>
-and
-<B>"U"</B>
-are used to move to a different category. The lower case letters move up,
-<B>u,</B>
-and down,
-<B>d,</B>
-the category list one category at a time. The upper case letters move 10
-categories at a time for fast movement. The cursor does wrap between the
-first and last categories. The current category is noted on the text screen
-with an arrow, and is indicated on the graphics screen by a box around the
-current color.
-
-<P>
-
-Changing colors - The color associated with the current category can be
-changed with the
-<B>"R, r, G, g, B,"</B>
-and
-<B>b</B>
-keys. The upper case letters increase the intensities of
-red
-<B>R,</B>
-green
-<B>G,</B>
-and blue
-<B>B</B>
-for the current category; the lower case letters decrease the intensities of
-these same colors for the current category. Video devices make all the
-colors of the spectrum by mixing red, green, and blue. For those
-accustomed to red, yellow, and blue being the primary colors, this can
-be confusing. For starters, yellow is made by mixing red and green. The
-intensities are listed on the text screen in as percentages.
-
-<P>
-
-Keys <B>I</B> and <B>i</B> increase and decrease the
-percentage change that each keystroke of one of the color
-keys (<EM>R, r, G, g, B, b</EM>) causes in its respective
-color. The increase increment is initially set to 10%.
-Thus, pressing the <EM>R</EM> key would will increase the
-red component of the current category by 10%.
-
-<P>
-
-Highlight - The
-<B>h</B>
-key toggles between the current category color and the current
-highlight color. This color is initially black but can be modified as
-above while in highlight mode. Blinking can be accomplished by repeatedly
-striking the
-<B>h</B>
-key. When changing to different categories using the movement keys as
-described above, while in highlight mode the category colors will be
-always left showing their actual colors. Only one category is highlighted
-at any one time.
-
-<P>
-
-Saving the current color table -
-Pressing the <B>c</B> key will save the current color table as you have
-modified it. This table will then be used next time you
-display or paint this raster map layer.
-
-<P>
-
-Color table toggle - Different types of color tables are suitable for
-different raster map layers.
-The key
-<B>t</B>
-flips between the following color tables: red, green, blue color ramp; gray
-scale; smooth changing color wave; random colors; and the saved color table.
-
-<P>
-
-Color table shift - The entire table is shifted up and down using the
-<B>+</B>
-and
-<B>-</B>
-keys.
-
-<P>
-
-Quitting the <EM>d.colors</EM> program - Pressing the
-<B>Q</B> key will cause you to quit the <EM>d.colors</EM>
-program. If colors have been modified but not saved,
-<EM>d.colors</EM> will ask:
-<PRE>
- Colors changed
- Save the changes? (y/n)
-</PRE>
-The user should type in <B>y</B> to save changes,
-or <B>n</B> to not save changes, before quitting the program.
-If the user types <B>n</B>, the program will ask:
-<PRE>
- Quit anyway? (y/n)
-</PRE>
-<H2>NOTES</H2>
-
-<P>
-
-The map whose color table is to be altered with
-<EM>d.colors</EM> must already be on display in the active
-display frame on the graphics monitor before
-<EM>d.colors</EM> is run. This can be done using the
-command <em><A HREF="d.rast.html">d.rast</a> map=name</EM> (where <EM>name</EM> is a raster map
-layer whose color table the user wishes to alter).
-
-<P>
-Some color monitors may not support the full range of colors required
-to display all of the map's categories listed in the map's color table.
-However, regardless of whether the user can see the color changes he is
-effecting to a map's color table, any changes to a map's color table
-made with <EM>d.colors</EM> that are saved will appear in the map's color table.
-
-<H2>SEE ALSO</H2>
-
-<EM>
-<A HREF="d.colortable.html">d.colortable</A>,
-<A HREF="d.rast.html">d.rast</A>,
-<A HREF="r.colors.html">r.colors</A>
-</EM>
-
-<H2>AUTHOR</H2>
-
-James Westervelt, U.S. Army Construction Engineering
-Research Laboratory
-
-<p>
-<i>Last changed: $Date$</i>
-
Copied: grass/trunk/display/d.colortable/d.colortable.html (from rev 32770, grass/trunk/display/d.colortable/description.html)
===================================================================
--- grass/trunk/display/d.colortable/d.colortable.html (rev 0)
+++ grass/trunk/display/d.colortable/d.colortable.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,111 @@
+<H2>DESCRIPTION</H2>
+
+
+The GRASS program <EM>d.colortable</EM>
+is used to display the color table associated with a raster map layer in the
+active frame on the graphics monitor. The map <EM>name</EM> should be
+an available raster map layer in the user's current mapset search path
+and location.
+
+<P>
+
+<H3>Parameters:</H3>
+
+<DL>
+<DT><B>map=</B><EM>name</EM>
+<DD>Name of a raster map layer in the user's current mapset search path
+whose color table is to be displayed.
+<DT><B>color=</B><EM>name</EM>
+<DD>Color of the lines separating the colors of the color table.
+<BR>
+Options: red, orange, yellow, green, blue,
+indigo, violet, gray, white</B>, and black.
+<BR>
+Default: <EM>white</EM>
+<DT><B>lines=</B><EM>value</EM>
+<DD>Number of lines to appear in the color table.
+<BR>
+Options: 1 - 1000
+<DT><B>cols=</B><EM>value</EM>
+<DD>Number of columns to appear in the color table.
+<BR>
+Options: 1 - 1000
+
+If the <EM>value</B>s</EM> of both <EM>lines</EM> and <EM>cols</EM> are not specified by
+the user, <EM>d.colortable</EM>
+divides the active frame equally among the number of categories
+present in the named raster map layer. If one option is specified,
+the other is automatically set to accommodate all categories.
+If both are specified, as many categories as possible are displayed.
+</DL>
+
+<P>
+The user can specify all needed parameters on the command line using the
+form:
+
+<P>
+<DL>
+<DD>
+<B>d.colortable map=</B><EM>name</EM>
+[<B>color=</B><EM>name</EM>]
+[<B>lines=</B><EM>value</EM>]
+[<B>cols=</B><EM>value</EM>]
+</DL>
+
+<P>
+If the user specifies the name of a map on the command line but does not
+specify the values of other parameters, parameter default values will be used.
+Alternately, if the user types simply <B>d.colortable</B> on the command line
+without any program arguments, the program will prompt the user for parameter
+settings using the standard GRASS <A HREF="parser.html">parser</A> interface described in the manual
+entry for <EM><A HREF="parser.html">parser</A></B>.</EM>
+
+<H2>EXAMPLE</H2>
+
+The user running the command:
+<DL>
+<DD>
+<B>d.colortable map=</B><EM>soils</EM>
+[<B>color=</B><EM>red</EM>]
+[<B>lines=</B><EM>1</EM>]
+[<B>cols=</B><EM>3</EM>]
+</DL>
+would see the active graphics frame divided into three columns
+extending the full frame height. The lines dividing the color table
+associated with the <EM>soils</EM> map would be displayed in red.
+The user would see, at most, only three of the colors from the <EM>soils</EM>
+color table displayed in the active frame (because the user requested
+that this frame be divided into three sections).
+
+<H2>NOTES</H2>
+
+If the user wishes to display the entire color table associated with
+a map, the user should either stipulate a number of lines (rows) and
+columns (cols) sufficient to accommodate the number of categories
+in the map's color table, or fail to assign values to one or both of
+<EM>lines</EM> and/or <EM>cols</B>.</EM>
+If the user runs <EM>d.colortable</EM> using the default number of
+lines and columns (the full graphics frame), all categories from the
+map's color table will be displayed. However, if the user requests
+that the color table associated with a map which has 10 data categories
+be displayed in a graphics frame with only 3 lines (rows) and 2 columns
+(a total of six cells),
+only six of the ten map categories will be displayed.
+
+<P>
+The user should run the GRASS program
+<EM><A HREF="d.erase.html">d.erase</A></EM> between
+runs of <EM>d.colortable</EM> to avoid confusion.
+
+<H2>SEE ALSO</H2>
+
+<EM><A HREF="d.colors.html">d.colors</A></EM><br>
+<EM><A HREF="d.erase.html">d.erase</A></EM><br>
+<EM><A HREF="d.rast.html">d.rast</A></EM><br>
+<EM><A HREF="parser.html">parser</A></EM>
+
+<H2>AUTHOR</H2>
+
+James Westervelt, U.S. Army Construction Engineering Research Laboratory
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/display/d.colortable/description.html
===================================================================
--- grass/trunk/display/d.colortable/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/display/d.colortable/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,111 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-
-The GRASS program <EM>d.colortable</EM>
-is used to display the color table associated with a raster map layer in the
-active frame on the graphics monitor. The map <EM>name</EM> should be
-an available raster map layer in the user's current mapset search path
-and location.
-
-<P>
-
-<H3>Parameters:</H3>
-
-<DL>
-<DT><B>map=</B><EM>name</EM>
-<DD>Name of a raster map layer in the user's current mapset search path
-whose color table is to be displayed.
-<DT><B>color=</B><EM>name</EM>
-<DD>Color of the lines separating the colors of the color table.
-<BR>
-Options: red, orange, yellow, green, blue,
-indigo, violet, gray, white</B>, and black.
-<BR>
-Default: <EM>white</EM>
-<DT><B>lines=</B><EM>value</EM>
-<DD>Number of lines to appear in the color table.
-<BR>
-Options: 1 - 1000
-<DT><B>cols=</B><EM>value</EM>
-<DD>Number of columns to appear in the color table.
-<BR>
-Options: 1 - 1000
-
-If the <EM>value</B>s</EM> of both <EM>lines</EM> and <EM>cols</EM> are not specified by
-the user, <EM>d.colortable</EM>
-divides the active frame equally among the number of categories
-present in the named raster map layer. If one option is specified,
-the other is automatically set to accommodate all categories.
-If both are specified, as many categories as possible are displayed.
-</DL>
-
-<P>
-The user can specify all needed parameters on the command line using the
-form:
-
-<P>
-<DL>
-<DD>
-<B>d.colortable map=</B><EM>name</EM>
-[<B>color=</B><EM>name</EM>]
-[<B>lines=</B><EM>value</EM>]
-[<B>cols=</B><EM>value</EM>]
-</DL>
-
-<P>
-If the user specifies the name of a map on the command line but does not
-specify the values of other parameters, parameter default values will be used.
-Alternately, if the user types simply <B>d.colortable</B> on the command line
-without any program arguments, the program will prompt the user for parameter
-settings using the standard GRASS <A HREF="parser.html">parser</A> interface described in the manual
-entry for <EM><A HREF="parser.html">parser</A></B>.</EM>
-
-<H2>EXAMPLE</H2>
-
-The user running the command:
-<DL>
-<DD>
-<B>d.colortable map=</B><EM>soils</EM>
-[<B>color=</B><EM>red</EM>]
-[<B>lines=</B><EM>1</EM>]
-[<B>cols=</B><EM>3</EM>]
-</DL>
-would see the active graphics frame divided into three columns
-extending the full frame height. The lines dividing the color table
-associated with the <EM>soils</EM> map would be displayed in red.
-The user would see, at most, only three of the colors from the <EM>soils</EM>
-color table displayed in the active frame (because the user requested
-that this frame be divided into three sections).
-
-<H2>NOTES</H2>
-
-If the user wishes to display the entire color table associated with
-a map, the user should either stipulate a number of lines (rows) and
-columns (cols) sufficient to accommodate the number of categories
-in the map's color table, or fail to assign values to one or both of
-<EM>lines</EM> and/or <EM>cols</B>.</EM>
-If the user runs <EM>d.colortable</EM> using the default number of
-lines and columns (the full graphics frame), all categories from the
-map's color table will be displayed. However, if the user requests
-that the color table associated with a map which has 10 data categories
-be displayed in a graphics frame with only 3 lines (rows) and 2 columns
-(a total of six cells),
-only six of the ten map categories will be displayed.
-
-<P>
-The user should run the GRASS program
-<EM><A HREF="d.erase.html">d.erase</A></EM> between
-runs of <EM>d.colortable</EM> to avoid confusion.
-
-<H2>SEE ALSO</H2>
-
-<EM><A HREF="d.colors.html">d.colors</A></EM><br>
-<EM><A HREF="d.erase.html">d.erase</A></EM><br>
-<EM><A HREF="d.rast.html">d.rast</A></EM><br>
-<EM><A HREF="parser.html">parser</A></EM>
-
-<H2>AUTHOR</H2>
-
-James Westervelt, U.S. Army Construction Engineering Research Laboratory
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/display/d.erase/d.erase.html (from rev 32770, grass/trunk/display/d.erase/description.html)
===================================================================
--- grass/trunk/display/d.erase/d.erase.html (rev 0)
+++ grass/trunk/display/d.erase/d.erase.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,17 @@
+<h2>DESCRIPTION</h2>
+
+<em>d.erase</em> erases the contents of the active graphics frame, and replaces it with
+the color black (by default) or by whatever color is specified by the user.
+<em>d.erase</em> will not alter the assignment of the active frame.
+
+<h2>SEE ALSO</h2>
+
+<em><a HREF="d.mon.html">d.mon</a></em>
+
+<h2>AUTHOR</h2>
+
+James Westervelt, U.S. Army Construction Engineering
+Research Laboratory
+
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/display/d.erase/description.html
===================================================================
--- grass/trunk/display/d.erase/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/display/d.erase/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,17 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>d.erase</em> erases the contents of the active graphics frame, and replaces it with
-the color black (by default) or by whatever color is specified by the user.
-<em>d.erase</em> will not alter the assignment of the active frame.
-
-<h2>SEE ALSO</h2>
-
-<em><a HREF="d.mon.html">d.mon</a></em>
-
-<h2>AUTHOR</h2>
-
-James Westervelt, U.S. Army Construction Engineering
-Research Laboratory
-
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/display/d.extract/d.extract.html (from rev 32770, grass/trunk/display/d.extract/description.html)
===================================================================
--- grass/trunk/display/d.extract/d.extract.html (rev 0)
+++ grass/trunk/display/d.extract/d.extract.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,25 @@
+<h2>DESCRIPTION</h2>
+
+<em>d.extract</em> allows a user to graphically select vector objects from
+an existing vector map and creates a new map containing only the selected
+objects.
+
+<h2>EXAMPLE</h2>
+
+<h3>Graphically extract roads from a roads map:</h3>
+<div class="code"><pre>
+d.mon x0
+d.vect roads
+d.extract input=roads output=interstate
+</pre></div>
+
+
+<h2>SEE ALSO</h2>
+
+<em><a HREF="v.extract.html">v.extract</a></em>
+
+<h2>AUTHOR</h2>
+
+Radim Blazek, Markus Neteler
+
+<p><i>Last changed: $Date$</i></p>
Deleted: grass/trunk/display/d.extract/description.html
===================================================================
--- grass/trunk/display/d.extract/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/display/d.extract/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,25 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>d.extract</em> allows a user to graphically select vector objects from
-an existing vector map and creates a new map containing only the selected
-objects.
-
-<h2>EXAMPLE</h2>
-
-<h3>Graphically extract roads from a roads map:</h3>
-<div class="code"><pre>
-d.mon x0
-d.vect roads
-d.extract input=roads output=interstate
-</pre></div>
-
-
-<h2>SEE ALSO</h2>
-
-<em><a HREF="v.extract.html">v.extract</a></em>
-
-<h2>AUTHOR</h2>
-
-Radim Blazek, Markus Neteler
-
-<p><i>Last changed: $Date$</i></p>
Copied: grass/trunk/display/d.font/d.font.html (from rev 32770, grass/trunk/display/d.font/description.html)
===================================================================
--- grass/trunk/display/d.font/d.font.html (rev 0)
+++ grass/trunk/display/d.font/d.font.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,74 @@
+<H2>DESCRIPTION</H2>
+
+
+<EM>d.font</EM> allows the user to select use of a specific text font for
+display of text on the graphics monitor.
+The GRASS program
+<EM><A HREF="../html/show.fonts.sh.html">show.fonts.sh</A></EM>
+is a UNIX Bourne shell macro which
+names and displays the fonts that can be selected using <EM>d.font</EM>.
+If the user does not specify a font when using other GRASS programs
+that display text, the font type <EM>romans</EM> is used by default.
+
+<P>
+The user can run this program either non-interactively or interactively.
+If the user specifies a font type name on the command line the program will
+run non-interactively.
+Alternately, the user can simply type <B>d.font</B> on the command line;
+in this case, the program will prompt the user for a display
+text font type using the standard GRASS interface described in the
+manual entry for <EM><A HREF="parser.html">parser</A></EM>.
+
+<P>
+<B>Parameter:</B>
+<DL>
+<DT><B>font=</B><EM>name</EM>
+<DD>Name of a font type, from among the font types italicized below.
+<BR>
+Default: <EM>romans</EM>
+<BR>
+Options: (italized)
+<BR><EM>cyrilc</EM> Cyrillic
+<BR><EM>gothgbt</EM> Gothic Great Britain triplex
+<BR><EM>gothgrt</EM> Gothic German triplex
+<BR><EM>gothitt</EM> Gothic Italian triplex
+<BR><EM>greekc</EM> Greek complex
+<BR><EM>greekcs</EM> Greek complex script
+<BR><EM>greekp</EM> Greek plain
+<BR><EM>greeks</EM> Greek simplex
+<BR><EM>italicc</EM> Italian complex
+<BR><EM>italiccs</EM> Italian complex small
+<BR><EM>italict</EM> Italian triplex
+<BR><EM>romanc</EM> Roman complex
+<BR><EM>romancs</EM> Roman complex small
+<BR><EM>romand</EM> Roman duplex
+<BR><EM>romanp</EM> Roman plain
+<BR><EM>romans</EM> Roman simplex
+<BR><EM>romant</EM> Roman triplex
+<BR><EM>scriptc</EM> Script complex
+<BR><EM>scripts</EM> Script simplex
+</DL>
+
+<H2>NOTES</H2>
+
+The font type
+<EM>romans</EM>
+is the fastest font type to display to the graphics monitor.
+
+<H2>SEE ALSO</H2>
+
+<EM><A HREF="d.text.html">d.text</A></EM><br>
+<EM><A HREF="d.title.html">d.title</A></EM><br>
+<EM><A HREF="parser.html">parser</A></EM>
+
+<H2>AUTHOR</H2>
+
+James Westervelt, U.S. Army Construction Engineering
+Research Laboratory
+
+<P>
+<EM>d.font</EM> uses the public domain version of the Hershey Fonts created
+by Dr. A.V. Hershey while working at the U.S. National Bureau of
+Standards.
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/display/d.font/description.html
===================================================================
--- grass/trunk/display/d.font/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/display/d.font/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,74 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-
-<EM>d.font</EM> allows the user to select use of a specific text font for
-display of text on the graphics monitor.
-The GRASS program
-<EM><A HREF="../html/show.fonts.sh.html">show.fonts.sh</A></EM>
-is a UNIX Bourne shell macro which
-names and displays the fonts that can be selected using <EM>d.font</EM>.
-If the user does not specify a font when using other GRASS programs
-that display text, the font type <EM>romans</EM> is used by default.
-
-<P>
-The user can run this program either non-interactively or interactively.
-If the user specifies a font type name on the command line the program will
-run non-interactively.
-Alternately, the user can simply type <B>d.font</B> on the command line;
-in this case, the program will prompt the user for a display
-text font type using the standard GRASS interface described in the
-manual entry for <EM><A HREF="parser.html">parser</A></EM>.
-
-<P>
-<B>Parameter:</B>
-<DL>
-<DT><B>font=</B><EM>name</EM>
-<DD>Name of a font type, from among the font types italicized below.
-<BR>
-Default: <EM>romans</EM>
-<BR>
-Options: (italized)
-<BR><EM>cyrilc</EM> Cyrillic
-<BR><EM>gothgbt</EM> Gothic Great Britain triplex
-<BR><EM>gothgrt</EM> Gothic German triplex
-<BR><EM>gothitt</EM> Gothic Italian triplex
-<BR><EM>greekc</EM> Greek complex
-<BR><EM>greekcs</EM> Greek complex script
-<BR><EM>greekp</EM> Greek plain
-<BR><EM>greeks</EM> Greek simplex
-<BR><EM>italicc</EM> Italian complex
-<BR><EM>italiccs</EM> Italian complex small
-<BR><EM>italict</EM> Italian triplex
-<BR><EM>romanc</EM> Roman complex
-<BR><EM>romancs</EM> Roman complex small
-<BR><EM>romand</EM> Roman duplex
-<BR><EM>romanp</EM> Roman plain
-<BR><EM>romans</EM> Roman simplex
-<BR><EM>romant</EM> Roman triplex
-<BR><EM>scriptc</EM> Script complex
-<BR><EM>scripts</EM> Script simplex
-</DL>
-
-<H2>NOTES</H2>
-
-The font type
-<EM>romans</EM>
-is the fastest font type to display to the graphics monitor.
-
-<H2>SEE ALSO</H2>
-
-<EM><A HREF="d.text.html">d.text</A></EM><br>
-<EM><A HREF="d.title.html">d.title</A></EM><br>
-<EM><A HREF="parser.html">parser</A></EM>
-
-<H2>AUTHOR</H2>
-
-James Westervelt, U.S. Army Construction Engineering
-Research Laboratory
-
-<P>
-<EM>d.font</EM> uses the public domain version of the Hershey Fonts created
-by Dr. A.V. Hershey while working at the U.S. National Bureau of
-Standards.
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/display/d.fontlist/d.fontlist.html (from rev 32770, grass/trunk/display/d.fontlist/description.html)
===================================================================
--- grass/trunk/display/d.fontlist/d.fontlist.html (rev 0)
+++ grass/trunk/display/d.fontlist/d.fontlist.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,15 @@
+<H2>DESCRIPTION</H2>
+
+<EM>d.fontlist</EM> outputs a list of available fonts for use with
+GRASS display commands.
+
+<H2>SEE ALSO</H2>
+
+<EM><A HREF="d.text.html">d.text</A></EM><br>
+<EM><A HREF="parser.html">parser</A></EM>
+
+<H2>AUTHOR</H2>
+
+Glynn Clements
+
+<p><i>Last changed: $Date: 2008-06-28 00:01:20 +0100 (Sat, 28 Jun 2008) $</i>
Deleted: grass/trunk/display/d.fontlist/description.html
===================================================================
--- grass/trunk/display/d.fontlist/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/display/d.fontlist/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,15 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-<EM>d.fontlist</EM> outputs a list of available fonts for use with
-GRASS display commands.
-
-<H2>SEE ALSO</H2>
-
-<EM><A HREF="d.text.html">d.text</A></EM><br>
-<EM><A HREF="parser.html">parser</A></EM>
-
-<H2>AUTHOR</H2>
-
-Glynn Clements
-
-<p><i>Last changed: $Date: 2008-06-28 00:01:20 +0100 (Sat, 28 Jun 2008) $</i>
Copied: grass/trunk/display/d.geodesic/d.geodesic.html (from rev 32770, grass/trunk/display/d.geodesic/description.html)
===================================================================
--- grass/trunk/display/d.geodesic/d.geodesic.html (rev 0)
+++ grass/trunk/display/d.geodesic/d.geodesic.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,42 @@
+<H2>DESCRIPTION</H2>
+
+<EM>d.geodesic</EM> displays a geodesic line in the active frame on the user's
+graphics monitor. This is also known as the great circle line and traces the
+shortest distance between two user-specified points on the curved surface of
+a longitude/latitude data set. The two coordinate locations named must fall
+within the boundaries of the user's current geographic region.
+
+<H2>OPTIONS</H2>
+
+This program can be run either interactively or non-interactively.
+If the user types <B>d.geodesic</B> on the command line and runs it without other program
+parameters, the mouse will be activated; the user is asked to use
+the mouse to indicate the starting and ending points of each geodesic line
+to be drawn. The default line color (black) and text color (red)
+will be used.
+
+<P>
+Alternately, the user can specify the starting and ending coordinates
+of the geodesic, line color, and text color on the command line,
+and run the program non-interactively.
+
+<P>
+Once the user indicates the starting and ending coordinates
+of the geodesic, the line and its length (in miles) are displayed to
+the user's graphics monitor. If the text color is set to <em>none</em>,
+the great circle distance is not displayed.
+
+<H2>NOTES</H2>
+
+This program works only with GRASS locations using a longitude/latitude
+coordinate system.
+
+<H2>SEE ALSO</H2>
+
+<EM><A HREF="d.rhumbline.html">d.rhumbline</A></EM>
+
+<H2>AUTHOR</H2>
+
+Michael Shapiro, U.S. Army Construction Engineering Research Laboratory
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/display/d.geodesic/description.html
===================================================================
--- grass/trunk/display/d.geodesic/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/display/d.geodesic/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,42 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-<EM>d.geodesic</EM> displays a geodesic line in the active frame on the user's
-graphics monitor. This is also known as the great circle line and traces the
-shortest distance between two user-specified points on the curved surface of
-a longitude/latitude data set. The two coordinate locations named must fall
-within the boundaries of the user's current geographic region.
-
-<H2>OPTIONS</H2>
-
-This program can be run either interactively or non-interactively.
-If the user types <B>d.geodesic</B> on the command line and runs it without other program
-parameters, the mouse will be activated; the user is asked to use
-the mouse to indicate the starting and ending points of each geodesic line
-to be drawn. The default line color (black) and text color (red)
-will be used.
-
-<P>
-Alternately, the user can specify the starting and ending coordinates
-of the geodesic, line color, and text color on the command line,
-and run the program non-interactively.
-
-<P>
-Once the user indicates the starting and ending coordinates
-of the geodesic, the line and its length (in miles) are displayed to
-the user's graphics monitor. If the text color is set to <em>none</em>,
-the great circle distance is not displayed.
-
-<H2>NOTES</H2>
-
-This program works only with GRASS locations using a longitude/latitude
-coordinate system.
-
-<H2>SEE ALSO</H2>
-
-<EM><A HREF="d.rhumbline.html">d.rhumbline</A></EM>
-
-<H2>AUTHOR</H2>
-
-Michael Shapiro, U.S. Army Construction Engineering Research Laboratory
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/display/d.graph/d.graph.html (from rev 32770, grass/trunk/display/d.graph/description.html)
===================================================================
--- grass/trunk/display/d.graph/d.graph.html (rev 0)
+++ grass/trunk/display/d.graph/d.graph.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,246 @@
+<H2>DESCRIPTION</H2>
+
+<EM>d.graph</EM>
+draws graphics that are described either from standard input (default),
+or within a file (if an <b>input</b> file name is identified on the
+command line). If graphics commands are entered from standard input,
+a <EM>CTRL-d</EM> is used to signal the end of input to <EM>d.graph</EM>.
+Coordinates are given either as a percentage of frame height and width
+(default) or in geographic coordinates (with the <B>-m</B> flag).
+<P>
+
+The program can be run interactively or non-interactively.
+The user can run the program completely non-interactively
+by specifying the name of a graphics file containing the
+<EM>d.graph</EM> graphics commands. If run non-interactively the
+<EM>d.graph</EM> command is saved to the display's dedraw history.
+
+The user can also elect to run the program partially interactively,
+by specifying any/all of the parameters <EM>except</EM>
+the graphics file <B>input=</B><EM>name</EM> parameter on the command line.
+In this case, <EM>d.graph</EM> will expect the user to input <EM>d.graph</EM>
+graphics commands from standard input (i.e., the keyboard) and
+will (silently) prompt the user for these graphics commands.
+
+<P>
+Alternately, the user can simply type <B>d.graph</B> on the command line,
+and be prompted for the values of all parameters<!-- (the user can still
+input graphics commands from either an input file or standard input
+using this form)-->. In this case, the user is presented with the standard
+GRASS GUI interface.
+
+<P>
+The default coordinate system used is 0-100 percent of the active frame
+in x and similarly 0-100 in y,
+regardless of the graphics monitor display frame size and aspect.
+The (0,0) location is the lower left corner of the active graphics
+monitor display frame. All values may be floating point.
+If the <B>-m</B> flag is given, geographic coordinates will be used instead.
+
+
+<H2>COMMANDS</H2>
+
+<P>
+The graphics language is simple, and uses the following commands:
+<BR>
+<DD>[
+<a href="#comment">#</a> |
+<a href="#move">move</a> |
+<a href="#draw">draw</a> |
+<a href="#polygon">polygon</a> |
+<a href="#polyline">polyline</a> |
+<a href="#color">color</a> |
+<a href="#text">text</a> |
+<a href="#size">size</a> |
+<a href="#symbol">symbol</a> |
+<a href="#rotation">rotation</a> |
+<a href="#icon">icon</a> |
+<a href="#width">width</a>
+]</DD>
+
+
+<DL>
+<a name="comment"></a>
+<DT><B>#</B> <EM>comment</EM>
+<DD>A line of comment which is ignored in the processing.
+
+<a name="move"></a>
+<DT><B>move</B> <EM>xpos ypos</EM>
+<DD>The current location is updated to <EM>xpos ypos</EM>.
+
+Unless the <B>-m</B> flag is used,
+values are stated as a percent of the active display frame's
+horizontal (<EM>xpos</EM>) and vertical (<EM>ypos</EM>) size,
+and may be floating point values. Values are between 0-100.
+<B>Note.</B> A space must separate <EM>xpos</EM> and <EM>ypos</EM>.
+
+<a name="draw"></a>
+<DT><B>draw</B> <EM>xpos ypos</EM>
+<DD>A line is drawn in the current color from the current location to the new
+location <EM>xpos ypos</EM>, which then becomes the current location.
+Unless the <B>-m</B> flag is used,
+values are stated as a percent of the active display frame's
+horizontal (<EM>xpos</EM>) and vertical (<EM>ypos</EM>) size,
+and may be floating point values. Values are between 0-100.
+<B>Note.</B> A space must separate <EM>xpos</EM> and <EM>ypos</EM>.
+
+<a name="polygon"></a>
+<DT><B>polygon</B>
+<BR> <EM> xpos ypos</EM>
+<BR> <EM> xpos ypos</EM>
+<BR> ...
+
+<DD>The coordinates appearing beneath the word <EM>polygon</EM>,
+one pair per line,
+circumscribe a polygon that is to be filled with the current color.
+
+<a name="polyline"></a>
+<DT><B>polyline</B>
+<BR> <EM> xpos ypos</EM>
+<BR> <EM> xpos ypos</EM>
+<BR> ...
+
+<DD>The coordinates appearing beneath the word <EM>polyline</EM>,
+one pair per line,
+circumscribe a polygon that is not to be filled with color.
+
+<a name="color"></a>
+<DT><B>color</B> <EM>color</EM>
+<DD>Sets the current color to that stated; subsequent graphics will be drawn
+in the stated color, until the current color is set to a different color.
+Options are <EM>red</EM>,
+<EM>orange</EM>,
+<EM>yellow</EM>,
+<EM>green</EM>,
+<EM>blue</EM>,
+<EM>indigo</EM>,
+<EM>violet</EM>,
+<EM>brown</EM>,
+<EM>magenta</EM>,
+<EM>gray</EM>,
+<EM>white</EM>,
+<EM>black</EM>,
+an R:G:B triplet (separated by colons),
+or the word "none" (draws in the default background color).
+
+<a name="text"></a>
+<DT><B>text</B> <EM>line-of-text</EM>
+<DD>The stated text is drawn at the current location using the current color,
+and the new current location is then positioned at the end of the text string.
+
+<a name="size"></a>
+<DT><B>size</B> <EM>xper yper</EM>
+<DD>Subsequent text will be drawn such that the text is
+<EM>xper</EM> percent of the graphics monitor display frame wide and
+<EM>yper</EM> percent of the frame high. By default, the text size is set to
+5 percent of the active frame's width and 5 percent of the frame's height.
+If only one value is given, then that value will be used for both x and y
+scaling.
+<BR>
+<B>Note.</B> A space must separate <EM>xper</EM> and <EM>yper</EM>.
+
+<a name="symbol"></a>
+<DT><B>symbol</B> <EM>type size xper yper [line_color [fill_color]]</EM>
+<DD>A symbol is drawn at the given size on the display monitor. The
+<EM>xper</EM> and <EM>yper</EM> options define the center of the icon and
+are given as a percentage of the display frame (<tt>0,0</tt> is lower left).
+The symbol can be any of those stored in <tt>$GISBASE/etc/symbol/</tt>
+(e.g. <i>basic/circle</i>) or stored in the user's mapset directory in the
+form <tt>$MAPSET/symbol/</tt><em>type/name</em>.
+The colors may be either a standard color name, an R:G:B triplet,
+or "none". If using an R:G:B triplet, each color value can range from 0-255.
+If not specified the default <EM>line_color</EM> is black and the default
+<EM>fill_color</EM> is grey.
+
+<a name="rotation"></a>
+<DT><B>rotation</B> <EM>angle</EM>
+<DD>Subsequent text and symbols will be drawn such that they are rotated
+<em>angle</em> degrees counter-clockwise from east.
+
+<a name="icon"></a>
+<DT><B>icon</B> <EM>type size x y</EM>
+<DD>Draws an icon of types <EM>o</EM>, <EM>x</EM>, or <EM>+</EM>
+with specified <EM>size</EM> (in %) at location <EM>x,y</EM>.
+Note: type <EM>o</EM> designates a square.
+<BR>
+
+<a name="width"></a>
+<DT><B>width</B> <EM>value</EM>
+<DD>Subsequent lines (including non-FreeType text) will be drawn with
+the given pixel thickness.
+<BR>The default value is 0.
+
+</DL>
+
+<H2>EXAMPLES</H2>
+
+For an example use of <EM>d.graph</EM>, examine the contents of the
+command file <EM><a href="grass_logo.txt">grass_logo.txt</a></EM>
+located in the <EM>d.graph</EM> source code directory. It will draw the
+CERL GRASS logo using the <EM>d.graph</EM> graphing commands stored in the file.
+Note that the coordinates in the <EM><a href="grass_logo.txt">grass_logo.txt</a></EM> file were
+taken directly off an image drawn by hand on graph paper.
+<!-- formerly names "grass.logo.sh" in GRASS 5 code. -->
+<P>
+A dynamic example can be found in the <em>d.polar</em> shell script.
+
+
+<h4>Draw a "star" symbol at a given map coordinate</h4>
+
+<div class="code"><pre>
+echo "symbol basic/star 20 2264417 5413182 black red" | d.graph -m
+</pre></div>
+
+
+<h4>Split the screen into quadrants:</h4>
+
+<div class="code"><pre>
+d.frame -s full_screen
+
+d.graph << EOF
+ color 80:80:120
+ polygon
+ 0 49.75
+ 0 50.25
+ 100 50.25
+ 100 49.75
+ polygon
+ 49.85 0
+ 50.15 0
+ 50.15 100
+ 49.85 100
+EOF
+</pre></div>
+
+
+<H2>NOTES</H2>
+
+<EM>d.graph</EM> remembers the last screen location (<EM>xpos ypos</EM>) to which
+the user moved, even after the user erases the display frame.
+If the user runs <EM>d.graph</EM> repeatedly, and wishes to start anew with
+the default (xpos ypos) screen location, the user should <EM>clear</EM> the
+display frame between runs of <EM>d.graph</EM>.
+
+<H2>LIMITATIONS</H2>
+
+There are no automated ways of generating graphic images. It is anticipated
+that GRASS user sites will write programs to convert output from a resident
+graphics editor into GRASS <EM>d.graph</EM> format.
+(e.g. EPS -> <em>d.graph</em>, perhaps with the help of a
+<a href="http://www.pstoedit.net/">pstoedit</a> plugin)
+
+<H2>SEE ALSO</H2>
+
+<EM><A HREF="d.font.html">d.font</A></EM><br>
+<EM><A HREF="d.frame.html">d.frame</A></EM><br>
+<EM><A HREF="d.labels.html">d.labels</A></EM><br>
+<!-- <EM><A HREF="d.mapgraph.html">d.mapgraph</A></EM><br> superseded by -m -->
+<EM><A HREF="d.polar.html">d.polar</A></EM><br>
+<EM><A HREF="d.text.html">d.text</A></EM><br>
+<EM><A HREF="d.where.html">d.where</A></EM><br>
+<!-- <EM><A HREF="grass.logo.sh.html">grass.logo.sh</A></EM><br> -->
+
+<H2>AUTHOR</H2>
+
+James Westervelt, U.S. Army Construction Engineering Research Laboratory
+<br><i>Last changed: $Date$</i>
Deleted: grass/trunk/display/d.graph/description.html
===================================================================
--- grass/trunk/display/d.graph/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/display/d.graph/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,246 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-<EM>d.graph</EM>
-draws graphics that are described either from standard input (default),
-or within a file (if an <b>input</b> file name is identified on the
-command line). If graphics commands are entered from standard input,
-a <EM>CTRL-d</EM> is used to signal the end of input to <EM>d.graph</EM>.
-Coordinates are given either as a percentage of frame height and width
-(default) or in geographic coordinates (with the <B>-m</B> flag).
-<P>
-
-The program can be run interactively or non-interactively.
-The user can run the program completely non-interactively
-by specifying the name of a graphics file containing the
-<EM>d.graph</EM> graphics commands. If run non-interactively the
-<EM>d.graph</EM> command is saved to the display's dedraw history.
-
-The user can also elect to run the program partially interactively,
-by specifying any/all of the parameters <EM>except</EM>
-the graphics file <B>input=</B><EM>name</EM> parameter on the command line.
-In this case, <EM>d.graph</EM> will expect the user to input <EM>d.graph</EM>
-graphics commands from standard input (i.e., the keyboard) and
-will (silently) prompt the user for these graphics commands.
-
-<P>
-Alternately, the user can simply type <B>d.graph</B> on the command line,
-and be prompted for the values of all parameters<!-- (the user can still
-input graphics commands from either an input file or standard input
-using this form)-->. In this case, the user is presented with the standard
-GRASS GUI interface.
-
-<P>
-The default coordinate system used is 0-100 percent of the active frame
-in x and similarly 0-100 in y,
-regardless of the graphics monitor display frame size and aspect.
-The (0,0) location is the lower left corner of the active graphics
-monitor display frame. All values may be floating point.
-If the <B>-m</B> flag is given, geographic coordinates will be used instead.
-
-
-<H2>COMMANDS</H2>
-
-<P>
-The graphics language is simple, and uses the following commands:
-<BR>
-<DD>[
-<a href="#comment">#</a> |
-<a href="#move">move</a> |
-<a href="#draw">draw</a> |
-<a href="#polygon">polygon</a> |
-<a href="#polyline">polyline</a> |
-<a href="#color">color</a> |
-<a href="#text">text</a> |
-<a href="#size">size</a> |
-<a href="#symbol">symbol</a> |
-<a href="#rotation">rotation</a> |
-<a href="#icon">icon</a> |
-<a href="#width">width</a>
-]</DD>
-
-
-<DL>
-<a name="comment"></a>
-<DT><B>#</B> <EM>comment</EM>
-<DD>A line of comment which is ignored in the processing.
-
-<a name="move"></a>
-<DT><B>move</B> <EM>xpos ypos</EM>
-<DD>The current location is updated to <EM>xpos ypos</EM>.
-
-Unless the <B>-m</B> flag is used,
-values are stated as a percent of the active display frame's
-horizontal (<EM>xpos</EM>) and vertical (<EM>ypos</EM>) size,
-and may be floating point values. Values are between 0-100.
-<B>Note.</B> A space must separate <EM>xpos</EM> and <EM>ypos</EM>.
-
-<a name="draw"></a>
-<DT><B>draw</B> <EM>xpos ypos</EM>
-<DD>A line is drawn in the current color from the current location to the new
-location <EM>xpos ypos</EM>, which then becomes the current location.
-Unless the <B>-m</B> flag is used,
-values are stated as a percent of the active display frame's
-horizontal (<EM>xpos</EM>) and vertical (<EM>ypos</EM>) size,
-and may be floating point values. Values are between 0-100.
-<B>Note.</B> A space must separate <EM>xpos</EM> and <EM>ypos</EM>.
-
-<a name="polygon"></a>
-<DT><B>polygon</B>
-<BR> <EM> xpos ypos</EM>
-<BR> <EM> xpos ypos</EM>
-<BR> ...
-
-<DD>The coordinates appearing beneath the word <EM>polygon</EM>,
-one pair per line,
-circumscribe a polygon that is to be filled with the current color.
-
-<a name="polyline"></a>
-<DT><B>polyline</B>
-<BR> <EM> xpos ypos</EM>
-<BR> <EM> xpos ypos</EM>
-<BR> ...
-
-<DD>The coordinates appearing beneath the word <EM>polyline</EM>,
-one pair per line,
-circumscribe a polygon that is not to be filled with color.
-
-<a name="color"></a>
-<DT><B>color</B> <EM>color</EM>
-<DD>Sets the current color to that stated; subsequent graphics will be drawn
-in the stated color, until the current color is set to a different color.
-Options are <EM>red</EM>,
-<EM>orange</EM>,
-<EM>yellow</EM>,
-<EM>green</EM>,
-<EM>blue</EM>,
-<EM>indigo</EM>,
-<EM>violet</EM>,
-<EM>brown</EM>,
-<EM>magenta</EM>,
-<EM>gray</EM>,
-<EM>white</EM>,
-<EM>black</EM>,
-an R:G:B triplet (separated by colons),
-or the word "none" (draws in the default background color).
-
-<a name="text"></a>
-<DT><B>text</B> <EM>line-of-text</EM>
-<DD>The stated text is drawn at the current location using the current color,
-and the new current location is then positioned at the end of the text string.
-
-<a name="size"></a>
-<DT><B>size</B> <EM>xper yper</EM>
-<DD>Subsequent text will be drawn such that the text is
-<EM>xper</EM> percent of the graphics monitor display frame wide and
-<EM>yper</EM> percent of the frame high. By default, the text size is set to
-5 percent of the active frame's width and 5 percent of the frame's height.
-If only one value is given, then that value will be used for both x and y
-scaling.
-<BR>
-<B>Note.</B> A space must separate <EM>xper</EM> and <EM>yper</EM>.
-
-<a name="symbol"></a>
-<DT><B>symbol</B> <EM>type size xper yper [line_color [fill_color]]</EM>
-<DD>A symbol is drawn at the given size on the display monitor. The
-<EM>xper</EM> and <EM>yper</EM> options define the center of the icon and
-are given as a percentage of the display frame (<tt>0,0</tt> is lower left).
-The symbol can be any of those stored in <tt>$GISBASE/etc/symbol/</tt>
-(e.g. <i>basic/circle</i>) or stored in the user's mapset directory in the
-form <tt>$MAPSET/symbol/</tt><em>type/name</em>.
-The colors may be either a standard color name, an R:G:B triplet,
-or "none". If using an R:G:B triplet, each color value can range from 0-255.
-If not specified the default <EM>line_color</EM> is black and the default
-<EM>fill_color</EM> is grey.
-
-<a name="rotation"></a>
-<DT><B>rotation</B> <EM>angle</EM>
-<DD>Subsequent text and symbols will be drawn such that they are rotated
-<em>angle</em> degrees counter-clockwise from east.
-
-<a name="icon"></a>
-<DT><B>icon</B> <EM>type size x y</EM>
-<DD>Draws an icon of types <EM>o</EM>, <EM>x</EM>, or <EM>+</EM>
-with specified <EM>size</EM> (in %) at location <EM>x,y</EM>.
-Note: type <EM>o</EM> designates a square.
-<BR>
-
-<a name="width"></a>
-<DT><B>width</B> <EM>value</EM>
-<DD>Subsequent lines (including non-FreeType text) will be drawn with
-the given pixel thickness.
-<BR>The default value is 0.
-
-</DL>
-
-<H2>EXAMPLES</H2>
-
-For an example use of <EM>d.graph</EM>, examine the contents of the
-command file <EM><a href="grass_logo.txt">grass_logo.txt</a></EM>
-located in the <EM>d.graph</EM> source code directory. It will draw the
-CERL GRASS logo using the <EM>d.graph</EM> graphing commands stored in the file.
-Note that the coordinates in the <EM><a href="grass_logo.txt">grass_logo.txt</a></EM> file were
-taken directly off an image drawn by hand on graph paper.
-<!-- formerly names "grass.logo.sh" in GRASS 5 code. -->
-<P>
-A dynamic example can be found in the <em>d.polar</em> shell script.
-
-
-<h4>Draw a "star" symbol at a given map coordinate</h4>
-
-<div class="code"><pre>
-echo "symbol basic/star 20 2264417 5413182 black red" | d.graph -m
-</pre></div>
-
-
-<h4>Split the screen into quadrants:</h4>
-
-<div class="code"><pre>
-d.frame -s full_screen
-
-d.graph << EOF
- color 80:80:120
- polygon
- 0 49.75
- 0 50.25
- 100 50.25
- 100 49.75
- polygon
- 49.85 0
- 50.15 0
- 50.15 100
- 49.85 100
-EOF
-</pre></div>
-
-
-<H2>NOTES</H2>
-
-<EM>d.graph</EM> remembers the last screen location (<EM>xpos ypos</EM>) to which
-the user moved, even after the user erases the display frame.
-If the user runs <EM>d.graph</EM> repeatedly, and wishes to start anew with
-the default (xpos ypos) screen location, the user should <EM>clear</EM> the
-display frame between runs of <EM>d.graph</EM>.
-
-<H2>LIMITATIONS</H2>
-
-There are no automated ways of generating graphic images. It is anticipated
-that GRASS user sites will write programs to convert output from a resident
-graphics editor into GRASS <EM>d.graph</EM> format.
-(e.g. EPS -> <em>d.graph</em>, perhaps with the help of a
-<a href="http://www.pstoedit.net/">pstoedit</a> plugin)
-
-<H2>SEE ALSO</H2>
-
-<EM><A HREF="d.font.html">d.font</A></EM><br>
-<EM><A HREF="d.frame.html">d.frame</A></EM><br>
-<EM><A HREF="d.labels.html">d.labels</A></EM><br>
-<!-- <EM><A HREF="d.mapgraph.html">d.mapgraph</A></EM><br> superseded by -m -->
-<EM><A HREF="d.polar.html">d.polar</A></EM><br>
-<EM><A HREF="d.text.html">d.text</A></EM><br>
-<EM><A HREF="d.where.html">d.where</A></EM><br>
-<!-- <EM><A HREF="grass.logo.sh.html">grass.logo.sh</A></EM><br> -->
-
-<H2>AUTHOR</H2>
-
-James Westervelt, U.S. Army Construction Engineering Research Laboratory
-<br><i>Last changed: $Date$</i>
Copied: grass/trunk/display/d.grid/d.grid.html (from rev 32770, grass/trunk/display/d.grid/description.html)
===================================================================
--- grass/trunk/display/d.grid/d.grid.html (rev 0)
+++ grass/trunk/display/d.grid/d.grid.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,87 @@
+<H2>DESCRIPTION</H2>
+
+<EM>d.grid</EM> overlays a grid of user-defined size and
+color in the active display frame on the graphics monitor.
+The grid can be created as a standard rectangular grid or
+a geographic grid. The grid will overlay, not overwrite,
+the contents of the active display frame.
+
+<P>
+
+<EM>d.grid</EM> can be run non-interactively or
+interactively. If the user specifies the grid
+<EM>size</EM> and (optionally) the grid <EM>color</EM> on
+the command line the program will run non-interactively; if
+no grid <EM>color</EM> is given the default will be used.
+Alternately, the user may simply type <B>d.grid</B> on the
+command line; in this case, the program will prompt the
+user for parameter values using the standard GRASS graphical
+user interface.
+
+
+<H2>NOTES</H2>
+
+<EM>d.grid</EM> will not erase grids already displayed in
+the active graphics display frame by previous invocations
+of <EM>d.grid</EM>; multiple invocations of <EM>d.grid</EM>
+will therefore result in the drawing of multiple grids
+inside the active graphics frame. (A command like
+<EM><A HREF="d.erase.html">d.erase</A></EM>, which erases the
+entire contents of the active display frame, must be run to
+erase previously drawn grids from the display frame.)
+
+<P>
+If the user provides a
+<EM>-g</EM> flag a geographic (projected) grid
+will be drawn. With the <EM>-g</EM> flag the <EM>size</EM>
+argument accepts both decimal degrees and colon separated
+ddd:mm:ss coordinates (eg. <tt>00:30:00</tt> for half of a degree).
+
+<p>
+A geographic grid cannot be drawn for a <EM>latitude/longitude</EM>
+or <EM>XY</EM> projection.
+<p>
+Colors may be standard named GRASS colors (red, green, aqua, etc.) or
+a numerical R:G:B triplet, where component values range from 0-255.<BR>
+<p>
+The grid drawing may be turned off by using the <em>-n</em> flag.<BR>
+The border drawing may be turned off by using the <em>-b</em> flag.<BR>
+The coordinate text may be turned off by using the <em>-t</em> flag.<BR>
+
+
+<H2>EXAMPLES</H2>
+To draw a red geographic grid with 30 minute grid spacing run
+either of the following:
+<PRE>
+ d.grid -g size=00:30:00 color=red
+</PRE>
+or
+<PRE>
+ d.grid -g size=0.5 color=255:0:0
+</PRE>
+To draw a blue standard rectangular grid at a 500 (meter) spacing run the following:
+<PRE>
+ d.grid size=500 color=blue
+</PRE>
+<BR>
+
+<H2>SEE ALSO</H2>
+
+<EM><A HREF="d.barscale.html">d.barscale</A></EM><br>
+<EM><A HREF="d.legend.html">d.legend</A></EM><br>
+<EM><A HREF="d.geodesic.html">d.geodesic</A></EM><br>
+<EM><A HREF="d.rhumbline.html">d.rhumbline</A></EM><br>
+<EM><A HREF="d.erase.html">d.erase</A></EM><br>
+<EM><A HREF="d.frame.html">d.frame</A></EM><br>
+<EM><A HREF="d.rast.html">d.rast</A></EM><br>
+
+
+
+<H2>AUTHORS</H2>
+
+James Westervelt, U.S. Army Construction Engineering Research Laboratory<BR>
+Geogrid support: Bob Covill<BR>
+Border support: Markus Neteler<BR>
+Text and RGB support: Hamish Bowman<BR>
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/display/d.grid/description.html
===================================================================
--- grass/trunk/display/d.grid/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/display/d.grid/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,87 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-<EM>d.grid</EM> overlays a grid of user-defined size and
-color in the active display frame on the graphics monitor.
-The grid can be created as a standard rectangular grid or
-a geographic grid. The grid will overlay, not overwrite,
-the contents of the active display frame.
-
-<P>
-
-<EM>d.grid</EM> can be run non-interactively or
-interactively. If the user specifies the grid
-<EM>size</EM> and (optionally) the grid <EM>color</EM> on
-the command line the program will run non-interactively; if
-no grid <EM>color</EM> is given the default will be used.
-Alternately, the user may simply type <B>d.grid</B> on the
-command line; in this case, the program will prompt the
-user for parameter values using the standard GRASS graphical
-user interface.
-
-
-<H2>NOTES</H2>
-
-<EM>d.grid</EM> will not erase grids already displayed in
-the active graphics display frame by previous invocations
-of <EM>d.grid</EM>; multiple invocations of <EM>d.grid</EM>
-will therefore result in the drawing of multiple grids
-inside the active graphics frame. (A command like
-<EM><A HREF="d.erase.html">d.erase</A></EM>, which erases the
-entire contents of the active display frame, must be run to
-erase previously drawn grids from the display frame.)
-
-<P>
-If the user provides a
-<EM>-g</EM> flag a geographic (projected) grid
-will be drawn. With the <EM>-g</EM> flag the <EM>size</EM>
-argument accepts both decimal degrees and colon separated
-ddd:mm:ss coordinates (eg. <tt>00:30:00</tt> for half of a degree).
-
-<p>
-A geographic grid cannot be drawn for a <EM>latitude/longitude</EM>
-or <EM>XY</EM> projection.
-<p>
-Colors may be standard named GRASS colors (red, green, aqua, etc.) or
-a numerical R:G:B triplet, where component values range from 0-255.<BR>
-<p>
-The grid drawing may be turned off by using the <em>-n</em> flag.<BR>
-The border drawing may be turned off by using the <em>-b</em> flag.<BR>
-The coordinate text may be turned off by using the <em>-t</em> flag.<BR>
-
-
-<H2>EXAMPLES</H2>
-To draw a red geographic grid with 30 minute grid spacing run
-either of the following:
-<PRE>
- d.grid -g size=00:30:00 color=red
-</PRE>
-or
-<PRE>
- d.grid -g size=0.5 color=255:0:0
-</PRE>
-To draw a blue standard rectangular grid at a 500 (meter) spacing run the following:
-<PRE>
- d.grid size=500 color=blue
-</PRE>
-<BR>
-
-<H2>SEE ALSO</H2>
-
-<EM><A HREF="d.barscale.html">d.barscale</A></EM><br>
-<EM><A HREF="d.legend.html">d.legend</A></EM><br>
-<EM><A HREF="d.geodesic.html">d.geodesic</A></EM><br>
-<EM><A HREF="d.rhumbline.html">d.rhumbline</A></EM><br>
-<EM><A HREF="d.erase.html">d.erase</A></EM><br>
-<EM><A HREF="d.frame.html">d.frame</A></EM><br>
-<EM><A HREF="d.rast.html">d.rast</A></EM><br>
-
-
-
-<H2>AUTHORS</H2>
-
-James Westervelt, U.S. Army Construction Engineering Research Laboratory<BR>
-Geogrid support: Bob Covill<BR>
-Border support: Markus Neteler<BR>
-Text and RGB support: Hamish Bowman<BR>
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/display/d.his/d.his.html (from rev 32770, grass/trunk/display/d.his/description.html)
===================================================================
--- grass/trunk/display/d.his/d.his.html (rev 0)
+++ grass/trunk/display/d.his/d.his.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,145 @@
+<H2>DESCRIPTION</H2>
+
+<EM>his</EM> stands for hue, intensity, and saturation.
+This program produces a raster map layer providing a
+visually pleasing combination of hue, intensity, and
+saturation values from two or three user-specified raster
+map layers.
+
+<P>
+
+The human brain automatically interprets the vast amount of
+visual information available according to basic rules.
+Color, or <EM>hue</EM>, is used to categorize objects.
+Shading, or <EM>intensity</EM>, is interpreted as
+three-dimensional texturing. Finally, the degree of
+haziness, or <EM>saturation</EM>, is associated with
+distance or depth. This program allows data from up to
+three raster map layers to be combined into an image which
+retains the original information in terms of <EM>hue</EM>,
+<EM>intensity</EM>, and <EM>saturation</EM>.
+
+<H2>OPTIONS</H2>
+
+This program can be run non-interactively or
+interactively. It will run non-interactively if the user
+specifies on the command line the name of a map containing
+hue values (<B>h_map</B>), and the name(s) of map(s)
+containing intensity values (<B>i_map</B>) and/or
+saturation values (<B>s_map</B>). The resulting image will
+be displayed in the active display frame on the graphics
+monitor.
+
+<P>
+
+Alternately, the user can run the program interactively by
+typing <B>d.his</B> without naming parameter values on the
+command line. In this case, the program will prompt the
+user for parameter values using the standard GRASS
+GUI interface.
+
+<P>
+
+While any raster map layer can be used to represent the hue
+information, map layers with a few very distinct colors
+work best. Only raster map layers representing
+continuously varying data like elevation, aspect, weights,
+intensities, or amounts can suitably be used to provide
+intensity and saturation information.
+
+<P>
+
+For example, a visually pleasing image can be
+made by using a watershed map for the <EM>hue</EM> factor,
+an aspect map for the <EM>intensity</EM> factor, and an
+elevation map for <EM>saturation</EM>. (The user may wish
+to leave out the elevation information for a first try.)
+Ideally, the resulting image should resemble the view from
+an aircraft looking at a terrain on a sunny day with a bit
+of haze in the valleys.
+
+<P>
+The <b>brighten</b> option does not truly represent a percentage,
+but calling it that makes the option easy to understand, and it
+sounds better than <i>Normalized Scaling Factor</i>.
+
+
+<H2>THE PROCESS</H2>
+
+Each map cell is processed individually. First, the working
+color is set to the color of the corresponding cell in the
+map layer chosen to represent <EM>HUE</EM>. Second, this
+color is multiplied by the <EM>red</EM> intensity of that
+cell in the <EM>INTENSITY</EM> map layer. This map layer
+should have an appropriate gray-scale color table
+associated with it. You can ensure this by using the color
+manipulation capabilities of
+<EM><A HREF="d.colors.html">d.colors</A></EM> or
+<EM><A HREF="r.colors.html">r.colors</A></EM>.
+
+Finally, the color is made somewhat gray-based on the
+<EM>red</EM> intensity of that cell in the
+<EM>SATURATION</EM> map layer. Again, this map layer
+should have a gray-scale color table associated with it.
+
+<H2>NOTES</H2>
+
+The name is misleading. The actual conversion used is
+
+<PRE>
+ <U>H</U>.i.s + <U>G</U>.(1-s)
+
+where
+
+ <U>H</U> is the R,G,B color from the hue map
+ i is the red value from the intensity map
+ s is the red value from the saturation map
+ <U>G</U> is 50% gray (R = G = B = 0.5)
+
+</PRE>
+
+<P>
+
+Either (but not both) of the intensity or the saturation
+map layers may be omitted. This means that it is possible
+to produce output images that represent combinations of
+<EM>his, hi,</EM> or <EM>hs</EM>.
+
+<P>
+Users wishing to store the result in new raster map layers
+instead of displaying it on the monitor should use the
+program <EM><A HREF="r.his.html">r.his</A></EM>.
+
+
+<H2>EXAMPLE</H2>
+<h4>Spearfish dataset</h4>
+
+<div class="code"><pre>
+ g.region rast=elevation.dem
+ r.shaded.relief map=elevation.dem shad=elev.shad_relf
+ d.mon x1
+ d.his h=elevation.dem i=elev.shad_relf brighten=50
+</pre></div>
+<BR>
+
+<H2>SEE ALSO</H2>
+
+<EM>
+<A HREF="d.colors.html">d.colors</A>,
+<A HREF="d.colortable.html">d.colortable</A>,
+<A HREF="d.frame.html">d.frame</A>,
+<A HREF="d.rgb.html">d.rgb</A>,
+<A HREF="r.colors.html">r.colors</A>,
+<A HREF="r.his.html">r.his</A>,
+<A HREF="i.his.rgb.html">i.his.rgb</A>,
+<A HREF="i.rgb.his.html">i.rgb.his</A>,
+<A HREF="hsv.rgb.sh.html">hsv.rgb.sh</A>,
+<A HREF="rgb.hsv.sh.html">rgb.hsv.sh</A>
+</EM>
+
+<H2>AUTHOR</H2>
+
+James Westervelt, U.S. Army Construction Engineering Research Laboratory
+
+<p>
+<i>Last changed: $Date$</i>
Deleted: grass/trunk/display/d.his/description.html
===================================================================
--- grass/trunk/display/d.his/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/display/d.his/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,145 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-<EM>his</EM> stands for hue, intensity, and saturation.
-This program produces a raster map layer providing a
-visually pleasing combination of hue, intensity, and
-saturation values from two or three user-specified raster
-map layers.
-
-<P>
-
-The human brain automatically interprets the vast amount of
-visual information available according to basic rules.
-Color, or <EM>hue</EM>, is used to categorize objects.
-Shading, or <EM>intensity</EM>, is interpreted as
-three-dimensional texturing. Finally, the degree of
-haziness, or <EM>saturation</EM>, is associated with
-distance or depth. This program allows data from up to
-three raster map layers to be combined into an image which
-retains the original information in terms of <EM>hue</EM>,
-<EM>intensity</EM>, and <EM>saturation</EM>.
-
-<H2>OPTIONS</H2>
-
-This program can be run non-interactively or
-interactively. It will run non-interactively if the user
-specifies on the command line the name of a map containing
-hue values (<B>h_map</B>), and the name(s) of map(s)
-containing intensity values (<B>i_map</B>) and/or
-saturation values (<B>s_map</B>). The resulting image will
-be displayed in the active display frame on the graphics
-monitor.
-
-<P>
-
-Alternately, the user can run the program interactively by
-typing <B>d.his</B> without naming parameter values on the
-command line. In this case, the program will prompt the
-user for parameter values using the standard GRASS
-GUI interface.
-
-<P>
-
-While any raster map layer can be used to represent the hue
-information, map layers with a few very distinct colors
-work best. Only raster map layers representing
-continuously varying data like elevation, aspect, weights,
-intensities, or amounts can suitably be used to provide
-intensity and saturation information.
-
-<P>
-
-For example, a visually pleasing image can be
-made by using a watershed map for the <EM>hue</EM> factor,
-an aspect map for the <EM>intensity</EM> factor, and an
-elevation map for <EM>saturation</EM>. (The user may wish
-to leave out the elevation information for a first try.)
-Ideally, the resulting image should resemble the view from
-an aircraft looking at a terrain on a sunny day with a bit
-of haze in the valleys.
-
-<P>
-The <b>brighten</b> option does not truly represent a percentage,
-but calling it that makes the option easy to understand, and it
-sounds better than <i>Normalized Scaling Factor</i>.
-
-
-<H2>THE PROCESS</H2>
-
-Each map cell is processed individually. First, the working
-color is set to the color of the corresponding cell in the
-map layer chosen to represent <EM>HUE</EM>. Second, this
-color is multiplied by the <EM>red</EM> intensity of that
-cell in the <EM>INTENSITY</EM> map layer. This map layer
-should have an appropriate gray-scale color table
-associated with it. You can ensure this by using the color
-manipulation capabilities of
-<EM><A HREF="d.colors.html">d.colors</A></EM> or
-<EM><A HREF="r.colors.html">r.colors</A></EM>.
-
-Finally, the color is made somewhat gray-based on the
-<EM>red</EM> intensity of that cell in the
-<EM>SATURATION</EM> map layer. Again, this map layer
-should have a gray-scale color table associated with it.
-
-<H2>NOTES</H2>
-
-The name is misleading. The actual conversion used is
-
-<PRE>
- <U>H</U>.i.s + <U>G</U>.(1-s)
-
-where
-
- <U>H</U> is the R,G,B color from the hue map
- i is the red value from the intensity map
- s is the red value from the saturation map
- <U>G</U> is 50% gray (R = G = B = 0.5)
-
-</PRE>
-
-<P>
-
-Either (but not both) of the intensity or the saturation
-map layers may be omitted. This means that it is possible
-to produce output images that represent combinations of
-<EM>his, hi,</EM> or <EM>hs</EM>.
-
-<P>
-Users wishing to store the result in new raster map layers
-instead of displaying it on the monitor should use the
-program <EM><A HREF="r.his.html">r.his</A></EM>.
-
-
-<H2>EXAMPLE</H2>
-<h4>Spearfish dataset</h4>
-
-<div class="code"><pre>
- g.region rast=elevation.dem
- r.shaded.relief map=elevation.dem shad=elev.shad_relf
- d.mon x1
- d.his h=elevation.dem i=elev.shad_relf brighten=50
-</pre></div>
-<BR>
-
-<H2>SEE ALSO</H2>
-
-<EM>
-<A HREF="d.colors.html">d.colors</A>,
-<A HREF="d.colortable.html">d.colortable</A>,
-<A HREF="d.frame.html">d.frame</A>,
-<A HREF="d.rgb.html">d.rgb</A>,
-<A HREF="r.colors.html">r.colors</A>,
-<A HREF="r.his.html">r.his</A>,
-<A HREF="i.his.rgb.html">i.his.rgb</A>,
-<A HREF="i.rgb.his.html">i.rgb.his</A>,
-<A HREF="hsv.rgb.sh.html">hsv.rgb.sh</A>,
-<A HREF="rgb.hsv.sh.html">rgb.hsv.sh</A>
-</EM>
-
-<H2>AUTHOR</H2>
-
-James Westervelt, U.S. Army Construction Engineering Research Laboratory
-
-<p>
-<i>Last changed: $Date$</i>
Copied: grass/trunk/display/d.histogram/d.histogram.html (from rev 32770, grass/trunk/display/d.histogram/description.html)
===================================================================
--- grass/trunk/display/d.histogram/d.histogram.html (rev 0)
+++ grass/trunk/display/d.histogram/d.histogram.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,40 @@
+<H2>DESCRIPTION</H2>
+
+<EM>d.histogram</EM> displays the category-value distribution for a
+user-specified raster map layer, in the form of a bar chart or a pie chart.
+The display will be displayed in the active display frame on the graphics
+monitor, using the colors in the raster map layer's color table. The
+program determines the raster map's category value distribution by counting
+cells.
+
+<H2>NOTES</H2>
+
+<EM>d.histogram</EM> respects the current geographic region settings
+and the current MASK (if one exists).
+
+<P>
+<EM>d.histogram</EM> uses the colors in the map's color look-up table
+(i.e., the map's <EM>colr</EM> or <EM>colr2</EM> file).
+
+<H2>SEE ALSO</H2>
+
+<em>
+<a href="d.colors.html">d.colors</a>,
+<a href="d.colortable.html">d.colortable</a>,
+<a href="d.frame.html">d.frame</a>,
+<a href="d.graph.html">d.graph</a>,
+<a href="d.linegraph.html">d.linegraph</a>,
+<a href="d.polar.html">d.polar</a>,
+<a href="g.region.html">g.region</a>,
+<a href="r.stats.html">r.stats</a>
+</em>
+
+<H2>AUTHOR</H2>
+
+Dave Johnson
+<BR> DBA Systems, Inc.
+<BR> 10560 Arrowhead Drive
+<BR> Fairfax, Virginia 22030
+
+<p>
+<i>Last changed: $Date$</i>
Deleted: grass/trunk/display/d.histogram/description.html
===================================================================
--- grass/trunk/display/d.histogram/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/display/d.histogram/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,40 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-<EM>d.histogram</EM> displays the category-value distribution for a
-user-specified raster map layer, in the form of a bar chart or a pie chart.
-The display will be displayed in the active display frame on the graphics
-monitor, using the colors in the raster map layer's color table. The
-program determines the raster map's category value distribution by counting
-cells.
-
-<H2>NOTES</H2>
-
-<EM>d.histogram</EM> respects the current geographic region settings
-and the current MASK (if one exists).
-
-<P>
-<EM>d.histogram</EM> uses the colors in the map's color look-up table
-(i.e., the map's <EM>colr</EM> or <EM>colr2</EM> file).
-
-<H2>SEE ALSO</H2>
-
-<em>
-<a href="d.colors.html">d.colors</a>,
-<a href="d.colortable.html">d.colortable</a>,
-<a href="d.frame.html">d.frame</a>,
-<a href="d.graph.html">d.graph</a>,
-<a href="d.linegraph.html">d.linegraph</a>,
-<a href="d.polar.html">d.polar</a>,
-<a href="g.region.html">g.region</a>,
-<a href="r.stats.html">r.stats</a>
-</em>
-
-<H2>AUTHOR</H2>
-
-Dave Johnson
-<BR> DBA Systems, Inc.
-<BR> 10560 Arrowhead Drive
-<BR> Fairfax, Virginia 22030
-
-<p>
-<i>Last changed: $Date$</i>
Copied: grass/trunk/display/d.info/d.info.html (from rev 32770, grass/trunk/display/d.info/description.html)
===================================================================
--- grass/trunk/display/d.info/d.info.html (rev 0)
+++ grass/trunk/display/d.info/d.info.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,26 @@
+<h2>DESCRIPTION</h2>
+
+<em>d.info</em> displays information about the active display monitor.
+
+<H2>NOTES</H2>
+
+Units are screen pixels (except for <em>-g</em> flag where map units
+are used).<BR>
+Where two numbers are given the format is: width, height.<BR>
+Where four numbers are given the format is: left, right, top, bottom.
+<BR><BR>
+Note: GRASS display pixel coordinates are measured from the top left.
+<P>
+<BR>
+
+<h2>SEE ALSO</h2>
+
+<em><a HREF="d.frame.html">d.frame</a></em><br>
+<em><a HREF="d.vect.html">d.vect</a></em><br>
+<em><a HREF="d.rast.html">d.rast</a></em><br>
+
+<h2>AUTHOR</h2>
+
+Glynn Clements
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/display/d.info/description.html
===================================================================
--- grass/trunk/display/d.info/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/display/d.info/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,26 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>d.info</em> displays information about the active display monitor.
-
-<H2>NOTES</H2>
-
-Units are screen pixels (except for <em>-g</em> flag where map units
-are used).<BR>
-Where two numbers are given the format is: width, height.<BR>
-Where four numbers are given the format is: left, right, top, bottom.
-<BR><BR>
-Note: GRASS display pixel coordinates are measured from the top left.
-<P>
-<BR>
-
-<h2>SEE ALSO</h2>
-
-<em><a HREF="d.frame.html">d.frame</a></em><br>
-<em><a HREF="d.vect.html">d.vect</a></em><br>
-<em><a HREF="d.rast.html">d.rast</a></em><br>
-
-<h2>AUTHOR</h2>
-
-Glynn Clements
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/display/d.labels/d.labels.html (from rev 32770, grass/trunk/display/d.labels/description.html)
===================================================================
--- grass/trunk/display/d.labels/d.labels.html (rev 0)
+++ grass/trunk/display/d.labels/d.labels.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,43 @@
+<H2>DESCRIPTION</H2>
+
+<EM>d.labels</EM> displays a <EM>paint</EM> label file in the
+active display frame on the graphics monitor. Each label has components
+which determine the text, the location of the text on the image, its
+size, and the background for the text. This file can be generated with
+the <EM><A HREF="v.label.html">v.label</A></EM> program or simply created
+by the user as an ASCII file (using a text editor) and placed in the
+appropriate directory under the user's current mapset and location
+(i.e. <tt>$MAPSET/paint/labels/</tt>).
+
+<H2>NOTES</H2>
+
+Some of the information stored in the label file is unused by
+<EM>d.labels</EM>.
+<!-- The unused information found in a label file is printed to standard
+output. -->
+This extra information is used by such programs as
+<EM><A HREF="ps.map.html">ps.map</A></EM>.
+
+<P>
+This module was formerly known as <em>d.paint.labels</em>.
+The the old version of <em>d.labels</em> from GRASS 5, which provided
+interactive placement and modification of paint labels, still needs to
+have its functionality merged into this module.
+
+<H2>SEE ALSO</H2>
+
+<EM><A HREF="d.font.html">d.font</A></EM><br>
+<EM><A HREF="d.text.html">d.text</A></EM><br>
+<EM><A HREF="d.title.html">d.title</A></EM><br>
+<EM><A HREF="ps.map.html">ps.map</A></EM><br>
+<EM><A HREF="v.label.html">v.label</A></EM>
+<BR>
+
+<H2>AUTHOR</H2>
+
+James Westervelt,
+U.S. Army Construction Engineering
+Research Laboratory
+
+<p>
+<i>Last changed: $Date$</i>
Deleted: grass/trunk/display/d.labels/description.html
===================================================================
--- grass/trunk/display/d.labels/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/display/d.labels/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,43 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-<EM>d.labels</EM> displays a <EM>paint</EM> label file in the
-active display frame on the graphics monitor. Each label has components
-which determine the text, the location of the text on the image, its
-size, and the background for the text. This file can be generated with
-the <EM><A HREF="v.label.html">v.label</A></EM> program or simply created
-by the user as an ASCII file (using a text editor) and placed in the
-appropriate directory under the user's current mapset and location
-(i.e. <tt>$MAPSET/paint/labels/</tt>).
-
-<H2>NOTES</H2>
-
-Some of the information stored in the label file is unused by
-<EM>d.labels</EM>.
-<!-- The unused information found in a label file is printed to standard
-output. -->
-This extra information is used by such programs as
-<EM><A HREF="ps.map.html">ps.map</A></EM>.
-
-<P>
-This module was formerly known as <em>d.paint.labels</em>.
-The the old version of <em>d.labels</em> from GRASS 5, which provided
-interactive placement and modification of paint labels, still needs to
-have its functionality merged into this module.
-
-<H2>SEE ALSO</H2>
-
-<EM><A HREF="d.font.html">d.font</A></EM><br>
-<EM><A HREF="d.text.html">d.text</A></EM><br>
-<EM><A HREF="d.title.html">d.title</A></EM><br>
-<EM><A HREF="ps.map.html">ps.map</A></EM><br>
-<EM><A HREF="v.label.html">v.label</A></EM>
-<BR>
-
-<H2>AUTHOR</H2>
-
-James Westervelt,
-U.S. Army Construction Engineering
-Research Laboratory
-
-<p>
-<i>Last changed: $Date$</i>
Copied: grass/trunk/display/d.legend/d.legend.html (from rev 32770, grass/trunk/display/d.legend/description.html)
===================================================================
--- grass/trunk/display/d.legend/d.legend.html (rev 0)
+++ grass/trunk/display/d.legend/d.legend.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,117 @@
+<H2>DESCRIPTION</H2>
+
+<EM>d.legend</EM> displays a legend for a user-specified
+raster map layer in the active frame on the graphics
+monitor.
+<P>
+
+The user can run <EM>d.legend</EM> either non-interactively
+or interactively. If the user specifies the name of a
+raster <B>map</B> layer on the command line, the program
+will run non-interactively. Default legend text
+<B>color</B> and position will be used unless
+the user specifies other values on the command line.
+
+<P>
+
+Alternately, the user can simply type <B>d.legend</B> on the command line;
+in this case, the program will prompt the user for parameter values
+using the standard GRASS GUI interface.
+
+<H2>NOTES</H2>
+
+The legend's default size is based on the dimensions of the
+active frame, specifically its height. <EM>d.legend</EM> will only
+obscure those portions of the active frame that directly underlie the legend.
+<p>
+When using the mouse or <B>at</B> to size & place the legend, a user may
+create a horizontal legend by making the box wider than it is tall.
+<p>
+Raster maps based on floating point values will display smoothed, from greatest
+to smallest value, while categorial raster maps will display in order, from
+top to bottom. Horizontal legends will always be smoothed. If the box is defined
+with inverted y-values or an inverted <B>range</B>, the legend will automatically
+flip. If this is not the desired result, the <B>-f</B> flag may be used to flip
+it back.
+<p>
+If the user attempts to display a very long legend in a relatively short
+display frame, the legend may appear in unreadably small text, or even revert
+to a smooth gradient legend. Use the <B>lines</B>, <B>thin</B>, <B>use</B>, <B>range</B>,
+and/or <B>-n</B> options to reduce the number of categories to be displayed,
+or the <B>-s</B> flag to force a smooth gradient legend.
+<p>
+The <B>lines</B> option will display the first number of categories, as defined
+by <EM>value</EM>, contained in the raster map. When used with the <B>-n</B> flag,
+it takes on a new meaning: "up to category #". When used with both
+<B>thin</B> and the <B>-n</B> flag, its meaning becomes more obscure. When
+using <B>lines</B>, auto-scaled text similar to "4 of 16 categories" will be placed at
+the bottom of the legend.
+<p>
+The <B>thin</B> option sets the thinning factor. For raster maps with a 0th
+category, <B>thin=</B><EM>10</EM> gives cats [0,10,20,...]. For raster maps
+starting at category 1, <B>thin=</B><EM>10</EM> gives cats [1,11,21,...].
+<p>
+The <B>use</B> option lets the user create a legend made up of arbitrary category
+values. e.g. <B>use=</B><EM>1000,100,10,0,-10,-100,-1000</EM>
+<p>
+The <B>range</B> option lets the user define the minimum and maximum categories
+to be used in the legend. It may also be used to define the limits of a smooth
+gradient legend created from a raster containing floating point values. Note
+the color scale will remain faithful to the category values as defined with
+<EM><A HREF="r.colors.html">r.colors</A></EM>, and the <B>range</B> may be
+extended to the limits defined by the <EM><A HREF="r.colors.html">r.colors</A></EM>
+color map.
+<p>
+The flag <B>-n</B> is useful for categorial maps, as it suppresses the
+drawing of non-existing categories (otherwise the full range is shown).
+<p>
+Vertical legends produced with <EM>d.legend</EM> will place text labels to the
+right of the legend box, horizontal legends will place text below. This text
+will be auto-scaled to fit within the frame, reducing the size of the legend
+if necessary. Legends positioned with the mouse or with the <B>at</B> option
+will not auto-scale text, in order to provide more control to the user.
+Smaller text may be obtained in this case by reducing the
+height of the box. The <B>-c</B> and <B>-v</B> flags may be used to suppress the
+display of category numbers and labels respectively, or used together to
+suppress all text of categorial raster maps.
+<p>
+The text produced from floating-point raster maps will automatically create
+output with a meaningful number of significant digits. For very small values,
+numbers will be expressed in scientific notation, e.g. "1.7e-9".
+<p>
+Legends placed with the mouse are not saved to the display window's history
+for automatic redraw. By setting the Debug level to 1 (see
+<EM><A HREF="g.gisenv.html">g.gisenv</A></EM>) the corresponding <b>at</b>
+setting can be determined.
+<p>
+Note that old scripts which relied on setting <B>lines</B> greater than the
+number of categories to scale the legend may no longer produce the desired
+output, although the auto-scaling should still produce something that looks
+good in this case.
+
+
+<H2>SEE ALSO</H2>
+
+<EM><A HREF="d.barscale.html">d.barscale</A></EM><BR>
+<EM><A HREF="d.colors.html">d.colors</A></EM><BR>
+<EM><A HREF="d.colortable.html">d.colortable</A></EM><BR>
+<EM><A HREF="d.erase.html">d.erase</A></EM><BR>
+<EM><A HREF="d.font.html">d.font</A></EM><BR>
+<EM><A HREF="d.grid.html">d.grid</A></EM><BR>
+<EM><A HREF="d.rast.html">d.rast</A></EM><BR>
+<!-- <EM><A HREF="d.rast.labels.html">d.rast.labels</A></EM><BR> -->
+<EM><A HREF="d.rast.leg.html">d.rast.leg</A></EM><BR>
+<EM><A HREF="d.text.html">d.text</A></EM><BR>
+<EM><A HREF="d.vect.thematic.html">d.vect.thematic</A></EM><BR>
+<EM><A HREF="d.what.rast.html">d.what.rast</A></EM><BR>
+<EM><A HREF="g.gisenv.html">g.gisenv</A></EM><BR>
+<EM><A HREF="r.reclass.html">r.reclass</A></EM><BR>
+
+
+<H2>AUTHORS</H2>
+Bill Brown, U.S. Army Construction Engineering Research Laboratories
+<BR>Late 2002: Rewrite of much of the code. Hamish Bowman,
+ Otago University, New Zealand
+<BR>Additional improvements from various authors
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/display/d.legend/description.html
===================================================================
--- grass/trunk/display/d.legend/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/display/d.legend/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,117 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-<EM>d.legend</EM> displays a legend for a user-specified
-raster map layer in the active frame on the graphics
-monitor.
-<P>
-
-The user can run <EM>d.legend</EM> either non-interactively
-or interactively. If the user specifies the name of a
-raster <B>map</B> layer on the command line, the program
-will run non-interactively. Default legend text
-<B>color</B> and position will be used unless
-the user specifies other values on the command line.
-
-<P>
-
-Alternately, the user can simply type <B>d.legend</B> on the command line;
-in this case, the program will prompt the user for parameter values
-using the standard GRASS GUI interface.
-
-<H2>NOTES</H2>
-
-The legend's default size is based on the dimensions of the
-active frame, specifically its height. <EM>d.legend</EM> will only
-obscure those portions of the active frame that directly underlie the legend.
-<p>
-When using the mouse or <B>at</B> to size & place the legend, a user may
-create a horizontal legend by making the box wider than it is tall.
-<p>
-Raster maps based on floating point values will display smoothed, from greatest
-to smallest value, while categorial raster maps will display in order, from
-top to bottom. Horizontal legends will always be smoothed. If the box is defined
-with inverted y-values or an inverted <B>range</B>, the legend will automatically
-flip. If this is not the desired result, the <B>-f</B> flag may be used to flip
-it back.
-<p>
-If the user attempts to display a very long legend in a relatively short
-display frame, the legend may appear in unreadably small text, or even revert
-to a smooth gradient legend. Use the <B>lines</B>, <B>thin</B>, <B>use</B>, <B>range</B>,
-and/or <B>-n</B> options to reduce the number of categories to be displayed,
-or the <B>-s</B> flag to force a smooth gradient legend.
-<p>
-The <B>lines</B> option will display the first number of categories, as defined
-by <EM>value</EM>, contained in the raster map. When used with the <B>-n</B> flag,
-it takes on a new meaning: "up to category #". When used with both
-<B>thin</B> and the <B>-n</B> flag, its meaning becomes more obscure. When
-using <B>lines</B>, auto-scaled text similar to "4 of 16 categories" will be placed at
-the bottom of the legend.
-<p>
-The <B>thin</B> option sets the thinning factor. For raster maps with a 0th
-category, <B>thin=</B><EM>10</EM> gives cats [0,10,20,...]. For raster maps
-starting at category 1, <B>thin=</B><EM>10</EM> gives cats [1,11,21,...].
-<p>
-The <B>use</B> option lets the user create a legend made up of arbitrary category
-values. e.g. <B>use=</B><EM>1000,100,10,0,-10,-100,-1000</EM>
-<p>
-The <B>range</B> option lets the user define the minimum and maximum categories
-to be used in the legend. It may also be used to define the limits of a smooth
-gradient legend created from a raster containing floating point values. Note
-the color scale will remain faithful to the category values as defined with
-<EM><A HREF="r.colors.html">r.colors</A></EM>, and the <B>range</B> may be
-extended to the limits defined by the <EM><A HREF="r.colors.html">r.colors</A></EM>
-color map.
-<p>
-The flag <B>-n</B> is useful for categorial maps, as it suppresses the
-drawing of non-existing categories (otherwise the full range is shown).
-<p>
-Vertical legends produced with <EM>d.legend</EM> will place text labels to the
-right of the legend box, horizontal legends will place text below. This text
-will be auto-scaled to fit within the frame, reducing the size of the legend
-if necessary. Legends positioned with the mouse or with the <B>at</B> option
-will not auto-scale text, in order to provide more control to the user.
-Smaller text may be obtained in this case by reducing the
-height of the box. The <B>-c</B> and <B>-v</B> flags may be used to suppress the
-display of category numbers and labels respectively, or used together to
-suppress all text of categorial raster maps.
-<p>
-The text produced from floating-point raster maps will automatically create
-output with a meaningful number of significant digits. For very small values,
-numbers will be expressed in scientific notation, e.g. "1.7e-9".
-<p>
-Legends placed with the mouse are not saved to the display window's history
-for automatic redraw. By setting the Debug level to 1 (see
-<EM><A HREF="g.gisenv.html">g.gisenv</A></EM>) the corresponding <b>at</b>
-setting can be determined.
-<p>
-Note that old scripts which relied on setting <B>lines</B> greater than the
-number of categories to scale the legend may no longer produce the desired
-output, although the auto-scaling should still produce something that looks
-good in this case.
-
-
-<H2>SEE ALSO</H2>
-
-<EM><A HREF="d.barscale.html">d.barscale</A></EM><BR>
-<EM><A HREF="d.colors.html">d.colors</A></EM><BR>
-<EM><A HREF="d.colortable.html">d.colortable</A></EM><BR>
-<EM><A HREF="d.erase.html">d.erase</A></EM><BR>
-<EM><A HREF="d.font.html">d.font</A></EM><BR>
-<EM><A HREF="d.grid.html">d.grid</A></EM><BR>
-<EM><A HREF="d.rast.html">d.rast</A></EM><BR>
-<!-- <EM><A HREF="d.rast.labels.html">d.rast.labels</A></EM><BR> -->
-<EM><A HREF="d.rast.leg.html">d.rast.leg</A></EM><BR>
-<EM><A HREF="d.text.html">d.text</A></EM><BR>
-<EM><A HREF="d.vect.thematic.html">d.vect.thematic</A></EM><BR>
-<EM><A HREF="d.what.rast.html">d.what.rast</A></EM><BR>
-<EM><A HREF="g.gisenv.html">g.gisenv</A></EM><BR>
-<EM><A HREF="r.reclass.html">r.reclass</A></EM><BR>
-
-
-<H2>AUTHORS</H2>
-Bill Brown, U.S. Army Construction Engineering Research Laboratories
-<BR>Late 2002: Rewrite of much of the code. Hamish Bowman,
- Otago University, New Zealand
-<BR>Additional improvements from various authors
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/display/d.linegraph/d.linegraph.html (from rev 32770, grass/trunk/display/d.linegraph/description.html)
===================================================================
--- grass/trunk/display/d.linegraph/d.linegraph.html (rev 0)
+++ grass/trunk/display/d.linegraph/d.linegraph.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,95 @@
+<H2>DESCRIPTION</H2>
+
+<EM>d.linegraph</EM> is a primitive program to draw simple x,y line graphs
+based on numerical data contained in separate files.
+<P>
+Data file format<BR>
+The X and Y data files for the graph are essentially a column of numbers in
+each file, with one input number per line. The program expects that each X
+value will have a corresponding Y value, therefore the number of lines in
+each data input file should be the same. Essentially, the X data becomes
+the X axis reference to which the Y data is plotted as a line. Therefore,
+the X data should be a monotonically increasing progression of numbers (i.e.
+"1,2,3,..."; "0, 10, 100, 1000,..."; "...-5,-1,0,1,5..."). If multiple Y
+data files are used, the Y axis scale will be based on the range of minimum
+and maximum values from all Y files, then all Y data given will be graphed
+according to that Y scale. Therefore, if multiple Y data inputs are used
+with dissimilar units, the graph produced comparing the two will be
+deceptive.
+
+<P>
+<DL>
+<DT><B>directoryname</B>
+<DD>Path to the directory where the input files are located. If this option
+is not used, the <EM>d.linegraph</EM> looks for files in the current directory.
+<DD>Example format: directory/usr/grass/data/graph
+
+<DT><B>ycoloroption[,option,...]]</B>
+<DD>Color to be used for drawing the lines in the graph. If multiple Y data
+files are used, an equal number of colors may be used to control the colors
+of the lines. Colors will be assigned to Y data in respect to the sequence
+of instantiation on the command line. Options are listed below. By
+default, a series of colors will be chosen by the program if none are
+provided upon invocation.
+<DD>Order of default colors: yellow, red, green, violet, blue, orange, gray,
+brown, magenta, white, indigo).
+
+<DT><B>titlecoloroption</B>
+<DD>The color to be used for titles, axis lines, tics, and scale numbers.
+<DD>Default: "white"
+<DD>Color options: red, orange, yellow, green, blue, indigo, violet,
+magenta, brown, gray, white, and black.
+
+<DT><B>xtitlevalue</B>
+<DD>Title to describe X data. Will be centered beneath the graph. Default
+is no title unless the need for a unit descriptor is computed by the program
+(i.e. X: title in hundreds). Also, see NOTES section (below) for a format
+caveat for multi-word titles.
+
+<DT><B>ytitlevalue</B>
+<DD>Title to describe Y data. Will be centered beneath the X data title.
+Default is no title unless the need for a unit descriptor is computed by
+the program (i.e. Y: ttiittllee in thousands). Also, see NOTES section
+(below) for a format caveat for multi-word titles. In the case of graphs
+with multiple lines, one may wish to use more specific title placement by
+using the <EM>d.text</EM> or <EM>v.label</EM> programs.
+
+<DT><B>titlevalue</B>
+<DD>Title to describe the graph. Will be centered over the top of graph.
+Default is no title. See NOTES section (below) for a format caveat for
+multi-word titles.
+</DL>
+
+<H2>NOTES</H2>
+Since the command line parser is not amiable to multiple word inputs, to
+input titles of more than one word, use the underscore character ("") to
+represent spaces (" ").
+<P>
+Example: "titleCensusdata1990" would be printed over the graph as "Census
+data 1990".
+<P>
+The way the program locates and labels tic marks is less than perfect: 1)
+although distances between Y tics is proportional to the value, they are
+not proportional on the X axis; 2) decimal values between -1 and 1 can be
+printed on the X axis, but not on Y. (With respect to the later, the input
+for Y values can all be multiplied by a factor of 10 before graphing).
+
+<P>
+It might be easier to use a 3rd party tool such as xgraph or GNUplot instead
+of <em>d.linegraph</em>.
+.
+(You can make GNUplot output pretty by using its SVG or PostScript output
+driver and converting that back into a rasterized image in a paint program)
+
+<H2>SEE ALSO</H2>
+<EM>
+<A HREF="d.frame.html">d.frame</A>,
+<A HREF="d.text.html">d.text</A>,
+<A HREF="v.label.html">v.label</A>
+</EM>
+
+<H2>AUTHOR</H2>
+Chris Rewerts, Agricultural Engineering, Purdue University
+
+<p>
+<i>Last changed: $Date$</i>
Deleted: grass/trunk/display/d.linegraph/description.html
===================================================================
--- grass/trunk/display/d.linegraph/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/display/d.linegraph/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,95 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-<EM>d.linegraph</EM> is a primitive program to draw simple x,y line graphs
-based on numerical data contained in separate files.
-<P>
-Data file format<BR>
-The X and Y data files for the graph are essentially a column of numbers in
-each file, with one input number per line. The program expects that each X
-value will have a corresponding Y value, therefore the number of lines in
-each data input file should be the same. Essentially, the X data becomes
-the X axis reference to which the Y data is plotted as a line. Therefore,
-the X data should be a monotonically increasing progression of numbers (i.e.
-"1,2,3,..."; "0, 10, 100, 1000,..."; "...-5,-1,0,1,5..."). If multiple Y
-data files are used, the Y axis scale will be based on the range of minimum
-and maximum values from all Y files, then all Y data given will be graphed
-according to that Y scale. Therefore, if multiple Y data inputs are used
-with dissimilar units, the graph produced comparing the two will be
-deceptive.
-
-<P>
-<DL>
-<DT><B>directoryname</B>
-<DD>Path to the directory where the input files are located. If this option
-is not used, the <EM>d.linegraph</EM> looks for files in the current directory.
-<DD>Example format: directory/usr/grass/data/graph
-
-<DT><B>ycoloroption[,option,...]]</B>
-<DD>Color to be used for drawing the lines in the graph. If multiple Y data
-files are used, an equal number of colors may be used to control the colors
-of the lines. Colors will be assigned to Y data in respect to the sequence
-of instantiation on the command line. Options are listed below. By
-default, a series of colors will be chosen by the program if none are
-provided upon invocation.
-<DD>Order of default colors: yellow, red, green, violet, blue, orange, gray,
-brown, magenta, white, indigo).
-
-<DT><B>titlecoloroption</B>
-<DD>The color to be used for titles, axis lines, tics, and scale numbers.
-<DD>Default: "white"
-<DD>Color options: red, orange, yellow, green, blue, indigo, violet,
-magenta, brown, gray, white, and black.
-
-<DT><B>xtitlevalue</B>
-<DD>Title to describe X data. Will be centered beneath the graph. Default
-is no title unless the need for a unit descriptor is computed by the program
-(i.e. X: title in hundreds). Also, see NOTES section (below) for a format
-caveat for multi-word titles.
-
-<DT><B>ytitlevalue</B>
-<DD>Title to describe Y data. Will be centered beneath the X data title.
-Default is no title unless the need for a unit descriptor is computed by
-the program (i.e. Y: ttiittllee in thousands). Also, see NOTES section
-(below) for a format caveat for multi-word titles. In the case of graphs
-with multiple lines, one may wish to use more specific title placement by
-using the <EM>d.text</EM> or <EM>v.label</EM> programs.
-
-<DT><B>titlevalue</B>
-<DD>Title to describe the graph. Will be centered over the top of graph.
-Default is no title. See NOTES section (below) for a format caveat for
-multi-word titles.
-</DL>
-
-<H2>NOTES</H2>
-Since the command line parser is not amiable to multiple word inputs, to
-input titles of more than one word, use the underscore character ("") to
-represent spaces (" ").
-<P>
-Example: "titleCensusdata1990" would be printed over the graph as "Census
-data 1990".
-<P>
-The way the program locates and labels tic marks is less than perfect: 1)
-although distances between Y tics is proportional to the value, they are
-not proportional on the X axis; 2) decimal values between -1 and 1 can be
-printed on the X axis, but not on Y. (With respect to the later, the input
-for Y values can all be multiplied by a factor of 10 before graphing).
-
-<P>
-It might be easier to use a 3rd party tool such as xgraph or GNUplot instead
-of <em>d.linegraph</em>.
-.
-(You can make GNUplot output pretty by using its SVG or PostScript output
-driver and converting that back into a rasterized image in a paint program)
-
-<H2>SEE ALSO</H2>
-<EM>
-<A HREF="d.frame.html">d.frame</A>,
-<A HREF="d.text.html">d.text</A>,
-<A HREF="v.label.html">v.label</A>
-</EM>
-
-<H2>AUTHOR</H2>
-Chris Rewerts, Agricultural Engineering, Purdue University
-
-<p>
-<i>Last changed: $Date$</i>
Copied: grass/trunk/display/d.measure/d.measure.html (from rev 32770, grass/trunk/display/d.measure/description.html)
===================================================================
--- grass/trunk/display/d.measure/d.measure.html (rev 0)
+++ grass/trunk/display/d.measure/d.measure.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,62 @@
+<H2>DESCRIPTION</H2>
+
+<EM>d.measure</EM> provides the user with an interactive
+way to measure the lengths and areas of lines and polygons
+drawn by the user in the active frame on the graphics
+monitor. Lines and polygons are drawn using a pointing
+device (mouse). Each line segment is drawn in colors
+<b>c1</b> and <b>c2</b>. A mouse button menu indicates
+that the user can find out the geographic coordinates of
+the cursor location, draw line segments between
+user-specified vertices, and quit <EM>d.measure</EM>. Lines
+and polygons are defined by the series of vertices marked
+by the user. If more than two successive vertices are
+drawn, <EM>d.measure</EM> prints the area encompassed
+(<EM>d.measure</EM> will assume the area is closed even if
+the user has not joined the first and last vertices).
+<!-- (not [currently] true!) Line lengths are stated in the same units
+as those of the current LOCATION. In a XY-LOCATION, where no units are
+available, <EM>d.measure</EM> prints a warning and gives results without
+units. -->
+Areas can be stated in hectares, square miles, square meters and
+square kilometers.
+
+Lines and polygons drawn using <EM>d.measure</EM> will
+overlay (not overwrite) whatever display currently appears
+in the active frame on the graphics monitor. The user can,
+for example, run
+<EM><A HREF="d.rast.html">d.rast</A></EM> or
+<EM><A HREF="d.vect.html">d.vect</A></EM> prior to running
+<EM>d.measure</EM>, and use raster and/or vector maps as a backdrop.
+
+<H2>NOTES</H2>
+
+<EM>d.measure</EM> uses all segments drawn by the user when computing area.
+If the user draws an area within another area, the combined
+area of both regions will be output.
+
+<H2>TODO</H2>
+
+Output lengths in the same units as those of the current LOCATION as
+found in the <tt>PROJ_UNITS</tt> file (see <EM>g.proj</EM>).
+Volunteers are welcome for this task.
+
+<H2>SEE ALSO</H2>
+
+<EM><A HREF="d.frame.html">d.frame</A></EM><br>
+<EM><A HREF="d.graph.html">d.graph</A></EM><br>
+<EM><A HREF="d.rast.html">d.rast</A></EM><br>
+<EM><A HREF="d.vect.html">d.vect</A></EM><br>
+<EM><A HREF="d.where.html">d.where</A></EM><br>
+<EM><A HREF="g.proj.html">g.proj</A></EM>
+
+
+<H2>AUTHORS</H2>
+
+James Westervelt,
+<BR>
+Michael Shapiro, <BR>
+U.S. Army Construction Engineering
+Research Laboratory
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/display/d.measure/description.html
===================================================================
--- grass/trunk/display/d.measure/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/display/d.measure/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,62 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-<EM>d.measure</EM> provides the user with an interactive
-way to measure the lengths and areas of lines and polygons
-drawn by the user in the active frame on the graphics
-monitor. Lines and polygons are drawn using a pointing
-device (mouse). Each line segment is drawn in colors
-<b>c1</b> and <b>c2</b>. A mouse button menu indicates
-that the user can find out the geographic coordinates of
-the cursor location, draw line segments between
-user-specified vertices, and quit <EM>d.measure</EM>. Lines
-and polygons are defined by the series of vertices marked
-by the user. If more than two successive vertices are
-drawn, <EM>d.measure</EM> prints the area encompassed
-(<EM>d.measure</EM> will assume the area is closed even if
-the user has not joined the first and last vertices).
-<!-- (not [currently] true!) Line lengths are stated in the same units
-as those of the current LOCATION. In a XY-LOCATION, where no units are
-available, <EM>d.measure</EM> prints a warning and gives results without
-units. -->
-Areas can be stated in hectares, square miles, square meters and
-square kilometers.
-
-Lines and polygons drawn using <EM>d.measure</EM> will
-overlay (not overwrite) whatever display currently appears
-in the active frame on the graphics monitor. The user can,
-for example, run
-<EM><A HREF="d.rast.html">d.rast</A></EM> or
-<EM><A HREF="d.vect.html">d.vect</A></EM> prior to running
-<EM>d.measure</EM>, and use raster and/or vector maps as a backdrop.
-
-<H2>NOTES</H2>
-
-<EM>d.measure</EM> uses all segments drawn by the user when computing area.
-If the user draws an area within another area, the combined
-area of both regions will be output.
-
-<H2>TODO</H2>
-
-Output lengths in the same units as those of the current LOCATION as
-found in the <tt>PROJ_UNITS</tt> file (see <EM>g.proj</EM>).
-Volunteers are welcome for this task.
-
-<H2>SEE ALSO</H2>
-
-<EM><A HREF="d.frame.html">d.frame</A></EM><br>
-<EM><A HREF="d.graph.html">d.graph</A></EM><br>
-<EM><A HREF="d.rast.html">d.rast</A></EM><br>
-<EM><A HREF="d.vect.html">d.vect</A></EM><br>
-<EM><A HREF="d.where.html">d.where</A></EM><br>
-<EM><A HREF="g.proj.html">g.proj</A></EM>
-
-
-<H2>AUTHORS</H2>
-
-James Westervelt,
-<BR>
-Michael Shapiro, <BR>
-U.S. Army Construction Engineering
-Research Laboratory
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/display/d.nviz/d.nviz.html (from rev 32770, grass/trunk/display/d.nviz/description.html)
===================================================================
--- grass/trunk/display/d.nviz/d.nviz.html (rev 0)
+++ grass/trunk/display/d.nviz/d.nviz.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,144 @@
+<H2>DESCRIPTION</H2>
+
+The <EM>d.nviz</EM> program allows the user to easily create a script
+that can be run in NVIZ to fly through a terrain.
+
+The NVIZ flight path can be chosen interactively from the GRASS
+monitor (<EM>-i</EM>) or supplied on the command line as comma
+separated coordinates. The program optionally allows a KeyFrame
+file to created (after running the script). This KeyFrame file can
+be loaded into the <EM>Keyframe Animation</EM> panel for fine
+tuning or editing.
+
+<p>
+The script generated by <EM>d.nviz</EM> can be run from the NVIZ
+command line (nviz script=script_name) or after NVIZ is started by
+selecting <EM>Scripting->Play Script</EM>.
+
+<H2>OPTIONS</H2>
+
+<H3>Flags:</H3>
+<DL>
+<DT><B>-i</B>
+<DD>Intercative mode
+<DD>The user selects the camera path from the GRASS monitor by
+ clicking the left mouse button along the route. Click the
+ right mouse button to finish.
+<DT><B>-f</B>
+<DD>Full render
+<DD>The script will draw all loaded NVIZ data and save scene to PPM image.
+<DT><B>-c</B>
+<DD>Flay at constant elevation
+<DD>With this flag the camera will be set to an elevation given by the
+ <EM>ht=</EM> parameter. The default is to fly at <EM>ht=</EM>
+ above the topography (i.e. camera height = elevation + ht)
+<DT><B>-k</B>
+<DD>Output KeyFrame file
+<DD>Generate a KeyFrame file that can be loaded from the NVIZ
+ <EM>Keyframe Animation</EM> panel. The KeyFrame file is
+ automatically assigned the script name with a
+ <EM>.kanimator</EM> extension.
+<DT><B>-o</B>
+<DD>Render the animation in an off-screen context
+<DT><B>-e</B>
+<DD>Enable vector and sites drawing
+</DL>
+
+
+<H3>Parameters:</H3>
+<DL>
+<DT><B>input</B>
+<DD>The name of the GRASS raster map with elevation data.
+<DD>This should be the same file that will be loaded in NVIZ.
+
+<DT><B>output</B>
+<DD>The name of the NVIZ script to create.
+
+<DT><B>name</B>
+<DD>The prefix for output images if running in full render mode (<EM>-f</EM>).
+<DD>The defulat preifix is NVIZ (eg. NVIZ0000.ppm).
+
+<DT><B>dist</B>
+<DD>The distance of the camera behind the center of view.
+
+<DT><B>ht</B>
+<DD>The height of the camera above the center of view.
+<DD>If the the <EM>-c</EM> flag is set, the height represents the actual camera height.
+
+<DT><B>frames</B>
+<DD>The number of frames in the animation.
+
+<DT><B>start</B>
+<DD>The starting frame number (default = 0).
+<DD> This option may be useful in full render mode when creating an
+animation in sections. For example the user may wish to start at frame
+number 2000.
+
+<DT><B>route</B>
+<DD>The comma seperated geographic coordinates for keyframe locations.
+<DD>The interactive flag (<EM>-i</EM>) overrides this option.
+
+</DL>
+
+<H2>EXAMPLE</H2>
+To interactively create an NVIZ animation from raster elev.rast with
+500 frames and the camera set to 50 meters above and 250 meters behind
+the scene, run the following:
+
+<div class="code"><pre>
+d.nviz -ik input=elevation.dem output=nviz.script dist=2400 ht=1220 frames=1000
+</pre></div>
+In the above the example the user is prompted to select the route from the GRASS monitor.
+The output script, nviz.script, can then be run in NVIZ:
+<div class="code"><pre>
+nviz el=elevation.dem script=nviz.script
+</pre></div>
+
+<H2>NOTES / HINTS</H2>
+The user must select at least four key-frame locations (points)
+ otherwise an error is generated.
+<p>
+If the GRASS region is changed the <EM>d.nviz</EM> command must be re-run.
+<p>
+The current GRASS region and the user supplied paramters are included
+as a comment at the top of the output script. This information can be
+used to easily re-create the animation.
+<p>
+The camera position is calculated backwards from the supplied
+position(s). It is possible that the camera position will lie outside
+the current window, in which case a non-fatal error is generated
+(Error: selected point is outside region). This error can result in
+jerky movements during the animation. To correct this problem reduce
+the <EM>dist=</EM> parameter or increase the current region.
+
+<h3>Loading the script into NVIZ</h3>
+
+The user can run the script at arbitrary resolution. To re-run it at
+higher spatial resolution or different settings, the user first loads
+the surface and sets the resolution, lighting, etc. Then internally
+the script generated by <em>d.nviz</em> is run. Alternatively, the
+user can run nviz with a previuosly saved state and the
+<em>d.nviz</em> generated script:
+
+<div class="code"><pre>
+nviz state=saved.state script=nviz.script
+</pre></div>
+
+<h3>Keyframe animator script</h3>
+Running the script generated by d.nviz within NVIZ, a new script for
+kanimator (keyframe animator) is created. The kanimator panel offers
+fine tuning of the speed (frame rate) as well as editing individual
+frames or inserting new frames. This new kanimator script has to be
+loaded from the Kanimator panel in NVIZ. In the Kanimator panel there
+are Save and Load button which allow the user to save and re-load a
+kanimator script. Once loaded, the key frames will appear in the GUI
+and can then be edited there.
+
+<H2>SEE ALSO</H2>
+
+<EM><A HREF="nviz.html">nviz</A></EM>
+
+<H2>AUTHOR</H2>
+
+<A HREF=mailto:bcovill at tekmap.ns.ca>Bob Covill</A>
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/display/d.nviz/description.html
===================================================================
--- grass/trunk/display/d.nviz/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/display/d.nviz/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,144 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-The <EM>d.nviz</EM> program allows the user to easily create a script
-that can be run in NVIZ to fly through a terrain.
-
-The NVIZ flight path can be chosen interactively from the GRASS
-monitor (<EM>-i</EM>) or supplied on the command line as comma
-separated coordinates. The program optionally allows a KeyFrame
-file to created (after running the script). This KeyFrame file can
-be loaded into the <EM>Keyframe Animation</EM> panel for fine
-tuning or editing.
-
-<p>
-The script generated by <EM>d.nviz</EM> can be run from the NVIZ
-command line (nviz script=script_name) or after NVIZ is started by
-selecting <EM>Scripting->Play Script</EM>.
-
-<H2>OPTIONS</H2>
-
-<H3>Flags:</H3>
-<DL>
-<DT><B>-i</B>
-<DD>Intercative mode
-<DD>The user selects the camera path from the GRASS monitor by
- clicking the left mouse button along the route. Click the
- right mouse button to finish.
-<DT><B>-f</B>
-<DD>Full render
-<DD>The script will draw all loaded NVIZ data and save scene to PPM image.
-<DT><B>-c</B>
-<DD>Flay at constant elevation
-<DD>With this flag the camera will be set to an elevation given by the
- <EM>ht=</EM> parameter. The default is to fly at <EM>ht=</EM>
- above the topography (i.e. camera height = elevation + ht)
-<DT><B>-k</B>
-<DD>Output KeyFrame file
-<DD>Generate a KeyFrame file that can be loaded from the NVIZ
- <EM>Keyframe Animation</EM> panel. The KeyFrame file is
- automatically assigned the script name with a
- <EM>.kanimator</EM> extension.
-<DT><B>-o</B>
-<DD>Render the animation in an off-screen context
-<DT><B>-e</B>
-<DD>Enable vector and sites drawing
-</DL>
-
-
-<H3>Parameters:</H3>
-<DL>
-<DT><B>input</B>
-<DD>The name of the GRASS raster map with elevation data.
-<DD>This should be the same file that will be loaded in NVIZ.
-
-<DT><B>output</B>
-<DD>The name of the NVIZ script to create.
-
-<DT><B>name</B>
-<DD>The prefix for output images if running in full render mode (<EM>-f</EM>).
-<DD>The defulat preifix is NVIZ (eg. NVIZ0000.ppm).
-
-<DT><B>dist</B>
-<DD>The distance of the camera behind the center of view.
-
-<DT><B>ht</B>
-<DD>The height of the camera above the center of view.
-<DD>If the the <EM>-c</EM> flag is set, the height represents the actual camera height.
-
-<DT><B>frames</B>
-<DD>The number of frames in the animation.
-
-<DT><B>start</B>
-<DD>The starting frame number (default = 0).
-<DD> This option may be useful in full render mode when creating an
-animation in sections. For example the user may wish to start at frame
-number 2000.
-
-<DT><B>route</B>
-<DD>The comma seperated geographic coordinates for keyframe locations.
-<DD>The interactive flag (<EM>-i</EM>) overrides this option.
-
-</DL>
-
-<H2>EXAMPLE</H2>
-To interactively create an NVIZ animation from raster elev.rast with
-500 frames and the camera set to 50 meters above and 250 meters behind
-the scene, run the following:
-
-<div class="code"><pre>
-d.nviz -ik input=elevation.dem output=nviz.script dist=2400 ht=1220 frames=1000
-</pre></div>
-In the above the example the user is prompted to select the route from the GRASS monitor.
-The output script, nviz.script, can then be run in NVIZ:
-<div class="code"><pre>
-nviz el=elevation.dem script=nviz.script
-</pre></div>
-
-<H2>NOTES / HINTS</H2>
-The user must select at least four key-frame locations (points)
- otherwise an error is generated.
-<p>
-If the GRASS region is changed the <EM>d.nviz</EM> command must be re-run.
-<p>
-The current GRASS region and the user supplied paramters are included
-as a comment at the top of the output script. This information can be
-used to easily re-create the animation.
-<p>
-The camera position is calculated backwards from the supplied
-position(s). It is possible that the camera position will lie outside
-the current window, in which case a non-fatal error is generated
-(Error: selected point is outside region). This error can result in
-jerky movements during the animation. To correct this problem reduce
-the <EM>dist=</EM> parameter or increase the current region.
-
-<h3>Loading the script into NVIZ</h3>
-
-The user can run the script at arbitrary resolution. To re-run it at
-higher spatial resolution or different settings, the user first loads
-the surface and sets the resolution, lighting, etc. Then internally
-the script generated by <em>d.nviz</em> is run. Alternatively, the
-user can run nviz with a previuosly saved state and the
-<em>d.nviz</em> generated script:
-
-<div class="code"><pre>
-nviz state=saved.state script=nviz.script
-</pre></div>
-
-<h3>Keyframe animator script</h3>
-Running the script generated by d.nviz within NVIZ, a new script for
-kanimator (keyframe animator) is created. The kanimator panel offers
-fine tuning of the speed (frame rate) as well as editing individual
-frames or inserting new frames. This new kanimator script has to be
-loaded from the Kanimator panel in NVIZ. In the Kanimator panel there
-are Save and Load button which allow the user to save and re-load a
-kanimator script. Once loaded, the key frames will appear in the GUI
-and can then be edited there.
-
-<H2>SEE ALSO</H2>
-
-<EM><A HREF="nviz.html">nviz</A></EM>
-
-<H2>AUTHOR</H2>
-
-<A HREF=mailto:bcovill at tekmap.ns.ca>Bob Covill</A>
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/display/d.path/d.path.html (from rev 32770, grass/trunk/display/d.path/description.html)
===================================================================
--- grass/trunk/display/d.path/d.path.html (rev 0)
+++ grass/trunk/display/d.path/d.path.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,43 @@
+<h2>DESCRIPTION</h2>
+
+<em>d.path</em> enables shortest path vector networking - based on DGLib
+(Directed Graph Library) vector network library
+(see <a href="http://grass.gdf-hannover.de/wiki/Vector_network_analysis">screenshot</a>).
+Costs may be either line lengths, or attributes saved in a database table.
+Supported are cost assignments for both arcs and nodes, and also different
+in both directions of a vector line. For areas cost will be calculated along
+boundary lines.
+
+<h2>NOTE</h2>
+
+The user needs to display a vector map before using d.path. The 'from' and 'to'
+points are entered by mouse into the map displayed in the GRASS monitor, or
+if the <b>coor</b> option is used they can be specified non-interactively.
+The actions bound to the mouse buttons are described in the terminal
+window when running the command.
+<P>
+To calculate shortest path non-interactively and save the path to a new vector
+map, use the <em>v.net.path</em> module.
+
+<h2>EXAMPLE</h2>
+
+<div class="code"><pre>
+# Spearfish
+
+d.vect roads
+d.path -b roads coor="601653.5,4922869.2","593330.8,4924096.6"
+</pre></div>
+
+<h2>SEE ALSO</h2>
+
+<em>
+<a HREF="v.net.path.html">v.net.path</a>,
+<a HREF="http://grass.itc.it/dglib/">DGLib</a>
+</em>
+
+<h2>AUTHOR</h2>
+
+Radim Blazek, ITC-Irst, Trento, Italy
+
+<p>
+<i>Last changed: $Date$</i>
Deleted: grass/trunk/display/d.path/description.html
===================================================================
--- grass/trunk/display/d.path/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/display/d.path/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,43 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>d.path</em> enables shortest path vector networking - based on DGLib
-(Directed Graph Library) vector network library
-(see <a href="http://grass.gdf-hannover.de/wiki/Vector_network_analysis">screenshot</a>).
-Costs may be either line lengths, or attributes saved in a database table.
-Supported are cost assignments for both arcs and nodes, and also different
-in both directions of a vector line. For areas cost will be calculated along
-boundary lines.
-
-<h2>NOTE</h2>
-
-The user needs to display a vector map before using d.path. The 'from' and 'to'
-points are entered by mouse into the map displayed in the GRASS monitor, or
-if the <b>coor</b> option is used they can be specified non-interactively.
-The actions bound to the mouse buttons are described in the terminal
-window when running the command.
-<P>
-To calculate shortest path non-interactively and save the path to a new vector
-map, use the <em>v.net.path</em> module.
-
-<h2>EXAMPLE</h2>
-
-<div class="code"><pre>
-# Spearfish
-
-d.vect roads
-d.path -b roads coor="601653.5,4922869.2","593330.8,4924096.6"
-</pre></div>
-
-<h2>SEE ALSO</h2>
-
-<em>
-<a HREF="v.net.path.html">v.net.path</a>,
-<a HREF="http://grass.itc.it/dglib/">DGLib</a>
-</em>
-
-<h2>AUTHOR</h2>
-
-Radim Blazek, ITC-Irst, Trento, Italy
-
-<p>
-<i>Last changed: $Date$</i>
Copied: grass/trunk/display/d.profile/d.profile.html (from rev 32770, grass/trunk/display/d.profile/description.html)
===================================================================
--- grass/trunk/display/d.profile/d.profile.html (rev 0)
+++ grass/trunk/display/d.profile/d.profile.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,194 @@
+<H2>DESCRIPTION</H2>
+
+This command works only interactively. It clears the entire
+graphics screen and provides a graphical interaction
+allowing the selection of transects for which profiles are
+then generated. Input parameters can be specified on the command line
+for quicker start-up.
+
+<H2>USER PROMPTS</H2>
+
+First, you will be presented with a prompt asking you to
+choose a raster map layer to be profiled. Then you will be
+prompted for an optional display raster. The optional display raster
+will be shown rather than the profiled raster. This is useful
+to be able to more easily see ground features, such as might be visible
+in an aerial photo or satellite image. Finally, you will
+be prompted for the name prefix for output file(s) containing the profile
+data. This is an optional feature.
+
+<P>
+
+After parameters are given, the raster layer will be
+displayed in the left half of the graphics monitor, and the
+right half will be divided into four
+frames. There will also be two frames along the top of the
+monitor: a mouse-button menu frame on the left, and a
+status frame on the right.
+
+<P>
+
+The mouse-button menu initially offers you three options:
+
+<DL>
+<DD>
+Mouse Buttons: <BR>
+Left: Where am I? <BR>
+Middle: Mark FIRST Point of Profile Line. <BR>
+Right: QUIT this. <BR>
+</DL>
+
+You may query the displayed raster map layer by indicating
+points with the left mouse-button. The coordinates and
+category value of each point that you indicate will be
+displayed on in the status frame. If you mark the first
+point of the profile line you will be presented with the
+following mouse-button menu:
+
+<DL>
+<DD>
+Mouse Buttons: <BR>
+Left: Where am I? <BR>
+Middle: Mark SECOND Point of Profile Line. <BR>
+Right: QUIT this. <BR>
+</DL>
+
+Once you mark the second point of the profile line, the
+profile line will be labeled (with a letter from A to D)
+and displayed in one of the four display frames on the
+right hand side of the screen. You will then be presented
+with a third mouse-button menu:
+
+<DL>
+<DD>
+Mouse Buttons: <BR>
+Left: DO ANOTHER <BR>
+Middle: CLEAR DISPLAY <BR>
+Right: QUIT this. <BR>
+</DL>
+
+If you would like to view another profile, click on the
+left mouse-button. If you would like to redisplay the
+raster map layer and clear out the four profile frames,
+click on the middle mouse-button. If you would like to
+quit, then click on the right button.
+
+<P>
+
+If you selected the <B>plotfile</B> option, you will have up to
+four files starting with the <EM>name</EM> and followed by a suffix
+of the plot letter <EM>A, B, C,</EM> or <EM>D</EM>. The plots that
+are written to these files reflect the last of each plot done with that
+letter (i.e. They will match what's in the display when you quit).
+
+<P>
+The format of the plot files is not geared toward any particular software,
+but should be easy to coax into a number of other programs. The first
+three lines contain some header information about the plot, each prefixed
+with a <TT>#</TT> sign to denote a comment. A fourth comment line describes
+the data that follows. It consists of the distance (always in meters),
+the cell value (in whatever units it is in), the easting in decimal format,
+and the northing in decimal format.
+The number of values will vary depending on the length of the profile, cell
+resolution and the slope angle of the profile line. Below is an example
+of a plotfile:
+<P>
+<TT>
+# Profile A of elev.ft at snows<BR>
+# From (702879.29679757, 4287317.55920185) to (702722.40973589, 4287061.72632285)<BR>
+# Stats: Count = 644, Min = 2424.658936, Max = 2513.246094<BR>
+# dist value east north<BR>
+0.000000 2513.246094 702879.102364 4287317.516912<BR>
+0.000000 2513.246094 702878.713496 4287317.118970<BR>
+0.556395 2513.246094 702878.324629 4287316.721029<BR>
+1.112790 2513.246094 702878.324629 4287316.323088<BR>
+...<P>
+</TT>
+
+<H2>NOTES</H2>
+
+You might notice the first two 'dist' values in the profile output above are
+both zero. This is due to the fact the cell resolution for this file is
+less than one meter, and so the function that calculates the distance
+considers the distance between the first cell and the second to be zero.
+You might also notice, the coordinates given in the header and displayed on
+screen are slightly different from the first and last coordinates given in
+the profile data output. This is because the profile data output finds the
+eastings and northings for the center of the cells while the coordinate
+transformations from mouse clicks might yield slightly different coordinates
+which still fall within the same cell boundaries. The difference should
+always be less than the distance between the center and any corner (not
+edge!) of the cell at the resolution of the profiled raster.
+
+<P>
+
+Only four output plotfiles can be made. Each time a new profile is run, the
+plotfile is immediately written to the file <EM>name</EM>.<EM>letter</EM>.
+One can take advantage of this fact to create an unlimited number of
+plotfiles simply by renaming the output files before running more profiles.
+This may not always be the case, but it is at the time of this writing.
+
+<P>
+
+Useful enhancements to <EM>d.profile</EM> would include:
+
+<OL>
+
+<LI>Adding an option to display profiles using category
+colors, like a bar-chart.
+
+<LI>Allowing profile lines to be defined by a series of
+points, not just two.
+
+<LI>Allowing profiles to be saved in a file, for later
+viewing by GRASS.
+
+<LI>Allowing the user to enter profile line points by
+typing coordinates.
+
+</OL>
+
+<H3>Perl Script to convert output to a site_list</H3>
+
+The script below will convert the <B>plotfile</B> output to the site_list format.
+It probably won't work 100% for lat/lon datasets.
+
+<P>
+
+<TT>
+<B>#! /usr/bin/perl -w</B><BR>
+# prof2sites.pl: converts the output of d.profile to a site_list
+<P>
+<B>my</B> (<EM>$dist</EM>, <EM>$elev</EM>, <EM>$east</EM>, <EM>$north</EM>);
+<P>
+<B>while</B> (<<B>STDIN</B>>)<BR>
+{<BR>
+ <B>if</B> (m/^#/)<BR>
+ {<BR>
+ <B>print</B> "<EM>$_</EM>";<BR>
+ }<BR>
+ <B>else</B><BR>
+ {<BR>
+ <B>chomp</B>;<BR>
+ (<EM>$dist</EM>, <EM>$elev</EM>, <EM>$east</EM>, <EM>$north</EM>) = <B>split</B> / /;<BR>
+ <B>print</B> "<EM>$east</EM>|<EM>$north</EM>|<EM>$elev</EM>|#1 \%<EM>$dist</EM> \@Profile\n";<BR>
+ }<BR>
+}<BR>
+</TT>
+
+<H2>BUGS</H2>
+
+None known.
+
+<H2>AUTHOR</H2>
+
+Dave Johnson
+<BR> DBA Systems, Inc. <BR>
+10560 Arrowhead Drive <BR>
+Fairfax, Virginia 22030
+
+<P>
+Modified by Eric G. Miller for profile output, support of
+floating point rasters, and optional display raster (02-Dec-2000).
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/display/d.profile/description.html
===================================================================
--- grass/trunk/display/d.profile/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/display/d.profile/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,194 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-This command works only interactively. It clears the entire
-graphics screen and provides a graphical interaction
-allowing the selection of transects for which profiles are
-then generated. Input parameters can be specified on the command line
-for quicker start-up.
-
-<H2>USER PROMPTS</H2>
-
-First, you will be presented with a prompt asking you to
-choose a raster map layer to be profiled. Then you will be
-prompted for an optional display raster. The optional display raster
-will be shown rather than the profiled raster. This is useful
-to be able to more easily see ground features, such as might be visible
-in an aerial photo or satellite image. Finally, you will
-be prompted for the name prefix for output file(s) containing the profile
-data. This is an optional feature.
-
-<P>
-
-After parameters are given, the raster layer will be
-displayed in the left half of the graphics monitor, and the
-right half will be divided into four
-frames. There will also be two frames along the top of the
-monitor: a mouse-button menu frame on the left, and a
-status frame on the right.
-
-<P>
-
-The mouse-button menu initially offers you three options:
-
-<DL>
-<DD>
-Mouse Buttons: <BR>
-Left: Where am I? <BR>
-Middle: Mark FIRST Point of Profile Line. <BR>
-Right: QUIT this. <BR>
-</DL>
-
-You may query the displayed raster map layer by indicating
-points with the left mouse-button. The coordinates and
-category value of each point that you indicate will be
-displayed on in the status frame. If you mark the first
-point of the profile line you will be presented with the
-following mouse-button menu:
-
-<DL>
-<DD>
-Mouse Buttons: <BR>
-Left: Where am I? <BR>
-Middle: Mark SECOND Point of Profile Line. <BR>
-Right: QUIT this. <BR>
-</DL>
-
-Once you mark the second point of the profile line, the
-profile line will be labeled (with a letter from A to D)
-and displayed in one of the four display frames on the
-right hand side of the screen. You will then be presented
-with a third mouse-button menu:
-
-<DL>
-<DD>
-Mouse Buttons: <BR>
-Left: DO ANOTHER <BR>
-Middle: CLEAR DISPLAY <BR>
-Right: QUIT this. <BR>
-</DL>
-
-If you would like to view another profile, click on the
-left mouse-button. If you would like to redisplay the
-raster map layer and clear out the four profile frames,
-click on the middle mouse-button. If you would like to
-quit, then click on the right button.
-
-<P>
-
-If you selected the <B>plotfile</B> option, you will have up to
-four files starting with the <EM>name</EM> and followed by a suffix
-of the plot letter <EM>A, B, C,</EM> or <EM>D</EM>. The plots that
-are written to these files reflect the last of each plot done with that
-letter (i.e. They will match what's in the display when you quit).
-
-<P>
-The format of the plot files is not geared toward any particular software,
-but should be easy to coax into a number of other programs. The first
-three lines contain some header information about the plot, each prefixed
-with a <TT>#</TT> sign to denote a comment. A fourth comment line describes
-the data that follows. It consists of the distance (always in meters),
-the cell value (in whatever units it is in), the easting in decimal format,
-and the northing in decimal format.
-The number of values will vary depending on the length of the profile, cell
-resolution and the slope angle of the profile line. Below is an example
-of a plotfile:
-<P>
-<TT>
-# Profile A of elev.ft at snows<BR>
-# From (702879.29679757, 4287317.55920185) to (702722.40973589, 4287061.72632285)<BR>
-# Stats: Count = 644, Min = 2424.658936, Max = 2513.246094<BR>
-# dist value east north<BR>
-0.000000 2513.246094 702879.102364 4287317.516912<BR>
-0.000000 2513.246094 702878.713496 4287317.118970<BR>
-0.556395 2513.246094 702878.324629 4287316.721029<BR>
-1.112790 2513.246094 702878.324629 4287316.323088<BR>
-...<P>
-</TT>
-
-<H2>NOTES</H2>
-
-You might notice the first two 'dist' values in the profile output above are
-both zero. This is due to the fact the cell resolution for this file is
-less than one meter, and so the function that calculates the distance
-considers the distance between the first cell and the second to be zero.
-You might also notice, the coordinates given in the header and displayed on
-screen are slightly different from the first and last coordinates given in
-the profile data output. This is because the profile data output finds the
-eastings and northings for the center of the cells while the coordinate
-transformations from mouse clicks might yield slightly different coordinates
-which still fall within the same cell boundaries. The difference should
-always be less than the distance between the center and any corner (not
-edge!) of the cell at the resolution of the profiled raster.
-
-<P>
-
-Only four output plotfiles can be made. Each time a new profile is run, the
-plotfile is immediately written to the file <EM>name</EM>.<EM>letter</EM>.
-One can take advantage of this fact to create an unlimited number of
-plotfiles simply by renaming the output files before running more profiles.
-This may not always be the case, but it is at the time of this writing.
-
-<P>
-
-Useful enhancements to <EM>d.profile</EM> would include:
-
-<OL>
-
-<LI>Adding an option to display profiles using category
-colors, like a bar-chart.
-
-<LI>Allowing profile lines to be defined by a series of
-points, not just two.
-
-<LI>Allowing profiles to be saved in a file, for later
-viewing by GRASS.
-
-<LI>Allowing the user to enter profile line points by
-typing coordinates.
-
-</OL>
-
-<H3>Perl Script to convert output to a site_list</H3>
-
-The script below will convert the <B>plotfile</B> output to the site_list format.
-It probably won't work 100% for lat/lon datasets.
-
-<P>
-
-<TT>
-<B>#! /usr/bin/perl -w</B><BR>
-# prof2sites.pl: converts the output of d.profile to a site_list
-<P>
-<B>my</B> (<EM>$dist</EM>, <EM>$elev</EM>, <EM>$east</EM>, <EM>$north</EM>);
-<P>
-<B>while</B> (<<B>STDIN</B>>)<BR>
-{<BR>
- <B>if</B> (m/^#/)<BR>
- {<BR>
- <B>print</B> "<EM>$_</EM>";<BR>
- }<BR>
- <B>else</B><BR>
- {<BR>
- <B>chomp</B>;<BR>
- (<EM>$dist</EM>, <EM>$elev</EM>, <EM>$east</EM>, <EM>$north</EM>) = <B>split</B> / /;<BR>
- <B>print</B> "<EM>$east</EM>|<EM>$north</EM>|<EM>$elev</EM>|#1 \%<EM>$dist</EM> \@Profile\n";<BR>
- }<BR>
-}<BR>
-</TT>
-
-<H2>BUGS</H2>
-
-None known.
-
-<H2>AUTHOR</H2>
-
-Dave Johnson
-<BR> DBA Systems, Inc. <BR>
-10560 Arrowhead Drive <BR>
-Fairfax, Virginia 22030
-
-<P>
-Modified by Eric G. Miller for profile output, support of
-floating point rasters, and optional display raster (02-Dec-2000).
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/display/d.rast/d.rast.html (from rev 32770, grass/trunk/display/d.rast/description.html)
===================================================================
--- grass/trunk/display/d.rast/d.rast.html (rev 0)
+++ grass/trunk/display/d.rast/d.rast.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,22 @@
+<h2>DESCRIPTION</h2>
+
+<em>d.rast</em> displays raster map layer(s) <em>name</em>
+in the active display frame on the graphics monitor.
+
+<h2>NOTES</h2>
+
+To overlay raster maps option (<b>-o</b>) may be used.
+
+<h2>SEE ALSO</h2>
+
+<em><a HREF="d.erase.html">d.erase</a></em><br>
+<em><a HREF="d.vect.html">d.vect</a></em><br>
+<em><a HREF="d.what.rast.html">d.what.rast</a></em><br>
+
+<h2>AUTHOR</h2>
+
+James Westervelt,
+U.S. Army Construction Engineering
+Research Laboratory
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/display/d.rast/description.html
===================================================================
--- grass/trunk/display/d.rast/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/display/d.rast/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,22 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>d.rast</em> displays raster map layer(s) <em>name</em>
-in the active display frame on the graphics monitor.
-
-<h2>NOTES</h2>
-
-To overlay raster maps option (<b>-o</b>) may be used.
-
-<h2>SEE ALSO</h2>
-
-<em><a HREF="d.erase.html">d.erase</a></em><br>
-<em><a HREF="d.vect.html">d.vect</a></em><br>
-<em><a HREF="d.what.rast.html">d.what.rast</a></em><br>
-
-<h2>AUTHOR</h2>
-
-James Westervelt,
-U.S. Army Construction Engineering
-Research Laboratory
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/display/d.rast.arrow/d.rast.arrow.html (from rev 32770, grass/trunk/display/d.rast.arrow/description.html)
===================================================================
--- grass/trunk/display/d.rast.arrow/d.rast.arrow.html (rev 0)
+++ grass/trunk/display/d.rast.arrow/d.rast.arrow.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,95 @@
+<H2>DESCRIPTION</H2>
+
+<EM>d.rast.arrow</EM>
+is designed to help users better visualize surface water flow direction,
+as indicated in an aspect raster map layer. There are two ways to specify
+the aspect layer the program is to use. The first is to display the aspect
+map layer on the graphics monitor before running <EM>d.rast.arrow</EM>.
+The second method involves setting the <EM>map</EM> parameter
+to the name of the desired aspect map.
+This allows the arrows to be drawn over any other maps already displayed
+on the graphics monitor.
+<P>
+
+<EM>d.rast.arrow</EM> will draw an arrow over each displayed cell
+to indicate in which direction the cell slopes. If the aspect
+layer has a category value denoting locations of "unknown" aspect,
+<EM>d.rast.arrow</EM> draws a question mark over the displayed cells
+of that category.
+Cells containing null data will be marked with an "X".
+<p>
+If you specify the <em>magnitude_map</em> option, arrow lengths
+denoting magnitude will be extracted from the cell values of the specified
+map. In this case the tail of the arrow will be centered on the source cell.
+You may adjust the overall scale using the <em>scale</em> option.
+<em>d.rast.arrow</em> will ignore NULL and negative magnitudes, and will
+warn you if the debug level is set at 5 or higher. Be aware. If your application
+uses negative values for magnitude, you can use <em>r.mapcalc</em> to prepare
+the magnitude map to suit your needs (absolute value, inverted direction and
+so on).
+
+<p>
+<H2>NOTES</H2>
+By default, arrows are drawn at the size of a cell and cannot be seen if
+the raster map is relatively close in scale. You can use the <em>skip</em>
+option to draw arrows every n-th cell in both directions if you are working
+with relatively high resolutions. It may be useful to disable the grid in
+this case, which is accomplished by setting its color to "<tt>none</tt>".
+<P>
+For GRASS and Compass type aspect maps, the cell values of the aspect map
+will determine the corresponding direction in 360 degrees. ANSWERS type
+aspect maps will be plotted in multiples of 15 degrees, and AGNPS type
+aspect maps will be displayed in D8 representation, i.e. the eight multiples
+of 45 degrees.
+<P>
+GRASS aspect maps are measured using Cartesian conventions, i.e. in degrees
+counterclockwise from east. e.g.:
+<UL>
+<pre>
+90 North
+180 West
+270 South
+0,360 East</pre>
+</UL>
+<P>
+They can be created from a raster elevation map with <em>r.slope.aspect</em>.
+<P>
+Compass type aspect maps are measured in degrees clockwise from north.
+<P>
+This module uses oceanographic conventions, i.e. arrows point downslope or
+direction "to", as opposed to atmospheric conventions (direction "from").
+
+
+<H2>EXAMPLE</H2>
+
+Convert U,V velocity component maps into magnitide,direction maps for use
+with <em>d.rast.arrow</em>:
+<pre>
+ r.mapcalc 'magnitude = sqrt(U_map^2 + V_map^2)'
+ r.mapcalc 'direction = atan(U_map, V_map)'
+ d.rast.arrow map=direction type=grass magnitude_map=magnitude skip=3 grid=none
+</pre>
+<BR>
+
+<H2>SEE ALSO</H2>
+
+<EM><A HREF="d.frame.html">d.frame</A></EM><BR>
+<EM><A HREF="d.rast.html">d.rast</A></EM><BR>
+<EM><A HREF="d.rast.edit.html">d.rast.edit</A></EM><BR>
+<EM><A HREF="d.rast.num.html">d.rast.num</A></EM><BR>
+<EM><A HREF="g.region.html">g.region</A></EM><BR>
+<EM><A HREF="r.slope.aspect.html">r.slope.aspect</A></EM><BR>
+<BR>
+
+<H2>AUTHORS</H2>
+
+<u>Original author</u><BR>
+Chris Rewerts<BR>
+<em>Agricultural Engineering,<BR>
+Purdue University</em><BR><BR>
+<u>Magnitude and 360 arrow code</u><BR>
+Hamish Bowman<BR>
+<em>Department of Marine Science, <BR>
+University of Otago, New Zealand</em>
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/display/d.rast.arrow/description.html
===================================================================
--- grass/trunk/display/d.rast.arrow/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/display/d.rast.arrow/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,95 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-<EM>d.rast.arrow</EM>
-is designed to help users better visualize surface water flow direction,
-as indicated in an aspect raster map layer. There are two ways to specify
-the aspect layer the program is to use. The first is to display the aspect
-map layer on the graphics monitor before running <EM>d.rast.arrow</EM>.
-The second method involves setting the <EM>map</EM> parameter
-to the name of the desired aspect map.
-This allows the arrows to be drawn over any other maps already displayed
-on the graphics monitor.
-<P>
-
-<EM>d.rast.arrow</EM> will draw an arrow over each displayed cell
-to indicate in which direction the cell slopes. If the aspect
-layer has a category value denoting locations of "unknown" aspect,
-<EM>d.rast.arrow</EM> draws a question mark over the displayed cells
-of that category.
-Cells containing null data will be marked with an "X".
-<p>
-If you specify the <em>magnitude_map</em> option, arrow lengths
-denoting magnitude will be extracted from the cell values of the specified
-map. In this case the tail of the arrow will be centered on the source cell.
-You may adjust the overall scale using the <em>scale</em> option.
-<em>d.rast.arrow</em> will ignore NULL and negative magnitudes, and will
-warn you if the debug level is set at 5 or higher. Be aware. If your application
-uses negative values for magnitude, you can use <em>r.mapcalc</em> to prepare
-the magnitude map to suit your needs (absolute value, inverted direction and
-so on).
-
-<p>
-<H2>NOTES</H2>
-By default, arrows are drawn at the size of a cell and cannot be seen if
-the raster map is relatively close in scale. You can use the <em>skip</em>
-option to draw arrows every n-th cell in both directions if you are working
-with relatively high resolutions. It may be useful to disable the grid in
-this case, which is accomplished by setting its color to "<tt>none</tt>".
-<P>
-For GRASS and Compass type aspect maps, the cell values of the aspect map
-will determine the corresponding direction in 360 degrees. ANSWERS type
-aspect maps will be plotted in multiples of 15 degrees, and AGNPS type
-aspect maps will be displayed in D8 representation, i.e. the eight multiples
-of 45 degrees.
-<P>
-GRASS aspect maps are measured using Cartesian conventions, i.e. in degrees
-counterclockwise from east. e.g.:
-<UL>
-<pre>
-90 North
-180 West
-270 South
-0,360 East</pre>
-</UL>
-<P>
-They can be created from a raster elevation map with <em>r.slope.aspect</em>.
-<P>
-Compass type aspect maps are measured in degrees clockwise from north.
-<P>
-This module uses oceanographic conventions, i.e. arrows point downslope or
-direction "to", as opposed to atmospheric conventions (direction "from").
-
-
-<H2>EXAMPLE</H2>
-
-Convert U,V velocity component maps into magnitide,direction maps for use
-with <em>d.rast.arrow</em>:
-<pre>
- r.mapcalc 'magnitude = sqrt(U_map^2 + V_map^2)'
- r.mapcalc 'direction = atan(U_map, V_map)'
- d.rast.arrow map=direction type=grass magnitude_map=magnitude skip=3 grid=none
-</pre>
-<BR>
-
-<H2>SEE ALSO</H2>
-
-<EM><A HREF="d.frame.html">d.frame</A></EM><BR>
-<EM><A HREF="d.rast.html">d.rast</A></EM><BR>
-<EM><A HREF="d.rast.edit.html">d.rast.edit</A></EM><BR>
-<EM><A HREF="d.rast.num.html">d.rast.num</A></EM><BR>
-<EM><A HREF="g.region.html">g.region</A></EM><BR>
-<EM><A HREF="r.slope.aspect.html">r.slope.aspect</A></EM><BR>
-<BR>
-
-<H2>AUTHORS</H2>
-
-<u>Original author</u><BR>
-Chris Rewerts<BR>
-<em>Agricultural Engineering,<BR>
-Purdue University</em><BR><BR>
-<u>Magnitude and 360 arrow code</u><BR>
-Hamish Bowman<BR>
-<em>Department of Marine Science, <BR>
-University of Otago, New Zealand</em>
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/display/d.rast.num/d.rast.num.html (from rev 32770, grass/trunk/display/d.rast.num/description.html)
===================================================================
--- grass/trunk/display/d.rast.num/d.rast.num.html (rev 0)
+++ grass/trunk/display/d.rast.num/d.rast.num.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,46 @@
+<H2>DESCRIPTION</H2>
+
+<EM>d.rast.num</EM>
+overlays cell category values onto a raster map layer displayed
+on the user's graphics monitor.
+
+Category values will be displayed in the text color given and scaled
+to fit within a single cell. A grid outlining each map cell will also
+be overlain in a user-specified color, unless it has been set to "none".
+
+<P>
+If no grid color is given the default will be used. If no map layer
+is specified, the program will use whatever raster map layer is
+currently displayed in the active frame on the graphics monitor.
+<P>
+If the <b>-f</b> flag is given the displayed number will take on the color
+of the base map in that cell.
+
+
+<H2>NOTES</H2>
+
+The user is advised to set the current region to a relatively
+small area (i.e., less than 100 rows by 100 columns);
+otherwise, the individual cells being displayed will be small
+and the category value associated with each will be difficult to see.
+No data cells are indicated with "Null".
+
+<H2>SEE ALSO</H2>
+
+
+<em><a href="d.frame.html">d.frame</a></em>,
+<em><a href="d.grid.html">d.grid</a></em>,
+<em><a href="d.rast.html">d.rast</a></em>,
+<em><a href="d.rast.arrow.html">d.rast.arrow</a></em>,
+<em><a href="d.rast.edit.html">d.rast.edit</a></em>,
+<em><a href="g.region.html">g.region</a></em>,
+<em><a href="r.slope.aspect.html">r.slope.aspect</a></em>
+
+
+<H2>AUTHORS</H2>
+
+Raghavan Srinivasan,
+and Chris Rewerts,<BR>
+Agricultural Engineering, Purdue University
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/display/d.rast.num/description.html
===================================================================
--- grass/trunk/display/d.rast.num/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/display/d.rast.num/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,46 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-<EM>d.rast.num</EM>
-overlays cell category values onto a raster map layer displayed
-on the user's graphics monitor.
-
-Category values will be displayed in the text color given and scaled
-to fit within a single cell. A grid outlining each map cell will also
-be overlain in a user-specified color, unless it has been set to "none".
-
-<P>
-If no grid color is given the default will be used. If no map layer
-is specified, the program will use whatever raster map layer is
-currently displayed in the active frame on the graphics monitor.
-<P>
-If the <b>-f</b> flag is given the displayed number will take on the color
-of the base map in that cell.
-
-
-<H2>NOTES</H2>
-
-The user is advised to set the current region to a relatively
-small area (i.e., less than 100 rows by 100 columns);
-otherwise, the individual cells being displayed will be small
-and the category value associated with each will be difficult to see.
-No data cells are indicated with "Null".
-
-<H2>SEE ALSO</H2>
-
-
-<em><a href="d.frame.html">d.frame</a></em>,
-<em><a href="d.grid.html">d.grid</a></em>,
-<em><a href="d.rast.html">d.rast</a></em>,
-<em><a href="d.rast.arrow.html">d.rast.arrow</a></em>,
-<em><a href="d.rast.edit.html">d.rast.edit</a></em>,
-<em><a href="g.region.html">g.region</a></em>,
-<em><a href="r.slope.aspect.html">r.slope.aspect</a></em>
-
-
-<H2>AUTHORS</H2>
-
-Raghavan Srinivasan,
-and Chris Rewerts,<BR>
-Agricultural Engineering, Purdue University
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/display/d.rgb/d.rgb.html (from rev 32770, grass/trunk/display/d.rgb/description.html)
===================================================================
--- grass/trunk/display/d.rgb/d.rgb.html (rev 0)
+++ grass/trunk/display/d.rgb/d.rgb.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,94 @@
+<H2>DESCRIPTION</H2>
+
+<EM>RGB</EM> stands for red, green, and blue. This program
+visually combines three raster map layers to form a color
+image. For each layer, the corresponding component from
+the layer's color table is used (e.g. for the red layer,
+the red component is used, and so on). In general, the
+layers should use a grey-scale color table.
+
+<H2>OPTIONS</H2>
+
+<H3>Flags:</H3>
+
+<DL>
+
+<DT><B>-o</B>
+
+<DD>Overlay the resulting raster map layer onto whatever is already
+displayed in the active graphics frame. Any no-data areas in any of
+the named raster maps will seem transparent, and reveal the underlying
+image previously displayed in the graphics frame. If the <B>-o</B>
+flag is set, only cells containing non-null values will be displayed
+from the <EM>overlaid</EM> raster map. All other areas (i.e., the
+portions of the overlaid map that contain null values) will leave the
+underlying display untouched.
+
+</DL>
+
+<H3>Parameters:</H3>
+
+<DL>
+<DT><B>red=</B><EM>name</EM>
+<DD>Name of raster map layer to be used for RED component.
+<DT><B>green=</B><EM>name</EM>
+<DD>Name of raster map layer to be used for GREEN component.
+<DT><B>blue=</B><EM>name</EM>
+<DD>Name of raster map layer to be used for BLUE component.
+</DL>
+
+<H2>NOTES</H2>
+
+This is a new version of <B>d.rgb</B>, which sends the
+data to the graphics monitor in true-color RGB format.
+
+Unlike the previous version, it does not attempt to
+quantize the combined image into a fixed number of colors.
+Nor does it have an option to generate a composite layer.
+
+The image and raster map layers will not display properly
+if the graphics device does not have a reasonable sampling
+of the RGB color-space.
+<P>
+
+If color quality of satellite image color composites seems to appear poor,
+run <EM><a href="r.colors.html">r.colors</A></EM> on the selected satellite
+channels.<P>
+Example:
+<dl>
+<dd><B>r.info -r</B> <EM>image.1</EM><BR>
+<tt>min=0<BR>
+max=255</tt><BR>
+
+<dd><B>r.colors map=</B><EM>image.1</EM> <B>color=</B><EM>rules</EM>
+<< EOF<BR>
+0 black<BR>
+255 white<BR>
+EOF<BR>
+
+<dd><B>r.colors map=</B><EM>image.2</EM> <B>rast=</B><EM>image.1</EM>
+<dd><B>r.colors map=</B><EM>image.3</EM> <B>rast=</B><EM>image.1</EM>
+</dl>
+
+<EM>Note: Future GRASS versions may do this for you automatically.</EM>
+<BR><BR><BR>
+
+To write out the color composite to a R/G/B raster maps, use
+<EM><a href="r.composite.html">r.composite</A></EM>.
+
+
+<H2>SEE ALSO</H2>
+
+<EM><A HREF="d.colors.html">d.colors</A></EM><br>
+<EM><A HREF="d.colortable.html">d.colortable</A></EM><br>
+<EM><A HREF="d.his.html">d.his</A></EM><br>
+<EM><A HREF="r.blend.html">r.blend</A></EM><br>
+<EM><A HREF="r.mapcalc.html">r.mapcalc</A></EM><br>
+<EM><A HREF="r.colors.html">r.colors</A></EM><br>
+<EM><A HREF="r.composite.html">r.composite</A></EM>
+
+<H2>AUTHOR</H2>
+
+Glynn Clements
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/display/d.rgb/description.html
===================================================================
--- grass/trunk/display/d.rgb/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/display/d.rgb/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,94 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-<EM>RGB</EM> stands for red, green, and blue. This program
-visually combines three raster map layers to form a color
-image. For each layer, the corresponding component from
-the layer's color table is used (e.g. for the red layer,
-the red component is used, and so on). In general, the
-layers should use a grey-scale color table.
-
-<H2>OPTIONS</H2>
-
-<H3>Flags:</H3>
-
-<DL>
-
-<DT><B>-o</B>
-
-<DD>Overlay the resulting raster map layer onto whatever is already
-displayed in the active graphics frame. Any no-data areas in any of
-the named raster maps will seem transparent, and reveal the underlying
-image previously displayed in the graphics frame. If the <B>-o</B>
-flag is set, only cells containing non-null values will be displayed
-from the <EM>overlaid</EM> raster map. All other areas (i.e., the
-portions of the overlaid map that contain null values) will leave the
-underlying display untouched.
-
-</DL>
-
-<H3>Parameters:</H3>
-
-<DL>
-<DT><B>red=</B><EM>name</EM>
-<DD>Name of raster map layer to be used for RED component.
-<DT><B>green=</B><EM>name</EM>
-<DD>Name of raster map layer to be used for GREEN component.
-<DT><B>blue=</B><EM>name</EM>
-<DD>Name of raster map layer to be used for BLUE component.
-</DL>
-
-<H2>NOTES</H2>
-
-This is a new version of <B>d.rgb</B>, which sends the
-data to the graphics monitor in true-color RGB format.
-
-Unlike the previous version, it does not attempt to
-quantize the combined image into a fixed number of colors.
-Nor does it have an option to generate a composite layer.
-
-The image and raster map layers will not display properly
-if the graphics device does not have a reasonable sampling
-of the RGB color-space.
-<P>
-
-If color quality of satellite image color composites seems to appear poor,
-run <EM><a href="r.colors.html">r.colors</A></EM> on the selected satellite
-channels.<P>
-Example:
-<dl>
-<dd><B>r.info -r</B> <EM>image.1</EM><BR>
-<tt>min=0<BR>
-max=255</tt><BR>
-
-<dd><B>r.colors map=</B><EM>image.1</EM> <B>color=</B><EM>rules</EM>
-<< EOF<BR>
-0 black<BR>
-255 white<BR>
-EOF<BR>
-
-<dd><B>r.colors map=</B><EM>image.2</EM> <B>rast=</B><EM>image.1</EM>
-<dd><B>r.colors map=</B><EM>image.3</EM> <B>rast=</B><EM>image.1</EM>
-</dl>
-
-<EM>Note: Future GRASS versions may do this for you automatically.</EM>
-<BR><BR><BR>
-
-To write out the color composite to a R/G/B raster maps, use
-<EM><a href="r.composite.html">r.composite</A></EM>.
-
-
-<H2>SEE ALSO</H2>
-
-<EM><A HREF="d.colors.html">d.colors</A></EM><br>
-<EM><A HREF="d.colortable.html">d.colortable</A></EM><br>
-<EM><A HREF="d.his.html">d.his</A></EM><br>
-<EM><A HREF="r.blend.html">r.blend</A></EM><br>
-<EM><A HREF="r.mapcalc.html">r.mapcalc</A></EM><br>
-<EM><A HREF="r.colors.html">r.colors</A></EM><br>
-<EM><A HREF="r.composite.html">r.composite</A></EM>
-
-<H2>AUTHOR</H2>
-
-Glynn Clements
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/display/d.rhumbline/d.rhumbline.html (from rev 32770, grass/trunk/display/d.rhumbline/description.html)
===================================================================
--- grass/trunk/display/d.rhumbline/d.rhumbline.html (rev 0)
+++ grass/trunk/display/d.rhumbline/d.rhumbline.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,51 @@
+<H2>DESCRIPTION</H2>
+
+A rhumbline (loxodrome) is a line following a constant angle of the
+compass (i.e., a line of constant direction). It crosses all meridians
+at the same angle, i.e. a path of constant bearing.
+
+ <!-- There are 32
+points on the compass (points are roughly 11 degrees 15
+minutes apart). --> <EM>d.rhumbline</EM> displays the
+rhumbline joining any two user-specified points in the
+active frame on the user's graphics monitor. The named
+coordinate locations must fall within the boundaries of the
+user's current geographic region.
+
+<P>
+
+The user can run this program either interactively or
+non-interactively. If the user simply types
+<B>d.rhumbline</B> on the command line and runs it without specifying
+parameter values, the mouse will be activated and the user
+will be asked to use the mouse to indicate the two
+endpoints of the rhumbline. The rhumbline is then drawn in
+the default color (black). <!-- The program also outputs the
+coordinate locations of the two endpoints on the user's
+terminal and the number associated with the mouse button
+depressed by the user in a format useful for input to other
+programs. -->
+
+<P>
+
+Alternately, the user can specify the starting and ending
+longitude/latitude coordinates of the rhumbline and
+(optionally) the color in which the rhumbline will be
+displayed; in this case, the program will run
+non-interactively.
+
+<H2>NOTES</H2>
+
+This program works only with longitude-latitude locations.
+
+<H2>SEE ALSO</H2>
+
+<EM><A HREF="d.geodesic.html">d.geodesic</A></EM>
+
+<H2>AUTHOR</H2>
+
+Michael Shapiro,
+U.S. Army Construction Engineering
+Research Laboratory
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/display/d.rhumbline/description.html
===================================================================
--- grass/trunk/display/d.rhumbline/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/display/d.rhumbline/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,51 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-A rhumbline (loxodrome) is a line following a constant angle of the
-compass (i.e., a line of constant direction). It crosses all meridians
-at the same angle, i.e. a path of constant bearing.
-
- <!-- There are 32
-points on the compass (points are roughly 11 degrees 15
-minutes apart). --> <EM>d.rhumbline</EM> displays the
-rhumbline joining any two user-specified points in the
-active frame on the user's graphics monitor. The named
-coordinate locations must fall within the boundaries of the
-user's current geographic region.
-
-<P>
-
-The user can run this program either interactively or
-non-interactively. If the user simply types
-<B>d.rhumbline</B> on the command line and runs it without specifying
-parameter values, the mouse will be activated and the user
-will be asked to use the mouse to indicate the two
-endpoints of the rhumbline. The rhumbline is then drawn in
-the default color (black). <!-- The program also outputs the
-coordinate locations of the two endpoints on the user's
-terminal and the number associated with the mouse button
-depressed by the user in a format useful for input to other
-programs. -->
-
-<P>
-
-Alternately, the user can specify the starting and ending
-longitude/latitude coordinates of the rhumbline and
-(optionally) the color in which the rhumbline will be
-displayed; in this case, the program will run
-non-interactively.
-
-<H2>NOTES</H2>
-
-This program works only with longitude-latitude locations.
-
-<H2>SEE ALSO</H2>
-
-<EM><A HREF="d.geodesic.html">d.geodesic</A></EM>
-
-<H2>AUTHOR</H2>
-
-Michael Shapiro,
-U.S. Army Construction Engineering
-Research Laboratory
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/display/d.text.new/d.text.html (from rev 32770, grass/trunk/display/d.text.new/description.html)
===================================================================
--- grass/trunk/display/d.text.new/d.text.html (rev 0)
+++ grass/trunk/display/d.text.new/d.text.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,109 @@
+<H2>DESCRIPTION</H2>
+
+<EM>d.text</EM> draws text in the active display frame on
+the graphics monitor. Text can be provided through
+standard input or redirected from a file (using the UNIX
+redirection mechanism).
+
+In addition to the options provided on the command line,
+colors, text size, font type, rotation angle, and boldness can be adjusted
+with commands in the standard input (i.e., if the user
+invokes <EM>d.text</EM> without options on the command
+line, and then assigns values to these options on lines
+within the standard input).
+
+<H3>Commands:</H3>
+
+<DL>
+
+<DT><B>.C</B> <EM>color</EM>
+<DD>
+(where <EM>color</EM> is one of the available colors) causes text appearing on
+subsequent lines to be drawn in that color.
+
+<DT><B>.S </B> <EM>size</EM>
+<DD>
+(where <EM>size</EM> is a percentage within the range 0 to
+100) adjusts text size. Note that a size of 10 would allow
+10 lines to be drawn in the active display frame, 5 would
+allow the drawing of 20 lines, and 50 would allow the
+drawing of 2 lines.
+
+<P>
+<DT><B>.F</B> <EM>font</EM>
+<DD>
+(where <EM>font</EM> is one of the fonts known by the GRASS program
+<EM><A HREF="d.font.html">d.font</A></EM>) manipulates
+the font type. Available fonts are listed in the GRASS manual entry for
+<EM><A HREF="d.font.html">d.font</A></EM>.
+The default font type used (if unspecified by the user)
+is <EM>romans</EM>.
+<!-- Run the GRASS macro
+<EM><A HREF="show.fonts.sh.html">show.fonts.sh</A></EM>
+to see what these fonts look like. -->
+
+<DT><B>.R </B> <EM>rotation</EM>
+<DD>
+(where <EM>rotation</EM> is an angle in degrees, counter-clockwise)
+to rotate the text.
+
+<DT><B>.B 1</B>
+<DD>stipulates that following text be printed in <B>bold</B>.
+This command means <EM>bold on</EM>.
+
+<DT><B>.B 0</B>
+<DD> turns <EM>bold off</EM> of all text appearing on lines beneath
+ it. (<EM>Bold off</EM> is used by default, if unspecified by the user.)
+
+</DL>
+
+<H2>EXAMPLE</H2>
+
+The following command will print the short phrase "This is
+a test of d.text" in the active display frame using the
+color yellow, in bold, and using 4/100'ths (4%) of the
+active frame's vertical space per line:
+<P>
+
+
+<pre>
+ <B>d.text</B> << EOF
+ .C yellow
+ .S 4
+ .B 1
+ This is a test of d.text
+ EOF
+</pre>
+
+
+The user presses <EM>control-d</EM>
+(the "Ctrl" and "d" keys) to end input to <EM>d.text</EM> (equal to EOF).
+
+<H2>NOTES</H2>
+
+Note that the GRASS command
+<EM><A HREF="d.title.html">d.title</A></EM> creates map TITLEs in a format
+suitable for input to <EM>d.text</EM>.
+
+<P>
+
+<EM>d.text</EM> needs escape sequences that can be used
+within lines to change colors, boldness, and perhaps size.
+
+<H2>SEE ALSO</H2>
+
+<EM><A HREF="d.font.html">d.font</A></EM><br>
+<EM><A HREF="d.title.html">d.title</A></EM><br>
+<!-- <EM><A HREF="show.fonts.sh.html">show.fonts.sh</A></EM><br> -->
+<EM><A HREF="d.labels.html">d.labels</A></EM><br>
+
+
+<H2>AUTHOR</H2>
+
+James Westervelt,
+U.S. Army Construction Engineering
+Research Laboratory
+<P>
+Updates by Huidae Cho
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/display/d.text.new/description.html
===================================================================
--- grass/trunk/display/d.text.new/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/display/d.text.new/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,109 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-<EM>d.text</EM> draws text in the active display frame on
-the graphics monitor. Text can be provided through
-standard input or redirected from a file (using the UNIX
-redirection mechanism).
-
-In addition to the options provided on the command line,
-colors, text size, font type, rotation angle, and boldness can be adjusted
-with commands in the standard input (i.e., if the user
-invokes <EM>d.text</EM> without options on the command
-line, and then assigns values to these options on lines
-within the standard input).
-
-<H3>Commands:</H3>
-
-<DL>
-
-<DT><B>.C</B> <EM>color</EM>
-<DD>
-(where <EM>color</EM> is one of the available colors) causes text appearing on
-subsequent lines to be drawn in that color.
-
-<DT><B>.S </B> <EM>size</EM>
-<DD>
-(where <EM>size</EM> is a percentage within the range 0 to
-100) adjusts text size. Note that a size of 10 would allow
-10 lines to be drawn in the active display frame, 5 would
-allow the drawing of 20 lines, and 50 would allow the
-drawing of 2 lines.
-
-<P>
-<DT><B>.F</B> <EM>font</EM>
-<DD>
-(where <EM>font</EM> is one of the fonts known by the GRASS program
-<EM><A HREF="d.font.html">d.font</A></EM>) manipulates
-the font type. Available fonts are listed in the GRASS manual entry for
-<EM><A HREF="d.font.html">d.font</A></EM>.
-The default font type used (if unspecified by the user)
-is <EM>romans</EM>.
-<!-- Run the GRASS macro
-<EM><A HREF="show.fonts.sh.html">show.fonts.sh</A></EM>
-to see what these fonts look like. -->
-
-<DT><B>.R </B> <EM>rotation</EM>
-<DD>
-(where <EM>rotation</EM> is an angle in degrees, counter-clockwise)
-to rotate the text.
-
-<DT><B>.B 1</B>
-<DD>stipulates that following text be printed in <B>bold</B>.
-This command means <EM>bold on</EM>.
-
-<DT><B>.B 0</B>
-<DD> turns <EM>bold off</EM> of all text appearing on lines beneath
- it. (<EM>Bold off</EM> is used by default, if unspecified by the user.)
-
-</DL>
-
-<H2>EXAMPLE</H2>
-
-The following command will print the short phrase "This is
-a test of d.text" in the active display frame using the
-color yellow, in bold, and using 4/100'ths (4%) of the
-active frame's vertical space per line:
-<P>
-
-
-<pre>
- <B>d.text</B> << EOF
- .C yellow
- .S 4
- .B 1
- This is a test of d.text
- EOF
-</pre>
-
-
-The user presses <EM>control-d</EM>
-(the "Ctrl" and "d" keys) to end input to <EM>d.text</EM> (equal to EOF).
-
-<H2>NOTES</H2>
-
-Note that the GRASS command
-<EM><A HREF="d.title.html">d.title</A></EM> creates map TITLEs in a format
-suitable for input to <EM>d.text</EM>.
-
-<P>
-
-<EM>d.text</EM> needs escape sequences that can be used
-within lines to change colors, boldness, and perhaps size.
-
-<H2>SEE ALSO</H2>
-
-<EM><A HREF="d.font.html">d.font</A></EM><br>
-<EM><A HREF="d.title.html">d.title</A></EM><br>
-<!-- <EM><A HREF="show.fonts.sh.html">show.fonts.sh</A></EM><br> -->
-<EM><A HREF="d.labels.html">d.labels</A></EM><br>
-
-
-<H2>AUTHOR</H2>
-
-James Westervelt,
-U.S. Army Construction Engineering
-Research Laboratory
-<P>
-Updates by Huidae Cho
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/display/d.thematic.area/d.thematic.area.html (from rev 32770, grass/trunk/display/d.thematic.area/description.html)
===================================================================
--- grass/trunk/display/d.thematic.area/d.thematic.area.html (rev 0)
+++ grass/trunk/display/d.thematic.area/d.thematic.area.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,31 @@
+<H2>DESCRIPTION</H2>
+
+<em>d.thematic.area</em> draws thematic coropleth vector maps based on an attribute column or an expression involving several columns. It takes a list of class breaks (excluding the minimum and maximum values) and a list of colors to apply to the classes (has to be the number of class breaks + 1).
+
+Instead of a list of class breaks, the user can also chose a classification algorithm and a number of classes. See the v.class man page for more information on these different algorithms.
+
+The <em>-l</em> flag instructs the module to print legend information (class min | class max | number of observations in class | color) to standard output for futher use in graphical software. When combined with the <em>-e</em> flag, the legend information will be extended with some additional statistical information. If the <em>-n</em> flag is set, the module will only print the legend information without drawing the map. If the user gives a <em>legendfile</em>, the module will write d.graph instructions for painting a legend into that file.
+
+
+<H2>EXAMPLE</H2>
+
+<div class="code"><pre>
+d.thematic.area -l map=communes3 data=pop breaks=111393.250000,222785.500000,334177.750000 colors=255:0:0,0:255:0,0:0:255,0,0,0
+</pre></div>
+
+The following example uses a calculated attribute (density = pop/area) and the standard deviation algorithm to calculate class breaks for 5 classes:
+<div class="code"><pre>
+d.thematic.area -l map=communes2 data=pop/area algorithm=std nbclasses=5 colors=0:0:255,50:100:255,255:100:50,255:0:0,156:0:0
+</pre></div>
+
+<H2>SEE ALSO</H2>
+
+<EM><A HREF="v.class.html">v.class</A></EM>
+<EM><A HREF="d.vect.html">d.vect</A></EM>
+<EM><A HREF="d.graph.html">d.graph</A></EM>
+<EM><A HREF="v.univar.html">v.univar</A></EM>
+
+
+<H2>AUTHOR</H2>
+
+Moritz Lennert
Deleted: grass/trunk/display/d.thematic.area/description.html
===================================================================
--- grass/trunk/display/d.thematic.area/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/display/d.thematic.area/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,31 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-<em>d.thematic.area</em> draws thematic coropleth vector maps based on an attribute column or an expression involving several columns. It takes a list of class breaks (excluding the minimum and maximum values) and a list of colors to apply to the classes (has to be the number of class breaks + 1).
-
-Instead of a list of class breaks, the user can also chose a classification algorithm and a number of classes. See the v.class man page for more information on these different algorithms.
-
-The <em>-l</em> flag instructs the module to print legend information (class min | class max | number of observations in class | color) to standard output for futher use in graphical software. When combined with the <em>-e</em> flag, the legend information will be extended with some additional statistical information. If the <em>-n</em> flag is set, the module will only print the legend information without drawing the map. If the user gives a <em>legendfile</em>, the module will write d.graph instructions for painting a legend into that file.
-
-
-<H2>EXAMPLE</H2>
-
-<div class="code"><pre>
-d.thematic.area -l map=communes3 data=pop breaks=111393.250000,222785.500000,334177.750000 colors=255:0:0,0:255:0,0:0:255,0,0,0
-</pre></div>
-
-The following example uses a calculated attribute (density = pop/area) and the standard deviation algorithm to calculate class breaks for 5 classes:
-<div class="code"><pre>
-d.thematic.area -l map=communes2 data=pop/area algorithm=std nbclasses=5 colors=0:0:255,50:100:255,255:100:50,255:0:0,156:0:0
-</pre></div>
-
-<H2>SEE ALSO</H2>
-
-<EM><A HREF="v.class.html">v.class</A></EM>
-<EM><A HREF="d.vect.html">d.vect</A></EM>
-<EM><A HREF="d.graph.html">d.graph</A></EM>
-<EM><A HREF="v.univar.html">v.univar</A></EM>
-
-
-<H2>AUTHOR</H2>
-
-Moritz Lennert
Copied: grass/trunk/display/d.title/d.title.html (from rev 32770, grass/trunk/display/d.title/description.html)
===================================================================
--- grass/trunk/display/d.title/d.title.html (rev 0)
+++ grass/trunk/display/d.title/d.title.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,62 @@
+<H2>DESCRIPTION</H2>
+
+<EM>d.title</EM> generates to standard output a string which can be used by
+<EM><A HREF="d.text.html">d.text</A></EM> to draw a TITLE for the raster map
+layer <EM>name</EM> in the active display frame on the graphics monitor.
+Output created by <EM>d.title</EM> can be redirected into a file, or piped
+directly into <EM><A HREF="d.text.html">d.text</A></EM> to display the map
+TITLE created by <EM>d.title</EM>. The map TITLE created will include the
+map layer's name, TITLE, MAPSET, LOCATION_NAME, geographic region boundary
+coordinates, and cell resolution.
+If the <b>-d</b> draw flag is used, then <EM>d.title</EM> will call
+<EM>d.text</EM> for you and the title will be automatically rendered
+to the display.
+
+
+<H2>NOTES</H2>
+
+The text created with
+<EM><A HREF="d.text.html">d.text</A></EM>
+will not necessarily fit within the
+active display frame on the graphics monitor;
+the user should choose a text size appropriate to this frame.
+
+
+<H2>EXAMPLES</H2>
+
+For example, a user wishing to create a suitable TITLE for the
+Spearfish, SD <EM>soils</EM> map layer and to display this TITLE in the
+active display frame on the graphics monitor might type the following:
+<DL>
+<DD> <B>d.title map=</B><EM>soils</EM> <B>color=</B><EM>red</EM> <B>size=</B><EM>5</EM> <B>> TITLE.file</B>
+<DD> <B><A HREF="d.text.html">d.text</A> < TITLE.file</B>
+</DL>
+Alternately, the user might pipe <EM>d.title</EM> output directly
+into <EM><A HREF="d.text.html">d.text</A>:</EM>
+<DL>
+<DD>
+<B>d.title map=</B><EM>soils</EM> <B>color=</B><EM>red</EM> <B>size=</B><EM>5</EM> |
+<A HREF="d.text.html">d.text</A>
+</DL>
+
+<P>
+A file created by <EM>d.title</EM> can be displayed
+with <EM><A HREF="d.text.html">d.text</A></EM>.
+Information contained in this file takes precedence over the
+<EM>color</EM> and <EM>size</EM> parameters for
+<EM><A HREF="d.text.html">d.text</A></EM>.
+
+
+<H2>SEE ALSO</H2>
+
+<EM><A HREF="d.font.html">d.font</A></EM><br>
+<EM><A HREF="d.text.html">d.text</A></EM><br>
+
+
+<H2>AUTHOR</H2>
+James Westervelt,
+U.S. Army Construction Engineering
+Research Laboratory
+
+<p>
+<i>Last changed: $Date$</i>
Deleted: grass/trunk/display/d.title/description.html
===================================================================
--- grass/trunk/display/d.title/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/display/d.title/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,62 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-<EM>d.title</EM> generates to standard output a string which can be used by
-<EM><A HREF="d.text.html">d.text</A></EM> to draw a TITLE for the raster map
-layer <EM>name</EM> in the active display frame on the graphics monitor.
-Output created by <EM>d.title</EM> can be redirected into a file, or piped
-directly into <EM><A HREF="d.text.html">d.text</A></EM> to display the map
-TITLE created by <EM>d.title</EM>. The map TITLE created will include the
-map layer's name, TITLE, MAPSET, LOCATION_NAME, geographic region boundary
-coordinates, and cell resolution.
-If the <b>-d</b> draw flag is used, then <EM>d.title</EM> will call
-<EM>d.text</EM> for you and the title will be automatically rendered
-to the display.
-
-
-<H2>NOTES</H2>
-
-The text created with
-<EM><A HREF="d.text.html">d.text</A></EM>
-will not necessarily fit within the
-active display frame on the graphics monitor;
-the user should choose a text size appropriate to this frame.
-
-
-<H2>EXAMPLES</H2>
-
-For example, a user wishing to create a suitable TITLE for the
-Spearfish, SD <EM>soils</EM> map layer and to display this TITLE in the
-active display frame on the graphics monitor might type the following:
-<DL>
-<DD> <B>d.title map=</B><EM>soils</EM> <B>color=</B><EM>red</EM> <B>size=</B><EM>5</EM> <B>> TITLE.file</B>
-<DD> <B><A HREF="d.text.html">d.text</A> < TITLE.file</B>
-</DL>
-Alternately, the user might pipe <EM>d.title</EM> output directly
-into <EM><A HREF="d.text.html">d.text</A>:</EM>
-<DL>
-<DD>
-<B>d.title map=</B><EM>soils</EM> <B>color=</B><EM>red</EM> <B>size=</B><EM>5</EM> |
-<A HREF="d.text.html">d.text</A>
-</DL>
-
-<P>
-A file created by <EM>d.title</EM> can be displayed
-with <EM><A HREF="d.text.html">d.text</A></EM>.
-Information contained in this file takes precedence over the
-<EM>color</EM> and <EM>size</EM> parameters for
-<EM><A HREF="d.text.html">d.text</A></EM>.
-
-
-<H2>SEE ALSO</H2>
-
-<EM><A HREF="d.font.html">d.font</A></EM><br>
-<EM><A HREF="d.text.html">d.text</A></EM><br>
-
-
-<H2>AUTHOR</H2>
-James Westervelt,
-U.S. Army Construction Engineering
-Research Laboratory
-
-<p>
-<i>Last changed: $Date$</i>
Copied: grass/trunk/display/d.vect/d.vect.html (from rev 32770, grass/trunk/display/d.vect/description.html)
===================================================================
--- grass/trunk/display/d.vect/d.vect.html (rev 0)
+++ grass/trunk/display/d.vect/d.vect.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,107 @@
+<h2>DESCRIPTION</h2>
+
+<em>d.vect</em> displays GRASS vector data in the active frame on the graphics
+monitor.
+
+<h2>NOTES</h2>
+
+<em>d.vect</em> can simply be used typing <tt><b>d.vect map=</b>vector_map</tt>.
+There are a large variety of optional parameters which allow the user to
+specify vector type, colors, data fields, SQL queries, label size and
+justification, etc.
+<P>
+By default <em>d.vect</em> fills in holes in polygons (islands).
+If you only want to show active areas limit the features with, e.g.,
+"<tt>d.vect cats=1-999999</tt>".
+<P>
+In order to display attributes in the map, <em>display=attr</em> must be
+specified in addition to the column name (<em>attrcol</em> parameter).
+
+<P>
+Colors may be specified in an attribute table column
+named 'GRASSRGB' (which is a <tt>varchar(11)</tt> column containing <tt>RRR:GGG:BBB</tt> values),
+see the flag <em>-a</em>.
+<P>
+A table for a vector map might look like this:
+
+<div class="code"><pre>
+echo "select * from testisola" | db.select
+cat|label|GRASSRGB
+0|no data|255:255:255
+90|FRASSILONGO|23:245:67
+104|LEVICO|23:145:67
+139|PERGINE VALSUGANA|223:45:237
+168|SANT'ORSOLA|223:45:67
+190|TENNA|123:45:67
+</pre></div>
+<P>
+To add the GRASSRGB color column, use <em>v.db.addcol</em>:
+<div class="code"><pre>
+v.db.addcol testisola col="GRASSRGB varchar(11)"
+</pre></div>
+<P>
+To add/change a color, use <em>v.db.update</em>:
+<div class="code"><pre>
+v.db.update testisola col=GRASSRGB val="123:45:237" where="cat=139"
+</pre></div>
+<P>
+A much simpler method of color coding is by using the <em>-c</em> flag which
+displays vector elements of like category number with a random color.
+<P>
+This module can use FreeType/TrueType fonts if they have already been selected with
+<em>d.font</em>.
+
+<h2>EXAMPLES</h2>
+
+Spearfish examples:
+
+<div class="code"><pre>
+# display roads with category numbers:
+d.vect roads display=shape,cat lcolor=green
+
+# display randomly colorized soils map with attributes
+d.vect -c soils disp=attr attrcol=label
+
+# display randomly colorized selected vectors from soils map
+d.vect -c soils where="label='VBF'" display=shape,attr attrcol=label
+</pre></div>
+
+<p>
+3D points, 3D lines and 3D polygons colorized according to z height:
+<div class="code"><pre>
+g.region rast=elevation.10m
+r.random elevation.10m n=5000 vector=random3d -d
+d.mon x0
+# display as black points
+d.vect random3d
+# display 3D points colorized according to z height
+d.vect -z random3d zcol=gyr
+
+# 3D contour lines
+r.contour elevation.10m out=contour20m step=20
+d.vect -z contour20m zcol=gyr
+
+# generate 3D triangles
+v.delaunay random3d out=random3d_del
+# display 3D polygons colorized according to z height
+d.vect -z random3d_del type=area zcol=gyr
+</pre></div>
+
+<h2>SEE ALSO</h2>
+
+<em>
+<a HREF="d.erase.html">d.erase</a>,
+<a HREF="d.what.vect.html">d.what.vect</a>,
+<a HREF="d.rast.html">d.rast</a>,
+<a HREF="v.db.addcol.html">v.db.addcol</a>
+<a HREF="v.db.update.html">v.db.update</a><br>
+<a HREF="sql.html">GRASS SQL interface</a>
+</em>
+
+<h2>AUTHORS</h2>
+
+CERL<br>
+Radim Blazek, ITC-Irst, Trento, Italy<br>
+other GRASS developers
+
+<p><i>Last changed: $Date$</i><p>
Deleted: grass/trunk/display/d.vect/description.html
===================================================================
--- grass/trunk/display/d.vect/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/display/d.vect/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,107 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>d.vect</em> displays GRASS vector data in the active frame on the graphics
-monitor.
-
-<h2>NOTES</h2>
-
-<em>d.vect</em> can simply be used typing <tt><b>d.vect map=</b>vector_map</tt>.
-There are a large variety of optional parameters which allow the user to
-specify vector type, colors, data fields, SQL queries, label size and
-justification, etc.
-<P>
-By default <em>d.vect</em> fills in holes in polygons (islands).
-If you only want to show active areas limit the features with, e.g.,
-"<tt>d.vect cats=1-999999</tt>".
-<P>
-In order to display attributes in the map, <em>display=attr</em> must be
-specified in addition to the column name (<em>attrcol</em> parameter).
-
-<P>
-Colors may be specified in an attribute table column
-named 'GRASSRGB' (which is a <tt>varchar(11)</tt> column containing <tt>RRR:GGG:BBB</tt> values),
-see the flag <em>-a</em>.
-<P>
-A table for a vector map might look like this:
-
-<div class="code"><pre>
-echo "select * from testisola" | db.select
-cat|label|GRASSRGB
-0|no data|255:255:255
-90|FRASSILONGO|23:245:67
-104|LEVICO|23:145:67
-139|PERGINE VALSUGANA|223:45:237
-168|SANT'ORSOLA|223:45:67
-190|TENNA|123:45:67
-</pre></div>
-<P>
-To add the GRASSRGB color column, use <em>v.db.addcol</em>:
-<div class="code"><pre>
-v.db.addcol testisola col="GRASSRGB varchar(11)"
-</pre></div>
-<P>
-To add/change a color, use <em>v.db.update</em>:
-<div class="code"><pre>
-v.db.update testisola col=GRASSRGB val="123:45:237" where="cat=139"
-</pre></div>
-<P>
-A much simpler method of color coding is by using the <em>-c</em> flag which
-displays vector elements of like category number with a random color.
-<P>
-This module can use FreeType/TrueType fonts if they have already been selected with
-<em>d.font</em>.
-
-<h2>EXAMPLES</h2>
-
-Spearfish examples:
-
-<div class="code"><pre>
-# display roads with category numbers:
-d.vect roads display=shape,cat lcolor=green
-
-# display randomly colorized soils map with attributes
-d.vect -c soils disp=attr attrcol=label
-
-# display randomly colorized selected vectors from soils map
-d.vect -c soils where="label='VBF'" display=shape,attr attrcol=label
-</pre></div>
-
-<p>
-3D points, 3D lines and 3D polygons colorized according to z height:
-<div class="code"><pre>
-g.region rast=elevation.10m
-r.random elevation.10m n=5000 vector=random3d -d
-d.mon x0
-# display as black points
-d.vect random3d
-# display 3D points colorized according to z height
-d.vect -z random3d zcol=gyr
-
-# 3D contour lines
-r.contour elevation.10m out=contour20m step=20
-d.vect -z contour20m zcol=gyr
-
-# generate 3D triangles
-v.delaunay random3d out=random3d_del
-# display 3D polygons colorized according to z height
-d.vect -z random3d_del type=area zcol=gyr
-</pre></div>
-
-<h2>SEE ALSO</h2>
-
-<em>
-<a HREF="d.erase.html">d.erase</a>,
-<a HREF="d.what.vect.html">d.what.vect</a>,
-<a HREF="d.rast.html">d.rast</a>,
-<a HREF="v.db.addcol.html">v.db.addcol</a>
-<a HREF="v.db.update.html">v.db.update</a><br>
-<a HREF="sql.html">GRASS SQL interface</a>
-</em>
-
-<h2>AUTHORS</h2>
-
-CERL<br>
-Radim Blazek, ITC-Irst, Trento, Italy<br>
-other GRASS developers
-
-<p><i>Last changed: $Date$</i><p>
Copied: grass/trunk/display/d.vect.chart/d.vect.chart.html (from rev 32770, grass/trunk/display/d.vect.chart/description.html)
===================================================================
--- grass/trunk/display/d.vect.chart/d.vect.chart.html (rev 0)
+++ grass/trunk/display/d.vect.chart/d.vect.chart.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,54 @@
+<h2>DESCRIPTION</h2>
+
+<em>d.vect.chart</em> displays charts for GRASS vector data in the active frame on the graphics
+monitor.
+
+<h2>NOTES</h2>
+
+The charts are positioned as follows:
+<ul>
+<li> vector points: on point position
+<li> vector lines: on line centers
+<li> vector areas: on area centroids
+</ul>
+
+Bar charts are placed with their lower edge starting from the y-coordinate of the feature being symbolized, and centered with respect to the x-coordinate. The <b>-c</b> flag can be used to center the bar chart in both x and y directions.
+<br><br>
+The 'sizecol' parameter is proportionate to the radius.
+<br><br>
+The optional <b>max_ref</b> parameter accepts a list of values that represent the maximum value for each column listed in the values for the parameter <b>columns</b>. These values are used to create a framed bar plot if <b>ctype</b> is <em>bar</em> (See Example 2).
+<h2>EXAMPLES</h2>
+
+<h3>Example 1</h3>
+<div class="code"><pre>
+d.vect.chart map=vectmap columns=cens51,cens61,cens71,cens81
+</pre></div>
+
+<h3>Example 2</h3>
+
+Create framed bar graphs of an erodibiliy index from the SPEARFISH dataset.
+<div class="code"><pre>
+r.to.vect -s -v in=erode.index out=erode_index feature=area
+v.extract in=erode_index out=erode_index_ctrds type=centroid
+d.rast aspect
+d.vect.chart map=erode_index_ctrds ctype=bar columns=cat \
+ size=10 max_ref=12 scale=1.5 colors=yellow
+d.vect erode_index_ctrds icon=basic/circle fcol=black col=black size=5
+</pre></div>
+
+Example screenshot (zoomed):<br>
+<img src="d.vect.chart_example.jpg" alt="d.vect.chart example">
+
+<h2>SEE ALSO</h2>
+
+<em><a HREF="d.erase.html">d.erase</a>,
+<a HREF="d.vect.html">d.vect</a>,
+<a href="d.vect.thematic.html">d.vect.thematic</a>,
+<a HREF="d.what.vect.html">d.what.vect</a>,
+<a HREF="d.rast.html">d.rast</a></em>
+
+<h2>AUTHOR</h2>
+
+Radim Blazek, ITC-Irst, Trento, Italy
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/display/d.vect.chart/description.html
===================================================================
--- grass/trunk/display/d.vect.chart/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/display/d.vect.chart/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,54 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>d.vect.chart</em> displays charts for GRASS vector data in the active frame on the graphics
-monitor.
-
-<h2>NOTES</h2>
-
-The charts are positioned as follows:
-<ul>
-<li> vector points: on point position
-<li> vector lines: on line centers
-<li> vector areas: on area centroids
-</ul>
-
-Bar charts are placed with their lower edge starting from the y-coordinate of the feature being symbolized, and centered with respect to the x-coordinate. The <b>-c</b> flag can be used to center the bar chart in both x and y directions.
-<br><br>
-The 'sizecol' parameter is proportionate to the radius.
-<br><br>
-The optional <b>max_ref</b> parameter accepts a list of values that represent the maximum value for each column listed in the values for the parameter <b>columns</b>. These values are used to create a framed bar plot if <b>ctype</b> is <em>bar</em> (See Example 2).
-<h2>EXAMPLES</h2>
-
-<h3>Example 1</h3>
-<div class="code"><pre>
-d.vect.chart map=vectmap columns=cens51,cens61,cens71,cens81
-</pre></div>
-
-<h3>Example 2</h3>
-
-Create framed bar graphs of an erodibiliy index from the SPEARFISH dataset.
-<div class="code"><pre>
-r.to.vect -s -v in=erode.index out=erode_index feature=area
-v.extract in=erode_index out=erode_index_ctrds type=centroid
-d.rast aspect
-d.vect.chart map=erode_index_ctrds ctype=bar columns=cat \
- size=10 max_ref=12 scale=1.5 colors=yellow
-d.vect erode_index_ctrds icon=basic/circle fcol=black col=black size=5
-</pre></div>
-
-Example screenshot (zoomed):<br>
-<img src="d.vect.chart_example.jpg" alt="d.vect.chart example">
-
-<h2>SEE ALSO</h2>
-
-<em><a HREF="d.erase.html">d.erase</a>,
-<a HREF="d.vect.html">d.vect</a>,
-<a href="d.vect.thematic.html">d.vect.thematic</a>,
-<a HREF="d.what.vect.html">d.what.vect</a>,
-<a HREF="d.rast.html">d.rast</a></em>
-
-<h2>AUTHOR</h2>
-
-Radim Blazek, ITC-Irst, Trento, Italy
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/display/d.what.rast/d.what.rast.html (from rev 32770, grass/trunk/display/d.what.rast/description.html)
===================================================================
--- grass/trunk/display/d.what.rast/d.what.rast.html (rev 0)
+++ grass/trunk/display/d.what.rast/d.what.rast.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,160 @@
+<h2>DESCRIPTION</h2>
+
+<em>d.what.rast</em> outputs the category values and labels
+associated with cell(s) at user-specified location(s) on
+user-named raster map layer(s).
+
+<p>
+
+The program will query the contents of raster map layer(s)
+named by the user on the command line. These map layers
+must exist in the user's current mapset search path. If
+the user does not name any raster map layers on the command
+line, <em>d.what.rast</em> will query the category contents
+of whatever raster map layer is already displayed in the
+active frame on the graphics monitor.
+
+<p>
+
+The program activates the mouse, and expects the user to
+indicate the cell location(s) to be queried by depressing a
+mouse button over desired location(s) within the current
+geographic region in the active display frame on the
+graphic monitor.
+
+<h2>EXAMPLE</h2>
+
+It is helpful, but not necessary, to first display a map to
+be used for reference in the active display frame before
+running <em>d.what.rast</em>. For example, the user might
+type the following series of commands and receive the
+output below.
+
+<p>
+
+<dl>
+<dt><b>d.rast map=</b><em>soils</em>
+<p>
+<dd>To first display the <em>soils</em> map in the active frame.</dd>
+</dl>
+
+<p>
+<dl>
+<dt><b>d.what.rast map=</b><em>soils,aspect</em><br>
+<p>
+<dd>User then moves the mouse to desired location on the
+displayed <em>soils</em> map layer, and presses the left
+mouse button to query the category contents of the
+<em>soils</em> and <em>aspect</em> maps at this geographic
+location. The program then outputs the below information
+to the user's terminal.</dd>
+</dl>
+
+<pre>
+617112(E) 3732014(N)
+soils in PERMANENT (44)Nunn clay loam, NdC
+aspect in PERMANENT (20)15 degrees north of west
+</pre>
+
+<p>
+The first line of output gives the easting (E) and northing (N) coordinates
+of the geographic location at which the user clicked the mouse.
+Subsequent lines give the selected map(s) name and mapset, map category value
+(within parentheses), and map category label corresponding to this
+user-selected map location.
+
+<p>
+
+The query may be repeated as often as desired using the
+left mouse button. The right button on the mouse is used
+to quit the <em>d.what.rast</em> session.
+
+<p>
+
+Users can set the <b>-t</b> flag to obtain a terse output
+from <em>d.what.rast</em>. This is useful when the user
+wishes output to be parsed by another program (like
+<em>awk</em>). If the <b>-t</b> flag is set, users can also
+select the field separator used (with the
+<b>fs=</b><em>name</em> option), or elect to use the
+default <b>:</b> field separator. In this case, the
+command
+
+<p>
+
+<dl>
+<dt><b>d.what.rast -t map=</b><em>soils,aspect</em>
+<p>
+<dd> produces output in the form shown below. The first line of
+output gives the easting, northing, and the mouse button
+return value (see NOTES below). Each
+subsequent line gives the map name and its mapset, the
+category value, and category label of the point specified
+on the user-named raster map layers. The default output
+field separator, a colon, is used since none was specified
+on the command line.</dd>
+</dl>
+
+<pre>
+617112:3732014:1
+soils at PERMANENT:44:Nunn clay loam, NdC
+aspect at PERMANENT:20:15 degrees north of west
+</pre>
+
+<p>
+
+Users can also use this program inside of shell scripts
+that require as input a map category value and a mouse
+button depressed. Users can choose an option to run
+<em>d.what.rast</em> only once, and return only the map
+category value found and the number of the mouse button
+depressed.
+
+<h2>NOTES</h2></a>
+
+Mouse button return values are as follows: 0 indicates no
+button was pressed, 1 indicates that the left mouse button
+was pressed, 2 indicates the middle button was pressed, and
+3 indicates that the right mouse button was pressed.
+
+<p>
+
+<em>d.what.rast</em> will always print its output to the
+terminal screen. <em>d.what.rast</em> output can be
+redirected into a file; however, if it is, the output will
+go both to the screen and to the file. For example:
+
+<p>
+
+<dl>
+<dt><b>d.what.rast map=</b><em>soils,aspect</em><b> > what.out</b>
+<p>
+<dd>will both send <em>d.what.rast</em> output to the screen
+and capture its output in the file named
+<em>what.out</em>.</dd>
+</dl>
+
+<p>
+
+The maximum number of raster map layers that can be queried at one time is 15.
+
+<p>
+
+<em><a HREF="d.what.vect.html">d.what.vect</a></em>
+allows the user to interactively query the category
+contents of multiple vector map layers at user-specified
+locations.
+
+<h2>SEE ALSO</h2>
+
+<em><a HREF="d.rast.html">d.rast</a></em><br>
+<em><a HREF="d.what.vect.html">d.what.vect</a></em><br>
+<em><a HREF="g.region.html">g.region</a></em><br>
+
+<h2>AUTHOR</h2>
+
+Michael Shapiro,
+U.S. Army Construction Engineering
+Research Laboratory
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/display/d.what.rast/description.html
===================================================================
--- grass/trunk/display/d.what.rast/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/display/d.what.rast/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,160 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>d.what.rast</em> outputs the category values and labels
-associated with cell(s) at user-specified location(s) on
-user-named raster map layer(s).
-
-<p>
-
-The program will query the contents of raster map layer(s)
-named by the user on the command line. These map layers
-must exist in the user's current mapset search path. If
-the user does not name any raster map layers on the command
-line, <em>d.what.rast</em> will query the category contents
-of whatever raster map layer is already displayed in the
-active frame on the graphics monitor.
-
-<p>
-
-The program activates the mouse, and expects the user to
-indicate the cell location(s) to be queried by depressing a
-mouse button over desired location(s) within the current
-geographic region in the active display frame on the
-graphic monitor.
-
-<h2>EXAMPLE</h2>
-
-It is helpful, but not necessary, to first display a map to
-be used for reference in the active display frame before
-running <em>d.what.rast</em>. For example, the user might
-type the following series of commands and receive the
-output below.
-
-<p>
-
-<dl>
-<dt><b>d.rast map=</b><em>soils</em>
-<p>
-<dd>To first display the <em>soils</em> map in the active frame.</dd>
-</dl>
-
-<p>
-<dl>
-<dt><b>d.what.rast map=</b><em>soils,aspect</em><br>
-<p>
-<dd>User then moves the mouse to desired location on the
-displayed <em>soils</em> map layer, and presses the left
-mouse button to query the category contents of the
-<em>soils</em> and <em>aspect</em> maps at this geographic
-location. The program then outputs the below information
-to the user's terminal.</dd>
-</dl>
-
-<pre>
-617112(E) 3732014(N)
-soils in PERMANENT (44)Nunn clay loam, NdC
-aspect in PERMANENT (20)15 degrees north of west
-</pre>
-
-<p>
-The first line of output gives the easting (E) and northing (N) coordinates
-of the geographic location at which the user clicked the mouse.
-Subsequent lines give the selected map(s) name and mapset, map category value
-(within parentheses), and map category label corresponding to this
-user-selected map location.
-
-<p>
-
-The query may be repeated as often as desired using the
-left mouse button. The right button on the mouse is used
-to quit the <em>d.what.rast</em> session.
-
-<p>
-
-Users can set the <b>-t</b> flag to obtain a terse output
-from <em>d.what.rast</em>. This is useful when the user
-wishes output to be parsed by another program (like
-<em>awk</em>). If the <b>-t</b> flag is set, users can also
-select the field separator used (with the
-<b>fs=</b><em>name</em> option), or elect to use the
-default <b>:</b> field separator. In this case, the
-command
-
-<p>
-
-<dl>
-<dt><b>d.what.rast -t map=</b><em>soils,aspect</em>
-<p>
-<dd> produces output in the form shown below. The first line of
-output gives the easting, northing, and the mouse button
-return value (see NOTES below). Each
-subsequent line gives the map name and its mapset, the
-category value, and category label of the point specified
-on the user-named raster map layers. The default output
-field separator, a colon, is used since none was specified
-on the command line.</dd>
-</dl>
-
-<pre>
-617112:3732014:1
-soils at PERMANENT:44:Nunn clay loam, NdC
-aspect at PERMANENT:20:15 degrees north of west
-</pre>
-
-<p>
-
-Users can also use this program inside of shell scripts
-that require as input a map category value and a mouse
-button depressed. Users can choose an option to run
-<em>d.what.rast</em> only once, and return only the map
-category value found and the number of the mouse button
-depressed.
-
-<h2>NOTES</h2></a>
-
-Mouse button return values are as follows: 0 indicates no
-button was pressed, 1 indicates that the left mouse button
-was pressed, 2 indicates the middle button was pressed, and
-3 indicates that the right mouse button was pressed.
-
-<p>
-
-<em>d.what.rast</em> will always print its output to the
-terminal screen. <em>d.what.rast</em> output can be
-redirected into a file; however, if it is, the output will
-go both to the screen and to the file. For example:
-
-<p>
-
-<dl>
-<dt><b>d.what.rast map=</b><em>soils,aspect</em><b> > what.out</b>
-<p>
-<dd>will both send <em>d.what.rast</em> output to the screen
-and capture its output in the file named
-<em>what.out</em>.</dd>
-</dl>
-
-<p>
-
-The maximum number of raster map layers that can be queried at one time is 15.
-
-<p>
-
-<em><a HREF="d.what.vect.html">d.what.vect</a></em>
-allows the user to interactively query the category
-contents of multiple vector map layers at user-specified
-locations.
-
-<h2>SEE ALSO</h2>
-
-<em><a HREF="d.rast.html">d.rast</a></em><br>
-<em><a HREF="d.what.vect.html">d.what.vect</a></em><br>
-<em><a HREF="g.region.html">g.region</a></em><br>
-
-<h2>AUTHOR</h2>
-
-Michael Shapiro,
-U.S. Army Construction Engineering
-Research Laboratory
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/display/d.what.vect/d.what.vect.html (from rev 32770, grass/trunk/display/d.what.vect/description.html)
===================================================================
--- grass/trunk/display/d.what.vect/d.what.vect.html (rev 0)
+++ grass/trunk/display/d.what.vect/d.what.vect.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,57 @@
+<h2>DESCRIPTION</h2>
+
+<em>d.what.vect</em>
+outputs the category value(s) associated with user-specified location(s)
+in user-specified vector map layer(s).
+
+<p>
+
+The program activates the mouse, and expects the user to indicate the
+location(s) to be queried by depressing a mouse button over desired location(s)
+within the current geographic region in the active display frame on the
+graphic monitor. Query results from map(s) are by default displayed in a new
+monitor, where label values can be added or changed. Using parameter <b>-x</b>
+informations will be displayed as plain text to terminal window.
+
+<h2>EXAMPLE</h2>
+
+A sample <em>d.what.vect</em> session is given below. Although it is not
+necessary that the user first displays a vector map to be queried in the
+active display frame, it is helpful to have a map displayed there for
+reference.
+
+<p>
+
+<b>d.vect map=</b><em>roads</em><p>
+Displays the <em>roads</em> vector map layer on the graphics monitor.
+<p>
+
+<b>d.what.vect map=</b><em>roads,geology</em><p>
+After typing this, the user moves the mouse to a desired location
+on the displayed <em>roads</em> map layer, and presses the left mouse
+button to query the category value of the <em>roads</em> and the
+<em>geology</em> vector map at this location.
+
+The program then outputs the category value of a line type corresponding
+to this user-selected map location, for the vector map queried by the user.
+
+<p>
+
+The query may be repeated as often as desired using the left mouse button. The
+middle mouse button toggles the flash color.
+The right button on the mouse is used to quit the <em>d.what.vect</em> session.
+
+<h2>SEE ALSO</h2>
+
+<em><a HREF="d.rast.html">d.rast</a></em><br>
+<em><a HREF="d.vect.html">d.vect</a></em><br>
+<em><a HREF="d.what.rast.html">d.what.rast</a></em><br>
+<em><a HREF="g.region.html">g.region</a></em><br>
+
+<h2>AUTHOR</h2>
+
+Jim Hinthorne,
+Central Washington University<br>
+Upgrades by Dennis Finch, National Park Service and Radim Blazek, ITC-Irst, Trento, Italy
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/display/d.what.vect/description.html
===================================================================
--- grass/trunk/display/d.what.vect/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/display/d.what.vect/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,57 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>d.what.vect</em>
-outputs the category value(s) associated with user-specified location(s)
-in user-specified vector map layer(s).
-
-<p>
-
-The program activates the mouse, and expects the user to indicate the
-location(s) to be queried by depressing a mouse button over desired location(s)
-within the current geographic region in the active display frame on the
-graphic monitor. Query results from map(s) are by default displayed in a new
-monitor, where label values can be added or changed. Using parameter <b>-x</b>
-informations will be displayed as plain text to terminal window.
-
-<h2>EXAMPLE</h2>
-
-A sample <em>d.what.vect</em> session is given below. Although it is not
-necessary that the user first displays a vector map to be queried in the
-active display frame, it is helpful to have a map displayed there for
-reference.
-
-<p>
-
-<b>d.vect map=</b><em>roads</em><p>
-Displays the <em>roads</em> vector map layer on the graphics monitor.
-<p>
-
-<b>d.what.vect map=</b><em>roads,geology</em><p>
-After typing this, the user moves the mouse to a desired location
-on the displayed <em>roads</em> map layer, and presses the left mouse
-button to query the category value of the <em>roads</em> and the
-<em>geology</em> vector map at this location.
-
-The program then outputs the category value of a line type corresponding
-to this user-selected map location, for the vector map queried by the user.
-
-<p>
-
-The query may be repeated as often as desired using the left mouse button. The
-middle mouse button toggles the flash color.
-The right button on the mouse is used to quit the <em>d.what.vect</em> session.
-
-<h2>SEE ALSO</h2>
-
-<em><a HREF="d.rast.html">d.rast</a></em><br>
-<em><a HREF="d.vect.html">d.vect</a></em><br>
-<em><a HREF="d.what.rast.html">d.what.rast</a></em><br>
-<em><a HREF="g.region.html">g.region</a></em><br>
-
-<h2>AUTHOR</h2>
-
-Jim Hinthorne,
-Central Washington University<br>
-Upgrades by Dennis Finch, National Park Service and Radim Blazek, ITC-Irst, Trento, Italy
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/display/d.where/d.where.html (from rev 32770, grass/trunk/display/d.where/description.html)
===================================================================
--- grass/trunk/display/d.where/d.where.html (rev 0)
+++ grass/trunk/display/d.where/d.where.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,61 @@
+<H2>DESCRIPTION</H2>
+
+
+<EM>d.where</EM> is an <EM>interactive</EM> program that
+allows the user, using the pointing device (mouse), to
+identify the geographic coordinates associated with point
+locations within the current geographic region in the
+active display frame on the graphics monitor.
+
+<P>
+Each mouse click will output the easting and northing of the point
+currently located beneath the mouse pointer.
+A mouse-button menu is presented so the user knows which
+mouse buttons to use. The output is always printed to the
+terminal screen; if the output is redirected into a file,
+it will be written to the file as well.
+
+<P>
+Mouse buttons:
+
+<pre>
+ Left: where am i
+ Middle: draw to/from here
+ Right: quit this
+</pre>
+
+The left mouse button prints the coordinates at the selected point,
+the middle mouse button allows to query two points (they are connected by a
+line for convenience). By using the right mouse button the module is left.
+
+
+<H2>NOTES</H2>
+
+This program uses the current geographic region setting and active frame.
+It is not necessary, although useful, to have displayed a map in the current
+frame before running <EM>d.where</EM>. The <b>-d</b> flag allows the user to
+optionally output latitude/longitude coordinates pair(s) in decimal degree
+rather than DD:MM:SS format. The <b>-w</b> flag is only valid
+if a datum is defined for the current location.
+
+If the <b>-f</b> flag is given the x,y frame coordinates of the active display
+monitor will be returned (as a percentage, 0,0 is bottom left).
+
+
+<H2>SEE ALSO</H2>
+
+<EM><A HREF="d.what.rast.html">d.what.rast</A></EM><br>
+<EM><A HREF="d.what.vect.html">d.what.vect</A></EM><br>
+<EM><A HREF="g.region.html">g.region</A></EM><br>
+<EM><A HREF="v.what.rast.html">v.what.rast</A></EM><br>
+<EM><A HREF="v.what.vect.html">v.what.vect</A></EM>
+
+
+<H2>AUTHORS</H2>
+
+James Westervelt, <br>
+Michael Shapiro, <BR>
+U.S. Army Construction Engineering
+Research Laboratory
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/display/d.where/description.html
===================================================================
--- grass/trunk/display/d.where/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/display/d.where/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,61 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-
-<EM>d.where</EM> is an <EM>interactive</EM> program that
-allows the user, using the pointing device (mouse), to
-identify the geographic coordinates associated with point
-locations within the current geographic region in the
-active display frame on the graphics monitor.
-
-<P>
-Each mouse click will output the easting and northing of the point
-currently located beneath the mouse pointer.
-A mouse-button menu is presented so the user knows which
-mouse buttons to use. The output is always printed to the
-terminal screen; if the output is redirected into a file,
-it will be written to the file as well.
-
-<P>
-Mouse buttons:
-
-<pre>
- Left: where am i
- Middle: draw to/from here
- Right: quit this
-</pre>
-
-The left mouse button prints the coordinates at the selected point,
-the middle mouse button allows to query two points (they are connected by a
-line for convenience). By using the right mouse button the module is left.
-
-
-<H2>NOTES</H2>
-
-This program uses the current geographic region setting and active frame.
-It is not necessary, although useful, to have displayed a map in the current
-frame before running <EM>d.where</EM>. The <b>-d</b> flag allows the user to
-optionally output latitude/longitude coordinates pair(s) in decimal degree
-rather than DD:MM:SS format. The <b>-w</b> flag is only valid
-if a datum is defined for the current location.
-
-If the <b>-f</b> flag is given the x,y frame coordinates of the active display
-monitor will be returned (as a percentage, 0,0 is bottom left).
-
-
-<H2>SEE ALSO</H2>
-
-<EM><A HREF="d.what.rast.html">d.what.rast</A></EM><br>
-<EM><A HREF="d.what.vect.html">d.what.vect</A></EM><br>
-<EM><A HREF="g.region.html">g.region</A></EM><br>
-<EM><A HREF="v.what.rast.html">v.what.rast</A></EM><br>
-<EM><A HREF="v.what.vect.html">v.what.vect</A></EM>
-
-
-<H2>AUTHORS</H2>
-
-James Westervelt, <br>
-Michael Shapiro, <BR>
-U.S. Army Construction Engineering
-Research Laboratory
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/display/d.zoom/d.zoom.html (from rev 32770, grass/trunk/display/d.zoom/description.html)
===================================================================
--- grass/trunk/display/d.zoom/d.zoom.html (rev 0)
+++ grass/trunk/display/d.zoom/d.zoom.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,45 @@
+<h2>DESCRIPTION</h2>
+
+<em>d.zoom</em> allows the user to interactively adjust the settings
+of the current geographic region using a pointing device such as
+a mouse.
+Like <em><a HREF="g.region.html">g.region</a></em>,
+<em>d.zoom</em> re-defines the settings of the geographic
+region. However, <em>d.zoom</em> allows the user to change
+the current region settings interactively, by either
+outlining the new region perimeter with a mouse, unzoom
+or pan the region. The graphics display is updated by the module.
+
+<p>
+
+After the user types the command <b>d.zoom</b> a mouse-button menu will appear
+directing the user.
+
+<p>
+
+Additionally the region settings can be modified by
+running <em><a HREF="g.region.html">g.region</a></em>.
+
+<h2>NOTES</h2>
+
+Although it is not necessary that the user display a map in
+the active display frame before running <em>d.zoom</em>, it
+is helpful to do this for reference. Using parameter <b>-f</b> integrate a
+pan function, <b>-h </b> facilitates the use for handhelds.
+
+<h2>SEE ALSO</h2>
+
+<em><a HREF="d.erase.html">d.erase</a></em><br>
+<em><a HREF="d.rast.html">d.rast</a></em><br>
+<em><a HREF="d.vect.html">d.vect</a></em><br>
+<em><a HREF="g.region.html">g.region</a></em>
+
+<h2>AUTHOR</h2>
+
+Michael Shapiro,
+U.S. Army Construction Engineering
+Research Laboratory
+<br>
+Improvements by Huidae Cho and Markus Neteler
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/display/d.zoom/description.html
===================================================================
--- grass/trunk/display/d.zoom/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/display/d.zoom/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,45 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>d.zoom</em> allows the user to interactively adjust the settings
-of the current geographic region using a pointing device such as
-a mouse.
-Like <em><a HREF="g.region.html">g.region</a></em>,
-<em>d.zoom</em> re-defines the settings of the geographic
-region. However, <em>d.zoom</em> allows the user to change
-the current region settings interactively, by either
-outlining the new region perimeter with a mouse, unzoom
-or pan the region. The graphics display is updated by the module.
-
-<p>
-
-After the user types the command <b>d.zoom</b> a mouse-button menu will appear
-directing the user.
-
-<p>
-
-Additionally the region settings can be modified by
-running <em><a HREF="g.region.html">g.region</a></em>.
-
-<h2>NOTES</h2>
-
-Although it is not necessary that the user display a map in
-the active display frame before running <em>d.zoom</em>, it
-is helpful to do this for reference. Using parameter <b>-f</b> integrate a
-pan function, <b>-h </b> facilitates the use for handhelds.
-
-<h2>SEE ALSO</h2>
-
-<em><a HREF="d.erase.html">d.erase</a></em><br>
-<em><a HREF="d.rast.html">d.rast</a></em><br>
-<em><a HREF="d.vect.html">d.vect</a></em><br>
-<em><a HREF="g.region.html">g.region</a></em>
-
-<h2>AUTHOR</h2>
-
-Michael Shapiro,
-U.S. Army Construction Engineering
-Research Laboratory
-<br>
-Improvements by Huidae Cho and Markus Neteler
-
-<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/doc/raster/r.example/description.html
===================================================================
--- grass/trunk/doc/raster/r.example/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/doc/raster/r.example/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,18 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-<EM>r.example</EM> does practically do nothing, except
-for illustrating GRASS raster programming. It copies
-over an existing raster map to a new raster map.
-See the source code for details.
-
-<H2>SEE ALSO</H2>
-
-<EM><A HREF="r.stats.html">r.stats</A></EM><br>
-<EM><A HREF="http://grass.itc.it/devel/index.php#prog">GRASS Programmer's Manual</A></EM>
-
-
-<H2>AUTHOR</H2>
-
-GRASS Development Team
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/doc/raster/r.example/r.example.html (from rev 32770, grass/trunk/doc/raster/r.example/description.html)
===================================================================
--- grass/trunk/doc/raster/r.example/r.example.html (rev 0)
+++ grass/trunk/doc/raster/r.example/r.example.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,18 @@
+<H2>DESCRIPTION</H2>
+
+<EM>r.example</EM> does practically do nothing, except
+for illustrating GRASS raster programming. It copies
+over an existing raster map to a new raster map.
+See the source code for details.
+
+<H2>SEE ALSO</H2>
+
+<EM><A HREF="r.stats.html">r.stats</A></EM><br>
+<EM><A HREF="http://grass.itc.it/devel/index.php#prog">GRASS Programmer's Manual</A></EM>
+
+
+<H2>AUTHOR</H2>
+
+GRASS Development Team
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/doc/vector/v.example/description.html
===================================================================
--- grass/trunk/doc/vector/v.example/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/doc/vector/v.example/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,21 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>v.example</em> is an example vector module that does something like
-labeling all vectors with value 1. A new map is written instead of updating
-the input map.
-
-<h2>EXAMPLE</h2>
-
-<div class="code"><pre>
-v.example input=map output=newmap
-</pre></div>
-
-<H2>SEE ALSO</H2>
-
-<EM><A HREF="http://grass.itc.it/devel/index.php#prog">GRASS Programmer's Manual</A></EM>
-
-<h2>AUTHOR</h2>
-
-Radim Blazek, ITC-irst, Trento, Italy
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/doc/vector/v.example/v.example.html (from rev 32770, grass/trunk/doc/vector/v.example/description.html)
===================================================================
--- grass/trunk/doc/vector/v.example/v.example.html (rev 0)
+++ grass/trunk/doc/vector/v.example/v.example.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,21 @@
+<h2>DESCRIPTION</h2>
+
+<em>v.example</em> is an example vector module that does something like
+labeling all vectors with value 1. A new map is written instead of updating
+the input map.
+
+<h2>EXAMPLE</h2>
+
+<div class="code"><pre>
+v.example input=map output=newmap
+</pre></div>
+
+<H2>SEE ALSO</H2>
+
+<EM><A HREF="http://grass.itc.it/devel/index.php#prog">GRASS Programmer's Manual</A></EM>
+
+<h2>AUTHOR</h2>
+
+Radim Blazek, ITC-irst, Trento, Italy
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/general/g.access/description.html
===================================================================
--- grass/trunk/general/g.access/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/general/g.access/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,46 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-This program allows the user to control access to the
-current mapset. Normally, any user can read data from any
-GRASS mapset. But sometimes it is desirable to prohibit
-access to certain sensitive data. The <EM>g.access</EM>
-command allows a user to restrict read and execute access
-to the current mapset (see UNIX <EM>chmod</EM> command).
-<EM>g.access</EM> will not modify write access to the
-current mapset.
-
-<P>
-
-The user may, for example, allow only users in the same
-UNIX group to read data files in the mapset, or restrict
-the mapset to personal use only.
-
-<H2>NOTES</H2>
-
-
-<P> Under GRASS, access to the mapset PERMANENT must be open to
-all users. This is because GRASS looks for the user's default geographic
-region definition settings and the location TITLE in files that are stored
-under the PERMANENT mapset directory. The <EM>g.access</EM> command,
-therefore, will not allow you to restrict access to the PERMANENT mapset.
-
-<P>
-The <EM><A HREF="g.mapsets.html">g.mapsets</A></EM> command isn't smart
-enough to tell if access to a specified mapset is restricted, and the user
-is therefore allowed to include the names of restricted mapsets in his
-search path. However, the data in a restricted mapset is still protected;
-any attempts to look for or use data in a restricted mapset will fail. The
-user will simply not see any data listed for a restricted mapset.
-
-<H2>SEE ALSO</H2>
-
-UNIX manual entries for <EM>chmod</EM> and <EM>group</EM>
-<BR>
-<EM><A HREF="g.mapsets.html">g.mapsets</A></EM>
-
-<H2>AUTHOR</H2>
-
-Michael Shapiro,
-U.S. Army Construction Engineering Research Laboratory
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/general/g.access/g.access.html (from rev 32770, grass/trunk/general/g.access/description.html)
===================================================================
--- grass/trunk/general/g.access/g.access.html (rev 0)
+++ grass/trunk/general/g.access/g.access.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,46 @@
+<H2>DESCRIPTION</H2>
+
+This program allows the user to control access to the
+current mapset. Normally, any user can read data from any
+GRASS mapset. But sometimes it is desirable to prohibit
+access to certain sensitive data. The <EM>g.access</EM>
+command allows a user to restrict read and execute access
+to the current mapset (see UNIX <EM>chmod</EM> command).
+<EM>g.access</EM> will not modify write access to the
+current mapset.
+
+<P>
+
+The user may, for example, allow only users in the same
+UNIX group to read data files in the mapset, or restrict
+the mapset to personal use only.
+
+<H2>NOTES</H2>
+
+
+<P> Under GRASS, access to the mapset PERMANENT must be open to
+all users. This is because GRASS looks for the user's default geographic
+region definition settings and the location TITLE in files that are stored
+under the PERMANENT mapset directory. The <EM>g.access</EM> command,
+therefore, will not allow you to restrict access to the PERMANENT mapset.
+
+<P>
+The <EM><A HREF="g.mapsets.html">g.mapsets</A></EM> command isn't smart
+enough to tell if access to a specified mapset is restricted, and the user
+is therefore allowed to include the names of restricted mapsets in his
+search path. However, the data in a restricted mapset is still protected;
+any attempts to look for or use data in a restricted mapset will fail. The
+user will simply not see any data listed for a restricted mapset.
+
+<H2>SEE ALSO</H2>
+
+UNIX manual entries for <EM>chmod</EM> and <EM>group</EM>
+<BR>
+<EM><A HREF="g.mapsets.html">g.mapsets</A></EM>
+
+<H2>AUTHOR</H2>
+
+Michael Shapiro,
+U.S. Army Construction Engineering Research Laboratory
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/general/g.dirseps/description.html
===================================================================
--- grass/trunk/general/g.dirseps/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/general/g.dirseps/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,11 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-<EM>g.dirseps</EM> is an internal tool only. It copies input string
-to stdout, changing directory separator characters as specified by flags.
-It is used for interoperability between Unix and MS-Windows pathnames.
-
-<H2>AUTHOR</H2>
-
-Paul Kelly
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/general/g.dirseps/g.dirseps.html (from rev 32770, grass/trunk/general/g.dirseps/description.html)
===================================================================
--- grass/trunk/general/g.dirseps/g.dirseps.html (rev 0)
+++ grass/trunk/general/g.dirseps/g.dirseps.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,11 @@
+<H2>DESCRIPTION</H2>
+
+<EM>g.dirseps</EM> is an internal tool only. It copies input string
+to stdout, changing directory separator characters as specified by flags.
+It is used for interoperability between Unix and MS-Windows pathnames.
+
+<H2>AUTHOR</H2>
+
+Paul Kelly
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/general/g.filename/description.html
===================================================================
--- grass/trunk/general/g.filename/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/general/g.filename/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,93 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-<em>g.filename</em> is designed for Bourne shell scripts that need to know
-the full file name, including it's path, for mapset elements, like raster,
-vector and site maps, region definitions and imagery groups.
-<p>
-The list of element names to search for is not fixed; any subdirectory of the
-mapset directory is a valid element name.
-<p>
-However, the user can find the list of standard GRASS element names in
-the file $GISBASE/etc/element_list. This is the file which
-g.remove/g.rename/g.copy use to determine which files need to be
-deleted/renamed/copied for a given entity type.
-
-<!-- unused
-<H2>OPTIONS</H2>
-
-<H3>Parameters:</H3>
-
-<DL>
-<DT><B>element=</B><EM>name</EM>
-
-<DD>The name of a GRASS data base element (i.e., directory
-within the GRASS mapset location).
-
-<DT><B>mapset=</B><EM>name</EM>
-
-<DD>The name of a GRASS data base mapset. As a
-convenience, a single dot (.) can be used to designate the
-current mapset.
-
-<DT><B>file=</B><EM>name</EM>
-
-<DD>The name of a GRASS data base file.
-</DL>
--->
-<H2>OUTPUT</H2>
-
-<EM>g.filename</EM>
-writes one line to standard output:
-
-<DL>
-<DD>
-file='<EM>full_file_pathname'</EM>
-</DL>
-
-The output is a <EM>/bin/sh</EM> command to set the
-variable specified by the file <EM>name</EM> to the full
-UNIX path name for the data base file. This variable may
-be set in the <EM>/bin/sh</EM> as follows:
-
-<DL>
-<DD>
-<div class="code"><pre>
-eval `g.filename element=<em>name</em> mapset=<em>name</em> file=<em>name</em>`
-</pre></div>
-</DL>
-
-
-<H2>NOTES</H2>
-
-This routine generates the filename, but does not care if the file (or mapset
-or element) exists or not. This feature allows shell scripts to create new data
-base files as well as use existing ones.
-
-<P>
-
-If the mapset is the current mapset, <EM>g.filename</EM>
-automatically creates the <EM>element</EM> specified if it
-doesn't already exist. This makes it easy to add new files
-to the data base without having to worry about the
-existence of the required data base directories. (This
-program will not create a new mapset, however, if that
-specified does not currently exist.)
-
-<P>
-The program exits with a 0 if everything is ok; it exits
-with a non-zero value if there is an error, in which case
-file=<EM>'full_file_pathname'</EM> is not output.
-
-<H2>SEE ALSO</H2>
-
-<EM><A HREF="g.ask.html">g.ask</A></EM><br>
-<EM><A HREF="g.findfile.html">g.findfile</A></EM><br>
-<EM><A HREF="g.gisenv.html">g.gisenv</A></EM><br>
-<EM><A HREF="parser.html">parser</A></EM>
-
-<H2>AUTHOR</H2>
-
-Michael Shapiro,
-U.S.Army Construction Engineering Research Laboratory
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/general/g.filename/g.filename.html (from rev 32770, grass/trunk/general/g.filename/description.html)
===================================================================
--- grass/trunk/general/g.filename/g.filename.html (rev 0)
+++ grass/trunk/general/g.filename/g.filename.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,93 @@
+<H2>DESCRIPTION</H2>
+
+<em>g.filename</em> is designed for Bourne shell scripts that need to know
+the full file name, including it's path, for mapset elements, like raster,
+vector and site maps, region definitions and imagery groups.
+<p>
+The list of element names to search for is not fixed; any subdirectory of the
+mapset directory is a valid element name.
+<p>
+However, the user can find the list of standard GRASS element names in
+the file $GISBASE/etc/element_list. This is the file which
+g.remove/g.rename/g.copy use to determine which files need to be
+deleted/renamed/copied for a given entity type.
+
+<!-- unused
+<H2>OPTIONS</H2>
+
+<H3>Parameters:</H3>
+
+<DL>
+<DT><B>element=</B><EM>name</EM>
+
+<DD>The name of a GRASS data base element (i.e., directory
+within the GRASS mapset location).
+
+<DT><B>mapset=</B><EM>name</EM>
+
+<DD>The name of a GRASS data base mapset. As a
+convenience, a single dot (.) can be used to designate the
+current mapset.
+
+<DT><B>file=</B><EM>name</EM>
+
+<DD>The name of a GRASS data base file.
+</DL>
+-->
+<H2>OUTPUT</H2>
+
+<EM>g.filename</EM>
+writes one line to standard output:
+
+<DL>
+<DD>
+file='<EM>full_file_pathname'</EM>
+</DL>
+
+The output is a <EM>/bin/sh</EM> command to set the
+variable specified by the file <EM>name</EM> to the full
+UNIX path name for the data base file. This variable may
+be set in the <EM>/bin/sh</EM> as follows:
+
+<DL>
+<DD>
+<div class="code"><pre>
+eval `g.filename element=<em>name</em> mapset=<em>name</em> file=<em>name</em>`
+</pre></div>
+</DL>
+
+
+<H2>NOTES</H2>
+
+This routine generates the filename, but does not care if the file (or mapset
+or element) exists or not. This feature allows shell scripts to create new data
+base files as well as use existing ones.
+
+<P>
+
+If the mapset is the current mapset, <EM>g.filename</EM>
+automatically creates the <EM>element</EM> specified if it
+doesn't already exist. This makes it easy to add new files
+to the data base without having to worry about the
+existence of the required data base directories. (This
+program will not create a new mapset, however, if that
+specified does not currently exist.)
+
+<P>
+The program exits with a 0 if everything is ok; it exits
+with a non-zero value if there is an error, in which case
+file=<EM>'full_file_pathname'</EM> is not output.
+
+<H2>SEE ALSO</H2>
+
+<EM><A HREF="g.ask.html">g.ask</A></EM><br>
+<EM><A HREF="g.findfile.html">g.findfile</A></EM><br>
+<EM><A HREF="g.gisenv.html">g.gisenv</A></EM><br>
+<EM><A HREF="parser.html">parser</A></EM>
+
+<H2>AUTHOR</H2>
+
+Michael Shapiro,
+U.S.Army Construction Engineering Research Laboratory
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/general/g.findetc/description.html
===================================================================
--- grass/trunk/general/g.findetc/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/general/g.findetc/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,27 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-<EM>g.findetc</EM> is designed for Bourne shell scripts that need to search
-for support data, programs and subfoldrs in any number of directories as
-specified in GRASS_ADDON_ETC, plus the GRASS application etc/ directory. This
-is designed for addon scripts that are installed outside the GRASS application
-directory, such as a user's home or a system addon directory.
-<p>
-
-<H2>OUTPUT</H2>
-
-<EM>g.findetc</EM> writes the full path to the file or directory to standard output
-
-<H2>SEE ALSO</H2>
-
-<EM><A HREF="g.ask.html">g.ask</A></EM><br>
-<EM><A HREF="g.filename.html">g.filename</A></EM><br>
-<EM><A HREF="g.findfile.html">g.findfile</A></EM><br>
-<EM><A HREF="g.gisenv.html">g.gisenv</A></EM><br>
-<EM><A HREF="g.mapsets.html">g.mapsets</A></EM><br>
-<EM><A HREF="parser.html">parser</A></EM>
-
-<H2>AUTHOR</H2>
-
-William Kyngesburye
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/general/g.findetc/g.findetc.html (from rev 32770, grass/trunk/general/g.findetc/description.html)
===================================================================
--- grass/trunk/general/g.findetc/g.findetc.html (rev 0)
+++ grass/trunk/general/g.findetc/g.findetc.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,27 @@
+<H2>DESCRIPTION</H2>
+
+<EM>g.findetc</EM> is designed for Bourne shell scripts that need to search
+for support data, programs and subfoldrs in any number of directories as
+specified in GRASS_ADDON_ETC, plus the GRASS application etc/ directory. This
+is designed for addon scripts that are installed outside the GRASS application
+directory, such as a user's home or a system addon directory.
+<p>
+
+<H2>OUTPUT</H2>
+
+<EM>g.findetc</EM> writes the full path to the file or directory to standard output
+
+<H2>SEE ALSO</H2>
+
+<EM><A HREF="g.ask.html">g.ask</A></EM><br>
+<EM><A HREF="g.filename.html">g.filename</A></EM><br>
+<EM><A HREF="g.findfile.html">g.findfile</A></EM><br>
+<EM><A HREF="g.gisenv.html">g.gisenv</A></EM><br>
+<EM><A HREF="g.mapsets.html">g.mapsets</A></EM><br>
+<EM><A HREF="parser.html">parser</A></EM>
+
+<H2>AUTHOR</H2>
+
+William Kyngesburye
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/general/g.findfile/description.html
===================================================================
--- grass/trunk/general/g.findfile/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/general/g.findfile/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,108 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-<EM>g.findfile</EM> is designed for Bourne shell scripts that need to search
-for mapset <em>elements</em>, including: raster, vector maps, region
-definitions and <em><a HREF="i.group.html">imagery</a></em> groups.
-<p>
-The list of <em>element</em> names to search for is not fixed; any
-subdirectory of the mapset directory is a valid <em>element</em> name.
-<p>
-However, the user can find the list of standard GRASS <em>element</em> names in
-the file $GISBASE/etc/element_list. This is the file which
-g.remove/g.rename/g.copy use to determine which files need to be
-deleted/renamed/copied for a given entity type.
-
-<!-- unused
-<H2>OPTIONS</H2>
-
-<H3>Parameters:</H3>
-
-<DL>
-
-<DT><B>element=</B><EM>name</EM>
-
-<DD>The data base element (i.e., directory within a GRASS
-mapset) to be searched.
-
-<DT><B>mapset=</B><EM>name</EM>
-
-<DD>The mapset in which to search for the specified file
-<EM>name</EM>. If not specified, all mapsets in the user's
-GRASS search path are searched. Otherwise, the specified
-mapset is searched. As a convenience, if specified as a
-single dot (.) only the current mapset is searched.
-
-<DT><B>file=</B><EM>name</EM>
-
-<DD>The name of a GRASS data file (of the stated
-<EM>element</EM> type) for which to search.
-
-</DL>
--->
-
-<H2>OUTPUT</H2>
-
-<EM>g.findfile</EM> writes four lines to standard output:
-
-<div class="code"><pre>
-name='<EM>file_name</EM>'
-mapset='<EM>mapset_name</EM>'
-file='<EM>unix_filename</EM>'
-fullname='<EM>grass_fullname</EM>'
-</pre></div>
-
-
-The output is <EM>/bin/sh</EM> commands to set the variable
-<EM>name</EM> to the GRASS data base file name,
-<EM>mapset</EM> to the mapset in which the file resides,
-and <EM>file</EM> to the full UNIX path name for the named
-file. These variables may be set in the <EM>/bin/sh</EM>
-as follows:
-
-<div class="code"><pre>
-eval `g.findfile element=name mapset=name file=name`
-</pre></div>
-<P>
-For example (raster map):
-<div class="code"><pre>
-eval `g.findfile element=cell file=mymap`
-</pre></div>
-
-<H2>NOTES</H2>
-
-If the specified file does not exist, the variables will be set as follows:
-
-<div class="code"><pre>
-name=
-mapset=
-fullname=
-file=
-</pre></div>
-
-
-The following is a way to test for this case:
-<div class="code">
-<PRE>
-if [ ! "$file" ]
-then
- exit
-fi
-</PRE>
-</DIV>
-
-Note that region files are searched as <em>element=windows</em>.
-
-<H2>SEE ALSO</H2>
-
-<EM><A HREF="g.ask.html">g.ask</A></EM><br>
-<EM><A HREF="g.filename.html">g.filename</A></EM><br>
-<EM><A HREF="g.gisenv.html">g.gisenv</A></EM><br>
-<EM><A HREF="g.mapsets.html">g.mapsets</A></EM><br>
-<EM><A HREF="parser.html">parser</A></EM>
-
-<H2>AUTHOR</H2>
-
-Michael Shapiro,
-U.S.Army Construction Engineering Research Laboratory
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/general/g.findfile/g.findfile.html (from rev 32770, grass/trunk/general/g.findfile/description.html)
===================================================================
--- grass/trunk/general/g.findfile/g.findfile.html (rev 0)
+++ grass/trunk/general/g.findfile/g.findfile.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,108 @@
+<H2>DESCRIPTION</H2>
+
+<EM>g.findfile</EM> is designed for Bourne shell scripts that need to search
+for mapset <em>elements</em>, including: raster, vector maps, region
+definitions and <em><a HREF="i.group.html">imagery</a></em> groups.
+<p>
+The list of <em>element</em> names to search for is not fixed; any
+subdirectory of the mapset directory is a valid <em>element</em> name.
+<p>
+However, the user can find the list of standard GRASS <em>element</em> names in
+the file $GISBASE/etc/element_list. This is the file which
+g.remove/g.rename/g.copy use to determine which files need to be
+deleted/renamed/copied for a given entity type.
+
+<!-- unused
+<H2>OPTIONS</H2>
+
+<H3>Parameters:</H3>
+
+<DL>
+
+<DT><B>element=</B><EM>name</EM>
+
+<DD>The data base element (i.e., directory within a GRASS
+mapset) to be searched.
+
+<DT><B>mapset=</B><EM>name</EM>
+
+<DD>The mapset in which to search for the specified file
+<EM>name</EM>. If not specified, all mapsets in the user's
+GRASS search path are searched. Otherwise, the specified
+mapset is searched. As a convenience, if specified as a
+single dot (.) only the current mapset is searched.
+
+<DT><B>file=</B><EM>name</EM>
+
+<DD>The name of a GRASS data file (of the stated
+<EM>element</EM> type) for which to search.
+
+</DL>
+-->
+
+<H2>OUTPUT</H2>
+
+<EM>g.findfile</EM> writes four lines to standard output:
+
+<div class="code"><pre>
+name='<EM>file_name</EM>'
+mapset='<EM>mapset_name</EM>'
+file='<EM>unix_filename</EM>'
+fullname='<EM>grass_fullname</EM>'
+</pre></div>
+
+
+The output is <EM>/bin/sh</EM> commands to set the variable
+<EM>name</EM> to the GRASS data base file name,
+<EM>mapset</EM> to the mapset in which the file resides,
+and <EM>file</EM> to the full UNIX path name for the named
+file. These variables may be set in the <EM>/bin/sh</EM>
+as follows:
+
+<div class="code"><pre>
+eval `g.findfile element=name mapset=name file=name`
+</pre></div>
+<P>
+For example (raster map):
+<div class="code"><pre>
+eval `g.findfile element=cell file=mymap`
+</pre></div>
+
+<H2>NOTES</H2>
+
+If the specified file does not exist, the variables will be set as follows:
+
+<div class="code"><pre>
+name=
+mapset=
+fullname=
+file=
+</pre></div>
+
+
+The following is a way to test for this case:
+<div class="code">
+<PRE>
+if [ ! "$file" ]
+then
+ exit
+fi
+</PRE>
+</DIV>
+
+Note that region files are searched as <em>element=windows</em>.
+
+<H2>SEE ALSO</H2>
+
+<EM><A HREF="g.ask.html">g.ask</A></EM><br>
+<EM><A HREF="g.filename.html">g.filename</A></EM><br>
+<EM><A HREF="g.gisenv.html">g.gisenv</A></EM><br>
+<EM><A HREF="g.mapsets.html">g.mapsets</A></EM><br>
+<EM><A HREF="parser.html">parser</A></EM>
+
+<H2>AUTHOR</H2>
+
+Michael Shapiro,
+U.S.Army Construction Engineering Research Laboratory
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/general/g.gisenv/description.html
===================================================================
--- grass/trunk/general/g.gisenv/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/general/g.gisenv/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,208 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-When a user runs GRASS, certain variables are set
-specifying the GRASS data base, location, mapset,
-peripheral device drivers, etc., being used in the current
-GRASS session. These variable name settings are recognized
-as long as the user is running a GRASS session.
-
-
-<h2>OPTIONS</h2>
-
-No prompts are given to the user when running
-<em>g.gisenv</em>. If run without arguments,
-<em>g.gisenv</em> lists all of the user's current GRASS
-variable settings. Results are sent to standard output,
-and may look like this:
-
-
-<div class="code"><pre>
-GISDBASE=/usr/grass5/data
-LOCATION_NAME=spearfish
-MAPSET=PERMANENT
-</pre></div>
-
-In this example, the full path name of the user's current
-location (i.e., <kbd>$LOCATION_NAME</kbd>) is
-<kbd>/usr/grass5/data/spearfish</kbd>, and the full path
-name of the user's current mapset (i.e.,
-<kbd>$MAPSET</kbd>) is
-<kbd>/usr/grass5/data/spearfish/PERMANENT</kbd>.
-
-
-<p>
-
-If the user specifies a <em>variable_name</em> on the
-command line (e.g., <b>g.gisenv MAPSET</b>), only the value
-for that particular GRASS variable is output to standard
-output. Possible variable names depend on the user's
-system, see <a href=variables.html>variables list</a> for details.
-
-
-<p>
-
-While other variables may be associated with each GRASS session
-(e.g., DIGITIZER, PAINTER, DISPLAY, and other variables), those stated
-below are essential.
-
-
-<dl>
-<dt><em>GISDBASE</em>
-
-<dd>The <kbd>$GISDBASE</kbd> is a directory in which all
-users' GRASS data are stored. Within the
-
-<kbd>$GISDBASE</kbd>, data are segregated into
-subdirectories (called "locations") based on the map
-coordinate system used and the geographic extent of the
-data. Each "location" directory itself contains
-subdirectories called "mapsets"; each "mapset" stores "data
-base elements" -- the directories (e.g., the
-<kbd>cell</kbd>, <kbd>cellhd</kbd>, <kbd>dig</kbd>, etc.,
-directories) in which GRASS data files are actually
-stored.
-
-<dt><em>LOCATION_NAME</em>
-
-<dd>The user must choose to work with the data under a single
-GRASS location within any given GRASS session; this
-location is then called the <em>current GRASS
-location</em>, and is specified by the variable
-<kbd>$LOCATION_NAME</kbd>. The <kbd>$LOCATION_NAME</kbd>
-
-is the GRASS data base location whose data will be affected
-by any GRASS commands issued during the user's current
-GRASS session, and is a subdirectory of the current
-<kbd>$GISDBASE</kbd>. Each "location" directory can
-contain multiple "mapset" directories (including the
-special mapset <kbd>PERMANENT</kbd>). Maps stored under
-the same GRASS <kbd>LOCATION_NAME</kbd> (and/or within the
-same <kbd>MAPSET</kbd>) must use the same coordinate system
-and typically fall within the boundaries of the same
-geographic region (aka, "location").
-
-
-<dt><em>MAPSET</em>
-
-<dd>Each "mapset" contains a set of maps relevant to the
-<kbd>LOCATION_NAME</kbd> directory in which it appears.
-Each <kbd>LOCATION_NAME</kbd> can contain multiple
-mapsets. (Mapsets which fall under the same
-
-<kbd>LOCATION_NAME</kbd> all contain data geographically
-relevant to the <kbd>LOCATION_NAME</kbd>, and all store
-data in the same map coordinate system. Frequently, maps
-are placed into different mapsets to distinguish file
-ownership -- e.g., each user might have his own mapset,
-storing any maps that he has created and/or are relevant to
-his work.) During each GRASS session, the user must choose
-one mapset to be the <em>current mapset</em>; the current
-mapset setting is given by <kbd>$MAPSET</kbd>, and is a
-subdirectory of <kbd>$LOCATION_NAME</kbd>. During a single
-GRASS session, the user can use available data in any of
-the mapsets stored under the current
-<kbd>LOCATION_NAME</kbd> directory that are in the user's
-mapset search path and accessible by the user. However,
-within a single GRASS session, the user only has
-<em>write</em> access to data stored under the <em>current
-mapset</em> (specified by the variable
-
-<kbd>$MAPSET</kbd>).
-
-
-<p>
-
-Each "mapset" stores GRASS data base elements (i.e., the
-directories in which GRASS data files are stored). Any
-maps created or modified by the user in the current GRASS
-session will be stored here. The <kbd>MAPSET</kbd>
-directory <kbd>PERMANENT</kbd> is generally reserved for
-the set of maps that form the base set for all users
-working under each <kbd>LOCATION_NAME</kbd>.
-
-</dl>
-
-Once within a GRASS session, GRASS users have access only
-to the data under a single GRASS data base directory (the
-<em>current GRASS data base</em>, specified by the variable
-
-<kbd>$GISDBASE</kbd>), and to a single GRASS location
-directory (the <em>current location</em>, specified by the
-variable <kbd>$LOCATION_NAME</kbd>). Within a single
-session, the user may only <em>modify</em> the data in the
-<em>current mapset</em> (specified by the variable
-<kbd>$MAPSET</kbd>), but may <em>use</em> data available
-under other mapsets under the same
-
-<kbd>LOCATION_NAME</kbd>.
-
-
-<p>
-
-All of these names must be legal names on the user's
-current system. For UNIX users, names less than 14
-characters and containing no non-printing or space codes
-are permissible. Examples of permissible names include:
-<em>one</em>, <em>mymap</em>, <em>VeGe_map</em>, and
-<em>1_for_me</em>. The underscore character can safely be
-used in place of a blank for multiple-word names.
-
-<h2>NOTES</h2>
-
-The output from
-
-<em>g.gisenv</em>
-
-when invoked without arguments is directly usable by /bin/sh.
-The following command will cast each variable into the UNIX environment:
-<p>
-
-<div class="code"><pre>
-<b>eval `g.gisenv`</b>
-</pre></div>
-
-<p>
-This works only for <em>/bin/sh</em>. The format of the
-output is not compatible with other UNIX shells.
-
-<h3>GRASS Debugging:</h3>
-
-To print debugging messages, the variable DEBUG must be set to level equal or
-greater than 0:
-<P>
-<div class="code"><pre>
-<TT>g.gisenv set="DEBUG=3"</TT>
-</pre></div>
-<P>
-
-Levels: (recommended levels)
-<ul>
-<li> 0 - silence
-<li> 1 - message is printed once or few times per module
-<li> 3 - each row (raster) or line (vector)
-<li> 5 - each cell (raster) or point (vector)
-</ul>
-
-To disable debugging messages, DEBUG must be set back to 0:
-<P>
-<div class="code"><pre>
-<TT>g.gisenv set="DEBUG=0"</TT>
-</pre></div>
-<P>
-
-
-<h2>SEE ALSO</h2>
-
-<em><a HREF="g.access.html">g.access</a></em><br>
-<em><a HREF="g.ask.html">g.ask</a></em><br>
-<em><a HREF="g.filename.html">g.filename</a></em><br>
-<em><a HREF="g.findfile.html">g.findfile</a></em><br>
-<em><a HREF="g.mapsets.html">g.mapsets</a></em><br>
-<em><a href="variables.html">variables list</a></em>
-
-<h2>AUTHOR</h2>
-
-Michael Shapiro,
-U.S.Army Construction Engineering Research Laboratory
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/general/g.gisenv/g.gisenv.html (from rev 32770, grass/trunk/general/g.gisenv/description.html)
===================================================================
--- grass/trunk/general/g.gisenv/g.gisenv.html (rev 0)
+++ grass/trunk/general/g.gisenv/g.gisenv.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,208 @@
+<h2>DESCRIPTION</h2>
+
+When a user runs GRASS, certain variables are set
+specifying the GRASS data base, location, mapset,
+peripheral device drivers, etc., being used in the current
+GRASS session. These variable name settings are recognized
+as long as the user is running a GRASS session.
+
+
+<h2>OPTIONS</h2>
+
+No prompts are given to the user when running
+<em>g.gisenv</em>. If run without arguments,
+<em>g.gisenv</em> lists all of the user's current GRASS
+variable settings. Results are sent to standard output,
+and may look like this:
+
+
+<div class="code"><pre>
+GISDBASE=/usr/grass5/data
+LOCATION_NAME=spearfish
+MAPSET=PERMANENT
+</pre></div>
+
+In this example, the full path name of the user's current
+location (i.e., <kbd>$LOCATION_NAME</kbd>) is
+<kbd>/usr/grass5/data/spearfish</kbd>, and the full path
+name of the user's current mapset (i.e.,
+<kbd>$MAPSET</kbd>) is
+<kbd>/usr/grass5/data/spearfish/PERMANENT</kbd>.
+
+
+<p>
+
+If the user specifies a <em>variable_name</em> on the
+command line (e.g., <b>g.gisenv MAPSET</b>), only the value
+for that particular GRASS variable is output to standard
+output. Possible variable names depend on the user's
+system, see <a href=variables.html>variables list</a> for details.
+
+
+<p>
+
+While other variables may be associated with each GRASS session
+(e.g., DIGITIZER, PAINTER, DISPLAY, and other variables), those stated
+below are essential.
+
+
+<dl>
+<dt><em>GISDBASE</em>
+
+<dd>The <kbd>$GISDBASE</kbd> is a directory in which all
+users' GRASS data are stored. Within the
+
+<kbd>$GISDBASE</kbd>, data are segregated into
+subdirectories (called "locations") based on the map
+coordinate system used and the geographic extent of the
+data. Each "location" directory itself contains
+subdirectories called "mapsets"; each "mapset" stores "data
+base elements" -- the directories (e.g., the
+<kbd>cell</kbd>, <kbd>cellhd</kbd>, <kbd>dig</kbd>, etc.,
+directories) in which GRASS data files are actually
+stored.
+
+<dt><em>LOCATION_NAME</em>
+
+<dd>The user must choose to work with the data under a single
+GRASS location within any given GRASS session; this
+location is then called the <em>current GRASS
+location</em>, and is specified by the variable
+<kbd>$LOCATION_NAME</kbd>. The <kbd>$LOCATION_NAME</kbd>
+
+is the GRASS data base location whose data will be affected
+by any GRASS commands issued during the user's current
+GRASS session, and is a subdirectory of the current
+<kbd>$GISDBASE</kbd>. Each "location" directory can
+contain multiple "mapset" directories (including the
+special mapset <kbd>PERMANENT</kbd>). Maps stored under
+the same GRASS <kbd>LOCATION_NAME</kbd> (and/or within the
+same <kbd>MAPSET</kbd>) must use the same coordinate system
+and typically fall within the boundaries of the same
+geographic region (aka, "location").
+
+
+<dt><em>MAPSET</em>
+
+<dd>Each "mapset" contains a set of maps relevant to the
+<kbd>LOCATION_NAME</kbd> directory in which it appears.
+Each <kbd>LOCATION_NAME</kbd> can contain multiple
+mapsets. (Mapsets which fall under the same
+
+<kbd>LOCATION_NAME</kbd> all contain data geographically
+relevant to the <kbd>LOCATION_NAME</kbd>, and all store
+data in the same map coordinate system. Frequently, maps
+are placed into different mapsets to distinguish file
+ownership -- e.g., each user might have his own mapset,
+storing any maps that he has created and/or are relevant to
+his work.) During each GRASS session, the user must choose
+one mapset to be the <em>current mapset</em>; the current
+mapset setting is given by <kbd>$MAPSET</kbd>, and is a
+subdirectory of <kbd>$LOCATION_NAME</kbd>. During a single
+GRASS session, the user can use available data in any of
+the mapsets stored under the current
+<kbd>LOCATION_NAME</kbd> directory that are in the user's
+mapset search path and accessible by the user. However,
+within a single GRASS session, the user only has
+<em>write</em> access to data stored under the <em>current
+mapset</em> (specified by the variable
+
+<kbd>$MAPSET</kbd>).
+
+
+<p>
+
+Each "mapset" stores GRASS data base elements (i.e., the
+directories in which GRASS data files are stored). Any
+maps created or modified by the user in the current GRASS
+session will be stored here. The <kbd>MAPSET</kbd>
+directory <kbd>PERMANENT</kbd> is generally reserved for
+the set of maps that form the base set for all users
+working under each <kbd>LOCATION_NAME</kbd>.
+
+</dl>
+
+Once within a GRASS session, GRASS users have access only
+to the data under a single GRASS data base directory (the
+<em>current GRASS data base</em>, specified by the variable
+
+<kbd>$GISDBASE</kbd>), and to a single GRASS location
+directory (the <em>current location</em>, specified by the
+variable <kbd>$LOCATION_NAME</kbd>). Within a single
+session, the user may only <em>modify</em> the data in the
+<em>current mapset</em> (specified by the variable
+<kbd>$MAPSET</kbd>), but may <em>use</em> data available
+under other mapsets under the same
+
+<kbd>LOCATION_NAME</kbd>.
+
+
+<p>
+
+All of these names must be legal names on the user's
+current system. For UNIX users, names less than 14
+characters and containing no non-printing or space codes
+are permissible. Examples of permissible names include:
+<em>one</em>, <em>mymap</em>, <em>VeGe_map</em>, and
+<em>1_for_me</em>. The underscore character can safely be
+used in place of a blank for multiple-word names.
+
+<h2>NOTES</h2>
+
+The output from
+
+<em>g.gisenv</em>
+
+when invoked without arguments is directly usable by /bin/sh.
+The following command will cast each variable into the UNIX environment:
+<p>
+
+<div class="code"><pre>
+<b>eval `g.gisenv`</b>
+</pre></div>
+
+<p>
+This works only for <em>/bin/sh</em>. The format of the
+output is not compatible with other UNIX shells.
+
+<h3>GRASS Debugging:</h3>
+
+To print debugging messages, the variable DEBUG must be set to level equal or
+greater than 0:
+<P>
+<div class="code"><pre>
+<TT>g.gisenv set="DEBUG=3"</TT>
+</pre></div>
+<P>
+
+Levels: (recommended levels)
+<ul>
+<li> 0 - silence
+<li> 1 - message is printed once or few times per module
+<li> 3 - each row (raster) or line (vector)
+<li> 5 - each cell (raster) or point (vector)
+</ul>
+
+To disable debugging messages, DEBUG must be set back to 0:
+<P>
+<div class="code"><pre>
+<TT>g.gisenv set="DEBUG=0"</TT>
+</pre></div>
+<P>
+
+
+<h2>SEE ALSO</h2>
+
+<em><a HREF="g.access.html">g.access</a></em><br>
+<em><a HREF="g.ask.html">g.ask</a></em><br>
+<em><a HREF="g.filename.html">g.filename</a></em><br>
+<em><a HREF="g.findfile.html">g.findfile</a></em><br>
+<em><a HREF="g.mapsets.html">g.mapsets</a></em><br>
+<em><a href="variables.html">variables list</a></em>
+
+<h2>AUTHOR</h2>
+
+Michael Shapiro,
+U.S.Army Construction Engineering Research Laboratory
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/general/g.gui/description.html
===================================================================
--- grass/trunk/general/g.gui/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/general/g.gui/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,53 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<p>
-This program allows user to start a selected graphical user interface (GUI)
-from the command line prompt.
-
-<p>
-Currently three different GUIs are supported:
-
-<ul>
-<li><b>tcltk</b> - Current Tcl/Tk based GUI aka the <em>gis.m</em>
- <a href="gis.m.html">GIS Manager</a></li>
-<li><b>oldtcltk</b> - Old Tcl/Tk based GUI aka the <em>d.m</em>
- <a href="d.m.html">Display Manager</a></li>
-<li><b>wxpython</b> - New wxPython based GUI aka
- <a href="wxGUI.html">wxGUI</a></li>
-</ul>
-
-If the <b>-u</b> update flag is given or the <em>g.gisenv</em>
-<tt>GRASS_GUI</tt> variable is missing, then the <tt>GRASS_GUI</tt>
-variable is permanently changed and the selected GUI will be used
-as the default UI from then on.
-
-
-<h2>NOTES</h2>
-
-Valid values for GRASS_GUI are <tt>text</tt>, <tt>tcltk</tt>,
-<tt>oldtcltk</tt>, and <tt>wxpython</tt>.
-
-<em>g.gisenv</em> variables are stored in the user's home directory
-in a hidden file called "<TT>.grassrc7</TT>". They are not shell environment
-variables and the "rc" file is not a classic UNIX run command file,
-it just contains persistent GRASS variables and is not executed.
-
-
-<h2>SEE ALSO</h2>
-
-<em>
-<a href="wxGUI.html">wxPython based new generation GUI</a>,
-<a href="http://grass.gdf-hannover.de/wiki/WxPython-based_GUI_for_GRASS">wxGUI wiki-page</a><br>
-<a href="gis.m.html">Tcl/Tk based GIS Manager (gis.m)</a>,<br>
-<a href="d.m.html">Tcl/Tk based Display Manager (d.m)</a>,<br><br>
-<a href="g.gisenv.html">g.gisenv</a>, <a href="variables.html">GRASS variables list</a>
-</em>
-
-
-<h2>AUTHORS</h2>
-
-Martin Landa, FBK-irst, Trento, Italy<BR>
-Hamish Bowman, Otago University, Dunedin, New Zealand (fine tuning)
-
-<p>
-<i>$Date$</i>
Copied: grass/trunk/general/g.gui/g.gui.html (from rev 32770, grass/trunk/general/g.gui/description.html)
===================================================================
--- grass/trunk/general/g.gui/g.gui.html (rev 0)
+++ grass/trunk/general/g.gui/g.gui.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,53 @@
+<h2>DESCRIPTION</h2>
+
+<p>
+This program allows user to start a selected graphical user interface (GUI)
+from the command line prompt.
+
+<p>
+Currently three different GUIs are supported:
+
+<ul>
+<li><b>tcltk</b> - Current Tcl/Tk based GUI aka the <em>gis.m</em>
+ <a href="gis.m.html">GIS Manager</a></li>
+<li><b>oldtcltk</b> - Old Tcl/Tk based GUI aka the <em>d.m</em>
+ <a href="d.m.html">Display Manager</a></li>
+<li><b>wxpython</b> - New wxPython based GUI aka
+ <a href="wxGUI.html">wxGUI</a></li>
+</ul>
+
+If the <b>-u</b> update flag is given or the <em>g.gisenv</em>
+<tt>GRASS_GUI</tt> variable is missing, then the <tt>GRASS_GUI</tt>
+variable is permanently changed and the selected GUI will be used
+as the default UI from then on.
+
+
+<h2>NOTES</h2>
+
+Valid values for GRASS_GUI are <tt>text</tt>, <tt>tcltk</tt>,
+<tt>oldtcltk</tt>, and <tt>wxpython</tt>.
+
+<em>g.gisenv</em> variables are stored in the user's home directory
+in a hidden file called "<TT>.grassrc7</TT>". They are not shell environment
+variables and the "rc" file is not a classic UNIX run command file,
+it just contains persistent GRASS variables and is not executed.
+
+
+<h2>SEE ALSO</h2>
+
+<em>
+<a href="wxGUI.html">wxPython based new generation GUI</a>,
+<a href="http://grass.gdf-hannover.de/wiki/WxPython-based_GUI_for_GRASS">wxGUI wiki-page</a><br>
+<a href="gis.m.html">Tcl/Tk based GIS Manager (gis.m)</a>,<br>
+<a href="d.m.html">Tcl/Tk based Display Manager (d.m)</a>,<br><br>
+<a href="g.gisenv.html">g.gisenv</a>, <a href="variables.html">GRASS variables list</a>
+</em>
+
+
+<h2>AUTHORS</h2>
+
+Martin Landa, FBK-irst, Trento, Italy<BR>
+Hamish Bowman, Otago University, Dunedin, New Zealand (fine tuning)
+
+<p>
+<i>$Date$</i>
Deleted: grass/trunk/general/g.mapset/description.html
===================================================================
--- grass/trunk/general/g.mapset/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/general/g.mapset/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,25 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>g.mapset</em> allows to change the current mapset
-
-<h2>NOTES</h2>
-
-The shell continues to use the history for the old mapset. To change this
-you can switch the history to the new settings by commands:<BR>
-<BR>
-<div class="code"><pre>
- history -w
- history -r /$GISDBASE/$LOCATION/$MAPSET/.bash_history
- HISTFILE=/$GISDBASE/$LOCATION/$MAPSET/.bash_history
-</pre></div><BR>
-
-<h2>SEE ALSO</h2>
-
-<em><a HREF="g.gisenv.html">g.gisenv</a></em><br>
-<em><a HREF="g.mapsets.html">g.mapsets</a></em><br>
-
-<h2>AUTHOR</h2>
-
-Radim Blazek
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/general/g.mapset/g.mapset.html (from rev 32770, grass/trunk/general/g.mapset/description.html)
===================================================================
--- grass/trunk/general/g.mapset/g.mapset.html (rev 0)
+++ grass/trunk/general/g.mapset/g.mapset.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,25 @@
+<h2>DESCRIPTION</h2>
+
+<em>g.mapset</em> allows to change the current mapset
+
+<h2>NOTES</h2>
+
+The shell continues to use the history for the old mapset. To change this
+you can switch the history to the new settings by commands:<BR>
+<BR>
+<div class="code"><pre>
+ history -w
+ history -r /$GISDBASE/$LOCATION/$MAPSET/.bash_history
+ HISTFILE=/$GISDBASE/$LOCATION/$MAPSET/.bash_history
+</pre></div><BR>
+
+<h2>SEE ALSO</h2>
+
+<em><a HREF="g.gisenv.html">g.gisenv</a></em><br>
+<em><a HREF="g.mapsets.html">g.mapsets</a></em><br>
+
+<h2>AUTHOR</h2>
+
+Radim Blazek
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/general/g.mapsets/description.html
===================================================================
--- grass/trunk/general/g.mapsets/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/general/g.mapsets/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,138 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-For basic information about Grass <em>mapset</em>, <em>location</em>
-and <em>data base</em> refer to <a HREF="helptext.html">GRASS Quickstart</a>.
-
-<p>
-A <em>mapset</em> holds a distinct set of data layers,
-each relevant to the same (or a subset of the same) geographic region,
-and each drawn in the same map coordinate system.
-At the outset of every GRASS session, the user identifies a
-GRASS data base, location, and mapset that are to be the
-user's <em>current data base</em>, <em>current location</em>,
-and <em>current mapset</em> for the duration of the session;
-any maps created by the user during the session
-will be stored under the <em>current mapset</em> set at the session's outset.
-(see <em><a href="g.mapset.html">g.mapset</a></em> [without an "s"] and
- <em><a href="g.gisenv.html">g.gisenv</a></em> for changing the mapset
- with a session)
-
-<p>
-The user can add, modify, and delete data layers that exist
-under his <em>current mapset</em>. Although the user can
-also <em>access</em> (i.e., use) data that are stored under
-<em>other</em> mapsets in the same GRASS location using the
-<tt>mapname at mapsetname</tt> notation or mapset search path, the user
-can only make permanent changes (create or modify data)
-located in the <em>current mapset</em>. The user's
-<em>mapset search path</em> lists the order in which other
-mapsets in the same GRASS location can be searched and
-their data accessed by the user. The user can modify the
-listing and order in which these mapsets are accessed by
-modifying the mapset search path; this can be done using
-the <em>g.mapsets</em> command. This program allows the
-user to use other's relevant map data without altering the
-original data layer, and without taking up disk space with
-a copy of the original map. The <tt>mapname at mapsetname</tt>
-notation may be used irrespective of the mapset search path,
-i.e., any map found in another mapset with sufficient
-<em><a href="g.access.html">g.access</a></em> privileges may
-be called in such a manner.
-
-
-<p>
-<em>g.mapsets</em> shows the user available mapsets under
-the current GRASS location, lists mapsets to which the user
-currently has access, and lists the order in which
-accessible mapsets will be accessed by GRASS programs
-searching for data files. The user is then given the
-opportunity to add or delete mapset names from his search
-path, or modify the order in which mapsets will be
-accessed.
-
-<p>
-When the user specifies the name of a data base element file
-(e.g., a particular vector map, raster map,
-<a HREF="i.group.html">imagery</a> group file, etc.)
-to a GRASS program, the program searches for the named file
-under each of the mapsets listed in the user's mapset search path
-in the order listed there until the program finds a file
-of the given name. (Users can also specify a file by
-its mapset, to make explicit the mapset from which the file is to be
-drawn; e.g., the command:
-
-
-<div class="code"><pre>
-<b><a HREF="g.copy.html">g.copy</a> rast=</b><em>'soils.file at PERMANENT',my.soils</em>
-</pre></div>
-
-
-ensures that a new file named <em>my.soils</em> is to be a copy of
-the file <em>soils.file</em> from the mapset PERMANENT.)
-
-<p>
-It is common for a user to have the special mapset
-<b>PERMANENT</b> included in his mapset search path, as
-this mapset typically contains finished base maps relevant
-to many applications. Often, other mapsets which contain
-sets of interpreted map layers will be likewise included in
-the user's mapset search path. Suppose, for example, that
-the mapset <em>Soil_Maps</em> contains interpreted soils
-map layers to which the user wants access. The mapset
-
-<em>Soil_Maps</em> should then be included in the user's
-<em>search path</em> variable.
-
-<p>
-The <em>mapset search path</em> is saved as part of the
-current mapset. When the user works with that mapset in
-subsequent GRASS sessions, the previously saved mapset
-search path will be used (and will continue to be used
-until it is modified by the user with <em>g.mapsets</em>).
-
-
-<h2>NOTES</h2>
-
-<em>g.mapsets</em> sets the current <em>mapset search
-path</em> to the <em>mapsets</em> named on the command
-line. If <em>g.mapsets</em> is typed but no <em>mapset</em>
-names are specified by the user on the command line, the
-program will print the user's current mapset search path,
-list available mapsets, and prompt the user for a new
-mapset search path listing.
-
-<p>
-The <em>addmapset</em> parameter allows for extending an existing
-<em>mapset search path</em>.
-
-<p>
-Users can restrict others' access to their mapset files
-through use of the GRASS program
-
-<em><a HREF="g.access.html">g.access</a></em>.
-
-Mapsets to which access is restricted can still be listed
-in another's mapset search path; however, access to these
-mapsets will remain restricted.
-
-<h2>SEE ALSO</h2>
-
-<em>
- <a HREF="g.access.html">g.access</a>,
- <a HREF="g.copy.html">g.copy</a>,
- <a HREF="g.gisenv.html">g.gisenv</a>,
- <a HREF="g.list.html">g.list</a>,
- <a HREF="g.mapset.html">g.mapset</a>
-</em>
-
-<h2>AUTHOR</h2>
-
-Michael Shapiro,
-U.S.Army Construction Engineering
-Research Laboratory
-<p>
-Greg Koerper,
-ManTech Environmental Technology, Inc.
-
-<p>
-<i>Last changed: $Date$</i>
Copied: grass/trunk/general/g.mapsets/g.mapsets.html (from rev 32770, grass/trunk/general/g.mapsets/description.html)
===================================================================
--- grass/trunk/general/g.mapsets/g.mapsets.html (rev 0)
+++ grass/trunk/general/g.mapsets/g.mapsets.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,138 @@
+<h2>DESCRIPTION</h2>
+
+For basic information about Grass <em>mapset</em>, <em>location</em>
+and <em>data base</em> refer to <a HREF="helptext.html">GRASS Quickstart</a>.
+
+<p>
+A <em>mapset</em> holds a distinct set of data layers,
+each relevant to the same (or a subset of the same) geographic region,
+and each drawn in the same map coordinate system.
+At the outset of every GRASS session, the user identifies a
+GRASS data base, location, and mapset that are to be the
+user's <em>current data base</em>, <em>current location</em>,
+and <em>current mapset</em> for the duration of the session;
+any maps created by the user during the session
+will be stored under the <em>current mapset</em> set at the session's outset.
+(see <em><a href="g.mapset.html">g.mapset</a></em> [without an "s"] and
+ <em><a href="g.gisenv.html">g.gisenv</a></em> for changing the mapset
+ with a session)
+
+<p>
+The user can add, modify, and delete data layers that exist
+under his <em>current mapset</em>. Although the user can
+also <em>access</em> (i.e., use) data that are stored under
+<em>other</em> mapsets in the same GRASS location using the
+<tt>mapname at mapsetname</tt> notation or mapset search path, the user
+can only make permanent changes (create or modify data)
+located in the <em>current mapset</em>. The user's
+<em>mapset search path</em> lists the order in which other
+mapsets in the same GRASS location can be searched and
+their data accessed by the user. The user can modify the
+listing and order in which these mapsets are accessed by
+modifying the mapset search path; this can be done using
+the <em>g.mapsets</em> command. This program allows the
+user to use other's relevant map data without altering the
+original data layer, and without taking up disk space with
+a copy of the original map. The <tt>mapname at mapsetname</tt>
+notation may be used irrespective of the mapset search path,
+i.e., any map found in another mapset with sufficient
+<em><a href="g.access.html">g.access</a></em> privileges may
+be called in such a manner.
+
+
+<p>
+<em>g.mapsets</em> shows the user available mapsets under
+the current GRASS location, lists mapsets to which the user
+currently has access, and lists the order in which
+accessible mapsets will be accessed by GRASS programs
+searching for data files. The user is then given the
+opportunity to add or delete mapset names from his search
+path, or modify the order in which mapsets will be
+accessed.
+
+<p>
+When the user specifies the name of a data base element file
+(e.g., a particular vector map, raster map,
+<a HREF="i.group.html">imagery</a> group file, etc.)
+to a GRASS program, the program searches for the named file
+under each of the mapsets listed in the user's mapset search path
+in the order listed there until the program finds a file
+of the given name. (Users can also specify a file by
+its mapset, to make explicit the mapset from which the file is to be
+drawn; e.g., the command:
+
+
+<div class="code"><pre>
+<b><a HREF="g.copy.html">g.copy</a> rast=</b><em>'soils.file at PERMANENT',my.soils</em>
+</pre></div>
+
+
+ensures that a new file named <em>my.soils</em> is to be a copy of
+the file <em>soils.file</em> from the mapset PERMANENT.)
+
+<p>
+It is common for a user to have the special mapset
+<b>PERMANENT</b> included in his mapset search path, as
+this mapset typically contains finished base maps relevant
+to many applications. Often, other mapsets which contain
+sets of interpreted map layers will be likewise included in
+the user's mapset search path. Suppose, for example, that
+the mapset <em>Soil_Maps</em> contains interpreted soils
+map layers to which the user wants access. The mapset
+
+<em>Soil_Maps</em> should then be included in the user's
+<em>search path</em> variable.
+
+<p>
+The <em>mapset search path</em> is saved as part of the
+current mapset. When the user works with that mapset in
+subsequent GRASS sessions, the previously saved mapset
+search path will be used (and will continue to be used
+until it is modified by the user with <em>g.mapsets</em>).
+
+
+<h2>NOTES</h2>
+
+<em>g.mapsets</em> sets the current <em>mapset search
+path</em> to the <em>mapsets</em> named on the command
+line. If <em>g.mapsets</em> is typed but no <em>mapset</em>
+names are specified by the user on the command line, the
+program will print the user's current mapset search path,
+list available mapsets, and prompt the user for a new
+mapset search path listing.
+
+<p>
+The <em>addmapset</em> parameter allows for extending an existing
+<em>mapset search path</em>.
+
+<p>
+Users can restrict others' access to their mapset files
+through use of the GRASS program
+
+<em><a HREF="g.access.html">g.access</a></em>.
+
+Mapsets to which access is restricted can still be listed
+in another's mapset search path; however, access to these
+mapsets will remain restricted.
+
+<h2>SEE ALSO</h2>
+
+<em>
+ <a HREF="g.access.html">g.access</a>,
+ <a HREF="g.copy.html">g.copy</a>,
+ <a HREF="g.gisenv.html">g.gisenv</a>,
+ <a HREF="g.list.html">g.list</a>,
+ <a HREF="g.mapset.html">g.mapset</a>
+</em>
+
+<h2>AUTHOR</h2>
+
+Michael Shapiro,
+U.S.Army Construction Engineering
+Research Laboratory
+<p>
+Greg Koerper,
+ManTech Environmental Technology, Inc.
+
+<p>
+<i>Last changed: $Date$</i>
Deleted: grass/trunk/general/g.message/description.html
===================================================================
--- grass/trunk/general/g.message/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/general/g.message/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,81 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<p>
-This program is to be used in shell/perl/python scripts, so the author does not
-need to use the <tt>echo</tt> program. The advantage of <em>g.message</em> is
-that it formats messages just like other GRASS modules do and that its
-functionality is influenced by the <tt>GRASS_VERBOSE</tt> and
-<tt>GRASS_MESSAGE_FORMAT</tt> environment variables.
-</p>
-<p>
-The program can be used for standard informative messages as well as warnings
-(<b>-w</b> flag) and fatal errors (<b>-e</b> flag). For debugging
-purposes, the <b>-d</b> flag will cause <em>g.message</em> to print a debugging
-message at the given level.
-</p>
-
-<h2>NOTES</h2>
-
-Messages containing "<tt>=</tt>" must use the full <b>message=</b> syntax so
-the parser doesn't get confused.
-<P>
-If you want a long message (mutli-line) to be dealt with as a single
-paragraph, use a single call to <em>g.message</em> with text split in the
-script using the backslash as the last character. (In shell scripts don't
-close the "quote")
-<P>
-A blank line may be obtained with: <tt>g.message ""</tt>
-<P>
-Redundant whitespace will be stripped away.
-<P>
-It's advisable to single quote the messages that are to be printed literally.
-It prevents a number of characters (most notably, space and the dollar sign
-'<tt>$</tt>') from being treated specifically by the Shell.
-<P>
-When it is necessary to include, for example, a variable's value as part of
-the message, the double quotes may be used, which do not deprive the
-dollar sign of its special variable-expansion powers.
-<P>
-While it is known that the interactive Bash instances may treat the
-exclamation mark '<tt>!</tt>' character specifically (making single quoting
-of it necessary), it shouldn't be the case for the non-interactive
-instances of Bash. None the less, to avoid context-based confusion later on
-you are enouraged to single-quote messages that do not require
-<tt>$VARIABLE</tt> expansion.
-<P>
-
-<h4>VERBOSITY LEVELS</h4>
-Controlled by the "<tt>GRASS_VERBOSE</tt>" environment variable. Typically this
-is set using the <tt>--quiet</tt> or <tt>--verbose</tt> command line options.
-<ul>
-<li>0 - only errors and warnings are printed
-<li>1 - progress messages are printed
-<li>2 - all module messages are printed
-<li>3 - additional verbose messages are printed
-</ul>
-
-<h4>DEBUG LEVELS</h4>
-Controlled by the "<tt>DEBUG</tt>" GRASS <i>gisenv</i> variable. (set with
-<em><a href="g.gisenv.html">g.gisenv</a></em>)
-<BR>
-Recommended levels:
-<ul>
-<li>1 - message is printed once or few times per module
-<li>3 - each row (raster) or line (vector)
-<li>5 - each cell (raster) or point (vector)
-</ul>
-
-<h2>SEE ALSO</h2>
-<em>
-<a href="variables.html">GRASS variables and environment variables</a>,<br>
-<a href="g.gisenv.html">g.gisenv</a>,
-<a href="g.parser.html">g.parser</a>
-</em>
-
-
-<h2>AUTHOR</h2>
-
-Jachym Cepicky
-
-<p>
-<i>Last changed: $Date$</i>
Copied: grass/trunk/general/g.message/g.message.html (from rev 32770, grass/trunk/general/g.message/description.html)
===================================================================
--- grass/trunk/general/g.message/g.message.html (rev 0)
+++ grass/trunk/general/g.message/g.message.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,81 @@
+<h2>DESCRIPTION</h2>
+
+<p>
+This program is to be used in shell/perl/python scripts, so the author does not
+need to use the <tt>echo</tt> program. The advantage of <em>g.message</em> is
+that it formats messages just like other GRASS modules do and that its
+functionality is influenced by the <tt>GRASS_VERBOSE</tt> and
+<tt>GRASS_MESSAGE_FORMAT</tt> environment variables.
+</p>
+<p>
+The program can be used for standard informative messages as well as warnings
+(<b>-w</b> flag) and fatal errors (<b>-e</b> flag). For debugging
+purposes, the <b>-d</b> flag will cause <em>g.message</em> to print a debugging
+message at the given level.
+</p>
+
+<h2>NOTES</h2>
+
+Messages containing "<tt>=</tt>" must use the full <b>message=</b> syntax so
+the parser doesn't get confused.
+<P>
+If you want a long message (mutli-line) to be dealt with as a single
+paragraph, use a single call to <em>g.message</em> with text split in the
+script using the backslash as the last character. (In shell scripts don't
+close the "quote")
+<P>
+A blank line may be obtained with: <tt>g.message ""</tt>
+<P>
+Redundant whitespace will be stripped away.
+<P>
+It's advisable to single quote the messages that are to be printed literally.
+It prevents a number of characters (most notably, space and the dollar sign
+'<tt>$</tt>') from being treated specifically by the Shell.
+<P>
+When it is necessary to include, for example, a variable's value as part of
+the message, the double quotes may be used, which do not deprive the
+dollar sign of its special variable-expansion powers.
+<P>
+While it is known that the interactive Bash instances may treat the
+exclamation mark '<tt>!</tt>' character specifically (making single quoting
+of it necessary), it shouldn't be the case for the non-interactive
+instances of Bash. None the less, to avoid context-based confusion later on
+you are enouraged to single-quote messages that do not require
+<tt>$VARIABLE</tt> expansion.
+<P>
+
+<h4>VERBOSITY LEVELS</h4>
+Controlled by the "<tt>GRASS_VERBOSE</tt>" environment variable. Typically this
+is set using the <tt>--quiet</tt> or <tt>--verbose</tt> command line options.
+<ul>
+<li>0 - only errors and warnings are printed
+<li>1 - progress messages are printed
+<li>2 - all module messages are printed
+<li>3 - additional verbose messages are printed
+</ul>
+
+<h4>DEBUG LEVELS</h4>
+Controlled by the "<tt>DEBUG</tt>" GRASS <i>gisenv</i> variable. (set with
+<em><a href="g.gisenv.html">g.gisenv</a></em>)
+<BR>
+Recommended levels:
+<ul>
+<li>1 - message is printed once or few times per module
+<li>3 - each row (raster) or line (vector)
+<li>5 - each cell (raster) or point (vector)
+</ul>
+
+<h2>SEE ALSO</h2>
+<em>
+<a href="variables.html">GRASS variables and environment variables</a>,<br>
+<a href="g.gisenv.html">g.gisenv</a>,
+<a href="g.parser.html">g.parser</a>
+</em>
+
+
+<h2>AUTHOR</h2>
+
+Jachym Cepicky
+
+<p>
+<i>Last changed: $Date$</i>
Deleted: grass/trunk/general/g.mkfontcap/description.html
===================================================================
--- grass/trunk/general/g.mkfontcap/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/general/g.mkfontcap/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,56 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-<p>
-<EM>g.mkfontcap</EM> is a utilty to generate a GRASS font configuration file
-("fontcap") containing details of the fonts available on the current system.
-If <a href="http://freetype.sourceforge.net/">Freetype</a> is not installed,
-the font list will be limited to the set of Hershey stroke fonts supplied
-with GRASS. With Freetype enabled however, the module will recursively scan
-all files within a predefined hierarchy to find Freetype-compatible scalable
-fonts. The list of directories scanned is currently:
-<div class="code"><pre>
- /usr/lib/X11/fonts
- /usr/share/X11/fonts
- /usr/share/fonts
- ${HOME}/Library/Fonts
- /Library/Fonts
- /System/Library/Fonts
- ${WINDIR}/Fonts
-</pre></div>
-These correspond to directories where fonts can be found on some common
-operating systems. Extra directories to search can easily by added using the
-<em>extradirs</em> parameter, which accepts a comma-separated list. An extra
-directory may optionally contain an environment variable <em>at the start</em>
-of the string, if enclosed in ${xxx} syntax (see examples above).</p>
-
-<p>The module will normally write to the standard fontcap file location,
-<tt>$GISBASE/etc/fontcap</tt>. If the environment variable
-<strong>GRASS_FONT_CAP</strong> is set, the output will instead be written
-to the file specified by that variable. This is useful if you don't have
-permission to modify <tt>$GISBASE/etc/fontcap</tt>: in this case you can
-use e.g.
-
-<div class="code"><pre>
-# use local file version instead of system copy
-GRASS_FONT_CAP=$HOME/.gfontcap
-export $GRASS_FONT_CAP
-
-g.mkfontcap
-</pre></div>
-
-to create a personal copy and then to make GRASS use that file
-instead of the system copy.
-</p>
-
-<p>The output list of fonts is sorted first by type (Stroke fonts first,
-followed by Freetype) and within each type by the short name of the font.</p>
-
-<H2>SEE ALSO</H2>
-
-<EM><a href="d.font.html">d.font</a></EM>
-
-<H2>AUTHOR</H2>
-
-Paul Kelly
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/general/g.mkfontcap/g.mkfontcap.html (from rev 32770, grass/trunk/general/g.mkfontcap/description.html)
===================================================================
--- grass/trunk/general/g.mkfontcap/g.mkfontcap.html (rev 0)
+++ grass/trunk/general/g.mkfontcap/g.mkfontcap.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,56 @@
+<H2>DESCRIPTION</H2>
+
+<p>
+<EM>g.mkfontcap</EM> is a utilty to generate a GRASS font configuration file
+("fontcap") containing details of the fonts available on the current system.
+If <a href="http://freetype.sourceforge.net/">Freetype</a> is not installed,
+the font list will be limited to the set of Hershey stroke fonts supplied
+with GRASS. With Freetype enabled however, the module will recursively scan
+all files within a predefined hierarchy to find Freetype-compatible scalable
+fonts. The list of directories scanned is currently:
+<div class="code"><pre>
+ /usr/lib/X11/fonts
+ /usr/share/X11/fonts
+ /usr/share/fonts
+ ${HOME}/Library/Fonts
+ /Library/Fonts
+ /System/Library/Fonts
+ ${WINDIR}/Fonts
+</pre></div>
+These correspond to directories where fonts can be found on some common
+operating systems. Extra directories to search can easily by added using the
+<em>extradirs</em> parameter, which accepts a comma-separated list. An extra
+directory may optionally contain an environment variable <em>at the start</em>
+of the string, if enclosed in ${xxx} syntax (see examples above).</p>
+
+<p>The module will normally write to the standard fontcap file location,
+<tt>$GISBASE/etc/fontcap</tt>. If the environment variable
+<strong>GRASS_FONT_CAP</strong> is set, the output will instead be written
+to the file specified by that variable. This is useful if you don't have
+permission to modify <tt>$GISBASE/etc/fontcap</tt>: in this case you can
+use e.g.
+
+<div class="code"><pre>
+# use local file version instead of system copy
+GRASS_FONT_CAP=$HOME/.gfontcap
+export $GRASS_FONT_CAP
+
+g.mkfontcap
+</pre></div>
+
+to create a personal copy and then to make GRASS use that file
+instead of the system copy.
+</p>
+
+<p>The output list of fonts is sorted first by type (Stroke fonts first,
+followed by Freetype) and within each type by the short name of the font.</p>
+
+<H2>SEE ALSO</H2>
+
+<EM><a href="d.font.html">d.font</a></EM>
+
+<H2>AUTHOR</H2>
+
+Paul Kelly
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/general/g.parser/description.html
===================================================================
--- grass/trunk/general/g.parser/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/general/g.parser/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,416 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-<head>
-<title>g.parser</title>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link rel="stylesheet" href="grassdocs.css" type="text/css">
-</head>
-<body bgcolor="white">
-
-<img src="grass_logo.png" alt="GRASS logo"><hr align=center size=6 noshade>
-
-<h2>NAME</h2>
-<em><b>g.parser</b></em>
-
-<H2>DESCRIPTION</H2>
-
-The <em>g.parser</em> module provides full parser support for GRASS scripts,
-including an auto-generated GUI interface, help page template, and command
-line option checking. In this way a simple script can very quickly be made
-into a full-fledged GRASS module.
-<P>
-
-<H2>OPTIONS</H2>
-
-After parsing the arguments are stored in environment variables for use in your
-scripts. These variables are named "GIS_FLAG_<NAME>" for flags and
-"GIS_OPT_<NAME>" for options.
-The names of variables are converted to upper case. For example if an option
-with key <b>input</b> was defined in the script header, the value will be
-available in variable <b>GIS_OPT_INPUT</b> and the value of flag with key <b>f</b>
-will be available in variable <b>GIS_FLAG_F</b>.
-<P>
-For flags, the value will be "1" if the flag was given, and "0" otherwise.
-<P>
-Typical header definitions are as follows:
-<div class="code"><pre>
-#%Module
-#% description: g.parser test script
-#%End
-#%flag
-#% key: f
-#% description: A flag
-#%end
-#%option
-#% key: raster
-#% type: string
-#% gisprompt: old,cell,raster
-#% description: Raster input map
-#% required : yes
-#%end
-</pre></div>
-
-<H2>NOTES</H2>
-
-An option can be instructed to allow multiple inputs by adding the following line:
-<pre>#% multiple : yes</pre>
-While this will only directly change the <i>Usage</i> section of the help
-screen, the option's environmental string may be easily parsed from within
-a script. For example, individual comma separated identities for an option
-named "input" can be parsed with the following Bash shell code:
-
-<div class="code"><pre>IFS=,
-for opt in $GIS_OPT_INPUT ; do
- ... "$opt"
-done
-</pre></div>
-
-<P>
-A "<tt>guisection</tt>" field may be added to each option and flag to specify
-that the options should appear in multiple tabs in the auto-generated GUI.
-Any options without a <tt>guisection</tt> field go into the "Options" tab.
-For example:
-<pre>#% guisection: tabname</pre>
-would put that option in a tab named <i>tabname</i>.
-
-<P>
-A "<tt>key_desc</tt>" field may be added to each option to specify the text that
-appears in the module's usage help section. For example:
-<pre>#% key_desc: filename</pre>
-added to an <b>input</b> option would create the usage summary
-<tt>[input=filename]</tt>.
-
-<P>
-If a script is run with --o, G_parser() will set <tt>GRASS_OVERWRITE=1</tt>,
-which has the same effect as passing --o to every module which is run
-from the script.
-Similarly, passing --q or --v will set <tt>GRASS_VERBOSE</tt> to 0 or 3
-respectively, which has the same effect as passing --q or --v to every
-module which is run from the script.
-Rather than checking whether --o, --q or --v were used, you should be
-checking $GRASS_OVERWRITE and/or $GRASS_VERBOSE instead. If those
-variables are set, the script should behave the same way regardless of
-whether they were set by --o, --q or --v being passed to the script or
-set by other means.
-
-<H2>AUTOMATED SCRIPT CREATION</H2>
-
-The flag <em>--script</em> added to a GRASS command, generates shell output.
-To write out a <em>g.parser</em> boilerplate for easy prototyping of shell
-scripts, the flag <em>--script</em> can be added to any GRASS command. Example:
-
-<div class="code"><pre>
-v.in.db --script
-</pre></div>
-
-<H2>Help page template (HTML)</H2>
-
-The flag <em>--html-description</em> added to a GRASS command, generates a
-related help page template in HTML. Example:
-
-<div class="code"><pre>
-v.in.db --html-description
-</pre></div>
-
-<H2>GUI window parser (XML)</H2>
-
-The flag <em>--interface-description</em> added to a GRASS command, generates a
-related help page template in XML. Example:
-
-<div class="code"><pre>
-v.in.db --interface-description
-</pre></div>
-
-<H2>GUI window parser (TclTk)</H2>
-
-The flag <em>--tcltk</em> added to a GRASS command, generates a
-a XML description of the GUI interface. Example
-
-<div class="code"><pre>
-v.in.db --tcltk
-</pre></div>
-
-
-<H2>TRANSLATION</h2>
-
-<em>g.parser</em> provides some support for translating the options of scripts.
-If called with the -t switch before the script filename like this
-
-<div class="code"><pre>
-g.parser -t somescriptfile
-</pre></div>
-
-<em>g.parser</em> will print the text of the translatable options to
-<tt>stdout</tt>, one per line, and exit. This is for internal use within
-the build system to prepare GRASS scripts for translation.
-
-
-<H2>EXAMPLES</H2>
-
-<h3>Example code for SHELL</h3>
-
-<div class="code"><pre>
-#!/bin/sh
-
-# g.parser demo script for shell programing
-
-#%Module
-#% description: g.parser test script
-#%End
-#%flag
-#% key: f
-#% description: A flag
-#%END
-#%option
-#% key: raster
-#% type: string
-#% gisprompt: old,cell,raster
-#% description: Raster input map
-#% required : yes
-#%end
-#%option
-#% key: vector
-#% type: string
-#% gisprompt: old,vector,vector
-#% description: Vector input map
-#% required : yes
-#%end
-#%option
-#% key: option1
-#% type: string
-#% description: An option
-#% required : no
-#%end
-
-if [ -z "$GISBASE" ] ; then
- echo "You must be in GRASS GIS to run this program." 1>&2
- exit 1
-fi
-
-if [ "$1" != "@ARGS_PARSED@" ] ; then
- exec g.parser "$0" "$@"
-fi
-
-#### add your code below ####
-echo ""
-
-if [ $GIS_FLAG_F -eq 1 ] ; then
- echo "Flag -f set"
-else
- echo "Flag -f not set"
-fi
-
-# test if parameter present:
-if [ -n "$GIS_OPT_OPTION1" ] ; then
- echo "Value of GIS_OPT_OPTION1: '$GIS_OPT_OPTION1'"
-fi
-
-echo "Value of GIS_OPT_RASTER: '$GIS_OPT_RASTER'"
-echo "Value of GIS_OPT_VECTOR: '$GIS_OPT_VECTOR'"
-
-</pre></div>
-
-
-<h3>Example code for Python</h3>
-
-<div class="code"><pre>
-#!/usr/bin/python
-
-# g.parser demo script for python programing
-
-#%Module
-#% description: g.parser test script (python)
-#%End
-#%flag
-#% key: f
-#% description: A flag
-#%END
-#%option
-#% key: raster
-#% type: string
-#% gisprompt: old,cell,raster
-#% description: Raster input map
-#% required : yes
-#%end
-#%option
-#% key: vector
-#% type: string
-#% gisprompt: old,vector,vector
-#% description: Vector input map
-#% required : yes
-#%end
-#%option
-#% key: option1
-#% type: string
-#% description: An option
-#% required : no
-#%end
-
-import os
-import sys
-
-def main():
-
- #### add your code here ####
-
- print ""
-
- if ( os.getenv('GIS_FLAG_F') == "1" ):
- print "Flag -f set"
- else:
- print "Flag -f not set"
-
- # test if parameter present:
- if ( os.getenv("GIS_OPT_OPTION1") != "" ):
- print "Value of GIS_OPT_OPTION1: '%s'" % os.getenv('GIS_OPT_OPTION1')
-
- print "Value of GIS_OPT_RASTER: '%s'" % os.getenv('GIS_OPT_RASTER')
- print "Value of GIS_OPT_VECTOR: '%s'" % os.getenv('GIS_OPT_VECTOR')
-
- #### end of your code ####
- return
-
-if __name__ == "__main__":
-
- if !os.getenv("GISBASE"):
- print >> sys.stderr, "You must be in GRASS GIS to run this program."
- sys.exit(0)
-
- if ( len(sys.argv) <= 1 or sys.argv[1] != "@ARGS_PARSED@" ):
- os.execvp("g.parser", [sys.argv[0]] + sys.argv)
- else:
- main();
-
-</pre></div>
-
-<P>
-The <tt>test.py</tt> script will provide following help text:
-<P>
-<div class="code"><pre>
-./test.py --help
-
-Description:
- g.parser test script (python)
-
-Usage:
- test.sh [-f] option=name
-
-Flags:
- -f a flag
-
-Parameters:
- option an option
-</pre></div>
-
-
-<h3>Example code for Perl</h3>
-
-<div class="code"><pre>
-#!/usr/bin/perl -w
-use strict;
-
-# g.parser demo script
-
-#%Module
-#% description: g.parser test script (perl)
-#% keywords: keyword1, keyword2
-#%End
-#%flag
-#% key: f
-#% description: A flag
-#%END
-#%option
-#% key: raster
-#% type: string
-#% gisprompt: old,cell,raster
-#% description: Raster input map
-#% required : yes
-#%end
-#%option
-#% key: vector
-#% type: string
-#% gisprompt: old,vector,vector
-#% description: Vector input map
-#% required : yes
-#%end
-#%option
-#% key: option1
-#% type: string
-#% description: An option
-#% required : no
-#%end
-
-if ( !$ENV{'GISBASE'} ) {
- printf(STDERR "You must be in GRASS GIS to run this program.\n");
- exit 1;
-}
-
-
-if( $ARGV[0] ne '@ARGS_PARSED@' ){
- my $arg = "";
- for (my $i=0; $i < @ARGV;$i++) {
- $arg .= " $ARGV[$i] ";
- }
- system("$ENV{GISBASE}/bin/g.parser $0 $arg");
- exit;
-}
-
-#### add your code here ####
-print "\n";
-if ( $ENV{'GIS_FLAG_F'} eq "1" ){
- print "Flag -f set\n"
-}
-else {
- print "Flag -f not set\n"
-}
-
-printf ("Value of GIS_OPT_option1: '%s'\n", $ENV{'GIS_OPT_OPTION1'});
-printf ("Value of GIS_OPT_raster: '%s'\n", $ENV{'GIS_OPT_RASTER'});
-printf ("Value of GIS_OPT_vect: '%s'\n", $ENV{'GIS_OPT_VECTOR'});
-
-#### end of your code ####
-
-</pre></div>
-
-
-<P>
-The <tt>test.pl</tt> script will provide following help text:
-<P>
-<div class="code"><pre>
-./test.pl --help
-
-Description:
- g.parser test script (perl)
-
-Usage:
- test.sh [-f] option=name
-
-Flags:
- -f a flag
-
-Parameters:
- option an option
-</pre></div>
-
-
-<H2>SEE ALSO</H2>
-
-<EM>
-<A HREF="d.ask.html">d.ask</A>,
-<A HREF="d.menu.html">d.menu</A>,
-<A HREF="g.ask.html">g.ask</A>,
-<A HREF="g.filename.html">g.filename</A>,
-<A HREF="g.findfile.html">g.findfile</A>,
-<A HREF="g.tempfile.html">g.tempfile</A>,
-</EM>
-and the <tt>SUBMITTING_SCRIPTS</tt> file in the GRASS source code.
-
-
-<H2>AUTHOR</H2>
-
-Glynn Clements
-<p>
-<i>Last changed: $Date$</i>
-</p>
-</body>
-</html>
Copied: grass/trunk/general/g.parser/g.parser.html (from rev 32770, grass/trunk/general/g.parser/description.html)
===================================================================
--- grass/trunk/general/g.parser/g.parser.html (rev 0)
+++ grass/trunk/general/g.parser/g.parser.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,416 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<head>
+<title>g.parser</title>
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
+<link rel="stylesheet" href="grassdocs.css" type="text/css">
+</head>
+<body bgcolor="white">
+
+<img src="grass_logo.png" alt="GRASS logo"><hr align=center size=6 noshade>
+
+<h2>NAME</h2>
+<em><b>g.parser</b></em>
+
+<H2>DESCRIPTION</H2>
+
+The <em>g.parser</em> module provides full parser support for GRASS scripts,
+including an auto-generated GUI interface, help page template, and command
+line option checking. In this way a simple script can very quickly be made
+into a full-fledged GRASS module.
+<P>
+
+<H2>OPTIONS</H2>
+
+After parsing the arguments are stored in environment variables for use in your
+scripts. These variables are named "GIS_FLAG_<NAME>" for flags and
+"GIS_OPT_<NAME>" for options.
+The names of variables are converted to upper case. For example if an option
+with key <b>input</b> was defined in the script header, the value will be
+available in variable <b>GIS_OPT_INPUT</b> and the value of flag with key <b>f</b>
+will be available in variable <b>GIS_FLAG_F</b>.
+<P>
+For flags, the value will be "1" if the flag was given, and "0" otherwise.
+<P>
+Typical header definitions are as follows:
+<div class="code"><pre>
+#%Module
+#% description: g.parser test script
+#%End
+#%flag
+#% key: f
+#% description: A flag
+#%end
+#%option
+#% key: raster
+#% type: string
+#% gisprompt: old,cell,raster
+#% description: Raster input map
+#% required : yes
+#%end
+</pre></div>
+
+<H2>NOTES</H2>
+
+An option can be instructed to allow multiple inputs by adding the following line:
+<pre>#% multiple : yes</pre>
+While this will only directly change the <i>Usage</i> section of the help
+screen, the option's environmental string may be easily parsed from within
+a script. For example, individual comma separated identities for an option
+named "input" can be parsed with the following Bash shell code:
+
+<div class="code"><pre>IFS=,
+for opt in $GIS_OPT_INPUT ; do
+ ... "$opt"
+done
+</pre></div>
+
+<P>
+A "<tt>guisection</tt>" field may be added to each option and flag to specify
+that the options should appear in multiple tabs in the auto-generated GUI.
+Any options without a <tt>guisection</tt> field go into the "Options" tab.
+For example:
+<pre>#% guisection: tabname</pre>
+would put that option in a tab named <i>tabname</i>.
+
+<P>
+A "<tt>key_desc</tt>" field may be added to each option to specify the text that
+appears in the module's usage help section. For example:
+<pre>#% key_desc: filename</pre>
+added to an <b>input</b> option would create the usage summary
+<tt>[input=filename]</tt>.
+
+<P>
+If a script is run with --o, G_parser() will set <tt>GRASS_OVERWRITE=1</tt>,
+which has the same effect as passing --o to every module which is run
+from the script.
+Similarly, passing --q or --v will set <tt>GRASS_VERBOSE</tt> to 0 or 3
+respectively, which has the same effect as passing --q or --v to every
+module which is run from the script.
+Rather than checking whether --o, --q or --v were used, you should be
+checking $GRASS_OVERWRITE and/or $GRASS_VERBOSE instead. If those
+variables are set, the script should behave the same way regardless of
+whether they were set by --o, --q or --v being passed to the script or
+set by other means.
+
+<H2>AUTOMATED SCRIPT CREATION</H2>
+
+The flag <em>--script</em> added to a GRASS command, generates shell output.
+To write out a <em>g.parser</em> boilerplate for easy prototyping of shell
+scripts, the flag <em>--script</em> can be added to any GRASS command. Example:
+
+<div class="code"><pre>
+v.in.db --script
+</pre></div>
+
+<H2>Help page template (HTML)</H2>
+
+The flag <em>--html-description</em> added to a GRASS command, generates a
+related help page template in HTML. Example:
+
+<div class="code"><pre>
+v.in.db --html-description
+</pre></div>
+
+<H2>GUI window parser (XML)</H2>
+
+The flag <em>--interface-description</em> added to a GRASS command, generates a
+related help page template in XML. Example:
+
+<div class="code"><pre>
+v.in.db --interface-description
+</pre></div>
+
+<H2>GUI window parser (TclTk)</H2>
+
+The flag <em>--tcltk</em> added to a GRASS command, generates a
+a XML description of the GUI interface. Example
+
+<div class="code"><pre>
+v.in.db --tcltk
+</pre></div>
+
+
+<H2>TRANSLATION</h2>
+
+<em>g.parser</em> provides some support for translating the options of scripts.
+If called with the -t switch before the script filename like this
+
+<div class="code"><pre>
+g.parser -t somescriptfile
+</pre></div>
+
+<em>g.parser</em> will print the text of the translatable options to
+<tt>stdout</tt>, one per line, and exit. This is for internal use within
+the build system to prepare GRASS scripts for translation.
+
+
+<H2>EXAMPLES</H2>
+
+<h3>Example code for SHELL</h3>
+
+<div class="code"><pre>
+#!/bin/sh
+
+# g.parser demo script for shell programing
+
+#%Module
+#% description: g.parser test script
+#%End
+#%flag
+#% key: f
+#% description: A flag
+#%END
+#%option
+#% key: raster
+#% type: string
+#% gisprompt: old,cell,raster
+#% description: Raster input map
+#% required : yes
+#%end
+#%option
+#% key: vector
+#% type: string
+#% gisprompt: old,vector,vector
+#% description: Vector input map
+#% required : yes
+#%end
+#%option
+#% key: option1
+#% type: string
+#% description: An option
+#% required : no
+#%end
+
+if [ -z "$GISBASE" ] ; then
+ echo "You must be in GRASS GIS to run this program." 1>&2
+ exit 1
+fi
+
+if [ "$1" != "@ARGS_PARSED@" ] ; then
+ exec g.parser "$0" "$@"
+fi
+
+#### add your code below ####
+echo ""
+
+if [ $GIS_FLAG_F -eq 1 ] ; then
+ echo "Flag -f set"
+else
+ echo "Flag -f not set"
+fi
+
+# test if parameter present:
+if [ -n "$GIS_OPT_OPTION1" ] ; then
+ echo "Value of GIS_OPT_OPTION1: '$GIS_OPT_OPTION1'"
+fi
+
+echo "Value of GIS_OPT_RASTER: '$GIS_OPT_RASTER'"
+echo "Value of GIS_OPT_VECTOR: '$GIS_OPT_VECTOR'"
+
+</pre></div>
+
+
+<h3>Example code for Python</h3>
+
+<div class="code"><pre>
+#!/usr/bin/python
+
+# g.parser demo script for python programing
+
+#%Module
+#% description: g.parser test script (python)
+#%End
+#%flag
+#% key: f
+#% description: A flag
+#%END
+#%option
+#% key: raster
+#% type: string
+#% gisprompt: old,cell,raster
+#% description: Raster input map
+#% required : yes
+#%end
+#%option
+#% key: vector
+#% type: string
+#% gisprompt: old,vector,vector
+#% description: Vector input map
+#% required : yes
+#%end
+#%option
+#% key: option1
+#% type: string
+#% description: An option
+#% required : no
+#%end
+
+import os
+import sys
+
+def main():
+
+ #### add your code here ####
+
+ print ""
+
+ if ( os.getenv('GIS_FLAG_F') == "1" ):
+ print "Flag -f set"
+ else:
+ print "Flag -f not set"
+
+ # test if parameter present:
+ if ( os.getenv("GIS_OPT_OPTION1") != "" ):
+ print "Value of GIS_OPT_OPTION1: '%s'" % os.getenv('GIS_OPT_OPTION1')
+
+ print "Value of GIS_OPT_RASTER: '%s'" % os.getenv('GIS_OPT_RASTER')
+ print "Value of GIS_OPT_VECTOR: '%s'" % os.getenv('GIS_OPT_VECTOR')
+
+ #### end of your code ####
+ return
+
+if __name__ == "__main__":
+
+ if !os.getenv("GISBASE"):
+ print >> sys.stderr, "You must be in GRASS GIS to run this program."
+ sys.exit(0)
+
+ if ( len(sys.argv) <= 1 or sys.argv[1] != "@ARGS_PARSED@" ):
+ os.execvp("g.parser", [sys.argv[0]] + sys.argv)
+ else:
+ main();
+
+</pre></div>
+
+<P>
+The <tt>test.py</tt> script will provide following help text:
+<P>
+<div class="code"><pre>
+./test.py --help
+
+Description:
+ g.parser test script (python)
+
+Usage:
+ test.sh [-f] option=name
+
+Flags:
+ -f a flag
+
+Parameters:
+ option an option
+</pre></div>
+
+
+<h3>Example code for Perl</h3>
+
+<div class="code"><pre>
+#!/usr/bin/perl -w
+use strict;
+
+# g.parser demo script
+
+#%Module
+#% description: g.parser test script (perl)
+#% keywords: keyword1, keyword2
+#%End
+#%flag
+#% key: f
+#% description: A flag
+#%END
+#%option
+#% key: raster
+#% type: string
+#% gisprompt: old,cell,raster
+#% description: Raster input map
+#% required : yes
+#%end
+#%option
+#% key: vector
+#% type: string
+#% gisprompt: old,vector,vector
+#% description: Vector input map
+#% required : yes
+#%end
+#%option
+#% key: option1
+#% type: string
+#% description: An option
+#% required : no
+#%end
+
+if ( !$ENV{'GISBASE'} ) {
+ printf(STDERR "You must be in GRASS GIS to run this program.\n");
+ exit 1;
+}
+
+
+if( $ARGV[0] ne '@ARGS_PARSED@' ){
+ my $arg = "";
+ for (my $i=0; $i < @ARGV;$i++) {
+ $arg .= " $ARGV[$i] ";
+ }
+ system("$ENV{GISBASE}/bin/g.parser $0 $arg");
+ exit;
+}
+
+#### add your code here ####
+print "\n";
+if ( $ENV{'GIS_FLAG_F'} eq "1" ){
+ print "Flag -f set\n"
+}
+else {
+ print "Flag -f not set\n"
+}
+
+printf ("Value of GIS_OPT_option1: '%s'\n", $ENV{'GIS_OPT_OPTION1'});
+printf ("Value of GIS_OPT_raster: '%s'\n", $ENV{'GIS_OPT_RASTER'});
+printf ("Value of GIS_OPT_vect: '%s'\n", $ENV{'GIS_OPT_VECTOR'});
+
+#### end of your code ####
+
+</pre></div>
+
+
+<P>
+The <tt>test.pl</tt> script will provide following help text:
+<P>
+<div class="code"><pre>
+./test.pl --help
+
+Description:
+ g.parser test script (perl)
+
+Usage:
+ test.sh [-f] option=name
+
+Flags:
+ -f a flag
+
+Parameters:
+ option an option
+</pre></div>
+
+
+<H2>SEE ALSO</H2>
+
+<EM>
+<A HREF="d.ask.html">d.ask</A>,
+<A HREF="d.menu.html">d.menu</A>,
+<A HREF="g.ask.html">g.ask</A>,
+<A HREF="g.filename.html">g.filename</A>,
+<A HREF="g.findfile.html">g.findfile</A>,
+<A HREF="g.tempfile.html">g.tempfile</A>,
+</EM>
+and the <tt>SUBMITTING_SCRIPTS</tt> file in the GRASS source code.
+
+
+<H2>AUTHOR</H2>
+
+Glynn Clements
+<p>
+<i>Last changed: $Date$</i>
+</p>
+</body>
+</html>
Deleted: grass/trunk/general/g.pnmcomp/description.html
===================================================================
--- grass/trunk/general/g.pnmcomp/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/general/g.pnmcomp/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,42 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-(culled from the mailing list)
-<BR>
-<pre>
-From: Glynn Clements
-Subject: Re: [GRASS5] Re: [GRASSLIST:10403] Transparency added
-Date: Sun, 19 Feb 2006 20:17:59 +0000
-
-g.pnmcomp isn't meant for end users. It's an internal tool for use by
-a Tcl/Tk GUI.
-
-In essence, g.pnmcomp generates a PPM image by overlaying a series of
-PPM/PGM pairs (PPM = RGB image, PGM = alpha channel).
-
-The intention is that d.* programs will emit PPM/PGM pairs (by way of
-the PNG-driver code being integrated into libraster). The GUI will
-manage a set of layers; each layer consists of the data necessary to
-generate a PPM/PGM pair.
-
-Whenever the layer "stack" changes (by adding, removing, hiding,
-showing or re-ordering layers), the GUI will render any layers for
-which it doesn't already have the PPM/PGM pair, then re-run g.pnmcomp
-to generate the final image (just redoing the composition is a lot
-faster than redrawing everything).
-
-A C/C++ GUI would either have g.pnmcomp's functionality (image
-composition) built-in, or would use the system's graphics API to
-perform composition (for translucent layers, you would need OpenGL or
-the Render extension, or something else which supports translucent
-rendering).
-
-Tk doesn't support transparent (masked) true-colour images (it does
-support transparent GIFs, but that's limited to 256 colours), and an
-image composition routine in Tcl would be unacceptably slow, hence
-the existence of g.pnmcomp.
-</pre>
-
-<H2>AUTHOR</H2>
-Glynn Clements
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/general/g.pnmcomp/g.pnmcomp.html (from rev 32770, grass/trunk/general/g.pnmcomp/description.html)
===================================================================
--- grass/trunk/general/g.pnmcomp/g.pnmcomp.html (rev 0)
+++ grass/trunk/general/g.pnmcomp/g.pnmcomp.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,42 @@
+<H2>DESCRIPTION</H2>
+
+(culled from the mailing list)
+<BR>
+<pre>
+From: Glynn Clements
+Subject: Re: [GRASS5] Re: [GRASSLIST:10403] Transparency added
+Date: Sun, 19 Feb 2006 20:17:59 +0000
+
+g.pnmcomp isn't meant for end users. It's an internal tool for use by
+a Tcl/Tk GUI.
+
+In essence, g.pnmcomp generates a PPM image by overlaying a series of
+PPM/PGM pairs (PPM = RGB image, PGM = alpha channel).
+
+The intention is that d.* programs will emit PPM/PGM pairs (by way of
+the PNG-driver code being integrated into libraster). The GUI will
+manage a set of layers; each layer consists of the data necessary to
+generate a PPM/PGM pair.
+
+Whenever the layer "stack" changes (by adding, removing, hiding,
+showing or re-ordering layers), the GUI will render any layers for
+which it doesn't already have the PPM/PGM pair, then re-run g.pnmcomp
+to generate the final image (just redoing the composition is a lot
+faster than redrawing everything).
+
+A C/C++ GUI would either have g.pnmcomp's functionality (image
+composition) built-in, or would use the system's graphics API to
+perform composition (for translucent layers, you would need OpenGL or
+the Render extension, or something else which supports translucent
+rendering).
+
+Tk doesn't support transparent (masked) true-colour images (it does
+support transparent GIFs, but that's limited to 256 colours), and an
+image composition routine in Tcl would be unacceptably slow, hence
+the existence of g.pnmcomp.
+</pre>
+
+<H2>AUTHOR</H2>
+Glynn Clements
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/general/g.proj/description.html
===================================================================
--- grass/trunk/general/g.proj/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/general/g.proj/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,221 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<P><em>g.proj</em> provides a means of converting a co-ordinate system
-description (i.e. projection information) between various formats.
-It requires <A HREF="http://www.gdal.org/ogr/">OGR</A> to compile. The basic
-functionality of the module is to report the projection information for the
-current location, either in conventional GRASS (-p flag) or PROJ.4 (-j flag)
-format.</P>
-
-<P>Projection information may also be output in the Well-Known Text (WKT)
-format popularised
-by proprietary GIS. In addition, if one of the parameters <em>georef</em>,
-<em>wkt</em>, <em>proj4</em> or <em>epsg</em> is specified, rather than the
-projection information being read from the current location it is imported
-from an external source as follows:
-<dl>
-<dt>georef=<em>filename</em></dt>
-<dd><em>g.proj</em> attempts to invoke GDAL and OGR in turn to read a
-georeferenced file <em>filename</em>. The projection information will be
-read from this file. If the file is not georeferenced or cannot be read,
-XY (unprojected) will be used.</dd>
-
-<dt>wkt=<em>filename</em> or <em>-</em></dt>
-<dd>The file <em>filename</em> should contain a projection description in WKT
-format with or without line-breaks (e.g. a '.prj' file). If <em>-</em> is given
-for the filename, the WKT description will be read from stdin rather than a
-file.</dd>
-
-<dt>proj4=<em>description</em> or <em>-</em></dt>
-<dd><em>description</em> should be a projection description in
-<A HREF="http://remotesensing.org/proj/">PROJ.4</a> format, enclosed in
-quotation marks if there are any spaces. If <em>-</em> is given for
-<em>description</em>, the PROJ.4 description will be read from stdin rather
-than as a directly-supplied command-line parameter.</dd>
-
-<dt>epsg=<em>number</em></dt>
-<dd><em>number</em> should correspond to the index number of a valid
-co-ordinate system in the <a href="http://www.epsg.org/CurrentDB.html">EPSG
-database</a>. EPSG code support is based upon a local copy of the GDAL CSV
-co-ordinate system and datum information files, stored in the directory
-${GISBASE}/etc/ogr_csv. These can be updated if necessary to support future
-revisions of the EPSG database.</dd>
-</dl>
-</P>
-
-<P>The -p, -j, -w, etc. flags are all functional when importing projection
-information from an external source, meaning that <em>g.proj</em> can be
-used to convert between representations of the information. It is
-<strong>not</strong> required that either the input or output be in GRASS
-format.</P>
-
-<P>In addition however, if the -c flag is specified, <em>g.proj</em> will
-create new GRASS projection files (PROJ_INFO, PROJ_UNITS, WIND and
-DEFAULT_WIND) based on the imported information. If the <em>location</em>
-parameter is specified in addition to -c, then a new location will be created.
-Otherwise the projection information files in the current location will be
-overwritten. The program will warn before doing this only if command-line
-interactive mode (<em>-i</em> flag) is selected.</P>
-
-<P>The final mode of operation of g.proj is to report on the datum
-information and datum transformation parameters associated with the
-co-ordinate system. The -d flag will report a human-readable summary of
-this.</P>
-
-<H2>NOTES</H2>
-
-<P>If the input co-ordinate system contains a datum name but no
-transformation parameters, and there is more than one suitable parameter set
-available (according to the files datum.table and datumtransform.table in
-${GISBASE}/etc), g.proj will check the value of the <em>datumtrans</em>
-option and act according to the following:<br>
-<strong>-1:</strong> List available parameter sets in a GUI-parsable (but also
-human-readable) format and exit.<br>
-<strong>0 (default):</strong> Continue without specifying parameters - if
-used when creating a location, other GRASS modules will use the "default"
-(likely non-optimum) parameters for this datum if necessary in the future.<br>
-<strong>Any other number less than or equal to the number of parameter sets
-available for this datum:</strong> Choose this parameter set and add it to the
-co-ordinate system description.<br>
-If the module is being used from the command-line through an interactive
-terminal, the <em>-i</em> flag can be specified to enable interactive
-selection of the parameter set, and the value of <em>datumtrans</em> (if
-specified) is ignored.<br>
-If the <em>-t</em> flag is specified, the module will attempt to change the
-datum transformation parameters using one of the above two methods
-<strong>even if</strong> a valid parameter set is already specified in the
-input co-ordinate system.</P>
-
-<P>Output is simply based on the input projection information. g.proj does
-<strong>not</strong> attempt to verify that the co-ordinate system thus
-described matches an existing system in use in the world. In particular,
-this means there are no EPSG Authority codes in the WKT output.</P>
-
-<P>WKT format shows the false eastings and northings in the projected unit
-(e.g. meters, feet) but in PROJ format it should always be given in meters.</P>
-
-<P>The maximum size of input WKT or PROJ.4 projection descriptions is
-limited to 8000 bytes.</P>
-
-<H2>EXAMPLES</H2>
-
-Print the projection information for the current location:<br>
-
-<div class="code"><pre>
-g.proj -p
-</pre></div>
-
-<p>
-Create a '.prj' file in ESRI format corresponding to the current location:<br>
-
-<div class="code"><pre>
-g.proj -wef > irish_grid.prj
-</pre></div>
-
-<p>
-Read the projection information from a geotiff file and print it in PROJ.4
-format:<br>
-
-<div class="code"><pre>
-g.proj -jf georef=ASTER_DEM20020508161837.tif
-</pre></div>
-
-<p>
-Convert the PROJ.4 projection description contained in a text file to WKT
-format:<br>
-
-<div class="code"><pre>
-cat proj4.description | g.proj -w proj4=-
-</pre></div>
-
-<p>
-Create a new location with the co-ordinate system referred to by EPSG code
-4326 (Latitude-Longitude/WGS84), without explicitly specifiying datum
-transformation parameters:<br>
-
-<div class="code"><pre>
-g.proj -c epsg=4326 location=latlong
-</pre></div>
-
-<p>
-Create a new location with the co-ordinate system referred to by ESRI-EPSG code
-900913 (<a href="http://spatialreference.org/ref/user/6/">Google Mercator Projection</a>)<br>
-
-<div class="code"><pre>
-g.proj -c epsg=900913 loc=google
-</pre></div>
-
-<p>
-Create a new location with the co-ordinate system referred to by EPSG code
-29900 (Irish Grid), selecting datum transformation parameter set no. 2:<br>
-
-<div class="code"><pre>
-g.proj -c epsg=29900 datumtrans=2 location=irish_grid
-</pre></div>
-
-<p>
-Create a new location with the same co-ordinate system as the current
-location:<br>
-
-<div class="code"><pre>
-g.proj -c location=newloc
-</pre></div>
-
-<p>
-Interactively change/update the datum transformation parameters for the
-current location:<br>
-
-<div class="code"><pre>
-g.proj -itc
-</pre></div>
-
-<p>
-Create a new location with the co-ordinate system from a WKT definition
-stored in a text file:<br>
-
-<div class="code"><pre>
-g.proj -c wkt=irish_grid.prj location=irish_grid
-</pre></div>
-
-<p>
-Reproject external raster map to current GRASS projection (does not always make sense!)
-using the GDAL 'gdalwarp' tool. We recommend to use the ERDAS/Img format and not
-to use the ESRI style of WKT:<br>
-<div class="code"><pre>
-# example for 30x30 pixel resolution (enforce with -tr to avoid odd values)
-gdalwarp -of HFA -tr 30 30 -t_srs "`g.proj -wf`" aster.img aster_tmerc.img
-</pre></div>
-
-<p>
-Reproject external vector map to current GRASS projection
-using the OGR 'ogr2ogr' tool:<br>
-<div class="code"><pre>
-ogr2ogr -t_srs "`g.proj -wf`" polbnda_italy_GB_ovest.shp polbnda_italy_LL.shp
-</pre></div>
-
-
-<H2>REFERENCES</H2>
-
-<a href="http://proj.maptools.org">PROJ 4</a>: Projection/datum support library<br>
-<a href="http://www.gdal.org">GDAL raster library and toolset</a><br>
-<a href="http://www.gdal.org/ogr/">OGR vector library and toolset</a>
-
-<P>
-<B>Further reading</B>
-<ul>
-<li> <a href="http://www.asprs.org/resources/grids/">ASPRS Grids and Datum</a>
-<li> <a href="http://www.mapref.org">MapRef - The Collection of Map Projections and Reference Systems for Europe</a>
-<li> <a href="http://www.remotesensing.org/geotiff/proj_list/">Projections Transform List</a> (PROJ4)
-</ul>
-
-<H2>SEE ALSO</H2>
-
-<EM><a href="g.setproj.html">g.setproj</a></EM><BR>
-<EM><a href="r.in.gdal.html">r.in.gdal</a></EM><BR>
-<EM><a href="v.in.ogr.html">v.in.ogr</a></EM>
-
-<h2>AUTHOR</h2>
-
-Paul Kelly
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/general/g.proj/g.proj.html (from rev 32770, grass/trunk/general/g.proj/description.html)
===================================================================
--- grass/trunk/general/g.proj/g.proj.html (rev 0)
+++ grass/trunk/general/g.proj/g.proj.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,221 @@
+<h2>DESCRIPTION</h2>
+
+<P><em>g.proj</em> provides a means of converting a co-ordinate system
+description (i.e. projection information) between various formats.
+It requires <A HREF="http://www.gdal.org/ogr/">OGR</A> to compile. The basic
+functionality of the module is to report the projection information for the
+current location, either in conventional GRASS (-p flag) or PROJ.4 (-j flag)
+format.</P>
+
+<P>Projection information may also be output in the Well-Known Text (WKT)
+format popularised
+by proprietary GIS. In addition, if one of the parameters <em>georef</em>,
+<em>wkt</em>, <em>proj4</em> or <em>epsg</em> is specified, rather than the
+projection information being read from the current location it is imported
+from an external source as follows:
+<dl>
+<dt>georef=<em>filename</em></dt>
+<dd><em>g.proj</em> attempts to invoke GDAL and OGR in turn to read a
+georeferenced file <em>filename</em>. The projection information will be
+read from this file. If the file is not georeferenced or cannot be read,
+XY (unprojected) will be used.</dd>
+
+<dt>wkt=<em>filename</em> or <em>-</em></dt>
+<dd>The file <em>filename</em> should contain a projection description in WKT
+format with or without line-breaks (e.g. a '.prj' file). If <em>-</em> is given
+for the filename, the WKT description will be read from stdin rather than a
+file.</dd>
+
+<dt>proj4=<em>description</em> or <em>-</em></dt>
+<dd><em>description</em> should be a projection description in
+<A HREF="http://remotesensing.org/proj/">PROJ.4</a> format, enclosed in
+quotation marks if there are any spaces. If <em>-</em> is given for
+<em>description</em>, the PROJ.4 description will be read from stdin rather
+than as a directly-supplied command-line parameter.</dd>
+
+<dt>epsg=<em>number</em></dt>
+<dd><em>number</em> should correspond to the index number of a valid
+co-ordinate system in the <a href="http://www.epsg.org/CurrentDB.html">EPSG
+database</a>. EPSG code support is based upon a local copy of the GDAL CSV
+co-ordinate system and datum information files, stored in the directory
+${GISBASE}/etc/ogr_csv. These can be updated if necessary to support future
+revisions of the EPSG database.</dd>
+</dl>
+</P>
+
+<P>The -p, -j, -w, etc. flags are all functional when importing projection
+information from an external source, meaning that <em>g.proj</em> can be
+used to convert between representations of the information. It is
+<strong>not</strong> required that either the input or output be in GRASS
+format.</P>
+
+<P>In addition however, if the -c flag is specified, <em>g.proj</em> will
+create new GRASS projection files (PROJ_INFO, PROJ_UNITS, WIND and
+DEFAULT_WIND) based on the imported information. If the <em>location</em>
+parameter is specified in addition to -c, then a new location will be created.
+Otherwise the projection information files in the current location will be
+overwritten. The program will warn before doing this only if command-line
+interactive mode (<em>-i</em> flag) is selected.</P>
+
+<P>The final mode of operation of g.proj is to report on the datum
+information and datum transformation parameters associated with the
+co-ordinate system. The -d flag will report a human-readable summary of
+this.</P>
+
+<H2>NOTES</H2>
+
+<P>If the input co-ordinate system contains a datum name but no
+transformation parameters, and there is more than one suitable parameter set
+available (according to the files datum.table and datumtransform.table in
+${GISBASE}/etc), g.proj will check the value of the <em>datumtrans</em>
+option and act according to the following:<br>
+<strong>-1:</strong> List available parameter sets in a GUI-parsable (but also
+human-readable) format and exit.<br>
+<strong>0 (default):</strong> Continue without specifying parameters - if
+used when creating a location, other GRASS modules will use the "default"
+(likely non-optimum) parameters for this datum if necessary in the future.<br>
+<strong>Any other number less than or equal to the number of parameter sets
+available for this datum:</strong> Choose this parameter set and add it to the
+co-ordinate system description.<br>
+If the module is being used from the command-line through an interactive
+terminal, the <em>-i</em> flag can be specified to enable interactive
+selection of the parameter set, and the value of <em>datumtrans</em> (if
+specified) is ignored.<br>
+If the <em>-t</em> flag is specified, the module will attempt to change the
+datum transformation parameters using one of the above two methods
+<strong>even if</strong> a valid parameter set is already specified in the
+input co-ordinate system.</P>
+
+<P>Output is simply based on the input projection information. g.proj does
+<strong>not</strong> attempt to verify that the co-ordinate system thus
+described matches an existing system in use in the world. In particular,
+this means there are no EPSG Authority codes in the WKT output.</P>
+
+<P>WKT format shows the false eastings and northings in the projected unit
+(e.g. meters, feet) but in PROJ format it should always be given in meters.</P>
+
+<P>The maximum size of input WKT or PROJ.4 projection descriptions is
+limited to 8000 bytes.</P>
+
+<H2>EXAMPLES</H2>
+
+Print the projection information for the current location:<br>
+
+<div class="code"><pre>
+g.proj -p
+</pre></div>
+
+<p>
+Create a '.prj' file in ESRI format corresponding to the current location:<br>
+
+<div class="code"><pre>
+g.proj -wef > irish_grid.prj
+</pre></div>
+
+<p>
+Read the projection information from a geotiff file and print it in PROJ.4
+format:<br>
+
+<div class="code"><pre>
+g.proj -jf georef=ASTER_DEM20020508161837.tif
+</pre></div>
+
+<p>
+Convert the PROJ.4 projection description contained in a text file to WKT
+format:<br>
+
+<div class="code"><pre>
+cat proj4.description | g.proj -w proj4=-
+</pre></div>
+
+<p>
+Create a new location with the co-ordinate system referred to by EPSG code
+4326 (Latitude-Longitude/WGS84), without explicitly specifiying datum
+transformation parameters:<br>
+
+<div class="code"><pre>
+g.proj -c epsg=4326 location=latlong
+</pre></div>
+
+<p>
+Create a new location with the co-ordinate system referred to by ESRI-EPSG code
+900913 (<a href="http://spatialreference.org/ref/user/6/">Google Mercator Projection</a>)<br>
+
+<div class="code"><pre>
+g.proj -c epsg=900913 loc=google
+</pre></div>
+
+<p>
+Create a new location with the co-ordinate system referred to by EPSG code
+29900 (Irish Grid), selecting datum transformation parameter set no. 2:<br>
+
+<div class="code"><pre>
+g.proj -c epsg=29900 datumtrans=2 location=irish_grid
+</pre></div>
+
+<p>
+Create a new location with the same co-ordinate system as the current
+location:<br>
+
+<div class="code"><pre>
+g.proj -c location=newloc
+</pre></div>
+
+<p>
+Interactively change/update the datum transformation parameters for the
+current location:<br>
+
+<div class="code"><pre>
+g.proj -itc
+</pre></div>
+
+<p>
+Create a new location with the co-ordinate system from a WKT definition
+stored in a text file:<br>
+
+<div class="code"><pre>
+g.proj -c wkt=irish_grid.prj location=irish_grid
+</pre></div>
+
+<p>
+Reproject external raster map to current GRASS projection (does not always make sense!)
+using the GDAL 'gdalwarp' tool. We recommend to use the ERDAS/Img format and not
+to use the ESRI style of WKT:<br>
+<div class="code"><pre>
+# example for 30x30 pixel resolution (enforce with -tr to avoid odd values)
+gdalwarp -of HFA -tr 30 30 -t_srs "`g.proj -wf`" aster.img aster_tmerc.img
+</pre></div>
+
+<p>
+Reproject external vector map to current GRASS projection
+using the OGR 'ogr2ogr' tool:<br>
+<div class="code"><pre>
+ogr2ogr -t_srs "`g.proj -wf`" polbnda_italy_GB_ovest.shp polbnda_italy_LL.shp
+</pre></div>
+
+
+<H2>REFERENCES</H2>
+
+<a href="http://proj.maptools.org">PROJ 4</a>: Projection/datum support library<br>
+<a href="http://www.gdal.org">GDAL raster library and toolset</a><br>
+<a href="http://www.gdal.org/ogr/">OGR vector library and toolset</a>
+
+<P>
+<B>Further reading</B>
+<ul>
+<li> <a href="http://www.asprs.org/resources/grids/">ASPRS Grids and Datum</a>
+<li> <a href="http://www.mapref.org">MapRef - The Collection of Map Projections and Reference Systems for Europe</a>
+<li> <a href="http://www.remotesensing.org/geotiff/proj_list/">Projections Transform List</a> (PROJ4)
+</ul>
+
+<H2>SEE ALSO</H2>
+
+<EM><a href="g.setproj.html">g.setproj</a></EM><BR>
+<EM><a href="r.in.gdal.html">r.in.gdal</a></EM><BR>
+<EM><a href="v.in.ogr.html">v.in.ogr</a></EM>
+
+<h2>AUTHOR</h2>
+
+Paul Kelly
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/general/g.region/description.html
===================================================================
--- grass/trunk/general/g.region/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/general/g.region/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,497 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-The <em>g.region</em> module allows the user to manage the
-settings of the current geographic region. These regional
-boundaries can be set by the user directly and/or set from
-a region definition file (stored under the
-<kbd>windows</kbd> directory in the user's current
-mapset). The user can create, modify, and store as many
-geographic region definitions as desired for any given
-mapset. However, only one of these geographic region
-definitions will be current at any given moment, for a
-specified mapset; i.e., GRASS programs that respect the
-geographic region settings will use the current geographic
-region settings.
-
-
-<h2>DEFINITIONS</h2>
-
-<dl>
-<dt><b>Region:</b>
-
-<dd>In GRASS, a <em>region</em> refers to a geographic area
-with some defined boundaries, based on a specific map
-coordinate system and map projection. Each region also has
-associated with it the specific east-west and north-south
-resolutions of its smallest units (rectangular units called
-"cells").
-
-<p>
-
-The region's boundaries are given as the northernmost,
-southernmost, easternmost, and westernmost points that
-define its extent (cell edges). The north and south boundaries
-are commonly called <em>northings</em>, while the east and west
-boundaries are called <em>eastings</em>.
-
-<p>
-
-The region's cell resolution defines the size of the
-smallest piece of data recognized (imported, analyzed,
-displayed, stored, etc.) by GRASS modules affected by the
-current region settings. The north-south and east-west cell
-resolutions need not be the same, thus allowing non-square
-data cells to exist.
-
-<P>
-Typically all raster and display modules are affected by the current
-region settings, but not vector modules.
-Some special modules diverge from this rule, for example raster import
-modules and <em>v.in.region</em>.
-
-
-<dt><b>Default Region:</b>
-
-<dd>Each GRASS LOCATION has a fixed
-geographic region, called the default geographic region
-(stored in the region file <kbd>DEFAULT_WIND</kbd> under
-the special mapset <kbd>PERMANENT</kbd>), that defines the
-extent of the data base. While this provides a starting
-point for defining new geographic regions, user-defined
-geographic regions need not fall within this geographic
-region. The current region can be reset to the default region
-with the <b>-d</b> flag. The default region is initially set
-when the location is first created and can be reset using the
-<b>-s</b> flag.
-
-<dt><b>Current Region:</b>
-
-<dd>Each mapset has a current geographic region. This
-region defines the geographic area in which all GRASS
-displays and raster analyses will be done. Raster data will be
-resampled, if necessary, to meet the cell resolutions of
-the current geographic region setting.
-
-<dt><b>Saved Regions:</b>
-
-<dd>Each GRASS MAPSET may contain any number of
-pre-defined, and named, geographic regions. These region
-definitions are stored in the user's current mapset
-location under the <kbd>windows</kbd> directory (also
-referred to as the user's saved region definitions).
-Any of these pre-defined geographic regions
-may be selected, by name, to become the current geographic
-region. Users may also access saved region definitions
-stored under other mapsets in the current location, if
-these mapsets are included in the user's mapset search
-path or the '@' operator is used (<tt>region_name at mapset</tt>).
-</dl>
-
-
-<h2>NOTES</h2>
-
-After all updates have been applied, the current region's
-southern and western boundaries are (silently) adjusted so
-that the north/south distance is a multiple of the
-north/south resolution and that the east/west distance is a
-multiple of the east/west resolution.
-
-<p>
-With the <b>-a</b> flag all four boundaries are adjusted
-to be even multiples of the resolution, aligning the region to the
-resolution supplied by the user. The default is to
-align the region resolution to match the region boundaries.
-
-<p>
-The <b>-m</b> flag will report the region resolution in meters. The
-resolution is calculated by averaging the resolution at the region
-boundaries. This resolution is calculated by dividing the geodesic
-distance in meters at the boundary by the number of rows or columns.
-For example the east / west resolution (ewres) is determined from an
-average of the geodesic distances at the North and South boundaries
-divided by the number of columns.
-<!-- add'l info. include?
-Print the region resolution in meters (from geodesic). With no other
-flags the default output format is shell stype (-g). The region resolution
-represents the center of the map. The resolutions are calculated at the four
-outside edges, then the two NS edges are averaged and the two EW edges are
-averaged, the results finally printed.
--->
-
-
-<p>
-The <b>-p</b> (or <b>-g</b>) option is recognized
-last. This means that all changes are applied to the
-region settings before printing occurs.
-<P>
-The <b>-g</b> flag prints the current region settings in shell script style.
-This format can be given back to <em>g.region</em> on its command line.
-This may also be used to save region settings as shell environment variables
-with the UNIX eval command, "<tt>eval `g.region -g`</tt>".
-
-
-<h3>Additional parameter information:</h3>
-
-<dl>
-<dt><b>3dview=</b><em>name</em>
-<dd>Make current region settings same as those in the named
-3dview file, which holds the region that was current when
-the 3dview was saved.
-
-
-<dt><b>zoom=</b><em>name</em>
-<dd>Shrink current region settings to the smallest region
-encompassing all non-NULL data in the named raster map
-layer that fall inside the user's current region. In this
-way you can tightly zoom in on isolated clumps within a
-bigger map.
-<p>
-If the user also includes the <b>rast=</b><em>name</em>
-option on the command line, <b>zoom=</b><em>name</em> will
-set the current region settings to the smallest region
-encompassing all non-NULL data in the named <b>zoom</b> map
-that fall inside the region stated in the cell header for
-the named <b>raster</b> map.
-
-
-<dt><b>align=</b><em>name</em>
-
-<dd>Set the current resolution equal to that of the named
-raster map, and align the current region to a row and
-column edge in the named map. Alignment only moves the
-existing region edges outward to the edges of the next
-nearest cell in the named raster map - not to the named
-map's edges. To perform the latter function, use the
-<b>rast=</b><em>name</em> option.
-</dl>
-
-
-
-<h2>EXAMPLES</h2>
-
-<dl>
-<dt>
-<div class="code"><pre>
-g.region n=7360100 e=699000
-</pre></div>
-<dd> will reset the northing and easting for the current
-region, but leave the south edge, west edge, and the region
-cell resolutions unchanged.
-
-<p>
-
-<dt><div class="code"><pre>
-g.region n=51:36:05N e=10:10:05E s=51:29:55N w=9:59:55E res=0:00:01
-</pre></div>
-
-<dd> will reset the northing, easting, southing, westing and resolution
-for the current region, here in DMS latitude-longitude style
-(decimal degrees and degrees with decimal minutes can also be used).
-
-<p>
-
-<dt><div class="code"><pre>
-g.region -dp s=698000
-</pre></div>
-
-<dd> will set the current region from the default region
-for the GRASS data base location, reset the south edge to
-698000, and then print the result.
-
-<p>
-
-<dt><div class="code"><pre>
-g.region n=n+1000 w=w-500
-</pre></div>
-
-<dd> The n=<em>value</em> may also be specified as a
-function of its current value: n=n+<em>value</em>
-increases the current northing, while n=n-<em>value</em>
-decreases it. This is also true for s=<em>value</em>,
-e=<em>value</em>, and w=<em>value</em>. In this example
-the current region's northern boundary is extended by 1000
-units and the current region's western boundary is
-decreased by 500 units.
-
-<p>
-
-<dt><div class="code"><pre>
-g.region n=s+1000 e=w+1000
-</pre></div>
-
-<dd> This form allows the user to set the region boundary
-values relative to one another. Here, the northern
-boundary coordinate is set equal to 1000 units larger than
-the southern boundary's coordinate value, and the eastern
-boundary's coordinate value is set equal to 1000 units
-larger than the western boundary's coordinate value. The
-corresponding forms s=n-<em>value</em> and
-
-<p>
-
-w=e-<em>value</em> may be used to set the values of the
-region's southern and western boundaries, relative to the
-northern and eastern boundary values.
-
-
-<dt><div class="code"><pre>
-g.region rast=soils
-</pre></div>
-
-<dd> This form will make the current region settings
-exactly the same as those given in the cell header file for
-the raster map layer <em>soils</em>.
-
-<p>
-
-
-<dt><div class="code"><pre>
-g.region rast=soils zoom=soils
-</pre></div>
-
-<dd> This form will first look up the cell header file for
-the raster map layer <em>soils</em>, use this as the
-current region setting, and then shrink the region down to
-the smallest region which still encompasses all non-NULL
-data in the map layer <em>soils</em>. Note that if the
-parameter <em>rast=soils</em> were not specified, the
-zoom would shrink to encompass all non-NULL data values in
-the soils map that were located within the <i>current region</i>
-settings.
-
-<p>
-
-
-<dt><div class="code"><pre>
-g.region -up rast=soils
-</pre></div>
-
-<dd> The <b>-u</b> option suppresses the re-setting of the
-current region definition. This can be useful when it is
-desired to only extract region information. In this case,
-the cell header file for the soils map layer is printed
-without changing the current region settings.
-
-<p>
-
-<dt><div class="code"><pre>
-g.region -up zoom=soils save=soils
-</pre></div>
-
-<dd> This will zoom into the smallest region which
-encompasses all non-NULL soils data values, and save the
-new region settings in a file to be called <em>soils</em>
-and stored under the <kbd>windows</kbd> directory in the
-user's current mapset. The current region settings are not
-changed.
-<p>
-
-
-<dt><div class="code"><pre>
-g.region b=0 t=3000 tbres=200 res3=100
-g.region -p3
-</pre></div>
-
-<dd> This will define the 3D region for voxel computations.
-In this example a volume with bottom (0m) to top (3000m)
-at horizontal resolution (100m) and vertical resolution (200m)
-is defined.
-
-<p>
-
-<dt><div class="code"><pre>
-g.region -p
-</pre></div>
-
-<dd> This will print the current region in the format:
-
-<div class="code"><pre>
-projection: 1 (UTM)
-zone: 13
-datum: nad27
-ellipsoid: clark66
-north: 4928000
-south: 4914000
-west: 590000
-east: 609000
-nsres: 20
-ewres: 20
-rows: 700
-cols: 950
-</pre></div>
-
-<p>
-
-<dt><div class="code"><pre>
-g.region -p3
-</pre></div>
-
-<dd> This will print the current region and the 3D region (used for voxels)
-in the format:
-
-<div class="code"><pre>
-projection: 1 (UTM)
-zone: 13
-datum: nad27
-ellipsoid: clark66
-north: 4928000
-south: 4914000
-west: 590000
-east: 609000
-top: 1.00000000
-bottom: 0.00000000
-nsres: 20
-nsres3: 20
-ewres: 20
-ewres3: 20
-tbres: 1
-rows: 700
-rows3: 700
-cols: 950
-cols3: 950
-depths: 1
-</pre></div>
-
-<p>
-
-<dt><div class="code"><pre>
-g.region -g
-</pre></div>
-
-<dd> The <b>-g</b> option prints the region in the
-following script style (key=value) format:
-
-<div class="code"><pre>
-n=4928000
-s=4914000
-w=590000
-e=609000
-nsres=20
-ewres=20
-rows=700
-cols=950
-</pre></div>
-
-<p>
-
-<dt><div class="code"><pre>
-g.region -bg
-</pre></div>
-
-<dd> The <b>-bg</b> option prints the region in the
-following script style (key=value) format plus the
-boundary box in latitude-longitude/WGS84:
-
-<div class="code"><pre>
-n=4928000
-s=4914000
-w=590000
-e=609000
-nsres=20
-ewres=20
-rows=700
-cols=950
-LL_W=-103.87080682
-LL_E=-103.62942884
-LL_N=44.50164277
-LL_S=44.37302019
-</pre></div>
-
-<p>
-
-<dt><div class="code"><pre>
-g.region -l
-</pre></div>
-
-<dd> The <b>-l</b> option prints the region in the
-following format:
-
-<div class="code"><pre>
-long: -103.86789484 lat: 44.50165890 (north/west corner)
-long: -103.62895703 lat: 44.49904013 (north/east corner)
-long: -103.63190061 lat: 44.37303558 (south/east corner)
-long: -103.87032572 lat: 44.37564292 (south/west corner)
-rows: 700
-cols: 950
-Center longitude: 103:44:59.170374W [-103.74977]
-Center latitude: 44:26:14.439781N [44.43734]
-</pre></div>
-
-<p>
-
-<dt><div class="code"><pre>
-g.region -pm
-</pre></div>
-
-<dd> This will print the current region in the format
- (latitude-longitude location):
-
-<div class="code"><pre>
-projection: 3 (Latitude-Longitude)
-zone: 0
-ellipsoid: wgs84
-north: 90N
-south: 40N
-west: 20W
-east: 20E
-nsres: 928.73944902
-ewres: 352.74269109
-rows: 6000
-cols: 4800
-</pre></div>
-Note that the resolution is here reported in meters, not decimal degrees.
-
-</dl>
-
-<p>
-Usage example of <em>g.region</em> in a shell with external software:<br>
-<!-- why not 'v.in.ogr spatial=' ?? -->
-Extract spatial subset of external vector map 'soils.shp' to new external
-vector map 'soils_cut.shp' using the OGR 'ogr2ogr' tool:<br>
-
-<div class="code"><pre>
-eval `g.region -g`
-ogr2ogr -spat $w $s $e $n soils_cut.shp soils.shp
-</pre></div>
-
-This requires that the location/SHAPE file projection match.
-
-
-<p>
-Usage example of <em>g.proj</em> and <em>g.region</em> in a shell with external software:<br>
-Extract spatial subset of external raster map 'p016r035_7t20020524_z17_nn30.tif'
-to new external raster map'p016r035_7t20020524_nc_spm_wake_nn30.tif using the GDAL
-'gdalwarp' tool:<br>
-
-<div class="code"><pre>
-eval `g.region -g`
-gdalwarp -t_srs "`g.proj -wf`" -te $w $s $e $n \
- p016r035_7t20020524_z17_nn30.tif \
- p016r035_7t20020524_nc_spm_wake_nn30.tif
-</pre></div>
-
-Here the input raster map does not have to match the location
-projection since it is reprojected on the fly.
-
-
-
-<h2>SEE ALSO</h2>
-
-<em>
-<a HREF="d.zoom.html">d.zoom</a><br>
-<a HREF="g.access.html">g.access</a><br>
-<a HREF="g.mapsets.html">g.mapsets</a><br>
-<a HREF="g.proj.html">g.proj</a><BR>
-<a HREF="g.setproj.html">g.setproj</a><BR>
-environment variables: <a HREF="variables.html#internal">GRASS_REGION and WIND_OVERRIDE</a>
-</em>
-
-
-<h2>AUTHOR</h2>
-
-Michael Shapiro,
-U.S.Army Construction Engineering
-Research Laboratory
-
-<p>
-<i>Last changed: $Date$</i>
Copied: grass/trunk/general/g.region/g.region.html (from rev 32770, grass/trunk/general/g.region/description.html)
===================================================================
--- grass/trunk/general/g.region/g.region.html (rev 0)
+++ grass/trunk/general/g.region/g.region.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,497 @@
+<h2>DESCRIPTION</h2>
+
+The <em>g.region</em> module allows the user to manage the
+settings of the current geographic region. These regional
+boundaries can be set by the user directly and/or set from
+a region definition file (stored under the
+<kbd>windows</kbd> directory in the user's current
+mapset). The user can create, modify, and store as many
+geographic region definitions as desired for any given
+mapset. However, only one of these geographic region
+definitions will be current at any given moment, for a
+specified mapset; i.e., GRASS programs that respect the
+geographic region settings will use the current geographic
+region settings.
+
+
+<h2>DEFINITIONS</h2>
+
+<dl>
+<dt><b>Region:</b>
+
+<dd>In GRASS, a <em>region</em> refers to a geographic area
+with some defined boundaries, based on a specific map
+coordinate system and map projection. Each region also has
+associated with it the specific east-west and north-south
+resolutions of its smallest units (rectangular units called
+"cells").
+
+<p>
+
+The region's boundaries are given as the northernmost,
+southernmost, easternmost, and westernmost points that
+define its extent (cell edges). The north and south boundaries
+are commonly called <em>northings</em>, while the east and west
+boundaries are called <em>eastings</em>.
+
+<p>
+
+The region's cell resolution defines the size of the
+smallest piece of data recognized (imported, analyzed,
+displayed, stored, etc.) by GRASS modules affected by the
+current region settings. The north-south and east-west cell
+resolutions need not be the same, thus allowing non-square
+data cells to exist.
+
+<P>
+Typically all raster and display modules are affected by the current
+region settings, but not vector modules.
+Some special modules diverge from this rule, for example raster import
+modules and <em>v.in.region</em>.
+
+
+<dt><b>Default Region:</b>
+
+<dd>Each GRASS LOCATION has a fixed
+geographic region, called the default geographic region
+(stored in the region file <kbd>DEFAULT_WIND</kbd> under
+the special mapset <kbd>PERMANENT</kbd>), that defines the
+extent of the data base. While this provides a starting
+point for defining new geographic regions, user-defined
+geographic regions need not fall within this geographic
+region. The current region can be reset to the default region
+with the <b>-d</b> flag. The default region is initially set
+when the location is first created and can be reset using the
+<b>-s</b> flag.
+
+<dt><b>Current Region:</b>
+
+<dd>Each mapset has a current geographic region. This
+region defines the geographic area in which all GRASS
+displays and raster analyses will be done. Raster data will be
+resampled, if necessary, to meet the cell resolutions of
+the current geographic region setting.
+
+<dt><b>Saved Regions:</b>
+
+<dd>Each GRASS MAPSET may contain any number of
+pre-defined, and named, geographic regions. These region
+definitions are stored in the user's current mapset
+location under the <kbd>windows</kbd> directory (also
+referred to as the user's saved region definitions).
+Any of these pre-defined geographic regions
+may be selected, by name, to become the current geographic
+region. Users may also access saved region definitions
+stored under other mapsets in the current location, if
+these mapsets are included in the user's mapset search
+path or the '@' operator is used (<tt>region_name at mapset</tt>).
+</dl>
+
+
+<h2>NOTES</h2>
+
+After all updates have been applied, the current region's
+southern and western boundaries are (silently) adjusted so
+that the north/south distance is a multiple of the
+north/south resolution and that the east/west distance is a
+multiple of the east/west resolution.
+
+<p>
+With the <b>-a</b> flag all four boundaries are adjusted
+to be even multiples of the resolution, aligning the region to the
+resolution supplied by the user. The default is to
+align the region resolution to match the region boundaries.
+
+<p>
+The <b>-m</b> flag will report the region resolution in meters. The
+resolution is calculated by averaging the resolution at the region
+boundaries. This resolution is calculated by dividing the geodesic
+distance in meters at the boundary by the number of rows or columns.
+For example the east / west resolution (ewres) is determined from an
+average of the geodesic distances at the North and South boundaries
+divided by the number of columns.
+<!-- add'l info. include?
+Print the region resolution in meters (from geodesic). With no other
+flags the default output format is shell stype (-g). The region resolution
+represents the center of the map. The resolutions are calculated at the four
+outside edges, then the two NS edges are averaged and the two EW edges are
+averaged, the results finally printed.
+-->
+
+
+<p>
+The <b>-p</b> (or <b>-g</b>) option is recognized
+last. This means that all changes are applied to the
+region settings before printing occurs.
+<P>
+The <b>-g</b> flag prints the current region settings in shell script style.
+This format can be given back to <em>g.region</em> on its command line.
+This may also be used to save region settings as shell environment variables
+with the UNIX eval command, "<tt>eval `g.region -g`</tt>".
+
+
+<h3>Additional parameter information:</h3>
+
+<dl>
+<dt><b>3dview=</b><em>name</em>
+<dd>Make current region settings same as those in the named
+3dview file, which holds the region that was current when
+the 3dview was saved.
+
+
+<dt><b>zoom=</b><em>name</em>
+<dd>Shrink current region settings to the smallest region
+encompassing all non-NULL data in the named raster map
+layer that fall inside the user's current region. In this
+way you can tightly zoom in on isolated clumps within a
+bigger map.
+<p>
+If the user also includes the <b>rast=</b><em>name</em>
+option on the command line, <b>zoom=</b><em>name</em> will
+set the current region settings to the smallest region
+encompassing all non-NULL data in the named <b>zoom</b> map
+that fall inside the region stated in the cell header for
+the named <b>raster</b> map.
+
+
+<dt><b>align=</b><em>name</em>
+
+<dd>Set the current resolution equal to that of the named
+raster map, and align the current region to a row and
+column edge in the named map. Alignment only moves the
+existing region edges outward to the edges of the next
+nearest cell in the named raster map - not to the named
+map's edges. To perform the latter function, use the
+<b>rast=</b><em>name</em> option.
+</dl>
+
+
+
+<h2>EXAMPLES</h2>
+
+<dl>
+<dt>
+<div class="code"><pre>
+g.region n=7360100 e=699000
+</pre></div>
+<dd> will reset the northing and easting for the current
+region, but leave the south edge, west edge, and the region
+cell resolutions unchanged.
+
+<p>
+
+<dt><div class="code"><pre>
+g.region n=51:36:05N e=10:10:05E s=51:29:55N w=9:59:55E res=0:00:01
+</pre></div>
+
+<dd> will reset the northing, easting, southing, westing and resolution
+for the current region, here in DMS latitude-longitude style
+(decimal degrees and degrees with decimal minutes can also be used).
+
+<p>
+
+<dt><div class="code"><pre>
+g.region -dp s=698000
+</pre></div>
+
+<dd> will set the current region from the default region
+for the GRASS data base location, reset the south edge to
+698000, and then print the result.
+
+<p>
+
+<dt><div class="code"><pre>
+g.region n=n+1000 w=w-500
+</pre></div>
+
+<dd> The n=<em>value</em> may also be specified as a
+function of its current value: n=n+<em>value</em>
+increases the current northing, while n=n-<em>value</em>
+decreases it. This is also true for s=<em>value</em>,
+e=<em>value</em>, and w=<em>value</em>. In this example
+the current region's northern boundary is extended by 1000
+units and the current region's western boundary is
+decreased by 500 units.
+
+<p>
+
+<dt><div class="code"><pre>
+g.region n=s+1000 e=w+1000
+</pre></div>
+
+<dd> This form allows the user to set the region boundary
+values relative to one another. Here, the northern
+boundary coordinate is set equal to 1000 units larger than
+the southern boundary's coordinate value, and the eastern
+boundary's coordinate value is set equal to 1000 units
+larger than the western boundary's coordinate value. The
+corresponding forms s=n-<em>value</em> and
+
+<p>
+
+w=e-<em>value</em> may be used to set the values of the
+region's southern and western boundaries, relative to the
+northern and eastern boundary values.
+
+
+<dt><div class="code"><pre>
+g.region rast=soils
+</pre></div>
+
+<dd> This form will make the current region settings
+exactly the same as those given in the cell header file for
+the raster map layer <em>soils</em>.
+
+<p>
+
+
+<dt><div class="code"><pre>
+g.region rast=soils zoom=soils
+</pre></div>
+
+<dd> This form will first look up the cell header file for
+the raster map layer <em>soils</em>, use this as the
+current region setting, and then shrink the region down to
+the smallest region which still encompasses all non-NULL
+data in the map layer <em>soils</em>. Note that if the
+parameter <em>rast=soils</em> were not specified, the
+zoom would shrink to encompass all non-NULL data values in
+the soils map that were located within the <i>current region</i>
+settings.
+
+<p>
+
+
+<dt><div class="code"><pre>
+g.region -up rast=soils
+</pre></div>
+
+<dd> The <b>-u</b> option suppresses the re-setting of the
+current region definition. This can be useful when it is
+desired to only extract region information. In this case,
+the cell header file for the soils map layer is printed
+without changing the current region settings.
+
+<p>
+
+<dt><div class="code"><pre>
+g.region -up zoom=soils save=soils
+</pre></div>
+
+<dd> This will zoom into the smallest region which
+encompasses all non-NULL soils data values, and save the
+new region settings in a file to be called <em>soils</em>
+and stored under the <kbd>windows</kbd> directory in the
+user's current mapset. The current region settings are not
+changed.
+<p>
+
+
+<dt><div class="code"><pre>
+g.region b=0 t=3000 tbres=200 res3=100
+g.region -p3
+</pre></div>
+
+<dd> This will define the 3D region for voxel computations.
+In this example a volume with bottom (0m) to top (3000m)
+at horizontal resolution (100m) and vertical resolution (200m)
+is defined.
+
+<p>
+
+<dt><div class="code"><pre>
+g.region -p
+</pre></div>
+
+<dd> This will print the current region in the format:
+
+<div class="code"><pre>
+projection: 1 (UTM)
+zone: 13
+datum: nad27
+ellipsoid: clark66
+north: 4928000
+south: 4914000
+west: 590000
+east: 609000
+nsres: 20
+ewres: 20
+rows: 700
+cols: 950
+</pre></div>
+
+<p>
+
+<dt><div class="code"><pre>
+g.region -p3
+</pre></div>
+
+<dd> This will print the current region and the 3D region (used for voxels)
+in the format:
+
+<div class="code"><pre>
+projection: 1 (UTM)
+zone: 13
+datum: nad27
+ellipsoid: clark66
+north: 4928000
+south: 4914000
+west: 590000
+east: 609000
+top: 1.00000000
+bottom: 0.00000000
+nsres: 20
+nsres3: 20
+ewres: 20
+ewres3: 20
+tbres: 1
+rows: 700
+rows3: 700
+cols: 950
+cols3: 950
+depths: 1
+</pre></div>
+
+<p>
+
+<dt><div class="code"><pre>
+g.region -g
+</pre></div>
+
+<dd> The <b>-g</b> option prints the region in the
+following script style (key=value) format:
+
+<div class="code"><pre>
+n=4928000
+s=4914000
+w=590000
+e=609000
+nsres=20
+ewres=20
+rows=700
+cols=950
+</pre></div>
+
+<p>
+
+<dt><div class="code"><pre>
+g.region -bg
+</pre></div>
+
+<dd> The <b>-bg</b> option prints the region in the
+following script style (key=value) format plus the
+boundary box in latitude-longitude/WGS84:
+
+<div class="code"><pre>
+n=4928000
+s=4914000
+w=590000
+e=609000
+nsres=20
+ewres=20
+rows=700
+cols=950
+LL_W=-103.87080682
+LL_E=-103.62942884
+LL_N=44.50164277
+LL_S=44.37302019
+</pre></div>
+
+<p>
+
+<dt><div class="code"><pre>
+g.region -l
+</pre></div>
+
+<dd> The <b>-l</b> option prints the region in the
+following format:
+
+<div class="code"><pre>
+long: -103.86789484 lat: 44.50165890 (north/west corner)
+long: -103.62895703 lat: 44.49904013 (north/east corner)
+long: -103.63190061 lat: 44.37303558 (south/east corner)
+long: -103.87032572 lat: 44.37564292 (south/west corner)
+rows: 700
+cols: 950
+Center longitude: 103:44:59.170374W [-103.74977]
+Center latitude: 44:26:14.439781N [44.43734]
+</pre></div>
+
+<p>
+
+<dt><div class="code"><pre>
+g.region -pm
+</pre></div>
+
+<dd> This will print the current region in the format
+ (latitude-longitude location):
+
+<div class="code"><pre>
+projection: 3 (Latitude-Longitude)
+zone: 0
+ellipsoid: wgs84
+north: 90N
+south: 40N
+west: 20W
+east: 20E
+nsres: 928.73944902
+ewres: 352.74269109
+rows: 6000
+cols: 4800
+</pre></div>
+Note that the resolution is here reported in meters, not decimal degrees.
+
+</dl>
+
+<p>
+Usage example of <em>g.region</em> in a shell with external software:<br>
+<!-- why not 'v.in.ogr spatial=' ?? -->
+Extract spatial subset of external vector map 'soils.shp' to new external
+vector map 'soils_cut.shp' using the OGR 'ogr2ogr' tool:<br>
+
+<div class="code"><pre>
+eval `g.region -g`
+ogr2ogr -spat $w $s $e $n soils_cut.shp soils.shp
+</pre></div>
+
+This requires that the location/SHAPE file projection match.
+
+
+<p>
+Usage example of <em>g.proj</em> and <em>g.region</em> in a shell with external software:<br>
+Extract spatial subset of external raster map 'p016r035_7t20020524_z17_nn30.tif'
+to new external raster map'p016r035_7t20020524_nc_spm_wake_nn30.tif using the GDAL
+'gdalwarp' tool:<br>
+
+<div class="code"><pre>
+eval `g.region -g`
+gdalwarp -t_srs "`g.proj -wf`" -te $w $s $e $n \
+ p016r035_7t20020524_z17_nn30.tif \
+ p016r035_7t20020524_nc_spm_wake_nn30.tif
+</pre></div>
+
+Here the input raster map does not have to match the location
+projection since it is reprojected on the fly.
+
+
+
+<h2>SEE ALSO</h2>
+
+<em>
+<a HREF="d.zoom.html">d.zoom</a><br>
+<a HREF="g.access.html">g.access</a><br>
+<a HREF="g.mapsets.html">g.mapsets</a><br>
+<a HREF="g.proj.html">g.proj</a><BR>
+<a HREF="g.setproj.html">g.setproj</a><BR>
+environment variables: <a HREF="variables.html#internal">GRASS_REGION and WIND_OVERRIDE</a>
+</em>
+
+
+<h2>AUTHOR</h2>
+
+Michael Shapiro,
+U.S.Army Construction Engineering
+Research Laboratory
+
+<p>
+<i>Last changed: $Date$</i>
Deleted: grass/trunk/general/g.setproj/description.html
===================================================================
--- grass/trunk/general/g.setproj/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/general/g.setproj/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,95 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-<head>
-<title>g.setproj</title>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link rel="stylesheet" href="grassdocs.css" type="text/css">
-</head>
-<body bgcolor="white">
-
-<img src="grass_logo.png" alt="GRASS logo"><hr align=center size=6 noshade>
-
-<H2>NAME</H2>
-
-<EM><b>g.setproj</b></EM> - Allows the user to create the PROJ_INFO and the
-PROJ_UNITS files to record the projection information associated with a
-current location.
-<BR>
-
-<H2>SYNOPSIS</H2>
-
-<B>g.setproj</B>
-
-<H2>DESCRIPTION</H2>
-
-Allows a user to create a PROJ_INFO file in the PERMANENT mapset of the
-current location. PROJ_INFO file is used to record the projection information
-associated with the specified mapset.
-
-<H2>NOTES</H2>
-
-The user running <EM>g.setproj</EM> must own the PERMANENT
-mapset and it must be currently selected.
-It is highly recommended to run <EM>g.setproj</EM> after
-creating a new location so that conversion programs (such
-as <EM>v.proj</EM>) can be run.
-
-<P>The user will be prompted for the projection name.
-Most projections are supported. The
-<A HREF="http://proj.maptools.org/">PROJ.4</A> abbreviations for the names are
-used with two exceptions, viz. 'll', for latitude / longitude geographic
-co-ordinates, and 'stp', for the State Plane Co-ordinate system (used in the
-USA).</P>
-
-<P>After the projection name, the user will be asked for a geodetic datum. If
-no datum transformation support is needed, the question may be answered with no,
-and no datum will be specified in the PROJ_INFO file. If this is the case
-the user must specify the ellipsoid (model of the curvature of the earth) to
-be used, otherwise it is determined by the datum being used.</P>
-
-<P>If the datum or ellipsoid required are not
-listed within this program, the user/administrator may add the definition
-to the files datum.table, datumtransform.table and ellipse.table in the
-$GISBASE/etc/ directory.</P>
-
-<P>Depending on the projection selected, the user will then be prompted for
-the various other parameters required to define it.</P>
-
-<P>
-
-The projections of aea, lcc, merc, leae, leac, and
-tmerc will generate a request to the user for the prime meridian and standard
-parallel for the output map.
-
-
-<H2>SEE ALSO</H2>
-
-<EM><A HREF="g.proj.html">g.proj</A></EM>,
-<EM><A HREF="m.proj.html">m.proj</A></EM>,
-<EM><A HREF="r.proj.html">r.proj</A></EM>,
-<EM><A HREF="v.proj.html">v.proj</A></EM>,
-<EM><A HREF="http://proj.maptools.org">PROJ.4</A></EM>
-
-<P>
-<B>Further reading</B>
-<ul>
-<li> A guide to <a href="http://erg.usgs.gov/isb/pubs/MapProjections/projections.html">Map Projections</a> by USGS
-<li> <a href="http://www.asprs.org/resources/grids/">ASPRS Grids and Datum</a>
-<li> <a href="http://www.mapref.org">MapRef - The Collection of Map Projections and Reference Systems for Europe</a>
-<li> <a href="http://www.remotesensing.org/geotiff/proj_list/">Projections Transform List</a> (PROJ4)
-</ul>
-
-<H2>AUTHOR</H2>
-
-Irina Kosinovsky,
-U.S. Army Construction Engineering
-Research Laboratory<BR>
-Morten Hulden, morten at tor.ngb.se - rewrote module and added 121 projections <BR>
-Andreas Lange, andreas.lange at rhein-main.de - added prelimnary map datum support
-
-<p>
-<i>Last changed: $Date$</i>
-</p>
-
-</body>
-</html>
Copied: grass/trunk/general/g.setproj/g.setproj.html (from rev 32770, grass/trunk/general/g.setproj/description.html)
===================================================================
--- grass/trunk/general/g.setproj/g.setproj.html (rev 0)
+++ grass/trunk/general/g.setproj/g.setproj.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,95 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<head>
+<title>g.setproj</title>
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
+<link rel="stylesheet" href="grassdocs.css" type="text/css">
+</head>
+<body bgcolor="white">
+
+<img src="grass_logo.png" alt="GRASS logo"><hr align=center size=6 noshade>
+
+<H2>NAME</H2>
+
+<EM><b>g.setproj</b></EM> - Allows the user to create the PROJ_INFO and the
+PROJ_UNITS files to record the projection information associated with a
+current location.
+<BR>
+
+<H2>SYNOPSIS</H2>
+
+<B>g.setproj</B>
+
+<H2>DESCRIPTION</H2>
+
+Allows a user to create a PROJ_INFO file in the PERMANENT mapset of the
+current location. PROJ_INFO file is used to record the projection information
+associated with the specified mapset.
+
+<H2>NOTES</H2>
+
+The user running <EM>g.setproj</EM> must own the PERMANENT
+mapset and it must be currently selected.
+It is highly recommended to run <EM>g.setproj</EM> after
+creating a new location so that conversion programs (such
+as <EM>v.proj</EM>) can be run.
+
+<P>The user will be prompted for the projection name.
+Most projections are supported. The
+<A HREF="http://proj.maptools.org/">PROJ.4</A> abbreviations for the names are
+used with two exceptions, viz. 'll', for latitude / longitude geographic
+co-ordinates, and 'stp', for the State Plane Co-ordinate system (used in the
+USA).</P>
+
+<P>After the projection name, the user will be asked for a geodetic datum. If
+no datum transformation support is needed, the question may be answered with no,
+and no datum will be specified in the PROJ_INFO file. If this is the case
+the user must specify the ellipsoid (model of the curvature of the earth) to
+be used, otherwise it is determined by the datum being used.</P>
+
+<P>If the datum or ellipsoid required are not
+listed within this program, the user/administrator may add the definition
+to the files datum.table, datumtransform.table and ellipse.table in the
+$GISBASE/etc/ directory.</P>
+
+<P>Depending on the projection selected, the user will then be prompted for
+the various other parameters required to define it.</P>
+
+<P>
+
+The projections of aea, lcc, merc, leae, leac, and
+tmerc will generate a request to the user for the prime meridian and standard
+parallel for the output map.
+
+
+<H2>SEE ALSO</H2>
+
+<EM><A HREF="g.proj.html">g.proj</A></EM>,
+<EM><A HREF="m.proj.html">m.proj</A></EM>,
+<EM><A HREF="r.proj.html">r.proj</A></EM>,
+<EM><A HREF="v.proj.html">v.proj</A></EM>,
+<EM><A HREF="http://proj.maptools.org">PROJ.4</A></EM>
+
+<P>
+<B>Further reading</B>
+<ul>
+<li> A guide to <a href="http://erg.usgs.gov/isb/pubs/MapProjections/projections.html">Map Projections</a> by USGS
+<li> <a href="http://www.asprs.org/resources/grids/">ASPRS Grids and Datum</a>
+<li> <a href="http://www.mapref.org">MapRef - The Collection of Map Projections and Reference Systems for Europe</a>
+<li> <a href="http://www.remotesensing.org/geotiff/proj_list/">Projections Transform List</a> (PROJ4)
+</ul>
+
+<H2>AUTHOR</H2>
+
+Irina Kosinovsky,
+U.S. Army Construction Engineering
+Research Laboratory<BR>
+Morten Hulden, morten at tor.ngb.se - rewrote module and added 121 projections <BR>
+Andreas Lange, andreas.lange at rhein-main.de - added prelimnary map datum support
+
+<p>
+<i>Last changed: $Date$</i>
+</p>
+
+</body>
+</html>
Deleted: grass/trunk/general/g.tempfile/description.html
===================================================================
--- grass/trunk/general/g.tempfile/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/general/g.tempfile/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,53 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-<EM>g.tempfile</EM>
-is designed for shell scripts that need to use large temporary files.
-GRASS provides a mechanism for temporary files that does not depend on
-/tmp. GRASS temporary files are created in the data base with the assumption
-that there will be enough space under the data base for large files.
-GRASS periodically removes temporary files that have been left behind
-by programs that failed to remove them before terminating.
-
-<P>
-
-<EM>g.tempfile</EM>
-creates an unique file and prints the name. The user is required to provide
-a process-id which will be used as part of the name of the file.
-Most Unix shells provide a way to get the process id of the current shell.
-For /bin/sh and /bin/csh this is $$.
-It is recommended that $$ be specified as the process-id for
-<EM>g.tempfile</EM>.
-
-<H2>EXAMPLE</H2>
-
-For /bin/sh scripts the following syntax should be used:
-<div class="code"><PRE>
-temp1=`g.tempfile pid=$$`
-temp2=`g.tempfile pid=$$`
-</PRE></div>
-For /bin/csh scripts, the following can be used:
-<div class="code"><PRE>
-set temp1=`g.tempfile pid=$$`
-set temp2=`g.tempfile pid=$$`
-</PRE></div>
-
-<H2>NOTES</H2>
-
-Each call to <EM>g.tempfile</EM>
-creates a different (i.e. unique) name.
-
-Although GRASS does eventually get around to removing
-tempfiles that have been left behind, the programmer should
-make every effort to remove these files. They often get
-large and take up disk space. If you write /bin/sh scripts,
-learn to use the /bin/sh <EM>trap</EM> command. If you
-write /bin/csh scripts, learn to use the /bin/csh
-<EM>onintr</EM> command.
-
-<H2>AUTHOR</H2>
-
-Michael Shapiro,
-U.S. Army Construction Engineering
-Research Laboratory
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/general/g.tempfile/g.tempfile.html (from rev 32770, grass/trunk/general/g.tempfile/description.html)
===================================================================
--- grass/trunk/general/g.tempfile/g.tempfile.html (rev 0)
+++ grass/trunk/general/g.tempfile/g.tempfile.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,53 @@
+<H2>DESCRIPTION</H2>
+
+<EM>g.tempfile</EM>
+is designed for shell scripts that need to use large temporary files.
+GRASS provides a mechanism for temporary files that does not depend on
+/tmp. GRASS temporary files are created in the data base with the assumption
+that there will be enough space under the data base for large files.
+GRASS periodically removes temporary files that have been left behind
+by programs that failed to remove them before terminating.
+
+<P>
+
+<EM>g.tempfile</EM>
+creates an unique file and prints the name. The user is required to provide
+a process-id which will be used as part of the name of the file.
+Most Unix shells provide a way to get the process id of the current shell.
+For /bin/sh and /bin/csh this is $$.
+It is recommended that $$ be specified as the process-id for
+<EM>g.tempfile</EM>.
+
+<H2>EXAMPLE</H2>
+
+For /bin/sh scripts the following syntax should be used:
+<div class="code"><PRE>
+temp1=`g.tempfile pid=$$`
+temp2=`g.tempfile pid=$$`
+</PRE></div>
+For /bin/csh scripts, the following can be used:
+<div class="code"><PRE>
+set temp1=`g.tempfile pid=$$`
+set temp2=`g.tempfile pid=$$`
+</PRE></div>
+
+<H2>NOTES</H2>
+
+Each call to <EM>g.tempfile</EM>
+creates a different (i.e. unique) name.
+
+Although GRASS does eventually get around to removing
+tempfiles that have been left behind, the programmer should
+make every effort to remove these files. They often get
+large and take up disk space. If you write /bin/sh scripts,
+learn to use the /bin/sh <EM>trap</EM> command. If you
+write /bin/csh scripts, learn to use the /bin/csh
+<EM>onintr</EM> command.
+
+<H2>AUTHOR</H2>
+
+Michael Shapiro,
+U.S. Army Construction Engineering
+Research Laboratory
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/general/g.transform/description.html
===================================================================
--- grass/trunk/general/g.transform/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/general/g.transform/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,15 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-<EM>g.transform</EM> is an utility to compute transformation
-based upon GCPs and output error measurements.
-
-<H2>SEE ALSO</H2>
-
-<EM><A HREF="i.rectify.html">i.rectify</A></EM>
-
-<H2>AUTHORS</H2>
-
-Brian J. Buckley<br>
-Glynn Clements
-
-<p><i>Last changed: $Date$</i></p>
Copied: grass/trunk/general/g.transform/g.transform.html (from rev 32770, grass/trunk/general/g.transform/description.html)
===================================================================
--- grass/trunk/general/g.transform/g.transform.html (rev 0)
+++ grass/trunk/general/g.transform/g.transform.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,15 @@
+<H2>DESCRIPTION</H2>
+
+<EM>g.transform</EM> is an utility to compute transformation
+based upon GCPs and output error measurements.
+
+<H2>SEE ALSO</H2>
+
+<EM><A HREF="i.rectify.html">i.rectify</A></EM>
+
+<H2>AUTHORS</H2>
+
+Brian J. Buckley<br>
+Glynn Clements
+
+<p><i>Last changed: $Date$</i></p>
Deleted: grass/trunk/general/g.version/description.html
===================================================================
--- grass/trunk/general/g.version/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/general/g.version/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,18 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-<EM>g.version</EM>
-prints to standard output the GRASS version number, date,
-the GRASS copyright and GRASS build information.
-
-<H2>NOTES</H2>
-
-This program requires no command line arguments; the user simply types
-<B>g.version</B> on the command line to see the version number and date
-of the GRASS software currently being run by the user.
-
-<H2>AUTHOR</H2>
-
-Michael Shapiro,
-U.S. Army Construction Engineering
-Research Laboratory
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/general/g.version/g.version.html (from rev 32770, grass/trunk/general/g.version/description.html)
===================================================================
--- grass/trunk/general/g.version/g.version.html (rev 0)
+++ grass/trunk/general/g.version/g.version.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,18 @@
+<H2>DESCRIPTION</H2>
+
+<EM>g.version</EM>
+prints to standard output the GRASS version number, date,
+the GRASS copyright and GRASS build information.
+
+<H2>NOTES</H2>
+
+This program requires no command line arguments; the user simply types
+<B>g.version</B> on the command line to see the version number and date
+of the GRASS software currently being run by the user.
+
+<H2>AUTHOR</H2>
+
+Michael Shapiro,
+U.S. Army Construction Engineering
+Research Laboratory
+<p><i>Last changed: $Date$</i>
Modified: grass/trunk/gui/tcltk/gis.m/Makefile
===================================================================
--- grass/trunk/gui/tcltk/gis.m/Makefile 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/gui/tcltk/gis.m/Makefile 2008-08-15 06:16:42 UTC (rev 32772)
@@ -4,20 +4,15 @@
include $(MODULE_TOPDIR)/include/Make/Script.make
-default: script install_scripts myhtml
+default: script install_scripts
install_scripts:
if [ ! -d $(GISBASE)/etc/gm ] ; then $(MKDIR) $(GISBASE)/etc/gm; fi
- #$(INSTALL) description.html $(GISBASE)/docs/html/gis.m.html
for file in *.tcl ; do $(INSTALL) $$file $(GISBASE)/etc/gm/ ; done
for file in *.gif ; do $(INSTALL_DATA) $$file $(GISBASE)/etc/gm/ ; done
for file in docs/gm_*.html ; do $(INSTALL_DATA) $$file $(GISBASE)/docs/html/ ; done
for file in docs/gm_*.png ; do $(INSTALL_DATA) $$file $(GISBASE)/docs/html/ ; done
for file in docs/gm_*.jpg ; do $(INSTALL_DATA) $$file $(GISBASE)/docs/html/ ; done
-myhtml:
- $(MAKE) htmlscript PGM=gis.m
-
-
$(BIN)/$(PGM).bat: $(PGM).bat
$(INSTALL_DATA) $< $@
Deleted: grass/trunk/gui/tcltk/gis.m/description.html
===================================================================
--- grass/trunk/gui/tcltk/gis.m/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/gui/tcltk/gis.m/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,431 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-The <b>GRASS GIS Manager</b>
-provides an interactive graphical interface to GRASS commands. By
-default, it is started automatically with each GRASS session. The GIS
-Manager can be quit by selecting the <em>'File->Exit</em><em>'</em>
-menu item. The GIS Manager can be restarted from the GRASS command line
-shell by typing "<i>gis.m</i>".<br>
-<br>
-The GIS Manager includes a set of pull-down menus for all GRASS GIS
-functions (analysis, file I/O, GIS configuration and management), two
-rows of buttons that manage display layers, an upper window in
-which layers to display are organized, and a lower
-window which contains options panels for layers in the layer tree.
-<br><br>
-
-<center>
-<img src="gm_gismgr.jpg" alt="GIS Manager window" height="551" width="480">
-</center>
-<br>
-
-<br>
-The top left button opens a new map display window. Each map display
-has a unique set of layers to display and region setting (zoom). Other
-buttons add layers of different types for display in the selected map
-display window. There are additional buttons for saving or opening
-group display file, starting XGANIM (display animator) display
-interfaces (requires motif), and digitizing.
-<i>Mouse-over help</i> is available for all buttons.
-
-<P>
-Map layers are listed in the window below the
-buttons. Layers can include raster and vector maps, text, map
-enhancements (scale and north arrow, and grids), and commands
-(where any GRASS command be written). Layers are displayed in as
-arranged in the layer tree: the bottom layer
-is displayed first and the top is displayed last, as if
-layers are a series of stacked overlays. Any layer can be
-renamed by double clicking on its name and typing a new name.
-
-<P>
-The check box to the left of each layer makes it active or inactive for
-display.
-Only active layers are displayed/redisplayed when the display button is
-pressed. Layers can be organized into groups; entire groups can be
-activated or deactivated for display. Groups can be saved to a file and
-opened in subsequent sessions, restoring all layers and their display
-options.
-
-<P>
-When a layer is selected with the mouse, its options are shown in the
-panel below the layer tree window. Help for each layer type can be
-accessed by pressing the GRASS button in the option panel.<br>
-
-<P>
-Each map display has a unique layer tree and region setting (zoom).
-Buttons on each map display manage the map in the display (zoom and
-pan), provide tools for query and distance measurement, and exporting
-or printing the display. The geographic coordinates under the cursor
-are displayed in the indicator window (lower right window frame). It is
-important to note that zooming in any display will have NO effect on
-the 'computational region' setting (set with g.region). Only by selecting
-the "Set current region to match display" item in the zoom menu (in the
-map display tool bar) will the current display extents be copied to
-the computational region extents.
-<br><br>
-
-<center>
-<img src="gm_mapdisp.jpg" alt="Map Display window" height="422" width="480">
-</center>
-<br><br>
-
-A separate console window shows all commands issued and all command
-output (upper window). GRASS commands (and any other unix/linux
-commands) can be run from the console (lower window).<br>
-
-<br>
-<center>
-<img src="gm_gronsole.png" alt="Output and command console window" height="231" width="480">
-</center>
-<br>
-
-
-<h2>GIS MANAGER BUTTON FUNCTIONS</h2>
-
-<img src="gm_gismgrtools.png" alt="GIS Manager Toolbar">
-
-
-<H3><u>Top Row</u></H3>
-
-<DL>
-
-<DT><img src="icons/grass/gui-startmon.gif"> Open new map display</DT>
-<DD>Opens a new map display and resets layer tree.</DD>
-
-<DT><img src="icons/grass/element-cell.gif"> Add raster layer</DT>
-<DD>Adds a raster map to the layer tree. Raster display options include:
-displaying a selected subset of raster cells, defined by their cat
-values; draping (or "fusing") a second map over the base map;
-and displaying legends for the base map and draped map.
-<i>See <a href="d.rast.html">d.rast</a> and <a href="d.his.html">d.his</a>
- (for draping/fusing).</i>
-</DD>
-
-<DT><img src="icons/grass/channel-rgb.gif"> Add RGB or HIS raster layer</DT>
-<DD>Combines and displays three raster maps defined as red, green, and blue
-channels; or combines and displays two or three raster maps defined as
-hue, intensity, and (optionally) saturation channels.
-<i>See <a href="d.rgb.html">d.rgb</a> and <a href="d.his.html">d.his</a>.</i>
-</DD>
-
-<DT><img src="icons/grass/module-d.histogram.gif"> Add histogram layer</DT>
-<DD>Adds a layer to display histogram of a raster map or image.
-<i>See <a href="d.histogram.html">d.histogram</a>.</i>
-</DD>
-
-<DT><img src="icons/grass/module-d.rast.num.gif"> Add cell values layer</DT>
-<DD>Adds map of raster cells with cell values printed inside.
-Only works when <10,000 cells are displayed.
-<i>See <a href="d.rast.num.html">d.rast.num</a>.</i>
-</DD>
-
-<DT><img src="icons/grass/module-d.rast.arrow.gif"> Add raster arrows layer</DT>
-<DD>Adds map of raster cells with directional arrows drawn.
-Arrow direction and length are determined by separate aspect/directional map
-and (optional) slope/intensity map.
-<i>See <a href="d.rast.arrow.html">d.rast.arrow</a>.</i>
-</DD>
-
-<DT><img src="icons/grass/module-d.legend.gif"> Add raster legend</DT>
-<DD>Adds a legend for a single raster map to the layer tree.
-Multiple options for formatting the legend are available.
-<i>See <a href="d.legend.html">d.legend</a>.</i>
-</DD>
-
-<DT><img src="icons/grass/element-vector.gif"> Add vector layer</DT>
-<DD>Adds a vector map to the layer tree. A large number of options are
-available for displaying the vector map, including: outline and fill
-color, icon type and size for points, line widths for all vector types,
-automatic labeling using an attribute column, querying cats or
-attributes to limit vectors displayed, and restricting vector display
-depending on region size.
-<i>See <a href="d.vect.html">d.vect</a>.</i>
-</DD>
-
-<DT><img src="icons/grass/module-d.vect.thematic.gif"> Add thematic map layer
-(for all vector types)</DT>
-<DD>Adds layer for thematic display values from a numeric attribute column
-associated with a vector map. Options include: thematic display type
-(graduated colors or point sizes), methods for creating display
-intervals, SQL query of attribute column to limit vector objects to
-display, control of point icon types and sizes, control of thematic
-color schemes, creation of legend for thematic map, and saving the
-results of thematic mapping to a ps.map instructions file for later
-printing.
-<i>See <a href="d.vect.thematic.html">d.vect.thematic</a>.</i>
-</DD>
-
-<DT><img src="icons/grass/module-d.vect.chart.gif"> Add thematic charts layer
-(for vector points)</DT>
-<DD>Adds layer in which pie or bar charts can be automatically created at
-vector point locations. Charts display values from selected columns in the
-associated attribute table. Options include: chart type, layer and
-attributes to chart, chart colors, and chart size (fixed or based on
-attribute column).
-<i>See <a href="d.vect.chart.html">d.vect.chart</a>.</i>
-</DD>
-
-<DT><img src="icons/grass/module-d.labels.gif"> Add raster labels layer for vector
-objects (from existing labels file)</DT>
-<DD>Add raster text layer from a labels file for vector objects created with
-the <em><a href="v.label.html">v.label</a></em> module (accessed from button
-in options panel). A labels file can also be created with a text editor.
-<i>See <a href="d.labels.html">d.labels</a>.</i>
-</DD>
-
-<DT><img src="icons/grass/module-d.text.gif"> Add text layer</DT>
-<DD>Adds layer to display a line of text using default GRASS font
-(selected with <em><a href="d.font.html">d.font</a></em>).
-Options include: text placement (screen coordinates); and text size,
-bolding, and color.
-<i>See <a href="d.text.html">d.text</a>.</i>
-</DD>
-
-<DT><img src="icons/grass/gui-maptext.gif"> Add PostScript labels layer for vector
-objects (from existing labels file)</DT>
-<DD>Add PostScript text layer from a labels file for vector objects created
-with the <em><a href="v.label.html">v.label</a></em> module (accessed from
-button in options panel). A labels file can also be created with a text editor.
-<i>See <a href="d.labels.html">d.labels</a>.</i>
-</DD>
-
-<DT><img src="icons/grass/gui-maplabels.gif"> Add PostScript text layer</DT>
-<DD>Adds layer to display a line of PostScript text. Options include: text
-placement by coordinates (geographic or screen); text
-alignment, font and line spacing; and text size, bolding, and color.
-</DL>
-
-<BR><BR>
-
-
-<H3><u>Bottom Row</u></H3>
-
-<DL>
-
-<DT><img src="icons/grass/module-d.barscale.gif"> Add scalebar and north arrow layer</DT>
-<DD>Adds layer to display a combined scalebar and north arrow. Options
-include scalebar placement (using screen coordinates or a mouse),
-scalebar format, and scalebar colors.
-<i>See <a href="d.barscale.html">d.barscale</a>.</i>
-</DD>
-
-<DT><img src="icons/grass/module-d.grid.gif"> Overlay grids and lines</DT>
-<DD>Adds layer to display regular grid (for all locations), or geodesic and
-rhumblines (for latitude/longitude locations only). Grid options
-include: grid and border colors, grid origin, and grid line spacing.
-Geodesic and rhumbline options include: line color, and xy coordinates
-(geographic) of line endpoints.
-<i>See <a href="d.grid.html">d.grid</a>, <a href="d.geodesic.html">d.geodesic</a>,
- and <a href="d.rhumbline.html">d.rhumbline</a>.</i>
-</DD>
-
-<DT><img src="icons/grass/gui-cmd.gif"> Add command layer</DT>
-<DD>Adds a layer in which a GRASS GIS command or command list can be entered.
-For a command list use the pipe symbol as "|" as separator.
-For example:
-
-<div class="code"><pre>
- d.rast soils | d.rast -o roads | d.vect streams col=blue
-</pre></div>
-
-Note that when an option of the command contains spaces, you need to
-escape them with the backslash ('\') character, for example:<BR>
-<tt>d.text text=Population\ density</tt>
-</DD>
-
-<DT><img src="icons/grass/gui-group.gif"> Add group</DT>
-<DD>Adds an empty layer group. Layers can then be added to the group.</DD>
-
-<DT><img src="icons/grass/edit-copy.gif"> Duplicate selected layer or group</DT>
-<DD>Adds a new layer that duplicates the selected layer.</DD>
-
-<DT><img src="icons/grass/edit-cut.gif"> Cut selected layer or group</DT>
-<DD>Deletes the selected group or layer.</DD>
-
-<DT><img src="icons/grass/file-new.gif"> Erase all layers and create a new group</DT>
-<DD>Removes all layers in the layer tree and creates a new, empty group to
-which new layers can be added.<br></DD>
-
-<DT><img src="icons/grass/file-open.gif"> Open an existing group file</DT>
-<DD>Opens an previously saved group file, containing a set of display
-layers and their option settings.</DD>
-
-<DT><img src="icons/grass/file-save.gif"> Save layers to group file</DT>
-<DD>Saves current set of layers and their options to a group file.</DD>
-
-<DT><img src="icons/grass/module-xganim.gif"> Animate raster map series</DT>
-<DD>Starts the interactive Animation Tool interface to display a series
-of raster maps as an animation.
-<i>See the <a href="gm_animate.html">Animation Tool help page</a></i>.
-</DD>
-
-<DT><img src="icons/grass/module-v.digit.gif"> Digitize raster or vector maps</DT>
-<DD>Starts the raster digitizing or vector digitizing module, depending on
-whether a raster or vector map is selected. Raster digitizing always
-creates a new map. Vector digitizing will either edit an existing map
-(if an existing vector map is selected in the layer tree) or create a
-new vector map (if the name of the new vector to be created is entered
-in the 'vector name' field of the options panel for a vector map
-layer).
-<i>See <a href="r.digit.html">r.digit</a> and <a href="v.digit.html">v.digit</a></i>.
-</DD>
-
-</DL>
-<BR><BR>
-
-
-
-<h2>MAP DISPLAY BUTTON FUNCTIONS</h2>
-
-<img src="gm_mapdisptools.png" alt="Map display toolbar">
-
-<DL>
-
-<DT><img src="icons/grass/gui-display.gif"> Display active layers (current region)</DT>
-<DD>Displays all active layers at current resolution and region extents for
-that map display window.</DD>
-
-<DT><img src="icons/grass/gui-zoom_current.gif"> Re-render and display all active
-layers and zoom to current region</DT>
-<DD>Resets the region to the resolution and extents to the values set with
-<em>g.region</em>; forces re-display and re-rendering all active layers.
-<i>See <a href="g.region.html">g.region</a>.</i></DD>
-
-<DT><img src="icons/grass/module-nviz.gif"> NVIZ</DT>
-<DD>Starts NVIZ, the <i>n</i>-dimensional visualization module and interactive
-graphical interface. All active raster and vector layers in the layer
-tree will be displayed in NVIZ.
-<i>See the <a href="nviz.html">nviz</a> manual.</i></DD>
-
-<DT><img src="icons/grass/module-d.nviz.gif"> Create fly through path for NVIZ</DT>
-<DD>Starts a GRASS module for interactive creation of a fly-through path to
-be animated in NVIZ.
-<i>See <a href="d.nviz.html">d.nviz</a></i>.</DD>
-
-<DT><img src="icons/grass/gui-erase.gif"> Erase to white</DT>
-<DD>Erases the currently selected monitor to a white background; also
-removes all frames.
-<i>See <a href="d.erase.html">d.erase</a> and
-<a href="d.frame.html">d.frame -e</a>.</i></DD>
-
-<DT><img src="icons/grass/gui-pointer.gif"> Arrow cursor</DT>
-<DD>Select arrow cursor for map display.</DD>
-
-<DT><img src="icons/grass/gui-zoom_in.gif"> Zoom in</DT>
-<DD>Interactive zooming with the mouse in the active display monitor.
-Drawing a box with the mouse (left button) and zoom-in cursor causes
-the display to zoom in so that the area defined by the box fills the
-display. The map resolution is not changed. Clicking with the zoom-in
-cursor causes the display to zoom in by 30%, centered on the point
-where the mouse is clicked. Zooming resets the display region extents
-(both size and location of area displayed). It does NOT affect the
-computational region for other GIS processes.
-<i>See <a href="g.region.html">g.region</a>.</i></DD>
-
-<DT><img src="icons/grass/gui-zoom_out.gif"> Zoom out</DT>
-<DD>Interactive zooming with the mouse in the active display monitor.
-Drawing a box with the mouse (left button) and zoom-out cursor causes
-the display to zoom in so that the area displayed shrinks to fill the
-area defined by the box. The map resolution is not changed. Clicking
-with the zoom-out cursor causes the display to zoom out by 30%, centered
-on the point where the mouse is clicked. Zooming resets the display
-region extents (both size and location of area displayed). It does NOT
-affect the computational region for other GIS processes.
-<i>See <a href="g.region.html">g.region</a>.</i></DD>
-
-<DT><img src="icons/grass/gui-pan.gif"> Pan</DT>
-<DD>Interactive selection of a new center of view in the active display
-monitor. Drag the pan cursor while pressing the left mouse button to pan.
-Panning changes the location of the region displayed but not the size of
-the area displayed or the resolution. Panning does NOT affect the
-computational region for other GIS processes.
-<i>See <a href="g.region.html">g.region</a>.</i></DD>
-
-<DT><img src="icons/grass/gui-zoom_back.gif"> Revert zoom</DT>
-<DD>Returns to the previous zoom. Up to 5 levels of zoom back are maintained.
-<i>See <a href="g.region.html">g.region</a>.</i></DD>
-
-<DT><img src="icons/grass/gui-mapzoom.gif"> Zoom menu</DT>
-<DD>Automatic zoom settings menu. Zoom to match the extents of a selected
-map or to match the extents of a saved region; save the current extents
-to a named region file; zoom to match the computational region (set with
-<em>g.region</em>) or to match the default region; set computational region
-(the mapset's <tt>WIND</tt> file) to match the current display extents
-(does not change the resolution).
-<i>See <a href="g.region.html">g.region</a>.</i></DD>
-
-<DT><img src="icons/grass/gui-query.gif"> Query tool (select a map first)</DT>
-<DD>Query selected raster (only the base map of a draped map will be
-queried), RGB raster map (all three map channels will be queried), or
-vector map using the mouse. A map must be selected before query.
-Vector charts and thematic vector maps cannot be queried. The
-results of the query will be displayed in the console window.
-<i>See <a href="r.what.html">r.what</a> and <a href="v.what.html">v.what</a></i>.
-</DD>
-
-<DT><img src="icons/grass/gui-measure.gif"> Distance measurement tool</DT>
-<DD>Interactive measurement of lengths defined with the mouse. The length
-of each segment and the cumulative length of all segments measuered is
-displayed in the console window. Lengths are measured in the current
-measurement unit.
-<i>See also <a href="d.measure.html">d.measure</a>.</i></DD>
-
-<DT><img src="icons/grass/gui-profile.gif"> Profile tool</DT>
-<DD>Interactively create profile of a raster map. Profile transect
-is drawn with the mouse in map display. The profile may be of the
-displayed map or a different map.<i>
-See the <a href="gm_profile.html">Profile Tool help page</a>.</i></DD>
-
-<DT><img src="icons/grass/file-print.gif"> Print map</DT>
-<DD>Prints map on the UNIX <i>lpr</i> printer or PostScript device;
-saves visible map display (including PostScript text and labels) to PDF
-or EPS file. Requires <tt>ghostscript</tt> for all output except EPS.</DD>
-
-<DT><img src="icons/grass/file-save.gif"> Export map display</DT>
-<DD>Exports visible map display to different raster graphic formats.
-Exported map does not include PostScript text or PostScript labels.</DD>
-
-<DT><img src="icons/grass/drawmode-strict.gif"> Strict draw mode</DT>
-<DD>Selects strict draw mode. In strict mode the aspect ratio and resolution
-from the last zoom are used when drawing the maps. The map will show only
-the area and resolution selected. It will not usually fill the screen.
-Strict mode only shows what is asked for.</DD>
-
-<DT><img src="icons/grass/drawmode-explore.gif"> Explore draw mode</DT>
-<DD>Selects explore draw mode. In explore mode the region from the last zoom
-is expanded to fill the entire screen. The resolution is adjusted to match
-the screen resolution. Explore mode shows as much as possible.</DD>
-
-</DL>
-
-
-<h2>CONFIGURATION</h2>
-
-<h3>Changing fonts</h3>
-
-Fonts used in <em>gis.m</em> can be changed as follows:
-<ul>
- <li>Runtime: edit file '<tt>$GISBASE/etc/gtcltk/options.tcl</tt>'</li>
- <li>Source code: edit file '<tt>lib/gtcltk/options.tcl</tt>' and recompile gtcltk</li>
-</ul>
-
-
-<h2>SEE ALSO</h2>
-
-The <em>gis.m</em> <a href="gm_animate.html">ANIMATION TOOL</a><br>
-The <em>gis.m</em> <a href="gm_georect.html">GEORECTIFY TOOL</a><br>
-The <em>gis.m</em> <a href="gm_profile.html">PROFILE TOOL</a><br>
-<P>
-<em><a href="g.gui.html">g.gui</a></em>: Starts the default GUI<BR>
-<a href="d.m.html"><em>d.m</em> GUI</a>: The old display manager GUI<BR>
-<a href="wxGUI.html">wxPython GUI</a>:
- The next generation GUI, currently under development<BR>
-
-
-<h2>AUTHORS</h2>
-Michael Barton, Arizona State University, Tempe, Arizona, USA<br>
-Cedric Shock, USA
-
-<p>
-<i>Last changed: $Date$</i>
Copied: grass/trunk/gui/tcltk/gis.m/gis.m.html (from rev 32770, grass/trunk/gui/tcltk/gis.m/description.html)
===================================================================
--- grass/trunk/gui/tcltk/gis.m/gis.m.html (rev 0)
+++ grass/trunk/gui/tcltk/gis.m/gis.m.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,431 @@
+<h2>DESCRIPTION</h2>
+
+The <b>GRASS GIS Manager</b>
+provides an interactive graphical interface to GRASS commands. By
+default, it is started automatically with each GRASS session. The GIS
+Manager can be quit by selecting the <em>'File->Exit</em><em>'</em>
+menu item. The GIS Manager can be restarted from the GRASS command line
+shell by typing "<i>gis.m</i>".<br>
+<br>
+The GIS Manager includes a set of pull-down menus for all GRASS GIS
+functions (analysis, file I/O, GIS configuration and management), two
+rows of buttons that manage display layers, an upper window in
+which layers to display are organized, and a lower
+window which contains options panels for layers in the layer tree.
+<br><br>
+
+<center>
+<img src="gm_gismgr.jpg" alt="GIS Manager window" height="551" width="480">
+</center>
+<br>
+
+<br>
+The top left button opens a new map display window. Each map display
+has a unique set of layers to display and region setting (zoom). Other
+buttons add layers of different types for display in the selected map
+display window. There are additional buttons for saving or opening
+group display file, starting XGANIM (display animator) display
+interfaces (requires motif), and digitizing.
+<i>Mouse-over help</i> is available for all buttons.
+
+<P>
+Map layers are listed in the window below the
+buttons. Layers can include raster and vector maps, text, map
+enhancements (scale and north arrow, and grids), and commands
+(where any GRASS command be written). Layers are displayed in as
+arranged in the layer tree: the bottom layer
+is displayed first and the top is displayed last, as if
+layers are a series of stacked overlays. Any layer can be
+renamed by double clicking on its name and typing a new name.
+
+<P>
+The check box to the left of each layer makes it active or inactive for
+display.
+Only active layers are displayed/redisplayed when the display button is
+pressed. Layers can be organized into groups; entire groups can be
+activated or deactivated for display. Groups can be saved to a file and
+opened in subsequent sessions, restoring all layers and their display
+options.
+
+<P>
+When a layer is selected with the mouse, its options are shown in the
+panel below the layer tree window. Help for each layer type can be
+accessed by pressing the GRASS button in the option panel.<br>
+
+<P>
+Each map display has a unique layer tree and region setting (zoom).
+Buttons on each map display manage the map in the display (zoom and
+pan), provide tools for query and distance measurement, and exporting
+or printing the display. The geographic coordinates under the cursor
+are displayed in the indicator window (lower right window frame). It is
+important to note that zooming in any display will have NO effect on
+the 'computational region' setting (set with g.region). Only by selecting
+the "Set current region to match display" item in the zoom menu (in the
+map display tool bar) will the current display extents be copied to
+the computational region extents.
+<br><br>
+
+<center>
+<img src="gm_mapdisp.jpg" alt="Map Display window" height="422" width="480">
+</center>
+<br><br>
+
+A separate console window shows all commands issued and all command
+output (upper window). GRASS commands (and any other unix/linux
+commands) can be run from the console (lower window).<br>
+
+<br>
+<center>
+<img src="gm_gronsole.png" alt="Output and command console window" height="231" width="480">
+</center>
+<br>
+
+
+<h2>GIS MANAGER BUTTON FUNCTIONS</h2>
+
+<img src="gm_gismgrtools.png" alt="GIS Manager Toolbar">
+
+
+<H3><u>Top Row</u></H3>
+
+<DL>
+
+<DT><img src="icons/grass/gui-startmon.gif"> Open new map display</DT>
+<DD>Opens a new map display and resets layer tree.</DD>
+
+<DT><img src="icons/grass/element-cell.gif"> Add raster layer</DT>
+<DD>Adds a raster map to the layer tree. Raster display options include:
+displaying a selected subset of raster cells, defined by their cat
+values; draping (or "fusing") a second map over the base map;
+and displaying legends for the base map and draped map.
+<i>See <a href="d.rast.html">d.rast</a> and <a href="d.his.html">d.his</a>
+ (for draping/fusing).</i>
+</DD>
+
+<DT><img src="icons/grass/channel-rgb.gif"> Add RGB or HIS raster layer</DT>
+<DD>Combines and displays three raster maps defined as red, green, and blue
+channels; or combines and displays two or three raster maps defined as
+hue, intensity, and (optionally) saturation channels.
+<i>See <a href="d.rgb.html">d.rgb</a> and <a href="d.his.html">d.his</a>.</i>
+</DD>
+
+<DT><img src="icons/grass/module-d.histogram.gif"> Add histogram layer</DT>
+<DD>Adds a layer to display histogram of a raster map or image.
+<i>See <a href="d.histogram.html">d.histogram</a>.</i>
+</DD>
+
+<DT><img src="icons/grass/module-d.rast.num.gif"> Add cell values layer</DT>
+<DD>Adds map of raster cells with cell values printed inside.
+Only works when <10,000 cells are displayed.
+<i>See <a href="d.rast.num.html">d.rast.num</a>.</i>
+</DD>
+
+<DT><img src="icons/grass/module-d.rast.arrow.gif"> Add raster arrows layer</DT>
+<DD>Adds map of raster cells with directional arrows drawn.
+Arrow direction and length are determined by separate aspect/directional map
+and (optional) slope/intensity map.
+<i>See <a href="d.rast.arrow.html">d.rast.arrow</a>.</i>
+</DD>
+
+<DT><img src="icons/grass/module-d.legend.gif"> Add raster legend</DT>
+<DD>Adds a legend for a single raster map to the layer tree.
+Multiple options for formatting the legend are available.
+<i>See <a href="d.legend.html">d.legend</a>.</i>
+</DD>
+
+<DT><img src="icons/grass/element-vector.gif"> Add vector layer</DT>
+<DD>Adds a vector map to the layer tree. A large number of options are
+available for displaying the vector map, including: outline and fill
+color, icon type and size for points, line widths for all vector types,
+automatic labeling using an attribute column, querying cats or
+attributes to limit vectors displayed, and restricting vector display
+depending on region size.
+<i>See <a href="d.vect.html">d.vect</a>.</i>
+</DD>
+
+<DT><img src="icons/grass/module-d.vect.thematic.gif"> Add thematic map layer
+(for all vector types)</DT>
+<DD>Adds layer for thematic display values from a numeric attribute column
+associated with a vector map. Options include: thematic display type
+(graduated colors or point sizes), methods for creating display
+intervals, SQL query of attribute column to limit vector objects to
+display, control of point icon types and sizes, control of thematic
+color schemes, creation of legend for thematic map, and saving the
+results of thematic mapping to a ps.map instructions file for later
+printing.
+<i>See <a href="d.vect.thematic.html">d.vect.thematic</a>.</i>
+</DD>
+
+<DT><img src="icons/grass/module-d.vect.chart.gif"> Add thematic charts layer
+(for vector points)</DT>
+<DD>Adds layer in which pie or bar charts can be automatically created at
+vector point locations. Charts display values from selected columns in the
+associated attribute table. Options include: chart type, layer and
+attributes to chart, chart colors, and chart size (fixed or based on
+attribute column).
+<i>See <a href="d.vect.chart.html">d.vect.chart</a>.</i>
+</DD>
+
+<DT><img src="icons/grass/module-d.labels.gif"> Add raster labels layer for vector
+objects (from existing labels file)</DT>
+<DD>Add raster text layer from a labels file for vector objects created with
+the <em><a href="v.label.html">v.label</a></em> module (accessed from button
+in options panel). A labels file can also be created with a text editor.
+<i>See <a href="d.labels.html">d.labels</a>.</i>
+</DD>
+
+<DT><img src="icons/grass/module-d.text.gif"> Add text layer</DT>
+<DD>Adds layer to display a line of text using default GRASS font
+(selected with <em><a href="d.font.html">d.font</a></em>).
+Options include: text placement (screen coordinates); and text size,
+bolding, and color.
+<i>See <a href="d.text.html">d.text</a>.</i>
+</DD>
+
+<DT><img src="icons/grass/gui-maptext.gif"> Add PostScript labels layer for vector
+objects (from existing labels file)</DT>
+<DD>Add PostScript text layer from a labels file for vector objects created
+with the <em><a href="v.label.html">v.label</a></em> module (accessed from
+button in options panel). A labels file can also be created with a text editor.
+<i>See <a href="d.labels.html">d.labels</a>.</i>
+</DD>
+
+<DT><img src="icons/grass/gui-maplabels.gif"> Add PostScript text layer</DT>
+<DD>Adds layer to display a line of PostScript text. Options include: text
+placement by coordinates (geographic or screen); text
+alignment, font and line spacing; and text size, bolding, and color.
+</DL>
+
+<BR><BR>
+
+
+<H3><u>Bottom Row</u></H3>
+
+<DL>
+
+<DT><img src="icons/grass/module-d.barscale.gif"> Add scalebar and north arrow layer</DT>
+<DD>Adds layer to display a combined scalebar and north arrow. Options
+include scalebar placement (using screen coordinates or a mouse),
+scalebar format, and scalebar colors.
+<i>See <a href="d.barscale.html">d.barscale</a>.</i>
+</DD>
+
+<DT><img src="icons/grass/module-d.grid.gif"> Overlay grids and lines</DT>
+<DD>Adds layer to display regular grid (for all locations), or geodesic and
+rhumblines (for latitude/longitude locations only). Grid options
+include: grid and border colors, grid origin, and grid line spacing.
+Geodesic and rhumbline options include: line color, and xy coordinates
+(geographic) of line endpoints.
+<i>See <a href="d.grid.html">d.grid</a>, <a href="d.geodesic.html">d.geodesic</a>,
+ and <a href="d.rhumbline.html">d.rhumbline</a>.</i>
+</DD>
+
+<DT><img src="icons/grass/gui-cmd.gif"> Add command layer</DT>
+<DD>Adds a layer in which a GRASS GIS command or command list can be entered.
+For a command list use the pipe symbol as "|" as separator.
+For example:
+
+<div class="code"><pre>
+ d.rast soils | d.rast -o roads | d.vect streams col=blue
+</pre></div>
+
+Note that when an option of the command contains spaces, you need to
+escape them with the backslash ('\') character, for example:<BR>
+<tt>d.text text=Population\ density</tt>
+</DD>
+
+<DT><img src="icons/grass/gui-group.gif"> Add group</DT>
+<DD>Adds an empty layer group. Layers can then be added to the group.</DD>
+
+<DT><img src="icons/grass/edit-copy.gif"> Duplicate selected layer or group</DT>
+<DD>Adds a new layer that duplicates the selected layer.</DD>
+
+<DT><img src="icons/grass/edit-cut.gif"> Cut selected layer or group</DT>
+<DD>Deletes the selected group or layer.</DD>
+
+<DT><img src="icons/grass/file-new.gif"> Erase all layers and create a new group</DT>
+<DD>Removes all layers in the layer tree and creates a new, empty group to
+which new layers can be added.<br></DD>
+
+<DT><img src="icons/grass/file-open.gif"> Open an existing group file</DT>
+<DD>Opens an previously saved group file, containing a set of display
+layers and their option settings.</DD>
+
+<DT><img src="icons/grass/file-save.gif"> Save layers to group file</DT>
+<DD>Saves current set of layers and their options to a group file.</DD>
+
+<DT><img src="icons/grass/module-xganim.gif"> Animate raster map series</DT>
+<DD>Starts the interactive Animation Tool interface to display a series
+of raster maps as an animation.
+<i>See the <a href="gm_animate.html">Animation Tool help page</a></i>.
+</DD>
+
+<DT><img src="icons/grass/module-v.digit.gif"> Digitize raster or vector maps</DT>
+<DD>Starts the raster digitizing or vector digitizing module, depending on
+whether a raster or vector map is selected. Raster digitizing always
+creates a new map. Vector digitizing will either edit an existing map
+(if an existing vector map is selected in the layer tree) or create a
+new vector map (if the name of the new vector to be created is entered
+in the 'vector name' field of the options panel for a vector map
+layer).
+<i>See <a href="r.digit.html">r.digit</a> and <a href="v.digit.html">v.digit</a></i>.
+</DD>
+
+</DL>
+<BR><BR>
+
+
+
+<h2>MAP DISPLAY BUTTON FUNCTIONS</h2>
+
+<img src="gm_mapdisptools.png" alt="Map display toolbar">
+
+<DL>
+
+<DT><img src="icons/grass/gui-display.gif"> Display active layers (current region)</DT>
+<DD>Displays all active layers at current resolution and region extents for
+that map display window.</DD>
+
+<DT><img src="icons/grass/gui-zoom_current.gif"> Re-render and display all active
+layers and zoom to current region</DT>
+<DD>Resets the region to the resolution and extents to the values set with
+<em>g.region</em>; forces re-display and re-rendering all active layers.
+<i>See <a href="g.region.html">g.region</a>.</i></DD>
+
+<DT><img src="icons/grass/module-nviz.gif"> NVIZ</DT>
+<DD>Starts NVIZ, the <i>n</i>-dimensional visualization module and interactive
+graphical interface. All active raster and vector layers in the layer
+tree will be displayed in NVIZ.
+<i>See the <a href="nviz.html">nviz</a> manual.</i></DD>
+
+<DT><img src="icons/grass/module-d.nviz.gif"> Create fly through path for NVIZ</DT>
+<DD>Starts a GRASS module for interactive creation of a fly-through path to
+be animated in NVIZ.
+<i>See <a href="d.nviz.html">d.nviz</a></i>.</DD>
+
+<DT><img src="icons/grass/gui-erase.gif"> Erase to white</DT>
+<DD>Erases the currently selected monitor to a white background; also
+removes all frames.
+<i>See <a href="d.erase.html">d.erase</a> and
+<a href="d.frame.html">d.frame -e</a>.</i></DD>
+
+<DT><img src="icons/grass/gui-pointer.gif"> Arrow cursor</DT>
+<DD>Select arrow cursor for map display.</DD>
+
+<DT><img src="icons/grass/gui-zoom_in.gif"> Zoom in</DT>
+<DD>Interactive zooming with the mouse in the active display monitor.
+Drawing a box with the mouse (left button) and zoom-in cursor causes
+the display to zoom in so that the area defined by the box fills the
+display. The map resolution is not changed. Clicking with the zoom-in
+cursor causes the display to zoom in by 30%, centered on the point
+where the mouse is clicked. Zooming resets the display region extents
+(both size and location of area displayed). It does NOT affect the
+computational region for other GIS processes.
+<i>See <a href="g.region.html">g.region</a>.</i></DD>
+
+<DT><img src="icons/grass/gui-zoom_out.gif"> Zoom out</DT>
+<DD>Interactive zooming with the mouse in the active display monitor.
+Drawing a box with the mouse (left button) and zoom-out cursor causes
+the display to zoom in so that the area displayed shrinks to fill the
+area defined by the box. The map resolution is not changed. Clicking
+with the zoom-out cursor causes the display to zoom out by 30%, centered
+on the point where the mouse is clicked. Zooming resets the display
+region extents (both size and location of area displayed). It does NOT
+affect the computational region for other GIS processes.
+<i>See <a href="g.region.html">g.region</a>.</i></DD>
+
+<DT><img src="icons/grass/gui-pan.gif"> Pan</DT>
+<DD>Interactive selection of a new center of view in the active display
+monitor. Drag the pan cursor while pressing the left mouse button to pan.
+Panning changes the location of the region displayed but not the size of
+the area displayed or the resolution. Panning does NOT affect the
+computational region for other GIS processes.
+<i>See <a href="g.region.html">g.region</a>.</i></DD>
+
+<DT><img src="icons/grass/gui-zoom_back.gif"> Revert zoom</DT>
+<DD>Returns to the previous zoom. Up to 5 levels of zoom back are maintained.
+<i>See <a href="g.region.html">g.region</a>.</i></DD>
+
+<DT><img src="icons/grass/gui-mapzoom.gif"> Zoom menu</DT>
+<DD>Automatic zoom settings menu. Zoom to match the extents of a selected
+map or to match the extents of a saved region; save the current extents
+to a named region file; zoom to match the computational region (set with
+<em>g.region</em>) or to match the default region; set computational region
+(the mapset's <tt>WIND</tt> file) to match the current display extents
+(does not change the resolution).
+<i>See <a href="g.region.html">g.region</a>.</i></DD>
+
+<DT><img src="icons/grass/gui-query.gif"> Query tool (select a map first)</DT>
+<DD>Query selected raster (only the base map of a draped map will be
+queried), RGB raster map (all three map channels will be queried), or
+vector map using the mouse. A map must be selected before query.
+Vector charts and thematic vector maps cannot be queried. The
+results of the query will be displayed in the console window.
+<i>See <a href="r.what.html">r.what</a> and <a href="v.what.html">v.what</a></i>.
+</DD>
+
+<DT><img src="icons/grass/gui-measure.gif"> Distance measurement tool</DT>
+<DD>Interactive measurement of lengths defined with the mouse. The length
+of each segment and the cumulative length of all segments measuered is
+displayed in the console window. Lengths are measured in the current
+measurement unit.
+<i>See also <a href="d.measure.html">d.measure</a>.</i></DD>
+
+<DT><img src="icons/grass/gui-profile.gif"> Profile tool</DT>
+<DD>Interactively create profile of a raster map. Profile transect
+is drawn with the mouse in map display. The profile may be of the
+displayed map or a different map.<i>
+See the <a href="gm_profile.html">Profile Tool help page</a>.</i></DD>
+
+<DT><img src="icons/grass/file-print.gif"> Print map</DT>
+<DD>Prints map on the UNIX <i>lpr</i> printer or PostScript device;
+saves visible map display (including PostScript text and labels) to PDF
+or EPS file. Requires <tt>ghostscript</tt> for all output except EPS.</DD>
+
+<DT><img src="icons/grass/file-save.gif"> Export map display</DT>
+<DD>Exports visible map display to different raster graphic formats.
+Exported map does not include PostScript text or PostScript labels.</DD>
+
+<DT><img src="icons/grass/drawmode-strict.gif"> Strict draw mode</DT>
+<DD>Selects strict draw mode. In strict mode the aspect ratio and resolution
+from the last zoom are used when drawing the maps. The map will show only
+the area and resolution selected. It will not usually fill the screen.
+Strict mode only shows what is asked for.</DD>
+
+<DT><img src="icons/grass/drawmode-explore.gif"> Explore draw mode</DT>
+<DD>Selects explore draw mode. In explore mode the region from the last zoom
+is expanded to fill the entire screen. The resolution is adjusted to match
+the screen resolution. Explore mode shows as much as possible.</DD>
+
+</DL>
+
+
+<h2>CONFIGURATION</h2>
+
+<h3>Changing fonts</h3>
+
+Fonts used in <em>gis.m</em> can be changed as follows:
+<ul>
+ <li>Runtime: edit file '<tt>$GISBASE/etc/gtcltk/options.tcl</tt>'</li>
+ <li>Source code: edit file '<tt>lib/gtcltk/options.tcl</tt>' and recompile gtcltk</li>
+</ul>
+
+
+<h2>SEE ALSO</h2>
+
+The <em>gis.m</em> <a href="gm_animate.html">ANIMATION TOOL</a><br>
+The <em>gis.m</em> <a href="gm_georect.html">GEORECTIFY TOOL</a><br>
+The <em>gis.m</em> <a href="gm_profile.html">PROFILE TOOL</a><br>
+<P>
+<em><a href="g.gui.html">g.gui</a></em>: Starts the default GUI<BR>
+<a href="d.m.html"><em>d.m</em> GUI</a>: The old display manager GUI<BR>
+<a href="wxGUI.html">wxPython GUI</a>:
+ The next generation GUI, currently under development<BR>
+
+
+<h2>AUTHORS</h2>
+Michael Barton, Arizona State University, Tempe, Arizona, USA<br>
+Cedric Shock, USA
+
+<p>
+<i>Last changed: $Date$</i>
Deleted: grass/trunk/imagery/i.atcorr/description.html
===================================================================
--- grass/trunk/imagery/i.atcorr/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/imagery/i.atcorr/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,523 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<b>i.atcorr</b> performs atmospheric correction on the input raster using the
-6S algorithm (Second Simulation of Satellite Signal in the Solar Spectrum). A
-detailed algorithm description is available at the
-<a href=http://modis-sr.ltdri.org/index.html>Land Surface Reflectance Science
-Computing Facility website</a> and Mauro A. Homem Antunes <a
-href="http://www.ltid.inpe.br/dsr/mauro/6s/download_6s.html">website about his
-6s version</a>.
-
-<p>
-Current region settings are ignored. The region is adjusted to cover the input
-raster before the atmospheric correction is performed. This should not affect
-the user's current region settings.
-
-<p>
-Because using a continuous elevation <em>ialt</em> or visibility <em>ivis</em>
-map makes execution time much longer, it is advised to use categorized maps
-instead, in conjuction with flag <em>-o</em>. This flag tells
-<b>i.atcorr</b> to try and speedup calculations. However, this option under
-certain conditions can make execution time longer.
-
-<p>
-If flag <em>-r</em> is used, the input data are treated as reflectance.
-Otherwise, the input data are treated as radiance values and are converted to
-reflectance at the <b>i.atcorr</b> runtime. The output data are always
-reflectance.
-
-<p>
-An example 6s parameters <em>icnd</em> file for <b>i.atcorr</b>:
-
-<p>
-<div class="code"><pre>
-8 - geometrical conditions=Landsat ETM+
-2 19 13.00 -47.410 -20.234 - month day hh.ddd longitude lattitude ("hh.ddd" is a decimal hour GMT)
-1 - atmospheric mode=tropical
-1 - aerosols model=continental
-15 - visibility [km] (aerosol model concentration)
--.600 - target at 600m above sea level
--1000 - sensor on board a satellite
-64 - 4th band of ETM+ Landsat 7
-</pre></div>
-
-
-<h2><font color="red">REMAINING DOCUMENTATION ISSUES</font></h2>
-1. Using the target elevation and visibility parameters in the <em>icnd</em>
-file overrides <em>ialt</em> and <em>ivis</em> input rasters. It is not clear
-what to do to force <b>i.atcorr</b> to use the rasters instead though.
-<p>
-2. The "example 6s parameters file" explains that "-.600" in line 6 means
-"target at 600 m ASL". However, in the section E of "6S CODE PARAMETER CHOICES"
-it reads: "xps <=0. means the target is at the sea level". This is contrary.
-<p>
-3. In section E, I'm not sure if the "-100< xpp <0" shouldn't actually be
-"-1000< xpp <0". ?
-<p>
-4. It is not explained what is the "iaer" parameter that section D refers to.
-<p>
-5. Section D's "Aerosol model concentration" title could use a better wording I
-suppose. The current one seems to mean "the concentration of the model of the
-aerosol". Should it be "Aerosol concentration model"?
-<p>
-6. It should be explained under what circumstances the use of categorized maps
-in conjuction with flag <em>-o</em> can slow down the calculations instead of
-speeding them up.
-<p>
-7. "This should not affect the user's current region settings" sounds ambigious.
-
-<p>
-
-<H2>6S CODE PARAMETER CHOICES</H2>
-
-<h3>A. Geometrical conditions:</h3>
-
-<table BORDERWIDTH="AUTO" CELLPADDING="3">
-
-<tr>
-<td>Code</td>
-<td>Description</td>
-<td>Details</td>
-</tr>
-
-<tr>
-<td>1</td>
-<td><b>meteosat</b> observation</td>
-<td>enter month,day,decimal hour (universal time-hh.ddd)
-<br>
-n. of column,n. of line.(full scale 5000*2500) </td>
-</tr>
-
-<tr>
-<td>2</td>
-<td><b>goes east </b>observation</td>
-<td>enter month,day,decimal hour (universal time-hh.ddd)
-<br>
-n. of column,n. of line.(full scale 17000*12000)c</td>
-</tr>
-
-<tr>
-<td>3</td>
-<td><b>goes west</b> observation</td>
-<td>enter month,day,decimal hour (universal time-hh.ddd)
-<br>
-n. of column,n. of line.(full scale 17000*12000)</td>
-</tr>
-
-<tr>
-<td>4</td>
-<td><b>avhrr</b> (PM noaa)</td>
-<td>enter month,day,decimal hour (universal time-hh.ddd)
-<br>
-n. of column(1-2048),xlonan,hna
-<br>
-give long.(xlonan) and overpass hour (hna) at
-<br>
-the ascendant node at equator</td>
-</tr>
-
-<tr>
-<td>5</td>
-<td><b>avhrr</b> (AM noaa)</td>
-<td>enter month,day,decimal hour (universal time-hh.ddd)
-<br>
-n. of column(1-2048),xlonan,hna
-<br>
-give long.(xlonan) and overpass hour (hna) at
-<br>
-the ascendant node at equator</td>
-</tr>
-
-<tr>
-<td>6</td>
-
-<td><b>hrv</b> (spot)</td>
-
-<td>enter month,day,hh.ddd,long.,lat. *</td>
-</tr>
-
-<tr>
-<td>7</td>
-
-<td><b>tm</b> (landsat)</td>
-
-<td>enter month,day,hh.ddd,long.,lat. *</td>
-</tr>
-
-<tr>
-<td>8</td>
-
-<td><b>etm+</b> (landsat7)</td>
-
-<td>enter month,day,hh.ddd,long.,lat. *</td>
-</tr>
-</table>
-
-<blockquote>
-* NOTE: for hrv, tm and etm+ experiments, longitude and lattitude
-are the coordinates of the scene center. Lattitude must be >0 for northern
-hemisphere and <0 for southern. Longitude must be >0 for eastern hemisphere
-and <0 for western.
-</blockquote>
-
-<br><h3>B. Atmospheric model</h3>
-
-<table BORDERWIDTH="AUTO" CELLPADDING="3">
-
-<tr>
-<td>Code</td>
-<td>Meaning</td>
-</tr>
-
-<tr>
-<td>0</td>
-<td>no gaseous absorption</td>
-</tr>
-
-<tr>
-<td>1</td>
-<td>tropical</td>
-</tr>
-
-<tr>
-<td>2</td>
-<td>midlatitude summer</td>
-</tr>
-
-<tr>
-<td>3</td>
-<td>midlatitude winter</td>
-</tr>
-
-<tr>
-<td>4</td>
-<td>subarctic summer</td>
-</tr>
-
-<tr>
-<td>5</td>
-<td>subarctic winter</td>
-</tr>
-
-<tr>
-<td>6</td>
-<td>us standard 62</td>
-</tr>
-
-<tr>
-<td>7</td>
-<td>Define your own atmospheric model as a set of the following 5 parameters
-per each measurement:<br>
-<br>altitude [km]
-<br>pressure [mb]
-<br>temperature [k]
-<br>h2o density [g/m3]
-<br>o3 density [g/m3]<br>
-<br>For example: there is one radiosonde measurement for each altitude of
-0-25km at a step of 1km, one measurment for each altitude of 25-50km at a step
-of 5km, and two single measurements for altitudes 70km and 100km. This makes 34
-measurments. In that case, there are 34*5 values to input.</td>
-</tr>
-
-<tr>
-<td>8</td>
-<td>Define your own atmospheric model providing values of the water vapor and
-ozone content:
-<br>
-<br>uw [g/cm2]
-<br>uo3 [cm-atm]
-<br>
-<br> The profile is taken from us62.</td>
-</tr>
-
-</table>
-
-<br><h3>C. Aerosols model</h3>
-
-<table BORDERWIDTH="AUTO" CELLPADDING="3">
-
-<tr>
-<td>Code</td>
-<td>Meaning</td>
-<td>Details</td>
-</tr>
-
-<tr>
-<td>0</td>
-<td>no aerosols</td>
-<td></td>
-</tr>
-
-<tr>
-<td>1</td>
-<td>continental model</td>
-<td></td>
-</tr>
-
-<tr>
-<td>2</td>
-<td>maritime model</td>
-<td></td>
-</tr>
-
-<tr>
-<td>3</td>
-<td>urban model</td>
-<td></td>
-</tr>
-
-<tr>
-<td>4</td>
-<td>shettle model for background desert aerosol</td>
-<td></td>
-</tr>
-
-<tr>
-<td>5</td>
-<td>biomass burning</td>
-<td></td>
-</tr>
-
-<tr>
-<td>6</td>
-<td>stratospheric model</td>
-<td></td>
-</tr>
-
-<tr>
-<td>7</td>
-<td>define your own model</td>
-<td>Enter the volumic percentage of each component:
-<br>
-<br>c(1) = volumic % of dust-like
-<br>c(2) = volumic % of water-soluble
-<br>c(3) = volumic % of oceanic
-<br>c(4) = volumic % of soot
-<br>
-<br>All values between 0 and 1.</td>
-</tr>
-
-<tr>
-<td>8</td>
-<td>define your own model</td>
-<td>Size distribution function: Multimodal Log Normal (up to 4 modes).</td>
-</tr>
-
-<tr>
-<td>9</td>
-<td>define your own model</td>
-<td>Size distribution function: Modified gamma.</td>
-</tr>
-
-<tr>
-<td>10</td>
-<td>define your own model</td>
-<td>Size distribution function: Junge Power-Law.</td>
-</tr>
-
-<tr>
-<td>11</td>
-
-<td>define your own model</td>
-
-<td>Sun-photometer measurements, 50 values max, entered as:
-<br>
-<br>r and d V / d (logr)
-<br>
-<br>where r is the radius [micron], V is the volume, d V / d (logr) [cm3/cm2/micron].
-<br>
-<br>Followed by:
-<br>
-<br>nr and ni for each wavelength
-<br>
-<br>where nr and ni are respectively the real and imaginary part of the
-refractive index.</td>
-</tr>
-</table>
-
-<br><h3>D. Aerosol model concentration (visibility)</h3>
-
-<blockquote>If you have an estimate of the meteorological parameter visibility
-v, enter directly the value of v [km] (the aerosol optical depth will be
-computed from a standard aerosol profile).
-<p>If you have an estimate of aerosol optical depth, enter v=0 for the
-visibility and enter the aerosol optical depth at 550nm.
-<p>NOTE: if iaer=0, enter v=-1.</blockquote>
-
-<br><h3>E. Target altitude (xps), sensor platform (xpp)</h3>
-
-<blockquote>xps <=0 means the target is at the sea level.
-<br>xps >0 means you know the altitude of the target expressed
-in km, and you put that value as xps.
-<br>
-
-<br>xpp=-1000 means that the sensor is on board a satellite.
-<br>xpp=0 means that the sensor is at the ground level.
-<br>-100<xpp<0 means you know the altitude of the sensor
-expressed in kilometers; this altitude is <b>relative to the target</b>
-altitude.
-
-<p>For aircraft simulations only (xpp is neither 0 nor -1000):
-<blockquote>
-puw,po3 (water vapor content,ozone content between the aircraft and the surface)
-<br>taerp (the aerosol optical thickness at 550nm between the aircraft and the
-surface)
-<p>If these data are not available, enter negative values for all of them.
-puw,po3 will then be interpolated from the us62 standard profile according
-to the values at the ground level. taerp will be computed according to a 2km
-exponential profile for aerosol.</blockquote>
-</blockquote>
-
-
-<br><h3>F. Sensor band</h3>
-
-<p>There are two possibilities: either define your own spectral conditions
-(codes -2, -1, 0, or 1) or choose a code indicating the band of one of the
-pre-defined satellites.
-
-<p>Define your own spectral conditions:
-<p>
-<table BORDERWIDTH="AUTO" CELLPADDING="3">
-
-<tr>
-<td>Code</td>
-<td>Meaning</td>
-</tr>
-
-<tr>
-<td>-2</td>
-<td>Enter wlinf, wlsup.
-<br>The filter function will be equal to 1 over the whole band (as iwave=0)
-but step by step output will be printed.</td>
-</tr>
-
-<tr>
-<td>-1</td>
-<td>Enter wl (monochr. cond, gaseous absorption is included).</td>
-</tr>
-
-<tr>
-<td>0</td>
-<td>Enter wlinf, wlsup.
-<br>The filter function will be equal to 1over the whole band.</td>
-</tr>
-
-<tr>
-<td>1</td>
-<td>Enter wlinf, wlsup and user's filter function s(lambda) by step of 0.0025
-micrometer.</td>
-</tr>
-</table>
-
-<p>Pre-defined satellite bands:
-<p>
-<table BORDERWIDTH="AUTO" CELLPADDING="3">
-
-<tr><td>Code</td><td>Meaning</td></tr>
-
-<tr><td>2</td><td><b>meteosat</b> vis band (0.350-1.110)</td></tr>
-
-<tr><td>3</td><td><b>goes east</b> band vis (0.490-0.900)</td></tr>
-<tr><td>4</td><td>goes west band vis (0.490-0.900)</td></tr>
-
-<tr><td>5</td><td><b>avhrr (noaa6)</b> band 1 (0.550-0.750)</td></tr>
-<tr><td>6</td><td>avhrr (noaa6) band 2 (0.690-1.120)</td></tr>
-
-<tr><td>7</td><td><b>avhrr (noaa7)</b> band 1 (0.500-0.800)</td></tr>
-<tr><td>8</td><td>avhrr (noaa7) band 2 (0.640-1.170)</td></tr>
-
-<tr><td>9</td><td><b>avhrr (noaa8)</b> band 1 (0.540-1.010)</td></tr>
-<tr><td>10</td><td>avhrr (noaa8) band 2 (0.680-1.120)</td></tr>
-
-<tr><td>11</td><td><b>avhrr (noaa9)</b> band 1 (0.530-0.810)</td></tr>
-<tr><td>12</td><td>avhrr (noaa9) band 1 (0.680-1.170)</td></tr>
-
-<tr><td>13</td><td><b>avhrr (noaa10)</b> band 1 (0.530-0.780)</td></tr>
-<tr><td>14</td><td>avhrr (noaa10) band 2 (0.600-1.190)</td></tr>
-
-<tr><td>15</td><td><b>avhrr (noaa11)</b> band 1 (0.540-0.820)</td></tr>
-<tr><td>16</td><td>avhrr (noaa11) band 2 (0.600-1.120)</td></tr>
-
-<tr><td>17</td><td><b>hrv1 (spot1)</b> band 1 (0.470-0.650)</td></tr>
-<tr><td>18</td><td>hrv1 (spot1) band 2 (0.600-0.720)</td></tr>
-<tr><td>19</td><td>hrv1 (spot1) band 3 (0.730-0.930)</td></tr>
-<tr><td>20</td><td>hrv1 (spot1) band pan (0.470-0.790)</td></tr>
-
-<tr><td>21</td><td><b>hrv2 (spot1)</b> band 1 (0.470-0.650)</td></tr>
-<tr><td>22</td><td>hrv2 (spot1) band 2 (0.590-0.730)</td></tr>
-<tr><td>23</td><td>hrv2 (spot1) band 3 (0.740-0.940)</td></tr>
-<tr><td>24</td><td>hrv2 (spot1) band pan (0.470-0.790)</td></tr>
-
-<tr><td>25</td><td><b>tm (landsat5)</b> band 1 (0.430-0.560)</td></tr>
-<tr><td>26</td><td>tm (landsat5) band 2 (0.500-0.650)</td></tr>
-<tr><td>27</td><td>tm (landsat5) band 3 (0.580-0.740)</td></tr>
-<tr><td>28</td><td>tm (landsat5) band 4 (0.730-0.950)</td></tr>
-<tr><td>29</td><td>tm (landsat5) band 5 (1.5025-1.890)</td></tr>
-<tr><td>30</td><td>tm (landsat5) band 7 (1.950-2.410)</td></tr>
-
-<tr><td>31</td><td><b>mss (landsat5)</b> band 1 (0.475-0.640)</td></tr>
-<tr><td>32</td><td>mss (landsat5) band 2 (0.580-0.750)</td></tr>
-<tr><td>33</td><td>mss (landsat5) band 3 (0.655-0.855)</td></tr>
-<tr><td>34</td><td>mss (landsat5) band 4 (0.785-1.100)</td></tr>
-
-<tr><td>35</td><td><b>MAS (ER2)</b> band 1 (0.5025-0.5875)</td></tr>
-<tr><td>36</td><td>MAS (ER2) band 2 (0.6075-0.7000)</td></tr>
-<tr><td>37</td><td>MAS (ER2) band 3 (0.8300-0.9125)</td></tr>
-<tr><td>38</td><td>MAS (ER2) band 4 (0.9000-0.9975)</td></tr>
-<tr><td>39</td><td>MAS (ER2) band 5 (1.8200-1.9575)</td></tr>
-<tr><td>40</td><td>MAS (ER2) band 6 (2.0950-2.1925)</td></tr>
-<tr><td>41</td><td>MAS (ER2) band 7 (3.5800-3.8700)</td></tr>
-
-<tr><td>42</td><td><b>MODIS</b> band 1 (0.6100-0.6850)</td></tr>
-<tr><td>43</td><td>MODIS band 2 (0.8200-0.9025)</td></tr>
-<tr><td>44</td><td>MODIS band 3 (0.4500-0.4825)</td></tr>
-<tr><td>45</td><td>MODIS band 4 (0.5400-0.5700)</td></tr>
-<tr><td>46</td><td>MODIS band 5 (1.2150-1.2700)</td></tr>
-<tr><td>47</td><td>MODIS band 6 (1.6000-1.6650)</td></tr>
-<tr><td>48</td><td>MODIS band 7 (2.0575-2.1825)</td></tr>
-
-<tr><td>49</td><td><b>avhrr (noaa12)</b> band 1 (0.500-1.000)</td></tr>
-<tr><td>50</td><td>avhrr (noaa12) band 2 (0.650-1.120)</td></tr>
-
-<tr><td>51</td><td><b>avhrr (noaa14)</b> band 1 (0.500-1.110)</td></tr>
-<tr><td>52</td><td>avhrr (noaa14) band 2 (0.680-1.100)</td></tr>
-
-<tr><td>53</td><td><b>POLDER</b> band 1 (0.4125-0.4775)</td></tr>
-<tr><td>54</td><td>POLDER band 2 (non polar) (0.4100-0.5225)</td></tr>
-<tr><td>55</td><td>POLDER band 3 (non polar) (0.5325-0.5950)</td></tr>
-<tr><td>56</td><td>POLDER band 4 P1 (0.6300-0.7025)</td></tr>
-<tr><td>57</td><td>POLDER band 5 (non polar) (0.7450-0.7800)</td></tr>
-<tr><td>58</td><td>POLDER band 6 (non polar) (0.7000-0.8300)</td></tr>
-<tr><td>59</td><td>POLDER band 7 P1 (0.8100-0.9200)</td></tr>
-<tr><td>60</td><td>POLDER band 8 (non polar) (0.8650-0.9400)</td></tr>
-
-<tr><td>61</td><td><b>etm+ (landsat7)</b> band 1 (0.435-0.520)</td></tr>
-<tr><td>62</td><td>etm+ (landsat7) band 2 (0.506-0.621)</td></tr>
-<tr><td>63</td><td>etm+ (landsat7) band 3 (0.622-0.702)</td></tr>
-<tr><td>64</td><td>etm+ (landsat7) band 4 (0.751-0.911)</td></tr>
-<tr><td>65</td><td>etm+ (landsat7) band 5 (1.512-1.792)</td></tr>
-<tr><td>66</td><td>etm+ (landsat7) band 7 (2.020-2.380)</td></tr>
-<tr><td>67</td><td>etm+ (landsat7) band 8 (0.504-0.909)</td></tr>
-
-</table>
-
-<H2>AUTHORS</H2>
-
-<p><em>Original version of the program for GRASS 5:</em>
-<br>Christo Zietsman, 13422863(at)sun.ac.za
-
-<p><em>Code clean-up and port to GRASS 6.3, 15.12.2006:</em>
-<br>Yann Chemin, ychemin(at)gmail.com
-
-<h2>REFERENCES</h2>
-
-<p>Vermote, E.F., Tanre, D., Deuze, J.L., Herman, M., and Morcrette, J.J., 1997,
-Second simulation of the satellite signal in the solar spectrum, 6S: An
-overview., IEEE Trans. Geosc. and Remote Sens. 35(3):675-686.
-
-<p><a href="http://modis-sr.ltdri.org/6S_code/6S_code2_thinner_stuff/6S_ltdri_org_manual.html">6s manual</a> at the <a href="http://modis-sr.ltdri.org/6S_code/index.html">6s homepage</a> of the Land Surface Reflectance Science Computing Facility
-
-<p>Mauro A. Homem Antunes <a href="http://www.ltid.inpe.br/dsr/mauro/6s/download_6s.html">website about his 6s version</a>
-
-<p><i>Last changed: $Date$</i>
-
Copied: grass/trunk/imagery/i.atcorr/i.atcorr.html (from rev 32770, grass/trunk/imagery/i.atcorr/description.html)
===================================================================
--- grass/trunk/imagery/i.atcorr/i.atcorr.html (rev 0)
+++ grass/trunk/imagery/i.atcorr/i.atcorr.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,523 @@
+<h2>DESCRIPTION</h2>
+
+<b>i.atcorr</b> performs atmospheric correction on the input raster using the
+6S algorithm (Second Simulation of Satellite Signal in the Solar Spectrum). A
+detailed algorithm description is available at the
+<a href=http://modis-sr.ltdri.org/index.html>Land Surface Reflectance Science
+Computing Facility website</a> and Mauro A. Homem Antunes <a
+href="http://www.ltid.inpe.br/dsr/mauro/6s/download_6s.html">website about his
+6s version</a>.
+
+<p>
+Current region settings are ignored. The region is adjusted to cover the input
+raster before the atmospheric correction is performed. This should not affect
+the user's current region settings.
+
+<p>
+Because using a continuous elevation <em>ialt</em> or visibility <em>ivis</em>
+map makes execution time much longer, it is advised to use categorized maps
+instead, in conjuction with flag <em>-o</em>. This flag tells
+<b>i.atcorr</b> to try and speedup calculations. However, this option under
+certain conditions can make execution time longer.
+
+<p>
+If flag <em>-r</em> is used, the input data are treated as reflectance.
+Otherwise, the input data are treated as radiance values and are converted to
+reflectance at the <b>i.atcorr</b> runtime. The output data are always
+reflectance.
+
+<p>
+An example 6s parameters <em>icnd</em> file for <b>i.atcorr</b>:
+
+<p>
+<div class="code"><pre>
+8 - geometrical conditions=Landsat ETM+
+2 19 13.00 -47.410 -20.234 - month day hh.ddd longitude lattitude ("hh.ddd" is a decimal hour GMT)
+1 - atmospheric mode=tropical
+1 - aerosols model=continental
+15 - visibility [km] (aerosol model concentration)
+-.600 - target at 600m above sea level
+-1000 - sensor on board a satellite
+64 - 4th band of ETM+ Landsat 7
+</pre></div>
+
+
+<h2><font color="red">REMAINING DOCUMENTATION ISSUES</font></h2>
+1. Using the target elevation and visibility parameters in the <em>icnd</em>
+file overrides <em>ialt</em> and <em>ivis</em> input rasters. It is not clear
+what to do to force <b>i.atcorr</b> to use the rasters instead though.
+<p>
+2. The "example 6s parameters file" explains that "-.600" in line 6 means
+"target at 600 m ASL". However, in the section E of "6S CODE PARAMETER CHOICES"
+it reads: "xps <=0. means the target is at the sea level". This is contrary.
+<p>
+3. In section E, I'm not sure if the "-100< xpp <0" shouldn't actually be
+"-1000< xpp <0". ?
+<p>
+4. It is not explained what is the "iaer" parameter that section D refers to.
+<p>
+5. Section D's "Aerosol model concentration" title could use a better wording I
+suppose. The current one seems to mean "the concentration of the model of the
+aerosol". Should it be "Aerosol concentration model"?
+<p>
+6. It should be explained under what circumstances the use of categorized maps
+in conjuction with flag <em>-o</em> can slow down the calculations instead of
+speeding them up.
+<p>
+7. "This should not affect the user's current region settings" sounds ambigious.
+
+<p>
+
+<H2>6S CODE PARAMETER CHOICES</H2>
+
+<h3>A. Geometrical conditions:</h3>
+
+<table BORDERWIDTH="AUTO" CELLPADDING="3">
+
+<tr>
+<td>Code</td>
+<td>Description</td>
+<td>Details</td>
+</tr>
+
+<tr>
+<td>1</td>
+<td><b>meteosat</b> observation</td>
+<td>enter month,day,decimal hour (universal time-hh.ddd)
+<br>
+n. of column,n. of line.(full scale 5000*2500) </td>
+</tr>
+
+<tr>
+<td>2</td>
+<td><b>goes east </b>observation</td>
+<td>enter month,day,decimal hour (universal time-hh.ddd)
+<br>
+n. of column,n. of line.(full scale 17000*12000)c</td>
+</tr>
+
+<tr>
+<td>3</td>
+<td><b>goes west</b> observation</td>
+<td>enter month,day,decimal hour (universal time-hh.ddd)
+<br>
+n. of column,n. of line.(full scale 17000*12000)</td>
+</tr>
+
+<tr>
+<td>4</td>
+<td><b>avhrr</b> (PM noaa)</td>
+<td>enter month,day,decimal hour (universal time-hh.ddd)
+<br>
+n. of column(1-2048),xlonan,hna
+<br>
+give long.(xlonan) and overpass hour (hna) at
+<br>
+the ascendant node at equator</td>
+</tr>
+
+<tr>
+<td>5</td>
+<td><b>avhrr</b> (AM noaa)</td>
+<td>enter month,day,decimal hour (universal time-hh.ddd)
+<br>
+n. of column(1-2048),xlonan,hna
+<br>
+give long.(xlonan) and overpass hour (hna) at
+<br>
+the ascendant node at equator</td>
+</tr>
+
+<tr>
+<td>6</td>
+
+<td><b>hrv</b> (spot)</td>
+
+<td>enter month,day,hh.ddd,long.,lat. *</td>
+</tr>
+
+<tr>
+<td>7</td>
+
+<td><b>tm</b> (landsat)</td>
+
+<td>enter month,day,hh.ddd,long.,lat. *</td>
+</tr>
+
+<tr>
+<td>8</td>
+
+<td><b>etm+</b> (landsat7)</td>
+
+<td>enter month,day,hh.ddd,long.,lat. *</td>
+</tr>
+</table>
+
+<blockquote>
+* NOTE: for hrv, tm and etm+ experiments, longitude and lattitude
+are the coordinates of the scene center. Lattitude must be >0 for northern
+hemisphere and <0 for southern. Longitude must be >0 for eastern hemisphere
+and <0 for western.
+</blockquote>
+
+<br><h3>B. Atmospheric model</h3>
+
+<table BORDERWIDTH="AUTO" CELLPADDING="3">
+
+<tr>
+<td>Code</td>
+<td>Meaning</td>
+</tr>
+
+<tr>
+<td>0</td>
+<td>no gaseous absorption</td>
+</tr>
+
+<tr>
+<td>1</td>
+<td>tropical</td>
+</tr>
+
+<tr>
+<td>2</td>
+<td>midlatitude summer</td>
+</tr>
+
+<tr>
+<td>3</td>
+<td>midlatitude winter</td>
+</tr>
+
+<tr>
+<td>4</td>
+<td>subarctic summer</td>
+</tr>
+
+<tr>
+<td>5</td>
+<td>subarctic winter</td>
+</tr>
+
+<tr>
+<td>6</td>
+<td>us standard 62</td>
+</tr>
+
+<tr>
+<td>7</td>
+<td>Define your own atmospheric model as a set of the following 5 parameters
+per each measurement:<br>
+<br>altitude [km]
+<br>pressure [mb]
+<br>temperature [k]
+<br>h2o density [g/m3]
+<br>o3 density [g/m3]<br>
+<br>For example: there is one radiosonde measurement for each altitude of
+0-25km at a step of 1km, one measurment for each altitude of 25-50km at a step
+of 5km, and two single measurements for altitudes 70km and 100km. This makes 34
+measurments. In that case, there are 34*5 values to input.</td>
+</tr>
+
+<tr>
+<td>8</td>
+<td>Define your own atmospheric model providing values of the water vapor and
+ozone content:
+<br>
+<br>uw [g/cm2]
+<br>uo3 [cm-atm]
+<br>
+<br> The profile is taken from us62.</td>
+</tr>
+
+</table>
+
+<br><h3>C. Aerosols model</h3>
+
+<table BORDERWIDTH="AUTO" CELLPADDING="3">
+
+<tr>
+<td>Code</td>
+<td>Meaning</td>
+<td>Details</td>
+</tr>
+
+<tr>
+<td>0</td>
+<td>no aerosols</td>
+<td></td>
+</tr>
+
+<tr>
+<td>1</td>
+<td>continental model</td>
+<td></td>
+</tr>
+
+<tr>
+<td>2</td>
+<td>maritime model</td>
+<td></td>
+</tr>
+
+<tr>
+<td>3</td>
+<td>urban model</td>
+<td></td>
+</tr>
+
+<tr>
+<td>4</td>
+<td>shettle model for background desert aerosol</td>
+<td></td>
+</tr>
+
+<tr>
+<td>5</td>
+<td>biomass burning</td>
+<td></td>
+</tr>
+
+<tr>
+<td>6</td>
+<td>stratospheric model</td>
+<td></td>
+</tr>
+
+<tr>
+<td>7</td>
+<td>define your own model</td>
+<td>Enter the volumic percentage of each component:
+<br>
+<br>c(1) = volumic % of dust-like
+<br>c(2) = volumic % of water-soluble
+<br>c(3) = volumic % of oceanic
+<br>c(4) = volumic % of soot
+<br>
+<br>All values between 0 and 1.</td>
+</tr>
+
+<tr>
+<td>8</td>
+<td>define your own model</td>
+<td>Size distribution function: Multimodal Log Normal (up to 4 modes).</td>
+</tr>
+
+<tr>
+<td>9</td>
+<td>define your own model</td>
+<td>Size distribution function: Modified gamma.</td>
+</tr>
+
+<tr>
+<td>10</td>
+<td>define your own model</td>
+<td>Size distribution function: Junge Power-Law.</td>
+</tr>
+
+<tr>
+<td>11</td>
+
+<td>define your own model</td>
+
+<td>Sun-photometer measurements, 50 values max, entered as:
+<br>
+<br>r and d V / d (logr)
+<br>
+<br>where r is the radius [micron], V is the volume, d V / d (logr) [cm3/cm2/micron].
+<br>
+<br>Followed by:
+<br>
+<br>nr and ni for each wavelength
+<br>
+<br>where nr and ni are respectively the real and imaginary part of the
+refractive index.</td>
+</tr>
+</table>
+
+<br><h3>D. Aerosol model concentration (visibility)</h3>
+
+<blockquote>If you have an estimate of the meteorological parameter visibility
+v, enter directly the value of v [km] (the aerosol optical depth will be
+computed from a standard aerosol profile).
+<p>If you have an estimate of aerosol optical depth, enter v=0 for the
+visibility and enter the aerosol optical depth at 550nm.
+<p>NOTE: if iaer=0, enter v=-1.</blockquote>
+
+<br><h3>E. Target altitude (xps), sensor platform (xpp)</h3>
+
+<blockquote>xps <=0 means the target is at the sea level.
+<br>xps >0 means you know the altitude of the target expressed
+in km, and you put that value as xps.
+<br>
+
+<br>xpp=-1000 means that the sensor is on board a satellite.
+<br>xpp=0 means that the sensor is at the ground level.
+<br>-100<xpp<0 means you know the altitude of the sensor
+expressed in kilometers; this altitude is <b>relative to the target</b>
+altitude.
+
+<p>For aircraft simulations only (xpp is neither 0 nor -1000):
+<blockquote>
+puw,po3 (water vapor content,ozone content between the aircraft and the surface)
+<br>taerp (the aerosol optical thickness at 550nm between the aircraft and the
+surface)
+<p>If these data are not available, enter negative values for all of them.
+puw,po3 will then be interpolated from the us62 standard profile according
+to the values at the ground level. taerp will be computed according to a 2km
+exponential profile for aerosol.</blockquote>
+</blockquote>
+
+
+<br><h3>F. Sensor band</h3>
+
+<p>There are two possibilities: either define your own spectral conditions
+(codes -2, -1, 0, or 1) or choose a code indicating the band of one of the
+pre-defined satellites.
+
+<p>Define your own spectral conditions:
+<p>
+<table BORDERWIDTH="AUTO" CELLPADDING="3">
+
+<tr>
+<td>Code</td>
+<td>Meaning</td>
+</tr>
+
+<tr>
+<td>-2</td>
+<td>Enter wlinf, wlsup.
+<br>The filter function will be equal to 1 over the whole band (as iwave=0)
+but step by step output will be printed.</td>
+</tr>
+
+<tr>
+<td>-1</td>
+<td>Enter wl (monochr. cond, gaseous absorption is included).</td>
+</tr>
+
+<tr>
+<td>0</td>
+<td>Enter wlinf, wlsup.
+<br>The filter function will be equal to 1over the whole band.</td>
+</tr>
+
+<tr>
+<td>1</td>
+<td>Enter wlinf, wlsup and user's filter function s(lambda) by step of 0.0025
+micrometer.</td>
+</tr>
+</table>
+
+<p>Pre-defined satellite bands:
+<p>
+<table BORDERWIDTH="AUTO" CELLPADDING="3">
+
+<tr><td>Code</td><td>Meaning</td></tr>
+
+<tr><td>2</td><td><b>meteosat</b> vis band (0.350-1.110)</td></tr>
+
+<tr><td>3</td><td><b>goes east</b> band vis (0.490-0.900)</td></tr>
+<tr><td>4</td><td>goes west band vis (0.490-0.900)</td></tr>
+
+<tr><td>5</td><td><b>avhrr (noaa6)</b> band 1 (0.550-0.750)</td></tr>
+<tr><td>6</td><td>avhrr (noaa6) band 2 (0.690-1.120)</td></tr>
+
+<tr><td>7</td><td><b>avhrr (noaa7)</b> band 1 (0.500-0.800)</td></tr>
+<tr><td>8</td><td>avhrr (noaa7) band 2 (0.640-1.170)</td></tr>
+
+<tr><td>9</td><td><b>avhrr (noaa8)</b> band 1 (0.540-1.010)</td></tr>
+<tr><td>10</td><td>avhrr (noaa8) band 2 (0.680-1.120)</td></tr>
+
+<tr><td>11</td><td><b>avhrr (noaa9)</b> band 1 (0.530-0.810)</td></tr>
+<tr><td>12</td><td>avhrr (noaa9) band 1 (0.680-1.170)</td></tr>
+
+<tr><td>13</td><td><b>avhrr (noaa10)</b> band 1 (0.530-0.780)</td></tr>
+<tr><td>14</td><td>avhrr (noaa10) band 2 (0.600-1.190)</td></tr>
+
+<tr><td>15</td><td><b>avhrr (noaa11)</b> band 1 (0.540-0.820)</td></tr>
+<tr><td>16</td><td>avhrr (noaa11) band 2 (0.600-1.120)</td></tr>
+
+<tr><td>17</td><td><b>hrv1 (spot1)</b> band 1 (0.470-0.650)</td></tr>
+<tr><td>18</td><td>hrv1 (spot1) band 2 (0.600-0.720)</td></tr>
+<tr><td>19</td><td>hrv1 (spot1) band 3 (0.730-0.930)</td></tr>
+<tr><td>20</td><td>hrv1 (spot1) band pan (0.470-0.790)</td></tr>
+
+<tr><td>21</td><td><b>hrv2 (spot1)</b> band 1 (0.470-0.650)</td></tr>
+<tr><td>22</td><td>hrv2 (spot1) band 2 (0.590-0.730)</td></tr>
+<tr><td>23</td><td>hrv2 (spot1) band 3 (0.740-0.940)</td></tr>
+<tr><td>24</td><td>hrv2 (spot1) band pan (0.470-0.790)</td></tr>
+
+<tr><td>25</td><td><b>tm (landsat5)</b> band 1 (0.430-0.560)</td></tr>
+<tr><td>26</td><td>tm (landsat5) band 2 (0.500-0.650)</td></tr>
+<tr><td>27</td><td>tm (landsat5) band 3 (0.580-0.740)</td></tr>
+<tr><td>28</td><td>tm (landsat5) band 4 (0.730-0.950)</td></tr>
+<tr><td>29</td><td>tm (landsat5) band 5 (1.5025-1.890)</td></tr>
+<tr><td>30</td><td>tm (landsat5) band 7 (1.950-2.410)</td></tr>
+
+<tr><td>31</td><td><b>mss (landsat5)</b> band 1 (0.475-0.640)</td></tr>
+<tr><td>32</td><td>mss (landsat5) band 2 (0.580-0.750)</td></tr>
+<tr><td>33</td><td>mss (landsat5) band 3 (0.655-0.855)</td></tr>
+<tr><td>34</td><td>mss (landsat5) band 4 (0.785-1.100)</td></tr>
+
+<tr><td>35</td><td><b>MAS (ER2)</b> band 1 (0.5025-0.5875)</td></tr>
+<tr><td>36</td><td>MAS (ER2) band 2 (0.6075-0.7000)</td></tr>
+<tr><td>37</td><td>MAS (ER2) band 3 (0.8300-0.9125)</td></tr>
+<tr><td>38</td><td>MAS (ER2) band 4 (0.9000-0.9975)</td></tr>
+<tr><td>39</td><td>MAS (ER2) band 5 (1.8200-1.9575)</td></tr>
+<tr><td>40</td><td>MAS (ER2) band 6 (2.0950-2.1925)</td></tr>
+<tr><td>41</td><td>MAS (ER2) band 7 (3.5800-3.8700)</td></tr>
+
+<tr><td>42</td><td><b>MODIS</b> band 1 (0.6100-0.6850)</td></tr>
+<tr><td>43</td><td>MODIS band 2 (0.8200-0.9025)</td></tr>
+<tr><td>44</td><td>MODIS band 3 (0.4500-0.4825)</td></tr>
+<tr><td>45</td><td>MODIS band 4 (0.5400-0.5700)</td></tr>
+<tr><td>46</td><td>MODIS band 5 (1.2150-1.2700)</td></tr>
+<tr><td>47</td><td>MODIS band 6 (1.6000-1.6650)</td></tr>
+<tr><td>48</td><td>MODIS band 7 (2.0575-2.1825)</td></tr>
+
+<tr><td>49</td><td><b>avhrr (noaa12)</b> band 1 (0.500-1.000)</td></tr>
+<tr><td>50</td><td>avhrr (noaa12) band 2 (0.650-1.120)</td></tr>
+
+<tr><td>51</td><td><b>avhrr (noaa14)</b> band 1 (0.500-1.110)</td></tr>
+<tr><td>52</td><td>avhrr (noaa14) band 2 (0.680-1.100)</td></tr>
+
+<tr><td>53</td><td><b>POLDER</b> band 1 (0.4125-0.4775)</td></tr>
+<tr><td>54</td><td>POLDER band 2 (non polar) (0.4100-0.5225)</td></tr>
+<tr><td>55</td><td>POLDER band 3 (non polar) (0.5325-0.5950)</td></tr>
+<tr><td>56</td><td>POLDER band 4 P1 (0.6300-0.7025)</td></tr>
+<tr><td>57</td><td>POLDER band 5 (non polar) (0.7450-0.7800)</td></tr>
+<tr><td>58</td><td>POLDER band 6 (non polar) (0.7000-0.8300)</td></tr>
+<tr><td>59</td><td>POLDER band 7 P1 (0.8100-0.9200)</td></tr>
+<tr><td>60</td><td>POLDER band 8 (non polar) (0.8650-0.9400)</td></tr>
+
+<tr><td>61</td><td><b>etm+ (landsat7)</b> band 1 (0.435-0.520)</td></tr>
+<tr><td>62</td><td>etm+ (landsat7) band 2 (0.506-0.621)</td></tr>
+<tr><td>63</td><td>etm+ (landsat7) band 3 (0.622-0.702)</td></tr>
+<tr><td>64</td><td>etm+ (landsat7) band 4 (0.751-0.911)</td></tr>
+<tr><td>65</td><td>etm+ (landsat7) band 5 (1.512-1.792)</td></tr>
+<tr><td>66</td><td>etm+ (landsat7) band 7 (2.020-2.380)</td></tr>
+<tr><td>67</td><td>etm+ (landsat7) band 8 (0.504-0.909)</td></tr>
+
+</table>
+
+<H2>AUTHORS</H2>
+
+<p><em>Original version of the program for GRASS 5:</em>
+<br>Christo Zietsman, 13422863(at)sun.ac.za
+
+<p><em>Code clean-up and port to GRASS 6.3, 15.12.2006:</em>
+<br>Yann Chemin, ychemin(at)gmail.com
+
+<h2>REFERENCES</h2>
+
+<p>Vermote, E.F., Tanre, D., Deuze, J.L., Herman, M., and Morcrette, J.J., 1997,
+Second simulation of the satellite signal in the solar spectrum, 6S: An
+overview., IEEE Trans. Geosc. and Remote Sens. 35(3):675-686.
+
+<p><a href="http://modis-sr.ltdri.org/6S_code/6S_code2_thinner_stuff/6S_ltdri_org_manual.html">6s manual</a> at the <a href="http://modis-sr.ltdri.org/6S_code/index.html">6s homepage</a> of the Land Surface Reflectance Science Computing Facility
+
+<p>Mauro A. Homem Antunes <a href="http://www.ltid.inpe.br/dsr/mauro/6s/download_6s.html">website about his 6s version</a>
+
+<p><i>Last changed: $Date$</i>
+
Deleted: grass/trunk/imagery/i.cca/description.html
===================================================================
--- grass/trunk/imagery/i.cca/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/imagery/i.cca/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,82 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-
-<B>i.cca</B> is an image processing program that takes from two to eight
-(raster) band files and a signature file, and outputs the same number of
-raster band files transformed to provide maximum separability of the
-categories indicated by the signatures. This implementation of the
-canonical components transformation is based on the algorithm contained in
-the <a href=http://dbwww.essc.psu.edu/lasdoc/user/canal.html>LAS image
-processing system</a>. CCA is also known as "Canonical components
-transformation".
-
-<P>
-
-Typically the user will use the
-<EM><A HREF="i.class.html">i.class</A></EM>
-program to collect a set of signatures and then pass those
-signatures along with the raster band files to
-<EM>i.cca</EM>. The raster band file names are specified
-on the command line by giving the group and subgroup that
-were used to collect the signatures.
-
-<P>
-
-The output raster map names are built by appending a ".1",
-".2", etc. to the output raster map name specified on the
-command line.
-
-<H3>Parameters:</H3>
-
-<DL>
-
-<DT><B>group=</B><EM>name</EM>
-
-<DD>Name of the <A HREF="i.group.html">imagery</A> group
-to which the 2 to 8 raster band files used belong.
-
-<DT><B>subgroup=</B><EM>name</EM>
-
-<DD>Name of the <A HREF="i.group.html">imagery</A>
-subgroup to which the 2 to 8 raster band files used
-belong.
-
-<DT><B>signature=</B><EM>name</EM>
-
-<DD>Name of an ASCII file containing spectral signatures.
-
-<DT><B>output=</B><EM>name</EM>
-
-<DD>Output raster map prefix name. The output raster map
-layer names are built by appending a ".1", ".2", etc. onto
-the <EM>output</EM> name specified by the user.
-
-</DL>
-
-<H2>NOTES</H2>
-
-<EM>i.cca</EM> respects the current geographic region definition
-and the current mask setting while performing the transformation.
-
-<H2>SEE ALSO</H2>
-
-Schowengerdt, Robert A. <B>Techniques for Image Processing and
-Classification in Remote Sensing</B>, Academic Press, 1983.
-
-<P>
-
-<EM><A HREF="i.class.html">i.class</A></EM><br>
-<EM><A HREF="i.pca.html">i.pca</A></EM><br>
-<EM><A HREF="r.covar.html">r.covar</A></EM><br>
-<EM><A HREF="r.mapcalc.html">r.mapcalc</A></EM>
-
-<H2>AUTHORS</H2>
-
-David Satnik, GIS Laboratory,
-Central Washington University
-
-<BR>
-
-Ali R. Vali,
-University of Texas
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/imagery/i.cca/i.cca.html (from rev 32770, grass/trunk/imagery/i.cca/description.html)
===================================================================
--- grass/trunk/imagery/i.cca/i.cca.html (rev 0)
+++ grass/trunk/imagery/i.cca/i.cca.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,82 @@
+<H2>DESCRIPTION</H2>
+
+
+<B>i.cca</B> is an image processing program that takes from two to eight
+(raster) band files and a signature file, and outputs the same number of
+raster band files transformed to provide maximum separability of the
+categories indicated by the signatures. This implementation of the
+canonical components transformation is based on the algorithm contained in
+the <a href=http://dbwww.essc.psu.edu/lasdoc/user/canal.html>LAS image
+processing system</a>. CCA is also known as "Canonical components
+transformation".
+
+<P>
+
+Typically the user will use the
+<EM><A HREF="i.class.html">i.class</A></EM>
+program to collect a set of signatures and then pass those
+signatures along with the raster band files to
+<EM>i.cca</EM>. The raster band file names are specified
+on the command line by giving the group and subgroup that
+were used to collect the signatures.
+
+<P>
+
+The output raster map names are built by appending a ".1",
+".2", etc. to the output raster map name specified on the
+command line.
+
+<H3>Parameters:</H3>
+
+<DL>
+
+<DT><B>group=</B><EM>name</EM>
+
+<DD>Name of the <A HREF="i.group.html">imagery</A> group
+to which the 2 to 8 raster band files used belong.
+
+<DT><B>subgroup=</B><EM>name</EM>
+
+<DD>Name of the <A HREF="i.group.html">imagery</A>
+subgroup to which the 2 to 8 raster band files used
+belong.
+
+<DT><B>signature=</B><EM>name</EM>
+
+<DD>Name of an ASCII file containing spectral signatures.
+
+<DT><B>output=</B><EM>name</EM>
+
+<DD>Output raster map prefix name. The output raster map
+layer names are built by appending a ".1", ".2", etc. onto
+the <EM>output</EM> name specified by the user.
+
+</DL>
+
+<H2>NOTES</H2>
+
+<EM>i.cca</EM> respects the current geographic region definition
+and the current mask setting while performing the transformation.
+
+<H2>SEE ALSO</H2>
+
+Schowengerdt, Robert A. <B>Techniques for Image Processing and
+Classification in Remote Sensing</B>, Academic Press, 1983.
+
+<P>
+
+<EM><A HREF="i.class.html">i.class</A></EM><br>
+<EM><A HREF="i.pca.html">i.pca</A></EM><br>
+<EM><A HREF="r.covar.html">r.covar</A></EM><br>
+<EM><A HREF="r.mapcalc.html">r.mapcalc</A></EM>
+
+<H2>AUTHORS</H2>
+
+David Satnik, GIS Laboratory,
+Central Washington University
+
+<BR>
+
+Ali R. Vali,
+University of Texas
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/imagery/i.class/description.html
===================================================================
--- grass/trunk/imagery/i.class/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/imagery/i.class/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,432 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-<EM>i.class</EM>
-performs the first pass in the GRASS two-pass supervised image
-classification process;
-the GRASS program
-<EM><A HREF="i.maxlik.html">i.maxlik</A></EM> executes the second pass.
-Both programs must be run to generate a classified map in GRASS
-raster format.
-
-<P>
-
-<EM>i.class</EM> is an interactive program that allows the user to outline
-a region on the screen and calculate the spectral signature based on the
-cells that are within that region. During this process the user will be
-shown a histogram of the region for each image band. The user can also
-display the cells of the image bands which fall within a user-specified
-number of standard deviations from the means in the spectral signature.
-By doing this, the user can see how much of the image
-is likely to be put into the class associated with the current signature.
-
-
-<P>
-
-The spectral signatures that result are composed of region means and
-covariance matrices. These region means and covariance matrices are used in
-the second pass (<EM><A HREF="i.maxlik.html">i.maxlik</A></EM>) to classify
-the image.
-
-
-<P>
-
-Alternatively, the spectral signatures generated by <EM>i.class</EM> can be
-used for seed means for the clusters in the
-<EM><A HREF="i.cluster.html">i.cluster</A></EM> program.
-
-
-<H2>USER INPUTS</H2>
-
-At the command line the user is asked to enter the name of the raster map
-to be displayed during the process of outlining regions.
-Typically, the user will want to enter the name of a color
-composite previously created by
-<EM><A HREF="r.composite.html">r.composite</A></EM>.
-
-However, the user can enter the name of any existing raster
-map. This leaves the potential for using a raster map not
-directly derived from the image as a backdrop on which the
-user can outline the classes of interest.
-
-<P>
-
-The first screen in the program <EM>i.class</EM> asks the user for the
-<A HREF="i.group.html">imagery</A> <EM>group</EM> and <EM>subgroup</EM>
-to be analyzed:
-
-
-<div class="code"><PRE>
-LOCATION: location SUPERVISED CLASSIFIER MAPSET: demo
-
- Please select the group and subgroup to be analyzed
-
-GROUP: spot_______ (list will show available groups)
-SUBGROUP: 123________ (list will show available subgroups)
-
-
- AFTER COMPLETING ALL ANSWERS, HIT <ESC> TO CONTINUE
- (OR <Ctrl-C> TO CANCEL)
-</PRE></div>
-
-<P>
-
-The <EM>group</EM> should contain the
-imagery bands that the user wishes
-to classify. The <EM>subgroup</EM> is a subset of this group.
-The user must create a group and a subgroup by running the GRASS program
-
-<EM><A HREF="i.group.html">i.group</A></EM>
-before running <EM>i.class</EM>. The subgroup should contain
-only the image bands that the user wishes to classify.
-Note that this subgroup must contain more than one band.
-
-<P>
-
-After the first screen, the program asks the user for the name of the
-resulting signature file. The signature file is both the output file for
-<EM>i.class</EM> and the required input file for the GRASS
-<EM><A HREF="i.maxlik.html">i.maxlik</A></EM> module.
-It contains the region means and covariance matrices that are used to
-classify an image in <EM><A HREF="i.maxlik.html">i.maxlik</A></EM>.
-The signature file will be saved in the
-<tt>$MAPSET/group/$GROUP/subgroup/$SUBGROUP/sig/</tt> directory.
-
-<P>
-
-After entering the resulting signature file name, the user
-is asked to enter the name of a seed signature file. This
-is optional. A "seed" signature file is a previously
-created signature file. Such a seed signature file may be
-the result of an earlier run of <EM>i.class</EM>. The seed
-signature file is copied into the new resulting signature
-file before any new signatures are added by
-<EM>i.class</EM>. In this way, you can collect the work
-from several sessions with <EM>i.class</EM> into one
-signature file.
-
-<P>
-
-At this point the <EM>i.class</EM> graphics screen will be
-drawn on the graphics monitor and the user will be directed
-to use the mouse. From this point on the user will
-primarily work with the mouse, selecting options from the
-menus and outlining regions on the screen. The only time
-that the user will need to return to the text terminal is
-to enter names for the signatures created.
-
-<H2>THE DISPLAY FRAMES</H2>
-
-The display frame layout that <EM>i.class</EM> uses is
-represented below for reference.
-
-<div class="code"><PRE>
-+-----------------------+---------------------------+
-| | |
-| | Map Display Frame |
-| | |
-| | |
-| Histogram Display | |
-| Frame | |
-| | |
-| | |
-| | |
-| +---------------------------+
-| | |
-| | Zoom Display Frame |
-| | |
-| | |
-| | |
-| | |
-| | |
-| | |
-+-----------------------+---------------------------+
-| Menu Frame |
-+---------------------------------------------------+
-</PRE></div>
-
-
-<H2>THE MENUS</H2>
-
-All of the menus in the <EM>i.class</EM> program are
-displayed across the bottom of the graphics monitor in the
-Menu Frame. To select an option from one of these menus,
-simply place the cursor over your selection and press any
-button on the mouse. Each of the menus is discussed in the
-following paragraphs.
-
-
-<A NAME="commandmenu"></a>
-<H3>The Command Menu</H3>
-
-The Command Menu includes the following selections:
-
-<DL>
-
-<DT><EM>Zoom</EM>
-
-<DD>This command allows the user to outline a rectangular
-region in either the Map or Zoom Display Frames and the
-region is displayed, magnified, to fit in the Zoom Display
-Frame. A red rectangle is drawn in the Map Display Frame,
-indicating what area the Zoom Display Frame shows.
-
-<P>
-
-To outline the rectangular region simply use any mouse button to anchor
-the first corner of the border and then use any button to choose the
-other corner.
-
-
-
-<DT><EM>Define region</EM>
-
-<DD>This selection takes the user to the
-<A HREF="#regionmenu">Region Menu</A>.
-This menu includes the
-options that allow the user to outline a region of interest
-on the displayed raster map.
-
-
-<DT><EM>Redisplay map</EM>
-
-<DD>This selection takes the user to the Redisplay Menu.
-The
-<A HREF="#redisplaymenu">Redisplay Menu</A>
-allows the user to redraw map display
-frames.
-
-<DT><EM>Analyze region</EM>
-
-<DD>This selection starts the process of analyzing the
-currently defined region. A histogram of the defined
-region will be displayed for each band. On the histogram
-for each band, the mean, standard deviation, minimum cell
-value and maximum cell value are marked. The histograms
-are automatically scaled in an attempt to fit the data into
-the space available, but it is possible that all of the
-data will not fit. In this case, as much of the data as
-possible, centered around the mean, will be displayed.
-After the histograms are displayed, the user will be given
-the
-<A HREF="#signaturemenu">Signature Menu</A>.
-
-<DT><EM>Quit</EM>
-<DD>The user should make this selection
-to end the session with <EM>i.class</EM>.
-
-</DL>
-
-<A NAME="regionmenu"></a>
-<H3>The Region Menu</H3>
-
-The Region Menu contains the following selections:
-
-<DL>
-
-<DT><EM>Erase region</EM>
-<DD>This selection erases any currently defined
-region.
-
-<DT><EM>Draw region</EM>
-<DD>This selection allows the user to use the mouse to
-draw a region on either the Map or Zoom Display Frame. An
-explanation of which mouse buttons to use is displayed in the Menu
-Frame. The user does not need to try to complete the region boundary. The
-last line of the region will be added when the user selects the
-Complete region option on the Region Menu.
-
-
-<DT><EM>Restore last region</EM>
-<DD>This selection restores the last region
-that was drawn. After a region is completed, it will be saved to be
-restored later. Only one previous region is saved.
-
-<DT><EM>Complete region</EM>
-<DD>This selection completes the region that is
-currently being drawn. As noted above, it saves the complete
-region to be restored later, if needed. Once the user has made a
-complete region, it can be analyzed with the Analyze Region
-selection on the <A HREF="#commandmenu">Command Menu</A>.
-
-<DT><EM>Done</EM>
-<DD>Use this selection to return to the
-<A HREF="#commandmenu">Command Menu</A>.
-
-</DL>
-
-<A NAME="redisplaymenu"></a>
-<H3>The Redisplay Map Menu</H3>
-
-The Redisplay Map Menu has the following selections, which are useful
-to redraw the raster maps displayed in the Map and Zoom Display Frames.
-
-<DL>
-
-<DT><EM>Map geographic region</EM>
-<DD>This selection causes the raster map in the Map
-Display Frame to be redrawn.
-
-<DT><EM>Zoom region</EM>
-<DD>This selection causes the Zoom Display Frame to
-be redrawn.
-
-
-<DT><EM>Both</EM>
-<DD>This selection causes both the Map and Zoom Display
-Frames to be redrawn.
-
-<DT><EM>Cancel</EM>
-<DD>Use this selection if you do not want to redisplay
-either of the above regions. The user will be returned to the
-<A HREF="#commandmenu">Command Menu</A>.
-
-</DL>
-
-<A NAME="signaturemenu"></a>
-<H3>The Analyze Region Menu</H3>
-
-The Analyze Region Menu contains the Signature Menu, which
-allows the user to set the number of standard deviations
-and the display color, and then to display (as an overlay)
-the cells that match the signature within the number of
-standard deviations specified. Note that once the matching
-cells are displayed, the Map Display Frame must be
-redisplayed to see only the original raster map again. The
-following selections are available on the Signature Menu:
-
-
-<DL>
-
-<DT><EM>Set std dev's</EM>
-
-<DD>This selection allows the user to set the number of
-standard deviations from the mean for the maximum and
-minimum range. The maximum and minimum range is used when
-finding the cells that "match" the signature. The user is
-presented with a menu of typical choices and an "Other"
-option. If the "Other" option is selected, enter the
-number of standard deviations from the keyboard on the text
-terminal. Otherwise, the selected option will be used.
-When the number of standard deviations is set, the
-histograms for each band will be redrawn with the maximum
-and minimum range marked.
-
-
-<P>
-
-Note that the number in parentheses on this
-selection is the current number of standard deviations.
-
-
-<DT><EM>Set color</EM>
-
-<DD>This selection allows the user to set the color for the
-display of cells that "match" the current signature. The
-user is presented with a menu of color choices. The color
-selected will be used when the Display Matches Menu
-selection is made.
-
-<P>
-
-Note that the color in parentheses on this selection is the current
-color for display.
-
-<DT><EM>Display matches</EM>
-
-<DD>This selection displays the cells that "match" the
-current signature in the current color. A cell "matches"
-the current signature if the cell value in each band is
-between the minimum range and maximum range for that band
-defined by the number of standard deviations currently
-set.
-
-<DT><EM>Done</EM>
-
-<DD>When this selection is chosen, the user will be asked
-whether or not he/she would like to save the current
-signature. If the user answers with the "Yes" selection,
-he/she will be asked to enter a description for the
-resultant signature file on the text terminal keyboard.
-The saved signature file description will be used by <EM>
-<A HREF="i.maxlik.html">i.maxlik</A></EM> to name the
-category that is created from the current signature. After
-either a "No" answer or the signature description is
-entered, the user is returned to the Command Menu.
-
-</DL>
-
-
-<H2>NOTES</H2>
-
-<EM>i.class</EM> uses the current MASK to generate the
-overlay for cells that match a signature. As a result, if
-a MASK already exists it will be removed during the
-execution of this program.
-
-<P>
-The cell values in the image bands cannot fall outside of
-the range of 0 to 255. <EM>i.class</EM> will report an
-error if they do.
-
-<P>
-<EM>i.class</EM>, like some of the other
-<A HREF="imagery.html">imagery</A> programs, does not use the
-
-standard GRASS display frames. After running
-<EM>i.class</EM>, you will need to create a display frame
-(e.g., using
-
-<EM><A HREF="d.frame.html">d.frame</A></EM> or
-
-<EM><A HREF="d.erase.html">d.erase</A></EM>)
-before you can use most of the GRASS display (d.) commands.
-
-<P>
-<EM><A HREF="i.group.html">i.group</A></EM>
-must be run before <EM>i.class</EM> to create an
-<A HREF="i.group.html">imagery</A> group and a subgroup
-containing the image bands to be classified.
-
-<P>
-The user can perform a supervised image classification by
-running <EM>i.class</EM> followed by
-
-<EM><A HREF="i.maxlik.html">i.maxlik</A></EM>.
-
-The user can perform an unsupervised classification
-by running
-
-<EM><A HREF="i.cluster.html">i.cluster</A></EM> followed by
-
-<EM><A HREF="i.maxlik.html">i.maxlik</A></EM>.
-
-<P>
-<EM>i.class</EM> is interactive and requires the user to be running
-a graphics display monitor (see <EM><A HREF="d.mon.html">d.mon</A></EM>)
-to run this program.
-
-
-<H2>SEE ALSO</H2>
-
-The GRASS 4 <em>
-<A HREF="http://grass.itc.it/gdp/imagery/grass4_image_processing.pdf">Image
-Processing manual</A></EM>
-
-<P>
-<EM><A HREF="d.frame.html">d.frame</A>,
-<A HREF="d.mon.html">d.mon</A>,
-<A HREF="g.region.html">g.region</A>,
-<A HREF="i.cca.html">i.cca</A>,
-<A HREF="i.cluster.html">i.cluster</A>,
-<A HREF="r.composite.html">r.composite</A>,
-<A HREF="i.group.html">i.group</A>,
-<A HREF="i.maxlik.html">i.maxlik</A>,
-<A HREF="r.mapcalc.html">r.mapcalc</A></EM>
-
-<H2>AUTHOR</H2>
-
-David Satnik,
-Central Washington University
-
-<p>
-<i>Last changed: $Date$</i>
Copied: grass/trunk/imagery/i.class/i.class.html (from rev 32770, grass/trunk/imagery/i.class/description.html)
===================================================================
--- grass/trunk/imagery/i.class/i.class.html (rev 0)
+++ grass/trunk/imagery/i.class/i.class.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,432 @@
+<H2>DESCRIPTION</H2>
+
+<EM>i.class</EM>
+performs the first pass in the GRASS two-pass supervised image
+classification process;
+the GRASS program
+<EM><A HREF="i.maxlik.html">i.maxlik</A></EM> executes the second pass.
+Both programs must be run to generate a classified map in GRASS
+raster format.
+
+<P>
+
+<EM>i.class</EM> is an interactive program that allows the user to outline
+a region on the screen and calculate the spectral signature based on the
+cells that are within that region. During this process the user will be
+shown a histogram of the region for each image band. The user can also
+display the cells of the image bands which fall within a user-specified
+number of standard deviations from the means in the spectral signature.
+By doing this, the user can see how much of the image
+is likely to be put into the class associated with the current signature.
+
+
+<P>
+
+The spectral signatures that result are composed of region means and
+covariance matrices. These region means and covariance matrices are used in
+the second pass (<EM><A HREF="i.maxlik.html">i.maxlik</A></EM>) to classify
+the image.
+
+
+<P>
+
+Alternatively, the spectral signatures generated by <EM>i.class</EM> can be
+used for seed means for the clusters in the
+<EM><A HREF="i.cluster.html">i.cluster</A></EM> program.
+
+
+<H2>USER INPUTS</H2>
+
+At the command line the user is asked to enter the name of the raster map
+to be displayed during the process of outlining regions.
+Typically, the user will want to enter the name of a color
+composite previously created by
+<EM><A HREF="r.composite.html">r.composite</A></EM>.
+
+However, the user can enter the name of any existing raster
+map. This leaves the potential for using a raster map not
+directly derived from the image as a backdrop on which the
+user can outline the classes of interest.
+
+<P>
+
+The first screen in the program <EM>i.class</EM> asks the user for the
+<A HREF="i.group.html">imagery</A> <EM>group</EM> and <EM>subgroup</EM>
+to be analyzed:
+
+
+<div class="code"><PRE>
+LOCATION: location SUPERVISED CLASSIFIER MAPSET: demo
+
+ Please select the group and subgroup to be analyzed
+
+GROUP: spot_______ (list will show available groups)
+SUBGROUP: 123________ (list will show available subgroups)
+
+
+ AFTER COMPLETING ALL ANSWERS, HIT <ESC> TO CONTINUE
+ (OR <Ctrl-C> TO CANCEL)
+</PRE></div>
+
+<P>
+
+The <EM>group</EM> should contain the
+imagery bands that the user wishes
+to classify. The <EM>subgroup</EM> is a subset of this group.
+The user must create a group and a subgroup by running the GRASS program
+
+<EM><A HREF="i.group.html">i.group</A></EM>
+before running <EM>i.class</EM>. The subgroup should contain
+only the image bands that the user wishes to classify.
+Note that this subgroup must contain more than one band.
+
+<P>
+
+After the first screen, the program asks the user for the name of the
+resulting signature file. The signature file is both the output file for
+<EM>i.class</EM> and the required input file for the GRASS
+<EM><A HREF="i.maxlik.html">i.maxlik</A></EM> module.
+It contains the region means and covariance matrices that are used to
+classify an image in <EM><A HREF="i.maxlik.html">i.maxlik</A></EM>.
+The signature file will be saved in the
+<tt>$MAPSET/group/$GROUP/subgroup/$SUBGROUP/sig/</tt> directory.
+
+<P>
+
+After entering the resulting signature file name, the user
+is asked to enter the name of a seed signature file. This
+is optional. A "seed" signature file is a previously
+created signature file. Such a seed signature file may be
+the result of an earlier run of <EM>i.class</EM>. The seed
+signature file is copied into the new resulting signature
+file before any new signatures are added by
+<EM>i.class</EM>. In this way, you can collect the work
+from several sessions with <EM>i.class</EM> into one
+signature file.
+
+<P>
+
+At this point the <EM>i.class</EM> graphics screen will be
+drawn on the graphics monitor and the user will be directed
+to use the mouse. From this point on the user will
+primarily work with the mouse, selecting options from the
+menus and outlining regions on the screen. The only time
+that the user will need to return to the text terminal is
+to enter names for the signatures created.
+
+<H2>THE DISPLAY FRAMES</H2>
+
+The display frame layout that <EM>i.class</EM> uses is
+represented below for reference.
+
+<div class="code"><PRE>
++-----------------------+---------------------------+
+| | |
+| | Map Display Frame |
+| | |
+| | |
+| Histogram Display | |
+| Frame | |
+| | |
+| | |
+| | |
+| +---------------------------+
+| | |
+| | Zoom Display Frame |
+| | |
+| | |
+| | |
+| | |
+| | |
+| | |
++-----------------------+---------------------------+
+| Menu Frame |
++---------------------------------------------------+
+</PRE></div>
+
+
+<H2>THE MENUS</H2>
+
+All of the menus in the <EM>i.class</EM> program are
+displayed across the bottom of the graphics monitor in the
+Menu Frame. To select an option from one of these menus,
+simply place the cursor over your selection and press any
+button on the mouse. Each of the menus is discussed in the
+following paragraphs.
+
+
+<A NAME="commandmenu"></a>
+<H3>The Command Menu</H3>
+
+The Command Menu includes the following selections:
+
+<DL>
+
+<DT><EM>Zoom</EM>
+
+<DD>This command allows the user to outline a rectangular
+region in either the Map or Zoom Display Frames and the
+region is displayed, magnified, to fit in the Zoom Display
+Frame. A red rectangle is drawn in the Map Display Frame,
+indicating what area the Zoom Display Frame shows.
+
+<P>
+
+To outline the rectangular region simply use any mouse button to anchor
+the first corner of the border and then use any button to choose the
+other corner.
+
+
+
+<DT><EM>Define region</EM>
+
+<DD>This selection takes the user to the
+<A HREF="#regionmenu">Region Menu</A>.
+This menu includes the
+options that allow the user to outline a region of interest
+on the displayed raster map.
+
+
+<DT><EM>Redisplay map</EM>
+
+<DD>This selection takes the user to the Redisplay Menu.
+The
+<A HREF="#redisplaymenu">Redisplay Menu</A>
+allows the user to redraw map display
+frames.
+
+<DT><EM>Analyze region</EM>
+
+<DD>This selection starts the process of analyzing the
+currently defined region. A histogram of the defined
+region will be displayed for each band. On the histogram
+for each band, the mean, standard deviation, minimum cell
+value and maximum cell value are marked. The histograms
+are automatically scaled in an attempt to fit the data into
+the space available, but it is possible that all of the
+data will not fit. In this case, as much of the data as
+possible, centered around the mean, will be displayed.
+After the histograms are displayed, the user will be given
+the
+<A HREF="#signaturemenu">Signature Menu</A>.
+
+<DT><EM>Quit</EM>
+<DD>The user should make this selection
+to end the session with <EM>i.class</EM>.
+
+</DL>
+
+<A NAME="regionmenu"></a>
+<H3>The Region Menu</H3>
+
+The Region Menu contains the following selections:
+
+<DL>
+
+<DT><EM>Erase region</EM>
+<DD>This selection erases any currently defined
+region.
+
+<DT><EM>Draw region</EM>
+<DD>This selection allows the user to use the mouse to
+draw a region on either the Map or Zoom Display Frame. An
+explanation of which mouse buttons to use is displayed in the Menu
+Frame. The user does not need to try to complete the region boundary. The
+last line of the region will be added when the user selects the
+Complete region option on the Region Menu.
+
+
+<DT><EM>Restore last region</EM>
+<DD>This selection restores the last region
+that was drawn. After a region is completed, it will be saved to be
+restored later. Only one previous region is saved.
+
+<DT><EM>Complete region</EM>
+<DD>This selection completes the region that is
+currently being drawn. As noted above, it saves the complete
+region to be restored later, if needed. Once the user has made a
+complete region, it can be analyzed with the Analyze Region
+selection on the <A HREF="#commandmenu">Command Menu</A>.
+
+<DT><EM>Done</EM>
+<DD>Use this selection to return to the
+<A HREF="#commandmenu">Command Menu</A>.
+
+</DL>
+
+<A NAME="redisplaymenu"></a>
+<H3>The Redisplay Map Menu</H3>
+
+The Redisplay Map Menu has the following selections, which are useful
+to redraw the raster maps displayed in the Map and Zoom Display Frames.
+
+<DL>
+
+<DT><EM>Map geographic region</EM>
+<DD>This selection causes the raster map in the Map
+Display Frame to be redrawn.
+
+<DT><EM>Zoom region</EM>
+<DD>This selection causes the Zoom Display Frame to
+be redrawn.
+
+
+<DT><EM>Both</EM>
+<DD>This selection causes both the Map and Zoom Display
+Frames to be redrawn.
+
+<DT><EM>Cancel</EM>
+<DD>Use this selection if you do not want to redisplay
+either of the above regions. The user will be returned to the
+<A HREF="#commandmenu">Command Menu</A>.
+
+</DL>
+
+<A NAME="signaturemenu"></a>
+<H3>The Analyze Region Menu</H3>
+
+The Analyze Region Menu contains the Signature Menu, which
+allows the user to set the number of standard deviations
+and the display color, and then to display (as an overlay)
+the cells that match the signature within the number of
+standard deviations specified. Note that once the matching
+cells are displayed, the Map Display Frame must be
+redisplayed to see only the original raster map again. The
+following selections are available on the Signature Menu:
+
+
+<DL>
+
+<DT><EM>Set std dev's</EM>
+
+<DD>This selection allows the user to set the number of
+standard deviations from the mean for the maximum and
+minimum range. The maximum and minimum range is used when
+finding the cells that "match" the signature. The user is
+presented with a menu of typical choices and an "Other"
+option. If the "Other" option is selected, enter the
+number of standard deviations from the keyboard on the text
+terminal. Otherwise, the selected option will be used.
+When the number of standard deviations is set, the
+histograms for each band will be redrawn with the maximum
+and minimum range marked.
+
+
+<P>
+
+Note that the number in parentheses on this
+selection is the current number of standard deviations.
+
+
+<DT><EM>Set color</EM>
+
+<DD>This selection allows the user to set the color for the
+display of cells that "match" the current signature. The
+user is presented with a menu of color choices. The color
+selected will be used when the Display Matches Menu
+selection is made.
+
+<P>
+
+Note that the color in parentheses on this selection is the current
+color for display.
+
+<DT><EM>Display matches</EM>
+
+<DD>This selection displays the cells that "match" the
+current signature in the current color. A cell "matches"
+the current signature if the cell value in each band is
+between the minimum range and maximum range for that band
+defined by the number of standard deviations currently
+set.
+
+<DT><EM>Done</EM>
+
+<DD>When this selection is chosen, the user will be asked
+whether or not he/she would like to save the current
+signature. If the user answers with the "Yes" selection,
+he/she will be asked to enter a description for the
+resultant signature file on the text terminal keyboard.
+The saved signature file description will be used by <EM>
+<A HREF="i.maxlik.html">i.maxlik</A></EM> to name the
+category that is created from the current signature. After
+either a "No" answer or the signature description is
+entered, the user is returned to the Command Menu.
+
+</DL>
+
+
+<H2>NOTES</H2>
+
+<EM>i.class</EM> uses the current MASK to generate the
+overlay for cells that match a signature. As a result, if
+a MASK already exists it will be removed during the
+execution of this program.
+
+<P>
+The cell values in the image bands cannot fall outside of
+the range of 0 to 255. <EM>i.class</EM> will report an
+error if they do.
+
+<P>
+<EM>i.class</EM>, like some of the other
+<A HREF="imagery.html">imagery</A> programs, does not use the
+
+standard GRASS display frames. After running
+<EM>i.class</EM>, you will need to create a display frame
+(e.g., using
+
+<EM><A HREF="d.frame.html">d.frame</A></EM> or
+
+<EM><A HREF="d.erase.html">d.erase</A></EM>)
+before you can use most of the GRASS display (d.) commands.
+
+<P>
+<EM><A HREF="i.group.html">i.group</A></EM>
+must be run before <EM>i.class</EM> to create an
+<A HREF="i.group.html">imagery</A> group and a subgroup
+containing the image bands to be classified.
+
+<P>
+The user can perform a supervised image classification by
+running <EM>i.class</EM> followed by
+
+<EM><A HREF="i.maxlik.html">i.maxlik</A></EM>.
+
+The user can perform an unsupervised classification
+by running
+
+<EM><A HREF="i.cluster.html">i.cluster</A></EM> followed by
+
+<EM><A HREF="i.maxlik.html">i.maxlik</A></EM>.
+
+<P>
+<EM>i.class</EM> is interactive and requires the user to be running
+a graphics display monitor (see <EM><A HREF="d.mon.html">d.mon</A></EM>)
+to run this program.
+
+
+<H2>SEE ALSO</H2>
+
+The GRASS 4 <em>
+<A HREF="http://grass.itc.it/gdp/imagery/grass4_image_processing.pdf">Image
+Processing manual</A></EM>
+
+<P>
+<EM><A HREF="d.frame.html">d.frame</A>,
+<A HREF="d.mon.html">d.mon</A>,
+<A HREF="g.region.html">g.region</A>,
+<A HREF="i.cca.html">i.cca</A>,
+<A HREF="i.cluster.html">i.cluster</A>,
+<A HREF="r.composite.html">r.composite</A>,
+<A HREF="i.group.html">i.group</A>,
+<A HREF="i.maxlik.html">i.maxlik</A>,
+<A HREF="r.mapcalc.html">r.mapcalc</A></EM>
+
+<H2>AUTHOR</H2>
+
+David Satnik,
+Central Washington University
+
+<p>
+<i>Last changed: $Date$</i>
Deleted: grass/trunk/imagery/i.cluster/description.html
===================================================================
--- grass/trunk/imagery/i.cluster/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/imagery/i.cluster/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,268 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-
-<EM>i.cluster</EM>
-performs the first pass in the GRASS two-pass unsupervised
-classification of imagery, while the GRASS program <EM>
-<A HREF="i.maxlik.html">i.maxlik</A></EM> executes
-the second pass. Both programs must be run to complete the unsupervised
-classification.
-
-
-<P>
-
-<EM>i.cluster</EM> is a clustering algorithm that reads
-through the (raster) imagery data and builds pixel clusters
-based on the spectral reflectances of the pixels (see Figure).
-The pixel clusters are imagery categories that can be related
-to land cover types on the ground. The spectral
-distributions of the clusters (which will be the land cover
-spectral signatures) are influenced by six parameters set
-by the user. The first parameter set by the user is the
-initial number of clusters to be discriminated.
-
-<p>
-<center>
-<img src="landsat_cluster.png" border=1><BR>
-<table border=0 width=590>
-<tr><td><center>
-<i>Fig.: Land use/land cover clustering of LANDSAT scene (simplified)</i>
-</center></td></tr>
-</table>
-</center>
-<p>
-
-<EM>i.cluster</EM> starts by generating spectral signatures
-for this number of clusters and "attempts" to end up with
-this number of clusters during the clustering process. The
-resulting number of clusters and their spectral
-distributions, however, are also influenced by the range of
-the spectral values (category values) in the image files
-and the other parameters set by the user. These parameters
-are: the minimum cluster size, minimum cluster separation,
-the percent convergence, the maximum number of iterations,
-and the row and column sampling intervals.
-
-
-<P>
-
-The cluster spectral signatures that result are composed of
-cluster means and covariance matrices. These cluster means
-and covariance matrices are used in the second pass
-(<EM><A HREF="i.maxlik.html">i.maxlik</A></EM>) to
-classify the image. The clusters or spectral classes
-result can be related to land cover types on the ground.
-
-The user has to specify the name of group file, the name of subgroup
-file, the name of a file to contain result signatures, the
-initial number of clusters to be discriminated, and
-optionally other parameters (see below)
-where the <EM>group</EM> should contain the imagery files
-that the user wishes to classify. The <EM>subgroup</EM> is
-a subset of this group. The user must create a group and
-subgroup by running the GRASS program
-
-<EM><A HREF="i.group.html">i.group</A></EM>
-
-before running <EM>i.cluster</EM>. The subgroup should
-contain only the imagery band files that the user wishes to
-classify. Note that this subgroup must contain more than
-one band file. The purpose of the group and subgroup is to
-collect map layers for classification or analysis. The
-<EM>sigfile</EM> is the file to contain result signatures
-which can be used as input for
-
-<EM><A HREF="i.maxlik.html">i.maxlik</A></EM>.
-
-The classes value is the initial number of clusters to be
-discriminated; any parameter values left unspecified are
-set to their default values.
-
-<H3>Flags:</H3>
-
-<DL>
-
-<DT><B>-q</B>
-
-<DD>Run quietly. Suppresses output of program
-percent-complete messages and the time elapsed from the
-beginning of the program. If this flag is not used, these
-messages are printed out.
-
-</DL>
-
-<H3>Parameters:</H3>
-
-<DL>
-
-
-<DT><B>group=</B><EM>name</EM>
-
-<DD>The name of the group file which contains the imagery
-files that the user wishes to classify.
-
-<DT><B>subgroup=</B><EM>name</EM>
-
-<DD>The name of the subset of the group specified in group
-option, which must contain only imagery band files and more
-than one band file. The user must create a group and a
-subgroup by running the GRASS program
-
-<EM><A HREF="i.group.html">i.group</A></EM>
-
-before
-running <EM>i.cluster</EM>.
-
-<DT><B>sigfile=</B><EM>name</EM>
-
-<DD>The name assigned to output signature file which
-contains signatures of classes and can be used as the input
-file for the GRASS program
-<EM><A HREF="i.maxlik.html">i.maxlik</A></EM>
-for an unsupervised classification.
-
-<DT><B>classes=</B><EM>value</EM>
-
-<DD>The number of clusters that will initially be
-identified in the clustering process before the iterations
-begin.
-
-<DT><B>seed=</B><EM>name</EM>
-
-<DD>The name of a seed signature file is optional. The seed
-signatures are signatures that contain cluster means and
-covariance matrices which were calculated prior to the
-current run of <EM>i.cluster</EM>. They may be acquired
-from a previously run of <EM>i.cluster</EM> or from a
-supervised classification signature training site section
-(e.g., using the signature file output by
-
-<EM><A HREF="i.class.html">i.class</A></EM>).
-
-The purpose of seed signatures is to optimize the cluster
-decision boundaries (means) for the number of clusters
-specified.
-
-<DT><B>sample=</B><EM>row_interval,col_interval</EM>
-
-<DD>These numbers are optional with default values based on
-the size of the data set such that the total pixels to be
-processed is approximately 10,000 (consider round up).
-
-<DT><B>iterations=</B><EM>value</EM>
-
-<DD>This parameter determines the maximum number of
-iterations which is greater than the number of iterations
-predicted to achieve the optimum percent convergence. The
-default value is 30. If the number of iterations reaches
-the maximum designated by the user; the user may want to
-rerun <EM>i.cluster</EM> with a higher number of iterations
-(see <A HREF="#reportfile"><EM>reportfile</EM></A>).
-
-<BR>
-
-Default: 30
-
-<A NAME="convergence"></a>
-<DT><B>convergence=</B><EM>value</EM>
-
-<DD>A high percent convergence is the point at which
-cluster means become stable during the iteration process.
-The default value is 98.0 percent. When clusters are being
-created, their means constantly change as pixels are
-assigned to them and the means are recalculated to include
-the new pixel. After all clusters have been created,
-<EM>i.cluster</EM> begins iterations that change cluster
-means by maximizing the distances between them. As these
-means shift, a higher and higher convergence is
-approached. Because means will never become totally
-static, a percent convergence and a maximum number of
-iterations are supplied to stop the iterative process. The
-percent convergence should be reached before the maximum
-number of iterations. If the maximum number of iterations
-is reached, it is probable that the desired percent
-convergence was not reached. The number of iterations is
-reported in the cluster statistics in the report file
-(see <A HREF="#reportfile"><EM>reportfile</EM></A>).
-
-<BR>
-
-Default: 98.0
-
-<DT><B>separation=</B><EM>value</EM>
-
-<DD>This is the minimum separation below which clusters
-will be merged in the iteration process. The default value
-is 0.0. This is an image-specific number (a "magic" number)
-that depends on the image data being classified and the
-number of final clusters that are acceptable. Its
-determination requires experimentation. Note that as the
-minimum class (or cluster) separation is increased, the
-maximum number of iterations should also be increased to
-achieve this separation with a high percentage of
-convergence
-(see <A HREF="#convergence"><EM>convergence</EM></A>).
-
-<BR>
-
-Default: 0.0
-
-<DT><B>min_size=</B><EM>value</EM>
-
-<DD>This is the minimum number of pixels that will be used
-to define a cluster, and is therefore the minimum number of
-pixels for which means and covariance matrices will be
-calculated.
-
-<BR>
-
-Default: 17
-
-<A NAME="reportfile"></A>
-<DT><B>reportfile=</B><EM>name</EM>
-
-<DD>The reportfile is an optional parameter which contains
-the result, i.e., the statistics for each cluster. Also
-included are the resulting percent convergence for the
-clusters, the number of iterations that was required to
-achieve the convergence, and the separability matrix.
-
-</DL>
-
-
-<H2>NOTES</H2>
-
-Running in command line mode, <EM>i.cluster</EM> will
-overwrite the output signature file and reportfile (if
-required by the user) without prompting if the files
-existed.
-
-<H2>SEE ALSO</H2>
-
-The GRASS 4 <em>
-<A HREF="http://grass.itc.it/gdp/imagery/grass4_image_processing.pdf">Image
-Processing manual</A></EM>
-
-<P>
-
-<EM>
-<A HREF="i.class.html">i.class</A><br>
-<A HREF="i.group.html">i.group</A><br>
-<A HREF="i.gensig.html">i.gensig</A><br>
-<A HREF="i.maxlik.html">i.maxlik</A>
-</EM>
-
-<H2>AUTHORS</H2>
-
-Michael Shapiro,
-U.S.Army Construction Engineering
-Research Laboratory
-
-<BR>
-
-Tao Wen,
-University of Illinois at
-Urbana-Champaign,
-Illinois
-<p>
-<i>Last changed: $Date$</i>
Copied: grass/trunk/imagery/i.cluster/i.cluster.html (from rev 32770, grass/trunk/imagery/i.cluster/description.html)
===================================================================
--- grass/trunk/imagery/i.cluster/i.cluster.html (rev 0)
+++ grass/trunk/imagery/i.cluster/i.cluster.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,268 @@
+<H2>DESCRIPTION</H2>
+
+
+<EM>i.cluster</EM>
+performs the first pass in the GRASS two-pass unsupervised
+classification of imagery, while the GRASS program <EM>
+<A HREF="i.maxlik.html">i.maxlik</A></EM> executes
+the second pass. Both programs must be run to complete the unsupervised
+classification.
+
+
+<P>
+
+<EM>i.cluster</EM> is a clustering algorithm that reads
+through the (raster) imagery data and builds pixel clusters
+based on the spectral reflectances of the pixels (see Figure).
+The pixel clusters are imagery categories that can be related
+to land cover types on the ground. The spectral
+distributions of the clusters (which will be the land cover
+spectral signatures) are influenced by six parameters set
+by the user. The first parameter set by the user is the
+initial number of clusters to be discriminated.
+
+<p>
+<center>
+<img src="landsat_cluster.png" border=1><BR>
+<table border=0 width=590>
+<tr><td><center>
+<i>Fig.: Land use/land cover clustering of LANDSAT scene (simplified)</i>
+</center></td></tr>
+</table>
+</center>
+<p>
+
+<EM>i.cluster</EM> starts by generating spectral signatures
+for this number of clusters and "attempts" to end up with
+this number of clusters during the clustering process. The
+resulting number of clusters and their spectral
+distributions, however, are also influenced by the range of
+the spectral values (category values) in the image files
+and the other parameters set by the user. These parameters
+are: the minimum cluster size, minimum cluster separation,
+the percent convergence, the maximum number of iterations,
+and the row and column sampling intervals.
+
+
+<P>
+
+The cluster spectral signatures that result are composed of
+cluster means and covariance matrices. These cluster means
+and covariance matrices are used in the second pass
+(<EM><A HREF="i.maxlik.html">i.maxlik</A></EM>) to
+classify the image. The clusters or spectral classes
+result can be related to land cover types on the ground.
+
+The user has to specify the name of group file, the name of subgroup
+file, the name of a file to contain result signatures, the
+initial number of clusters to be discriminated, and
+optionally other parameters (see below)
+where the <EM>group</EM> should contain the imagery files
+that the user wishes to classify. The <EM>subgroup</EM> is
+a subset of this group. The user must create a group and
+subgroup by running the GRASS program
+
+<EM><A HREF="i.group.html">i.group</A></EM>
+
+before running <EM>i.cluster</EM>. The subgroup should
+contain only the imagery band files that the user wishes to
+classify. Note that this subgroup must contain more than
+one band file. The purpose of the group and subgroup is to
+collect map layers for classification or analysis. The
+<EM>sigfile</EM> is the file to contain result signatures
+which can be used as input for
+
+<EM><A HREF="i.maxlik.html">i.maxlik</A></EM>.
+
+The classes value is the initial number of clusters to be
+discriminated; any parameter values left unspecified are
+set to their default values.
+
+<H3>Flags:</H3>
+
+<DL>
+
+<DT><B>-q</B>
+
+<DD>Run quietly. Suppresses output of program
+percent-complete messages and the time elapsed from the
+beginning of the program. If this flag is not used, these
+messages are printed out.
+
+</DL>
+
+<H3>Parameters:</H3>
+
+<DL>
+
+
+<DT><B>group=</B><EM>name</EM>
+
+<DD>The name of the group file which contains the imagery
+files that the user wishes to classify.
+
+<DT><B>subgroup=</B><EM>name</EM>
+
+<DD>The name of the subset of the group specified in group
+option, which must contain only imagery band files and more
+than one band file. The user must create a group and a
+subgroup by running the GRASS program
+
+<EM><A HREF="i.group.html">i.group</A></EM>
+
+before
+running <EM>i.cluster</EM>.
+
+<DT><B>sigfile=</B><EM>name</EM>
+
+<DD>The name assigned to output signature file which
+contains signatures of classes and can be used as the input
+file for the GRASS program
+<EM><A HREF="i.maxlik.html">i.maxlik</A></EM>
+for an unsupervised classification.
+
+<DT><B>classes=</B><EM>value</EM>
+
+<DD>The number of clusters that will initially be
+identified in the clustering process before the iterations
+begin.
+
+<DT><B>seed=</B><EM>name</EM>
+
+<DD>The name of a seed signature file is optional. The seed
+signatures are signatures that contain cluster means and
+covariance matrices which were calculated prior to the
+current run of <EM>i.cluster</EM>. They may be acquired
+from a previously run of <EM>i.cluster</EM> or from a
+supervised classification signature training site section
+(e.g., using the signature file output by
+
+<EM><A HREF="i.class.html">i.class</A></EM>).
+
+The purpose of seed signatures is to optimize the cluster
+decision boundaries (means) for the number of clusters
+specified.
+
+<DT><B>sample=</B><EM>row_interval,col_interval</EM>
+
+<DD>These numbers are optional with default values based on
+the size of the data set such that the total pixels to be
+processed is approximately 10,000 (consider round up).
+
+<DT><B>iterations=</B><EM>value</EM>
+
+<DD>This parameter determines the maximum number of
+iterations which is greater than the number of iterations
+predicted to achieve the optimum percent convergence. The
+default value is 30. If the number of iterations reaches
+the maximum designated by the user; the user may want to
+rerun <EM>i.cluster</EM> with a higher number of iterations
+(see <A HREF="#reportfile"><EM>reportfile</EM></A>).
+
+<BR>
+
+Default: 30
+
+<A NAME="convergence"></a>
+<DT><B>convergence=</B><EM>value</EM>
+
+<DD>A high percent convergence is the point at which
+cluster means become stable during the iteration process.
+The default value is 98.0 percent. When clusters are being
+created, their means constantly change as pixels are
+assigned to them and the means are recalculated to include
+the new pixel. After all clusters have been created,
+<EM>i.cluster</EM> begins iterations that change cluster
+means by maximizing the distances between them. As these
+means shift, a higher and higher convergence is
+approached. Because means will never become totally
+static, a percent convergence and a maximum number of
+iterations are supplied to stop the iterative process. The
+percent convergence should be reached before the maximum
+number of iterations. If the maximum number of iterations
+is reached, it is probable that the desired percent
+convergence was not reached. The number of iterations is
+reported in the cluster statistics in the report file
+(see <A HREF="#reportfile"><EM>reportfile</EM></A>).
+
+<BR>
+
+Default: 98.0
+
+<DT><B>separation=</B><EM>value</EM>
+
+<DD>This is the minimum separation below which clusters
+will be merged in the iteration process. The default value
+is 0.0. This is an image-specific number (a "magic" number)
+that depends on the image data being classified and the
+number of final clusters that are acceptable. Its
+determination requires experimentation. Note that as the
+minimum class (or cluster) separation is increased, the
+maximum number of iterations should also be increased to
+achieve this separation with a high percentage of
+convergence
+(see <A HREF="#convergence"><EM>convergence</EM></A>).
+
+<BR>
+
+Default: 0.0
+
+<DT><B>min_size=</B><EM>value</EM>
+
+<DD>This is the minimum number of pixels that will be used
+to define a cluster, and is therefore the minimum number of
+pixels for which means and covariance matrices will be
+calculated.
+
+<BR>
+
+Default: 17
+
+<A NAME="reportfile"></A>
+<DT><B>reportfile=</B><EM>name</EM>
+
+<DD>The reportfile is an optional parameter which contains
+the result, i.e., the statistics for each cluster. Also
+included are the resulting percent convergence for the
+clusters, the number of iterations that was required to
+achieve the convergence, and the separability matrix.
+
+</DL>
+
+
+<H2>NOTES</H2>
+
+Running in command line mode, <EM>i.cluster</EM> will
+overwrite the output signature file and reportfile (if
+required by the user) without prompting if the files
+existed.
+
+<H2>SEE ALSO</H2>
+
+The GRASS 4 <em>
+<A HREF="http://grass.itc.it/gdp/imagery/grass4_image_processing.pdf">Image
+Processing manual</A></EM>
+
+<P>
+
+<EM>
+<A HREF="i.class.html">i.class</A><br>
+<A HREF="i.group.html">i.group</A><br>
+<A HREF="i.gensig.html">i.gensig</A><br>
+<A HREF="i.maxlik.html">i.maxlik</A>
+</EM>
+
+<H2>AUTHORS</H2>
+
+Michael Shapiro,
+U.S.Army Construction Engineering
+Research Laboratory
+
+<BR>
+
+Tao Wen,
+University of Illinois at
+Urbana-Champaign,
+Illinois
+<p>
+<i>Last changed: $Date$</i>
Deleted: grass/trunk/imagery/i.fft/description.html
===================================================================
--- grass/trunk/imagery/i.fft/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/imagery/i.fft/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,76 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-
-<EM>i.fft</EM> is an image processing program based on the FFT algorithm
-given by Frigo et al. (1998), that processes a single input raster map layer
-(<B>input_image</B>) and constructs the real and imaginary Fourier
-components in frequency space.
-
-<H2>NOTES</H2>
-
-The real and imaginary components are stored as arrays of
-doubles in the <EM>cell_misc</EM> directory (for use in the
-inverse transform program,
-
-<EM><A HREF="i.ifft.html">i.ifft</A></EM>),
-
-and are also scaled and formatted into the
-<B>real_image</B> and <B>imaginary_image</B> raster map
-layers for inspection, masking, etc. In these raster map
-layers the low frequency components are in the center and
-the high frequency components are toward the edges. The
-<B>input_image</B> need not be square; before
-processing, the X and Y dimensions of the
-<B>input_image</B> are padded with zeroes to the next
-highest power of two in extent (i.e., 256 x 256 is
-processed at that size, but 200 x 400 is padded to 256 x
-512). The cell category values for viewing, etc., are
-calculated by taking the natural log of the actual values
-then rescaling to 255, or whatever optional range is given
-on the command line, as suggested by Richards (1986). A
-color table is assigned to the resultant map layer.
-
-
-<P>
-
-The current geographic region and mask settings are
-respected when reading the input file. The presence of a
-mask will, in general, make the resulting fast Fourier
-transform invalid, or at least difficult to interpret.
-
-<H2>SEE ALSO</H2>
-
-M. Frigo and S. G. Johnson (1998): "FFTW: An Adaptive Software Architecture
-for the FFT". See <a href=>www.FFTW.org</a>: FFTW is a C subroutine library
-for computing the Discrete Fourier Transform (DFT) in one or more
-dimensions, of both real and complex data, and of arbitrary input size.
-
-<P>
-
-<B>Remote Sensing Digital Image Analysis</B>,
-by John A. Richards,
-Springer-Verlag, 1986.
-
-
-<P>
-
-Personal communication,
-between progam author and Ali R. Vali,
-Space Research Center,
-<A HREF="http://www.utexas.edu">University of Texas</A>, Austin, 1990.
-
-<P>
-
-<EM><A HREF="i.cca.html">i.cca</A></EM><br>
-<EM><A HREF="i.class.html">i.class</A></EM><br>
-<EM><A HREF="i.ifft.html">i.ifft</A></EM><br>
-<EM><A HREF="i.pca.html">i.pca</A></EM>
-
-<H2>AUTHOR</H2>
-
-David Satnik, GIS Laboratory,
-Central Washington University
-<br>
-Glynn Clements (FFTW support)
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/imagery/i.fft/i.fft.html (from rev 32770, grass/trunk/imagery/i.fft/description.html)
===================================================================
--- grass/trunk/imagery/i.fft/i.fft.html (rev 0)
+++ grass/trunk/imagery/i.fft/i.fft.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,76 @@
+<H2>DESCRIPTION</H2>
+
+
+<EM>i.fft</EM> is an image processing program based on the FFT algorithm
+given by Frigo et al. (1998), that processes a single input raster map layer
+(<B>input_image</B>) and constructs the real and imaginary Fourier
+components in frequency space.
+
+<H2>NOTES</H2>
+
+The real and imaginary components are stored as arrays of
+doubles in the <EM>cell_misc</EM> directory (for use in the
+inverse transform program,
+
+<EM><A HREF="i.ifft.html">i.ifft</A></EM>),
+
+and are also scaled and formatted into the
+<B>real_image</B> and <B>imaginary_image</B> raster map
+layers for inspection, masking, etc. In these raster map
+layers the low frequency components are in the center and
+the high frequency components are toward the edges. The
+<B>input_image</B> need not be square; before
+processing, the X and Y dimensions of the
+<B>input_image</B> are padded with zeroes to the next
+highest power of two in extent (i.e., 256 x 256 is
+processed at that size, but 200 x 400 is padded to 256 x
+512). The cell category values for viewing, etc., are
+calculated by taking the natural log of the actual values
+then rescaling to 255, or whatever optional range is given
+on the command line, as suggested by Richards (1986). A
+color table is assigned to the resultant map layer.
+
+
+<P>
+
+The current geographic region and mask settings are
+respected when reading the input file. The presence of a
+mask will, in general, make the resulting fast Fourier
+transform invalid, or at least difficult to interpret.
+
+<H2>SEE ALSO</H2>
+
+M. Frigo and S. G. Johnson (1998): "FFTW: An Adaptive Software Architecture
+for the FFT". See <a href=>www.FFTW.org</a>: FFTW is a C subroutine library
+for computing the Discrete Fourier Transform (DFT) in one or more
+dimensions, of both real and complex data, and of arbitrary input size.
+
+<P>
+
+<B>Remote Sensing Digital Image Analysis</B>,
+by John A. Richards,
+Springer-Verlag, 1986.
+
+
+<P>
+
+Personal communication,
+between progam author and Ali R. Vali,
+Space Research Center,
+<A HREF="http://www.utexas.edu">University of Texas</A>, Austin, 1990.
+
+<P>
+
+<EM><A HREF="i.cca.html">i.cca</A></EM><br>
+<EM><A HREF="i.class.html">i.class</A></EM><br>
+<EM><A HREF="i.ifft.html">i.ifft</A></EM><br>
+<EM><A HREF="i.pca.html">i.pca</A></EM>
+
+<H2>AUTHOR</H2>
+
+David Satnik, GIS Laboratory,
+Central Washington University
+<br>
+Glynn Clements (FFTW support)
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/imagery/i.gensig/description.html
===================================================================
--- grass/trunk/imagery/i.gensig/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/imagery/i.gensig/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,139 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-
-<EM>i.gensig</EM>
-is a non-interactive method for generating input into
-<EM><A HREF="i.maxlik.html">i.maxlik</A></EM>.
-It can be used as the first pass in the GRASS two-pass
-classification process (instead of
-<EM><A HREF="i.cluster.html">i.cluster</A></EM>
- or
-<EM><A HREF="i.class.html">i.class</A></EM>).
-
-It reads a raster map layer, called the training map, which
-has some of the pixels or regions already classified.
-<EM>i.gensig</EM> will then extract spectral signatures
-from an image based on the classification of the pixels in
-the training map and make these signatures available to
-
-<EM><A HREF="i.maxlik.html">i.maxlik</A></EM>.
-
-
-<P>
-
-The user would then execute the GRASS program
-<EM><A HREF="i.maxlik.html">i.maxlik</A></EM>
-to actually create the final classified map.
-
-
-<H2>OPTIONS</H2>
-
-<H3>Parameters</H3>
-
-<DL>
-
-<DT><B>trainingmap=</B><EM>name</EM>
-
-<DD>ground truth training map
-
-<P>
-
-This map must be prepared by the user in advance. Programs like
-<EM><A HREF="v.digit.html">v.digit</A></EM> or <EM>
-<A HREF="r.digit.html">r.digit</A></EM> can be
-used to define representative
-areas of the classes the user defines to be in the image.
-Of course other methods could be devised by the user for creating
-this training map - <EM>i.gensig</EM> makes no assumption about the origin
-of this map layer. It simply creates signatures for the classes defined
-in the training map for the image to be classified (the image is
-specified in other options - see below).
-
-<DT><B>group=</B><EM>name</EM>
-
-<DD>imagery group
-
-<P>
-
-This is the name of the group that contains the band files
-which comprise the image to be analyzed. The <EM>
-<A HREF="i.group.html">i.group</A> </EM> command is
-used to construct groups of raster layers which comprise an
-image.
-
-
-<P>
-
-<A NAME="subgroup"><DT><B>subgroup=</B><EM>name</EM></A>
-
-<DD>subgroup containing image files
-
-<P>
-
-This names the subgroup within the group that selects a
-subset of the bands to be analyzed. The <EM>
-<A HREF="i.group.html">i.group</A> </EM> command is
-also used to prepare this subgroup. The subgroup mechanism
-allows the user to select a subset of all the band files
-that form an image.
-
-
-<DT><B>signaturefile=</B><EM>name</EM>
-
-<DD>resultant signature file
-
-<P>
-
-This is the resultant signature file (containing the means
-and covariance matrices) for each class in the training map
-that is associated with the band files in the subgroup
-select (see <A HREF="#subgroup">above</A>).
-
-</DL>
-
-<H2>INTERACTIVE MODE</H2>
-
-If none of the arguments are specified on the command line,
-<EM>i.gensig</EM>
-will interactively prompt for the names of these maps and files.
-
-
-<P>
-
-It should be noted that interactive mode here only means
-interactive prompting for maps and files.
-It does not mean visualization of the signatures that
-result from the process.
-
-
-<H2>SEE ALSO</H2>
-
-<EM><A HREF="i.group.html">i.group</A></EM>
-for creating groups and subgroups.
-
-<P>
-
-<EM><A HREF="v.digit.html">v.digit</A></EM>
-and
-<EM><A HREF="r.digit.html">r.digit</A></EM>
-for interactively creating the training map.
-
-<P>
-
-<EM><A HREF="i.cluster.html">i.cluster</A></EM>
-for unsupervised clustering as an alternative to
-<EM>i.gensig</EM> to create signatures.
-
-
-<P>
-
-<EM><A HREF="i.class.html">i.class</A></EM>
-for a graphic/interactive as an alternative to
-<EM>i.gensig</EM> to create signatures.
-
-<H2>AUTHOR</H2>
-
-Michael Shapiro,
-U.S.Army Construction Engineering Research Laboratory
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/imagery/i.gensig/i.gensig.html (from rev 32770, grass/trunk/imagery/i.gensig/description.html)
===================================================================
--- grass/trunk/imagery/i.gensig/i.gensig.html (rev 0)
+++ grass/trunk/imagery/i.gensig/i.gensig.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,139 @@
+<H2>DESCRIPTION</H2>
+
+
+<EM>i.gensig</EM>
+is a non-interactive method for generating input into
+<EM><A HREF="i.maxlik.html">i.maxlik</A></EM>.
+It can be used as the first pass in the GRASS two-pass
+classification process (instead of
+<EM><A HREF="i.cluster.html">i.cluster</A></EM>
+ or
+<EM><A HREF="i.class.html">i.class</A></EM>).
+
+It reads a raster map layer, called the training map, which
+has some of the pixels or regions already classified.
+<EM>i.gensig</EM> will then extract spectral signatures
+from an image based on the classification of the pixels in
+the training map and make these signatures available to
+
+<EM><A HREF="i.maxlik.html">i.maxlik</A></EM>.
+
+
+<P>
+
+The user would then execute the GRASS program
+<EM><A HREF="i.maxlik.html">i.maxlik</A></EM>
+to actually create the final classified map.
+
+
+<H2>OPTIONS</H2>
+
+<H3>Parameters</H3>
+
+<DL>
+
+<DT><B>trainingmap=</B><EM>name</EM>
+
+<DD>ground truth training map
+
+<P>
+
+This map must be prepared by the user in advance. Programs like
+<EM><A HREF="v.digit.html">v.digit</A></EM> or <EM>
+<A HREF="r.digit.html">r.digit</A></EM> can be
+used to define representative
+areas of the classes the user defines to be in the image.
+Of course other methods could be devised by the user for creating
+this training map - <EM>i.gensig</EM> makes no assumption about the origin
+of this map layer. It simply creates signatures for the classes defined
+in the training map for the image to be classified (the image is
+specified in other options - see below).
+
+<DT><B>group=</B><EM>name</EM>
+
+<DD>imagery group
+
+<P>
+
+This is the name of the group that contains the band files
+which comprise the image to be analyzed. The <EM>
+<A HREF="i.group.html">i.group</A> </EM> command is
+used to construct groups of raster layers which comprise an
+image.
+
+
+<P>
+
+<A NAME="subgroup"><DT><B>subgroup=</B><EM>name</EM></A>
+
+<DD>subgroup containing image files
+
+<P>
+
+This names the subgroup within the group that selects a
+subset of the bands to be analyzed. The <EM>
+<A HREF="i.group.html">i.group</A> </EM> command is
+also used to prepare this subgroup. The subgroup mechanism
+allows the user to select a subset of all the band files
+that form an image.
+
+
+<DT><B>signaturefile=</B><EM>name</EM>
+
+<DD>resultant signature file
+
+<P>
+
+This is the resultant signature file (containing the means
+and covariance matrices) for each class in the training map
+that is associated with the band files in the subgroup
+select (see <A HREF="#subgroup">above</A>).
+
+</DL>
+
+<H2>INTERACTIVE MODE</H2>
+
+If none of the arguments are specified on the command line,
+<EM>i.gensig</EM>
+will interactively prompt for the names of these maps and files.
+
+
+<P>
+
+It should be noted that interactive mode here only means
+interactive prompting for maps and files.
+It does not mean visualization of the signatures that
+result from the process.
+
+
+<H2>SEE ALSO</H2>
+
+<EM><A HREF="i.group.html">i.group</A></EM>
+for creating groups and subgroups.
+
+<P>
+
+<EM><A HREF="v.digit.html">v.digit</A></EM>
+and
+<EM><A HREF="r.digit.html">r.digit</A></EM>
+for interactively creating the training map.
+
+<P>
+
+<EM><A HREF="i.cluster.html">i.cluster</A></EM>
+for unsupervised clustering as an alternative to
+<EM>i.gensig</EM> to create signatures.
+
+
+<P>
+
+<EM><A HREF="i.class.html">i.class</A></EM>
+for a graphic/interactive as an alternative to
+<EM>i.gensig</EM> to create signatures.
+
+<H2>AUTHOR</H2>
+
+Michael Shapiro,
+U.S.Army Construction Engineering Research Laboratory
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/imagery/i.gensigset/description.html
===================================================================
--- grass/trunk/imagery/i.gensigset/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/imagery/i.gensigset/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,264 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-
-<EM>i.gensigset</EM>
-is a non-interactive method for generating input into
-
-<EM><A HREF="i.smap.html">i.smap</A>.</EM>
-
-It is used as the first pass in the a two-pass
-classification process. It reads a raster map layer,
-called the training map, which has some of the pixels or
-regions already classified. <EM>i.gensigset</EM> will then
-extract spectral signatures from an image based on the
-classification of the pixels in the training map and make
-these signatures available to
-
-<EM><A HREF="i.smap.html">i.smap</A>.</EM>
-
-
-<P>
-
-The user would then execute the GRASS program <EM>
-<A HREF="i.smap.html">i.smap</A></EM> to create the
-final classified map.
-
-<H2>OPTIONS</H2>
-
-<H3>Parameters</H3>
-
-<DL>
-
-<DT><B>trainingmap=</B><EM>name</EM>
-
-<DD>ground truth training map
-
-
-<P>
-
-This raster layer, supplied as input by the user, has some
-of its pixels already classified, and the rest (probably
-most) of the pixels unclassified. Classified means that
-the pixel has a non-zero value and unclassified means that
-the pixel has a zero value.
-
-<P>
-
-This map must be prepared by the user in advance.
-The user must use
-
-<EM><A HREF="r.digit.html">r.digit</A></EM>,
-
-a combination of
-<EM><A HREF="v.digit.html">v.digit</A></EM>
-and
-<EM><A HREF="v.to.rast.html">v.to.rast</A></EM>,
-or some other import/developement process (e.g.,
-<EM><A HREF="v.in.transects.html">v.in.transects</A>)</EM>
-to define the areas
-representative
-of the classes in the image.
-
-
-<P>
-
-At present, there is no fully-interactive tool specifically
-designed for producing this layer.
-
-<DT><B>group=</B><EM>name</EM>
-
-<DD>imagery group
-
-<P>
-
-This is the name of the group that contains the band files
-which comprise the image to be analyzed. The
-
-<EM><A HREF="i.group.html">i.group</A></EM>
-
-command is used to construct groups of raster layers which
-comprise an image.
-
-<P>
-
-<DT><B>subgroup=</B><EM>name</EM>
-
-<DD>subgroup containing image files
-
-
-<P>
-
-This names the subgroup within the group that selects a
-subset of the bands to be analyzed. The
-
-<EM><A HREF="i.group.html">i.group</A></EM>
-
-command is also used to prepare this subgroup. The
-subgroup mechanism allows the user to select a subset of
-all the band files that form an image.
-
-
-<DT><B>signaturefile=</B><EM>name</EM>
-
-<DD>resultant signature file
-
-<P>
-
-This is the resultant signature file (containing the means
-and covariance matrices) for each class in the training map
-that is associated with the band files in the subgroup
-selected.
-
-<P>
-
-
-<DT><B>maxsig=</B><EM>value</EM>
-
-<DD>maximum number of sub-signatures in any class
-
-<BR>
-
-default: 10
-
-<P>
-
-The spectral signatures which are produced by this program
-are "mixed" signatures (see <A HREF="#notes">NOTES</A>).
-Each signature contains one or more subsignatures
-(represeting subclasses). The algorithm in this program
-starts with a maximum number of subclasses and reduces this
-number to a minimal number of subclasses which are
-spectrally distinct. The user has the option to set this
-starting value with this option.
-
-</DL>
-
-
-<H2>INTERACTIVE MODE</H2>
-
-If none of the arguments are specified on the command line,
-<EM>i.gensigset</EM> will interactively prompt for the
-names of these maps and files.
-
-<P>
-
-It should be noted that interactive mode here only means
-interactive prompting for maps and files. It does not mean
-visualization of the signatures that result from the
-process.
-
-<P>
-
-
-<A NAME="notes"><H2>NOTES</H2></A>
-
-The algorithm in <EM>i.gensigset</EM> determines the
-parameters of a spectral class model known as a Gaussian
-mixture distribution. The parameters are estimated using
-multispectral image data and a training map which labels
-the class of a subset of the image pixels. The mixture
-class parameters are stored as a class signature which can
-be used for subsequent segmentation (i.e., classification)
-of the multispectral image.
-
-<P>
-
-The Gaussian mixture class is a useful model because it can
-be used to describe the behavior of an information class
-which contains pixels with a variety of distinct spectral
-characteristics. For example, forest, grasslands or urban
-areas are examples of information classes that a user may
-wish to separate in an image. However, each of these
-information classes may contain subclasses each with its
-own distinctive spectral characteristic. For example, a
-forest may contain a variety of different tree species each
-with its own spectral behavior.
-
-
-<P>
-
-The objective of mixture classes is to improve segmentation
-performance by modeling each information class as a
-probabilistic mixture with a variety of subclasses. The
-mixture class model also removes the need to perform an
-initial unsupervised segmentation for the purposes of
-identifying these subclasses. However, if misclassified
-samples are used in the training process, these erroneous
-samples may be grouped as a separate undesired subclass.
-Therefore, care should be taken to provided accurate
-training data.
-
-
-<P>
-
-This clustering algorithm estimates both the number of
-distinct subclasses in each class, and the spectral mean
-and covariance for each subclass. The number of subclasses
-is estimated using Rissanen's minimum description length
-(MDL) criteria
-[<A HREF="#rissanen83">1</A>].
-This criteria attempts to determine
-the number of subclasses which "best" describe the data.
-The approximate maximum likelihood estimates of the mean
-and covariance of the subclasses are computed using the
-expectation maximization (EM) algorithm
-[<A HREF="#dempster77">2</A>,<A HREF="#redner84">3</A>].
-
-
-<H2>REFERENCES</H2>
-
-<OL>
-
-<LI><A NAME="rissanen83">J. Rissanen,</A>
-"A Universal Prior for Integers and Estimation by Minimum
-Description Length,"
-<EM>Annals of Statistics,</EM>
-vol. 11, no. 2, pp. 417-431, 1983.
-
-
-<LI><A NAME="dempster77">A. Dempster, N. Laird and D. Rubin,</A>
-"Maximum Likelihood from Incomplete Data via the EM Algorithm,"
-<EM>J. Roy. Statist. Soc. B,</EM>
-vol. 39, no. 1, pp. 1-38, 1977.
-
-<LI><A NAME="redner84">E. Redner and H. Walker,</A>
-"Mixture Densities, Maximum Likelihood and the EM Algorithm,"
-<EM>SIAM Review,</EM>
-vol. 26, no. 2, April 1984.
-
-</OL>
-
-<H2>SEE ALSO</H2>
-
-<EM><A HREF="i.group.html">i.group</A></EM>
-for creating groups and subgroups
-
-
-<P>
-
-<EM><A HREF="v.digit.html">v.digit</A></EM>
-and
-<EM><A HREF="r.digit.html">r.digit</A></EM>
-for interactively creating the training map.
-
-
-<P>
-
-<EM><A HREF="i.smap.html">i.smap</A></EM>
-for creating a final classification layer from the signatures
-generated by <EM>i.gensigset.</EM>
-
-
-<H2>AUTHORS</H2>
-
-Charles Bouman,
-School of
-Electrical Engineering,
-Purdue University
-<BR>
-
-Michael Shapiro,
-U.S.Army Construction Engineering
-Research Laboratory
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/imagery/i.gensigset/i.gensigset.html (from rev 32770, grass/trunk/imagery/i.gensigset/description.html)
===================================================================
--- grass/trunk/imagery/i.gensigset/i.gensigset.html (rev 0)
+++ grass/trunk/imagery/i.gensigset/i.gensigset.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,264 @@
+<H2>DESCRIPTION</H2>
+
+
+<EM>i.gensigset</EM>
+is a non-interactive method for generating input into
+
+<EM><A HREF="i.smap.html">i.smap</A>.</EM>
+
+It is used as the first pass in the a two-pass
+classification process. It reads a raster map layer,
+called the training map, which has some of the pixels or
+regions already classified. <EM>i.gensigset</EM> will then
+extract spectral signatures from an image based on the
+classification of the pixels in the training map and make
+these signatures available to
+
+<EM><A HREF="i.smap.html">i.smap</A>.</EM>
+
+
+<P>
+
+The user would then execute the GRASS program <EM>
+<A HREF="i.smap.html">i.smap</A></EM> to create the
+final classified map.
+
+<H2>OPTIONS</H2>
+
+<H3>Parameters</H3>
+
+<DL>
+
+<DT><B>trainingmap=</B><EM>name</EM>
+
+<DD>ground truth training map
+
+
+<P>
+
+This raster layer, supplied as input by the user, has some
+of its pixels already classified, and the rest (probably
+most) of the pixels unclassified. Classified means that
+the pixel has a non-zero value and unclassified means that
+the pixel has a zero value.
+
+<P>
+
+This map must be prepared by the user in advance.
+The user must use
+
+<EM><A HREF="r.digit.html">r.digit</A></EM>,
+
+a combination of
+<EM><A HREF="v.digit.html">v.digit</A></EM>
+and
+<EM><A HREF="v.to.rast.html">v.to.rast</A></EM>,
+or some other import/developement process (e.g.,
+<EM><A HREF="v.in.transects.html">v.in.transects</A>)</EM>
+to define the areas
+representative
+of the classes in the image.
+
+
+<P>
+
+At present, there is no fully-interactive tool specifically
+designed for producing this layer.
+
+<DT><B>group=</B><EM>name</EM>
+
+<DD>imagery group
+
+<P>
+
+This is the name of the group that contains the band files
+which comprise the image to be analyzed. The
+
+<EM><A HREF="i.group.html">i.group</A></EM>
+
+command is used to construct groups of raster layers which
+comprise an image.
+
+<P>
+
+<DT><B>subgroup=</B><EM>name</EM>
+
+<DD>subgroup containing image files
+
+
+<P>
+
+This names the subgroup within the group that selects a
+subset of the bands to be analyzed. The
+
+<EM><A HREF="i.group.html">i.group</A></EM>
+
+command is also used to prepare this subgroup. The
+subgroup mechanism allows the user to select a subset of
+all the band files that form an image.
+
+
+<DT><B>signaturefile=</B><EM>name</EM>
+
+<DD>resultant signature file
+
+<P>
+
+This is the resultant signature file (containing the means
+and covariance matrices) for each class in the training map
+that is associated with the band files in the subgroup
+selected.
+
+<P>
+
+
+<DT><B>maxsig=</B><EM>value</EM>
+
+<DD>maximum number of sub-signatures in any class
+
+<BR>
+
+default: 10
+
+<P>
+
+The spectral signatures which are produced by this program
+are "mixed" signatures (see <A HREF="#notes">NOTES</A>).
+Each signature contains one or more subsignatures
+(represeting subclasses). The algorithm in this program
+starts with a maximum number of subclasses and reduces this
+number to a minimal number of subclasses which are
+spectrally distinct. The user has the option to set this
+starting value with this option.
+
+</DL>
+
+
+<H2>INTERACTIVE MODE</H2>
+
+If none of the arguments are specified on the command line,
+<EM>i.gensigset</EM> will interactively prompt for the
+names of these maps and files.
+
+<P>
+
+It should be noted that interactive mode here only means
+interactive prompting for maps and files. It does not mean
+visualization of the signatures that result from the
+process.
+
+<P>
+
+
+<A NAME="notes"><H2>NOTES</H2></A>
+
+The algorithm in <EM>i.gensigset</EM> determines the
+parameters of a spectral class model known as a Gaussian
+mixture distribution. The parameters are estimated using
+multispectral image data and a training map which labels
+the class of a subset of the image pixels. The mixture
+class parameters are stored as a class signature which can
+be used for subsequent segmentation (i.e., classification)
+of the multispectral image.
+
+<P>
+
+The Gaussian mixture class is a useful model because it can
+be used to describe the behavior of an information class
+which contains pixels with a variety of distinct spectral
+characteristics. For example, forest, grasslands or urban
+areas are examples of information classes that a user may
+wish to separate in an image. However, each of these
+information classes may contain subclasses each with its
+own distinctive spectral characteristic. For example, a
+forest may contain a variety of different tree species each
+with its own spectral behavior.
+
+
+<P>
+
+The objective of mixture classes is to improve segmentation
+performance by modeling each information class as a
+probabilistic mixture with a variety of subclasses. The
+mixture class model also removes the need to perform an
+initial unsupervised segmentation for the purposes of
+identifying these subclasses. However, if misclassified
+samples are used in the training process, these erroneous
+samples may be grouped as a separate undesired subclass.
+Therefore, care should be taken to provided accurate
+training data.
+
+
+<P>
+
+This clustering algorithm estimates both the number of
+distinct subclasses in each class, and the spectral mean
+and covariance for each subclass. The number of subclasses
+is estimated using Rissanen's minimum description length
+(MDL) criteria
+[<A HREF="#rissanen83">1</A>].
+This criteria attempts to determine
+the number of subclasses which "best" describe the data.
+The approximate maximum likelihood estimates of the mean
+and covariance of the subclasses are computed using the
+expectation maximization (EM) algorithm
+[<A HREF="#dempster77">2</A>,<A HREF="#redner84">3</A>].
+
+
+<H2>REFERENCES</H2>
+
+<OL>
+
+<LI><A NAME="rissanen83">J. Rissanen,</A>
+"A Universal Prior for Integers and Estimation by Minimum
+Description Length,"
+<EM>Annals of Statistics,</EM>
+vol. 11, no. 2, pp. 417-431, 1983.
+
+
+<LI><A NAME="dempster77">A. Dempster, N. Laird and D. Rubin,</A>
+"Maximum Likelihood from Incomplete Data via the EM Algorithm,"
+<EM>J. Roy. Statist. Soc. B,</EM>
+vol. 39, no. 1, pp. 1-38, 1977.
+
+<LI><A NAME="redner84">E. Redner and H. Walker,</A>
+"Mixture Densities, Maximum Likelihood and the EM Algorithm,"
+<EM>SIAM Review,</EM>
+vol. 26, no. 2, April 1984.
+
+</OL>
+
+<H2>SEE ALSO</H2>
+
+<EM><A HREF="i.group.html">i.group</A></EM>
+for creating groups and subgroups
+
+
+<P>
+
+<EM><A HREF="v.digit.html">v.digit</A></EM>
+and
+<EM><A HREF="r.digit.html">r.digit</A></EM>
+for interactively creating the training map.
+
+
+<P>
+
+<EM><A HREF="i.smap.html">i.smap</A></EM>
+for creating a final classification layer from the signatures
+generated by <EM>i.gensigset.</EM>
+
+
+<H2>AUTHORS</H2>
+
+Charles Bouman,
+School of
+Electrical Engineering,
+Purdue University
+<BR>
+
+Michael Shapiro,
+U.S.Army Construction Engineering
+Research Laboratory
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/imagery/i.group/description.html
===================================================================
--- grass/trunk/imagery/i.group/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/imagery/i.group/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,51 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-<EM>i.group</EM> allows the user to collect raster map layers in an imagery
-group by assigning them to user-named subgroups or other groups. This
-enables the user to run analyses on any combination of the raster map layers
-in a group. The user creates the groups and subgroups and selects the
-raster map layers that are to reside in them. Imagery analysis programs like
-<EM><A HREF="i.points.html">i.points</A></EM>,
-<EM><a href="i.rectify.html">i.rectify</A></EM>, <EM>i.ortho.rectify</EM> and
-others ask the user for the name of an imagery group whose data are to be
-analyzed. Imagery analysis programs like
-<EM><a href="i.cluster.html">i.cluster</A></EM> and
-<EM><a href="i.maxlik.html">i.maxlik</A></EM> ask the user for the imagery group
-and imagery subgroup whose data are to be analyzed.
-
-
-<H2>NOTES</H2>
-
-The <EM>i.group</EM> options are only available for
-imagery map layers in the current LOCATION_NAME.
-
-<P>
-Subgroup names may not contain more than 12 characters.
-
-
-<H2>SEE ALSO</H2>
-
-The GRASS 4 <em>
-<A HREF="http://grass.itc.it/gdp/imagery/grass4_image_processing.pdf">Image
-Processing manual</A></EM>
-
-<P>
-<EM>
-<A HREF="i.cluster.html">i.cluster</A><br>
-<A HREF="i.maxlik.html">i.maxlik</A><br>
-<A HREF="i.points.html">i.points</A><br>
-<A HREF="i.rectify.html">i.rectify</A><br>
-<a HREF="i.ortho.photo.html">i.ortho.photo</A>
-</EM>
-
-
-<H2>AUTHOR</H2>
-
-Michael Shapiro,
-U.S.Army Construction Engineering
-Research Laboratory
-<br>
-Parser support: Bob Covill (Tekmap, Canada)
-
-<p>
-<i>Last changed: $Date$</i>
Copied: grass/trunk/imagery/i.group/i.group.html (from rev 32770, grass/trunk/imagery/i.group/description.html)
===================================================================
--- grass/trunk/imagery/i.group/i.group.html (rev 0)
+++ grass/trunk/imagery/i.group/i.group.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,51 @@
+<H2>DESCRIPTION</H2>
+
+<EM>i.group</EM> allows the user to collect raster map layers in an imagery
+group by assigning them to user-named subgroups or other groups. This
+enables the user to run analyses on any combination of the raster map layers
+in a group. The user creates the groups and subgroups and selects the
+raster map layers that are to reside in them. Imagery analysis programs like
+<EM><A HREF="i.points.html">i.points</A></EM>,
+<EM><a href="i.rectify.html">i.rectify</A></EM>, <EM>i.ortho.rectify</EM> and
+others ask the user for the name of an imagery group whose data are to be
+analyzed. Imagery analysis programs like
+<EM><a href="i.cluster.html">i.cluster</A></EM> and
+<EM><a href="i.maxlik.html">i.maxlik</A></EM> ask the user for the imagery group
+and imagery subgroup whose data are to be analyzed.
+
+
+<H2>NOTES</H2>
+
+The <EM>i.group</EM> options are only available for
+imagery map layers in the current LOCATION_NAME.
+
+<P>
+Subgroup names may not contain more than 12 characters.
+
+
+<H2>SEE ALSO</H2>
+
+The GRASS 4 <em>
+<A HREF="http://grass.itc.it/gdp/imagery/grass4_image_processing.pdf">Image
+Processing manual</A></EM>
+
+<P>
+<EM>
+<A HREF="i.cluster.html">i.cluster</A><br>
+<A HREF="i.maxlik.html">i.maxlik</A><br>
+<A HREF="i.points.html">i.points</A><br>
+<A HREF="i.rectify.html">i.rectify</A><br>
+<a HREF="i.ortho.photo.html">i.ortho.photo</A>
+</EM>
+
+
+<H2>AUTHOR</H2>
+
+Michael Shapiro,
+U.S.Army Construction Engineering
+Research Laboratory
+<br>
+Parser support: Bob Covill (Tekmap, Canada)
+
+<p>
+<i>Last changed: $Date$</i>
Deleted: grass/trunk/imagery/i.his.rgb/description.html
===================================================================
--- grass/trunk/imagery/i.his.rgb/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/imagery/i.his.rgb/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,47 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-
-<EM>i.his.rgb</EM> is an image processing program that
-processes three input raster map layers as hue, intensity
-and saturation components and produces three output raster
-map layers representing the red, green and blue components
-of this data. The output raster map layers are created by
-a standard hue-intensity-saturation (his) to red-green-blue
-(rgb) color transformation. Each output raster map layer
-is given a linear gray scale color table. The current
-geographic region and mask settings are respected.
-
-<H2>NOTES</H2>
-
-It is not possible to process three bands with
-<EM>i.his.rgb</EM> and then exactly recover the original
-bands with
-
-<EM><A HREF="i.rgb.his.html">i.rgb.his</A></EM>.
-
-This is due to loss of precision because of integer
-computations and rounding. Tests have shown that more than
-70% of the original cell values will be reproduced exactly
-after transformation in both directions and that 99% will
-be within plus or minus 1. A few cell values may differ
-significantly from their original values.
-
-<H2>SEE ALSO</H2>
-
-<EM><A HREF="hsv.rgb.sh.html">hsv.rgb.sh</A></EM><br>
-<EM><A HREF="i.colors.html">i.colors</A></EM><br>
-<EM><A HREF="i.rgb.his.html">i.rgb.his</A></EM><br>
-<EM><A HREF="r.colors.html">r.colors</A></EM><br>
-<EM><A HREF="rgb.hsv.sh.html">rgb.hsv.sh</A></EM>
-
-<H2>AUTHOR</H2>
-
-David Satnik, GIS Laboratory,
-Central Washington University
-
-<P>
-
-with acknowledgements to Ali Vali, Univ. of Texas Space Research
-Center, for the core routine.
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/imagery/i.his.rgb/i.his.rgb.html (from rev 32770, grass/trunk/imagery/i.his.rgb/description.html)
===================================================================
--- grass/trunk/imagery/i.his.rgb/i.his.rgb.html (rev 0)
+++ grass/trunk/imagery/i.his.rgb/i.his.rgb.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,47 @@
+<H2>DESCRIPTION</H2>
+
+
+<EM>i.his.rgb</EM> is an image processing program that
+processes three input raster map layers as hue, intensity
+and saturation components and produces three output raster
+map layers representing the red, green and blue components
+of this data. The output raster map layers are created by
+a standard hue-intensity-saturation (his) to red-green-blue
+(rgb) color transformation. Each output raster map layer
+is given a linear gray scale color table. The current
+geographic region and mask settings are respected.
+
+<H2>NOTES</H2>
+
+It is not possible to process three bands with
+<EM>i.his.rgb</EM> and then exactly recover the original
+bands with
+
+<EM><A HREF="i.rgb.his.html">i.rgb.his</A></EM>.
+
+This is due to loss of precision because of integer
+computations and rounding. Tests have shown that more than
+70% of the original cell values will be reproduced exactly
+after transformation in both directions and that 99% will
+be within plus or minus 1. A few cell values may differ
+significantly from their original values.
+
+<H2>SEE ALSO</H2>
+
+<EM><A HREF="hsv.rgb.sh.html">hsv.rgb.sh</A></EM><br>
+<EM><A HREF="i.colors.html">i.colors</A></EM><br>
+<EM><A HREF="i.rgb.his.html">i.rgb.his</A></EM><br>
+<EM><A HREF="r.colors.html">r.colors</A></EM><br>
+<EM><A HREF="rgb.hsv.sh.html">rgb.hsv.sh</A></EM>
+
+<H2>AUTHOR</H2>
+
+David Satnik, GIS Laboratory,
+Central Washington University
+
+<P>
+
+with acknowledgements to Ali Vali, Univ. of Texas Space Research
+Center, for the core routine.
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/imagery/i.ifft/description.html
===================================================================
--- grass/trunk/imagery/i.ifft/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/imagery/i.ifft/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,73 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-
-<EM>i.ifft</EM> is an image processing program based on the algorithm given
-by Frigo et al. (1998), that converts real and imaginary frequency space
-images (produced by
-<EM><A HREF="i.fft.html">i.fft</A></EM>) into a normal image.
-
-<H2>NOTES</H2>
-
-The current mask is respected when reading the real and
-imaginary component files; thus, creating a mask is a
-primary step for
-selecting the portion of the frequency space data to be included in the
-inverse transform. The GRASS program <EM>r.digit</EM> can be used to create
-masks while viewing the real or imaginary component image. Alternatively
-<em>r.circle</em> can be used to generate high-, low- and donut filters
-specifying the DC point as circle/ring center.
-When <EM>i.ifft</EM> is executed, it (automatically) uses the same GRASS
-region definition setting that was used during the original transformation
-done with <EM><A HREF="i.fft.html">i.fft</A></EM>.
-
-
-<P>
-
-The real and imaginary components are read from arrays of
-doubles in the <EM>cell_misc</EM> directory (produced by
-the forward transform program,
-
-<EM><A HREF="i.fft.html">i.fft</A></EM>),
-
-and the reconstructed image will preserve the cell value
-scaling of the original image processed by
-
-<EM><A HREF="i.fft.html">i.fft</A></EM>. No color
-table is assigned to the output map; one should be created
-before viewing the <EM>output_image</EM>.
-
-<H2>SEE ALSO</H2>
-
-M. Frigo and S. G. Johnson (1998): "FFTW: An Adaptive Software Architecture
-for the FFT". See <a href=>www.FFTW.org</a>: FFTW is a C subroutine library
-for computing the Discrete Fourier Transform (DFT) in one or more
-dimensions, of both real and complex data, and of arbitrary input size.
-
-<P>
-
-<B>Remote Sensing Digital Image Analysis</B>,
-by John A. Richards,
-Springer-Verlag, 1986.
-
-<P>
-
-Personal communication,
-between program author and Ali R. Vali, Space Research Center,
-University of Texas, Austin, 1990.
-
-<P>
-
-<EM><A HREF="i.cca.html">i.cca</A></EM>,
-<EM><A HREF="i.class.html">i.class</A></EM>,
-<EM><A HREF="i.fft.html">i.fft</A></EM>,
-<EM><A HREF="i.pca.html">i.pca</A></EM>,
-<EM><A HREF="r.circle.html">r.circle</A></EM>
-
-<H2>AUTHOR</H2>
-
-David Satnik, GIS Laboratory,
-Central Washington University
-<br>
-Glynn Clements (FFTW support)
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/imagery/i.ifft/i.ifft.html (from rev 32770, grass/trunk/imagery/i.ifft/description.html)
===================================================================
--- grass/trunk/imagery/i.ifft/i.ifft.html (rev 0)
+++ grass/trunk/imagery/i.ifft/i.ifft.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,73 @@
+<H2>DESCRIPTION</H2>
+
+
+<EM>i.ifft</EM> is an image processing program based on the algorithm given
+by Frigo et al. (1998), that converts real and imaginary frequency space
+images (produced by
+<EM><A HREF="i.fft.html">i.fft</A></EM>) into a normal image.
+
+<H2>NOTES</H2>
+
+The current mask is respected when reading the real and
+imaginary component files; thus, creating a mask is a
+primary step for
+selecting the portion of the frequency space data to be included in the
+inverse transform. The GRASS program <EM>r.digit</EM> can be used to create
+masks while viewing the real or imaginary component image. Alternatively
+<em>r.circle</em> can be used to generate high-, low- and donut filters
+specifying the DC point as circle/ring center.
+When <EM>i.ifft</EM> is executed, it (automatically) uses the same GRASS
+region definition setting that was used during the original transformation
+done with <EM><A HREF="i.fft.html">i.fft</A></EM>.
+
+
+<P>
+
+The real and imaginary components are read from arrays of
+doubles in the <EM>cell_misc</EM> directory (produced by
+the forward transform program,
+
+<EM><A HREF="i.fft.html">i.fft</A></EM>),
+
+and the reconstructed image will preserve the cell value
+scaling of the original image processed by
+
+<EM><A HREF="i.fft.html">i.fft</A></EM>. No color
+table is assigned to the output map; one should be created
+before viewing the <EM>output_image</EM>.
+
+<H2>SEE ALSO</H2>
+
+M. Frigo and S. G. Johnson (1998): "FFTW: An Adaptive Software Architecture
+for the FFT". See <a href=>www.FFTW.org</a>: FFTW is a C subroutine library
+for computing the Discrete Fourier Transform (DFT) in one or more
+dimensions, of both real and complex data, and of arbitrary input size.
+
+<P>
+
+<B>Remote Sensing Digital Image Analysis</B>,
+by John A. Richards,
+Springer-Verlag, 1986.
+
+<P>
+
+Personal communication,
+between program author and Ali R. Vali, Space Research Center,
+University of Texas, Austin, 1990.
+
+<P>
+
+<EM><A HREF="i.cca.html">i.cca</A></EM>,
+<EM><A HREF="i.class.html">i.class</A></EM>,
+<EM><A HREF="i.fft.html">i.fft</A></EM>,
+<EM><A HREF="i.pca.html">i.pca</A></EM>,
+<EM><A HREF="r.circle.html">r.circle</A></EM>
+
+<H2>AUTHOR</H2>
+
+David Satnik, GIS Laboratory,
+Central Washington University
+<br>
+Glynn Clements (FFTW support)
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/imagery/i.maxlik/description.html
===================================================================
--- grass/trunk/imagery/i.maxlik/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/imagery/i.maxlik/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,187 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-
-<EM>i.maxlik</EM> is a maximum-likelihood discriminant
-analysis classifier. It can be used to perform the second
-step in either an unsupervised or a supervised image
-classification.
-
-<P>
-Either image classification methods are performed in two
-steps. The first step in an unsupervised image
-classification is performed by
-<EM><A HREF="i.cluster.html">i.cluster</A></EM>; the
-first step in a supervised classification is executed by
-the GRASS program <EM>
-<A HREF="i.class.html">i.class</A></EM>. In both cases,
-the second step in the image classification procedure is
-performed by <EM>i.maxlik</EM>.
-
-
-<P>
-In an unsupervised classification, the maximum-likelihood
-classifier uses the cluster means and covariance matrices
-from the <EM><A HREF="i.cluster.html">i.cluster</A></EM>
-signature file to determine to which category (spectral
-class) each cell in the image has the highest probability
-of belonging. In a supervised image classification, the
-maximum-likelihood classifier uses the region means and
-covariance matrices from the spectral signature file
-generated by <EM>
-<A HREF="i.class.html">i.class</A></EM>, based on regions
-(groups of image pixels) chosen by the user, to determine
-to which category each cell in the image has the highest
-probability of belonging.
-
-
-<P>
-In either case, the raster map layer output by
-<EM>i.maxlik</EM> is a classified image in which each cell
-has been assigned to a spectral class (i.e., a category).
-The spectral classes (categories) can be related to
-specific land cover types on the ground.
-
-
-<P>
-The program will run non-interactively if the user
-specifies the names of raster map layers, i.e., group and
-subgroup names, seed signature file name, result
-classification file name, and any combination of
-non-required options in the command line, using the form
-
-
-<DL>
-<DD>
-<B>i.maxlik</B>[<B>-q</B>] <B>group=</B><EM>name</EM>
-<B>subgroup=</B><EM>name</EM>
-<B>sigfile=</B><EM>name</EM> <B>class=</B><EM>name</EM>
-[<B>reject=</B><EM>name</EM>]
-</DL>
-
-where each flag and options have the meanings stated below.
-
-<P>
-
-Alternatively, the user can simply type <EM>i.maxlik</EM>
-in the command line without program arguments. In this case
-the user will be prompted for the program parameter
-settings; the program will run foreground.
-
-
-<H2>OPTIONS</H2>
-
-
-<H3>Flags:</H3>
-
-<DL>
-
-<DT><B>-q</B>
-
-<DD>Run quietly, without printing program messages to standard output.
-
-</DL>
-
-<H3>Parameters:</H3>
-
-<DL>
-
-<DT><B>group=</B><EM>name</EM>
-
-<DD>The <A HREF="i.group.html">imagery</A> group
-contains the subgroup to be classified.
-
-<DT><B>subgroup=</B><EM>name</EM>
-
-<DD>The subgroup contains image files, which were used to create
-the signature file
-in the program <EM><A HREF="i.cluster.html">i.cluster</A></EM>,
-<EM><A HREF="i.class.html">i.class</A></EM>, or
-<EM><A HREF="i.gensig.html">i.gensig</A></EM> to be classified.
-
-<DT><B>sigfile=</B><EM>name</EM>
-
-<DD>The name of the signatures to be used for the
-classification. The signature file contains the cluster and
-covariance matrices that were calculated by the GRASS
-program <EM><A HREF="i.cluster.html">i.cluster</A></EM>
-(or the region means and covariance matrices generated by
-<EM><A HREF="i.class.html">i.class</A></EM>, if the
-user runs a supervised classification). These spectral
-signatures are what determine the categories (classes) to
-which image pixels will be assigned during the
-classification process.
-
-<DT><B>class=</B><EM>name</EM>
-
-<DD>The name of a raster map holds the classification
-results. This new raster map layer will contain categories
-that can be related to land cover categories on the
-ground.
-
-<DT><B>reject=</B><EM>name</EM>
-
-<DD>The optional name of a raster map holds the reject
-threshold results. This is the result of a chi square test
-on each discriminant result at various threshold levels of
-confidence to determine at what confidence level each cell
-classified (categorized). It is the reject threshold map
-layer, and contains one calculated confidence level for
-each classified cell in the classified image. One of the
-possible uses for this map layer is as a mask, to identify
-cells in the classified image that have the lowest
-probability of being assigned to the correct class.
-
-</DL>
-
-
-<H2>NOTES</H2>
-
-The maximum-likelihood classifier assumes that the spectral
-signatures for each class (category) in each band file
-are normally distributed (i.e., Gaussian in nature).
-Algorithms, such as
-<EM><A HREF="i.cluster.html">i.cluster</A></EM>,
-<EM><A HREF="i.class.html">i.class</A></EM>,
-or <EM><A HREF="i.gensig.html">i.gensig</A></EM>,
-however, can create signatures that are not valid
-distributed (more likely with
-<EM><A HREF="i.class.html">i.class</A>).</EM>
-If this occurs,
-<EM>i.maxlik</EM>
-will reject them and display a warning message.
-
-<P>
-This program runs interactively if the user types
-<EM>i.maxlik</EM> only. If the user types <EM>i.maxlik</EM>
-along with all required options, it will overwrite the
-classified raster map without prompting if this map
-existed.
-
-
-<H2>SEE ALSO</H2>
-
-The GRASS 4 <em>
-<A HREF="http://grass.itc.it/gdp/imagery/grass4_image_processing.pdf">Image
-Processing manual</A></EM>
-
-<P>
-<EM>
-<A HREF="i.class.html">i.class</A><br>
-<A HREF="i.cluster.html">i.cluster</A><br>
-<A HREF="i.gensig.html">i.gensig</A><br>
-<A HREF="i.group.html">i.group</A>
-</EM>
-
-<H2>AUTHORS</H2>
-
-Michael Shapiro,
-U.S.Army Construction Engineering
-Research Laboratory
-
-<BR>
-Tao Wen,
-University of Illinois at Urbana-Champaign,
-Illinois
-
-<p>
-<i>Last changed: $Date$</i>
Copied: grass/trunk/imagery/i.maxlik/i.maxlik.html (from rev 32770, grass/trunk/imagery/i.maxlik/description.html)
===================================================================
--- grass/trunk/imagery/i.maxlik/i.maxlik.html (rev 0)
+++ grass/trunk/imagery/i.maxlik/i.maxlik.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,187 @@
+<H2>DESCRIPTION</H2>
+
+
+<EM>i.maxlik</EM> is a maximum-likelihood discriminant
+analysis classifier. It can be used to perform the second
+step in either an unsupervised or a supervised image
+classification.
+
+<P>
+Either image classification methods are performed in two
+steps. The first step in an unsupervised image
+classification is performed by
+<EM><A HREF="i.cluster.html">i.cluster</A></EM>; the
+first step in a supervised classification is executed by
+the GRASS program <EM>
+<A HREF="i.class.html">i.class</A></EM>. In both cases,
+the second step in the image classification procedure is
+performed by <EM>i.maxlik</EM>.
+
+
+<P>
+In an unsupervised classification, the maximum-likelihood
+classifier uses the cluster means and covariance matrices
+from the <EM><A HREF="i.cluster.html">i.cluster</A></EM>
+signature file to determine to which category (spectral
+class) each cell in the image has the highest probability
+of belonging. In a supervised image classification, the
+maximum-likelihood classifier uses the region means and
+covariance matrices from the spectral signature file
+generated by <EM>
+<A HREF="i.class.html">i.class</A></EM>, based on regions
+(groups of image pixels) chosen by the user, to determine
+to which category each cell in the image has the highest
+probability of belonging.
+
+
+<P>
+In either case, the raster map layer output by
+<EM>i.maxlik</EM> is a classified image in which each cell
+has been assigned to a spectral class (i.e., a category).
+The spectral classes (categories) can be related to
+specific land cover types on the ground.
+
+
+<P>
+The program will run non-interactively if the user
+specifies the names of raster map layers, i.e., group and
+subgroup names, seed signature file name, result
+classification file name, and any combination of
+non-required options in the command line, using the form
+
+
+<DL>
+<DD>
+<B>i.maxlik</B>[<B>-q</B>] <B>group=</B><EM>name</EM>
+<B>subgroup=</B><EM>name</EM>
+<B>sigfile=</B><EM>name</EM> <B>class=</B><EM>name</EM>
+[<B>reject=</B><EM>name</EM>]
+</DL>
+
+where each flag and options have the meanings stated below.
+
+<P>
+
+Alternatively, the user can simply type <EM>i.maxlik</EM>
+in the command line without program arguments. In this case
+the user will be prompted for the program parameter
+settings; the program will run foreground.
+
+
+<H2>OPTIONS</H2>
+
+
+<H3>Flags:</H3>
+
+<DL>
+
+<DT><B>-q</B>
+
+<DD>Run quietly, without printing program messages to standard output.
+
+</DL>
+
+<H3>Parameters:</H3>
+
+<DL>
+
+<DT><B>group=</B><EM>name</EM>
+
+<DD>The <A HREF="i.group.html">imagery</A> group
+contains the subgroup to be classified.
+
+<DT><B>subgroup=</B><EM>name</EM>
+
+<DD>The subgroup contains image files, which were used to create
+the signature file
+in the program <EM><A HREF="i.cluster.html">i.cluster</A></EM>,
+<EM><A HREF="i.class.html">i.class</A></EM>, or
+<EM><A HREF="i.gensig.html">i.gensig</A></EM> to be classified.
+
+<DT><B>sigfile=</B><EM>name</EM>
+
+<DD>The name of the signatures to be used for the
+classification. The signature file contains the cluster and
+covariance matrices that were calculated by the GRASS
+program <EM><A HREF="i.cluster.html">i.cluster</A></EM>
+(or the region means and covariance matrices generated by
+<EM><A HREF="i.class.html">i.class</A></EM>, if the
+user runs a supervised classification). These spectral
+signatures are what determine the categories (classes) to
+which image pixels will be assigned during the
+classification process.
+
+<DT><B>class=</B><EM>name</EM>
+
+<DD>The name of a raster map holds the classification
+results. This new raster map layer will contain categories
+that can be related to land cover categories on the
+ground.
+
+<DT><B>reject=</B><EM>name</EM>
+
+<DD>The optional name of a raster map holds the reject
+threshold results. This is the result of a chi square test
+on each discriminant result at various threshold levels of
+confidence to determine at what confidence level each cell
+classified (categorized). It is the reject threshold map
+layer, and contains one calculated confidence level for
+each classified cell in the classified image. One of the
+possible uses for this map layer is as a mask, to identify
+cells in the classified image that have the lowest
+probability of being assigned to the correct class.
+
+</DL>
+
+
+<H2>NOTES</H2>
+
+The maximum-likelihood classifier assumes that the spectral
+signatures for each class (category) in each band file
+are normally distributed (i.e., Gaussian in nature).
+Algorithms, such as
+<EM><A HREF="i.cluster.html">i.cluster</A></EM>,
+<EM><A HREF="i.class.html">i.class</A></EM>,
+or <EM><A HREF="i.gensig.html">i.gensig</A></EM>,
+however, can create signatures that are not valid
+distributed (more likely with
+<EM><A HREF="i.class.html">i.class</A>).</EM>
+If this occurs,
+<EM>i.maxlik</EM>
+will reject them and display a warning message.
+
+<P>
+This program runs interactively if the user types
+<EM>i.maxlik</EM> only. If the user types <EM>i.maxlik</EM>
+along with all required options, it will overwrite the
+classified raster map without prompting if this map
+existed.
+
+
+<H2>SEE ALSO</H2>
+
+The GRASS 4 <em>
+<A HREF="http://grass.itc.it/gdp/imagery/grass4_image_processing.pdf">Image
+Processing manual</A></EM>
+
+<P>
+<EM>
+<A HREF="i.class.html">i.class</A><br>
+<A HREF="i.cluster.html">i.cluster</A><br>
+<A HREF="i.gensig.html">i.gensig</A><br>
+<A HREF="i.group.html">i.group</A>
+</EM>
+
+<H2>AUTHORS</H2>
+
+Michael Shapiro,
+U.S.Army Construction Engineering
+Research Laboratory
+
+<BR>
+Tao Wen,
+University of Illinois at Urbana-Champaign,
+Illinois
+
+<p>
+<i>Last changed: $Date$</i>
Deleted: grass/trunk/imagery/i.ortho.photo/menu/description.html
===================================================================
--- grass/trunk/imagery/i.ortho.photo/menu/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/imagery/i.ortho.photo/menu/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,201 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-<EM>i.ortho.photo</EM>
-allows the user to ortho-rectify imagery group files.
-An imagery group consists of several scanned aerial photographs
-(raster maps) of a common area.
-Imagery groups can be created or modified using the
-GRASS Image Processing Program
-
-<EM><A HREF="i.group.html">i.group</A></EM>,
-
-or using the first menu option described below.
-<EM>i.ortho.photo</EM> guides the user through the steps required to
-ortho-rectify the raster maps in a single imagery group.
-
-
-<P>
-
-The first menu in <EM>i.ortho.photo</EM> provides the user with the following
-options:
-
-
-<DL>
-<DT>Initialization Options:
-<DD>
-1) Select/Modify imagery group <BR>
-2) Select/Modify imagery group target<BR>
-3) Select/Modify target elevation model <BR>
-4) Select/Modify imagery group camera <BR>
-<BR>
-<DT>Transformation Parameter Computation:
-<DD>
-5) Compute image-to-photo transformation parameters<BR>
-6) Initialize exposure station parameters<BR>
-7) Compute photo-to-target transformation parameters<BR>
-<BR>
-<DT>Ortho-rectification Option:
-<DD>
-8) Ortho-rectify imagery group raster maps
-<BR>
-<DT>RETURN to exit
-<DD>>
-
-</DL>
-
-To ortho-rectify aerial images the user has to follow the menu options step by
-step. Generally the user builds a target location containing a projected DEM
-and a map reference (topo sheet or other map). Another xy-location will
-contain the aerial photo. The entire rectification process is started within
-the xy-location. First the target to the projected location has to be set
-(i.target), then the image references (fiducial points) will be defined. After
-describing the camera parameters, reference points from aerial image to the
-topo sheet from the target location will be set. The local elevation will be
-taken from the target DEM. Finally the aerial image will be rectified.
-<p>
-The options to follow are described as follows:
-
-<DL>
-<DT><EM>1. Select/Modify imagery group</EM>
-
-<DD>The current imagery group is display at the top of the
-previous menu. You may select another (new or existing)
-imagery group for the ortho-rectification program using
-option (1). After choosing option (1) you will be prompted
-for the name of a new or existing imagery group. Option
-(1) using the GRASS Image Processing Program
-
-<EM><A HREF="i.group.html">i.group</A></EM>,
-
-for creation or modification of imagery groups. For more
-information on imagery group creation or modification
-please the the GRASS manual page for
-
-<EM><A HREF="i.group.html">i.group</A></EM>.
-
-
-<DT><EM>2. Select/Modify imagery group target</EM>
-
-<DD>The target location and mapset may be selected or
-modified using option (2). After choosing option (2) you
-will be prompted for the names of the target location and
-mapset, where the ortho-rectified raster maps will
-reside. The target location is also the location from
-which the elevation model (raster map) will be selected --
-see option (3). Option (2) uses the GRASS Image Processing
-Program
-
-<EM><A HREF="i.target.html">i.target</A></EM>,
-
-for selection or
-modification of the imagery group target location and mapset.
-For more information on imagery group
-selection or modification please the the GRASS manual page for
-
-<EM><A HREF="i.target.html">i.target</A></EM>.
-
-
-<DT><EM>3. Select/Modify target elevation model</EM>
-
-<DD>Option (3) allows you to select the raster map from
-the target location to be used as the elevation model. The
-elevation model is required for both the computation of
-photo-to-target parameters (option 6) and for the
-ortho-rectification of the imagery group files (option 8).
-The raster map select for the elevation model should cover
-the entire area of the image group to be ortho-rectified.
-Currently, the elevation model raster map is expected to
-be in units of meters. DTED and DEM files are suitable for
-use as the elevation model in the ortho-rectification
-program. After selection option (3) you will be prompted
-for the name of the raster map in the target location that
-you want to use as the elevation model.
-
-
-<DT><EM>4. Select/Modify imagery group camera</EM>
-
-<DD>Using option (4) you may select or create an camera
-reference file that will be used with the current imagery
-group. A camera reference file contains information on the
-internal characteristics of the aerial camera, as well as
-the geometry of the fiducial or reseau marks. The most
-important characteristic of the camera is its focal
-length. Fiducial or reseau marks locations are required to
-compute the scanned image to photo-coordinate
-transformation parameter (option 5). For a more detailed
-description of option (4) please see the GRASS manual page
-for
-
-<EM><A HREF="photo.camera.html">photo.camera</A></EM>.
-
-
-<DT><EM>5. Compute image-to-photo transformation parameters</EM>
-
-<DD>The scanned image to photo-coordinate transformation
-parameters are computed using option (5). In this
-interactive option you associate scanned reference points
-(fiducials, reseau marks, etc.) with their known photo
-coordinates from the camera reference file. Complete
-documentation for this option is available under the manual
-entry
-
-<EM><A HREF="photo.2image.html">photo.2image</A></EM>.
-
-<DT><EM>6. Initialize exposure station parameters</EM>
-
-<DD>If option (6) is selected, initial camera exposure
-station parameters and initial variances may be selected or
-modified. Complete documentation for this option is
-available under the manual entry
-<EM><A HREF="photo.init.html">photo.init</A></EM>.
-
-<DT><EM>7. Compute photo-to-target transformation parameters</EM>
-
-<DD>The photo to target transformation parameters are
-compute using option (7). Here control points are marked on
-one or more imagery group files and associated with there
-known standard (e.g. UTM) and elevation coordinates. Complete
-documentation for this option is available under the manual
-entry
-<EM><A HREF="photo.2target.html">photo.2target</A></EM>.
-
-
-
-<DT><EM>8. Ortho-photo imagery group files</EM>
-
-<DD>Option (8) is used to perform the actual image
-ortho-rectification after all of the transformation
-parameters have been computed. Ortho-rectified raster
-files will be created in the target location for each
-selected imagery group file. You may select either the
-current window in the target location or the minimal
-bounding window for the ortho-rectified image. Complete
-documentation for this option is available under the manual
-entry
-
-<EM><A HREF="photo.rectify.html">photo.rectify</A></EM>.
-
-</DL>
-
-<H2>NOTES</H2>
-
-<EM>i.ortho.photo</EM> currently requires the elevation
-model to be in meters, and the target location to be a standard (e.g. UTM)
-coordinate system.
-
-<H2>SEE ALSO</H2>
-
-<EM><A HREF="photo.camera.html">photo.camera</A></EM>,
-<EM><A HREF="photo.2image.html">photo.2image</A></EM>,
-<EM><A HREF="photo.2target.html">photo.2target</A></EM>,
-<EM><A HREF="photo.init.html">photo.init</A></EM>,
-<EM><A HREF="photo.rectify.html">photo.rectify</A></EM>
-
-<H2>AUTHOR</H2>
-
-Mike Baba, DBA Systems, Inc.
-<P>
-Updated rectification and elevation map to FP 1/2002 Markus Neteler
-
-<p>
-<i>Last changed: $Date$</i>
Copied: grass/trunk/imagery/i.ortho.photo/menu/i.ortho.photo.html (from rev 32770, grass/trunk/imagery/i.ortho.photo/menu/description.html)
===================================================================
--- grass/trunk/imagery/i.ortho.photo/menu/i.ortho.photo.html (rev 0)
+++ grass/trunk/imagery/i.ortho.photo/menu/i.ortho.photo.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,201 @@
+<H2>DESCRIPTION</H2>
+
+<EM>i.ortho.photo</EM>
+allows the user to ortho-rectify imagery group files.
+An imagery group consists of several scanned aerial photographs
+(raster maps) of a common area.
+Imagery groups can be created or modified using the
+GRASS Image Processing Program
+
+<EM><A HREF="i.group.html">i.group</A></EM>,
+
+or using the first menu option described below.
+<EM>i.ortho.photo</EM> guides the user through the steps required to
+ortho-rectify the raster maps in a single imagery group.
+
+
+<P>
+
+The first menu in <EM>i.ortho.photo</EM> provides the user with the following
+options:
+
+
+<DL>
+<DT>Initialization Options:
+<DD>
+1) Select/Modify imagery group <BR>
+2) Select/Modify imagery group target<BR>
+3) Select/Modify target elevation model <BR>
+4) Select/Modify imagery group camera <BR>
+<BR>
+<DT>Transformation Parameter Computation:
+<DD>
+5) Compute image-to-photo transformation parameters<BR>
+6) Initialize exposure station parameters<BR>
+7) Compute photo-to-target transformation parameters<BR>
+<BR>
+<DT>Ortho-rectification Option:
+<DD>
+8) Ortho-rectify imagery group raster maps
+<BR>
+<DT>RETURN to exit
+<DD>>
+
+</DL>
+
+To ortho-rectify aerial images the user has to follow the menu options step by
+step. Generally the user builds a target location containing a projected DEM
+and a map reference (topo sheet or other map). Another xy-location will
+contain the aerial photo. The entire rectification process is started within
+the xy-location. First the target to the projected location has to be set
+(i.target), then the image references (fiducial points) will be defined. After
+describing the camera parameters, reference points from aerial image to the
+topo sheet from the target location will be set. The local elevation will be
+taken from the target DEM. Finally the aerial image will be rectified.
+<p>
+The options to follow are described as follows:
+
+<DL>
+<DT><EM>1. Select/Modify imagery group</EM>
+
+<DD>The current imagery group is display at the top of the
+previous menu. You may select another (new or existing)
+imagery group for the ortho-rectification program using
+option (1). After choosing option (1) you will be prompted
+for the name of a new or existing imagery group. Option
+(1) using the GRASS Image Processing Program
+
+<EM><A HREF="i.group.html">i.group</A></EM>,
+
+for creation or modification of imagery groups. For more
+information on imagery group creation or modification
+please the the GRASS manual page for
+
+<EM><A HREF="i.group.html">i.group</A></EM>.
+
+
+<DT><EM>2. Select/Modify imagery group target</EM>
+
+<DD>The target location and mapset may be selected or
+modified using option (2). After choosing option (2) you
+will be prompted for the names of the target location and
+mapset, where the ortho-rectified raster maps will
+reside. The target location is also the location from
+which the elevation model (raster map) will be selected --
+see option (3). Option (2) uses the GRASS Image Processing
+Program
+
+<EM><A HREF="i.target.html">i.target</A></EM>,
+
+for selection or
+modification of the imagery group target location and mapset.
+For more information on imagery group
+selection or modification please the the GRASS manual page for
+
+<EM><A HREF="i.target.html">i.target</A></EM>.
+
+
+<DT><EM>3. Select/Modify target elevation model</EM>
+
+<DD>Option (3) allows you to select the raster map from
+the target location to be used as the elevation model. The
+elevation model is required for both the computation of
+photo-to-target parameters (option 6) and for the
+ortho-rectification of the imagery group files (option 8).
+The raster map select for the elevation model should cover
+the entire area of the image group to be ortho-rectified.
+Currently, the elevation model raster map is expected to
+be in units of meters. DTED and DEM files are suitable for
+use as the elevation model in the ortho-rectification
+program. After selection option (3) you will be prompted
+for the name of the raster map in the target location that
+you want to use as the elevation model.
+
+
+<DT><EM>4. Select/Modify imagery group camera</EM>
+
+<DD>Using option (4) you may select or create an camera
+reference file that will be used with the current imagery
+group. A camera reference file contains information on the
+internal characteristics of the aerial camera, as well as
+the geometry of the fiducial or reseau marks. The most
+important characteristic of the camera is its focal
+length. Fiducial or reseau marks locations are required to
+compute the scanned image to photo-coordinate
+transformation parameter (option 5). For a more detailed
+description of option (4) please see the GRASS manual page
+for
+
+<EM><A HREF="photo.camera.html">photo.camera</A></EM>.
+
+
+<DT><EM>5. Compute image-to-photo transformation parameters</EM>
+
+<DD>The scanned image to photo-coordinate transformation
+parameters are computed using option (5). In this
+interactive option you associate scanned reference points
+(fiducials, reseau marks, etc.) with their known photo
+coordinates from the camera reference file. Complete
+documentation for this option is available under the manual
+entry
+
+<EM><A HREF="photo.2image.html">photo.2image</A></EM>.
+
+<DT><EM>6. Initialize exposure station parameters</EM>
+
+<DD>If option (6) is selected, initial camera exposure
+station parameters and initial variances may be selected or
+modified. Complete documentation for this option is
+available under the manual entry
+<EM><A HREF="photo.init.html">photo.init</A></EM>.
+
+<DT><EM>7. Compute photo-to-target transformation parameters</EM>
+
+<DD>The photo to target transformation parameters are
+compute using option (7). Here control points are marked on
+one or more imagery group files and associated with there
+known standard (e.g. UTM) and elevation coordinates. Complete
+documentation for this option is available under the manual
+entry
+<EM><A HREF="photo.2target.html">photo.2target</A></EM>.
+
+
+
+<DT><EM>8. Ortho-photo imagery group files</EM>
+
+<DD>Option (8) is used to perform the actual image
+ortho-rectification after all of the transformation
+parameters have been computed. Ortho-rectified raster
+files will be created in the target location for each
+selected imagery group file. You may select either the
+current window in the target location or the minimal
+bounding window for the ortho-rectified image. Complete
+documentation for this option is available under the manual
+entry
+
+<EM><A HREF="photo.rectify.html">photo.rectify</A></EM>.
+
+</DL>
+
+<H2>NOTES</H2>
+
+<EM>i.ortho.photo</EM> currently requires the elevation
+model to be in meters, and the target location to be a standard (e.g. UTM)
+coordinate system.
+
+<H2>SEE ALSO</H2>
+
+<EM><A HREF="photo.camera.html">photo.camera</A></EM>,
+<EM><A HREF="photo.2image.html">photo.2image</A></EM>,
+<EM><A HREF="photo.2target.html">photo.2target</A></EM>,
+<EM><A HREF="photo.init.html">photo.init</A></EM>,
+<EM><A HREF="photo.rectify.html">photo.rectify</A></EM>
+
+<H2>AUTHOR</H2>
+
+Mike Baba, DBA Systems, Inc.
+<P>
+Updated rectification and elevation map to FP 1/2002 Markus Neteler
+
+<p>
+<i>Last changed: $Date$</i>
Modified: grass/trunk/imagery/i.ortho.photo/photo.2image/Makefile
===================================================================
--- grass/trunk/imagery/i.ortho.photo/photo.2image/Makefile 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/imagery/i.ortho.photo/photo.2image/Makefile 2008-08-15 06:16:42 UTC (rev 32772)
@@ -11,6 +11,6 @@
default: etc
-$(PGM).tmp.html: description.html
+$(PGM).tmp.html: $(PGM).html
$(INSTALL_DATA) $< $@
Deleted: grass/trunk/imagery/i.ortho.photo/photo.2image/description.html
===================================================================
--- grass/trunk/imagery/i.ortho.photo/photo.2image/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/imagery/i.ortho.photo/photo.2image/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,377 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-<head>
-<title>photo.2image</title>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link rel="stylesheet" href="grassdocs.css" type="text/css">
-</head>
-<body bgcolor="white">
-
-<img src="grass_logo.png" alt="GRASS logo"><hr align=center size=6 noshade>
-
-<h2>NAME</h2>
-<em><b>photo.2image</b></em>
-
-<H2>DESCRIPTION</H2>
-
-<EM>photo.2image</EM> is an imagery function that enables
-you to mark fiducial or reseau points on an image to be
-ortho-rectified and then computes the image-to-photo
-coordinate transformation parameters. The coordinates of
-the fiducials or reseau marks can be choosen for a camera
-reference file.
-
-<P>
-
-During the process of marking reference points with known
-photo coordinates, you may compute the RMS (root mean
-square) error for each reference point entered.
-<EM>photo.2image</EM> does this by calculating the
-transformation equation (the same one that is calculated by
-<EM><A HREF="i.points.html">i.points</A> </EM>),
-and then plugging these results into an equation for RMS
-error.
-
-
-<P>
-
-<EM>photo.2image</EM> offers a zoom option to locate
-precisely the fiducial or reseau point to be marked on an
-image.
-
-
-<P>
-
-To run <EM>photo.2image</EM>, a graphics monitor is
-required.
-
-<P>
-
-The procedure for marking fiducial or reseau points,
-entering known photo-coordinates, and analyzing the RMS
-error is described below.
-
-
-<P>
-
-The terminal screen displays this message:
-
-
-<P>
-
-<B>use mouse now...</B>
-
-
-<P>
-
-The graphics monitor displays the following screen:
-
-<PRE>
- +---------------------------+---------------------------------+
- |imagery | |
- +---------------------------+---------------------------------+
- | | |
- | | |
- | | |
- | | |
- | | |
- | | |
- | | |
- +---------------------------+---------------------------------+
- | | |
- | | |
- | | |
- | | |
- | | |
- | | |
- | | |
- +---------------------------+---------------------------------+
- | | |
- +---------------------------+---------------------------------+
-</PRE>
-
-<P>
-
-A pop-down menu like that shown below will be superimposed on the
-left half of the screen:
-
-<P>
-<PRE>
- +------------------------------------------+
- | Double click on raster map to be plotted |
- | Double click here to cancel |
- +------------------------------------------+
- +----------------+
- |Mapset imagery |
- +-------+--------+
- |gs13.1 | gs21.1 |
- +-------+--------+
- |gs14.1 | gs22.2 |
- +-------+--------+
-</PRE>
-Any single file in the imagery group may be used on which to mark
-points, and you may mark points on more than one file
-in the imagery group to accumulate the suggested minimum number of
-4-8 fiducial or ressue points.
-The imagery file selected is displayed in the upper
-left quadrant of the screen.
-<P>
-
-<H2>CAMERA FILE</H2>
-
-The camera reference file may be viewed by placing the mouse
-cross hairs on the words CAMERA. The camera reference file
-will be displayed in the lower left quadrant of the display:
-
-
-<P>
-<PRE>
-
-|---------------------------------------------------------------|
-|Camera Reference File |
-|---------------------------------------------------------------|
-| CAMERA NAME : camera name |
-| CAMERA ID : L1234 |
-| CAMERA CFL : 153.021 mm. |
-| CAMERA XP : 0.050 mm. |
-| CAMERA XP : 0.056 mm. |
-| number of fid. 4 |
-|---------------------------------------------------------------|
-| |
-|ID (X PHOTO) mm. (Y PHOTO) mm. |
-|_______________________________________________________________|
-|1 -105.023 110.123 |
-|2 107.987 109.834 |
-|3 110.965 -104.329 |
-|4 -103.932 -110.352 |
-|_______________________________________________________________|
-</PRE>
-<P>
-The following menu is displayed at the bottom
-of the graphics display:
-<P>
-<B>
-<PRE>
-+-----+------+-----------+--------+---------+-------------------+-------------+
-|Quit | Zoom | Plot Cell | Camera | Analyze | Input->KEYBOARD | CAMERA FILE |
-+-----+------+-----------+--------+---------+-------------------+-------------+
-</PRE>
-</B>
-<P>
-<H2>ZOOM</H2>
-
-To magnify the displayed file, you must
-place the mouse cross hairs on the word ZOOM. The following menu
-will then be displayed at the bottom of the screen:
-<P>
-<B>
-<PRE>
-+-------+-----+-------++--------------------+
-|Cancel | Box | Point ||Select type of ZOOM |
-+-------+-----+-------++--------------------+
-</PRE>
-</B>
-<P>
-You have the option of identifying the zoom window either by using
-the mouse to make a box, or by using the mouse to mark the center
-of the desired window, and adjusting the magnification factor.
-The terminal screen will display a mouse button menu to guide you in
-identifying the window. The section of the image within the zoom window
-will be displayed in the upper right hand quadrant.
-<P>
-<H2>MARKING REFERENCE POINTS</H2>
-
-To mark the known reference points (fiducial marks, reseau marks, etc.)
-on the image, you must place the mouse cross hairs
-on the corresponding location on the image to be marked and press
-the left hand button on the mouse. A diamond shaped symbol will be marked
-on the image.
-<P>
-If you wish to use the camera reference file only as a
-comparative reference, then the keyboard can be chosen as
-the means to input photo coordinates corresponding to the marked
-reference points on the image. This is done by placing the mouse
-cross hairs on the word KEYBOARD and pressing the left
-button on the mouse.
-<P>
-The following menu is displayed on the graphics terminal:
-<P>
-<PRE>
-+------------------------------------+--------------------------+
-|Point 1 marked at IMAGE COORDINATES | |
-|east: 1023.77 | |
-|north: 506.56 | |
-| | |
-| | |
-| | |
-| | |
-| | |
-+------------------------------------+--------------------------+
-|Enter PHOTO COORDINATES as x and y: |
-+---------------------------------------------------------------+
-</PRE>
-</B>
-<P>
-You then enter the known (x,y) photo coordinates, relative
-to the perspective center, for the reference
-point marked on the image. If you
-do not wish to enter a coordinate, simply hit RETURN to continue;
-the marked reference point will disappear.
-<P>
-If you select the CAMERA FILE option, then reference points
-marked on the image will be associated with selected photo
-coordinates from the displayed camera reference file. In this option,
-when you mark a point on the image, the following menu is
-displayed on the graphics terminal:
-<P>
-<PRE>
--------------------------------------------------------------
-CANCEL Double click on the fiducial mark to be referenced
--------------------------------------------------------------
-</PRE>
-<P>
-
-If you would like to select the photo coordinates of a displayed
-reference mark, this can be accomplished by placing the mouse
-cross hairs on the reference point to be selected and pressing
-the left button on the mouse twice. After a reference point is selected
-from the display, you are prompted with "Look ok? (Y/N)".
-If you respond with no, the reference point is ignored.
-If you respond with yes, the following is displayed on the terminal:
-<P>
-<P>
-<PRE>
-+----------------------------------------+--------------------------+
-|Point 1 marked at IMAGE COORDINATES | |
-|east: 1023.77 | |
-|north: 1065.41 | |
-| | |
-| | |
-|Point 1 referenced at PHOTO COORDINATES | |
-|X: -105.023 | |
-|Y: 110.122 | |
-| | |
-| | |
-| | |
-| | |
-| | |
-+----------------------------------------+--------------------------+
-| use mouse now... |
-+----------------------------------------+--------------------------+
-</PRE>
-</B>
-<P>
-The photo coordinates and the corresponding image coordinates are
-automatically saved in the photo_points file associated with the imagery
-group.
-<P>
-<P>
-<H2>ANALYZE</H2>
-
-After a number of points have been marked (4 to 8), you can
-check the RMS error of the points marked on the image. This is done
-by placing the mouse cross hairs on the word ANALYZE at the bottom
-of the monitor. An error report resembling the one shown below
-is superimposed on the monitor:
-<P>
-<PRE>
-+--------------------------------------------------------------------+
-| error image photo |
-| |
-|# row col photo east north x y |
-|1 0.0 -0.9 1.0 1048.5 -144.8 -105.023 110.122 |
-|2 0.4 1.0 1.3 2153.1 -567.2 107.987 109.834 |
-|3 -1.2 -0.5 0.6 1452.8 -476.5 110.965 -104.329 |
-|4 1.1 0.5 1.3 1034.0 -109.2 -103.932 -110.352 |
-| |
-+--------------------------------------------------------------------+
-| overall rms error: 4.46 |
-+--------------------------------------------------------------------+
-</PRE>
-<P>
- The following menu then appears at the bottom of the monitor:
-<P>
-<PRE>
-+-----+-------+------+-----------------------------------------------+
-|DONE | PRINT | FILE | Double click on point to be included/excluded |
-+-----+-------+------+-----------------------------------------------+
-</PRE>
-</B>
-<P>
-
-The RMS error for the image is given under the column
-TITLEd "error" and subTITLEd "row" and "col". In the above
-report, point number 1 is 0.0 rows and -0.9 columns from
-the predicted location calculated from the transformation
-equation. The RMS error for the photo coordinates is
-listed under the heading "photo". This is the RMS error
-for the x and y coordinates of the photo coordinates but it
-is presented in the table using one general value. The
-overall RMS error is displayed at the bottom of the screen
-in milimeters. Points that create high RMS error are
-displayed in red on the monitor (represented here in
-italics).
-
-
-<P>
-
-The location of the point marked on the imagery group file
-is given under the heading "image" and the subheadings
-"east" and "north". The location of the point in the photo
-coordinates is given under the heading "photo" and the
-subheadings "x" and "y". If you would like to exclude or
-include a point, this can be accomplished by placing the
-mouse cross hairs on the point number to be included (if
-the point is absent) or excluded (if the point is
-displayed) and pressing the left button on the mouse
-twice. When a point is excluded, it is not afterwards
-included in the calculation of the RMS error, or included
-in the final transformation matrix. However, it can be
-retrieved within <EM>photo.2image</EM> at any time by
-double clicking with the mouse as described above.
-
-
-<P>
-
-
-<H2>QUIT</H2>
-
-To end the <EM>photo.2image</EM> program place the mouse cross hairs
-on the word QUIT; the marked reference points (including coordinates)
-will be saved.
-
-
-<P>
-
-
-<H2>NOTES</H2>
-
-A good rule of thumb is to mark at least 4 to 8 points which are
-evenly distributed over the perimeter of the imagery
-group file in order to obtain
-an accurate transformation equation for the rectification process.
-The RMS error may increase with more points added, but the
-transformation equation will be more accurate.
-
-
-<P>
-
-An RMS error of less than or equal to approximately one resolution
-unit (pixel) for the image being rectified is generally considered
-acceptable.
-
-<H2>SEE ALSO</H2>
-
-<EM><A HREF="i.ortho.photo.html">i.ortho.photo</A></EM>,
-<EM><A HREF="photo.camera.html">photo.camera</A></EM>,
-<EM><A HREF="photo.2target.html">photo.2target</A></EM>,
-<EM><A HREF="photo.init.html">photo.init</A></EM>,
-<EM><A HREF="photo.rectify.html">photo.rectify</A></EM>
-
-<H2>AUTHOR</H2>
-
-Mike Baba, DBA Systems, Inc.
-
-<p><i>Last changed: $Date$</i>
-</body>
-</html>
Copied: grass/trunk/imagery/i.ortho.photo/photo.2image/photo.2image.html (from rev 32770, grass/trunk/imagery/i.ortho.photo/photo.2image/description.html)
===================================================================
--- grass/trunk/imagery/i.ortho.photo/photo.2image/photo.2image.html (rev 0)
+++ grass/trunk/imagery/i.ortho.photo/photo.2image/photo.2image.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,377 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<head>
+<title>photo.2image</title>
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
+<link rel="stylesheet" href="grassdocs.css" type="text/css">
+</head>
+<body bgcolor="white">
+
+<img src="grass_logo.png" alt="GRASS logo"><hr align=center size=6 noshade>
+
+<h2>NAME</h2>
+<em><b>photo.2image</b></em>
+
+<H2>DESCRIPTION</H2>
+
+<EM>photo.2image</EM> is an imagery function that enables
+you to mark fiducial or reseau points on an image to be
+ortho-rectified and then computes the image-to-photo
+coordinate transformation parameters. The coordinates of
+the fiducials or reseau marks can be choosen for a camera
+reference file.
+
+<P>
+
+During the process of marking reference points with known
+photo coordinates, you may compute the RMS (root mean
+square) error for each reference point entered.
+<EM>photo.2image</EM> does this by calculating the
+transformation equation (the same one that is calculated by
+<EM><A HREF="i.points.html">i.points</A> </EM>),
+and then plugging these results into an equation for RMS
+error.
+
+
+<P>
+
+<EM>photo.2image</EM> offers a zoom option to locate
+precisely the fiducial or reseau point to be marked on an
+image.
+
+
+<P>
+
+To run <EM>photo.2image</EM>, a graphics monitor is
+required.
+
+<P>
+
+The procedure for marking fiducial or reseau points,
+entering known photo-coordinates, and analyzing the RMS
+error is described below.
+
+
+<P>
+
+The terminal screen displays this message:
+
+
+<P>
+
+<B>use mouse now...</B>
+
+
+<P>
+
+The graphics monitor displays the following screen:
+
+<PRE>
+ +---------------------------+---------------------------------+
+ |imagery | |
+ +---------------------------+---------------------------------+
+ | | |
+ | | |
+ | | |
+ | | |
+ | | |
+ | | |
+ | | |
+ +---------------------------+---------------------------------+
+ | | |
+ | | |
+ | | |
+ | | |
+ | | |
+ | | |
+ | | |
+ +---------------------------+---------------------------------+
+ | | |
+ +---------------------------+---------------------------------+
+</PRE>
+
+<P>
+
+A pop-down menu like that shown below will be superimposed on the
+left half of the screen:
+
+<P>
+<PRE>
+ +------------------------------------------+
+ | Double click on raster map to be plotted |
+ | Double click here to cancel |
+ +------------------------------------------+
+ +----------------+
+ |Mapset imagery |
+ +-------+--------+
+ |gs13.1 | gs21.1 |
+ +-------+--------+
+ |gs14.1 | gs22.2 |
+ +-------+--------+
+</PRE>
+Any single file in the imagery group may be used on which to mark
+points, and you may mark points on more than one file
+in the imagery group to accumulate the suggested minimum number of
+4-8 fiducial or ressue points.
+The imagery file selected is displayed in the upper
+left quadrant of the screen.
+<P>
+
+<H2>CAMERA FILE</H2>
+
+The camera reference file may be viewed by placing the mouse
+cross hairs on the words CAMERA. The camera reference file
+will be displayed in the lower left quadrant of the display:
+
+
+<P>
+<PRE>
+
+|---------------------------------------------------------------|
+|Camera Reference File |
+|---------------------------------------------------------------|
+| CAMERA NAME : camera name |
+| CAMERA ID : L1234 |
+| CAMERA CFL : 153.021 mm. |
+| CAMERA XP : 0.050 mm. |
+| CAMERA XP : 0.056 mm. |
+| number of fid. 4 |
+|---------------------------------------------------------------|
+| |
+|ID (X PHOTO) mm. (Y PHOTO) mm. |
+|_______________________________________________________________|
+|1 -105.023 110.123 |
+|2 107.987 109.834 |
+|3 110.965 -104.329 |
+|4 -103.932 -110.352 |
+|_______________________________________________________________|
+</PRE>
+<P>
+The following menu is displayed at the bottom
+of the graphics display:
+<P>
+<B>
+<PRE>
++-----+------+-----------+--------+---------+-------------------+-------------+
+|Quit | Zoom | Plot Cell | Camera | Analyze | Input->KEYBOARD | CAMERA FILE |
++-----+------+-----------+--------+---------+-------------------+-------------+
+</PRE>
+</B>
+<P>
+<H2>ZOOM</H2>
+
+To magnify the displayed file, you must
+place the mouse cross hairs on the word ZOOM. The following menu
+will then be displayed at the bottom of the screen:
+<P>
+<B>
+<PRE>
++-------+-----+-------++--------------------+
+|Cancel | Box | Point ||Select type of ZOOM |
++-------+-----+-------++--------------------+
+</PRE>
+</B>
+<P>
+You have the option of identifying the zoom window either by using
+the mouse to make a box, or by using the mouse to mark the center
+of the desired window, and adjusting the magnification factor.
+The terminal screen will display a mouse button menu to guide you in
+identifying the window. The section of the image within the zoom window
+will be displayed in the upper right hand quadrant.
+<P>
+<H2>MARKING REFERENCE POINTS</H2>
+
+To mark the known reference points (fiducial marks, reseau marks, etc.)
+on the image, you must place the mouse cross hairs
+on the corresponding location on the image to be marked and press
+the left hand button on the mouse. A diamond shaped symbol will be marked
+on the image.
+<P>
+If you wish to use the camera reference file only as a
+comparative reference, then the keyboard can be chosen as
+the means to input photo coordinates corresponding to the marked
+reference points on the image. This is done by placing the mouse
+cross hairs on the word KEYBOARD and pressing the left
+button on the mouse.
+<P>
+The following menu is displayed on the graphics terminal:
+<P>
+<PRE>
++------------------------------------+--------------------------+
+|Point 1 marked at IMAGE COORDINATES | |
+|east: 1023.77 | |
+|north: 506.56 | |
+| | |
+| | |
+| | |
+| | |
+| | |
++------------------------------------+--------------------------+
+|Enter PHOTO COORDINATES as x and y: |
++---------------------------------------------------------------+
+</PRE>
+</B>
+<P>
+You then enter the known (x,y) photo coordinates, relative
+to the perspective center, for the reference
+point marked on the image. If you
+do not wish to enter a coordinate, simply hit RETURN to continue;
+the marked reference point will disappear.
+<P>
+If you select the CAMERA FILE option, then reference points
+marked on the image will be associated with selected photo
+coordinates from the displayed camera reference file. In this option,
+when you mark a point on the image, the following menu is
+displayed on the graphics terminal:
+<P>
+<PRE>
+-------------------------------------------------------------
+CANCEL Double click on the fiducial mark to be referenced
+-------------------------------------------------------------
+</PRE>
+<P>
+
+If you would like to select the photo coordinates of a displayed
+reference mark, this can be accomplished by placing the mouse
+cross hairs on the reference point to be selected and pressing
+the left button on the mouse twice. After a reference point is selected
+from the display, you are prompted with "Look ok? (Y/N)".
+If you respond with no, the reference point is ignored.
+If you respond with yes, the following is displayed on the terminal:
+<P>
+<P>
+<PRE>
++----------------------------------------+--------------------------+
+|Point 1 marked at IMAGE COORDINATES | |
+|east: 1023.77 | |
+|north: 1065.41 | |
+| | |
+| | |
+|Point 1 referenced at PHOTO COORDINATES | |
+|X: -105.023 | |
+|Y: 110.122 | |
+| | |
+| | |
+| | |
+| | |
+| | |
++----------------------------------------+--------------------------+
+| use mouse now... |
++----------------------------------------+--------------------------+
+</PRE>
+</B>
+<P>
+The photo coordinates and the corresponding image coordinates are
+automatically saved in the photo_points file associated with the imagery
+group.
+<P>
+<P>
+<H2>ANALYZE</H2>
+
+After a number of points have been marked (4 to 8), you can
+check the RMS error of the points marked on the image. This is done
+by placing the mouse cross hairs on the word ANALYZE at the bottom
+of the monitor. An error report resembling the one shown below
+is superimposed on the monitor:
+<P>
+<PRE>
++--------------------------------------------------------------------+
+| error image photo |
+| |
+|# row col photo east north x y |
+|1 0.0 -0.9 1.0 1048.5 -144.8 -105.023 110.122 |
+|2 0.4 1.0 1.3 2153.1 -567.2 107.987 109.834 |
+|3 -1.2 -0.5 0.6 1452.8 -476.5 110.965 -104.329 |
+|4 1.1 0.5 1.3 1034.0 -109.2 -103.932 -110.352 |
+| |
++--------------------------------------------------------------------+
+| overall rms error: 4.46 |
++--------------------------------------------------------------------+
+</PRE>
+<P>
+ The following menu then appears at the bottom of the monitor:
+<P>
+<PRE>
++-----+-------+------+-----------------------------------------------+
+|DONE | PRINT | FILE | Double click on point to be included/excluded |
++-----+-------+------+-----------------------------------------------+
+</PRE>
+</B>
+<P>
+
+The RMS error for the image is given under the column
+TITLEd "error" and subTITLEd "row" and "col". In the above
+report, point number 1 is 0.0 rows and -0.9 columns from
+the predicted location calculated from the transformation
+equation. The RMS error for the photo coordinates is
+listed under the heading "photo". This is the RMS error
+for the x and y coordinates of the photo coordinates but it
+is presented in the table using one general value. The
+overall RMS error is displayed at the bottom of the screen
+in milimeters. Points that create high RMS error are
+displayed in red on the monitor (represented here in
+italics).
+
+
+<P>
+
+The location of the point marked on the imagery group file
+is given under the heading "image" and the subheadings
+"east" and "north". The location of the point in the photo
+coordinates is given under the heading "photo" and the
+subheadings "x" and "y". If you would like to exclude or
+include a point, this can be accomplished by placing the
+mouse cross hairs on the point number to be included (if
+the point is absent) or excluded (if the point is
+displayed) and pressing the left button on the mouse
+twice. When a point is excluded, it is not afterwards
+included in the calculation of the RMS error, or included
+in the final transformation matrix. However, it can be
+retrieved within <EM>photo.2image</EM> at any time by
+double clicking with the mouse as described above.
+
+
+<P>
+
+
+<H2>QUIT</H2>
+
+To end the <EM>photo.2image</EM> program place the mouse cross hairs
+on the word QUIT; the marked reference points (including coordinates)
+will be saved.
+
+
+<P>
+
+
+<H2>NOTES</H2>
+
+A good rule of thumb is to mark at least 4 to 8 points which are
+evenly distributed over the perimeter of the imagery
+group file in order to obtain
+an accurate transformation equation for the rectification process.
+The RMS error may increase with more points added, but the
+transformation equation will be more accurate.
+
+
+<P>
+
+An RMS error of less than or equal to approximately one resolution
+unit (pixel) for the image being rectified is generally considered
+acceptable.
+
+<H2>SEE ALSO</H2>
+
+<EM><A HREF="i.ortho.photo.html">i.ortho.photo</A></EM>,
+<EM><A HREF="photo.camera.html">photo.camera</A></EM>,
+<EM><A HREF="photo.2target.html">photo.2target</A></EM>,
+<EM><A HREF="photo.init.html">photo.init</A></EM>,
+<EM><A HREF="photo.rectify.html">photo.rectify</A></EM>
+
+<H2>AUTHOR</H2>
+
+Mike Baba, DBA Systems, Inc.
+
+<p><i>Last changed: $Date$</i>
+</body>
+</html>
Modified: grass/trunk/imagery/i.ortho.photo/photo.2target/Makefile
===================================================================
--- grass/trunk/imagery/i.ortho.photo/photo.2target/Makefile 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/imagery/i.ortho.photo/photo.2target/Makefile 2008-08-15 06:16:42 UTC (rev 32772)
@@ -10,6 +10,3 @@
include $(MODULE_TOPDIR)/include/Make/Module.make
default: etc
-
-$(PGM).tmp.html: $(ETC)/$(PGM)$(EXE)
- $(call htmldesc,$(ETC)/$(PGM)$(EXE))
Deleted: grass/trunk/imagery/i.ortho.photo/photo.2target/description.html
===================================================================
--- grass/trunk/imagery/i.ortho.photo/photo.2target/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/imagery/i.ortho.photo/photo.2target/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,383 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-<EM>photo.2target</EM>
-is an imagery function that enables you to
-mark control points on an image to be ortho-rectified
-and then input the coordinates of each point for calculation
-of rectification parameters.
-
-Rectification is the mapping of an image from one coordinate
-system to another. The geometry of an image extracted into
-a GRASS LOCATION having an x,y coordinate system is not
-planimetric. To create a planimetric image, that is, to
-convert the x,y coordinate system into a standard coordinate
-system (for example, the UTM coordinate system or the State
-Plane coordinate system), points from a map having the
-standard coordinates must be associated with the same points
-on the image to be rectified.
-
-The ortho-rectification parameters are computed in two
-phases. The first phase computes a transformation matrix between image
-(row,col) coordinates and photo (x,y) coordinates relative to the
-perspective center. The transformation matrix is computed
-explicitly in the option <EM>
-<A HREF="photo.2image.html">photo.2image</A>
-</EM>.
-
-The second phase, <EM>photo.2target</EM>, enables you
-to mark control points on the image
-and then input the standard coordinates
-(Easting,Northing, and elevation) to determine the
-parameters for a three dimensional projective transformation.
-
-<EM>
-<A HREF="photo.init.html">photo.init</A>
-</EM> may be run before
-running <EM>photo.2target</EM>
-to modify the initial camera exposure station parameters, and/or
-modify the standard deviation of these parameters.
-<EM>
-<A HREF="photo.init.html">photo.init</A>
-</EM> is not required but generally is helpful.
-
-
-<P>
-
-During the process of marking control points and entering standard
-coordinates, you may compute the RMS (root mean square)
-error for each control point entered. photo.2target does this by
-calculating the transformation equation, and then
-plugging these results into an equation for RMS error.
-
-
-<P>
-
-<EM>photo.2target</EM> offers a zoom option to locate precisely the point
-to be marked on an image. This program also offers you the option
-of acquiring standard coordinates for a marked point from a map
-layer in the target database, or from a digitizer.
-
-
-<P>
-
-To run <EM>photo.2target</EM>, a graphics monitor is required.
-
-
-<P>
-
-The procedure for marking points, entering coordinates, and calculating RMS
-error is described below.
-
-
-<P>
-
-The terminal screen displays the following message:
-
-
-<P>
-<B>use mouse now...</B>
-<P>
-The graphics monitor displays the following screen:
-<P>
-<PRE>
-+-----------------------------+--------------------------------+
-|imagery filename (mag) | target filename (mag) |
-+-----------------------------+--------------------------------+
-| | |
-| | |
-| | |
-| | |
-| | |
-| | |
-| | |
-+-----------------------------+--------------------------------+
-| | |
-| | |
-| | |
-| | |
-| | |
-| | |
-+-----------------------------+--------------------------------+
-|QUIT ZOOM PLOTCELL ANALYZE | |
-+-----------------------------+--------------------------------+
-</PRE>
-<P>
-A pop-down menu like that shown below will be superimposed on the
-left half of the screen:
-<P>
-<PRE>
- +------------------------------------------+
- | Double click on raster map to be plotted |
- | Double click here to cancel |
- +------------------------------------------+
- +--------------------+
- | Mapset PERMANENT |
- +---------+----------+
- |gs13.1 | gs14.1 |
- +---------+----------+
- |gs21.1 | gs22.2 |
- +---------+----------+
-
-</PRE>
-<P>
-Any single file in the imagery group may be used to mark
-points, and you can mark points on more than one file
-in the imagery group to accumulate the 12 points suggested minimum.
-Any file in the imagery group can be rectified (using
-<EM>
-<A HREF="photo.rectify.html">photo.rectify</A>
-</EM>) based on the rectification parameters
-computed from these control points.
-<P>
-The imagery file you select is displayed in the upper
-left quadrant of the screen.
-
-<H2>ZOOM</H2>
-
-To magnify the displayed file, you must
-place the mouse cross hairs on the word ZOOM. The following menu
-will then be displayed at the bottom of the screen:
-<P>
-<PRE>
-
- +-------+-----+-------++--------------------+
- |Cancel | Box | Point ||Select type of ZOOM |
- +-------+-----+-------++--------------------+
-</PRE>
-<P>
-You may identifying the zoom window either by using
-the mouse to make a box, or by using the mouse to mark the center of
-the window and entering a magnification factor.
-The terminal screen will display a mouse button menu to guide you in
-identifying the window.
-<P>
-It is also possible to start zoom by box with middle mouse button
-and pan by right mouse button.
-<P>
-<H2>MARKING POINTS</H2>
-To mark the points on the image that correspond to the points on a
-standard coordinate system map, you must place the mouse
-cross hairs on the corresponding location on the image to be marked
-and press the
-left hand button on the mouse. A diamond shaped symbol will be
-marked on the image. The terminal will display the following
-menu:
-<P>
-<PRE>
- +------------------------------------+--------------------------+
- |Point 1 marked at IMAGE COORDINATES | |
- |IMAGE X: 1023.77 | |
- |IMAGE Y: -164.41 | |
- | | |
- +------------------------------------+--------------------------+
- |Enter CONTROL COORDINATES as east,north,elevation: |
- +---------------------------------------------------------------+
-</PRE>
-<P>
-You then enter the easting, northing, and elevation for the point
-marked on the image. If you wish not to enter a
-coordinate, simply hit RETURN to return control
-to the mouse; the marked point then disappears.
-<P>
-Entered point can be canceled by right mouse button click.
-<P>
-<H2>PLOT CELL</H2>
-
-In addition to acquiring control points from a standard map,
-you have the option of acquiring the points from
-a cell-map in the target database. The database map is displayed by
-placing the mouse cross hairs on the words PLOT CELL. The
-following line is then displayed at the bottom of the monitor:
-<P>
-<PRE>
- +-------+---------------------------------------+
- |Cancel | Indicate which side should be plotted |
- +-------+---------------------------------------+
-</PRE>
-<P>
-Which side of the monitor is to be plotted
-is indicated by placing the mouse cross hairs on the
-half of the monitor screen that you would like to use,
-and pressing the left mouse button. The following pop-down
-menu will be superimposed on the half of the screen that was
-chosen:
-<P>
-<PRE>
- +------------------------------------------+
- | Double click on raster map to be plotted |
- | Double click here to cancel |
- +------------------------------------------+
-</PRE>
-<PRE>
- +-----------------------------+
- | Mapset user1 |
- +--------------+--------------+
- |tm.rectified | |
- +--------------+--------------+
- |tm.classified | |
- +--------------+--------------+
- | Mapset PERMANENT |
- +--------------+--------------+
- |elevation | geology |
- +--------------+--------------+
- |slope | soils |
- +--------------+--------------+
- |aspect | |
- +--------------+--------------+
- |roads | |
- +--------------+--------------+
- |streams | |
- +--------------+--------------+
- |airfields | |
- +--------------+--------------+
-</PRE>
-<P>
-After the map is displayed the following message appears at
-the bottom of the monitor:
-<P>
-<PRE>
- +-----------------+----------+--------+
- |input method -> | keyboard | screen |
- +-----------------+----------+--------+
-</PRE>
-<P>
-If you wish to use the plotted map only as a
-comparative reference, the keyboard can be chosen as
-the means to input coordinates corresponding to the marked
-control points. This is done by placing the mouse
-cross hairs on the word KEYBOARD and pressing the left
-button on the mouse.
-<P>
-If you select the SCREEN option, points marked on
-the image will automatically be associated with the
-coordinates from the corresponding points on the target
-database map, and a corresponding elevation from the cell-file
-selected for elevation data. In this option, when you mark a point
-on the image, the following menu is displayed on the
-terminal:
-<P>
-<PRE>
- +------------------------------------+--------------------------+
- |Point 5 marked at IMAGE COORDINATES | |
- |IMAGE X: 1023.77 | |
- |IMAGE Y: -164.41 | |
- | | |
- | | |
- |Control Point location | |
- |East: 679132.57 | |
- |North: 4351080.67 | |
- |Elevation: 1010.00 | |
- | | |
- | | |
- | | |
- +------------------------------------+--------------------------+
- |use mouse now... |
- +---------------------------------------------------------------+
-</PRE>
-<P>
-The coordinates for the target database map are automatically saved
-as the coordinates corresponding to the marked control point on the image.
-
-<H2>ANALYZE</H2>
-
-After a number of points have been marked (4 to 7), you can
-check the RMS error of the points marked on the image. This is done
-by placing the mouse cross hairs on the word ANALYZE at the bottom
-of the monitor. An error report resembling that shown below
-is superimposed on the monitor:
-<P>
-<PRE>
-+--------------------------------------------------------------------------+
-| error |
-|# east north target east north east north elev. |
-+--------------------------------------------------------------------------+
-|1 0.0 -0.9 1.0 48.5 4.8 79132.5 351080.6 10.0 |
-|2 0.4 1.0 1.3 53.1 7.2 84314.7 399001.4 239.3 |
-|3 -1.2 -0.5 0.6 52.8 6.5 67841.4 457682.8 209.5 |
-|4 1.1 0.5 1.3 34.0 9.2 77573.8 352626.4 432.5 |
-|5 -2.7 14.0 14.2 48.6 -144.9 79132.6 351080.7 985.0 |
-| |
-+--------------------------------------------------------------------------+
-| overall rms error: 4.46 |
-+--------------------------------------------------------------------------+
-</PRE>
-<P>
- The following menu then appears at the bottom of the monitor:
-<P>
-<PRE>
- +-----+------------+------------------------------------------------+
- |DONE | PRINT FILE | Double click on point to be included/excluded |
- +-----+------------+------------------------------------------------+
-</PRE>
-<P>
-The RMS error for the image is given under the column TITLEd "error"
-and subTITLEd "east" and "north". In the above report, point number 1
-is 0.0 and -0.9 meters (east and north)
-from the predicted location calculated from
-the transformation equation.
-The RMS error for the target map is listed under the heading "target".
-This is the RMS error for the east and north coordinates of the
-target map but it is presented in the table using one general value.
-The overall RMS error is displayed at the bottom of the screen in meters.
-Points that create high RMS error are displayed in red on the monitor
-(represented here in italics).
-<P>
-The image coordinates of the point marked on the
-imagery group file is given under the heading "image" and the
-subheadings "east" and "north". The location of the control point in the
-target database is given under the heading "control" and the
-subheadings "east","north", and "elev". If you would like to
-exclude or include a control point, this can be accomplished by placing
-the mouse cross hairs on the control point number to be included (if the
-point is absent) or excluded (if the point is displayed) and
-pressing the left button on the mouse twice.
-When a point is excluded, it is not afterwards included in the calculation
-of the RMS error, or included in the final rectification parameters.
-However, it can be retrieved within <EM>photo.2target</EM> at any time
-by double clicking with the mouse as described above.
-
-<H2>QUIT</H2>
-
-To end the <EM>photo.2target</EM> program place the mouse cross hairs
-on the word QUIT; the marked control points (including coordinates)
-will be saved.
-
-<H2>NOTES</H2>
-
-During the course of marking control points and computing
-the ortho-rectification parameters, a matrix inversion error may occur.
-This is caused by trying to invert a non-singular normal equation matrix.
-When this situation
-arises, the status of all previously selected control points are modified,
-the control points are excluded. Running
-<EM>
-<A HREF="photo.init.html">photo.init</A>
-</EM> for the selected imagery group with accurate
-camera exposure station parameters should remedy the situation.
-The excluded control points may again be included as described in the section
-ANALYZE.
-<P>
-<P>
-A good rule of thumb is to mark at least 12 to 15 points which are
-evenly distributed over the entire imagery group file in order to obtain
-an accurate transformation parameters for the rectification process.
-The RMS error may increase with more points added, but the
-transformation parameters will be more accurate over the entire image.
-<P>
-An RMS error of less than or equal to approximately one resolution
-unit (pixel) for the image being rectified is generally considered
-acceptable.
-
-<H2>SEE ALSO</H2>
-
-<EM><A HREF="i.ortho.photo.html">i.ortho.photo</A></EM>,
-<EM><A HREF="photo.camera.html">photo.camera</A></EM>,
-<EM><A HREF="photo.2image.html">photo.2image</A></EM>,
-<EM><A HREF="photo.init.html">photo.init</A></EM>,
-<EM><A HREF="photo.rectify.html">photo.rectify</A></EM>
-
-<H2>AUTHOR</H2>
-
-Mike Baba, DBA Systems, Inc.
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/imagery/i.ortho.photo/photo.2target/photo.2target.html (from rev 32770, grass/trunk/imagery/i.ortho.photo/photo.2target/description.html)
===================================================================
--- grass/trunk/imagery/i.ortho.photo/photo.2target/photo.2target.html (rev 0)
+++ grass/trunk/imagery/i.ortho.photo/photo.2target/photo.2target.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,383 @@
+<H2>DESCRIPTION</H2>
+
+<EM>photo.2target</EM>
+is an imagery function that enables you to
+mark control points on an image to be ortho-rectified
+and then input the coordinates of each point for calculation
+of rectification parameters.
+
+Rectification is the mapping of an image from one coordinate
+system to another. The geometry of an image extracted into
+a GRASS LOCATION having an x,y coordinate system is not
+planimetric. To create a planimetric image, that is, to
+convert the x,y coordinate system into a standard coordinate
+system (for example, the UTM coordinate system or the State
+Plane coordinate system), points from a map having the
+standard coordinates must be associated with the same points
+on the image to be rectified.
+
+The ortho-rectification parameters are computed in two
+phases. The first phase computes a transformation matrix between image
+(row,col) coordinates and photo (x,y) coordinates relative to the
+perspective center. The transformation matrix is computed
+explicitly in the option <EM>
+<A HREF="photo.2image.html">photo.2image</A>
+</EM>.
+
+The second phase, <EM>photo.2target</EM>, enables you
+to mark control points on the image
+and then input the standard coordinates
+(Easting,Northing, and elevation) to determine the
+parameters for a three dimensional projective transformation.
+
+<EM>
+<A HREF="photo.init.html">photo.init</A>
+</EM> may be run before
+running <EM>photo.2target</EM>
+to modify the initial camera exposure station parameters, and/or
+modify the standard deviation of these parameters.
+<EM>
+<A HREF="photo.init.html">photo.init</A>
+</EM> is not required but generally is helpful.
+
+
+<P>
+
+During the process of marking control points and entering standard
+coordinates, you may compute the RMS (root mean square)
+error for each control point entered. photo.2target does this by
+calculating the transformation equation, and then
+plugging these results into an equation for RMS error.
+
+
+<P>
+
+<EM>photo.2target</EM> offers a zoom option to locate precisely the point
+to be marked on an image. This program also offers you the option
+of acquiring standard coordinates for a marked point from a map
+layer in the target database, or from a digitizer.
+
+
+<P>
+
+To run <EM>photo.2target</EM>, a graphics monitor is required.
+
+
+<P>
+
+The procedure for marking points, entering coordinates, and calculating RMS
+error is described below.
+
+
+<P>
+
+The terminal screen displays the following message:
+
+
+<P>
+<B>use mouse now...</B>
+<P>
+The graphics monitor displays the following screen:
+<P>
+<PRE>
++-----------------------------+--------------------------------+
+|imagery filename (mag) | target filename (mag) |
++-----------------------------+--------------------------------+
+| | |
+| | |
+| | |
+| | |
+| | |
+| | |
+| | |
++-----------------------------+--------------------------------+
+| | |
+| | |
+| | |
+| | |
+| | |
+| | |
++-----------------------------+--------------------------------+
+|QUIT ZOOM PLOTCELL ANALYZE | |
++-----------------------------+--------------------------------+
+</PRE>
+<P>
+A pop-down menu like that shown below will be superimposed on the
+left half of the screen:
+<P>
+<PRE>
+ +------------------------------------------+
+ | Double click on raster map to be plotted |
+ | Double click here to cancel |
+ +------------------------------------------+
+ +--------------------+
+ | Mapset PERMANENT |
+ +---------+----------+
+ |gs13.1 | gs14.1 |
+ +---------+----------+
+ |gs21.1 | gs22.2 |
+ +---------+----------+
+
+</PRE>
+<P>
+Any single file in the imagery group may be used to mark
+points, and you can mark points on more than one file
+in the imagery group to accumulate the 12 points suggested minimum.
+Any file in the imagery group can be rectified (using
+<EM>
+<A HREF="photo.rectify.html">photo.rectify</A>
+</EM>) based on the rectification parameters
+computed from these control points.
+<P>
+The imagery file you select is displayed in the upper
+left quadrant of the screen.
+
+<H2>ZOOM</H2>
+
+To magnify the displayed file, you must
+place the mouse cross hairs on the word ZOOM. The following menu
+will then be displayed at the bottom of the screen:
+<P>
+<PRE>
+
+ +-------+-----+-------++--------------------+
+ |Cancel | Box | Point ||Select type of ZOOM |
+ +-------+-----+-------++--------------------+
+</PRE>
+<P>
+You may identifying the zoom window either by using
+the mouse to make a box, or by using the mouse to mark the center of
+the window and entering a magnification factor.
+The terminal screen will display a mouse button menu to guide you in
+identifying the window.
+<P>
+It is also possible to start zoom by box with middle mouse button
+and pan by right mouse button.
+<P>
+<H2>MARKING POINTS</H2>
+To mark the points on the image that correspond to the points on a
+standard coordinate system map, you must place the mouse
+cross hairs on the corresponding location on the image to be marked
+and press the
+left hand button on the mouse. A diamond shaped symbol will be
+marked on the image. The terminal will display the following
+menu:
+<P>
+<PRE>
+ +------------------------------------+--------------------------+
+ |Point 1 marked at IMAGE COORDINATES | |
+ |IMAGE X: 1023.77 | |
+ |IMAGE Y: -164.41 | |
+ | | |
+ +------------------------------------+--------------------------+
+ |Enter CONTROL COORDINATES as east,north,elevation: |
+ +---------------------------------------------------------------+
+</PRE>
+<P>
+You then enter the easting, northing, and elevation for the point
+marked on the image. If you wish not to enter a
+coordinate, simply hit RETURN to return control
+to the mouse; the marked point then disappears.
+<P>
+Entered point can be canceled by right mouse button click.
+<P>
+<H2>PLOT CELL</H2>
+
+In addition to acquiring control points from a standard map,
+you have the option of acquiring the points from
+a cell-map in the target database. The database map is displayed by
+placing the mouse cross hairs on the words PLOT CELL. The
+following line is then displayed at the bottom of the monitor:
+<P>
+<PRE>
+ +-------+---------------------------------------+
+ |Cancel | Indicate which side should be plotted |
+ +-------+---------------------------------------+
+</PRE>
+<P>
+Which side of the monitor is to be plotted
+is indicated by placing the mouse cross hairs on the
+half of the monitor screen that you would like to use,
+and pressing the left mouse button. The following pop-down
+menu will be superimposed on the half of the screen that was
+chosen:
+<P>
+<PRE>
+ +------------------------------------------+
+ | Double click on raster map to be plotted |
+ | Double click here to cancel |
+ +------------------------------------------+
+</PRE>
+<PRE>
+ +-----------------------------+
+ | Mapset user1 |
+ +--------------+--------------+
+ |tm.rectified | |
+ +--------------+--------------+
+ |tm.classified | |
+ +--------------+--------------+
+ | Mapset PERMANENT |
+ +--------------+--------------+
+ |elevation | geology |
+ +--------------+--------------+
+ |slope | soils |
+ +--------------+--------------+
+ |aspect | |
+ +--------------+--------------+
+ |roads | |
+ +--------------+--------------+
+ |streams | |
+ +--------------+--------------+
+ |airfields | |
+ +--------------+--------------+
+</PRE>
+<P>
+After the map is displayed the following message appears at
+the bottom of the monitor:
+<P>
+<PRE>
+ +-----------------+----------+--------+
+ |input method -> | keyboard | screen |
+ +-----------------+----------+--------+
+</PRE>
+<P>
+If you wish to use the plotted map only as a
+comparative reference, the keyboard can be chosen as
+the means to input coordinates corresponding to the marked
+control points. This is done by placing the mouse
+cross hairs on the word KEYBOARD and pressing the left
+button on the mouse.
+<P>
+If you select the SCREEN option, points marked on
+the image will automatically be associated with the
+coordinates from the corresponding points on the target
+database map, and a corresponding elevation from the cell-file
+selected for elevation data. In this option, when you mark a point
+on the image, the following menu is displayed on the
+terminal:
+<P>
+<PRE>
+ +------------------------------------+--------------------------+
+ |Point 5 marked at IMAGE COORDINATES | |
+ |IMAGE X: 1023.77 | |
+ |IMAGE Y: -164.41 | |
+ | | |
+ | | |
+ |Control Point location | |
+ |East: 679132.57 | |
+ |North: 4351080.67 | |
+ |Elevation: 1010.00 | |
+ | | |
+ | | |
+ | | |
+ +------------------------------------+--------------------------+
+ |use mouse now... |
+ +---------------------------------------------------------------+
+</PRE>
+<P>
+The coordinates for the target database map are automatically saved
+as the coordinates corresponding to the marked control point on the image.
+
+<H2>ANALYZE</H2>
+
+After a number of points have been marked (4 to 7), you can
+check the RMS error of the points marked on the image. This is done
+by placing the mouse cross hairs on the word ANALYZE at the bottom
+of the monitor. An error report resembling that shown below
+is superimposed on the monitor:
+<P>
+<PRE>
++--------------------------------------------------------------------------+
+| error |
+|# east north target east north east north elev. |
++--------------------------------------------------------------------------+
+|1 0.0 -0.9 1.0 48.5 4.8 79132.5 351080.6 10.0 |
+|2 0.4 1.0 1.3 53.1 7.2 84314.7 399001.4 239.3 |
+|3 -1.2 -0.5 0.6 52.8 6.5 67841.4 457682.8 209.5 |
+|4 1.1 0.5 1.3 34.0 9.2 77573.8 352626.4 432.5 |
+|5 -2.7 14.0 14.2 48.6 -144.9 79132.6 351080.7 985.0 |
+| |
++--------------------------------------------------------------------------+
+| overall rms error: 4.46 |
++--------------------------------------------------------------------------+
+</PRE>
+<P>
+ The following menu then appears at the bottom of the monitor:
+<P>
+<PRE>
+ +-----+------------+------------------------------------------------+
+ |DONE | PRINT FILE | Double click on point to be included/excluded |
+ +-----+------------+------------------------------------------------+
+</PRE>
+<P>
+The RMS error for the image is given under the column TITLEd "error"
+and subTITLEd "east" and "north". In the above report, point number 1
+is 0.0 and -0.9 meters (east and north)
+from the predicted location calculated from
+the transformation equation.
+The RMS error for the target map is listed under the heading "target".
+This is the RMS error for the east and north coordinates of the
+target map but it is presented in the table using one general value.
+The overall RMS error is displayed at the bottom of the screen in meters.
+Points that create high RMS error are displayed in red on the monitor
+(represented here in italics).
+<P>
+The image coordinates of the point marked on the
+imagery group file is given under the heading "image" and the
+subheadings "east" and "north". The location of the control point in the
+target database is given under the heading "control" and the
+subheadings "east","north", and "elev". If you would like to
+exclude or include a control point, this can be accomplished by placing
+the mouse cross hairs on the control point number to be included (if the
+point is absent) or excluded (if the point is displayed) and
+pressing the left button on the mouse twice.
+When a point is excluded, it is not afterwards included in the calculation
+of the RMS error, or included in the final rectification parameters.
+However, it can be retrieved within <EM>photo.2target</EM> at any time
+by double clicking with the mouse as described above.
+
+<H2>QUIT</H2>
+
+To end the <EM>photo.2target</EM> program place the mouse cross hairs
+on the word QUIT; the marked control points (including coordinates)
+will be saved.
+
+<H2>NOTES</H2>
+
+During the course of marking control points and computing
+the ortho-rectification parameters, a matrix inversion error may occur.
+This is caused by trying to invert a non-singular normal equation matrix.
+When this situation
+arises, the status of all previously selected control points are modified,
+the control points are excluded. Running
+<EM>
+<A HREF="photo.init.html">photo.init</A>
+</EM> for the selected imagery group with accurate
+camera exposure station parameters should remedy the situation.
+The excluded control points may again be included as described in the section
+ANALYZE.
+<P>
+<P>
+A good rule of thumb is to mark at least 12 to 15 points which are
+evenly distributed over the entire imagery group file in order to obtain
+an accurate transformation parameters for the rectification process.
+The RMS error may increase with more points added, but the
+transformation parameters will be more accurate over the entire image.
+<P>
+An RMS error of less than or equal to approximately one resolution
+unit (pixel) for the image being rectified is generally considered
+acceptable.
+
+<H2>SEE ALSO</H2>
+
+<EM><A HREF="i.ortho.photo.html">i.ortho.photo</A></EM>,
+<EM><A HREF="photo.camera.html">photo.camera</A></EM>,
+<EM><A HREF="photo.2image.html">photo.2image</A></EM>,
+<EM><A HREF="photo.init.html">photo.init</A></EM>,
+<EM><A HREF="photo.rectify.html">photo.rectify</A></EM>
+
+<H2>AUTHOR</H2>
+
+Mike Baba, DBA Systems, Inc.
+
+<p><i>Last changed: $Date$</i>
Modified: grass/trunk/imagery/i.ortho.photo/photo.camera/Makefile
===================================================================
--- grass/trunk/imagery/i.ortho.photo/photo.camera/Makefile 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/imagery/i.ortho.photo/photo.camera/Makefile 2008-08-15 06:16:42 UTC (rev 32772)
@@ -11,7 +11,5 @@
default: etc
-htmletc:
- $(MKDIR) $(GISBASE)/docs/html
- $(INSTALL_DATA) description.html $(GISBASE)/docs/html/$(PGM).html
- $(INSTALL_DATA) *.png $(GISBASE)/docs/html/
+$(PGM).tmp.html: $(PGM).html
+ $(INSTALL_DATA) $< $@
Deleted: grass/trunk/imagery/i.ortho.photo/photo.camera/description.html
===================================================================
--- grass/trunk/imagery/i.ortho.photo/photo.camera/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/imagery/i.ortho.photo/photo.camera/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,126 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-<head>
-<title></title>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link rel="stylesheet" href="grassdocs.css" type="text/css">
-</head>
-<body bgcolor="white">
-
-<img src="grass_logo.png" alt="GRASS logo"><hr align=center size=6 noshade>
-
-<h2>NAME</h2>
-<em><b></b></em>
-
-<H2>DESCRIPTION</H2>
-
-<EM>photo.camera</EM> creates or modifies entries in a camera reference
-file. For ortho-photo rectification, a camera reference file is required for
-computation of scanned image to photo-coordinate transformation parameters.
-There are two coordinate systems: The image coordinate system (in pixels)
-and the photo coordinate system (in milli-meters). The inner orientation
-establishes a relation between the pixels and the image coordinates with
-help of fiducial marks.
-
-<P>
-
-The first prompt in the program will ask you for the name of
-the camera reference file to be created or modified. You may
-create a new camera reference file by entering a new name, or modify an
-existing camera reference file by entering the name of an existing camera file.
-
-<P>
-After entering the camera file name, following menu is displayed:
-<P>
-Please provide the following information
-
-
-<P>
-<PRE>
-
- CAMERA NAME: <EM>camera name</EM>______
- CAMERA IDENTIFICATION: <EM>identification</EM>___
- CALIBRATED FOCAL LENGTH mm.:_________________
- POINT OF SYMMETRY (X) mm.:_________________
- POINT OF SYMMETRY (Y) mm.:_________________
- MAXIMUM NUMBER OF FIDUCIALS:_________________
-
- AFTER COMPLETING ALL ANSWERS, HIT <ESC> TO CONTINUE
- (OR <Ctrl-C> TO CANCEL)
-</PRE>
-
-The camera name and identification describe the camera reference file.
-The calibrated focal length and the point of symmetry are used in computing
-the photo-to-target transformation parameters. These values should be entered
-from the camera calibration report (usually available from the photograph
-supplier).
-
-<p>
-<img src="photo.camera.png" alt="Sketch of aerial photo"><br>
-<i>This example is the camera Zeiss LMK9 265-002A belonging to the Hellenic
-Military Geographical Survey (HMGS) and calibrated in December 1985</i>
-<p>
-
-The photo coordinate system origin is the so-called calibrated principal
-point (PP, Principal Point of Symmetry) which is in the center of the image.
-The origin of the axes is at the intersection of the radii traced from the
-fiducial marks. In the ideal case of no deviations in the camera (see camera
-calibration certificate) the center is the origin and the values are 0 for
-both X and Y of Point of Symmetry. But usually the principal point does not
-fall on the intersection of the radii at the center of the picture. This
-excentricity is usually of the order of a few micrometers. <P>
-
-You are then asked to enter the X and Y photo coordinates of each fiducial
-as follows.
-These fiducials (or reseau) marks are index marks imaged on film which serve
-as reference photo coordinate system. The maximum number of fiducials will
-determine the number of fiducial or reseau coordinate pairs to be entered
-below. The origin is the center of the image (or the point of symmetry) and
-X and Y are left-right and up-down. The order is up to the user, but must be
-kept consistent throughout the rectification process.
-<P>
-
-On this screen you should enter the fiducial or
-reseau photo-coordinates as given in the camera calibration report. The X,
-and Y coordinates are in milli-meters from the principle point.
-
-<P>
-Please provide the following information
-<PRE>
- Fid# FID ID X Y
-
- 1__ _____ 0.0___ 0.0___
- 2__ _____ 0.0___ 0.0___
- 3__ _____ 0.0___ 0.0___
- 4__ _____ 0.0___ 0.0___
- 5__ _____ 0.0___ 0.0___
- 6__ _____ 0.0___ 0.0___
- 7__ _____ 0.0___ 0.0___
- 8__ _____ 0.0___ 0.0___
- 9__ _____ 0.0___ 0.0___
- 10_ _____ 0.0___ 0.0___
-
- next: end__
-
- AFTER COMPLETING ALL ANSWERS, HIT <ESC> TO CONTINUE
- (OR <Ctrl-C> TO CANCEL)
-</PRE>
-The input display is repeated until the number of MAXIMUM FIDUCIALS
-is reached.
-
-
-<H2>SEE ALSO</H2>
-
-<EM><A HREF="i.ortho.photo.html">i.ortho.photo</A></EM>,
-<EM><A HREF="photo.2image.html">photo.2image</A></EM>,
-<EM><A HREF="photo.2target.html">photo.2target</A></EM>,
-<EM><A HREF="photo.init.html">photo.init</A></EM>
-
-
-<H2>AUTHOR</H2>
-
-Mike Baba, DBA Systems, Inc.
-
-<p><i>Last changed: $Date$</i>
-</body>
-</html>
Copied: grass/trunk/imagery/i.ortho.photo/photo.camera/photo.camera.html (from rev 32770, grass/trunk/imagery/i.ortho.photo/photo.camera/description.html)
===================================================================
--- grass/trunk/imagery/i.ortho.photo/photo.camera/photo.camera.html (rev 0)
+++ grass/trunk/imagery/i.ortho.photo/photo.camera/photo.camera.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,126 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<head>
+<title></title>
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
+<link rel="stylesheet" href="grassdocs.css" type="text/css">
+</head>
+<body bgcolor="white">
+
+<img src="grass_logo.png" alt="GRASS logo"><hr align=center size=6 noshade>
+
+<h2>NAME</h2>
+<em><b></b></em>
+
+<H2>DESCRIPTION</H2>
+
+<EM>photo.camera</EM> creates or modifies entries in a camera reference
+file. For ortho-photo rectification, a camera reference file is required for
+computation of scanned image to photo-coordinate transformation parameters.
+There are two coordinate systems: The image coordinate system (in pixels)
+and the photo coordinate system (in milli-meters). The inner orientation
+establishes a relation between the pixels and the image coordinates with
+help of fiducial marks.
+
+<P>
+
+The first prompt in the program will ask you for the name of
+the camera reference file to be created or modified. You may
+create a new camera reference file by entering a new name, or modify an
+existing camera reference file by entering the name of an existing camera file.
+
+<P>
+After entering the camera file name, following menu is displayed:
+<P>
+Please provide the following information
+
+
+<P>
+<PRE>
+
+ CAMERA NAME: <EM>camera name</EM>______
+ CAMERA IDENTIFICATION: <EM>identification</EM>___
+ CALIBRATED FOCAL LENGTH mm.:_________________
+ POINT OF SYMMETRY (X) mm.:_________________
+ POINT OF SYMMETRY (Y) mm.:_________________
+ MAXIMUM NUMBER OF FIDUCIALS:_________________
+
+ AFTER COMPLETING ALL ANSWERS, HIT <ESC> TO CONTINUE
+ (OR <Ctrl-C> TO CANCEL)
+</PRE>
+
+The camera name and identification describe the camera reference file.
+The calibrated focal length and the point of symmetry are used in computing
+the photo-to-target transformation parameters. These values should be entered
+from the camera calibration report (usually available from the photograph
+supplier).
+
+<p>
+<img src="photo.camera.png" alt="Sketch of aerial photo"><br>
+<i>This example is the camera Zeiss LMK9 265-002A belonging to the Hellenic
+Military Geographical Survey (HMGS) and calibrated in December 1985</i>
+<p>
+
+The photo coordinate system origin is the so-called calibrated principal
+point (PP, Principal Point of Symmetry) which is in the center of the image.
+The origin of the axes is at the intersection of the radii traced from the
+fiducial marks. In the ideal case of no deviations in the camera (see camera
+calibration certificate) the center is the origin and the values are 0 for
+both X and Y of Point of Symmetry. But usually the principal point does not
+fall on the intersection of the radii at the center of the picture. This
+excentricity is usually of the order of a few micrometers. <P>
+
+You are then asked to enter the X and Y photo coordinates of each fiducial
+as follows.
+These fiducials (or reseau) marks are index marks imaged on film which serve
+as reference photo coordinate system. The maximum number of fiducials will
+determine the number of fiducial or reseau coordinate pairs to be entered
+below. The origin is the center of the image (or the point of symmetry) and
+X and Y are left-right and up-down. The order is up to the user, but must be
+kept consistent throughout the rectification process.
+<P>
+
+On this screen you should enter the fiducial or
+reseau photo-coordinates as given in the camera calibration report. The X,
+and Y coordinates are in milli-meters from the principle point.
+
+<P>
+Please provide the following information
+<PRE>
+ Fid# FID ID X Y
+
+ 1__ _____ 0.0___ 0.0___
+ 2__ _____ 0.0___ 0.0___
+ 3__ _____ 0.0___ 0.0___
+ 4__ _____ 0.0___ 0.0___
+ 5__ _____ 0.0___ 0.0___
+ 6__ _____ 0.0___ 0.0___
+ 7__ _____ 0.0___ 0.0___
+ 8__ _____ 0.0___ 0.0___
+ 9__ _____ 0.0___ 0.0___
+ 10_ _____ 0.0___ 0.0___
+
+ next: end__
+
+ AFTER COMPLETING ALL ANSWERS, HIT <ESC> TO CONTINUE
+ (OR <Ctrl-C> TO CANCEL)
+</PRE>
+The input display is repeated until the number of MAXIMUM FIDUCIALS
+is reached.
+
+
+<H2>SEE ALSO</H2>
+
+<EM><A HREF="i.ortho.photo.html">i.ortho.photo</A></EM>,
+<EM><A HREF="photo.2image.html">photo.2image</A></EM>,
+<EM><A HREF="photo.2target.html">photo.2target</A></EM>,
+<EM><A HREF="photo.init.html">photo.init</A></EM>
+
+
+<H2>AUTHOR</H2>
+
+Mike Baba, DBA Systems, Inc.
+
+<p><i>Last changed: $Date$</i>
+</body>
+</html>
Modified: grass/trunk/imagery/i.ortho.photo/photo.init/Makefile
===================================================================
--- grass/trunk/imagery/i.ortho.photo/photo.init/Makefile 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/imagery/i.ortho.photo/photo.init/Makefile 2008-08-15 06:16:42 UTC (rev 32772)
@@ -11,6 +11,6 @@
default: etc
-$(PGM).tmp.html: description.html
+$(PGM).tmp.html: $(PGM).html
$(INSTALL_DATA) $< $@
Deleted: grass/trunk/imagery/i.ortho.photo/photo.init/description.html
===================================================================
--- grass/trunk/imagery/i.ortho.photo/photo.init/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/imagery/i.ortho.photo/photo.init/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,127 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-<head>
-<title>photo.init</title>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link rel="stylesheet" href="grassdocs.css" type="text/css">
-</head>
-<body bgcolor="white">
-
-<img src="grass_logo.png" alt="GRASS logo"><hr align=center size=6 noshade>
-
-<h2>NAME</h2>
-<em><b>photo.init</b></em>
-
-<H2>DESCRIPTION</H2>
-
-Aerial photographs may be either vertical or oblique. Vertical photographs
-can be truly vertical (nadir), or slightly tilted (less than 3 degree
-from the vertical). Usually aerial photos are tilted to some degree. We
-refer to the term <i>vertical photograph</i> up to a tilt of 3 degree.
-<br>
-Oblique aerial photographs are purposely taken with an
-angle between 3 and 90 degree from the nadir direction.
-<P>
-<b>The use of <EM>photo.init</EM> (menu 6) is only required when rectifying a
-tilted or oblique aerial photo.</b>
-<P>
-<EM>photo.init</EM> creates or modifies entries in a camera initial exposure
-station file for imagery group referenced by a sub-block. These entries
-include: the (XC,YC,ZC) standard (e.g. UTM) approximate coordinates of the camera exposure
-station; initial roll, pitch, and yaw angles (in degrees) of the cameras
-attitude; and the <EM>a priori</EM> standard deviations for these
-parameters. During the imagery program, photo.rectify, the initial camera
-exposure station file is used for computation of the ortho-rectification
-parameters. If no initial camera exposure station file exist, the default
-values are computed from the control points file created in <EM><A
-HREF="photo.2target.html">photo.2target</A></EM>.
-
-
-<P>
-
-The following menu is displayed:
-<PRE>
- Please provide the following information
-
- INITIAL XC: Meters __________
- INITIAL YC: Meters __________
- INITIAL ZC: Meters __________
- INITIAL omega (roll) degrees: __________
- INITIAL phi (pitch) degrees: __________
- INITIAL kappa (yaw) degrees: __________
-
- Standard Deviation XC: Meters __________
- Standard Deviation YC: Meters __________
- Standard Deviation ZC: Meters __________
- Std. Dev. omega (roll) degrees: __________
- Std. Dev. phi (pitch) degrees: __________
- Std. Dev. kappa (yaw) degrees: __________
-
- Use these values at run time? (1=yes, 0=no)
-
- AFTER COMPLETING ALL ANSWERS, HIT <ESC> TO CONTINUE
- (OR <Ctrl-C> TO CANCEL)
-</PRE>
-
-<P>
-The INITIAL values for (XC,YC,ZC) are expressed in standard (e.g. UTM) coordinates, and
-represent an approximation for the location of the camera at the time of
-exposure.
-
-<ul>
-<li> X: East aircraft position;
-<li> Y: North aircraft position;
-<li> Z: Flight altitude above sea level
-</ul>
-
-<P>
-
-The INITIAL values for (omega,phi,kappa) are expressed in degrees, and
-represent an approximation for the cameras attitude at the time of
-exposure.
-
-<ul>
-<li> Omega (roll): Raising or lowering of the wings (turning around the
- aircraft's axis);
-<li> Phi (pitch): Raising or lowering of the aircraft's front (turning
- around the wings' axis);
-<li> Kappa (yaw): Rotation needed to align the aerial photo to true north:
- needs to be denoted as +90 degree for clockwise turn and -90 degree for
- a counterclockwise turn.
-</ul>
-
-
-<P>
-
-The standard deviations for (XC,YC,ZC) are expressed in meters, and
-are used as <EM>a priori</EM> values for the standard deviations used in
-computation of the ortho rectification parameters.
-
-
-<P>
-
-The standard deviations for (omega,phi,kappa) are expressed in degrees, and
-are used as <EM>a priori</EM> values for the standard deviations used in
-computation of the ortho rectification parameters.
-
-<P>
-If <i>Use these values at run time? (1=yes, 0=no)</i> is set to 0, the
-values in this menu are not used.
-
-<H2>SEE ALSO</H2>
-
-<EM><A HREF="i.ortho.photo.html">i.ortho.photo</A></EM>,
-<EM><A HREF="photo.camera.html">photo.camera</A></EM>,
-<EM><A HREF="photo.2image.html">photo.2image</A></EM>,
-<EM><A HREF="photo.2target.html">photo.2target</A></EM>,
-<EM><A HREF="photo.rectify.html">photo.rectify</A></EM>
-
-
-
-<H2>AUTHOR</H2>
-
-Mike Baba, DBA Systems, Inc.
-<p><i>Last changed: $Date$</i>
-
-</body>
-</html>
Copied: grass/trunk/imagery/i.ortho.photo/photo.init/photo.init.html (from rev 32770, grass/trunk/imagery/i.ortho.photo/photo.init/description.html)
===================================================================
--- grass/trunk/imagery/i.ortho.photo/photo.init/photo.init.html (rev 0)
+++ grass/trunk/imagery/i.ortho.photo/photo.init/photo.init.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,127 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<head>
+<title>photo.init</title>
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
+<link rel="stylesheet" href="grassdocs.css" type="text/css">
+</head>
+<body bgcolor="white">
+
+<img src="grass_logo.png" alt="GRASS logo"><hr align=center size=6 noshade>
+
+<h2>NAME</h2>
+<em><b>photo.init</b></em>
+
+<H2>DESCRIPTION</H2>
+
+Aerial photographs may be either vertical or oblique. Vertical photographs
+can be truly vertical (nadir), or slightly tilted (less than 3 degree
+from the vertical). Usually aerial photos are tilted to some degree. We
+refer to the term <i>vertical photograph</i> up to a tilt of 3 degree.
+<br>
+Oblique aerial photographs are purposely taken with an
+angle between 3 and 90 degree from the nadir direction.
+<P>
+<b>The use of <EM>photo.init</EM> (menu 6) is only required when rectifying a
+tilted or oblique aerial photo.</b>
+<P>
+<EM>photo.init</EM> creates or modifies entries in a camera initial exposure
+station file for imagery group referenced by a sub-block. These entries
+include: the (XC,YC,ZC) standard (e.g. UTM) approximate coordinates of the camera exposure
+station; initial roll, pitch, and yaw angles (in degrees) of the cameras
+attitude; and the <EM>a priori</EM> standard deviations for these
+parameters. During the imagery program, photo.rectify, the initial camera
+exposure station file is used for computation of the ortho-rectification
+parameters. If no initial camera exposure station file exist, the default
+values are computed from the control points file created in <EM><A
+HREF="photo.2target.html">photo.2target</A></EM>.
+
+
+<P>
+
+The following menu is displayed:
+<PRE>
+ Please provide the following information
+
+ INITIAL XC: Meters __________
+ INITIAL YC: Meters __________
+ INITIAL ZC: Meters __________
+ INITIAL omega (roll) degrees: __________
+ INITIAL phi (pitch) degrees: __________
+ INITIAL kappa (yaw) degrees: __________
+
+ Standard Deviation XC: Meters __________
+ Standard Deviation YC: Meters __________
+ Standard Deviation ZC: Meters __________
+ Std. Dev. omega (roll) degrees: __________
+ Std. Dev. phi (pitch) degrees: __________
+ Std. Dev. kappa (yaw) degrees: __________
+
+ Use these values at run time? (1=yes, 0=no)
+
+ AFTER COMPLETING ALL ANSWERS, HIT <ESC> TO CONTINUE
+ (OR <Ctrl-C> TO CANCEL)
+</PRE>
+
+<P>
+The INITIAL values for (XC,YC,ZC) are expressed in standard (e.g. UTM) coordinates, and
+represent an approximation for the location of the camera at the time of
+exposure.
+
+<ul>
+<li> X: East aircraft position;
+<li> Y: North aircraft position;
+<li> Z: Flight altitude above sea level
+</ul>
+
+<P>
+
+The INITIAL values for (omega,phi,kappa) are expressed in degrees, and
+represent an approximation for the cameras attitude at the time of
+exposure.
+
+<ul>
+<li> Omega (roll): Raising or lowering of the wings (turning around the
+ aircraft's axis);
+<li> Phi (pitch): Raising or lowering of the aircraft's front (turning
+ around the wings' axis);
+<li> Kappa (yaw): Rotation needed to align the aerial photo to true north:
+ needs to be denoted as +90 degree for clockwise turn and -90 degree for
+ a counterclockwise turn.
+</ul>
+
+
+<P>
+
+The standard deviations for (XC,YC,ZC) are expressed in meters, and
+are used as <EM>a priori</EM> values for the standard deviations used in
+computation of the ortho rectification parameters.
+
+
+<P>
+
+The standard deviations for (omega,phi,kappa) are expressed in degrees, and
+are used as <EM>a priori</EM> values for the standard deviations used in
+computation of the ortho rectification parameters.
+
+<P>
+If <i>Use these values at run time? (1=yes, 0=no)</i> is set to 0, the
+values in this menu are not used.
+
+<H2>SEE ALSO</H2>
+
+<EM><A HREF="i.ortho.photo.html">i.ortho.photo</A></EM>,
+<EM><A HREF="photo.camera.html">photo.camera</A></EM>,
+<EM><A HREF="photo.2image.html">photo.2image</A></EM>,
+<EM><A HREF="photo.2target.html">photo.2target</A></EM>,
+<EM><A HREF="photo.rectify.html">photo.rectify</A></EM>
+
+
+
+<H2>AUTHOR</H2>
+
+Mike Baba, DBA Systems, Inc.
+<p><i>Last changed: $Date$</i>
+
+</body>
+</html>
Modified: grass/trunk/imagery/i.ortho.photo/photo.rectify/Makefile
===================================================================
--- grass/trunk/imagery/i.ortho.photo/photo.rectify/Makefile 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/imagery/i.ortho.photo/photo.rectify/Makefile 2008-08-15 06:16:42 UTC (rev 32772)
@@ -13,6 +13,6 @@
default: etc
-$(PGM).tmp.html: description.html
+$(PGM).tmp.html: $(PGM).html
$(INSTALL_DATA) $< $@
Deleted: grass/trunk/imagery/i.ortho.photo/photo.rectify/description.html
===================================================================
--- grass/trunk/imagery/i.ortho.photo/photo.rectify/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/imagery/i.ortho.photo/photo.rectify/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,88 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-<head>
-<title>photo.rectify</title>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link rel="stylesheet" href="grassdocs.css" type="text/css">
-</head>
-<body bgcolor="white">
-
-<img src="grass_logo.png" alt="GRASS logo"><hr align=center size=6 noshade>
-
-<h2>NAME</h2>
-<em><b>photo.rectify</b></em>
-
-<H2>DESCRIPTION</H2>
-
-<EM>photo.rectify</EM> rectifies an image by using the image to photo
-coordinate transformation matrix created by <A HREF="photo.2image.html">photo.2image</A>
-and the rectification parameters created by <A HREF="photo.2target.html">photo.2target</A>.
-Rectification is the process by which the geometry of an image is made
-planimetric. This is accomplished by mapping an image from one coordinate
-system to another. In photo.rectify the parameters computed by
-<A HREF="photo.2image.html">photo.2image</A> and
-<A HREF="photo.2target.html">photo.2target</A> are used in equations to
-convert x,y image coordinates to standard map coordinates for each pixel in
-the image. The result is an image with a standard map coordinate system,
-compensated for relief distortions and photographic tilt. Upon completion of
-the program the rectified image is deposited in a previously targeted GRASS
-LOCATION.
-<P> You are asked to select the file(s) within the imagery group
-to be rectified:
-<P> Please select the file(s) to rectify by naming an
-output file <P> <PRE>
-
- gs13.1 in PERMANENT gs13.orect...
- gs14.1 in PERMANENT .............
-
- (enter list by any name to get a list of existing raster maps)
-
- AFTER COMPLETING ALL ANSWERS, HIT <ESC> TO CONTINUE
- (OR <Ctrl-C> TO CANCEL)
-</PRE>
-<P>
-<P>
-More than one file may be rectified at a time. Each file
-should have a unique output file name.
-<P>
-The next prompt asks you to select one of two windows:
-<P>
-<PRE>
- Please select one of the following options
- 1. Use the current window in the target location
- 2. Determine the smallest window which covers the image
- >
-</PRE>
-<P>
-<EM>photo.rectify</EM> will only rectify that portion of the
-image that occurs within the chosen window. Only that portion will be
-relocated in the target database. It is therefore important to check the
-current window in the target LOCATION if choice number one is selected.
-<P>
-The process may take an hour or more depending on the size of the image,
-the speed of the computer, the number files, and the size and resolution
-of the selected window.
-<P>
-The rectified image will be located in the target LOCATION when the program
-is completed. The original unrectified files are not modified or removed.
-
-<H2>SEE ALSO</H2>
-
-<EM>
-<A HREF="i.ortho.photo.html">i.ortho.photo</A><br>
-<A HREF="photo.camera.html">photo.camera</A><br>
-<A HREF="photo.2image.html">photo.2image</A><br>
-<A HREF="photo.2target.html">photo.2target</A><br>
-<A HREF="photo.init.html">photo.init</A>
-</EM>
-
-
-
-<H2>AUTHOR</H2>
-Mike Baba, DBA Systems, Inc.<br>
-Updated rectification and elevation map to FP 1/2002 Markus Neteler
-
-<p><i>Last changed: $Date$</i>
-
-</body>
-</html>
Copied: grass/trunk/imagery/i.ortho.photo/photo.rectify/photo.rectify.html (from rev 32770, grass/trunk/imagery/i.ortho.photo/photo.rectify/description.html)
===================================================================
--- grass/trunk/imagery/i.ortho.photo/photo.rectify/photo.rectify.html (rev 0)
+++ grass/trunk/imagery/i.ortho.photo/photo.rectify/photo.rectify.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,88 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<head>
+<title>photo.rectify</title>
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
+<link rel="stylesheet" href="grassdocs.css" type="text/css">
+</head>
+<body bgcolor="white">
+
+<img src="grass_logo.png" alt="GRASS logo"><hr align=center size=6 noshade>
+
+<h2>NAME</h2>
+<em><b>photo.rectify</b></em>
+
+<H2>DESCRIPTION</H2>
+
+<EM>photo.rectify</EM> rectifies an image by using the image to photo
+coordinate transformation matrix created by <A HREF="photo.2image.html">photo.2image</A>
+and the rectification parameters created by <A HREF="photo.2target.html">photo.2target</A>.
+Rectification is the process by which the geometry of an image is made
+planimetric. This is accomplished by mapping an image from one coordinate
+system to another. In photo.rectify the parameters computed by
+<A HREF="photo.2image.html">photo.2image</A> and
+<A HREF="photo.2target.html">photo.2target</A> are used in equations to
+convert x,y image coordinates to standard map coordinates for each pixel in
+the image. The result is an image with a standard map coordinate system,
+compensated for relief distortions and photographic tilt. Upon completion of
+the program the rectified image is deposited in a previously targeted GRASS
+LOCATION.
+<P> You are asked to select the file(s) within the imagery group
+to be rectified:
+<P> Please select the file(s) to rectify by naming an
+output file <P> <PRE>
+
+ gs13.1 in PERMANENT gs13.orect...
+ gs14.1 in PERMANENT .............
+
+ (enter list by any name to get a list of existing raster maps)
+
+ AFTER COMPLETING ALL ANSWERS, HIT <ESC> TO CONTINUE
+ (OR <Ctrl-C> TO CANCEL)
+</PRE>
+<P>
+<P>
+More than one file may be rectified at a time. Each file
+should have a unique output file name.
+<P>
+The next prompt asks you to select one of two windows:
+<P>
+<PRE>
+ Please select one of the following options
+ 1. Use the current window in the target location
+ 2. Determine the smallest window which covers the image
+ >
+</PRE>
+<P>
+<EM>photo.rectify</EM> will only rectify that portion of the
+image that occurs within the chosen window. Only that portion will be
+relocated in the target database. It is therefore important to check the
+current window in the target LOCATION if choice number one is selected.
+<P>
+The process may take an hour or more depending on the size of the image,
+the speed of the computer, the number files, and the size and resolution
+of the selected window.
+<P>
+The rectified image will be located in the target LOCATION when the program
+is completed. The original unrectified files are not modified or removed.
+
+<H2>SEE ALSO</H2>
+
+<EM>
+<A HREF="i.ortho.photo.html">i.ortho.photo</A><br>
+<A HREF="photo.camera.html">photo.camera</A><br>
+<A HREF="photo.2image.html">photo.2image</A><br>
+<A HREF="photo.2target.html">photo.2target</A><br>
+<A HREF="photo.init.html">photo.init</A>
+</EM>
+
+
+
+<H2>AUTHOR</H2>
+Mike Baba, DBA Systems, Inc.<br>
+Updated rectification and elevation map to FP 1/2002 Markus Neteler
+
+<p><i>Last changed: $Date$</i>
+
+</body>
+</html>
Deleted: grass/trunk/imagery/i.pca/description.html
===================================================================
--- grass/trunk/imagery/i.pca/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/imagery/i.pca/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,85 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-
-<EM>i.pca</EM> is an image processing program based on the
-algorithm provided by Vali (1990), that processes n (2
->= n) input raster map layers and produces n output
-raster map layers containing the principal components of
-the input data in decreasing order of variance
-("contrast"). The output raster map layers are assigned
-names with .1, .2, ... .n suffixes. The current geographic
-region definition and mask settings are respected when
-reading the input raster map layers. When the rescale
-option is used, the output files are rescaled to fit the
-min,max range.
-
-<H2>OPTIONS</H2>
-
-<H3>Parameters:</H3>
-
-<DL>
-
-<DT><B>input=</B><EM>name,name</EM>[<EM>,name,name</EM>,...]
-
-<DD>Name of two or more input raster map layers.
-
-<DT><B>output=</B><EM>name</EM>
-
-<DD>The output raster map layer name to which suffixes are
-added. Each output raster map layer is assigned this
-user-specified <EM>name</EM> with a numerical (.1, .2, ...
-.n) suffix.
-
-<DT><B>rescale=</B><EM>min,max</EM>
-
-<DD>The optional output category range. (Default: 0,255) If
-rescale=0,0, no rescaling is performed on output files.
-
-<DD>If output is rescaled, the output raster will be of type CELL. If
-the output is not rescaled, the output raster will be of type DCELL.
-
-</DL>
-
-<H2>NOTES</H2>
-
-Richards (1986) gives a good example of the application of principal
-components analysis (pca) to a time series of LANDSAT images of a burned
-region in Australia.
-
-<H2>SEE ALSO</H2>
-
-Richards, John A.,
-<B>Remote Sensing Digital Image Analysis</B>,
-Springer-Verlag, 1986.
-
-<P>
-
-Vali, Ali R.,
-Personal communication,
-Space Research Center,
-University of Texas, Austin, 1990.
-
-<P>
-
-<EM><A HREF="i.cca.html">i.cca</A></EM><br>
-<EM><A HREF="i.class.html">i.class</A></EM><br>
-<EM><A HREF="i.fft.html">i.fft</A></EM><br>
-<EM><A HREF="i.ifft.html">i.ifft</A></EM><br>
-<EM><A HREF="m.eigensystem.html">m.eigensystem</A></EM><br>
-<EM><A HREF="r.covar.html">r.covar</A></EM><br>
-<EM><A HREF="r.mapcalc.html">r.mapcalc</A></EM>
-
-<H2>AUTHOR</H2>
-
-David Satnik, GIS Laboratory
-<p>
-Major modifications for GRASS 4.1 were made by <br>
-Olga Waupotitsch and
-Michael Shapiro,
-U.S.Army Construction Engineering
-Research Laboratory
-<p>
-Rewritten for GRASS 6.x and major modifications by <br>
-Brad Douglas
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/imagery/i.pca/i.pca.html (from rev 32770, grass/trunk/imagery/i.pca/description.html)
===================================================================
--- grass/trunk/imagery/i.pca/i.pca.html (rev 0)
+++ grass/trunk/imagery/i.pca/i.pca.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,85 @@
+<H2>DESCRIPTION</H2>
+
+
+<EM>i.pca</EM> is an image processing program based on the
+algorithm provided by Vali (1990), that processes n (2
+>= n) input raster map layers and produces n output
+raster map layers containing the principal components of
+the input data in decreasing order of variance
+("contrast"). The output raster map layers are assigned
+names with .1, .2, ... .n suffixes. The current geographic
+region definition and mask settings are respected when
+reading the input raster map layers. When the rescale
+option is used, the output files are rescaled to fit the
+min,max range.
+
+<H2>OPTIONS</H2>
+
+<H3>Parameters:</H3>
+
+<DL>
+
+<DT><B>input=</B><EM>name,name</EM>[<EM>,name,name</EM>,...]
+
+<DD>Name of two or more input raster map layers.
+
+<DT><B>output=</B><EM>name</EM>
+
+<DD>The output raster map layer name to which suffixes are
+added. Each output raster map layer is assigned this
+user-specified <EM>name</EM> with a numerical (.1, .2, ...
+.n) suffix.
+
+<DT><B>rescale=</B><EM>min,max</EM>
+
+<DD>The optional output category range. (Default: 0,255) If
+rescale=0,0, no rescaling is performed on output files.
+
+<DD>If output is rescaled, the output raster will be of type CELL. If
+the output is not rescaled, the output raster will be of type DCELL.
+
+</DL>
+
+<H2>NOTES</H2>
+
+Richards (1986) gives a good example of the application of principal
+components analysis (pca) to a time series of LANDSAT images of a burned
+region in Australia.
+
+<H2>SEE ALSO</H2>
+
+Richards, John A.,
+<B>Remote Sensing Digital Image Analysis</B>,
+Springer-Verlag, 1986.
+
+<P>
+
+Vali, Ali R.,
+Personal communication,
+Space Research Center,
+University of Texas, Austin, 1990.
+
+<P>
+
+<EM><A HREF="i.cca.html">i.cca</A></EM><br>
+<EM><A HREF="i.class.html">i.class</A></EM><br>
+<EM><A HREF="i.fft.html">i.fft</A></EM><br>
+<EM><A HREF="i.ifft.html">i.ifft</A></EM><br>
+<EM><A HREF="m.eigensystem.html">m.eigensystem</A></EM><br>
+<EM><A HREF="r.covar.html">r.covar</A></EM><br>
+<EM><A HREF="r.mapcalc.html">r.mapcalc</A></EM>
+
+<H2>AUTHOR</H2>
+
+David Satnik, GIS Laboratory
+<p>
+Major modifications for GRASS 4.1 were made by <br>
+Olga Waupotitsch and
+Michael Shapiro,
+U.S.Army Construction Engineering
+Research Laboratory
+<p>
+Rewritten for GRASS 6.x and major modifications by <br>
+Brad Douglas
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/imagery/i.points/description.html
===================================================================
--- grass/trunk/imagery/i.points/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/imagery/i.points/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,424 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-<EM>i.points</EM> is an
-<A HREF="imagery.html">imagery</A> function that enables
-the user to mark points on a (raster) image to be rectified
-and then input the geographic coordinates of each point for
-calculation of a coordinate transformation matrix.
-<EM>i.points</EM> must be followed by use of the GRASS
-program <EM><A HREF="i.rectify.html">i.rectify</A></EM>, which
-rectifies the image using the transformation matrix
-coefficients calculated by <EM>i.points</EM>.
-
-<P>
-
-<EM>Rectification</EM> is the mapping (transformation) of
-an image from one coordinate system to another. The
-geometry of an image extracted into a GRASS LOCATION having
-an x,y coordinate system is not planimetric. To create a
-planimetric image, that is, to convert the x,y coordinate
-system into a standard coordinate system (for example, the
-UTM coordinate system or the State Plane coordinate
-system), points from a map having the standard coordinates
-must be associated with the same points on the image to be
-rectified. <EM>i.points</EM> enables the user to mark
-points on an image and input the standard coordinates for
-that point. <EM>i.points</EM> then calculates a least
-squares regression using the two coordinate systems (x,y
-and standard) for the marked points. A matrix containing
-transformation coefficients is the output file for
-<EM>i.points</EM>.
-
-<P>
-During the process of marking points and entering map
-coordinates, the user can compute the RMS (root mean
-square) error for each point entered. <EM>i.points</EM>
-does this by calculating the transformation equation (the
-same one that is calculated in the GRASS program <EM>
-<A HREF="i.rectify.html">i.rectify</A></EM>), and then
-plugging these results into an equation for RMS error.
-
-<P>
-<EM>i.points</EM> offers a zoom option to locate precisely
-the point to be marked on an image. This program also
-offers the user the option of acquiring standard
-coordinates for a marked point from a map layer in the
-target data base.
-
-<P>
-<EM><A HREF="i.target.html">i.target</A></EM> must be
-run before running <EM>i.points</EM> to enable the PLOT
-RASTER option to be used and to identify a target data base
-LOCATION_NAME and MAPSET for the rectified image. To run
-<EM>i.points</EM>, a graphics monitor is required.
-
-<P>
-The procedure for marking points, entering coordinates, and
-calculating RMS error is described below.
-
-<P>
-The first prompt in the program asks the user for the
-<A HREF="i.group.html">imagery group</A> to be
-registered. Note that if
-<EM><A HREF="i.target.html">i.target</A></EM> is not run
-before <EM>i.points</EM>, the <EM>i.points</EM> program
-will display the following error message:
-
-<PRE>
-ERROR: Target information for group [spot] missing
- Please run i.target for group [spot]
-</PRE>
-
-After entering the group to be registered the terminal screen
-displays the message:
-
-<PRE>
- Use mouse now...
-</PRE>
-
-The graphics monitor displays the following screen:
-
-<PRE>
- ______________________________________________________________
-| imagery filename (mag) | target filename (mag) |
-|_________________________________|___________________________|
-| | |
-| | |
-| | |
-| | |
-| | |
-| | |
-| | |
-|_________________________________|___________________________|
-| | |
-| | |
-| | |
-| | |
-| | |
-| | |
-| | |
-|_________________________________|___________________________|
-| QUIT ZOOM PLOT RASTER ANALYZE| |
-|_________________________________|___________________________|
-</PRE>
-
-A pop-down menu like that shown below will be superimposed on the
-left half of the screen:
-
-
-<PRE>
- __________________________________
- | Double click on raster map layer|
- | to be plotted |
- | Double click here to cancel |
- |_________________________________|
-
- ____________________
- | Mapset demo |
- |___________________|
- | spotclass| spot.1|
- |__________|________|
- | composite| spot.2|
- |__________|________|
- | spot.3 | |
- |__________|________|
-</PRE>
-
-Any single raster map layer in the
-
-<A HREF="i.group.html">imagery group</A> may be used on
-
-which to mark points, and the user can mark points on more
-than one raster map layer in the
-
-<A HREF="i.group.html">imagery group</A> to accumulate the
-
-suggested minimum number of 12 points. Any raster map
-layer in the <A HREF="i.group.html">imagery group</A>
-can be rectified (using
-
-<EM><A HREF="i.rectify.html">i.rectify</A></EM>) based on the
-transformation matrix computed from these points.
-
-
-<P>
-
-The imagery file chosen by
-the user is displayed in the upper left quadrant of the
-screen.
-
-<H3>ZOOM</H3>
-
-To magnify the displayed file, the user must
-place the mouse cross hairs on the word ZOOM. The following menu
-will then be displayed at the bottom of the screen:
-
-<PRE>
- ____________________________________________
- | Cancel| Box| Point| Select type of ZOOM|
- |_______|_____|_______|_____________________|
-</PRE>
-
-
-The user has the option of identifying the zoom region
-either by using the mouse to make a box, or by using the
-mouse to mark the two diagonal points of the desired
-region. The terminal screen will display a mouse button
-menu to guide the user in identifying the corner points of
-the region.
-
-<H3>MARKING POINTS</H3>
-
-To mark the points on the image that correspond to the
-points on a standard coordinate system map, the user must
-place the mouse cross hairs on the corresponding location
-on the image to be marked and press the left hand button on
-the mouse. A diamond shaped symbol will be marked on the
-image. The user's terminal will display the following
-menu:
-
-
-<PRE>
- ___________________________________________________________
-| Point 1 marked on the image at| |
-| East: 1023.77 | |
-| North: -164.41 | |
-| | |
-| | |
-| | |
-| | |
-| | |
-|__________________________________________________________|
-| Enter coordinates as east north: |
-|__________________________________________________________|
-</PRE>
-
-The user then enters the easting and northing (separated by
-a space) for the point marked on the image. If the user
-wishes not to enter a coordinate, he or she may simply hit
-RETURN to return control to the mouse; the marked point
-then disappears.
-
-<H3>PLOT RASTER</H3>
-
-In addition to acquiring reference points from a standard
-map, the user has the option of acquiring the reference
-points from a raster map layer in the target data base
-LOCATION_NAME. The data base raster map layer is displayed
-by placing the mouse cross hairs on the words PLOT RASTER.
-The following line is then displayed at the bottom of the
-graphics monitor:
-
-
-<PRE>
- ________________________________________________
- | Cancel| Indicate which side should be plotted|
- |_______|_______________________________________|
-</PRE>
-
-Which side of the graphics monitor is to be plotted
-is indicated by placing the mouse cross hairs on the
-half of the graphics monitor screen that the user would like to use,
-and pressing the left mouse button. The following pop-down
-menu will be superimposed on the half of the screen that was chosen:
-
-
-<PRE>
- _________________________________________
- | Double click on raster (cell) map layer|
- | to be plotted |
- | Double click here to cancel |
- |________________________________________|
-
- ______________________________
- | Mapset demo |
- |_____________________________|
- | tm.rectified | |
- |______________|______________|
- | tm.classified| |
- |_____________________________|
- | Mapset PERMANENT |
- |_____________________________|
- | elevation | geology |
- |______________|______________|
- | slope | soils |
- |______________|______________|
- | aspect | |
- |______________|______________|
- | roads | |
- |______________|______________|
-</PRE>
-
-After the raster map layer is displayed the following message appears
-at the bottom of the graphics monitor:
-
-
-<PRE>
- ______________________________________
- | input method -->| keyboard| screen|
- |_________________|__________|________|
-</PRE>
-
-If the user wishes to use the plotted raster map layer only
-as a comparative reference, then the keyboard can be chosen
-as the means to input coordinates corresponding to the
-marked points on the image. This is done by placing the
-mouse cross hairs on the word KEYBOARD and pressing the
-left button on the mouse.
-
-
-<P>
-
-If the user selects the SCREEN option, then points marked
-on the image will automatically be associated with the
-coordinates from the corresponding points on the target
-data base map layer. In this option, when the user marks a
-point on the image, the following menu is displayed at the
-terminal:
-
-
-<PRE>
-___________________________________________________________
-| Point 5 marked on the image at| |
-| East: 1023.77 | |
-| North: -164.41 | |
-| | |
-| | |
-| Point located at | |
-| East: 679132.57 | |
-| North: 4351080.67 | |
-| | |
-| | |
-| | |
-| | |
-| | |
-|__________________________________________________________|
-| use mouse now... |
-|__________________________________________________________|
-</PRE>
-
-
-The user then uses the mouse to mark a corresponding point
-on the displayed image from the target data base. The
-coordinates for the target data base map layer are
-automatically saved as the coordinates corresponding to the
-marked point on the image.
-
-<H3>ANALYZE</H3>
-
-After a number of points have been marked (4 to 7), the
-user can check the RMS error of the points marked on the
-image. This is done by placing the mouse cross hairs on
-the word ANALYZE at the bottom of the graphics monitor. An
-error report resembling that shown below is superimposed on
-the graphics monitor:
-
-
-<PRE>
-______________________________________________________________________
-| error image target |
-|# row col target east north east north |
-|____________________________________________________________________|
-|1 0.0 -0.9 1.0 1048.5 -144.8 679132.5 4351080.6|
-|2 0.4 1.0 1.3 2153.1 -567.2 684314.7 4399001.4|
-|3 -1.2 -0.5 .6 1452.8 -476.5 567841.4 3457682.8|
-|4 1.1 0.5 1.3 1034.0 -109.2 677573.8 4352626.4|
-|5 -2.7 14.0 14.2 1048.6 -144.9 679132.6 4351080.7|
-| |
-|____________________________________________________________________|
-| overall rms error: 4.46 |
-|____________________________________________________________________|
-</PRE>
-
-The following menu then appears at the bottom of the graphics monitor:
-
-<PRE>
- ____________________________________________________________________
-| DONE| PRINT FILE| Double click on point to be included/excluded|
-|_____|____________|________________________________________________|
-</PRE>
-
-The RMS error for the image is given under the column
-TITLEd "error" and subTITLEd "row" and "col". In the above
-report, point number 1 is 0.0 rows and -0.9 columns from
-the predicted location calculated from the transformation
-equation. The RMS error for the target raster map layer is
-listed under the heading "target". This is the RMS error
-for the east and north coordinates of the target map layer,
-but it is presented in the table using one general value.
-The overall RMS error is displayed at the bottom of the
-screen in meters. Points that create high RMS error are
-displayed in red on the graphics monitor (represented here
-in italics).
-
-<P>
-The location of the point marked on the
-<A HREF="i.group.html">imagery group</A> file is given
-under the heading "image" and the subheadings "east" and
-"north". The location of the point in the target data base
-is given under the heading "target" and the subheadings
-"east" and "north". If the user would like to exclude or
-include a point, this can be accomplished by placing the
-mouse cross hairs on the point number to be included (if
-the point is absent) or excluded (if the point is
-displayed) and pressing the left button on the mouse
-twice. When a point is excluded, it is not afterwards
-included in the calculation of the RMS error, or included
-in the final transformation matrix. However, it can be
-retrieved within <EM>i.points</EM> at any time by double
-clicking with the mouse as described above.
-
-<H3>QUIT</H3>
-
-To end the <EM>i.points</EM> program place the mouse cross
-hairs on the word QUIT; the marked points (including
-coordinates) will be saved.
-
-
-<H2>NOTES</H2>
-
-A good rule of thumb is to mark at least 12 to 15 points
-which are evenly distributed over the entire
-<A HREF="i.group.html">imagery group</A> file in order to
-obtain an accurate transformation equation for the
-rectification process. The RMS error may increase with
-more points added, but the transformation equation will be
-more accurate.
-
-<P>
-An RMS error of less than or equal to approximately one
-resolution unit (pixel or cell) for the image being
-rectified is generally considered acceptable.
-
-<P>
-In order to use a digitizer with <EM>i.points</EM>, at
-least one digitizer driver besides "none" (the on-screen
-digitizer) must be available in the digitcap file.
-
-<P>
-This program is interactive.
-
-
-<H2>SEE ALSO</H2>
-
-The GRASS 4 <em>
-<A HREF="http://grass.itc.it/gdp/imagery/grass4_image_processing.pdf">Image
-Processing manual</A></EM>
-
-<P>
-<EM>
-<A HREF="g.mapsets.html">g.mapsets</A><br>
-<A HREF="i.group.html">i.group</A><br>
-<A HREF="i.rectify.html">i.rectify</A><br>
-<A HREF="i.target.html">i.target</A><br>
-<A HREF="i.vpoints.html">i.vpoints</A>
-</EM><br>
-<em><a href="gm_georect.html">gis.m: GEORECTIFY TOOL</a></em>
-
-
-<H2>AUTHOR</H2>
-
-Michael Shapiro,
-U.S.Army Construction Engineering Research Laboratory
-<p>
-<i>Last changed: $Date$</i></p>
Copied: grass/trunk/imagery/i.points/i.points.html (from rev 32770, grass/trunk/imagery/i.points/description.html)
===================================================================
--- grass/trunk/imagery/i.points/i.points.html (rev 0)
+++ grass/trunk/imagery/i.points/i.points.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,424 @@
+<H2>DESCRIPTION</H2>
+
+<EM>i.points</EM> is an
+<A HREF="imagery.html">imagery</A> function that enables
+the user to mark points on a (raster) image to be rectified
+and then input the geographic coordinates of each point for
+calculation of a coordinate transformation matrix.
+<EM>i.points</EM> must be followed by use of the GRASS
+program <EM><A HREF="i.rectify.html">i.rectify</A></EM>, which
+rectifies the image using the transformation matrix
+coefficients calculated by <EM>i.points</EM>.
+
+<P>
+
+<EM>Rectification</EM> is the mapping (transformation) of
+an image from one coordinate system to another. The
+geometry of an image extracted into a GRASS LOCATION having
+an x,y coordinate system is not planimetric. To create a
+planimetric image, that is, to convert the x,y coordinate
+system into a standard coordinate system (for example, the
+UTM coordinate system or the State Plane coordinate
+system), points from a map having the standard coordinates
+must be associated with the same points on the image to be
+rectified. <EM>i.points</EM> enables the user to mark
+points on an image and input the standard coordinates for
+that point. <EM>i.points</EM> then calculates a least
+squares regression using the two coordinate systems (x,y
+and standard) for the marked points. A matrix containing
+transformation coefficients is the output file for
+<EM>i.points</EM>.
+
+<P>
+During the process of marking points and entering map
+coordinates, the user can compute the RMS (root mean
+square) error for each point entered. <EM>i.points</EM>
+does this by calculating the transformation equation (the
+same one that is calculated in the GRASS program <EM>
+<A HREF="i.rectify.html">i.rectify</A></EM>), and then
+plugging these results into an equation for RMS error.
+
+<P>
+<EM>i.points</EM> offers a zoom option to locate precisely
+the point to be marked on an image. This program also
+offers the user the option of acquiring standard
+coordinates for a marked point from a map layer in the
+target data base.
+
+<P>
+<EM><A HREF="i.target.html">i.target</A></EM> must be
+run before running <EM>i.points</EM> to enable the PLOT
+RASTER option to be used and to identify a target data base
+LOCATION_NAME and MAPSET for the rectified image. To run
+<EM>i.points</EM>, a graphics monitor is required.
+
+<P>
+The procedure for marking points, entering coordinates, and
+calculating RMS error is described below.
+
+<P>
+The first prompt in the program asks the user for the
+<A HREF="i.group.html">imagery group</A> to be
+registered. Note that if
+<EM><A HREF="i.target.html">i.target</A></EM> is not run
+before <EM>i.points</EM>, the <EM>i.points</EM> program
+will display the following error message:
+
+<PRE>
+ERROR: Target information for group [spot] missing
+ Please run i.target for group [spot]
+</PRE>
+
+After entering the group to be registered the terminal screen
+displays the message:
+
+<PRE>
+ Use mouse now...
+</PRE>
+
+The graphics monitor displays the following screen:
+
+<PRE>
+ ______________________________________________________________
+| imagery filename (mag) | target filename (mag) |
+|_________________________________|___________________________|
+| | |
+| | |
+| | |
+| | |
+| | |
+| | |
+| | |
+|_________________________________|___________________________|
+| | |
+| | |
+| | |
+| | |
+| | |
+| | |
+| | |
+|_________________________________|___________________________|
+| QUIT ZOOM PLOT RASTER ANALYZE| |
+|_________________________________|___________________________|
+</PRE>
+
+A pop-down menu like that shown below will be superimposed on the
+left half of the screen:
+
+
+<PRE>
+ __________________________________
+ | Double click on raster map layer|
+ | to be plotted |
+ | Double click here to cancel |
+ |_________________________________|
+
+ ____________________
+ | Mapset demo |
+ |___________________|
+ | spotclass| spot.1|
+ |__________|________|
+ | composite| spot.2|
+ |__________|________|
+ | spot.3 | |
+ |__________|________|
+</PRE>
+
+Any single raster map layer in the
+
+<A HREF="i.group.html">imagery group</A> may be used on
+
+which to mark points, and the user can mark points on more
+than one raster map layer in the
+
+<A HREF="i.group.html">imagery group</A> to accumulate the
+
+suggested minimum number of 12 points. Any raster map
+layer in the <A HREF="i.group.html">imagery group</A>
+can be rectified (using
+
+<EM><A HREF="i.rectify.html">i.rectify</A></EM>) based on the
+transformation matrix computed from these points.
+
+
+<P>
+
+The imagery file chosen by
+the user is displayed in the upper left quadrant of the
+screen.
+
+<H3>ZOOM</H3>
+
+To magnify the displayed file, the user must
+place the mouse cross hairs on the word ZOOM. The following menu
+will then be displayed at the bottom of the screen:
+
+<PRE>
+ ____________________________________________
+ | Cancel| Box| Point| Select type of ZOOM|
+ |_______|_____|_______|_____________________|
+</PRE>
+
+
+The user has the option of identifying the zoom region
+either by using the mouse to make a box, or by using the
+mouse to mark the two diagonal points of the desired
+region. The terminal screen will display a mouse button
+menu to guide the user in identifying the corner points of
+the region.
+
+<H3>MARKING POINTS</H3>
+
+To mark the points on the image that correspond to the
+points on a standard coordinate system map, the user must
+place the mouse cross hairs on the corresponding location
+on the image to be marked and press the left hand button on
+the mouse. A diamond shaped symbol will be marked on the
+image. The user's terminal will display the following
+menu:
+
+
+<PRE>
+ ___________________________________________________________
+| Point 1 marked on the image at| |
+| East: 1023.77 | |
+| North: -164.41 | |
+| | |
+| | |
+| | |
+| | |
+| | |
+|__________________________________________________________|
+| Enter coordinates as east north: |
+|__________________________________________________________|
+</PRE>
+
+The user then enters the easting and northing (separated by
+a space) for the point marked on the image. If the user
+wishes not to enter a coordinate, he or she may simply hit
+RETURN to return control to the mouse; the marked point
+then disappears.
+
+<H3>PLOT RASTER</H3>
+
+In addition to acquiring reference points from a standard
+map, the user has the option of acquiring the reference
+points from a raster map layer in the target data base
+LOCATION_NAME. The data base raster map layer is displayed
+by placing the mouse cross hairs on the words PLOT RASTER.
+The following line is then displayed at the bottom of the
+graphics monitor:
+
+
+<PRE>
+ ________________________________________________
+ | Cancel| Indicate which side should be plotted|
+ |_______|_______________________________________|
+</PRE>
+
+Which side of the graphics monitor is to be plotted
+is indicated by placing the mouse cross hairs on the
+half of the graphics monitor screen that the user would like to use,
+and pressing the left mouse button. The following pop-down
+menu will be superimposed on the half of the screen that was chosen:
+
+
+<PRE>
+ _________________________________________
+ | Double click on raster (cell) map layer|
+ | to be plotted |
+ | Double click here to cancel |
+ |________________________________________|
+
+ ______________________________
+ | Mapset demo |
+ |_____________________________|
+ | tm.rectified | |
+ |______________|______________|
+ | tm.classified| |
+ |_____________________________|
+ | Mapset PERMANENT |
+ |_____________________________|
+ | elevation | geology |
+ |______________|______________|
+ | slope | soils |
+ |______________|______________|
+ | aspect | |
+ |______________|______________|
+ | roads | |
+ |______________|______________|
+</PRE>
+
+After the raster map layer is displayed the following message appears
+at the bottom of the graphics monitor:
+
+
+<PRE>
+ ______________________________________
+ | input method -->| keyboard| screen|
+ |_________________|__________|________|
+</PRE>
+
+If the user wishes to use the plotted raster map layer only
+as a comparative reference, then the keyboard can be chosen
+as the means to input coordinates corresponding to the
+marked points on the image. This is done by placing the
+mouse cross hairs on the word KEYBOARD and pressing the
+left button on the mouse.
+
+
+<P>
+
+If the user selects the SCREEN option, then points marked
+on the image will automatically be associated with the
+coordinates from the corresponding points on the target
+data base map layer. In this option, when the user marks a
+point on the image, the following menu is displayed at the
+terminal:
+
+
+<PRE>
+___________________________________________________________
+| Point 5 marked on the image at| |
+| East: 1023.77 | |
+| North: -164.41 | |
+| | |
+| | |
+| Point located at | |
+| East: 679132.57 | |
+| North: 4351080.67 | |
+| | |
+| | |
+| | |
+| | |
+| | |
+|__________________________________________________________|
+| use mouse now... |
+|__________________________________________________________|
+</PRE>
+
+
+The user then uses the mouse to mark a corresponding point
+on the displayed image from the target data base. The
+coordinates for the target data base map layer are
+automatically saved as the coordinates corresponding to the
+marked point on the image.
+
+<H3>ANALYZE</H3>
+
+After a number of points have been marked (4 to 7), the
+user can check the RMS error of the points marked on the
+image. This is done by placing the mouse cross hairs on
+the word ANALYZE at the bottom of the graphics monitor. An
+error report resembling that shown below is superimposed on
+the graphics monitor:
+
+
+<PRE>
+______________________________________________________________________
+| error image target |
+|# row col target east north east north |
+|____________________________________________________________________|
+|1 0.0 -0.9 1.0 1048.5 -144.8 679132.5 4351080.6|
+|2 0.4 1.0 1.3 2153.1 -567.2 684314.7 4399001.4|
+|3 -1.2 -0.5 .6 1452.8 -476.5 567841.4 3457682.8|
+|4 1.1 0.5 1.3 1034.0 -109.2 677573.8 4352626.4|
+|5 -2.7 14.0 14.2 1048.6 -144.9 679132.6 4351080.7|
+| |
+|____________________________________________________________________|
+| overall rms error: 4.46 |
+|____________________________________________________________________|
+</PRE>
+
+The following menu then appears at the bottom of the graphics monitor:
+
+<PRE>
+ ____________________________________________________________________
+| DONE| PRINT FILE| Double click on point to be included/excluded|
+|_____|____________|________________________________________________|
+</PRE>
+
+The RMS error for the image is given under the column
+TITLEd "error" and subTITLEd "row" and "col". In the above
+report, point number 1 is 0.0 rows and -0.9 columns from
+the predicted location calculated from the transformation
+equation. The RMS error for the target raster map layer is
+listed under the heading "target". This is the RMS error
+for the east and north coordinates of the target map layer,
+but it is presented in the table using one general value.
+The overall RMS error is displayed at the bottom of the
+screen in meters. Points that create high RMS error are
+displayed in red on the graphics monitor (represented here
+in italics).
+
+<P>
+The location of the point marked on the
+<A HREF="i.group.html">imagery group</A> file is given
+under the heading "image" and the subheadings "east" and
+"north". The location of the point in the target data base
+is given under the heading "target" and the subheadings
+"east" and "north". If the user would like to exclude or
+include a point, this can be accomplished by placing the
+mouse cross hairs on the point number to be included (if
+the point is absent) or excluded (if the point is
+displayed) and pressing the left button on the mouse
+twice. When a point is excluded, it is not afterwards
+included in the calculation of the RMS error, or included
+in the final transformation matrix. However, it can be
+retrieved within <EM>i.points</EM> at any time by double
+clicking with the mouse as described above.
+
+<H3>QUIT</H3>
+
+To end the <EM>i.points</EM> program place the mouse cross
+hairs on the word QUIT; the marked points (including
+coordinates) will be saved.
+
+
+<H2>NOTES</H2>
+
+A good rule of thumb is to mark at least 12 to 15 points
+which are evenly distributed over the entire
+<A HREF="i.group.html">imagery group</A> file in order to
+obtain an accurate transformation equation for the
+rectification process. The RMS error may increase with
+more points added, but the transformation equation will be
+more accurate.
+
+<P>
+An RMS error of less than or equal to approximately one
+resolution unit (pixel or cell) for the image being
+rectified is generally considered acceptable.
+
+<P>
+In order to use a digitizer with <EM>i.points</EM>, at
+least one digitizer driver besides "none" (the on-screen
+digitizer) must be available in the digitcap file.
+
+<P>
+This program is interactive.
+
+
+<H2>SEE ALSO</H2>
+
+The GRASS 4 <em>
+<A HREF="http://grass.itc.it/gdp/imagery/grass4_image_processing.pdf">Image
+Processing manual</A></EM>
+
+<P>
+<EM>
+<A HREF="g.mapsets.html">g.mapsets</A><br>
+<A HREF="i.group.html">i.group</A><br>
+<A HREF="i.rectify.html">i.rectify</A><br>
+<A HREF="i.target.html">i.target</A><br>
+<A HREF="i.vpoints.html">i.vpoints</A>
+</EM><br>
+<em><a href="gm_georect.html">gis.m: GEORECTIFY TOOL</a></em>
+
+
+<H2>AUTHOR</H2>
+
+Michael Shapiro,
+U.S.Army Construction Engineering Research Laboratory
+<p>
+<i>Last changed: $Date$</i></p>
Deleted: grass/trunk/imagery/i.rectify/description.html
===================================================================
--- grass/trunk/imagery/i.rectify/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/imagery/i.rectify/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,232 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-
-<EM>i.rectify</EM> uses the control
-points identified in
-<EM><A HREF="i.points.html">i.points</A></EM>
-or
-<EM><A HREF="i.vpoints.html">i.vpoints</A></EM>
-
-to calculate a transformation matrix based on a first,
-second, or third order polynomial and then converts x,y
-cell coordinates to standard map coordinates for each pixel
-in the image. The result is a planimetric image with a
-transformed coordinate system (i.e., a different coordinate
-system than before it was rectified).
-
-<P>
-
-<EM><A HREF="i.points.html">i.points</A></EM>
-or
-<EM><A HREF="i.vpoints.html">i.vpoints</A></EM>
-
-must be run before <EM>i.rectify</EM>, and both programs
-are required to rectify an image. An image must be
-rectified before it can reside in a standard coordinate
-LOCATION, and therefore be analyzed with the other map
-layers in the standard coordinate LOCATION. Upon
-completion of <EM>i.rectify</EM>, the rectified image is
-deposited in the target standard coordinate LOCATION. This
-LOCATION is selected using
-
-<EM><A HREF="i.target.html">i.target</A></EM>.
-
-<H2>Program Prompts</H2>
-
-The first prompt in the program asks for the name of
-the group containing the files to be rectified.
-
-
-<PRE>
- Enter the group containing files to be rectified
- Enter 'list' for a list of existing imagery groups
- Enter 'list -f' for a verbose listing
- Hit RETURN to cancel request
- >
-</PRE>
-
- This is the same imagery group that was selected in
-
-<EM><A HREF="i.points.html">i.points</A></EM>
-or
-<EM><A HREF="i.vpoints.html">i.vpoints</A></EM>
-
-and the group that contains the raster maps with the marked
-points and their associated map coordinates. You are then
-asked to select the raster map(s) within the group to be
-rectified:
-
-
-<PRE>
-Please select the file(s) to rectify by naming an output file
-
- spot1.1 in mapsetname .............
- spot1.2 in mapsetname .............
- spot1.3 in mapsetname .............
- spotclass1 in mapsetname spotrectify1.
-
- spotreject1 in mapsetname .............
-
-(enter list by any name to get a list of existing raster maps)
-
-AFTER COMPLETING ALL ANSWERS, HIT <ESC> TO CONTINUE
- (OR<Ctrl-C> TO CANCEL)
-</PRE>
-
-More than one raster map may be rectified at a time. Each
-cell file should be given a unique output file name.
-
-
-<P>
-
-Next, you are asked to select one of two windows regions:
-
-
-<PRE>
- Please select one of the following options
- 1. Use the current window in the target location
- 2. Determine the smallest window which covers the image
- >
-</PRE>
-
-The <EM>i.rectify</EM> program will only rectify that
-portion of the image or raster map that occurs within the
-chosen window region, and only that portion of the cell
-file will be relocated in the target database. It is
-important therefore, to check the current mapset window in
-the target LOCATION if choice number one is selected.
-
-<P>
-
-If you are rectifying a file with plans to patch it to
-another file using the GRASS program <em>r.patch</em>,
-choose option number one, the current window in the target
-location. This window, however, must be the default window
-for the target LOCATION. When a file being rectified is
-smaller than the default window in which it is being
-rectified, zeros are added to the rectified file. Patching
-files of the same size that contain 0/non-zero data,
-eliminates the possibility of a no-data line the patched
-result. This is because, when the images are patched, the
-zeros in the image are "covered" with non-zero pixel
-values. When rectifying files that are going to be
-patched, rectify all of the files using the same default
-window.
-
-
-<P>
-
-Select the order of transformation desired with the <b>order</b> option:
-
-<PRE>
-Select order of transformation --> 1st Order 2nd Order 3rd Order
-</PRE>
-
-The program will immediately recalculate the RMSE and the
-number of points required.
-
-<h3>Linear affine transformation (1st order transformation)</h3>
-
-<DL>
- <DD> x' = ax + by +c
- <DD> y' = Ax + Bt +C
-</DL>
-
-The a,b,c,A,B,C are determined by least squares regression
-based on the control points entered. This transformation
-applies scaling, translation and rotation. It is NOT a
-general purpose rubber-sheeting, nor is it ortho-photo
-rectification using a DEM, not second order polynomial,
-etc. It can be used if (1) you have geometrically correct
-images, and (2) the terrain or camera distortion effect can
-be ignored.
-
-
-<H3>Polynomial Transformation Matrix (2nd, 3d order transformation)</H3>
-
-The ANALYZE function has been changed to support
-calculating the registration coefficients using a first,
-second, or third order transformation matrix. The number
-of control points required for a selected order of
-transformation (represented by n) is
-
-<DL>
-<DD>((n + 1) * (n + 2) / 2)
-</DL>
-
-or 3, 6, and 10 respectively. It is strongly recommended
-that one or more additional points be identified to allow
-for an overly- determined transformation calculation which
-will generate the Root Mean Square (RMS) error values for
-each included point. The RMS error values for all the
-included control points are immediately recalculated when
-the user selects a different transformation order from the
-menu bar. The polynomial equations are performed using a
-modified Gaussian elimination method.
-
-<H3>Program Execution</H3>
-
-Note: The rectified image or rectified raster maps will be
-located in the target LOCATION when the program is
-completed. The original unrectified files are not modified
-or removed.
-
-<P>
-<!--
-Note: In interactive mode it is possible to define a new file name
-for the target images. This is (currently) not provided in command line
-mode.
--->
-
-<h2>NOTES</h2>
-
-<EM>i.rectify</EM> uses nearest neighbor resampling during
-the transformation choosing the actual pixel that has its centre nearest to
-the point location in the image. Advantage of this method is that the pixel
-brightness of the image is kept as <EM>i.rectify</EM> rearranges the
-geometry of the image pixels.
-<P>
-
-If <em>i.rectify</em> starts normally but after some time the following text is seen:
-<br><tt>
-GIS ERROR: error while writing to temp file
-</tt><br>
-the user may try the flag <EM>-c</EM> (or the module needs more free space
-on the hard drive).
-
-
-<H2>SEE ALSO</H2>
-
-The GRASS 4 <em>
-<A HREF="http://grass.itc.it/gdp/imagery/grass4_image_processing.pdf">Image
-Processing manual</A></EM>
-
-<P>
-<EM>
-<A HREF="g.transform.html">g.transform</A>,
-<A HREF="r.proj.html">r.proj</A>,
-<A HREF="v.proj.html">v.proj</A>,
-<A HREF="i.group.html">i.group</A>,
-<A HREF="i.points.html">i.points</A>,
-<A HREF="i.vpoints.html">i.vpoints</A>,
-<A HREF="i.target.html">i.target</A>
-</EM><br>
-<em><a href="gm_georect.html">gis.m: GEORECTIFY TOOL</a></em>
-
-
-<H2>AUTHORS</H2>
-
-William R. Enslin,
-Michigan State University,
-Center for Remote Sensing
-
-<p>
-Modified for GRASS 5.0 by:<BR>
-Luca Palmeri (palmeri at ux1.unipd.it)<BR>
-Bill Hughes<BR>
-Pierre de Mouveaux (pmx at audiovu.com)
-<BR>
-CMD mode by Bob Covill
-
-<p>
-<i>Last changed: $Date$</i>
Copied: grass/trunk/imagery/i.rectify/i.rectify.html (from rev 32770, grass/trunk/imagery/i.rectify/description.html)
===================================================================
--- grass/trunk/imagery/i.rectify/i.rectify.html (rev 0)
+++ grass/trunk/imagery/i.rectify/i.rectify.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,232 @@
+<H2>DESCRIPTION</H2>
+
+
+<EM>i.rectify</EM> uses the control
+points identified in
+<EM><A HREF="i.points.html">i.points</A></EM>
+or
+<EM><A HREF="i.vpoints.html">i.vpoints</A></EM>
+
+to calculate a transformation matrix based on a first,
+second, or third order polynomial and then converts x,y
+cell coordinates to standard map coordinates for each pixel
+in the image. The result is a planimetric image with a
+transformed coordinate system (i.e., a different coordinate
+system than before it was rectified).
+
+<P>
+
+<EM><A HREF="i.points.html">i.points</A></EM>
+or
+<EM><A HREF="i.vpoints.html">i.vpoints</A></EM>
+
+must be run before <EM>i.rectify</EM>, and both programs
+are required to rectify an image. An image must be
+rectified before it can reside in a standard coordinate
+LOCATION, and therefore be analyzed with the other map
+layers in the standard coordinate LOCATION. Upon
+completion of <EM>i.rectify</EM>, the rectified image is
+deposited in the target standard coordinate LOCATION. This
+LOCATION is selected using
+
+<EM><A HREF="i.target.html">i.target</A></EM>.
+
+<H2>Program Prompts</H2>
+
+The first prompt in the program asks for the name of
+the group containing the files to be rectified.
+
+
+<PRE>
+ Enter the group containing files to be rectified
+ Enter 'list' for a list of existing imagery groups
+ Enter 'list -f' for a verbose listing
+ Hit RETURN to cancel request
+ >
+</PRE>
+
+ This is the same imagery group that was selected in
+
+<EM><A HREF="i.points.html">i.points</A></EM>
+or
+<EM><A HREF="i.vpoints.html">i.vpoints</A></EM>
+
+and the group that contains the raster maps with the marked
+points and their associated map coordinates. You are then
+asked to select the raster map(s) within the group to be
+rectified:
+
+
+<PRE>
+Please select the file(s) to rectify by naming an output file
+
+ spot1.1 in mapsetname .............
+ spot1.2 in mapsetname .............
+ spot1.3 in mapsetname .............
+ spotclass1 in mapsetname spotrectify1.
+
+ spotreject1 in mapsetname .............
+
+(enter list by any name to get a list of existing raster maps)
+
+AFTER COMPLETING ALL ANSWERS, HIT <ESC> TO CONTINUE
+ (OR<Ctrl-C> TO CANCEL)
+</PRE>
+
+More than one raster map may be rectified at a time. Each
+cell file should be given a unique output file name.
+
+
+<P>
+
+Next, you are asked to select one of two windows regions:
+
+
+<PRE>
+ Please select one of the following options
+ 1. Use the current window in the target location
+ 2. Determine the smallest window which covers the image
+ >
+</PRE>
+
+The <EM>i.rectify</EM> program will only rectify that
+portion of the image or raster map that occurs within the
+chosen window region, and only that portion of the cell
+file will be relocated in the target database. It is
+important therefore, to check the current mapset window in
+the target LOCATION if choice number one is selected.
+
+<P>
+
+If you are rectifying a file with plans to patch it to
+another file using the GRASS program <em>r.patch</em>,
+choose option number one, the current window in the target
+location. This window, however, must be the default window
+for the target LOCATION. When a file being rectified is
+smaller than the default window in which it is being
+rectified, zeros are added to the rectified file. Patching
+files of the same size that contain 0/non-zero data,
+eliminates the possibility of a no-data line the patched
+result. This is because, when the images are patched, the
+zeros in the image are "covered" with non-zero pixel
+values. When rectifying files that are going to be
+patched, rectify all of the files using the same default
+window.
+
+
+<P>
+
+Select the order of transformation desired with the <b>order</b> option:
+
+<PRE>
+Select order of transformation --> 1st Order 2nd Order 3rd Order
+</PRE>
+
+The program will immediately recalculate the RMSE and the
+number of points required.
+
+<h3>Linear affine transformation (1st order transformation)</h3>
+
+<DL>
+ <DD> x' = ax + by +c
+ <DD> y' = Ax + Bt +C
+</DL>
+
+The a,b,c,A,B,C are determined by least squares regression
+based on the control points entered. This transformation
+applies scaling, translation and rotation. It is NOT a
+general purpose rubber-sheeting, nor is it ortho-photo
+rectification using a DEM, not second order polynomial,
+etc. It can be used if (1) you have geometrically correct
+images, and (2) the terrain or camera distortion effect can
+be ignored.
+
+
+<H3>Polynomial Transformation Matrix (2nd, 3d order transformation)</H3>
+
+The ANALYZE function has been changed to support
+calculating the registration coefficients using a first,
+second, or third order transformation matrix. The number
+of control points required for a selected order of
+transformation (represented by n) is
+
+<DL>
+<DD>((n + 1) * (n + 2) / 2)
+</DL>
+
+or 3, 6, and 10 respectively. It is strongly recommended
+that one or more additional points be identified to allow
+for an overly- determined transformation calculation which
+will generate the Root Mean Square (RMS) error values for
+each included point. The RMS error values for all the
+included control points are immediately recalculated when
+the user selects a different transformation order from the
+menu bar. The polynomial equations are performed using a
+modified Gaussian elimination method.
+
+<H3>Program Execution</H3>
+
+Note: The rectified image or rectified raster maps will be
+located in the target LOCATION when the program is
+completed. The original unrectified files are not modified
+or removed.
+
+<P>
+<!--
+Note: In interactive mode it is possible to define a new file name
+for the target images. This is (currently) not provided in command line
+mode.
+-->
+
+<h2>NOTES</h2>
+
+<EM>i.rectify</EM> uses nearest neighbor resampling during
+the transformation choosing the actual pixel that has its centre nearest to
+the point location in the image. Advantage of this method is that the pixel
+brightness of the image is kept as <EM>i.rectify</EM> rearranges the
+geometry of the image pixels.
+<P>
+
+If <em>i.rectify</em> starts normally but after some time the following text is seen:
+<br><tt>
+GIS ERROR: error while writing to temp file
+</tt><br>
+the user may try the flag <EM>-c</EM> (or the module needs more free space
+on the hard drive).
+
+
+<H2>SEE ALSO</H2>
+
+The GRASS 4 <em>
+<A HREF="http://grass.itc.it/gdp/imagery/grass4_image_processing.pdf">Image
+Processing manual</A></EM>
+
+<P>
+<EM>
+<A HREF="g.transform.html">g.transform</A>,
+<A HREF="r.proj.html">r.proj</A>,
+<A HREF="v.proj.html">v.proj</A>,
+<A HREF="i.group.html">i.group</A>,
+<A HREF="i.points.html">i.points</A>,
+<A HREF="i.vpoints.html">i.vpoints</A>,
+<A HREF="i.target.html">i.target</A>
+</EM><br>
+<em><a href="gm_georect.html">gis.m: GEORECTIFY TOOL</a></em>
+
+
+<H2>AUTHORS</H2>
+
+William R. Enslin,
+Michigan State University,
+Center for Remote Sensing
+
+<p>
+Modified for GRASS 5.0 by:<BR>
+Luca Palmeri (palmeri at ux1.unipd.it)<BR>
+Bill Hughes<BR>
+Pierre de Mouveaux (pmx at audiovu.com)
+<BR>
+CMD mode by Bob Covill
+
+<p>
+<i>Last changed: $Date$</i>
Deleted: grass/trunk/imagery/i.rgb.his/description.html
===================================================================
--- grass/trunk/imagery/i.rgb.his/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/imagery/i.rgb.his/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,29 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-
-<EM>i.rgb.his</EM> is an image processing program that
-processes three input raster map layers as red, green, and
-blue components and produces three output raster map layers
-representing the hue, intensity, and saturation of the
-data. The output raster map layers are created by a
-standard red-green-blue (rgb) to hue-intensity-saturation
-(his) color transformation. Each output raster map layer
-is given a linear gray scale color table. The current
-geographic region definition and mask settings are
-respected.
-
-<H2>SEE ALSO</H2>
-
-<EM><A HREF="hsv.rgb.sh.html">hsv.rgb.sh</A></EM><br>
-<EM><A HREF="i.his.rgb.html">i.his.rgb</A></EM><br>
-<EM><A HREF="rgb.hsv.sh.html">rgb.hsv.sh</A></EM>
-
-<H2>AUTHOR</H2>
-
-David Satnik, GIS Laboratory,
-Central Washington University,
-<BR>
-with acknowledgements to Ali Vali, Space Research
-Center, for the core routine.
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/imagery/i.rgb.his/i.rgb.his.html (from rev 32770, grass/trunk/imagery/i.rgb.his/description.html)
===================================================================
--- grass/trunk/imagery/i.rgb.his/i.rgb.his.html (rev 0)
+++ grass/trunk/imagery/i.rgb.his/i.rgb.his.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,29 @@
+<H2>DESCRIPTION</H2>
+
+
+<EM>i.rgb.his</EM> is an image processing program that
+processes three input raster map layers as red, green, and
+blue components and produces three output raster map layers
+representing the hue, intensity, and saturation of the
+data. The output raster map layers are created by a
+standard red-green-blue (rgb) to hue-intensity-saturation
+(his) color transformation. Each output raster map layer
+is given a linear gray scale color table. The current
+geographic region definition and mask settings are
+respected.
+
+<H2>SEE ALSO</H2>
+
+<EM><A HREF="hsv.rgb.sh.html">hsv.rgb.sh</A></EM><br>
+<EM><A HREF="i.his.rgb.html">i.his.rgb</A></EM><br>
+<EM><A HREF="rgb.hsv.sh.html">rgb.hsv.sh</A></EM>
+
+<H2>AUTHOR</H2>
+
+David Satnik, GIS Laboratory,
+Central Washington University,
+<BR>
+with acknowledgements to Ali Vali, Space Research
+Center, for the core routine.
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/imagery/i.smap/shapiro/description.html
===================================================================
--- grass/trunk/imagery/i.smap/shapiro/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/imagery/i.smap/shapiro/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,198 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-
-The <EM>i.smap</EM> program is used to segment
-multispectral images using a spectral class model known as
-a Gaussian mixture distribution. Since Gaussian mixture
-distributions include conventional multivariate Gaussian
-distributions, this program may also be used to segment
-multispectral images based on simple spectral mean and
-covariance parameters.
-
-<P>
-
-<EM>i.smap</EM> has two modes of operation. The first mode
-is the sequential maximum a posteriori (SMAP) mode
-[<A HREF="#ref1">1</A>,<A HREF="#ref2">2</A>]. The SMAP
-segmentation algorithm attempts to improve segmentation
-accuracy by segmenting the image into regions rather than
-segmenting each pixel separately
-(see <A HREF="#notes">NOTES</A>).
-
-
-<P>
-
-The second mode is the more conventional maximum likelihood (ML)
-classification which classifies each pixel separately,
-but requires somewhat less computation. This mode is selected with
-the <B>-m</B> flag (see <A HREF="#mflag.html">below</A>).
-
-<H2>OPTIONS</H2>
-
-<H3>Flags:</H3>
-
-<DL>
-
-<DT><B>-m</B></A>
-
-<DD>Use maximum likelihood estimation (instead of smap).
-Normal operation is to use SMAP estimation (see
-<A HREF="#notes">NOTES</A>).
-
-<DT><B>-q</B>
-
-<DD>Run quietly, without printing messages about program
-progress. Without this flag, messages will be printed (to
-stderr) as the program progresses.
-
-</DL>
-
-
-<H3>Parameters:</H3>
-
-<DL>
-<DT><B>group=</B><EM>name</EM>
-
-<DD>imagery group<BR>
-The imagery group that defines the image to be classified.
-
-<DT><B>subgroup=</B><EM>name</EM>
-
-<DD>imagery subgroup<BR>
-The subgroup within the group specified that specifies the
-subset of the band files that are to be used as image data
-to be classified.
-
-<DT><B>signaturefile=</B><EM>name</EM>
-
-<DD>imagery signaturefile<BR>
-The signature file that contains the spectral signatures (i.e., the
-statistics) for the classes to be identified in the image.
-This signature file is produced by the program
-<EM><A HREF="i.gensigset.html">i.gensigset</A></EM>
-(see <A HREF="#notes">NOTES</A>).
-
-<DT><B>blocksize=</B><EM>value</EM>
-
-<DD>size of submatrix to process at one time<BR>
-default: 128<BR>
-This option specifies the size of the "window" to be used when
-reading the image data.
-
-<P>
-
-This program was written to be nice about memory usage
-without influencing the resultant classification. This
-option allows the user to control how much memory is used.
-More memory may mean faster (or slower) operation depending
-on how much real memory your machine has and how much
-virtual memory the program uses.
-
-<P>
-
-The size of the submatrix used in segmenting the image has
-a principle function of controlling memory usage; however,
-it also can have a subtle effect on the quality of the
-segmentation in the smap mode. The smoothing parameters
-for the smap segmentation are estimated separately for each
-submatrix. Therefore, if the image has regions with
-qualitatively different behavior, (e.g., natural woodlands
-and man-made agricultural fields) it may be useful to use a
-submatrix small enough so that different smoothing
-parameters may be used for each distinctive region of the
-image.
-
-<P>
-
-The submatrix size has no effect on the performance of the
-ML segmentation method.
-
-<DT><B>output=</B><EM>name</EM>
-
-<DD>output raster map.<BR>
-The name of a raster map that will contain the
-classification results. This new raster map layer will
-contain categories that can be related to landcover
-categories on the ground.
-
-</DL>
-
-<H2>INTERACTIVE MODE</H2>
-
-If none of the arguments are specified on the command line,
-<EM>i.smap</EM> will interactively prompt for the names of
-the maps and files.
-
-<A NAME="notes"><H2>NOTES</H2></A>
-
-The SMAP algorithm exploits the fact that nearby pixels in
-an image are likely to have the same class. It works by
-segmenting the image at various scales or resolutions and
-using the coarse scale segmentations to guide the finer
-scale segmentations. In addition to reducing the number of
-misclassifications, the SMAP algorithm generally produces
-segmentations with larger connected regions of a fixed
-class which may be useful in some applications.
-
-<P>
-
-The amount of smoothing that is performed in the
-segmentation is dependent of the behavior of the data in
-the image. If the data suggests that the nearby pixels
-often change class, then the algorithm will adaptively
-reduce the amount of smoothing. This ensures that
-excessively large regions are not formed.
-
-<P>
-
-The module i.smap does not support MASKed or NULL cells. Therefore
-it might be necessary to create a copy of the classification results
-using e.g. r.mapcalc.
-<p>
-r.mapcalc MASKed_map=classification results
-
-<H2>REFERENCES</H2>
-
-<OL>
-<LI>C. Bouman and M. Shapiro,
-"Multispectral Image Segmentation using a Multiscale Image Model",
-<EM>Proc. of IEEE Int'l Conf. on Acoust., Speech and Sig. Proc.,</EM>
-pp. III-565 - III-568, San Francisco, California, March
-23-26, 1992.
-
-<LI>C. Bouman and M. Shapiro 1994,
-"A Multiscale Random Field
-Model for Bayesian Image Segmentation",
-<EM>IEEE Trans. on Image Processing., 3(2), 162-177"</EM>
-
-<LI>McCauley, J.D. and B.A. Engel 1995,
-"Comparison of Scene Segmentations: SMAP, ECHO and Maximum Likelyhood",
-<EM>IEEE Trans. on Geoscience and Remote Sensing, 33(6): 1313-1316.</EM>
-</OL>
-
-<H2>SEE ALSO</H2>
-
-<EM><A HREF="i.group.html">i.group</A></EM>
-for creating groups and subgroups
-
-<P>
-
-<EM><A HREF="r.mapcalc.html">r.mapcalc</A></EM>
-to copy classification result in order to cut out MASKed subareas
-
-<P>
-
-<EM><A HREF="i.gensigset.html">i.gensigset</A></EM>
-to generate the signature file required by this program
-
-<H2>AUTHORS</H2>
-
-<a href=http://dynamo.ecn.purdue.edu/~bouman/software/segmentation/>Charles Bouman,
-School of Electrical Engineering, Purdue University</a>
-
-<BR>
-Michael Shapiro,
-U.S.Army Construction Engineering
-Research Laboratory
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/imagery/i.smap/shapiro/i.smap.html (from rev 32770, grass/trunk/imagery/i.smap/shapiro/description.html)
===================================================================
--- grass/trunk/imagery/i.smap/shapiro/i.smap.html (rev 0)
+++ grass/trunk/imagery/i.smap/shapiro/i.smap.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,198 @@
+<H2>DESCRIPTION</H2>
+
+
+The <EM>i.smap</EM> program is used to segment
+multispectral images using a spectral class model known as
+a Gaussian mixture distribution. Since Gaussian mixture
+distributions include conventional multivariate Gaussian
+distributions, this program may also be used to segment
+multispectral images based on simple spectral mean and
+covariance parameters.
+
+<P>
+
+<EM>i.smap</EM> has two modes of operation. The first mode
+is the sequential maximum a posteriori (SMAP) mode
+[<A HREF="#ref1">1</A>,<A HREF="#ref2">2</A>]. The SMAP
+segmentation algorithm attempts to improve segmentation
+accuracy by segmenting the image into regions rather than
+segmenting each pixel separately
+(see <A HREF="#notes">NOTES</A>).
+
+
+<P>
+
+The second mode is the more conventional maximum likelihood (ML)
+classification which classifies each pixel separately,
+but requires somewhat less computation. This mode is selected with
+the <B>-m</B> flag (see <A HREF="#mflag.html">below</A>).
+
+<H2>OPTIONS</H2>
+
+<H3>Flags:</H3>
+
+<DL>
+
+<DT><B>-m</B></A>
+
+<DD>Use maximum likelihood estimation (instead of smap).
+Normal operation is to use SMAP estimation (see
+<A HREF="#notes">NOTES</A>).
+
+<DT><B>-q</B>
+
+<DD>Run quietly, without printing messages about program
+progress. Without this flag, messages will be printed (to
+stderr) as the program progresses.
+
+</DL>
+
+
+<H3>Parameters:</H3>
+
+<DL>
+<DT><B>group=</B><EM>name</EM>
+
+<DD>imagery group<BR>
+The imagery group that defines the image to be classified.
+
+<DT><B>subgroup=</B><EM>name</EM>
+
+<DD>imagery subgroup<BR>
+The subgroup within the group specified that specifies the
+subset of the band files that are to be used as image data
+to be classified.
+
+<DT><B>signaturefile=</B><EM>name</EM>
+
+<DD>imagery signaturefile<BR>
+The signature file that contains the spectral signatures (i.e., the
+statistics) for the classes to be identified in the image.
+This signature file is produced by the program
+<EM><A HREF="i.gensigset.html">i.gensigset</A></EM>
+(see <A HREF="#notes">NOTES</A>).
+
+<DT><B>blocksize=</B><EM>value</EM>
+
+<DD>size of submatrix to process at one time<BR>
+default: 128<BR>
+This option specifies the size of the "window" to be used when
+reading the image data.
+
+<P>
+
+This program was written to be nice about memory usage
+without influencing the resultant classification. This
+option allows the user to control how much memory is used.
+More memory may mean faster (or slower) operation depending
+on how much real memory your machine has and how much
+virtual memory the program uses.
+
+<P>
+
+The size of the submatrix used in segmenting the image has
+a principle function of controlling memory usage; however,
+it also can have a subtle effect on the quality of the
+segmentation in the smap mode. The smoothing parameters
+for the smap segmentation are estimated separately for each
+submatrix. Therefore, if the image has regions with
+qualitatively different behavior, (e.g., natural woodlands
+and man-made agricultural fields) it may be useful to use a
+submatrix small enough so that different smoothing
+parameters may be used for each distinctive region of the
+image.
+
+<P>
+
+The submatrix size has no effect on the performance of the
+ML segmentation method.
+
+<DT><B>output=</B><EM>name</EM>
+
+<DD>output raster map.<BR>
+The name of a raster map that will contain the
+classification results. This new raster map layer will
+contain categories that can be related to landcover
+categories on the ground.
+
+</DL>
+
+<H2>INTERACTIVE MODE</H2>
+
+If none of the arguments are specified on the command line,
+<EM>i.smap</EM> will interactively prompt for the names of
+the maps and files.
+
+<A NAME="notes"><H2>NOTES</H2></A>
+
+The SMAP algorithm exploits the fact that nearby pixels in
+an image are likely to have the same class. It works by
+segmenting the image at various scales or resolutions and
+using the coarse scale segmentations to guide the finer
+scale segmentations. In addition to reducing the number of
+misclassifications, the SMAP algorithm generally produces
+segmentations with larger connected regions of a fixed
+class which may be useful in some applications.
+
+<P>
+
+The amount of smoothing that is performed in the
+segmentation is dependent of the behavior of the data in
+the image. If the data suggests that the nearby pixels
+often change class, then the algorithm will adaptively
+reduce the amount of smoothing. This ensures that
+excessively large regions are not formed.
+
+<P>
+
+The module i.smap does not support MASKed or NULL cells. Therefore
+it might be necessary to create a copy of the classification results
+using e.g. r.mapcalc.
+<p>
+r.mapcalc MASKed_map=classification results
+
+<H2>REFERENCES</H2>
+
+<OL>
+<LI>C. Bouman and M. Shapiro,
+"Multispectral Image Segmentation using a Multiscale Image Model",
+<EM>Proc. of IEEE Int'l Conf. on Acoust., Speech and Sig. Proc.,</EM>
+pp. III-565 - III-568, San Francisco, California, March
+23-26, 1992.
+
+<LI>C. Bouman and M. Shapiro 1994,
+"A Multiscale Random Field
+Model for Bayesian Image Segmentation",
+<EM>IEEE Trans. on Image Processing., 3(2), 162-177"</EM>
+
+<LI>McCauley, J.D. and B.A. Engel 1995,
+"Comparison of Scene Segmentations: SMAP, ECHO and Maximum Likelyhood",
+<EM>IEEE Trans. on Geoscience and Remote Sensing, 33(6): 1313-1316.</EM>
+</OL>
+
+<H2>SEE ALSO</H2>
+
+<EM><A HREF="i.group.html">i.group</A></EM>
+for creating groups and subgroups
+
+<P>
+
+<EM><A HREF="r.mapcalc.html">r.mapcalc</A></EM>
+to copy classification result in order to cut out MASKed subareas
+
+<P>
+
+<EM><A HREF="i.gensigset.html">i.gensigset</A></EM>
+to generate the signature file required by this program
+
+<H2>AUTHORS</H2>
+
+<a href=http://dynamo.ecn.purdue.edu/~bouman/software/segmentation/>Charles Bouman,
+School of Electrical Engineering, Purdue University</a>
+
+<BR>
+Michael Shapiro,
+U.S.Army Construction Engineering
+Research Laboratory
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/imagery/i.target/description.html
===================================================================
--- grass/trunk/imagery/i.target/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/imagery/i.target/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,52 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-<EM>i.target</EM> targets an <A HREF="i.group.html">imagery
-group</a> to a GRASS data base location name and mapset.
-
-A location name and mapset are required for the
-<EM><A HREF="i.rectify.html">i.rectify</A></EM> imagery module, into which
-to write the rectified map just prior to completion of the program;
-<EM>i.target</EM> enables the user to specify this location.
-
-<EM>i.target</EM> must be run before
-<EM><A HREF="i.points.html">i.points</A></EM> and
-<EM><A HREF="i.rectify.html">i.rectify</A></EM>.
-
-<H2>NOTES</H2>
-
-<P>
-The module's first option asks for the name of the
-<A HREF="i.group.html">imagery group</A> that needs a target.
-The imagery group must be present in the user's current mapset.
-
-An <A HREF="i.group.html">imagery group</A> may be targeted to any GRASS
-location.
-<P>
-If a group name is given without setting options, the currently targeted
-group will be displayed.
-
-
-<H2>SEE ALSO</H2>
-
-The GRASS 4 <em>
-<A HREF="http://grass.itc.it/gdp/imagery/grass4_image_processing.pdf">Image
-Processing manual</A></EM>
-
-<P>
-<EM>
-<A HREF="i.group.html">i.group</A><BR>
-<A HREF="i.points.html">i.points</A><BR>
-<A HREF="i.vpoints.html">i.vpoints</A><BR>
-<A HREF="i.rectify.html">i.rectify</A>
-</EM><br>
-<em><a href="gm_georect.html">gis.m: GEORECTIFY TOOL</a></em>
-
-
-<H2>AUTHOR</H2>
-
-Michael Shapiro,
-U.S. Army Construction Engineering Research Laboratory<p>
-Parser support: Bob Covill
-
-<p>
-<i>Last changed: $Date$</i>
Copied: grass/trunk/imagery/i.target/i.target.html (from rev 32770, grass/trunk/imagery/i.target/description.html)
===================================================================
--- grass/trunk/imagery/i.target/i.target.html (rev 0)
+++ grass/trunk/imagery/i.target/i.target.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,52 @@
+<H2>DESCRIPTION</H2>
+
+<EM>i.target</EM> targets an <A HREF="i.group.html">imagery
+group</a> to a GRASS data base location name and mapset.
+
+A location name and mapset are required for the
+<EM><A HREF="i.rectify.html">i.rectify</A></EM> imagery module, into which
+to write the rectified map just prior to completion of the program;
+<EM>i.target</EM> enables the user to specify this location.
+
+<EM>i.target</EM> must be run before
+<EM><A HREF="i.points.html">i.points</A></EM> and
+<EM><A HREF="i.rectify.html">i.rectify</A></EM>.
+
+<H2>NOTES</H2>
+
+<P>
+The module's first option asks for the name of the
+<A HREF="i.group.html">imagery group</A> that needs a target.
+The imagery group must be present in the user's current mapset.
+
+An <A HREF="i.group.html">imagery group</A> may be targeted to any GRASS
+location.
+<P>
+If a group name is given without setting options, the currently targeted
+group will be displayed.
+
+
+<H2>SEE ALSO</H2>
+
+The GRASS 4 <em>
+<A HREF="http://grass.itc.it/gdp/imagery/grass4_image_processing.pdf">Image
+Processing manual</A></EM>
+
+<P>
+<EM>
+<A HREF="i.group.html">i.group</A><BR>
+<A HREF="i.points.html">i.points</A><BR>
+<A HREF="i.vpoints.html">i.vpoints</A><BR>
+<A HREF="i.rectify.html">i.rectify</A>
+</EM><br>
+<em><a href="gm_georect.html">gis.m: GEORECTIFY TOOL</a></em>
+
+
+<H2>AUTHOR</H2>
+
+Michael Shapiro,
+U.S. Army Construction Engineering Research Laboratory<p>
+Parser support: Bob Covill
+
+<p>
+<i>Last changed: $Date$</i>
Deleted: grass/trunk/imagery/i.vpoints/description.html
===================================================================
--- grass/trunk/imagery/i.vpoints/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/imagery/i.vpoints/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,342 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-This program enables the user to identify coordinate pairs of points from a
-vector map or keyboard entry and corresponding points in an image to be
-rectified. The map coordinate values of each point are used to calculate a
-transformation matrix. The operator may then use the
-<EM><a href="i.rectify.html">i.rectify</A></EM> program to rectify the image using
-the transformation matrix coefficients calculated from the control point
-file created in <EM>i.vpoints</EM>. The
-<EM> <a href="i.rectify.html">i.rectify</A></EM> program performs a first, second or
-third order transformation of the image.
-
-<P>
-The first step is to display the unrectified image and
-corresponding vector map data. The operator would then
-mark corresponding control point locations on the image and
-map. To identify the precise location of a point to be
-marked, <EM>i.vpoints</EM> has a zoom option. In addition to
-marking control points on an image to be rectified and
-inputting their world coordinate values using the
-keyboard, <EM>i.vpoints</EM> has the option to simultaneously
-display vector map data available in the targeted database,
-and identify on the vector map the location of the
-corresponding marked points. When this option is chosen,
-the coordinate values are input automatically. Any GRASS
-map layer or vector map in the targeted database LOCATION
-can be displayed using <EM>i.vpoints</EM>. The <EM>i.vpoints</EM> program
-also has the capability of overlaying (i.e., warping) the
-vector data onto the raster image to visually check the
-accuracy of the registration based on the current set of
-active control points. During the process of marking
-points and entering map coordinates, the user can compute
-the RMS (root mean square) error for each point entered.
-The <EM>i.vpoints</EM> program does this by calculating a
-transformation equation (the same one that is calculated in
-the GRASS program
-
-<A HREF="i.rectify.html">i.rectify</A>
-2). Coefficients are
-computed for the equation. The coefficients are then used in the
-equation along with the x,y coordinates of the marked points. The
-results are plugged into an equation for RMS error. The
-interpretation of RMS error is described in the ANALYZE subsection.
-
-
-<P>
-The procedures for marking control points (registration
-points), displaying vector map layers, overlaying vector maps onto
-the raster image, and calculating RMS error are described in the
-following sections .
-
-
-<P>
-To enter the program (the <EM>i.vpoints</EM> program requires the use of a
-graphics monitor) type <EM>i.vpoints</EM>:
-
-
-<DL>
- <DD><B>i.vpoints</B>
-</DL>
-
-The first prompt in the program asks for the imagery group to
-be registered . . .
-
-
-<PRE>
- Enter imagery group to be registered
- Enter 'list' for a list of existing imagery groups
- Enter 'list -f' for a verbose listing
- Hit RETURN to cancel request
- >
-</PRE>
-
-For example,
-
-<DL>
-<DD>><B>list</B>
-</DL>
-
-might produce the following response:
-
-<PRE>
- <list>
- Available groups
- - - - - - - - - - - - - - - - - - - - - - - - - - -
- test
- - - - - - - - - - - - - - - - - - - - - - - - - - -
- hit RETURN to continue -->
-</PRE>
-whereas,
-<DL>
-<DD>><B>list -f</B>
-</DL>
-
-might produce the following response
-
-<PRE>
- Available groups
- - - - - - - - - - - - - - - - - - - - - - - - - - -
- test
- photo in PERMANENT
- res2 in tifftest
- - - - - - - - - - - - - - - - - - - - - - - - - - -
- hit RETURN to continue -->
-</PRE>
-
-The imagery group entered above should contain the files
-that you wish to rectify. After entering the group to be
-registered, the terminal screen displays the message:
-<PRE>
- >test
- <test>
- Use mouse now . . .
-</PRE>
-And the color graphics monitor displays the following
-screen:
-
-<P>
- Any single file in the imagery group may be used to mark
-points, and points can be marked on more than one file in the
-imagery group to accumulate the suggested minimum number of points
-(3 for a 1st order transformation, 6 for a 2nd order, and 10 for a
-3rd order). Any file in the imagery group can be subsequently
-rectified (using <EM><A HREF="i.rectify.html">i.rectify</A></EM>)
-based on the transformation matrix computed from these points.
-
-<P>
- The chosen file is displayed in the upper left quadrant of the
-monitor at a default magnification based on the extent of the
-current active window.
-
-<P>
-
-<B>RASTER IMAGE</B>
-
-<P>
- The raster image option on the menu at the bottom of the
-window allows the user to display any single file in the imagery
-group in the upper right quadrant of the window screen. The option
-provides the same file selection pick list as is presented when you
-first enter the <EM>i.vpoints</EM> program. When you select this option,
-the program will erase the data contained in all of the four
-quadrant windows and will reinitialize all program values.
-
-
-<P>
-
-<B>VECTOR MAPS</B>
-<P>
- The vector maps option on the menu at the bottom of the screen
-allows the user to display vector map data in the upper right
-quadrant of the screen. After selecting the vector map layer to
-display, a menu selection bar appears along the bottom on the
-screen. This pick list is used to select the line color (blue,
-gray, green, red, white, or yellow) for the selected vector data
-layer.
-<P>
-<B>Refresh</B>
-<P>
- The refresh option on the main menu allows the user to
-"refresh" or re-draw the displayed vector data. This function will
-erase all outlines showing the limits of previously zoomed areas.
-A "yes/no" roompt will appear:
-<PRE>
- Refresh Map ? NO YES
-</PRE>
-<P>
-<B>Zoom</B>
-<P>
- To enlarge a raster or vector image, place the mouse cross
-hairs on the word zoom on the main menu and press the left button.
-The following menu will be displayed at the bottom. of the screen:
-<PRE>
- CANCEL BOX POINT Select type of zoom
-</PRE>
-You have the option to identify the map extent of the zoom window
-using either the mouse to define a box, or the mouse to mark a
-center point from which to enlarge the image. The box option first
-prompts you to identify a starting corner for the zoom region and
-then allows you to define the area to be zoomed using a rubber band
-box. The prompts appear as follows...
-<PRE>
- CANCEL Mark the first corner of region
-
- CANCEL Define the region
-</PRE>
-After marking the first corner of the region to be enlarged, hold
-down the left button and move the mouse to change the size and
-shape of the rubber band box. After defining the area to be
-enlarged, press the right button to accept it.
-
-
-<P>
-
-The point method for enlarging an image will display a mouse menu
-to guide you in selecting the appropriate enlargement. To enlarge
-or reduce the magnification factor, place the cursor on the "+" or
-"-" box and press the left button on the mouse.
-<P>
-<P>
-You may zoom either the raster or the vector display.
-<P>
-Upon accepting the new region limits, the raster or vector data are
-redisplayed in either the lower left (raster) or lower right
-(vector) windows.
-<P>
-The extent of the zoomed area is outlined on the unzoomed image in
-the main window area.
-<P>
- While the main menu is displayed, you can mark
-corrosponding control points on the raster and vector
-images or enter map coordinates from the keyboard. If you
-are using coordinates taken from a reference map, circle
-these points and then use whatever means you have available
-to identify as precisely as possible the coordinate values
-for these points. Digitizing software is recommended,
-especially GRASS v.digit. Once you have
-determined the standard coordinates (for example, UTM's) of
-each circled point, you are ready to mark the points on the
-displayed image.
-<P>
- To mark the points on the image, that correspond to the points
-on the standard coordinate map, place the mouse cross hairs on the
-point on the image to be marked (you will probably have to ZOOM to
-find the exact spot) and press the left hand button on the mouse.
-A diamond shaped symbol will be marked on the image. The text
-monitor will display the following screen:
-<PRE>
- Point 1 marked on the image at
- East: 1023.77
- North: -164.41
-
- Enter coordinates as east north:
-</PRE>
-<B>Analyze</B>
-<P>
-
- After a number of points have been marked (a minimum of 4 for
-a 1st order transformation, 7 for a 2nd order, and 11 for a 3rd
-order), the RMS error of the points marked on the image can be
-checked. This is done by placing the cross hairs on the word
-ANALYZE on the main menu at the bottom of the monitor. The
-following error report is superimposed on the monitor:
-<PRE>
-
- error image target
- # col row target east north east north
-
- 1 -0.9 0.0 1.0 1048.5 -144.8 679132.5 4351080.6
- 2 1.0 0.4 1.3 2153.1 -567.2 684314.7 4399001.4
- .
- .
- .
- Overall rms error 76.85
-</PRE>
-
- The RMS error for the image being rectified is recorded under
-the column "error" and subTITLEd "row' and "col". In the above
-report, the marked point number 1 is 0.0 rows and -0.9 columns from
-the predicted location calculated by the transformation equation.
- The RMS error for the target database map is recorded under
-the heading "error" and the subheading "target". This is the RMS
-error for the east and the north coordinate values of the target
-map, but it is represented in the table using one general value.
- The overall RMS error for the image is displayed at the bottom
-of the screen in meters. Points that generate a high RMS error are
-displayed in red on the monitor.
- The x,y coordinate values of the point marked on the image
-being rectified are recorded under the heading "image" and the
-subheadings "east" and "north".
- The standard coordinate values of the point in the target
-database are recorded under the heading "target" and the
-subheadings "east" and "north".
- If the user would like to exclude or include a point, this can
-be accomplished by placing the mouse cross hairs on the point
-number to be included (if the point is absent) or excluded (if the
-point is displayed) and then pressing the left button on the mouse
-twice. When a point is excluded, it is not included in the
-calculation of the RMS error, or included in the final
-transformation matrix. However, it can be retrieved within
-<EM>i.vpoints</EM> at any time by double clicking with the mouse as
-described above.
-<P>
-The following menu appears at the bottom of the monitor:
-<PRE>
- DONE PRINT FILE OVERLAY DELETE ON Transformation -
--> 1st ORDER Double click on point to be DELETED
-</PRE>
-Selecting DELETE ON will toggle the option to DELETE OFF, the
-toggle option is used to allow the user to physically remove a
-control point from the POINTS file instead of just flagging it as
-an non-active reference point.
-<P>
-<B>Overlay</B>
-<P>
-Overlay allows the user to overlay the vector map(s) onto the
-raster image. Overlay can be used to warp (register) and display
-the selected vector map data on top of the raster image contained
-in the upper left window of the color screen. An inverse
-coordinate transformation is performed using the currently active
-order of transformation (i.e., first, second, or third).
-<PRE>
- Overlay vectors on raster image NO YES
-</PRE>
-By selecting the 1st ORDER option, the user may select the order of
-transformation desired:
-<PRE>
- Select order of transformation --> 1st Order 2nd Order 3rd Order
-</PRE>
-The program will immediately recalculate the RMSE and the number of
-points required.
-<P>
-<B>Quit</B>
-<P>
- To exit the <EM>i.vpoints</EM> program, place the mouse cross hairs on
-the word QUIT at the bottom of the monitor and all of the marked
-points (including coordinates) will be saved.
-
-<H2>SEE ALSO</H2>
-
-The GRASS 4 <em>
-<A HREF="http://grass.itc.it/gdp/imagery/grass4_image_processing.pdf">Image
-Processing manual</A></EM>
-
-<P>
-<EM>
-<A HREF="g.mapsets.html">g.mapsets</A><BR>
-<A HREF="i.group.html">i.group</A><BR>
-<A HREF="i.points.html">i.points</A><BR>
-<A HREF="i.rectify.html">i.rectify</A><BR>
-<A HREF="i.target.html">i.target</A>
-</EM><br>
-<em><a href="gm_georect.html">gis.m: GEORECTIFY TOOL</a></em>
-
-
-<H2>AUTHOR</H2>
-
-William R. Enslin, Michigan State University Center for Remote Sensing<br>
-Radim Blazek (update to GRASS 5.7)<BR>
-Hamish Bowman (finish GRASS 6 porting)
-<p>
-<i>Last changed: $Date$</i></p>
Copied: grass/trunk/imagery/i.vpoints/i.vpoints.html (from rev 32770, grass/trunk/imagery/i.vpoints/description.html)
===================================================================
--- grass/trunk/imagery/i.vpoints/i.vpoints.html (rev 0)
+++ grass/trunk/imagery/i.vpoints/i.vpoints.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,342 @@
+<H2>DESCRIPTION</H2>
+
+This program enables the user to identify coordinate pairs of points from a
+vector map or keyboard entry and corresponding points in an image to be
+rectified. The map coordinate values of each point are used to calculate a
+transformation matrix. The operator may then use the
+<EM><a href="i.rectify.html">i.rectify</A></EM> program to rectify the image using
+the transformation matrix coefficients calculated from the control point
+file created in <EM>i.vpoints</EM>. The
+<EM> <a href="i.rectify.html">i.rectify</A></EM> program performs a first, second or
+third order transformation of the image.
+
+<P>
+The first step is to display the unrectified image and
+corresponding vector map data. The operator would then
+mark corresponding control point locations on the image and
+map. To identify the precise location of a point to be
+marked, <EM>i.vpoints</EM> has a zoom option. In addition to
+marking control points on an image to be rectified and
+inputting their world coordinate values using the
+keyboard, <EM>i.vpoints</EM> has the option to simultaneously
+display vector map data available in the targeted database,
+and identify on the vector map the location of the
+corresponding marked points. When this option is chosen,
+the coordinate values are input automatically. Any GRASS
+map layer or vector map in the targeted database LOCATION
+can be displayed using <EM>i.vpoints</EM>. The <EM>i.vpoints</EM> program
+also has the capability of overlaying (i.e., warping) the
+vector data onto the raster image to visually check the
+accuracy of the registration based on the current set of
+active control points. During the process of marking
+points and entering map coordinates, the user can compute
+the RMS (root mean square) error for each point entered.
+The <EM>i.vpoints</EM> program does this by calculating a
+transformation equation (the same one that is calculated in
+the GRASS program
+
+<A HREF="i.rectify.html">i.rectify</A>
+2). Coefficients are
+computed for the equation. The coefficients are then used in the
+equation along with the x,y coordinates of the marked points. The
+results are plugged into an equation for RMS error. The
+interpretation of RMS error is described in the ANALYZE subsection.
+
+
+<P>
+The procedures for marking control points (registration
+points), displaying vector map layers, overlaying vector maps onto
+the raster image, and calculating RMS error are described in the
+following sections .
+
+
+<P>
+To enter the program (the <EM>i.vpoints</EM> program requires the use of a
+graphics monitor) type <EM>i.vpoints</EM>:
+
+
+<DL>
+ <DD><B>i.vpoints</B>
+</DL>
+
+The first prompt in the program asks for the imagery group to
+be registered . . .
+
+
+<PRE>
+ Enter imagery group to be registered
+ Enter 'list' for a list of existing imagery groups
+ Enter 'list -f' for a verbose listing
+ Hit RETURN to cancel request
+ >
+</PRE>
+
+For example,
+
+<DL>
+<DD>><B>list</B>
+</DL>
+
+might produce the following response:
+
+<PRE>
+ <list>
+ Available groups
+ - - - - - - - - - - - - - - - - - - - - - - - - - -
+ test
+ - - - - - - - - - - - - - - - - - - - - - - - - - -
+ hit RETURN to continue -->
+</PRE>
+whereas,
+<DL>
+<DD>><B>list -f</B>
+</DL>
+
+might produce the following response
+
+<PRE>
+ Available groups
+ - - - - - - - - - - - - - - - - - - - - - - - - - -
+ test
+ photo in PERMANENT
+ res2 in tifftest
+ - - - - - - - - - - - - - - - - - - - - - - - - - -
+ hit RETURN to continue -->
+</PRE>
+
+The imagery group entered above should contain the files
+that you wish to rectify. After entering the group to be
+registered, the terminal screen displays the message:
+<PRE>
+ >test
+ <test>
+ Use mouse now . . .
+</PRE>
+And the color graphics monitor displays the following
+screen:
+
+<P>
+ Any single file in the imagery group may be used to mark
+points, and points can be marked on more than one file in the
+imagery group to accumulate the suggested minimum number of points
+(3 for a 1st order transformation, 6 for a 2nd order, and 10 for a
+3rd order). Any file in the imagery group can be subsequently
+rectified (using <EM><A HREF="i.rectify.html">i.rectify</A></EM>)
+based on the transformation matrix computed from these points.
+
+<P>
+ The chosen file is displayed in the upper left quadrant of the
+monitor at a default magnification based on the extent of the
+current active window.
+
+<P>
+
+<B>RASTER IMAGE</B>
+
+<P>
+ The raster image option on the menu at the bottom of the
+window allows the user to display any single file in the imagery
+group in the upper right quadrant of the window screen. The option
+provides the same file selection pick list as is presented when you
+first enter the <EM>i.vpoints</EM> program. When you select this option,
+the program will erase the data contained in all of the four
+quadrant windows and will reinitialize all program values.
+
+
+<P>
+
+<B>VECTOR MAPS</B>
+<P>
+ The vector maps option on the menu at the bottom of the screen
+allows the user to display vector map data in the upper right
+quadrant of the screen. After selecting the vector map layer to
+display, a menu selection bar appears along the bottom on the
+screen. This pick list is used to select the line color (blue,
+gray, green, red, white, or yellow) for the selected vector data
+layer.
+<P>
+<B>Refresh</B>
+<P>
+ The refresh option on the main menu allows the user to
+"refresh" or re-draw the displayed vector data. This function will
+erase all outlines showing the limits of previously zoomed areas.
+A "yes/no" roompt will appear:
+<PRE>
+ Refresh Map ? NO YES
+</PRE>
+<P>
+<B>Zoom</B>
+<P>
+ To enlarge a raster or vector image, place the mouse cross
+hairs on the word zoom on the main menu and press the left button.
+The following menu will be displayed at the bottom. of the screen:
+<PRE>
+ CANCEL BOX POINT Select type of zoom
+</PRE>
+You have the option to identify the map extent of the zoom window
+using either the mouse to define a box, or the mouse to mark a
+center point from which to enlarge the image. The box option first
+prompts you to identify a starting corner for the zoom region and
+then allows you to define the area to be zoomed using a rubber band
+box. The prompts appear as follows...
+<PRE>
+ CANCEL Mark the first corner of region
+
+ CANCEL Define the region
+</PRE>
+After marking the first corner of the region to be enlarged, hold
+down the left button and move the mouse to change the size and
+shape of the rubber band box. After defining the area to be
+enlarged, press the right button to accept it.
+
+
+<P>
+
+The point method for enlarging an image will display a mouse menu
+to guide you in selecting the appropriate enlargement. To enlarge
+or reduce the magnification factor, place the cursor on the "+" or
+"-" box and press the left button on the mouse.
+<P>
+<P>
+You may zoom either the raster or the vector display.
+<P>
+Upon accepting the new region limits, the raster or vector data are
+redisplayed in either the lower left (raster) or lower right
+(vector) windows.
+<P>
+The extent of the zoomed area is outlined on the unzoomed image in
+the main window area.
+<P>
+ While the main menu is displayed, you can mark
+corrosponding control points on the raster and vector
+images or enter map coordinates from the keyboard. If you
+are using coordinates taken from a reference map, circle
+these points and then use whatever means you have available
+to identify as precisely as possible the coordinate values
+for these points. Digitizing software is recommended,
+especially GRASS v.digit. Once you have
+determined the standard coordinates (for example, UTM's) of
+each circled point, you are ready to mark the points on the
+displayed image.
+<P>
+ To mark the points on the image, that correspond to the points
+on the standard coordinate map, place the mouse cross hairs on the
+point on the image to be marked (you will probably have to ZOOM to
+find the exact spot) and press the left hand button on the mouse.
+A diamond shaped symbol will be marked on the image. The text
+monitor will display the following screen:
+<PRE>
+ Point 1 marked on the image at
+ East: 1023.77
+ North: -164.41
+
+ Enter coordinates as east north:
+</PRE>
+<B>Analyze</B>
+<P>
+
+ After a number of points have been marked (a minimum of 4 for
+a 1st order transformation, 7 for a 2nd order, and 11 for a 3rd
+order), the RMS error of the points marked on the image can be
+checked. This is done by placing the cross hairs on the word
+ANALYZE on the main menu at the bottom of the monitor. The
+following error report is superimposed on the monitor:
+<PRE>
+
+ error image target
+ # col row target east north east north
+
+ 1 -0.9 0.0 1.0 1048.5 -144.8 679132.5 4351080.6
+ 2 1.0 0.4 1.3 2153.1 -567.2 684314.7 4399001.4
+ .
+ .
+ .
+ Overall rms error 76.85
+</PRE>
+
+ The RMS error for the image being rectified is recorded under
+the column "error" and subTITLEd "row' and "col". In the above
+report, the marked point number 1 is 0.0 rows and -0.9 columns from
+the predicted location calculated by the transformation equation.
+ The RMS error for the target database map is recorded under
+the heading "error" and the subheading "target". This is the RMS
+error for the east and the north coordinate values of the target
+map, but it is represented in the table using one general value.
+ The overall RMS error for the image is displayed at the bottom
+of the screen in meters. Points that generate a high RMS error are
+displayed in red on the monitor.
+ The x,y coordinate values of the point marked on the image
+being rectified are recorded under the heading "image" and the
+subheadings "east" and "north".
+ The standard coordinate values of the point in the target
+database are recorded under the heading "target" and the
+subheadings "east" and "north".
+ If the user would like to exclude or include a point, this can
+be accomplished by placing the mouse cross hairs on the point
+number to be included (if the point is absent) or excluded (if the
+point is displayed) and then pressing the left button on the mouse
+twice. When a point is excluded, it is not included in the
+calculation of the RMS error, or included in the final
+transformation matrix. However, it can be retrieved within
+<EM>i.vpoints</EM> at any time by double clicking with the mouse as
+described above.
+<P>
+The following menu appears at the bottom of the monitor:
+<PRE>
+ DONE PRINT FILE OVERLAY DELETE ON Transformation -
+-> 1st ORDER Double click on point to be DELETED
+</PRE>
+Selecting DELETE ON will toggle the option to DELETE OFF, the
+toggle option is used to allow the user to physically remove a
+control point from the POINTS file instead of just flagging it as
+an non-active reference point.
+<P>
+<B>Overlay</B>
+<P>
+Overlay allows the user to overlay the vector map(s) onto the
+raster image. Overlay can be used to warp (register) and display
+the selected vector map data on top of the raster image contained
+in the upper left window of the color screen. An inverse
+coordinate transformation is performed using the currently active
+order of transformation (i.e., first, second, or third).
+<PRE>
+ Overlay vectors on raster image NO YES
+</PRE>
+By selecting the 1st ORDER option, the user may select the order of
+transformation desired:
+<PRE>
+ Select order of transformation --> 1st Order 2nd Order 3rd Order
+</PRE>
+The program will immediately recalculate the RMSE and the number of
+points required.
+<P>
+<B>Quit</B>
+<P>
+ To exit the <EM>i.vpoints</EM> program, place the mouse cross hairs on
+the word QUIT at the bottom of the monitor and all of the marked
+points (including coordinates) will be saved.
+
+<H2>SEE ALSO</H2>
+
+The GRASS 4 <em>
+<A HREF="http://grass.itc.it/gdp/imagery/grass4_image_processing.pdf">Image
+Processing manual</A></EM>
+
+<P>
+<EM>
+<A HREF="g.mapsets.html">g.mapsets</A><BR>
+<A HREF="i.group.html">i.group</A><BR>
+<A HREF="i.points.html">i.points</A><BR>
+<A HREF="i.rectify.html">i.rectify</A><BR>
+<A HREF="i.target.html">i.target</A>
+</EM><br>
+<em><a href="gm_georect.html">gis.m: GEORECTIFY TOOL</a></em>
+
+
+<H2>AUTHOR</H2>
+
+William R. Enslin, Michigan State University Center for Remote Sensing<br>
+Radim Blazek (update to GRASS 5.7)<BR>
+Hamish Bowman (finish GRASS 6 porting)
+<p>
+<i>Last changed: $Date$</i></p>
Deleted: grass/trunk/imagery/i.zc/description.html
===================================================================
--- grass/trunk/imagery/i.zc/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/imagery/i.zc/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,113 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-
-<EM>i.zc</EM> is an image processing program used for edge
-detection. The raster map produced shows the location of
-"boundaries" on the input map. Boundaries tend to be found
-in regions of changing cell values and tend to run
-perpendicular to the direction of the slope. The algorithm
-used for edge detection is one of the "zero-crossing"
-algorithms and is discussed briefly below.
-
-
-<P>
-
-This program will be run interactively if the user types
-<B>i.zc</B> without program arguments on the command line.
-In this event, the program will prompt the user for
-parameter values using the standard interface described in
-the manual entry for <EM><A HREF="parser.html">parser</A></EM>.
-Alternately, the
-user can run the program non-interactively by specifying
-program parameter values on the command line.
-
-
-<H2>OPTIONS</H2>
-
-<H3>Parameters:</H3>
-
-<DL>
-
-<DT><B>input_map=</B><EM>name</EM>
-
-<DD>Name of input raster map layer.
-
-<DT><B>zc_map=</B><EM>name</EM>
-
-<DD>Name of raster map layer to be used for zero-crossing values.
-
-<DT><B>width=</B><EM>value</EM>
-
-<DD>This parameter determines the x-y extent of the
-Gaussian filter. The default value is 9; higher and lower
-values can be tested by the user. Increasing the width
-will result in finding "edges" representing more gradual
-changes in cell values.
-
-<BR>
-
-Default: 9
-
-<DT><B>threshold=</B><EM>value</EM>
-
-<DD>This parameter determines the "sensitivity" of the
-Gaussian filter. The default value is 10; higher and
-lower values can be tested by the user. Increasing the
-threshold value will result in fewer edges being found.
-
-<BR>
-
-Default: 10
-
-<DT><B>orientations=</B><EM>value</EM>
-
-<DD>This value is the number of azimuth directions the
-cells on the output raster map layer are categorized into
-(similar to the aspect raster map layer produced by the
-
-<EM><A HREF="r.slope.aspect.html">r.slope.aspect</A></EM>
-
-program). For example, a value of 16 would result in
-detected edges being categorized into one of 16 bins
-depending on the direction of the edge at that point.
-
-<BR>
-
-Default: 1
-
-</DL>
-
-The current region definition and mask settings are respected
-when reading the input map.
-
-<H2>NOTES</H2>
-
-The procedure to find the "edges" in the image is as follows:
-
-<OL>
-<LI> The Fourier transform of the image is taken,
-<LI> The Fourier transform of the Laplacian of a two-dimensional
-Gaussian function is used to filter the transformed image,
-<LI> The result is run through an inverse Fourier transform,
-<LI> The resulting image is traversed in search of places where the image
-changes from positive to negative or from negative to positive,
-<LI> Each cell in the map where the value crosses zero
-(with a change in value greater than the threshold value)
-is marked as an edge and an orientation is assigned to it.
-The resulting raster map layer is output.
-</OL>
-
-<H2>SEE ALSO</H2>
-
-<EM><A HREF="i.fft.html">i.fft</A></EM>,
-<EM><A HREF="i.ifft.html">i.ifft</A></EM>,
-<EM><A HREF="r.mapcalc.html">r.mapcalc</A></EM>,
-<EM><A HREF="r.mfilter.html">r.mfilter</A></EM>,
-<EM><A HREF="r.slope.aspect.html">r.slope.aspect</A></EM>
-
-<H2>AUTHOR</H2>
-
-David Satnik, GIS Laboratory,
-Central Washington University
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/imagery/i.zc/i.zc.html (from rev 32770, grass/trunk/imagery/i.zc/description.html)
===================================================================
--- grass/trunk/imagery/i.zc/i.zc.html (rev 0)
+++ grass/trunk/imagery/i.zc/i.zc.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,113 @@
+<H2>DESCRIPTION</H2>
+
+
+<EM>i.zc</EM> is an image processing program used for edge
+detection. The raster map produced shows the location of
+"boundaries" on the input map. Boundaries tend to be found
+in regions of changing cell values and tend to run
+perpendicular to the direction of the slope. The algorithm
+used for edge detection is one of the "zero-crossing"
+algorithms and is discussed briefly below.
+
+
+<P>
+
+This program will be run interactively if the user types
+<B>i.zc</B> without program arguments on the command line.
+In this event, the program will prompt the user for
+parameter values using the standard interface described in
+the manual entry for <EM><A HREF="parser.html">parser</A></EM>.
+Alternately, the
+user can run the program non-interactively by specifying
+program parameter values on the command line.
+
+
+<H2>OPTIONS</H2>
+
+<H3>Parameters:</H3>
+
+<DL>
+
+<DT><B>input_map=</B><EM>name</EM>
+
+<DD>Name of input raster map layer.
+
+<DT><B>zc_map=</B><EM>name</EM>
+
+<DD>Name of raster map layer to be used for zero-crossing values.
+
+<DT><B>width=</B><EM>value</EM>
+
+<DD>This parameter determines the x-y extent of the
+Gaussian filter. The default value is 9; higher and lower
+values can be tested by the user. Increasing the width
+will result in finding "edges" representing more gradual
+changes in cell values.
+
+<BR>
+
+Default: 9
+
+<DT><B>threshold=</B><EM>value</EM>
+
+<DD>This parameter determines the "sensitivity" of the
+Gaussian filter. The default value is 10; higher and
+lower values can be tested by the user. Increasing the
+threshold value will result in fewer edges being found.
+
+<BR>
+
+Default: 10
+
+<DT><B>orientations=</B><EM>value</EM>
+
+<DD>This value is the number of azimuth directions the
+cells on the output raster map layer are categorized into
+(similar to the aspect raster map layer produced by the
+
+<EM><A HREF="r.slope.aspect.html">r.slope.aspect</A></EM>
+
+program). For example, a value of 16 would result in
+detected edges being categorized into one of 16 bins
+depending on the direction of the edge at that point.
+
+<BR>
+
+Default: 1
+
+</DL>
+
+The current region definition and mask settings are respected
+when reading the input map.
+
+<H2>NOTES</H2>
+
+The procedure to find the "edges" in the image is as follows:
+
+<OL>
+<LI> The Fourier transform of the image is taken,
+<LI> The Fourier transform of the Laplacian of a two-dimensional
+Gaussian function is used to filter the transformed image,
+<LI> The result is run through an inverse Fourier transform,
+<LI> The resulting image is traversed in search of places where the image
+changes from positive to negative or from negative to positive,
+<LI> Each cell in the map where the value crosses zero
+(with a change in value greater than the threshold value)
+is marked as an edge and an orientation is assigned to it.
+The resulting raster map layer is output.
+</OL>
+
+<H2>SEE ALSO</H2>
+
+<EM><A HREF="i.fft.html">i.fft</A></EM>,
+<EM><A HREF="i.ifft.html">i.ifft</A></EM>,
+<EM><A HREF="r.mapcalc.html">r.mapcalc</A></EM>,
+<EM><A HREF="r.mfilter.html">r.mfilter</A></EM>,
+<EM><A HREF="r.slope.aspect.html">r.slope.aspect</A></EM>
+
+<H2>AUTHOR</H2>
+
+David Satnik, GIS Laboratory,
+Central Washington University
+
+<p><i>Last changed: $Date$</i>
Modified: grass/trunk/lib/cairodriver/Makefile
===================================================================
--- grass/trunk/lib/cairodriver/Makefile 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/lib/cairodriver/Makefile 2008-08-15 06:16:42 UTC (rev 32772)
@@ -2,19 +2,17 @@
include $(MODULE_TOPDIR)/include/Make/Platform.make
-PACKAGE ="libcairodriver"
-DEFS=-DPACKAGE=\"$(PACKAGE)\"
-
-EXTRA_CFLAGS=-I../driver $(CAIROINC) $(PICFLAGS) $(DEFS)
+EXTRA_CFLAGS=-I../driver $(CAIROINC)
EXTRA_LIBS=$(DRIVERLIB) $(GISLIB) $(CAIROLIB)
# added constant to /include/Make/Grass.make.in
LIB_NAME = $(CAIRODRIVER_LIBNAME)
+PGM = cairodriver
include $(MODULE_TOPDIR)/include/Make/Lib.make
ifneq ($(USE_CAIRO),)
-default: lib
+default: lib htmldir
else
default:
endif
Copied: grass/trunk/lib/cairodriver/cairodriver.html (from rev 32770, grass/trunk/lib/cairodriver/description.html)
===================================================================
--- grass/trunk/lib/cairodriver/cairodriver.html (rev 0)
+++ grass/trunk/lib/cairodriver/cairodriver.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,174 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<HTML>
+<HEAD>
+ <TITLE>Cairo driver</TITLE>
+ <META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
+ <link rel="stylesheet" href="grassdocs.css" type="text/css">
+</HEAD>
+<BODY bgColor=white>
+
+<img src="grass_logo.png" alt="GRASS logo"><hr align=center size=6 noshade>
+
+<H2>NAME</H2>
+<EM><B>Cairo driver</B></EM> - driver for bitmap or vector output using
+the Cairo graphics library.
+<BR>
+<EM>(drivers)</EM>
+
+<H2>DESCRIPTION</H2>
+
+The Cairo driver generates PNG, BMP, PPM, PS, PDF or SVG images from GRASS
+display commands, using the
+<A HREF="http://www.cairographics.org/">Cairo graphics library</A>.
+The image format is selected from the extension of the output file.
+
+<P>
+It is started as 'pseudo' monitor (output to an image file) and when
+stopped, all output from previously used display commands are written to
+the output file.
+
+<H2>USAGE</H2>
+
+<H3>Environment variables</H3>
+
+Several environment variables affect the operation of the Cairo driver:
+
+<UL>
+ <LI><B>GRASS_WIDTH=xxx</B><BR>
+ the width of the image.
+ </LI><BR>
+ <LI><B>GRASS_HEIGHT=yyy</B><BR>
+ the height of the image.
+ </LI><BR>
+ <LI><B>GRASS_CAIROFILE=filename</B><BR>
+ the name and format of the resulting image file, default is
+ <tt>map.png</tt>.<BR>
+ The image format is determined from the file extension.<BR>
+ Supported bitmap formats:
+ <UL>
+ <LI><B>.png</B> - Portable Network Graphics (PNG)</LI>
+ <LI><B>.bmp</B> - Windows Bitmap (BMP)</LI>
+ <LI><B>.ppm</B> - Portable Pixmap (PPM)</LI>
+ </UL>
+ Supported vector formats:
+ <UL>
+ <LI><B>.pdf</B> - Portable Document Format (PDF)</LI>
+ <LI><B>.ps</B> - PostScript (PS)</LI>
+ <LI><B>.svg</B> - Scalable Vector Graphics (SVG)</LI>
+ </UL>
+ (Note: Some formats may not be available, depending on your platform and
+ the Cairo library that GRASS was built with.)
+ </LI><BR>
+ <LI><B>GRASS_BACKGROUNDCOLOR=RRGGBB</B><BR>
+ specifies the background color to use in RGB
+ notation (hex values). Default is <b>FFFFFF</b> (white).
+ </LI><BR>
+ <LI><B>GRASS_TRANSPARENT=[TRUE|FALSE]</B><BR>
+ sets transparent background on (TRUE) or off (FALSE, default).
+ </LI><BR>
+ <LI><B>GRASS_AUTO_WRITE=[TRUE|FALSE]</B><BR>
+ if set to <tt>TRUE</tt>, the image file will be written after each
+ operation (i.e. whenever a client disconnects), rather than
+ only being written out when the driver terminates.<BR>
+ (Note: This only applies to bitmap formats - vector formats
+ are always written directly to file).
+ </LI><BR>
+ <LI><B>GRASS_CAIRO_READ</B><BR>
+ if <tt>TRUE</tt>, the Cairo driver will initialize the image from
+ the contents of GRASS_CAIROFILE.<BR>
+ (Note: This is only supported for bitmap formats)
+ </LI><BR>
+ <LI><B>GRASS_CAIRO_MAPPED</B><BR>
+ if <tt>TRUE</tt>, the Cairo driver will map GRASS_CAIROFILE as its framebuffer,
+ rather than using memory. This only works with BMP files.
+ </LI>
+</UL>
+
+<H3>Examples</H3>
+
+Example using the driver directly (bash-syntax):
+<div class="code"><PRE>
+export GRASS_CAIROFILE=spearfish.png
+export GRASS_WIDTH=800
+export GRASS_HEIGHT=800
+
+d.mon start=cairo
+d.rast map=elevation.10m
+d.vect map=streams width=1 color=blue fcolor=aqua type=area,line
+d.vect map=roads width=2
+d.mon stop=cairo
+</PRE></div>
+
+Example using <em><a href="d.out.file.html">d.out.file</a></em>:
+<div class="code"><PRE>
+d.mon x0
+d.rast map=elevation.10m
+d.vect map=streams width=1 color=blue fcolor=aqua type=area,line
+d.vect map=roads width=2
+
+d.out.file -c sf_cairo format=png size=800,800
+</PRE></div>
+
+<P>
+A more complicated example using <em><a href="d.out.file.html">d.out.file</a></em>:
+<div class="code"><PRE>
+r.shaded.relief map=elevation.dem
+r.watershed elev=elevation.dem basin=watershed.basin thresh=10000
+
+d.mon x1
+d.shadedmap rel=elevation.dem.shade drape=watershed.basin bright=30
+d.vect streams color=aqua fcolor=aqua type=area,line
+d.vect roads where="label ~ 'light-duty road'" color=grey
+d.vect roads where="label ~ 'unimproved'" color=orange
+d.vect roads where="label ~ 'secondary highway'" color=100:100:100 width=2
+d.vect roads where="label ~ 'primary highway'" color=50:50:50 width=2
+d.vect railroads col=red width=2
+d.vect roads where="label = 'interstate'" color=black width=3
+
+d.vect archsites icon=basic/star size=25 fcolor=yellow
+
+d.font Andale_Mono
+echo "Spearfish, SD" | d.text color=black at=28,53 -b
+
+d.out.file -c sf_cairo2 format=png
+</PRE></div>
+
+
+<H2>NOTES</H2>
+
+The driver is still in development. Enable it by specifying
+<CODE>--with-cairo</CODE> when configuring GRASS. This
+requires a reasonably recent version of the Cairo libraries
+and a working pkg-config.
+
+<P>
+Antialiasing is enabled by default for bitmap formats. There is
+currently no way of disabling this.
+
+<P>
+Cairo supports true vector format output whenever possible. However,
+if the selected format doesn't support a necessary feature, Cairo may
+fall back on rendering a bitmap representation of the image wrapped in
+the selected vector format.
+
+<P>
+Cairo driver output via <em><A HREF="d.out.file.html">d.out.file</A></em>
+is supported via the -c flag.</P>
+
+<h2>SEE ALSO</h2>
+<EM>
+<A HREF="htmlmapdriver.html">HTMLMAP driver</A>,
+<A HREF="pngdriver.html">PNG driver</A>,
+<A HREF="psdriver.html">PostScript driver</A>,
+<A href="xdriver.html">XDRIVER</A>
+<BR>
+<A HREF="d.frame.html">d.frame</A>,
+<A href="d.mon.html">d.mon</A>,
+<A href="d.rast.html">d.rast</A>,
+<A href="d.vect.html">d.vect</A>
+<A href="d.out.file.html">d.out.file</A>
+</EM>
+
+<H2>AUTHOR</H2>
+Lars Ahlzen <<I>lars (at) ahlzen.com</I>><BR>
+and the GRASS Development Team.
Deleted: grass/trunk/lib/cairodriver/description.html
===================================================================
--- grass/trunk/lib/cairodriver/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/lib/cairodriver/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,174 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
- <TITLE>Cairo driver</TITLE>
- <META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
- <link rel="stylesheet" href="grassdocs.css" type="text/css">
-</HEAD>
-<BODY bgColor=white>
-
-<img src="grass_logo.png" alt="GRASS logo"><hr align=center size=6 noshade>
-
-<H2>NAME</H2>
-<EM><B>Cairo driver</B></EM> - driver for bitmap or vector output using
-the Cairo graphics library.
-<BR>
-<EM>(drivers)</EM>
-
-<H2>DESCRIPTION</H2>
-
-The Cairo driver generates PNG, BMP, PPM, PS, PDF or SVG images from GRASS
-display commands, using the
-<A HREF="http://www.cairographics.org/">Cairo graphics library</A>.
-The image format is selected from the extension of the output file.
-
-<P>
-It is started as 'pseudo' monitor (output to an image file) and when
-stopped, all output from previously used display commands are written to
-the output file.
-
-<H2>USAGE</H2>
-
-<H3>Environment variables</H3>
-
-Several environment variables affect the operation of the Cairo driver:
-
-<UL>
- <LI><B>GRASS_WIDTH=xxx</B><BR>
- the width of the image.
- </LI><BR>
- <LI><B>GRASS_HEIGHT=yyy</B><BR>
- the height of the image.
- </LI><BR>
- <LI><B>GRASS_CAIROFILE=filename</B><BR>
- the name and format of the resulting image file, default is
- <tt>map.png</tt>.<BR>
- The image format is determined from the file extension.<BR>
- Supported bitmap formats:
- <UL>
- <LI><B>.png</B> - Portable Network Graphics (PNG)</LI>
- <LI><B>.bmp</B> - Windows Bitmap (BMP)</LI>
- <LI><B>.ppm</B> - Portable Pixmap (PPM)</LI>
- </UL>
- Supported vector formats:
- <UL>
- <LI><B>.pdf</B> - Portable Document Format (PDF)</LI>
- <LI><B>.ps</B> - PostScript (PS)</LI>
- <LI><B>.svg</B> - Scalable Vector Graphics (SVG)</LI>
- </UL>
- (Note: Some formats may not be available, depending on your platform and
- the Cairo library that GRASS was built with.)
- </LI><BR>
- <LI><B>GRASS_BACKGROUNDCOLOR=RRGGBB</B><BR>
- specifies the background color to use in RGB
- notation (hex values). Default is <b>FFFFFF</b> (white).
- </LI><BR>
- <LI><B>GRASS_TRANSPARENT=[TRUE|FALSE]</B><BR>
- sets transparent background on (TRUE) or off (FALSE, default).
- </LI><BR>
- <LI><B>GRASS_AUTO_WRITE=[TRUE|FALSE]</B><BR>
- if set to <tt>TRUE</tt>, the image file will be written after each
- operation (i.e. whenever a client disconnects), rather than
- only being written out when the driver terminates.<BR>
- (Note: This only applies to bitmap formats - vector formats
- are always written directly to file).
- </LI><BR>
- <LI><B>GRASS_CAIRO_READ</B><BR>
- if <tt>TRUE</tt>, the Cairo driver will initialize the image from
- the contents of GRASS_CAIROFILE.<BR>
- (Note: This is only supported for bitmap formats)
- </LI><BR>
- <LI><B>GRASS_CAIRO_MAPPED</B><BR>
- if <tt>TRUE</tt>, the Cairo driver will map GRASS_CAIROFILE as its framebuffer,
- rather than using memory. This only works with BMP files.
- </LI>
-</UL>
-
-<H3>Examples</H3>
-
-Example using the driver directly (bash-syntax):
-<div class="code"><PRE>
-export GRASS_CAIROFILE=spearfish.png
-export GRASS_WIDTH=800
-export GRASS_HEIGHT=800
-
-d.mon start=cairo
-d.rast map=elevation.10m
-d.vect map=streams width=1 color=blue fcolor=aqua type=area,line
-d.vect map=roads width=2
-d.mon stop=cairo
-</PRE></div>
-
-Example using <em><a href="d.out.file.html">d.out.file</a></em>:
-<div class="code"><PRE>
-d.mon x0
-d.rast map=elevation.10m
-d.vect map=streams width=1 color=blue fcolor=aqua type=area,line
-d.vect map=roads width=2
-
-d.out.file -c sf_cairo format=png size=800,800
-</PRE></div>
-
-<P>
-A more complicated example using <em><a href="d.out.file.html">d.out.file</a></em>:
-<div class="code"><PRE>
-r.shaded.relief map=elevation.dem
-r.watershed elev=elevation.dem basin=watershed.basin thresh=10000
-
-d.mon x1
-d.shadedmap rel=elevation.dem.shade drape=watershed.basin bright=30
-d.vect streams color=aqua fcolor=aqua type=area,line
-d.vect roads where="label ~ 'light-duty road'" color=grey
-d.vect roads where="label ~ 'unimproved'" color=orange
-d.vect roads where="label ~ 'secondary highway'" color=100:100:100 width=2
-d.vect roads where="label ~ 'primary highway'" color=50:50:50 width=2
-d.vect railroads col=red width=2
-d.vect roads where="label = 'interstate'" color=black width=3
-
-d.vect archsites icon=basic/star size=25 fcolor=yellow
-
-d.font Andale_Mono
-echo "Spearfish, SD" | d.text color=black at=28,53 -b
-
-d.out.file -c sf_cairo2 format=png
-</PRE></div>
-
-
-<H2>NOTES</H2>
-
-The driver is still in development. Enable it by specifying
-<CODE>--with-cairo</CODE> when configuring GRASS. This
-requires a reasonably recent version of the Cairo libraries
-and a working pkg-config.
-
-<P>
-Antialiasing is enabled by default for bitmap formats. There is
-currently no way of disabling this.
-
-<P>
-Cairo supports true vector format output whenever possible. However,
-if the selected format doesn't support a necessary feature, Cairo may
-fall back on rendering a bitmap representation of the image wrapped in
-the selected vector format.
-
-<P>
-Cairo driver output via <em><A HREF="d.out.file.html">d.out.file</A></em>
-is supported via the -c flag.</P>
-
-<h2>SEE ALSO</h2>
-<EM>
-<A HREF="htmlmapdriver.html">HTMLMAP driver</A>,
-<A HREF="pngdriver.html">PNG driver</A>,
-<A HREF="psdriver.html">PostScript driver</A>,
-<A href="xdriver.html">XDRIVER</A>
-<BR>
-<A HREF="d.frame.html">d.frame</A>,
-<A href="d.mon.html">d.mon</A>,
-<A href="d.rast.html">d.rast</A>,
-<A href="d.vect.html">d.vect</A>
-<A href="d.out.file.html">d.out.file</A>
-</EM>
-
-<H2>AUTHOR</H2>
-Lars Ahlzen <<I>lars (at) ahlzen.com</I>><BR>
-and the GRASS Development Team.
Modified: grass/trunk/lib/db/sqlp/Makefile
===================================================================
--- grass/trunk/lib/db/sqlp/Makefile 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/lib/db/sqlp/Makefile 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,6 +1,7 @@
MODULE_TOPDIR = ../../..
LIB_NAME = $(SQLP_LIBNAME)
+PGM = sql
LIB_OBJS = \
alloc.o \
@@ -14,9 +15,7 @@
include $(MODULE_TOPDIR)/include/Make/Lib.make
-default: lib
- $(MKDIR) $(GISBASE)/docs/html
- $(INSTALL_DATA) description.html $(GISBASE)/docs/html/sql.html
+default: lib htmldir
y.tab.c y.tab.h: yac.y
$(YACC) -d -v yac.y
Deleted: grass/trunk/lib/db/sqlp/description.html
===================================================================
--- grass/trunk/lib/db/sqlp/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/lib/db/sqlp/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,150 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-<head>
-<title>SQL support in GRASS GIS</title>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link rel="stylesheet" href="grassdocs.css" type="text/css">
-</head>
-
-<!-- This file is lib/db/sqlp/description.html -->
-
-<body bgcolor="white">
-
-<img src="grass_logo.png" alt="GRASS logo"><hr align=center size=6 noshade>
-
-<H2>SQL support in GRASS GIS</H2>
-
-GRASS can use various RDBMS and embedded databases.
-SQL queries are directly passed to the underlying
-database system.
-The set of supported SQL commands depends on the RDMBS
-and driver selected.
-
-<H2>Drivers</H2>
-The list of available drivers can vary in various binary
-distributions of GRASS.
-<p>
-
-<table border=1 >
-<tr><td><a href="grass-dbf.html">dbf</a></td><td>DBF files. Data are stored in DBF files.</td>
-<td><a href="http://shapelib.maptools.org/dbf_api.html">http://shapelib.maptools.org/dbf_api.html</a></td></tr>
-
-<tr><td><a href="grass-sqlite.html">sqlite</a></td><td>SQLite embedded database.</td>
-<td><a href="http://sqlite.org/">http://sqlite.org/</a></td></tr>
-
-<tr><td><a href="grass-pg.html">pg</a></td><td>PostgreSQL RDBMS.</td>
-<td><a href="http://postgresql.org/">http://postgresql.org/</a></td></tr>
-
-<tr><td><a href="grass-mysql.html">mysql</a></td><td>MySQL RDBMS.</td>
-<td><a href="http://mysql.org/">http://mysql.org/</a></td></tr>
-
-<tr><td><a href="grass-mesql.html">mesql</a></td><td>MySQL embedded database.</td>
-<td><a href="http://mysql.org/">http://mysql.org/</a></td></tr>
-
-<tr><td><a href="grass-odbc.html">odbc</a></td><td>UnixODBC. (PostgreSQL, Oracle, etc.)</td>
-<td><a href="http://www.unixodbc.org/">http://www.unixodbc.org/</a></td></tr>
-
-</table>
-
-
-<H2>NOTES</H2>
-
-<ul>
-<li> SQL does not support '.' (dots) in table names.
-<li> Supported table name characters are only:<br>
- [A-Za-z][A-Za-z0-9_]*
-<li> A table name must start with a character, not a number.
-<li> Text-string matching requires the text part to be 'single quoted'.
-When run from the command line multiple queries should be contained
-in "double quotes". e.g.<br>
-<div class="code"><pre>
-d.vect map where="individual='juvenile' and area='beach'"
-</pre></div>
-<li> An error message such as "dbmi: Protocol error" either indicates an invalid column name
- or an unsupported column type (then the GRASS SQL parser needs to be extended).
-<li> DBF column names are limited to 10 characters (DBF API definition)
-</ul>
-
-
-<h2>EXAMPLES</h2>
-
-Display all vector points except for LAMAR valley and <i>extensive trapping</i> (brackets are superfluous in this example):
-<div class="code"><pre>
-d.vect trapping_sites_points fcol=black icon=basic/diamond col=white size=13 \
- where="valley <> 'LAMAR' OR (valley = 'LAMAR' AND description = 'extensive trapping')"
-</pre></div>
-
-<p>
-Select all attributes from table where str1 column values are not 'No Name':
-<div class="code"><pre>
-echo "SELECT * FROM archsites WHERE str1 <> 'No Name'" | db.select
-</pre></div>
-<p>
-
-
-<p>Example of subquery expressions from a list (does not work for DBF driver):
-<div class="code"><pre>
-v.db.select mysites where="id IN ('P04', 'P05')"
-</pre></div>
-
-
-<p>Example of pattern matching:
-<div class="code"><pre>
-# match exactly number of characters (here: 2), does not work for DBF driver:
-v.db.select mysites where="id LIKE 'P__'"
-
-#define wildcard:
-v.db.select mysites where="id LIKE 'P%'"
-</pre></div>
-
-<p>Example of null handling:
-<div class="code"><pre>
-v.db.addcol map=roads col="nulltest int"
-v.db.update map=roads col=nulltest value=1 where="cat > 2"
-d.vect roads where="nulltest is null"
-v.db.update map=roads col=nulltest value=2 where="cat <= 2"
-</pre></div>
-
-
-<p>Examples of complex expressions in updates (using v.db.* modules):
-<div class="code"><pre>
-v.db.addcol map=roads col="exprtest double precision"
-v.db.update map=roads col=exprtest value=cat/nulltest
-v.db.update map=roads col=exprtest value=cat/nulltest+cat where=cat=1
-</pre></div>
-
-
-<p>Examples of complex expressions in updates (using db.* modules):
-<div class="code"><pre>
-echo "UPDATE roads SET exprtest=null"
-echo "UPDATE roads SET exprtest=cat/2" | db.execute
-echo "UPDATE roads SET exprtest=cat/2+cat/3" | db.execute
-echo "UPDATE roads SET exprtest=NULL WHERE cat>2" | db.execute
-echo "UPDATE roads SET exprtest=cat/3*(cat+1) WHERE exprtest IS NULL" | db.execute"
-</pre></div>
-
-
-<p>
-Instead of creating and updating new columns with an expression,
-you can use the expression directly in a command:
-<div class="code"><pre>
-d.vect roads where="(cat/3*(cat+1))>8"
-d.vect roads where="cat>exprtest"
-</pre></div>
-
-
-
-<h2>SEE ALSO</h2>
-
-<a href="databaseintro.html">Database management in GRASS GIS</a>,<BR>
-<a href="database.html">Help pages for database modules</a>,<BR>
-<a href=http://www.redhat.com/docs/manuals/database/RHDB-2.1-Manual/sql/sqlreference.html>SQL
- Guide and Reference</a> (Red Hat)
-
-
-<p><i>Last changed: $Date$</i></p>
-<HR>
-<BR><a href=index.html>Help Index</a>
-<P>© 2008 <a href="http://grass.osgeo.org">GRASS Development Team</a></P>
-</body>
-</html>
Copied: grass/trunk/lib/db/sqlp/sql.html (from rev 32770, grass/trunk/lib/db/sqlp/description.html)
===================================================================
--- grass/trunk/lib/db/sqlp/sql.html (rev 0)
+++ grass/trunk/lib/db/sqlp/sql.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,150 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<head>
+<title>SQL support in GRASS GIS</title>
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
+<link rel="stylesheet" href="grassdocs.css" type="text/css">
+</head>
+
+<!-- This file is lib/db/sqlp/description.html -->
+
+<body bgcolor="white">
+
+<img src="grass_logo.png" alt="GRASS logo"><hr align=center size=6 noshade>
+
+<H2>SQL support in GRASS GIS</H2>
+
+GRASS can use various RDBMS and embedded databases.
+SQL queries are directly passed to the underlying
+database system.
+The set of supported SQL commands depends on the RDMBS
+and driver selected.
+
+<H2>Drivers</H2>
+The list of available drivers can vary in various binary
+distributions of GRASS.
+<p>
+
+<table border=1 >
+<tr><td><a href="grass-dbf.html">dbf</a></td><td>DBF files. Data are stored in DBF files.</td>
+<td><a href="http://shapelib.maptools.org/dbf_api.html">http://shapelib.maptools.org/dbf_api.html</a></td></tr>
+
+<tr><td><a href="grass-sqlite.html">sqlite</a></td><td>SQLite embedded database.</td>
+<td><a href="http://sqlite.org/">http://sqlite.org/</a></td></tr>
+
+<tr><td><a href="grass-pg.html">pg</a></td><td>PostgreSQL RDBMS.</td>
+<td><a href="http://postgresql.org/">http://postgresql.org/</a></td></tr>
+
+<tr><td><a href="grass-mysql.html">mysql</a></td><td>MySQL RDBMS.</td>
+<td><a href="http://mysql.org/">http://mysql.org/</a></td></tr>
+
+<tr><td><a href="grass-mesql.html">mesql</a></td><td>MySQL embedded database.</td>
+<td><a href="http://mysql.org/">http://mysql.org/</a></td></tr>
+
+<tr><td><a href="grass-odbc.html">odbc</a></td><td>UnixODBC. (PostgreSQL, Oracle, etc.)</td>
+<td><a href="http://www.unixodbc.org/">http://www.unixodbc.org/</a></td></tr>
+
+</table>
+
+
+<H2>NOTES</H2>
+
+<ul>
+<li> SQL does not support '.' (dots) in table names.
+<li> Supported table name characters are only:<br>
+ [A-Za-z][A-Za-z0-9_]*
+<li> A table name must start with a character, not a number.
+<li> Text-string matching requires the text part to be 'single quoted'.
+When run from the command line multiple queries should be contained
+in "double quotes". e.g.<br>
+<div class="code"><pre>
+d.vect map where="individual='juvenile' and area='beach'"
+</pre></div>
+<li> An error message such as "dbmi: Protocol error" either indicates an invalid column name
+ or an unsupported column type (then the GRASS SQL parser needs to be extended).
+<li> DBF column names are limited to 10 characters (DBF API definition)
+</ul>
+
+
+<h2>EXAMPLES</h2>
+
+Display all vector points except for LAMAR valley and <i>extensive trapping</i> (brackets are superfluous in this example):
+<div class="code"><pre>
+d.vect trapping_sites_points fcol=black icon=basic/diamond col=white size=13 \
+ where="valley <> 'LAMAR' OR (valley = 'LAMAR' AND description = 'extensive trapping')"
+</pre></div>
+
+<p>
+Select all attributes from table where str1 column values are not 'No Name':
+<div class="code"><pre>
+echo "SELECT * FROM archsites WHERE str1 <> 'No Name'" | db.select
+</pre></div>
+<p>
+
+
+<p>Example of subquery expressions from a list (does not work for DBF driver):
+<div class="code"><pre>
+v.db.select mysites where="id IN ('P04', 'P05')"
+</pre></div>
+
+
+<p>Example of pattern matching:
+<div class="code"><pre>
+# match exactly number of characters (here: 2), does not work for DBF driver:
+v.db.select mysites where="id LIKE 'P__'"
+
+#define wildcard:
+v.db.select mysites where="id LIKE 'P%'"
+</pre></div>
+
+<p>Example of null handling:
+<div class="code"><pre>
+v.db.addcol map=roads col="nulltest int"
+v.db.update map=roads col=nulltest value=1 where="cat > 2"
+d.vect roads where="nulltest is null"
+v.db.update map=roads col=nulltest value=2 where="cat <= 2"
+</pre></div>
+
+
+<p>Examples of complex expressions in updates (using v.db.* modules):
+<div class="code"><pre>
+v.db.addcol map=roads col="exprtest double precision"
+v.db.update map=roads col=exprtest value=cat/nulltest
+v.db.update map=roads col=exprtest value=cat/nulltest+cat where=cat=1
+</pre></div>
+
+
+<p>Examples of complex expressions in updates (using db.* modules):
+<div class="code"><pre>
+echo "UPDATE roads SET exprtest=null"
+echo "UPDATE roads SET exprtest=cat/2" | db.execute
+echo "UPDATE roads SET exprtest=cat/2+cat/3" | db.execute
+echo "UPDATE roads SET exprtest=NULL WHERE cat>2" | db.execute
+echo "UPDATE roads SET exprtest=cat/3*(cat+1) WHERE exprtest IS NULL" | db.execute"
+</pre></div>
+
+
+<p>
+Instead of creating and updating new columns with an expression,
+you can use the expression directly in a command:
+<div class="code"><pre>
+d.vect roads where="(cat/3*(cat+1))>8"
+d.vect roads where="cat>exprtest"
+</pre></div>
+
+
+
+<h2>SEE ALSO</h2>
+
+<a href="databaseintro.html">Database management in GRASS GIS</a>,<BR>
+<a href="database.html">Help pages for database modules</a>,<BR>
+<a href=http://www.redhat.com/docs/manuals/database/RHDB-2.1-Manual/sql/sqlreference.html>SQL
+ Guide and Reference</a> (Red Hat)
+
+
+<p><i>Last changed: $Date$</i></p>
+<HR>
+<BR><a href=index.html>Help Index</a>
+<P>© 2008 <a href="http://grass.osgeo.org">GRASS Development Team</a></P>
+</body>
+</html>
Modified: grass/trunk/lib/htmldriver/Makefile
===================================================================
--- grass/trunk/lib/htmldriver/Makefile 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/lib/htmldriver/Makefile 2008-08-15 06:16:42 UTC (rev 32772)
@@ -2,13 +2,12 @@
include $(MODULE_TOPDIR)/include/Make/Platform.make
-PACKAGE ="libhtmldriver"
-DEFS=-DPACKAGE=\"$(PACKAGE)\"
-EXTRA_CFLAGS=-I../driver $(PICFLAGS) $(DEFS)
+EXTRA_CFLAGS=-I../driver
EXTRA_LIBS=$(DRIVERLIB) $(GISLIB)
LIB_NAME = $(HTMLDRIVER_LIBNAME)
+PGM = htmldriver
include $(MODULE_TOPDIR)/include/Make/Lib.make
-default: lib
+default: lib htmldir
Deleted: grass/trunk/lib/htmldriver/description.html
===================================================================
--- grass/trunk/lib/htmldriver/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/lib/htmldriver/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,190 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
- <TITLE>HTMLMAP driver</TITLE>
- <META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
- <link rel="stylesheet" href="grassdocs.css" type="text/css">
-</HEAD>
-<BODY bgColor=white>
-
-<img src="grass_logo.png" alt="GRASS logo"><hr align=center size=6 noshade>
-
-<H2>NAME</H2>
-
-<EM><B>HTMLMAP driver</B></EM> - driver to create HTML image maps.
-<BR><EM>(drivers)</EM>
-
-<H2>DESCRIPTION</H2>
-
-The HTMLMAP driver allows the generation of HTML image maps
-for area vector data. HTML image maps are used in conjunction with images to
-provide unique URL targets for different portions of an image. The HTMLMAP
-driver can create both client-side image maps embedded into HTML files, or
-server-side image maps used by web server software.
-<P>
-Note that GRASS display commands that require the MOUSE will not work
-correctly (or at all!)
-<P>
-Polygons can at most have 100 vertices (this limit imposed by HTML image map
-formats, see <B>GRASS_HTMLMAXPOINTS</B> below.) The driver will attempt to
-trim polygons that have more that 100
-vertices by removing vertices with the least amount of angle to the next
-vertice. Also, any polygon that is entirely bounded by another polygon will be
-discarded.
-<P>
-Text written to the driver before polygons are used as the HREF tag for all
-subsequent polygons written. All polygons that exist in a vector map will have
-the same HREF tag.
-<P>
-The only GRASS display commands that should be used with this driver are:
-<UL>
- <LI><a href="d.text.html">d.text</A>
- - pass href information for resulting image maps.</LI>
- <LI><a href="d.vect.html">d.vect</A>
- - draw polygons from a vector map.</LI>
-</UL>
-
-<H2>USAGE</H2>
-
-<H3>Environment variables</H3>Several environment variables effect the operation
-of HTMLMAP.
-
-<UL>
- <LI><B>GRASS_WIDTH=xxx</B><BR>the width of the image map (default is
- 640).
- </LI><BR>
- <LI><B>GRASS_HEIGHT=yyy</B><BR>the height of the image map (default is
- 480).
- </LI><BR>
- <LI><B>GRASS_HTMLTYPE=type</B><BR>the type of image mape to create (default is
- CLIENT):
- <UL>
- <DD><TT><B>CLIENT</B></TT> Netscape/IE client-side image map.
- (NAME="map")<BR>
- <DD><TT><B>APACHE</B></TT> Apache/NCSA server-side image
- map.<BR>
- <DD><TT><B>RAW</B></TT> Raw url
- and polygon vertices ( <I>url x1 y1 x2 y2
- ..... </I>), suitable for conversion to CERN server format, or any other
- format with user supplied conversion program.</DD>
- </UL>
- </LI><BR>
- <LI><B>GRASS_HTMLFILE=filename</B><BR>
- specifies the resulting file to store
- the html image map, default is <tt>htmlmap</tt>. Files without absolute path
- names are written in the current directory where the driver was started.
- <BR>
- <em>Any existing file of the same name is overwritten without
- warning.</em>
- </LI><BR>
- <LI><B>GRASS_HTMLMINDIST=n</B><BR>specifies the minimum distance in pixels
- that a point must change from the previous point to keep in the list of
- vertices for a polygon. The default is <tt>2</tt>, which means that a
- point's x and y difference from the previous point must change by a number
- of pixels greater than this value. This parameter helps to eliminate
- closely spaced points.
- </LI><BR>
- <LI><B>GRASS_HTMLMINBBOX=n</B><BR>specifies the minimum bounding box
- dimensions to record a polygon as a clickable area.
- The default is <tt>2</tt>, which means that a polygon with a bounding box
- of less than this value is not included. This parameter helps to eliminate
- polygons than are a point or line.
- </LI><BR>
- <LI><B>GRASS_HTMLMAXPOINTS=n</B><BR>specifies the maximum number of
- vertices included in a polygon's clickable area.
- The default is <tt>99</tt>. Some browsers can only accomodate polygons of
- 100 vertices or less. The HTMLMAP driver automatically ensures that a
- polygon is closed by making the last point the same as the first
- point.</LI><BR>
-</UL>
-
-<H3>Typical usage</H3>
-<UL>
- <LI>Start up the driver
-<DIV class="code"><PRE>
-d.mon start=HTMLMAP
-</PRE></DIV>
- </LI>
- <LI>Display text strings (HREF's) and polygons
-<DIV class="code"><PRE>
-echo "http://www.no-such-place.net/area51/" | d.text
-d.vect map=area51
-echo "http://www.roswell-nm.net/little/green/men.html" | d.text
-d.vect map=roswell
-</PRE></div>
- <LI>Stop the driver when all polygon have been displayed. This will cause a file
- named 'htmlmap' to be created in your current directory.
-<DIV class="code"><PRE>
-d.mon stop=HTMLMAP
-</PRE></DIV>
- <LI>You will also want to create an image for your image map. Use the PNG
- driver and other utilities to create .gif or .jpg files.
- <i>The following example is somewhat out of date and refers to options
- available in GRASS 5.</i>
-<DIV class="code"><PRE>
-# using previous GRASS_WIDTH & GRASS_HEIGHT
-d.mon start=PNG
-d.mon select=PNG
-d.rast map=terrain
-d.vect map=area51 fillcolor=white linecolor=blue
-d.vect map=roswell fillcolor=yellow linecolor=blue
-d.vect map=states color=green
-d.vect map=roads color=black
-d.mon stop=PNG
-<!-- ???? FIXME -->
-# make the region the same as the newly created cell for ppm export
-g.region save=saved.reg
-g.region raster=D_cell
-r.out.ppm -q input=D_cell output=alien.ppm
-
-# use the netpbm utilities to create a gif (quantize if needed)
-ppmquant 128 <alien.ppm | ppmtogif >alien.gif
-
-# assemble some html with the image and the image map
-echo '<html><body><img src="alien.gif" usemap="#map">' >alien.html
-cat htmlmap >>alien.html
-echo '</body></html>' >>alien.html
-
-# don't forget to reset your region
-g.region region=saved.reg
-
-# take a look and test it out
-netscape file:`pwd`/alien.html &
-</PRE></DIV>
- </LI>
-</UL>
-
-<H2>NOTES</H2>
-
-HTMLMAP was adapted from the CELL driver in GRASS 4.3.
-Point-in-polygon test code was lifted from Randolph Franklin's web page, see
-<UL>
- <LI><a href="http://www.ecse.rpi.edu/Homepages/wrf/">http://www.ecse.rpi.edu/Homepages/wrf/</A></LI>
- <LI><a href="http://www.ecse.rpi.edu/Homepages/wrf/research/geom/pnpoly.html">http://www.ecse.rpi.edu/Homepages/wrf/research/geom/pnpoly.html</A></LI>
-</UL>
-
-<P>
-If you create an HTML file with two or more images and image maps, you will
-need to edit the map names. The HTMLMAP driver creates its map with the name
-<tt>map</tt>. A small sed script can easily change the map name:
-
-<PRE>
- sed -e 's/NAME="map"/NAME="foomap"/' < htmlmap > foomap.html
-</PRE>
-
-<H2>SEE ALSO</H2>
-
-<EM>
- <a href="displaydrivers.html">Display drivers</a>
- <br>
- <a href="pngdriver.html">PNG driver</A>,
- <a href="psdriver.html">PostScript driver</A>,
- <a href="xdriver.html">XDRIVER</A>
- <BR>
- <A href="d.mon.html">d.mon</A>,
- <a href="d.text.html">d.text</A>,
- <a href="d.vect.html">d.vect</A>
-</EM>
-
-<p>
-<i>Last changed: $Date: 2008-03-23 14:34:53 +0000 (Sun, 23 Mar 2008) $</i>
Copied: grass/trunk/lib/htmldriver/htmldriver.html (from rev 32770, grass/trunk/lib/htmldriver/description.html)
===================================================================
--- grass/trunk/lib/htmldriver/htmldriver.html (rev 0)
+++ grass/trunk/lib/htmldriver/htmldriver.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,190 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<HTML>
+<HEAD>
+ <TITLE>HTMLMAP driver</TITLE>
+ <META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
+ <link rel="stylesheet" href="grassdocs.css" type="text/css">
+</HEAD>
+<BODY bgColor=white>
+
+<img src="grass_logo.png" alt="GRASS logo"><hr align=center size=6 noshade>
+
+<H2>NAME</H2>
+
+<EM><B>HTMLMAP driver</B></EM> - driver to create HTML image maps.
+<BR><EM>(drivers)</EM>
+
+<H2>DESCRIPTION</H2>
+
+The HTMLMAP driver allows the generation of HTML image maps
+for area vector data. HTML image maps are used in conjunction with images to
+provide unique URL targets for different portions of an image. The HTMLMAP
+driver can create both client-side image maps embedded into HTML files, or
+server-side image maps used by web server software.
+<P>
+Note that GRASS display commands that require the MOUSE will not work
+correctly (or at all!)
+<P>
+Polygons can at most have 100 vertices (this limit imposed by HTML image map
+formats, see <B>GRASS_HTMLMAXPOINTS</B> below.) The driver will attempt to
+trim polygons that have more that 100
+vertices by removing vertices with the least amount of angle to the next
+vertice. Also, any polygon that is entirely bounded by another polygon will be
+discarded.
+<P>
+Text written to the driver before polygons are used as the HREF tag for all
+subsequent polygons written. All polygons that exist in a vector map will have
+the same HREF tag.
+<P>
+The only GRASS display commands that should be used with this driver are:
+<UL>
+ <LI><a href="d.text.html">d.text</A>
+ - pass href information for resulting image maps.</LI>
+ <LI><a href="d.vect.html">d.vect</A>
+ - draw polygons from a vector map.</LI>
+</UL>
+
+<H2>USAGE</H2>
+
+<H3>Environment variables</H3>Several environment variables effect the operation
+of HTMLMAP.
+
+<UL>
+ <LI><B>GRASS_WIDTH=xxx</B><BR>the width of the image map (default is
+ 640).
+ </LI><BR>
+ <LI><B>GRASS_HEIGHT=yyy</B><BR>the height of the image map (default is
+ 480).
+ </LI><BR>
+ <LI><B>GRASS_HTMLTYPE=type</B><BR>the type of image mape to create (default is
+ CLIENT):
+ <UL>
+ <DD><TT><B>CLIENT</B></TT> Netscape/IE client-side image map.
+ (NAME="map")<BR>
+ <DD><TT><B>APACHE</B></TT> Apache/NCSA server-side image
+ map.<BR>
+ <DD><TT><B>RAW</B></TT> Raw url
+ and polygon vertices ( <I>url x1 y1 x2 y2
+ ..... </I>), suitable for conversion to CERN server format, or any other
+ format with user supplied conversion program.</DD>
+ </UL>
+ </LI><BR>
+ <LI><B>GRASS_HTMLFILE=filename</B><BR>
+ specifies the resulting file to store
+ the html image map, default is <tt>htmlmap</tt>. Files without absolute path
+ names are written in the current directory where the driver was started.
+ <BR>
+ <em>Any existing file of the same name is overwritten without
+ warning.</em>
+ </LI><BR>
+ <LI><B>GRASS_HTMLMINDIST=n</B><BR>specifies the minimum distance in pixels
+ that a point must change from the previous point to keep in the list of
+ vertices for a polygon. The default is <tt>2</tt>, which means that a
+ point's x and y difference from the previous point must change by a number
+ of pixels greater than this value. This parameter helps to eliminate
+ closely spaced points.
+ </LI><BR>
+ <LI><B>GRASS_HTMLMINBBOX=n</B><BR>specifies the minimum bounding box
+ dimensions to record a polygon as a clickable area.
+ The default is <tt>2</tt>, which means that a polygon with a bounding box
+ of less than this value is not included. This parameter helps to eliminate
+ polygons than are a point or line.
+ </LI><BR>
+ <LI><B>GRASS_HTMLMAXPOINTS=n</B><BR>specifies the maximum number of
+ vertices included in a polygon's clickable area.
+ The default is <tt>99</tt>. Some browsers can only accomodate polygons of
+ 100 vertices or less. The HTMLMAP driver automatically ensures that a
+ polygon is closed by making the last point the same as the first
+ point.</LI><BR>
+</UL>
+
+<H3>Typical usage</H3>
+<UL>
+ <LI>Start up the driver
+<DIV class="code"><PRE>
+d.mon start=HTMLMAP
+</PRE></DIV>
+ </LI>
+ <LI>Display text strings (HREF's) and polygons
+<DIV class="code"><PRE>
+echo "http://www.no-such-place.net/area51/" | d.text
+d.vect map=area51
+echo "http://www.roswell-nm.net/little/green/men.html" | d.text
+d.vect map=roswell
+</PRE></div>
+ <LI>Stop the driver when all polygon have been displayed. This will cause a file
+ named 'htmlmap' to be created in your current directory.
+<DIV class="code"><PRE>
+d.mon stop=HTMLMAP
+</PRE></DIV>
+ <LI>You will also want to create an image for your image map. Use the PNG
+ driver and other utilities to create .gif or .jpg files.
+ <i>The following example is somewhat out of date and refers to options
+ available in GRASS 5.</i>
+<DIV class="code"><PRE>
+# using previous GRASS_WIDTH & GRASS_HEIGHT
+d.mon start=PNG
+d.mon select=PNG
+d.rast map=terrain
+d.vect map=area51 fillcolor=white linecolor=blue
+d.vect map=roswell fillcolor=yellow linecolor=blue
+d.vect map=states color=green
+d.vect map=roads color=black
+d.mon stop=PNG
+<!-- ???? FIXME -->
+# make the region the same as the newly created cell for ppm export
+g.region save=saved.reg
+g.region raster=D_cell
+r.out.ppm -q input=D_cell output=alien.ppm
+
+# use the netpbm utilities to create a gif (quantize if needed)
+ppmquant 128 <alien.ppm | ppmtogif >alien.gif
+
+# assemble some html with the image and the image map
+echo '<html><body><img src="alien.gif" usemap="#map">' >alien.html
+cat htmlmap >>alien.html
+echo '</body></html>' >>alien.html
+
+# don't forget to reset your region
+g.region region=saved.reg
+
+# take a look and test it out
+netscape file:`pwd`/alien.html &
+</PRE></DIV>
+ </LI>
+</UL>
+
+<H2>NOTES</H2>
+
+HTMLMAP was adapted from the CELL driver in GRASS 4.3.
+Point-in-polygon test code was lifted from Randolph Franklin's web page, see
+<UL>
+ <LI><a href="http://www.ecse.rpi.edu/Homepages/wrf/">http://www.ecse.rpi.edu/Homepages/wrf/</A></LI>
+ <LI><a href="http://www.ecse.rpi.edu/Homepages/wrf/research/geom/pnpoly.html">http://www.ecse.rpi.edu/Homepages/wrf/research/geom/pnpoly.html</A></LI>
+</UL>
+
+<P>
+If you create an HTML file with two or more images and image maps, you will
+need to edit the map names. The HTMLMAP driver creates its map with the name
+<tt>map</tt>. A small sed script can easily change the map name:
+
+<PRE>
+ sed -e 's/NAME="map"/NAME="foomap"/' < htmlmap > foomap.html
+</PRE>
+
+<H2>SEE ALSO</H2>
+
+<EM>
+ <a href="displaydrivers.html">Display drivers</a>
+ <br>
+ <a href="pngdriver.html">PNG driver</A>,
+ <a href="psdriver.html">PostScript driver</A>,
+ <a href="xdriver.html">XDRIVER</A>
+ <BR>
+ <A href="d.mon.html">d.mon</A>,
+ <a href="d.text.html">d.text</A>,
+ <a href="d.vect.html">d.vect</A>
+</EM>
+
+<p>
+<i>Last changed: $Date: 2008-03-23 14:34:53 +0000 (Sun, 23 Mar 2008) $</i>
Modified: grass/trunk/lib/pngdriver/Makefile
===================================================================
--- grass/trunk/lib/pngdriver/Makefile 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/lib/pngdriver/Makefile 2008-08-15 06:16:42 UTC (rev 32772)
@@ -2,12 +2,11 @@
include $(MODULE_TOPDIR)/include/Make/Platform.make
-PACKAGE ="libpngdriver"
-DEFS=-DPACKAGE=\"$(PACKAGE)\"
-EXTRA_CFLAGS=$(GETHOSTNAME) $(ZLIBINCPATH) $(PNGINC) -I../driver $(PICFLAGS) $(DEFS)
+EXTRA_CFLAGS=$(GETHOSTNAME) $(ZLIBINCPATH) $(PNGINC) -I../driver
EXTRA_LIBS=$(DRIVERLIB) $(GISLIB) $(PNGLIB)
LIB_NAME = $(PNGDRIVER_LIBNAME)
+PGM = cairodriver
LIB_OBJS = \
Box.o \
@@ -37,4 +36,4 @@
include $(MODULE_TOPDIR)/include/Make/Lib.make
-default: lib
+default: lib htmldir
Deleted: grass/trunk/lib/pngdriver/description.html
===================================================================
--- grass/trunk/lib/pngdriver/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/lib/pngdriver/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,125 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
- <TITLE>PNG driver</TITLE>
- <META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
- <link rel="stylesheet" href="grassdocs.css" type="text/css">
-</HEAD>
-<BODY bgColor=white>
-
-<img src="grass_logo.png" alt="GRASS logo"><hr align=center size=6 noshade>
-
-<H2>NAME</H2>
-<EM><B> PNG driver</B></EM> - driver to create PNG and PPM images.
-<BR><EM>(drivers)</EM>
-
-<H2>DESCRIPTION</H2>
-
-The PNG driver generates PNG and PPM images from GRASS display commands.
-Per default PNG files are written with this driver. It is started as 'pseudo' monitor
-(image file instead) and when stopped, all output from previously used
-display commands are written to the PNG image file.
-
-<H2>USAGE</H2>
-
-<H3>Environment variables</H3>
-Several environment variables effect the operation
-of the PNG driver.
-<UL>
- <LI><B>GRASS_WIDTH=xxx</B><BR>
- the width of the image map (default is 640).</LI><BR>
- <LI><B>GRASS_HEIGHT=yyy</B><BR>
- the height of the image map (default is 480).</LI><BR>
- <LI><B>GRASS_PNGFILE=filename</B><BR>
- the filename to put the resulting image in, default is <tt>map.png</tt>.
- If you set GRASS_PNGFILE to a filename which ends in ".ppm", a PPM
- file will be created.<br><br>
- <LI><B>GRASS_BACKGROUNDCOLOR=RRGGBB</B><BR>
- specifies the background color to use in RGB
- notation (hex values). Default is <b>000000</b> (black).<br><br>
- <LI><B>GRASS_TRANSPARENT=[TRUE|FALSE]</B><BR>
- sets transparent background on (TRUE) or off (FALSE, default).</LI><BR>
- <LI><B>GRASS_TRUECOLOR=[TRUE|FALSE]</B><BR>
- sets true-color support</LI><BR>
- <LI><B>GRASS_PNG_COMPRESSION=[0|1|9]</B><BR>
- compression level of PNG files (0 = none, 1 = fastest, 9 = best, default is 6)</LI><BR>
- <LI><B>GRASS_PNG_AUTO_WRITE=[TRUE|FALSE]</B><BR>
- if set to <tt>TRUE</tt>, the image file will be written after each
- operation (i.e. whenever a client disconnects), rather than
- only being written out when the driver terminates.</LI><BR>
- <LI><B>GRASS_PNG_READ</B><BR>
- if <tt>TRUE</tt>, the PNG driver will initialize the image from
- the contents of GRASS_PNGFILE.</LI><BR>
- <LI><B>GRASS_PNG_MAPPED</B><BR>
- if <tt>TRUE</tt>, the PNG driver will map GRASS_PNGFILE as its framebuffer,
- rather than using memory. This only works with BMP files.</LI><BR>
- <LI><B>GRASS_RENDER_IMMEDIATE=[TRUE|FALSE]</B><BR>
- tells the raster library to use its built-in PNG driver rather
- than connecting to an external monitor process using sockets. If
- <tt>TRUE</tt>, there is no need to run <tt>d.mon start=PNG</tt>.
-</UL>
-
-<H3>Example</H3>
-<OL>
- <LI>Define driver settings (here: bash shell syntax)
-<DIV class="code"><PRE>
-export GRASS_RENDER_IMMEDIATE=TRUE
-export GRASS_TRUECOLOR=TRUE
-</PRE></DIV>
- </LI>
- <LI>Start up the driver
-<DIV class="code"><PRE>
-d.mon start=PNG
-</PRE></DIV>
- </LI>
- <LI>Display raster map and vector polygons
-<DIV class="code"><PRE>
-d.rast <i>somerastermap</i>
-d.vect <i>somevectormap</i> color=red
-</PRE></DIV>
- </LI>
- <LI> Stop the driver subsequently. This will write a
- file named <tt>map.png</tt> to be created in your current directory:
-<DIV class="code"><PRE>
-d.mon stop=PNG
-</PRE></DIV>
- </LI>
-</OL>
-
-<H2>NOTES</H2>
-
-The PNG driver uses the libpng (see the <a href="http://www.libpng.org/pub/png/">libpng</a>
-home page) and zlib (see the
-<a href="http://www.zlib.net">zlib</a> home page), all which needs to
-be installed for the PNG driver to work (it's worth it).
-<p>
-The resolution of the <i>PNG</i> raster map is defined by the map
-extents. Use <em>g.region -p</em> to get the number of rows and cols and
-use the environment variables to set the PNG size. If you would like a
-larger image, multiply both rows and cols by the same whole number to
-preserve the aspect ratio.
-<p>
-Further PNG file processing (e.g. quantization to 1 bit for monochrome images)
-can be done with 'pnmquant' of the <a href="http://netpbm.sourceforge.net/">netpbm</a> tools.
-
-<h2>SEE ALSO</h2>
-<EM>
- <a href="displaydrivers.html">Display drivers</a>
- <br>
- <A HREF="htmlmapdriver.html">HTMLMAP driver</A>,
- <A HREF="psdriver.html">PostScript driver</A>,
- <A href="xdriver.html">XDRIVER</A>
- <BR>
- <A HREF="d.frame.html">d.frame</A>,
- <A href="d.mon.html">d.mon</A>,
- <A href="d.rast.html">d.rast</A>,
- <A href="d.vect.html">d.vect</A>
-</EM>
-
-<H2>AUTHOR</H2>
-Original version: Per Henrik Johansen <<I>phj (at) norgit.no</I>> <I><a href="http://www.norgit.no">NORGIT AS</a></I>
-<BR>
-Rewritten by: Glynn Clements, 2003
-
-<p>
-<i>Last changed: $Date: 2008-03-23 14:34:53 +0000 (Sun, 23 Mar 2008) $</i>
Copied: grass/trunk/lib/pngdriver/pngdriver.html (from rev 32770, grass/trunk/lib/pngdriver/description.html)
===================================================================
--- grass/trunk/lib/pngdriver/pngdriver.html (rev 0)
+++ grass/trunk/lib/pngdriver/pngdriver.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,125 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<HTML>
+<HEAD>
+ <TITLE>PNG driver</TITLE>
+ <META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
+ <link rel="stylesheet" href="grassdocs.css" type="text/css">
+</HEAD>
+<BODY bgColor=white>
+
+<img src="grass_logo.png" alt="GRASS logo"><hr align=center size=6 noshade>
+
+<H2>NAME</H2>
+<EM><B> PNG driver</B></EM> - driver to create PNG and PPM images.
+<BR><EM>(drivers)</EM>
+
+<H2>DESCRIPTION</H2>
+
+The PNG driver generates PNG and PPM images from GRASS display commands.
+Per default PNG files are written with this driver. It is started as 'pseudo' monitor
+(image file instead) and when stopped, all output from previously used
+display commands are written to the PNG image file.
+
+<H2>USAGE</H2>
+
+<H3>Environment variables</H3>
+Several environment variables effect the operation
+of the PNG driver.
+<UL>
+ <LI><B>GRASS_WIDTH=xxx</B><BR>
+ the width of the image map (default is 640).</LI><BR>
+ <LI><B>GRASS_HEIGHT=yyy</B><BR>
+ the height of the image map (default is 480).</LI><BR>
+ <LI><B>GRASS_PNGFILE=filename</B><BR>
+ the filename to put the resulting image in, default is <tt>map.png</tt>.
+ If you set GRASS_PNGFILE to a filename which ends in ".ppm", a PPM
+ file will be created.<br><br>
+ <LI><B>GRASS_BACKGROUNDCOLOR=RRGGBB</B><BR>
+ specifies the background color to use in RGB
+ notation (hex values). Default is <b>000000</b> (black).<br><br>
+ <LI><B>GRASS_TRANSPARENT=[TRUE|FALSE]</B><BR>
+ sets transparent background on (TRUE) or off (FALSE, default).</LI><BR>
+ <LI><B>GRASS_TRUECOLOR=[TRUE|FALSE]</B><BR>
+ sets true-color support</LI><BR>
+ <LI><B>GRASS_PNG_COMPRESSION=[0|1|9]</B><BR>
+ compression level of PNG files (0 = none, 1 = fastest, 9 = best, default is 6)</LI><BR>
+ <LI><B>GRASS_PNG_AUTO_WRITE=[TRUE|FALSE]</B><BR>
+ if set to <tt>TRUE</tt>, the image file will be written after each
+ operation (i.e. whenever a client disconnects), rather than
+ only being written out when the driver terminates.</LI><BR>
+ <LI><B>GRASS_PNG_READ</B><BR>
+ if <tt>TRUE</tt>, the PNG driver will initialize the image from
+ the contents of GRASS_PNGFILE.</LI><BR>
+ <LI><B>GRASS_PNG_MAPPED</B><BR>
+ if <tt>TRUE</tt>, the PNG driver will map GRASS_PNGFILE as its framebuffer,
+ rather than using memory. This only works with BMP files.</LI><BR>
+ <LI><B>GRASS_RENDER_IMMEDIATE=[TRUE|FALSE]</B><BR>
+ tells the raster library to use its built-in PNG driver rather
+ than connecting to an external monitor process using sockets. If
+ <tt>TRUE</tt>, there is no need to run <tt>d.mon start=PNG</tt>.
+</UL>
+
+<H3>Example</H3>
+<OL>
+ <LI>Define driver settings (here: bash shell syntax)
+<DIV class="code"><PRE>
+export GRASS_RENDER_IMMEDIATE=TRUE
+export GRASS_TRUECOLOR=TRUE
+</PRE></DIV>
+ </LI>
+ <LI>Start up the driver
+<DIV class="code"><PRE>
+d.mon start=PNG
+</PRE></DIV>
+ </LI>
+ <LI>Display raster map and vector polygons
+<DIV class="code"><PRE>
+d.rast <i>somerastermap</i>
+d.vect <i>somevectormap</i> color=red
+</PRE></DIV>
+ </LI>
+ <LI> Stop the driver subsequently. This will write a
+ file named <tt>map.png</tt> to be created in your current directory:
+<DIV class="code"><PRE>
+d.mon stop=PNG
+</PRE></DIV>
+ </LI>
+</OL>
+
+<H2>NOTES</H2>
+
+The PNG driver uses the libpng (see the <a href="http://www.libpng.org/pub/png/">libpng</a>
+home page) and zlib (see the
+<a href="http://www.zlib.net">zlib</a> home page), all which needs to
+be installed for the PNG driver to work (it's worth it).
+<p>
+The resolution of the <i>PNG</i> raster map is defined by the map
+extents. Use <em>g.region -p</em> to get the number of rows and cols and
+use the environment variables to set the PNG size. If you would like a
+larger image, multiply both rows and cols by the same whole number to
+preserve the aspect ratio.
+<p>
+Further PNG file processing (e.g. quantization to 1 bit for monochrome images)
+can be done with 'pnmquant' of the <a href="http://netpbm.sourceforge.net/">netpbm</a> tools.
+
+<h2>SEE ALSO</h2>
+<EM>
+ <a href="displaydrivers.html">Display drivers</a>
+ <br>
+ <A HREF="htmlmapdriver.html">HTMLMAP driver</A>,
+ <A HREF="psdriver.html">PostScript driver</A>,
+ <A href="xdriver.html">XDRIVER</A>
+ <BR>
+ <A HREF="d.frame.html">d.frame</A>,
+ <A href="d.mon.html">d.mon</A>,
+ <A href="d.rast.html">d.rast</A>,
+ <A href="d.vect.html">d.vect</A>
+</EM>
+
+<H2>AUTHOR</H2>
+Original version: Per Henrik Johansen <<I>phj (at) norgit.no</I>> <I><a href="http://www.norgit.no">NORGIT AS</a></I>
+<BR>
+Rewritten by: Glynn Clements, 2003
+
+<p>
+<i>Last changed: $Date: 2008-03-23 14:34:53 +0000 (Sun, 23 Mar 2008) $</i>
Modified: grass/trunk/lib/psdriver/Makefile
===================================================================
--- grass/trunk/lib/psdriver/Makefile 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/lib/psdriver/Makefile 2008-08-15 06:16:42 UTC (rev 32772)
@@ -2,16 +2,15 @@
include $(MODULE_TOPDIR)/include/Make/Platform.make
-PACKAGE ="libpsdriver"
-DEFS=-DPACKAGE=\"$(PACKAGE)\"
-EXTRA_CFLAGS=-I../driver $(PICFLAGS) $(DEFS)
+EXTRA_CFLAGS=-I../driver
EXTRA_LIBS=$(DRIVERLIB) $(GISLIB)
LIB_NAME = $(PSDRIVER_LIBNAME)
+PGM = psdriver
include $(MODULE_TOPDIR)/include/Make/Lib.make
-default: lib $(ETC)/psdriver.ps
+default: lib htmldir $(ETC)/psdriver.ps
$(ETC)/psdriver.ps: psdriver.ps
$(INSTALL_DATA) $< $@
Deleted: grass/trunk/lib/psdriver/description.html
===================================================================
--- grass/trunk/lib/psdriver/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/lib/psdriver/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,109 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
- <TITLE>PS driver</TITLE>
- <META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
- <link rel="stylesheet" href="grassdocs.css" type="text/css">
-</HEAD>
-<BODY bgColor=white>
-
-<img src="grass_logo.png" alt="GRASS logo"><hr align=center size=6 noshade>
-
-<H2>NAME</H2>
-<EM><B> PS driver</B></EM> - driver to create PostScript files.
-<BR><EM>(drivers)</EM>
-
-<H2>DESCRIPTION</H2>
-
-The PS driver generates a PostScript file from GRASS display commands.
-The driver is started as 'pseudo' monitor (PS file instead) and when
-stopped, all output from previously used display commands are written
-to the PostScript file.
-
-<H2>USAGE</H2>
-<H3>Environment variables</H3>
-Several environment variables effect the operation
-of the PS driver:
-
-<UL>
- <LI><B>GRASS_PSFILE</B><BR>
- name of output file. If it ends with ".eps" an EPS file
- will be created.</LI><BR>
- <LI><B>GRASS_PAPER</B><BR>
- sets the screen dimensions and margins to
- fit a standard paper size, see also GRASS_WIDTH, GRASS_HEIGHT.</LI><BR>
- <LI><B>GRASS_WIDTH</B><BR>
- defines the width of the screen, see also GRASS_HEIGHT</LI><BR>
- <LI><B>GRASS_HEIGHT</B><BR>
- defines the height of the screen, see also GRASS_WIDTH</LI><BR>
- <LI><B>GRASS_TRUECOLOR</B><BR>
- if <tt>TRUE</tt>, the PS driver generates color output, otherwise
- monochrome.</LI><BR>
- <LI><B>GRASS_LANDSCAPE</B><BR>
- if <tt>TRUE</tt>, the screen is rotated 90 degrees
- counter-clockwise so that a "landscape" screen fits better on
- "portrait" paper.</LI><BR>
- <LI><B>GRASS_PS_HEADER</B><BR>
- if <tt>FALSE</tt>, the output is appended to any existing file,
- and no prolog or setup sections are generated.</LI><BR>
- <LI><B>GRASS_PS_TRAILER</B><BR>
- if <tt>FALSE</tt>, no trailer section is generated.</LI>
-</UL>
-
-<H3>Example</H3>
-<OL>
- <LI>Start up the driver
-<DIV class="code"><PRE>
-d.mon start=PS
-</PRE></DIV>
- </LI>
- <LI>Display raster map and vector polygons
-<DIV class="code"><PRE>
-d.rast <i>somerastermap</i>
-d.vect map=<i>somevectormap</i> color=red
-</PRE></DIV>
- </LI>
- <LI> Stop the driver subsequently. This will write a
- file named <tt>map.ps</tt> to be created in your current directory:
-<DIV class="code"><PRE>
-d.mon stop=PS
-</PRE></DIV>
- </LI>
-</OL>
-
-<H2>NOTES</H2>
-
-The resolution of the <i>PS</i> raster map is defined by the map
-extents. Use <em>g.region -p</em> to get the number of rows and cols and
-use the environment variables to set the PS size. If you would like a
-larger image, multiply both rows and cols by the same whole number to
-preserve the aspect ratio.
-<P>
-GRASS_TRUECOLOR requires either PostScript level 2 or level 1 plus the
-colorimage and setrgbcolor operators (this is the case for colour printers
-which pre-date level 2 PostScript).
-<p>
-Only masked images (<tt>d.rast -o</tt>, <tt>d.rgb -o</tt>, <tt>d.his
--n</tt>) require PostScript level 3.
-
-<h2>SEE ALSO</h2>
-<EM>
- <a href="displaydrivers.html">Display drivers</a>
- <br>
- <A HREF="htmlmapdriver.html">HTMLMAP driver</A>,
- <A HREF="pngdriver.html">PNG driver</A>,
- <A href="xdriver.html">XDRIVER</A>
- <BR>
- <A HREF="d.frame.html">d.frame</A>,
- <A href="d.out.file.html">d.out.file</A>,
- <A href="d.mon.html">d.mon</A>,
- <A href="d.rast.html">d.rast</A>,
- <A href="d.vect.html">d.vect</A>
-</EM>
-
-<H2>AUTHOR</H2>
-
-Glynn Clements, 2007
-
-<p>
-<i>Last changed: $Date: 2008-03-23 14:34:53 +0000 (Sun, 23 Mar 2008) $</i>
Copied: grass/trunk/lib/psdriver/psdriver.html (from rev 32770, grass/trunk/lib/psdriver/description.html)
===================================================================
--- grass/trunk/lib/psdriver/psdriver.html (rev 0)
+++ grass/trunk/lib/psdriver/psdriver.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,109 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<HTML>
+<HEAD>
+ <TITLE>PS driver</TITLE>
+ <META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
+ <link rel="stylesheet" href="grassdocs.css" type="text/css">
+</HEAD>
+<BODY bgColor=white>
+
+<img src="grass_logo.png" alt="GRASS logo"><hr align=center size=6 noshade>
+
+<H2>NAME</H2>
+<EM><B> PS driver</B></EM> - driver to create PostScript files.
+<BR><EM>(drivers)</EM>
+
+<H2>DESCRIPTION</H2>
+
+The PS driver generates a PostScript file from GRASS display commands.
+The driver is started as 'pseudo' monitor (PS file instead) and when
+stopped, all output from previously used display commands are written
+to the PostScript file.
+
+<H2>USAGE</H2>
+<H3>Environment variables</H3>
+Several environment variables effect the operation
+of the PS driver:
+
+<UL>
+ <LI><B>GRASS_PSFILE</B><BR>
+ name of output file. If it ends with ".eps" an EPS file
+ will be created.</LI><BR>
+ <LI><B>GRASS_PAPER</B><BR>
+ sets the screen dimensions and margins to
+ fit a standard paper size, see also GRASS_WIDTH, GRASS_HEIGHT.</LI><BR>
+ <LI><B>GRASS_WIDTH</B><BR>
+ defines the width of the screen, see also GRASS_HEIGHT</LI><BR>
+ <LI><B>GRASS_HEIGHT</B><BR>
+ defines the height of the screen, see also GRASS_WIDTH</LI><BR>
+ <LI><B>GRASS_TRUECOLOR</B><BR>
+ if <tt>TRUE</tt>, the PS driver generates color output, otherwise
+ monochrome.</LI><BR>
+ <LI><B>GRASS_LANDSCAPE</B><BR>
+ if <tt>TRUE</tt>, the screen is rotated 90 degrees
+ counter-clockwise so that a "landscape" screen fits better on
+ "portrait" paper.</LI><BR>
+ <LI><B>GRASS_PS_HEADER</B><BR>
+ if <tt>FALSE</tt>, the output is appended to any existing file,
+ and no prolog or setup sections are generated.</LI><BR>
+ <LI><B>GRASS_PS_TRAILER</B><BR>
+ if <tt>FALSE</tt>, no trailer section is generated.</LI>
+</UL>
+
+<H3>Example</H3>
+<OL>
+ <LI>Start up the driver
+<DIV class="code"><PRE>
+d.mon start=PS
+</PRE></DIV>
+ </LI>
+ <LI>Display raster map and vector polygons
+<DIV class="code"><PRE>
+d.rast <i>somerastermap</i>
+d.vect map=<i>somevectormap</i> color=red
+</PRE></DIV>
+ </LI>
+ <LI> Stop the driver subsequently. This will write a
+ file named <tt>map.ps</tt> to be created in your current directory:
+<DIV class="code"><PRE>
+d.mon stop=PS
+</PRE></DIV>
+ </LI>
+</OL>
+
+<H2>NOTES</H2>
+
+The resolution of the <i>PS</i> raster map is defined by the map
+extents. Use <em>g.region -p</em> to get the number of rows and cols and
+use the environment variables to set the PS size. If you would like a
+larger image, multiply both rows and cols by the same whole number to
+preserve the aspect ratio.
+<P>
+GRASS_TRUECOLOR requires either PostScript level 2 or level 1 plus the
+colorimage and setrgbcolor operators (this is the case for colour printers
+which pre-date level 2 PostScript).
+<p>
+Only masked images (<tt>d.rast -o</tt>, <tt>d.rgb -o</tt>, <tt>d.his
+-n</tt>) require PostScript level 3.
+
+<h2>SEE ALSO</h2>
+<EM>
+ <a href="displaydrivers.html">Display drivers</a>
+ <br>
+ <A HREF="htmlmapdriver.html">HTMLMAP driver</A>,
+ <A HREF="pngdriver.html">PNG driver</A>,
+ <A href="xdriver.html">XDRIVER</A>
+ <BR>
+ <A HREF="d.frame.html">d.frame</A>,
+ <A href="d.out.file.html">d.out.file</A>,
+ <A href="d.mon.html">d.mon</A>,
+ <A href="d.rast.html">d.rast</A>,
+ <A href="d.vect.html">d.vect</A>
+</EM>
+
+<H2>AUTHOR</H2>
+
+Glynn Clements, 2007
+
+<p>
+<i>Last changed: $Date: 2008-03-23 14:34:53 +0000 (Sun, 23 Mar 2008) $</i>
Deleted: grass/trunk/misc/m.cogo/description.html
===================================================================
--- grass/trunk/misc/m.cogo/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/misc/m.cogo/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,145 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-<EM>m.cogo</EM> converts data points between bearing and distance
-and X,Y coordinates. Only simple bearing/distance or coordinate
-pairs are handled. It assumes a cartesian coordinate system.
-
-<P>
-Input can be entered via standard input (default) or from the file
-<B>input=</B><EM>name</EM>. Specifying the input as "-" also
-specifies standard input, and is useful for using the program in
-a pipeline. Output will be to standard output unless a file
-name other than "-" is specified. The input file must
-closely adhere to the following format, where up to a 10 character
-label is allowed but not required (see <B>-l</B> flag).
-
-<P>
-<B>Example COGO input:</B>
-<div class="code"><pre>
- P23 N 23:14:12 W 340
- P24 S 04:18:56 E 230
- ...
-</pre></div>
-
-<P>
-The first column may contain a label and you must use the <B>-l</B>
-flag so the program knows. This is followed by a space, and then
-either the character 'N' or 'S' to indicate whether the bearing is
-relative to the north or south directions. After another space,
-the angle begins in degrees, minutes, and seconds in
-"DDD:MM:SS.SSSS" format. Generally, the angle can be of the form
-<EM>digits + separator + digits + separator + digits [+ '.' + digits]</EM>.
-A space follows the angle, and is then followed by either the 'E' or 'W'
-characters. A space separates the bearing from the distance (which should
-be in appropriate linear units).
-
-<P>
-<B>Output of the above input:</B>
-<div class="code"><pre>
- -134.140211 312.420236 P23
- -116.832837 83.072345 P24
- ...
-</pre></div>
-<P>
-Unless specified with the <B>coord</B> option, calculations begin from (0,0).
-
-<P>
-For those unfamiliar with the notation for bearings: Picture yourself in the
-center of a circle. The first hemispere notation tell you whether you should
-face north or south. Then you read the angle and either turn that many
-degrees to the east or west, depending on the second hemisphere notation.
-Finally, you move <distance> units in that direction to get to the
-next station.
-</P>
-
-<EM>m.cogo</EM> can be run either non-interactively or
-interactively. The program will be run non-interactively
-if the user specifies any parameter or flag. Use "m.cogo -",
-to run the program in a pipeline. Without any flags or
-parameters, <EM>m.cogo</EM> will prompt for each value
-using the familiar GRASS parser interface.
-
-<P>
-
-<H2>NOTES</H2>
-
-This program is very simplistic, and will not handle deviations
-from the input format explained above. Currently, the
-program doesn't do anything particularly useful with
-the output. However, it is envisioned that this program
-will be extended to provide the capability to generate
-vector and/or sites layers.
-
-
-<H2>EXAMPLE</H2>
-
-<div class="code"><pre>
- m.cogo -l in=cogo.dat
-</pre></div>
-
-Where the <tt>cogo.dat</tt> input file looks like:
-<div class="code"><pre>
-# Sample COGO input file -- This defines an area.
-# <label> <bearing> <distance>
-P001 S 88:44:56 W 6.7195
-P002 N 33:34:15 W 2.25
-P003 N 23:23:50 W 31.4024
-P004 N 05:04:45 W 25.6981
-P005 N 18:07:25 E 22.2439
-P006 N 27:49:50 E 75.7317
-P007 N 22:56:50 E 87.4482
-P008 N 37:45:15 E 37.7835
-P009 N 46:04:30 E 11.5854
-P010 N 90:00:00 E 8.8201
-P011 N 90:00:00 E 164.1128
-P012 S 48:41:12 E 10.1311
-P013 S 00:25:50 W 255.7652
-P014 N 88:03:13 W 98.8567
-P015 S 88:44:56 W 146.2713
-P016 S 88:44:56 W 18.7164
-</pre></div>
-
-Round trip:
-<div class="code"><pre>
- m.cogo -l in=cogo.dat | m.cogo -rl in="-"
-</pre></div>
-
-
-Import as a vector points map:
-<div class="code"><pre>
- m.cogo -l in=cogo.dat | v.in.ascii out=cogo_points x=1 y=2 fs=space
-</pre></div>
-
-
-Shell script to import as a vector line map:
-<div class="code"><pre>
- m.cogo -l in=cogo.dat | tac | awk '
- BEGIN { FS=" " ; R=0 }
- $1~/\d*\.\d*/ { printf(" %.8f %.8f\n", $1, $2) ; ++R }
- END { printf("L %d\n", R) }' | tac | \
- v.in.ascii -n format=standard out=cogo_line
-</pre></div>
-
-Unclosed lines may be snapped with <em>v.clean</em>, converted to
-boundaries with <em>v.type</em>, and closed boundaries may be
-converted to areas with <em>v.centroids</em>.
-
-
-<H2>SEE ALSO</H2>
-
-<em>
-<a HREF="v.centroids.html">v.centroids</a>,
-<a HREF="v.clean.html">v.clean</a>,
-<a HREF="v.digit.html">v.digit</a>,
-<a HREF="v.in.ascii.html">v.in.ascii</a>,
-<a HREF="v.type.html">v.type</a>
-</em>
-
-
-
-<H2>AUTHOR</H2>
-
-Eric G. Miller
-
-<p>
-<i>Last changed: $Date$</i>
Copied: grass/trunk/misc/m.cogo/m.cogo.html (from rev 32770, grass/trunk/misc/m.cogo/description.html)
===================================================================
--- grass/trunk/misc/m.cogo/m.cogo.html (rev 0)
+++ grass/trunk/misc/m.cogo/m.cogo.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,145 @@
+<H2>DESCRIPTION</H2>
+
+<EM>m.cogo</EM> converts data points between bearing and distance
+and X,Y coordinates. Only simple bearing/distance or coordinate
+pairs are handled. It assumes a cartesian coordinate system.
+
+<P>
+Input can be entered via standard input (default) or from the file
+<B>input=</B><EM>name</EM>. Specifying the input as "-" also
+specifies standard input, and is useful for using the program in
+a pipeline. Output will be to standard output unless a file
+name other than "-" is specified. The input file must
+closely adhere to the following format, where up to a 10 character
+label is allowed but not required (see <B>-l</B> flag).
+
+<P>
+<B>Example COGO input:</B>
+<div class="code"><pre>
+ P23 N 23:14:12 W 340
+ P24 S 04:18:56 E 230
+ ...
+</pre></div>
+
+<P>
+The first column may contain a label and you must use the <B>-l</B>
+flag so the program knows. This is followed by a space, and then
+either the character 'N' or 'S' to indicate whether the bearing is
+relative to the north or south directions. After another space,
+the angle begins in degrees, minutes, and seconds in
+"DDD:MM:SS.SSSS" format. Generally, the angle can be of the form
+<EM>digits + separator + digits + separator + digits [+ '.' + digits]</EM>.
+A space follows the angle, and is then followed by either the 'E' or 'W'
+characters. A space separates the bearing from the distance (which should
+be in appropriate linear units).
+
+<P>
+<B>Output of the above input:</B>
+<div class="code"><pre>
+ -134.140211 312.420236 P23
+ -116.832837 83.072345 P24
+ ...
+</pre></div>
+<P>
+Unless specified with the <B>coord</B> option, calculations begin from (0,0).
+
+<P>
+For those unfamiliar with the notation for bearings: Picture yourself in the
+center of a circle. The first hemispere notation tell you whether you should
+face north or south. Then you read the angle and either turn that many
+degrees to the east or west, depending on the second hemisphere notation.
+Finally, you move <distance> units in that direction to get to the
+next station.
+</P>
+
+<EM>m.cogo</EM> can be run either non-interactively or
+interactively. The program will be run non-interactively
+if the user specifies any parameter or flag. Use "m.cogo -",
+to run the program in a pipeline. Without any flags or
+parameters, <EM>m.cogo</EM> will prompt for each value
+using the familiar GRASS parser interface.
+
+<P>
+
+<H2>NOTES</H2>
+
+This program is very simplistic, and will not handle deviations
+from the input format explained above. Currently, the
+program doesn't do anything particularly useful with
+the output. However, it is envisioned that this program
+will be extended to provide the capability to generate
+vector and/or sites layers.
+
+
+<H2>EXAMPLE</H2>
+
+<div class="code"><pre>
+ m.cogo -l in=cogo.dat
+</pre></div>
+
+Where the <tt>cogo.dat</tt> input file looks like:
+<div class="code"><pre>
+# Sample COGO input file -- This defines an area.
+# <label> <bearing> <distance>
+P001 S 88:44:56 W 6.7195
+P002 N 33:34:15 W 2.25
+P003 N 23:23:50 W 31.4024
+P004 N 05:04:45 W 25.6981
+P005 N 18:07:25 E 22.2439
+P006 N 27:49:50 E 75.7317
+P007 N 22:56:50 E 87.4482
+P008 N 37:45:15 E 37.7835
+P009 N 46:04:30 E 11.5854
+P010 N 90:00:00 E 8.8201
+P011 N 90:00:00 E 164.1128
+P012 S 48:41:12 E 10.1311
+P013 S 00:25:50 W 255.7652
+P014 N 88:03:13 W 98.8567
+P015 S 88:44:56 W 146.2713
+P016 S 88:44:56 W 18.7164
+</pre></div>
+
+Round trip:
+<div class="code"><pre>
+ m.cogo -l in=cogo.dat | m.cogo -rl in="-"
+</pre></div>
+
+
+Import as a vector points map:
+<div class="code"><pre>
+ m.cogo -l in=cogo.dat | v.in.ascii out=cogo_points x=1 y=2 fs=space
+</pre></div>
+
+
+Shell script to import as a vector line map:
+<div class="code"><pre>
+ m.cogo -l in=cogo.dat | tac | awk '
+ BEGIN { FS=" " ; R=0 }
+ $1~/\d*\.\d*/ { printf(" %.8f %.8f\n", $1, $2) ; ++R }
+ END { printf("L %d\n", R) }' | tac | \
+ v.in.ascii -n format=standard out=cogo_line
+</pre></div>
+
+Unclosed lines may be snapped with <em>v.clean</em>, converted to
+boundaries with <em>v.type</em>, and closed boundaries may be
+converted to areas with <em>v.centroids</em>.
+
+
+<H2>SEE ALSO</H2>
+
+<em>
+<a HREF="v.centroids.html">v.centroids</a>,
+<a HREF="v.clean.html">v.clean</a>,
+<a HREF="v.digit.html">v.digit</a>,
+<a HREF="v.in.ascii.html">v.in.ascii</a>,
+<a HREF="v.type.html">v.type</a>
+</em>
+
+
+
+<H2>AUTHOR</H2>
+
+Eric G. Miller
+
+<p>
+<i>Last changed: $Date$</i>
Deleted: grass/trunk/ps/ps.map/description.html
===================================================================
--- grass/trunk/ps/ps.map/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/ps/ps.map/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,1606 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-<EM>ps.map</EM> is a cartographic mapping program for producing high quality
-hardcopy maps in PostScript format. Output can include a raster map, any
-number of vector overlays, text labels, decorations, and other spatial data.
-
-<P>
-A file of mapping instructions that describes the various spatial and textual
-information to be printed must be prepared prior to running <EM>ps.map</EM>.
-
-
-<H2>NOTES</H2>
-
-<P>
-The order of commands is generally unimportant but may affect how some layers
-are drawn. For example to plot <B>vpoints</B> above <B>vareas</B> list the
-<B>vpoints</B> entry first. Raster maps are always drawn first, and only a
-single raster map (or 3 if part of a RGB group) may be used.
-
-<P>
-The hash character ('<tt>#</tt>') may be used at the beginning of a line
-to indicate that the line is a comment. Blank lines will also be ignored.
-
-<P>
-Be aware that some mapping instructions require the <i>end</i> command
-and some do not. Any instruction that allows subcommands will require
-it, any instruction that does not allow subcommands will not.
-
-<P>
-The resolution and extent of raster maps plotted with <EM>ps.map</EM> are
-controlled by the current region settings via the
-<a href="g.region.html">g.region</a> module. The output filesize is largely
-a function of the region resolution, so special care should be taken
-if working with large raster datasets. For example if the desired output is
-US-Letter sized paper at 300dpi, with 1" margins and the raster filling the
-entire page, the usable area on the page will be 6.5" x 9", which at 300
-dots/inch is equivalent to a region of 1950 columns x 2700 rows (see
-"<tt>g.region -p</tt>"). Any higher resolution settings will make the
-output file larger, but with a consumer printer you probably won't be able
-to resolve any better detail in the hardcopy.
-
-<P>
-The user can specify negative or greater than 100 percentage values for
-positioning several map decorations and embedded EPS-files, to move them
-outside the current map box region (for example to position a caption,
-barscale, or legend above or below the map box).
-
-<P>
-One "pixel" is 1/72 of an inch.
-
-<P>
-For users wanting to use special characters (such as accented characters) it
-is important to note that <em>ps.map</em> uses <tt>ISO-8859-1</tt> encoding.
-This means that your instructions file will have to be encoded in this
-encoding. If you normally work in a different encoding environment (such as
-<tt>UTF-8</tt>), you have to transform your file to the <tt>ISO-8859-1</tt>
-encoding, for example by using the <tt>iconv</tt> utility:
-</P>
-<DIV class="code"><PRE>
-iconv -f UTF-8 -t ISO_8859-1 utf_file > iso_file
-</PRE></DIV>
-
-
-<P><P>
-
-<H2>MAPPING INSTRUCTIONS</H2>
-
-The mapping instructions allow the user to specify various spatial data
-to be plotted. These instructions are normally prepared in a regular
-text file using a system editor. Some instructions are single line
-instructions while others are multiple line. Multiple line instructions
-consist of the main instruction followed by a subsection of one or more
-additional instructions and are terminated with an <i>end</i> instruction.
-<P>
-
-<h3>Instruction keywords:</h3>
-[
-<a href="#border">border</a> |
-<a href="#colortable">colortable</a> |
-<a href="#comments">comments</a> |
-<a href="#copies">copies</a> |
-<a href="#eps">eps</a> |
-<a href="#geogrid">geogrid</a> |
-<a href="#greyrast">greyrast</a> |
-<a href="#grid">grid</a> |
-<a href="#group">group</a> |
-<a href="#header">header</a> |
-<a href="#labels">labels</a> |
-<a href="#line">line</a> |
-<a href="#mapinfo">mapinfo</a> |
-<a href="#maploc">maploc</a> |
-<a href="#maskcolor">maskcolor</a> |
-<a href="#outline">outline</a> |
-<a href="#paper">paper</a> |
-<a href="#point">point</a> |
-<a href="#psfile">psfile</a> |
-<a href="#raster">raster</a> |
-<a href="#read">read</a> |
-<a href="#rectangle">rectangle</a> |
-<a href="#region">region</a> |
-<a href="#rgb">rgb</a> |
-<a href="#scale">scale</a> |
-<a href="#scalebar">scalebar</a> |
-<a href="#setcolor">setcolor</a> |
-<a href="#text">text</a> |
-<a href="#vareas">vareas</a> |
-<a href="#vlines">vlines</a> |
-<a href="#vpoints">vpoints</a> |
-<a href="#vlegend">vlegend</a> |
-<a href="#end">end</a>
-]
-
-
-<h3>Common instructions</h3>
-Instructions that may be included in the subsection under several
-different main instructions are:
-
-<DL>
-<DT><B>where</B> <EM>x y</EM>
-
-<DD>The top left corner of the bounding box of the item to be plotted
-is located <EM>x</EM> inches from the left edge of the paper and
-<EM>y</EM> inches from the top edge of the paper. If <EM>x</EM> is less than
-or equal to zero, the default horizontal location is used. If <EM>y</EM>
-is less than or equal to zero, the default vertical location is used.
-
-<DT><B>font</B> <EM>font name</EM>
-
-<DD>The name of the PostScript font.
-Fonts present in all PostScript implementations are:
-<tt>
-Times-Roman,
-Times-Italic,
-Times-Bold,
-Times-BoldItalic,
-Helvetica,
-Helvetica-Oblique,
-Helvetica-Bold,
-Helvetica-BoldOblique,
-Courier,
-Courier-Oblique,
-Courier-Bold,
-and
-Courier-BoldOblique</tt>.
-<BR>
-The default is Helvetica.
-</DD>
-
-
-<DT><B>fontsize</B> <EM>font size</EM>
-
-<DD>The size of the PostScript font (in 1/72nds of an inch).
-The default is 10.
-</DD>
-
-
-<a name="NAMED_COLORS"></a>
-<DT><B>color</B> <EM>name</EM>
-
-<DD>The following colors names are accepted by <EM>ps.map</EM>:
-<tt>
-aqua,
-black,
-blue,
-brown,
-cyan,
-gray,
-grey,
-green,
-indigo,
-magenta,
-orange,
-purple,
-red,
-violet,
-white,
-yellow
-</tt>.
-<BR><BR>
-For vectors and some plotting commands you can also specify
-'<tt>none</tt>' or '<tt>R:G:B</tt>' (e.g '<tt>255:0:0</tt>').
-</DD>
-</DL>
-<P>
-<BR>
-
-<h3>Command usage</h3>
-
-<a name="border"></a>
-<H2>border</H2>
-
-Controls the border which is drawn around the map area.
-<PRE>
-USAGE: <B>border</B> [y|n]
- <B>color</B> color
- <B>width</B> #
- <B>end</B>
-</PRE>
-The <B>color</B> may be either a standard GRASS color, a R:G:B triplet,
-or "none". The width is specified in points, unless followed by an "i"
-in which case it is measured in inches.
-The default is a black border box of width 1 point.
-<P>
-The border can be turned off completely with the
-"<tt>border n</tt>" instruction. In this case
-the <B>end</B> command should not be given as the
-main command will be treated as a single line instruction.
-<P>
-
-This example would create a grey border 0.1" wide.
-<PRE>
-EXAMPLE:
- <B>border</B>
- <B>color</B> grey
- <B>width</B> 0.1i
- <B>end</B>
-</PRE>
-<P>
-
-
-<a name="colortable"></a>
-<H2>colortable</H2>
-
-Prints the color table for the raster map layer anywhere on the page.
-<PRE>
-USAGE: <B>colortable</B> [y|n]
- <B>where</B> x y
- <B>raster</B> raster map
- <B>range</B> minimum maximum
- <B>width</B> table width
- <B>height</B> table height (FP legend only)
- <B>cols</B> table columns
- <B>font</B> font name
- <B>fontsize</B> font size
- <B>color</B> text color
- <B>nodata</B> [Y|n]
- <B>tickbar</B> [y|N]
- <B>end</B>
-</PRE>
-The color table will display the colors for each raster map layer
-category value and the category label.
-If <B>raster</B> is omitted, the colortable defaults to a previously registered raster layer.
-The legend's <B>range</B> can be adjusted for floating point rasters, but if
-set beyond the extent of the map's range be sure that you have set up color
-rules with <em>r.colors</em> which cover this range.
-The default location for the colortable is immediately below any other
-map legend information, starting at the left margin.
-The default text color is black.
-Omitting the <B>colortable</B> instruction would result in
-no color table. For floating point legends <B>width</B> is width of color
-band only. <B>height</B> is used only for floating point legend.
-Adding the <B>nodata n</B> instruction will prevent the "no data" box
-from being drawn (category based legends only).
-Adding the <B>tickbar y</B> instruction will change the tick mark style
-so that ticks are drawn across the color table instead of protruding out
-to the right (floating point legends only).
-<P>
-<B>Note</B>: Be careful about asking for color tables for
-raster map layers which have many categories, such as elevation.
-This could result in the printing of an extremely long color table!
-<P>
-Another issue is that the color table only includes categories which
-have a label. If there are only a few categories, you can use
-r.support to manually add labels. If there are too many categories to
-do this, you could write a script to add dummy labels to the cats file<br>
-(<gisdbase>/<location>/<mapset>/cats/<mapname>).
-<P>
-If the colortable is turned off with a "<tt>colortable n</tt>"
-instruction the <B>end</B> command should not be given as the
-main command will be treated as a single line instruction.
-
-<P>
-
-This example would print a color table immediately below any other map legend
-information, starting at the left margin, with 4 columns:
-<PRE>
-EXAMPLE:
- <B>colortable</B> y
- <B>cols</B> 4
- <B>width</B> 4
- <B>end</B>
-</PRE>
-<P>
-
-
-<a name="comments"></a>
-<H2>comments</H2>
-
-Prints comments anywhere on the page.
-<PRE>
-USAGE: <B>comments</B> commentfile
- <B>where</B> x y
- <B>font</B> font name
- <B>fontsize</B> font size
- <B>color</B> text color
- <B>end</B>
-</PRE>
-The default location is immediately below the last item item printed,
-starting at the left margin. The default text color is black.
-<P>
-If you wish to use parentheses spanning multiple lines you will need to
-quote them with a backslash to prevent the PostScript interpreter from
-getting confused. e.g. '<B><TT>\(</TT></B>' and '<B><TT>\)</TT></B>'
-
-<P>
-
-This example prints in blue
-whatever is in the file <EM>veg.comments</EM> starting at
-1.5 inches from the left edge of the page and 7.25 inches from the top of
-the page, using a 15/72 inch Helvetica Bold font.
-<PRE>
-EXAMPLE:
- <B>raster</B> vegetation
- <B>comments</B> veg.comments
- <B>where</B> 1.5 7.25
- <B>font</B> Helvetica Bold
- <B>fontsize</B> 15
- <B>color</B> blue
- <B>end</B>
-</PRE>
-Presumably, the file
-<EM>veg.comments</EM>
-contain comments
-pertaining to the raster map layer <EM>vegetation</EM>,
-such as "This map was created by classifying a LANDSAT TM image".
-<P>
-
-
-<a name="copies"></a>
-<H2>copies</H2>
-
-Specifies the number of copies to be printed.
-<PRE>
-USAGE: <B>copies</B> n
-</PRE>
-Each page will be printed n times.
-<P>
-This instruction is identical to the <EM>copies</EM> command line parameter.
-<P>
-
-
-<a name="eps"></a>
-<H2>eps</H2>
-
-Places EPS (Encapsulated PostScript) pictures on the output map.
-<PRE>
-USAGE: <B>eps</B> east north
- <B>eps</B> x% y%
- <B>epsfile</B> EPS file
- <B>scale</B> #
- <B>rotate</B> #
- <B>masked</B> [y|n]
- <B>end</B>
-</PRE>
-The EPS picture location is entered in the main
-instruction line by giving either the map
-coordinates or by using percentages of the geographic region.
-The EPS picture will be <i>centered</i> at the given position.
-The user must specify full EPS file path <B>epsfile</B>.
-The user may also specify the <B>scale</B> of the icon
-(default is 1.0), the <B>rotate</B> i.e. rotation in degrees
-(default is 0)
-and whether the point is to be <B>masked</B>
-by the current mask.
-(See manual entry for <EM><A HREF="r.mask.html">r.mask</A></EM>
-for more information on the mask.)
-<P>
-
-This example would place a EPS file ./epsf/logo.eps
-at the point (E456000 N7890000). This picture would be
-rotated 20 degrees clockwise, 3 times bigger than
-in original file and would not be masked by the current mask.
-<PRE>
-EXAMPLE:
- <B>eps</B> 456000 7890000
- <B>epsfile</B> ./epsf/logo.eps
- <B>scale</B> 3
- <B>rotate</B> 20
- <B>masked</B> n
- <B>end</B>
-</PRE>
-Of course, multiple EPS pictures may be drawn with multiple
-<EM>eps</EM>
-instructions.
-<P>
-
-
-<a name="geogrid"></a>
-<H2>geogrid</H2>
-
-Overlays a geographic grid onto the output map.
-<PRE>
-USAGE: <B>geogrid</B> spacing unit
- <B>color</B> color
- <B>numbers</B> # [color]
- <B>font</B> font name
- <B>fontsize</B> font size
- <B>width</B> #
- <B>end</B>
-</PRE>
-The <B>spacing</B> and spacing unit of the geographic grid is given
-on the main instruction line. The <B>spacing</B> unit is given as one of <B>d</B> for
-degrees, <B>m</B> for minutes, and <B>s</B> for seconds.
-The subsection instructions allow the user to specify
-the <B>color</B> of the geographic grid lines,
-whether coordinate <B>numbers</B> should appear
-on the geographic grid lines, the <B>width</B>
-of the lines (accepts decimal points [floating points]
-as well as integers), and
-if they should appear every grid line (1), every other grid line
-(2), etc., and what color the numbers should be. The defaults are
-black grid lines, unnumbered.
-
-<P>
-
-NOTE: The <B>geogrid</B> draws grid numbers on the east and south borders of the map.
-
-<P>
-
-This example would overlay a blue geographic grid with a spacing of 30 minutes
-onto the output map. Alternate grid
-lines would be numbered with yellow numbers.
-<PRE>
-EXAMPLE:
- <B>geogrid</B> 30 m
- <B>color</B> blue
- <B>numbers</B> 2 yellow
- <B>end</B>
-</PRE>
-<P>
-
-
-<a name="greyrast"></a>
-<H2>greyrast</H2>
-
-Selects a raster map layer for output in shades of grey.
-<PRE>
-USAGE: <B>greyrast</B> mapname
-</PRE>
-For each
-<EM>ps.map</EM>
-run, only one raster map layer can be requested (using either the
-<EM>greyrast</EM> or the <EM>raster</EM> instruction).
-<P>
-
-
-<a name="grid"></a>
-<H2>grid</H2>
-
-Overlays a coordinate grid onto the output map.
-<PRE>
-USAGE: <B>grid</B> spacing
- <B>color</B> color
- <B>numbers</B> # [color]
- <B>cross</B> cross size
- <B>font</B> font name
- <B>fontsize</B> font size
- <B>width</B> #
- <B>end</B>
-</PRE>
-The <B>spacing</B> of the grid is given (in the geographic coordinate
-system units) on the main instruction line. The subsection instructions
-allow the user to specify
-the <B>color</B> of the grid lines,
-whether coordinate <B>numbers</B> should appear
-on the grid lines, and if they
-should appear every grid line (1), every other grid line
-(2), etc., and what color the numbers should be.
-The <B>cross</B> argument draws grid intersection crosses instead of grid lines,
-with cross size given in geographic coordinate system units.
-The defaults are black grid lines, unnumbered.
-
-<P>
-
-This example would overlay a green grid with a spacing of 10000 meters
-(for a metered database, like UTM) onto the output map. Alternate grid
-lines would be numbered with red numbers.
-<PRE>
-EXAMPLE:
- <B>grid</B> 10000
- <B>color</B> green
- <B>numbers</B> 2 red
- <B>end</B>
-</PRE>
-<P>
-
-
-<a name="group"></a>
-<H2>group</H2>
-
-Selects an RGB imagery group for output.
-<PRE>
-USAGE: <B>group</B> <EM>groupname</EM>
-</PRE>
-This is similar to <EM>raster</EM>, except that it uses an imagery group
-instead of a raster map layer. The group must contain three raster map
-layers, comprising the red, green and blue bands of the image.
-<P>
-
-
-<a name="header"></a>
-<H2>header</H2>
-
-Prints the map header above the map.
-<PRE>
-USAGE: <B>header</B>
- <B>file</B> header file
- <B>font</B> font name
- <B>fontsize</B> font size
- <B>color</B> text color
- <B>end</B>
-</PRE>
-If the <EM>file</EM> sub-instruction is absent the header will consist
-of the map's title <!-- from hist file -->
-and the location's description.<!-- PERMANENT/MYNAME -->
-The text will be centered on the page above the map.
-The default text color is black.
-
-<P>
-
-This example prints (in red) whatever is in the file <EM>soils.hdr</EM> above
-the map, using a 20/72 inch <tt>Courier</tt> font.
-<PRE>
-EXAMPLE:
- <B>header</B>
- <B>file</B> soils.hdr
- <B>font</B> Courier
- <B>fontsize</B> 20
- <B>color</B> red
- <B>end</B>
-</PRE>
-<P>
-
-
-<a name="labels"></a>
-<H2>labels</H2>
-
-Selects a labels file for output (see manual entry for
-<EM>
-<A HREF="v.label.html">v.label</A>
-).</EM>
-<PRE>
-USAGE: <B>labels</B> labelfile
- <B>font</B> font name
- <B>end</B>
-</PRE>
-<P>
-NOTE: ps.map can read new option 'ROTATE:' from labels file, which
-specifies counter clockwise rotation in degrees.
-<P>
-This example would paint labels from the labels file called
-<EM>town.names</EM>. Presumably, these labels would indicate the names of
-towns on the map.
-<PRE>
-EXAMPLE:
- <B>labels</B> town.names
- <B>end</B>
-</PRE>
-<P>
-
-
-<a name="line"></a>
-<H2>line</H2>
-
-Draws lines on the output map.
-<PRE>
-USAGE: <B>line</B> east north east north
- <B>line</B> x% y% x% y%
- <B>color</B> color
- <B>width</B> #
- <B>masked</B> [y|n]
- <B>end</B>
-</PRE>
-The beginning and ending points of the line are entered on the main
-instruction. These points can be defined either by map coordinates or
-by using percentages of the geographic region.
-The user may also specify line
-<B>color</B>,
-<B>width</B>
-in pixels (accepts decimal points [floating points] as well as integers),
-and if the line is to be <B>masked</B> by the current mask.
-(See manual entry for <EM><A HREF="r.mask.html">r.mask</A>
-</EM> for more information on the mask.)
-<P>
-
-This example would draw a yellow line from the point x=10% y=80%
-to the point x=30% y=70%. This line
-would be 2 pixels wide and would appear even if there is a mask.
-<PRE>
-EXAMPLE:
- <B>line</B> 10% 80% 30% 70%
- <B>color</B> yellow
- <B>width</B> 2
- <B>masked</B> n
- <B>end</B>
-</PRE>
-Of course, multiple lines may be drawn with multiple
-<EM>line</EM>
-instructions.
-<P>
-
-
-<a name="mapinfo"></a>
-<H2>mapinfo</H2>
-
-Prints the portion of the map legend containing the scale, grid and
-region information, on or below the map.
-<PRE>
-USAGE: <B>mapinfo</B>
- <B>where</B> x y
- <B>font</B> font name
- <B>fontsize</B> font size
- <B>color</B> text color
- <B>background</B> box color|none
- <B>border</B> color|none
- <B>end</B>
-</PRE>
-The default location is immediately below the map,
-starting at the left edge of the map.
-The default text color is black.
-The default background box color is white.
-<P>
-<EM>border</EM> will draw a border around the legend using the specified color.
- (see <a href="#NAMED_COLORS">NAMED COLORS</a>)
-<P>
-
-This example prints (in brown) the scale, grid and region information
-immediately below the map and starting 1.5 inches from the left edge
-of the page, using a 12/72 inch <tt>Courier</tt> font.
-
-<PRE>
-EXAMPLE:
- <B>mapinfo</B>
- <B>where</B> 1.5 0
- <B>font</B> Courier
- <B>fontsize</B> 12
- <B>color</B> brown
- <B>end</B>
-</PRE>
-<P>
-
-
-<a name="maploc"></a>
-<H2>maploc</H2>
-
-Positions the map on the page.
-<PRE>
-USAGE: <B>maploc</B> x y [width height]
-</PRE>
-The upper left corner of the map will be positioned <EM>x</EM> inches from
-the left edge of the page and <EM>y</EM> inches from the top of the page.
-If <EM>width</EM> and <EM>height</EM> (in inches) are present, the map will be
-rescaled, if necessary, to fit.
-
-<P>
-
-This example positions the upper left corner of the map 2.0 inches from
-the left edge and 3.5 inches from the top edge of the map.
-<PRE>
-EXAMPLE:
- <B>maploc</B> 2.0 3.5
-</PRE>
-<P>
-
-
-<a name="maskcolor"></a>
-<H2>maskcolor</H2>
-
-Color to be used for mask.
-<PRE>
-USAGE: <B>maskcolor</B> color
-</PRE>
-
-
-<a name="outline"></a>
-<H2>outline</H2>
-
-Outlines the areas of a raster map layer with a specified color.
-<PRE>
-USAGE: <B>outline</B>
- <B>color</B> color
- <B>width</B> width of line in pixels
- <B>end</B>
-</PRE>
-Distinct areas of the raster map will be separated from each other visually
-by drawing a border (or outline) in the specified
-<B>color</B>
-(default: black). For
-<B>width</B>
-the program accepts decimal points [floating points] as well as integers.
-Note: it is
-important the user enter the instruction <B>end</B> even if a color is not
-chosen.
-(It is hoped that in the future the outline of a different raster map
-layer other than the one currently being painted may be placed on the map.)
-
-<P>
-
-This example would outline the category areas of the
-<EM>soils</EM>
-raster map layer
-in grey.
-<PRE>
-EXAMPLE:
- <B>raster</B> soils
- <B>outline</B>
- <B>color</B> grey
- <B>width</B> 2
- <B>end</B>
-</PRE>
-<P>
-
-
-<a name="paper"></a>
-<H2>paper</H2>
-
-Specifies paper size and margins.
-<PRE>
-USAGE: <B>paper</B> paper name
- <B>height</B> #
- <B>width</B> #
- <B>left</B> #
- <B>right</B> #
- <B>bottom</B> #
- <B>top</B> #
- <B>end</B>
-</PRE>
-<B>paper</B> may select predefined paper name
- (a4,a3,a2,a1,a0,us-legal,us-letter,us-tabloid).
- Default paper size is a4. The measures are defined in <em>inches</em>.
-<B>left</B>, <B>right</B>, <B>bottom</B> and <B>top</B> are paper margins.
-If the plot is rotated with the <b>-r</b> command line flag, measures
-are applied to the <em>rotated</em> page.
-<P>
-
-<PRE>
-EXAMPLE:
- <B>paper</B> a3
- <B>end</B>
-</PRE>
-<P>
-<PRE>
-EXAMPLE:
- <B>paper</B>
- <B>width</B> 10
- <B>height</B> 10
- <B>left</B> 2
- <B>right</B> 2
- <B>bottom</B> 2
- <B>top</B> 2
- <B>end</B>
-</PRE>
-<P>
-
-
-<a name="point"></a>
-<H2>point</H2>
-
-Places additional points or icons on the output map.
-<PRE>
-USAGE: <B>point</B> east north
- <B>point</B> x% y%
- <B>color</B> color
- <B>fcolor</B> color
- <B>symbol</B> symbol group/name
- <B>size</B> #
- <B>rotate</B> #
- <B>masked</B> [y|n]
- <B>end</B>
-</PRE>
-The point location is entered in the main instruction line by giving either the map
-coordinates or by using percentages of the geographic region.
-The user may also specify the point <B>color</B>,
-the <B>size</B> of symbol in points,
-the rotation angle (in degrees CCW),
-and whether the point is to be <B>masked</B> by the current mask.
-(See manual entry for <EM> <A HREF="r.mask.html">r.mask</A>
-</EM> for more information on the mask.)
-<P>
-
-This example would place a purple diamond (from icon file
-<EM>diamond</EM>) at the point (E456000 N7890000). This diamond would be the
-the size of a 15 points and would not be masked by the current mask.
-<PRE>
-EXAMPLE:
- <B>point</B> 456000 7890000
- <B>fcolor</B> purple
- <B>color</B> black
- <B>symbol</B> basic/diamond
- <B>size</B> 15
- <B>masked</B> n
- <B>end</B>
-</PRE>
-Of course, multiple points may be drawn with multiple
-<EM>point</EM>
-instructions.
-<P>
-
-
-<a name="psfile"></a>
-<H2>psfile</H2>
-
-Copies a file containing PostScript commands into the output file.
-
-<P>
-
-<B>Note:</B>
-<EM>ps.map</EM>
-will not search for this file. The user must be in the
-correct directory or specify the full path on the <B>psfile</B> instruction.
-(Note to /bin/csh users: ~ won't work with this instruction).
-<PRE>
-USAGE: <B>psfile</B> filename
-</PRE>
-This example copies the file "logo.ps" into the output file.
-<PRE>
-EXAMPLE:
- <B>psfile</B> logo.ps
-</PRE>
-<P>
-
-
-<a name="raster"></a>
-<H2>raster</H2>
-
-Selects a raster map layer for output.
-<PRE>
-USAGE: <B>raster</B> mapname
-</PRE>
-For each <EM>ps.map</EM> run, only one raster map layer (or set
-of layers or imagery group; see below) can be requested. If no
-raster map layer is requested, a completely white map will be
-produced. It can be useful to select no raster map layer in
-order to provide a white background for vector maps.
-<P>
-Note that an imagery group selected with the <EM>group</EM>
-option, or a set of three raster layers selected with the
-<EM>rgb</EM> option, count as a raster map layer for the
-purposes of the preceding paragraph.
-<P>
-
-This example would paint a map of the raster map layer <EM>soils</EM>.
-
-<PRE>
-EXAMPLE:
- <B>raster</B> soils
-</PRE>
-<P>
-
-
-<a name="read"></a>
-<H2>read</H2>
-
-Provides <EM>ps.map</EM> with a previously prepared input stream.
-<PRE>
-USAGE: <B>read</B> previously prepared UNIX file
-</PRE>
-Mapping instructions can be placed into a file and read into
-<EM>ps.map.</EM>
-
-<P>
-
-<B>Note:</B>
-<EM>ps.map</EM>
-will not search for this file. The user must be in the
-correct directory or specify the full path on the <B>read</B> instruction.
-(Note to /bin/csh users: ~ won't work with this instruction).
-
-<P>
-
-This example reads the UNIX file <EM>pmap.roads</EM> into <EM>ps.map</EM>.
-This file may contain all the <EM>ps.map</EM> instructions for placing
-the vector map layer <EM>roads</EM> onto the output map.
-<PRE>
-EXAMPLE:
- <B>read</B> pmap.roads
-</PRE>
-The user may have created this file because this vector map layer
-is particularly useful for many <EM>ps.map</EM>
-outputs. By using the <B>read</B> option, the user need not enter all the input
-for the <B>vector</B> instruction, but simply <B>read</B> the previously prepared
-file with the correct instructions.
-<P>
-
-
-<a name="rectangle"></a>
-<H2>rectangle</H2>
-
-Draws rectangle on the output map.
-<PRE>
-USAGE: <B>rectangle</B> east north east north
- <B>rectangle</B> x% y% x% y%
- <B>color</B> color
- <B>fcolor</B> fill color
- <B>width</B> #
- <B>masked</B> [y|n]
- <B>end</B>
-</PRE>
-The two corners of the rectangle are entered on the main
-instruction. These points can be defined either by map coordinates or
-by using percentages of the geographic region.
-The user may also specify line
-<B>color</B>, fill color <B>fcolor</B>, <B>width</B>
-in pixels (accepts decimal points [floating points] as well as integers),
-and if the rectangle is to be <B>masked</B> by the current mask.
-(See manual entry for <EM><A HREF="r.mask.html">r.mask</A></EM>
-for more information on the mask.)
-<BR>
-Multiple rectangles may be drawn by using multiple <EM>rectangle</EM> instructions.
-<P>
-
-This example would draw a yellow rectangle filled by green from the point x=10% y=80%
-to the point x=30% y=70%. This line
-would be 2 pixels wide and would appear even if there is a mask.
-<PRE>
-EXAMPLE:
- <B>rectangle</B> 10% 80% 30% 70%
- <B>color</B> yellow
- <B>fcolor</B> green
- <B>width</B> 2
- <B>masked</B> n
- <B>end</B>
-</PRE>
-<P>
-
-
-<a name="region"></a>
-<H2>region</H2>
-
-Places the outline of a smaller geographic region
-on the output.
-<PRE>
-USAGE: <B>region</B> regionfile
- <B>color</B> color
- <B>width</B> #
- <B>end</B>
-</PRE>
-Geographic region settings are created and saved using <EM> the
-<A HREF="g.region.html">g.region</A></EM> module.
-The <EM>ps.map</EM> <EM>region</EM> option can be used to show an outline of
-a smaller region which was printed on a separate run of <EM>ps.map</EM>
-on other user-created maps.
-<P>
-The user can specify the <B>color</B>
-and the <B>width</B> in pixel units (accepts decimal points
-[floating points] as well as integers) of the outline.
-The default is a black border of one pixel width.
-<P>
-This example would place a white outline, 2 pixels wide, of the
-geographic region called <EM>fire.zones</EM> onto the output map.
-This geographic region would have been created and saved using
-<EM><A HREF="g.region.html">g.region</A></EM>.
-<PRE>
-EXAMPLE:
- <B>region</B> fire.zones
- <B>color</B> white
- <B>width</B> 2
- <B>end</B>
-</PRE>
-<P>
-
-
-<a name="rgb"></a>
-<H2>rgb</H2>
-
-Selects three raster map layers for output as an RGB color image.
-<PRE>
-USAGE: <B>rgb</B> <EM>red</EM> <EM>green</EM> <EM>blue</EM>
-</PRE>
-This is similar to <EM>raster</EM>, except that it uses three
-raster map layers instead of a single layer. The three layers
-are composed to form a color image, similar to <EM>d.rgb</EM>.
-<P>
-
-For each layer, only one of the components of the layer's color
-table is used: the red component for the red layer, and so on.
-This will give the desired result if all of the layers have a
-grey-scale color table, or if each layer's color table uses the
-hue appropriate to the layer.
-<P>
-
-
-<a name="scale"></a>
-<H2>scale</H2>
-
-Selects a scale for the output map.
-<PRE>
-USAGE: <B>scale</B> <EM>scale</EM>
-</PRE>
-The scale can be selected either as:
-<DL>
-<DT>
-<DD>a relative ratio, e.g. 1:25000;
-<DT>
-<DD>an absolute width of the printed map, e.g. 10 inches;
-<DT>
-<DD>the number of printed paper panels, e.g. 3 panels
-<EM>.I</EM>
-(at the present time, only 1 panel is supported);
-<DT>
-<DD>the number of miles per inch, e.g. 1 inch equals 4 miles.
-</DD>
-</DL>
-<P>
-
-This example would set the scale of the map to 1 unit = 25000
-units.
-<PRE>
-EXAMPLE:
- <B>scale</B> 1:25000
-</PRE>
-<P>
-This instruction is identical to the <EM>scale</EM> command line parameter.
-<BR>
-<em>NOTE: Using "scale" from the command line is depreciated and while
-still provided for compatibility reasons it will be removed in the future.
-Please use the "scale" mapping instruction instead.</em>
-<P>
-
-
-<a name="scalebar"></a>
-<H2>scalebar</H2>
-
-Draws a scalebar on the map.
-<PRE>
-USAGE: <B>scalebar</B> [f|s]
- <B>where</B> x y
- <B>length</B> scale length
- <B>height</B> scale height
- <B>segment</B> no. segments
- <B>numbers</B> #
- <B>fontsize</B> font size
- <B>background</B> [Y|n]
- <B>end</B>
-</PRE>
-Draw one of two types of scale bar.
-Fancy (f) draws alternating black and white scale boxes.
-Simple (s) draws a plain line scale. The default type is fancy.
-The subsection instructions allow the user to set <B>where</B> the scalebar
-is placed, the <B>length</B> of the scalebar (in geographic coordinate
-system units), the <B>height</B> of the scalebar in inches, and the number of
-<B>segments</B> (or tics for simple). The <B>number</B> of annotations
-numbers every n-th segment.
-The <B>background</B> command can turn off the background box for the text.
-<P>
-The scalebar <B>length</B> is the only required argument. The defaults are a
-fancy scalebar with 4 segments, each segment labeled, and a height of 0.1
-inches. The default location is 2 inches from the top of the page and
-halfway across.
-<P>
-NOTE: The scalebar is centered on the location given.
-<P>
-This example draws a simple scalebar 1000 meters (for a metered database, like UTM) long,
-with tics every 200 meters, labeled every second tic. The scalebar is drawn 5 inches from the top and 4 inches from the left and is 0.25 inches high.
-<PRE>
-EXAMPLE:
- <B>scalebar</B> s
- <B>where</B> 4 5
- <B>length</B> 1000
- <B>height</B> 0.25
- <B>segment</B> 5
- <B>numbers</B> 2
- <B>end</B>
-</PRE>
-
-
-<a name="setcolor"></a>
-<H2>setcolor</H2>
-
-Overrides the color assigned to one or more categories
-of the raster map layer.
-<PRE>
-USAGE: <B>setcolor</B> cat(s) color
-</PRE>
-This example would set the color for categories 2,5 and 8 of the raster
-map layer <EM>watersheds</EM> to white and category 10 to green.
-(<B>NOTE</B>: no spaces are inserted between the category values.)
-<PRE>
-EXAMPLE:
- <B>raster</B> watersheds
- <B>setcolor</B> 2,5,8 white
- <B>setcolor</B> 10 green
-</PRE>
-Of course,
-<EM>setcolor</EM>
-can be requested more than once to override the default color for additional
-categories. More than one category can be changed for each request by listing
-all the category values separated by commas (but with no spaces).
-<P>
-
-
-<a name="text"></a>
-<H2>text</H2>
-
-Places text on the map.
-<PRE>
-USAGE: <B>text</B> east north text
- <B>text</B> x% y% text
- <B>font</B> fontname
- <B>color</B> color|none
- <B>width</B> #
- <B>hcolor</B> color|none
- <B>hwidth</B> #
- <B>background</B> color|none
- <B>border</B> color|none
- <B>fontsize</B> font size
- <B>size</B> #
- <B>ref</B> reference point
- <B>rotate</B> degrees CCW
- <B>xoffset</B> #
- <B>yoffset</B> #
- <B>opaque</B> [y|n]
- <B>end</B>
-</PRE>
-The user specifies where the text will be placed by
-providing map coordinates or percentages of the geographic region.
-The text follows these coordinates on the same instruction line.
-More than one line of text can be specified by notating the end of a line with
-<B>\n</B>
-(e.g. USA<B>\n</B>CERL).
-<P>
-The user can then specify various text features:
-<P>
-<B>font:</B>
-the PostScript font. Common possibilities are listed at the start of this
-help page. The default is <tt>Helvetica</tt>.
-<P>
-<B>color</B>
-(see <a href="#NAMED_COLORS">NAMED COLORS</a>);
-<P>
-<B>width</B>
-of the lines used to draw the text to make thicker letters
-(accepts decimal points [floating points] as well as integers);
-<P>
-<B>size</B> and <B>fontsize.</B>
-<B>size</B> gives the vertical height of the letters in meters on the
-ground (text size will grow or shrink depending on the scale at which
-the map is painted). Alternatively <B>fontsize</B> can set the font
-size directly. If neither <B>size</B> or <B>fontsize</B> is given, a
-default font size of 10 will be used;
-<P>
-the highlight color (<B>hcolor</B>) and
-the width of the highlight color (<B>hwidth</B>);
-<P>
-the text-enclosing-box <B>background</B> color;
-the text box <B>border</B> color;
-<P>
-<B>ref.</B>
-This reference point specifies the text handle - what
-part of the text should be placed on the location specified by the map
-coordinates. Reference points can refer to:
-[lower|upper|center] [left|right|center] of the text to be printed; The default is center center, i.e the text is centered on the reference point.
-<P>
-<B>rotate</B>
-sets the text rotation angle, measured in degrees counter-clockwise.
-<P>
-<B>yoffset</B>,
-which provides finer placement of text by shifting the
-text a vertical distance in pixels from the specified north. The vertical
-offset will shift the location to the south if positive, north if negative;
-<P>
-<B>xoffset</B>,
-which shifts the text a horizontal distance in pixels from
-the specified east The horizontal offset will shift the location east if
-positive, west if negative;
-<P>
-<B>opaque</B>,
-whether or not the text should be <B>opaque</B> to vectors. Entering <B>no</B>
-to the opaque option will allow the user to see any vectors which go
-through the text's background box. Otherwise, they will end at the box's edge.
-<P>
-<BR>
-The following example would place the text <EM>SPEARFISH LAND COVER</EM>
-at the coordinates E650000 N7365000. The text would be a total of
-3 pixels wide (2 pixels of red text and 1 pixel black highlight), have a white
-background enclosed in a red box, and be 500 meters in size. The lower right
-corner of the text would be centered over the coordinates provided. All
-vectors on the map would stop at the border of this text.
-<PRE>
-EXAMPLE:
- <B>text</B> 650000 7365000 SPEARFISH LAND COVER
- <B>font</B> romand
- <B>color</B> red
- <B>width</B> 2
- <B>hcolor</B> black
- <B>hwidth</B> 1
- <B>background</B> white
- <B>border</B> red
- <B>size</B> 500
- <B>ref</B> lower left
- <B>opaque</B> y
- <B>end</B>
-</PRE>
-<P>
-
-
-<a name="vareas"></a>
-<H2>vareas</H2>
-
-Selects a vector map layer for output and plots areas.
-<PRE>
-USAGE: <B>vareas</B> vectormap
- <B>layer</B> # (layer number used with cats/where option)
- <B>cats</B> list of categories (e.g. 1,3,5-7)
- <B>where</B> SQL where statement
- <B>masked</B> [y|n]
- <B>color</B> color
- <B>fcolor</B> color
- <B>rgbcolumn</B> column
- <B>width</B> #
- <B>label</B> label to use in legend
- <B>lpos</B> position in legend
- <B>pat</B> pattern file
- <B>pwidth</B> #
- <B>scale</B> #
- <B>end</B>
-</PRE>
-The user can specify:
-<P>
-<B>color</B> - color of the vector lines or area boundaries;
-<P>
-<B>fcolor</B> - the area fill color;
-<P>
-<B>rgbcolumn</B> - name of color definition column used for the area fill color;
-<P>
-<B>width</B> - width of the vectors lines or area boundaries in pixels
-(accepts decimal points [floating points] as well as integers);
-<P>
-<B>masked</B> - whether or not the raster map layer is to be masked
-by the current mask;
-(see manual entry <EM><A HREF="r.mask.html">r.mask</A></EM>
-for more information on the mask)
-<P>
-<B>cats</B> - which categories should be plotted (default is all);
-<P>
-<B>where</B> - select features using a SQL where statement.
-For example: <tt>vlastnik = 'Cimrman'</tt>;
-<P>
-<B>label</B> - for description in <a href="#vlegend">vlegend</a>.
-Default is: map(mapset);
-<P>
-<B>lpos</B> - position vector is plotted in legend. If lpos is
-0 then this vector is omitted in legend. If more vectors used the
-same lpos then their symbols in legend are merged and label for
-first vector is used.
-<P>
-<B>pat</B> - full path to pattern file. The pattern file contains header and
-simple PostScript commands. It is similar to EPS but more limited, meaning that
-while each pattern file is a true EPS file, most EPS files are not useful as pattern
-files because they contain restricted commands. Color and width of patterns are set
-by <B>fcolor</B> (red, green, ..., none, R:G:B) and <B>width</B> until overwritten
-in the pattern file.
-Pattern may be scaled with the <b>scale</b> command. Several standard hatching
-patterns are provided in <tt>$GISBASE/etc/paint/patterns/</tt>.
-Demonstrative images can be found on the
-<a href="http://grass.gdf-hannover.de/wiki/AreaFillPatterns">GRASS Wiki site</a>.
-
-You can also create your own custom pattern files in a text editor.
-Example of pattern file:
-
-<div class="code"><PRE>
-%!PS-Adobe-2.0 EPSF-1.2
-%%BoundingBox: 0 0 10 10
-newpath
-5 0 moveto
-5 10 lineto
-stroke
-</PRE></div>
-
-
-<P>
-<B>scale</B> - pattern scale
-<P>
-<B>pwidth</B> - pattern line width, width is used by pattern until the width is overwritten
-in pattern file.
-<P>
-
-<PRE>
-EXAMPLE:
- <B>vareas</B> forest
- <B>color</B> blue
- <B>width</B> 1
- <B>masked</B> y
- <B>cats</B> 2,5-7
- <B>end</B>
-</PRE>
-<P>
-
-
-<a name="vlines"></a>
-<H2>vlines</H2>
-
-Selects a vector map layer for output and plots lines.
-<PRE>
-USAGE: <B>vlines</B> vectormap
- <B>type</B> line and/or boundary
- <B>layer</B> # (layer number used with cats/where option)
- <B>cats</B> list of categories (e.g. 1,3,5-7)
- <B>where</B> SQL where statement like: vlastnik = 'Cimrman'
- <B>masked</B> [y|n]
- <B>color</B> color
- <B>rgbcolumn</B> column
- <B>width</B> #
- <B>cwidth</B> #
- <B>hcolor</B> color
- <B>hwidth</B> #
- <B>offset</B> #
- <B>coffset</B> #
- <B>ref</B> left|right
- <B>style</B> 00001111
- <B>label</B> label
- <B>lpos</B> #
- <B>end</B>
-</PRE>
-The user can specify:
-<P>
-<B>type</B> - the default is lines only;
-<P>
-<B>color</B> - color of the vector lines or area boundaries;
-<P>
-<B>rgbcolumn</B> - name of color definition column used for the vector lines or area boundaries;
-<P>
-<B>width</B> - width of the vectors lines or area boundaries in pixels
-(accepts decimal points [floating points] as well as integers);
-<P>
-<B>cwidth</B> - width of the vectors lines. If cwidth is used then
-width of line is equal to cwidth * category value and width is
-used in legend;
-<P>
-<B>hcolor</B> - the highlight color for the vector lines;
-<P>
-<B>hwidth</B> - the width of the highlight color in pixels;
-<P>
-<B>offset</B> (experimental) - offset for the vectors lines in pixels for plotting
-parallel lines in distance equal to offset (accepts positive or
-negative decimal points). Useful to print streets with several parallel lanes;
-<P>
-<B>coffset</B> (experimental) - offset for the vectors lines. If coffset is used then
-offset of line is equal to coffset * category value and offset is
-used in legend;
-<P>
-<B>ref</B> (experimental) - line justification.
-<P>
-<B>masked</B> - whether or not the raster map layer is to be masked
-by the current mask;
-(see manual entry <EM><A HREF="r.mask.html">r.mask</A></EM>
-for more information on the mask);
-<P>
-<B>style</B> - the line style allows the vectors
-to be dashed in different patterns. This is done by typing a
-series of numbers (0's and 1's) in a desired sequence or pattern.
-The first block of repeated zeros or ones represents "draw", the second
-block represents "blank".
-An even number of blocks will repeat the pattern, an odd number of blocks
-will alternate the pattern.
-The default is "solid";
-<P>
-<B>cats</B> - which categories should be plotted (default is all);
-<P>
-<B>label</B> - for description in <a href="#vlegend">vlegend</a>.
-Default is: map(mapset);
-<P>
-<B>lpos</B> - position vector is plotted in legend. If lpos is
-0 then this vector is omitted in legend. If more vectors used the
-same lpos then their symbols in legend are merged and label for
-first vector is used.
-<P>
-
-<PRE>
-EXAMPLE:
- <B>vlines</B> streams
- <B>color</B> blue
- <B>width</B> 2
- <B>hcolor</B> white
- <B>hwidth</B> 1
- <B>masked</B> y
- <B>cats</B> 2
- <B>label</B> Streams - category 2
- <B>end</B>
-</PRE>
-<P>
-
-
-<a name="vpoints"></a>
-<H2>vpoints</H2>
-
-Selects vector point data to be placed on the output map
-<PRE>
-USAGE: <B>vpoints</B> vectormap
- <B>type</B> point and/or centroid
- <B>layer</B> # (layer number used with cats/where/sizecol options)
- <B>cats</B> list of categories (e.g. 1,3,5-7)
- <B>where</B> SQL where statement like: vlastnik = 'Cimrman'
- <B>masked</B> [y|n]
- <B>color</B> color
- <B>fcolor</B> color
- <B>rgbcolumn</B> column
- <B>width</B> #
- <B>eps</B> epsfile
- <B>symbol</B> symbol group/name
- <B>size</B> #
- <B>sizecolumn</B> attribute column used for symbol sizing
- <B>scale</B> scaling factor for sizecolumn values
- <B>rotate</B> #
- <B>rotatecolumn</B> column
- <B>label</B> legend label
- <B>lpos</B> position in legend
- <B>end</B>
-</PRE>
-The user may specify the
-the <B>color</B> of the sites (see section on <a href="#NAMED_COLORS">NAMED COLORS</a>);
-either the GRASS <B>symbol</B> or
-the <B>eps</B> Encapsulated Postscript file to be used to represent the presence of a site
-(if '<B>$</B>' is used in the EPS file path it will be replaced by category number);
-and <B>rotate</B> (in degrees) for counter-clockwise rotation.
-<BR>
-The size of the icon (number of times larger than the size it is in
-the icon file) is typically given by the <B>size</B> option. Alternatively
-the size of the symbol or EPS graphic can be taken from an attribute column
-by using the <B>sizecolumn</B> command. The value given by <B>sizecolumn</B> may be
-scaled by using the <B>scale</B> factor setting (default scaling is 1.0).
-In a similar manner symbol color can be read from <B>rgbcolumn</B>
-and the rotation angle read from <B>rotatecolumn</B>.
-
-<PRE>
-EXAMPLE:
- <B>vpoints</B> windmills
- <B>color</B> blue
- <B>symbol</B> mills/windmill
- <B>size</B> 10
- <B>end</B>
-</PRE>
-<P>
-
-<a name="vlegend"></a>
-<H2>vlegend</H2>
-
-Prints the portion of the map legend containing the
-vector information, on or below the map.
-
-<PRE>
-USAGE: <B>vlegend</B>
- <B>where</B> x y
- <B>font</B> font name
- <B>fontsize</B> font size
- <B>width</B> width of color symbol
- <B>cols</B> number of columns to print
- <B>border</B> color|none
- <B>end</B>
-</PRE>
-The default location is immediately below the legend containing the
-scale, grid and region information, starting at the left edge of the map.
-If the <EM>where</EM> instruction is present and <EM>y</EM> is less than or
-equal to zero, the vector legend will be positioned immediately below
-the map, starting <EM>x</EM> inches from the left edge of the page.
-
-<P>
-<EM>width</EM> is the width in inches of the color symbol (for areas) in front of the
-legend text. The default is 1/24 * fontsize inches.
-<EM>cols</EM> is the number of columns to split the legend into. The default is one
-column. The maximum number of colums is 10, or equal to the number of legend entries
-if there are less than 10 entries.
-<P>
-<EM>border</EM> will draw a border around the legend using the specified color.
- (see <a href="#NAMED_COLORS">NAMED COLORS</a>)
-<P>
-Alternatively, the user can create a custom legend by using the
-<a href="#rectangle">rectangle</a>, <a href="#point">point</a>, and
-<a href="#text">text</a> instructions.
-<P>
-This example prints the vector legend
-immediately below the map and starting 4.5 inches from the left edge
-of the page, using a 12/72 inch Helvetica font.
-
-<PRE>
-EXAMPLE:
- <B>vlegend</B>
- <B>where</B> 4.5 0
- <B>font</B> Courier
- <B>fontsize</B> 12
- <B>end</B>
-</PRE>
-<P>
-
-
-<a name="end"></a>
-<H2>end</H2>
-
-Terminates input and begin painting the map.
-
-<PRE>
-USAGE: <B>end</B>
-</PRE>
-<BR>
-<P>
-
-
-
-<H2>EXAMPLE ps.map INPUT FILE</H2>
-
-The following is an example of a <EM>ps.map</EM> script file. The file has been
-named <EM>spear.soils</EM>.
-This script file can be entered at the command line:
-
-<PRE>
- <B>ps.map input=</B><EM>spear.soils</EM> <B>output=</B><EM>soils.ps</EM>
-</PRE>
-<PRE>
-
-# this ps.map example draws a map of Spearfish, SD
-<B>raster</B> soils
-<B>outline</B>
- <B>color</B> black
- <B>width</B> 1
- <B>end</B>
-<B>comments</B> soil.cmt
- <B>where</B> 1 6
- <B>font</B> Helvetica
- <B>end</B>
-<B>colortable</B> y
- <B>where</B> 1 6.5
- <B>cols</B> 4
- <B>width</B> 4
- <B>font</B> Helvetica
- <B>end</B>
-<B>setcolor</B> 6,8,9 white
-<B>setcolor</B> 10 green
-<B>vlines</B> roads
- <B>width</B> 2
- <B>style</B> 0111
- <B>color</B> grey
- <B>masked</B> n
- <B>end</B>
-<B>vlegend</B>
- <B>where</B> 4.5 0
- <B>font</B> Courier
- <B>fontsize</B> 8
- <B>end</B>
-<B>text</B> 30% 100% SPEARFISH SOILS MAP
- <B>color</B> red
- <B>width</B> 1
- <B>hcolor</B> black
- <B>hwidth</B> 1
- <B>background</B> white
- <B>border</B> red
- <B>size</B> 500
- <B>ref</B> lower left
- <B>end</B>
-<B>line</B> 606969.73 3423092.91 616969.73 3423092.91
- <B>color</B> yellow
- <B>width</B> 2
- <B>end</B>
-<B>point</B> 40% 60%
- <B>color</B> purple
- <B>symbol</B> basic/diamond
- <B>size</B> 25
- <B>masked</B> n
- <B>end</B>
-<B>scale</B> 1:125000
-<B>scalebar</B> f
- <B>where</B> 4.5 6.5
- <B>length</B> 5000
- <B>height</B> 0.05
- <B>segment</B> 5
- <B>numbers</B> 5
- <B>end</B>
-<B>geogrid</B> 60 s
- <B>color</B> blue
- <B>numbers</B> 2 yellow
- <B>end</B>
-<B>paper</B> a4
- <B>end</B>
-<B>end</B>
-
-</PRE>
-
-<P>
-More examples can be found on the
-<a href="http://grass.osgeo.org/wiki/Ps.map_scripts">GRASS Wiki</a>
-help site.
-<P>
-
-
-<H2>CHANGES BETWEEN VERSION 5.0.x/5.4.x and 6.0</H2>
-<UL>
-<LI>Devices and ps.select do not exist any more. Paper is defined by the
-<EM>paper</EM> instruction.</LI>
-<LI><EM>vpoints</EM> are used instead of <EM>sites</EM> (points are read from vector).</LI>
-<LI><EM>vector</EM> is substituted by <EM>vpoints</EM>, <EM>vlines</EM> and <EM>vareas</EM>.</LI>
-<LI>Symbols are used instead of icons (different format and directory).</LI>
-<LI>Map legend can be printed in columns.</LI>
-</UL>
-
-
-<H2>SEE ALSO</H2>
-<em>
-<a href="g.region.html">g.region</a>,
-<a href="v.label.html">v.label</a>
-</em>
-
-<H2>AUTHOR</H2>
-
-Paul Carlson, USDA, SCS, NHQ-CGIS<BR>
-Modifications: Radim Blazek, Glynn Clements, Bob Covill, Hamish Bowman
-<p>
-<i>Last changed: $Date$</i>
Copied: grass/trunk/ps/ps.map/ps.map.html (from rev 32770, grass/trunk/ps/ps.map/description.html)
===================================================================
--- grass/trunk/ps/ps.map/ps.map.html (rev 0)
+++ grass/trunk/ps/ps.map/ps.map.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,1606 @@
+<H2>DESCRIPTION</H2>
+
+<EM>ps.map</EM> is a cartographic mapping program for producing high quality
+hardcopy maps in PostScript format. Output can include a raster map, any
+number of vector overlays, text labels, decorations, and other spatial data.
+
+<P>
+A file of mapping instructions that describes the various spatial and textual
+information to be printed must be prepared prior to running <EM>ps.map</EM>.
+
+
+<H2>NOTES</H2>
+
+<P>
+The order of commands is generally unimportant but may affect how some layers
+are drawn. For example to plot <B>vpoints</B> above <B>vareas</B> list the
+<B>vpoints</B> entry first. Raster maps are always drawn first, and only a
+single raster map (or 3 if part of a RGB group) may be used.
+
+<P>
+The hash character ('<tt>#</tt>') may be used at the beginning of a line
+to indicate that the line is a comment. Blank lines will also be ignored.
+
+<P>
+Be aware that some mapping instructions require the <i>end</i> command
+and some do not. Any instruction that allows subcommands will require
+it, any instruction that does not allow subcommands will not.
+
+<P>
+The resolution and extent of raster maps plotted with <EM>ps.map</EM> are
+controlled by the current region settings via the
+<a href="g.region.html">g.region</a> module. The output filesize is largely
+a function of the region resolution, so special care should be taken
+if working with large raster datasets. For example if the desired output is
+US-Letter sized paper at 300dpi, with 1" margins and the raster filling the
+entire page, the usable area on the page will be 6.5" x 9", which at 300
+dots/inch is equivalent to a region of 1950 columns x 2700 rows (see
+"<tt>g.region -p</tt>"). Any higher resolution settings will make the
+output file larger, but with a consumer printer you probably won't be able
+to resolve any better detail in the hardcopy.
+
+<P>
+The user can specify negative or greater than 100 percentage values for
+positioning several map decorations and embedded EPS-files, to move them
+outside the current map box region (for example to position a caption,
+barscale, or legend above or below the map box).
+
+<P>
+One "pixel" is 1/72 of an inch.
+
+<P>
+For users wanting to use special characters (such as accented characters) it
+is important to note that <em>ps.map</em> uses <tt>ISO-8859-1</tt> encoding.
+This means that your instructions file will have to be encoded in this
+encoding. If you normally work in a different encoding environment (such as
+<tt>UTF-8</tt>), you have to transform your file to the <tt>ISO-8859-1</tt>
+encoding, for example by using the <tt>iconv</tt> utility:
+</P>
+<DIV class="code"><PRE>
+iconv -f UTF-8 -t ISO_8859-1 utf_file > iso_file
+</PRE></DIV>
+
+
+<P><P>
+
+<H2>MAPPING INSTRUCTIONS</H2>
+
+The mapping instructions allow the user to specify various spatial data
+to be plotted. These instructions are normally prepared in a regular
+text file using a system editor. Some instructions are single line
+instructions while others are multiple line. Multiple line instructions
+consist of the main instruction followed by a subsection of one or more
+additional instructions and are terminated with an <i>end</i> instruction.
+<P>
+
+<h3>Instruction keywords:</h3>
+[
+<a href="#border">border</a> |
+<a href="#colortable">colortable</a> |
+<a href="#comments">comments</a> |
+<a href="#copies">copies</a> |
+<a href="#eps">eps</a> |
+<a href="#geogrid">geogrid</a> |
+<a href="#greyrast">greyrast</a> |
+<a href="#grid">grid</a> |
+<a href="#group">group</a> |
+<a href="#header">header</a> |
+<a href="#labels">labels</a> |
+<a href="#line">line</a> |
+<a href="#mapinfo">mapinfo</a> |
+<a href="#maploc">maploc</a> |
+<a href="#maskcolor">maskcolor</a> |
+<a href="#outline">outline</a> |
+<a href="#paper">paper</a> |
+<a href="#point">point</a> |
+<a href="#psfile">psfile</a> |
+<a href="#raster">raster</a> |
+<a href="#read">read</a> |
+<a href="#rectangle">rectangle</a> |
+<a href="#region">region</a> |
+<a href="#rgb">rgb</a> |
+<a href="#scale">scale</a> |
+<a href="#scalebar">scalebar</a> |
+<a href="#setcolor">setcolor</a> |
+<a href="#text">text</a> |
+<a href="#vareas">vareas</a> |
+<a href="#vlines">vlines</a> |
+<a href="#vpoints">vpoints</a> |
+<a href="#vlegend">vlegend</a> |
+<a href="#end">end</a>
+]
+
+
+<h3>Common instructions</h3>
+Instructions that may be included in the subsection under several
+different main instructions are:
+
+<DL>
+<DT><B>where</B> <EM>x y</EM>
+
+<DD>The top left corner of the bounding box of the item to be plotted
+is located <EM>x</EM> inches from the left edge of the paper and
+<EM>y</EM> inches from the top edge of the paper. If <EM>x</EM> is less than
+or equal to zero, the default horizontal location is used. If <EM>y</EM>
+is less than or equal to zero, the default vertical location is used.
+
+<DT><B>font</B> <EM>font name</EM>
+
+<DD>The name of the PostScript font.
+Fonts present in all PostScript implementations are:
+<tt>
+Times-Roman,
+Times-Italic,
+Times-Bold,
+Times-BoldItalic,
+Helvetica,
+Helvetica-Oblique,
+Helvetica-Bold,
+Helvetica-BoldOblique,
+Courier,
+Courier-Oblique,
+Courier-Bold,
+and
+Courier-BoldOblique</tt>.
+<BR>
+The default is Helvetica.
+</DD>
+
+
+<DT><B>fontsize</B> <EM>font size</EM>
+
+<DD>The size of the PostScript font (in 1/72nds of an inch).
+The default is 10.
+</DD>
+
+
+<a name="NAMED_COLORS"></a>
+<DT><B>color</B> <EM>name</EM>
+
+<DD>The following colors names are accepted by <EM>ps.map</EM>:
+<tt>
+aqua,
+black,
+blue,
+brown,
+cyan,
+gray,
+grey,
+green,
+indigo,
+magenta,
+orange,
+purple,
+red,
+violet,
+white,
+yellow
+</tt>.
+<BR><BR>
+For vectors and some plotting commands you can also specify
+'<tt>none</tt>' or '<tt>R:G:B</tt>' (e.g '<tt>255:0:0</tt>').
+</DD>
+</DL>
+<P>
+<BR>
+
+<h3>Command usage</h3>
+
+<a name="border"></a>
+<H2>border</H2>
+
+Controls the border which is drawn around the map area.
+<PRE>
+USAGE: <B>border</B> [y|n]
+ <B>color</B> color
+ <B>width</B> #
+ <B>end</B>
+</PRE>
+The <B>color</B> may be either a standard GRASS color, a R:G:B triplet,
+or "none". The width is specified in points, unless followed by an "i"
+in which case it is measured in inches.
+The default is a black border box of width 1 point.
+<P>
+The border can be turned off completely with the
+"<tt>border n</tt>" instruction. In this case
+the <B>end</B> command should not be given as the
+main command will be treated as a single line instruction.
+<P>
+
+This example would create a grey border 0.1" wide.
+<PRE>
+EXAMPLE:
+ <B>border</B>
+ <B>color</B> grey
+ <B>width</B> 0.1i
+ <B>end</B>
+</PRE>
+<P>
+
+
+<a name="colortable"></a>
+<H2>colortable</H2>
+
+Prints the color table for the raster map layer anywhere on the page.
+<PRE>
+USAGE: <B>colortable</B> [y|n]
+ <B>where</B> x y
+ <B>raster</B> raster map
+ <B>range</B> minimum maximum
+ <B>width</B> table width
+ <B>height</B> table height (FP legend only)
+ <B>cols</B> table columns
+ <B>font</B> font name
+ <B>fontsize</B> font size
+ <B>color</B> text color
+ <B>nodata</B> [Y|n]
+ <B>tickbar</B> [y|N]
+ <B>end</B>
+</PRE>
+The color table will display the colors for each raster map layer
+category value and the category label.
+If <B>raster</B> is omitted, the colortable defaults to a previously registered raster layer.
+The legend's <B>range</B> can be adjusted for floating point rasters, but if
+set beyond the extent of the map's range be sure that you have set up color
+rules with <em>r.colors</em> which cover this range.
+The default location for the colortable is immediately below any other
+map legend information, starting at the left margin.
+The default text color is black.
+Omitting the <B>colortable</B> instruction would result in
+no color table. For floating point legends <B>width</B> is width of color
+band only. <B>height</B> is used only for floating point legend.
+Adding the <B>nodata n</B> instruction will prevent the "no data" box
+from being drawn (category based legends only).
+Adding the <B>tickbar y</B> instruction will change the tick mark style
+so that ticks are drawn across the color table instead of protruding out
+to the right (floating point legends only).
+<P>
+<B>Note</B>: Be careful about asking for color tables for
+raster map layers which have many categories, such as elevation.
+This could result in the printing of an extremely long color table!
+<P>
+Another issue is that the color table only includes categories which
+have a label. If there are only a few categories, you can use
+r.support to manually add labels. If there are too many categories to
+do this, you could write a script to add dummy labels to the cats file<br>
+(<gisdbase>/<location>/<mapset>/cats/<mapname>).
+<P>
+If the colortable is turned off with a "<tt>colortable n</tt>"
+instruction the <B>end</B> command should not be given as the
+main command will be treated as a single line instruction.
+
+<P>
+
+This example would print a color table immediately below any other map legend
+information, starting at the left margin, with 4 columns:
+<PRE>
+EXAMPLE:
+ <B>colortable</B> y
+ <B>cols</B> 4
+ <B>width</B> 4
+ <B>end</B>
+</PRE>
+<P>
+
+
+<a name="comments"></a>
+<H2>comments</H2>
+
+Prints comments anywhere on the page.
+<PRE>
+USAGE: <B>comments</B> commentfile
+ <B>where</B> x y
+ <B>font</B> font name
+ <B>fontsize</B> font size
+ <B>color</B> text color
+ <B>end</B>
+</PRE>
+The default location is immediately below the last item item printed,
+starting at the left margin. The default text color is black.
+<P>
+If you wish to use parentheses spanning multiple lines you will need to
+quote them with a backslash to prevent the PostScript interpreter from
+getting confused. e.g. '<B><TT>\(</TT></B>' and '<B><TT>\)</TT></B>'
+
+<P>
+
+This example prints in blue
+whatever is in the file <EM>veg.comments</EM> starting at
+1.5 inches from the left edge of the page and 7.25 inches from the top of
+the page, using a 15/72 inch Helvetica Bold font.
+<PRE>
+EXAMPLE:
+ <B>raster</B> vegetation
+ <B>comments</B> veg.comments
+ <B>where</B> 1.5 7.25
+ <B>font</B> Helvetica Bold
+ <B>fontsize</B> 15
+ <B>color</B> blue
+ <B>end</B>
+</PRE>
+Presumably, the file
+<EM>veg.comments</EM>
+contain comments
+pertaining to the raster map layer <EM>vegetation</EM>,
+such as "This map was created by classifying a LANDSAT TM image".
+<P>
+
+
+<a name="copies"></a>
+<H2>copies</H2>
+
+Specifies the number of copies to be printed.
+<PRE>
+USAGE: <B>copies</B> n
+</PRE>
+Each page will be printed n times.
+<P>
+This instruction is identical to the <EM>copies</EM> command line parameter.
+<P>
+
+
+<a name="eps"></a>
+<H2>eps</H2>
+
+Places EPS (Encapsulated PostScript) pictures on the output map.
+<PRE>
+USAGE: <B>eps</B> east north
+ <B>eps</B> x% y%
+ <B>epsfile</B> EPS file
+ <B>scale</B> #
+ <B>rotate</B> #
+ <B>masked</B> [y|n]
+ <B>end</B>
+</PRE>
+The EPS picture location is entered in the main
+instruction line by giving either the map
+coordinates or by using percentages of the geographic region.
+The EPS picture will be <i>centered</i> at the given position.
+The user must specify full EPS file path <B>epsfile</B>.
+The user may also specify the <B>scale</B> of the icon
+(default is 1.0), the <B>rotate</B> i.e. rotation in degrees
+(default is 0)
+and whether the point is to be <B>masked</B>
+by the current mask.
+(See manual entry for <EM><A HREF="r.mask.html">r.mask</A></EM>
+for more information on the mask.)
+<P>
+
+This example would place a EPS file ./epsf/logo.eps
+at the point (E456000 N7890000). This picture would be
+rotated 20 degrees clockwise, 3 times bigger than
+in original file and would not be masked by the current mask.
+<PRE>
+EXAMPLE:
+ <B>eps</B> 456000 7890000
+ <B>epsfile</B> ./epsf/logo.eps
+ <B>scale</B> 3
+ <B>rotate</B> 20
+ <B>masked</B> n
+ <B>end</B>
+</PRE>
+Of course, multiple EPS pictures may be drawn with multiple
+<EM>eps</EM>
+instructions.
+<P>
+
+
+<a name="geogrid"></a>
+<H2>geogrid</H2>
+
+Overlays a geographic grid onto the output map.
+<PRE>
+USAGE: <B>geogrid</B> spacing unit
+ <B>color</B> color
+ <B>numbers</B> # [color]
+ <B>font</B> font name
+ <B>fontsize</B> font size
+ <B>width</B> #
+ <B>end</B>
+</PRE>
+The <B>spacing</B> and spacing unit of the geographic grid is given
+on the main instruction line. The <B>spacing</B> unit is given as one of <B>d</B> for
+degrees, <B>m</B> for minutes, and <B>s</B> for seconds.
+The subsection instructions allow the user to specify
+the <B>color</B> of the geographic grid lines,
+whether coordinate <B>numbers</B> should appear
+on the geographic grid lines, the <B>width</B>
+of the lines (accepts decimal points [floating points]
+as well as integers), and
+if they should appear every grid line (1), every other grid line
+(2), etc., and what color the numbers should be. The defaults are
+black grid lines, unnumbered.
+
+<P>
+
+NOTE: The <B>geogrid</B> draws grid numbers on the east and south borders of the map.
+
+<P>
+
+This example would overlay a blue geographic grid with a spacing of 30 minutes
+onto the output map. Alternate grid
+lines would be numbered with yellow numbers.
+<PRE>
+EXAMPLE:
+ <B>geogrid</B> 30 m
+ <B>color</B> blue
+ <B>numbers</B> 2 yellow
+ <B>end</B>
+</PRE>
+<P>
+
+
+<a name="greyrast"></a>
+<H2>greyrast</H2>
+
+Selects a raster map layer for output in shades of grey.
+<PRE>
+USAGE: <B>greyrast</B> mapname
+</PRE>
+For each
+<EM>ps.map</EM>
+run, only one raster map layer can be requested (using either the
+<EM>greyrast</EM> or the <EM>raster</EM> instruction).
+<P>
+
+
+<a name="grid"></a>
+<H2>grid</H2>
+
+Overlays a coordinate grid onto the output map.
+<PRE>
+USAGE: <B>grid</B> spacing
+ <B>color</B> color
+ <B>numbers</B> # [color]
+ <B>cross</B> cross size
+ <B>font</B> font name
+ <B>fontsize</B> font size
+ <B>width</B> #
+ <B>end</B>
+</PRE>
+The <B>spacing</B> of the grid is given (in the geographic coordinate
+system units) on the main instruction line. The subsection instructions
+allow the user to specify
+the <B>color</B> of the grid lines,
+whether coordinate <B>numbers</B> should appear
+on the grid lines, and if they
+should appear every grid line (1), every other grid line
+(2), etc., and what color the numbers should be.
+The <B>cross</B> argument draws grid intersection crosses instead of grid lines,
+with cross size given in geographic coordinate system units.
+The defaults are black grid lines, unnumbered.
+
+<P>
+
+This example would overlay a green grid with a spacing of 10000 meters
+(for a metered database, like UTM) onto the output map. Alternate grid
+lines would be numbered with red numbers.
+<PRE>
+EXAMPLE:
+ <B>grid</B> 10000
+ <B>color</B> green
+ <B>numbers</B> 2 red
+ <B>end</B>
+</PRE>
+<P>
+
+
+<a name="group"></a>
+<H2>group</H2>
+
+Selects an RGB imagery group for output.
+<PRE>
+USAGE: <B>group</B> <EM>groupname</EM>
+</PRE>
+This is similar to <EM>raster</EM>, except that it uses an imagery group
+instead of a raster map layer. The group must contain three raster map
+layers, comprising the red, green and blue bands of the image.
+<P>
+
+
+<a name="header"></a>
+<H2>header</H2>
+
+Prints the map header above the map.
+<PRE>
+USAGE: <B>header</B>
+ <B>file</B> header file
+ <B>font</B> font name
+ <B>fontsize</B> font size
+ <B>color</B> text color
+ <B>end</B>
+</PRE>
+If the <EM>file</EM> sub-instruction is absent the header will consist
+of the map's title <!-- from hist file -->
+and the location's description.<!-- PERMANENT/MYNAME -->
+The text will be centered on the page above the map.
+The default text color is black.
+
+<P>
+
+This example prints (in red) whatever is in the file <EM>soils.hdr</EM> above
+the map, using a 20/72 inch <tt>Courier</tt> font.
+<PRE>
+EXAMPLE:
+ <B>header</B>
+ <B>file</B> soils.hdr
+ <B>font</B> Courier
+ <B>fontsize</B> 20
+ <B>color</B> red
+ <B>end</B>
+</PRE>
+<P>
+
+
+<a name="labels"></a>
+<H2>labels</H2>
+
+Selects a labels file for output (see manual entry for
+<EM>
+<A HREF="v.label.html">v.label</A>
+).</EM>
+<PRE>
+USAGE: <B>labels</B> labelfile
+ <B>font</B> font name
+ <B>end</B>
+</PRE>
+<P>
+NOTE: ps.map can read new option 'ROTATE:' from labels file, which
+specifies counter clockwise rotation in degrees.
+<P>
+This example would paint labels from the labels file called
+<EM>town.names</EM>. Presumably, these labels would indicate the names of
+towns on the map.
+<PRE>
+EXAMPLE:
+ <B>labels</B> town.names
+ <B>end</B>
+</PRE>
+<P>
+
+
+<a name="line"></a>
+<H2>line</H2>
+
+Draws lines on the output map.
+<PRE>
+USAGE: <B>line</B> east north east north
+ <B>line</B> x% y% x% y%
+ <B>color</B> color
+ <B>width</B> #
+ <B>masked</B> [y|n]
+ <B>end</B>
+</PRE>
+The beginning and ending points of the line are entered on the main
+instruction. These points can be defined either by map coordinates or
+by using percentages of the geographic region.
+The user may also specify line
+<B>color</B>,
+<B>width</B>
+in pixels (accepts decimal points [floating points] as well as integers),
+and if the line is to be <B>masked</B> by the current mask.
+(See manual entry for <EM><A HREF="r.mask.html">r.mask</A>
+</EM> for more information on the mask.)
+<P>
+
+This example would draw a yellow line from the point x=10% y=80%
+to the point x=30% y=70%. This line
+would be 2 pixels wide and would appear even if there is a mask.
+<PRE>
+EXAMPLE:
+ <B>line</B> 10% 80% 30% 70%
+ <B>color</B> yellow
+ <B>width</B> 2
+ <B>masked</B> n
+ <B>end</B>
+</PRE>
+Of course, multiple lines may be drawn with multiple
+<EM>line</EM>
+instructions.
+<P>
+
+
+<a name="mapinfo"></a>
+<H2>mapinfo</H2>
+
+Prints the portion of the map legend containing the scale, grid and
+region information, on or below the map.
+<PRE>
+USAGE: <B>mapinfo</B>
+ <B>where</B> x y
+ <B>font</B> font name
+ <B>fontsize</B> font size
+ <B>color</B> text color
+ <B>background</B> box color|none
+ <B>border</B> color|none
+ <B>end</B>
+</PRE>
+The default location is immediately below the map,
+starting at the left edge of the map.
+The default text color is black.
+The default background box color is white.
+<P>
+<EM>border</EM> will draw a border around the legend using the specified color.
+ (see <a href="#NAMED_COLORS">NAMED COLORS</a>)
+<P>
+
+This example prints (in brown) the scale, grid and region information
+immediately below the map and starting 1.5 inches from the left edge
+of the page, using a 12/72 inch <tt>Courier</tt> font.
+
+<PRE>
+EXAMPLE:
+ <B>mapinfo</B>
+ <B>where</B> 1.5 0
+ <B>font</B> Courier
+ <B>fontsize</B> 12
+ <B>color</B> brown
+ <B>end</B>
+</PRE>
+<P>
+
+
+<a name="maploc"></a>
+<H2>maploc</H2>
+
+Positions the map on the page.
+<PRE>
+USAGE: <B>maploc</B> x y [width height]
+</PRE>
+The upper left corner of the map will be positioned <EM>x</EM> inches from
+the left edge of the page and <EM>y</EM> inches from the top of the page.
+If <EM>width</EM> and <EM>height</EM> (in inches) are present, the map will be
+rescaled, if necessary, to fit.
+
+<P>
+
+This example positions the upper left corner of the map 2.0 inches from
+the left edge and 3.5 inches from the top edge of the map.
+<PRE>
+EXAMPLE:
+ <B>maploc</B> 2.0 3.5
+</PRE>
+<P>
+
+
+<a name="maskcolor"></a>
+<H2>maskcolor</H2>
+
+Color to be used for mask.
+<PRE>
+USAGE: <B>maskcolor</B> color
+</PRE>
+
+
+<a name="outline"></a>
+<H2>outline</H2>
+
+Outlines the areas of a raster map layer with a specified color.
+<PRE>
+USAGE: <B>outline</B>
+ <B>color</B> color
+ <B>width</B> width of line in pixels
+ <B>end</B>
+</PRE>
+Distinct areas of the raster map will be separated from each other visually
+by drawing a border (or outline) in the specified
+<B>color</B>
+(default: black). For
+<B>width</B>
+the program accepts decimal points [floating points] as well as integers.
+Note: it is
+important the user enter the instruction <B>end</B> even if a color is not
+chosen.
+(It is hoped that in the future the outline of a different raster map
+layer other than the one currently being painted may be placed on the map.)
+
+<P>
+
+This example would outline the category areas of the
+<EM>soils</EM>
+raster map layer
+in grey.
+<PRE>
+EXAMPLE:
+ <B>raster</B> soils
+ <B>outline</B>
+ <B>color</B> grey
+ <B>width</B> 2
+ <B>end</B>
+</PRE>
+<P>
+
+
+<a name="paper"></a>
+<H2>paper</H2>
+
+Specifies paper size and margins.
+<PRE>
+USAGE: <B>paper</B> paper name
+ <B>height</B> #
+ <B>width</B> #
+ <B>left</B> #
+ <B>right</B> #
+ <B>bottom</B> #
+ <B>top</B> #
+ <B>end</B>
+</PRE>
+<B>paper</B> may select predefined paper name
+ (a4,a3,a2,a1,a0,us-legal,us-letter,us-tabloid).
+ Default paper size is a4. The measures are defined in <em>inches</em>.
+<B>left</B>, <B>right</B>, <B>bottom</B> and <B>top</B> are paper margins.
+If the plot is rotated with the <b>-r</b> command line flag, measures
+are applied to the <em>rotated</em> page.
+<P>
+
+<PRE>
+EXAMPLE:
+ <B>paper</B> a3
+ <B>end</B>
+</PRE>
+<P>
+<PRE>
+EXAMPLE:
+ <B>paper</B>
+ <B>width</B> 10
+ <B>height</B> 10
+ <B>left</B> 2
+ <B>right</B> 2
+ <B>bottom</B> 2
+ <B>top</B> 2
+ <B>end</B>
+</PRE>
+<P>
+
+
+<a name="point"></a>
+<H2>point</H2>
+
+Places additional points or icons on the output map.
+<PRE>
+USAGE: <B>point</B> east north
+ <B>point</B> x% y%
+ <B>color</B> color
+ <B>fcolor</B> color
+ <B>symbol</B> symbol group/name
+ <B>size</B> #
+ <B>rotate</B> #
+ <B>masked</B> [y|n]
+ <B>end</B>
+</PRE>
+The point location is entered in the main instruction line by giving either the map
+coordinates or by using percentages of the geographic region.
+The user may also specify the point <B>color</B>,
+the <B>size</B> of symbol in points,
+the rotation angle (in degrees CCW),
+and whether the point is to be <B>masked</B> by the current mask.
+(See manual entry for <EM> <A HREF="r.mask.html">r.mask</A>
+</EM> for more information on the mask.)
+<P>
+
+This example would place a purple diamond (from icon file
+<EM>diamond</EM>) at the point (E456000 N7890000). This diamond would be the
+the size of a 15 points and would not be masked by the current mask.
+<PRE>
+EXAMPLE:
+ <B>point</B> 456000 7890000
+ <B>fcolor</B> purple
+ <B>color</B> black
+ <B>symbol</B> basic/diamond
+ <B>size</B> 15
+ <B>masked</B> n
+ <B>end</B>
+</PRE>
+Of course, multiple points may be drawn with multiple
+<EM>point</EM>
+instructions.
+<P>
+
+
+<a name="psfile"></a>
+<H2>psfile</H2>
+
+Copies a file containing PostScript commands into the output file.
+
+<P>
+
+<B>Note:</B>
+<EM>ps.map</EM>
+will not search for this file. The user must be in the
+correct directory or specify the full path on the <B>psfile</B> instruction.
+(Note to /bin/csh users: ~ won't work with this instruction).
+<PRE>
+USAGE: <B>psfile</B> filename
+</PRE>
+This example copies the file "logo.ps" into the output file.
+<PRE>
+EXAMPLE:
+ <B>psfile</B> logo.ps
+</PRE>
+<P>
+
+
+<a name="raster"></a>
+<H2>raster</H2>
+
+Selects a raster map layer for output.
+<PRE>
+USAGE: <B>raster</B> mapname
+</PRE>
+For each <EM>ps.map</EM> run, only one raster map layer (or set
+of layers or imagery group; see below) can be requested. If no
+raster map layer is requested, a completely white map will be
+produced. It can be useful to select no raster map layer in
+order to provide a white background for vector maps.
+<P>
+Note that an imagery group selected with the <EM>group</EM>
+option, or a set of three raster layers selected with the
+<EM>rgb</EM> option, count as a raster map layer for the
+purposes of the preceding paragraph.
+<P>
+
+This example would paint a map of the raster map layer <EM>soils</EM>.
+
+<PRE>
+EXAMPLE:
+ <B>raster</B> soils
+</PRE>
+<P>
+
+
+<a name="read"></a>
+<H2>read</H2>
+
+Provides <EM>ps.map</EM> with a previously prepared input stream.
+<PRE>
+USAGE: <B>read</B> previously prepared UNIX file
+</PRE>
+Mapping instructions can be placed into a file and read into
+<EM>ps.map.</EM>
+
+<P>
+
+<B>Note:</B>
+<EM>ps.map</EM>
+will not search for this file. The user must be in the
+correct directory or specify the full path on the <B>read</B> instruction.
+(Note to /bin/csh users: ~ won't work with this instruction).
+
+<P>
+
+This example reads the UNIX file <EM>pmap.roads</EM> into <EM>ps.map</EM>.
+This file may contain all the <EM>ps.map</EM> instructions for placing
+the vector map layer <EM>roads</EM> onto the output map.
+<PRE>
+EXAMPLE:
+ <B>read</B> pmap.roads
+</PRE>
+The user may have created this file because this vector map layer
+is particularly useful for many <EM>ps.map</EM>
+outputs. By using the <B>read</B> option, the user need not enter all the input
+for the <B>vector</B> instruction, but simply <B>read</B> the previously prepared
+file with the correct instructions.
+<P>
+
+
+<a name="rectangle"></a>
+<H2>rectangle</H2>
+
+Draws rectangle on the output map.
+<PRE>
+USAGE: <B>rectangle</B> east north east north
+ <B>rectangle</B> x% y% x% y%
+ <B>color</B> color
+ <B>fcolor</B> fill color
+ <B>width</B> #
+ <B>masked</B> [y|n]
+ <B>end</B>
+</PRE>
+The two corners of the rectangle are entered on the main
+instruction. These points can be defined either by map coordinates or
+by using percentages of the geographic region.
+The user may also specify line
+<B>color</B>, fill color <B>fcolor</B>, <B>width</B>
+in pixels (accepts decimal points [floating points] as well as integers),
+and if the rectangle is to be <B>masked</B> by the current mask.
+(See manual entry for <EM><A HREF="r.mask.html">r.mask</A></EM>
+for more information on the mask.)
+<BR>
+Multiple rectangles may be drawn by using multiple <EM>rectangle</EM> instructions.
+<P>
+
+This example would draw a yellow rectangle filled by green from the point x=10% y=80%
+to the point x=30% y=70%. This line
+would be 2 pixels wide and would appear even if there is a mask.
+<PRE>
+EXAMPLE:
+ <B>rectangle</B> 10% 80% 30% 70%
+ <B>color</B> yellow
+ <B>fcolor</B> green
+ <B>width</B> 2
+ <B>masked</B> n
+ <B>end</B>
+</PRE>
+<P>
+
+
+<a name="region"></a>
+<H2>region</H2>
+
+Places the outline of a smaller geographic region
+on the output.
+<PRE>
+USAGE: <B>region</B> regionfile
+ <B>color</B> color
+ <B>width</B> #
+ <B>end</B>
+</PRE>
+Geographic region settings are created and saved using <EM> the
+<A HREF="g.region.html">g.region</A></EM> module.
+The <EM>ps.map</EM> <EM>region</EM> option can be used to show an outline of
+a smaller region which was printed on a separate run of <EM>ps.map</EM>
+on other user-created maps.
+<P>
+The user can specify the <B>color</B>
+and the <B>width</B> in pixel units (accepts decimal points
+[floating points] as well as integers) of the outline.
+The default is a black border of one pixel width.
+<P>
+This example would place a white outline, 2 pixels wide, of the
+geographic region called <EM>fire.zones</EM> onto the output map.
+This geographic region would have been created and saved using
+<EM><A HREF="g.region.html">g.region</A></EM>.
+<PRE>
+EXAMPLE:
+ <B>region</B> fire.zones
+ <B>color</B> white
+ <B>width</B> 2
+ <B>end</B>
+</PRE>
+<P>
+
+
+<a name="rgb"></a>
+<H2>rgb</H2>
+
+Selects three raster map layers for output as an RGB color image.
+<PRE>
+USAGE: <B>rgb</B> <EM>red</EM> <EM>green</EM> <EM>blue</EM>
+</PRE>
+This is similar to <EM>raster</EM>, except that it uses three
+raster map layers instead of a single layer. The three layers
+are composed to form a color image, similar to <EM>d.rgb</EM>.
+<P>
+
+For each layer, only one of the components of the layer's color
+table is used: the red component for the red layer, and so on.
+This will give the desired result if all of the layers have a
+grey-scale color table, or if each layer's color table uses the
+hue appropriate to the layer.
+<P>
+
+
+<a name="scale"></a>
+<H2>scale</H2>
+
+Selects a scale for the output map.
+<PRE>
+USAGE: <B>scale</B> <EM>scale</EM>
+</PRE>
+The scale can be selected either as:
+<DL>
+<DT>
+<DD>a relative ratio, e.g. 1:25000;
+<DT>
+<DD>an absolute width of the printed map, e.g. 10 inches;
+<DT>
+<DD>the number of printed paper panels, e.g. 3 panels
+<EM>.I</EM>
+(at the present time, only 1 panel is supported);
+<DT>
+<DD>the number of miles per inch, e.g. 1 inch equals 4 miles.
+</DD>
+</DL>
+<P>
+
+This example would set the scale of the map to 1 unit = 25000
+units.
+<PRE>
+EXAMPLE:
+ <B>scale</B> 1:25000
+</PRE>
+<P>
+This instruction is identical to the <EM>scale</EM> command line parameter.
+<BR>
+<em>NOTE: Using "scale" from the command line is depreciated and while
+still provided for compatibility reasons it will be removed in the future.
+Please use the "scale" mapping instruction instead.</em>
+<P>
+
+
+<a name="scalebar"></a>
+<H2>scalebar</H2>
+
+Draws a scalebar on the map.
+<PRE>
+USAGE: <B>scalebar</B> [f|s]
+ <B>where</B> x y
+ <B>length</B> scale length
+ <B>height</B> scale height
+ <B>segment</B> no. segments
+ <B>numbers</B> #
+ <B>fontsize</B> font size
+ <B>background</B> [Y|n]
+ <B>end</B>
+</PRE>
+Draw one of two types of scale bar.
+Fancy (f) draws alternating black and white scale boxes.
+Simple (s) draws a plain line scale. The default type is fancy.
+The subsection instructions allow the user to set <B>where</B> the scalebar
+is placed, the <B>length</B> of the scalebar (in geographic coordinate
+system units), the <B>height</B> of the scalebar in inches, and the number of
+<B>segments</B> (or tics for simple). The <B>number</B> of annotations
+numbers every n-th segment.
+The <B>background</B> command can turn off the background box for the text.
+<P>
+The scalebar <B>length</B> is the only required argument. The defaults are a
+fancy scalebar with 4 segments, each segment labeled, and a height of 0.1
+inches. The default location is 2 inches from the top of the page and
+halfway across.
+<P>
+NOTE: The scalebar is centered on the location given.
+<P>
+This example draws a simple scalebar 1000 meters (for a metered database, like UTM) long,
+with tics every 200 meters, labeled every second tic. The scalebar is drawn 5 inches from the top and 4 inches from the left and is 0.25 inches high.
+<PRE>
+EXAMPLE:
+ <B>scalebar</B> s
+ <B>where</B> 4 5
+ <B>length</B> 1000
+ <B>height</B> 0.25
+ <B>segment</B> 5
+ <B>numbers</B> 2
+ <B>end</B>
+</PRE>
+
+
+<a name="setcolor"></a>
+<H2>setcolor</H2>
+
+Overrides the color assigned to one or more categories
+of the raster map layer.
+<PRE>
+USAGE: <B>setcolor</B> cat(s) color
+</PRE>
+This example would set the color for categories 2,5 and 8 of the raster
+map layer <EM>watersheds</EM> to white and category 10 to green.
+(<B>NOTE</B>: no spaces are inserted between the category values.)
+<PRE>
+EXAMPLE:
+ <B>raster</B> watersheds
+ <B>setcolor</B> 2,5,8 white
+ <B>setcolor</B> 10 green
+</PRE>
+Of course,
+<EM>setcolor</EM>
+can be requested more than once to override the default color for additional
+categories. More than one category can be changed for each request by listing
+all the category values separated by commas (but with no spaces).
+<P>
+
+
+<a name="text"></a>
+<H2>text</H2>
+
+Places text on the map.
+<PRE>
+USAGE: <B>text</B> east north text
+ <B>text</B> x% y% text
+ <B>font</B> fontname
+ <B>color</B> color|none
+ <B>width</B> #
+ <B>hcolor</B> color|none
+ <B>hwidth</B> #
+ <B>background</B> color|none
+ <B>border</B> color|none
+ <B>fontsize</B> font size
+ <B>size</B> #
+ <B>ref</B> reference point
+ <B>rotate</B> degrees CCW
+ <B>xoffset</B> #
+ <B>yoffset</B> #
+ <B>opaque</B> [y|n]
+ <B>end</B>
+</PRE>
+The user specifies where the text will be placed by
+providing map coordinates or percentages of the geographic region.
+The text follows these coordinates on the same instruction line.
+More than one line of text can be specified by notating the end of a line with
+<B>\n</B>
+(e.g. USA<B>\n</B>CERL).
+<P>
+The user can then specify various text features:
+<P>
+<B>font:</B>
+the PostScript font. Common possibilities are listed at the start of this
+help page. The default is <tt>Helvetica</tt>.
+<P>
+<B>color</B>
+(see <a href="#NAMED_COLORS">NAMED COLORS</a>);
+<P>
+<B>width</B>
+of the lines used to draw the text to make thicker letters
+(accepts decimal points [floating points] as well as integers);
+<P>
+<B>size</B> and <B>fontsize.</B>
+<B>size</B> gives the vertical height of the letters in meters on the
+ground (text size will grow or shrink depending on the scale at which
+the map is painted). Alternatively <B>fontsize</B> can set the font
+size directly. If neither <B>size</B> or <B>fontsize</B> is given, a
+default font size of 10 will be used;
+<P>
+the highlight color (<B>hcolor</B>) and
+the width of the highlight color (<B>hwidth</B>);
+<P>
+the text-enclosing-box <B>background</B> color;
+the text box <B>border</B> color;
+<P>
+<B>ref.</B>
+This reference point specifies the text handle - what
+part of the text should be placed on the location specified by the map
+coordinates. Reference points can refer to:
+[lower|upper|center] [left|right|center] of the text to be printed; The default is center center, i.e the text is centered on the reference point.
+<P>
+<B>rotate</B>
+sets the text rotation angle, measured in degrees counter-clockwise.
+<P>
+<B>yoffset</B>,
+which provides finer placement of text by shifting the
+text a vertical distance in pixels from the specified north. The vertical
+offset will shift the location to the south if positive, north if negative;
+<P>
+<B>xoffset</B>,
+which shifts the text a horizontal distance in pixels from
+the specified east The horizontal offset will shift the location east if
+positive, west if negative;
+<P>
+<B>opaque</B>,
+whether or not the text should be <B>opaque</B> to vectors. Entering <B>no</B>
+to the opaque option will allow the user to see any vectors which go
+through the text's background box. Otherwise, they will end at the box's edge.
+<P>
+<BR>
+The following example would place the text <EM>SPEARFISH LAND COVER</EM>
+at the coordinates E650000 N7365000. The text would be a total of
+3 pixels wide (2 pixels of red text and 1 pixel black highlight), have a white
+background enclosed in a red box, and be 500 meters in size. The lower right
+corner of the text would be centered over the coordinates provided. All
+vectors on the map would stop at the border of this text.
+<PRE>
+EXAMPLE:
+ <B>text</B> 650000 7365000 SPEARFISH LAND COVER
+ <B>font</B> romand
+ <B>color</B> red
+ <B>width</B> 2
+ <B>hcolor</B> black
+ <B>hwidth</B> 1
+ <B>background</B> white
+ <B>border</B> red
+ <B>size</B> 500
+ <B>ref</B> lower left
+ <B>opaque</B> y
+ <B>end</B>
+</PRE>
+<P>
+
+
+<a name="vareas"></a>
+<H2>vareas</H2>
+
+Selects a vector map layer for output and plots areas.
+<PRE>
+USAGE: <B>vareas</B> vectormap
+ <B>layer</B> # (layer number used with cats/where option)
+ <B>cats</B> list of categories (e.g. 1,3,5-7)
+ <B>where</B> SQL where statement
+ <B>masked</B> [y|n]
+ <B>color</B> color
+ <B>fcolor</B> color
+ <B>rgbcolumn</B> column
+ <B>width</B> #
+ <B>label</B> label to use in legend
+ <B>lpos</B> position in legend
+ <B>pat</B> pattern file
+ <B>pwidth</B> #
+ <B>scale</B> #
+ <B>end</B>
+</PRE>
+The user can specify:
+<P>
+<B>color</B> - color of the vector lines or area boundaries;
+<P>
+<B>fcolor</B> - the area fill color;
+<P>
+<B>rgbcolumn</B> - name of color definition column used for the area fill color;
+<P>
+<B>width</B> - width of the vectors lines or area boundaries in pixels
+(accepts decimal points [floating points] as well as integers);
+<P>
+<B>masked</B> - whether or not the raster map layer is to be masked
+by the current mask;
+(see manual entry <EM><A HREF="r.mask.html">r.mask</A></EM>
+for more information on the mask)
+<P>
+<B>cats</B> - which categories should be plotted (default is all);
+<P>
+<B>where</B> - select features using a SQL where statement.
+For example: <tt>vlastnik = 'Cimrman'</tt>;
+<P>
+<B>label</B> - for description in <a href="#vlegend">vlegend</a>.
+Default is: map(mapset);
+<P>
+<B>lpos</B> - position vector is plotted in legend. If lpos is
+0 then this vector is omitted in legend. If more vectors used the
+same lpos then their symbols in legend are merged and label for
+first vector is used.
+<P>
+<B>pat</B> - full path to pattern file. The pattern file contains header and
+simple PostScript commands. It is similar to EPS but more limited, meaning that
+while each pattern file is a true EPS file, most EPS files are not useful as pattern
+files because they contain restricted commands. Color and width of patterns are set
+by <B>fcolor</B> (red, green, ..., none, R:G:B) and <B>width</B> until overwritten
+in the pattern file.
+Pattern may be scaled with the <b>scale</b> command. Several standard hatching
+patterns are provided in <tt>$GISBASE/etc/paint/patterns/</tt>.
+Demonstrative images can be found on the
+<a href="http://grass.gdf-hannover.de/wiki/AreaFillPatterns">GRASS Wiki site</a>.
+
+You can also create your own custom pattern files in a text editor.
+Example of pattern file:
+
+<div class="code"><PRE>
+%!PS-Adobe-2.0 EPSF-1.2
+%%BoundingBox: 0 0 10 10
+newpath
+5 0 moveto
+5 10 lineto
+stroke
+</PRE></div>
+
+
+<P>
+<B>scale</B> - pattern scale
+<P>
+<B>pwidth</B> - pattern line width, width is used by pattern until the width is overwritten
+in pattern file.
+<P>
+
+<PRE>
+EXAMPLE:
+ <B>vareas</B> forest
+ <B>color</B> blue
+ <B>width</B> 1
+ <B>masked</B> y
+ <B>cats</B> 2,5-7
+ <B>end</B>
+</PRE>
+<P>
+
+
+<a name="vlines"></a>
+<H2>vlines</H2>
+
+Selects a vector map layer for output and plots lines.
+<PRE>
+USAGE: <B>vlines</B> vectormap
+ <B>type</B> line and/or boundary
+ <B>layer</B> # (layer number used with cats/where option)
+ <B>cats</B> list of categories (e.g. 1,3,5-7)
+ <B>where</B> SQL where statement like: vlastnik = 'Cimrman'
+ <B>masked</B> [y|n]
+ <B>color</B> color
+ <B>rgbcolumn</B> column
+ <B>width</B> #
+ <B>cwidth</B> #
+ <B>hcolor</B> color
+ <B>hwidth</B> #
+ <B>offset</B> #
+ <B>coffset</B> #
+ <B>ref</B> left|right
+ <B>style</B> 00001111
+ <B>label</B> label
+ <B>lpos</B> #
+ <B>end</B>
+</PRE>
+The user can specify:
+<P>
+<B>type</B> - the default is lines only;
+<P>
+<B>color</B> - color of the vector lines or area boundaries;
+<P>
+<B>rgbcolumn</B> - name of color definition column used for the vector lines or area boundaries;
+<P>
+<B>width</B> - width of the vectors lines or area boundaries in pixels
+(accepts decimal points [floating points] as well as integers);
+<P>
+<B>cwidth</B> - width of the vectors lines. If cwidth is used then
+width of line is equal to cwidth * category value and width is
+used in legend;
+<P>
+<B>hcolor</B> - the highlight color for the vector lines;
+<P>
+<B>hwidth</B> - the width of the highlight color in pixels;
+<P>
+<B>offset</B> (experimental) - offset for the vectors lines in pixels for plotting
+parallel lines in distance equal to offset (accepts positive or
+negative decimal points). Useful to print streets with several parallel lanes;
+<P>
+<B>coffset</B> (experimental) - offset for the vectors lines. If coffset is used then
+offset of line is equal to coffset * category value and offset is
+used in legend;
+<P>
+<B>ref</B> (experimental) - line justification.
+<P>
+<B>masked</B> - whether or not the raster map layer is to be masked
+by the current mask;
+(see manual entry <EM><A HREF="r.mask.html">r.mask</A></EM>
+for more information on the mask);
+<P>
+<B>style</B> - the line style allows the vectors
+to be dashed in different patterns. This is done by typing a
+series of numbers (0's and 1's) in a desired sequence or pattern.
+The first block of repeated zeros or ones represents "draw", the second
+block represents "blank".
+An even number of blocks will repeat the pattern, an odd number of blocks
+will alternate the pattern.
+The default is "solid";
+<P>
+<B>cats</B> - which categories should be plotted (default is all);
+<P>
+<B>label</B> - for description in <a href="#vlegend">vlegend</a>.
+Default is: map(mapset);
+<P>
+<B>lpos</B> - position vector is plotted in legend. If lpos is
+0 then this vector is omitted in legend. If more vectors used the
+same lpos then their symbols in legend are merged and label for
+first vector is used.
+<P>
+
+<PRE>
+EXAMPLE:
+ <B>vlines</B> streams
+ <B>color</B> blue
+ <B>width</B> 2
+ <B>hcolor</B> white
+ <B>hwidth</B> 1
+ <B>masked</B> y
+ <B>cats</B> 2
+ <B>label</B> Streams - category 2
+ <B>end</B>
+</PRE>
+<P>
+
+
+<a name="vpoints"></a>
+<H2>vpoints</H2>
+
+Selects vector point data to be placed on the output map
+<PRE>
+USAGE: <B>vpoints</B> vectormap
+ <B>type</B> point and/or centroid
+ <B>layer</B> # (layer number used with cats/where/sizecol options)
+ <B>cats</B> list of categories (e.g. 1,3,5-7)
+ <B>where</B> SQL where statement like: vlastnik = 'Cimrman'
+ <B>masked</B> [y|n]
+ <B>color</B> color
+ <B>fcolor</B> color
+ <B>rgbcolumn</B> column
+ <B>width</B> #
+ <B>eps</B> epsfile
+ <B>symbol</B> symbol group/name
+ <B>size</B> #
+ <B>sizecolumn</B> attribute column used for symbol sizing
+ <B>scale</B> scaling factor for sizecolumn values
+ <B>rotate</B> #
+ <B>rotatecolumn</B> column
+ <B>label</B> legend label
+ <B>lpos</B> position in legend
+ <B>end</B>
+</PRE>
+The user may specify the
+the <B>color</B> of the sites (see section on <a href="#NAMED_COLORS">NAMED COLORS</a>);
+either the GRASS <B>symbol</B> or
+the <B>eps</B> Encapsulated Postscript file to be used to represent the presence of a site
+(if '<B>$</B>' is used in the EPS file path it will be replaced by category number);
+and <B>rotate</B> (in degrees) for counter-clockwise rotation.
+<BR>
+The size of the icon (number of times larger than the size it is in
+the icon file) is typically given by the <B>size</B> option. Alternatively
+the size of the symbol or EPS graphic can be taken from an attribute column
+by using the <B>sizecolumn</B> command. The value given by <B>sizecolumn</B> may be
+scaled by using the <B>scale</B> factor setting (default scaling is 1.0).
+In a similar manner symbol color can be read from <B>rgbcolumn</B>
+and the rotation angle read from <B>rotatecolumn</B>.
+
+<PRE>
+EXAMPLE:
+ <B>vpoints</B> windmills
+ <B>color</B> blue
+ <B>symbol</B> mills/windmill
+ <B>size</B> 10
+ <B>end</B>
+</PRE>
+<P>
+
+<a name="vlegend"></a>
+<H2>vlegend</H2>
+
+Prints the portion of the map legend containing the
+vector information, on or below the map.
+
+<PRE>
+USAGE: <B>vlegend</B>
+ <B>where</B> x y
+ <B>font</B> font name
+ <B>fontsize</B> font size
+ <B>width</B> width of color symbol
+ <B>cols</B> number of columns to print
+ <B>border</B> color|none
+ <B>end</B>
+</PRE>
+The default location is immediately below the legend containing the
+scale, grid and region information, starting at the left edge of the map.
+If the <EM>where</EM> instruction is present and <EM>y</EM> is less than or
+equal to zero, the vector legend will be positioned immediately below
+the map, starting <EM>x</EM> inches from the left edge of the page.
+
+<P>
+<EM>width</EM> is the width in inches of the color symbol (for areas) in front of the
+legend text. The default is 1/24 * fontsize inches.
+<EM>cols</EM> is the number of columns to split the legend into. The default is one
+column. The maximum number of colums is 10, or equal to the number of legend entries
+if there are less than 10 entries.
+<P>
+<EM>border</EM> will draw a border around the legend using the specified color.
+ (see <a href="#NAMED_COLORS">NAMED COLORS</a>)
+<P>
+Alternatively, the user can create a custom legend by using the
+<a href="#rectangle">rectangle</a>, <a href="#point">point</a>, and
+<a href="#text">text</a> instructions.
+<P>
+This example prints the vector legend
+immediately below the map and starting 4.5 inches from the left edge
+of the page, using a 12/72 inch Helvetica font.
+
+<PRE>
+EXAMPLE:
+ <B>vlegend</B>
+ <B>where</B> 4.5 0
+ <B>font</B> Courier
+ <B>fontsize</B> 12
+ <B>end</B>
+</PRE>
+<P>
+
+
+<a name="end"></a>
+<H2>end</H2>
+
+Terminates input and begin painting the map.
+
+<PRE>
+USAGE: <B>end</B>
+</PRE>
+<BR>
+<P>
+
+
+
+<H2>EXAMPLE ps.map INPUT FILE</H2>
+
+The following is an example of a <EM>ps.map</EM> script file. The file has been
+named <EM>spear.soils</EM>.
+This script file can be entered at the command line:
+
+<PRE>
+ <B>ps.map input=</B><EM>spear.soils</EM> <B>output=</B><EM>soils.ps</EM>
+</PRE>
+<PRE>
+
+# this ps.map example draws a map of Spearfish, SD
+<B>raster</B> soils
+<B>outline</B>
+ <B>color</B> black
+ <B>width</B> 1
+ <B>end</B>
+<B>comments</B> soil.cmt
+ <B>where</B> 1 6
+ <B>font</B> Helvetica
+ <B>end</B>
+<B>colortable</B> y
+ <B>where</B> 1 6.5
+ <B>cols</B> 4
+ <B>width</B> 4
+ <B>font</B> Helvetica
+ <B>end</B>
+<B>setcolor</B> 6,8,9 white
+<B>setcolor</B> 10 green
+<B>vlines</B> roads
+ <B>width</B> 2
+ <B>style</B> 0111
+ <B>color</B> grey
+ <B>masked</B> n
+ <B>end</B>
+<B>vlegend</B>
+ <B>where</B> 4.5 0
+ <B>font</B> Courier
+ <B>fontsize</B> 8
+ <B>end</B>
+<B>text</B> 30% 100% SPEARFISH SOILS MAP
+ <B>color</B> red
+ <B>width</B> 1
+ <B>hcolor</B> black
+ <B>hwidth</B> 1
+ <B>background</B> white
+ <B>border</B> red
+ <B>size</B> 500
+ <B>ref</B> lower left
+ <B>end</B>
+<B>line</B> 606969.73 3423092.91 616969.73 3423092.91
+ <B>color</B> yellow
+ <B>width</B> 2
+ <B>end</B>
+<B>point</B> 40% 60%
+ <B>color</B> purple
+ <B>symbol</B> basic/diamond
+ <B>size</B> 25
+ <B>masked</B> n
+ <B>end</B>
+<B>scale</B> 1:125000
+<B>scalebar</B> f
+ <B>where</B> 4.5 6.5
+ <B>length</B> 5000
+ <B>height</B> 0.05
+ <B>segment</B> 5
+ <B>numbers</B> 5
+ <B>end</B>
+<B>geogrid</B> 60 s
+ <B>color</B> blue
+ <B>numbers</B> 2 yellow
+ <B>end</B>
+<B>paper</B> a4
+ <B>end</B>
+<B>end</B>
+
+</PRE>
+
+<P>
+More examples can be found on the
+<a href="http://grass.osgeo.org/wiki/Ps.map_scripts">GRASS Wiki</a>
+help site.
+<P>
+
+
+<H2>CHANGES BETWEEN VERSION 5.0.x/5.4.x and 6.0</H2>
+<UL>
+<LI>Devices and ps.select do not exist any more. Paper is defined by the
+<EM>paper</EM> instruction.</LI>
+<LI><EM>vpoints</EM> are used instead of <EM>sites</EM> (points are read from vector).</LI>
+<LI><EM>vector</EM> is substituted by <EM>vpoints</EM>, <EM>vlines</EM> and <EM>vareas</EM>.</LI>
+<LI>Symbols are used instead of icons (different format and directory).</LI>
+<LI>Map legend can be printed in columns.</LI>
+</UL>
+
+
+<H2>SEE ALSO</H2>
+<em>
+<a href="g.region.html">g.region</a>,
+<a href="v.label.html">v.label</a>
+</em>
+
+<H2>AUTHOR</H2>
+
+Paul Carlson, USDA, SCS, NHQ-CGIS<BR>
+Modifications: Radim Blazek, Glynn Clements, Bob Covill, Hamish Bowman
+<p>
+<i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.average/description.html
===================================================================
--- grass/trunk/raster/r.average/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.average/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,144 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-
-<em>r.average</em> calculates the average value of data
-contained in a <em>cover</em> raster map layer for areas
-assigned the same category value in the user-specified
-<em>base</em> raster map layer. These averaged values are
-stored in the category labels file associated with a new
-<em>output</em> map layer.
-
-The values to be averaged are taken from a user-specified
-<em>cover</em> map. The <em>category values</em> for the
-<em>cover</em> map will be averaged, unless the <b>-c</b>
-flag is set. If the <b>-c</b> flag is set, the values that
-appear in the <em>category labels</em> file for the
-<em>cover</em> map will be averaged instead (see example
-below).
-
-<p>
-
-The <em>output</em> map is actually a <em>reclass</em> of the <em>base</em>
-map (see <em> <a href="r.reclass.html">r.reclass</a></em>), and will have
-exactly the same <em>category values</em> as the <em>base</em> map. The
-averaged values computed by <em>r.average</em> are stored in the
-<em>output</em> map's <em>category labels</em> file.
-
-The <b>base=</b> map is an existing raster map layer in the user's current
-mapset search path. For each group of cells assigned the same category
-value in the <em>base</em> map, the values assigned these cells in the
-<em>cover</em> map will be averaged.
-
-The <em>cover</em> map is an existing raster map layer containing the values
-(in the form of cell category values or cell category labels) to be averaged
-within each category of the <em>base</em> map.
-
-<h2>NOTES</h2>
-
-The <b>-c</b> option requires that the category label for
-each category in the <em>cover</em> map be a valid number,
-integer, or decimal. To be exact, if the first item in the
-label is numeric, then that value is used. Otherwise, zero
-is used. The following table covers all possible cases:
-
-<p>
-<pre>
- category value
- label used by -c
- ______________________
- .12 .12
- .80 KF .8
- no data 0
-</pre>
-<p>
-
-(This flag is very similar to the @ operator in
-<em><a href="r.mapcalc.html">r.mapcalc</a></em>,
-and the user is encouraged to read the manual entry for
-<em><a href="r.mapcalc.html">r.mapcalc</a></em>
-to see how it works there.)
-
-<p>
-
-The user should use the results of <em>r.average</em> with
-care. Since this utility assigns a value to each cell
-which is based on global information (i.e., information at
-spatial locations other than just the location of the cell
-itself), the resultant map layer is only valid if the
-geographic region and mask settings are the same as they
-were at the time that the result map was created.
-
-<p>
-
-Results are affected by the current region settings and mask.
-
-<h2>EXAMPLE</h2>
-
-Assume that
-<em>farms</em>
-is a map with 7 farms (i.e., 7 categories), and that
-<em>soils.Kfactor</em>
-is a map of soil K factor values with the following category file:
-
-<pre>
- cat cat
- value label
- 0 no soil data
- 1 .10
- 2 .15
- 3 .17
- 4 .20
- 5 .24
- 6 .28
- 7 .32
- 8 .37
- 9 .43
-</pre>
-
-Then
-
-<p>
-<dl>
-<dd>
-<b>r.average -c base=</b><em>farms</em>
-<b>cover=</b><em>soils.Kfactor</em> <b>output=</b><em>K.by.farm</em>
-</dl>
-
-will compute the average soil K factor for each farm, and store the result
-in the output map <em>K.by.farm</em>, which will be a reclass of
-<em>farms</em> with category labels as follows (example only):
-
-<pre>
- cat cat
- value label
- 1 .1023
- 2 .1532
- 3 .172
- 4 .3872
- 5 .003
- 6 .28
- 7 .2345
-</pre>
-
-
-
-<h2>SEE ALSO</h2>
-
-<em><a href="g.region.html">g.region</a></em>,
-<em><a href="r.category.html">r.category</a></em>,
-<em><a href="r.clump.html">r.clump</a></em>,
-<em><a href="r.describe.html">r.describe</a></em>,
-<em><a href="r.mapcalc.html">r.mapcalc</a></em>,
-<em><a href="r.mfilter.html">r.mfilter</a></em>,
-<em><a href="r.mode.html">r.mode</a></em>,
-<em><a href="r.neighbors.html">r.neighbors</a></em>,
-<em><a href="r.reclass.html">r.reclass</a></em>,
-<em><a href="r.statistics.html">r.statistics</a></em>,
-<em><a href="r.stats.html">r.stats</a></em>
-
-<h2>AUTHOR</h2>
-
-Michael Shapiro,
-U.S. Army Construction Engineering Research Laboratory
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.average/r.average.html (from rev 32770, grass/trunk/raster/r.average/description.html)
===================================================================
--- grass/trunk/raster/r.average/r.average.html (rev 0)
+++ grass/trunk/raster/r.average/r.average.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,144 @@
+<h2>DESCRIPTION</h2>
+
+
+<em>r.average</em> calculates the average value of data
+contained in a <em>cover</em> raster map layer for areas
+assigned the same category value in the user-specified
+<em>base</em> raster map layer. These averaged values are
+stored in the category labels file associated with a new
+<em>output</em> map layer.
+
+The values to be averaged are taken from a user-specified
+<em>cover</em> map. The <em>category values</em> for the
+<em>cover</em> map will be averaged, unless the <b>-c</b>
+flag is set. If the <b>-c</b> flag is set, the values that
+appear in the <em>category labels</em> file for the
+<em>cover</em> map will be averaged instead (see example
+below).
+
+<p>
+
+The <em>output</em> map is actually a <em>reclass</em> of the <em>base</em>
+map (see <em> <a href="r.reclass.html">r.reclass</a></em>), and will have
+exactly the same <em>category values</em> as the <em>base</em> map. The
+averaged values computed by <em>r.average</em> are stored in the
+<em>output</em> map's <em>category labels</em> file.
+
+The <b>base=</b> map is an existing raster map layer in the user's current
+mapset search path. For each group of cells assigned the same category
+value in the <em>base</em> map, the values assigned these cells in the
+<em>cover</em> map will be averaged.
+
+The <em>cover</em> map is an existing raster map layer containing the values
+(in the form of cell category values or cell category labels) to be averaged
+within each category of the <em>base</em> map.
+
+<h2>NOTES</h2>
+
+The <b>-c</b> option requires that the category label for
+each category in the <em>cover</em> map be a valid number,
+integer, or decimal. To be exact, if the first item in the
+label is numeric, then that value is used. Otherwise, zero
+is used. The following table covers all possible cases:
+
+<p>
+<pre>
+ category value
+ label used by -c
+ ______________________
+ .12 .12
+ .80 KF .8
+ no data 0
+</pre>
+<p>
+
+(This flag is very similar to the @ operator in
+<em><a href="r.mapcalc.html">r.mapcalc</a></em>,
+and the user is encouraged to read the manual entry for
+<em><a href="r.mapcalc.html">r.mapcalc</a></em>
+to see how it works there.)
+
+<p>
+
+The user should use the results of <em>r.average</em> with
+care. Since this utility assigns a value to each cell
+which is based on global information (i.e., information at
+spatial locations other than just the location of the cell
+itself), the resultant map layer is only valid if the
+geographic region and mask settings are the same as they
+were at the time that the result map was created.
+
+<p>
+
+Results are affected by the current region settings and mask.
+
+<h2>EXAMPLE</h2>
+
+Assume that
+<em>farms</em>
+is a map with 7 farms (i.e., 7 categories), and that
+<em>soils.Kfactor</em>
+is a map of soil K factor values with the following category file:
+
+<pre>
+ cat cat
+ value label
+ 0 no soil data
+ 1 .10
+ 2 .15
+ 3 .17
+ 4 .20
+ 5 .24
+ 6 .28
+ 7 .32
+ 8 .37
+ 9 .43
+</pre>
+
+Then
+
+<p>
+<dl>
+<dd>
+<b>r.average -c base=</b><em>farms</em>
+<b>cover=</b><em>soils.Kfactor</em> <b>output=</b><em>K.by.farm</em>
+</dl>
+
+will compute the average soil K factor for each farm, and store the result
+in the output map <em>K.by.farm</em>, which will be a reclass of
+<em>farms</em> with category labels as follows (example only):
+
+<pre>
+ cat cat
+ value label
+ 1 .1023
+ 2 .1532
+ 3 .172
+ 4 .3872
+ 5 .003
+ 6 .28
+ 7 .2345
+</pre>
+
+
+
+<h2>SEE ALSO</h2>
+
+<em><a href="g.region.html">g.region</a></em>,
+<em><a href="r.category.html">r.category</a></em>,
+<em><a href="r.clump.html">r.clump</a></em>,
+<em><a href="r.describe.html">r.describe</a></em>,
+<em><a href="r.mapcalc.html">r.mapcalc</a></em>,
+<em><a href="r.mfilter.html">r.mfilter</a></em>,
+<em><a href="r.mode.html">r.mode</a></em>,
+<em><a href="r.neighbors.html">r.neighbors</a></em>,
+<em><a href="r.reclass.html">r.reclass</a></em>,
+<em><a href="r.statistics.html">r.statistics</a></em>,
+<em><a href="r.stats.html">r.stats</a></em>
+
+<h2>AUTHOR</h2>
+
+Michael Shapiro,
+U.S. Army Construction Engineering Research Laboratory
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.basins.fill/description.html
===================================================================
--- grass/trunk/raster/r.basins.fill/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.basins.fill/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,55 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-
-<em>r.basins.fill</em>
-generates a raster map layer depicting subbasins, based
-on input raster map layers for the coded stream network
-(where each channel segment has been "coded" with a unique category value)
-and for the ridges within a given watershed.
-The raster map layer depicting ridges should include
-the ridge which defines the perimeter of the watershed.
-The coded stream network can be generated
-as part of the
-<em><a href="r.watershed.html">r.watershed</a></em> program,
-but the map layer of ridges will need to be created by hand
-(for example, through digitizing done in <em><a href="v.digit.html">v.digit</a></em>).
-
-<p>
-
-The resulting output raster map layer will
-code the subbasins with category values matching
-those of the channel segments passing through them.
-A user-supplied number of passes through the data is
-made in an attempt to fill in these subbasins.
-If the resulting map layer from this program appears to
-have holes within a subbasin, the program should be
-rerun with a higher number of passes.
-<br><br>
-
-
-<h2>NOTES</h2>
-
-The current geographic region setting is ignored.
-Instead, the geographic region for the entire input stream's
-map layer is used.
-
-<h2>SEE ALSO</h2>
-
-See Appendix A of the <b>GRASS</b> <a
-href="http://grass.itc.it/gdp/raster/r.watershed.ps">Tutorial:
-r.watershed</a> for further details on the combined use of
-<em>r.basins.fill</em> and <em><a href="r.watershed.html">r.watershed</a></em>.
-
-<p>
-<em><a href="r.watershed.html">r.watershed</a></em>,
-<em><a href="v.digit.html">v.digit</a></em>
-
-<h2>AUTHORS</h2>
-
-Dale White,
-Dept. of Geography,
-Pennsylvania State University
-<br>
-Larry Band, Dept. of Geography, University of Toronto, Canada
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.basins.fill/r.basins.fill.html (from rev 32770, grass/trunk/raster/r.basins.fill/description.html)
===================================================================
--- grass/trunk/raster/r.basins.fill/r.basins.fill.html (rev 0)
+++ grass/trunk/raster/r.basins.fill/r.basins.fill.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,55 @@
+<h2>DESCRIPTION</h2>
+
+
+<em>r.basins.fill</em>
+generates a raster map layer depicting subbasins, based
+on input raster map layers for the coded stream network
+(where each channel segment has been "coded" with a unique category value)
+and for the ridges within a given watershed.
+The raster map layer depicting ridges should include
+the ridge which defines the perimeter of the watershed.
+The coded stream network can be generated
+as part of the
+<em><a href="r.watershed.html">r.watershed</a></em> program,
+but the map layer of ridges will need to be created by hand
+(for example, through digitizing done in <em><a href="v.digit.html">v.digit</a></em>).
+
+<p>
+
+The resulting output raster map layer will
+code the subbasins with category values matching
+those of the channel segments passing through them.
+A user-supplied number of passes through the data is
+made in an attempt to fill in these subbasins.
+If the resulting map layer from this program appears to
+have holes within a subbasin, the program should be
+rerun with a higher number of passes.
+<br><br>
+
+
+<h2>NOTES</h2>
+
+The current geographic region setting is ignored.
+Instead, the geographic region for the entire input stream's
+map layer is used.
+
+<h2>SEE ALSO</h2>
+
+See Appendix A of the <b>GRASS</b> <a
+href="http://grass.itc.it/gdp/raster/r.watershed.ps">Tutorial:
+r.watershed</a> for further details on the combined use of
+<em>r.basins.fill</em> and <em><a href="r.watershed.html">r.watershed</a></em>.
+
+<p>
+<em><a href="r.watershed.html">r.watershed</a></em>,
+<em><a href="v.digit.html">v.digit</a></em>
+
+<h2>AUTHORS</h2>
+
+Dale White,
+Dept. of Geography,
+Pennsylvania State University
+<br>
+Larry Band, Dept. of Geography, University of Toronto, Canada
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.bitpattern/description.html
===================================================================
--- grass/trunk/raster/r.bitpattern/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.bitpattern/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,52 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-
-<em>r.bitpattern</em> performs bit pattern comparisons.
-The module can be used to pixelwise verify a satellite image
-for low quality pixels if a Quality Control Bit Index map is
-provided (e.g. as for MODIS sensor maps).
-
-The functionality is two-fold:
-
-<ol>
-<li>define position: set bit(s) to 1 which shall match,
- then convert this position pattern to integer, set pattern=
- parameter with that integer value
-<li>define pattern *value* which should be in that position:
- first bit pattern of value, convert to integer, set
- patval= parameter
-</ol>
-
-If several bitpatterns have to be tested, the resulting maps
-can be used to exclude low quality pixel in the input satellite
-image using <em>r.mapcalc</em> (OR and NOT operators).
-
-<h2>EXAMPLE</h2>
-
-<ol>
-<li>define position:
-<pre>
- xx xx 1x xx
- binary: 1000 -> integer: 8 -> pattern=8
-</pre>
-
-<li>define value:
-<pre>
- Ex.: we want to check for 0 in that position
- xx xx 0x xx
- binary: 0000 -> integer: 0 -> patval=0
- if value can be arbitray (0/1), then assume 0 value
-</pre>
-</ol>
-
-<h2>SEE ALSO</h2>
-
-<em>
-<a href="r.mapcalc.html">r.mapcalc</a>
-</em>
-
-<h2>AUTHORS</h2>
-
-Radim Blazek, Markus Neteler
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.bitpattern/r.bitpattern.html (from rev 32770, grass/trunk/raster/r.bitpattern/description.html)
===================================================================
--- grass/trunk/raster/r.bitpattern/r.bitpattern.html (rev 0)
+++ grass/trunk/raster/r.bitpattern/r.bitpattern.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,52 @@
+<h2>DESCRIPTION</h2>
+
+
+<em>r.bitpattern</em> performs bit pattern comparisons.
+The module can be used to pixelwise verify a satellite image
+for low quality pixels if a Quality Control Bit Index map is
+provided (e.g. as for MODIS sensor maps).
+
+The functionality is two-fold:
+
+<ol>
+<li>define position: set bit(s) to 1 which shall match,
+ then convert this position pattern to integer, set pattern=
+ parameter with that integer value
+<li>define pattern *value* which should be in that position:
+ first bit pattern of value, convert to integer, set
+ patval= parameter
+</ol>
+
+If several bitpatterns have to be tested, the resulting maps
+can be used to exclude low quality pixel in the input satellite
+image using <em>r.mapcalc</em> (OR and NOT operators).
+
+<h2>EXAMPLE</h2>
+
+<ol>
+<li>define position:
+<pre>
+ xx xx 1x xx
+ binary: 1000 -> integer: 8 -> pattern=8
+</pre>
+
+<li>define value:
+<pre>
+ Ex.: we want to check for 0 in that position
+ xx xx 0x xx
+ binary: 0000 -> integer: 0 -> patval=0
+ if value can be arbitray (0/1), then assume 0 value
+</pre>
+</ol>
+
+<h2>SEE ALSO</h2>
+
+<em>
+<a href="r.mapcalc.html">r.mapcalc</a>
+</em>
+
+<h2>AUTHORS</h2>
+
+Radim Blazek, Markus Neteler
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.buffer/description.html
===================================================================
--- grass/trunk/raster/r.buffer/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.buffer/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,117 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>r.buffer</em> creates a new raster map layer showing
-buffer (a.k.a. "distance" or "proximity") zones around all
-cells that contain non-NULL category values in an existing
-raster map layer. The distances of buffer zones from cells
-with non-zero category values are user-chosen. Suppose,
-for example, that you want to place buffer zones around
-roads. This program could create the raster map layer
-shown below on the right based on road information
-contained in the raster map layer shown on the left.
-
-<div class="code"><pre>
- 000000000000000000000000 222233333333333333444444
- 111000000000000000000000 111222222222223333333333
- 000111111111100000000000 222111111111122223333333
- 000000001000011100000000 332222221222211122222222
- 000000001000000011111111 333333321233222211111111
- 000000001000000000000000 433333321233333222222222
- 000000001000000000000000 444443321233333333333333
- 000000001000000000000000 444443321233443333333333
- 000000001000000000000000 444443321233444444444444
-
- Category 0: No roads
- Category 1: Road location
- Category 2: Buffer Zone 1 around roads
- Category 3: Buffer Zone 2 around roads
- Category 4: Buffer Zone 3 around roads
-</pre></div>
-<br>
-
-<h2>NOTES</h2>
-
-The user has the option of identifying up to 250 continuous zones.
-The zones are identified by specifying the upper limit of each desired zone
-(<em>r.buffer</em> assumes that <tt>0</tt> is the starting point).
-("Continuous" is used in the sense that each category
-zone's lower value is the previous zone's upper value. The
-first buffer zone always has distance <tt>0</tt> as its lower
-bound.) Buffer distances can be specified using one of five units with the <em>
-units</em> parameter: <em>meters, kilometers, feet, miles</em>, and <em>nautmiles</em>
-(nautical miles).
-<p>
-
-<!-- ??? is this the real method used or some ancient option ??? -->
-Distances from cells containing the user-specified category values
-are calculated using the "fromcell" method. This method locates each
-cell that contains a category value from which distances are to be
-calculated, and draws the requested distance rings around
-them. This method works very fast when there are few cells
-containing the category values of interest, but works
-slowly when there are numerous cells containing the
-category values of interest spread throughout the area.
-<p>
-
-<em>r.buffer</em> measures distances from center of cell to
-center of cell using Euclidean distance measure for
-planimetric locations (like UTM) and using ellipsoidal
-geodesic distance measure for latitude/longitude locations.
-<p>
-
-<em>r.buffer</em> calculates distance zones from all cells having non-NULL
-category values in the <em>input</em> map. If the user wishes to calculate
-distances from only selected <em>input</em> map layer
-category values, the user should run (for example)
-<em><a href="r.reclass.html">r.reclass</a></em> prior to
-<em>r.buffer</em>, to reclass all categories from which distance zones
-are not desired to be calculated into category NULL.
-<p>
-
-The <b>-z</b> flag can be used to ignore raster values of zero instead of NULL
-values in the input raster map.
-<p>
-
-<h2>EXAMPLE</h2>
-
-In the following example, the buffer zones would be (in the default units
-of meters): 0-100, 101-200, 201-300, 301-400 and 401-500.
-<br>
-<div class="code"><pre>
-<b>r.buffer input=</b>roads <b>output=</b>roads.buf <b>distances=</b>100,200,300,400,500
-</pre></div>
-
-Result:
-
-<div class="code"><pre>
-<b>r.category input=</b>roads.buf
-
- 1 distances calculated from these locations
- 2 0-100 meters
- 3 100-200 meters
- 4 200-300 meters
- 5 300-400 meters
- 6 400-500 meters
-</pre></div>
-
-<h2>SEE ALSO</h2>
-
-<em>
-<a href="g.region.html">g.region</a><br>
-<a href="r.cost.html">r.cost</a><br>
-<a href="r.mapcalc.html">r.mapcalc</a><br>
-<a href="r.reclass.html">r.reclass</a><br>
-<a href="v.buffer.html">v.buffer</a>
-</em>
-
-
-<h2>AUTHORS</h2>
-
-Michael Shapiro, U.S. Army Construction Engineering
-Research Laboratory
-<br>
-James Westervelt, U.S. Army Construction Engineering
-Research Laboratory
-
-<p>
-<i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.buffer/r.buffer.html (from rev 32770, grass/trunk/raster/r.buffer/description.html)
===================================================================
--- grass/trunk/raster/r.buffer/r.buffer.html (rev 0)
+++ grass/trunk/raster/r.buffer/r.buffer.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,117 @@
+<h2>DESCRIPTION</h2>
+
+<em>r.buffer</em> creates a new raster map layer showing
+buffer (a.k.a. "distance" or "proximity") zones around all
+cells that contain non-NULL category values in an existing
+raster map layer. The distances of buffer zones from cells
+with non-zero category values are user-chosen. Suppose,
+for example, that you want to place buffer zones around
+roads. This program could create the raster map layer
+shown below on the right based on road information
+contained in the raster map layer shown on the left.
+
+<div class="code"><pre>
+ 000000000000000000000000 222233333333333333444444
+ 111000000000000000000000 111222222222223333333333
+ 000111111111100000000000 222111111111122223333333
+ 000000001000011100000000 332222221222211122222222
+ 000000001000000011111111 333333321233222211111111
+ 000000001000000000000000 433333321233333222222222
+ 000000001000000000000000 444443321233333333333333
+ 000000001000000000000000 444443321233443333333333
+ 000000001000000000000000 444443321233444444444444
+
+ Category 0: No roads
+ Category 1: Road location
+ Category 2: Buffer Zone 1 around roads
+ Category 3: Buffer Zone 2 around roads
+ Category 4: Buffer Zone 3 around roads
+</pre></div>
+<br>
+
+<h2>NOTES</h2>
+
+The user has the option of identifying up to 250 continuous zones.
+The zones are identified by specifying the upper limit of each desired zone
+(<em>r.buffer</em> assumes that <tt>0</tt> is the starting point).
+("Continuous" is used in the sense that each category
+zone's lower value is the previous zone's upper value. The
+first buffer zone always has distance <tt>0</tt> as its lower
+bound.) Buffer distances can be specified using one of five units with the <em>
+units</em> parameter: <em>meters, kilometers, feet, miles</em>, and <em>nautmiles</em>
+(nautical miles).
+<p>
+
+<!-- ??? is this the real method used or some ancient option ??? -->
+Distances from cells containing the user-specified category values
+are calculated using the "fromcell" method. This method locates each
+cell that contains a category value from which distances are to be
+calculated, and draws the requested distance rings around
+them. This method works very fast when there are few cells
+containing the category values of interest, but works
+slowly when there are numerous cells containing the
+category values of interest spread throughout the area.
+<p>
+
+<em>r.buffer</em> measures distances from center of cell to
+center of cell using Euclidean distance measure for
+planimetric locations (like UTM) and using ellipsoidal
+geodesic distance measure for latitude/longitude locations.
+<p>
+
+<em>r.buffer</em> calculates distance zones from all cells having non-NULL
+category values in the <em>input</em> map. If the user wishes to calculate
+distances from only selected <em>input</em> map layer
+category values, the user should run (for example)
+<em><a href="r.reclass.html">r.reclass</a></em> prior to
+<em>r.buffer</em>, to reclass all categories from which distance zones
+are not desired to be calculated into category NULL.
+<p>
+
+The <b>-z</b> flag can be used to ignore raster values of zero instead of NULL
+values in the input raster map.
+<p>
+
+<h2>EXAMPLE</h2>
+
+In the following example, the buffer zones would be (in the default units
+of meters): 0-100, 101-200, 201-300, 301-400 and 401-500.
+<br>
+<div class="code"><pre>
+<b>r.buffer input=</b>roads <b>output=</b>roads.buf <b>distances=</b>100,200,300,400,500
+</pre></div>
+
+Result:
+
+<div class="code"><pre>
+<b>r.category input=</b>roads.buf
+
+ 1 distances calculated from these locations
+ 2 0-100 meters
+ 3 100-200 meters
+ 4 200-300 meters
+ 5 300-400 meters
+ 6 400-500 meters
+</pre></div>
+
+<h2>SEE ALSO</h2>
+
+<em>
+<a href="g.region.html">g.region</a><br>
+<a href="r.cost.html">r.cost</a><br>
+<a href="r.mapcalc.html">r.mapcalc</a><br>
+<a href="r.reclass.html">r.reclass</a><br>
+<a href="v.buffer.html">v.buffer</a>
+</em>
+
+
+<h2>AUTHORS</h2>
+
+Michael Shapiro, U.S. Army Construction Engineering
+Research Laboratory
+<br>
+James Westervelt, U.S. Army Construction Engineering
+Research Laboratory
+
+<p>
+<i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.carve/description.html
===================================================================
--- grass/trunk/raster/r.carve/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.carve/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,48 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>r.carve</em> accepts vector stream data as input, transforms them to
-raster, and subtracts a defaultdepth+additionaldepth from a DEM. If
-the given width is more than 1 cell, it will carve the stream with the
-given width. With the -n flag it should eliminate all flat cells within
-the stream, so when and if the water gets into the stream it will
-flow. The <em>points</em> option generates x,y,z for points which define the stream
-with the z-value of the bottom of the carved-in stream. These points
-can then be combined with contours to interpolate a new DEM with
-better representation of valleys.
-
-<h2>NOTE</h2>
-
-<em>r.carve</em> does not create a depressionless DEM because many
-depressions are in flat areas and not in the streams.
-
-
-<h2>EXAMPLE</h2>
-
-<div class="code"><pre>
-g.region rast=elevation.10m -p
-r.carve rast=elevation.10m vect=streams out=carve_dem width=20 depth=5
-</pre></div>
-
-<h2>BUGS</h2>
-<!-- Is this still the case as of Jan 11, 2008? - EP -->
-The module does not operate yet in latitude-longitude locations. It
-has not been thoroughly tested, so not all options may work properly -
-but this was the intention.
-
-<h2>REFERENCES</h2>
-
-<a href="http://skagit.meas.ncsu.edu/~helena/gmslab/reports/cerl99/rep99.html">Terrain
-modeling and Soil Erosion Simulations for Fort Hood and Fort Polk test
-areas</a>, by Helena Mitasova, Lubos Mitas, William M. Brown, Douglas
-M. Johnston, GMSL (Report for CERL 1999)
-
-<h2>SEE ALSO</h2>
-<em><a href="r.flow.html">r.flow</a></em>,
-<em><a href="r.fill.dir.html">r.fill.dir</a></em>,
-<em><a href="r.watershed.html">r.watershed</a></em>
-
-<h2>AUTHOR</h2>
-Bill Brown (GMSL)<br>
-GRASS 6 update: Brad Douglas
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.carve/r.carve.html (from rev 32770, grass/trunk/raster/r.carve/description.html)
===================================================================
--- grass/trunk/raster/r.carve/r.carve.html (rev 0)
+++ grass/trunk/raster/r.carve/r.carve.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,48 @@
+<h2>DESCRIPTION</h2>
+
+<em>r.carve</em> accepts vector stream data as input, transforms them to
+raster, and subtracts a defaultdepth+additionaldepth from a DEM. If
+the given width is more than 1 cell, it will carve the stream with the
+given width. With the -n flag it should eliminate all flat cells within
+the stream, so when and if the water gets into the stream it will
+flow. The <em>points</em> option generates x,y,z for points which define the stream
+with the z-value of the bottom of the carved-in stream. These points
+can then be combined with contours to interpolate a new DEM with
+better representation of valleys.
+
+<h2>NOTE</h2>
+
+<em>r.carve</em> does not create a depressionless DEM because many
+depressions are in flat areas and not in the streams.
+
+
+<h2>EXAMPLE</h2>
+
+<div class="code"><pre>
+g.region rast=elevation.10m -p
+r.carve rast=elevation.10m vect=streams out=carve_dem width=20 depth=5
+</pre></div>
+
+<h2>BUGS</h2>
+<!-- Is this still the case as of Jan 11, 2008? - EP -->
+The module does not operate yet in latitude-longitude locations. It
+has not been thoroughly tested, so not all options may work properly -
+but this was the intention.
+
+<h2>REFERENCES</h2>
+
+<a href="http://skagit.meas.ncsu.edu/~helena/gmslab/reports/cerl99/rep99.html">Terrain
+modeling and Soil Erosion Simulations for Fort Hood and Fort Polk test
+areas</a>, by Helena Mitasova, Lubos Mitas, William M. Brown, Douglas
+M. Johnston, GMSL (Report for CERL 1999)
+
+<h2>SEE ALSO</h2>
+<em><a href="r.flow.html">r.flow</a></em>,
+<em><a href="r.fill.dir.html">r.fill.dir</a></em>,
+<em><a href="r.watershed.html">r.watershed</a></em>
+
+<h2>AUTHOR</h2>
+Bill Brown (GMSL)<br>
+GRASS 6 update: Brad Douglas
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.cats/description.html
===================================================================
--- grass/trunk/raster/r.cats/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.cats/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,178 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-
-<em>r.category</em> prints the category values and labels for the raster map
-layer specified by <b>map=</b><em>name</em> to standard output.
-
-<p>
-
-The user can specify all needed parameters on the command line, and run the
-program non-interactively. If the user does not specify any categories
-(e.g., using the optional <b>cats=</b><em>range</em>[,<em>range</em>,...]
-argument), then all the category values and labels for the named raster map
-layer that occur in the map are printed. The entire <em>map</em> is read
-using <em><a href="r.describe.html">r.describe</a></em>, to determine which
-categories occur in the <em>map</em>. If a listing of categories is
-specified, then the labels for those categories only are printed. The
-<em>cats</em> may be specified as single category values, or as ranges of
-values. The user may also (optionally) specify that a field separator other
-than a space or tab be used to separate the category value from its
-corresponding category label in the output, by using the
-<b>fs=</b><em>character</em>|<em>space</em>|<em>tab</em> option (see example
-below). If no field separator is specified by the user, a tab is used to
-separate these fields in the output, by default.
-
-<p>
-
-The output is sent to standard output in the form of one category per line,
-with the category value first on the line, then an ASCII TAB character (or
-whatever single character or space is specified using the <b>fs</b>
-parameter), then the label for the category.
-
-
-<h2>NOTES</h2>
-
-Any ASCII TAB characters which may be in the label are replaced by spaces.
-<p>
-The output from <em>r.category</em> can be redirected into a file, or piped into
-another program.
-
-<h3>Input from a file</h3>
-
-The <b>rules</b> option allows the user to assign category labels from values
-found in a file. The label can refer to a single category, range of
-categories, floating point value, or a range of floating point values.
-The format is given as follows.
-<div class="code"><pre>
-cat:Label
-val1:val2:Label
-</pre></div>
-
-If the filename is given as "-", the category labels are read from <tt>stdin</tt>
-
-
-<h3>Default and dynamic category labels</h3>
-
-Default and dynamic category labels can be created for categories that
-are not explicitly labeled.
-
-The coefficient line can be followed by explicit category labels
-which override the format label generation.
-<pre>
- 0:no data
- 2: .
- 5: . ## explicit category labels
- 7: .
-</pre>
-explicit labels can be also of the form:
-<pre>
- 5.5:5:9 label description
- or
- 15:30 label description
-</pre>
-<p>
-In the format line
-<ul>
-<li>$1 refers to the value num*5.0+1000 (ie, using the first 2 coefficients)
-<li>$2 refers to the value num*5.0+1005 (ie, using the last 2 coefficients)
-</ul>
- $1.2 will print $1 with 2 decimal places.
-<p>
-Also, the form $?xxx$yyy$ translates into yyy if the category is 1, xxx
-otherwise. The $yyy$ is optional. Thus
-<p>
- $1 meter$?s
-<p>
-will become: 1 meter (for category 1)<br>
- 2 meters (for category 2), etc.
-
-<p>
-format='Elevation: $1.2 to $2.2 feet' ## Format Statement
-coefficients="5.0,1000,5.0,1005" ## Coefficients
-<p>
-The format and coefficients above would be used to generate the
-following statement in creation of the format appropriate category
-string for category "num":
-<p>
- sprintf(buff,"Elevation: %.2f to %.2f feet", num*5.0+1000, num*5.0*1005)
-
-<p>
-Note: while both the format and coefficent lines must be present
- a blank line for the format string will effectively suppress
- automatic label generation.
-<!--
-Note: quant rules of Categories structures are heavily dependant
-on the fact that rules are stored in the same order they are entered.
-since i-th rule and i-th label are entered at the same time, we
-know that i-th rule maps fp range to i, thus we know for sure
-that cats.labels[i] corresponds to i-th quant rule
--->
-<p>
-To use a "<tt>$</tt>" in the label without triggering the plural test,
-put "<tt>$$</tt>" in the format string.
-<p>
-Use 'single quotes' when using a "<tt>$</tt>" on the command line to
-avoid unwanted shell substitution.
-
-
-<h2>EXAMPLES</h2>
-
-<p>
-<dl>
-<dt><div class="code"><pre>
-r.category map=soils
-</pre></div>
-<dd>
-prints the values and labels associated with all of the categories in the
-<em>soils</em> raster map layer;
-
-<dt><div class="code"><pre>
-r.category map=soils cats=10,12,15-20
-</pre></div>
-<dd>
-prints only the category values and labels for <em>soils</em> map layer
-categories <tt>10, 12</tt>, and <tt>15</tt> through <tt>20</tt>; and
-
-<dt><div class="code"><pre>
-r.category map=soils cats=10,20 fs=':'
-</pre></div>
-<dd>
-prints the values and labels for <em>soils</em> map layer categories
-<tt>10</tt> and <tt>20</tt>, but uses "<tt>:</tt>" (instead of a tab)
-as the character separating the category values from the category
-values in the output.
-</dl>
-
-<dl>
-<dt>Example output:
-<dd>
-<p>
-<div class="code"><pre>
-10:Dumps, mine, Cc
-20:Kyle clay, KaA
-</pre></div>
-</dl>
-
-
-<h2>TODO</h2>
-
-Respect the <b>fs=</b> field separator setting for input rules.
-
-
-<h2>SEE ALSO</h2>
-
-UNIX Manual entries for <i>awk</i> and <i>sort</i>
-
-<p>
-<em><a href="r.coin.html">r.coin</a></em>,
-<em><a href="r.describe.html">r.describe</a></em>,
-<em><a href="d.what.rast.html">d.what.rast</a></em>,
-<em><a href="r.support.html">r.support</a></em>
-
-<h2>AUTHORS</h2>
-
-Michael Shapiro, U.S. Army Construction Engineering Research Laboratory<br>
-Hamish Bowman, University of Otago, New Zealand (label creation options)
-
-<p>
-<i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.cats/r.category.html (from rev 32770, grass/trunk/raster/r.cats/description.html)
===================================================================
--- grass/trunk/raster/r.cats/r.category.html (rev 0)
+++ grass/trunk/raster/r.cats/r.category.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,178 @@
+<h2>DESCRIPTION</h2>
+
+
+<em>r.category</em> prints the category values and labels for the raster map
+layer specified by <b>map=</b><em>name</em> to standard output.
+
+<p>
+
+The user can specify all needed parameters on the command line, and run the
+program non-interactively. If the user does not specify any categories
+(e.g., using the optional <b>cats=</b><em>range</em>[,<em>range</em>,...]
+argument), then all the category values and labels for the named raster map
+layer that occur in the map are printed. The entire <em>map</em> is read
+using <em><a href="r.describe.html">r.describe</a></em>, to determine which
+categories occur in the <em>map</em>. If a listing of categories is
+specified, then the labels for those categories only are printed. The
+<em>cats</em> may be specified as single category values, or as ranges of
+values. The user may also (optionally) specify that a field separator other
+than a space or tab be used to separate the category value from its
+corresponding category label in the output, by using the
+<b>fs=</b><em>character</em>|<em>space</em>|<em>tab</em> option (see example
+below). If no field separator is specified by the user, a tab is used to
+separate these fields in the output, by default.
+
+<p>
+
+The output is sent to standard output in the form of one category per line,
+with the category value first on the line, then an ASCII TAB character (or
+whatever single character or space is specified using the <b>fs</b>
+parameter), then the label for the category.
+
+
+<h2>NOTES</h2>
+
+Any ASCII TAB characters which may be in the label are replaced by spaces.
+<p>
+The output from <em>r.category</em> can be redirected into a file, or piped into
+another program.
+
+<h3>Input from a file</h3>
+
+The <b>rules</b> option allows the user to assign category labels from values
+found in a file. The label can refer to a single category, range of
+categories, floating point value, or a range of floating point values.
+The format is given as follows.
+<div class="code"><pre>
+cat:Label
+val1:val2:Label
+</pre></div>
+
+If the filename is given as "-", the category labels are read from <tt>stdin</tt>
+
+
+<h3>Default and dynamic category labels</h3>
+
+Default and dynamic category labels can be created for categories that
+are not explicitly labeled.
+
+The coefficient line can be followed by explicit category labels
+which override the format label generation.
+<pre>
+ 0:no data
+ 2: .
+ 5: . ## explicit category labels
+ 7: .
+</pre>
+explicit labels can be also of the form:
+<pre>
+ 5.5:5:9 label description
+ or
+ 15:30 label description
+</pre>
+<p>
+In the format line
+<ul>
+<li>$1 refers to the value num*5.0+1000 (ie, using the first 2 coefficients)
+<li>$2 refers to the value num*5.0+1005 (ie, using the last 2 coefficients)
+</ul>
+ $1.2 will print $1 with 2 decimal places.
+<p>
+Also, the form $?xxx$yyy$ translates into yyy if the category is 1, xxx
+otherwise. The $yyy$ is optional. Thus
+<p>
+ $1 meter$?s
+<p>
+will become: 1 meter (for category 1)<br>
+ 2 meters (for category 2), etc.
+
+<p>
+format='Elevation: $1.2 to $2.2 feet' ## Format Statement
+coefficients="5.0,1000,5.0,1005" ## Coefficients
+<p>
+The format and coefficients above would be used to generate the
+following statement in creation of the format appropriate category
+string for category "num":
+<p>
+ sprintf(buff,"Elevation: %.2f to %.2f feet", num*5.0+1000, num*5.0*1005)
+
+<p>
+Note: while both the format and coefficent lines must be present
+ a blank line for the format string will effectively suppress
+ automatic label generation.
+<!--
+Note: quant rules of Categories structures are heavily dependant
+on the fact that rules are stored in the same order they are entered.
+since i-th rule and i-th label are entered at the same time, we
+know that i-th rule maps fp range to i, thus we know for sure
+that cats.labels[i] corresponds to i-th quant rule
+-->
+<p>
+To use a "<tt>$</tt>" in the label without triggering the plural test,
+put "<tt>$$</tt>" in the format string.
+<p>
+Use 'single quotes' when using a "<tt>$</tt>" on the command line to
+avoid unwanted shell substitution.
+
+
+<h2>EXAMPLES</h2>
+
+<p>
+<dl>
+<dt><div class="code"><pre>
+r.category map=soils
+</pre></div>
+<dd>
+prints the values and labels associated with all of the categories in the
+<em>soils</em> raster map layer;
+
+<dt><div class="code"><pre>
+r.category map=soils cats=10,12,15-20
+</pre></div>
+<dd>
+prints only the category values and labels for <em>soils</em> map layer
+categories <tt>10, 12</tt>, and <tt>15</tt> through <tt>20</tt>; and
+
+<dt><div class="code"><pre>
+r.category map=soils cats=10,20 fs=':'
+</pre></div>
+<dd>
+prints the values and labels for <em>soils</em> map layer categories
+<tt>10</tt> and <tt>20</tt>, but uses "<tt>:</tt>" (instead of a tab)
+as the character separating the category values from the category
+values in the output.
+</dl>
+
+<dl>
+<dt>Example output:
+<dd>
+<p>
+<div class="code"><pre>
+10:Dumps, mine, Cc
+20:Kyle clay, KaA
+</pre></div>
+</dl>
+
+
+<h2>TODO</h2>
+
+Respect the <b>fs=</b> field separator setting for input rules.
+
+
+<h2>SEE ALSO</h2>
+
+UNIX Manual entries for <i>awk</i> and <i>sort</i>
+
+<p>
+<em><a href="r.coin.html">r.coin</a></em>,
+<em><a href="r.describe.html">r.describe</a></em>,
+<em><a href="d.what.rast.html">d.what.rast</a></em>,
+<em><a href="r.support.html">r.support</a></em>
+
+<h2>AUTHORS</h2>
+
+Michael Shapiro, U.S. Army Construction Engineering Research Laboratory<br>
+Hamish Bowman, University of Otago, New Zealand (label creation options)
+
+<p>
+<i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.circle/description.html
===================================================================
--- grass/trunk/raster/r.circle/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.circle/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,56 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-This module creates an output raster map centered on the <em>x,y</em> values specified
-with the <em>coordinate</em> parameter, out to the edge of the current region.
-The output cell values increase linearly from the specified center. The <em>min</em>
-and <em>max</em> parameters control the inner and outer output raster map radii, respectively.
-
-<p>
-The <em>mult</em> parameter can be used to multiply the output raster cells by a common factor.
-Note that this parameter does not affect the output raster position or size; only the z-values
-are changed with this parameter.
-<p>
-Binary-output raster maps (solid circles of one value) can be created
-with the <b>-b</b> flag. Raster maps so created can be used to create
-binary filters for use in <em>i.ifft</em> (inverse Fourier transformations;
-apply filter with <em>r.mask</em>).
-
-
-<h2>EXAMPLES</h2>
-
-Generate a raster circle at current map center with a radius of 300m and outwardly
-increasing raster values:
-
-<pre>
-EASTCENTER=`g.region -c | awk ' /center easting:/ { print $3 }'`
-NORTHCENTER=`g.region -c | awk ' /center northing:/ { print $3 }'`
-r.circle output=circle coordinate=${EASTCENTER},${NORTHCENTER} max=300
-</pre>
-
-Generate a binary raster ring around current map center with an inner radius
-of 500m and an outer radius of 1000m:
-
-<pre>
-EASTCENTER=`g.region -c | awk ' /center easting:/ { print $3 }'`
-NORTHCENTER=`g.region -c | awk ' /center northing:/ { print $3 }'`
-r.circle -b output=circle coordinate=${EASTCENTER},${NORTHCENTER} min=500 max=1000
-</pre>
-
-
-<h2>SEE ALSO</h2>
-<em>
-<a href="g.region.html">g.region</a>,
-<a href="g.remove.html">g.remove</a>,
-<a href="g.rename.html">g.rename</a>,
-<a href="i.fft.html">i.fft</a>,
-<a href="i.ifft.html">i.ifft</a>,
-<a href="r.mask">r.mask</a>
-</em>
-
-
-<h2>AUTHOR</h2>
-Bill Brown, U.S. Army Construction Engineering Research Laboratory<br>
-Additional flag/min/max parameter by Markus Neteler, University of Hannover
-
-<p>
-<i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.circle/r.circle.html (from rev 32770, grass/trunk/raster/r.circle/description.html)
===================================================================
--- grass/trunk/raster/r.circle/r.circle.html (rev 0)
+++ grass/trunk/raster/r.circle/r.circle.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,56 @@
+<h2>DESCRIPTION</h2>
+
+This module creates an output raster map centered on the <em>x,y</em> values specified
+with the <em>coordinate</em> parameter, out to the edge of the current region.
+The output cell values increase linearly from the specified center. The <em>min</em>
+and <em>max</em> parameters control the inner and outer output raster map radii, respectively.
+
+<p>
+The <em>mult</em> parameter can be used to multiply the output raster cells by a common factor.
+Note that this parameter does not affect the output raster position or size; only the z-values
+are changed with this parameter.
+<p>
+Binary-output raster maps (solid circles of one value) can be created
+with the <b>-b</b> flag. Raster maps so created can be used to create
+binary filters for use in <em>i.ifft</em> (inverse Fourier transformations;
+apply filter with <em>r.mask</em>).
+
+
+<h2>EXAMPLES</h2>
+
+Generate a raster circle at current map center with a radius of 300m and outwardly
+increasing raster values:
+
+<pre>
+EASTCENTER=`g.region -c | awk ' /center easting:/ { print $3 }'`
+NORTHCENTER=`g.region -c | awk ' /center northing:/ { print $3 }'`
+r.circle output=circle coordinate=${EASTCENTER},${NORTHCENTER} max=300
+</pre>
+
+Generate a binary raster ring around current map center with an inner radius
+of 500m and an outer radius of 1000m:
+
+<pre>
+EASTCENTER=`g.region -c | awk ' /center easting:/ { print $3 }'`
+NORTHCENTER=`g.region -c | awk ' /center northing:/ { print $3 }'`
+r.circle -b output=circle coordinate=${EASTCENTER},${NORTHCENTER} min=500 max=1000
+</pre>
+
+
+<h2>SEE ALSO</h2>
+<em>
+<a href="g.region.html">g.region</a>,
+<a href="g.remove.html">g.remove</a>,
+<a href="g.rename.html">g.rename</a>,
+<a href="i.fft.html">i.fft</a>,
+<a href="i.ifft.html">i.ifft</a>,
+<a href="r.mask">r.mask</a>
+</em>
+
+
+<h2>AUTHOR</h2>
+Bill Brown, U.S. Army Construction Engineering Research Laboratory<br>
+Additional flag/min/max parameter by Markus Neteler, University of Hannover
+
+<p>
+<i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.clump/description.html
===================================================================
--- grass/trunk/raster/r.clump/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.clump/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,53 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>r.clump</em> finds all areas of contiguous cell category values in the
-input raster map layer <em>name.</em> It assigns a unique category value
-to each such area ("clump") in the resulting output raster map layer
-<em>name.</em>
-
-Category distinctions in the input raster map layer are preserved. This
-means that if distinct category values are adjacent, they will NOT be
-clumped together. (The user can run <em><A
-HREF="r.reclass.html">r.reclass</a></em> prior to <em>r.clump</em> to
-recategorize cells and reassign cell category values.)
-
-<h2>NOTES</h2>
-
-<em>r.clump</em> moves a 2x2 matrix over the input raster map layer.
-The lower right-hand corner of the matrix is grouped with the cells above it,
-or to the left of it (diagonal cells are not considered.)
-<p>
-
-<em>r.clump</em> works properly with raster map layers that
-contain only "fat" areas (more than a single cell in
-width). Linear elements (lines that are a single cell
-wide) may or may not be clumped together depending on the
-direction of the line - horizontal and vertical lines of
-cells are considered to be contiguous, but diagonal lines
-of cells are not considered to be contiguous and are broken
-up into separate clumps.
-
-<p>
-
-A random color table and other support files are
-generated for the <em>output</em> raster map layer.
-
-<h2>SEE ALSO</h2>
-
-<em><a href="r.average.html">r.average</a></em><br>
-<em><a href="r.buffer.html">r.buffer</a></em><br>
-<em><a href="r.grow.html">r.grow</a><br></em><br>
-<em><a href="r.mapcalc.html">r.mapcalc</a></em><br>
-<em><a href="r.mfilter.html">r.mfilter</a></em><br>
-<em><a href="r.neighbors.html">r.neighbors</a></em><br>
-<em><a href="r.to.vect.html">r.to.vect</a></em><br>
-<em><a href="r.reclass.html">r.reclass</a></em><br>
-<em><a href="r.statistics.html">r.statistics</a></em><br>
-<em><a href="r.support.html">r.support</a></em>
-
-<h2>AUTHOR</h2>
-
-Michael Shapiro, U.S. Army Construction Engineering
-Research Laboratory
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.clump/r.clump.html (from rev 32770, grass/trunk/raster/r.clump/description.html)
===================================================================
--- grass/trunk/raster/r.clump/r.clump.html (rev 0)
+++ grass/trunk/raster/r.clump/r.clump.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,53 @@
+<h2>DESCRIPTION</h2>
+
+<em>r.clump</em> finds all areas of contiguous cell category values in the
+input raster map layer <em>name.</em> It assigns a unique category value
+to each such area ("clump") in the resulting output raster map layer
+<em>name.</em>
+
+Category distinctions in the input raster map layer are preserved. This
+means that if distinct category values are adjacent, they will NOT be
+clumped together. (The user can run <em><A
+HREF="r.reclass.html">r.reclass</a></em> prior to <em>r.clump</em> to
+recategorize cells and reassign cell category values.)
+
+<h2>NOTES</h2>
+
+<em>r.clump</em> moves a 2x2 matrix over the input raster map layer.
+The lower right-hand corner of the matrix is grouped with the cells above it,
+or to the left of it (diagonal cells are not considered.)
+<p>
+
+<em>r.clump</em> works properly with raster map layers that
+contain only "fat" areas (more than a single cell in
+width). Linear elements (lines that are a single cell
+wide) may or may not be clumped together depending on the
+direction of the line - horizontal and vertical lines of
+cells are considered to be contiguous, but diagonal lines
+of cells are not considered to be contiguous and are broken
+up into separate clumps.
+
+<p>
+
+A random color table and other support files are
+generated for the <em>output</em> raster map layer.
+
+<h2>SEE ALSO</h2>
+
+<em><a href="r.average.html">r.average</a></em><br>
+<em><a href="r.buffer.html">r.buffer</a></em><br>
+<em><a href="r.grow.html">r.grow</a><br></em><br>
+<em><a href="r.mapcalc.html">r.mapcalc</a></em><br>
+<em><a href="r.mfilter.html">r.mfilter</a></em><br>
+<em><a href="r.neighbors.html">r.neighbors</a></em><br>
+<em><a href="r.to.vect.html">r.to.vect</a></em><br>
+<em><a href="r.reclass.html">r.reclass</a></em><br>
+<em><a href="r.statistics.html">r.statistics</a></em><br>
+<em><a href="r.support.html">r.support</a></em>
+
+<h2>AUTHOR</h2>
+
+Michael Shapiro, U.S. Army Construction Engineering
+Research Laboratory
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.coin/description.html
===================================================================
--- grass/trunk/raster/r.coin/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.coin/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,204 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>r.coin</em> tabulates the mutual occurrence of two
-raster map layers' categories with respect to one another.
-This analysis program respects the current geographic
-region and mask settings.
-
-<p>
-
-<em>r.coin</em>
-tabulates the coincidence of category values among the two
-map layers and prepares the basic table from which the
-report is to be created. This tabulation is followed by an
-indication of how long the coincidence table will be. If
-the table is extremely long, the user may decide that
-viewing it is not so important after all, and may cancel
-the request at this point. Assuming the user continues,
-<em>r.coin</em> then allows the user to choose one of eight
-units of measure in which the report results can be given.
-These units are:
-
-<p>
-
-<dl>
-<dt><em>c</em> <dd>cells
-<dt><em>p</em> <dd>percent cover of region
-<dt><em>x</em> <dd>percent of <map name> category (column)
-<dt><em>y</em> <dd>percent of <map name> category (row)
-<dt><em>a</em> <dd>acres
-<dt><em>h</em> <dd>hectares
-<dt><em>k</em> <dd>square kilometers
-<dt><em>m</em> <dd>square miles
-</dl>
-
-<p>
-
-Note that three of these options give results as percentage
-values: "p" is based on the grand total number of cells;
-"x" is based on only column totals; and "y" is based on
-only row totals. Only one unit of measure can be selected
-per report output. Type in just one of the letters
-designating a unit of measure followed by a
-<RETURN>. The report will be printed to the screen
-for review. After reviewing the report on the screen, the
-user is given several options. The report may be saved to
-a file and/or sent to a printer. If printed, it may be
-printed with either 80 or 132 columns. Finally, the user
-is given the option to rerun the coincidence tabulation
-using a different unit of measurement.
-
-<p>
-
-<h2>NOTES</h2>
-
-It is <b>not</b> a good idea to run <em>r.coin</em> on a
-map layer which has a monstrous number of categories (e.g.,
-unreclassed elevation). Because <em>r.coin</em> reports
-information for each and every category, it is better to
-reclassify those categories (using <em>r.reclass</em>)
-into a more manageable number prior to running
-<em>r.coin</em> on the reclassed raster map layer.
-
-<p>
-
-<h2>EXAMPLE</h2>
-
-Below is a sample of tabular output produced by
-<em>r.coin</em>. Here, map output is stated in units of
-square miles. The report tabulates the coincidence of the
-Spearfish sample database's <em>owner</em> and
-<em>road</em> raster map layers' categories. The
-<em>owner</em> categories in this case refer to whether the
-land is in private hands (category 1) or is owned by the
-U.S. Forest Service (category 2). The <em>roads</em> map
-layer categories refer to various types of roads (with the
-exception of category value "0", which indicates "no data";
-i.e., map locations at which no roads exist).
-<em>r.coin</em> does not report category labels. The user
-should run
-<em><a href="r.report.html">r.report</a></em> or
-<em><a href="r.category.html">r.category</a></em>
-to obtain this information.
-
-<p>
-
-The body of the report is arranged in panels. The map layer
-with the most categories is arranged along the vertical
-axis of the table; the other, along the horizontal axis.
-Each panel has a maximum of 5 categories (9 if printed)
-across the top. In addition, the last two columns reflect a
-cross total of each column for each row. All of the
-categories of the map layer arranged along the vertical
-axis are included in each panel. There is a total at the
-bottom of each column representing the sum of all the rows
-in that column. A second total represents the sum of all
-the non-zero category rows. A cross total (Table Row Total)
-of all columns for each row appears in a separate panel.
-
-<p>
-
-Note how the following information may be obtained from the sample report.
-
-<p>
-
-In the Spearfish data base, in area not owned by the Forest Service, there
-are 50.63 square miles of land not used for roads. Roads make up 9.27 square
-miles of land in this area.
-<p>
-Of the total 102.70 square miles in Spearfish, 42.80
-square miles is owned by the Forest Service.
-<br>
-In total, there are 14.58 square miles of roads.
-<p>
-There are more category 2 roads outside Forest Service land
-(2.92 mi. sq.)
-than there are inside Forest land boundaries (0.72 mi. sq.).
-
-<p>
-Following is a sample report.
-
-<pre>
-+------------------------------------------------------------+
-| COINCIDENCE TABULATION REPORT |
-|------------------------------------------------------------|
-|Location: spearfish Mapset: PERMANENT Date: Wed Jun 1 |
-| |
-| Layer 1: owner -- Ownership |
-| Layer 2: roads -- Roads |
-| Mask: none |
-| |
-| Units: square miles |
-|------------------------------------------------------------|
-| Window: North: 4928000.00 |
-| West: 590000.00 East: 609000.00 |
-| South: 4914000.00 |
-+------------------------------------------------------------+
-
-Panel #1 of 1
-+--------------------------------------------------------+
-| | owner | Panel Row Total |
-| cat# | 1 | 2 | w cat 0 | w/o cat 0 |
-|--------------------------------------------------------|
-|r 0 | 50.63 | 37.49 | 88.12 | 88.12 |
-|o 1 | 1.53 | 0.68 | 2.21 | 2.21 |
-|a 2 | 2.92 | 0.72 | 3.64 | 3.64 |
-|d 3 | 3.97 | 2.57 | 6.54 | 6.54 |
-|s 4 | 0.65 | 1.36 | 2.00 | 2.00 |
-| 5 | 0.19 | 0.00 | 0.19 | 0.19 |
-|--------------------------------------------------------|
-|Total | | | | |
-|with 0 | 59.90 | 42.80 | 102.70 | 102.70 |
-|--------------------------------------------------------|
-|w/o 0 | 9.27 | 5.32 | 14.58 | 14.58 |
-+--------------------------------------------------------+
-
-
-+--------------------------------+
-| | Table Row Total |
-| cat# | w cat 0 | w/o cat 0 |
-|--------------------------------|
-|r 0 | 88.12 | 88.12 |
-|o 1 | 2.21 | 2.21 |
-|a 2 | 3.64 | 3.64 |
-|d 3 | 6.54 | 6.54 |
-|s 4 | 2.00 | 2.00 |
-| 5 | 0.19 | 0.19 |
-|--------------------------------|
-|Total | | |
-|with 0 | 102.70 | 102.70 |
-|--------------------------------|
-|w/o 0 | 14.58 | 14.58 |
-+--------------------------------+
-</pre>
-
-<p>
-
-<em>r.coin</em> calculates the coincidence of two raster
-map layers. Although <em>r.coin</em> allows the user to
-rerun the report using different units, it is not possible
-to simply rerun the report with different map layers. In
-order to choose new map layers, it is necessary to rerun
-<em>r.coin.</em>
-
-<h2>SEE ALSO</h2>
-
-<em>
-<a href="g.region.html">g.region</a>,
-<!-- not ported to GRASS 6 <a href="m.ipf.html">m.ipf</a>, -->
-<a href="r.category.html">r.category</a>,
-<a href="r.describe.html">r.describe</a>,
-<a href="r.reclass.html">r.reclass</a>,
-<a href="r.report.html">r.report</a>,
-<a href="r.stats.html">r.stats</a>
-</em>
-
-<h2>AUTHORS</h2>
-
-Michael O'Shea,
-<br>
-Michael Shapiro, <br>
-U.S. Army Construction Engineering Research Laboratory
-
-<p>
-<i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.coin/r.coin.html (from rev 32770, grass/trunk/raster/r.coin/description.html)
===================================================================
--- grass/trunk/raster/r.coin/r.coin.html (rev 0)
+++ grass/trunk/raster/r.coin/r.coin.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,204 @@
+<h2>DESCRIPTION</h2>
+
+<em>r.coin</em> tabulates the mutual occurrence of two
+raster map layers' categories with respect to one another.
+This analysis program respects the current geographic
+region and mask settings.
+
+<p>
+
+<em>r.coin</em>
+tabulates the coincidence of category values among the two
+map layers and prepares the basic table from which the
+report is to be created. This tabulation is followed by an
+indication of how long the coincidence table will be. If
+the table is extremely long, the user may decide that
+viewing it is not so important after all, and may cancel
+the request at this point. Assuming the user continues,
+<em>r.coin</em> then allows the user to choose one of eight
+units of measure in which the report results can be given.
+These units are:
+
+<p>
+
+<dl>
+<dt><em>c</em> <dd>cells
+<dt><em>p</em> <dd>percent cover of region
+<dt><em>x</em> <dd>percent of <map name> category (column)
+<dt><em>y</em> <dd>percent of <map name> category (row)
+<dt><em>a</em> <dd>acres
+<dt><em>h</em> <dd>hectares
+<dt><em>k</em> <dd>square kilometers
+<dt><em>m</em> <dd>square miles
+</dl>
+
+<p>
+
+Note that three of these options give results as percentage
+values: "p" is based on the grand total number of cells;
+"x" is based on only column totals; and "y" is based on
+only row totals. Only one unit of measure can be selected
+per report output. Type in just one of the letters
+designating a unit of measure followed by a
+<RETURN>. The report will be printed to the screen
+for review. After reviewing the report on the screen, the
+user is given several options. The report may be saved to
+a file and/or sent to a printer. If printed, it may be
+printed with either 80 or 132 columns. Finally, the user
+is given the option to rerun the coincidence tabulation
+using a different unit of measurement.
+
+<p>
+
+<h2>NOTES</h2>
+
+It is <b>not</b> a good idea to run <em>r.coin</em> on a
+map layer which has a monstrous number of categories (e.g.,
+unreclassed elevation). Because <em>r.coin</em> reports
+information for each and every category, it is better to
+reclassify those categories (using <em>r.reclass</em>)
+into a more manageable number prior to running
+<em>r.coin</em> on the reclassed raster map layer.
+
+<p>
+
+<h2>EXAMPLE</h2>
+
+Below is a sample of tabular output produced by
+<em>r.coin</em>. Here, map output is stated in units of
+square miles. The report tabulates the coincidence of the
+Spearfish sample database's <em>owner</em> and
+<em>road</em> raster map layers' categories. The
+<em>owner</em> categories in this case refer to whether the
+land is in private hands (category 1) or is owned by the
+U.S. Forest Service (category 2). The <em>roads</em> map
+layer categories refer to various types of roads (with the
+exception of category value "0", which indicates "no data";
+i.e., map locations at which no roads exist).
+<em>r.coin</em> does not report category labels. The user
+should run
+<em><a href="r.report.html">r.report</a></em> or
+<em><a href="r.category.html">r.category</a></em>
+to obtain this information.
+
+<p>
+
+The body of the report is arranged in panels. The map layer
+with the most categories is arranged along the vertical
+axis of the table; the other, along the horizontal axis.
+Each panel has a maximum of 5 categories (9 if printed)
+across the top. In addition, the last two columns reflect a
+cross total of each column for each row. All of the
+categories of the map layer arranged along the vertical
+axis are included in each panel. There is a total at the
+bottom of each column representing the sum of all the rows
+in that column. A second total represents the sum of all
+the non-zero category rows. A cross total (Table Row Total)
+of all columns for each row appears in a separate panel.
+
+<p>
+
+Note how the following information may be obtained from the sample report.
+
+<p>
+
+In the Spearfish data base, in area not owned by the Forest Service, there
+are 50.63 square miles of land not used for roads. Roads make up 9.27 square
+miles of land in this area.
+<p>
+Of the total 102.70 square miles in Spearfish, 42.80
+square miles is owned by the Forest Service.
+<br>
+In total, there are 14.58 square miles of roads.
+<p>
+There are more category 2 roads outside Forest Service land
+(2.92 mi. sq.)
+than there are inside Forest land boundaries (0.72 mi. sq.).
+
+<p>
+Following is a sample report.
+
+<pre>
++------------------------------------------------------------+
+| COINCIDENCE TABULATION REPORT |
+|------------------------------------------------------------|
+|Location: spearfish Mapset: PERMANENT Date: Wed Jun 1 |
+| |
+| Layer 1: owner -- Ownership |
+| Layer 2: roads -- Roads |
+| Mask: none |
+| |
+| Units: square miles |
+|------------------------------------------------------------|
+| Window: North: 4928000.00 |
+| West: 590000.00 East: 609000.00 |
+| South: 4914000.00 |
++------------------------------------------------------------+
+
+Panel #1 of 1
++--------------------------------------------------------+
+| | owner | Panel Row Total |
+| cat# | 1 | 2 | w cat 0 | w/o cat 0 |
+|--------------------------------------------------------|
+|r 0 | 50.63 | 37.49 | 88.12 | 88.12 |
+|o 1 | 1.53 | 0.68 | 2.21 | 2.21 |
+|a 2 | 2.92 | 0.72 | 3.64 | 3.64 |
+|d 3 | 3.97 | 2.57 | 6.54 | 6.54 |
+|s 4 | 0.65 | 1.36 | 2.00 | 2.00 |
+| 5 | 0.19 | 0.00 | 0.19 | 0.19 |
+|--------------------------------------------------------|
+|Total | | | | |
+|with 0 | 59.90 | 42.80 | 102.70 | 102.70 |
+|--------------------------------------------------------|
+|w/o 0 | 9.27 | 5.32 | 14.58 | 14.58 |
++--------------------------------------------------------+
+
+
++--------------------------------+
+| | Table Row Total |
+| cat# | w cat 0 | w/o cat 0 |
+|--------------------------------|
+|r 0 | 88.12 | 88.12 |
+|o 1 | 2.21 | 2.21 |
+|a 2 | 3.64 | 3.64 |
+|d 3 | 6.54 | 6.54 |
+|s 4 | 2.00 | 2.00 |
+| 5 | 0.19 | 0.19 |
+|--------------------------------|
+|Total | | |
+|with 0 | 102.70 | 102.70 |
+|--------------------------------|
+|w/o 0 | 14.58 | 14.58 |
++--------------------------------+
+</pre>
+
+<p>
+
+<em>r.coin</em> calculates the coincidence of two raster
+map layers. Although <em>r.coin</em> allows the user to
+rerun the report using different units, it is not possible
+to simply rerun the report with different map layers. In
+order to choose new map layers, it is necessary to rerun
+<em>r.coin.</em>
+
+<h2>SEE ALSO</h2>
+
+<em>
+<a href="g.region.html">g.region</a>,
+<!-- not ported to GRASS 6 <a href="m.ipf.html">m.ipf</a>, -->
+<a href="r.category.html">r.category</a>,
+<a href="r.describe.html">r.describe</a>,
+<a href="r.reclass.html">r.reclass</a>,
+<a href="r.report.html">r.report</a>,
+<a href="r.stats.html">r.stats</a>
+</em>
+
+<h2>AUTHORS</h2>
+
+Michael O'Shea,
+<br>
+Michael Shapiro, <br>
+U.S. Army Construction Engineering Research Laboratory
+
+<p>
+<i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.colors/description.html
===================================================================
--- grass/trunk/raster/r.colors/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.colors/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,314 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<i>r.colors</i> allows the user to create and/or modify the color table for a
-raster map layer. The map layer (specified on the command line by
-<b>map=</b><i>name</i>) must exist in the user's current mapset search path.
-The color table specified by <b>color=</b><i>type</i> must be one of the
-following:
-
-<pre>
- color type description
- aspect (aspect oriented grey colors)
- aspectcolr (aspect oriented rainbow colors)
- bcyr (blue through cyan through yellow to red)
- bgyr (blue through green through yellow to red)
- byg (blue through yellow to green colors)
- byr (blue through yellow to red colors)
- curvature (for terrain curvatures (from v.surf.rst and r.slope.aspect curvature colors))
- differences (differences oriented colors)
- elevation (maps percentage ranges of raster values to elevation color ramp)
- etopo2 (rainbow color ramp for the ETOPO2 2-minute Worldwide Bathymetry/Topography dataset)
- evi (enhanced vegetative index colors)
- grey (grey scale)
- grey1.0 (grey scale for raster values between 0.0-1.0)
- grey255 (grey scale for raster values bewtween 0-255)
- grey.eq (histogram-equalized grey scale)
- grey.log (histogram logarithmic transformed grey scale)
- gyr (green through yellow to red colors)
- ndvi (Normalized Difference Vegetation Index colors)
- population (color table covering human population classification breaks)
- rainbow (rainbow color table)
- ramp (color ramp)
- random (random color table)
- rules (create new color table based on user-specified rules)
- ryb (red through yellow to blue colors)
- ryg (red through yellow to green colors)
- slope (r.slope.aspect-type slope colors for raster values 0-90)
- srtm (color palette for Shuttle Radar Topography Mission elevation values)
- terrain (global elevation color table covering -11000 to +8850m)
- wave (color wave)
-</pre>
-
-<p>
-The <b>rast</b> option allows user to specify a raster map <i>name</i> from which
-to copy the color map.
-
-<p>
-Extra color tables (aspect, aspectcolr, bcyr, bgyr, byg, byr, curvature, differences,
-elevation, etopo2, evi, grey, grey1.0, grey255, gyr, ndvi, population, rainbow, ramp, ryb, ryg, slope, srtm, terrain, wave) are stored in $GISBASE/etc/colors/.
-User-defined color tables can also be stored in this directory for access from the <em>color</em> parameter.
-<p>
-The <b>-e</b> flag equalizes the original raster's color table. It can preclude
-the need for <em>grey.eq</em> rule, when used as
-<b>-e color=</b><em>grey</em>. Note however, that this will not yield a color
-table identical to <em>color=grey.eq</em>, because <em>grey.eq</em> scales
-the fraction by 256 to get a grey level, while <b>-e</b> uses it to interpolate
-the original colour table. If the original colour table is a 0-255 grey scale,
-<b>-e</b> is effectively scaling the fraction by 255. Different algorithms are
-used. <b>-e</b> is designed to work with any color table, both the floating
-point and the integer raster maps.
-
-<p>
-The <b>-g</b> flag divides the raster's grey value range into 100
-logarithmically equal steps (where "step" is a rule with the same grey level
-for the start and end points). It can preclude the need for <em>grey.log</em>
-rule, when used as <b>-g color=</b><em>grey</em>. Note however, that this
-will not yield a color table identical to <em>color=grey.log</em>. Different
-algorithms are used. Unlike <b>color=</b><em>grey.log</em>, <b>-g</b> is
-designed to work with both floating point and integer rasters, without
-performance issues with large datasets, of any original color table. Logarithmic
-scaling doesn't work on negative values. In the case when the value range
-includes zero, there's no realistic solution.
-
-<p>
-The <b>-e</b> and <b>-g</b> flags are not mutually exclusive.
-
-<p>
-If the user specifies the <b>-w</b> flag, the current color table file for
-the input map will not be overwritten. This means that the color table is
-created only if the <i>map</i> does not already have a color table. If this
-option is not specified, the color table will be created if one does not
-exist, or modified if it does.
-
-<p>
-If the user sets the <b>-q</b> flag, <i>r.colors</i> will run quietly,
-Without printing numerous messages on its progress to standard output.
-<p>Color table types <i>aspect, grey, grey.eq</i> (histogram-equalized grey
-scale), <i>byg</i> (blue-yellow-green), <i>byr</i> (blue-yellow-red),
-<i>gyr</i> (green-yellow-red), <i>rainbow, ramp, ryg</i> (red-yellow-green),
-<i>random</i>, and <i>wave</i> are pre-defined color tables that
-<i>r.colors</i> knows how to create without any further input.
-
-<p>
-In general, tables which associate colors with percentages (aspect, bcyr, byg,
-byr, elevation, grey, gyr, rainbow, ramp, ryb, ryg and wave) can be applied to
-any data, while those which use absolute values (aspectcolr, curvature, etopo2,
-evi, ndvi, population, slope, srtm, and terrain) only make sense for data with
-certain ranges.
-
-One can get a rough idea of the applicability of a colour table by reading the
-corresponding rules file ($GISBASE/etc/colors/<name>).
-For example the <em>slope</em> rule is defined as:
-
-<div class="code"><pre>
-0 255:255:255
-2 255:255:0
-5 0:255:0
-10 0:255 255
-15 0:0:255
-30 255:0:255
-50 255:0:0
-90 0:0:0
-</pre></div>
-
-<p>
-This is designed for the slope map generated by r.slope.aspect, where the value
-is a slope angle between 0 and 90 degrees.
-
-<p>
-Similarly, the <em>aspectcolr</em> rule:
-
-<div class="code"><pre>
-0 white
-1 yellow
-90 green
-180 cyan
-270 red
-360 yellow
-</pre></div>
-
-<p>
-is designed for the aspect maps produced by r.slope.aspect, where the value is a
-heading between 0 and 360 degrees.
-
-<p>
-The <i>rules</i> color table type will cause <i>r.colors</i> to read color
-table specifications from standard input (stdin) and will build the color table
-accordingly.
-
-<p>
-Using color table type <i>rules</i>, there are <!--three-->two ways to build a color
-table: <!--by color list,--> by category values and by "percent" values.
-
-<!-- HB: this causes an error in current code, maybe easy to enable functionality from old code??
-<p>
-Building a customized color table by color list is the simplest of the three
-rules methods: just list the colors you wish to appear in the color table in the
-order that you wish them to appear. Use the standard GRASS color names: white,
-black, red, green, blue, yellow, magenta, cyan, aqua, grey, gray, orange, brown,
-purple, violet, and indigo.
-
-<p>
-For example, to create a color table for the raster map layer <i>elevation</i>
-that assigns greens to low map category values, browns to the next larger
-map category values, and yellows to the still larger map category values,
-one would type:
-
-<div class="code"><pre>
-<b>r.colors map=</b><i>elevation</i> <b>color=</b><i>rules</i>
-green
-brown
-yellow
-end
-</pre></div>
--->
-<p>
-To build a color table by category values' indices, the user should determine
-the range of category values in the raster map layer with which the color table
-will be used. Specific category values will then be associated with specific
-colors. Note that a color does not have to be assigned for every valid category
-value because <i>r.colors</i> will interpolate a color ramp to fill in where
-color specification rules have been left out. The format of such a specification
-is as follows:
-
-<div class="code"><pre>
-category_value color_name
-category_value color_name
-.. ..
-.. ..
-category_value color_name
-end
-</pre></div>
-
-<p>
-Each category value must be valid for the raster map layer, category values must
-be in ascending order and only use standard GRASS color names (see above).
-
-<p>
-Colors can also be specified by color numbers each in the range 0-255. The
-format of a category value color table specification using color numbers instead
-of color names is as follows:
-
-<div class="code"><pre>
-category_value red_number:green_number:blue_number
-category_value red_number:green_number:blue_number
-.. .. .. ..
-.. .. .. ..
-category_value red_number:green_number:blue_number
-end
-</pre></div>
-
-<p>
-Specifying a color table by "percent" values allows one to treat a color table
-as if it were numbered from 0 to 100. The format of a "percent" value color
-table specification is the same as for a category value color specification,
-except that the category values are replaced by "percent" values, each from
-0-100, in ascending order. The format is as follows:
-
-<div class="code"><pre>
-percent_value% color_name
-percent_value% color_name
-.. ..
-.. ..
-percent_value% color_name
-end
-</pre></div>
-
-<p>
-Using "percent" value color table specification rules, colors can also
-be specified by color numbers each in the range 0-255. The format of a
-percent value color table specification using color numbers instead of
-color names is as follows:
-
-<div class="code"><pre>
-percent_value% red_number:green_number:blue_number
-percent_value% red_number:green_number:blue_number
-.. .. .. ..
-.. .. .. ..
-percent_value% red_number:green_number:blue_number
-end
-</pre></div>
-
-<p>
-Note that you can also mix these <!--three-->two methods of color table
-specification; for example:
-
-<div class="code"><pre>
-0 black
-10% yellow
-78 blue<!--\n magenta
-purple
-brown-->
-100% 0:255:230
-end
-</pre></div>
-
-<p>
-To set the NULL (no data) color, use the "nv" parameter:
-
-<div class="code"><pre>
-0 black
-10% yellow
-nv white
-end
-</pre></div>
-
-<h2>EXAMPLES</h2>
-
-The below example shows how you can specify colors for a three category map,
-assigning red to category 1, green to category 2, and blue to category 3. Start
-by using a text editor to create the following rules specification file (save it
-with the name <i>rules.file</i>):
-
-<div class="code"><pre>
-1 red
-2 green
-3 blue
-end
-</pre></div>
-
-<p>
-The color table can then by assigned to map <i>threecats</i> by the following
-GRASS command:
-
-<div class="code"><pre>
-cat rules.file | r.colors -i map=threecats
-</pre></div>
-
-<p><br>
-To create a natural looking LUT for true map layer <i>elevation</i>, use the
-following rules specification file. It will assign light green shades to the
-lower elevations (first 20% of the LUT), and then darker greens (next 15%, and
-next 20%) and light browns (next 20%) for middle elevations, and darker browns
-(next 15%) for higher elevations, and finally yellow for the highest peaks (last
-10% of LUT).
-
-<div class="code"><pre>
-0% 0:230:0
-20% 0:160:0
-35% 50:130:0
-55% 120:100:30
-75% 120:130:40
-90% 170:160:50
-100% 255:255:100
-</pre></div>
-
-
-<h2>SEE ALSO</h2>
-
-<em>
-<a href="d.colors.html">d.colors</a>,
-<a href="d.colortable.html">d.colortable</a>,
-<a href="d.legend.html">d.legend</a>,
-<a href="r.support.html">r.support</a>
-</em>
-<p>
-<a href="http://colorbrewer.org">ColorBrewer</a> is an online tool designed to
-help people select good color schemes for maps and other graphics.
-
-
-<h2>AUTHORS</h2>
-Michael Shapiro and David Johnson
-
-<p>
-<i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.colors/r.colors.html (from rev 32770, grass/trunk/raster/r.colors/description.html)
===================================================================
--- grass/trunk/raster/r.colors/r.colors.html (rev 0)
+++ grass/trunk/raster/r.colors/r.colors.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,314 @@
+<h2>DESCRIPTION</h2>
+
+<i>r.colors</i> allows the user to create and/or modify the color table for a
+raster map layer. The map layer (specified on the command line by
+<b>map=</b><i>name</i>) must exist in the user's current mapset search path.
+The color table specified by <b>color=</b><i>type</i> must be one of the
+following:
+
+<pre>
+ color type description
+ aspect (aspect oriented grey colors)
+ aspectcolr (aspect oriented rainbow colors)
+ bcyr (blue through cyan through yellow to red)
+ bgyr (blue through green through yellow to red)
+ byg (blue through yellow to green colors)
+ byr (blue through yellow to red colors)
+ curvature (for terrain curvatures (from v.surf.rst and r.slope.aspect curvature colors))
+ differences (differences oriented colors)
+ elevation (maps percentage ranges of raster values to elevation color ramp)
+ etopo2 (rainbow color ramp for the ETOPO2 2-minute Worldwide Bathymetry/Topography dataset)
+ evi (enhanced vegetative index colors)
+ grey (grey scale)
+ grey1.0 (grey scale for raster values between 0.0-1.0)
+ grey255 (grey scale for raster values bewtween 0-255)
+ grey.eq (histogram-equalized grey scale)
+ grey.log (histogram logarithmic transformed grey scale)
+ gyr (green through yellow to red colors)
+ ndvi (Normalized Difference Vegetation Index colors)
+ population (color table covering human population classification breaks)
+ rainbow (rainbow color table)
+ ramp (color ramp)
+ random (random color table)
+ rules (create new color table based on user-specified rules)
+ ryb (red through yellow to blue colors)
+ ryg (red through yellow to green colors)
+ slope (r.slope.aspect-type slope colors for raster values 0-90)
+ srtm (color palette for Shuttle Radar Topography Mission elevation values)
+ terrain (global elevation color table covering -11000 to +8850m)
+ wave (color wave)
+</pre>
+
+<p>
+The <b>rast</b> option allows user to specify a raster map <i>name</i> from which
+to copy the color map.
+
+<p>
+Extra color tables (aspect, aspectcolr, bcyr, bgyr, byg, byr, curvature, differences,
+elevation, etopo2, evi, grey, grey1.0, grey255, gyr, ndvi, population, rainbow, ramp, ryb, ryg, slope, srtm, terrain, wave) are stored in $GISBASE/etc/colors/.
+User-defined color tables can also be stored in this directory for access from the <em>color</em> parameter.
+<p>
+The <b>-e</b> flag equalizes the original raster's color table. It can preclude
+the need for <em>grey.eq</em> rule, when used as
+<b>-e color=</b><em>grey</em>. Note however, that this will not yield a color
+table identical to <em>color=grey.eq</em>, because <em>grey.eq</em> scales
+the fraction by 256 to get a grey level, while <b>-e</b> uses it to interpolate
+the original colour table. If the original colour table is a 0-255 grey scale,
+<b>-e</b> is effectively scaling the fraction by 255. Different algorithms are
+used. <b>-e</b> is designed to work with any color table, both the floating
+point and the integer raster maps.
+
+<p>
+The <b>-g</b> flag divides the raster's grey value range into 100
+logarithmically equal steps (where "step" is a rule with the same grey level
+for the start and end points). It can preclude the need for <em>grey.log</em>
+rule, when used as <b>-g color=</b><em>grey</em>. Note however, that this
+will not yield a color table identical to <em>color=grey.log</em>. Different
+algorithms are used. Unlike <b>color=</b><em>grey.log</em>, <b>-g</b> is
+designed to work with both floating point and integer rasters, without
+performance issues with large datasets, of any original color table. Logarithmic
+scaling doesn't work on negative values. In the case when the value range
+includes zero, there's no realistic solution.
+
+<p>
+The <b>-e</b> and <b>-g</b> flags are not mutually exclusive.
+
+<p>
+If the user specifies the <b>-w</b> flag, the current color table file for
+the input map will not be overwritten. This means that the color table is
+created only if the <i>map</i> does not already have a color table. If this
+option is not specified, the color table will be created if one does not
+exist, or modified if it does.
+
+<p>
+If the user sets the <b>-q</b> flag, <i>r.colors</i> will run quietly,
+Without printing numerous messages on its progress to standard output.
+<p>Color table types <i>aspect, grey, grey.eq</i> (histogram-equalized grey
+scale), <i>byg</i> (blue-yellow-green), <i>byr</i> (blue-yellow-red),
+<i>gyr</i> (green-yellow-red), <i>rainbow, ramp, ryg</i> (red-yellow-green),
+<i>random</i>, and <i>wave</i> are pre-defined color tables that
+<i>r.colors</i> knows how to create without any further input.
+
+<p>
+In general, tables which associate colors with percentages (aspect, bcyr, byg,
+byr, elevation, grey, gyr, rainbow, ramp, ryb, ryg and wave) can be applied to
+any data, while those which use absolute values (aspectcolr, curvature, etopo2,
+evi, ndvi, population, slope, srtm, and terrain) only make sense for data with
+certain ranges.
+
+One can get a rough idea of the applicability of a colour table by reading the
+corresponding rules file ($GISBASE/etc/colors/<name>).
+For example the <em>slope</em> rule is defined as:
+
+<div class="code"><pre>
+0 255:255:255
+2 255:255:0
+5 0:255:0
+10 0:255 255
+15 0:0:255
+30 255:0:255
+50 255:0:0
+90 0:0:0
+</pre></div>
+
+<p>
+This is designed for the slope map generated by r.slope.aspect, where the value
+is a slope angle between 0 and 90 degrees.
+
+<p>
+Similarly, the <em>aspectcolr</em> rule:
+
+<div class="code"><pre>
+0 white
+1 yellow
+90 green
+180 cyan
+270 red
+360 yellow
+</pre></div>
+
+<p>
+is designed for the aspect maps produced by r.slope.aspect, where the value is a
+heading between 0 and 360 degrees.
+
+<p>
+The <i>rules</i> color table type will cause <i>r.colors</i> to read color
+table specifications from standard input (stdin) and will build the color table
+accordingly.
+
+<p>
+Using color table type <i>rules</i>, there are <!--three-->two ways to build a color
+table: <!--by color list,--> by category values and by "percent" values.
+
+<!-- HB: this causes an error in current code, maybe easy to enable functionality from old code??
+<p>
+Building a customized color table by color list is the simplest of the three
+rules methods: just list the colors you wish to appear in the color table in the
+order that you wish them to appear. Use the standard GRASS color names: white,
+black, red, green, blue, yellow, magenta, cyan, aqua, grey, gray, orange, brown,
+purple, violet, and indigo.
+
+<p>
+For example, to create a color table for the raster map layer <i>elevation</i>
+that assigns greens to low map category values, browns to the next larger
+map category values, and yellows to the still larger map category values,
+one would type:
+
+<div class="code"><pre>
+<b>r.colors map=</b><i>elevation</i> <b>color=</b><i>rules</i>
+green
+brown
+yellow
+end
+</pre></div>
+-->
+<p>
+To build a color table by category values' indices, the user should determine
+the range of category values in the raster map layer with which the color table
+will be used. Specific category values will then be associated with specific
+colors. Note that a color does not have to be assigned for every valid category
+value because <i>r.colors</i> will interpolate a color ramp to fill in where
+color specification rules have been left out. The format of such a specification
+is as follows:
+
+<div class="code"><pre>
+category_value color_name
+category_value color_name
+.. ..
+.. ..
+category_value color_name
+end
+</pre></div>
+
+<p>
+Each category value must be valid for the raster map layer, category values must
+be in ascending order and only use standard GRASS color names (see above).
+
+<p>
+Colors can also be specified by color numbers each in the range 0-255. The
+format of a category value color table specification using color numbers instead
+of color names is as follows:
+
+<div class="code"><pre>
+category_value red_number:green_number:blue_number
+category_value red_number:green_number:blue_number
+.. .. .. ..
+.. .. .. ..
+category_value red_number:green_number:blue_number
+end
+</pre></div>
+
+<p>
+Specifying a color table by "percent" values allows one to treat a color table
+as if it were numbered from 0 to 100. The format of a "percent" value color
+table specification is the same as for a category value color specification,
+except that the category values are replaced by "percent" values, each from
+0-100, in ascending order. The format is as follows:
+
+<div class="code"><pre>
+percent_value% color_name
+percent_value% color_name
+.. ..
+.. ..
+percent_value% color_name
+end
+</pre></div>
+
+<p>
+Using "percent" value color table specification rules, colors can also
+be specified by color numbers each in the range 0-255. The format of a
+percent value color table specification using color numbers instead of
+color names is as follows:
+
+<div class="code"><pre>
+percent_value% red_number:green_number:blue_number
+percent_value% red_number:green_number:blue_number
+.. .. .. ..
+.. .. .. ..
+percent_value% red_number:green_number:blue_number
+end
+</pre></div>
+
+<p>
+Note that you can also mix these <!--three-->two methods of color table
+specification; for example:
+
+<div class="code"><pre>
+0 black
+10% yellow
+78 blue<!--\n magenta
+purple
+brown-->
+100% 0:255:230
+end
+</pre></div>
+
+<p>
+To set the NULL (no data) color, use the "nv" parameter:
+
+<div class="code"><pre>
+0 black
+10% yellow
+nv white
+end
+</pre></div>
+
+<h2>EXAMPLES</h2>
+
+The below example shows how you can specify colors for a three category map,
+assigning red to category 1, green to category 2, and blue to category 3. Start
+by using a text editor to create the following rules specification file (save it
+with the name <i>rules.file</i>):
+
+<div class="code"><pre>
+1 red
+2 green
+3 blue
+end
+</pre></div>
+
+<p>
+The color table can then by assigned to map <i>threecats</i> by the following
+GRASS command:
+
+<div class="code"><pre>
+cat rules.file | r.colors -i map=threecats
+</pre></div>
+
+<p><br>
+To create a natural looking LUT for true map layer <i>elevation</i>, use the
+following rules specification file. It will assign light green shades to the
+lower elevations (first 20% of the LUT), and then darker greens (next 15%, and
+next 20%) and light browns (next 20%) for middle elevations, and darker browns
+(next 15%) for higher elevations, and finally yellow for the highest peaks (last
+10% of LUT).
+
+<div class="code"><pre>
+0% 0:230:0
+20% 0:160:0
+35% 50:130:0
+55% 120:100:30
+75% 120:130:40
+90% 170:160:50
+100% 255:255:100
+</pre></div>
+
+
+<h2>SEE ALSO</h2>
+
+<em>
+<a href="d.colors.html">d.colors</a>,
+<a href="d.colortable.html">d.colortable</a>,
+<a href="d.legend.html">d.legend</a>,
+<a href="r.support.html">r.support</a>
+</em>
+<p>
+<a href="http://colorbrewer.org">ColorBrewer</a> is an online tool designed to
+help people select good color schemes for maps and other graphics.
+
+
+<h2>AUTHORS</h2>
+Michael Shapiro and David Johnson
+
+<p>
+<i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.composite/description.html
===================================================================
--- grass/trunk/raster/r.composite/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.composite/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,45 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-This program combines three raster maps to form a
-composite RGB map. For each input map layer, the corresponding
-component from the map's color table is used (e.g. for
-the red map, the red component is used, and so on). In
-general, the maps should use a gray-scale color table.
-
-<h2>NOTES</h2>
-
-The default number of intensity levels for each component is 32,
-resulting in a total of 32768 possible colors (equivalent to 15 bits
-per pixel). If significantly more levels than this are used, not only
-will <em>r.composite</em> take longer to run, but displaying the
-resulting layer with <em><a href="d.rast.html">d.rast</a></em> will
-also be significantly slower.
-
-<p>
-Floyd-Steinberg dithering is optionally used with the <b>-d</b> flag.
-
-<h2>EXAMPLE</h2>
-Creating a composite RGB raster using 32 color levels per layer, with dithering:
-
-<div class="code"><pre>
-r.composite -d red=elevation.r green=elevation.g blue=elevation.b output=elev.composite
-</pre></div>
-
-<h2>SEE ALSO</h2>
-
-<em>
-<a href="d.rast.html">d.rast</a>,
-<a href="d.rgb.html">d.rgb</a>,
-<a href="r.blend.html">r.blend</a>,
-<a href="r.colors.html">r.colors</a>
-</em>
-<p>
-<em>
-<a href="http://en.wikipedia.org/wiki/Floyd-Steinberg_dithering">Wikipedia Entry: Floyd-Steinberg dithering</a>
-</em>
-
-<h2>AUTHOR</h2>
-
-Glynn Clements
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.composite/r.composite.html (from rev 32770, grass/trunk/raster/r.composite/description.html)
===================================================================
--- grass/trunk/raster/r.composite/r.composite.html (rev 0)
+++ grass/trunk/raster/r.composite/r.composite.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,45 @@
+<h2>DESCRIPTION</h2>
+
+This program combines three raster maps to form a
+composite RGB map. For each input map layer, the corresponding
+component from the map's color table is used (e.g. for
+the red map, the red component is used, and so on). In
+general, the maps should use a gray-scale color table.
+
+<h2>NOTES</h2>
+
+The default number of intensity levels for each component is 32,
+resulting in a total of 32768 possible colors (equivalent to 15 bits
+per pixel). If significantly more levels than this are used, not only
+will <em>r.composite</em> take longer to run, but displaying the
+resulting layer with <em><a href="d.rast.html">d.rast</a></em> will
+also be significantly slower.
+
+<p>
+Floyd-Steinberg dithering is optionally used with the <b>-d</b> flag.
+
+<h2>EXAMPLE</h2>
+Creating a composite RGB raster using 32 color levels per layer, with dithering:
+
+<div class="code"><pre>
+r.composite -d red=elevation.r green=elevation.g blue=elevation.b output=elev.composite
+</pre></div>
+
+<h2>SEE ALSO</h2>
+
+<em>
+<a href="d.rast.html">d.rast</a>,
+<a href="d.rgb.html">d.rgb</a>,
+<a href="r.blend.html">r.blend</a>,
+<a href="r.colors.html">r.colors</a>
+</em>
+<p>
+<em>
+<a href="http://en.wikipedia.org/wiki/Floyd-Steinberg_dithering">Wikipedia Entry: Floyd-Steinberg dithering</a>
+</em>
+
+<h2>AUTHOR</h2>
+
+Glynn Clements
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.compress/description.html
===================================================================
--- grass/trunk/raster/r.compress/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.compress/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,148 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-The GRASS program <em>r.compress</em> can be used to compress and decompress
-raster map layers.
-
-<p>
-
-During compression, this program reformats raster maps
-using a run-length-encoding (RLE) algorithm. Raster map
-layers which contain very little information (such as
-boundary, geology, soils and land use maps) can be greatly
-reduced in size. Some raster map layers are shrunk to
-roughly 1% of their original sizes. Raster map layers
-containing complex images such as elevation and photo or
-satellite images may increase slightly in size.
-<!-- The 'new compressed format' probably isn't new anymore as of 2008. - EP
-GRASS uses a new compressed format, -->
-All new raster maps are now automatically stored in compressed
-form (see FORMATS below). GRASS programs can read both compressed
-and regular (uncompressed) file formats. This allows the use
-of whichever raster data format consumes less space.
-
-<p>
-
-As an example, the Spearfish data base raster map layer
-<em>owner</em> was originally a size of 26600 bytes. After
-it was compressed, the raster map became only 1249 bytes
-(25351 bytes smaller).
-
-<p>
-
-Raster files may be decompressed to return them to their
-original format, using the <b>-u</b> flag of
-<em>r.compress</em>. If <em>r.compress</em> is asked to
-compress a raster map which is already compressed (or to
-decompress an already decompressed raster map), it simply informs
-the user the map is already (de)compressed and exits.
-
-<h2>NOTES</h2>
-
-<em>r.compress</em> can be run either non-interactively or
-interactively. In non-interactive use, the user must
-specify the name(s) of the raster map layer(s) to be
-compressed (or decompressed) on the command line, using the
-form <b>map=</b><em>name</em>[,<em>name</em>,...] (where
-each <em>name</em> is the name of a raster map layer to be
-compressed or decompressed). The default behavior is to
-compress the named map(s).
-
-<h3>FORMATS</h3>
-
-Conceptually, a raster data file consists of rows of cells,
-with each row containing the same number of cells. A cell
-consists of one or more bytes. The number of bytes per
-cell depends on the category values stored in the cell.
-Category values in the range 0-255 require 1 byte per cell,
-while category values in the range 256-65535 require 2
-bytes, and category values in the range above 65535 require
-3 (or more) bytes per cell.
-
-<p>
-
-The <b>decompressed</b> raster map format matches the
-conceptual format. For example, a raster map with 1 byte
-cells that is 100 rows with 200 cells per row, consists of
-20,000 bytes. Running the UNIX command <em>ls -l</em> on
-this file will show a size of 20,000. If the cells were 2
-byte cells, the file would require 40,000 bytes. The map
-layer category values start with the upper left corner cell
-followed by the other cells along the northern boundary.
-The byte following the last byte of that first row is the
-first cell of the second row of category values (moving
-from left to right). There are no end-of-row markers or
-other syncing codes in the raster map. A cell header file
-(<em>cellhd</em>) is used to define how this string of bytes
-is broken up into rows of category values.
-
-<p>
-
-The <b>compressed</b> format is not so simple, but is quite
-elegant in its design. It not only requires less disk space
-to store the raster data, but often can result in faster
-execution of graphic and analysis programs since there is
-less disk I/O. There are two compressed formats: the
-pre-version 3.0 format (which GRASS programs can read but
-no longer produce), and the version 3.0 format (which is
-automatically used when new raster map layers are
-created).
-
-<h4>PRE-3.0 FORMAT:</h4>
-
-First 3 bytes (chars) - These are a special code that identifies
-the raster data as compressed.
-
-<p>
-
-Address array (long) - array (size of the number of rows +
-1) of addresses pointing to the internal start of each row.
-Because each row may be a different size, this array is
-necessary to provide a mapping of the data.
-
-<p>
-
-Row by row, beginning at the northern edge of the data, a
-series of byte groups describes the data. The number of
-bytes in each group is the number of bytes per cell plus
-one. The first byte of each group gives a count (up to
-255) of the number of cells that contain the category
-values given by the remaining bytes of the group.
-
-<h4>POST-3.0 FORMAT:</h4>
-
-The 3 byte code is not used.
-Instead, a field in the cell header is used to indicate compressed format.
-
-<p>
-
-The address array is the same.
-
-<p>
-
-The RLE format is the same as the pre-3.0 RLE, except that
-each row of data is preceded by a single byte containing
-the number of bytes per cell for the row, and if
-run-length-encoding the row would not require less space
-than non-run-length-encoding, then the row is not encoded.
-
-<p>
-
-These improvements give better compression than the pre-3.0
-format in 99% of the raster data layers. The kinds of
-raster data layers which get bigger are those in which each
-row would be larger if compressed (e.g., imagery band
-files). But even in this case the raster data layer would
-only be larger by the size of the address array and the
-single byte preceding each row.
-
-<h2>SEE ALSO</h2>
-
-<em><a href="r.support.html">r.support</a></em>
-
-<h2>AUTHORS</h2>
-
-James Westervelt,<br>
-Michael Shapiro,<br>
-U.S. Army Construction Engineering Research Laboratory
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.compress/r.compress.html (from rev 32770, grass/trunk/raster/r.compress/description.html)
===================================================================
--- grass/trunk/raster/r.compress/r.compress.html (rev 0)
+++ grass/trunk/raster/r.compress/r.compress.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,148 @@
+<h2>DESCRIPTION</h2>
+
+The GRASS program <em>r.compress</em> can be used to compress and decompress
+raster map layers.
+
+<p>
+
+During compression, this program reformats raster maps
+using a run-length-encoding (RLE) algorithm. Raster map
+layers which contain very little information (such as
+boundary, geology, soils and land use maps) can be greatly
+reduced in size. Some raster map layers are shrunk to
+roughly 1% of their original sizes. Raster map layers
+containing complex images such as elevation and photo or
+satellite images may increase slightly in size.
+<!-- The 'new compressed format' probably isn't new anymore as of 2008. - EP
+GRASS uses a new compressed format, -->
+All new raster maps are now automatically stored in compressed
+form (see FORMATS below). GRASS programs can read both compressed
+and regular (uncompressed) file formats. This allows the use
+of whichever raster data format consumes less space.
+
+<p>
+
+As an example, the Spearfish data base raster map layer
+<em>owner</em> was originally a size of 26600 bytes. After
+it was compressed, the raster map became only 1249 bytes
+(25351 bytes smaller).
+
+<p>
+
+Raster files may be decompressed to return them to their
+original format, using the <b>-u</b> flag of
+<em>r.compress</em>. If <em>r.compress</em> is asked to
+compress a raster map which is already compressed (or to
+decompress an already decompressed raster map), it simply informs
+the user the map is already (de)compressed and exits.
+
+<h2>NOTES</h2>
+
+<em>r.compress</em> can be run either non-interactively or
+interactively. In non-interactive use, the user must
+specify the name(s) of the raster map layer(s) to be
+compressed (or decompressed) on the command line, using the
+form <b>map=</b><em>name</em>[,<em>name</em>,...] (where
+each <em>name</em> is the name of a raster map layer to be
+compressed or decompressed). The default behavior is to
+compress the named map(s).
+
+<h3>FORMATS</h3>
+
+Conceptually, a raster data file consists of rows of cells,
+with each row containing the same number of cells. A cell
+consists of one or more bytes. The number of bytes per
+cell depends on the category values stored in the cell.
+Category values in the range 0-255 require 1 byte per cell,
+while category values in the range 256-65535 require 2
+bytes, and category values in the range above 65535 require
+3 (or more) bytes per cell.
+
+<p>
+
+The <b>decompressed</b> raster map format matches the
+conceptual format. For example, a raster map with 1 byte
+cells that is 100 rows with 200 cells per row, consists of
+20,000 bytes. Running the UNIX command <em>ls -l</em> on
+this file will show a size of 20,000. If the cells were 2
+byte cells, the file would require 40,000 bytes. The map
+layer category values start with the upper left corner cell
+followed by the other cells along the northern boundary.
+The byte following the last byte of that first row is the
+first cell of the second row of category values (moving
+from left to right). There are no end-of-row markers or
+other syncing codes in the raster map. A cell header file
+(<em>cellhd</em>) is used to define how this string of bytes
+is broken up into rows of category values.
+
+<p>
+
+The <b>compressed</b> format is not so simple, but is quite
+elegant in its design. It not only requires less disk space
+to store the raster data, but often can result in faster
+execution of graphic and analysis programs since there is
+less disk I/O. There are two compressed formats: the
+pre-version 3.0 format (which GRASS programs can read but
+no longer produce), and the version 3.0 format (which is
+automatically used when new raster map layers are
+created).
+
+<h4>PRE-3.0 FORMAT:</h4>
+
+First 3 bytes (chars) - These are a special code that identifies
+the raster data as compressed.
+
+<p>
+
+Address array (long) - array (size of the number of rows +
+1) of addresses pointing to the internal start of each row.
+Because each row may be a different size, this array is
+necessary to provide a mapping of the data.
+
+<p>
+
+Row by row, beginning at the northern edge of the data, a
+series of byte groups describes the data. The number of
+bytes in each group is the number of bytes per cell plus
+one. The first byte of each group gives a count (up to
+255) of the number of cells that contain the category
+values given by the remaining bytes of the group.
+
+<h4>POST-3.0 FORMAT:</h4>
+
+The 3 byte code is not used.
+Instead, a field in the cell header is used to indicate compressed format.
+
+<p>
+
+The address array is the same.
+
+<p>
+
+The RLE format is the same as the pre-3.0 RLE, except that
+each row of data is preceded by a single byte containing
+the number of bytes per cell for the row, and if
+run-length-encoding the row would not require less space
+than non-run-length-encoding, then the row is not encoded.
+
+<p>
+
+These improvements give better compression than the pre-3.0
+format in 99% of the raster data layers. The kinds of
+raster data layers which get bigger are those in which each
+row would be larger if compressed (e.g., imagery band
+files). But even in this case the raster data layer would
+only be larger by the size of the address array and the
+single byte preceding each row.
+
+<h2>SEE ALSO</h2>
+
+<em><a href="r.support.html">r.support</a></em>
+
+<h2>AUTHORS</h2>
+
+James Westervelt,<br>
+Michael Shapiro,<br>
+U.S. Army Construction Engineering Research Laboratory
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.contour/description.html
===================================================================
--- grass/trunk/raster/r.contour/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.contour/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,36 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>r.contour</em> produces a GRASS binary vector map of specified contours from a GRASS raster map.
-
-Contours can be produced using a comma-separated list of values in <b>levels</b>, or at some regular increment using the <b>step</b> parameter, using <b>minlevel</b> and <b>maxlevel</b> as minimum and maximum contour values, respectively. If no <b>minlevel</b> or <b>maxlevel</b> is specified, the minimum and maximum cell values in the <b>input</b> raster map will be used.
-
-<h2>NOTES</h2>
-<em>r.contour</em> will either step through incremental contours or produce
-contours from a list of levels, not both. If both a list of levels and
-a step are specified, the list will be produced and the step will be ignored.
-
-<p>Zero is treated as a valid data value by <em>r.contour</em>.
-
-<p>If a contour level exactly matches a category value in the raster map,
-the contour line may backtrack on itself, causing illegal arcs to be produced
-in the output GRASS vector map.
-
-<p>The optional <b>cut</b> parameter allows the user to specify a minimum number of
-raster cells eligilble to be included in a contour line written to the <b>output</b>
-vector map. It acts like a filter, omitting spurs, single points, etc., making the output more generalized.
-
-<h2>EXAMPLE</h2>
-In the Spearfish location, produce a vector contour map from input raster <i>elevation.dem</i>
-with contour levels from 1000m to 2000m, 100m contour step, and a minimum of 200 input raster
-points contributing to the contour line:
-
-<div><pre class="code">
-r.contour input=elevation.dem output=elevation_dem_contours minlevel=1000 maxlevel=2000 step=100 cut=200
-</pre></div>
-
-<h2>AUTHORS</h2>
-Terry Baker, U.S. Army Construction Engineering Research Laboratory<br>
-3/2001: cut parameter and fixes by Andrea Aime (aaime at libero.it)
-
-<p><i>Last changed: $Date$</i>
-
Copied: grass/trunk/raster/r.contour/r.contour.html (from rev 32770, grass/trunk/raster/r.contour/description.html)
===================================================================
--- grass/trunk/raster/r.contour/r.contour.html (rev 0)
+++ grass/trunk/raster/r.contour/r.contour.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,36 @@
+<h2>DESCRIPTION</h2>
+
+<em>r.contour</em> produces a GRASS binary vector map of specified contours from a GRASS raster map.
+
+Contours can be produced using a comma-separated list of values in <b>levels</b>, or at some regular increment using the <b>step</b> parameter, using <b>minlevel</b> and <b>maxlevel</b> as minimum and maximum contour values, respectively. If no <b>minlevel</b> or <b>maxlevel</b> is specified, the minimum and maximum cell values in the <b>input</b> raster map will be used.
+
+<h2>NOTES</h2>
+<em>r.contour</em> will either step through incremental contours or produce
+contours from a list of levels, not both. If both a list of levels and
+a step are specified, the list will be produced and the step will be ignored.
+
+<p>Zero is treated as a valid data value by <em>r.contour</em>.
+
+<p>If a contour level exactly matches a category value in the raster map,
+the contour line may backtrack on itself, causing illegal arcs to be produced
+in the output GRASS vector map.
+
+<p>The optional <b>cut</b> parameter allows the user to specify a minimum number of
+raster cells eligilble to be included in a contour line written to the <b>output</b>
+vector map. It acts like a filter, omitting spurs, single points, etc., making the output more generalized.
+
+<h2>EXAMPLE</h2>
+In the Spearfish location, produce a vector contour map from input raster <i>elevation.dem</i>
+with contour levels from 1000m to 2000m, 100m contour step, and a minimum of 200 input raster
+points contributing to the contour line:
+
+<div><pre class="code">
+r.contour input=elevation.dem output=elevation_dem_contours minlevel=1000 maxlevel=2000 step=100 cut=200
+</pre></div>
+
+<h2>AUTHORS</h2>
+Terry Baker, U.S. Army Construction Engineering Research Laboratory<br>
+3/2001: cut parameter and fixes by Andrea Aime (aaime at libero.it)
+
+<p><i>Last changed: $Date$</i>
+
Deleted: grass/trunk/raster/r.cost/description.html
===================================================================
--- grass/trunk/raster/r.cost/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.cost/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,260 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-
-<p><em>r.cost</em> determines the cumulative cost of moving to each
-cell on a <em>cost surface</em> (the <b>input</b> raster map) from
-other user-specified cell(s) whose locations are specified by their
-geographic coordinate(s). Each cell in the original cost surface map
-will contain a category value which represents the cost of traversing
-that cell. <em>r.cost</em> will produce an <b>output</b> raster map in
-which each cell contains the lowest total cost of traversing the
-space between each cell and the user-specified points. (Diagonal
-costs are multiplied by a factor that depends on the dimensions of
-the cell.) This program uses the current geographic region settings.
-The <b>output</b> map will be of the same data format as the <b>input</b>
-map, integer or floating point.</p>
-
-<h2>OPTIONS</h2>
-
-The <b>input</b> <em>name</em> is the name of a raster map whose category values
-represent the surface cost. The <b>output</b> <em>name</em> is the name of the
-resultant raster map of cumulative cost.
-
-<p>
-<em>r.cost</em> can be run with three different methods of identifying the
-starting point(s). One or more points (geographic coordinate pairs) can be
-provided as specified <b>coordinate</b>s on the command line, from a vector
-points file, or from a raster map.
-All non-NULL cells are considered to be starting points.
-
-Each <em>x,y</em> <b>coordinate</b> pair gives the geographic location of a
-point from which the transportation cost should be figured. As many points as
-desired can be entered by the user. These starting points can also be read
-from a vector points file through the <b>start_sites</b> option or from a
-raster map through the <b>start_rast</b> option.
-<p>
-<em>r.cost</em> will stop cumulating costs when either <b>max_cost</b> is reached,
-or one of the stop points given with <b>stop_coordinates</b> is reached.
-Alternatively, the stop points can be read from a vector points file with the
-<b>stop_sites</b> option. During execution, once the cumulative cost to all
-stopping points has been determined, processing stops.
-
-Both sites read from a vector points file and those given on the command line
-will be processed.
-
-
-<p>
-The null cells in the <b>input</b> map can be assigned a (positive floating
-point) cost with the <b>null_cost</b> option.
-<br>
-When input map null cells are given a cost with the <b>null_cost</b>
-option, the corresponding cells in the output map are no longer null
-cells. By using the <b>-n</b> flag, the null cells of the input map are
-retained as null cells in the output map.</p>
-
-<p>
-As <em>r.cost</em> can run for a very long time, it can be useful to
-use the <b>-v</b> verbose flag to track progress.
-
-<p>
-The Knight's move (<b>-k</b> flag) may be used to improve the accuracy of
-the output. In the diagram below, the center location (<tt>O</tt>) represents a
-grid cell from which cumulative distances are calculated. Those
-neighbors marked with an <tt>X</tt> are always considered for cumulative cost
-updates. With the <b>-k</b> option, the neighbors marked with a <tt>K</tt> are
-also considered.
-</p>
-<div class="code"><pre>
- . . . . . . . . . . . . . . .
- . . . K . . K . . .
- . . . . . . . . . . . . . . .
- . . K . X . X . X . K . .
- . . . . . . . . . . . . . . .
- . . . X . O . X . . .
- . . . . . . . . . . . . . . .
- . . K . X . X . X . K . .
- . . . . . . . . . . . . . . .
- . . . K . . K . . .
- . . . . . . . . . . . . . . .
-</pre></div>
-<br>
-Knight's move example:
-<center>
-<img src=rcost_knightsmove.png border=1><br>
-<table border=0 width=590>
-<tr><td><center>
-<i>Flat cost surface without (left pane) and with the knight's move (right pane).
-The default is to grow the cost outwards in 8 directions.
-Using the knight's move grows it outwards in 16 directions.</i>
-</center></td></tr>
-</table>
-</center>
-
-
-<h2>NULL CELLS</h2>
-
-<p>By default null cells in the input raster map are excluded from
-the algorithm, and thus retained in the output map.
-<p>
-If one wants <b>r.cost</b> to transparently cross any region of null cells,
-the <b>null_cost</b>=<tt>0.0</tt> option should be used. Then null cells just
-propagate the adjacent costs. These cells can be retained as null cells in the
-output map by using the <b>-n</b> flag.
-
-<h2>NOTES</h2>
-
-<p>Sometimes, when the differences among integer cell category values in the
-<em>r.cost</em> cumulative cost surface output are small, this
-cumulative cost output cannot accurately be used as input to <em><a href="r.drain.html">r.drain</a></em>
-(<em><a href="r.drain.html">r.drain</a></em> will output bad
-results). This problem can be circumvented by making the differences
-between cell category values in the cumulative cost output bigger. It
-is recommended that, if the output from <em>r.cost</em> is to be used
-as input to <em><a href="r.drain.html">r.drain</a></em>, the user
-multiply the input cost surface map to <em>r.cost</em> by the value
-of the map's cell resolution, before running <em>r.cost</em>. This
-can be done using <em><a href="r.mapcalc.html">r.mapcalc</a></em>. The map
-resolution can be found using <em><a href="g.region.html">g.region</a></em>.
-This problem doesn't arise with floating point maps.
-
-
-<h4>Algorithm notes</h4>
-
-The fundamental approach to calculating minimum travel cost is as
-follows:<p> The user generates a raster map indicating the cost of
-traversing each cell in the north-south and east-west directions.
-This map, along with a set of starting points are submitted to
-<em>r.cost</em>. The starting points are put into a list cells from which
-costs to the adjacent cells are to be calculated. The cell on the
-list with the lowest cumulative cost is selected for computing costs to
-the neighboring cells. Costs are computed and those cells are put
-on the list and the originating cell is finalized. This process
-of selecting the lowest cumulative cost cell, computing costs to the
-neighbors, putting the neighbors on the list and removing the
-originating cell from the list continues until the list is empty.
-<p>
-The most time consuming aspect of this algorithm is the management of
-the list of cells for which cumulative costs have been at least
-initially computed. <em>r.cost</em> uses a binary tree with an linked list
-at each node in the tree for efficiently holding cells with identical
-cumulative costs.
-<p>
-<em>r.cost</em>, like most all GRASS raster programs, is also made to be run on
-maps larger that can fit in available computer memory. As the
-algorithm works through the dynamic list of cells it can move almost
-randomly around the entire area. <em>r.cost</em> divides the entire area
-into a number of pieces and swaps these pieces in and out of memory (to
-and from disk) as needed. This provides a virtual memory approach
-optimally designed for 2-D raster maps.
-The amount of map to hold in memory at one time can be controlled with the
-<b>percent_memory</b> option. For large maps this value will have to be set
-to a lower value.
-
-
-<h2>EXAMPLES</h2>
-
-<p>Consider the following example:
-</p>
-<div class="code"><pre>
- Input:
- COST SURFACE
- . . . . . . . . . . . . . . .
- . 2 . 2 . 1 . 1 . 5 . 5 . 5 .
- . . . . . . . . . . . . . . .
- . 2 . 2 . 8 . 8 . 5 . 2 . 1 .
- . . . . . . . . . . . . . . .
- . 7 . 1 . 1 . 8 . 2 . 2 . 2 .
- . . . . . . . . . . . . . . .
- . 8 . 7 . 8 . 8 . 8 . 8 . 5 .
- . . . . . . . . . . _____ . .
- . 8 . 8 . 1 . 1 . 5 | <b>3</b> | 9 .
- . . . . . . . . . . |___| . .
- . 8 . 1 . 1 . 2 . 5 . 3 . 9 .
- . . . . . . . . . . . . . . .
-
-
-Output (using -k): Output (not using -k):
- CUMULATIVE COST SURFACE CUMULATIVE COST SURFACE
- . . . . . . . . . . . . . . . . . . . <b>* * * * *</b> . . . . . .
- . 21. 21. 20. 19. 17. 15. 14. . 22. 21<b>* 21* 20*</b> 17. 15. 14.
- . . . . . . . . . . . . . . . . . . . <b>* * * * *</b> . . . . . .
- . 20. 19. 22. 19. 15. 12. 11. . 20. 19. 22<b>* 20*</b> 15. 12. 11.
- . . . . . . . . . . . . . . . . . . . . . <b>* * * * *</b> . . . .
- . 22. 18. 17. 17. 12. 11. 9. . 22. 18. 17<b>* 18* 13*</b> 11. 9.
- . . . . . . . . . . . . . . . . . . . . . <b>* * * * *</b> . . . .
- . 21. 14. 13. 12. 8. 6. 6. . 21. 14. 13. 12. 8. 6. 6.
- . . . . . . . . . . _____. . . . . . . . . . . . . . . . .
- . 16. 13. 8. 7. 4 | <b>0</b> | 6. . 16. 13. 8. 7 . 4. 0. 6.
- . . . . . . . . . . |___|. . . . . . . . . . . . . . . . .
- . 14. 9. 8. 9. 6. 3. 8. . 14. 9. 8. 9 . 6. 3. 8.
- . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
-</pre></div>
-
-<p>
-<!-- ??? are "starting" and "ending" swapped in the following text ??? -->
-The user-provided ending location in the above example is the boxed <b>3</b>
-in the above input map. The costs in the output map represent the total
-cost of moving from each box ("cell") to one or more (here,
-only one) starting location(s). Cells surrounded by asterisks are
-those that are different between operations using and not using the
-Knight's move (<b>-k</b>) option.
-
-<h4>Output analysis</h4>
-
-The output map can be viewed, for example, as an elevation model in which
-the starting location(s) is/are the lowest point(s). Outputs from <em>r.cost</em>
-can be used as inputs to <em><a href="r.drain.html">r.drain</a></em>, in order
-to trace the least-cost path given by this model between any given cell
-and the <em>r.cost</em> starting location(s). The two programs, when
-used together, generate least-cost paths or corridors between any two
-map locations (cells).
-
-<h4>Shortest distance surfaces</h4>
-The <em>r.cost</em> module allows for computing the shortest distance
-of each pixel from raster lines, such as determining the shortest distances
-of households to the nearby road. For this cost surfaces with cost value 1 are
-used. The calculation is done with <em>r.cost</em> as follows
-(example for Spearfish region):
-
-<div class="code"><pre>
- g.region rast=roads -p
- r.mapcalc "area.one=1"
- r.cost -k input=area.one output=distance start_rast=roads
- d.rast distance
- d.rast.num distance
-
- #transform to metric distance from cell distance using the raster resolution:
- r.mapcalc "dist_meters=distance * (ewres()+nsres())/2."
- d.rast dist_meters
-</pre></div>
-
-
-<h2>BUGS</h2>
-
-The percentage done calculation reported in verbose mode is often not linear
-and ends well before 100%. This does not affect output.
-
-
-<h2>SEE ALSO</h2>
-
-<em><a href="r.drain.html">r.drain</a></em>,
-<em><a href="r.walk.html">r.walk</a></em>,
-<em><a href="r.in.ascii.html">r.in.ascii</a></em>,
-<em><a href="r.mapcalc.html">r.mapcalc</a></em>,
-<em><a href="r.out.ascii.html">r.out.ascii</a></em>
-
-<h2>AUTHOR</h2>
-
-Antony Awaida,<br>
-Intelligent Engineering<br>
-Systems Laboratory,<br>
-M.I.T.<br>
-<br>
-James Westervelt,<br>
-U.S.Army Construction Engineering Research Laboratory
-
-<p>Updated for Grass 5<br>
-Pierre de Mouveaux (pmx at audiovu.com)
-</p>
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.cost/r.cost.html (from rev 32770, grass/trunk/raster/r.cost/description.html)
===================================================================
--- grass/trunk/raster/r.cost/r.cost.html (rev 0)
+++ grass/trunk/raster/r.cost/r.cost.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,260 @@
+<h2>DESCRIPTION</h2>
+
+
+<p><em>r.cost</em> determines the cumulative cost of moving to each
+cell on a <em>cost surface</em> (the <b>input</b> raster map) from
+other user-specified cell(s) whose locations are specified by their
+geographic coordinate(s). Each cell in the original cost surface map
+will contain a category value which represents the cost of traversing
+that cell. <em>r.cost</em> will produce an <b>output</b> raster map in
+which each cell contains the lowest total cost of traversing the
+space between each cell and the user-specified points. (Diagonal
+costs are multiplied by a factor that depends on the dimensions of
+the cell.) This program uses the current geographic region settings.
+The <b>output</b> map will be of the same data format as the <b>input</b>
+map, integer or floating point.</p>
+
+<h2>OPTIONS</h2>
+
+The <b>input</b> <em>name</em> is the name of a raster map whose category values
+represent the surface cost. The <b>output</b> <em>name</em> is the name of the
+resultant raster map of cumulative cost.
+
+<p>
+<em>r.cost</em> can be run with three different methods of identifying the
+starting point(s). One or more points (geographic coordinate pairs) can be
+provided as specified <b>coordinate</b>s on the command line, from a vector
+points file, or from a raster map.
+All non-NULL cells are considered to be starting points.
+
+Each <em>x,y</em> <b>coordinate</b> pair gives the geographic location of a
+point from which the transportation cost should be figured. As many points as
+desired can be entered by the user. These starting points can also be read
+from a vector points file through the <b>start_sites</b> option or from a
+raster map through the <b>start_rast</b> option.
+<p>
+<em>r.cost</em> will stop cumulating costs when either <b>max_cost</b> is reached,
+or one of the stop points given with <b>stop_coordinates</b> is reached.
+Alternatively, the stop points can be read from a vector points file with the
+<b>stop_sites</b> option. During execution, once the cumulative cost to all
+stopping points has been determined, processing stops.
+
+Both sites read from a vector points file and those given on the command line
+will be processed.
+
+
+<p>
+The null cells in the <b>input</b> map can be assigned a (positive floating
+point) cost with the <b>null_cost</b> option.
+<br>
+When input map null cells are given a cost with the <b>null_cost</b>
+option, the corresponding cells in the output map are no longer null
+cells. By using the <b>-n</b> flag, the null cells of the input map are
+retained as null cells in the output map.</p>
+
+<p>
+As <em>r.cost</em> can run for a very long time, it can be useful to
+use the <b>-v</b> verbose flag to track progress.
+
+<p>
+The Knight's move (<b>-k</b> flag) may be used to improve the accuracy of
+the output. In the diagram below, the center location (<tt>O</tt>) represents a
+grid cell from which cumulative distances are calculated. Those
+neighbors marked with an <tt>X</tt> are always considered for cumulative cost
+updates. With the <b>-k</b> option, the neighbors marked with a <tt>K</tt> are
+also considered.
+</p>
+<div class="code"><pre>
+ . . . . . . . . . . . . . . .
+ . . . K . . K . . .
+ . . . . . . . . . . . . . . .
+ . . K . X . X . X . K . .
+ . . . . . . . . . . . . . . .
+ . . . X . O . X . . .
+ . . . . . . . . . . . . . . .
+ . . K . X . X . X . K . .
+ . . . . . . . . . . . . . . .
+ . . . K . . K . . .
+ . . . . . . . . . . . . . . .
+</pre></div>
+<br>
+Knight's move example:
+<center>
+<img src=rcost_knightsmove.png border=1><br>
+<table border=0 width=590>
+<tr><td><center>
+<i>Flat cost surface without (left pane) and with the knight's move (right pane).
+The default is to grow the cost outwards in 8 directions.
+Using the knight's move grows it outwards in 16 directions.</i>
+</center></td></tr>
+</table>
+</center>
+
+
+<h2>NULL CELLS</h2>
+
+<p>By default null cells in the input raster map are excluded from
+the algorithm, and thus retained in the output map.
+<p>
+If one wants <b>r.cost</b> to transparently cross any region of null cells,
+the <b>null_cost</b>=<tt>0.0</tt> option should be used. Then null cells just
+propagate the adjacent costs. These cells can be retained as null cells in the
+output map by using the <b>-n</b> flag.
+
+<h2>NOTES</h2>
+
+<p>Sometimes, when the differences among integer cell category values in the
+<em>r.cost</em> cumulative cost surface output are small, this
+cumulative cost output cannot accurately be used as input to <em><a href="r.drain.html">r.drain</a></em>
+(<em><a href="r.drain.html">r.drain</a></em> will output bad
+results). This problem can be circumvented by making the differences
+between cell category values in the cumulative cost output bigger. It
+is recommended that, if the output from <em>r.cost</em> is to be used
+as input to <em><a href="r.drain.html">r.drain</a></em>, the user
+multiply the input cost surface map to <em>r.cost</em> by the value
+of the map's cell resolution, before running <em>r.cost</em>. This
+can be done using <em><a href="r.mapcalc.html">r.mapcalc</a></em>. The map
+resolution can be found using <em><a href="g.region.html">g.region</a></em>.
+This problem doesn't arise with floating point maps.
+
+
+<h4>Algorithm notes</h4>
+
+The fundamental approach to calculating minimum travel cost is as
+follows:<p> The user generates a raster map indicating the cost of
+traversing each cell in the north-south and east-west directions.
+This map, along with a set of starting points are submitted to
+<em>r.cost</em>. The starting points are put into a list cells from which
+costs to the adjacent cells are to be calculated. The cell on the
+list with the lowest cumulative cost is selected for computing costs to
+the neighboring cells. Costs are computed and those cells are put
+on the list and the originating cell is finalized. This process
+of selecting the lowest cumulative cost cell, computing costs to the
+neighbors, putting the neighbors on the list and removing the
+originating cell from the list continues until the list is empty.
+<p>
+The most time consuming aspect of this algorithm is the management of
+the list of cells for which cumulative costs have been at least
+initially computed. <em>r.cost</em> uses a binary tree with an linked list
+at each node in the tree for efficiently holding cells with identical
+cumulative costs.
+<p>
+<em>r.cost</em>, like most all GRASS raster programs, is also made to be run on
+maps larger that can fit in available computer memory. As the
+algorithm works through the dynamic list of cells it can move almost
+randomly around the entire area. <em>r.cost</em> divides the entire area
+into a number of pieces and swaps these pieces in and out of memory (to
+and from disk) as needed. This provides a virtual memory approach
+optimally designed for 2-D raster maps.
+The amount of map to hold in memory at one time can be controlled with the
+<b>percent_memory</b> option. For large maps this value will have to be set
+to a lower value.
+
+
+<h2>EXAMPLES</h2>
+
+<p>Consider the following example:
+</p>
+<div class="code"><pre>
+ Input:
+ COST SURFACE
+ . . . . . . . . . . . . . . .
+ . 2 . 2 . 1 . 1 . 5 . 5 . 5 .
+ . . . . . . . . . . . . . . .
+ . 2 . 2 . 8 . 8 . 5 . 2 . 1 .
+ . . . . . . . . . . . . . . .
+ . 7 . 1 . 1 . 8 . 2 . 2 . 2 .
+ . . . . . . . . . . . . . . .
+ . 8 . 7 . 8 . 8 . 8 . 8 . 5 .
+ . . . . . . . . . . _____ . .
+ . 8 . 8 . 1 . 1 . 5 | <b>3</b> | 9 .
+ . . . . . . . . . . |___| . .
+ . 8 . 1 . 1 . 2 . 5 . 3 . 9 .
+ . . . . . . . . . . . . . . .
+
+
+Output (using -k): Output (not using -k):
+ CUMULATIVE COST SURFACE CUMULATIVE COST SURFACE
+ . . . . . . . . . . . . . . . . . . . <b>* * * * *</b> . . . . . .
+ . 21. 21. 20. 19. 17. 15. 14. . 22. 21<b>* 21* 20*</b> 17. 15. 14.
+ . . . . . . . . . . . . . . . . . . . <b>* * * * *</b> . . . . . .
+ . 20. 19. 22. 19. 15. 12. 11. . 20. 19. 22<b>* 20*</b> 15. 12. 11.
+ . . . . . . . . . . . . . . . . . . . . . <b>* * * * *</b> . . . .
+ . 22. 18. 17. 17. 12. 11. 9. . 22. 18. 17<b>* 18* 13*</b> 11. 9.
+ . . . . . . . . . . . . . . . . . . . . . <b>* * * * *</b> . . . .
+ . 21. 14. 13. 12. 8. 6. 6. . 21. 14. 13. 12. 8. 6. 6.
+ . . . . . . . . . . _____. . . . . . . . . . . . . . . . .
+ . 16. 13. 8. 7. 4 | <b>0</b> | 6. . 16. 13. 8. 7 . 4. 0. 6.
+ . . . . . . . . . . |___|. . . . . . . . . . . . . . . . .
+ . 14. 9. 8. 9. 6. 3. 8. . 14. 9. 8. 9 . 6. 3. 8.
+ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
+</pre></div>
+
+<p>
+<!-- ??? are "starting" and "ending" swapped in the following text ??? -->
+The user-provided ending location in the above example is the boxed <b>3</b>
+in the above input map. The costs in the output map represent the total
+cost of moving from each box ("cell") to one or more (here,
+only one) starting location(s). Cells surrounded by asterisks are
+those that are different between operations using and not using the
+Knight's move (<b>-k</b>) option.
+
+<h4>Output analysis</h4>
+
+The output map can be viewed, for example, as an elevation model in which
+the starting location(s) is/are the lowest point(s). Outputs from <em>r.cost</em>
+can be used as inputs to <em><a href="r.drain.html">r.drain</a></em>, in order
+to trace the least-cost path given by this model between any given cell
+and the <em>r.cost</em> starting location(s). The two programs, when
+used together, generate least-cost paths or corridors between any two
+map locations (cells).
+
+<h4>Shortest distance surfaces</h4>
+The <em>r.cost</em> module allows for computing the shortest distance
+of each pixel from raster lines, such as determining the shortest distances
+of households to the nearby road. For this cost surfaces with cost value 1 are
+used. The calculation is done with <em>r.cost</em> as follows
+(example for Spearfish region):
+
+<div class="code"><pre>
+ g.region rast=roads -p
+ r.mapcalc "area.one=1"
+ r.cost -k input=area.one output=distance start_rast=roads
+ d.rast distance
+ d.rast.num distance
+
+ #transform to metric distance from cell distance using the raster resolution:
+ r.mapcalc "dist_meters=distance * (ewres()+nsres())/2."
+ d.rast dist_meters
+</pre></div>
+
+
+<h2>BUGS</h2>
+
+The percentage done calculation reported in verbose mode is often not linear
+and ends well before 100%. This does not affect output.
+
+
+<h2>SEE ALSO</h2>
+
+<em><a href="r.drain.html">r.drain</a></em>,
+<em><a href="r.walk.html">r.walk</a></em>,
+<em><a href="r.in.ascii.html">r.in.ascii</a></em>,
+<em><a href="r.mapcalc.html">r.mapcalc</a></em>,
+<em><a href="r.out.ascii.html">r.out.ascii</a></em>
+
+<h2>AUTHOR</h2>
+
+Antony Awaida,<br>
+Intelligent Engineering<br>
+Systems Laboratory,<br>
+M.I.T.<br>
+<br>
+James Westervelt,<br>
+U.S.Army Construction Engineering Research Laboratory
+
+<p>Updated for Grass 5<br>
+Pierre de Mouveaux (pmx at audiovu.com)
+</p>
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.covar/description.html
===================================================================
--- grass/trunk/raster/r.covar/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.covar/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,96 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-
-<em>r.covar</em> outputs a covariance/correlation matrix for user-specified
-raster map layer(s). The output can be printed, or saved by redirecting
-output into a file.
-
-<p>
-
-The output is an N x N symmetric covariance (correlation) matrix,
-where N is the number of raster map layers specified on the command line.
-
-
-<h2>NOTES</h2>
-
-This module can be used as the first step of a principle components
-transformation.
-The covariance matrix would be input into a system which determines
-eigen values and eigen vectors. An NxN covariance matrix would result in
-N real eigen values and N eigen vectors (each composed of N real numbers).
-
-<p>
-
-The module <em><a href="m.eigensystem.html">m.eigensystem</a></em> in
-src.contrib can be compiled and used to generate the eigen values and
-vectors.
-
-<h2>EXAMPLE</h2>
-
-For example,
-
-<dl>
-<dd>
-<b>r.covar</b> map=</b><em>layer.1</em>,<em>layer.2</em>,<em>layer.3</em>
-</dl>
-
-would produce a 3x3 matrix (values are example only):
-
-<pre>
- 1.000000 0.914922 0.889581
- 0.914922 1.000000 0.939452
- 0.889581 0.939452 1.000000
-</pre>
-
-In the above example, the eigen values and corresponding eigen vectors
-for the covariance matrix are:
-
-<pre>
-component eigen value eigen vector
- 1 1159.745202 < 0.691002 0.720528 0.480511 >
- 2 5.970541 < 0.711939 -0.635820 -0.070394 >
- 3 146.503197 < 0.226584 0.347470 -0.846873 >
-</pre>
-
-The component corresponding to each vector can be produced using
-<em><a href="r.mapcalc.html">r.mapcalc</a></em>
-as follows:
-
-<dl>
-<dd>
-<b>r.mapcalc</b> 'pc.1 = 0.691002*layer.1 + 0.720528*layer.2 + 0.480511*layer.3'
-<br>
-<b>r.mapcalc</b> 'pc.2 = 0.711939*layer.1 - 0.635820*layer.2 - 0.070394*layer.3'
-<br>
-<b>r.mapcalc</b> 'pc.3 = 0.226584*layer.1 + 0.347470*layer.2 - 0.846873*layer.3'
-</dl>
-
-Note that based on the relative sizes of the eigen values,
-<em>pc.1</em>
-will contain about 88% of the variance in the data set,
-<em>pc.2</em>
-will contain about 1% of the variance in the data set, and
-<em>pc.3</em>
-will contain about 11% of the variance in the data set.
-
-Also, note that the range of values produced in
-<em>pc.1</em>, <em>pc.2</em>, and <em>pc.3</em> will
-not (in general) be the same as those for
-<em>layer.1</em>, <em>layer.2</em>, and <em>layer.3</em>.
-It may be necessary to rescale
-<em>pc.1</em>, <em>pc.2</em> and <em>pc.3</em> to
-the desired range (e.g. 0-255).
-This can be done with <em><a href="r.rescale.html">r.rescale</a></em>.
-
-<h2>SEE ALSO</h2>
-
-<em><a href="i.pca.html">i.pca</a></em>,
-<em><a href="m.eigensystem.html">m.eigensystem</a></em>,
-<em><a href="r.mapcalc.html">r.mapcalc</a></em>,
-<em><a href="r.rescale.html">r.rescale</a></em>
-
-<h2>AUTHOR</h2>
-
-Michael Shapiro, U.S. Army Construction Engineering Research Laboratory
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.covar/r.covar.html (from rev 32770, grass/trunk/raster/r.covar/description.html)
===================================================================
--- grass/trunk/raster/r.covar/r.covar.html (rev 0)
+++ grass/trunk/raster/r.covar/r.covar.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,96 @@
+<h2>DESCRIPTION</h2>
+
+
+<em>r.covar</em> outputs a covariance/correlation matrix for user-specified
+raster map layer(s). The output can be printed, or saved by redirecting
+output into a file.
+
+<p>
+
+The output is an N x N symmetric covariance (correlation) matrix,
+where N is the number of raster map layers specified on the command line.
+
+
+<h2>NOTES</h2>
+
+This module can be used as the first step of a principle components
+transformation.
+The covariance matrix would be input into a system which determines
+eigen values and eigen vectors. An NxN covariance matrix would result in
+N real eigen values and N eigen vectors (each composed of N real numbers).
+
+<p>
+
+The module <em><a href="m.eigensystem.html">m.eigensystem</a></em> in
+src.contrib can be compiled and used to generate the eigen values and
+vectors.
+
+<h2>EXAMPLE</h2>
+
+For example,
+
+<dl>
+<dd>
+<b>r.covar</b> map=</b><em>layer.1</em>,<em>layer.2</em>,<em>layer.3</em>
+</dl>
+
+would produce a 3x3 matrix (values are example only):
+
+<pre>
+ 1.000000 0.914922 0.889581
+ 0.914922 1.000000 0.939452
+ 0.889581 0.939452 1.000000
+</pre>
+
+In the above example, the eigen values and corresponding eigen vectors
+for the covariance matrix are:
+
+<pre>
+component eigen value eigen vector
+ 1 1159.745202 < 0.691002 0.720528 0.480511 >
+ 2 5.970541 < 0.711939 -0.635820 -0.070394 >
+ 3 146.503197 < 0.226584 0.347470 -0.846873 >
+</pre>
+
+The component corresponding to each vector can be produced using
+<em><a href="r.mapcalc.html">r.mapcalc</a></em>
+as follows:
+
+<dl>
+<dd>
+<b>r.mapcalc</b> 'pc.1 = 0.691002*layer.1 + 0.720528*layer.2 + 0.480511*layer.3'
+<br>
+<b>r.mapcalc</b> 'pc.2 = 0.711939*layer.1 - 0.635820*layer.2 - 0.070394*layer.3'
+<br>
+<b>r.mapcalc</b> 'pc.3 = 0.226584*layer.1 + 0.347470*layer.2 - 0.846873*layer.3'
+</dl>
+
+Note that based on the relative sizes of the eigen values,
+<em>pc.1</em>
+will contain about 88% of the variance in the data set,
+<em>pc.2</em>
+will contain about 1% of the variance in the data set, and
+<em>pc.3</em>
+will contain about 11% of the variance in the data set.
+
+Also, note that the range of values produced in
+<em>pc.1</em>, <em>pc.2</em>, and <em>pc.3</em> will
+not (in general) be the same as those for
+<em>layer.1</em>, <em>layer.2</em>, and <em>layer.3</em>.
+It may be necessary to rescale
+<em>pc.1</em>, <em>pc.2</em> and <em>pc.3</em> to
+the desired range (e.g. 0-255).
+This can be done with <em><a href="r.rescale.html">r.rescale</a></em>.
+
+<h2>SEE ALSO</h2>
+
+<em><a href="i.pca.html">i.pca</a></em>,
+<em><a href="m.eigensystem.html">m.eigensystem</a></em>,
+<em><a href="r.mapcalc.html">r.mapcalc</a></em>,
+<em><a href="r.rescale.html">r.rescale</a></em>
+
+<h2>AUTHOR</h2>
+
+Michael Shapiro, U.S. Army Construction Engineering Research Laboratory
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.cross/description.html
===================================================================
--- grass/trunk/raster/r.cross/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.cross/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,109 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>r.cross</em> creates an <em>output</em> raster map layer representing
-all unique combinations of category values in the raster input layers
-(<b>input=</b><em>name,name,name</em>, ...). At least two, but not more than
-ten, <em>input</em> map layers must be specified. The user must also
-specify a name to be assigned to the <em>output</em> raster map layer
-created by <em>r.cross</em>.
-
-<h2>OPTIONS</h2>
-
-The program will be run non-interactively if the user specifies
-the names of between 2-10 raster map layers be used as <em>input</em>,
-and the name of a raster map layer to hold program <em>output</em>.
-
-<p>
-
-With the <b>-z</b> flag zero data values are not crossed.
-This means that if a zero category value occurs in any input data layer,
-the combination is assigned to category zero in the resulting map layer,
-even if other data layers contain non-zero data.
-In the example given above, use of the <b>-z</b> option
-would cause 3 categories to be generated instead of 5.
-
-<p>
-
-If the <b>-z</b> flag is not specified, then map layer combinations
-in which not all category values are zero will be assigned
-a unique category value in the resulting map layer.
-
-<p>
-
-Category values in the new <em>output</em> map layer will be the
-cross-product of the category values from these existing <em>input</em> map
-layers.
-
-<h2>EXAMPLE</h2>
-
-For example, suppose that, using two raster map layers,
-the following combinations occur:
-
-<div class="code"><pre>
- map1 map2
- ___________
- 0 1
- 0 2
- 1 1
- 1 2
- 2 4
-</pre></div>
-
-
-<em>r.cross</em> would produce a new raster map layer with 5 categories:
-
-<div class="code"><pre>
- map1 map2 output
- ____________________
- 0 1 1
- 0 2 2
- 1 1 3
- 1 2 4
- 2 4 5
-</pre></div>
-
-Note: The actual category value assigned to a particular combination
-in the <em>result</em> map layer is
-dependent on the order in which the combinations occur in the input map
-layer data and can be considered essentially random.
-The example given here is illustrative only.
-
-<h2>SUPPORT FILES</h2>
-
-The category file created for the <em>output</em> raster map
-layer describes the
-combinations of input map layer category values which generated
-each category.
-In the above example, the category labels would be:
-
-<div class="code"><pre>
- category category
- value label
- ______________________________
- 1 layer1(0) layer2(1)
- 2 layer1(0) layer2(2)
- 3 layer1(1) layer2(1)
- 4 layer1(1) layer2(2)
- 5 layer1(2) layer2(4)
-</pre></div>
-
-A random color table is also generated for the <em>output</em> map layer.
-
-<h2>NOTES</h2>
-
-When run non-interactively, <em>r.cross</em> will not protect existing
-files in the user's mapset. If the user specifies an <em>output</em>
-file name that already exists in his mapset, the existing file will
-be overwritten by the new <em>r.cross</em> output.
-
-<h2>SEE ALSO</h2>
-
-<em><a href="r.covar.html">r.covar</a></em>,
-<em><a href="r.stats.html">r.stats</a></em>
-
-<h2>AUTHOR</h2>
-
-Michael Shapiro, U.S. Army Construction Engineering Research Laboratory
-
-<p>
-<i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.cross/r.cross.html (from rev 32770, grass/trunk/raster/r.cross/description.html)
===================================================================
--- grass/trunk/raster/r.cross/r.cross.html (rev 0)
+++ grass/trunk/raster/r.cross/r.cross.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,109 @@
+<h2>DESCRIPTION</h2>
+
+<em>r.cross</em> creates an <em>output</em> raster map layer representing
+all unique combinations of category values in the raster input layers
+(<b>input=</b><em>name,name,name</em>, ...). At least two, but not more than
+ten, <em>input</em> map layers must be specified. The user must also
+specify a name to be assigned to the <em>output</em> raster map layer
+created by <em>r.cross</em>.
+
+<h2>OPTIONS</h2>
+
+The program will be run non-interactively if the user specifies
+the names of between 2-10 raster map layers be used as <em>input</em>,
+and the name of a raster map layer to hold program <em>output</em>.
+
+<p>
+
+With the <b>-z</b> flag zero data values are not crossed.
+This means that if a zero category value occurs in any input data layer,
+the combination is assigned to category zero in the resulting map layer,
+even if other data layers contain non-zero data.
+In the example given above, use of the <b>-z</b> option
+would cause 3 categories to be generated instead of 5.
+
+<p>
+
+If the <b>-z</b> flag is not specified, then map layer combinations
+in which not all category values are zero will be assigned
+a unique category value in the resulting map layer.
+
+<p>
+
+Category values in the new <em>output</em> map layer will be the
+cross-product of the category values from these existing <em>input</em> map
+layers.
+
+<h2>EXAMPLE</h2>
+
+For example, suppose that, using two raster map layers,
+the following combinations occur:
+
+<div class="code"><pre>
+ map1 map2
+ ___________
+ 0 1
+ 0 2
+ 1 1
+ 1 2
+ 2 4
+</pre></div>
+
+
+<em>r.cross</em> would produce a new raster map layer with 5 categories:
+
+<div class="code"><pre>
+ map1 map2 output
+ ____________________
+ 0 1 1
+ 0 2 2
+ 1 1 3
+ 1 2 4
+ 2 4 5
+</pre></div>
+
+Note: The actual category value assigned to a particular combination
+in the <em>result</em> map layer is
+dependent on the order in which the combinations occur in the input map
+layer data and can be considered essentially random.
+The example given here is illustrative only.
+
+<h2>SUPPORT FILES</h2>
+
+The category file created for the <em>output</em> raster map
+layer describes the
+combinations of input map layer category values which generated
+each category.
+In the above example, the category labels would be:
+
+<div class="code"><pre>
+ category category
+ value label
+ ______________________________
+ 1 layer1(0) layer2(1)
+ 2 layer1(0) layer2(2)
+ 3 layer1(1) layer2(1)
+ 4 layer1(1) layer2(2)
+ 5 layer1(2) layer2(4)
+</pre></div>
+
+A random color table is also generated for the <em>output</em> map layer.
+
+<h2>NOTES</h2>
+
+When run non-interactively, <em>r.cross</em> will not protect existing
+files in the user's mapset. If the user specifies an <em>output</em>
+file name that already exists in his mapset, the existing file will
+be overwritten by the new <em>r.cross</em> output.
+
+<h2>SEE ALSO</h2>
+
+<em><a href="r.covar.html">r.covar</a></em>,
+<em><a href="r.stats.html">r.stats</a></em>
+
+<h2>AUTHOR</h2>
+
+Michael Shapiro, U.S. Army Construction Engineering Research Laboratory
+
+<p>
+<i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.describe/description.html
===================================================================
--- grass/trunk/raster/r.describe/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.describe/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,109 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em><b>r.describe</b></em> prints a terse listing of category values found in
-a user-specified raster map layer.
-
-<p>
-
-<em><b>r.describe</b></em> ignores the current geographic region and mask, and
-reads the full extent of the input raster map. This functionality is useful if the
-user intends to <em>reclassify</em> or <em>rescale</em> the data,
-since these functions (<em><a href="r.reclass.html">r.reclass</a></em> and
-<em><a href="r.rescale.html">r.rescale</a></em>)
-also ignore the current <em>geographic region</em>
-and <em>mask</em>.
-
-<p>
-The <em><b>nv</b></em> parameter sets the string to be used to represent <tt>NULL</tt>
-values in the module output; the default is '*'.
-
-<p>
-The <em><b>nsteps</b></em> parameter sets the number of quantisation steps to divide into
-the input raster map.
-
-<h2>NOTES</h2>
-
-<h3>FLAGS</h3>
-
-If the user selects the <b>-r</b> flag, a range of category values found in
-the raster map layer will be printed. The range is divided into three groups:
-negative, positive, and zero. If negative values occur, the minimum and maximum
-negative values will be printed. If positive values occur, the minimum and maximum
-positive values will be printed. If zero occurs, this will be indicated. The range
-report will generally run faster than the full list (the default output).
-
-<p>
-
-The <b>-d</b> flag can be used to force <em>r.describe</em> to respect the current region
-extents when repoting raster map categories. The default behavior is to read the full
-extent of the input raster map.
-
-<p>
-If the <b>-1</b> flag is specified, the output appears with one category value/range per line.
-
-<p>
-The <b>-n</b> flag suppresses the reporting of <tt>NULL</tt> values.
-
-<h2>EXAMPLES</h2>
-
-The following examples are from the Spearfish60 sample Location:
-
-<p>
-
-# Print the full list of raster map categories:
-<div class="code"><pre>
-r.describe landcover.30m
-* 11 21-23 31 32 41-43 51 71 81-83 85 91 92
-</pre></div>
-<p>
-
-# Print the raster range only:
-<div class="code"><pre>
-r.describe -r landcover.30m
-11 thru 92
-*
-</pre></div>
-
-# Print raster map category range, suppressing nulls:
-<div class="code"><pre>
-r.describe -n landcover.30m
-11 21-23 31 32 41-43 51 71 81-83 85 91 92
-</pre></div>
-<p>
-
-# Print raster map categories, one category per line:
-<div class="code"><pre>
-r.describe -1 geology
-
-*
-1
-2
-3
-4
-5
-6
-7
-8
-9
-</pre></div>
-<p>
-
-<h2>SEE ALSO</h2>
-
-<em>
-<a href="g.region.html">g.region</a>,
-<a href="r.mask.html">r.mask</a>,
-<a href="r.reclass.html">r.reclass</a>,
-<a href="r.report.html">r.report</a>,
-<a href="r.rescale.html">r.rescale</a>,
-<a href="r.stats.html">r.stats</a>,
-<a href="r.univar.html">r.univar</a>
-
-</em>
-
-<h2>AUTHOR</h2>
-
-Michael Shapiro, U.S. Army Construction Engineering Research Laboratory
-
-<p>
-<i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.describe/r.describe.html (from rev 32770, grass/trunk/raster/r.describe/description.html)
===================================================================
--- grass/trunk/raster/r.describe/r.describe.html (rev 0)
+++ grass/trunk/raster/r.describe/r.describe.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,109 @@
+<h2>DESCRIPTION</h2>
+
+<em><b>r.describe</b></em> prints a terse listing of category values found in
+a user-specified raster map layer.
+
+<p>
+
+<em><b>r.describe</b></em> ignores the current geographic region and mask, and
+reads the full extent of the input raster map. This functionality is useful if the
+user intends to <em>reclassify</em> or <em>rescale</em> the data,
+since these functions (<em><a href="r.reclass.html">r.reclass</a></em> and
+<em><a href="r.rescale.html">r.rescale</a></em>)
+also ignore the current <em>geographic region</em>
+and <em>mask</em>.
+
+<p>
+The <em><b>nv</b></em> parameter sets the string to be used to represent <tt>NULL</tt>
+values in the module output; the default is '*'.
+
+<p>
+The <em><b>nsteps</b></em> parameter sets the number of quantisation steps to divide into
+the input raster map.
+
+<h2>NOTES</h2>
+
+<h3>FLAGS</h3>
+
+If the user selects the <b>-r</b> flag, a range of category values found in
+the raster map layer will be printed. The range is divided into three groups:
+negative, positive, and zero. If negative values occur, the minimum and maximum
+negative values will be printed. If positive values occur, the minimum and maximum
+positive values will be printed. If zero occurs, this will be indicated. The range
+report will generally run faster than the full list (the default output).
+
+<p>
+
+The <b>-d</b> flag can be used to force <em>r.describe</em> to respect the current region
+extents when repoting raster map categories. The default behavior is to read the full
+extent of the input raster map.
+
+<p>
+If the <b>-1</b> flag is specified, the output appears with one category value/range per line.
+
+<p>
+The <b>-n</b> flag suppresses the reporting of <tt>NULL</tt> values.
+
+<h2>EXAMPLES</h2>
+
+The following examples are from the Spearfish60 sample Location:
+
+<p>
+
+# Print the full list of raster map categories:
+<div class="code"><pre>
+r.describe landcover.30m
+* 11 21-23 31 32 41-43 51 71 81-83 85 91 92
+</pre></div>
+<p>
+
+# Print the raster range only:
+<div class="code"><pre>
+r.describe -r landcover.30m
+11 thru 92
+*
+</pre></div>
+
+# Print raster map category range, suppressing nulls:
+<div class="code"><pre>
+r.describe -n landcover.30m
+11 21-23 31 32 41-43 51 71 81-83 85 91 92
+</pre></div>
+<p>
+
+# Print raster map categories, one category per line:
+<div class="code"><pre>
+r.describe -1 geology
+
+*
+1
+2
+3
+4
+5
+6
+7
+8
+9
+</pre></div>
+<p>
+
+<h2>SEE ALSO</h2>
+
+<em>
+<a href="g.region.html">g.region</a>,
+<a href="r.mask.html">r.mask</a>,
+<a href="r.reclass.html">r.reclass</a>,
+<a href="r.report.html">r.report</a>,
+<a href="r.rescale.html">r.rescale</a>,
+<a href="r.stats.html">r.stats</a>,
+<a href="r.univar.html">r.univar</a>
+
+</em>
+
+<h2>AUTHOR</h2>
+
+Michael Shapiro, U.S. Army Construction Engineering Research Laboratory
+
+<p>
+<i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.digit/description.html
===================================================================
--- grass/trunk/raster/r.digit/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.digit/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,78 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-The GRASS tool <em>r.digit</em> provides the user with a
-way to draw lines, areas, and circles on a monitor screen,
-and to save these features in a raster map. Lines, areas,
-and circles are to be drawn using a pointing device
-(mouse). A mouse button menu indicates the consequences of
-pressing each mouse button. The user is requested to enter
-the category number associated with the line, area, or
-circle subsequently drawn by the user. Lines, areas, and
-circles are defined by the series of points marked by the
-user inside the map window. <em>r.digit</em> will close
-areas when the user has not. By drawing a series of such
-features, the user can repair maps, identify areas of
-interest, or simply draw graphics for advertisement. When
-drawing is completed, a raster map based on the user's
-instructions is generated. It is available for use as a
-mask, in analyses, and for display.
-
-<p>
-The <b>bgcmd</b> option is intended to be used with display (d.*) commands.
-If several display commands are to be used to render the background
-they should be separated with the semi-colon ';' character.
-When run from the command line, these display commands will generally
-need to be "quoted" as they will contain spaces (see examples).
-<p>
-Digitizing is done in a "polygon" method. Each area is
-circumscribed completely. Two or more overlapping areas and/or lines
-might define a single part of a map. Each part of the map,
-however, is assigned only the LAST area or line which
-covered it.
-
-<h3>THE PROCESS:</h3>
-
-<h4>Start a monitor and display a raster to help setup and zoom to area of interest</h4>
-<div class="code"><pre>
-d.mon x0
-</pre></div>
-<p>
-
-<h4>Digitizing an area based on a existing map; creating a new raster map</h4>
-<div class="code"><pre>
-r.digit out=name_of_new_raster_map bgcmd="d.rast map=name_of_raster"
-</pre></div>
-
-<ol>
-
-<li>Choose to define an area or line, exit, or quit.
-If you choose to finish (<tt>exit</tt>) a new map is then created.
-If you quit, the session exits with nothing created.
-
-<li>If you choose to make an area or line you must identify
-the category number for that area or line.
-
-<li>Using the mouse trace the line or circumscribe the area;
-or, finish (go to Step 1).
-
-</ol>
-
-<h2>SEE ALSO</h2>
-
-
-<em><a href="v.digit.html">v.digit</a></em>,
-<em><a href="d.graph.html">d.graph</a></em>,
-<em><a href="d.linegraph.html">d.linegraph</a></em>,
-<em><a href="g.region.html">g.region</a></em>,
-<em><a href="r.in.poly.html">r.in.poly</a></em>,
-<em><a href="r.mapcalc.html">r.mapcalc</a></em>,
-<em><a href="r.to.vect.html">r.to.vect</a></em>,
-<em><a href="v.in.ascii.html">v.in.ascii</a></em>
-
-
-<h2>AUTHOR</h2>
-
-Michael Shapiro, U.S.Army Construction Engineering
-Research Laboratory
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.digit/r.digit.html (from rev 32770, grass/trunk/raster/r.digit/description.html)
===================================================================
--- grass/trunk/raster/r.digit/r.digit.html (rev 0)
+++ grass/trunk/raster/r.digit/r.digit.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,78 @@
+<h2>DESCRIPTION</h2>
+
+The GRASS tool <em>r.digit</em> provides the user with a
+way to draw lines, areas, and circles on a monitor screen,
+and to save these features in a raster map. Lines, areas,
+and circles are to be drawn using a pointing device
+(mouse). A mouse button menu indicates the consequences of
+pressing each mouse button. The user is requested to enter
+the category number associated with the line, area, or
+circle subsequently drawn by the user. Lines, areas, and
+circles are defined by the series of points marked by the
+user inside the map window. <em>r.digit</em> will close
+areas when the user has not. By drawing a series of such
+features, the user can repair maps, identify areas of
+interest, or simply draw graphics for advertisement. When
+drawing is completed, a raster map based on the user's
+instructions is generated. It is available for use as a
+mask, in analyses, and for display.
+
+<p>
+The <b>bgcmd</b> option is intended to be used with display (d.*) commands.
+If several display commands are to be used to render the background
+they should be separated with the semi-colon ';' character.
+When run from the command line, these display commands will generally
+need to be "quoted" as they will contain spaces (see examples).
+<p>
+Digitizing is done in a "polygon" method. Each area is
+circumscribed completely. Two or more overlapping areas and/or lines
+might define a single part of a map. Each part of the map,
+however, is assigned only the LAST area or line which
+covered it.
+
+<h3>THE PROCESS:</h3>
+
+<h4>Start a monitor and display a raster to help setup and zoom to area of interest</h4>
+<div class="code"><pre>
+d.mon x0
+</pre></div>
+<p>
+
+<h4>Digitizing an area based on a existing map; creating a new raster map</h4>
+<div class="code"><pre>
+r.digit out=name_of_new_raster_map bgcmd="d.rast map=name_of_raster"
+</pre></div>
+
+<ol>
+
+<li>Choose to define an area or line, exit, or quit.
+If you choose to finish (<tt>exit</tt>) a new map is then created.
+If you quit, the session exits with nothing created.
+
+<li>If you choose to make an area or line you must identify
+the category number for that area or line.
+
+<li>Using the mouse trace the line or circumscribe the area;
+or, finish (go to Step 1).
+
+</ol>
+
+<h2>SEE ALSO</h2>
+
+
+<em><a href="v.digit.html">v.digit</a></em>,
+<em><a href="d.graph.html">d.graph</a></em>,
+<em><a href="d.linegraph.html">d.linegraph</a></em>,
+<em><a href="g.region.html">g.region</a></em>,
+<em><a href="r.in.poly.html">r.in.poly</a></em>,
+<em><a href="r.mapcalc.html">r.mapcalc</a></em>,
+<em><a href="r.to.vect.html">r.to.vect</a></em>,
+<em><a href="v.in.ascii.html">v.in.ascii</a></em>
+
+
+<h2>AUTHOR</h2>
+
+Michael Shapiro, U.S.Army Construction Engineering
+Research Laboratory
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.distance/description.html
===================================================================
--- grass/trunk/raster/r.distance/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.distance/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,67 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>r.distance</em> locates the closest points between "objects" in two raster maps. An
-"object" is defined as all the grid cells that have the same category
-number, and closest means having the shortest "straight-line" distance.
-The cell centers are considered for the distance calculation (two
-adjacent grid cells have the distance between their cell centers).
-<p>
-
-The output is an ascii list, one line per pair of objects, in the following form:
-<div class="code"><pre>
-cat1:cat2:distance:east1:north1:east2:north2
-</pre></div>
-
-<dl>
-<dt><b>cat1</b>
-<dd>Category number from map1
-
-<dt><b>cat2</b>
-<dd>Category number from map2
-
-<dt><b>distance</b>
-<dd>The distance in meters between "cat1" and "cat2"
-
-<dt><b>east1,north1</b>
-<dd>The coordinates of the grid cell "cat1" which is closest to "cat2"
-
-<dt><b>east2,north2</b>
-<dd>The coordinates of the grid cell "cat2" which is closest to "cat1"
-</dl>
-
-<h3>Flags</h3>
-<b>-l</b>
-The -l flag outputs the category labels of the matched raster objects at the
-beginning of the line, if they exist.
-<p>
-<b>-o</b>
-The -o flag reports zero distance if the input rasters are overlapping.
-<p>
-
-<h2>NOTES</h2>
-The output format lends itself to filtering. For example, to "see" lines
-connecting each of the category pairs in two maps, filter the output using
-awk and then into <em>d.graph</em>:
-<p>
-
-<div class="code"><pre>r.distance maps=map1,map2 | \
-awk -F: '{print "move",$4,$5,"\ndraw",$6,$7}' | d.graph -m</pre></div>
-
-<p>
-To create a vector map of all the "map1" coordinates, filter the output into
-awk and then into <em>v.in.ascii</em>:
-<p>
-
-<div class="code"><pre>r.distance maps=map1,map2 | \
-<br>awk -F: '{print $4,$5}' | v.in.ascii format=point output=name fs=space</pre></div>
-
-<h2>SEE ALSO</h2>
-<em><a href="r.buffer.html">r.buffer</a></em>,
-<em><a href="r.cost.html">r.cost</a></em>,
-<em><a href="r.drain.html">r.drain</a></em>,
-<em><a href="v.distance.html">v.distance</a></em>
-
-<h2>AUTHOR</h2>
-Michael Shapiro, U.S. Army Construction Engineering Research Laboratory
-
-<p><i>Last changed: $Date$</i></p>
Copied: grass/trunk/raster/r.distance/r.distance.html (from rev 32770, grass/trunk/raster/r.distance/description.html)
===================================================================
--- grass/trunk/raster/r.distance/r.distance.html (rev 0)
+++ grass/trunk/raster/r.distance/r.distance.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,67 @@
+<h2>DESCRIPTION</h2>
+
+<em>r.distance</em> locates the closest points between "objects" in two raster maps. An
+"object" is defined as all the grid cells that have the same category
+number, and closest means having the shortest "straight-line" distance.
+The cell centers are considered for the distance calculation (two
+adjacent grid cells have the distance between their cell centers).
+<p>
+
+The output is an ascii list, one line per pair of objects, in the following form:
+<div class="code"><pre>
+cat1:cat2:distance:east1:north1:east2:north2
+</pre></div>
+
+<dl>
+<dt><b>cat1</b>
+<dd>Category number from map1
+
+<dt><b>cat2</b>
+<dd>Category number from map2
+
+<dt><b>distance</b>
+<dd>The distance in meters between "cat1" and "cat2"
+
+<dt><b>east1,north1</b>
+<dd>The coordinates of the grid cell "cat1" which is closest to "cat2"
+
+<dt><b>east2,north2</b>
+<dd>The coordinates of the grid cell "cat2" which is closest to "cat1"
+</dl>
+
+<h3>Flags</h3>
+<b>-l</b>
+The -l flag outputs the category labels of the matched raster objects at the
+beginning of the line, if they exist.
+<p>
+<b>-o</b>
+The -o flag reports zero distance if the input rasters are overlapping.
+<p>
+
+<h2>NOTES</h2>
+The output format lends itself to filtering. For example, to "see" lines
+connecting each of the category pairs in two maps, filter the output using
+awk and then into <em>d.graph</em>:
+<p>
+
+<div class="code"><pre>r.distance maps=map1,map2 | \
+awk -F: '{print "move",$4,$5,"\ndraw",$6,$7}' | d.graph -m</pre></div>
+
+<p>
+To create a vector map of all the "map1" coordinates, filter the output into
+awk and then into <em>v.in.ascii</em>:
+<p>
+
+<div class="code"><pre>r.distance maps=map1,map2 | \
+<br>awk -F: '{print $4,$5}' | v.in.ascii format=point output=name fs=space</pre></div>
+
+<h2>SEE ALSO</h2>
+<em><a href="r.buffer.html">r.buffer</a></em>,
+<em><a href="r.cost.html">r.cost</a></em>,
+<em><a href="r.drain.html">r.drain</a></em>,
+<em><a href="v.distance.html">v.distance</a></em>
+
+<h2>AUTHOR</h2>
+Michael Shapiro, U.S. Army Construction Engineering Research Laboratory
+
+<p><i>Last changed: $Date$</i></p>
Deleted: grass/trunk/raster/r.drain/description.html
===================================================================
--- grass/trunk/raster/r.drain/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.drain/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,194 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-
-<em>r.drain</em> traces a flow through a least-cost path in an elevation
-model. The <b>input</b> elevation surface (a raster map layer) might
-be a cumulative cost map generated by the
-<em><a href="r.cost.html">r.cost</a></em> program.
-
-The <b>output</b> result (also a raster map layer) will show one or more
-least-cost paths between each user-provided location(s) and the minima
-(low category values) in the <b>input</b> map. By default, the <b>output</b>
-will be an integer CELL map with <tt>1</tt> along the least cost path,
-and null cells elsewhere.
-
-<p>
-With the <b>-c</b> (<em>copy</em>) flag, the input map cell values are
-copied verbatim along the path. With the <b>-a</b> (<em>accumulate</em>)
-flag, the accumulated cell value from the starting point up to the current
-cell is written on output. With either the <b>-c</b> or the <b>-a</b> flags, the
-<b>output</b> map is created with the same cell type as the <b>input</b> map (integer,
-float or double).
-With the <b>-n</b> (<em>number</em>) flag, the cells are numbered consecutively from the
-starting point to the final point.
-The <b>-c</b>, <b>-a</b>, and <b>-n</b> flags are mutually incompatible.
-
-<p>
-The path is calculated by choosing the steeper "slope" between adjacent
-cells. The slope calculation accurately acounts for the variable scale in
-lat-lon projections.
-
-<p>
-The <b>coordinate</b> parameter consists of map E and N grid coordinates of
-a starting point. Each x,y pair is the easting and northing (respectively) of
-a starting point from which a least-cost corridor will be developed.
-The <b>vector_points</b> parameter can take multiple vector maps containing
-additional starting points.
-Up to 1024 starting points can be input from a combination of the
-<b>coordinate</b> and <b>vector_points</b> parameters.
-
-<h2>NOTES</h2>
-
-<em>r.drain</em> currently finds only the lowest point
-(the cell having the smallest category value) in the
-input file that can be reached through directly adjacent cells
-that are less than or equal in value to the cell reached immediately
-prior to it; therefore, it will not necessarily reach the lowest point
-in the input file. It currently finds <em>pits</em> in the data, rather
-than the lowest point in the entire input map. The <em>r.fill.dir</em>,
-<em>r.terraflow</em>, and <em>r.basins.fill</em> modules can be used to
-fill in subbasins prior to processing with <em>r.drain</em>.
-
-<p>
-
-<em>r.drain</em> will not give sane results at the region boundary. On outer rows
-and columns bordering the edge of the region, the flow direction is always directly out
-of the map. In this case, the user could try adjusting the region extents slightly with
-<em>g.region</em> to allow additional outlet paths for <em>r.drain</em>.
-
-<h2>EXAMPLES</h2>
-
-Consider the following example:
-
-<div class="code"><pre>
-Input: Output:
- ELEVATION SURFACE LEAST COST PATH
-. . ----- . . . . . . . . . . . . . . . . . . . . . . . . .
-. 20| 19| 17. 16. 17. 16. 16. . . 1 . 1 . 1 . . . .
-. . |___| . . . . . . . . . . . . . . . . . . . . . . . . .
-. 18. 18. 24. 18. 15. 12. 11. . . . . . 1 . . .
-. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
-. 22. 16. 16. 18. 10. 10. 10. . . . . . 1 . . .
-. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
-. 17. 15. 15. 15. 10. 8 . 8 . . . . . . . 1 . .
-. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
-. 24. 16. 8 . 7 . 8 . 0 .12 . . . . . . . 1 . .
-. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
-. 17. 9 . 8 . 7 . 8 . 6 .12 . . . . . . . . .
-. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
-</pre></div>
-
-<p>
-
-The user-provided starting location in the above example is
-the boxed <b>19</b> in the left-hand map. The path in the output
-shows the least-cost corridor for moving from the starting
-box to the lowest (smallest) possible point. This is the path a raindrop
-would take in this landscape.
-<p>
-
-With the <b>-c</b> <em>(copy)</em> flag, you get the following result:
-
-<div class="code"><pre>
-Input: Output:
- ELEVATION SURFACE LEAST COST PATH
-. . ----- . . . . . . . . . . . . . . . . . . . . . . . . .
-. 20| 19| 17. 16. 17. 16. 16. . . 19. 17. 16. . . .
-. . |___| . . . . . . . . . . . . . . . . . . . . . . . . .
-. 18. 18. 24. 18. 15. 12. 11. . . . . . 15. . .
-. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
-. 22. 16. 16. 18. 10. 10. 10. . . . . . 10. . .
-. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
-. 17. 15. 15. 15. 10. 8 . 8 . . . . . . . 8 . .
-. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
-. 24. 16. 8 . 7 . 8 . 0 .12 . . . . . . . 0 . .
-. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
-. 17. 9 . 8 . 7 . 8 . 6 .12 . . . . . . . . .
-. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
-
-Note that the last <em>0</em> will not be put in the null values map.
-</pre></div>
-
-<p>
-
-With the <b>-a</b> <em>(accumulate)</em> flag, you get the following result:
-
-<div class="code"><pre>
-Input: Output:
- ELEVATION SURFACE LEAST COST PATH
-. . ----- . . . . . . . . . . . . . . . . . . . . . . . . .
-. 20| 19| 17. 16. 17. 16. 16. . . 19. 36. 52. . . .
-. . |___| . . . . . . . . . . . . . . . . . . . . . . . . .
-. 18. 18. 24. 18. 15. 12. 11. . . . . . 67. . .
-. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
-. 22. 16. 16. 18. 10. 10. 10. . . . . . 77. . .
-. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
-. 17. 15. 15. 15. 10. 8 . 8 . . . . . . . 85. .
-. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
-. 24. 16. 8 . 7 . 8 . 0 .12 . . . . . . . 85. .
-. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
-. 17. 9 . 8 . 7 . 8 . 6 .12 . . . . . . . . .
-. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
-</pre></div>
-
-<p>
-
-With the <b>-n</b> <em>(number)</em> flag, you get the following result:
-
-<div class="code"><pre>
-Input: Output:
- ELEVATION SURFACE LEAST COST PATH
-. . ----- . . . . . . . . . . . . . . . . . . . . . . . . .
-. 20| 19| 17. 16. 17. 16. 16. . . 1 . 2 . 3 . . . .
-. . |___| . . . . . . . . . . . . . . . . . . . . . . . . .
-. 18. 18. 24. 18. 15. 12. 11. . . . . . 4 . . .
-. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
-. 22. 16. 16. 18. 10. 10. 10. . . . . . 5 . . .
-. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
-. 17. 15. 15. 15. 10. 8 . 8 . . . . . . . 6 . .
-. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
-. 24. 16. 8 . 7 . 8 . 0 .12 . . . . . . . 7 . .
-. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
-. 17. 9 . 8 . 7 . 8 . 6 .12 . . . . . . . . .
-. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
-</pre></div>
-
-<p>
-
-<h2>BUGS</h2>
-
-<p>
-Sometimes, when the differences among integer cell category values in the
-<em><a href="r.cost.html">r.cost</a></em> cumulative cost surface output are
-small, this cumulative cost output cannot accurately be used as input to
-<em>r.drain</em> (<em>t.drain</em> will output bad results).
-This problem can be circumvented by making the differences
-between cell category values in the cumulative cost output bigger. It
-is recommended that if the output from <em>r.cost</em> is to be used
-as input to <em>r.drain</em>, the user multiply the <em>r.cost</em>
-input cost surface map by the value of the map's cell resolution,
-before running <em>r.cost</em>. This can be done using
-<em><a href="r.mapcalc.html">r.mapcalc</a></em>. The map resolution can be
-found using <em><a href="g.region.html">g.region</a></em>.
-This problem doesn't arise with floating point maps.
-
-
-<h2>SEE ALSO</h2>
-
-<em><a href="g.region.html">g.region</a></em>,
-<em><a href="r.cost.html">r.cost</a></em>,
-<em><a href="r.fill.dir.html">r.fill.dir</a></em>,
-<em><a href="r.basins.fill.html">r.basins.fill</a></em>,
-<em><a href="r.terraflow.html">r.terraflow</a></em>,
-<em><a href="r.mapcalc.html">r.mapcalc</a></em>,
-<em><a href="r.walk.html">r.walk</a></em>
-
-<h2>AUTHOR</h2>
-
-Completely rewritten by Roger S. Miller, 2001
-<p>
-July 2004 at WebValley 2004, error checking and vector points added by
-Matteo Franchi (Liceo Leonardo Da Vinci, Trento) and
-Roberto Flor (ITC-irst, Trento, Italy)
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.drain/r.drain.html (from rev 32770, grass/trunk/raster/r.drain/description.html)
===================================================================
--- grass/trunk/raster/r.drain/r.drain.html (rev 0)
+++ grass/trunk/raster/r.drain/r.drain.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,194 @@
+<h2>DESCRIPTION</h2>
+
+
+<em>r.drain</em> traces a flow through a least-cost path in an elevation
+model. The <b>input</b> elevation surface (a raster map layer) might
+be a cumulative cost map generated by the
+<em><a href="r.cost.html">r.cost</a></em> program.
+
+The <b>output</b> result (also a raster map layer) will show one or more
+least-cost paths between each user-provided location(s) and the minima
+(low category values) in the <b>input</b> map. By default, the <b>output</b>
+will be an integer CELL map with <tt>1</tt> along the least cost path,
+and null cells elsewhere.
+
+<p>
+With the <b>-c</b> (<em>copy</em>) flag, the input map cell values are
+copied verbatim along the path. With the <b>-a</b> (<em>accumulate</em>)
+flag, the accumulated cell value from the starting point up to the current
+cell is written on output. With either the <b>-c</b> or the <b>-a</b> flags, the
+<b>output</b> map is created with the same cell type as the <b>input</b> map (integer,
+float or double).
+With the <b>-n</b> (<em>number</em>) flag, the cells are numbered consecutively from the
+starting point to the final point.
+The <b>-c</b>, <b>-a</b>, and <b>-n</b> flags are mutually incompatible.
+
+<p>
+The path is calculated by choosing the steeper "slope" between adjacent
+cells. The slope calculation accurately acounts for the variable scale in
+lat-lon projections.
+
+<p>
+The <b>coordinate</b> parameter consists of map E and N grid coordinates of
+a starting point. Each x,y pair is the easting and northing (respectively) of
+a starting point from which a least-cost corridor will be developed.
+The <b>vector_points</b> parameter can take multiple vector maps containing
+additional starting points.
+Up to 1024 starting points can be input from a combination of the
+<b>coordinate</b> and <b>vector_points</b> parameters.
+
+<h2>NOTES</h2>
+
+<em>r.drain</em> currently finds only the lowest point
+(the cell having the smallest category value) in the
+input file that can be reached through directly adjacent cells
+that are less than or equal in value to the cell reached immediately
+prior to it; therefore, it will not necessarily reach the lowest point
+in the input file. It currently finds <em>pits</em> in the data, rather
+than the lowest point in the entire input map. The <em>r.fill.dir</em>,
+<em>r.terraflow</em>, and <em>r.basins.fill</em> modules can be used to
+fill in subbasins prior to processing with <em>r.drain</em>.
+
+<p>
+
+<em>r.drain</em> will not give sane results at the region boundary. On outer rows
+and columns bordering the edge of the region, the flow direction is always directly out
+of the map. In this case, the user could try adjusting the region extents slightly with
+<em>g.region</em> to allow additional outlet paths for <em>r.drain</em>.
+
+<h2>EXAMPLES</h2>
+
+Consider the following example:
+
+<div class="code"><pre>
+Input: Output:
+ ELEVATION SURFACE LEAST COST PATH
+. . ----- . . . . . . . . . . . . . . . . . . . . . . . . .
+. 20| 19| 17. 16. 17. 16. 16. . . 1 . 1 . 1 . . . .
+. . |___| . . . . . . . . . . . . . . . . . . . . . . . . .
+. 18. 18. 24. 18. 15. 12. 11. . . . . . 1 . . .
+. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
+. 22. 16. 16. 18. 10. 10. 10. . . . . . 1 . . .
+. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
+. 17. 15. 15. 15. 10. 8 . 8 . . . . . . . 1 . .
+. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
+. 24. 16. 8 . 7 . 8 . 0 .12 . . . . . . . 1 . .
+. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
+. 17. 9 . 8 . 7 . 8 . 6 .12 . . . . . . . . .
+. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
+</pre></div>
+
+<p>
+
+The user-provided starting location in the above example is
+the boxed <b>19</b> in the left-hand map. The path in the output
+shows the least-cost corridor for moving from the starting
+box to the lowest (smallest) possible point. This is the path a raindrop
+would take in this landscape.
+<p>
+
+With the <b>-c</b> <em>(copy)</em> flag, you get the following result:
+
+<div class="code"><pre>
+Input: Output:
+ ELEVATION SURFACE LEAST COST PATH
+. . ----- . . . . . . . . . . . . . . . . . . . . . . . . .
+. 20| 19| 17. 16. 17. 16. 16. . . 19. 17. 16. . . .
+. . |___| . . . . . . . . . . . . . . . . . . . . . . . . .
+. 18. 18. 24. 18. 15. 12. 11. . . . . . 15. . .
+. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
+. 22. 16. 16. 18. 10. 10. 10. . . . . . 10. . .
+. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
+. 17. 15. 15. 15. 10. 8 . 8 . . . . . . . 8 . .
+. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
+. 24. 16. 8 . 7 . 8 . 0 .12 . . . . . . . 0 . .
+. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
+. 17. 9 . 8 . 7 . 8 . 6 .12 . . . . . . . . .
+. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
+
+Note that the last <em>0</em> will not be put in the null values map.
+</pre></div>
+
+<p>
+
+With the <b>-a</b> <em>(accumulate)</em> flag, you get the following result:
+
+<div class="code"><pre>
+Input: Output:
+ ELEVATION SURFACE LEAST COST PATH
+. . ----- . . . . . . . . . . . . . . . . . . . . . . . . .
+. 20| 19| 17. 16. 17. 16. 16. . . 19. 36. 52. . . .
+. . |___| . . . . . . . . . . . . . . . . . . . . . . . . .
+. 18. 18. 24. 18. 15. 12. 11. . . . . . 67. . .
+. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
+. 22. 16. 16. 18. 10. 10. 10. . . . . . 77. . .
+. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
+. 17. 15. 15. 15. 10. 8 . 8 . . . . . . . 85. .
+. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
+. 24. 16. 8 . 7 . 8 . 0 .12 . . . . . . . 85. .
+. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
+. 17. 9 . 8 . 7 . 8 . 6 .12 . . . . . . . . .
+. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
+</pre></div>
+
+<p>
+
+With the <b>-n</b> <em>(number)</em> flag, you get the following result:
+
+<div class="code"><pre>
+Input: Output:
+ ELEVATION SURFACE LEAST COST PATH
+. . ----- . . . . . . . . . . . . . . . . . . . . . . . . .
+. 20| 19| 17. 16. 17. 16. 16. . . 1 . 2 . 3 . . . .
+. . |___| . . . . . . . . . . . . . . . . . . . . . . . . .
+. 18. 18. 24. 18. 15. 12. 11. . . . . . 4 . . .
+. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
+. 22. 16. 16. 18. 10. 10. 10. . . . . . 5 . . .
+. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
+. 17. 15. 15. 15. 10. 8 . 8 . . . . . . . 6 . .
+. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
+. 24. 16. 8 . 7 . 8 . 0 .12 . . . . . . . 7 . .
+. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
+. 17. 9 . 8 . 7 . 8 . 6 .12 . . . . . . . . .
+. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
+</pre></div>
+
+<p>
+
+<h2>BUGS</h2>
+
+<p>
+Sometimes, when the differences among integer cell category values in the
+<em><a href="r.cost.html">r.cost</a></em> cumulative cost surface output are
+small, this cumulative cost output cannot accurately be used as input to
+<em>r.drain</em> (<em>t.drain</em> will output bad results).
+This problem can be circumvented by making the differences
+between cell category values in the cumulative cost output bigger. It
+is recommended that if the output from <em>r.cost</em> is to be used
+as input to <em>r.drain</em>, the user multiply the <em>r.cost</em>
+input cost surface map by the value of the map's cell resolution,
+before running <em>r.cost</em>. This can be done using
+<em><a href="r.mapcalc.html">r.mapcalc</a></em>. The map resolution can be
+found using <em><a href="g.region.html">g.region</a></em>.
+This problem doesn't arise with floating point maps.
+
+
+<h2>SEE ALSO</h2>
+
+<em><a href="g.region.html">g.region</a></em>,
+<em><a href="r.cost.html">r.cost</a></em>,
+<em><a href="r.fill.dir.html">r.fill.dir</a></em>,
+<em><a href="r.basins.fill.html">r.basins.fill</a></em>,
+<em><a href="r.terraflow.html">r.terraflow</a></em>,
+<em><a href="r.mapcalc.html">r.mapcalc</a></em>,
+<em><a href="r.walk.html">r.walk</a></em>
+
+<h2>AUTHOR</h2>
+
+Completely rewritten by Roger S. Miller, 2001
+<p>
+July 2004 at WebValley 2004, error checking and vector points added by
+Matteo Franchi (Liceo Leonardo Da Vinci, Trento) and
+Roberto Flor (ITC-irst, Trento, Italy)
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.fill.dir/description.html
===================================================================
--- grass/trunk/raster/r.fill.dir/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.fill.dir/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,106 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-
-<em>r.fill.dir</em> filters and generates a depressionless
-elevation map and a flow direction map from a given raster elevation map.
-
-<h2>NOTES</h2>
-
-The <b>type</b> parameter is the type of format at which the user wishes to create
-the flow direction map. The <i>agnps</i> format gives category values from
-1-8, with 1 facing north and increasing values in the clockwise direction.
-The <i>answers</i> format gives category values from 0-360 degrees, with 0
-(360) facing east and values increasing in the counter clockwise direction
-at 45 degree increments. The <i>grass</i> format gives the same category
-values as the <em><a href="r.slope.aspect.html">r.slope.aspect</a></em>
-program.<p>
-
-The method adopted to filter the elevation map and rectify it is
-based on the paper titled "Software Tools to Extract Structure from Digital
-Elevation Data for Geographic Information System Analysis" by S.K. Jenson
-and J.O. Domingue (1988).
-<p>
-
-The procedure takes an elevation layer as input and initially fills all the
-depressions with one pass across the layer. Next, the flow direction
-algorithm tries to find a unique direction for each cell. If the watershed
-program detects areas with pothholes, it delineates this area from the rest
-of the area and once again the depressions are filled using the neighborhood
-technique used by the flow direction routine. The final output will be a
-depressionless elevation layer and a unique flow direction layer.
-<p>
-
-This (D8) flow algorithm performs as follows: At each raster cell the code
-determines the slope to each of the 8 surrounding cells and assigns the flow
-direction to the highest slope out of the cell. If there is more than one
-equal, non-zero slope then the code picks one direction based on preferences
-that are hard-coded into the program. If the highest slope is flat and in
-more than one direction then the code first tries to select an alternative
-based on flow directions in the adjacent cells. <em>r.fill.dir</em> iteratates that process,
-effectively propagating flow directions from areas where the directions are
-known into the area where the flow direction can't otherwise be resolved.
-
-<p>
-The flow direction map can be encoded in either ANSWERS (Beasley et.al,
-1982) or AGNPS (Young et.al, 1985) form, so that it can be readily used as
-input to these hydrologic models. The resulting depressionless elevation
-layer can further be manipulated for deriving slopes and other attributes
-required by the hydrologic models.
-<p>
-
-In case of local problems, those unfilled areas can be stored optionally.
-Each unfilled area in this maps is numbered. The <b>-f</b> flag
-instructs the program to fill single-cell pits but otherwise to just find
-the undrained areas and exit. With the <b>-f</b> flag set the program
-writes an elevation map with just single-cell pits filled, a direction map
-with unresolved problems and a map of the undrained areas that were found
-but not filled. This option was included because filling DEMs was often not
-the best way to solve a drainage problem. These options let the user get a
-partially-fixed elevation map, identify the remaining problems and fix the
-problems appropriately.
-<p>
-
-<em>r.fill.dir</em> is sensitive to the current window setting. Thus
-the program can be used to generate a flow direction map for any
-sub-area within the full map layer. Also, <em>r.fill.dir</em> is
-sensitive to any <em>mask</em> in effect.
-<p>
-
-In some cases it may be necessary to run r.fill.dir repeatedly (using output
-from one run as input to the next run) before all of problem areas are
-filled.
-
-<h2>EXAMPLE</h2>
-
-<div class="code"><pre>
-r.fill.dir input=ansi.elev elevation=ansi.fill.elev direction=ansi.asp
-</pre></div>
-
-<p>
-will create a depressionless (sinkless) elevation map ansi.fill.elev and a flow
-direction map ansi.asp for the type "grass".
-
-<h2>SEE ALSO</h2>
-
-<em>
-<a href="r.fillnulls.html">r.fillnulls</a>,
-<a href="r.slope.aspect.html">r.slope.aspect</a></em>
-
-<p>
-Beasley, D.B. and L.F. Huggins. 1982. ANSWERS (areal nonpoint source watershed environmental response simulation): User's manual. U.S. EPA-905/9-82-001, Chicago, IL, 54 p.
-<p>
-Jenson, S.K., and J.O. Domingue. 1988. Extracting topographic structure from
-digital elevation model data for geographic information system analysis. Photogram. Engr. and Remote Sens. 54: 1593-1600.
-<p>
-Young, R.A., C.A. Onstad, D.D. Bosch and W.P. Anderson. 1985. Agricultural nonpoint surface pollution models (AGNPS) I and II model documentation. St. Paul: Minn. Pollution control Agency and Washington D.C., USDA-Agricultural Research
-Service.
-<p>
-
-<h2>AUTHOR</h2>
-Fortran version:
-Raghavan Srinivasan, Agricultural Engineering Department, Purdue
-University<br>
-Rewrite to C with enhancements:
-Roger S. Miller
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.fill.dir/r.fill.dir.html (from rev 32770, grass/trunk/raster/r.fill.dir/description.html)
===================================================================
--- grass/trunk/raster/r.fill.dir/r.fill.dir.html (rev 0)
+++ grass/trunk/raster/r.fill.dir/r.fill.dir.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,106 @@
+<h2>DESCRIPTION</h2>
+
+
+<em>r.fill.dir</em> filters and generates a depressionless
+elevation map and a flow direction map from a given raster elevation map.
+
+<h2>NOTES</h2>
+
+The <b>type</b> parameter is the type of format at which the user wishes to create
+the flow direction map. The <i>agnps</i> format gives category values from
+1-8, with 1 facing north and increasing values in the clockwise direction.
+The <i>answers</i> format gives category values from 0-360 degrees, with 0
+(360) facing east and values increasing in the counter clockwise direction
+at 45 degree increments. The <i>grass</i> format gives the same category
+values as the <em><a href="r.slope.aspect.html">r.slope.aspect</a></em>
+program.<p>
+
+The method adopted to filter the elevation map and rectify it is
+based on the paper titled "Software Tools to Extract Structure from Digital
+Elevation Data for Geographic Information System Analysis" by S.K. Jenson
+and J.O. Domingue (1988).
+<p>
+
+The procedure takes an elevation layer as input and initially fills all the
+depressions with one pass across the layer. Next, the flow direction
+algorithm tries to find a unique direction for each cell. If the watershed
+program detects areas with pothholes, it delineates this area from the rest
+of the area and once again the depressions are filled using the neighborhood
+technique used by the flow direction routine. The final output will be a
+depressionless elevation layer and a unique flow direction layer.
+<p>
+
+This (D8) flow algorithm performs as follows: At each raster cell the code
+determines the slope to each of the 8 surrounding cells and assigns the flow
+direction to the highest slope out of the cell. If there is more than one
+equal, non-zero slope then the code picks one direction based on preferences
+that are hard-coded into the program. If the highest slope is flat and in
+more than one direction then the code first tries to select an alternative
+based on flow directions in the adjacent cells. <em>r.fill.dir</em> iteratates that process,
+effectively propagating flow directions from areas where the directions are
+known into the area where the flow direction can't otherwise be resolved.
+
+<p>
+The flow direction map can be encoded in either ANSWERS (Beasley et.al,
+1982) or AGNPS (Young et.al, 1985) form, so that it can be readily used as
+input to these hydrologic models. The resulting depressionless elevation
+layer can further be manipulated for deriving slopes and other attributes
+required by the hydrologic models.
+<p>
+
+In case of local problems, those unfilled areas can be stored optionally.
+Each unfilled area in this maps is numbered. The <b>-f</b> flag
+instructs the program to fill single-cell pits but otherwise to just find
+the undrained areas and exit. With the <b>-f</b> flag set the program
+writes an elevation map with just single-cell pits filled, a direction map
+with unresolved problems and a map of the undrained areas that were found
+but not filled. This option was included because filling DEMs was often not
+the best way to solve a drainage problem. These options let the user get a
+partially-fixed elevation map, identify the remaining problems and fix the
+problems appropriately.
+<p>
+
+<em>r.fill.dir</em> is sensitive to the current window setting. Thus
+the program can be used to generate a flow direction map for any
+sub-area within the full map layer. Also, <em>r.fill.dir</em> is
+sensitive to any <em>mask</em> in effect.
+<p>
+
+In some cases it may be necessary to run r.fill.dir repeatedly (using output
+from one run as input to the next run) before all of problem areas are
+filled.
+
+<h2>EXAMPLE</h2>
+
+<div class="code"><pre>
+r.fill.dir input=ansi.elev elevation=ansi.fill.elev direction=ansi.asp
+</pre></div>
+
+<p>
+will create a depressionless (sinkless) elevation map ansi.fill.elev and a flow
+direction map ansi.asp for the type "grass".
+
+<h2>SEE ALSO</h2>
+
+<em>
+<a href="r.fillnulls.html">r.fillnulls</a>,
+<a href="r.slope.aspect.html">r.slope.aspect</a></em>
+
+<p>
+Beasley, D.B. and L.F. Huggins. 1982. ANSWERS (areal nonpoint source watershed environmental response simulation): User's manual. U.S. EPA-905/9-82-001, Chicago, IL, 54 p.
+<p>
+Jenson, S.K., and J.O. Domingue. 1988. Extracting topographic structure from
+digital elevation model data for geographic information system analysis. Photogram. Engr. and Remote Sens. 54: 1593-1600.
+<p>
+Young, R.A., C.A. Onstad, D.D. Bosch and W.P. Anderson. 1985. Agricultural nonpoint surface pollution models (AGNPS) I and II model documentation. St. Paul: Minn. Pollution control Agency and Washington D.C., USDA-Agricultural Research
+Service.
+<p>
+
+<h2>AUTHOR</h2>
+Fortran version:
+Raghavan Srinivasan, Agricultural Engineering Department, Purdue
+University<br>
+Rewrite to C with enhancements:
+Roger S. Miller
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.flow/description.html
===================================================================
--- grass/trunk/raster/r.flow/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.flow/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,193 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-This program generates flowlines using a combined raster-vector
-approach (see <a href="http://skagit.meas.ncsu.edu/~helena/gmslab/papers/hmg.rev1.ps">Mitasova and
-Hofierka 1993</a> and <a href="http://skagit.meas.ncsu.edu/~helena/gmslab/papers/ijgis.html">Mitasova et
-al. 1995</a>) from an input elevation raster map <b>elevin</b>
-(integer or floating point), and optionally an input aspect raster map
-<b>aspin</b> and/or an input barrier raster map <b>barin</b>. There are
-three possible output maps which can be produced in any combination
-simultaneously: a vector map <b>flout</b> of flowlines, a raster map
-<b>lgout</b> of flowpath lengths, and a raster map <b>dsout</b> of flowline
-densities (which are equal upslope contributed areas per unit width, when
-multiplied by resolution).
-<p>
-
-Aspect used for input must follow the same rules as aspect computed
-in other GRASS programs (see <a href="v.surf.rst.html">v.surf.rst</a>
-or <a href="r.slope.aspect.html">r.slope.aspect</a>).
-<p>
-
-Flowline output is given in a vector map <b>flout</b>, (flowlines generated
-downhill). The line segments of flowline vectors have endpoints on edges
-of a grid formed by drawing imaginary lines through the centers of the
-cells in the elevation map. Flowlines are generated from each cell downhill
-by default; they can be generated uphill using the flag <b>-u</b>. A flowline
-stops if its next segment would reverse the direction of flow (from up
-to down or vice-versa), cross a barrier, or arrive at a cell with undefined
-elevation or aspect. Another option, <b>skip</b>=val, indicates that only
-the flowlines from every val-th cell are to be included in <b>flout</b>.
-The default <b>skip</b> is max(1, <rows in elevin>/50, <cols in elevin>/50).
-A high <b>skip</b> usually speeds up processing time and often improves
-the readability of a visualization of <b>flout</b>.
-<p>
-
-Flowpath length output is given in a raster map <b>lgout</b>. The value
-in each grid cell is the sum of the planar lengths of all segments of the
-flowline generated from that cell. If the flag <b>-3</b> is given, elevation
-is taken into account in calculating the length of each segment.
-
-<p>Flowline density downhill or uphill output is given in a raster map
-<b>dsout.</b> The value in each grid cell is the number of flowlines which
-pass through that grid cell, that means the number of flowlines from the
-entire map which have segment endpoints within that cell.
-
-
-With the <b>-m</b> flag less memory is used as aspect at each cell is computed
-on the fly. This option incurs a severe performance penalty. If this flag is given,
-the aspect input map (if any) will be ignored.
-
-<!-- doesn't exist
-<p><b>-M</b> Use a fixed size memory and utilize page-swapping to handle
-large input files. This option incurs a severe performance penalty but
-is the only way to handle arbitrarily-large data files. If this flag is
-given, the <b>-m</b> flag will be ignored.
--->
-
-The <b>barin</b> parameter is a raster map name with non-zero
-values representing barriers as input.
-
-
-<h2>NOTES</h2>
-For best results, use input elevation maps with high precision units (e.g.,
-centimeters) so that flowlines do not terminate prematurely in flat areas.
-To prevent the creation of tiny flowline segments with imperceivable changes
-in elevation, an endpoint which would land very close to the center of
-a grid cell is quantized to the exact center of that cell. The maximum
-distance between the intercepts along each axis of a single diagonal segment
-and another segment of 1/2 degree different aspect is taken to be "very
-close" for that axis. Note that this distance (the so-called "quantization
-error") is about 1-2% of the resolution on maps with square cells.
-
-<p>The values in length maps computed using the <b>-u</b> flag represent
-the distances from each cell to an upland flat or singular point. Such
-distances are useful in water erosion modeling for computation of the LS
-factor in the standard form of USLE. Uphill flowlines merge on ridge lines;
-by redirecting the order of the flowline points in the output vector map,
-dispersed waterflow can be simulated. The density map can be used for the
-extraction of ridge lines.
-
-<p>Computing the flowlines downhill simulates the actual flow (also known
-as the raindrop method). These flowlines tend to merge in valleys; they
-can be used for localization of areas with waterflow accumulation and for
-the extraction of channels. The downslope flowline density multiplied by
-the resolution can be used as an approximation of the upslope contributing
-area per unit contour width. This area is a measure of potential water
-flux for the steady state conditions and can be used in the modeling of
-water erosion for the computation of the unit stream power based LS factor
-or sediment transport capacity.
-
-<p>The program has been designed for modeling erosion on hillslopes and
-has rather strict conditions for ending flowlines. It is therefore not
-very suitable for the extraction of stream networks or delineation of watersheds
-unless a DEM without pits or flat areas is available
-(<a href=r.fill.dir.html>r.fill.dir</a> can be used to fill pits).
-
-<p> To label the vector flowlines automatically, the user can use
-<a href=v.category.html>v.category</a> (add categories).
-
-<h3>Algorithm background</h3>
-
-<p>1. Construction of flow-lines (slope-lines): <em>r.flow</em> uses an original
-vector-grid algorithm which uses an infinite number of directions between
-0.0000... and 360.0000... and traces the flow as a line (vector) in the
-direction of gradient (rather than from cell to cell in one of the 8
-directions = D-infinity algorithm). They are traced in any direction using
-aspect (so there is no limitation to 8 directions here). The D8 algorithm
-produces zig-zag lines. The value in the outlet is very similar for both
-<em>r.flow</em> and <em>r.flowmd</em> (GRASS 5 only) algorithms (because it is
-essentially the watershed area), however the spatial distribution of flow,
-especially on hillslopes is quite different. It is still a 1D flow routing
-so the dispersal flow is not accurately described, but still better than D8.
-
-<p>2. Computation of contributing areas: <em>r.flow</em> uses a single flow
-algorithm, i.e. all flow is transported to a single cell downslope.
-
-<h3><b>Differences between <em>r.flow</em> and <em>r.flowmd</em></b></h3>
-<p>
-
-<ol>
-
-<li> <em>r.flow</em> has an option to compute slope and aspect internally thus making
-the program capable to process much larger data sets than <em>r.flowmd</em>. It has
-also 2 additional options for handling of large data sets but it is not
-known that they work properly.
-<li> the programs handle the special cases when the flowline passes exactly
-(or very close) through the grid vertices differently.
-<li> <em>r.flowmd</em> has the simplified multiple flow addition so the results are
-smoother.
-</ol>
-
-In conclusion, <em>r.flowmd</em> produces nicer results but is slower and it does not
-support as large data sets as <em>r.flow</em>.
-
-
-<h3>Diagnostics</h3>
-
-<p>"ERROR: r.flow: " input " file's resolution differs from current" region
-resolution
-
-<p>The resolutions of all input files and the current region must match.
-
-<p>"ERROR: r.flow: resolution too unbalanced (" val " x " val ")" The difference
-in length between the two axes of a grid cell is so great that quantization
-error is larger than one of the dimensions. Resample the map and try again.
-
-<h2>REFERENCES</h2>
-
-<p>Mitasova, H., L. Mitas, 1993, Interpolation by regularized spline with
-tension : I. Theory and implementation. Mathematical Geology 25, p. 641-655.
-(<a href=http://skagit.meas.ncsu.edu/~helena/gmslab/papers/lmg.rev1.ps>online</a>)
-
-<p>Mitasova and Hofierka 1993 : Interpolation by Regularized Spline with
-Tension: II. Application to Terrain Modeling and Surface Geometry Analysis.
-Mathematical Geology 25(6), 657-669. (<a href=http://skagit.meas.ncsu.edu/~helena/gmslab/papers/hmg.rev1.ps>online</a>)
-
-<p>Mitasova, H., Mitas, L., Brown, W.M., Gerdes, D.P., Kosinovsky, I.,
-Baker, T., 1995: Modeling spatially and temporally distributed phenomena:
-New methods and tools for GRASS GIS. International Journal of Geographical
-Information Systems 9(4), 433-446.
-
-<p>Mitasova, H., J. Hofierka, M. Zlocha, L.R. Iverson, 1996, Modeling
-topographic potential for erosion and deposition using GIS. Int. Journal of
-Geographical Information Science, 10(5), 629-641. (reply to a comment to
-this paper appears in 1997 in Int. Journal of Geographical Information
-Science, Vol. 11, No. 6)
-
-<p>Mitasova, H.(1993): Surfaces and modeling. Grassclippings (winter and
-spring) p.18-19.
-
-<h2>SEE ALSO</h2>
-
-<a href="r.basins.fill.html">r.basins.fill</a>,
-<a href="r.drain.html">r.drain</a>,
-<a href="r.fill.dir.html">r.fill.dir</a>,
-<a href="r.water.outlet.html">r.water.outlet</a>,
-<a href="r.watershed.html">r.watershed</a>,
-<a href="v.category.html">v.category</a>,
-<a href="v.to.rast.html">v.to.rast</a>
-
-
-<h2>AUTHORS</h2>
-
-<p><i>Original version of program:</i>
-<br>Maros Zlocha and Jaroslav Hofierka, Comenius University, Bratislava,
-Slovakia,
-
-<p><i>The current version of the program (adapted for GRASS5.0)</i>:
-<br>Joshua Caplan, Mark Ruesink, Helena Mitasova, University of Illinois
-at Urbana-Champaign with support from USA CERL.<br>
-<a href=http://skagit.meas.ncsu.edu/~helena/gmslab/>GMSL/University of Illinois at
-Urbana-Champaign</a>
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.flow/r.flow.html (from rev 32770, grass/trunk/raster/r.flow/description.html)
===================================================================
--- grass/trunk/raster/r.flow/r.flow.html (rev 0)
+++ grass/trunk/raster/r.flow/r.flow.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,193 @@
+<h2>DESCRIPTION</h2>
+
+This program generates flowlines using a combined raster-vector
+approach (see <a href="http://skagit.meas.ncsu.edu/~helena/gmslab/papers/hmg.rev1.ps">Mitasova and
+Hofierka 1993</a> and <a href="http://skagit.meas.ncsu.edu/~helena/gmslab/papers/ijgis.html">Mitasova et
+al. 1995</a>) from an input elevation raster map <b>elevin</b>
+(integer or floating point), and optionally an input aspect raster map
+<b>aspin</b> and/or an input barrier raster map <b>barin</b>. There are
+three possible output maps which can be produced in any combination
+simultaneously: a vector map <b>flout</b> of flowlines, a raster map
+<b>lgout</b> of flowpath lengths, and a raster map <b>dsout</b> of flowline
+densities (which are equal upslope contributed areas per unit width, when
+multiplied by resolution).
+<p>
+
+Aspect used for input must follow the same rules as aspect computed
+in other GRASS programs (see <a href="v.surf.rst.html">v.surf.rst</a>
+or <a href="r.slope.aspect.html">r.slope.aspect</a>).
+<p>
+
+Flowline output is given in a vector map <b>flout</b>, (flowlines generated
+downhill). The line segments of flowline vectors have endpoints on edges
+of a grid formed by drawing imaginary lines through the centers of the
+cells in the elevation map. Flowlines are generated from each cell downhill
+by default; they can be generated uphill using the flag <b>-u</b>. A flowline
+stops if its next segment would reverse the direction of flow (from up
+to down or vice-versa), cross a barrier, or arrive at a cell with undefined
+elevation or aspect. Another option, <b>skip</b>=val, indicates that only
+the flowlines from every val-th cell are to be included in <b>flout</b>.
+The default <b>skip</b> is max(1, <rows in elevin>/50, <cols in elevin>/50).
+A high <b>skip</b> usually speeds up processing time and often improves
+the readability of a visualization of <b>flout</b>.
+<p>
+
+Flowpath length output is given in a raster map <b>lgout</b>. The value
+in each grid cell is the sum of the planar lengths of all segments of the
+flowline generated from that cell. If the flag <b>-3</b> is given, elevation
+is taken into account in calculating the length of each segment.
+
+<p>Flowline density downhill or uphill output is given in a raster map
+<b>dsout.</b> The value in each grid cell is the number of flowlines which
+pass through that grid cell, that means the number of flowlines from the
+entire map which have segment endpoints within that cell.
+
+
+With the <b>-m</b> flag less memory is used as aspect at each cell is computed
+on the fly. This option incurs a severe performance penalty. If this flag is given,
+the aspect input map (if any) will be ignored.
+
+<!-- doesn't exist
+<p><b>-M</b> Use a fixed size memory and utilize page-swapping to handle
+large input files. This option incurs a severe performance penalty but
+is the only way to handle arbitrarily-large data files. If this flag is
+given, the <b>-m</b> flag will be ignored.
+-->
+
+The <b>barin</b> parameter is a raster map name with non-zero
+values representing barriers as input.
+
+
+<h2>NOTES</h2>
+For best results, use input elevation maps with high precision units (e.g.,
+centimeters) so that flowlines do not terminate prematurely in flat areas.
+To prevent the creation of tiny flowline segments with imperceivable changes
+in elevation, an endpoint which would land very close to the center of
+a grid cell is quantized to the exact center of that cell. The maximum
+distance between the intercepts along each axis of a single diagonal segment
+and another segment of 1/2 degree different aspect is taken to be "very
+close" for that axis. Note that this distance (the so-called "quantization
+error") is about 1-2% of the resolution on maps with square cells.
+
+<p>The values in length maps computed using the <b>-u</b> flag represent
+the distances from each cell to an upland flat or singular point. Such
+distances are useful in water erosion modeling for computation of the LS
+factor in the standard form of USLE. Uphill flowlines merge on ridge lines;
+by redirecting the order of the flowline points in the output vector map,
+dispersed waterflow can be simulated. The density map can be used for the
+extraction of ridge lines.
+
+<p>Computing the flowlines downhill simulates the actual flow (also known
+as the raindrop method). These flowlines tend to merge in valleys; they
+can be used for localization of areas with waterflow accumulation and for
+the extraction of channels. The downslope flowline density multiplied by
+the resolution can be used as an approximation of the upslope contributing
+area per unit contour width. This area is a measure of potential water
+flux for the steady state conditions and can be used in the modeling of
+water erosion for the computation of the unit stream power based LS factor
+or sediment transport capacity.
+
+<p>The program has been designed for modeling erosion on hillslopes and
+has rather strict conditions for ending flowlines. It is therefore not
+very suitable for the extraction of stream networks or delineation of watersheds
+unless a DEM without pits or flat areas is available
+(<a href=r.fill.dir.html>r.fill.dir</a> can be used to fill pits).
+
+<p> To label the vector flowlines automatically, the user can use
+<a href=v.category.html>v.category</a> (add categories).
+
+<h3>Algorithm background</h3>
+
+<p>1. Construction of flow-lines (slope-lines): <em>r.flow</em> uses an original
+vector-grid algorithm which uses an infinite number of directions between
+0.0000... and 360.0000... and traces the flow as a line (vector) in the
+direction of gradient (rather than from cell to cell in one of the 8
+directions = D-infinity algorithm). They are traced in any direction using
+aspect (so there is no limitation to 8 directions here). The D8 algorithm
+produces zig-zag lines. The value in the outlet is very similar for both
+<em>r.flow</em> and <em>r.flowmd</em> (GRASS 5 only) algorithms (because it is
+essentially the watershed area), however the spatial distribution of flow,
+especially on hillslopes is quite different. It is still a 1D flow routing
+so the dispersal flow is not accurately described, but still better than D8.
+
+<p>2. Computation of contributing areas: <em>r.flow</em> uses a single flow
+algorithm, i.e. all flow is transported to a single cell downslope.
+
+<h3><b>Differences between <em>r.flow</em> and <em>r.flowmd</em></b></h3>
+<p>
+
+<ol>
+
+<li> <em>r.flow</em> has an option to compute slope and aspect internally thus making
+the program capable to process much larger data sets than <em>r.flowmd</em>. It has
+also 2 additional options for handling of large data sets but it is not
+known that they work properly.
+<li> the programs handle the special cases when the flowline passes exactly
+(or very close) through the grid vertices differently.
+<li> <em>r.flowmd</em> has the simplified multiple flow addition so the results are
+smoother.
+</ol>
+
+In conclusion, <em>r.flowmd</em> produces nicer results but is slower and it does not
+support as large data sets as <em>r.flow</em>.
+
+
+<h3>Diagnostics</h3>
+
+<p>"ERROR: r.flow: " input " file's resolution differs from current" region
+resolution
+
+<p>The resolutions of all input files and the current region must match.
+
+<p>"ERROR: r.flow: resolution too unbalanced (" val " x " val ")" The difference
+in length between the two axes of a grid cell is so great that quantization
+error is larger than one of the dimensions. Resample the map and try again.
+
+<h2>REFERENCES</h2>
+
+<p>Mitasova, H., L. Mitas, 1993, Interpolation by regularized spline with
+tension : I. Theory and implementation. Mathematical Geology 25, p. 641-655.
+(<a href=http://skagit.meas.ncsu.edu/~helena/gmslab/papers/lmg.rev1.ps>online</a>)
+
+<p>Mitasova and Hofierka 1993 : Interpolation by Regularized Spline with
+Tension: II. Application to Terrain Modeling and Surface Geometry Analysis.
+Mathematical Geology 25(6), 657-669. (<a href=http://skagit.meas.ncsu.edu/~helena/gmslab/papers/hmg.rev1.ps>online</a>)
+
+<p>Mitasova, H., Mitas, L., Brown, W.M., Gerdes, D.P., Kosinovsky, I.,
+Baker, T., 1995: Modeling spatially and temporally distributed phenomena:
+New methods and tools for GRASS GIS. International Journal of Geographical
+Information Systems 9(4), 433-446.
+
+<p>Mitasova, H., J. Hofierka, M. Zlocha, L.R. Iverson, 1996, Modeling
+topographic potential for erosion and deposition using GIS. Int. Journal of
+Geographical Information Science, 10(5), 629-641. (reply to a comment to
+this paper appears in 1997 in Int. Journal of Geographical Information
+Science, Vol. 11, No. 6)
+
+<p>Mitasova, H.(1993): Surfaces and modeling. Grassclippings (winter and
+spring) p.18-19.
+
+<h2>SEE ALSO</h2>
+
+<a href="r.basins.fill.html">r.basins.fill</a>,
+<a href="r.drain.html">r.drain</a>,
+<a href="r.fill.dir.html">r.fill.dir</a>,
+<a href="r.water.outlet.html">r.water.outlet</a>,
+<a href="r.watershed.html">r.watershed</a>,
+<a href="v.category.html">v.category</a>,
+<a href="v.to.rast.html">v.to.rast</a>
+
+
+<h2>AUTHORS</h2>
+
+<p><i>Original version of program:</i>
+<br>Maros Zlocha and Jaroslav Hofierka, Comenius University, Bratislava,
+Slovakia,
+
+<p><i>The current version of the program (adapted for GRASS5.0)</i>:
+<br>Joshua Caplan, Mark Ruesink, Helena Mitasova, University of Illinois
+at Urbana-Champaign with support from USA CERL.<br>
+<a href=http://skagit.meas.ncsu.edu/~helena/gmslab/>GMSL/University of Illinois at
+Urbana-Champaign</a>
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.grow.distance/description.html
===================================================================
--- grass/trunk/raster/r.grow.distance/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.grow.distance/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,69 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-
-<em>r.grow.distance</em> generates a raster map representing the
-distance to the nearest non-null cell in the input map.
-
-<h2>NOTES</h2>
-The user has the option of specifying four different metrics which
-control the geometry in which grown cells are created, (controlled by
-the <b>metric</b> parameter): <i>Euclidean</i>, <i>Squared</i>,
-<i>Manhattan</i>, and <i>Maximum</i>.
-
-<p>
-
-The <i>Euclidean distance</i> or <i>Euclidean metric</i> is the "ordinary" distance
-between two points that one would measure with a ruler, which can be
-proven by repeated application of the Pythagorean theorem.
-The formula is given by:
-
-<div class="code"><pre>d(dx,dy) = sqrt(dx^2 + dy^2)</pre></div>
-
-Cells grown using this metric would form isolines of distance that are
-circular from a given point, with the distance given by the <b>radius</b>.
-
-<p>
-The <i>Squared</i> metric is the <i>Euclidean</i> distance squared,
-i.e. it simply omits the square-root calculation. This may be faster,
-and is sufficient if only relative values are required.
-
-<p>
-
-The <i>Manhattan metric</i>, or <i>Taxicab geometry</i>, is a form of geometry in
-which the usual metric of Euclidean geometry is replaced by a new
-metric in which the distance between two points is the sum of the (absolute)
-differences of their coordinates. The name alludes to the grid layout of
-most streets on the island of Manhattan, which causes the shortest path a
-car could take between two points in the city to have length equal to the
-points' distance in taxicab geometry.
-The formula is given by:
-
-<div class="code"><pre>d(dx,dy) = abs(dx) + abs(dy)</pre></div>
-
-where cells grown using this metric would form isolines of distance that are
-rhombus-shaped from a given point.
-
-<p>
-
-The <i>Maximum metric</i> is given by the formula
-
-<div class="code"><pre>d(dx,dy) = max(abs(dx),abs(dy))</pre></div>
-
-where the isolines of distance from a point are squares.
-
-<h2>SEE ALSO</h2>
-
-<em><a href="r.grow.html">r.grow</a></em><br>
-<em><a href="r.buffer.html">r.buffer</a></em><br>
-<em><a href="r.patch.html">r.patch</a></em>
-
-<p>
-
-<em><a href="http://en.wikipedia.org/wiki/Euclidean_metric">Wikipedia Entry: Euclidean Metric</a><br>
-<em><a href="http://en.wikipedia.org/wiki/Manhattan_metric">Wikipedia Entry: Manhattan Metric</a>
-
-<h2>AUTHORS</h2>
-
-Glynn Clements
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.grow.distance/r.grow.distance.html (from rev 32770, grass/trunk/raster/r.grow.distance/description.html)
===================================================================
--- grass/trunk/raster/r.grow.distance/r.grow.distance.html (rev 0)
+++ grass/trunk/raster/r.grow.distance/r.grow.distance.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,69 @@
+<h2>DESCRIPTION</h2>
+
+
+<em>r.grow.distance</em> generates a raster map representing the
+distance to the nearest non-null cell in the input map.
+
+<h2>NOTES</h2>
+The user has the option of specifying four different metrics which
+control the geometry in which grown cells are created, (controlled by
+the <b>metric</b> parameter): <i>Euclidean</i>, <i>Squared</i>,
+<i>Manhattan</i>, and <i>Maximum</i>.
+
+<p>
+
+The <i>Euclidean distance</i> or <i>Euclidean metric</i> is the "ordinary" distance
+between two points that one would measure with a ruler, which can be
+proven by repeated application of the Pythagorean theorem.
+The formula is given by:
+
+<div class="code"><pre>d(dx,dy) = sqrt(dx^2 + dy^2)</pre></div>
+
+Cells grown using this metric would form isolines of distance that are
+circular from a given point, with the distance given by the <b>radius</b>.
+
+<p>
+The <i>Squared</i> metric is the <i>Euclidean</i> distance squared,
+i.e. it simply omits the square-root calculation. This may be faster,
+and is sufficient if only relative values are required.
+
+<p>
+
+The <i>Manhattan metric</i>, or <i>Taxicab geometry</i>, is a form of geometry in
+which the usual metric of Euclidean geometry is replaced by a new
+metric in which the distance between two points is the sum of the (absolute)
+differences of their coordinates. The name alludes to the grid layout of
+most streets on the island of Manhattan, which causes the shortest path a
+car could take between two points in the city to have length equal to the
+points' distance in taxicab geometry.
+The formula is given by:
+
+<div class="code"><pre>d(dx,dy) = abs(dx) + abs(dy)</pre></div>
+
+where cells grown using this metric would form isolines of distance that are
+rhombus-shaped from a given point.
+
+<p>
+
+The <i>Maximum metric</i> is given by the formula
+
+<div class="code"><pre>d(dx,dy) = max(abs(dx),abs(dy))</pre></div>
+
+where the isolines of distance from a point are squares.
+
+<h2>SEE ALSO</h2>
+
+<em><a href="r.grow.html">r.grow</a></em><br>
+<em><a href="r.buffer.html">r.buffer</a></em><br>
+<em><a href="r.patch.html">r.patch</a></em>
+
+<p>
+
+<em><a href="http://en.wikipedia.org/wiki/Euclidean_metric">Wikipedia Entry: Euclidean Metric</a><br>
+<em><a href="http://en.wikipedia.org/wiki/Manhattan_metric">Wikipedia Entry: Manhattan Metric</a>
+
+<h2>AUTHORS</h2>
+
+Glynn Clements
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.grow2/description.html
===================================================================
--- grass/trunk/raster/r.grow2/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.grow2/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,77 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-
-<em>r.grow</em> adds cells around the perimeters of all areas
-in a user-specified raster map layer and stores the output in
-a new raster map layer. The user can use it to grow by one or
-more than one cell (by varying the size of the <b>radius</b>
-parameter), or like <em>r.buffer</em>, but with the
-option of preserving the original cells (similar to combining
-<em>r.buffer</em> and <em>r.patch</em>).
-
-<h2>NOTES</h2>
-The user has the option of specifying three different metrics which
-control the geometry in which grown cells are created, (controlled by
-the <b>metric</b> parameter): <i>Euclidean</i>, <i>Manhattan</i>, and
-<i>Maximum</i>.
-
-<p>
-
-The <i>Euclidean distance</i> or <i>Euclidean metric</i> is the "ordinary" distance
-between two points that one would measure with a ruler, which can be
-proven by repeated application of the Pythagorean theorem.
-The formula is given by:
-
-<div class="code"><pre>d(dx,dy) = sqrt(dx^2 + dy^2)</pre></div>
-
-Cells grown using this metric would form isolines of distance that are
-circular from a given point, with the distance given by the <b>radius</b>.
-
-<p>
-
-The <i>Manhattan metric</i>, or <i>Taxicab geometry</i>, is a form of geometry in
-which the usual metric of Euclidean geometry is replaced by a new
-metric in which the distance between two points is the sum of the (absolute)
-differences of their coordinates. The name alludes to the grid layout of
-most streets on the island of Manhattan, which causes the shortest path a
-car could take between two points in the city to have length equal to the
-points' distance in taxicab geometry.
-The formula is given by:
-
-<div class="code"><pre>d(dx,dy) = abs(dx) + abs(dy)</pre></div>
-
-where cells grown using this metric would form isolines of distance that are
-rhombus-shaped from a given point.
-
-<p>
-
-The <i>Maximum metric</i> is given by the formula
-
-<div class="code"><pre>d(dx,dy) = max(abs(dx),abs(dy))</pre></div>
-
-where the isolines of distance from a point are squares.
-
-<p>
-
-If there are two cells which are equal candidates to grow into an empty space,
-<em>r.grow</em> will choose the northernmost candidate; if there are multiple
-candidates with the same northing, the westernmost is chosen.
-
-<h2>SEE ALSO</h2>
-
-<em><a href="r.buffer.html">r.buffer</a></em><br>
-<em><a href="r.patch.html">r.patch</a></em>
-
-<p>
-
-<em><a href="http://en.wikipedia.org/wiki/Euclidean_metric">Wikipedia Entry: Euclidean Metric</a><br>
-<em><a href="http://en.wikipedia.org/wiki/Manhattan_metric">Wikipedia Entry: Manhattan Metric</a>
-
-<h2>AUTHORS</h2>
-
-Marjorie Larson,
-U.S. Army Construction Engineering Research Laboratory
-<p>
-Glynn Clements
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.grow2/r.grow.html (from rev 32770, grass/trunk/raster/r.grow2/description.html)
===================================================================
--- grass/trunk/raster/r.grow2/r.grow.html (rev 0)
+++ grass/trunk/raster/r.grow2/r.grow.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,77 @@
+<h2>DESCRIPTION</h2>
+
+
+<em>r.grow</em> adds cells around the perimeters of all areas
+in a user-specified raster map layer and stores the output in
+a new raster map layer. The user can use it to grow by one or
+more than one cell (by varying the size of the <b>radius</b>
+parameter), or like <em>r.buffer</em>, but with the
+option of preserving the original cells (similar to combining
+<em>r.buffer</em> and <em>r.patch</em>).
+
+<h2>NOTES</h2>
+The user has the option of specifying three different metrics which
+control the geometry in which grown cells are created, (controlled by
+the <b>metric</b> parameter): <i>Euclidean</i>, <i>Manhattan</i>, and
+<i>Maximum</i>.
+
+<p>
+
+The <i>Euclidean distance</i> or <i>Euclidean metric</i> is the "ordinary" distance
+between two points that one would measure with a ruler, which can be
+proven by repeated application of the Pythagorean theorem.
+The formula is given by:
+
+<div class="code"><pre>d(dx,dy) = sqrt(dx^2 + dy^2)</pre></div>
+
+Cells grown using this metric would form isolines of distance that are
+circular from a given point, with the distance given by the <b>radius</b>.
+
+<p>
+
+The <i>Manhattan metric</i>, or <i>Taxicab geometry</i>, is a form of geometry in
+which the usual metric of Euclidean geometry is replaced by a new
+metric in which the distance between two points is the sum of the (absolute)
+differences of their coordinates. The name alludes to the grid layout of
+most streets on the island of Manhattan, which causes the shortest path a
+car could take between two points in the city to have length equal to the
+points' distance in taxicab geometry.
+The formula is given by:
+
+<div class="code"><pre>d(dx,dy) = abs(dx) + abs(dy)</pre></div>
+
+where cells grown using this metric would form isolines of distance that are
+rhombus-shaped from a given point.
+
+<p>
+
+The <i>Maximum metric</i> is given by the formula
+
+<div class="code"><pre>d(dx,dy) = max(abs(dx),abs(dy))</pre></div>
+
+where the isolines of distance from a point are squares.
+
+<p>
+
+If there are two cells which are equal candidates to grow into an empty space,
+<em>r.grow</em> will choose the northernmost candidate; if there are multiple
+candidates with the same northing, the westernmost is chosen.
+
+<h2>SEE ALSO</h2>
+
+<em><a href="r.buffer.html">r.buffer</a></em><br>
+<em><a href="r.patch.html">r.patch</a></em>
+
+<p>
+
+<em><a href="http://en.wikipedia.org/wiki/Euclidean_metric">Wikipedia Entry: Euclidean Metric</a><br>
+<em><a href="http://en.wikipedia.org/wiki/Manhattan_metric">Wikipedia Entry: Manhattan Metric</a>
+
+<h2>AUTHORS</h2>
+
+Marjorie Larson,
+U.S. Army Construction Engineering Research Laboratory
+<p>
+Glynn Clements
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.gwflow/description.html
===================================================================
--- grass/trunk/raster/r.gwflow/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.gwflow/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,120 +0,0 @@
-<h2>DESCRIPTION</h2>
-This numerical program calculates transient, confined and
-unconfined groundwater flow in two dimensions based on
-raster maps and the current region resolution.
-All initial and boundary conditions must be provided as
-raster maps.
-
-<p>
-<center>
-<img src=r_gwflow_concept.png border=0><br>
-<table border=0 width=700>
-<tr><td><center>
-<i>Workflow of r.gwflow</i>
-</center></td></tr>
-</table>
-</center>
-<p>
-
-<em>r.gwflow</em> calculates the piezometric head and optionally the
-filter velocity field, based on the hydraulic conductivity and the piezometric head.
-The vector components can be visualized with paraview if they are exported
-with <em>r.out.vtk</em>.
-<br>
-<br>
-The groundwater flow will always be calculated transient.
-If you want to calculate stady state, set the timestep
-to a large number (billions of seconds) or set the
-specific yield/ effective porosity raster maps to zero.
-
-
-<h2>NOTES</h2>
-
-The groundwater flow calculation is based on Darcy's law and a
-finite volume discretization. The solved groundwater flow partial
-differential equation is of the following form:
-
-<p>
-(dh/dt)*Ss = Kxx * (d^2h/dx^2) + Kyy * (d^2h/dy^2) + q
-
-<ul>
-<li>h -- the piezometric head im [m]</li>
-<li>dt -- the time step for transient calculation in [s]</li>
-<li>S -- the specific yield [1/m]</li>
-<li>Kxx -- the hydraulic conductivity tensor part in x direction in [m/s]</li>
-<li>Kyy -- the hydraulic conductivity tensor part in y direction in [m/s]</li>
-<li>q - inner source in meter per second [1/s]</li>
-</ul>
-
-<br>
-<br>
-Two different boundary conditions are implemented,
-the Dirichlet and Neumann conditions. By default the calculation area is surrounded by homogeneous Neumann boundary conditions.
-The calculation and boundary status of single cells must be set with a status map,
-the following states are supportet:
-
-<ul>
-<li>0 == inactive - the cell with status 0 will not be calculated, active cells will have a no flow boundary to this cell</li>
-<li>1 == active - this cell is used for groundwater floaw calculation, inner sources and recharge can be defined for those cells</li>
-<li>2 == Dirichlet - cells of this type will have a fixed piezometric head value which do not change over the time </li>
-</ul>
-
-<br>
-<br>
-The groundwater flow equation can be solved with several solvers.
-Two iterative solvers with sparse and quadratic matrices support are implemented.
-The conjugate gradients (cg) method and the biconjugate gradients-stabilized (bicgstab) method.
-Aditionally a direct Gauss solver and LU solver are available. Those direct solvers
-only work with normal quadratic matrices, so be careful using them with large maps
-(maps of size 10.000 cells will need more than one gigabyte of RAM).
-Always prefer a sparse matrix solver.
-
-<h2>EXAMPLE</h2>
-Use this small script to create a working
-groundwater flow area and data. Make sure you are not in a lat/lon projection.
-
-<div class="code"><pre>
-# set the region accordingly
-g.region res=25 res3=25 t=100 b=0 n=1000 s=0 w=0 e=1000
-
-#now create the input raster maps for confined and unconfined aquifers
-r.mapcalc "phead=if(row() == 1 , 50, 40)"
-r.mapcalc "status=if(row() == 1 , 2, 1)"
-r.mapcalc "well=if(row() == 20 && col() == 20 , -0.001, 0)"
-r.mapcalc "hydcond=0.00025"
-r.mapcalc "recharge=0"
-r.mapcalc "top_conf=20.0"
-r.mapcalc "top_unconf=70.0"
-r.mapcalc "bottom=0.0"
-r.mapcalc "null=0.0"
-r.mapcalc "poros=0.15"
-r.mapcalc "syield=0.0001"
-
-#confined groundwater flow with cg solver and sparse matrix
-r.gwflow --o -s solver=cg top=top_conf bottom=bottom phead=phead status=status \
-hc_x=hydcond hc_y=hydcond q=well s=syield r=recharge output=gwresult_conf \
-dt=8640000 type=confined velocity=gwresult_conf_velocity
-
-#unconfined groundwater flow with cg solver and sparse matrix
-r.gwflow --o -s solver=cg top=top_unconf bottom=bottom phead=phead \
-status=status hc_x=hydcond hc_y=hydcond q=well s=poros r=recharge \
-output=gwresult_unconf dt=8640000 type=unconfined velocity=gwresult_unconf_velocity
-
-# The data can be visulaized with paraview when exported with r.out.vtk
-r.out.vtk -p in=gwresult_conf,status vector=gwresult_conf_velocity_x,gwresult_conf_velocity_y,null out=/tmp/gwdata_conf2d.vtk
-r.out.vtk -p elevation=gwresult_unconf in=gwresult_unconf,status vector=gwresult_unconf_velocity_x,gwresult_unconf_velocity_y,null out=/tmp/gwdata_unconf2d.vtk
-
-#now load the data into paraview
-paraview --data=/tmp/gwdata_conf2d.vtk &
-paraview --data=/tmp/gwdata_unconf2d.vtk &
-</pre></div>
-
-<h2>SEE ALSO</h2>
-
-<em><a href="r3.gwflow.html">r3.gwflow</a></em><br>
-<em><a href="r.out.vtk.html">r.out.vtk</a></em><br>
-
-<h2>AUTHOR</h2>
-Soeren Gebbert
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.gwflow/r.gwflow.html (from rev 32770, grass/trunk/raster/r.gwflow/description.html)
===================================================================
--- grass/trunk/raster/r.gwflow/r.gwflow.html (rev 0)
+++ grass/trunk/raster/r.gwflow/r.gwflow.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,120 @@
+<h2>DESCRIPTION</h2>
+This numerical program calculates transient, confined and
+unconfined groundwater flow in two dimensions based on
+raster maps and the current region resolution.
+All initial and boundary conditions must be provided as
+raster maps.
+
+<p>
+<center>
+<img src=r_gwflow_concept.png border=0><br>
+<table border=0 width=700>
+<tr><td><center>
+<i>Workflow of r.gwflow</i>
+</center></td></tr>
+</table>
+</center>
+<p>
+
+<em>r.gwflow</em> calculates the piezometric head and optionally the
+filter velocity field, based on the hydraulic conductivity and the piezometric head.
+The vector components can be visualized with paraview if they are exported
+with <em>r.out.vtk</em>.
+<br>
+<br>
+The groundwater flow will always be calculated transient.
+If you want to calculate stady state, set the timestep
+to a large number (billions of seconds) or set the
+specific yield/ effective porosity raster maps to zero.
+
+
+<h2>NOTES</h2>
+
+The groundwater flow calculation is based on Darcy's law and a
+finite volume discretization. The solved groundwater flow partial
+differential equation is of the following form:
+
+<p>
+(dh/dt)*Ss = Kxx * (d^2h/dx^2) + Kyy * (d^2h/dy^2) + q
+
+<ul>
+<li>h -- the piezometric head im [m]</li>
+<li>dt -- the time step for transient calculation in [s]</li>
+<li>S -- the specific yield [1/m]</li>
+<li>Kxx -- the hydraulic conductivity tensor part in x direction in [m/s]</li>
+<li>Kyy -- the hydraulic conductivity tensor part in y direction in [m/s]</li>
+<li>q - inner source in meter per second [1/s]</li>
+</ul>
+
+<br>
+<br>
+Two different boundary conditions are implemented,
+the Dirichlet and Neumann conditions. By default the calculation area is surrounded by homogeneous Neumann boundary conditions.
+The calculation and boundary status of single cells must be set with a status map,
+the following states are supportet:
+
+<ul>
+<li>0 == inactive - the cell with status 0 will not be calculated, active cells will have a no flow boundary to this cell</li>
+<li>1 == active - this cell is used for groundwater floaw calculation, inner sources and recharge can be defined for those cells</li>
+<li>2 == Dirichlet - cells of this type will have a fixed piezometric head value which do not change over the time </li>
+</ul>
+
+<br>
+<br>
+The groundwater flow equation can be solved with several solvers.
+Two iterative solvers with sparse and quadratic matrices support are implemented.
+The conjugate gradients (cg) method and the biconjugate gradients-stabilized (bicgstab) method.
+Aditionally a direct Gauss solver and LU solver are available. Those direct solvers
+only work with normal quadratic matrices, so be careful using them with large maps
+(maps of size 10.000 cells will need more than one gigabyte of RAM).
+Always prefer a sparse matrix solver.
+
+<h2>EXAMPLE</h2>
+Use this small script to create a working
+groundwater flow area and data. Make sure you are not in a lat/lon projection.
+
+<div class="code"><pre>
+# set the region accordingly
+g.region res=25 res3=25 t=100 b=0 n=1000 s=0 w=0 e=1000
+
+#now create the input raster maps for confined and unconfined aquifers
+r.mapcalc "phead=if(row() == 1 , 50, 40)"
+r.mapcalc "status=if(row() == 1 , 2, 1)"
+r.mapcalc "well=if(row() == 20 && col() == 20 , -0.001, 0)"
+r.mapcalc "hydcond=0.00025"
+r.mapcalc "recharge=0"
+r.mapcalc "top_conf=20.0"
+r.mapcalc "top_unconf=70.0"
+r.mapcalc "bottom=0.0"
+r.mapcalc "null=0.0"
+r.mapcalc "poros=0.15"
+r.mapcalc "syield=0.0001"
+
+#confined groundwater flow with cg solver and sparse matrix
+r.gwflow --o -s solver=cg top=top_conf bottom=bottom phead=phead status=status \
+hc_x=hydcond hc_y=hydcond q=well s=syield r=recharge output=gwresult_conf \
+dt=8640000 type=confined velocity=gwresult_conf_velocity
+
+#unconfined groundwater flow with cg solver and sparse matrix
+r.gwflow --o -s solver=cg top=top_unconf bottom=bottom phead=phead \
+status=status hc_x=hydcond hc_y=hydcond q=well s=poros r=recharge \
+output=gwresult_unconf dt=8640000 type=unconfined velocity=gwresult_unconf_velocity
+
+# The data can be visulaized with paraview when exported with r.out.vtk
+r.out.vtk -p in=gwresult_conf,status vector=gwresult_conf_velocity_x,gwresult_conf_velocity_y,null out=/tmp/gwdata_conf2d.vtk
+r.out.vtk -p elevation=gwresult_unconf in=gwresult_unconf,status vector=gwresult_unconf_velocity_x,gwresult_unconf_velocity_y,null out=/tmp/gwdata_unconf2d.vtk
+
+#now load the data into paraview
+paraview --data=/tmp/gwdata_conf2d.vtk &
+paraview --data=/tmp/gwdata_unconf2d.vtk &
+</pre></div>
+
+<h2>SEE ALSO</h2>
+
+<em><a href="r3.gwflow.html">r3.gwflow</a></em><br>
+<em><a href="r.out.vtk.html">r.out.vtk</a></em><br>
+
+<h2>AUTHOR</h2>
+Soeren Gebbert
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.his/description.html
===================================================================
--- grass/trunk/raster/r.his/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.his/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,126 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<i>his</i> stands for hue, intensity, and saturation.
-This program produces red, green and blue raster map layers
-providing a visually pleasing combination of hue,
-intensity, and saturation values from two or three
-user-specified raster map layers.
-
-<p>
-
-The human brain automatically interprets the vast amount of
-visual information available according to basic rules.
-Color, or <i>hue</i>, is used to categorize objects.
-Shading, or <i>intensity</i>, is interpreted as
-three-dimensional texturing. Finally, the degree of
-haziness, or <i>saturation</i>, is associated with
-distance or depth. This program allows data from up to
-three raster map layers to be combined into a color image
-(in the form of separate red, green and blue raster map
-layers) which retains the original information in terms of
-<i>hue</i>, <i>intensity</i>, and <i>saturation</i>.
-
-<p>
-
-While any raster map layer can be used to represent the hue
-information, map layers with a few very distinct colors
-work best. Only raster map layers representing
-continuously varying data like elevation, aspect, weights,
-intensities, or amounts can suitably be used to provide
-intensity and saturation information.
-
-<p>
-
-For example, a visually pleasing image can be made by using
-a watershed map for the <i>hue</i> factor, an aspect map
-for the <i>intensity</i> factor, and an elevation map for
-<i>saturation</i>. (The user may wish to leave out the
-elevation information for a first try.) Ideally, the
-resulting image should resemble the view from an aircraft
-looking at a terrain on a sunny day with a bit of haze in
-the valleys.
-
-<h3>The Process</h3>
-
-Each map cell is processed individually. First, the working
-color is set to the color of the corresponding cell in the
-map layer chosen to represent <i>HUE</i>. Second, this
-color is multiplied by the <i>red</i> intensity of that
-cell in the <i>INTENSITY</i> map layer. This map layer
-should have an appropriate gray-scale color table
-associated with it. You can ensure this by using the color
-manipulation capabilities of
-<em><a href="d.colors.html">d.colors</a></em> or
-<em><a href="r.colors.html">r.colors</a></em>.
-Finally, the color is made somewhat gray-based on the
-<i>red</i> intensity of that cell in the
-<i>SATURATION</i> map layer. Again, this map layer
-should have a gray-scale color table associated with it.
-
-<h2>NOTES</h2>
-
-The name is misleading. The actual conversion used is
-
-<pre>
- <u>H</u>.i.s + <u>G</u>.(1-s)
-
-where
-
- <u>H</u> is the R,G,B color from the hue map
- i is the red value from the intensity map
- s is the red value from the saturation map
- <u>G</u> is 50% gray (R = G = B = 0.5)
-
-</pre>
-
-<p>
-
-Either (but not both) of the intensity or the saturation
-map layers may be omitted. This means that it is possible
-to produce output images that represent combinations of
-<i>his, hi,</i> or <i>hs</i>.
-
-The separate <i>red</i>, <i>green</i> and <i>blue</i>
-maps can be displayed on the graphics monitor using
-<em><a href="d.rgb.html">d.rgb</a></em>, or combined into
-a composite RGB layer using
-<em><a href="r.composite.html">r.composite</a></em>.
-
-Users wishing to simply display an <i>his</i> composite
-image without actually generating any layers should use the
-program <em><a href="d.his.html">d.his</a></em>.
-
-
-<h2>EXAMPLE</h2>
-
-Recreate the following <em>d.his</em> command using <em>r.his</em>:
-<div class="code"><pre>
- r.shaded.relief map=elevation.dem shad=elev.shad_relf
- d.his h=elevation.dem i=elev.shad_relf brighten=50
-</pre></div>
-
-<div class="code"><pre>
- r.mapcalc 'elev.shad_relf_bright50 = #elev.shad_relf * 1.5'
- r.colors elev.shad_relf_bright50 color=grey255
- r.his h_map=elevation.dem i_map=elev.shad_relf_bright50 r_map=esr.r g_map=esr.g bmap=esr.b
- d.rgb red=esr.r green=esr.g blue=esr.b
-</pre></div>
-
-
-<h2>SEE ALSO</h2>
-
-<em><a href="d.his.html">d.his</a></em>,
-<em><a href="d.colors.html">d.colors</a></em>,
-<em><a href="d.colortable.html">d.colortable</a></em>,
-<em><a href="d.rgb.html">d.rgb</a></em>,
-<em><a href="r.blend.html">r.blend</a></em>,
-<em><a href="r.colors.html">r.colors</a></em>,
-<em><a href="r.composite.html">r.composite</a></em>
-<em><a href="i.his.rgb.html">i.his.rgb</a></em>,
-<em><a href="i.rgb.his.html">i.rgb.his</a></em>
-
-<h2>AUTHOR</h2>
-
-Glynn Clements (based upon <em><a href="d.his.html">d.his</a></em>)
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.his/r.his.html (from rev 32770, grass/trunk/raster/r.his/description.html)
===================================================================
--- grass/trunk/raster/r.his/r.his.html (rev 0)
+++ grass/trunk/raster/r.his/r.his.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,126 @@
+<h2>DESCRIPTION</h2>
+
+<i>his</i> stands for hue, intensity, and saturation.
+This program produces red, green and blue raster map layers
+providing a visually pleasing combination of hue,
+intensity, and saturation values from two or three
+user-specified raster map layers.
+
+<p>
+
+The human brain automatically interprets the vast amount of
+visual information available according to basic rules.
+Color, or <i>hue</i>, is used to categorize objects.
+Shading, or <i>intensity</i>, is interpreted as
+three-dimensional texturing. Finally, the degree of
+haziness, or <i>saturation</i>, is associated with
+distance or depth. This program allows data from up to
+three raster map layers to be combined into a color image
+(in the form of separate red, green and blue raster map
+layers) which retains the original information in terms of
+<i>hue</i>, <i>intensity</i>, and <i>saturation</i>.
+
+<p>
+
+While any raster map layer can be used to represent the hue
+information, map layers with a few very distinct colors
+work best. Only raster map layers representing
+continuously varying data like elevation, aspect, weights,
+intensities, or amounts can suitably be used to provide
+intensity and saturation information.
+
+<p>
+
+For example, a visually pleasing image can be made by using
+a watershed map for the <i>hue</i> factor, an aspect map
+for the <i>intensity</i> factor, and an elevation map for
+<i>saturation</i>. (The user may wish to leave out the
+elevation information for a first try.) Ideally, the
+resulting image should resemble the view from an aircraft
+looking at a terrain on a sunny day with a bit of haze in
+the valleys.
+
+<h3>The Process</h3>
+
+Each map cell is processed individually. First, the working
+color is set to the color of the corresponding cell in the
+map layer chosen to represent <i>HUE</i>. Second, this
+color is multiplied by the <i>red</i> intensity of that
+cell in the <i>INTENSITY</i> map layer. This map layer
+should have an appropriate gray-scale color table
+associated with it. You can ensure this by using the color
+manipulation capabilities of
+<em><a href="d.colors.html">d.colors</a></em> or
+<em><a href="r.colors.html">r.colors</a></em>.
+Finally, the color is made somewhat gray-based on the
+<i>red</i> intensity of that cell in the
+<i>SATURATION</i> map layer. Again, this map layer
+should have a gray-scale color table associated with it.
+
+<h2>NOTES</h2>
+
+The name is misleading. The actual conversion used is
+
+<pre>
+ <u>H</u>.i.s + <u>G</u>.(1-s)
+
+where
+
+ <u>H</u> is the R,G,B color from the hue map
+ i is the red value from the intensity map
+ s is the red value from the saturation map
+ <u>G</u> is 50% gray (R = G = B = 0.5)
+
+</pre>
+
+<p>
+
+Either (but not both) of the intensity or the saturation
+map layers may be omitted. This means that it is possible
+to produce output images that represent combinations of
+<i>his, hi,</i> or <i>hs</i>.
+
+The separate <i>red</i>, <i>green</i> and <i>blue</i>
+maps can be displayed on the graphics monitor using
+<em><a href="d.rgb.html">d.rgb</a></em>, or combined into
+a composite RGB layer using
+<em><a href="r.composite.html">r.composite</a></em>.
+
+Users wishing to simply display an <i>his</i> composite
+image without actually generating any layers should use the
+program <em><a href="d.his.html">d.his</a></em>.
+
+
+<h2>EXAMPLE</h2>
+
+Recreate the following <em>d.his</em> command using <em>r.his</em>:
+<div class="code"><pre>
+ r.shaded.relief map=elevation.dem shad=elev.shad_relf
+ d.his h=elevation.dem i=elev.shad_relf brighten=50
+</pre></div>
+
+<div class="code"><pre>
+ r.mapcalc 'elev.shad_relf_bright50 = #elev.shad_relf * 1.5'
+ r.colors elev.shad_relf_bright50 color=grey255
+ r.his h_map=elevation.dem i_map=elev.shad_relf_bright50 r_map=esr.r g_map=esr.g bmap=esr.b
+ d.rgb red=esr.r green=esr.g blue=esr.b
+</pre></div>
+
+
+<h2>SEE ALSO</h2>
+
+<em><a href="d.his.html">d.his</a></em>,
+<em><a href="d.colors.html">d.colors</a></em>,
+<em><a href="d.colortable.html">d.colortable</a></em>,
+<em><a href="d.rgb.html">d.rgb</a></em>,
+<em><a href="r.blend.html">r.blend</a></em>,
+<em><a href="r.colors.html">r.colors</a></em>,
+<em><a href="r.composite.html">r.composite</a></em>
+<em><a href="i.his.rgb.html">i.his.rgb</a></em>,
+<em><a href="i.rgb.his.html">i.rgb.his</a></em>
+
+<h2>AUTHOR</h2>
+
+Glynn Clements (based upon <em><a href="d.his.html">d.his</a></em>)
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.in.arc/description.html
===================================================================
--- grass/trunk/raster/r.in.arc/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.in.arc/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,52 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>r.in.arc</em> allows a user to create a (binary) GRASS raster map layer
-from an ESRI ARC/INFO ascii GRID file with (optional) title.
-
-<p>
-
-The ARC/INFO ascii GRID file header has 6 lines (last line optional):
-<div class="code"><pre>
- ncols:
- nrows:
- xllcorner:
- yllcorner:
- cellsize:
- nodata_value:
-</pre></div>
-
-or alternatively (not supported by <em>r.in.arc</em>, but by
-<i><a href=r.in.gdal.html>r.in.gdal</a></i>, last line optional):
-
-<div class="code"><pre>
- ncols:
- nrows:
- xllcenter:
- yllcenter:
- cellsize:
- nodata_value:
-</pre></div>
-
-<h2>NOTES</h2>
-
-<em>r.in.arc</em> handles floating point cell values. The <b>mult</b>
-option allows the number of significant figures of a floating point cell
-to be increased before importing. Multiples of ten are the most functional
-multipliers.
-
-<h2>EXAMPLE</h2>
-
-To import a ARC/INFO ascii grid, applying a 10x multiplier during import, with title:
-<div class="code"><pre>
-r.in.arc input=elev_meters.asc output=elev_decimeters title="Elevation data converted to decimeters" mult=10
-</div></pre>
-
-<h2>SEE ALSO</h2>
-
-<i><a href="r.in.gdal.html">r.in.gdal</a></i>
-<i><a href="r.out.arc.html">r.out.arc</a></i>
-
-<h2>AUTHOR</h2>
-Unknown German author, updated by Bill Brown to floating point support.
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.in.arc/r.in.arc.html (from rev 32770, grass/trunk/raster/r.in.arc/description.html)
===================================================================
--- grass/trunk/raster/r.in.arc/r.in.arc.html (rev 0)
+++ grass/trunk/raster/r.in.arc/r.in.arc.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,52 @@
+<h2>DESCRIPTION</h2>
+
+<em>r.in.arc</em> allows a user to create a (binary) GRASS raster map layer
+from an ESRI ARC/INFO ascii GRID file with (optional) title.
+
+<p>
+
+The ARC/INFO ascii GRID file header has 6 lines (last line optional):
+<div class="code"><pre>
+ ncols:
+ nrows:
+ xllcorner:
+ yllcorner:
+ cellsize:
+ nodata_value:
+</pre></div>
+
+or alternatively (not supported by <em>r.in.arc</em>, but by
+<i><a href=r.in.gdal.html>r.in.gdal</a></i>, last line optional):
+
+<div class="code"><pre>
+ ncols:
+ nrows:
+ xllcenter:
+ yllcenter:
+ cellsize:
+ nodata_value:
+</pre></div>
+
+<h2>NOTES</h2>
+
+<em>r.in.arc</em> handles floating point cell values. The <b>mult</b>
+option allows the number of significant figures of a floating point cell
+to be increased before importing. Multiples of ten are the most functional
+multipliers.
+
+<h2>EXAMPLE</h2>
+
+To import a ARC/INFO ascii grid, applying a 10x multiplier during import, with title:
+<div class="code"><pre>
+r.in.arc input=elev_meters.asc output=elev_decimeters title="Elevation data converted to decimeters" mult=10
+</div></pre>
+
+<h2>SEE ALSO</h2>
+
+<i><a href="r.in.gdal.html">r.in.gdal</a></i>
+<i><a href="r.out.arc.html">r.out.arc</a></i>
+
+<h2>AUTHOR</h2>
+Unknown German author, updated by Bill Brown to floating point support.
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.in.ascii/description.html
===================================================================
--- grass/trunk/raster/r.in.ascii/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.in.ascii/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,121 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>r.in.ascii</em> allows a user to create a (binary) GRASS raster map
-layer from an ASCII raster input file with (optional) TITLE.
-
-<p>
-
-The GRASS ASCII <b>input</b> file has a header section which describes
-the location and size of the data, followed by the data itself.
-
-<p>
-
-The header has 6 lines:
-
-<div class="code"><pre>
-north: xxxxxx.xx
-south: xxxxxx.xx
-east: xxxxxx.xx
-west: xxxxxx.xx
-rows: r
-cols: c
-</pre></div>
-
-The north, south, east, and west field values entered
-are the coordinates of the edges of the geographic region.
-The rows and cols field values entered describe the dimensions
-of the matrix of data to follow.
-The data which follows is <em>r</em> rows of <em>c</em> integers.
-
-<p>
-
-Optionally the following parameters can be defined in the header section:
-
-<div class="code"><pre>
-null: nn
-type: float
-multiplier: 2.
-</pre></div>
-
-<p>
-
-"null" defines a string or number to be converted to NULL value (no
-data).<br>
-"type" defines the data type (int, float double) and is not required.<br>
-"multiplier" is an optional parameter to multiply each cell value.
-
-<h2>NOTES</h2>
-
-The geographic coordinates north, south, east, and west
-describe the outer edges of the geographic region. They
-run along the edges of the cells at the edge of the
-geographic region and <em>not</em> through the center of the cells
-at the edges.
-The NW value occurs at the beginning of the first line of data, and the
-SW value occurs at the beginning of the last line of data.
-
-<p>
-
-The data (which follows the header section) must contain
-<tt>r</tt> <em>x</em> <tt>c</tt> values, but it is not necessary
-that all the data for a row be on one line. A row may be
-split over many lines.
-
-<p>
-
-<em>r.in.ascii</em> may import <i>integer</i>, <i>floating point</i>, or <i>double</i> cell
-types using the <b>-i</b>, <b>-f</b>, and <b>-d</b> flags, respectively.
-
-<p>
-
-The header information in ESRI Raster ASCII files differs from GRASS.
-To convert an Arc/Info (ArcView) ASCII grid file into GRASS, see
-<em><a href="r.in.arc.html">r.in.arc</a></em>.
-
-<p>
-
-SURFER (Golden Software) ASCII files may be imported by passing the <b>-s</b> flag.
-
-<h2>EXAMPLE</h2>
-
-The following is a sample <b>input</b> file to <em>r.in.ascii</em>:
-
-<div class="code"><pre>
-north: 4299000.00
-south: 4247000.00
-east: 528000.00
-west: 500000.00
-rows: 10
-cols: 15
-null: -9999
-
-1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
-1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
-1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
-1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
-1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
-1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
-1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
-1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
-1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
-1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
-</pre></div>
-
-<h2>SEE ALSO</h2>
-
-<em>
-<a href="r.out.ascii.html">r.out.ascii</a>,
-<a href="r.in.arc.html">r.in.arc</a>,
-<a href="r.in.gdal.html">r.in.gdal</a>,
-<a href="r.out.arc.html">r.out.arc</a>,
-<a href="r.in.bin.html">r.in.bin</a>,
-<a href="r3.in.ascii.html">r3.in.ascii</a></em>,
-<a href="http://grass.itc.it/gdp/html_grass5/ascii_formats.html">GRASS ASCII formats</a>
-</em>
-
-<h2>AUTHOR</h2>
-
-Michael Shapiro, U.S. Army Construction Engineering Research Laboratory<br>
-Surfer support by Roger Miller
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.in.ascii/r.in.ascii.html (from rev 32770, grass/trunk/raster/r.in.ascii/description.html)
===================================================================
--- grass/trunk/raster/r.in.ascii/r.in.ascii.html (rev 0)
+++ grass/trunk/raster/r.in.ascii/r.in.ascii.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,121 @@
+<h2>DESCRIPTION</h2>
+
+<em>r.in.ascii</em> allows a user to create a (binary) GRASS raster map
+layer from an ASCII raster input file with (optional) TITLE.
+
+<p>
+
+The GRASS ASCII <b>input</b> file has a header section which describes
+the location and size of the data, followed by the data itself.
+
+<p>
+
+The header has 6 lines:
+
+<div class="code"><pre>
+north: xxxxxx.xx
+south: xxxxxx.xx
+east: xxxxxx.xx
+west: xxxxxx.xx
+rows: r
+cols: c
+</pre></div>
+
+The north, south, east, and west field values entered
+are the coordinates of the edges of the geographic region.
+The rows and cols field values entered describe the dimensions
+of the matrix of data to follow.
+The data which follows is <em>r</em> rows of <em>c</em> integers.
+
+<p>
+
+Optionally the following parameters can be defined in the header section:
+
+<div class="code"><pre>
+null: nn
+type: float
+multiplier: 2.
+</pre></div>
+
+<p>
+
+"null" defines a string or number to be converted to NULL value (no
+data).<br>
+"type" defines the data type (int, float double) and is not required.<br>
+"multiplier" is an optional parameter to multiply each cell value.
+
+<h2>NOTES</h2>
+
+The geographic coordinates north, south, east, and west
+describe the outer edges of the geographic region. They
+run along the edges of the cells at the edge of the
+geographic region and <em>not</em> through the center of the cells
+at the edges.
+The NW value occurs at the beginning of the first line of data, and the
+SW value occurs at the beginning of the last line of data.
+
+<p>
+
+The data (which follows the header section) must contain
+<tt>r</tt> <em>x</em> <tt>c</tt> values, but it is not necessary
+that all the data for a row be on one line. A row may be
+split over many lines.
+
+<p>
+
+<em>r.in.ascii</em> may import <i>integer</i>, <i>floating point</i>, or <i>double</i> cell
+types using the <b>-i</b>, <b>-f</b>, and <b>-d</b> flags, respectively.
+
+<p>
+
+The header information in ESRI Raster ASCII files differs from GRASS.
+To convert an Arc/Info (ArcView) ASCII grid file into GRASS, see
+<em><a href="r.in.arc.html">r.in.arc</a></em>.
+
+<p>
+
+SURFER (Golden Software) ASCII files may be imported by passing the <b>-s</b> flag.
+
+<h2>EXAMPLE</h2>
+
+The following is a sample <b>input</b> file to <em>r.in.ascii</em>:
+
+<div class="code"><pre>
+north: 4299000.00
+south: 4247000.00
+east: 528000.00
+west: 500000.00
+rows: 10
+cols: 15
+null: -9999
+
+1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
+1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
+1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
+1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
+1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
+1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
+1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
+1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
+1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
+1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
+</pre></div>
+
+<h2>SEE ALSO</h2>
+
+<em>
+<a href="r.out.ascii.html">r.out.ascii</a>,
+<a href="r.in.arc.html">r.in.arc</a>,
+<a href="r.in.gdal.html">r.in.gdal</a>,
+<a href="r.out.arc.html">r.out.arc</a>,
+<a href="r.in.bin.html">r.in.bin</a>,
+<a href="r3.in.ascii.html">r3.in.ascii</a></em>,
+<a href="http://grass.itc.it/gdp/html_grass5/ascii_formats.html">GRASS ASCII formats</a>
+</em>
+
+<h2>AUTHOR</h2>
+
+Michael Shapiro, U.S. Army Construction Engineering Research Laboratory<br>
+Surfer support by Roger Miller
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.in.bin/description.html
===================================================================
--- grass/trunk/raster/r.in.bin/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.in.bin/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,134 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-
-<em>r.in.bin</em> allows a user to create a (binary) GRASS raster map layer
-from a variety of binary raster data formats.
-
-<p>
-The <b> -s</b> flag is used for importing two's-complement signed data.
-<p>
-The <b> -h</b> flag is used to read region information from a Generic
-Mapping Tools (GMT) type binary header. It is compatible with GMT binary
-grid types 1 and 2.
-<p>
-The north, south, east, and west field values entered
-are the coordinates of the edges of the geographic region.
-The rows and cols field values entered describe the dimensions
-of the matrix of data to follow. If input is a
-<a href=http://gmt.soest.hawaii.edu/>GMT</a> binary array
-(-h flag), the six dimension fields are obtained from the GMT header.
-If the bytes field is entered incorrectly an error will be generated
-suggesting a closer bytes value.
-
-<p>
-<em>r.in.bin</em> can be used to import numerous binary arrays including:
-ETOPO30, ETOPO-5, ETOPO-2, Globe DEM, BIL, AVHRR and GMT binary arrays (ID 1 & 2)
-<p>
-
-<h2>NOTES</h2>
-
-If optional parameters are not supplied, <b>r.in.bin</b> attempts
-to calculate them. For example if the rows and columns parameters are
-not entered, <b>r.in.bin</b> automatically calculates them by subtracting
-south from north and west from east. This will only produce correct
-results if the raster resolution equals 1. Also, if the north, south,
-east, and west parameters are not entered, <b>r.in.bin</b> assigns
-them from the rows and columns parameters. In the above AVHRR example,
-the raster would be assigned a north=128, south=0, east=128, west=0.
-<p>
-The geographic coordinates north, south, east, and west
-describe the outer edges of the geographic region. They
-run along the edges of the cells at the edge of the
-geographic region and <em>not</em> through the center of the cells
-at the edges.
-<p>
-Eastern limit of geographic region (in projected coordinates must be east
-of the west parameter value, but in geographical coordinates will wrap
-around the globe; user errors can be detected by comparing the <em>ewres</em> and
-<em>nsres</em> values of the imported map layer carefully).
-<br>
-Western limit of geographic region (in projected coordinates must be west
-of the east parameter value, but in geographical coordinates will wrap
-around the globe; user errors can be detected by comparing the <em>ewres</em> and
-<em>nsres</em> values of the imported map layer carefully).
-<p>
-Notes on (non)signed data:<p>
-If you use the -s flag the highest bit is the sign bit. If this is 1 the
-data is negative, and the data interval is half of the unsigned (not
-exactly).
-<p>
-This flag is only used if <b>bytes=</b> 1. If <b>bytes=</b> is greater
-than 1 the flag is ignored.
-
-<h2>EXAMPLES</h2>
-
-<h3>GTOPO30 DEM</h3>
-The following is a sample call of <em>r.in.bin</em> to import
-<a href=http://edcdaac.usgs.gov/gtopo30/gtopo30.asp>GTOPO30 DEM</a>
-data:
-<p>
-<div class="code"><pre>
-r.in.bin -sb input=E020N90.DEM output=gtopo30 bytes=2 north=90 south=40
-east=60 west=20 r=6000 c=4800
-</pre></div>
-
-<p>
-(you can add "anull=-9999" if you want sea level to have a NULL value)
-
-<h3>GMT</h3>
-The following is a sample call of <em>r.in.bin</em> to import a GMT
-type 1 (float) binary array:
-<p>
-<div class="code"><pre>
-r.in.bin -hf input=sample.grd output=sample.grass
-</pre></div>
-<p>
-(-b could be used to swap bytes if required)
-
-<h3>AVHRR</h3>
-The following is a sample call of <em>r.in.bin</em> to import an AVHRR image:
-<p>
-<div class="code"><pre>
-r.in.bin in=p07_b6.dat out=avhrr c=128 r=128
-</pre></div>
-
-
-<h3>ETOPO2</h3>
-The following is a sample call of <em>r.in.bin</em> to import
-<a href=http://www.ngdc.noaa.gov/mgg/image/2minrelief.html>ETOPO2 DEM</a> data (here full data set):
-<p>
-<div class="code"><pre>
-r.in.bin ETOPO2.dos.bin out=ETOPO2min r=5400 c=10800 n=90 s=-90 w=-180 e=180 bytes=2
-r.colors ETOPO2min rules=terrain
-</pre></div>
-
-<h3>TOPEX/SRTM30 PLUS</h3>
-The following is a sample call of <em>r.in.bin</em> to import
-<a href="http://topex.ucsd.edu/WWW_html/srtm30_plus.html">SRTM30 PLUS</a> data:
-<p>
-<div class="code"><pre>
-r.in.bin -sb input=e020n40.Bathmetry.srtm output=e020n40_topex \
- bytes=2 north=40 south=-10 east=60 west=20 r=6000 c=4800
-r.colors e020n40_topex rules=etopo2
-</pre></div>
-
-
-<h2>SEE ALSO</h2>
-
-<em>
-<a href="r.out.bin.html">r.out.bin</a>,
-<a href="r.in.ascii.html">r.in.ascii</a>,
-<a href="r.out.ascii.html">r.out.ascii</a>,
-<a href="r.in.arc.html">r.in.arc</a>,
-<a href="r.out.arc.html">r.out.arc</a>,
-<a href="r.in.gdal.html">r.in.gdal</a>,
-<a href="r.out.gdal.html">r.out.gdal</a>,
-<a href="r.in.srtm.html">r.in.srtm</a>
-</em>
-
-<h2>AUTHORS</h2>
-
-Jacques Bouchard, France (bouchard at onera.fr)<br>
-Bob Covill, Canada (bcovill at tekmap.ns.ca)<br>
-Man page: Zsolt Felker (felker at c160.pki.matav.hu)
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.in.bin/r.in.bin.html (from rev 32770, grass/trunk/raster/r.in.bin/description.html)
===================================================================
--- grass/trunk/raster/r.in.bin/r.in.bin.html (rev 0)
+++ grass/trunk/raster/r.in.bin/r.in.bin.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,134 @@
+<h2>DESCRIPTION</h2>
+
+
+<em>r.in.bin</em> allows a user to create a (binary) GRASS raster map layer
+from a variety of binary raster data formats.
+
+<p>
+The <b> -s</b> flag is used for importing two's-complement signed data.
+<p>
+The <b> -h</b> flag is used to read region information from a Generic
+Mapping Tools (GMT) type binary header. It is compatible with GMT binary
+grid types 1 and 2.
+<p>
+The north, south, east, and west field values entered
+are the coordinates of the edges of the geographic region.
+The rows and cols field values entered describe the dimensions
+of the matrix of data to follow. If input is a
+<a href=http://gmt.soest.hawaii.edu/>GMT</a> binary array
+(-h flag), the six dimension fields are obtained from the GMT header.
+If the bytes field is entered incorrectly an error will be generated
+suggesting a closer bytes value.
+
+<p>
+<em>r.in.bin</em> can be used to import numerous binary arrays including:
+ETOPO30, ETOPO-5, ETOPO-2, Globe DEM, BIL, AVHRR and GMT binary arrays (ID 1 & 2)
+<p>
+
+<h2>NOTES</h2>
+
+If optional parameters are not supplied, <b>r.in.bin</b> attempts
+to calculate them. For example if the rows and columns parameters are
+not entered, <b>r.in.bin</b> automatically calculates them by subtracting
+south from north and west from east. This will only produce correct
+results if the raster resolution equals 1. Also, if the north, south,
+east, and west parameters are not entered, <b>r.in.bin</b> assigns
+them from the rows and columns parameters. In the above AVHRR example,
+the raster would be assigned a north=128, south=0, east=128, west=0.
+<p>
+The geographic coordinates north, south, east, and west
+describe the outer edges of the geographic region. They
+run along the edges of the cells at the edge of the
+geographic region and <em>not</em> through the center of the cells
+at the edges.
+<p>
+Eastern limit of geographic region (in projected coordinates must be east
+of the west parameter value, but in geographical coordinates will wrap
+around the globe; user errors can be detected by comparing the <em>ewres</em> and
+<em>nsres</em> values of the imported map layer carefully).
+<br>
+Western limit of geographic region (in projected coordinates must be west
+of the east parameter value, but in geographical coordinates will wrap
+around the globe; user errors can be detected by comparing the <em>ewres</em> and
+<em>nsres</em> values of the imported map layer carefully).
+<p>
+Notes on (non)signed data:<p>
+If you use the -s flag the highest bit is the sign bit. If this is 1 the
+data is negative, and the data interval is half of the unsigned (not
+exactly).
+<p>
+This flag is only used if <b>bytes=</b> 1. If <b>bytes=</b> is greater
+than 1 the flag is ignored.
+
+<h2>EXAMPLES</h2>
+
+<h3>GTOPO30 DEM</h3>
+The following is a sample call of <em>r.in.bin</em> to import
+<a href=http://edcdaac.usgs.gov/gtopo30/gtopo30.asp>GTOPO30 DEM</a>
+data:
+<p>
+<div class="code"><pre>
+r.in.bin -sb input=E020N90.DEM output=gtopo30 bytes=2 north=90 south=40
+east=60 west=20 r=6000 c=4800
+</pre></div>
+
+<p>
+(you can add "anull=-9999" if you want sea level to have a NULL value)
+
+<h3>GMT</h3>
+The following is a sample call of <em>r.in.bin</em> to import a GMT
+type 1 (float) binary array:
+<p>
+<div class="code"><pre>
+r.in.bin -hf input=sample.grd output=sample.grass
+</pre></div>
+<p>
+(-b could be used to swap bytes if required)
+
+<h3>AVHRR</h3>
+The following is a sample call of <em>r.in.bin</em> to import an AVHRR image:
+<p>
+<div class="code"><pre>
+r.in.bin in=p07_b6.dat out=avhrr c=128 r=128
+</pre></div>
+
+
+<h3>ETOPO2</h3>
+The following is a sample call of <em>r.in.bin</em> to import
+<a href=http://www.ngdc.noaa.gov/mgg/image/2minrelief.html>ETOPO2 DEM</a> data (here full data set):
+<p>
+<div class="code"><pre>
+r.in.bin ETOPO2.dos.bin out=ETOPO2min r=5400 c=10800 n=90 s=-90 w=-180 e=180 bytes=2
+r.colors ETOPO2min rules=terrain
+</pre></div>
+
+<h3>TOPEX/SRTM30 PLUS</h3>
+The following is a sample call of <em>r.in.bin</em> to import
+<a href="http://topex.ucsd.edu/WWW_html/srtm30_plus.html">SRTM30 PLUS</a> data:
+<p>
+<div class="code"><pre>
+r.in.bin -sb input=e020n40.Bathmetry.srtm output=e020n40_topex \
+ bytes=2 north=40 south=-10 east=60 west=20 r=6000 c=4800
+r.colors e020n40_topex rules=etopo2
+</pre></div>
+
+
+<h2>SEE ALSO</h2>
+
+<em>
+<a href="r.out.bin.html">r.out.bin</a>,
+<a href="r.in.ascii.html">r.in.ascii</a>,
+<a href="r.out.ascii.html">r.out.ascii</a>,
+<a href="r.in.arc.html">r.in.arc</a>,
+<a href="r.out.arc.html">r.out.arc</a>,
+<a href="r.in.gdal.html">r.in.gdal</a>,
+<a href="r.out.gdal.html">r.out.gdal</a>,
+<a href="r.in.srtm.html">r.in.srtm</a>
+</em>
+
+<h2>AUTHORS</h2>
+
+Jacques Bouchard, France (bouchard at onera.fr)<br>
+Bob Covill, Canada (bcovill at tekmap.ns.ca)<br>
+Man page: Zsolt Felker (felker at c160.pki.matav.hu)
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.in.gdal/description.html
===================================================================
--- grass/trunk/raster/r.in.gdal/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.in.gdal/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,260 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>r.in.gdal</em> allows a user to create a (binary) GRASS raster map layer,
-or imagery group, from any GDAL supported raster map format, with an optional
-title. The imported file may also be optionally used to create a new location.
-
-<!--<h2>OPTIONS</h2>
-
-Extended explanations:
-
-<h3>Flags:</h3>
-
-<dt><b>-e</b>
-<dd>Extend the DEFAULT_WIND in PERMANENT mapset to include the region of
-the new map layer. Old resolution is preserved, but the region, and rows/cols
-are updated. This will fail if the user doesn't have write access to the
-PERMANENT mapset.
-</dl>-->
-
-<h3>GDAL supported raster formats</h3>
-
-Full details on GDAL supported formats are available at:<p>
-
-<a href="http://www.gdal.org/formats_list.html">http://www.gdal.org/formats_list.html</a><p>
-
-Selected formats of more than 80 supported formats:
-<div class="code"><pre>
-
-Long Format Name Code Creation Georeferencing Maximum File Size
-
-Arc/Info ASCII Grid AAIGrid Yes Yes No limits
-Arc/Info Binary Grid AIG No Yes --
-AIRSAR Polarimetric AIRSAR No No --
-Microsoft Windows Device Independent Bitmap (.bmp) BMP Yes Yes 4GiB
-BSB Nautical Chart Format (.kap) BSB No Yes --
-VTP Binary Terrain Format (.bt) BT Yes Yes --
-CEOS (Spot for instance) CEOS No No --
-First Generation USGS DOQ (.doq) DOQ1 No Yes --
-New Labelled USGS DOQ (.doq) DOQ2 No Yes --
-Data (.dt0, .dt1) DTED No Yes --
-ERMapper Compressed Wavelets (.ecw) ECW Yes Yes
-ESRI .hdr Labelled EHdr No Yes --
-ENVI .hdr Labelled Raster ENVI Yes Yes No limits
-Envisat Image Product (.n1) Envisat No No --
-EOSAT FAST Format FAST No Yes --
-FITS (.fits) FITS Yes No
-Graphics Interchange Format (.gif) GIF Yes No 2GB
-Arc/Info Binary Grid (.adf) GIO Yes Yes
-GRASS Rasters GRASS No Yes --
-TIFF / GeoTIFF (.tif) GTiff Yes Yes 4GiB
-Hierarchical Data Format Release 4 (HDF4) HDF4 Yes Yes 2GiB
-Erdas Imagine (.img) HFA Yes Yes No limits
-Atlantis MFF2e HKV Yes Yes No limits
-Image Display and Analysis (WinDisp) IDA Yes Yes 2GB
-ILWIS Raster Map (.mpr,.mpl) ILWIS Yes Yes --
-Japanese DEM (.mem) JDEM No Yes --
-JPEG JFIF (.jpg) JPEG Yes Yes 4GiB (max dimentions 65500x65500)
-JPEG2000 (.jp2, .j2k) JPEG2000 Yes Yes 2GiB
-JPEG2000 (.jp2, .j2k) JP2KAK Yes Yes No limits
-NOAA Polar Orbiter Level 1b Data Set (AVHRR) L1B No Yes --
-Erdas 7.x .LAN and .GIS LAN No Yes 2GB
-In Memory Raster MEM Yes Yes 2GiB
-Atlantis MFF MFF Yes Yes No limits
-Multi-resolution Seamless Image Database MrSID No Yes --
-NDF NLAPS Data Format No Yes No limits
-NITF NITF Yes Yes
-NetCDF netCDF Yes Yes 2GB
-OGDI Bridge OGDI No Yes --
-PCI .aux Labelled PAux Yes No No limits
-PCI Geomatics Database File PCIDSK Yes Yes No limits
-Portable Network Graphics (.png) PNG Yes No
-PCRaster (.map) PCRaster Yes No
-Netpbm (.ppm,.pgm) PNM Yes No No limits
-RadarSat2 XML (product.xml) RS2 No Yes 4GB
-USGS SDTS DEM (*CATD.DDF) SDTS No Yes --
-SAR CEOS SAR_CEOS No Yes --
-USGS ASCII DEM (.dem) USGSDEM No Yes --
-X11 Pixmap (.xpm) XPM Yes No
-</pre></div>
-
-<h3>Location Creation</h3>
-
-<em>r.in.gdal</em> attempts to preserve projection information when importing
-datasets if the source format includes projection information, and if
-the GDAL driver supports it. If the projection of the source dataset does
-not match the projection of the current location <em>r.in.gdal</em> will
-report an error message (<tt>Projection of dataset does not appear to
-match current location</tt>) and then report the PROJ_INFO parameters of
-the source dataset.
-
-<p>
-
-If the user wishes to ignore the difference between the apparent coordinate
-system of the source data and the current location, they may pass the
-<b>-o</b> flag to override the projection check.
-
-<p>
-
-If the user wishes to import the data with the full projection definition,
-it is possible to have r.in.gdal automatically create a new location based
-on the projection and extents of the file being read. This is accomplished
-by passing the name to be used for the new location via the <b>location</b>
-parameter. Upon completion of the command, a new location will have been
-created (with only a PERMANENT mapset), and the raster will have been
-imported with the indicated <b>output</b> name into the PERMANENT mapset.
-
-<p>
-
-Support for GCPs: In case the image contains GCPs they are written to a
-POINTS file within an imagery group. They can directly be used for
-<a href=i.rectify.html>i.rectify</a>. The <b>target</b> option allows to
-automatically re-project the GCPs from their own projection into another
-projection read from the PROJ_INFO file of the location name
-<b>target</b>.
-
-<h2>NOTES</h2>
-
-Planned improvements to <em>r.in.gdal</em> in the future include support for
-reporting everything known about a dataset if the <b>output</b> parameter is not set.
-
-<p>
-
-The <em>r.in.gdal</em> comand does support the following features, as long as
-the underlying format driver supports it:
-
-<p>
-
-<dl>
-
-<dt> Color Table
-<dd> Bands with associated colortables will have the color tables transferred.
-Note that if the source has no colormap, r.in.gdal in GRASS 5.0 will emit
-no colormap. Use r.colors map=... color=grey to assign a greyscale colormap.
-In a future version of GRASS r.in.gdal will likely be upgraded to automatically
-emit greyscale colormaps.
-<br>
-
-<dt> Data Types
-<dd> Most GDAL data types are supported. Float32 and Float64 type bands
-are translated as GRASS floating point cells (but not double precision ...
-this could be added if needed), and most other types are translated as
-GRASS integer cells. This includes 16bit integer data sources. Complex
-(some SAR signal data formats) data bands are translated to two floating
-point cell layers (*.real and *.imaginary).<br>
-
-<dt> Georeferencing
-<dd> If the dataset has affine georeferencing information, this will be used
-to set the north, south, east and west edges. Rotational coefficients will
-be ignored, resulting in incorrect positioning for rotated datasets.<br>
-
-<dt> Projection
-<dd> The datasets projection will be used to compare to the current location
-or to define a new location. Internally GDAL represents projections in
-OpenGIS Well Known Text format. A large subset of the total set of GRASS
-projections are supported.<br>
-
-<dt> Null Values
-<dd> Raster bands for which a null value is recognised by GDAL will have
-the null pixels transformed into GRASS style nulls during import. Many
-generic formats (and formats poorly supported by GDAL) do not have a way
-of recognising null pixels in which case r.null should be used after the
-import.<br>
-
-<dt> GCPs
-<dd> Datasets that have Ground Control Points will have them imported as
-a POINTS file associated with the imagery group. Datasets with only one
-band that would otherwise have been translated as a simple raster map
-will also have an associated imagery group if there are ground control points.
-The coordinate system of the ground control points is reported by r.in.gdal
-but not preserved. It is up to the user to ensure that the location
-established with i.target has a compatible coordinate system before using
-the points with i.rectify.<br>
-
-</dl>
-
-<h3>Error Messages</h3>
-
-<i>"ERROR: Input map is rotated - cannot import."</i><br>
-In this case the image must be first externally rotated, applying the rotation info stored in
-the metadata field of the raster image file. For example, the
-<a href="http://www.gdal.org/gdal_utilities.html">gdalwarp</a> software can be used
-to transform the map to North-up (note, there are several gdalwarp parameters to select the
-resampling algorithm):
-
-<div class="code"><pre>
-gdalwarp rotated.tif northup.tif
-</pre></div>
-
-<p>
-<i>"ERROR: Projection of dataset does not appear to match the current location."</i><br>
-
-You need to create a location whose projection matches the data you
-wish to import. Try using <b>location</b> parameter to create a new location based
-upon the projection information in the file. If desired, you can then re-project
-it to another location with <em>r.proj</em>.
-
-<h2>EXAMPLES</h2>
-
-<h3>GTOPO30 DEM</h3>
-
-To avoid that the GTOPO30 data are read incorrectly, you can add a new line
-"PIXELTYPE SIGNEDINT" in the .HDR to force interpretation of the file as
-signed rather than unsigned integers. Then the .DEM file can be imported.
-Finally, e.g. the 'terrain' color table can be assigned to the imported map
-with <em>r.colors</em>.
-
-
-<h3>GLOBE DEM</h3>
-
-To import <a href="http://www.ngdc.noaa.gov/seg/topo/gltiles.shtml">GLOBE DEM tiles</a>
-(approx 1km resolution, better than GTOPO30 DEM data), the user has to download
-additionally the related <a href="ftp://ftp.ngdc.noaa.gov/GLOBE_DEM/data/elev/esri/hdr/">HDR file(s)</a>.
-Finally, e.g. the 'terrain' color table can be assigned to the imported map with <em>r.colors</em>.
-
-<h3>Worldclim.org</h3>
-To import <a href="http://www.worldclim.org">Worldclim</a> data, the following
-line has to be added to each .hdr file:
-<div class="code"><pre>
-PIXELTYPE SIGNEDINT
-</pre></div>
-
-<h3>HDF</h3>
-
-The import of HDF bands requires the specification of the individual bands
-as seen by GDAL:
-<div class="code"><pre>
-# Example MODIS FPAR
-gdalinfo MOD15A2.A2003153.h18v04.004.2003171141042.hdf
-...
-Subdatasets:
- SUBDATASET_1_NAME=HDF4_EOS:EOS_GRID:"MOD15A2.A2003153.h18v04.004.2003171141042.hdf":MOD_Grid_MOD15A2:Fpar_1km
- SUBDATASET_1_DESC=[1200x1200] Fpar_1km MOD_Grid_MOD15A2 (8-bit unsigned integer)
- SUBDATASET_2_NAME=HDF4_EOS:EOS_GRID:"MOD15A2.A2003153.h18v04.004.2003171141042.hdf":MOD_Grid_MOD15A2:Lai_1km
- SUBDATASET_2_DESC=[1200x1200] Lai_1km MOD_Grid_MOD15A2 (8-bit unsigned integer)
-...
-
-# import of first band, here FPAR 1km:
-r.in.gdal HDF4_EOS:EOS_GRID:"MOD15A2.A2003153.h18v04.004.2003171141042.hdf":MOD_Grid_MOD15A2:Fpar_1km \
- out=fpar_1km_2003_06_02
-# ... likewise for other HDF bands in the file.
-</pre></div>
-
-<h2>SEE ALSO</h2>
-<em>
-<a href="r.colors.html">r.colors</a>,
-<a href="r.in.ascii.html">r.in.ascii</a>,
-<a href="r.in.arc.html">r.in.arc</a>,
-<a href="r.in.bin.html">r.in.bin</a>,
-<a href="r.null.html">r.null</a>
-</em>
-
-<h2>REFERENCES</h2>
-
-GDAL Pages: <a href="http://www.gdal.org">http://www.gdal.org/</a><br>
-
-<h2>AUTHOR</h2>
-
-<a href="http://home.gdal.org/warmerda/">Frank Warmerdam</a> (<a href="mailto:warmerdam AT pobox dot com">email</a>).
-
-<p><i>Last changed: $Date$</i>I
Copied: grass/trunk/raster/r.in.gdal/r.in.gdal.html (from rev 32770, grass/trunk/raster/r.in.gdal/description.html)
===================================================================
--- grass/trunk/raster/r.in.gdal/r.in.gdal.html (rev 0)
+++ grass/trunk/raster/r.in.gdal/r.in.gdal.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,260 @@
+<h2>DESCRIPTION</h2>
+
+<em>r.in.gdal</em> allows a user to create a (binary) GRASS raster map layer,
+or imagery group, from any GDAL supported raster map format, with an optional
+title. The imported file may also be optionally used to create a new location.
+
+<!--<h2>OPTIONS</h2>
+
+Extended explanations:
+
+<h3>Flags:</h3>
+
+<dt><b>-e</b>
+<dd>Extend the DEFAULT_WIND in PERMANENT mapset to include the region of
+the new map layer. Old resolution is preserved, but the region, and rows/cols
+are updated. This will fail if the user doesn't have write access to the
+PERMANENT mapset.
+</dl>-->
+
+<h3>GDAL supported raster formats</h3>
+
+Full details on GDAL supported formats are available at:<p>
+
+<a href="http://www.gdal.org/formats_list.html">http://www.gdal.org/formats_list.html</a><p>
+
+Selected formats of more than 80 supported formats:
+<div class="code"><pre>
+
+Long Format Name Code Creation Georeferencing Maximum File Size
+
+Arc/Info ASCII Grid AAIGrid Yes Yes No limits
+Arc/Info Binary Grid AIG No Yes --
+AIRSAR Polarimetric AIRSAR No No --
+Microsoft Windows Device Independent Bitmap (.bmp) BMP Yes Yes 4GiB
+BSB Nautical Chart Format (.kap) BSB No Yes --
+VTP Binary Terrain Format (.bt) BT Yes Yes --
+CEOS (Spot for instance) CEOS No No --
+First Generation USGS DOQ (.doq) DOQ1 No Yes --
+New Labelled USGS DOQ (.doq) DOQ2 No Yes --
+Data (.dt0, .dt1) DTED No Yes --
+ERMapper Compressed Wavelets (.ecw) ECW Yes Yes
+ESRI .hdr Labelled EHdr No Yes --
+ENVI .hdr Labelled Raster ENVI Yes Yes No limits
+Envisat Image Product (.n1) Envisat No No --
+EOSAT FAST Format FAST No Yes --
+FITS (.fits) FITS Yes No
+Graphics Interchange Format (.gif) GIF Yes No 2GB
+Arc/Info Binary Grid (.adf) GIO Yes Yes
+GRASS Rasters GRASS No Yes --
+TIFF / GeoTIFF (.tif) GTiff Yes Yes 4GiB
+Hierarchical Data Format Release 4 (HDF4) HDF4 Yes Yes 2GiB
+Erdas Imagine (.img) HFA Yes Yes No limits
+Atlantis MFF2e HKV Yes Yes No limits
+Image Display and Analysis (WinDisp) IDA Yes Yes 2GB
+ILWIS Raster Map (.mpr,.mpl) ILWIS Yes Yes --
+Japanese DEM (.mem) JDEM No Yes --
+JPEG JFIF (.jpg) JPEG Yes Yes 4GiB (max dimentions 65500x65500)
+JPEG2000 (.jp2, .j2k) JPEG2000 Yes Yes 2GiB
+JPEG2000 (.jp2, .j2k) JP2KAK Yes Yes No limits
+NOAA Polar Orbiter Level 1b Data Set (AVHRR) L1B No Yes --
+Erdas 7.x .LAN and .GIS LAN No Yes 2GB
+In Memory Raster MEM Yes Yes 2GiB
+Atlantis MFF MFF Yes Yes No limits
+Multi-resolution Seamless Image Database MrSID No Yes --
+NDF NLAPS Data Format No Yes No limits
+NITF NITF Yes Yes
+NetCDF netCDF Yes Yes 2GB
+OGDI Bridge OGDI No Yes --
+PCI .aux Labelled PAux Yes No No limits
+PCI Geomatics Database File PCIDSK Yes Yes No limits
+Portable Network Graphics (.png) PNG Yes No
+PCRaster (.map) PCRaster Yes No
+Netpbm (.ppm,.pgm) PNM Yes No No limits
+RadarSat2 XML (product.xml) RS2 No Yes 4GB
+USGS SDTS DEM (*CATD.DDF) SDTS No Yes --
+SAR CEOS SAR_CEOS No Yes --
+USGS ASCII DEM (.dem) USGSDEM No Yes --
+X11 Pixmap (.xpm) XPM Yes No
+</pre></div>
+
+<h3>Location Creation</h3>
+
+<em>r.in.gdal</em> attempts to preserve projection information when importing
+datasets if the source format includes projection information, and if
+the GDAL driver supports it. If the projection of the source dataset does
+not match the projection of the current location <em>r.in.gdal</em> will
+report an error message (<tt>Projection of dataset does not appear to
+match current location</tt>) and then report the PROJ_INFO parameters of
+the source dataset.
+
+<p>
+
+If the user wishes to ignore the difference between the apparent coordinate
+system of the source data and the current location, they may pass the
+<b>-o</b> flag to override the projection check.
+
+<p>
+
+If the user wishes to import the data with the full projection definition,
+it is possible to have r.in.gdal automatically create a new location based
+on the projection and extents of the file being read. This is accomplished
+by passing the name to be used for the new location via the <b>location</b>
+parameter. Upon completion of the command, a new location will have been
+created (with only a PERMANENT mapset), and the raster will have been
+imported with the indicated <b>output</b> name into the PERMANENT mapset.
+
+<p>
+
+Support for GCPs: In case the image contains GCPs they are written to a
+POINTS file within an imagery group. They can directly be used for
+<a href=i.rectify.html>i.rectify</a>. The <b>target</b> option allows to
+automatically re-project the GCPs from their own projection into another
+projection read from the PROJ_INFO file of the location name
+<b>target</b>.
+
+<h2>NOTES</h2>
+
+Planned improvements to <em>r.in.gdal</em> in the future include support for
+reporting everything known about a dataset if the <b>output</b> parameter is not set.
+
+<p>
+
+The <em>r.in.gdal</em> comand does support the following features, as long as
+the underlying format driver supports it:
+
+<p>
+
+<dl>
+
+<dt> Color Table
+<dd> Bands with associated colortables will have the color tables transferred.
+Note that if the source has no colormap, r.in.gdal in GRASS 5.0 will emit
+no colormap. Use r.colors map=... color=grey to assign a greyscale colormap.
+In a future version of GRASS r.in.gdal will likely be upgraded to automatically
+emit greyscale colormaps.
+<br>
+
+<dt> Data Types
+<dd> Most GDAL data types are supported. Float32 and Float64 type bands
+are translated as GRASS floating point cells (but not double precision ...
+this could be added if needed), and most other types are translated as
+GRASS integer cells. This includes 16bit integer data sources. Complex
+(some SAR signal data formats) data bands are translated to two floating
+point cell layers (*.real and *.imaginary).<br>
+
+<dt> Georeferencing
+<dd> If the dataset has affine georeferencing information, this will be used
+to set the north, south, east and west edges. Rotational coefficients will
+be ignored, resulting in incorrect positioning for rotated datasets.<br>
+
+<dt> Projection
+<dd> The datasets projection will be used to compare to the current location
+or to define a new location. Internally GDAL represents projections in
+OpenGIS Well Known Text format. A large subset of the total set of GRASS
+projections are supported.<br>
+
+<dt> Null Values
+<dd> Raster bands for which a null value is recognised by GDAL will have
+the null pixels transformed into GRASS style nulls during import. Many
+generic formats (and formats poorly supported by GDAL) do not have a way
+of recognising null pixels in which case r.null should be used after the
+import.<br>
+
+<dt> GCPs
+<dd> Datasets that have Ground Control Points will have them imported as
+a POINTS file associated with the imagery group. Datasets with only one
+band that would otherwise have been translated as a simple raster map
+will also have an associated imagery group if there are ground control points.
+The coordinate system of the ground control points is reported by r.in.gdal
+but not preserved. It is up to the user to ensure that the location
+established with i.target has a compatible coordinate system before using
+the points with i.rectify.<br>
+
+</dl>
+
+<h3>Error Messages</h3>
+
+<i>"ERROR: Input map is rotated - cannot import."</i><br>
+In this case the image must be first externally rotated, applying the rotation info stored in
+the metadata field of the raster image file. For example, the
+<a href="http://www.gdal.org/gdal_utilities.html">gdalwarp</a> software can be used
+to transform the map to North-up (note, there are several gdalwarp parameters to select the
+resampling algorithm):
+
+<div class="code"><pre>
+gdalwarp rotated.tif northup.tif
+</pre></div>
+
+<p>
+<i>"ERROR: Projection of dataset does not appear to match the current location."</i><br>
+
+You need to create a location whose projection matches the data you
+wish to import. Try using <b>location</b> parameter to create a new location based
+upon the projection information in the file. If desired, you can then re-project
+it to another location with <em>r.proj</em>.
+
+<h2>EXAMPLES</h2>
+
+<h3>GTOPO30 DEM</h3>
+
+To avoid that the GTOPO30 data are read incorrectly, you can add a new line
+"PIXELTYPE SIGNEDINT" in the .HDR to force interpretation of the file as
+signed rather than unsigned integers. Then the .DEM file can be imported.
+Finally, e.g. the 'terrain' color table can be assigned to the imported map
+with <em>r.colors</em>.
+
+
+<h3>GLOBE DEM</h3>
+
+To import <a href="http://www.ngdc.noaa.gov/seg/topo/gltiles.shtml">GLOBE DEM tiles</a>
+(approx 1km resolution, better than GTOPO30 DEM data), the user has to download
+additionally the related <a href="ftp://ftp.ngdc.noaa.gov/GLOBE_DEM/data/elev/esri/hdr/">HDR file(s)</a>.
+Finally, e.g. the 'terrain' color table can be assigned to the imported map with <em>r.colors</em>.
+
+<h3>Worldclim.org</h3>
+To import <a href="http://www.worldclim.org">Worldclim</a> data, the following
+line has to be added to each .hdr file:
+<div class="code"><pre>
+PIXELTYPE SIGNEDINT
+</pre></div>
+
+<h3>HDF</h3>
+
+The import of HDF bands requires the specification of the individual bands
+as seen by GDAL:
+<div class="code"><pre>
+# Example MODIS FPAR
+gdalinfo MOD15A2.A2003153.h18v04.004.2003171141042.hdf
+...
+Subdatasets:
+ SUBDATASET_1_NAME=HDF4_EOS:EOS_GRID:"MOD15A2.A2003153.h18v04.004.2003171141042.hdf":MOD_Grid_MOD15A2:Fpar_1km
+ SUBDATASET_1_DESC=[1200x1200] Fpar_1km MOD_Grid_MOD15A2 (8-bit unsigned integer)
+ SUBDATASET_2_NAME=HDF4_EOS:EOS_GRID:"MOD15A2.A2003153.h18v04.004.2003171141042.hdf":MOD_Grid_MOD15A2:Lai_1km
+ SUBDATASET_2_DESC=[1200x1200] Lai_1km MOD_Grid_MOD15A2 (8-bit unsigned integer)
+...
+
+# import of first band, here FPAR 1km:
+r.in.gdal HDF4_EOS:EOS_GRID:"MOD15A2.A2003153.h18v04.004.2003171141042.hdf":MOD_Grid_MOD15A2:Fpar_1km \
+ out=fpar_1km_2003_06_02
+# ... likewise for other HDF bands in the file.
+</pre></div>
+
+<h2>SEE ALSO</h2>
+<em>
+<a href="r.colors.html">r.colors</a>,
+<a href="r.in.ascii.html">r.in.ascii</a>,
+<a href="r.in.arc.html">r.in.arc</a>,
+<a href="r.in.bin.html">r.in.bin</a>,
+<a href="r.null.html">r.null</a>
+</em>
+
+<h2>REFERENCES</h2>
+
+GDAL Pages: <a href="http://www.gdal.org">http://www.gdal.org/</a><br>
+
+<h2>AUTHOR</h2>
+
+<a href="http://home.gdal.org/warmerda/">Frank Warmerdam</a> (<a href="mailto:warmerdam AT pobox dot com">email</a>).
+
+<p><i>Last changed: $Date$</i>I
Deleted: grass/trunk/raster/r.in.gridatb/description.html
===================================================================
--- grass/trunk/raster/r.in.gridatb/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.in.gridatb/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,16 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-
-<em>r.in.gridatb</em> imports GRIDATB.FOR map file (TOPMODEL) into GRASS
-raster map.
-
-<h2>SEE ALSO</h2>
-
-<em><a href="r.topmodel.html">r.topmodel</a>,</em>
-<em><a href="r.out.gridatb.html">r.out.gridatb</a></em>
-
-<h2>AUTHOR</h2>
-
-Huidae Cho based on code from Keith Beven
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.in.gridatb/r.in.gridatb.html (from rev 32770, grass/trunk/raster/r.in.gridatb/description.html)
===================================================================
--- grass/trunk/raster/r.in.gridatb/r.in.gridatb.html (rev 0)
+++ grass/trunk/raster/r.in.gridatb/r.in.gridatb.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,16 @@
+<h2>DESCRIPTION</h2>
+
+
+<em>r.in.gridatb</em> imports GRIDATB.FOR map file (TOPMODEL) into GRASS
+raster map.
+
+<h2>SEE ALSO</h2>
+
+<em><a href="r.topmodel.html">r.topmodel</a>,</em>
+<em><a href="r.out.gridatb.html">r.out.gridatb</a></em>
+
+<h2>AUTHOR</h2>
+
+Huidae Cho based on code from Keith Beven
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.in.mat/description.html
===================================================================
--- grass/trunk/raster/r.in.mat/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.in.mat/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,135 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>r.in.mat</em> will import a GRASS raster map from a Version 4 MAT-File
-which was created with Matlab or Octave.
-Attributes such as map title and bounds will also be imported if they exist.
-<br>
-<br>
-Specifically, the following array variables will be read:<br>
-<ul>
- <li><b> map_data</b>
- <li><b> map_name</b>
- <li><b> map_title</b>
- <li><b> map_northern_edge</b>
- <li><b> map_southern_edge</b>
- <li><b> map_eastern_edge</b>
- <li><b> map_western_edge</b>
-</ul>
-
-Any other variables in the MAT-file will be simply skipped over.<br>
-<br>
-The '<b>map_name</b>' variable is optional, if it exists, and is valid, the
-new map will be thus named. If it doesn't exist or a name is specified with
-the <b>output=</b> option, the raster map's name will be set to
-"<tt>MatFile</tt>" or the name specified respectively.
-(maximum 64 characters; normal GRASS naming rules apply)
-<br>
-<br>
-The '<b>map_title</b>' variable is optional, the map's title is set if it
-exists.
-<br>
-<br>
-The '<b>map_northern_edge</b>' and like variables are mandatory unless the
-user is importing to a "XY" non-georeferenced location
-(e.g. imagery data). Latitude and longitude values should be in decimal form.
-
-
-<h2>NOTES</h2>
-
-<em>r.in.mat</em> imports a Version 4 MAT-File. These files can be
-successfully created with more modern versions of Matlab and Octave
-(see "EXAMPLES" below).<br><br>
-
-Everything should be Endian safe, so the file to be imported can be simply
-copied between different system architectures without binary translation
-(caveat: see "TODO" below).<br><br>
-
-As there is no IEEE value for <tt>NaN</tt> in integer arrays, GRASS's null
-value may be used to represent it within these maps. Usually Matlab will save
-any integer based matrix with <tt>NaN</tt> values as a double-precision
-floating point array, so this usually isn't an issue. To save space, once the
-map is loaded into GRASS you can convert it back to an integer map with the
-following command:
-<div class="code"><pre>
-r.mapcalc int_map="int(MATFile_map)"
-</pre></div>
-
-<tt>NaN</tt> values in either floating point or double-precision floating point
-matrices should translate into null values as expected.<br><br>
-
-
-<em>r.in.mat</em> must load the entire map array into memory before writing,
-therefore it might have problems with <i>huge</i> arrays.
-(a 3000x4000 DCELL map uses about 100mb RAM)<br><br>
-
-GRASS defines its map bounds at the outer-edge of the bounding cells, not at
-the coordinates of their centroids. Thus, the following Matlab commands may
-be used to determine and check the map's resolution information will be correct:
-<div class="code"><pre>
- [rows cols] = size(map_data)
- x_range = map_eastern_edge - map_western_edge
- y_range = map_northern_edge - map_southern_edge
- ns_res = y_range/rows
- ew_res = x_range/cols
-</pre></div>
-
-<br>
-Remember Matlab arrays are referenced as <tt>(row,column)</tt>,
-i.e. <tt>(y,x)</tt>.
-<br><br>
-In addition, <em>r.in.mat</em> and <em>r.out.mat</em> make for a nice
-binary container format for transferring georeferenced maps around,
-even if you don't use Matlab or Octave.
-
-<h2>EXAMPLES</h2>
-
-In Matlab, save with:
-<div class="code"><pre>
-save filename.mat map_* -v4
-</pre></div>
-
-In Octave, save with:
-<div class="code"><pre>
-save -mat4-binary filename.mat map_*
-</pre></div>
-
-<br>
-
-<h2>TODO</h2>
-
-Robust support for mixed-Endian importation.
-<i>(This is a work in progress, please help by reporting any failures to the
-<a href="http://trac.osgeo.org/grass/">
-GRASS bug tracking system</a></i>; you will need to login with an OSGeo Userid)
-<br>
-Add support for importing map history, category information, color map, etc.
-if they exist.
-<br>
-Option to import a version 5 MAT-File, with map and support information
-stored in a single structured array.
-
-<h2>BUGS</h2>
-
-If you encounter any problems, please contact the GRASS Development Team.
-
-<h2>SEE ALSO</h2>
-
-<i>
-<a href="r.out.mat.html">r.out.mat</a>,
-<a href="r.in.ascii.html">r.in.ascii</a>,
-<a href="r.in.bin.html">r.in.bin</a>,
-<a href="r.mapcalc.html">r.mapcalc</a>,
-<a href="r.null.html">r.null</a>.<p>
-The <a href="http://www.octave.org">Octave</a> project
-</i>
-
-
-<h2>AUTHOR</h2>
-
-Hamish Bowman<br> <i>
-Department of Marine Science<br>
-University of Otago<br>
-New Zealand</i><br>
-
-<br>
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.in.mat/r.in.mat.html (from rev 32770, grass/trunk/raster/r.in.mat/description.html)
===================================================================
--- grass/trunk/raster/r.in.mat/r.in.mat.html (rev 0)
+++ grass/trunk/raster/r.in.mat/r.in.mat.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,135 @@
+<h2>DESCRIPTION</h2>
+
+<em>r.in.mat</em> will import a GRASS raster map from a Version 4 MAT-File
+which was created with Matlab or Octave.
+Attributes such as map title and bounds will also be imported if they exist.
+<br>
+<br>
+Specifically, the following array variables will be read:<br>
+<ul>
+ <li><b> map_data</b>
+ <li><b> map_name</b>
+ <li><b> map_title</b>
+ <li><b> map_northern_edge</b>
+ <li><b> map_southern_edge</b>
+ <li><b> map_eastern_edge</b>
+ <li><b> map_western_edge</b>
+</ul>
+
+Any other variables in the MAT-file will be simply skipped over.<br>
+<br>
+The '<b>map_name</b>' variable is optional, if it exists, and is valid, the
+new map will be thus named. If it doesn't exist or a name is specified with
+the <b>output=</b> option, the raster map's name will be set to
+"<tt>MatFile</tt>" or the name specified respectively.
+(maximum 64 characters; normal GRASS naming rules apply)
+<br>
+<br>
+The '<b>map_title</b>' variable is optional, the map's title is set if it
+exists.
+<br>
+<br>
+The '<b>map_northern_edge</b>' and like variables are mandatory unless the
+user is importing to a "XY" non-georeferenced location
+(e.g. imagery data). Latitude and longitude values should be in decimal form.
+
+
+<h2>NOTES</h2>
+
+<em>r.in.mat</em> imports a Version 4 MAT-File. These files can be
+successfully created with more modern versions of Matlab and Octave
+(see "EXAMPLES" below).<br><br>
+
+Everything should be Endian safe, so the file to be imported can be simply
+copied between different system architectures without binary translation
+(caveat: see "TODO" below).<br><br>
+
+As there is no IEEE value for <tt>NaN</tt> in integer arrays, GRASS's null
+value may be used to represent it within these maps. Usually Matlab will save
+any integer based matrix with <tt>NaN</tt> values as a double-precision
+floating point array, so this usually isn't an issue. To save space, once the
+map is loaded into GRASS you can convert it back to an integer map with the
+following command:
+<div class="code"><pre>
+r.mapcalc int_map="int(MATFile_map)"
+</pre></div>
+
+<tt>NaN</tt> values in either floating point or double-precision floating point
+matrices should translate into null values as expected.<br><br>
+
+
+<em>r.in.mat</em> must load the entire map array into memory before writing,
+therefore it might have problems with <i>huge</i> arrays.
+(a 3000x4000 DCELL map uses about 100mb RAM)<br><br>
+
+GRASS defines its map bounds at the outer-edge of the bounding cells, not at
+the coordinates of their centroids. Thus, the following Matlab commands may
+be used to determine and check the map's resolution information will be correct:
+<div class="code"><pre>
+ [rows cols] = size(map_data)
+ x_range = map_eastern_edge - map_western_edge
+ y_range = map_northern_edge - map_southern_edge
+ ns_res = y_range/rows
+ ew_res = x_range/cols
+</pre></div>
+
+<br>
+Remember Matlab arrays are referenced as <tt>(row,column)</tt>,
+i.e. <tt>(y,x)</tt>.
+<br><br>
+In addition, <em>r.in.mat</em> and <em>r.out.mat</em> make for a nice
+binary container format for transferring georeferenced maps around,
+even if you don't use Matlab or Octave.
+
+<h2>EXAMPLES</h2>
+
+In Matlab, save with:
+<div class="code"><pre>
+save filename.mat map_* -v4
+</pre></div>
+
+In Octave, save with:
+<div class="code"><pre>
+save -mat4-binary filename.mat map_*
+</pre></div>
+
+<br>
+
+<h2>TODO</h2>
+
+Robust support for mixed-Endian importation.
+<i>(This is a work in progress, please help by reporting any failures to the
+<a href="http://trac.osgeo.org/grass/">
+GRASS bug tracking system</a></i>; you will need to login with an OSGeo Userid)
+<br>
+Add support for importing map history, category information, color map, etc.
+if they exist.
+<br>
+Option to import a version 5 MAT-File, with map and support information
+stored in a single structured array.
+
+<h2>BUGS</h2>
+
+If you encounter any problems, please contact the GRASS Development Team.
+
+<h2>SEE ALSO</h2>
+
+<i>
+<a href="r.out.mat.html">r.out.mat</a>,
+<a href="r.in.ascii.html">r.in.ascii</a>,
+<a href="r.in.bin.html">r.in.bin</a>,
+<a href="r.mapcalc.html">r.mapcalc</a>,
+<a href="r.null.html">r.null</a>.<p>
+The <a href="http://www.octave.org">Octave</a> project
+</i>
+
+
+<h2>AUTHOR</h2>
+
+Hamish Bowman<br> <i>
+Department of Marine Science<br>
+University of Otago<br>
+New Zealand</i><br>
+
+<br>
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.in.poly/description.html
===================================================================
--- grass/trunk/raster/r.in.poly/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.in.poly/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,116 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-
-<em>r.in.poly</em> allows the creation of GRASS binary
-raster maps from ASCII files in the current directory
-containing polygon, linear, and point features.
-
-<p>
-
-The <b>input</b> file is an ASCII text file containing the
-polygon, linear, and point feature definitions.
-The format of this file is described in the
-<a href="#format.html"><i>INPUT FORMAT</i></a> section below.
-
-<p>
-
-The number of raster <b>rows</b> to hold in memory is per default 4096.
-This parameter allows users with less memory (or more) on their
-system to control how much memory <em>r.in.poly</em> uses.
-Usually the default value is fine.
-
-
-<h2>NOTES</h2>
-
-<p>
-
-The data will be imported using the current region settings to set the
-new raster map's bounds and resolution. Any features falling outside
-the current region will be cropped. The region settings are contolled
-with the <em>g.region</em> module.
-
-<p>
-
-The format is a simplified version of the standard GRASS vector ASCII
-format used by <em>v.in.ascii</em>.
-
-<p>
-
-Polygons are filled, i.e. they define an area.
-
-<A NAME="format.html"></a>
-<h3>Input Format</h3>
-
-The input format for the <b>input</b> file consists of
-sections describing either polygonal areas, linear features, or
-point features. The basic format is:
-
-<div class="code"><pre>
-A <for polygonal areas>
- easting northing
- .
- .
- .
-= cat# label
-L <for linear features>
- easting northing
- .
- .
- .
-= cat# label
-P <for single cell point features>
- easting northing
-= cat# label
-</pre></div>
-
-
-The <tt>A</tt> signals the beginning of a filled polygon.
-It must appear in the first column.
-
-The <tt>L</tt> signals the beginning of a linear feature.
-It also must appear in the first column.
-
-The <tt>P</tt> signals the beginning of a single cell point feature.
-Again, it must appear in the first column.
-
-The coordinates of the vertices of the polygon, or the coordinates defining
-the linear or point feature follow and must have a space in the first
-column and at least one space between the <em>easting</em> and the
-<em>northing.</em> To give meaning to the features, the
-"<tt>=</tt>" indicates that the feature currently being
-processed has category value <em>cat#</em> (which must be
-an integer) and a <em>label</em> (which may be more than
-one word, or which may be omitted).
-
-
-<h2>EXAMPLE</h2>
-
-An area described by four points:
-
-<div class="code"><pre>
-A
- 591316.80 4926455.50
- 591410.25 4926482.40
- 591434.60 4926393.60
- 591341.20 4926368.70
-= 42 stadium
-</pre></div>
-
-<h2>SEE ALSO</h2>
-<i>
-<a href="r.digit.html">r.digit</a></i> (for interactive on-screen polygon/line digitizing for raster maps)<br>
-<i><a href="r.colors.html">r.colors</a></i> (for raster map color table creation)<br>
-<i><a href="d.rast.edit.html">d.rast.edit</a><br>
-<a href="g.region.html">g.region</a><br>
-<a href="r.in.xyz.html">r.in.xyz</a><br>
-<a href="r.patch.html">r.patch</a><br>
-<a href="v.in.ascii.html">v.in.ascii</a><br>
-<a href="v.digit.html">v.digit</a><br>
-</i>
-
-<h2>AUTHOR</h2>
-
-Michael Shapiro, U.S.Army Construction Engineering Research Laboratory
-
-<p>
-<i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.in.poly/r.in.poly.html (from rev 32770, grass/trunk/raster/r.in.poly/description.html)
===================================================================
--- grass/trunk/raster/r.in.poly/r.in.poly.html (rev 0)
+++ grass/trunk/raster/r.in.poly/r.in.poly.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,116 @@
+<h2>DESCRIPTION</h2>
+
+
+<em>r.in.poly</em> allows the creation of GRASS binary
+raster maps from ASCII files in the current directory
+containing polygon, linear, and point features.
+
+<p>
+
+The <b>input</b> file is an ASCII text file containing the
+polygon, linear, and point feature definitions.
+The format of this file is described in the
+<a href="#format.html"><i>INPUT FORMAT</i></a> section below.
+
+<p>
+
+The number of raster <b>rows</b> to hold in memory is per default 4096.
+This parameter allows users with less memory (or more) on their
+system to control how much memory <em>r.in.poly</em> uses.
+Usually the default value is fine.
+
+
+<h2>NOTES</h2>
+
+<p>
+
+The data will be imported using the current region settings to set the
+new raster map's bounds and resolution. Any features falling outside
+the current region will be cropped. The region settings are contolled
+with the <em>g.region</em> module.
+
+<p>
+
+The format is a simplified version of the standard GRASS vector ASCII
+format used by <em>v.in.ascii</em>.
+
+<p>
+
+Polygons are filled, i.e. they define an area.
+
+<A NAME="format.html"></a>
+<h3>Input Format</h3>
+
+The input format for the <b>input</b> file consists of
+sections describing either polygonal areas, linear features, or
+point features. The basic format is:
+
+<div class="code"><pre>
+A <for polygonal areas>
+ easting northing
+ .
+ .
+ .
+= cat# label
+L <for linear features>
+ easting northing
+ .
+ .
+ .
+= cat# label
+P <for single cell point features>
+ easting northing
+= cat# label
+</pre></div>
+
+
+The <tt>A</tt> signals the beginning of a filled polygon.
+It must appear in the first column.
+
+The <tt>L</tt> signals the beginning of a linear feature.
+It also must appear in the first column.
+
+The <tt>P</tt> signals the beginning of a single cell point feature.
+Again, it must appear in the first column.
+
+The coordinates of the vertices of the polygon, or the coordinates defining
+the linear or point feature follow and must have a space in the first
+column and at least one space between the <em>easting</em> and the
+<em>northing.</em> To give meaning to the features, the
+"<tt>=</tt>" indicates that the feature currently being
+processed has category value <em>cat#</em> (which must be
+an integer) and a <em>label</em> (which may be more than
+one word, or which may be omitted).
+
+
+<h2>EXAMPLE</h2>
+
+An area described by four points:
+
+<div class="code"><pre>
+A
+ 591316.80 4926455.50
+ 591410.25 4926482.40
+ 591434.60 4926393.60
+ 591341.20 4926368.70
+= 42 stadium
+</pre></div>
+
+<h2>SEE ALSO</h2>
+<i>
+<a href="r.digit.html">r.digit</a></i> (for interactive on-screen polygon/line digitizing for raster maps)<br>
+<i><a href="r.colors.html">r.colors</a></i> (for raster map color table creation)<br>
+<i><a href="d.rast.edit.html">d.rast.edit</a><br>
+<a href="g.region.html">g.region</a><br>
+<a href="r.in.xyz.html">r.in.xyz</a><br>
+<a href="r.patch.html">r.patch</a><br>
+<a href="v.in.ascii.html">v.in.ascii</a><br>
+<a href="v.digit.html">v.digit</a><br>
+</i>
+
+<h2>AUTHOR</h2>
+
+Michael Shapiro, U.S.Army Construction Engineering Research Laboratory
+
+<p>
+<i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.in.xyz/description.html
===================================================================
--- grass/trunk/raster/r.in.xyz/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.in.xyz/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,244 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-The <em>r.in.xyz</em> module will load and bin ungridded x,y,z ASCII data
-into a new raster map. The user may choose from a variety of statistical
-methods in creating the new raster.
-<p>
-
-<em>r.in.xyz</em> is designed for processing massive point cloud datasets,
-for example raw LIDAR or sidescan sonar swath data. It has been tested with
-datasets as large as 1.5 billion points.
-<p>
-
-Available statistics for populating the raster are:<br>
-<ul>
-<table>
-<tr><td><em>n</em></td> <td>number of points in cell</td></tr>
-<tr><td><em>min</em></td> <td>minimum value of points in cell</td></tr>
-<tr><td><em>max</em></td> <td>maximum value of points in cell</td></tr>
-<tr><td><em>range</em></td> <td>range of points in cell</td></tr>
-<tr><td><em>sum</em></td> <td>sum of points in cell</td></tr>
-<tr><td><em>mean</em></td> <td>average value of points in cell</td></tr>
-<tr><td><em>stddev</em></td> <td>standard deviation of points in cell</td></tr>
-<tr><td><em>variance</em></td> <td>variance of points in cell</td></tr>
-<tr><td><em>coeff_var</em></td><td>coefficient of variance of points in cell</td></tr>
-<tr><td><em>median</em></td> <td>median value of points in cell</td></tr>
-<tr valign="baseline"><td><em>percentile</em> </td>
- <td>p<sup><i>th</i></sup> percentile of points in cell</td></tr>
-<tr><td><em>skewness</em></td> <td>skewness of points in cell</td></tr>
-<tr><td><em>trimmean</em></td> <td>trimmed mean of points in cell</td></tr>
-</table><br>
-
-<li><em>Variance</em> and derivatives use the biased estimator (n). [subject to change]
-<li><em>Coefficient of variance</em> is given in percentage and defined as
-<tt>(stddev/mean)*100</tt>.
-</ul>
-<br>
-
-<h2>NOTES</h2>
-
-<h4>Memory use</h4>
-
-While the <b>input</b> file can be arbitrarily large, <em>r.in.xyz</em>
-will use a large amount of system memory for large raster regions (10000x10000).
-If the module refuses to start complaining that there isn't enough memory,
-use the <b>percent</b> parameter to run the module in several passes.
-In addition using a less precise map format (<tt>CELL</tt> [integer] or
-<tt>FCELL</tt> [floating point]) will use less memory than a <tt>DCELL</tt>
-[double precision floating point] <b>output</b> map. Methods such as <em>n,
-min, max, sum</em> will also use less memory, while <em>stddev, variance,
-and coeff_var</em> will use more.
-
-The aggregate functions <em>median, percentile, skewness</em> and
-<em>trimmed mean</em> will also use more memory.
-
-<p>
-
-The default map <b>type</b>=<tt>FCELL</tt> is intended as compromise between
-preserving data precision and limiting system resource consumption.
-If reading data from a <tt>stdin</tt> stream, the program can only run using
-a single pass.
-
-<h4>Setting region bounds and resolution</h4>
-
-You can use the <b>-s</b> scan flag to find the extent of the input data
-(and thus point density) before performing the full import. Use
-<em>g.region</em> to adjust the region bounds to match. The <b>-g</b> shell
-style flag prints the extent suitable as parameters for <em>g.region</em>.
-A suitable resolution can be found by dividing the number of input points
-by the area covered. e.g.
-
-<div class="code"><pre>
- wc -l inputfile.txt
- g.region -p
- # points_per_cell = n_points / (rows * cols)
-
- g.region -e
- # UTM location:
- # points_per_sq_m = n_points / (ns_extent * ew_extent)
-
- # Lat/Lon location:
- # points_per_sq_m = n_points / (ns_extent * ew_extent*cos(lat) * (1852*60)^2)
-</pre></div>
-
-<p>
-
-If you only intend to interpolate the data with <em>r.to.vect</em> and
-<em>v.surf.rst</em>, then there is little point to setting the region
-resolution so fine that you only catch one data point per cell -- you might
-as well use "<tt>v.in.ascii -zbt</tt>" directly.
-
-
-<h4>Filtering</h4>
-
-Points falling outside the current region will be skipped. This includes
-points falling <em>exactly</em> on the southern region bound.
-(to capture those adjust the region with "<tt>g.region s=s-0.000001</tt>";
-see <em>g.region</em>)
-<p>
-Blank lines and comment lines starting with the hash symbol (<tt>#</tt>)
-will be skipped.
-
-<p>
-
-The <b>zrange</b> parameter may be used for filtering the input data by
-vertical extent. Example uses might include preparing multiple raster
-sections to be combined into a 3D raster array with <em>r.to.rast3</em>, or
-for filtering outliers on relatively flat terrain.
-
-<p>
-
-In varied terrain the user may find that <em>min</em> maps make for a good
-noise filter as most LIDAR noise is from premature hits. The <em>min</em> map
-may also be useful to find the underlying topography in a forested or urban
-environment if the cells are over sampled.
-
-<p>
-
-The user can use a combination of <em>r.in.xyz</em> <b>output</b> maps to create
-custom filters. e.g. use <em>r.mapcalc</em> to create a <tt>mean-(2*stddev)</tt>
-map. [In this example the user may want to include a lower bound filter in
-<em>r.mapcalc</em> to remove highly variable points (small <em>n</em>) or run
-<em>r.neighbors</em> to smooth the stddev map before further use.]
-
-
-<h4>Reprojection</h4>
-
-If the raster map is to be reprojected, it may be more appropriate to reproject
-the input points with <em>m.proj</em> or <em>cs2cs</em> before running
-<em>r.in.xyz</em>.
-
-<h4>Interpolation into a DEM</h4>
-
-The vector engine's topographic abilities introduce a finite memory overhead
-per vector point which will typically limit a vector map to approximately
-3 million points (~ 1750^2 cells). If you want more, use the <em>r.to.vect</em>
-<b>-b</b> flag to skip building topology. Without topology, however, all
-you'll be able to do with the vector map is display with <em>d.vect</em> and
-interpolate with <em>v.surf.rst</em>.
-Run <em>r.univar</em> on your raster map to check the number of non-NULL cells
-and adjust bounds and/or resolution as needed before proceeding.
-
-<p>
-
-Typical commands to create a DEM using a regularized spline fit:
-<div class="code"><pre>
- r.univar lidar_min
- r.to.vect -z feature=point in=lidar_min out=lidar_min_pt
- v.surf.rst layer=0 in=lidar_min_pt elev=lidar_min.rst
-</pre></div>
-<br>
-
-<h2>EXAMPLE</h2>
-
-Import the <a href="http://mpa.itc.it/grasstutor/data_menu2nd.phtml">Jockey's
-Ridge, NC, LIDAR dataset</a>, and process into a clean DEM:
-
-<div class="code"><pre>
- # scan and set region bounds
- r.in.xyz -s fs=, in=lidaratm2.txt out=test
- g.region n=35.969493 s=35.949693 e=-75.620999 w=-75.639999
- g.region res=0:00:00.075 -a
- # create "n" map containing count of points per cell for checking density
- r.in.xyz in=lidaratm2.txt out=lidar_n fs=, method=n zrange=-2,50
- # check point density [rho = n_sum / (rows*cols)]
- r.univar lidar_n | grep sum
- # create "min" map (elevation filtered for premature hits)
- r.in.xyz in=lidaratm2.txt out=lidar_min fs=, method=min zrange=-2,50
- # zoom to area of interest
- g.region n=35:57:56.25N s=35:57:13.575N w=75:38:23.7W e=75:37:15.675W
- # check number of non-null cells (try and keep under a few million)
- r.univar lidar_min | grep '^n:'
- # convert to points
- r.to.vect -z feature=point in=lidar_min out=lidar_min_pt
- # interpolate using a regularized spline fit
- v.surf.rst layer=0 in=lidar_min_pt elev=lidar_min.rst
- # set color scale to something interesting
- r.colors lidar_min.rst rule=bcyr -n -e
- # prepare a 1:1:1 scaled version for NVIZ visualization (for lat/lon input)
- r.mapcalc "lidar_min.rst_scaled = lidar_min.rst / (1852*60)"
- r.colors lidar_min.rst_scaled rule=bcyr -n -e
-</pre></div>
-<br>
-
-
-<h2>TODO</h2>
-
-<ul>
-<li> Support for multiple map output from a single run.<br>
- <tt>method=string[,string,...] output=name[,name,...]</tt>
-</ul>
-
-<h2>BUGS</h2>
-
-<ul>
-<li> <em>n</em> map sum can be ever-so-slightly more than `<tt>wc -l</tt>`
- with e.g. <tt>percent=10</tt> or less.
- <br>Cause unknown.
-
-<li> <em>n</em> map <tt>percent=100</tt> and <tt>percent=xx</tt> maps
- differ slightly (point will fall above/below the segmentation line)
- <br>Investigate with "<tt>r.mapcalc diff=bin_n.100 - bin_n.33</tt>" etc.
- <br>Cause unknown.
-
-<li> "<tt>nan</tt>" can leak into <em>coeff_var</em> maps.
- <br>Cause unknown. Possible work-around: "<tt>r.null setnull=nan</tt>"
-<!-- Another method: r.mapcalc 'No_nan = if(map == map, map, null() )' -->
-</ul>
-
-If you encounter any problems (or solutions!) please contact the GRASS
-Development Team.
-
-<h2>SEE ALSO</h2>
-
-<i>
-<a href="g.region.html">g.region</a><br>
-<a href="m.proj.html">m.proj</a><br>
-<a href="r.fillnulls.html">r.fillnulls</a><br>
-<a href="r.in.ascii.html">r.in.ascii</a><br>
-<a href="r.mapcalc.html">r.mapcalc</a><br>
-<a href="r.neighbors.html">r.neighbors</a><br>
-<a href="r.out.xyz.html">r.out.xyz</a><br>
-<a href="r.to.rast3.html">r.to.rast3</a><br>
-<a href="r.to.vect.html">r.to.vect</a><br>
-<a href="r.univar.html">r.univar</a><br>
-<a href="r.univar.sh.html">r.univar.sh</a><br>
-<a href="v.in.ascii.html">v.in.ascii</a><br>
-<a href="v.out.ascii.html">v.out.ascii</a><br>
-<a href="v.surf.rst.html">v.surf.rst</a>
-</i>
-
-
-<h2>AUTHORS</h2>
-
-Hamish Bowman<br> <i>
-Department of Marine Science<br>
-University of Otago<br>
-New Zealand</i><br>
-<br>
-Extended by Volker Wichmann to support the aggregate functions
-<i>median, percentile, skewness</i> and <i>trimmed mean</i>.
-
-<br>
-<p>
-<i>Last changed: $Date$</i></p>
Copied: grass/trunk/raster/r.in.xyz/r.in.xyz.html (from rev 32770, grass/trunk/raster/r.in.xyz/description.html)
===================================================================
--- grass/trunk/raster/r.in.xyz/r.in.xyz.html (rev 0)
+++ grass/trunk/raster/r.in.xyz/r.in.xyz.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,244 @@
+<h2>DESCRIPTION</h2>
+
+The <em>r.in.xyz</em> module will load and bin ungridded x,y,z ASCII data
+into a new raster map. The user may choose from a variety of statistical
+methods in creating the new raster.
+<p>
+
+<em>r.in.xyz</em> is designed for processing massive point cloud datasets,
+for example raw LIDAR or sidescan sonar swath data. It has been tested with
+datasets as large as 1.5 billion points.
+<p>
+
+Available statistics for populating the raster are:<br>
+<ul>
+<table>
+<tr><td><em>n</em></td> <td>number of points in cell</td></tr>
+<tr><td><em>min</em></td> <td>minimum value of points in cell</td></tr>
+<tr><td><em>max</em></td> <td>maximum value of points in cell</td></tr>
+<tr><td><em>range</em></td> <td>range of points in cell</td></tr>
+<tr><td><em>sum</em></td> <td>sum of points in cell</td></tr>
+<tr><td><em>mean</em></td> <td>average value of points in cell</td></tr>
+<tr><td><em>stddev</em></td> <td>standard deviation of points in cell</td></tr>
+<tr><td><em>variance</em></td> <td>variance of points in cell</td></tr>
+<tr><td><em>coeff_var</em></td><td>coefficient of variance of points in cell</td></tr>
+<tr><td><em>median</em></td> <td>median value of points in cell</td></tr>
+<tr valign="baseline"><td><em>percentile</em> </td>
+ <td>p<sup><i>th</i></sup> percentile of points in cell</td></tr>
+<tr><td><em>skewness</em></td> <td>skewness of points in cell</td></tr>
+<tr><td><em>trimmean</em></td> <td>trimmed mean of points in cell</td></tr>
+</table><br>
+
+<li><em>Variance</em> and derivatives use the biased estimator (n). [subject to change]
+<li><em>Coefficient of variance</em> is given in percentage and defined as
+<tt>(stddev/mean)*100</tt>.
+</ul>
+<br>
+
+<h2>NOTES</h2>
+
+<h4>Memory use</h4>
+
+While the <b>input</b> file can be arbitrarily large, <em>r.in.xyz</em>
+will use a large amount of system memory for large raster regions (10000x10000).
+If the module refuses to start complaining that there isn't enough memory,
+use the <b>percent</b> parameter to run the module in several passes.
+In addition using a less precise map format (<tt>CELL</tt> [integer] or
+<tt>FCELL</tt> [floating point]) will use less memory than a <tt>DCELL</tt>
+[double precision floating point] <b>output</b> map. Methods such as <em>n,
+min, max, sum</em> will also use less memory, while <em>stddev, variance,
+and coeff_var</em> will use more.
+
+The aggregate functions <em>median, percentile, skewness</em> and
+<em>trimmed mean</em> will also use more memory.
+
+<p>
+
+The default map <b>type</b>=<tt>FCELL</tt> is intended as compromise between
+preserving data precision and limiting system resource consumption.
+If reading data from a <tt>stdin</tt> stream, the program can only run using
+a single pass.
+
+<h4>Setting region bounds and resolution</h4>
+
+You can use the <b>-s</b> scan flag to find the extent of the input data
+(and thus point density) before performing the full import. Use
+<em>g.region</em> to adjust the region bounds to match. The <b>-g</b> shell
+style flag prints the extent suitable as parameters for <em>g.region</em>.
+A suitable resolution can be found by dividing the number of input points
+by the area covered. e.g.
+
+<div class="code"><pre>
+ wc -l inputfile.txt
+ g.region -p
+ # points_per_cell = n_points / (rows * cols)
+
+ g.region -e
+ # UTM location:
+ # points_per_sq_m = n_points / (ns_extent * ew_extent)
+
+ # Lat/Lon location:
+ # points_per_sq_m = n_points / (ns_extent * ew_extent*cos(lat) * (1852*60)^2)
+</pre></div>
+
+<p>
+
+If you only intend to interpolate the data with <em>r.to.vect</em> and
+<em>v.surf.rst</em>, then there is little point to setting the region
+resolution so fine that you only catch one data point per cell -- you might
+as well use "<tt>v.in.ascii -zbt</tt>" directly.
+
+
+<h4>Filtering</h4>
+
+Points falling outside the current region will be skipped. This includes
+points falling <em>exactly</em> on the southern region bound.
+(to capture those adjust the region with "<tt>g.region s=s-0.000001</tt>";
+see <em>g.region</em>)
+<p>
+Blank lines and comment lines starting with the hash symbol (<tt>#</tt>)
+will be skipped.
+
+<p>
+
+The <b>zrange</b> parameter may be used for filtering the input data by
+vertical extent. Example uses might include preparing multiple raster
+sections to be combined into a 3D raster array with <em>r.to.rast3</em>, or
+for filtering outliers on relatively flat terrain.
+
+<p>
+
+In varied terrain the user may find that <em>min</em> maps make for a good
+noise filter as most LIDAR noise is from premature hits. The <em>min</em> map
+may also be useful to find the underlying topography in a forested or urban
+environment if the cells are over sampled.
+
+<p>
+
+The user can use a combination of <em>r.in.xyz</em> <b>output</b> maps to create
+custom filters. e.g. use <em>r.mapcalc</em> to create a <tt>mean-(2*stddev)</tt>
+map. [In this example the user may want to include a lower bound filter in
+<em>r.mapcalc</em> to remove highly variable points (small <em>n</em>) or run
+<em>r.neighbors</em> to smooth the stddev map before further use.]
+
+
+<h4>Reprojection</h4>
+
+If the raster map is to be reprojected, it may be more appropriate to reproject
+the input points with <em>m.proj</em> or <em>cs2cs</em> before running
+<em>r.in.xyz</em>.
+
+<h4>Interpolation into a DEM</h4>
+
+The vector engine's topographic abilities introduce a finite memory overhead
+per vector point which will typically limit a vector map to approximately
+3 million points (~ 1750^2 cells). If you want more, use the <em>r.to.vect</em>
+<b>-b</b> flag to skip building topology. Without topology, however, all
+you'll be able to do with the vector map is display with <em>d.vect</em> and
+interpolate with <em>v.surf.rst</em>.
+Run <em>r.univar</em> on your raster map to check the number of non-NULL cells
+and adjust bounds and/or resolution as needed before proceeding.
+
+<p>
+
+Typical commands to create a DEM using a regularized spline fit:
+<div class="code"><pre>
+ r.univar lidar_min
+ r.to.vect -z feature=point in=lidar_min out=lidar_min_pt
+ v.surf.rst layer=0 in=lidar_min_pt elev=lidar_min.rst
+</pre></div>
+<br>
+
+<h2>EXAMPLE</h2>
+
+Import the <a href="http://mpa.itc.it/grasstutor/data_menu2nd.phtml">Jockey's
+Ridge, NC, LIDAR dataset</a>, and process into a clean DEM:
+
+<div class="code"><pre>
+ # scan and set region bounds
+ r.in.xyz -s fs=, in=lidaratm2.txt out=test
+ g.region n=35.969493 s=35.949693 e=-75.620999 w=-75.639999
+ g.region res=0:00:00.075 -a
+ # create "n" map containing count of points per cell for checking density
+ r.in.xyz in=lidaratm2.txt out=lidar_n fs=, method=n zrange=-2,50
+ # check point density [rho = n_sum / (rows*cols)]
+ r.univar lidar_n | grep sum
+ # create "min" map (elevation filtered for premature hits)
+ r.in.xyz in=lidaratm2.txt out=lidar_min fs=, method=min zrange=-2,50
+ # zoom to area of interest
+ g.region n=35:57:56.25N s=35:57:13.575N w=75:38:23.7W e=75:37:15.675W
+ # check number of non-null cells (try and keep under a few million)
+ r.univar lidar_min | grep '^n:'
+ # convert to points
+ r.to.vect -z feature=point in=lidar_min out=lidar_min_pt
+ # interpolate using a regularized spline fit
+ v.surf.rst layer=0 in=lidar_min_pt elev=lidar_min.rst
+ # set color scale to something interesting
+ r.colors lidar_min.rst rule=bcyr -n -e
+ # prepare a 1:1:1 scaled version for NVIZ visualization (for lat/lon input)
+ r.mapcalc "lidar_min.rst_scaled = lidar_min.rst / (1852*60)"
+ r.colors lidar_min.rst_scaled rule=bcyr -n -e
+</pre></div>
+<br>
+
+
+<h2>TODO</h2>
+
+<ul>
+<li> Support for multiple map output from a single run.<br>
+ <tt>method=string[,string,...] output=name[,name,...]</tt>
+</ul>
+
+<h2>BUGS</h2>
+
+<ul>
+<li> <em>n</em> map sum can be ever-so-slightly more than `<tt>wc -l</tt>`
+ with e.g. <tt>percent=10</tt> or less.
+ <br>Cause unknown.
+
+<li> <em>n</em> map <tt>percent=100</tt> and <tt>percent=xx</tt> maps
+ differ slightly (point will fall above/below the segmentation line)
+ <br>Investigate with "<tt>r.mapcalc diff=bin_n.100 - bin_n.33</tt>" etc.
+ <br>Cause unknown.
+
+<li> "<tt>nan</tt>" can leak into <em>coeff_var</em> maps.
+ <br>Cause unknown. Possible work-around: "<tt>r.null setnull=nan</tt>"
+<!-- Another method: r.mapcalc 'No_nan = if(map == map, map, null() )' -->
+</ul>
+
+If you encounter any problems (or solutions!) please contact the GRASS
+Development Team.
+
+<h2>SEE ALSO</h2>
+
+<i>
+<a href="g.region.html">g.region</a><br>
+<a href="m.proj.html">m.proj</a><br>
+<a href="r.fillnulls.html">r.fillnulls</a><br>
+<a href="r.in.ascii.html">r.in.ascii</a><br>
+<a href="r.mapcalc.html">r.mapcalc</a><br>
+<a href="r.neighbors.html">r.neighbors</a><br>
+<a href="r.out.xyz.html">r.out.xyz</a><br>
+<a href="r.to.rast3.html">r.to.rast3</a><br>
+<a href="r.to.vect.html">r.to.vect</a><br>
+<a href="r.univar.html">r.univar</a><br>
+<a href="r.univar.sh.html">r.univar.sh</a><br>
+<a href="v.in.ascii.html">v.in.ascii</a><br>
+<a href="v.out.ascii.html">v.out.ascii</a><br>
+<a href="v.surf.rst.html">v.surf.rst</a>
+</i>
+
+
+<h2>AUTHORS</h2>
+
+Hamish Bowman<br> <i>
+Department of Marine Science<br>
+University of Otago<br>
+New Zealand</i><br>
+<br>
+Extended by Volker Wichmann to support the aggregate functions
+<i>median, percentile, skewness</i> and <i>trimmed mean</i>.
+
+<br>
+<p>
+<i>Last changed: $Date$</i></p>
Deleted: grass/trunk/raster/r.info/description.html
===================================================================
--- grass/trunk/raster/r.info/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.info/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,113 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>r.info</em> reports some basic information about a
-user-specified raster map layer. This map layer must exist
-in the user's current mapset search path. Information
-about the map's boundaries, resolution, projection, data
-type, category number, data base location and mapset,
-the timestamp and history are put into a table and written to standard
-output. The types of information listed can also be found
-in the <i>cats</i>, <i>cellhd</i>, and <i>hist</i>
-directories under the mapset in which the named map is
-stored.
-
-<p>
-
-The user can save the tabular output to a file
-by using the UNIX redirection mechanism (>); for example, the user
-might save a report on the <em>soils</em> map layer in a file called
-<em>soil.rpt</em> by typing:
-
-<div class="code"><pre>
-r.info map=soils > soil.rpt
-</pre></div>
-
-<h2>NOTES</h2>
-
-On large maps, the total number of cells in the map may not be displayed
-with an accurate number. This is only cosmetic.
-
-<p>
-
-Some standards (ISO-C90) and compilers do not support the 'long long' type
-as a 64-bit type. In the case that GRASS was built with such a compiler,
-an accuracy message may be displayed in the output of <em>r.info</em>
-after Total Cells:
-
-<p>
-
-<h2>EXAMPLES</h2>
-
-Below is a full report produced by <em>r.info</em> for the raster map
-<i>slope</i> in the Spearfish sample data base:
-
-<div class="code"><pre>
- +----------------------------------------------------------------------------+
- | Layer: slope Date: Mon Nov 5 10:55:57 2001 |
- | Mapset: PERMANENT Login of Creator: neteler |
- | Location: spearfish60 |
- | DataBase: /home/neteler/grassdaten |
- | Title: slope in degrees ( slope ) |
- | Timestamp: 20 Mar 1984 10:30 -0600 / 21 Mar 2020 10:30 -0600 |
- |----------------------------------------------------------------------------|
- | |
- | Type of Map: raster Number of Categories: 255 |
- | Data Type: FCELL |
- | Rows: 477 |
- | Columns: 634 |
- | Total Cells: 302418 |
- | Projection: UTM (zone 13) |
- | N: 4928010 S: 4913700 Res: 30 |
- | E: 609000 W: 589980 Res: 30 |
- | Range of data: min = 0.000000 max = 52.520164 |
- | |
- | Data Source: |
- | raster elevation file elevation.dem |
- | |
- | |
- | Data Description: |
- | generated by r.slope.aspect |
- | |
- | Comments: |
- | slope map elev = elevation.dem |
- | zfactor = 1.00 format = degrees |
- | min_slp_allowed = 0.000000 |
- | |
- +----------------------------------------------------------------------------+
-</pre></div>
-
-Alternatively, the output from <em>r.info</em> may be confined to a more terse
-subset of the available information by passing various flags to the module:
-
-<div class="code"><pre>
-r.info -rst slope
-min=0.000000
-max=52.520164
-nsres=30
-ewres=30
-datatype=FCELL
-
-r.info -g slope
-north=4928030
-south=4913690
-east=609000
-west=589980
-</pre></div>
-
-<h2>SEE ALSO</h2>
-
-<em><a href="g.mapsets.html">g.mapsets</a>,</em>
-<em><a href="r.coin.html">r.coin</a>,</em>
-<em><a href="r.describe.html">r.describe</a>,</em>
-<em><a href="r.report.html">r.report</a>,</em>
-<em><a href="r.stats.html">r.stats</a>,</em>
-<em><a href="r.support.html">r.support</a>,</em>
-<em><a href="r.univar.html">r.univar</a>,</em>
-<em><a href="r.what.html">r.what</a></em>
-
-<h2>AUTHOR</h2>
-
-Michael O'Shea,
-<a href="http://www.cecer.army.mil/">U.S. Army Construction Engineering Research Laboratory</a>
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.info/r.info.html (from rev 32770, grass/trunk/raster/r.info/description.html)
===================================================================
--- grass/trunk/raster/r.info/r.info.html (rev 0)
+++ grass/trunk/raster/r.info/r.info.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,113 @@
+<h2>DESCRIPTION</h2>
+
+<em>r.info</em> reports some basic information about a
+user-specified raster map layer. This map layer must exist
+in the user's current mapset search path. Information
+about the map's boundaries, resolution, projection, data
+type, category number, data base location and mapset,
+the timestamp and history are put into a table and written to standard
+output. The types of information listed can also be found
+in the <i>cats</i>, <i>cellhd</i>, and <i>hist</i>
+directories under the mapset in which the named map is
+stored.
+
+<p>
+
+The user can save the tabular output to a file
+by using the UNIX redirection mechanism (>); for example, the user
+might save a report on the <em>soils</em> map layer in a file called
+<em>soil.rpt</em> by typing:
+
+<div class="code"><pre>
+r.info map=soils > soil.rpt
+</pre></div>
+
+<h2>NOTES</h2>
+
+On large maps, the total number of cells in the map may not be displayed
+with an accurate number. This is only cosmetic.
+
+<p>
+
+Some standards (ISO-C90) and compilers do not support the 'long long' type
+as a 64-bit type. In the case that GRASS was built with such a compiler,
+an accuracy message may be displayed in the output of <em>r.info</em>
+after Total Cells:
+
+<p>
+
+<h2>EXAMPLES</h2>
+
+Below is a full report produced by <em>r.info</em> for the raster map
+<i>slope</i> in the Spearfish sample data base:
+
+<div class="code"><pre>
+ +----------------------------------------------------------------------------+
+ | Layer: slope Date: Mon Nov 5 10:55:57 2001 |
+ | Mapset: PERMANENT Login of Creator: neteler |
+ | Location: spearfish60 |
+ | DataBase: /home/neteler/grassdaten |
+ | Title: slope in degrees ( slope ) |
+ | Timestamp: 20 Mar 1984 10:30 -0600 / 21 Mar 2020 10:30 -0600 |
+ |----------------------------------------------------------------------------|
+ | |
+ | Type of Map: raster Number of Categories: 255 |
+ | Data Type: FCELL |
+ | Rows: 477 |
+ | Columns: 634 |
+ | Total Cells: 302418 |
+ | Projection: UTM (zone 13) |
+ | N: 4928010 S: 4913700 Res: 30 |
+ | E: 609000 W: 589980 Res: 30 |
+ | Range of data: min = 0.000000 max = 52.520164 |
+ | |
+ | Data Source: |
+ | raster elevation file elevation.dem |
+ | |
+ | |
+ | Data Description: |
+ | generated by r.slope.aspect |
+ | |
+ | Comments: |
+ | slope map elev = elevation.dem |
+ | zfactor = 1.00 format = degrees |
+ | min_slp_allowed = 0.000000 |
+ | |
+ +----------------------------------------------------------------------------+
+</pre></div>
+
+Alternatively, the output from <em>r.info</em> may be confined to a more terse
+subset of the available information by passing various flags to the module:
+
+<div class="code"><pre>
+r.info -rst slope
+min=0.000000
+max=52.520164
+nsres=30
+ewres=30
+datatype=FCELL
+
+r.info -g slope
+north=4928030
+south=4913690
+east=609000
+west=589980
+</pre></div>
+
+<h2>SEE ALSO</h2>
+
+<em><a href="g.mapsets.html">g.mapsets</a>,</em>
+<em><a href="r.coin.html">r.coin</a>,</em>
+<em><a href="r.describe.html">r.describe</a>,</em>
+<em><a href="r.report.html">r.report</a>,</em>
+<em><a href="r.stats.html">r.stats</a>,</em>
+<em><a href="r.support.html">r.support</a>,</em>
+<em><a href="r.univar.html">r.univar</a>,</em>
+<em><a href="r.what.html">r.what</a></em>
+
+<h2>AUTHOR</h2>
+
+Michael O'Shea,
+<a href="http://www.cecer.army.mil/">U.S. Army Construction Engineering Research Laboratory</a>
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.kappa/description.html
===================================================================
--- grass/trunk/raster/r.kappa/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.kappa/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,66 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-
-<em>r.kappa</em> tabulates the error matrix of classification result by
-crossing classified map layer with respect to reference map layer. Both
-overall <em>kappa</em> (accompanied by its <em>variance</em>) and
-conditional <em>kappa</em> values are calculated. This analysis program
-respects the current geographic region and mask settings.
-<p>
-<em>r.kappa</em> calculates the error matrix of the
-two map layers and prepares the table from which the report
-is to be created. <em>kappa</em> values for overall and
-each classes are computed along with their variances. Also
-percent of commission and ommission error, total correct
-classified result by pixel counts, total area in pixel
-counts and percentage of overall correctly classified
-pixels are tabulated.
-
-<p>
-The report will be write to an output file which is in
-plain text format and named by user at prompt of running
-the program.
-
-
-<p>
-The body of the report is arranged in panels. The
-classified result map layer categories is arranged along
-the vertical axis of the table, while the reference map
-layer categories along the horizontal axis. Each panel has
-a maximum of 5 categories (9 if wide format) across the
-top. In addition, the last column of the last panel
-reflects a cross total of each column for each row. All of
-the categories of the map layer arranged along the vertical
-axis, i.e., the reference map layer, are included in each
-panel. There is a total at the bottom of each column
-representing the sum of all the rows in that column.
-
-
-<h2>NOTES</h2>
-
-It is recommended to reclassify categories of classified
-result map layer into a more manageable number before
-running <em>r.kappa</em> on the classified raster map
-layer. Because <em>r.kappa</em> calculates and then reports
-information for each and every category.
-
-<p>
-
-<em>NA</em>'s in output file mean non-applicable in case
-<em>MASK</em> exists.
-
-<h2>SEE ALSO</h2>
-
-<em><a href="g.region.html">g.region</a></em>,
-<!--<em><a href="m.ipf.html">m.ipf</a></em>,-->
-<em><a href="r.category.html">r.category</a></em>,
-<em><a href="r.mask.html">r.mask</a></em>,
-<em><a href="r.reclass.html">r.reclass</a></em>,
-<em><a href="r.report.html">r.report</a></em>,
-<em><a href="r.stats.html">r.stats</a></em>
-
-<h2>AUTHOR</h2>
-
-Tao Wen, University of Illinois at Urbana-Champaign, Illinois
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.kappa/r.kappa.html (from rev 32770, grass/trunk/raster/r.kappa/description.html)
===================================================================
--- grass/trunk/raster/r.kappa/r.kappa.html (rev 0)
+++ grass/trunk/raster/r.kappa/r.kappa.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,66 @@
+<h2>DESCRIPTION</h2>
+
+
+<em>r.kappa</em> tabulates the error matrix of classification result by
+crossing classified map layer with respect to reference map layer. Both
+overall <em>kappa</em> (accompanied by its <em>variance</em>) and
+conditional <em>kappa</em> values are calculated. This analysis program
+respects the current geographic region and mask settings.
+<p>
+<em>r.kappa</em> calculates the error matrix of the
+two map layers and prepares the table from which the report
+is to be created. <em>kappa</em> values for overall and
+each classes are computed along with their variances. Also
+percent of commission and ommission error, total correct
+classified result by pixel counts, total area in pixel
+counts and percentage of overall correctly classified
+pixels are tabulated.
+
+<p>
+The report will be write to an output file which is in
+plain text format and named by user at prompt of running
+the program.
+
+
+<p>
+The body of the report is arranged in panels. The
+classified result map layer categories is arranged along
+the vertical axis of the table, while the reference map
+layer categories along the horizontal axis. Each panel has
+a maximum of 5 categories (9 if wide format) across the
+top. In addition, the last column of the last panel
+reflects a cross total of each column for each row. All of
+the categories of the map layer arranged along the vertical
+axis, i.e., the reference map layer, are included in each
+panel. There is a total at the bottom of each column
+representing the sum of all the rows in that column.
+
+
+<h2>NOTES</h2>
+
+It is recommended to reclassify categories of classified
+result map layer into a more manageable number before
+running <em>r.kappa</em> on the classified raster map
+layer. Because <em>r.kappa</em> calculates and then reports
+information for each and every category.
+
+<p>
+
+<em>NA</em>'s in output file mean non-applicable in case
+<em>MASK</em> exists.
+
+<h2>SEE ALSO</h2>
+
+<em><a href="g.region.html">g.region</a></em>,
+<!--<em><a href="m.ipf.html">m.ipf</a></em>,-->
+<em><a href="r.category.html">r.category</a></em>,
+<em><a href="r.mask.html">r.mask</a></em>,
+<em><a href="r.reclass.html">r.reclass</a></em>,
+<em><a href="r.report.html">r.report</a></em>,
+<em><a href="r.stats.html">r.stats</a></em>
+
+<h2>AUTHOR</h2>
+
+Tao Wen, University of Illinois at Urbana-Champaign, Illinois
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.lake/description.html
===================================================================
--- grass/trunk/raster/r.lake/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.lake/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,90 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<p>The module fills a lake to a target water level from a given start point. The user
-can think of it as <em>r.grow</em> with additional checks for elevation. The resulting
-raster map contains cells with values representing lake depth and NULL for all other
-cells beyond the lake.</p>
-
-<p>This module uses a 3x3 moving window approach to find all cells that
-match three criteria and to define the lake:
-
-<ul>
- <li>cells are below the specified elevation (i.e., water level);</li>
- <li>cells are connected with an initial cell (seed or E,N value);</li>
- <li>cells are not NULL or masked.</li>
-</ul>
-</p>
-
-<p>The water level must be in DEM units.</p>
-
-<h2>NOTES</h2>
-
-The seed (starting) point can be a raster map with at least one
-cell value greater than zero, or a seed point can be specified as an E,
-N coordinate pair. If the seed is specified as a coordinate pair, an additional
-check is done to make sure that the target water level is above the level of
-the DEM. When a raster map is used as a seed, however, no such checks are done.
-Specifying a target water level below surface represented by DEM will result in an
-empty map. Note: a raster lake map created in a previous run can also be used
-as a seed map for a new run to simulate rising water levels.</p>
-
-<p>
-
-The module will create a new map (<b>lake=foo</b>) or can be set to replace
-the input (<b>seed=bar</b>) map if the <b>-o</b> flag is used. The user can use
-<b>-o</b> flag to create animations of rising water level without
-producing a separate map for each frame. An initial seed map must be created
-to start the sequence, and will be overwritten during subsequent runs with resulting
-water levels maps (i.e., a single file serves for both input and output).</p>
-
-<p>
-
-Negative output (the <b>-n</b> flag) is useful for visualisations in NVIZ.
-It equals the mapcalc's expression <em>"negative = 0 - positive"</em>.</p>
-
-<h3>MAPCALC EQUIVALENT - FOR GRASS HACKERS</h3>
-
-This module was initially created as a script using
-<em>r.mapcalc</em>. This had some limitations - it was slow and no
-checks where done to find out required iteration count. The shell script
-code (using <em>r.mapcalc</em>) used in the original script is shown below:
-
-<div class="code"><pre>
-${seedmap} = if( ${dem}, \
-if( if( isnull(${seedmap}),0,${seedmap}>0), ${wlevel}-${dem}, \
- if( \
- if(isnull(${seedmap}[-1,0]),0, ${seedmap}[-1,0]>0 && ${wlevel}>${dem}) ||\
- if(isnull(${seedmap}[-1,1]),0, ${seedmap}[-1,1]>0 && ${wlevel}>${dem}) ||\
- if(isnull(${seedmap}[0,1]), 0, ${seedmap}[0,1]>0 && ${wlevel}>${dem}) ||\
- if(isnull(${seedmap}[1,1]), 0, ${seedmap}[1,1]>0 && ${wlevel}>${dem}) ||\
- if(isnull(${seedmap}[1,0]), 0, ${seedmap}[1,0]>0 && ${wlevel}>${dem}) ||\
- if(isnull(${seedmap}[1,-1]),0, ${seedmap}[1,-1]>0 && ${wlevel}>${dem}) ||\
- if(isnull(${seedmap}[0,-1]),0, ${seedmap}[0,-1]>0 && ${wlevel}>${dem}) ||\
- if(isnull(${seedmap}[-1,-1]),0, ${seedmap}[-1,-1]>0 && ${wlevel}>${dem}),\
- ${wlevel}-${dem}, null() )))
-</pre></div>
-
-The ${seedmap} variable is replaced by seed map names, ${dem} with DEM map name, and
-${wlevel} with target water level. To get single water level, this code block is
-called with same level numerous times (in a loop) as the lake grows by single cells
-during single run.</p>
-
-<h2>BUGS/KNOWN ISSUES</h2>
-
-<ul>
- <li>The entire map is loaded into RAM.</li>
- <li>The module is NOT large file safe. (due to the previous point)</li>
- <li>A completely negative seed map will not work! At least one cell must have
- a value >0. Output from <em>r.lake -n</em> can NOT be used as input in the next run.</li>
-</ul>
-
-<h2>SEE ALSO</h2>
-
-<em><a href="r.mapcalc.html">r.mapcalc</a>,
-<a href="r.grow.html">r.grow</a>,
-<a href="r.plane.html">r.plane</a></em>
-
-<h2>AUTHOR</h2>
-Maris Nartiss (maris.nartiss gmail.com)
-
-<p><i>Last changed: $Date$</i></p>
Copied: grass/trunk/raster/r.lake/r.lake.html (from rev 32770, grass/trunk/raster/r.lake/description.html)
===================================================================
--- grass/trunk/raster/r.lake/r.lake.html (rev 0)
+++ grass/trunk/raster/r.lake/r.lake.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,90 @@
+<h2>DESCRIPTION</h2>
+
+<p>The module fills a lake to a target water level from a given start point. The user
+can think of it as <em>r.grow</em> with additional checks for elevation. The resulting
+raster map contains cells with values representing lake depth and NULL for all other
+cells beyond the lake.</p>
+
+<p>This module uses a 3x3 moving window approach to find all cells that
+match three criteria and to define the lake:
+
+<ul>
+ <li>cells are below the specified elevation (i.e., water level);</li>
+ <li>cells are connected with an initial cell (seed or E,N value);</li>
+ <li>cells are not NULL or masked.</li>
+</ul>
+</p>
+
+<p>The water level must be in DEM units.</p>
+
+<h2>NOTES</h2>
+
+The seed (starting) point can be a raster map with at least one
+cell value greater than zero, or a seed point can be specified as an E,
+N coordinate pair. If the seed is specified as a coordinate pair, an additional
+check is done to make sure that the target water level is above the level of
+the DEM. When a raster map is used as a seed, however, no such checks are done.
+Specifying a target water level below surface represented by DEM will result in an
+empty map. Note: a raster lake map created in a previous run can also be used
+as a seed map for a new run to simulate rising water levels.</p>
+
+<p>
+
+The module will create a new map (<b>lake=foo</b>) or can be set to replace
+the input (<b>seed=bar</b>) map if the <b>-o</b> flag is used. The user can use
+<b>-o</b> flag to create animations of rising water level without
+producing a separate map for each frame. An initial seed map must be created
+to start the sequence, and will be overwritten during subsequent runs with resulting
+water levels maps (i.e., a single file serves for both input and output).</p>
+
+<p>
+
+Negative output (the <b>-n</b> flag) is useful for visualisations in NVIZ.
+It equals the mapcalc's expression <em>"negative = 0 - positive"</em>.</p>
+
+<h3>MAPCALC EQUIVALENT - FOR GRASS HACKERS</h3>
+
+This module was initially created as a script using
+<em>r.mapcalc</em>. This had some limitations - it was slow and no
+checks where done to find out required iteration count. The shell script
+code (using <em>r.mapcalc</em>) used in the original script is shown below:
+
+<div class="code"><pre>
+${seedmap} = if( ${dem}, \
+if( if( isnull(${seedmap}),0,${seedmap}>0), ${wlevel}-${dem}, \
+ if( \
+ if(isnull(${seedmap}[-1,0]),0, ${seedmap}[-1,0]>0 && ${wlevel}>${dem}) ||\
+ if(isnull(${seedmap}[-1,1]),0, ${seedmap}[-1,1]>0 && ${wlevel}>${dem}) ||\
+ if(isnull(${seedmap}[0,1]), 0, ${seedmap}[0,1]>0 && ${wlevel}>${dem}) ||\
+ if(isnull(${seedmap}[1,1]), 0, ${seedmap}[1,1]>0 && ${wlevel}>${dem}) ||\
+ if(isnull(${seedmap}[1,0]), 0, ${seedmap}[1,0]>0 && ${wlevel}>${dem}) ||\
+ if(isnull(${seedmap}[1,-1]),0, ${seedmap}[1,-1]>0 && ${wlevel}>${dem}) ||\
+ if(isnull(${seedmap}[0,-1]),0, ${seedmap}[0,-1]>0 && ${wlevel}>${dem}) ||\
+ if(isnull(${seedmap}[-1,-1]),0, ${seedmap}[-1,-1]>0 && ${wlevel}>${dem}),\
+ ${wlevel}-${dem}, null() )))
+</pre></div>
+
+The ${seedmap} variable is replaced by seed map names, ${dem} with DEM map name, and
+${wlevel} with target water level. To get single water level, this code block is
+called with same level numerous times (in a loop) as the lake grows by single cells
+during single run.</p>
+
+<h2>BUGS/KNOWN ISSUES</h2>
+
+<ul>
+ <li>The entire map is loaded into RAM.</li>
+ <li>The module is NOT large file safe. (due to the previous point)</li>
+ <li>A completely negative seed map will not work! At least one cell must have
+ a value >0. Output from <em>r.lake -n</em> can NOT be used as input in the next run.</li>
+</ul>
+
+<h2>SEE ALSO</h2>
+
+<em><a href="r.mapcalc.html">r.mapcalc</a>,
+<a href="r.grow.html">r.grow</a>,
+<a href="r.plane.html">r.plane</a></em>
+
+<h2>AUTHOR</h2>
+Maris Nartiss (maris.nartiss gmail.com)
+
+<p><i>Last changed: $Date$</i></p>
Deleted: grass/trunk/raster/r.le/r.le.patch/description.html
===================================================================
--- grass/trunk/raster/r.le/r.le.patch/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.le/r.le.patch/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,40 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-The <em>r.le.patch</em> module calculates attribute, patch size, core
-(interior) size, shape, fractal dimension, and perimeter measures for sets
-of patches in a landscape.
-
-
-<h2>NOTES</h2>
-
-Full instructions can be found in the <b>r.le manual</b> (see "REFERENCES"
-section below) and the <em><a href="r.le.setup.html">r.le.setup</a></em>
-help page.
-
-
-<h2>REFERENCES</h2>
-
-Baker, W.L. and Y. Cai. 1992. The r.le programs for multiscale analysis of
-landscape structure using the GRASS geographical information system.
-Landscape Ecology 7(4):291-302.
-<p>
-The <A href="http://grass.itc.it/gdp/landscape/r_le_manual5.pdf"><i>r.le</i>
-manual: Quantitative analysis of landscape structures</a> (GRASS 5; 2001)
-
-<h2>SEE ALSO</h2>
-
-<em>
-<!-- <a href="r.le.dist.html">r.le.dist</a>,
-<a href="r.le.null.html">r.le.null</a>, -->
-<a href="r.le.pixel.html">r.le.pixel</a>,
-<!-- <a href="r.le.rename.html">r.le.rename</a>, -->
-<a href="r.le.setup.html">r.le.setup</a>,
-<a href="r.le.trace.html">r.le.trace</a></em>
-
-<h2>AUTHOR</h2>
-
-William L. Baker Department of Geography and Recreation University of
-Wyoming Laramie, Wyoming 82071 U.S.A.
-
-<p>
-<i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.le/r.le.patch/r.le.patch.html (from rev 32770, grass/trunk/raster/r.le/r.le.patch/description.html)
===================================================================
--- grass/trunk/raster/r.le/r.le.patch/r.le.patch.html (rev 0)
+++ grass/trunk/raster/r.le/r.le.patch/r.le.patch.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,40 @@
+<h2>DESCRIPTION</h2>
+
+The <em>r.le.patch</em> module calculates attribute, patch size, core
+(interior) size, shape, fractal dimension, and perimeter measures for sets
+of patches in a landscape.
+
+
+<h2>NOTES</h2>
+
+Full instructions can be found in the <b>r.le manual</b> (see "REFERENCES"
+section below) and the <em><a href="r.le.setup.html">r.le.setup</a></em>
+help page.
+
+
+<h2>REFERENCES</h2>
+
+Baker, W.L. and Y. Cai. 1992. The r.le programs for multiscale analysis of
+landscape structure using the GRASS geographical information system.
+Landscape Ecology 7(4):291-302.
+<p>
+The <A href="http://grass.itc.it/gdp/landscape/r_le_manual5.pdf"><i>r.le</i>
+manual: Quantitative analysis of landscape structures</a> (GRASS 5; 2001)
+
+<h2>SEE ALSO</h2>
+
+<em>
+<!-- <a href="r.le.dist.html">r.le.dist</a>,
+<a href="r.le.null.html">r.le.null</a>, -->
+<a href="r.le.pixel.html">r.le.pixel</a>,
+<!-- <a href="r.le.rename.html">r.le.rename</a>, -->
+<a href="r.le.setup.html">r.le.setup</a>,
+<a href="r.le.trace.html">r.le.trace</a></em>
+
+<h2>AUTHOR</h2>
+
+William L. Baker Department of Geography and Recreation University of
+Wyoming Laramie, Wyoming 82071 U.S.A.
+
+<p>
+<i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.le/r.le.pixel/description.html
===================================================================
--- grass/trunk/raster/r.le/r.le.pixel/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.le/r.le.pixel/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,39 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-The <em>r.le.pixel</em> module contains a set of measures for attributes,
-diversity, texture, juxtaposition, and edge.
-
-
-<h2>NOTES</h2>
-
-Full instructions can be found in the <b>r.le manual</b> (see "REFERENCES"
-section below) and the <em><a href="r.le.setup.html">r.le.setup</a></em>
-help page.
-
-
-<h2>REFERENCES</h2>
-
-Baker, W.L. and Y. Cai. 1992. The r.le programs for multiscale analysis of
-landscape structure using the GRASS geographical information system.
-Landscape Ecology 7(4):291-302.
-<p>
-The <A href="http://grass.itc.it/gdp/landscape/r_le_manual5.pdf"><i>r.le</i>
-manual: Quantitative analysis of landscape structures</a> (GRASS 5; 2001)
-
-<h2>SEE ALSO</h2>
-
-<em>
-<!-- <a href="r.le.dist.html">r.le.dist</a>,
-<a href="r.le.null.html">r.le.null</a>, -->
-<a href="r.le.patch.html">r.le.patch</a>,
-<!-- <a href="r.le.rename.html">r.le.rename</a>, -->
-<a href="r.le.setup.html">r.le.setup</a>,
-<a href="r.le.trace.html">r.le.trace</a></em>
-
-<h2>AUTHOR</h2>
-
-William L. Baker Department of Geography and Recreation University of
-Wyoming Laramie, Wyoming 82071 U.S.A.
-
-<p>
-<i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.le/r.le.pixel/r.le.pixel.html (from rev 32770, grass/trunk/raster/r.le/r.le.pixel/description.html)
===================================================================
--- grass/trunk/raster/r.le/r.le.pixel/r.le.pixel.html (rev 0)
+++ grass/trunk/raster/r.le/r.le.pixel/r.le.pixel.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,39 @@
+<h2>DESCRIPTION</h2>
+
+The <em>r.le.pixel</em> module contains a set of measures for attributes,
+diversity, texture, juxtaposition, and edge.
+
+
+<h2>NOTES</h2>
+
+Full instructions can be found in the <b>r.le manual</b> (see "REFERENCES"
+section below) and the <em><a href="r.le.setup.html">r.le.setup</a></em>
+help page.
+
+
+<h2>REFERENCES</h2>
+
+Baker, W.L. and Y. Cai. 1992. The r.le programs for multiscale analysis of
+landscape structure using the GRASS geographical information system.
+Landscape Ecology 7(4):291-302.
+<p>
+The <A href="http://grass.itc.it/gdp/landscape/r_le_manual5.pdf"><i>r.le</i>
+manual: Quantitative analysis of landscape structures</a> (GRASS 5; 2001)
+
+<h2>SEE ALSO</h2>
+
+<em>
+<!-- <a href="r.le.dist.html">r.le.dist</a>,
+<a href="r.le.null.html">r.le.null</a>, -->
+<a href="r.le.patch.html">r.le.patch</a>,
+<!-- <a href="r.le.rename.html">r.le.rename</a>, -->
+<a href="r.le.setup.html">r.le.setup</a>,
+<a href="r.le.trace.html">r.le.trace</a></em>
+
+<h2>AUTHOR</h2>
+
+William L. Baker Department of Geography and Recreation University of
+Wyoming Laramie, Wyoming 82071 U.S.A.
+
+<p>
+<i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.le/r.le.setup/description.html
===================================================================
--- grass/trunk/raster/r.le/r.le.setup/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.le/r.le.setup/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,472 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>r.le.setup</em> program is used to set
-up the sampling and analysis framework that will be used by the other
-<em>r.le</em> programs.
-
-<h2>NOTES</h2>
-
-<i>Full instructions can be found in the <b>r.le manual</b> (see "REFERENCES"
-section below).</i>
-<p>
-
-The first menu allows the user to define a rectangular sampling frame,
-select how sampling will be done (regions, sampling units, moving window),
-setup the limits for groups and classes, and change the color table.
-Use the left mouse button to make your choice.
-
-<p>
-
-Information about the structure of the landscape is obtained by overlaying
-a set of sampling areas on top of a specified part (the sampling frame of
-a map layer, and then calculating specific structural measures for the part
-of the map layer that corresponds to the area in each sampling area.
-
-<p>
-
-To setup a <em><b>sampling frame</b></em> click on SAMPLING FRAME in the
-main menu. The program will ask "Will the sampling frame (total area
-within which sampling units are distributed) be the whole map? (y/n) [y]"
-Just hit a carriage return to accept the default, which is to use the
-whole map. You do not need to setup a sampling frame if you want to use
-the whole map, as this is the default. To setup a different sampling
-frame type "n" in response to this question. Then use the mouse and a
-rubber band box to outline a rectangular sampling frame on screen.
-This box will be moved to the nearest row and column of the map.
-You will be asked last whether you want to "Refresh the screen before
-choosing more setup?" If you don't like the sampling frame you just setup,
-answer yes to this question, then click on SAMPLING FRAME again to redo
-this part of the setup. This sampling frame will be used in all subsequent
-setup procedures unless you change it. You can change it at any time by
-simply clicking on SAMPLING FRAME again.
-
-<p>
-
-A <em><b>sampling area</b></em> may be one of four things. First, it is
-possible to treat the entire map layer as the one (and only) sampling area.
-Second, if the map layer can be divided into meaningful geographical regions,
-then it is possible to treat the regions themselves as sampling areas.
-The third option is that the sampling areas may be sampling units of
-fixed shape and size (also called scale) that are placed within the map
-layer as a whole. The fourth and final option is that the sampling area
-may be moved systematically across the map as a moving window.
-
-<p>
-
-If regions are to be used as the sampling areas , then the user can use
-<em>r.le.setup</em> to draw regions or any existing map of regions can
-simply be used directly. To draw regions and create a new regions map
-in <em>r.le.setup</em> select "REGIONS" from the first <em>r.le.setup</em>
-menu, and the user is asked to do the following:
-
-<dl>
-<pre>
-1. "ENTER THE NEW REGION MAP NAME:". Only a new raster map name is
-acceptable. The user can type LIST to find out the existing raster map
-names in this location and mapset.
-
-2. "PLEASE OUTLINE REGION # 1". The user should move the mouse cursor
-into the graphic monitor window and use the mouse buttons as instructed:
-Left button: where am I.to display the current coordinates of the cursor.
-Middle button: Mark start (next) point. to enter a vertex of the region
-boundary.
-Right button: Finish region-connect to 1st point to close the region
-boundary by setting the last vertex to be equal to the first one.
-
-3. A "REGION OPTIONS:" menu is displayed and the user should use the mouse
-to select one of
- the options:<br>
-"DRAW MORE": repeat the above process and setup another region.
-"START OVER": abandon the previous setup and start all over again.
-"DONE-SAVE": save the regions outlined so far and exit this procedure.
-"QUIT-NO SAVE": quit the procedure without saving the regions.
-</pre>
-</dl>
-
-Once the "DONE-SAVE" option is selected, the new raster map of the sampling
-regions is generated. It is displayed on the monitor window for several
-seconds, the monitor window is refreshed, the main menu is displayed again,
-and the program is ready for other setup work. Note that you cannot draw
-regions in areas outside the mask, if a mask is present (see <em>r.mask</em>
-command).
-
-<p>
-
-The user can also use the GRASS <em>r.digit</em> or <em>v.digit</em>
-programs to digitize circular or polygonal regions and to create a
-sampling regions map without using <em>r.le.setup</em>. Or, as mention
-above, an existing raster map can be used as a regions map.
-
-<p>
-
-If sampling units are to be used as the sampling areas (Fig. 2), then
-choose "SAMPLING UNITS" from the first <em>r.le.setup</em> menu.
-The program checks the <em>r.le.para</em> subdirectory for an existing
-"units" file from a previous setup session and allows the user to rename
-this file (to save it) before proceeding. The r.le.setup program will
-otherwise overwrite the "units" file. Then the following choice is
-displayed followed by a series of other choices:
-
-<dl>
-<dd>
-<pre>
- Which do you want to do?
- (1) Use the keyboard to enter sampling unit parameters
- (2) Draw the sampling units with the mouse
- Enter 1 or 2:
-
-</pre>
-</dl>
-
-When sampling units are defined using the keyboard, the user inputs the
-shape and size (scale) of the sampling units by specifying dimensions
-in pixels using the keyboard. When sampling units are drawn with the
-mouse, the user clicks the mouse to define the sampling units in the
-GRASS monitor window, and then actually places the sampling units for
-each scale onto the map. By placing the units with the mouse the user
-can directly determine the method of sampling unit distribution as well
-as the shape, size, and number of sampling units.
-
-<p>
-
-If the choice is made to define sampling units using the keyboard, the
-following series of questions must be answered:
-
-<dl>
-<dd>
-<pre>
- How many different SCALES do you want (1-15)?
-</pre>
-</dl>
-
-The user is asked to specify the number of scales that will be used.
-The <em>r.le</em> programs allow the user to simultaneously sample the
-same map with the same measures using sampling areas of different sizes.
-Currently there can be between 1 and 15 scales that can be sampled
-simultaneously. Substantial output can be produced if many scales are used.
-
-<p>
-
-Sampling units must be placed spatially into the landscape. There are
-five options for doing this :
-
-<p>
-
-<em>Random nonoverlapping</em><br>
-Sampling units are placed in the landscape by randomly choosing numbers
-that specify the location of the upper left corner of each sampling unit,
-subject to the constraint that successive sampling units not overlap other
-sampling units or the edge of the landscape, and that they must be entirely
-within the area defined by the mask (see <em>r.mask</em> command) if one
-exists.
-
-<p>
-
-<em>Systematic contiguous</em><br>
-Sampling units are placed side by side across the rows. The user will
-be able to enter a row and column to indicate where the upper left corner
-of the systematic contiguous framework should be placed. Rows are numbered
-from the top down beginning with row 1 of the sampling frame. Columns are
-numbered from left to right, beginning with column 1 of the sampling frame.
-A random starting location can be obtained by using a standard random
-number table to choose the starting row and column. The <em>r.le.setup</em>
-program does not avoid placing the set of sampling units over areas
-outside the mask. The user will have to make sure that sampling units do
-not extend outside the mask by choosing a particular starting row and
-column or by drawing a sampling frame before placing the set of sampling
-units.
-
-<p>
-
-<em>Systematic noncontiguous</em><br>
-The user must specify the starting row and column as in #2 above and the
-amount of spacing (in pixels) between sampling units. Horizontal and
-vertical spacing are identical. Sampling units are again placed side by
-side (but spaced) across the rows. As in #2 the program does not avoid
-placing sampling units outside the masked area; the user will have to
-position the set of units to avoid areas outside the mask.
-
-<p>
-
-<em>Stratified random</em><br>
-The strata are rectangular areas within which single sampling units
-are randomly located. The user must first specify the starting row
-and column as in #2 above. Then the user must specify the number of
-strata in the horizontal and vertical directions. As in #2 the program
-does not avoid placing sampling units outside the masked area; the user
-will have to position the set of units to avoid areas outside the mask.
-
-<p>
-
-<em>Centered over sites</em><br>
-The user must specify the name of a sitefile containing point locations.
-A single sampling unit is placed with its center over each site in the site
-file. This is a useful approach for determining the landscape structure
-around points, such as around the location of wildlife observations.
-
-<p>
-
-The user is prompted to enter a ratio that defines the shape of the
-sampling units. Sampling units may have any rectangular shape,
-including square as a special case of rectangular. Rectangular shapes
-are specified by entering the ratio of columns/rows (horizontal
-dimension/vertical dimension) as a real number. For example, to obtain
-a sampling unit 10 columns wide by 4 rows long specify the ratio as 2.5
-(10/4).
-<dl>
-<dd>
-<pre>
- Recommended maximum SIZE is m in x cell total area. <br>
- What size (in cells) for each sampling unit of scale n?
-</pre>
-</dl>
-
-The user is then given the recommended maximum possible size for a
-sampling unit (in pixels) and asked to input the size of sampling units
-at each scale. Sampling units can be of any size, but the maximum size
-is the size of the landscape as a whole. All the sampling units, that
-make up a single sampling scale, are the same size. After specifying
-the size, the program determines the nearest actual number of rows and
-columns, and hence size, that is closest to the requested size, given
-the shape requested earlier.
-<dl>
-<dd>
-<pre>
- The nearest size is x cells wide X y cells high = xy cells
- Is this size OK? (y/n) [y]
-
- Maximum NUMBER of units in scale n is p?
- What NUMBER of sampling units do you want to try to use?
-</pre>
-</dl>
-
-The maximum number of units that can be placed over the map, given the
-shape and size of the units, is then given. The user can then choose
-the number of sampling units to be used in the map layer. It may not
-always be possible to choose the maximum number, depending upon the
-shape of the sampling units. In the case of systematic contiguous and
-noncontiguous, the program will indicate how many units will fit across
-the columns and down the rows. The user can then specify a particular
-layout (e.g., 6 units could be placed as 2 rows of 3 per row or as 3
-rows of 2 per row).
-<dl>
-<dd>
-<pre>
- Is this set of sampling units OK? (y/n) [y]
-</pre>
-</dl>
-
-Finally, the set of sampling units is displayed on the screen (e.g., Fig. 1)
-and the user is asked whether it is acceptable. If the answer is no, then
-the user is asked if the screen should be refreshed before redisplaying
-the menu for "Methods of sampling unit distribution" so that the user can
-try the sampling unit setup again.
-
-<p>
-
-The choice is made to define sampling units using the mouse, then the
-following menu for use with the mouse is displayed:
-<dl>
-<dd>
-<pre>
- Outline the standard sampling unit of scale n.
- Left button: Check unit size
- Middle button: Move cursor
- Right button: Lower right corner of unit here
-</pre>
-</dl>
-
-The user can then use the mouse and the rubber band box to outline the
-standard sampling unit. Once it has been outlined, the number of columns
-and rows in the unit, the ratio of width/length and the size of the unit,
-in cells, will be displayed. After this first unit is outlined, then a
-new menu is displayed:
-<dl>
-<dd>
-<pre>
- Outline more sampling units of scale n?
- Left button: Exit
- Middle button: Check unit position
- Right button: Lower right corner of next unit here
-</pre>
-</dl>
-
-The user can then place more units identical to the standard unit by
-simply clicking the right mouse button where the lower right corner of
-the unit should be placed. The rest of the rubber band box can be
-ignored while placing additional units. The program is set up so that
-units cannot be placed so they overlap one another, so they overlap the
-area outside the mask, or so they overlap the edge of the sampling frame.
-Warning messages are issued for all three of these errors and a sampling
-unit is simply not placed.
-
-<p>
-
-Using this procedure a rectangular "window" or single sampling area is
-moved systematically across the map to produce a new map (Fig. 2,3).
-This sampling procedure can only be used with the measures that produce
-a single value or with a single class or group when measures produce
-distributions of values (Table 1). The first class or group specified
-when defining class or group limits (section 2.3.2.) is used if
-distributional measures are chosen with the moving window sampling
-method. In this case, the user should manually edit the
-<em>r.le.para/recl_tb</em> file so that the desired group is listed as
-the first group in this file.
-
-<p>
-
-Sampling begins with the upper left corner of the window placed over
-the upper left corner of the sampling frame. It is strongly recommended
-that the user read the section on the GRASS mask (section 2.2.2) prior
-to setting up the moving window, as this mask can be used to speed up
-the moving window operation. The value of the chosen measure is
-calculated for the window area. This value is assigned to the location
-on the new map layer corresponding to the center pixel in the window if
-the window has odd (e.g. 3 X 3) dimensions. The value is assigned to
-the location on the new map layer corresponding to the first pixel below
-and to the right of the center if the window has even dimensions
-(e.g. 6 X 10). If this pixel has the value "0," which means "no data" in
-GRASS, then this pixel is skipped and a value of "0" is assigned to the
-corresponding location in the new map. The window is then moved to the
-right (across the row) by one pixel, and the process is repeated.
-At the end of the row, the window is moved down one pixel, and then back
-across the row. This option produces a new map layer, whose dimensions
-are smaller by approximately (m-1)/2 rows and columns, where m is the
-number of rows or columns in the window.
-
-<p>
-
-If the "MOVE-WINDOW" option in the main menu is selected, first the
-program checks for an existing "move_wind" file, in the r.le.para
-subdirectory, containing moving window specifications from a previous
-session. The user is given the option to avoid overwriting this file
-by entering a new file name for the old "move_wind" file. Users should
-be aware that moving window analyses are very slow, because a large
-number of sampling units are, in effect, used. See the appendix on
-"Time needed to complete analyses with the r.le programs" for some
-ideas about how moving window size and sampling frame area affect
-the needed time to complete the analyses.
-
-<p>
-
-The <em>r.le</em> programs <em>r.le.dist</em> and <em>r.le.patch</em>
-allow the attribute categories in the input map to be reclassed into
-several attribute groups, and reports the analysis results by each of
-these attribute groups. It is necessary to setup group limits for
-all measures that say "by gp" when typing "<em>r.le.dist help</em>"
-or "<em>r.le.patch help</em>" at the GRASS prompt. The same reclassing
-can be done with the measurement indices (e.g., size), except that each
-"cohort" (class) of the reclassed indices is called an index class
-instead of a group. It is also necessary to setup class limits for
-all measures that say "by class" when typing "<em>r.le.dist help</em>"
-or "<em>r.le.patch help</em>" at the GRASS prompt.
-
-<p>
-
-Group/class limits are setup by choosing "GROUP/CLASS LIMITS" from the
-main menu upon starting <em>r.le.setup</em>, or you can create the files
-manually using a text editor. The program checks for existing group/class
-limit files in subdirectory <em>r.le.para</em> and allows the user to
-rename these files prior to continuing. If the files are not renamed
-the program will overwrite them. The files are named recl_tb (attribute
-group limits), size (size class limits), shape_PA (shape index class
-limits for perimeter/area index), shape_CPA (shape index class limits
-for corrected perimeter/area index), shape_RCC (shape index class limits
-for related circumscribing circle index), and from_to (for the
-<em>r.le.dist</em> program distance methods m7-m9).
-
-<p>
-
-Attribute groups and index classes are defined in a different way.
-In the <em>r.le</em> programs attribute groups are defined as in the
-following example:
-<dl>
-<dd>
-<pre>
- 1, 3, 5, 7, 9 <b>thru</b> 21 = 1 (comment)
- 31 <b>thru</b> 50 = 2 (comment)
- <b>end</b>
-</pre>
-</dl>
-
-In this example, the existing categories 1, 3, 5, 7, {9, 10, ... 20, 21}
-are included in the new group 1, while {31, 32, 33, ..., 49, 50} are
-included in the new group 2. The characters in bold are the "key words"
-that are required in the definition. Each line is called one "reclass rule".
-
-<p>
-
-The GRASS reclass convention is adopted here with a little modification
-(see "<em>r.reclass</em>" command in the GRASS User's Manual).
-The difference is that r.le only allows one rule for each group while the
-GRASS <em>r.reclass</em> command allows more than one. The definition of
-"from" and "to" groups is simply the extension of the GRASS reclass rule.
-The advantage of using the GRASS reclass convention is that the user can
-generate a permanent reclassed map, using GRASS programs, directly from the
-<em>r.le</em> setup results.
-
-<p>
-
-The <em>r.le</em> measurement index classes are defined by the lower
-limits of the classes, as in the following example:
-<dl>
-<dd>
-<pre>
- 0.0, 10.0, 50.0, 200.0, <b>-999</b>
-</pre>
-</dl>
-
-This means:
-<dl>
-<dd>
-<pre>
- if v >= 0.0 and v < 10.0 then v belongs to index class 1;
- if v >= 10.0 and v < 50.0 then v belongs to index class 2;
- if v >= 50.0 and v < 200.0 then v belongs to index class 3;
- if v >= 200.0 then v belongs to index class 4;
-</pre>
-</dl>
-
-where v is the calculated index value and <b>-999</b> marks the end of
-the index class definition. The measurement index can be the size index,
-one of the three shape indices, or one of the three distance indices.
-The program is currently designed to allow no more than 25 attribute
-groups, 25 size classes, 25 shape index classes, and 25 distance index
-classes. As an alternative, the user may want to permanently group
-certain attributes prior to entering the <em>r.le</em> programs.
-For example, the user may want to group attributes 1-10, in a map whose
-attributes are ages, into a single attribute representing young patches.
-The user can do this using the GRASS <em>r.reclass</em> and
-<em>r.resample</em> commands, which will create a new map layer that can
-then be analyzed directly (without setting up group limits) with the
-<em>r.le</em> programs.
-
-
-
-<h2>REFERENCES</h2>
-
-Baker, W.L. and Y. Cai. 1992. The r.le programs for multiscale analysis of
-landscape structure using the GRASS geographical information system.
-Landscape Ecology 7(4):291-302.
-<p>
-The <A href="http://grass.itc.it/gdp/landscape/r_le_manual5.pdf"><i>r.le</i>
-manual: Quantitative analysis of landscape structures</a> (GRASS 5; 2001)
-
-
-<h2>SEE ALSO</h2>
-
-<em>
-<!-- <a href="r.le.dist.html">r.le.dist</a>,
-<a href="r.le.null.html">r.le.null</a>, -->
-<a href="r.le.patch.html">r.le.patch</a>,
-<a href="r.le.pixel.html">r.le.pixel</a>,
-<!-- <a href="r.le.rename.html">r.le.rename</a>, -->
-<a href="r.le.trace.html">r.le.trace</a></em>
-
-<h2>AUTHOR</h2>
-
-William L. Baker Department of Geography and Recreation University of
-Wyoming Laramie, Wyoming 82071 U.S.A.
-
-<p>
-<i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.le/r.le.setup/r.le.setup.html (from rev 32770, grass/trunk/raster/r.le/r.le.setup/description.html)
===================================================================
--- grass/trunk/raster/r.le/r.le.setup/r.le.setup.html (rev 0)
+++ grass/trunk/raster/r.le/r.le.setup/r.le.setup.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,472 @@
+<h2>DESCRIPTION</h2>
+
+<em>r.le.setup</em> program is used to set
+up the sampling and analysis framework that will be used by the other
+<em>r.le</em> programs.
+
+<h2>NOTES</h2>
+
+<i>Full instructions can be found in the <b>r.le manual</b> (see "REFERENCES"
+section below).</i>
+<p>
+
+The first menu allows the user to define a rectangular sampling frame,
+select how sampling will be done (regions, sampling units, moving window),
+setup the limits for groups and classes, and change the color table.
+Use the left mouse button to make your choice.
+
+<p>
+
+Information about the structure of the landscape is obtained by overlaying
+a set of sampling areas on top of a specified part (the sampling frame of
+a map layer, and then calculating specific structural measures for the part
+of the map layer that corresponds to the area in each sampling area.
+
+<p>
+
+To setup a <em><b>sampling frame</b></em> click on SAMPLING FRAME in the
+main menu. The program will ask "Will the sampling frame (total area
+within which sampling units are distributed) be the whole map? (y/n) [y]"
+Just hit a carriage return to accept the default, which is to use the
+whole map. You do not need to setup a sampling frame if you want to use
+the whole map, as this is the default. To setup a different sampling
+frame type "n" in response to this question. Then use the mouse and a
+rubber band box to outline a rectangular sampling frame on screen.
+This box will be moved to the nearest row and column of the map.
+You will be asked last whether you want to "Refresh the screen before
+choosing more setup?" If you don't like the sampling frame you just setup,
+answer yes to this question, then click on SAMPLING FRAME again to redo
+this part of the setup. This sampling frame will be used in all subsequent
+setup procedures unless you change it. You can change it at any time by
+simply clicking on SAMPLING FRAME again.
+
+<p>
+
+A <em><b>sampling area</b></em> may be one of four things. First, it is
+possible to treat the entire map layer as the one (and only) sampling area.
+Second, if the map layer can be divided into meaningful geographical regions,
+then it is possible to treat the regions themselves as sampling areas.
+The third option is that the sampling areas may be sampling units of
+fixed shape and size (also called scale) that are placed within the map
+layer as a whole. The fourth and final option is that the sampling area
+may be moved systematically across the map as a moving window.
+
+<p>
+
+If regions are to be used as the sampling areas , then the user can use
+<em>r.le.setup</em> to draw regions or any existing map of regions can
+simply be used directly. To draw regions and create a new regions map
+in <em>r.le.setup</em> select "REGIONS" from the first <em>r.le.setup</em>
+menu, and the user is asked to do the following:
+
+<dl>
+<pre>
+1. "ENTER THE NEW REGION MAP NAME:". Only a new raster map name is
+acceptable. The user can type LIST to find out the existing raster map
+names in this location and mapset.
+
+2. "PLEASE OUTLINE REGION # 1". The user should move the mouse cursor
+into the graphic monitor window and use the mouse buttons as instructed:
+Left button: where am I.to display the current coordinates of the cursor.
+Middle button: Mark start (next) point. to enter a vertex of the region
+boundary.
+Right button: Finish region-connect to 1st point to close the region
+boundary by setting the last vertex to be equal to the first one.
+
+3. A "REGION OPTIONS:" menu is displayed and the user should use the mouse
+to select one of
+ the options:<br>
+"DRAW MORE": repeat the above process and setup another region.
+"START OVER": abandon the previous setup and start all over again.
+"DONE-SAVE": save the regions outlined so far and exit this procedure.
+"QUIT-NO SAVE": quit the procedure without saving the regions.
+</pre>
+</dl>
+
+Once the "DONE-SAVE" option is selected, the new raster map of the sampling
+regions is generated. It is displayed on the monitor window for several
+seconds, the monitor window is refreshed, the main menu is displayed again,
+and the program is ready for other setup work. Note that you cannot draw
+regions in areas outside the mask, if a mask is present (see <em>r.mask</em>
+command).
+
+<p>
+
+The user can also use the GRASS <em>r.digit</em> or <em>v.digit</em>
+programs to digitize circular or polygonal regions and to create a
+sampling regions map without using <em>r.le.setup</em>. Or, as mention
+above, an existing raster map can be used as a regions map.
+
+<p>
+
+If sampling units are to be used as the sampling areas (Fig. 2), then
+choose "SAMPLING UNITS" from the first <em>r.le.setup</em> menu.
+The program checks the <em>r.le.para</em> subdirectory for an existing
+"units" file from a previous setup session and allows the user to rename
+this file (to save it) before proceeding. The r.le.setup program will
+otherwise overwrite the "units" file. Then the following choice is
+displayed followed by a series of other choices:
+
+<dl>
+<dd>
+<pre>
+ Which do you want to do?
+ (1) Use the keyboard to enter sampling unit parameters
+ (2) Draw the sampling units with the mouse
+ Enter 1 or 2:
+
+</pre>
+</dl>
+
+When sampling units are defined using the keyboard, the user inputs the
+shape and size (scale) of the sampling units by specifying dimensions
+in pixels using the keyboard. When sampling units are drawn with the
+mouse, the user clicks the mouse to define the sampling units in the
+GRASS monitor window, and then actually places the sampling units for
+each scale onto the map. By placing the units with the mouse the user
+can directly determine the method of sampling unit distribution as well
+as the shape, size, and number of sampling units.
+
+<p>
+
+If the choice is made to define sampling units using the keyboard, the
+following series of questions must be answered:
+
+<dl>
+<dd>
+<pre>
+ How many different SCALES do you want (1-15)?
+</pre>
+</dl>
+
+The user is asked to specify the number of scales that will be used.
+The <em>r.le</em> programs allow the user to simultaneously sample the
+same map with the same measures using sampling areas of different sizes.
+Currently there can be between 1 and 15 scales that can be sampled
+simultaneously. Substantial output can be produced if many scales are used.
+
+<p>
+
+Sampling units must be placed spatially into the landscape. There are
+five options for doing this :
+
+<p>
+
+<em>Random nonoverlapping</em><br>
+Sampling units are placed in the landscape by randomly choosing numbers
+that specify the location of the upper left corner of each sampling unit,
+subject to the constraint that successive sampling units not overlap other
+sampling units or the edge of the landscape, and that they must be entirely
+within the area defined by the mask (see <em>r.mask</em> command) if one
+exists.
+
+<p>
+
+<em>Systematic contiguous</em><br>
+Sampling units are placed side by side across the rows. The user will
+be able to enter a row and column to indicate where the upper left corner
+of the systematic contiguous framework should be placed. Rows are numbered
+from the top down beginning with row 1 of the sampling frame. Columns are
+numbered from left to right, beginning with column 1 of the sampling frame.
+A random starting location can be obtained by using a standard random
+number table to choose the starting row and column. The <em>r.le.setup</em>
+program does not avoid placing the set of sampling units over areas
+outside the mask. The user will have to make sure that sampling units do
+not extend outside the mask by choosing a particular starting row and
+column or by drawing a sampling frame before placing the set of sampling
+units.
+
+<p>
+
+<em>Systematic noncontiguous</em><br>
+The user must specify the starting row and column as in #2 above and the
+amount of spacing (in pixels) between sampling units. Horizontal and
+vertical spacing are identical. Sampling units are again placed side by
+side (but spaced) across the rows. As in #2 the program does not avoid
+placing sampling units outside the masked area; the user will have to
+position the set of units to avoid areas outside the mask.
+
+<p>
+
+<em>Stratified random</em><br>
+The strata are rectangular areas within which single sampling units
+are randomly located. The user must first specify the starting row
+and column as in #2 above. Then the user must specify the number of
+strata in the horizontal and vertical directions. As in #2 the program
+does not avoid placing sampling units outside the masked area; the user
+will have to position the set of units to avoid areas outside the mask.
+
+<p>
+
+<em>Centered over sites</em><br>
+The user must specify the name of a sitefile containing point locations.
+A single sampling unit is placed with its center over each site in the site
+file. This is a useful approach for determining the landscape structure
+around points, such as around the location of wildlife observations.
+
+<p>
+
+The user is prompted to enter a ratio that defines the shape of the
+sampling units. Sampling units may have any rectangular shape,
+including square as a special case of rectangular. Rectangular shapes
+are specified by entering the ratio of columns/rows (horizontal
+dimension/vertical dimension) as a real number. For example, to obtain
+a sampling unit 10 columns wide by 4 rows long specify the ratio as 2.5
+(10/4).
+<dl>
+<dd>
+<pre>
+ Recommended maximum SIZE is m in x cell total area. <br>
+ What size (in cells) for each sampling unit of scale n?
+</pre>
+</dl>
+
+The user is then given the recommended maximum possible size for a
+sampling unit (in pixels) and asked to input the size of sampling units
+at each scale. Sampling units can be of any size, but the maximum size
+is the size of the landscape as a whole. All the sampling units, that
+make up a single sampling scale, are the same size. After specifying
+the size, the program determines the nearest actual number of rows and
+columns, and hence size, that is closest to the requested size, given
+the shape requested earlier.
+<dl>
+<dd>
+<pre>
+ The nearest size is x cells wide X y cells high = xy cells
+ Is this size OK? (y/n) [y]
+
+ Maximum NUMBER of units in scale n is p?
+ What NUMBER of sampling units do you want to try to use?
+</pre>
+</dl>
+
+The maximum number of units that can be placed over the map, given the
+shape and size of the units, is then given. The user can then choose
+the number of sampling units to be used in the map layer. It may not
+always be possible to choose the maximum number, depending upon the
+shape of the sampling units. In the case of systematic contiguous and
+noncontiguous, the program will indicate how many units will fit across
+the columns and down the rows. The user can then specify a particular
+layout (e.g., 6 units could be placed as 2 rows of 3 per row or as 3
+rows of 2 per row).
+<dl>
+<dd>
+<pre>
+ Is this set of sampling units OK? (y/n) [y]
+</pre>
+</dl>
+
+Finally, the set of sampling units is displayed on the screen (e.g., Fig. 1)
+and the user is asked whether it is acceptable. If the answer is no, then
+the user is asked if the screen should be refreshed before redisplaying
+the menu for "Methods of sampling unit distribution" so that the user can
+try the sampling unit setup again.
+
+<p>
+
+The choice is made to define sampling units using the mouse, then the
+following menu for use with the mouse is displayed:
+<dl>
+<dd>
+<pre>
+ Outline the standard sampling unit of scale n.
+ Left button: Check unit size
+ Middle button: Move cursor
+ Right button: Lower right corner of unit here
+</pre>
+</dl>
+
+The user can then use the mouse and the rubber band box to outline the
+standard sampling unit. Once it has been outlined, the number of columns
+and rows in the unit, the ratio of width/length and the size of the unit,
+in cells, will be displayed. After this first unit is outlined, then a
+new menu is displayed:
+<dl>
+<dd>
+<pre>
+ Outline more sampling units of scale n?
+ Left button: Exit
+ Middle button: Check unit position
+ Right button: Lower right corner of next unit here
+</pre>
+</dl>
+
+The user can then place more units identical to the standard unit by
+simply clicking the right mouse button where the lower right corner of
+the unit should be placed. The rest of the rubber band box can be
+ignored while placing additional units. The program is set up so that
+units cannot be placed so they overlap one another, so they overlap the
+area outside the mask, or so they overlap the edge of the sampling frame.
+Warning messages are issued for all three of these errors and a sampling
+unit is simply not placed.
+
+<p>
+
+Using this procedure a rectangular "window" or single sampling area is
+moved systematically across the map to produce a new map (Fig. 2,3).
+This sampling procedure can only be used with the measures that produce
+a single value or with a single class or group when measures produce
+distributions of values (Table 1). The first class or group specified
+when defining class or group limits (section 2.3.2.) is used if
+distributional measures are chosen with the moving window sampling
+method. In this case, the user should manually edit the
+<em>r.le.para/recl_tb</em> file so that the desired group is listed as
+the first group in this file.
+
+<p>
+
+Sampling begins with the upper left corner of the window placed over
+the upper left corner of the sampling frame. It is strongly recommended
+that the user read the section on the GRASS mask (section 2.2.2) prior
+to setting up the moving window, as this mask can be used to speed up
+the moving window operation. The value of the chosen measure is
+calculated for the window area. This value is assigned to the location
+on the new map layer corresponding to the center pixel in the window if
+the window has odd (e.g. 3 X 3) dimensions. The value is assigned to
+the location on the new map layer corresponding to the first pixel below
+and to the right of the center if the window has even dimensions
+(e.g. 6 X 10). If this pixel has the value "0," which means "no data" in
+GRASS, then this pixel is skipped and a value of "0" is assigned to the
+corresponding location in the new map. The window is then moved to the
+right (across the row) by one pixel, and the process is repeated.
+At the end of the row, the window is moved down one pixel, and then back
+across the row. This option produces a new map layer, whose dimensions
+are smaller by approximately (m-1)/2 rows and columns, where m is the
+number of rows or columns in the window.
+
+<p>
+
+If the "MOVE-WINDOW" option in the main menu is selected, first the
+program checks for an existing "move_wind" file, in the r.le.para
+subdirectory, containing moving window specifications from a previous
+session. The user is given the option to avoid overwriting this file
+by entering a new file name for the old "move_wind" file. Users should
+be aware that moving window analyses are very slow, because a large
+number of sampling units are, in effect, used. See the appendix on
+"Time needed to complete analyses with the r.le programs" for some
+ideas about how moving window size and sampling frame area affect
+the needed time to complete the analyses.
+
+<p>
+
+The <em>r.le</em> programs <em>r.le.dist</em> and <em>r.le.patch</em>
+allow the attribute categories in the input map to be reclassed into
+several attribute groups, and reports the analysis results by each of
+these attribute groups. It is necessary to setup group limits for
+all measures that say "by gp" when typing "<em>r.le.dist help</em>"
+or "<em>r.le.patch help</em>" at the GRASS prompt. The same reclassing
+can be done with the measurement indices (e.g., size), except that each
+"cohort" (class) of the reclassed indices is called an index class
+instead of a group. It is also necessary to setup class limits for
+all measures that say "by class" when typing "<em>r.le.dist help</em>"
+or "<em>r.le.patch help</em>" at the GRASS prompt.
+
+<p>
+
+Group/class limits are setup by choosing "GROUP/CLASS LIMITS" from the
+main menu upon starting <em>r.le.setup</em>, or you can create the files
+manually using a text editor. The program checks for existing group/class
+limit files in subdirectory <em>r.le.para</em> and allows the user to
+rename these files prior to continuing. If the files are not renamed
+the program will overwrite them. The files are named recl_tb (attribute
+group limits), size (size class limits), shape_PA (shape index class
+limits for perimeter/area index), shape_CPA (shape index class limits
+for corrected perimeter/area index), shape_RCC (shape index class limits
+for related circumscribing circle index), and from_to (for the
+<em>r.le.dist</em> program distance methods m7-m9).
+
+<p>
+
+Attribute groups and index classes are defined in a different way.
+In the <em>r.le</em> programs attribute groups are defined as in the
+following example:
+<dl>
+<dd>
+<pre>
+ 1, 3, 5, 7, 9 <b>thru</b> 21 = 1 (comment)
+ 31 <b>thru</b> 50 = 2 (comment)
+ <b>end</b>
+</pre>
+</dl>
+
+In this example, the existing categories 1, 3, 5, 7, {9, 10, ... 20, 21}
+are included in the new group 1, while {31, 32, 33, ..., 49, 50} are
+included in the new group 2. The characters in bold are the "key words"
+that are required in the definition. Each line is called one "reclass rule".
+
+<p>
+
+The GRASS reclass convention is adopted here with a little modification
+(see "<em>r.reclass</em>" command in the GRASS User's Manual).
+The difference is that r.le only allows one rule for each group while the
+GRASS <em>r.reclass</em> command allows more than one. The definition of
+"from" and "to" groups is simply the extension of the GRASS reclass rule.
+The advantage of using the GRASS reclass convention is that the user can
+generate a permanent reclassed map, using GRASS programs, directly from the
+<em>r.le</em> setup results.
+
+<p>
+
+The <em>r.le</em> measurement index classes are defined by the lower
+limits of the classes, as in the following example:
+<dl>
+<dd>
+<pre>
+ 0.0, 10.0, 50.0, 200.0, <b>-999</b>
+</pre>
+</dl>
+
+This means:
+<dl>
+<dd>
+<pre>
+ if v >= 0.0 and v < 10.0 then v belongs to index class 1;
+ if v >= 10.0 and v < 50.0 then v belongs to index class 2;
+ if v >= 50.0 and v < 200.0 then v belongs to index class 3;
+ if v >= 200.0 then v belongs to index class 4;
+</pre>
+</dl>
+
+where v is the calculated index value and <b>-999</b> marks the end of
+the index class definition. The measurement index can be the size index,
+one of the three shape indices, or one of the three distance indices.
+The program is currently designed to allow no more than 25 attribute
+groups, 25 size classes, 25 shape index classes, and 25 distance index
+classes. As an alternative, the user may want to permanently group
+certain attributes prior to entering the <em>r.le</em> programs.
+For example, the user may want to group attributes 1-10, in a map whose
+attributes are ages, into a single attribute representing young patches.
+The user can do this using the GRASS <em>r.reclass</em> and
+<em>r.resample</em> commands, which will create a new map layer that can
+then be analyzed directly (without setting up group limits) with the
+<em>r.le</em> programs.
+
+
+
+<h2>REFERENCES</h2>
+
+Baker, W.L. and Y. Cai. 1992. The r.le programs for multiscale analysis of
+landscape structure using the GRASS geographical information system.
+Landscape Ecology 7(4):291-302.
+<p>
+The <A href="http://grass.itc.it/gdp/landscape/r_le_manual5.pdf"><i>r.le</i>
+manual: Quantitative analysis of landscape structures</a> (GRASS 5; 2001)
+
+
+<h2>SEE ALSO</h2>
+
+<em>
+<!-- <a href="r.le.dist.html">r.le.dist</a>,
+<a href="r.le.null.html">r.le.null</a>, -->
+<a href="r.le.patch.html">r.le.patch</a>,
+<a href="r.le.pixel.html">r.le.pixel</a>,
+<!-- <a href="r.le.rename.html">r.le.rename</a>, -->
+<a href="r.le.trace.html">r.le.trace</a></em>
+
+<h2>AUTHOR</h2>
+
+William L. Baker Department of Geography and Recreation University of
+Wyoming Laramie, Wyoming 82071 U.S.A.
+
+<p>
+<i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.le/r.le.trace/description.html
===================================================================
--- grass/trunk/raster/r.le/r.le.trace/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.le/r.le.trace/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,43 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-The <em>r.le.trace</em> module can be used to display the boundary of each
-<b>r.le</b> patch and show how the boundary is traced, display the attribute,
-size, perimeter, and shape indices for each patch, and save the data in an
-output file.
-
-
-<h2>NOTES</h2>
-
-Full instructions can be found in the <b>r.le manual</b> (see "REFERENCES"
-section below) and the <em><a href="r.le.setup.html">r.le.setup</a></em>
-help page.
-
-
-<h2>REFERENCES</h2>
-
-Baker, W.L. and Y. Cai. 1992. The r.le programs for multiscale analysis of
-landscape structure using the GRASS geographical information system.
-Landscape Ecology 7(4):291-302.
-<p>
-The <A href="http://grass.itc.it/gdp/landscape/r_le_manual5.pdf"><i>r.le</i>
-manual: Quantitative analysis of landscape structures</a> (GRASS 5; 2001)
-
-
-<h2>SEE ALSO</h2>
-
-<em>
-<!--<a href="r.le.dist.html">r.le.dist</a>,
-<a href="r.le.null.html">r.le.null</a>, -->
-<a href="r.le.patch.html">r.le.patch</a>,
-<a href="r.le.pixel.html">r.le.pixel</a>,
-<!-- <a href="r.le.rename.html">r.le.rename</a>, -->
-<a href="r.le.setup.html">r.le.setup</a>
-</em>
-
-<h2>AUTHOR</h2>
-
-William L. Baker Department of Geography and Recreation University of
-Wyoming Laramie, Wyoming 82071 U.S.A.
-
-<p>
-<i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.le/r.le.trace/r.le.trace.html (from rev 32770, grass/trunk/raster/r.le/r.le.trace/description.html)
===================================================================
--- grass/trunk/raster/r.le/r.le.trace/r.le.trace.html (rev 0)
+++ grass/trunk/raster/r.le/r.le.trace/r.le.trace.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,43 @@
+<h2>DESCRIPTION</h2>
+
+The <em>r.le.trace</em> module can be used to display the boundary of each
+<b>r.le</b> patch and show how the boundary is traced, display the attribute,
+size, perimeter, and shape indices for each patch, and save the data in an
+output file.
+
+
+<h2>NOTES</h2>
+
+Full instructions can be found in the <b>r.le manual</b> (see "REFERENCES"
+section below) and the <em><a href="r.le.setup.html">r.le.setup</a></em>
+help page.
+
+
+<h2>REFERENCES</h2>
+
+Baker, W.L. and Y. Cai. 1992. The r.le programs for multiscale analysis of
+landscape structure using the GRASS geographical information system.
+Landscape Ecology 7(4):291-302.
+<p>
+The <A href="http://grass.itc.it/gdp/landscape/r_le_manual5.pdf"><i>r.le</i>
+manual: Quantitative analysis of landscape structures</a> (GRASS 5; 2001)
+
+
+<h2>SEE ALSO</h2>
+
+<em>
+<!--<a href="r.le.dist.html">r.le.dist</a>,
+<a href="r.le.null.html">r.le.null</a>, -->
+<a href="r.le.patch.html">r.le.patch</a>,
+<a href="r.le.pixel.html">r.le.pixel</a>,
+<!-- <a href="r.le.rename.html">r.le.rename</a>, -->
+<a href="r.le.setup.html">r.le.setup</a>
+</em>
+
+<h2>AUTHOR</h2>
+
+William L. Baker Department of Geography and Recreation University of
+Wyoming Laramie, Wyoming 82071 U.S.A.
+
+<p>
+<i>Last changed: $Date$</i>
Modified: grass/trunk/raster/r.li/Makefile
===================================================================
--- grass/trunk/raster/r.li/Makefile 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.li/Makefile 2008-08-15 06:16:42 UTC (rev 32772)
@@ -23,8 +23,7 @@
include $(MODULE_TOPDIR)/include/Make/Dir.make
-default: parsubdirs
- $(INSTALL_DATA) description.html $(GISBASE)/docs/html/r.li.html
+default: parsubdirs htmldir
clean: cleansubdirs
Deleted: grass/trunk/raster/r.li/description.html
===================================================================
--- grass/trunk/raster/r.li/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.li/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,186 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-<head>
-<title>r.li</title>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link rel="stylesheet" href="grassdocs.css" type="text/css">
-</head>
-<body bgcolor="white">
-
-<img src="grass_logo.png" alt="GRASS logo"><hr align=center size=6 noshade>
-
-<h2>NAME</h2>
-<em><b>r.li</b></em> - package overview
-
-<h2>KEYWORDS</h2>
-raster, landscape structure analysis, overview, landscape metrics, landscape pattern, landscape analysis
-
-<h2>DESCRIPTION</h2>
-
-The <em>r.li</em> suite is a toolset for multiscale analysis of landscape structure.
-It aims at replacing the <em>r.le</em> suite of modules through a client-server,
-multiprocess implementation. External software for quantitative measures of landscape
-structure is for example FRAGSTATS (McGarigal and Marks 1995).
-<p>
-The <em>r.li</em> suite offers a set of patch and diversity indices.
-It supports analysis of landscapes composed of a mosaic of
-patches, but, more generally, the modules work with any two-dimensional
-raster map whose cell values are integer (e.g., 1, 2) or floating point
-(e.g., 1.1, 3.2) values. The <em>r.li.setup</em> module has options for
-controlling the shape, size, number, and distribution of sampling
-areas used to collect information about the landscape structure.
-Sampling area shapes can be the entire map or a moving
-window of square, rectangular or with circular shape. The size of
-sampling areas can be changed, so that the landscape can be analyzed
-at a variety of spatial scales simultaneously. Sampling areas may be
-distributed across the landscape in a random, systematic, or
-stratified-random manner, or as a moving window.
-<p>
-The <em>r.li</em> modules can calculate a number of measures that produce
-single values as output (e.g. mean patch size in the sampling area),
-as well as measures that produce a distribution of values as output
-(e.g. frequency distribution of patch sizes in the sampling area). The
-results are stored as raster maps.
-
-<p>
-The general procedure to calculate an index from a raster map is two-fold:
-
-<ol>
-<li>run <em>r.li.setup</em>: create a configuration file selecting the parts of
- raster to analyze.
-
-<li>run <em>r.li.'index'</em> (e.g., <em>r.li.patchdensity</em>) for calculate the selected
- index using on the areas selected on configuration file.
-</ol>
-
-<h2>NOTE</h2>
-
-Also the <em>r.li.daemon</em> has a main function and it can be run, but it is only a
-template for development of new indices.
-<!-- mhh ??: -->
-The function itself has no meaning, it can be used only for debug.
-
-<h2>EXAMPLE</h2>
-
-To calculate a patch density index on a whole 'geology' raster map in the
-Spearfish region, using a 5x5 moving window, follow this procedure:
-
-<ol>
-<li> CREATE A NEW CONFIGURATION FILE
- <ol>
- <li> run
-<div class="code"><pre>
- r.li.setup
-</pre></div>
- <li> The main <em>r.li.setup</em> window is displayed, click on "New"
- <li> Now it is displayed the new configuration window,
- enter the configuration file name (e.g., "my_conf", do not use absolute paths)
- and the name of raster map (e.g., "geology").
- The other fields are not needed for this configuration.
- <li> Click on "Setup sampling frame", select "Whole maplayer" and click "OK"
- <li> Click on "Setup sampling areas", select "Moving window" and click "OK"
- <li> Click on "Use keyboard to enter moving window dimension"
- <li> Select "Rectangle" and enter 5 on "heigth" and "width" fields
- <li> Click on "Save settings"
- <li> Close <em>r.li.setup</em> window
- </ol>
-<li> CALCULATE PATCHDENSITY INDEX
-<ol>
- <li> set region settings to geology raster map:
-<div class="code"><pre>
- g.region rast=geology -p
-</pre></div>
- <li> run <em>r.li.patchdensity</em>:
-<div class="code"><pre>
- r.li.patchdensity map=geology conf=my_conf out=patchdens
-</pre></div>
- </ol>
-</ol>
-
-The resulting patch density is stored in "patchdens" raster map.
-
-You can verify the result for example with contour lines:
-<div class="code"><pre>
-r.contour in=patchdens out=patchdens step=5
-d.rast patchdens
-d.vect -c patchdens
-</pre></div>
-
-Note that if you want to run another index with the same area
-configuration, you don't have to create another configuration file.
-
-You can also use the same area configuration file on another map. The
-program rescale it automatically. For instance if you have selected a
-5x5 sample area on 100x100 raster map, and you use the same
-configuration file on a 200x200 raster map, then the sample area is
-10x10.
-
-<h2>SEE ALSO</h2>
-
-<b>Core modules</b>:
-<ul>
- <li> <a href="r.li.daemon.html">r.li.daemon</a>: job launch daemon</li>
- <li> <a href="r.li.setup.html">r.li.setup</a>: Configuration editor for r.li.'index'</li>
-</ul>
-
-<b>Patch indices</b>:
-<ul>
-<li>Indices based on patch number:
-<ul>
- <li> <a href="r.li.patchdensity.html">r.li.patchdensity</a>: Calculates patch density index on a raster map, using a 4 neighbour algorithm</li>
- <li> <a href="r.li.patchnum.html">r.li.patchnum</a>: Calculates patch number index on a raster map, using a 4 neighbour algorithm</li>
-</ul>
-<li>Indices based on patch dimension:
-<ul>
- <li> <a href="r.li.mps.html">r.li.mps</a>: Calculates mean patch size index on a raster map, using a 4 neighbour algorithm</li>
- <li> <a href="r.li.padcv.html">r.li.padcv</a>: Calculates coefficient of variation of patch area on a raster map</li>
- <li> <a href="r.li.padrange.html">r.li.padrange</a>: Calculates range of patch area size on a raster map</li>
- <li> <a href="r.li.padsd.html">r.li.padsd</a>: Calculates standard deviation of patch area a raster map</li>
-</ul>
-<li>Indices based on patch shape:
-<ul>
- <li> <a href="r.li.shape.html">r.li.shape</a>: Calculates shape index on a raster map</li>
-</ul>
-<li>Indices based on patch edge: <!-- border? -->
-<ul>
- <li> <a href="r.li.edgedensity.html">r.li.edgedensity</a>: Calculates edge density index on a raster map, using a 4 neighbour algorithm</li>
-</ul>
-<li>Indices based on patch attributes:
-<ul>
- <li> <a href="r.li.cwed.html">r.li.cwed</a>: Calculates contrast Weighted Edge Density index on a raster map</li>
- <li> <a href="r.li.mpa.html">r.li.mpa</a>: Calculates mean pixel attribute index on a raster map</li>
-</ul>
-</ul>
-
-<b>Diversity indices</b>:
-<ul>
- <li> <a href="r.li.dominance.html">r.li.dominance</a>: Calculates dominance's diversity index on a raster map</li>
- <li> <a href="r.li.richness.html">r.li.richness</a>: Calculates dominance's diversity index on a raster map</li>
- <li> <a href="r.li.shannon.html">r.li.shannon</a>: Calculates Shannon's diversity index on a raster map</li>
- <li> <a href="r.li.simpson.html">r.li.simpson</a>: Calculates Simpson's diversity index on a raster map</li>
-</ul>
-
-<h2>ADDING NEW INDICES</h2>
-New indices can be defined and implemented by any C programmer, without having to
-deal with all basic functions (IO etc.). The computing architecture and the functions
-are clearly separated, thus allowing an easy expandability. Every index is defined
-separately, placed in a directory along with its Makefile for compiling it and a file
-description.html which describes the index including a simple example of use.
-
-<h2>REFERENCES</h2>
-
-McGarigal, K., and B. J. Marks. 1995. FRAGSTATS: spatial pattern
-analysis program for quantifying landscape structure. USDA For. Serv.
-Gen. Tech. Rep. PNW-351 (<a href="http://www.fs.fed.us/pnw/pubs/gtr_351.pdf">PDF</a>).
-
-<h2>AUTHORS</h2>
-<a href="mailto:porta at cli.di.unipi.it">Claudio Porta</a> and
-<a href="mailto:spano at cli.di.unipi.it">Lucio Davide Spano</a>, students of Computer Science
-University of Pisa (Italy). <br>
-Commission from Faunalia Pontedera (PI)<br>
-
-<p><i>Last changed: $Date$</i>
-<hr>
-<p><a href="index.html">Main index</a> - <a href="raster.html">raster index</a> - <a href="full_index.html">Full index</a>
-</body>
-</html>
Deleted: grass/trunk/raster/r.li/r.li.cwed/description.html
===================================================================
--- grass/trunk/raster/r.li/r.li.cwed/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.li/r.li.cwed/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,70 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-<EM>r.li.cwed</EM> (contrast weighted edge density) calculates the edge density
-between patch types specified:
-<P><img src="rlicwed_formula.png"> </P>
-<P>with:
-
-<ul>
-<li> <B>k</B>: attribute<BR>
-<li> <B>m</B>: number of non-null attributes in the sampling area<BR>
-<li> <B>e<small><small>ik</small></small></B>: total length of edge in landscape between patch types i and k<BR>
-<li><B> d<small><small>ik</small></small></B>: dissimilarity (edge contrast weight) between patch types i and k<BR>
-<li> <B>Area</B>: total landscape area<BR>
-</ul><BR>
-
-The input file have a row for each couple of patch type that we want to
-consider in the calculation. Each row must to have this syntax:<BR>
-<small>patchType1,patchType2,dissimilarityBetweenPatchType1andPatchType2</small><BR>
-
-
-<H2>EXAMPLES</H2>
-To calculate mean pixel attribute index on map my_map, using
-my_conf configuration file and saving results in
-my_out file run:<BR>
-<div class="code"><pre>
-r.li.cwed map=my_map conf=my_conf path=my_file output=my_out
-</pre></div>
-
-<BR>Example of input file:<BR>
-12,16,0.65<BR>
-44,123,0.32<BR>
-56,12,0.54<BR>
-23,66,0.99<BR>
-
-<H2>NOTES</H2>
-Do not use absolute path names for output files. They are raster if
-moving window disposition was selected, otherwise they are in
-~/.r.li/output folder.
-<BR>
-If the raster is full of null value it is considered to have 0 patch and CWED=0.
-If Area is 0 r.li.cwed returns -1. This is possible
-only if the map is masked.<BR>
-If you want to have null values instead run <BR>
-<div class="code"><pre>
-r.null setnull=-1 map=my_map
-</pre></div>
-after index calculation.<BR>
-<BR>
-
-<H2>REFERENCES</H2>
-McGarigal, K., and B. J. Marks. 1995. FRAGSTATS: spatial pattern
-analysis program for quantifying landscape structure. USDA For. Serv.
-Gen. Tech. Rep. PNW-351.
-
-<H2>SEE ALSO</H2>
-
-<EM><A HREF="r.li.html">r.li</A></EM> package overview <BR>
-<EM><A HREF="r.li.daemon.html">r.li.daemon</A></EM><BR>
-<EM><A HREF="r.li.setup.html">r.li.setup</A></EM>
-
-<H2>AUTHORS</H2>
-Serena Pallecchi student of Computer Science University of Pisa (Italy).<BR>
-Commission from Faunalia Pontedera (PI), Italy (www.faunalia.it)
-
-<H2>BUGS</H2>
-Please send bugs reports to
-<a href="mailto:pallecch at cli.di.unipi.it">pallecch at cli.di.unipi.it</a><BR>
-
-<p><i>Last changed: $Date$</i></p>
-
Copied: grass/trunk/raster/r.li/r.li.cwed/r.li.cwed.html (from rev 32770, grass/trunk/raster/r.li/r.li.cwed/description.html)
===================================================================
--- grass/trunk/raster/r.li/r.li.cwed/r.li.cwed.html (rev 0)
+++ grass/trunk/raster/r.li/r.li.cwed/r.li.cwed.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,70 @@
+<H2>DESCRIPTION</H2>
+
+<EM>r.li.cwed</EM> (contrast weighted edge density) calculates the edge density
+between patch types specified:
+<P><img src="rlicwed_formula.png"> </P>
+<P>with:
+
+<ul>
+<li> <B>k</B>: attribute<BR>
+<li> <B>m</B>: number of non-null attributes in the sampling area<BR>
+<li> <B>e<small><small>ik</small></small></B>: total length of edge in landscape between patch types i and k<BR>
+<li><B> d<small><small>ik</small></small></B>: dissimilarity (edge contrast weight) between patch types i and k<BR>
+<li> <B>Area</B>: total landscape area<BR>
+</ul><BR>
+
+The input file have a row for each couple of patch type that we want to
+consider in the calculation. Each row must to have this syntax:<BR>
+<small>patchType1,patchType2,dissimilarityBetweenPatchType1andPatchType2</small><BR>
+
+
+<H2>EXAMPLES</H2>
+To calculate mean pixel attribute index on map my_map, using
+my_conf configuration file and saving results in
+my_out file run:<BR>
+<div class="code"><pre>
+r.li.cwed map=my_map conf=my_conf path=my_file output=my_out
+</pre></div>
+
+<BR>Example of input file:<BR>
+12,16,0.65<BR>
+44,123,0.32<BR>
+56,12,0.54<BR>
+23,66,0.99<BR>
+
+<H2>NOTES</H2>
+Do not use absolute path names for output files. They are raster if
+moving window disposition was selected, otherwise they are in
+~/.r.li/output folder.
+<BR>
+If the raster is full of null value it is considered to have 0 patch and CWED=0.
+If Area is 0 r.li.cwed returns -1. This is possible
+only if the map is masked.<BR>
+If you want to have null values instead run <BR>
+<div class="code"><pre>
+r.null setnull=-1 map=my_map
+</pre></div>
+after index calculation.<BR>
+<BR>
+
+<H2>REFERENCES</H2>
+McGarigal, K., and B. J. Marks. 1995. FRAGSTATS: spatial pattern
+analysis program for quantifying landscape structure. USDA For. Serv.
+Gen. Tech. Rep. PNW-351.
+
+<H2>SEE ALSO</H2>
+
+<EM><A HREF="r.li.html">r.li</A></EM> package overview <BR>
+<EM><A HREF="r.li.daemon.html">r.li.daemon</A></EM><BR>
+<EM><A HREF="r.li.setup.html">r.li.setup</A></EM>
+
+<H2>AUTHORS</H2>
+Serena Pallecchi student of Computer Science University of Pisa (Italy).<BR>
+Commission from Faunalia Pontedera (PI), Italy (www.faunalia.it)
+
+<H2>BUGS</H2>
+Please send bugs reports to
+<a href="mailto:pallecch at cli.di.unipi.it">pallecch at cli.di.unipi.it</a><BR>
+
+<p><i>Last changed: $Date$</i></p>
+
Modified: grass/trunk/raster/r.li/r.li.daemon/Makefile
===================================================================
--- grass/trunk/raster/r.li/r.li.daemon/Makefile 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.li/r.li.daemon/Makefile 2008-08-15 06:16:42 UTC (rev 32772)
@@ -3,10 +3,10 @@
EXTRA_LIBS=$(GISLIB)
LIB_NAME = grass_rli
+PGM = r.li.daemon
DEPENDENCIES = $(GISDEP)
include $(MODULE_TOPDIR)/include/Make/Lib.make
-default: lib
- $(INSTALL_DATA) description.html $(GISBASE)/docs/html/r.li.daemon.html
+default: lib htmldir
Deleted: grass/trunk/raster/r.li/r.li.daemon/description.html
===================================================================
--- grass/trunk/raster/r.li/r.li.daemon/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.li/r.li.daemon/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,95 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-<head>
-<title>r.li</title>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link rel="stylesheet" href="grassdocs.css" type="text/css">
-</head>
-<body bgcolor="white">
-
-<img src="grass_logo.png" alt="GRASS logo"><hr align=center size=6 noshade>
-
-<H2>DESCRIPTION</H2>
-
-<EM>r.li.daemon</EM> provides a support for landscape index calculation on raster
-maps. It hides the managment of areas, defined using <a href="r.li.setup.html">r.li.setup</a>
-command. It do not have to be used like a standalone program, but its functions are
-a library used by all <em>r.li.[index]</em> commands.<br>
-This description is a tutorial for new index definition. <br><br>
-The developer has only to focus on a unique area, like in mathematical definitions, and
-has to write a C implementation of it.<br>
-The areas are defined using a <em>struct</em> called <b>area_des</b> and it members are
-explained in the source code (doxygen) documentation.
-<p>
-To write a new index only two steps are needed:
-<ol>
- <li>
- Define a function and insert its declaration on file <b>index.h</b> in <em>r.li.daemon</em>
- folder, which contains all index declarations. This function must be of this kind:
- <br><div class="code"><pre>
- int index(int fd, char ** par, area_des ad, double * result)
- </pre></div><br>
- where: <ul>
- <li><i>fd</i> is the raster map descriptor
- <li><i>par</i> is a matrix for special parameter (like argv in main)
- <li><i>ad</i> is the area descriptor
- <li><i>result</i> is where to put the index calculation result
- </ul>
- This function has to return 1 on success and 0 otherwise. <br><br>
- <li>
- Create a main for command line arguments parsing, and call the function
- <br><div class="code"><pre>
- int calculateIndex(char * file, int f(int, char** area_des, double *), char **parameters, char *raster, char *output);
- </pre></div><br>
- from the <i>r.li</i> library, for starting raster analysis.<br>
- It follows the meaning of parameters:
- <ul>
- <li><i>file</i> name of configuration file created using <a href="r.li.setup.html">r.li.setup</a>
- <li><i>f</i> pointer to index function defined above
- <li><i>parameters</i> pointer to index special parameters
- <li><i>raster</i> name of raster to use
- <li><i>output</i> output file name
- </ul>
-</ol>
-Compile it using a changed Makefile based on the file for <em>r.li.patchdensity</em>.
-
-<H2>NOTES</H2>
-Using GRASS library function to access raster rows can slow down moving windows
-execution. It is recommended to use
-<br><div class="code"><pre>
-RLI_get_cell_row(int, int, area_des)
-RLI_get_fcell_row(int, int, area_des)
-RLI_get_dcell_row(int, int, area_des)
-</pre></div><br>
-to use an ad hoc build memory managment developed to speed up the system.
-The documentation is in doxygen files.
-
-
-<H2>SEE ALSO</H2>
-
-<EM><A HREF="http://grass.itc.it/gdp/landscape/r_le_manual5.pdf">old r.le manual</A></EM><BR>
-<EM><A HREF="r.li.html">r.li</A></EM> package overview <BR>
-<EM><A HREF="r.li.patchdensity.html">r.li.patchdensity</A></EM>,
-<EM><A HREF="r.li.setup.html">r.li.setup</A></EM>
-
-<H2>AUTHORS</H2>
-Claudio Porta and Lucio Davide Spano, students of Computer Science
-University of Pisa (Italy).<br>
-Commission from Faunalia Pontedera (PI)<br>
-Rebuild of r.le.setup from William L. Baker
-This program is free software under the GPL (>=v2)
-Read the COPYING file that comes with GRASS for details.
-
-
-<H2>BUGS</h2>
-Pleas send bugs reports to
-<a href="mailto:spano at cli.di.unipi.it">spano at cli.di.unipi.it</a>,
-<a href="mailto:porta at cli.di.unipi.it">porta at cli.di.unipi.it</a><br>
-<BR>
-
-<p><i>Last changed: $Date$</i>
-
-<HR>
-<P><a href="index.html">Main index</a> - <a href="raster.html">raster index</a> - <a href="full_index.html">Full index</a>
-</body>
-</html>
Copied: grass/trunk/raster/r.li/r.li.daemon/r.li.daemon.html (from rev 32770, grass/trunk/raster/r.li/r.li.daemon/description.html)
===================================================================
--- grass/trunk/raster/r.li/r.li.daemon/r.li.daemon.html (rev 0)
+++ grass/trunk/raster/r.li/r.li.daemon/r.li.daemon.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,95 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<head>
+<title>r.li</title>
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
+<link rel="stylesheet" href="grassdocs.css" type="text/css">
+</head>
+<body bgcolor="white">
+
+<img src="grass_logo.png" alt="GRASS logo"><hr align=center size=6 noshade>
+
+<H2>DESCRIPTION</H2>
+
+<EM>r.li.daemon</EM> provides a support for landscape index calculation on raster
+maps. It hides the managment of areas, defined using <a href="r.li.setup.html">r.li.setup</a>
+command. It do not have to be used like a standalone program, but its functions are
+a library used by all <em>r.li.[index]</em> commands.<br>
+This description is a tutorial for new index definition. <br><br>
+The developer has only to focus on a unique area, like in mathematical definitions, and
+has to write a C implementation of it.<br>
+The areas are defined using a <em>struct</em> called <b>area_des</b> and it members are
+explained in the source code (doxygen) documentation.
+<p>
+To write a new index only two steps are needed:
+<ol>
+ <li>
+ Define a function and insert its declaration on file <b>index.h</b> in <em>r.li.daemon</em>
+ folder, which contains all index declarations. This function must be of this kind:
+ <br><div class="code"><pre>
+ int index(int fd, char ** par, area_des ad, double * result)
+ </pre></div><br>
+ where: <ul>
+ <li><i>fd</i> is the raster map descriptor
+ <li><i>par</i> is a matrix for special parameter (like argv in main)
+ <li><i>ad</i> is the area descriptor
+ <li><i>result</i> is where to put the index calculation result
+ </ul>
+ This function has to return 1 on success and 0 otherwise. <br><br>
+ <li>
+ Create a main for command line arguments parsing, and call the function
+ <br><div class="code"><pre>
+ int calculateIndex(char * file, int f(int, char** area_des, double *), char **parameters, char *raster, char *output);
+ </pre></div><br>
+ from the <i>r.li</i> library, for starting raster analysis.<br>
+ It follows the meaning of parameters:
+ <ul>
+ <li><i>file</i> name of configuration file created using <a href="r.li.setup.html">r.li.setup</a>
+ <li><i>f</i> pointer to index function defined above
+ <li><i>parameters</i> pointer to index special parameters
+ <li><i>raster</i> name of raster to use
+ <li><i>output</i> output file name
+ </ul>
+</ol>
+Compile it using a changed Makefile based on the file for <em>r.li.patchdensity</em>.
+
+<H2>NOTES</H2>
+Using GRASS library function to access raster rows can slow down moving windows
+execution. It is recommended to use
+<br><div class="code"><pre>
+RLI_get_cell_row(int, int, area_des)
+RLI_get_fcell_row(int, int, area_des)
+RLI_get_dcell_row(int, int, area_des)
+</pre></div><br>
+to use an ad hoc build memory managment developed to speed up the system.
+The documentation is in doxygen files.
+
+
+<H2>SEE ALSO</H2>
+
+<EM><A HREF="http://grass.itc.it/gdp/landscape/r_le_manual5.pdf">old r.le manual</A></EM><BR>
+<EM><A HREF="r.li.html">r.li</A></EM> package overview <BR>
+<EM><A HREF="r.li.patchdensity.html">r.li.patchdensity</A></EM>,
+<EM><A HREF="r.li.setup.html">r.li.setup</A></EM>
+
+<H2>AUTHORS</H2>
+Claudio Porta and Lucio Davide Spano, students of Computer Science
+University of Pisa (Italy).<br>
+Commission from Faunalia Pontedera (PI)<br>
+Rebuild of r.le.setup from William L. Baker
+This program is free software under the GPL (>=v2)
+Read the COPYING file that comes with GRASS for details.
+
+
+<H2>BUGS</h2>
+Pleas send bugs reports to
+<a href="mailto:spano at cli.di.unipi.it">spano at cli.di.unipi.it</a>,
+<a href="mailto:porta at cli.di.unipi.it">porta at cli.di.unipi.it</a><br>
+<BR>
+
+<p><i>Last changed: $Date$</i>
+
+<HR>
+<P><a href="index.html">Main index</a> - <a href="raster.html">raster index</a> - <a href="full_index.html">Full index</a>
+</body>
+</html>
Deleted: grass/trunk/raster/r.li/r.li.dominance/description.html
===================================================================
--- grass/trunk/raster/r.li/r.li.dominance/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.li/r.li.dominance/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,48 +0,0 @@
-<h2>DESCRIPTION</h2>
-<em>r.li.dominance</em>
-calculates the "dominance's diversity index" as:<br>
-<img src="rliDominance_formula.png"> <br>
-with: <br>
-<ul>
- <li><b>m</b>: number of different patch type<br> </li>
- <li><b>i</b>: patch type<br></li>
- <li><b>p<small><small>i</small></small></b>: proportion of the landscape occupied by patch type i<br></li>
-</ul>
-
-
-<h2>EXAMPLES</h2>
-To calculate dominance's diversity index on map my_map, using
-my_conf configuration file and saving results in my_out file run:<br>
-<div class="code"><pre>
-r.li.dominance map=my_map conf=my_conf output=my_out
-</pre></div>
-
-<h2>NOTES</h2>
-Do not use absolute path names for output files. They are raster if
-moving window disposition was selected, otherwise they are in
-~/.r.li/output folder. <br>
-
-If input raster is full of null values r.li.dominance returns -1.<br>
-If you want to have null values instead run <br>
-<div class="code"><pre>
-r.null setnull=-1 map=my_map
-</pre></div>
-after index calculation.
-
-
-<h2>SEE ALSO</h2>
-<em>
-<a href="r.li.html">r.li</a>
-<a href="r.le.html">r.le</a>
-</em>
-
-
-<h2>AUTHORS</h2>
-Serena Pallecchi student of Computer Science University of Pisa (Italy).<br>
-Commission from Faunalia Pontedera (PI), Italy (www.faunalia.it)
-
-<h2>BUGS</h2>
-Please send bugs reports to
-<a href="mailto:pallecch at cli.di.unipi.it">pallecch at cli.di.unipi.it</a><br>
-
-<p><i>Last changed: $Date$</i></p>
Copied: grass/trunk/raster/r.li/r.li.dominance/r.li.dominance.html (from rev 32770, grass/trunk/raster/r.li/r.li.dominance/description.html)
===================================================================
--- grass/trunk/raster/r.li/r.li.dominance/r.li.dominance.html (rev 0)
+++ grass/trunk/raster/r.li/r.li.dominance/r.li.dominance.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,48 @@
+<h2>DESCRIPTION</h2>
+<em>r.li.dominance</em>
+calculates the "dominance's diversity index" as:<br>
+<img src="rliDominance_formula.png"> <br>
+with: <br>
+<ul>
+ <li><b>m</b>: number of different patch type<br> </li>
+ <li><b>i</b>: patch type<br></li>
+ <li><b>p<small><small>i</small></small></b>: proportion of the landscape occupied by patch type i<br></li>
+</ul>
+
+
+<h2>EXAMPLES</h2>
+To calculate dominance's diversity index on map my_map, using
+my_conf configuration file and saving results in my_out file run:<br>
+<div class="code"><pre>
+r.li.dominance map=my_map conf=my_conf output=my_out
+</pre></div>
+
+<h2>NOTES</h2>
+Do not use absolute path names for output files. They are raster if
+moving window disposition was selected, otherwise they are in
+~/.r.li/output folder. <br>
+
+If input raster is full of null values r.li.dominance returns -1.<br>
+If you want to have null values instead run <br>
+<div class="code"><pre>
+r.null setnull=-1 map=my_map
+</pre></div>
+after index calculation.
+
+
+<h2>SEE ALSO</h2>
+<em>
+<a href="r.li.html">r.li</a>
+<a href="r.le.html">r.le</a>
+</em>
+
+
+<h2>AUTHORS</h2>
+Serena Pallecchi student of Computer Science University of Pisa (Italy).<br>
+Commission from Faunalia Pontedera (PI), Italy (www.faunalia.it)
+
+<h2>BUGS</h2>
+Please send bugs reports to
+<a href="mailto:pallecch at cli.di.unipi.it">pallecch at cli.di.unipi.it</a><br>
+
+<p><i>Last changed: $Date$</i></p>
Deleted: grass/trunk/raster/r.li/r.li.edgedensity/description.html
===================================================================
--- grass/trunk/raster/r.li/r.li.edgedensity/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.li/r.li.edgedensity/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,63 +0,0 @@
-
-<h2>DESCRIPTION</h2>
-<em>r.li.edgedensity </em>calculates:<br>
-<br>
-<ul>
- <li> the density of all the edge of patch i<br></li>
- <img alt="" src="rliEdgeDensity_formula1.png"><br>
- or<br><br>
- <li> the density of all the edge in the sampling area if i isn't specified<br></li>
- <img alt="" src="rliEdgeDensity_formula2.png"><br></ul>
-<p>with:</p>
-<ul>
- <li><b>k</b>: patch type<br></li>
- <li><b>m</b>: number of patch type<br> </li>
- <li><b>n</b>: number of edge segment of patch type k</li>
- <li><b>e<small><small>ik </small></small></b>:total length of edge in landscape involving patch type k</li>
- <li> <B>Area</B>: total landscape area<BR>
-</ul>
-
-<h2>REFERENCES</h2>
-McGarigal, K., and B. J. Marks. 1995. FRAGSTATS: spatial pattern
-analysis program for quantifying landscape structure. USDA For. Serv.
-Gen. Tech. Rep. PNW-351.
-
-<h2>EXAMPLES</h2>
-To calculate edge density index on map my_map, using
-my_conf configuration file and saving results in
-my_out file run:<br>
-<B>r.li.edgedensity map=</B>my_map <B>conf=</B>my_conf <B>output=</B>my_out <br><br>
-To calculate edge density index of patch_type 34, using
-my_conf configuration file and on map my_map, saving results in my_out
-file run:<br>
-<B>r.li.edgedensity map=</B>my_map <B>conf=</B>my_conf <B>output=</B>my_out <B>patch_type=</B>34
-<br>
-
-<h2>NOTES</h2>
-Do not use absolute path names for output files. They are raster if
-moving window disposition was selected, otherwise they are in
-~/.r.li/output folder.
-<br>
-If input raster is full of null values r.li.edgedensity consider to have 0
-patch.<br>
-If area is 0 r.li.edgedensity returns -1; this is possible only if input
-raster is masked.
-If you want to have null values instead run <br>
-<B>r.null setnull=-1 map=</B>my_map <br>
-after index calculation.
-
-<h2>SEE ALSO</h2>
-<em>
-<a href="r.li.html">r.li</a>
-</em>
-
-<h2>AUTHORS</h2>
-Serena Pallecchi student of Computer Science University of Pisa (Italy).<br>
-Commission from Faunalia Pontedera (PI), Italy (www.faunalia.it)
-
-<h2>BUGS</h2>
-Please send bugs reports to
-<a href="mailto:pallecch at cli.di.unipi.it">pallecch at cli.di.unipi.it</a><br>
-
-<p><i>Last changed: $Date$</i>
-
Copied: grass/trunk/raster/r.li/r.li.edgedensity/r.li.edgedensity.html (from rev 32770, grass/trunk/raster/r.li/r.li.edgedensity/description.html)
===================================================================
--- grass/trunk/raster/r.li/r.li.edgedensity/r.li.edgedensity.html (rev 0)
+++ grass/trunk/raster/r.li/r.li.edgedensity/r.li.edgedensity.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,63 @@
+
+<h2>DESCRIPTION</h2>
+<em>r.li.edgedensity </em>calculates:<br>
+<br>
+<ul>
+ <li> the density of all the edge of patch i<br></li>
+ <img alt="" src="rliEdgeDensity_formula1.png"><br>
+ or<br><br>
+ <li> the density of all the edge in the sampling area if i isn't specified<br></li>
+ <img alt="" src="rliEdgeDensity_formula2.png"><br></ul>
+<p>with:</p>
+<ul>
+ <li><b>k</b>: patch type<br></li>
+ <li><b>m</b>: number of patch type<br> </li>
+ <li><b>n</b>: number of edge segment of patch type k</li>
+ <li><b>e<small><small>ik </small></small></b>:total length of edge in landscape involving patch type k</li>
+ <li> <B>Area</B>: total landscape area<BR>
+</ul>
+
+<h2>REFERENCES</h2>
+McGarigal, K., and B. J. Marks. 1995. FRAGSTATS: spatial pattern
+analysis program for quantifying landscape structure. USDA For. Serv.
+Gen. Tech. Rep. PNW-351.
+
+<h2>EXAMPLES</h2>
+To calculate edge density index on map my_map, using
+my_conf configuration file and saving results in
+my_out file run:<br>
+<B>r.li.edgedensity map=</B>my_map <B>conf=</B>my_conf <B>output=</B>my_out <br><br>
+To calculate edge density index of patch_type 34, using
+my_conf configuration file and on map my_map, saving results in my_out
+file run:<br>
+<B>r.li.edgedensity map=</B>my_map <B>conf=</B>my_conf <B>output=</B>my_out <B>patch_type=</B>34
+<br>
+
+<h2>NOTES</h2>
+Do not use absolute path names for output files. They are raster if
+moving window disposition was selected, otherwise they are in
+~/.r.li/output folder.
+<br>
+If input raster is full of null values r.li.edgedensity consider to have 0
+patch.<br>
+If area is 0 r.li.edgedensity returns -1; this is possible only if input
+raster is masked.
+If you want to have null values instead run <br>
+<B>r.null setnull=-1 map=</B>my_map <br>
+after index calculation.
+
+<h2>SEE ALSO</h2>
+<em>
+<a href="r.li.html">r.li</a>
+</em>
+
+<h2>AUTHORS</h2>
+Serena Pallecchi student of Computer Science University of Pisa (Italy).<br>
+Commission from Faunalia Pontedera (PI), Italy (www.faunalia.it)
+
+<h2>BUGS</h2>
+Please send bugs reports to
+<a href="mailto:pallecch at cli.di.unipi.it">pallecch at cli.di.unipi.it</a><br>
+
+<p><i>Last changed: $Date$</i>
+
Copied: grass/trunk/raster/r.li/r.li.html (from rev 32770, grass/trunk/raster/r.li/description.html)
===================================================================
--- grass/trunk/raster/r.li/r.li.html (rev 0)
+++ grass/trunk/raster/r.li/r.li.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,186 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<head>
+<title>r.li</title>
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
+<link rel="stylesheet" href="grassdocs.css" type="text/css">
+</head>
+<body bgcolor="white">
+
+<img src="grass_logo.png" alt="GRASS logo"><hr align=center size=6 noshade>
+
+<h2>NAME</h2>
+<em><b>r.li</b></em> - package overview
+
+<h2>KEYWORDS</h2>
+raster, landscape structure analysis, overview, landscape metrics, landscape pattern, landscape analysis
+
+<h2>DESCRIPTION</h2>
+
+The <em>r.li</em> suite is a toolset for multiscale analysis of landscape structure.
+It aims at replacing the <em>r.le</em> suite of modules through a client-server,
+multiprocess implementation. External software for quantitative measures of landscape
+structure is for example FRAGSTATS (McGarigal and Marks 1995).
+<p>
+The <em>r.li</em> suite offers a set of patch and diversity indices.
+It supports analysis of landscapes composed of a mosaic of
+patches, but, more generally, the modules work with any two-dimensional
+raster map whose cell values are integer (e.g., 1, 2) or floating point
+(e.g., 1.1, 3.2) values. The <em>r.li.setup</em> module has options for
+controlling the shape, size, number, and distribution of sampling
+areas used to collect information about the landscape structure.
+Sampling area shapes can be the entire map or a moving
+window of square, rectangular or with circular shape. The size of
+sampling areas can be changed, so that the landscape can be analyzed
+at a variety of spatial scales simultaneously. Sampling areas may be
+distributed across the landscape in a random, systematic, or
+stratified-random manner, or as a moving window.
+<p>
+The <em>r.li</em> modules can calculate a number of measures that produce
+single values as output (e.g. mean patch size in the sampling area),
+as well as measures that produce a distribution of values as output
+(e.g. frequency distribution of patch sizes in the sampling area). The
+results are stored as raster maps.
+
+<p>
+The general procedure to calculate an index from a raster map is two-fold:
+
+<ol>
+<li>run <em>r.li.setup</em>: create a configuration file selecting the parts of
+ raster to analyze.
+
+<li>run <em>r.li.'index'</em> (e.g., <em>r.li.patchdensity</em>) for calculate the selected
+ index using on the areas selected on configuration file.
+</ol>
+
+<h2>NOTE</h2>
+
+Also the <em>r.li.daemon</em> has a main function and it can be run, but it is only a
+template for development of new indices.
+<!-- mhh ??: -->
+The function itself has no meaning, it can be used only for debug.
+
+<h2>EXAMPLE</h2>
+
+To calculate a patch density index on a whole 'geology' raster map in the
+Spearfish region, using a 5x5 moving window, follow this procedure:
+
+<ol>
+<li> CREATE A NEW CONFIGURATION FILE
+ <ol>
+ <li> run
+<div class="code"><pre>
+ r.li.setup
+</pre></div>
+ <li> The main <em>r.li.setup</em> window is displayed, click on "New"
+ <li> Now it is displayed the new configuration window,
+ enter the configuration file name (e.g., "my_conf", do not use absolute paths)
+ and the name of raster map (e.g., "geology").
+ The other fields are not needed for this configuration.
+ <li> Click on "Setup sampling frame", select "Whole maplayer" and click "OK"
+ <li> Click on "Setup sampling areas", select "Moving window" and click "OK"
+ <li> Click on "Use keyboard to enter moving window dimension"
+ <li> Select "Rectangle" and enter 5 on "heigth" and "width" fields
+ <li> Click on "Save settings"
+ <li> Close <em>r.li.setup</em> window
+ </ol>
+<li> CALCULATE PATCHDENSITY INDEX
+<ol>
+ <li> set region settings to geology raster map:
+<div class="code"><pre>
+ g.region rast=geology -p
+</pre></div>
+ <li> run <em>r.li.patchdensity</em>:
+<div class="code"><pre>
+ r.li.patchdensity map=geology conf=my_conf out=patchdens
+</pre></div>
+ </ol>
+</ol>
+
+The resulting patch density is stored in "patchdens" raster map.
+
+You can verify the result for example with contour lines:
+<div class="code"><pre>
+r.contour in=patchdens out=patchdens step=5
+d.rast patchdens
+d.vect -c patchdens
+</pre></div>
+
+Note that if you want to run another index with the same area
+configuration, you don't have to create another configuration file.
+
+You can also use the same area configuration file on another map. The
+program rescale it automatically. For instance if you have selected a
+5x5 sample area on 100x100 raster map, and you use the same
+configuration file on a 200x200 raster map, then the sample area is
+10x10.
+
+<h2>SEE ALSO</h2>
+
+<b>Core modules</b>:
+<ul>
+ <li> <a href="r.li.daemon.html">r.li.daemon</a>: job launch daemon</li>
+ <li> <a href="r.li.setup.html">r.li.setup</a>: Configuration editor for r.li.'index'</li>
+</ul>
+
+<b>Patch indices</b>:
+<ul>
+<li>Indices based on patch number:
+<ul>
+ <li> <a href="r.li.patchdensity.html">r.li.patchdensity</a>: Calculates patch density index on a raster map, using a 4 neighbour algorithm</li>
+ <li> <a href="r.li.patchnum.html">r.li.patchnum</a>: Calculates patch number index on a raster map, using a 4 neighbour algorithm</li>
+</ul>
+<li>Indices based on patch dimension:
+<ul>
+ <li> <a href="r.li.mps.html">r.li.mps</a>: Calculates mean patch size index on a raster map, using a 4 neighbour algorithm</li>
+ <li> <a href="r.li.padcv.html">r.li.padcv</a>: Calculates coefficient of variation of patch area on a raster map</li>
+ <li> <a href="r.li.padrange.html">r.li.padrange</a>: Calculates range of patch area size on a raster map</li>
+ <li> <a href="r.li.padsd.html">r.li.padsd</a>: Calculates standard deviation of patch area a raster map</li>
+</ul>
+<li>Indices based on patch shape:
+<ul>
+ <li> <a href="r.li.shape.html">r.li.shape</a>: Calculates shape index on a raster map</li>
+</ul>
+<li>Indices based on patch edge: <!-- border? -->
+<ul>
+ <li> <a href="r.li.edgedensity.html">r.li.edgedensity</a>: Calculates edge density index on a raster map, using a 4 neighbour algorithm</li>
+</ul>
+<li>Indices based on patch attributes:
+<ul>
+ <li> <a href="r.li.cwed.html">r.li.cwed</a>: Calculates contrast Weighted Edge Density index on a raster map</li>
+ <li> <a href="r.li.mpa.html">r.li.mpa</a>: Calculates mean pixel attribute index on a raster map</li>
+</ul>
+</ul>
+
+<b>Diversity indices</b>:
+<ul>
+ <li> <a href="r.li.dominance.html">r.li.dominance</a>: Calculates dominance's diversity index on a raster map</li>
+ <li> <a href="r.li.richness.html">r.li.richness</a>: Calculates dominance's diversity index on a raster map</li>
+ <li> <a href="r.li.shannon.html">r.li.shannon</a>: Calculates Shannon's diversity index on a raster map</li>
+ <li> <a href="r.li.simpson.html">r.li.simpson</a>: Calculates Simpson's diversity index on a raster map</li>
+</ul>
+
+<h2>ADDING NEW INDICES</h2>
+New indices can be defined and implemented by any C programmer, without having to
+deal with all basic functions (IO etc.). The computing architecture and the functions
+are clearly separated, thus allowing an easy expandability. Every index is defined
+separately, placed in a directory along with its Makefile for compiling it and a file
+description.html which describes the index including a simple example of use.
+
+<h2>REFERENCES</h2>
+
+McGarigal, K., and B. J. Marks. 1995. FRAGSTATS: spatial pattern
+analysis program for quantifying landscape structure. USDA For. Serv.
+Gen. Tech. Rep. PNW-351 (<a href="http://www.fs.fed.us/pnw/pubs/gtr_351.pdf">PDF</a>).
+
+<h2>AUTHORS</h2>
+<a href="mailto:porta at cli.di.unipi.it">Claudio Porta</a> and
+<a href="mailto:spano at cli.di.unipi.it">Lucio Davide Spano</a>, students of Computer Science
+University of Pisa (Italy). <br>
+Commission from Faunalia Pontedera (PI)<br>
+
+<p><i>Last changed: $Date$</i>
+<hr>
+<p><a href="index.html">Main index</a> - <a href="raster.html">raster index</a> - <a href="full_index.html">Full index</a>
+</body>
+</html>
Deleted: grass/trunk/raster/r.li/r.li.mpa/description.html
===================================================================
--- grass/trunk/raster/r.li/r.li.mpa/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.li/r.li.mpa/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,56 +0,0 @@
-<h2>DESCRIPTION</h2>
-<em>r.li.mpa</em>
-(mean pixel attribute) calculates the average value of the attribute of all the non-null
-cells in the sampling area as:<br>
-<img src="rlimpa_formula.png"> <br>
-with:<br>
-<ul>
- <li><b>i</b>: attribute<br></li>
- <li><b>m</b>: number of non-null attributes in the sampling area </li>
- <li><b>w<small><small>i</small></small></b>: number of cells of attribute i</li>
- <li><b>size</b>: size of sampling area (in cells)<br>
- </li>
-</ul>
-
-
-<h2>EXAMPLES</h2>
-To calculate mean pixel attribute index on map my_map, using
-my_conf configuration file and saving results in
-my_out file run:<br>
-<div class="code"><pre>
-r.li.mpa map=my_map conf=my_conf output=my_out
-</pre></div>
-
-<h2>NOTES</h2>
-Do not use absolute path names for output files. They are raster if
-moving window disposition was selected, otherwise they are in
-~/.r.li/output folder.<br>
-If input raster is full of null values r.li.mpa consider to
-have 0 patch.<br>
-If area is 0 r.li.mpa returns -1; it is possible only if the
-raster is masked <br>
-If you want to have null values instead run <br>
-<div class="code"><pre>
-r.null setnull=-1 map=my_map
-</pre></div>
-after index calculation.
-
-
-<h2>SEE ALSO</h2>
-<em>
-<a href="r.li.html">r.li</a>
-<a href="r.le.html">r.le</a>
-</em>
-
-
-<h2>AUTHORS</h2>
-Serena Pallecchi student of Computer Science University of Pisa (Italy).<br>
-Commission from Faunalia Pontedera (PI), Italy (www.faunalia.it)
-
-
-<h2>BUGS</h2>
-Please send bugs reports to
-<a href="mailto:pallecch at cli.di.unipi.it">pallecch at cli.di.unipi.it</a>
-
-<p><i>Last changed: $Date$</i>
-
Copied: grass/trunk/raster/r.li/r.li.mpa/r.li.mpa.html (from rev 32770, grass/trunk/raster/r.li/r.li.mpa/description.html)
===================================================================
--- grass/trunk/raster/r.li/r.li.mpa/r.li.mpa.html (rev 0)
+++ grass/trunk/raster/r.li/r.li.mpa/r.li.mpa.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,56 @@
+<h2>DESCRIPTION</h2>
+<em>r.li.mpa</em>
+(mean pixel attribute) calculates the average value of the attribute of all the non-null
+cells in the sampling area as:<br>
+<img src="rlimpa_formula.png"> <br>
+with:<br>
+<ul>
+ <li><b>i</b>: attribute<br></li>
+ <li><b>m</b>: number of non-null attributes in the sampling area </li>
+ <li><b>w<small><small>i</small></small></b>: number of cells of attribute i</li>
+ <li><b>size</b>: size of sampling area (in cells)<br>
+ </li>
+</ul>
+
+
+<h2>EXAMPLES</h2>
+To calculate mean pixel attribute index on map my_map, using
+my_conf configuration file and saving results in
+my_out file run:<br>
+<div class="code"><pre>
+r.li.mpa map=my_map conf=my_conf output=my_out
+</pre></div>
+
+<h2>NOTES</h2>
+Do not use absolute path names for output files. They are raster if
+moving window disposition was selected, otherwise they are in
+~/.r.li/output folder.<br>
+If input raster is full of null values r.li.mpa consider to
+have 0 patch.<br>
+If area is 0 r.li.mpa returns -1; it is possible only if the
+raster is masked <br>
+If you want to have null values instead run <br>
+<div class="code"><pre>
+r.null setnull=-1 map=my_map
+</pre></div>
+after index calculation.
+
+
+<h2>SEE ALSO</h2>
+<em>
+<a href="r.li.html">r.li</a>
+<a href="r.le.html">r.le</a>
+</em>
+
+
+<h2>AUTHORS</h2>
+Serena Pallecchi student of Computer Science University of Pisa (Italy).<br>
+Commission from Faunalia Pontedera (PI), Italy (www.faunalia.it)
+
+
+<h2>BUGS</h2>
+Please send bugs reports to
+<a href="mailto:pallecch at cli.di.unipi.it">pallecch at cli.di.unipi.it</a>
+
+<p><i>Last changed: $Date$</i>
+
Deleted: grass/trunk/raster/r.li/r.li.mps/description.html
===================================================================
--- grass/trunk/raster/r.li/r.li.mps/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.li/r.li.mps/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,54 +0,0 @@
-<h2>DESCRIPTION</h2>
-<em>r.li.mps</em>
-(mean patch size) calculates the mean size of the patches in the sampling area as:<br>
-<img src="rlimps_formula.png"><br>
-
-with:
-<ul>
- <li><b>A</b>:sampling area size without null cells</li>
- <li><b>Npatch</b>: number of patches<br>
- </li>
-</ul>
-
-
-<h2>EXAMPLES</h2>
-To calculate mean path size index on map my_map, using
-my_conf configuration file and saving results in
-my_out file run:<br>
-<div class="code"><pre>
-r.li.mps map=my_map conf=my_conf output=my_out
-</pre></div>
-
-
-<h2>NOTES</h2>
-Do not use absolute path names for output files. They are raster if
-moving window disposition was selected, otherwise they are in
-~/.r.li/output folder.
-<br>
-If input raster is full of null values r.li.mps returns 0.<br>
-If you want to have null values instead run <br>
-<div class="code"><pre>
-r.null setnull=0 map=my_map
-</pre></div>
-
-after index calculation.
-
-
-<h2>SEE ALSO</h2>
-<em>
-<a href="r.li.html">r.li</a>
-<a href="r.le.html">r.le</a>
-</em>
-
-
-<h2>AUTHORS</h2>
-Serena Pallecchi student of Computer Science University of Pisa (Italy).<br>
-Commission from Faunalia Pontedera (PI), Italy (www.faunalia.it)
-
-
-<h2>BUGS</h2>
-Please send bugs reports to
-<a href="mailto:pallecch at cli.di.unipi.it">pallecch at cli.di.unipi.it</a><br>
-
-<p><i>Last changed: $Date$</i>
-
Copied: grass/trunk/raster/r.li/r.li.mps/r.li.mps.html (from rev 32770, grass/trunk/raster/r.li/r.li.mps/description.html)
===================================================================
--- grass/trunk/raster/r.li/r.li.mps/r.li.mps.html (rev 0)
+++ grass/trunk/raster/r.li/r.li.mps/r.li.mps.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,54 @@
+<h2>DESCRIPTION</h2>
+<em>r.li.mps</em>
+(mean patch size) calculates the mean size of the patches in the sampling area as:<br>
+<img src="rlimps_formula.png"><br>
+
+with:
+<ul>
+ <li><b>A</b>:sampling area size without null cells</li>
+ <li><b>Npatch</b>: number of patches<br>
+ </li>
+</ul>
+
+
+<h2>EXAMPLES</h2>
+To calculate mean path size index on map my_map, using
+my_conf configuration file and saving results in
+my_out file run:<br>
+<div class="code"><pre>
+r.li.mps map=my_map conf=my_conf output=my_out
+</pre></div>
+
+
+<h2>NOTES</h2>
+Do not use absolute path names for output files. They are raster if
+moving window disposition was selected, otherwise they are in
+~/.r.li/output folder.
+<br>
+If input raster is full of null values r.li.mps returns 0.<br>
+If you want to have null values instead run <br>
+<div class="code"><pre>
+r.null setnull=0 map=my_map
+</pre></div>
+
+after index calculation.
+
+
+<h2>SEE ALSO</h2>
+<em>
+<a href="r.li.html">r.li</a>
+<a href="r.le.html">r.le</a>
+</em>
+
+
+<h2>AUTHORS</h2>
+Serena Pallecchi student of Computer Science University of Pisa (Italy).<br>
+Commission from Faunalia Pontedera (PI), Italy (www.faunalia.it)
+
+
+<h2>BUGS</h2>
+Please send bugs reports to
+<a href="mailto:pallecch at cli.di.unipi.it">pallecch at cli.di.unipi.it</a><br>
+
+<p><i>Last changed: $Date$</i>
+
Deleted: grass/trunk/raster/r.li/r.li.padcv/description.html
===================================================================
--- grass/trunk/raster/r.li/r.li.padcv/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.li/r.li.padcv/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,60 +0,0 @@
-<h2>DESCRIPTION</h2>
-<em>r.li.padcv</em>
- (patch area distribution coefficient of variation) calculates
-as:<br>
-<img src="rlipadcv_formula1.png"> <br>
-with:<br>
-<ul>
- <li><b>SD</b>: standard deviation of patch area size <br></li>
- <img src="rlipadcv_formula2.png"> <br>
- <li><b>MPS</b>: mean patch area size<br></li>
- <li><b>a<small><small>i</small></small></b>: area of patch i<br></li>
- <li><b>N<small>patch</small></b>: number of patch<br></li>
- </li>
-</ul>
-
-
-<h2>REFERENCES</h2>
-McGarigal, K., and B. J. Marks. 1995. FRAGSTATS: spatial pattern
-analysis program for quantifying landscape structure. USDA For. Serv.
-Gen. Tech. Rep. PNW-351.
-
-<h2>EXAMPLES</h2>
-To calculate mean pixel attribute index on map my_map, using
-my_conf configuration file and saving results in
-my_out file run:<br>
-<div class="code"><pre>
-r.li.padcv map=my_map conf=my_conf output=my_out
-</pre></div>
-
-
-<h2>NOTES</h2>
-Do not use absolute path names for output files. They are raster if
-moving window disposition was selected, otherwise they are in
-~/.r.li/output folder.<br>
-If input raster is not full of null values r.li.padcv returns a value >=0 that is PADcv. <br>
-If input raster is full of null values r.li.padcv returns -1. <br>
-If you want to have null values instead run <br>
-<div class="code"><pre>
-r.null setnull=-1 map=my_map
-</pre></div>
-after index calculation.
-
-
-<h2>SEE ALSO</h2>
-<em>
-<a href="r.li.html">r.li</a>
-</em>
-
-
-<h2>AUTHORS</h2>
-Serena Pallecchi student of Computer Science University of Pisa (Italy).<br>
-Commission from Faunalia Pontedera (PI), Italy (www.faunalia.it)
-
-
-<h2>BUGS</h2>
-Please send bugs reports to
-<a href="mailto:pallecch at cli.di.unipi.it">pallecch at cli.di.unipi.it</a><br>
-
-<p><i>Last changed: $Date$</i>
-
Copied: grass/trunk/raster/r.li/r.li.padcv/r.li.padcv.html (from rev 32770, grass/trunk/raster/r.li/r.li.padcv/description.html)
===================================================================
--- grass/trunk/raster/r.li/r.li.padcv/r.li.padcv.html (rev 0)
+++ grass/trunk/raster/r.li/r.li.padcv/r.li.padcv.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,60 @@
+<h2>DESCRIPTION</h2>
+<em>r.li.padcv</em>
+ (patch area distribution coefficient of variation) calculates
+as:<br>
+<img src="rlipadcv_formula1.png"> <br>
+with:<br>
+<ul>
+ <li><b>SD</b>: standard deviation of patch area size <br></li>
+ <img src="rlipadcv_formula2.png"> <br>
+ <li><b>MPS</b>: mean patch area size<br></li>
+ <li><b>a<small><small>i</small></small></b>: area of patch i<br></li>
+ <li><b>N<small>patch</small></b>: number of patch<br></li>
+ </li>
+</ul>
+
+
+<h2>REFERENCES</h2>
+McGarigal, K., and B. J. Marks. 1995. FRAGSTATS: spatial pattern
+analysis program for quantifying landscape structure. USDA For. Serv.
+Gen. Tech. Rep. PNW-351.
+
+<h2>EXAMPLES</h2>
+To calculate mean pixel attribute index on map my_map, using
+my_conf configuration file and saving results in
+my_out file run:<br>
+<div class="code"><pre>
+r.li.padcv map=my_map conf=my_conf output=my_out
+</pre></div>
+
+
+<h2>NOTES</h2>
+Do not use absolute path names for output files. They are raster if
+moving window disposition was selected, otherwise they are in
+~/.r.li/output folder.<br>
+If input raster is not full of null values r.li.padcv returns a value >=0 that is PADcv. <br>
+If input raster is full of null values r.li.padcv returns -1. <br>
+If you want to have null values instead run <br>
+<div class="code"><pre>
+r.null setnull=-1 map=my_map
+</pre></div>
+after index calculation.
+
+
+<h2>SEE ALSO</h2>
+<em>
+<a href="r.li.html">r.li</a>
+</em>
+
+
+<h2>AUTHORS</h2>
+Serena Pallecchi student of Computer Science University of Pisa (Italy).<br>
+Commission from Faunalia Pontedera (PI), Italy (www.faunalia.it)
+
+
+<h2>BUGS</h2>
+Please send bugs reports to
+<a href="mailto:pallecch at cli.di.unipi.it">pallecch at cli.di.unipi.it</a><br>
+
+<p><i>Last changed: $Date$</i>
+
Deleted: grass/trunk/raster/r.li/r.li.padrange/description.html
===================================================================
--- grass/trunk/raster/r.li/r.li.padrange/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.li/r.li.padrange/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,57 +0,0 @@
-<h2>DESCRIPTION</h2>
-<em>r.li.padrange</em>
- (patch area distribution range) calculates
-as:<br>
-<img src="rlipadrange_formula.png"> <br>
-with:<br>
-<ul>
- <li><b>a<small><small>max</small></small></b>: max patch area size<br></li>
- <li><b>a<small><small>min</small></small></b>: min patch area size<br></li>
- </li>
-</ul>
-
-<h2>EXAMPLES</h2>
-To calculate range of patch area size, using
-my_conf configuration file and saving results in
-my_out file run:<br>
-<div class="code"><pre>
-r.li.padrange map=my_map conf=my_conf output=my_out
-</pre></div>
-
-
-<h2>NOTES</h2>
-Do not use absolute path names for output files. They are raster if
-moving window disposition was selected, otherwise they are in
-~/.r.li/output folder.<br>
-If input raster is not full of null values r.li.padrange returns a
-value >=0 that is PADcv. <br>
-If input raster is full of null values r.li.padrange returns -1. <br>
-If you want to have null values instead run <br>
-
-<div class="code"><pre>
-r.null setnull=-1 map=my_map
-</pre></div>
-
-after index calculation.
-
-<h2>REFERENCES</h2>
-McGarigal, K., and B. J. Marks. 1995. FRAGSTATS: spatial pattern
-analysis program for quantifying landscape structure. USDA For. Serv.
-Gen. Tech. Rep. PNW-351.
-
-<h2>SEE ALSO</h2>
-<em>
-<a href="r.li.html">r.li</a>
-</em>
-
-
-<h2>AUTHORS</h2>
-Serena Pallecchi student of Computer Science University of Pisa (Italy).<br>
-Commission from Faunalia Pontedera (PI), Italy (www.faunalia.it)
-
-<h2>BUGS</h2>
-Please send bugs reports to
-<a href="mailto:pallecch at cli.di.unipi.it">pallecch at cli.di.unipi.it</a><br>
-
-<p><i>Last changed: $Date$</i></p>
-
Copied: grass/trunk/raster/r.li/r.li.padrange/r.li.padrange.html (from rev 32770, grass/trunk/raster/r.li/r.li.padrange/description.html)
===================================================================
--- grass/trunk/raster/r.li/r.li.padrange/r.li.padrange.html (rev 0)
+++ grass/trunk/raster/r.li/r.li.padrange/r.li.padrange.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,57 @@
+<h2>DESCRIPTION</h2>
+<em>r.li.padrange</em>
+ (patch area distribution range) calculates
+as:<br>
+<img src="rlipadrange_formula.png"> <br>
+with:<br>
+<ul>
+ <li><b>a<small><small>max</small></small></b>: max patch area size<br></li>
+ <li><b>a<small><small>min</small></small></b>: min patch area size<br></li>
+ </li>
+</ul>
+
+<h2>EXAMPLES</h2>
+To calculate range of patch area size, using
+my_conf configuration file and saving results in
+my_out file run:<br>
+<div class="code"><pre>
+r.li.padrange map=my_map conf=my_conf output=my_out
+</pre></div>
+
+
+<h2>NOTES</h2>
+Do not use absolute path names for output files. They are raster if
+moving window disposition was selected, otherwise they are in
+~/.r.li/output folder.<br>
+If input raster is not full of null values r.li.padrange returns a
+value >=0 that is PADcv. <br>
+If input raster is full of null values r.li.padrange returns -1. <br>
+If you want to have null values instead run <br>
+
+<div class="code"><pre>
+r.null setnull=-1 map=my_map
+</pre></div>
+
+after index calculation.
+
+<h2>REFERENCES</h2>
+McGarigal, K., and B. J. Marks. 1995. FRAGSTATS: spatial pattern
+analysis program for quantifying landscape structure. USDA For. Serv.
+Gen. Tech. Rep. PNW-351.
+
+<h2>SEE ALSO</h2>
+<em>
+<a href="r.li.html">r.li</a>
+</em>
+
+
+<h2>AUTHORS</h2>
+Serena Pallecchi student of Computer Science University of Pisa (Italy).<br>
+Commission from Faunalia Pontedera (PI), Italy (www.faunalia.it)
+
+<h2>BUGS</h2>
+Please send bugs reports to
+<a href="mailto:pallecch at cli.di.unipi.it">pallecch at cli.di.unipi.it</a><br>
+
+<p><i>Last changed: $Date$</i></p>
+
Deleted: grass/trunk/raster/r.li/r.li.padsd/description.html
===================================================================
--- grass/trunk/raster/r.li/r.li.padsd/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.li/r.li.padsd/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,52 +0,0 @@
-<h2>DESCRIPTION</h2>
-<em>r.li.padsd</em> (patch area distribution standard deviation) calculates as:<br>
-<img src="rlipadsd_formula.png"> <br>
-with:<br>
-<ul>
- <li><b>MPS</b>: mean patch area size<br></li>
- <li><b>a<small><small>i</small></small></b>: area of patch i<br></li>
- <li><b>N<small>patch</small></b>: number of patch<br></li>
- </li>
-</ul>
-
-<h2>EXAMPLES</h2>
-To calculate mean pixel attribute index on map my_map, using
-my_conf configuration file and saving results in
-my_out file run:<br>
-<div class="code"><pre>
-r.li.padsd map=my_map conf=my_conf output=my_out
-</pre></div>
-
-<h2>NOTES</h2>
-Do not use absolute path names for output files. They are raster if
-moving window disposition was selected, otherwise they are in
-~/.r.li/output folder.<br>
-If input raster is not full of null values r.li.padsd returns a value >=0 that is PADsd. <br>
-If input raster is full of null values r.li.padsd returns -1. <br>
-If you want to have null values instead run <br>
-<div class="code"><pre>
-r.null setnull=-1 map=my_map
-</pre></div>
-
-after index calculation.
-
-<h2>REFERENCES</h2>
-McGarigal, K., and B. J. Marks. 1995. FRAGSTATS: spatial pattern
-analysis program for quantifying landscape structure. USDA For. Serv.
-Gen. Tech. Rep. PNW-351.
-
-<h2>SEE ALSO</h2>
-<em>
-<a href="r.li.html">r.li</a>
-</em>
-
-<h2>AUTHORS</h2>
-Serena Pallecchi student of Computer Science University of Pisa (Italy).<br>
-Commission from Faunalia Pontedera (PI), Italy (www.faunalia.it)
-
-
-<h2>BUGS</h2>
-Please send bugs reports to
-<a href="mailto:pallecch at cli.di.unipi.it">pallecch at cli.di.unipi.it</a><br>
-
-<p><i>Last changed: $Date$</i></p>
Copied: grass/trunk/raster/r.li/r.li.padsd/r.li.padsd.html (from rev 32770, grass/trunk/raster/r.li/r.li.padsd/description.html)
===================================================================
--- grass/trunk/raster/r.li/r.li.padsd/r.li.padsd.html (rev 0)
+++ grass/trunk/raster/r.li/r.li.padsd/r.li.padsd.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,52 @@
+<h2>DESCRIPTION</h2>
+<em>r.li.padsd</em> (patch area distribution standard deviation) calculates as:<br>
+<img src="rlipadsd_formula.png"> <br>
+with:<br>
+<ul>
+ <li><b>MPS</b>: mean patch area size<br></li>
+ <li><b>a<small><small>i</small></small></b>: area of patch i<br></li>
+ <li><b>N<small>patch</small></b>: number of patch<br></li>
+ </li>
+</ul>
+
+<h2>EXAMPLES</h2>
+To calculate mean pixel attribute index on map my_map, using
+my_conf configuration file and saving results in
+my_out file run:<br>
+<div class="code"><pre>
+r.li.padsd map=my_map conf=my_conf output=my_out
+</pre></div>
+
+<h2>NOTES</h2>
+Do not use absolute path names for output files. They are raster if
+moving window disposition was selected, otherwise they are in
+~/.r.li/output folder.<br>
+If input raster is not full of null values r.li.padsd returns a value >=0 that is PADsd. <br>
+If input raster is full of null values r.li.padsd returns -1. <br>
+If you want to have null values instead run <br>
+<div class="code"><pre>
+r.null setnull=-1 map=my_map
+</pre></div>
+
+after index calculation.
+
+<h2>REFERENCES</h2>
+McGarigal, K., and B. J. Marks. 1995. FRAGSTATS: spatial pattern
+analysis program for quantifying landscape structure. USDA For. Serv.
+Gen. Tech. Rep. PNW-351.
+
+<h2>SEE ALSO</h2>
+<em>
+<a href="r.li.html">r.li</a>
+</em>
+
+<h2>AUTHORS</h2>
+Serena Pallecchi student of Computer Science University of Pisa (Italy).<br>
+Commission from Faunalia Pontedera (PI), Italy (www.faunalia.it)
+
+
+<h2>BUGS</h2>
+Please send bugs reports to
+<a href="mailto:pallecch at cli.di.unipi.it">pallecch at cli.di.unipi.it</a><br>
+
+<p><i>Last changed: $Date$</i></p>
Deleted: grass/trunk/raster/r.li/r.li.patchdensity/description.html
===================================================================
--- grass/trunk/raster/r.li/r.li.patchdensity/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.li/r.li.patchdensity/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,64 +0,0 @@
-<H2>DESCRIPTION</H2>
-<EM>r.li.patchdensity</EM> is a patch index for <em>r.li</em> suite.
-It calculates the function:
-
-<div class="code"><pre>
-f(sample_area) = (Patch_Number/Area) * 1000000
-</pre></div>
-
-that is 1000000 by number of patch for area unit.
-This index is calculated using a 4 neighbour algorithm.
-
-<H2>EXAMPLES</H2>
-To calculate patch density index on map <em>my_map</em>, using <em>my_conf</em>
-configuration file (previously defined with <em>r.li.setup</em>) and saving
-results in the raster map <em>my_out</em>, run:
-
-<div class="code"><pre>
-r.li.patchdensity map=my_map conf=my_conf out=my_out
-</pre></div>
-
-<p>
-Example for Spearfish forest areas:
-<div class="code"><pre>
-g.region rast=landcover.30m -p
-# extract forested areas:
-r.category landcover.30m
-r.mapcalc "forests=if(landcover.30m >= 41 && landcover.30m <=43,1,null())"
-
-# patch density (7x7 moving window defined in r.li.setup):
-r.li.patchdensity forests conf=movwindow7 out=forests_p_dens7
-d.rast.leg forests_p_dens7
-
-r.to.vect forests out=forests feature=area
-d.vect forests type=boundary
-</pre></div>
-
-<H2>NOTES</H2>
-
-A map of NULL values is considered to have zero patches. <br>
-If you want to have null values instead run <br>
-<div class="code"><pre>
-r.null setnull=0 map=my_out
-<pre></div>
-after index calculation.<br>
-<!-- next ??????: -->
-If raster area is 0, <em>r.li.patchdensity</em> returns -1. This is only possible
-if the raster is masked.
-
-<H2>SEE ALSO</H2>
-<EM><A HREF="r.li.html">r.li</A></EM> package overview <BR>
-<EM><A HREF="r.li.daemon.html">r.li.daemon</A></EM><BR>
-<EM><A HREF="r.li.setup.html">r.li.setup</A></EM>
-
-<H2>AUTHORS</H2>
-Claudio Porta and Lucio Davide Spano, students of Computer Science
-University of Pisa (Italy).<br>
-Commission from Faunalia Pontedera (PI) (www.faunalia.it)<br>
-
-<H2>BUGS</h2>
-Please send bugs reports to
-<a href="mailto:spano at cli.di.unipi.it">spano at cli.di.unipi.it</a>,
-<a href="mailto:porta at cli.di.unipi.it">porta at cli.di.unipi.it</a><BR>
-
-<p><i>Last changed: $Date$</i<pre>
Copied: grass/trunk/raster/r.li/r.li.patchdensity/r.li.patchdensity.html (from rev 32770, grass/trunk/raster/r.li/r.li.patchdensity/description.html)
===================================================================
--- grass/trunk/raster/r.li/r.li.patchdensity/r.li.patchdensity.html (rev 0)
+++ grass/trunk/raster/r.li/r.li.patchdensity/r.li.patchdensity.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,64 @@
+<H2>DESCRIPTION</H2>
+<EM>r.li.patchdensity</EM> is a patch index for <em>r.li</em> suite.
+It calculates the function:
+
+<div class="code"><pre>
+f(sample_area) = (Patch_Number/Area) * 1000000
+</pre></div>
+
+that is 1000000 by number of patch for area unit.
+This index is calculated using a 4 neighbour algorithm.
+
+<H2>EXAMPLES</H2>
+To calculate patch density index on map <em>my_map</em>, using <em>my_conf</em>
+configuration file (previously defined with <em>r.li.setup</em>) and saving
+results in the raster map <em>my_out</em>, run:
+
+<div class="code"><pre>
+r.li.patchdensity map=my_map conf=my_conf out=my_out
+</pre></div>
+
+<p>
+Example for Spearfish forest areas:
+<div class="code"><pre>
+g.region rast=landcover.30m -p
+# extract forested areas:
+r.category landcover.30m
+r.mapcalc "forests=if(landcover.30m >= 41 && landcover.30m <=43,1,null())"
+
+# patch density (7x7 moving window defined in r.li.setup):
+r.li.patchdensity forests conf=movwindow7 out=forests_p_dens7
+d.rast.leg forests_p_dens7
+
+r.to.vect forests out=forests feature=area
+d.vect forests type=boundary
+</pre></div>
+
+<H2>NOTES</H2>
+
+A map of NULL values is considered to have zero patches. <br>
+If you want to have null values instead run <br>
+<div class="code"><pre>
+r.null setnull=0 map=my_out
+<pre></div>
+after index calculation.<br>
+<!-- next ??????: -->
+If raster area is 0, <em>r.li.patchdensity</em> returns -1. This is only possible
+if the raster is masked.
+
+<H2>SEE ALSO</H2>
+<EM><A HREF="r.li.html">r.li</A></EM> package overview <BR>
+<EM><A HREF="r.li.daemon.html">r.li.daemon</A></EM><BR>
+<EM><A HREF="r.li.setup.html">r.li.setup</A></EM>
+
+<H2>AUTHORS</H2>
+Claudio Porta and Lucio Davide Spano, students of Computer Science
+University of Pisa (Italy).<br>
+Commission from Faunalia Pontedera (PI) (www.faunalia.it)<br>
+
+<H2>BUGS</h2>
+Please send bugs reports to
+<a href="mailto:spano at cli.di.unipi.it">spano at cli.di.unipi.it</a>,
+<a href="mailto:porta at cli.di.unipi.it">porta at cli.di.unipi.it</a><BR>
+
+<p><i>Last changed: $Date$</i<pre>
Deleted: grass/trunk/raster/r.li/r.li.patchnum/description.html
===================================================================
--- grass/trunk/raster/r.li/r.li.patchnum/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.li/r.li.patchnum/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,40 +0,0 @@
-<H2>DESCRIPTION</H2>
-<EM>r.li.patchnum</EM> is a patch index for r.li program.<br>
-It calculates the function <br>
-<I> f(sample_area)= Patch_Number </I><br>
-This index is calculated using a 4 neighbour algorithm<br>
-
-<H2>EXAMPLES</H2>
-To calculate patch number index on map my_map, using
-<em>my_conf</em> configuration file and saving results in
-my_out file run:
-<div class="code"><pre>
-r.li.patchnumber map=my_map conf=my_conf out=my_out
-</pre></div>
-
-<H2>NOTES</H2>
-
-An that is full of null values is considered to have zero patch. <br>
-If you want to have null values instead run <br>
-<div class="code"><pre>
-r.null setnull=0 map=my_map
-</pre></div>
-after index calculation.<br>
-
-<H2>SEE ALSO</H2>
-<EM><A HREF="r.li.html">r.li</A></EM> package overview <BR>
-<EM><A HREF="r.li.daemon.html">r.li.daemon</A></EM><BR>
-<EM><A HREF="r.li.setup.html">r.li.setup</A></EM>
-
-<H2>AUTHORS</H2>
-Claudio Porta and Lucio Davide Spano, students of Computer Science
-University of Pisa (Italy).<br>
-Commission from Faunalia Pontedera (PI) (www.faunalia.it)<br>
-
-<H2>BUGS</h2>
-Please send bugs reports to
-<a href="mailto:spano at cli.di.unipi.it">spano at cli.di.unipi.it</a>,
-<a href="mailto:porta at cli.di.unipi.it">porta at cli.di.unipi.it</a><BR>
-
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.li/r.li.patchnum/r.li.patchnum.html (from rev 32770, grass/trunk/raster/r.li/r.li.patchnum/description.html)
===================================================================
--- grass/trunk/raster/r.li/r.li.patchnum/r.li.patchnum.html (rev 0)
+++ grass/trunk/raster/r.li/r.li.patchnum/r.li.patchnum.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,40 @@
+<H2>DESCRIPTION</H2>
+<EM>r.li.patchnum</EM> is a patch index for r.li program.<br>
+It calculates the function <br>
+<I> f(sample_area)= Patch_Number </I><br>
+This index is calculated using a 4 neighbour algorithm<br>
+
+<H2>EXAMPLES</H2>
+To calculate patch number index on map my_map, using
+<em>my_conf</em> configuration file and saving results in
+my_out file run:
+<div class="code"><pre>
+r.li.patchnumber map=my_map conf=my_conf out=my_out
+</pre></div>
+
+<H2>NOTES</H2>
+
+An that is full of null values is considered to have zero patch. <br>
+If you want to have null values instead run <br>
+<div class="code"><pre>
+r.null setnull=0 map=my_map
+</pre></div>
+after index calculation.<br>
+
+<H2>SEE ALSO</H2>
+<EM><A HREF="r.li.html">r.li</A></EM> package overview <BR>
+<EM><A HREF="r.li.daemon.html">r.li.daemon</A></EM><BR>
+<EM><A HREF="r.li.setup.html">r.li.setup</A></EM>
+
+<H2>AUTHORS</H2>
+Claudio Porta and Lucio Davide Spano, students of Computer Science
+University of Pisa (Italy).<br>
+Commission from Faunalia Pontedera (PI) (www.faunalia.it)<br>
+
+<H2>BUGS</h2>
+Please send bugs reports to
+<a href="mailto:spano at cli.di.unipi.it">spano at cli.di.unipi.it</a>,
+<a href="mailto:porta at cli.di.unipi.it">porta at cli.di.unipi.it</a><BR>
+
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.li/r.li.richness/description.html
===================================================================
--- grass/trunk/raster/r.li/r.li.richness/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.li/r.li.richness/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,45 +0,0 @@
-<h2>DESCRIPTION</h2>
-<em>r.li.richness</em> calculates the "richness's diversity index" as:<br>
-<img src="rliRichness_formula.png"> <br>
-with: <br>
-<ul>
- <li><b>m</b>: number of different patch type<br> </li>
-</ul>
-
-<h2>EXAMPLES</h2>
-To calculate richness's diversity index on map my_map, using
-my_conf configuration file and saving results in my_out file run:<br>
-<div class="code"><pre>
-r.li.richness map=my_map conf=my_conf output=my_out
-</pre></div>
-
-<h2>NOTES</h2>
-Do not use absolute path names for output files. They are raster if
-moving window disposition was selected, otherwise they are in
-~/.r.li/output folder. <br>
-
-If input raster is full of null values r.li.richness returns -1.<br>
-If you want to have null values instead run <br>
-after index calculation.
-
-<h2>REFERENCES</h2>
-McGarigal, K., and B. J. Marks. 1995. FRAGSTATS: spatial pattern
-analysis program for quantifying landscape structure. USDA For. Serv.
-Gen. Tech. Rep. PNW-351.
-
-<h2>SEE ALSO</h2>
-<em>
-<a href="r.li.html">r.li</a>
-</em>
-
-
-<h2>AUTHORS</h2>
-Serena Pallecchi student of Computer Science University of Pisa (Italy).<br>
-Commission from Faunalia Pontedera (PI), Italy (www.faunalia.it)
-
-<h2>BUGS</h2>
-Please send bugs reports to
-<a href="mailto:pallecch at cli.di.unipi.it">pallecch at cli.di.unipi.it</a><br>
-
-<p><i>Last changed: $Date$</i></p>
-
Copied: grass/trunk/raster/r.li/r.li.richness/r.li.richness.html (from rev 32770, grass/trunk/raster/r.li/r.li.richness/description.html)
===================================================================
--- grass/trunk/raster/r.li/r.li.richness/r.li.richness.html (rev 0)
+++ grass/trunk/raster/r.li/r.li.richness/r.li.richness.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,45 @@
+<h2>DESCRIPTION</h2>
+<em>r.li.richness</em> calculates the "richness's diversity index" as:<br>
+<img src="rliRichness_formula.png"> <br>
+with: <br>
+<ul>
+ <li><b>m</b>: number of different patch type<br> </li>
+</ul>
+
+<h2>EXAMPLES</h2>
+To calculate richness's diversity index on map my_map, using
+my_conf configuration file and saving results in my_out file run:<br>
+<div class="code"><pre>
+r.li.richness map=my_map conf=my_conf output=my_out
+</pre></div>
+
+<h2>NOTES</h2>
+Do not use absolute path names for output files. They are raster if
+moving window disposition was selected, otherwise they are in
+~/.r.li/output folder. <br>
+
+If input raster is full of null values r.li.richness returns -1.<br>
+If you want to have null values instead run <br>
+after index calculation.
+
+<h2>REFERENCES</h2>
+McGarigal, K., and B. J. Marks. 1995. FRAGSTATS: spatial pattern
+analysis program for quantifying landscape structure. USDA For. Serv.
+Gen. Tech. Rep. PNW-351.
+
+<h2>SEE ALSO</h2>
+<em>
+<a href="r.li.html">r.li</a>
+</em>
+
+
+<h2>AUTHORS</h2>
+Serena Pallecchi student of Computer Science University of Pisa (Italy).<br>
+Commission from Faunalia Pontedera (PI), Italy (www.faunalia.it)
+
+<h2>BUGS</h2>
+Please send bugs reports to
+<a href="mailto:pallecch at cli.di.unipi.it">pallecch at cli.di.unipi.it</a><br>
+
+<p><i>Last changed: $Date$</i></p>
+
Deleted: grass/trunk/raster/r.li/r.li.setup/description.html
===================================================================
--- grass/trunk/raster/r.li/r.li.setup/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.li/r.li.setup/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,158 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-<EM>r.li.setup</EM> creates and shows configuration files for the
-others r.li programs. For a general introduction, see
-<a href="r.li.html">r.li</a>.
-<br>
-The configurations are raster map independent,
-it means that you can use a file created on a raster map for analyze any
-other you have. <br>
-The program is completly interactive and uses a GUI to help you
-in your choices.
-
-<h3>Analysis methods</h3>
-
-Definition of region for analysis:
-<ul>
-<li> Whole maplayer: entire map (current region),
-<li> Keyboard setting: based on keyboard selection for region definition,
-<li> Draw the sampling frame: based on interactive region selection via mouse.
-</ul>
-
-Definition of creation of sampling area:
-<ul>
-<li> Whole maplayer: use entire area selected above,
-<li> Regions: select one to many subareas via mouse,
-<li> Sample units: automated selection of sampling area (for details see below)
-<ul>
- <li> Random nonoverlapping,
- <li> Systematic contiguous,
- <li> Systematic noncontiguous,
- <li> Stratified random,
- <li> Centered over sites (vector points).
-</ul>
-<li> Moving window: rectagular or circular with size
-<li> Select areas from the overlayed vector map (for details see below)
-</ul>
-
-<img src="sampleAreas.jpg" alt="Sampling area definition">
-
-
-<h3>Usage details</h3>
-
-The startup window shows your configuration files, you can:
-<ol>
-<li><em><b>Load a file</b></em>: the configuration is printed using
-rectangles with differents colors (green for the raster map,
-red for the sample
-frame and blue for the sample areas), and other notes (disposition of
-sample areas etc).
-The configuration file is saved in <tt>~/.r.li/history/my_conf</tt>.
-<!-- NOT REALLY CLEAR: -->
-Configuration output files are raster if moving window disposition was
-selected, otherwise they are in ~/.r.li/output folder.
-<br>
-All dimension are percentage of raster rows or columns.
-<li><em><b>Create a new file:</b></em> this create a new configuration
-file in an interactive way, in three steps
- <ol>
- <li> Choose file name and maps to use for setting:
- <ul>
- <li> <em>Configuration file name </em>(required): the name
- of new configuration file
- <li> <em>Raster map name</em> (required): the name of raster
- map to use for setting
- <li> <em>Vector map to overlay</em> (optional): name of a vector
- map to overlay in setting
- <li> <em>Site file to overlay</em> (optional): name of vector map
- of points type to overlay in setting
- </ul>
- <li> Set the sampling frame. The sample frame is a rectangular area
- which contains all the areas to analyze. It can be defined in three
- ways:
- <ul>
- <li><em>Whole map layer</em>: the sample frame is the whole map
- <li><em>Keyboard setting</em>: the user enters the coordinates in
- cells of upper left corner of sampling frame and its length in
- rows and columns</em>
- <li><em>Draw the sample frame</em>: the user draws the sample frame
- on map using mouse.
- </ul>
- <li> Set the sample areas. The sample areas are simply the areas to
- analyze. They can be defined in five ways (see the picture below):
- <ul>
- <li><em>Whole map layer</em>: the sample area is the whole sample
- frame
- <li><em>Regions</em>: the user enters the number of areas and then
- draws them using mouse.
- <li><em>Sample units</em>: they are areas of rectangular or circular
- shape. The user can define them using keyboard or mouse.
- <ul>
- <li>keyboard: the user define the shape of sample unists and
- their disposition:
- <ul>
- <li><em>Random non overlapping</em>: the user specifies
- the number of sample units and they are placed in a
- random way at runtime. It is guaranted that the
- areas do not intersect themselfs.
- <li><em>Systematic contiguous</em>: the defined sample
- is placed covering the sample frame, side by side
- across rows.
- <li><em>Systematic non contiguous</em>: the same as above,
- but here ever rectangle is spaced from another by
- a specified number of cells
- <li><em>Stratified random</em>: the sample frame is
- divided in n strats of rows and m strats of columns
- (n and m are given by user), then the specified
- number of sample areas are placed in a random way,
- one for every m*n areas defined by strats.
- <li><em>Centered over sites</em>: the sample areas
- are placed into sample frame centering them on points
- in site file.
- </ul>
- <li>mouse: the user chooses the shape and then draws the
- specified number of sample areas on map.
- </ul>
- <li><em>Moving Window:</em> the user defines a rectangular or
- circular area, it is moved over all the raster increasing only
- of a cell for every move(in columns if possible, if not in rows).
- It produces a new raster containing the result of all analysis.
- <li><em>Select areas from the overlayed vector map</em>:
- the sample areas are defined by the vector map selected above.
- For every cat in vector map, the procedure prompts the
- user if he wants to include it as sample area.
- The resulting configuration file can be used only with the
- specified raster map, and the procedure can be used only if
- whole map layer is selected as sampling frame.
- </ol>
-<li><em><b>Remove a file</b></em> the selected file is deleted from the
-available configuration files.
-<li><em><b>Help</b></em>: open this help text.
-<li><em><b>Close</b></em> module window.
-</ol>
-
-<H2>NOTES</H2>
-Configuration files are raster map independent because areas are saved using
-relative coordinates.
-
-<H2>SEE ALSO</H2>
-<EM><A HREF="http://grass.itc.it/gdp/landscape/r_le_manual5.pdf">
-old r.le manual</A></EM><BR>
-<EM><A HREF="r.li.html">r.li</A></EM> package overview <BR>
-<EM><A HREF="r.li.daemon.html">r.li.daemon</A></EM>,
-<EM><A HREF="r.li.patchdensity.html">r.li.patchdensity</A></EM>
-
-<H2>AUTHORS</H2>
-Claudio Porta & Lucio Davide Spano, students of Computer Science
-University of Pisa (Italy).<br>
-Commission from Faunalia Pontedera (PI)<br>
-Rebuild of r.le.setup from William L. Baker
-
-<H2>BUGS</h2>
-Pleas send bugs reports to
-<a href="mailto:spano at cli.di.unipi.it">spano at cli.di.unipi.it</a>,
-<a href="mailto:porta at cli.di.unipi.it">porta at cli.di.unipi.it</a><BR>
-<a href="mailto:cavallini at faunalia.it">cavallini at faunalia.it</a>
-
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.li/r.li.setup/r.li.setup.html (from rev 32770, grass/trunk/raster/r.li/r.li.setup/description.html)
===================================================================
--- grass/trunk/raster/r.li/r.li.setup/r.li.setup.html (rev 0)
+++ grass/trunk/raster/r.li/r.li.setup/r.li.setup.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,158 @@
+<H2>DESCRIPTION</H2>
+
+<EM>r.li.setup</EM> creates and shows configuration files for the
+others r.li programs. For a general introduction, see
+<a href="r.li.html">r.li</a>.
+<br>
+The configurations are raster map independent,
+it means that you can use a file created on a raster map for analyze any
+other you have. <br>
+The program is completly interactive and uses a GUI to help you
+in your choices.
+
+<h3>Analysis methods</h3>
+
+Definition of region for analysis:
+<ul>
+<li> Whole maplayer: entire map (current region),
+<li> Keyboard setting: based on keyboard selection for region definition,
+<li> Draw the sampling frame: based on interactive region selection via mouse.
+</ul>
+
+Definition of creation of sampling area:
+<ul>
+<li> Whole maplayer: use entire area selected above,
+<li> Regions: select one to many subareas via mouse,
+<li> Sample units: automated selection of sampling area (for details see below)
+<ul>
+ <li> Random nonoverlapping,
+ <li> Systematic contiguous,
+ <li> Systematic noncontiguous,
+ <li> Stratified random,
+ <li> Centered over sites (vector points).
+</ul>
+<li> Moving window: rectagular or circular with size
+<li> Select areas from the overlayed vector map (for details see below)
+</ul>
+
+<img src="sampleAreas.jpg" alt="Sampling area definition">
+
+
+<h3>Usage details</h3>
+
+The startup window shows your configuration files, you can:
+<ol>
+<li><em><b>Load a file</b></em>: the configuration is printed using
+rectangles with differents colors (green for the raster map,
+red for the sample
+frame and blue for the sample areas), and other notes (disposition of
+sample areas etc).
+The configuration file is saved in <tt>~/.r.li/history/my_conf</tt>.
+<!-- NOT REALLY CLEAR: -->
+Configuration output files are raster if moving window disposition was
+selected, otherwise they are in ~/.r.li/output folder.
+<br>
+All dimension are percentage of raster rows or columns.
+<li><em><b>Create a new file:</b></em> this create a new configuration
+file in an interactive way, in three steps
+ <ol>
+ <li> Choose file name and maps to use for setting:
+ <ul>
+ <li> <em>Configuration file name </em>(required): the name
+ of new configuration file
+ <li> <em>Raster map name</em> (required): the name of raster
+ map to use for setting
+ <li> <em>Vector map to overlay</em> (optional): name of a vector
+ map to overlay in setting
+ <li> <em>Site file to overlay</em> (optional): name of vector map
+ of points type to overlay in setting
+ </ul>
+ <li> Set the sampling frame. The sample frame is a rectangular area
+ which contains all the areas to analyze. It can be defined in three
+ ways:
+ <ul>
+ <li><em>Whole map layer</em>: the sample frame is the whole map
+ <li><em>Keyboard setting</em>: the user enters the coordinates in
+ cells of upper left corner of sampling frame and its length in
+ rows and columns</em>
+ <li><em>Draw the sample frame</em>: the user draws the sample frame
+ on map using mouse.
+ </ul>
+ <li> Set the sample areas. The sample areas are simply the areas to
+ analyze. They can be defined in five ways (see the picture below):
+ <ul>
+ <li><em>Whole map layer</em>: the sample area is the whole sample
+ frame
+ <li><em>Regions</em>: the user enters the number of areas and then
+ draws them using mouse.
+ <li><em>Sample units</em>: they are areas of rectangular or circular
+ shape. The user can define them using keyboard or mouse.
+ <ul>
+ <li>keyboard: the user define the shape of sample unists and
+ their disposition:
+ <ul>
+ <li><em>Random non overlapping</em>: the user specifies
+ the number of sample units and they are placed in a
+ random way at runtime. It is guaranted that the
+ areas do not intersect themselfs.
+ <li><em>Systematic contiguous</em>: the defined sample
+ is placed covering the sample frame, side by side
+ across rows.
+ <li><em>Systematic non contiguous</em>: the same as above,
+ but here ever rectangle is spaced from another by
+ a specified number of cells
+ <li><em>Stratified random</em>: the sample frame is
+ divided in n strats of rows and m strats of columns
+ (n and m are given by user), then the specified
+ number of sample areas are placed in a random way,
+ one for every m*n areas defined by strats.
+ <li><em>Centered over sites</em>: the sample areas
+ are placed into sample frame centering them on points
+ in site file.
+ </ul>
+ <li>mouse: the user chooses the shape and then draws the
+ specified number of sample areas on map.
+ </ul>
+ <li><em>Moving Window:</em> the user defines a rectangular or
+ circular area, it is moved over all the raster increasing only
+ of a cell for every move(in columns if possible, if not in rows).
+ It produces a new raster containing the result of all analysis.
+ <li><em>Select areas from the overlayed vector map</em>:
+ the sample areas are defined by the vector map selected above.
+ For every cat in vector map, the procedure prompts the
+ user if he wants to include it as sample area.
+ The resulting configuration file can be used only with the
+ specified raster map, and the procedure can be used only if
+ whole map layer is selected as sampling frame.
+ </ol>
+<li><em><b>Remove a file</b></em> the selected file is deleted from the
+available configuration files.
+<li><em><b>Help</b></em>: open this help text.
+<li><em><b>Close</b></em> module window.
+</ol>
+
+<H2>NOTES</H2>
+Configuration files are raster map independent because areas are saved using
+relative coordinates.
+
+<H2>SEE ALSO</H2>
+<EM><A HREF="http://grass.itc.it/gdp/landscape/r_le_manual5.pdf">
+old r.le manual</A></EM><BR>
+<EM><A HREF="r.li.html">r.li</A></EM> package overview <BR>
+<EM><A HREF="r.li.daemon.html">r.li.daemon</A></EM>,
+<EM><A HREF="r.li.patchdensity.html">r.li.patchdensity</A></EM>
+
+<H2>AUTHORS</H2>
+Claudio Porta & Lucio Davide Spano, students of Computer Science
+University of Pisa (Italy).<br>
+Commission from Faunalia Pontedera (PI)<br>
+Rebuild of r.le.setup from William L. Baker
+
+<H2>BUGS</h2>
+Pleas send bugs reports to
+<a href="mailto:spano at cli.di.unipi.it">spano at cli.di.unipi.it</a>,
+<a href="mailto:porta at cli.di.unipi.it">porta at cli.di.unipi.it</a><BR>
+<a href="mailto:cavallini at faunalia.it">cavallini at faunalia.it</a>
+
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.li/r.li.shannon/description.html
===================================================================
--- grass/trunk/raster/r.li/r.li.shannon/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.li/r.li.shannon/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,50 +0,0 @@
-<h2>DESCRIPTION</h2>
-<em>r.li.shannon</em>
-calculates the "shannon's diversity index" as: <br>
-<img src="rliShannon_formula.png"><br>
-with:<br>
-<ul>
- <li><b>i</b>: patch type<br></li>
- <li><b>m</b>: number of patch type<br></li>
- <li><b>p<small><small>i</small></small></b>: proportion of the landscape occupied by patch type i<br></li>
-</ul>
-
-<h2>REFERENCES</h2>
-McGarigal, K., and B. J. Marks. 1995. FRAGSTATS: spatial pattern
-analysis program for quantifying landscape structure. USDA For. Serv.
-Gen. Tech. Rep. PNW-351.
-
-<h2>EXAMPLES</h2>
-To calculate shannon's diversity index on map my_map, using
-my_conf configuration file and saving results in my_out file run:<br>
-<div class="code"><pre>
-r.li.shannon map=my_map conf=my_conf output=my_out
-</pre></div>
-
-<h2>NOTES</h2>
-Do not use absolute path names for output files. They are raster if
-moving window disposition was selected, otherwise they are in
-~/.r.li/output folder. <br>
-If input raster is full of null values r.li.shannon returns -1. <br>
-If you want to have null values instead run <br>
-<div class="code"><pre>
-r.null setnull=-1 map=my_map
-</pre></div>
-after index calculation.
-
-
-<h2>SEE ALSO</h2>
-<em>
-<a href="r.li.html">r.li</a>
-</em>
-
-<h2>AUTHORS</h2>
-Serena Pallecchi student of Computer Science University of Pisa (Italy).<br>
-Commission from Faunalia Pontedera (PI), Italy (www.faunalia.it)
-
-<h2>BUGS</h2>
-Please send bugs reports to
-<a href="mailto:pallecch at cli.di.unipi.it">pallecch at cli.di.unipi.it</a><br>
-
-<p><i>Last changed: $Date$</i>
-
Copied: grass/trunk/raster/r.li/r.li.shannon/r.li.shannon.html (from rev 32770, grass/trunk/raster/r.li/r.li.shannon/description.html)
===================================================================
--- grass/trunk/raster/r.li/r.li.shannon/r.li.shannon.html (rev 0)
+++ grass/trunk/raster/r.li/r.li.shannon/r.li.shannon.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,50 @@
+<h2>DESCRIPTION</h2>
+<em>r.li.shannon</em>
+calculates the "shannon's diversity index" as: <br>
+<img src="rliShannon_formula.png"><br>
+with:<br>
+<ul>
+ <li><b>i</b>: patch type<br></li>
+ <li><b>m</b>: number of patch type<br></li>
+ <li><b>p<small><small>i</small></small></b>: proportion of the landscape occupied by patch type i<br></li>
+</ul>
+
+<h2>REFERENCES</h2>
+McGarigal, K., and B. J. Marks. 1995. FRAGSTATS: spatial pattern
+analysis program for quantifying landscape structure. USDA For. Serv.
+Gen. Tech. Rep. PNW-351.
+
+<h2>EXAMPLES</h2>
+To calculate shannon's diversity index on map my_map, using
+my_conf configuration file and saving results in my_out file run:<br>
+<div class="code"><pre>
+r.li.shannon map=my_map conf=my_conf output=my_out
+</pre></div>
+
+<h2>NOTES</h2>
+Do not use absolute path names for output files. They are raster if
+moving window disposition was selected, otherwise they are in
+~/.r.li/output folder. <br>
+If input raster is full of null values r.li.shannon returns -1. <br>
+If you want to have null values instead run <br>
+<div class="code"><pre>
+r.null setnull=-1 map=my_map
+</pre></div>
+after index calculation.
+
+
+<h2>SEE ALSO</h2>
+<em>
+<a href="r.li.html">r.li</a>
+</em>
+
+<h2>AUTHORS</h2>
+Serena Pallecchi student of Computer Science University of Pisa (Italy).<br>
+Commission from Faunalia Pontedera (PI), Italy (www.faunalia.it)
+
+<h2>BUGS</h2>
+Please send bugs reports to
+<a href="mailto:pallecch at cli.di.unipi.it">pallecch at cli.di.unipi.it</a><br>
+
+<p><i>Last changed: $Date$</i>
+
Deleted: grass/trunk/raster/r.li/r.li.shape/description.html
===================================================================
--- grass/trunk/raster/r.li/r.li.shape/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.li/r.li.shape/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,30 +0,0 @@
-<H2>DESCRIPTION</H2>
-<EM>r.li.shape</EM> is a patch index for r.li program.<br>
-It calculates the function <br>
-<I> f(sample_area)= Area </I><br>
-
-<H2>EXAMPLES</H2>
-To calculate area index on map my_map, using
-<em>my_conf</em> configuration file and saving results in
-my_out file run:
-<div class="code"><pre>
-r.li.shape map=my_map conf=my_conf out=my_out
-</pre></div>
-
-<H2>SEE ALSO</H2>
-<EM><A HREF="r.li.html">r.li</A></EM> package overview <BR>
-<EM><A HREF="r.li.daemon.html">r.li.daemon</A></EM><BR>
-<EM><A HREF="r.li.setup.html">r.li.setup</A></EM>
-
-<H2>AUTHORS</H2>
-Claudio Porta and Lucio Davide Spano, students of Computer Science
-University of Pisa (Italy).<br>
-Commission from Faunalia Pontedera (PI) (www.faunalia.it)<br>
-
-<H2>BUGS</h2>
-Please send bugs reports to
-<a href="mailto:spano at cli.di.unipi.it">spano at cli.di.unipi.it</a>,
-<a href="mailto:porta at cli.di.unipi.it">porta at cli.di.unipi.it</a><BR>
-<BR>
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.li/r.li.shape/r.li.shape.html (from rev 32770, grass/trunk/raster/r.li/r.li.shape/description.html)
===================================================================
--- grass/trunk/raster/r.li/r.li.shape/r.li.shape.html (rev 0)
+++ grass/trunk/raster/r.li/r.li.shape/r.li.shape.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,30 @@
+<H2>DESCRIPTION</H2>
+<EM>r.li.shape</EM> is a patch index for r.li program.<br>
+It calculates the function <br>
+<I> f(sample_area)= Area </I><br>
+
+<H2>EXAMPLES</H2>
+To calculate area index on map my_map, using
+<em>my_conf</em> configuration file and saving results in
+my_out file run:
+<div class="code"><pre>
+r.li.shape map=my_map conf=my_conf out=my_out
+</pre></div>
+
+<H2>SEE ALSO</H2>
+<EM><A HREF="r.li.html">r.li</A></EM> package overview <BR>
+<EM><A HREF="r.li.daemon.html">r.li.daemon</A></EM><BR>
+<EM><A HREF="r.li.setup.html">r.li.setup</A></EM>
+
+<H2>AUTHORS</H2>
+Claudio Porta and Lucio Davide Spano, students of Computer Science
+University of Pisa (Italy).<br>
+Commission from Faunalia Pontedera (PI) (www.faunalia.it)<br>
+
+<H2>BUGS</h2>
+Please send bugs reports to
+<a href="mailto:spano at cli.di.unipi.it">spano at cli.di.unipi.it</a>,
+<a href="mailto:porta at cli.di.unipi.it">porta at cli.di.unipi.it</a><BR>
+<BR>
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.li/r.li.simpson/description.html
===================================================================
--- grass/trunk/raster/r.li/r.li.simpson/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.li/r.li.simpson/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,53 +0,0 @@
-<h2>DESCRIPTION</h2>
-<em>r.li.simpson</em>
-calculates the "simpson's diversity index" as:<br>
-<img src="rliSimpson_formula.png"> <br>
-with: <br>
-<ul>
- <li><b>i</b>: patch type<br> </li>
- <li><b>m</b>: number of patch type<br> </li>
- <li><b>p<small><small>i</small></small></b>: proportion of the landscape occupied by patch type i<br> </li>
-</ul>
-
-
-<h2>REFERENCES</h2>
-McGarigal, K., and B. J. Marks. 1995. FRAGSTATS: spatial pattern
-analysis program for quantifying landscape structure. USDA For. Serv.
-Gen. Tech. Rep. PNW-351.
-
-<h2>EXAMPLES</h2>
-To calculate simpson's diversity index on map my_map, using
-my_conf configuration file and saving results in my_out file run:<br>
-<div class="code"><pre>
-r.li.simpson map=my_map conf=my_conf output=my_out
-</pre></div>
-
-<h2>NOTES</h2>
-Do not use absolute path names for output files. They are raster if
-moving window disposition was selected, otherwise they are in
-~/.r.li/output folder. <br>
-
-If input raster is full of null values r.li.simpson returns -1.<br>
-If you want to have null values instead run <br>
-<div class="code"><pre>
-r.null setnull=-1 map=my_map
-</pre></div>
-after index calculation.
-
-
-<h2>SEE ALSO</h2>
-<em>
-<a href="r.li.html">r.li</a>
-</em>
-
-
-<h2>AUTHORS</h2>
-Serena Pallecchi student of Computer Science University of Pisa (Italy).<br>
-Commission from Faunalia Pontedera (PI), Italy (www.faunalia.it)
-
-<h2>BUGS</h2>
-Please send bugs reports to
-<a href="mailto:pallecch at cli.di.unipi.it">pallecch at cli.di.unipi.it</a><br>
-
-<p><i>Last changed: $Date$</i>
-
Copied: grass/trunk/raster/r.li/r.li.simpson/r.li.simpson.html (from rev 32770, grass/trunk/raster/r.li/r.li.simpson/description.html)
===================================================================
--- grass/trunk/raster/r.li/r.li.simpson/r.li.simpson.html (rev 0)
+++ grass/trunk/raster/r.li/r.li.simpson/r.li.simpson.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,53 @@
+<h2>DESCRIPTION</h2>
+<em>r.li.simpson</em>
+calculates the "simpson's diversity index" as:<br>
+<img src="rliSimpson_formula.png"> <br>
+with: <br>
+<ul>
+ <li><b>i</b>: patch type<br> </li>
+ <li><b>m</b>: number of patch type<br> </li>
+ <li><b>p<small><small>i</small></small></b>: proportion of the landscape occupied by patch type i<br> </li>
+</ul>
+
+
+<h2>REFERENCES</h2>
+McGarigal, K., and B. J. Marks. 1995. FRAGSTATS: spatial pattern
+analysis program for quantifying landscape structure. USDA For. Serv.
+Gen. Tech. Rep. PNW-351.
+
+<h2>EXAMPLES</h2>
+To calculate simpson's diversity index on map my_map, using
+my_conf configuration file and saving results in my_out file run:<br>
+<div class="code"><pre>
+r.li.simpson map=my_map conf=my_conf output=my_out
+</pre></div>
+
+<h2>NOTES</h2>
+Do not use absolute path names for output files. They are raster if
+moving window disposition was selected, otherwise they are in
+~/.r.li/output folder. <br>
+
+If input raster is full of null values r.li.simpson returns -1.<br>
+If you want to have null values instead run <br>
+<div class="code"><pre>
+r.null setnull=-1 map=my_map
+</pre></div>
+after index calculation.
+
+
+<h2>SEE ALSO</h2>
+<em>
+<a href="r.li.html">r.li</a>
+</em>
+
+
+<h2>AUTHORS</h2>
+Serena Pallecchi student of Computer Science University of Pisa (Italy).<br>
+Commission from Faunalia Pontedera (PI), Italy (www.faunalia.it)
+
+<h2>BUGS</h2>
+Please send bugs reports to
+<a href="mailto:pallecch at cli.di.unipi.it">pallecch at cli.di.unipi.it</a><br>
+
+<p><i>Last changed: $Date$</i>
+
Deleted: grass/trunk/raster/r.los/description.html
===================================================================
--- grass/trunk/raster/r.los/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.los/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,95 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-
-<em>r.los</em> generates a raster output map in which the cells that are
-visible from a user-specified observer position are marked with the
-vertical angle (in degrees) required to see those cells (viewshed).
-A value of 0 is directly below the specified viewing position,
-90 is due horizontal, and 180 is directly above the observer.
-The angle to the cell containing the viewing position is undefined
-and set to 180.
-
-<p>
-To run <em>r.los</em>, the user must specify at least
-an <b>input</b> map name, <b>output</b> map name, and the geographic
-<b>coordinate</b>s of the user's viewing location;
-any remaining parameters whose values are unspecified
-will be set to their default values (see below).
-
-<p>
-The <b>patt_map</b> is the name of a binary (1/0) raster map layer in which
-cells within the areas of interest are assigned the category value '1', and
-all other cells are assigned the category value '0' or NULL. If this parameter is
-omitted, the analysis will be performed for the whole area within a certain
-distance of the viewing point inside the geographic region boundaries.
-<br>
-Default: assign all cells that are within the <b>max_dist</b> and within
-the user's current geographic region boundaries a value of 1.
-
-<p>
-The <b>obs_elev</b> parameter defines the height of the observer (in
-meters) above the viewing point's elevation.
-<p>
-
-The <b>max_dist</b> parameter is the maximum distance (in meters) from the
-viewing point inside of which the line of sight analysis will be performed.
-The cells outside this distance range are assigned a NULL value.
-
-
-<h2>NOTES</h2>
-
-For accurate results, the program must be run with the resolution of the
-geographic region set equal to the resolution of the data
-(see <em><a href="g.region.html">g.region</a></em>).
-
-<p>
-The time to complete the calculation increases dramatically with the region size.
-Try to keep the columns and rows under 1000.
-
-<p>
-It is advisable to use a 'pattern layer' which identifies
-the areas of interest in which the line of sight analysis
-is required. Such a measure will reduce the time taken by
-the program to run.
-
-<p>
-The curvature of the Earth is not taken into account for these calculations.
-However, for interest's sake, a handy calculation for distance to the true horizon
-is approximated by <i>d = sqrt(13*h)</i> where <i>h</i> is the height of the observer
-in meters (above sea level) and <i>d</i> is the distance to the horizon in km.
-This may be useful for setting the <b>max_dist</b> value.
-
-
-<h2>EXAMPLE</h2>
-
-Spearfish example - calculation of viewshed from 50m tower
-on top of a mountain:
-
-<div class="code"><pre>
-r.los elevation.dem out=los coord=598869,4916642 obs_elev=50 max_dist=10000
-r.colors -e los color=bgyr
-d.shadedmap relief=aspect drape=los bright=10
-echo "symbol extra/target 25 598869 4916642 red" | d.graph -m
-</pre></div>
-
-<h2>TODO</h2>
-
-Rewrite using ideas from <em>r.cva</em> and a method which scales better
-to large regions.<br>A suggested method is detailed in:<br>
-Izraelevitz, David (USACE).<br>
-'A Fast Algorithm for Approximate Viewshed Computation'<br>
-<i>Photogrammetric Engineering & Remote Sensing</i>, July 2003
-<!-- http://article.gmane.org/gmane.comp.gis.grass.devel/1781
- Post by Paul Kelly 2003-08-13 to grass-dev,
- "Re: [bug #2061] (grass) r.los needs FP update" -->
-
-<h2>SEE ALSO</h2>
-
-<em><a href="g.region.html">g.region</a></em>
-
-<h2>AUTHOR</h2>
-
-Kewan Q. Khawaja, Intelligent Engineering Systems Laboratory, M.I.T.
-
-<p>
-<i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.los/r.los.html (from rev 32770, grass/trunk/raster/r.los/description.html)
===================================================================
--- grass/trunk/raster/r.los/r.los.html (rev 0)
+++ grass/trunk/raster/r.los/r.los.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,95 @@
+<h2>DESCRIPTION</h2>
+
+
+<em>r.los</em> generates a raster output map in which the cells that are
+visible from a user-specified observer position are marked with the
+vertical angle (in degrees) required to see those cells (viewshed).
+A value of 0 is directly below the specified viewing position,
+90 is due horizontal, and 180 is directly above the observer.
+The angle to the cell containing the viewing position is undefined
+and set to 180.
+
+<p>
+To run <em>r.los</em>, the user must specify at least
+an <b>input</b> map name, <b>output</b> map name, and the geographic
+<b>coordinate</b>s of the user's viewing location;
+any remaining parameters whose values are unspecified
+will be set to their default values (see below).
+
+<p>
+The <b>patt_map</b> is the name of a binary (1/0) raster map layer in which
+cells within the areas of interest are assigned the category value '1', and
+all other cells are assigned the category value '0' or NULL. If this parameter is
+omitted, the analysis will be performed for the whole area within a certain
+distance of the viewing point inside the geographic region boundaries.
+<br>
+Default: assign all cells that are within the <b>max_dist</b> and within
+the user's current geographic region boundaries a value of 1.
+
+<p>
+The <b>obs_elev</b> parameter defines the height of the observer (in
+meters) above the viewing point's elevation.
+<p>
+
+The <b>max_dist</b> parameter is the maximum distance (in meters) from the
+viewing point inside of which the line of sight analysis will be performed.
+The cells outside this distance range are assigned a NULL value.
+
+
+<h2>NOTES</h2>
+
+For accurate results, the program must be run with the resolution of the
+geographic region set equal to the resolution of the data
+(see <em><a href="g.region.html">g.region</a></em>).
+
+<p>
+The time to complete the calculation increases dramatically with the region size.
+Try to keep the columns and rows under 1000.
+
+<p>
+It is advisable to use a 'pattern layer' which identifies
+the areas of interest in which the line of sight analysis
+is required. Such a measure will reduce the time taken by
+the program to run.
+
+<p>
+The curvature of the Earth is not taken into account for these calculations.
+However, for interest's sake, a handy calculation for distance to the true horizon
+is approximated by <i>d = sqrt(13*h)</i> where <i>h</i> is the height of the observer
+in meters (above sea level) and <i>d</i> is the distance to the horizon in km.
+This may be useful for setting the <b>max_dist</b> value.
+
+
+<h2>EXAMPLE</h2>
+
+Spearfish example - calculation of viewshed from 50m tower
+on top of a mountain:
+
+<div class="code"><pre>
+r.los elevation.dem out=los coord=598869,4916642 obs_elev=50 max_dist=10000
+r.colors -e los color=bgyr
+d.shadedmap relief=aspect drape=los bright=10
+echo "symbol extra/target 25 598869 4916642 red" | d.graph -m
+</pre></div>
+
+<h2>TODO</h2>
+
+Rewrite using ideas from <em>r.cva</em> and a method which scales better
+to large regions.<br>A suggested method is detailed in:<br>
+Izraelevitz, David (USACE).<br>
+'A Fast Algorithm for Approximate Viewshed Computation'<br>
+<i>Photogrammetric Engineering & Remote Sensing</i>, July 2003
+<!-- http://article.gmane.org/gmane.comp.gis.grass.devel/1781
+ Post by Paul Kelly 2003-08-13 to grass-dev,
+ "Re: [bug #2061] (grass) r.los needs FP update" -->
+
+<h2>SEE ALSO</h2>
+
+<em><a href="g.region.html">g.region</a></em>
+
+<h2>AUTHOR</h2>
+
+Kewan Q. Khawaja, Intelligent Engineering Systems Laboratory, M.I.T.
+
+<p>
+<i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.median/description.html
===================================================================
--- grass/trunk/raster/r.median/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.median/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,68 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-
-<em>r.median</em> calculates the median category of data
-contained in a <b>cover</b> raster map layer for areas
-assigned the same category value in the user-specified
-<b>base</b> raster map layer. These median values are
-stored in the new <b>output</b> map layer.
-
-<p>
-The <b>output</b> map is actually a <em>reclass</em> of the <b>base</b> map.
-
-The <b>base</b> map is an existing raster map layer in the user's current
-mapset search path. For each group of cells assigned the
-same category value in the <b>base</b> map, the median of
-the values assigned these cells in the <b>cover</b> map
-will be computed.
-
-<p>
-The <b>cover</b> map is an existing raster map layer containing the values
-to be used to compute the median within each category of the <b>base</b> map.
-
-
-<h2>NOTES</h2>
-
-The user should use the results of <em>r.median</em> with
-care. Since this utility assigns a value to each cell
-which is based on global information (i.e., information at
-spatial locations other than just the location of the cell
-itself), the resultant map layer is only valid if the
-geographic region and mask settings are the same as they
-were at the time that the result map was created.
-
-<p>
-Results are affected by the current region settings and mask.
-
-<h2>EXAMPLE</h2>
-
-Median K-factor (erosion) for Spearfish fields:
-
-<div class="code"><pre>
-g.region rast=fields -p
-r.median base=fields cover=soils.Kfactor output=K.by.farm.median
-r.univar K.by.farm.median
-</pre></div>
-
-<h2>SEE ALSO</h2>
-
-<em><a href="g.region.html">g.region</a></em>,
-<em><a href="r.average.html">r.average</a></em>,
-<em><a href="r.category.html">r.category</a></em>,
-<em><a href="r.clump.html">r.clump</a></em>,
-<em><a href="r.describe.html">r.describe</a></em>,
-<em><a href="r.mapcalc.html">r.mapcalc</a></em>,
-<em><a href="r.mfilter.html">r.mfilter</a></em>,
-<em><a href="r.mode.html">r.mode</a></em>,
-<em><a href="r.neighbors.html">r.neighbors</a></em>,
-<em><a href="r.reclass.html">r.reclass</a></em>,
-<em><a href="r.statistics.html">r.statistics</a></em>,
-<em><a href="r.stats.html">r.stats</a></em>,
-<em><a href="r.univar.html">r.univar</a></em>
-
-<h2>AUTHOR</h2>
-
-Michael Shapiro,
-U.S.Army Construction Engineering Research Laboratory
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.median/r.median.html (from rev 32770, grass/trunk/raster/r.median/description.html)
===================================================================
--- grass/trunk/raster/r.median/r.median.html (rev 0)
+++ grass/trunk/raster/r.median/r.median.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,68 @@
+<h2>DESCRIPTION</h2>
+
+
+<em>r.median</em> calculates the median category of data
+contained in a <b>cover</b> raster map layer for areas
+assigned the same category value in the user-specified
+<b>base</b> raster map layer. These median values are
+stored in the new <b>output</b> map layer.
+
+<p>
+The <b>output</b> map is actually a <em>reclass</em> of the <b>base</b> map.
+
+The <b>base</b> map is an existing raster map layer in the user's current
+mapset search path. For each group of cells assigned the
+same category value in the <b>base</b> map, the median of
+the values assigned these cells in the <b>cover</b> map
+will be computed.
+
+<p>
+The <b>cover</b> map is an existing raster map layer containing the values
+to be used to compute the median within each category of the <b>base</b> map.
+
+
+<h2>NOTES</h2>
+
+The user should use the results of <em>r.median</em> with
+care. Since this utility assigns a value to each cell
+which is based on global information (i.e., information at
+spatial locations other than just the location of the cell
+itself), the resultant map layer is only valid if the
+geographic region and mask settings are the same as they
+were at the time that the result map was created.
+
+<p>
+Results are affected by the current region settings and mask.
+
+<h2>EXAMPLE</h2>
+
+Median K-factor (erosion) for Spearfish fields:
+
+<div class="code"><pre>
+g.region rast=fields -p
+r.median base=fields cover=soils.Kfactor output=K.by.farm.median
+r.univar K.by.farm.median
+</pre></div>
+
+<h2>SEE ALSO</h2>
+
+<em><a href="g.region.html">g.region</a></em>,
+<em><a href="r.average.html">r.average</a></em>,
+<em><a href="r.category.html">r.category</a></em>,
+<em><a href="r.clump.html">r.clump</a></em>,
+<em><a href="r.describe.html">r.describe</a></em>,
+<em><a href="r.mapcalc.html">r.mapcalc</a></em>,
+<em><a href="r.mfilter.html">r.mfilter</a></em>,
+<em><a href="r.mode.html">r.mode</a></em>,
+<em><a href="r.neighbors.html">r.neighbors</a></em>,
+<em><a href="r.reclass.html">r.reclass</a></em>,
+<em><a href="r.statistics.html">r.statistics</a></em>,
+<em><a href="r.stats.html">r.stats</a></em>,
+<em><a href="r.univar.html">r.univar</a></em>
+
+<h2>AUTHOR</h2>
+
+Michael Shapiro,
+U.S.Army Construction Engineering Research Laboratory
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.mfilter/description.html
===================================================================
--- grass/trunk/raster/r.mfilter/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.mfilter/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,156 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-
-<em>r.mfilter</em> filters the raster <em>input</em> to produce the
-raster <em>output</em> according to the matrix <em>filter</em> designed
-by the user (see <em>FILTERS</em> below).
-The filter is applied <em>repeat</em> times (default <em>value</em> is 1).
-The <em>output</em> raster map layer can be given a <em>TITLE</em> if desired.
-(This TITLE should be put in quotes if it contains more than one word.)
-
-With <b>-z</b> flag the filter is applied only to zero category values in
-the input raster map layer. The non-zero category values are not changed.
-Note that if there is more than one filter step, this rule is applied to the
-intermediate raster map layer -- only zero category values which result from
-the first filter will be changed. In most cases this will NOT be the
-desired result. Hence -z should be used only with single step filters.
-<p>
-
-The <b>filter</b> parameter defines the name of an existing, user-created
-UNIX ASCII file whose contents is a matrix defining the way in which the
-<em>input</em> file will be filtered. The format of this file is described
-below, under FILTERS.
-<p>
-
-The <b>repeat</b> parameter defines the number of times the <em>filter</em>
-is to be applied to the <em>input</em> data.
-
-<h2>FILTERS</h2>
-
-The <em>filter</em> file is a normal UNIX ASCII file designed by the user.
-It has the following format:
-<pre>
- TITLE TITLE
- MATRIX n
- .
- n lines of n integers
- .
- DIVISOR d
- TYPE S/P
-</pre>
-
-
-<dt>TITLE
-
-<dd>A one-line TITLE for the filter.
-If a TITLE was not specified on the command line, it can be specified here.
-This TITLE would be used to construct a TITLE for the resulting raster map
-layer. It should be a one-line description of the filter.
-
-<dt>MATRIX
-
-<dd>The matrix (n x n) follows on the next n lines. <em>n</em> must be
-an odd integer greater than or equal to 3.
-The matrix itself consists of n rows of n integers.
-The integers must be separated from each other by at least 1 blank.
-
-<dt>DIVISOR
-
-<dd>The filter divisor is <em>d</em>. If not specified, the default is 1.
-If the divisor is zero (0), then the divisor is dependent on the
-category values in the neighborhood
-(see HOW THE FILTER WORKS below).
-
-<dt>TYPE
-
-<dd>The filter type. <em>S</em> means sequential, while <em>P</em> mean parallel.
-If not specified, the default is S.
-
-
-<p>
-
-Sequential filtering happens in place. As the filter is applied to the
-raster map layer, the category values that were changed in neighboring
-cells affect the resulting category value of the current
-cell being filtered.
-
-
-<p>
-Parallel filtering happens in such a way that the original raster
-map layer category values are used to produce the new category value.
-
-
-<p>
-More than one filter may be specified in the filter file.
-The additional filter(s) are described just like the first.
-For example, the following describes two filters:
-</p>
-
-</dd>
-
-
-<h2>EXAMPLE FILTER FILE</h2>
-
-<pre>
- TITLE 3x3 average, non-zero data only, followed by 5x5 average
- MATRIX 3
- 1 1 1
- 1 1 1
- 1 1 1
- DIVISOR 0
- TYPE P
-
- MATRIX 5
- 1 1 1 1 1
- 1 1 1 1 1
- 1 1 1 1 1
- 1 1 1 1 1
- 1 1 1 1 1
- DIVISOR 25
- TYPE P
-</pre>
-
-<h2>HOW THE FILTER WORKS</h2>
-
-The filter process produces a new category value for each cell
-in the input raster map layer by multiplying the category values of the
-cells in the n x n neighborhood around the center cell
-by the corresponding matrix value and adding them together.
-If a divisor is specified, the sum is divided by this divisor,
-rounding to the nearest integer.
-(If a zero divisor was specified, then
-the divisor is computed for each cell as the sum of the MATRIX
-values where the corresponding input cell is non-zero.)
-
-
-<p>
-
-If more than one filter step is specified, either because the
-repeat value was greater than one or because the filter file
-contained more than one matrix, these steps are performed
-sequentially. This means that first one filter is applied to
-the entire input raster map layer to produce an intermediate result;
-then the next filter is applied to the intermediate result to
-produce another intermediate result; and so on, until the
-final filter is applied. Then the output cell is written.
-
-<h2>NOTES</h2>
-
-If the resolution of the geographic region does not agree with the
-resolution of the raster map layer, unintended resampling of the original
-data may occur. The user should be sure that the geographic region
-is set properly.
-
-<h2>SEE ALSO</h2>
-
-<em><a href="g.region.html">g.region</a></em>,
-<em><a href="r.clump.html">r.clump</a></em>,
-<em><a href="r.neighbors.html">r.neighbors</a></em>
-
-<h2>AUTHOR</h2>
-
-Michael Shapiro,
-U.S.Army Construction Engineering Research Laboratory
-
-<p>
-<i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.mfilter/r.mfilter.html (from rev 32770, grass/trunk/raster/r.mfilter/description.html)
===================================================================
--- grass/trunk/raster/r.mfilter/r.mfilter.html (rev 0)
+++ grass/trunk/raster/r.mfilter/r.mfilter.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,156 @@
+<h2>DESCRIPTION</h2>
+
+
+<em>r.mfilter</em> filters the raster <em>input</em> to produce the
+raster <em>output</em> according to the matrix <em>filter</em> designed
+by the user (see <em>FILTERS</em> below).
+The filter is applied <em>repeat</em> times (default <em>value</em> is 1).
+The <em>output</em> raster map layer can be given a <em>TITLE</em> if desired.
+(This TITLE should be put in quotes if it contains more than one word.)
+
+With <b>-z</b> flag the filter is applied only to zero category values in
+the input raster map layer. The non-zero category values are not changed.
+Note that if there is more than one filter step, this rule is applied to the
+intermediate raster map layer -- only zero category values which result from
+the first filter will be changed. In most cases this will NOT be the
+desired result. Hence -z should be used only with single step filters.
+<p>
+
+The <b>filter</b> parameter defines the name of an existing, user-created
+UNIX ASCII file whose contents is a matrix defining the way in which the
+<em>input</em> file will be filtered. The format of this file is described
+below, under FILTERS.
+<p>
+
+The <b>repeat</b> parameter defines the number of times the <em>filter</em>
+is to be applied to the <em>input</em> data.
+
+<h2>FILTERS</h2>
+
+The <em>filter</em> file is a normal UNIX ASCII file designed by the user.
+It has the following format:
+<pre>
+ TITLE TITLE
+ MATRIX n
+ .
+ n lines of n integers
+ .
+ DIVISOR d
+ TYPE S/P
+</pre>
+
+
+<dt>TITLE
+
+<dd>A one-line TITLE for the filter.
+If a TITLE was not specified on the command line, it can be specified here.
+This TITLE would be used to construct a TITLE for the resulting raster map
+layer. It should be a one-line description of the filter.
+
+<dt>MATRIX
+
+<dd>The matrix (n x n) follows on the next n lines. <em>n</em> must be
+an odd integer greater than or equal to 3.
+The matrix itself consists of n rows of n integers.
+The integers must be separated from each other by at least 1 blank.
+
+<dt>DIVISOR
+
+<dd>The filter divisor is <em>d</em>. If not specified, the default is 1.
+If the divisor is zero (0), then the divisor is dependent on the
+category values in the neighborhood
+(see HOW THE FILTER WORKS below).
+
+<dt>TYPE
+
+<dd>The filter type. <em>S</em> means sequential, while <em>P</em> mean parallel.
+If not specified, the default is S.
+
+
+<p>
+
+Sequential filtering happens in place. As the filter is applied to the
+raster map layer, the category values that were changed in neighboring
+cells affect the resulting category value of the current
+cell being filtered.
+
+
+<p>
+Parallel filtering happens in such a way that the original raster
+map layer category values are used to produce the new category value.
+
+
+<p>
+More than one filter may be specified in the filter file.
+The additional filter(s) are described just like the first.
+For example, the following describes two filters:
+</p>
+
+</dd>
+
+
+<h2>EXAMPLE FILTER FILE</h2>
+
+<pre>
+ TITLE 3x3 average, non-zero data only, followed by 5x5 average
+ MATRIX 3
+ 1 1 1
+ 1 1 1
+ 1 1 1
+ DIVISOR 0
+ TYPE P
+
+ MATRIX 5
+ 1 1 1 1 1
+ 1 1 1 1 1
+ 1 1 1 1 1
+ 1 1 1 1 1
+ 1 1 1 1 1
+ DIVISOR 25
+ TYPE P
+</pre>
+
+<h2>HOW THE FILTER WORKS</h2>
+
+The filter process produces a new category value for each cell
+in the input raster map layer by multiplying the category values of the
+cells in the n x n neighborhood around the center cell
+by the corresponding matrix value and adding them together.
+If a divisor is specified, the sum is divided by this divisor,
+rounding to the nearest integer.
+(If a zero divisor was specified, then
+the divisor is computed for each cell as the sum of the MATRIX
+values where the corresponding input cell is non-zero.)
+
+
+<p>
+
+If more than one filter step is specified, either because the
+repeat value was greater than one or because the filter file
+contained more than one matrix, these steps are performed
+sequentially. This means that first one filter is applied to
+the entire input raster map layer to produce an intermediate result;
+then the next filter is applied to the intermediate result to
+produce another intermediate result; and so on, until the
+final filter is applied. Then the output cell is written.
+
+<h2>NOTES</h2>
+
+If the resolution of the geographic region does not agree with the
+resolution of the raster map layer, unintended resampling of the original
+data may occur. The user should be sure that the geographic region
+is set properly.
+
+<h2>SEE ALSO</h2>
+
+<em><a href="g.region.html">g.region</a></em>,
+<em><a href="r.clump.html">r.clump</a></em>,
+<em><a href="r.neighbors.html">r.neighbors</a></em>
+
+<h2>AUTHOR</h2>
+
+Michael Shapiro,
+U.S.Army Construction Engineering Research Laboratory
+
+<p>
+<i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.mfilter.fp/description.html
===================================================================
--- grass/trunk/raster/r.mfilter.fp/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.mfilter.fp/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,157 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-
-<em>r.mfilter.fp</em> filters the raster <em>input</em> to produce the
-raster <em>output</em> according to the matrix <em>filter</em> designed
-by the user (see <em>FILTERS</em> below).
-The filter is applied <em>repeat</em> times (default <em>value</em> is 1).
-The <em>output</em> raster map layer can be given a <em>TITLE</em> if desired.
-(This TITLE should be put in quotes if it contains more than one word.)
-
-With <b>-z</b> flag the filter is applied only to null values in
-the input raster map layer. The non-null category values are not changed.
-Note that if there is more than one filter step, this rule is applied to the
-intermediate raster map layer -- only null category values which result from
-the first filter will be changed. In most cases this will NOT be the
-desired result. Hence -z should be used only with single step filters.
-<p>
-
-The <b>filter</b> parameter defines the name of an existing, user-created
-UNIX ASCII file whose contents is a matrix defining the way in which the
-<em>input</em> file will be filtered. The format of this file is described
-below, under FILTERS.
-<p>
-
-The <b>repeat</b> parameter defines the number of times the <em>filter</em>
-is to be applied to the <em>input</em> data.
-
-<h2>FILTERS</h2>
-
-The <em>filter</em> file is a normal UNIX ASCII file designed by the user.
-It has the following format:
-<pre>
- TITLE TITLE
- MATRIX n
- .
- n lines of n values
- .
- DIVISOR d
- TYPE S/P
-</pre>
-
-
-<dt>TITLE
-
-<dd>A one-line TITLE for the filter.
-If a TITLE was not specified on the command line, it can be specified here.
-This TITLE would be used to construct a TITLE for the resulting raster map
-layer. It should be a one-line description of the filter.
-
-<dt>MATRIX
-
-<dd>The matrix (n x n) follows on the next n lines. <em>n</em> must be
-an odd integer greater than or equal to 3.
-The matrix itself consists of n rows of n values.
-The values must be separated from each other by at least 1 blank.
-
-<dt>DIVISOR
-
-<dd>The filter divisor is <em>d</em>. If not specified, the default is 1.
-If the divisor is zero (0), then the divisor is dependent on the
-category values in the neighborhood
-(see HOW THE FILTER WORKS below).
-
-<dt>TYPE
-
-<dd>The filter type. <em>S</em> means sequential, while <em>P</em> mean parallel.
-If not specified, the default is S.
-
-
-<p>
-
-Sequential filtering happens in place. As the filter is applied to the
-raster map layer, the category values that were changed in neighboring
-cells affect the resulting category value of the current
-cell being filtered.
-
-
-<p>
-Parallel filtering happens in such a way that the original raster
-map layer category values are used to produce the new category value.
-
-
-<p>
-More than one filter may be specified in the filter file.
-The additional filter(s) are described just like the first.
-For example, the following describes two filters:
-</p>
-
-</dd>
-
-
-<h2>EXAMPLE FILTER FILE</h2>
-
-<pre>
- TITLE 3x3 average, non-null data only, followed by 5x5 average
- MATRIX 3
- 1 1 1
- 1 1 1
- 1 1 1
- DIVISOR 0
- TYPE P
-
- MATRIX 5
- 1 1 1 1 1
- 1 1 1 1 1
- 1 1 1 1 1
- 1 1 1 1 1
- 1 1 1 1 1
- DIVISOR 25
- TYPE P
-</pre>
-
-<h2>HOW THE FILTER WORKS</h2>
-
-The filter process produces a new category value for each cell
-in the input raster map layer by multiplying the category values of the
-cells in the n x n neighborhood around the center cell
-by the corresponding matrix value and adding them together.
-If a divisor is specified, the sum is divided by this divisor.
-(If a zero divisor was specified, then
-the divisor is computed for each cell as the sum of the MATRIX
-values where the corresponding input cell is non-null.)
-
-
-<p>
-
-If more than one filter step is specified, either because the
-repeat value was greater than one or because the filter file
-contained more than one matrix, these steps are performed
-sequentially. This means that first one filter is applied to
-the entire input raster map layer to produce an intermediate result;
-then the next filter is applied to the intermediate result to
-produce another intermediate result; and so on, until the
-final filter is applied. Then the output cell is written.
-
-<h2>NOTES</h2>
-
-If the resolution of the geographic region does not agree with the
-resolution of the raster map layer, unintended resampling of the original
-data may occur. The user should be sure that the geographic region
-is set properly.
-
-<h2>SEE ALSO</h2>
-
-<em><a href="g.region.html">g.region</a></em>,
-<em><a href="r.clump.html">r.clump</a></em>,
-<em><a href="r.neighbors.html">r.neighbors</a></em>
-<em><a href="r.mfilter.html">r.mfilter</a></em>
-
-<h2>AUTHOR</h2>
-
-Glynn Clements.
-Based upon r.mfilter, by Michael Shapiro,
-U.S.Army Construction Engineering Research Laboratory
-
-<p>
-<i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.mfilter.fp/r.mfilter.fp.html (from rev 32770, grass/trunk/raster/r.mfilter.fp/description.html)
===================================================================
--- grass/trunk/raster/r.mfilter.fp/r.mfilter.fp.html (rev 0)
+++ grass/trunk/raster/r.mfilter.fp/r.mfilter.fp.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,157 @@
+<h2>DESCRIPTION</h2>
+
+
+<em>r.mfilter.fp</em> filters the raster <em>input</em> to produce the
+raster <em>output</em> according to the matrix <em>filter</em> designed
+by the user (see <em>FILTERS</em> below).
+The filter is applied <em>repeat</em> times (default <em>value</em> is 1).
+The <em>output</em> raster map layer can be given a <em>TITLE</em> if desired.
+(This TITLE should be put in quotes if it contains more than one word.)
+
+With <b>-z</b> flag the filter is applied only to null values in
+the input raster map layer. The non-null category values are not changed.
+Note that if there is more than one filter step, this rule is applied to the
+intermediate raster map layer -- only null category values which result from
+the first filter will be changed. In most cases this will NOT be the
+desired result. Hence -z should be used only with single step filters.
+<p>
+
+The <b>filter</b> parameter defines the name of an existing, user-created
+UNIX ASCII file whose contents is a matrix defining the way in which the
+<em>input</em> file will be filtered. The format of this file is described
+below, under FILTERS.
+<p>
+
+The <b>repeat</b> parameter defines the number of times the <em>filter</em>
+is to be applied to the <em>input</em> data.
+
+<h2>FILTERS</h2>
+
+The <em>filter</em> file is a normal UNIX ASCII file designed by the user.
+It has the following format:
+<pre>
+ TITLE TITLE
+ MATRIX n
+ .
+ n lines of n values
+ .
+ DIVISOR d
+ TYPE S/P
+</pre>
+
+
+<dt>TITLE
+
+<dd>A one-line TITLE for the filter.
+If a TITLE was not specified on the command line, it can be specified here.
+This TITLE would be used to construct a TITLE for the resulting raster map
+layer. It should be a one-line description of the filter.
+
+<dt>MATRIX
+
+<dd>The matrix (n x n) follows on the next n lines. <em>n</em> must be
+an odd integer greater than or equal to 3.
+The matrix itself consists of n rows of n values.
+The values must be separated from each other by at least 1 blank.
+
+<dt>DIVISOR
+
+<dd>The filter divisor is <em>d</em>. If not specified, the default is 1.
+If the divisor is zero (0), then the divisor is dependent on the
+category values in the neighborhood
+(see HOW THE FILTER WORKS below).
+
+<dt>TYPE
+
+<dd>The filter type. <em>S</em> means sequential, while <em>P</em> mean parallel.
+If not specified, the default is S.
+
+
+<p>
+
+Sequential filtering happens in place. As the filter is applied to the
+raster map layer, the category values that were changed in neighboring
+cells affect the resulting category value of the current
+cell being filtered.
+
+
+<p>
+Parallel filtering happens in such a way that the original raster
+map layer category values are used to produce the new category value.
+
+
+<p>
+More than one filter may be specified in the filter file.
+The additional filter(s) are described just like the first.
+For example, the following describes two filters:
+</p>
+
+</dd>
+
+
+<h2>EXAMPLE FILTER FILE</h2>
+
+<pre>
+ TITLE 3x3 average, non-null data only, followed by 5x5 average
+ MATRIX 3
+ 1 1 1
+ 1 1 1
+ 1 1 1
+ DIVISOR 0
+ TYPE P
+
+ MATRIX 5
+ 1 1 1 1 1
+ 1 1 1 1 1
+ 1 1 1 1 1
+ 1 1 1 1 1
+ 1 1 1 1 1
+ DIVISOR 25
+ TYPE P
+</pre>
+
+<h2>HOW THE FILTER WORKS</h2>
+
+The filter process produces a new category value for each cell
+in the input raster map layer by multiplying the category values of the
+cells in the n x n neighborhood around the center cell
+by the corresponding matrix value and adding them together.
+If a divisor is specified, the sum is divided by this divisor.
+(If a zero divisor was specified, then
+the divisor is computed for each cell as the sum of the MATRIX
+values where the corresponding input cell is non-null.)
+
+
+<p>
+
+If more than one filter step is specified, either because the
+repeat value was greater than one or because the filter file
+contained more than one matrix, these steps are performed
+sequentially. This means that first one filter is applied to
+the entire input raster map layer to produce an intermediate result;
+then the next filter is applied to the intermediate result to
+produce another intermediate result; and so on, until the
+final filter is applied. Then the output cell is written.
+
+<h2>NOTES</h2>
+
+If the resolution of the geographic region does not agree with the
+resolution of the raster map layer, unintended resampling of the original
+data may occur. The user should be sure that the geographic region
+is set properly.
+
+<h2>SEE ALSO</h2>
+
+<em><a href="g.region.html">g.region</a></em>,
+<em><a href="r.clump.html">r.clump</a></em>,
+<em><a href="r.neighbors.html">r.neighbors</a></em>
+<em><a href="r.mfilter.html">r.mfilter</a></em>
+
+<h2>AUTHOR</h2>
+
+Glynn Clements.
+Based upon r.mfilter, by Michael Shapiro,
+U.S.Army Construction Engineering Research Laboratory
+
+<p>
+<i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.mode/description.html
===================================================================
--- grass/trunk/raster/r.mode/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.mode/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,67 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>r.mode</em> calculates the most frequently occurring value (i. e., mode)
-of data contained in a <em>cover</em> raster map layer for areas assigned
-the same category value in the user-specified <em>base</em> raster map
-layer. These modes are stored in the new <em>output</em> map layer.
-
-<p>
-The <em>output</em> map is actually a <em>reclass</em> of the <em>base</em>
-map.
-
-<p>
-The <b>base</b> parameter defines an existing raster map layer in the user's
-current mapset search path. For each group of cells assigned the same
-category value in the <em>base</em> map, the mode of the values assigned
-these cells in the <em>cover</em> map will be computed.
-
-<p>
-The <b>cover</b> parameter defines an existing raster map layer containing
-the values to be used to compute the mode within each category of the
-<em>base</em> map.
-
-<h2>NOTES</h2>
-
-The user should use the results of <em>r.mode</em> with care.
-Since this utility assigns a value to each
-cell which is based on global information (i.e., information at spatial
-locations other than just the location of the cell itself), the resultant
-map layer is only valid if the geographic region and mask settings are
-the same as they were at the time that the result map was created.
-
-<p>
-Results are affected by the current region settings and mask.
-
-<h2>EXAMPLE</h2>
-
-Mode of K-factor (erosion) for Spearfish fields:
-
-<div class="code"><pre>
-g.region rast=fields -p
-r.mode base=fields cover=soils.Kfactor output=K.by.farm.mode
-r.univar K.by.farm.mode
-</pre></div>
-
-<h2>SEE ALSO</h2>
-
-<em><a href="g.region.html">g.region</a></em>,
-<em><a href="r.average.html">r.average</a></em>,
-<em><a href="r.category.html">r.category</a></em>,
-<em><a href="r.clump.html">r.clump</a></em>,
-<em><a href="r.describe.html">r.describe</a></em>,
-<em><a href="r.mapcalc.html">r.mapcalc</a></em>,
-<em><a href="r.median.html">r.median</a></em>,
-<em><a href="r.mfilter.html">r.mfilter</a></em>,
-<em><a href="r.neighbors.html">r.neighbors</a></em>,
-<em><a href="r.reclass.html">r.reclass</a></em>,
-<em><a href="r.stats.html">r.stats</a></em>,
-<em><a href="r.statistics.html">r.statistics</a></em>,
-<em><a href="r.univar.html">r.univar</a></em>
-
-
-<h2>AUTHOR</h2>
-
-Michael Shapiro,
-U.S.Army Construction Engineering Research Laboratory
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.mode/r.mode.html (from rev 32770, grass/trunk/raster/r.mode/description.html)
===================================================================
--- grass/trunk/raster/r.mode/r.mode.html (rev 0)
+++ grass/trunk/raster/r.mode/r.mode.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,67 @@
+<h2>DESCRIPTION</h2>
+
+<em>r.mode</em> calculates the most frequently occurring value (i. e., mode)
+of data contained in a <em>cover</em> raster map layer for areas assigned
+the same category value in the user-specified <em>base</em> raster map
+layer. These modes are stored in the new <em>output</em> map layer.
+
+<p>
+The <em>output</em> map is actually a <em>reclass</em> of the <em>base</em>
+map.
+
+<p>
+The <b>base</b> parameter defines an existing raster map layer in the user's
+current mapset search path. For each group of cells assigned the same
+category value in the <em>base</em> map, the mode of the values assigned
+these cells in the <em>cover</em> map will be computed.
+
+<p>
+The <b>cover</b> parameter defines an existing raster map layer containing
+the values to be used to compute the mode within each category of the
+<em>base</em> map.
+
+<h2>NOTES</h2>
+
+The user should use the results of <em>r.mode</em> with care.
+Since this utility assigns a value to each
+cell which is based on global information (i.e., information at spatial
+locations other than just the location of the cell itself), the resultant
+map layer is only valid if the geographic region and mask settings are
+the same as they were at the time that the result map was created.
+
+<p>
+Results are affected by the current region settings and mask.
+
+<h2>EXAMPLE</h2>
+
+Mode of K-factor (erosion) for Spearfish fields:
+
+<div class="code"><pre>
+g.region rast=fields -p
+r.mode base=fields cover=soils.Kfactor output=K.by.farm.mode
+r.univar K.by.farm.mode
+</pre></div>
+
+<h2>SEE ALSO</h2>
+
+<em><a href="g.region.html">g.region</a></em>,
+<em><a href="r.average.html">r.average</a></em>,
+<em><a href="r.category.html">r.category</a></em>,
+<em><a href="r.clump.html">r.clump</a></em>,
+<em><a href="r.describe.html">r.describe</a></em>,
+<em><a href="r.mapcalc.html">r.mapcalc</a></em>,
+<em><a href="r.median.html">r.median</a></em>,
+<em><a href="r.mfilter.html">r.mfilter</a></em>,
+<em><a href="r.neighbors.html">r.neighbors</a></em>,
+<em><a href="r.reclass.html">r.reclass</a></em>,
+<em><a href="r.stats.html">r.stats</a></em>,
+<em><a href="r.statistics.html">r.statistics</a></em>,
+<em><a href="r.univar.html">r.univar</a></em>
+
+
+<h2>AUTHOR</h2>
+
+Michael Shapiro,
+U.S.Army Construction Engineering Research Laboratory
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.neighbors/description.html
===================================================================
--- grass/trunk/raster/r.neighbors/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.neighbors/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,291 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em><b>r.neighbors</b></em> looks at each cell in a raster input
-file, and examines the values assigned to the
-cells in some user-defined "neighborhood" around it. It
-outputs a new raster map layer in which each cell is
-assigned a value that is some (user-specified)
-function of the values in that cell's neighborhood. For
-example, each cell in the output layer might be assigned a
-value equal to the average of the values
-appearing in its 3 x 3 cell "neighborhood" in the input
-layer.
-
-
-<p>
-
-The program will be run non-interactively if the user
-specifies program arguments (see OPTIONS) on the command
-line. Alternately, the user can simply type
-<em><b>r.neighbors</b></em> on the command line, without program
-arguments. In this case, the user will be prompted for
-flag settings and parameter values.
-
-<h3>OPTIONS</h3>
-
-The user must specify the names of the raster map layers to
-be used for <b>input</b> and <b>output</b>, the
-<b>method</b> used to analyze neighborhood
-values (i.e., the neighborhood function or operation to be
-performed), and the <b>size</b> of the neighborhood.
-Optionally, the user can also specify the <b>TITLE</b> to
-be assigned to the raster map layer <b>output</b>, elect
-to not align the resolution of the output with that of the
-input (the <b>-a</b> option), run <em><b>r.neighbors</b></em> with
-a custom matrix weights with the <em>weight</em> option, and
-elect to run <em><b>r.neighbors</b></em> quietly (the <b>-q</b> option).
-These options are described further below.
-
-
-<p>
-
-<em>Neighborhood Operation Methods:</em>
-The <b>neighborhood</b> operators determine what new
-value a center cell in a neighborhood will have after examining
-values inside its neighboring cells.
-Each cell in a raster map layer becomes the center cell of a neighborhood
-as the neighborhood window moves from cell to cell throughout the map layer.
-<em><b>r.neighbors</b></em> can perform the following operations:
-
-<p>
-<dl>
-
-<dt><b>average</b>
-
-<dd>The average value within the neighborhood.
-In the following example, the result would be:
-
-<br>
-
-(7*4 + 6 + 5 + 4*3)/9 = 5.66
-
-<br>
-
-The result is rounded to the nearest integer (in this case 6).
-
-<dt><b>median</b>
-
-<dd>The value found half-way through a list of the
-neighborhood's values,
-when these are ranged in numerical order.
-
-<dt><b>mode</b>
-
-<dd>The most frequently occurring value in the neighborhood.
-
-<dt><b>minimum</b>
-
-<dd>The minimum value within the neighborhood.
-
-<dt><b>maximum</b>
-
-<dd>The maximum value within the neighborhood.
-<pre>
- Raw Data Operation New Data
- ---------------- ----------------
- | 7 | 7 | 5 | | | | |
- |----|----|----| average |----|----|----|
- | 4 | 7 | 4 |--------->| | 6 | |
- |----|----|----| |----|----|----|
- | 7 | 6 | 4 | | | | |
- |----|----|----| |----|----|----|
-</pre>
-
-<dt><b>stddev</b>
-
-<dd>The statistical standard deviation of values
-within the neighborhood (rounded to the nearest integer).
-
-<dt><b>sum</b>
-
-<dd>The sum of values within the neighborhood.
-
-<dt><b>variance</b>
-
-<dd>The statistical variance of values
-within the neighborhood (rounded to the nearest integer).
-
-<dt><b>diversity</b>
-
-<dd>The number of different values within the neighborhood.
-In the above example, the diversity is 4.
-
-<dt><b>interspersion</b>
-
-<dd>The percentage of cells containing values which differ from the values
-assigned to the center cell in the neighborhood, plus 1.
-In the above example, the interspersion is:
-
-<br>
-
-5/8 * 100 + 1 = 63.5
-
-<br>
-
-The result is rounded to the nearest integer (in this case 64).
-
-</dl>
-<p>
-<br>
-
-<em>Neighborhood Size:</em>
-<dd>The neighborhood <b>size</b> specifies which cells surrounding any given
-cell fall into the neighborhood for that cell.
-The <b>size</b> must be an odd integer.
-For example,
-<pre>
- _ _ _
- |_|_|_|
- 3 x 3 neighborhood ---> |_|_|_|
- |_|_|_|
-
-</pre>
-</dd>
-<p>
-
-<em>Matrix weights:</em>
-<dd>A custom matrix can be used if none of the neighborhood operation
-methods are desirable by using the <b>weight</b>. This option must
-be used in conjunction with the <b>size</b> option to specify the
-matrix size. The weights desired are to be entered into a text file.
-For example, to calculate the focal mean with a matrix <b>size</b> of
-3,
-<pre>
-r.neigbors in=input.map out=output.map size=3 weight=weights.txt
-</pre>
-
-The contents of the weight.txt file:
-<pre>
-3 3 3
-1 4 8
-9 5 3
-</pre>
-
-This corresponds to the following 3x3 matrix:
-<pre>
- -------
- |3|3|3|
- -------
- |1|4|8|
- -------
- |9|5|3|
- -------
-</pre>
-
-<p>
-
-<h3>FLAGS</h3>
-
-<dt><b>-a</b>
-
-<dd>If specified, <em><b>r.neighbors</b></em> will not align the output
-raster map layer with that of the input raster map layer.
-The <em><b>r.neighbors</b></em> program works in the current geographic region.
-It is recommended, but not required, that the resolution
-of the geographic region be the same as that of the raster map layer.
-By default, if unspecified,
-<em><b>r.neighbors</b></em> will align these geographic region settings.
-<p>
-
-<dt><b>-c</b>
-<dd>
-This flag will use a circular neighborhood for the moving analysis window,
-centered on the current cell.
-
-<p>
-The exact masks for the first few neighborhood sizes are as follows:
-<div class="code"><pre>
-3x3 . X . 5x5 . . X . . 7x7 . . . X . . .
- X O X . X X X . . X X X X X .
- . X . X X O X X . X X X X X .
- . X X X . X X X O X X X
- . . X . . . X X X X X .
- . X X X X X .
- . . . X . . .
-
-9x9 . . . . X . . . . 11x11 . . . . . X . . . . .
- . . X X X X X . . . . X X X X X X X . .
- . X X X X X X X . . X X X X X X X X X .
- . X X X X X X X . . X X X X X X X X X .
- X X X X O X X X X . X X X X X X X X X .
- . X X X X X X X . X X X X X O X X X X X
- . X X X X X X X . . X X X X X X X X X .
- . . X X X X X . . . X X X X X X X X X .
- . . . . X . . . . . X X X X X X X X X .
- . . X X X X X X X . .
- . . . . . X . . . . .
-</pre></div>
-
-
-
-<p>
-
-<dt><b>-q</b>
-
-<dd>If specified, <em><b>r.neighbors</b></em> will run relatively quietly
-(i.e., without printing to standard output notes on the program's progress).
-If unspecified, the program will print messages to standard output by default.
-</dd>
-
-
-<h2>NOTES</h2>
-
-The <em><b>r.neighbors</b></em> program works in the current geographic region
-with the current mask, if any. It is recommended, but not required,
-that the resolution of the geographic region be the same as that
-of the raster map layer. By default, <em><b>r.neighbors</b></em> will align
-these geographic region settings. However, the user can elect to keep
-original input and output resolutions which are not aligned by specifying
-this (e.g., using the <b>-a</b> option).
-
-<p>
-The <b>-c</b> flag and the <b>weights</b> parameter are mutually exclusive.
-Any use of the two together will produce an error. Differently-shaped neighborhood
-analysis windows may be achieved by using the <b>weight=</b> parameter to specify
-a weights file where all values are equal (for <b>method</b>=sum, the sum of the
-weights should be 1). The user can also vary the weights at the edge of the
-neighborhood according to the proportion of the cell that lies inside the neighborhood circle,
-effectively anti-aliasing the analysis mask.
-<p>
-
-For aggregates where a weighted calculation isn't meaningful
-(specifically: minimum, maximum, diversity and interspersion), the
-weights are used to create a binary mask, where zero causes the cell
-to be ignored and any non-zero value causes the cell to be used.
-<p>
-
-<em><b>r.neighbors</b></em> copies the GRASS <em>color</em> files associated with
-the input raster map layer for those output map layers that are based
-on the neighborhood average, median, mode, minimum, and maximum.
-Because standard deviation, variance, diversity, and interspersion are indices,
-rather than direct correspondents to input values,
-no <em>color</em> files are copied for these map layers.
-(The user should note that although the <em>color</em> file is copied
-for <em>average</em> neighborhood function output,
-whether or not the color file makes sense for the output
-will be dependent on the input data values.)
-
-<h2>SEE ALSO</h2>
-
-<em><a href="g.region.html">g.region</a></em><br>
-<em><a href="r.clump.html">r.clump</a></em><br>
-<em><a href="r.mapcalc.html">r.mapcalc</a></em><br>
-<em><a href="r.mfilter.html">r.mfilter</a></em><br>
-<em><a href="r.statistics.html">r.statistics</a></em><br>
-<em><a href="r.support.html">r.support</a></em>
-
-<h2>AUTHOR</h2>
-
-Michael Shapiro,
-U.S.Army Construction Engineering Research Laboratory
-
-<p><i>Last changed: $Date$</i>
-
-
-
-
-
-
-
-
-
Copied: grass/trunk/raster/r.neighbors/r.neighbors.html (from rev 32770, grass/trunk/raster/r.neighbors/description.html)
===================================================================
--- grass/trunk/raster/r.neighbors/r.neighbors.html (rev 0)
+++ grass/trunk/raster/r.neighbors/r.neighbors.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,291 @@
+<h2>DESCRIPTION</h2>
+
+<em><b>r.neighbors</b></em> looks at each cell in a raster input
+file, and examines the values assigned to the
+cells in some user-defined "neighborhood" around it. It
+outputs a new raster map layer in which each cell is
+assigned a value that is some (user-specified)
+function of the values in that cell's neighborhood. For
+example, each cell in the output layer might be assigned a
+value equal to the average of the values
+appearing in its 3 x 3 cell "neighborhood" in the input
+layer.
+
+
+<p>
+
+The program will be run non-interactively if the user
+specifies program arguments (see OPTIONS) on the command
+line. Alternately, the user can simply type
+<em><b>r.neighbors</b></em> on the command line, without program
+arguments. In this case, the user will be prompted for
+flag settings and parameter values.
+
+<h3>OPTIONS</h3>
+
+The user must specify the names of the raster map layers to
+be used for <b>input</b> and <b>output</b>, the
+<b>method</b> used to analyze neighborhood
+values (i.e., the neighborhood function or operation to be
+performed), and the <b>size</b> of the neighborhood.
+Optionally, the user can also specify the <b>TITLE</b> to
+be assigned to the raster map layer <b>output</b>, elect
+to not align the resolution of the output with that of the
+input (the <b>-a</b> option), run <em><b>r.neighbors</b></em> with
+a custom matrix weights with the <em>weight</em> option, and
+elect to run <em><b>r.neighbors</b></em> quietly (the <b>-q</b> option).
+These options are described further below.
+
+
+<p>
+
+<em>Neighborhood Operation Methods:</em>
+The <b>neighborhood</b> operators determine what new
+value a center cell in a neighborhood will have after examining
+values inside its neighboring cells.
+Each cell in a raster map layer becomes the center cell of a neighborhood
+as the neighborhood window moves from cell to cell throughout the map layer.
+<em><b>r.neighbors</b></em> can perform the following operations:
+
+<p>
+<dl>
+
+<dt><b>average</b>
+
+<dd>The average value within the neighborhood.
+In the following example, the result would be:
+
+<br>
+
+(7*4 + 6 + 5 + 4*3)/9 = 5.66
+
+<br>
+
+The result is rounded to the nearest integer (in this case 6).
+
+<dt><b>median</b>
+
+<dd>The value found half-way through a list of the
+neighborhood's values,
+when these are ranged in numerical order.
+
+<dt><b>mode</b>
+
+<dd>The most frequently occurring value in the neighborhood.
+
+<dt><b>minimum</b>
+
+<dd>The minimum value within the neighborhood.
+
+<dt><b>maximum</b>
+
+<dd>The maximum value within the neighborhood.
+<pre>
+ Raw Data Operation New Data
+ ---------------- ----------------
+ | 7 | 7 | 5 | | | | |
+ |----|----|----| average |----|----|----|
+ | 4 | 7 | 4 |--------->| | 6 | |
+ |----|----|----| |----|----|----|
+ | 7 | 6 | 4 | | | | |
+ |----|----|----| |----|----|----|
+</pre>
+
+<dt><b>stddev</b>
+
+<dd>The statistical standard deviation of values
+within the neighborhood (rounded to the nearest integer).
+
+<dt><b>sum</b>
+
+<dd>The sum of values within the neighborhood.
+
+<dt><b>variance</b>
+
+<dd>The statistical variance of values
+within the neighborhood (rounded to the nearest integer).
+
+<dt><b>diversity</b>
+
+<dd>The number of different values within the neighborhood.
+In the above example, the diversity is 4.
+
+<dt><b>interspersion</b>
+
+<dd>The percentage of cells containing values which differ from the values
+assigned to the center cell in the neighborhood, plus 1.
+In the above example, the interspersion is:
+
+<br>
+
+5/8 * 100 + 1 = 63.5
+
+<br>
+
+The result is rounded to the nearest integer (in this case 64).
+
+</dl>
+<p>
+<br>
+
+<em>Neighborhood Size:</em>
+<dd>The neighborhood <b>size</b> specifies which cells surrounding any given
+cell fall into the neighborhood for that cell.
+The <b>size</b> must be an odd integer.
+For example,
+<pre>
+ _ _ _
+ |_|_|_|
+ 3 x 3 neighborhood ---> |_|_|_|
+ |_|_|_|
+
+</pre>
+</dd>
+<p>
+
+<em>Matrix weights:</em>
+<dd>A custom matrix can be used if none of the neighborhood operation
+methods are desirable by using the <b>weight</b>. This option must
+be used in conjunction with the <b>size</b> option to specify the
+matrix size. The weights desired are to be entered into a text file.
+For example, to calculate the focal mean with a matrix <b>size</b> of
+3,
+<pre>
+r.neigbors in=input.map out=output.map size=3 weight=weights.txt
+</pre>
+
+The contents of the weight.txt file:
+<pre>
+3 3 3
+1 4 8
+9 5 3
+</pre>
+
+This corresponds to the following 3x3 matrix:
+<pre>
+ -------
+ |3|3|3|
+ -------
+ |1|4|8|
+ -------
+ |9|5|3|
+ -------
+</pre>
+
+<p>
+
+<h3>FLAGS</h3>
+
+<dt><b>-a</b>
+
+<dd>If specified, <em><b>r.neighbors</b></em> will not align the output
+raster map layer with that of the input raster map layer.
+The <em><b>r.neighbors</b></em> program works in the current geographic region.
+It is recommended, but not required, that the resolution
+of the geographic region be the same as that of the raster map layer.
+By default, if unspecified,
+<em><b>r.neighbors</b></em> will align these geographic region settings.
+<p>
+
+<dt><b>-c</b>
+<dd>
+This flag will use a circular neighborhood for the moving analysis window,
+centered on the current cell.
+
+<p>
+The exact masks for the first few neighborhood sizes are as follows:
+<div class="code"><pre>
+3x3 . X . 5x5 . . X . . 7x7 . . . X . . .
+ X O X . X X X . . X X X X X .
+ . X . X X O X X . X X X X X .
+ . X X X . X X X O X X X
+ . . X . . . X X X X X .
+ . X X X X X .
+ . . . X . . .
+
+9x9 . . . . X . . . . 11x11 . . . . . X . . . . .
+ . . X X X X X . . . . X X X X X X X . .
+ . X X X X X X X . . X X X X X X X X X .
+ . X X X X X X X . . X X X X X X X X X .
+ X X X X O X X X X . X X X X X X X X X .
+ . X X X X X X X . X X X X X O X X X X X
+ . X X X X X X X . . X X X X X X X X X .
+ . . X X X X X . . . X X X X X X X X X .
+ . . . . X . . . . . X X X X X X X X X .
+ . . X X X X X X X . .
+ . . . . . X . . . . .
+</pre></div>
+
+
+
+<p>
+
+<dt><b>-q</b>
+
+<dd>If specified, <em><b>r.neighbors</b></em> will run relatively quietly
+(i.e., without printing to standard output notes on the program's progress).
+If unspecified, the program will print messages to standard output by default.
+</dd>
+
+
+<h2>NOTES</h2>
+
+The <em><b>r.neighbors</b></em> program works in the current geographic region
+with the current mask, if any. It is recommended, but not required,
+that the resolution of the geographic region be the same as that
+of the raster map layer. By default, <em><b>r.neighbors</b></em> will align
+these geographic region settings. However, the user can elect to keep
+original input and output resolutions which are not aligned by specifying
+this (e.g., using the <b>-a</b> option).
+
+<p>
+The <b>-c</b> flag and the <b>weights</b> parameter are mutually exclusive.
+Any use of the two together will produce an error. Differently-shaped neighborhood
+analysis windows may be achieved by using the <b>weight=</b> parameter to specify
+a weights file where all values are equal (for <b>method</b>=sum, the sum of the
+weights should be 1). The user can also vary the weights at the edge of the
+neighborhood according to the proportion of the cell that lies inside the neighborhood circle,
+effectively anti-aliasing the analysis mask.
+<p>
+
+For aggregates where a weighted calculation isn't meaningful
+(specifically: minimum, maximum, diversity and interspersion), the
+weights are used to create a binary mask, where zero causes the cell
+to be ignored and any non-zero value causes the cell to be used.
+<p>
+
+<em><b>r.neighbors</b></em> copies the GRASS <em>color</em> files associated with
+the input raster map layer for those output map layers that are based
+on the neighborhood average, median, mode, minimum, and maximum.
+Because standard deviation, variance, diversity, and interspersion are indices,
+rather than direct correspondents to input values,
+no <em>color</em> files are copied for these map layers.
+(The user should note that although the <em>color</em> file is copied
+for <em>average</em> neighborhood function output,
+whether or not the color file makes sense for the output
+will be dependent on the input data values.)
+
+<h2>SEE ALSO</h2>
+
+<em><a href="g.region.html">g.region</a></em><br>
+<em><a href="r.clump.html">r.clump</a></em><br>
+<em><a href="r.mapcalc.html">r.mapcalc</a></em><br>
+<em><a href="r.mfilter.html">r.mfilter</a></em><br>
+<em><a href="r.statistics.html">r.statistics</a></em><br>
+<em><a href="r.support.html">r.support</a></em>
+
+<h2>AUTHOR</h2>
+
+Michael Shapiro,
+U.S.Army Construction Engineering Research Laboratory
+
+<p><i>Last changed: $Date$</i>
+
+
+
+
+
+
+
+
+
Deleted: grass/trunk/raster/r.null/description.html
===================================================================
--- grass/trunk/raster/r.null/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.null/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,63 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-The function of <em>r.null</em> is to explicitly create the NULL-value
-bitmap file. The intended usage is to fix "old" maps that don't have a
-NULL-value bitmap file (i.e. to indicate if zero is valid value or is to be
-converted to NULL). The module does not work with reclassified maps.
-
-<p>
-
-The design is flexible. Ranges of values can be set to NULL and/or the NULL
-value can be eliminated and replace with a specified value.
-<p>
-
-The <b>setnull</b> parameter is used to specify values in the ranges to
-be set to NULL. A range is either a single value (e.g., 5.3), or a pair of
-values (e.g., 4.76-34.56). Existing NULL-values are left NULL, unless the
-null argument is requested.
-<p>
-
-The <b>null</b> parameter eliminates the NULL value and replaces it with
-value. This argument is applied only to existing NULL values, and not to the
-NULLs created by the setnull argument.
-
-<h2>EXAMPLES</h2>
-Set specific values of a classified map to NULL:<br>
-<div class="code"><pre>
-r.null map=landcover.30m setnull=21,22
-</pre></div>
-
-Set NULL-values of a map to a specific value:<br>
-<div class="code"><pre>
-r.null map=fields null=99
-</pre></div>
-
-
-<h2>NOTES</h2>
-
-Note that value is restricted to integer if the map is an integer map.
-<p>
-<em>r.null</em> and reclassified maps:<br>
-The problem is, if r.null was run on the reclass raster it would alter the
-original and any other reclass rasters of the original. Therefore r.null
-doesn't allow to recode reclassified maps (products of r.reclass).
-<br>
-So, the way to recode such a map is: The user makes a raster out of the
-reclass that isn't a reclass by copying it:<br>
-
-<div class="code"><pre>
-r.mapcalc newmap = reclass
-</pre></div>
-
-
-<h2>SEE ALSO</h2>
-
-<em><a href="r.support.html">r.support</a></em>
-and
-<em><a href="r.quant.html">r.quant</a></em>
-
-<h2>AUTHOR</h2>
-
-U.S.Army Construction Engineering Research Laboratory
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.null/r.null.html (from rev 32770, grass/trunk/raster/r.null/description.html)
===================================================================
--- grass/trunk/raster/r.null/r.null.html (rev 0)
+++ grass/trunk/raster/r.null/r.null.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,63 @@
+<h2>DESCRIPTION</h2>
+
+The function of <em>r.null</em> is to explicitly create the NULL-value
+bitmap file. The intended usage is to fix "old" maps that don't have a
+NULL-value bitmap file (i.e. to indicate if zero is valid value or is to be
+converted to NULL). The module does not work with reclassified maps.
+
+<p>
+
+The design is flexible. Ranges of values can be set to NULL and/or the NULL
+value can be eliminated and replace with a specified value.
+<p>
+
+The <b>setnull</b> parameter is used to specify values in the ranges to
+be set to NULL. A range is either a single value (e.g., 5.3), or a pair of
+values (e.g., 4.76-34.56). Existing NULL-values are left NULL, unless the
+null argument is requested.
+<p>
+
+The <b>null</b> parameter eliminates the NULL value and replaces it with
+value. This argument is applied only to existing NULL values, and not to the
+NULLs created by the setnull argument.
+
+<h2>EXAMPLES</h2>
+Set specific values of a classified map to NULL:<br>
+<div class="code"><pre>
+r.null map=landcover.30m setnull=21,22
+</pre></div>
+
+Set NULL-values of a map to a specific value:<br>
+<div class="code"><pre>
+r.null map=fields null=99
+</pre></div>
+
+
+<h2>NOTES</h2>
+
+Note that value is restricted to integer if the map is an integer map.
+<p>
+<em>r.null</em> and reclassified maps:<br>
+The problem is, if r.null was run on the reclass raster it would alter the
+original and any other reclass rasters of the original. Therefore r.null
+doesn't allow to recode reclassified maps (products of r.reclass).
+<br>
+So, the way to recode such a map is: The user makes a raster out of the
+reclass that isn't a reclass by copying it:<br>
+
+<div class="code"><pre>
+r.mapcalc newmap = reclass
+</pre></div>
+
+
+<h2>SEE ALSO</h2>
+
+<em><a href="r.support.html">r.support</a></em>
+and
+<em><a href="r.quant.html">r.quant</a></em>
+
+<h2>AUTHOR</h2>
+
+U.S.Army Construction Engineering Research Laboratory
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.out.arc/description.html
===================================================================
--- grass/trunk/raster/r.out.arc/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.out.arc/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,59 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-
-<em>r.out.arc</em> converts a user-specified raster map layer
-(<b>input=</b><em>name</em>) into an ESRI ARC-GRID ascii file
-(<b>output=</b><em>name</em>) suitable for export to other computer systems.
-The dp=<em>value</em> option (where <em>value</em> is a number of the user's
-choice) can be used to request that numbers after decimal points are
-limited. However, to use this, the user should know the maximum number of
-digits that will occur in the output file. The user can find the maximum
-number of digits occurring in the output file by running <em>r.out.arc</em>
-without the <b>dp=</b><em>value</em> option.
-
-
-<p>
-
-The GRASS program <em><a href="r.in.arc.html">r.in.arc</a></em> can be used
-to perform the reverse function, converting an ESRI ARC-GRID ascii file in
-suitable format to GRASS raster map format. The order of cell values in
-file is from lower left to upper right (reverse to GRASS).
-
-<h2>NOTES</h2>
-
-The output from <em>r.out.arc</em> may also be placed into a file
-by using the UNIX redirection mechanism; e.g.:
-
-<div class="code"><pre>
-r.out.arc input=soils output=- > out.grd
-</pre></div>
-
-The output file <em>out.grd</em> can then be copied
-onto a CDROM or floppy disk for export purposes.
-
-<p><br>
-An Arc ASCII grid can be loaded into ArcGIS 8.3 though ArcToolbox.<br>
-Use the "Import to Raster" -> "ASCII to Grid" tool to create a binary grid
-which can be selected using ArcCatalog. The spatial analyst extension may
-need to be installed and activated within Arc.
-<p>
-In ArcGIS 9.0 the import tool can be found at:<br>
-ArcMap -> Toolbox -> Conversion Tools -> To Raster -> ASCII to Raster
-<p>
-A GeoTIFF created with <em><a href="r.out.gdal.html">r.out.gdal</a></em> is
-sometimes a better solution for transferring raster maps to other GIS software.
-<p>
-<h2>SEE ALSO</h2>
-
-<em><a href="r.in.arc.html">r.in.arc</a></em><br>
-<em><a href="r.out.gdal.html">r.out.gdal</a></em><br>
-
-
-<h2>AUTHOR</h2>
-
-Markus Neteler, University of Hannover, Germany, <br>
-based on r.out.ascii written by <br>
-Michael Shapiro,
-U.S.Army Construction Engineering Research Laboratory
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.out.arc/r.out.arc.html (from rev 32770, grass/trunk/raster/r.out.arc/description.html)
===================================================================
--- grass/trunk/raster/r.out.arc/r.out.arc.html (rev 0)
+++ grass/trunk/raster/r.out.arc/r.out.arc.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,59 @@
+<h2>DESCRIPTION</h2>
+
+
+<em>r.out.arc</em> converts a user-specified raster map layer
+(<b>input=</b><em>name</em>) into an ESRI ARC-GRID ascii file
+(<b>output=</b><em>name</em>) suitable for export to other computer systems.
+The dp=<em>value</em> option (where <em>value</em> is a number of the user's
+choice) can be used to request that numbers after decimal points are
+limited. However, to use this, the user should know the maximum number of
+digits that will occur in the output file. The user can find the maximum
+number of digits occurring in the output file by running <em>r.out.arc</em>
+without the <b>dp=</b><em>value</em> option.
+
+
+<p>
+
+The GRASS program <em><a href="r.in.arc.html">r.in.arc</a></em> can be used
+to perform the reverse function, converting an ESRI ARC-GRID ascii file in
+suitable format to GRASS raster map format. The order of cell values in
+file is from lower left to upper right (reverse to GRASS).
+
+<h2>NOTES</h2>
+
+The output from <em>r.out.arc</em> may also be placed into a file
+by using the UNIX redirection mechanism; e.g.:
+
+<div class="code"><pre>
+r.out.arc input=soils output=- > out.grd
+</pre></div>
+
+The output file <em>out.grd</em> can then be copied
+onto a CDROM or floppy disk for export purposes.
+
+<p><br>
+An Arc ASCII grid can be loaded into ArcGIS 8.3 though ArcToolbox.<br>
+Use the "Import to Raster" -> "ASCII to Grid" tool to create a binary grid
+which can be selected using ArcCatalog. The spatial analyst extension may
+need to be installed and activated within Arc.
+<p>
+In ArcGIS 9.0 the import tool can be found at:<br>
+ArcMap -> Toolbox -> Conversion Tools -> To Raster -> ASCII to Raster
+<p>
+A GeoTIFF created with <em><a href="r.out.gdal.html">r.out.gdal</a></em> is
+sometimes a better solution for transferring raster maps to other GIS software.
+<p>
+<h2>SEE ALSO</h2>
+
+<em><a href="r.in.arc.html">r.in.arc</a></em><br>
+<em><a href="r.out.gdal.html">r.out.gdal</a></em><br>
+
+
+<h2>AUTHOR</h2>
+
+Markus Neteler, University of Hannover, Germany, <br>
+based on r.out.ascii written by <br>
+Michael Shapiro,
+U.S.Army Construction Engineering Research Laboratory
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.out.ascii/description.html
===================================================================
--- grass/trunk/raster/r.out.ascii/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.out.ascii/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,63 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>r.out.ascii</em> converts a user-specified raster map layer
-(<b>input=</b><em>name</em>) into an ASCII grid in a text file
-(<b>output=</b><em>name</em>) suitable for export to
-other computer systems.
-
-<p>
-
-The GRASS program <em><a href="r.in.ascii.html">r.in.ascii</a></em> can be
-used to perform the reverse function, converting an ASCII file in suitable
-format to GRASS raster map format.
-<p>
-<!--With <b>-s</b> flag SURFER .grd ASCII GRID instead of GRASS ASCII GRID is
-written (with reverted row order, different header).
-<p>
-With <b>-m</b> flag MODFLOW (USGS) free-format array instead of GRASS ASCII
-GRID is written.-->
-
-<p>
-To write a SURFER .grd ASCII GRID file (with reverted row order and different
-header) use the <em>-s</em> flag:
-
-<div class="code"><pre>
-r.out.ascii -s input=inname output=outname.grd [dp=value]
-</pre></div>
-
-NULL data are coded to "1.70141e+038" for SURFER ASCII GRID files (ignoring
-the <em>null=</em> parameter).
-
-<h2>NOTES</h2>
-
-The output from <em>r.out.ascii</em> may be placed into a file by using the
-UNIX redirection mechanism; e.g.:
-
-<div class="code"><pre>
-r.out.ascii input=soils output=- > out.file
-</pre></div>
-
-The output file out.file can then be printed or copied onto a CDROM
-or floppy disk for export purposes.
-<p>
-To export the raster values as x,y,z values of cell centers (one per line)
-use the <em><a href="r.out.xyz.html">r.out.xyz</a></em> module.
-
-<h2>SEE ALSO</h2>
-
-<em>
-<a href="r.in.ascii.html">r.in.ascii</a>,
-<a href="r.in.arc.html">r.in.arc</a>,
-<a href="r.out.bin.html">r.out.bin</a>,
-<a href="r.out.gdal.html">r.out.gdal</a>,
-<a href="r.out.xyz.html">r.out.xyz</a>
-</em>
-
-<h2>AUTHOR</h2>
-Michael Shapiro,
-U.S. Army Construction Engineering Research Laboratory
-<p>
-Surfer support by Markus Neteler
-
-<p>
-<i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.out.ascii/r.out.ascii.html (from rev 32770, grass/trunk/raster/r.out.ascii/description.html)
===================================================================
--- grass/trunk/raster/r.out.ascii/r.out.ascii.html (rev 0)
+++ grass/trunk/raster/r.out.ascii/r.out.ascii.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,63 @@
+<h2>DESCRIPTION</h2>
+
+<em>r.out.ascii</em> converts a user-specified raster map layer
+(<b>input=</b><em>name</em>) into an ASCII grid in a text file
+(<b>output=</b><em>name</em>) suitable for export to
+other computer systems.
+
+<p>
+
+The GRASS program <em><a href="r.in.ascii.html">r.in.ascii</a></em> can be
+used to perform the reverse function, converting an ASCII file in suitable
+format to GRASS raster map format.
+<p>
+<!--With <b>-s</b> flag SURFER .grd ASCII GRID instead of GRASS ASCII GRID is
+written (with reverted row order, different header).
+<p>
+With <b>-m</b> flag MODFLOW (USGS) free-format array instead of GRASS ASCII
+GRID is written.-->
+
+<p>
+To write a SURFER .grd ASCII GRID file (with reverted row order and different
+header) use the <em>-s</em> flag:
+
+<div class="code"><pre>
+r.out.ascii -s input=inname output=outname.grd [dp=value]
+</pre></div>
+
+NULL data are coded to "1.70141e+038" for SURFER ASCII GRID files (ignoring
+the <em>null=</em> parameter).
+
+<h2>NOTES</h2>
+
+The output from <em>r.out.ascii</em> may be placed into a file by using the
+UNIX redirection mechanism; e.g.:
+
+<div class="code"><pre>
+r.out.ascii input=soils output=- > out.file
+</pre></div>
+
+The output file out.file can then be printed or copied onto a CDROM
+or floppy disk for export purposes.
+<p>
+To export the raster values as x,y,z values of cell centers (one per line)
+use the <em><a href="r.out.xyz.html">r.out.xyz</a></em> module.
+
+<h2>SEE ALSO</h2>
+
+<em>
+<a href="r.in.ascii.html">r.in.ascii</a>,
+<a href="r.in.arc.html">r.in.arc</a>,
+<a href="r.out.bin.html">r.out.bin</a>,
+<a href="r.out.gdal.html">r.out.gdal</a>,
+<a href="r.out.xyz.html">r.out.xyz</a>
+</em>
+
+<h2>AUTHOR</h2>
+Michael Shapiro,
+U.S. Army Construction Engineering Research Laboratory
+<p>
+Surfer support by Markus Neteler
+
+<p>
+<i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.out.bin/description.html
===================================================================
--- grass/trunk/raster/r.out.bin/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.out.bin/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,43 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-The <em>r.out.bin</em> program exports a GRASS raster map to a binary array
-file. Optionally, output can be sent to standard output (stdout) for direct
-input (pipe) into other applications. Data is exported according to the
-original GRASS raster type (e.g. float). If the "-i" flag is specified, an
-integer array is output. The region parameters are printed to stderr.
-
-<h2>NOTES</h2>
-
-With the -h flag, data can be directly used by
-<a href=http://gmt.soest.hawaii.edu/>GMT</a> as Grid Format 1 (float) or
-2 (short). For example:
-
-<div class="code"><pre>
-r.out.bin -h input=grass.raster output=new.grd
-grdinfo new.grd=1 (if float)
-</pre></div>
-
-<p>
-Exported data can be piped directly into the GMT program xyz2grd.
-<div class="code"><pre>
-r.out.bin input=grass.raster output=- | xyz2grd -R.... -ZTLf -
-</pre></div>
-
-The example uses the GMT program xyz2grd with the -ZTLf flag indicating that
-a float array was output.
-
-<h2>SEE ALSO</h2>
-
-<em><a href="r.in.bin.html">r.in.bin</a>,
-<a href="r.in.ascii.html">r.in.ascii</a>
-<a href="r.out.ascii.html">r.out.ascii</a>
-<a href="r.in.arc.html">r.in.arc</a>,
-<a href="r.out.arc.html">r.out.arc</a></em>
-
-
-<h2>AUTHOR</h2>
-This program is derived from <em><a href="r.out.ascii.html">r.out.ascii</a></em>
-with a few modifications. <br>
-Author: <a href=mailto:bcovill at tekmap.ns.ca>Bob Covill</a>
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.out.bin/r.out.bin.html (from rev 32770, grass/trunk/raster/r.out.bin/description.html)
===================================================================
--- grass/trunk/raster/r.out.bin/r.out.bin.html (rev 0)
+++ grass/trunk/raster/r.out.bin/r.out.bin.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,43 @@
+<h2>DESCRIPTION</h2>
+
+The <em>r.out.bin</em> program exports a GRASS raster map to a binary array
+file. Optionally, output can be sent to standard output (stdout) for direct
+input (pipe) into other applications. Data is exported according to the
+original GRASS raster type (e.g. float). If the "-i" flag is specified, an
+integer array is output. The region parameters are printed to stderr.
+
+<h2>NOTES</h2>
+
+With the -h flag, data can be directly used by
+<a href=http://gmt.soest.hawaii.edu/>GMT</a> as Grid Format 1 (float) or
+2 (short). For example:
+
+<div class="code"><pre>
+r.out.bin -h input=grass.raster output=new.grd
+grdinfo new.grd=1 (if float)
+</pre></div>
+
+<p>
+Exported data can be piped directly into the GMT program xyz2grd.
+<div class="code"><pre>
+r.out.bin input=grass.raster output=- | xyz2grd -R.... -ZTLf -
+</pre></div>
+
+The example uses the GMT program xyz2grd with the -ZTLf flag indicating that
+a float array was output.
+
+<h2>SEE ALSO</h2>
+
+<em><a href="r.in.bin.html">r.in.bin</a>,
+<a href="r.in.ascii.html">r.in.ascii</a>
+<a href="r.out.ascii.html">r.out.ascii</a>
+<a href="r.in.arc.html">r.in.arc</a>,
+<a href="r.out.arc.html">r.out.arc</a></em>
+
+
+<h2>AUTHOR</h2>
+This program is derived from <em><a href="r.out.ascii.html">r.out.ascii</a></em>
+with a few modifications. <br>
+Author: <a href=mailto:bcovill at tekmap.ns.ca>Bob Covill</a>
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.out.gdal/description.html
===================================================================
--- grass/trunk/raster/r.out.gdal/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.out.gdal/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,140 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>r.out.gdal</em> allows a user to export a GRASS raster map layer
-into any GDAL supported raster map format.
-
-For possible <em>metaopt</em> parameters see the 'supported formats' pages
-of GDAL.
-The <em>createopt</em> may be used to create TFW or World files ("TFW=YES",
-"WORLDFILE=ON").
-<p>
-<em>r.out.gdal</em> also supports the export of multiband rasters through
-a group (created e.g. with <em>i.group</em>), when the group's name is entered
-as input.
-
-<h2>SUPPORTED RASTER FORMATS</h2>
-
-The set of <a href="http://www.gdal.org/formats_list.html">supported
-raster formats</a> written by <em>r.out.gdal</em> depends on the
-local GDAL installation. Available may be (incomplete list):<p>
-
-<pre>
- AAIGrid: Arc/Info ASCII Grid
- BMP: MS Windows Device Independent Bitmap
- BSB: Maptech BSB Nautical Charts
- DTED: DTED Elevation Raster
- ELAS: ELAS
- ENVI: ENVI .hdr Labelled
- FIT: FIT Image
- GIF: Graphics Interchange Format (.gif)
- GTiff: GeoTIFF
- HDF4Image: HDF4 Dataset
- HFA: Erdas Imagine Images (.img)
- JPEG2000: JPEG-2000 part 1 (ISO/IEC 15444-1)
- JPEG: JPEG JFIF
- MEM: In Memory Raster
- MFF2: Atlantis MFF2 (HKV) Raster
- MFF: Atlantis MFF Raster
- NITF: National Imagery Transmission Format
- PAux: PCI .aux Labelled
- PCIDSK: PCIDSK Database File
- PNG: Portable Network Graphics
- PNM: Portable Pixmap Format (netpbm)
- VRT: Virtual Raster
- XPM: X11 PixMap Format
-</pre>
-
-<h2>NOTES</h2>
-
-When writing out GeoTIFF format for users of ESRI software or ImageMagick,
-the band interleaving should be switched to pixel interleaving using
-<em>createopt="INTERLEAVE=PIXEL"</em>.
-<p>
-To specify multiple options use a comma separated list
-(<em>createopt="TFW=YES,COMPRESS=DEFLATE"</em>).
-<p>
-Out of the GDAL data types, the closest match for GRASS CELL, FCELL and DCELL
-rasters are respectively Int32, Float32 and Float64. These are not exact
-equivalents, but they will preserve the max possible data range and number of
-decimal places for each respective GRASS raster data type. Please keep in mind, that
-not all CELL rasters will require Int32 - e.g., 0-255 CELL raster are covered
-by the Byte <em>type</em> as well. Moreover, some GDAL-supported formats do not
-support all the data types possible in GDAL and GRASS. Use
-<em><a href="r.info">r.info</a></em> to check the data type and range for your
-GRASS raster, refer to specific format documentation
-(<a href="http://www.gdal.org/">GDAL website</a>, format vendor's docs) and
-e.g. the Wikipedia article
-<em><a href="http://en.wikipedia.org/wiki/C_syntax#Typical_boundaries_of_primitive_integral_types">Typical boundaries of primitive integral types</a></em>
-for details.
-
-<h2>EXAMPLES</h2>
-
-<h4>Export the integer raster roads map to GeoTIFF format:</h4>
-<div class="code"><pre>
-r.out.gdal input=roads output=roads.tif type=UInt16
-</pre></div>
-<p>
-
-<h4>Export a DCELL raster map in GeoTIFF format suitable for ESRI software:</h4>
-<div class="code"><pre>
-r.out.gdal in=elevation.10m out=ned_elev10m.tif type=Float64 createopt="INTERLEAVE=PIXEL,TFW=YES"
-</pre></div>
-<p>
-
-<h4>Export the floating point raster elevation map to ERDAS/IMG format:</h4>
-<div class="code"><pre>
-r.out.gdal input=elevation.10m output=elev_dem10.img format=HFA type=Float32
-</pre></div>
-
-<h4>Export group of image maps as multi-band file</h4>
-<div class="code"><pre>
-g.list group
-i.group group=tm7 subgroup=tm7 input=tm7_10,tm7_20,tm7_30,tm7_40,tm7_50,tm7_60,tm7_70
-i.group -l tm7
-r.out.gdal tm7 type=UInt16 out=lsat_multiband.tif
-gdalinfo lsat_multiband.tif
-</pre></div>
-
-
-<h2>GDAL RELATED ERROR MESSAGES</h2>
-
-<ul>
-<li> "ERROR 6: SetColorInterpretation() not supported for this dataset.": This <i>may</i>
- indicate that the color table was not written properly. But usually it will be
- correct and the message can be ignored.</li>
-<li> "ERROR 6: SetNoDataValue() not supported for this dataset.": The selected output format
- does not support "no data". It is recommended to use a different output format.</li>
-<li> "Warning 1: Lost metadata writing to GeoTIFF ... too large to fit in tag.": The color table metadata
- are too large. It is recommended to use a different output format.</li>
-</ul>
-
-
-<h2>SEE ALSO</h2>
-
-The <a href="http://www.gdal.org/formats_list.html">GDAL supported formats</a>
-page.
-<br>
-<em>
-<a href="r.out.ascii.html">r.out.ascii</a>,
-<a href="r.out.arc.html">r.out.arc</a>,
-<a href="r.out.bin.html">r.out.bin</a>,
-<a href="r.out.mat.html">r.out.mat</a>,
-<a href="r.out.png.html">r.out.png</a>,
-<a href="r.out.ppm.html">r.out.ppm</a>,
-<a href="r.out.tiff.html">r.out.tiff</a>
-<br>
-<a href="r.out.gdal.sh.html">r.out.gdal.sh</a></em>
- (old shell script version using <tt>gdal_translate</tt>)
-
-
-<h2>REFERENCES</h2>
-
-GDAL Pages: <a href="http://www.gdal.org">http://www.gdal.org</a>
-
-
-<h2>AUTHOR</h2>
-
-Vytautas Vebra (oliver4grass at gmail.com)
-
-<p>
-<i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.out.gdal/r.out.gdal.html (from rev 32770, grass/trunk/raster/r.out.gdal/description.html)
===================================================================
--- grass/trunk/raster/r.out.gdal/r.out.gdal.html (rev 0)
+++ grass/trunk/raster/r.out.gdal/r.out.gdal.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,140 @@
+<h2>DESCRIPTION</h2>
+
+<em>r.out.gdal</em> allows a user to export a GRASS raster map layer
+into any GDAL supported raster map format.
+
+For possible <em>metaopt</em> parameters see the 'supported formats' pages
+of GDAL.
+The <em>createopt</em> may be used to create TFW or World files ("TFW=YES",
+"WORLDFILE=ON").
+<p>
+<em>r.out.gdal</em> also supports the export of multiband rasters through
+a group (created e.g. with <em>i.group</em>), when the group's name is entered
+as input.
+
+<h2>SUPPORTED RASTER FORMATS</h2>
+
+The set of <a href="http://www.gdal.org/formats_list.html">supported
+raster formats</a> written by <em>r.out.gdal</em> depends on the
+local GDAL installation. Available may be (incomplete list):<p>
+
+<pre>
+ AAIGrid: Arc/Info ASCII Grid
+ BMP: MS Windows Device Independent Bitmap
+ BSB: Maptech BSB Nautical Charts
+ DTED: DTED Elevation Raster
+ ELAS: ELAS
+ ENVI: ENVI .hdr Labelled
+ FIT: FIT Image
+ GIF: Graphics Interchange Format (.gif)
+ GTiff: GeoTIFF
+ HDF4Image: HDF4 Dataset
+ HFA: Erdas Imagine Images (.img)
+ JPEG2000: JPEG-2000 part 1 (ISO/IEC 15444-1)
+ JPEG: JPEG JFIF
+ MEM: In Memory Raster
+ MFF2: Atlantis MFF2 (HKV) Raster
+ MFF: Atlantis MFF Raster
+ NITF: National Imagery Transmission Format
+ PAux: PCI .aux Labelled
+ PCIDSK: PCIDSK Database File
+ PNG: Portable Network Graphics
+ PNM: Portable Pixmap Format (netpbm)
+ VRT: Virtual Raster
+ XPM: X11 PixMap Format
+</pre>
+
+<h2>NOTES</h2>
+
+When writing out GeoTIFF format for users of ESRI software or ImageMagick,
+the band interleaving should be switched to pixel interleaving using
+<em>createopt="INTERLEAVE=PIXEL"</em>.
+<p>
+To specify multiple options use a comma separated list
+(<em>createopt="TFW=YES,COMPRESS=DEFLATE"</em>).
+<p>
+Out of the GDAL data types, the closest match for GRASS CELL, FCELL and DCELL
+rasters are respectively Int32, Float32 and Float64. These are not exact
+equivalents, but they will preserve the max possible data range and number of
+decimal places for each respective GRASS raster data type. Please keep in mind, that
+not all CELL rasters will require Int32 - e.g., 0-255 CELL raster are covered
+by the Byte <em>type</em> as well. Moreover, some GDAL-supported formats do not
+support all the data types possible in GDAL and GRASS. Use
+<em><a href="r.info">r.info</a></em> to check the data type and range for your
+GRASS raster, refer to specific format documentation
+(<a href="http://www.gdal.org/">GDAL website</a>, format vendor's docs) and
+e.g. the Wikipedia article
+<em><a href="http://en.wikipedia.org/wiki/C_syntax#Typical_boundaries_of_primitive_integral_types">Typical boundaries of primitive integral types</a></em>
+for details.
+
+<h2>EXAMPLES</h2>
+
+<h4>Export the integer raster roads map to GeoTIFF format:</h4>
+<div class="code"><pre>
+r.out.gdal input=roads output=roads.tif type=UInt16
+</pre></div>
+<p>
+
+<h4>Export a DCELL raster map in GeoTIFF format suitable for ESRI software:</h4>
+<div class="code"><pre>
+r.out.gdal in=elevation.10m out=ned_elev10m.tif type=Float64 createopt="INTERLEAVE=PIXEL,TFW=YES"
+</pre></div>
+<p>
+
+<h4>Export the floating point raster elevation map to ERDAS/IMG format:</h4>
+<div class="code"><pre>
+r.out.gdal input=elevation.10m output=elev_dem10.img format=HFA type=Float32
+</pre></div>
+
+<h4>Export group of image maps as multi-band file</h4>
+<div class="code"><pre>
+g.list group
+i.group group=tm7 subgroup=tm7 input=tm7_10,tm7_20,tm7_30,tm7_40,tm7_50,tm7_60,tm7_70
+i.group -l tm7
+r.out.gdal tm7 type=UInt16 out=lsat_multiband.tif
+gdalinfo lsat_multiband.tif
+</pre></div>
+
+
+<h2>GDAL RELATED ERROR MESSAGES</h2>
+
+<ul>
+<li> "ERROR 6: SetColorInterpretation() not supported for this dataset.": This <i>may</i>
+ indicate that the color table was not written properly. But usually it will be
+ correct and the message can be ignored.</li>
+<li> "ERROR 6: SetNoDataValue() not supported for this dataset.": The selected output format
+ does not support "no data". It is recommended to use a different output format.</li>
+<li> "Warning 1: Lost metadata writing to GeoTIFF ... too large to fit in tag.": The color table metadata
+ are too large. It is recommended to use a different output format.</li>
+</ul>
+
+
+<h2>SEE ALSO</h2>
+
+The <a href="http://www.gdal.org/formats_list.html">GDAL supported formats</a>
+page.
+<br>
+<em>
+<a href="r.out.ascii.html">r.out.ascii</a>,
+<a href="r.out.arc.html">r.out.arc</a>,
+<a href="r.out.bin.html">r.out.bin</a>,
+<a href="r.out.mat.html">r.out.mat</a>,
+<a href="r.out.png.html">r.out.png</a>,
+<a href="r.out.ppm.html">r.out.ppm</a>,
+<a href="r.out.tiff.html">r.out.tiff</a>
+<br>
+<a href="r.out.gdal.sh.html">r.out.gdal.sh</a></em>
+ (old shell script version using <tt>gdal_translate</tt>)
+
+
+<h2>REFERENCES</h2>
+
+GDAL Pages: <a href="http://www.gdal.org">http://www.gdal.org</a>
+
+
+<h2>AUTHOR</h2>
+
+Vytautas Vebra (oliver4grass at gmail.com)
+
+<p>
+<i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.out.gridatb/description.html
===================================================================
--- grass/trunk/raster/r.out.gridatb/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.out.gridatb/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,16 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-
-<em>r.out.gridatb</em> exports a GRASS raster map to GRIDATB.FOR map file
-(TOPMODEL)
-
-<h2>SEE ALSO</h2>
-
-<em><a href="r.topmodel.html">r.topmodel</a>,</em>
-<em><a href="r.in.gridatb.html">r.in.gridatb</a></em>
-
-<h2>AUTHOR</h2>
-
-Huidae Cho based on code from Keith Beven
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.out.gridatb/r.out.gridatb.html (from rev 32770, grass/trunk/raster/r.out.gridatb/description.html)
===================================================================
--- grass/trunk/raster/r.out.gridatb/r.out.gridatb.html (rev 0)
+++ grass/trunk/raster/r.out.gridatb/r.out.gridatb.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,16 @@
+<h2>DESCRIPTION</h2>
+
+
+<em>r.out.gridatb</em> exports a GRASS raster map to GRIDATB.FOR map file
+(TOPMODEL)
+
+<h2>SEE ALSO</h2>
+
+<em><a href="r.topmodel.html">r.topmodel</a>,</em>
+<em><a href="r.in.gridatb.html">r.in.gridatb</a></em>
+
+<h2>AUTHOR</h2>
+
+Huidae Cho based on code from Keith Beven
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.out.mat/description.html
===================================================================
--- grass/trunk/raster/r.out.mat/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.out.mat/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,99 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>r.out.mat</em> will export a GRASS raster map to a MAT-File which can
-be loaded into Matlab or Octave for plotting or further analysis.
-Attributes such as map title and bounds will also be exported into
-additional array variables.<br>
-<br>
-Specifically, the following array variables are created:<br>
-<ul>
- <li><b> map_data</b>
- <li><b> map_name</b>
- <li><b> map_title</b> (if it exists)
- <li><b> map_northern_edge</b>
- <li><b> map_southern_edge</b>
- <li><b> map_eastern_edge</b>
- <li><b> map_western_edge</b>
-</ul>
-
-<br>
-In addition, <em>r.out.mat</em> makes for a nice binary container format
-for transferring georeferenced maps around, even if you don't use Matlab
-or Octave.
-
-<h2>NOTES</h2>
-
-<em>r.out.mat</em> exports a Version 4 MAT-File. These files should
-successfully load into more modern versions of Matlab and Octave
-without any problems.<br><br>
-
-Everything should be Endian safe, so the resultant file can be simply
-copied between different system architectures without binary translation.
-<br><br>
-
-As there is no IEEE value for <tt>NaN</tt> for integer maps, GRASS's null
-value is used to represent it within these maps. You'll have to do something
-like this to clean them once the map is loaded into Matlab:
-<pre> map_data(find(map_data < -1e9)) = NaN;</pre>
-
-Null values in maps containing either floating point or double-precision
-floating point data should translate into <tt>NaN</tt> values as expected.
-<br><br>
-
-
-<em>r.out.mat</em> must load the entire map into memory before writing,
-therefore it might have problems with <i>huge</i> maps.
-(a 3000x4000 DCELL map uses about 100mb RAM)<br><br>
-
-GRASS defines its map bounds at the outer-edge of the bounding cells, not at
-the coordinates of their centroids. Thus, the following Matlab commands may
-be used to determine the map's resolution information:
-<div class="code"><pre>
- [rows cols] = size(map_data)
- x_range = map_eastern_edge - map_western_edge
- y_range = map_northern_edge - map_southern_edge
- ns_res = y_range/rows
- ew_res = x_range/cols
-</pre></div>
-<br>
-
-<h2>EXAMPLE</h2>
-
-In Matlab, plot with either:
-<div class="code"><pre>
-imagesc(map_data), axis equal, axis tight, colorbar
-</pre></div>
-
-or
-<div class="code"><pre>
-contourf(map_data, 24), axis ij, axis equal, axis tight, colorbar
-</pre></div>
-
-<br>
-
-<h2>TODO</h2>
-
-Add support for exporting map history, category information, color map, etc.
-<br>
-Option to export as a version 5 MAT-File, with map and support information
-stored in a single structured array.
-
-<h2>SEE ALSO</h2>
-
-<i>
-<a href="r.in.mat.html">r.in.mat</a><br>
-<a href="r.out.ascii.html">r.out.ascii</a>, <a href="r.out.bin.html">r.out.bin</a><br>
-<a href="r.null.html">r.null</a><br>
-The <a href="http://www.octave.org">Octave</a> project
-</i>
-
-
-<h2>AUTHOR</h2>
-
-Hamish Bowman<br> <i>
-Department of Marine Science<br>
-University of Otago<br>
-New Zealand</i><br>
-
-<br>
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.out.mat/r.out.mat.html (from rev 32770, grass/trunk/raster/r.out.mat/description.html)
===================================================================
--- grass/trunk/raster/r.out.mat/r.out.mat.html (rev 0)
+++ grass/trunk/raster/r.out.mat/r.out.mat.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,99 @@
+<h2>DESCRIPTION</h2>
+
+<em>r.out.mat</em> will export a GRASS raster map to a MAT-File which can
+be loaded into Matlab or Octave for plotting or further analysis.
+Attributes such as map title and bounds will also be exported into
+additional array variables.<br>
+<br>
+Specifically, the following array variables are created:<br>
+<ul>
+ <li><b> map_data</b>
+ <li><b> map_name</b>
+ <li><b> map_title</b> (if it exists)
+ <li><b> map_northern_edge</b>
+ <li><b> map_southern_edge</b>
+ <li><b> map_eastern_edge</b>
+ <li><b> map_western_edge</b>
+</ul>
+
+<br>
+In addition, <em>r.out.mat</em> makes for a nice binary container format
+for transferring georeferenced maps around, even if you don't use Matlab
+or Octave.
+
+<h2>NOTES</h2>
+
+<em>r.out.mat</em> exports a Version 4 MAT-File. These files should
+successfully load into more modern versions of Matlab and Octave
+without any problems.<br><br>
+
+Everything should be Endian safe, so the resultant file can be simply
+copied between different system architectures without binary translation.
+<br><br>
+
+As there is no IEEE value for <tt>NaN</tt> for integer maps, GRASS's null
+value is used to represent it within these maps. You'll have to do something
+like this to clean them once the map is loaded into Matlab:
+<pre> map_data(find(map_data < -1e9)) = NaN;</pre>
+
+Null values in maps containing either floating point or double-precision
+floating point data should translate into <tt>NaN</tt> values as expected.
+<br><br>
+
+
+<em>r.out.mat</em> must load the entire map into memory before writing,
+therefore it might have problems with <i>huge</i> maps.
+(a 3000x4000 DCELL map uses about 100mb RAM)<br><br>
+
+GRASS defines its map bounds at the outer-edge of the bounding cells, not at
+the coordinates of their centroids. Thus, the following Matlab commands may
+be used to determine the map's resolution information:
+<div class="code"><pre>
+ [rows cols] = size(map_data)
+ x_range = map_eastern_edge - map_western_edge
+ y_range = map_northern_edge - map_southern_edge
+ ns_res = y_range/rows
+ ew_res = x_range/cols
+</pre></div>
+<br>
+
+<h2>EXAMPLE</h2>
+
+In Matlab, plot with either:
+<div class="code"><pre>
+imagesc(map_data), axis equal, axis tight, colorbar
+</pre></div>
+
+or
+<div class="code"><pre>
+contourf(map_data, 24), axis ij, axis equal, axis tight, colorbar
+</pre></div>
+
+<br>
+
+<h2>TODO</h2>
+
+Add support for exporting map history, category information, color map, etc.
+<br>
+Option to export as a version 5 MAT-File, with map and support information
+stored in a single structured array.
+
+<h2>SEE ALSO</h2>
+
+<i>
+<a href="r.in.mat.html">r.in.mat</a><br>
+<a href="r.out.ascii.html">r.out.ascii</a>, <a href="r.out.bin.html">r.out.bin</a><br>
+<a href="r.null.html">r.null</a><br>
+The <a href="http://www.octave.org">Octave</a> project
+</i>
+
+
+<h2>AUTHOR</h2>
+
+Hamish Bowman<br> <i>
+Department of Marine Science<br>
+University of Otago<br>
+New Zealand</i><br>
+
+<br>
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.out.mpeg/description.html
===================================================================
--- grass/trunk/raster/r.out.mpeg/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.out.mpeg/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,104 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>r.out.mpeg</em> is a tool for combining a series of GRASS raster maps
-into a single MPEG-1 (Motion Pictures Expert Group) format file. MPEG-1 is
-a "lossy" video compression format, so the quality of each resulting frame
-of the animation will be much diminished from the original raster image.
-The resulting output file may then be viewed using your favorite mpeg-format
-viewing program.
-MPEG-2 and MPEG-4 provide much better quality animations.
-
-<p>
-The user may define up to four "views", or sub-windows, to animate
-simultaneously. e.g., View 1 could be rainfall, View 2 flooded areas, View
-3 damage to bridges or levees, View 4 other economic damage, all animated as
-a time series. A black border 2 pixels wide is drawn around each view. There
-is an arbitrary limit of 400 files per view (400 animation frames).
-Temporary files are created in the conversion process, so lack of adequate
-tmp space could also limit the number of frames you are able to convert.
-<!-- flag to keep these to feed into another more modern encoder? -->
-
-<p>
-The environment variable GMPEG_SIZE is checked for a value to use as the
-dimension, in pixels, of the longest dimension of the animation image. If
-GMPEG_SIZE is not set, the animation size defaults to the rows & columns
-in the current GRASS region, scaling if necessary to a default minimum size
-of 200 and maximum of 500. These size defaults are overridden when using
-the -c flag (see below). The resolution of the current GRASS region is
-maintained, independent of image size. Playback programs have to decode the
-compressed data "on-the-fly", therefore smaller dimensioned animations will
-provide higher frame rates and smoother animations.
-
-<p>
-UNIX - style wild cards may be used with the command line version in place
-of a raster map name, but wild cards must be quoted.
-
-<h2>Example:</h2>
-<div class="code"><pre>
-r.out.mpeg view1="rain[1-9]","rain1[0-2]" view2="temp*"
-</pre></div>
-
-<p>
-If the number of files differs for each view, the view with the fewest files
-will determine the number of frames in the animation.
-
-<p>
-With <b>-c</b> flag the module converts "on the fly", uses less disk space
-by using <em>r.out.ppm</em> with stdout option to convert frames as needed
-instead of converting all frames to ppm before encoding. Only use when
-encoding a single view. Use of this option also overrides any size
-defaults, using the <b>CURRENTLY DEFINED GRASS REGION for the output size</b>.
-So be careful to set region to a reasonable size prior to encoding.
-
-<p>
-A quality value of <em>qual=1</em> will yield higher quality images, but
-with less compression (larger MPEG file size). Compression ratios will vary
-depending on the number of frames in the animation, but an MPEG produced
-using <em>qual=5</em> will usually be about 60% the size of the MPEG
-produced using <em>qual=1</em>.
-
-<h2>BUGS</h2>
-MPEG images must be 16-pixel aligned for successful compression, so if the
-rows & columns of the calculated image size (scaled, with borders added)
-are not evenly divisible by 16, a few rows/columns will be cut off the
-bottom & right sides of the image. The MPEG format is optimized to
-recognize image MOTION, so abrupt changes from one frame to another will
-cause a "noisy" encoding.
-
-<h2>NOTES</h2>
-This program requires the program <em>mpeg_encode</em> (aka <em>ppmtompeg</em>):
-<p>
-MPEG-1 Video Software Encoder<br>
-(Version 1.3; March 14, 1994)
-<p>
-Lawrence A. Rowe, Kevin Gong, Ketan Patel, and Dan Wallach Computer Science
-Division-EECS, <dd>Univ. of Calif. at Berkeley</dd>
-<p>
-Available from Berkeley:
-<a href="http://bmrc.berkeley.edu/frame/research/mpeg/mpeg_encode.html">http://bmrc.berkeley.edu/frame/research/mpeg/mpeg_encode.html</a>
-<br>or as part of the netpbm package (<em>ppmtompeg</em>):
-<a href="http://netpbm.sourceforge.net">http://netpbm.sourceforge.net</a>
-
-<p>
-Playback may be done with many viewers; <em>mpeg_encode</em>'s official companion
-is <em>mpeg_play</em> available from Berkeley at
-<a href="ftp://mm-ftp.cs.berkeley.edu/pub/multimedia/mpeg/play/">ftp://mm-ftp.cs.berkeley.edu/pub/multimedia/mpeg/play/</a>
-or a precompiled Debian package from
-<a href="http://packages.debian.org/ucbmpeg-play">http://packages.debian.org/ucbmpeg-play</a>
-(includes maintained source code).
-
-<p>
-Use of the <em>-c</em> flag requires the <em>r.out.ppm</em> GRASS module
-with the <em>stdout</em> option.
-
-
-<h2>SEE ALSO</h2>
-<em><a href="r.out.ppm.html">r.out.ppm</a></em>
-<br>
-
-
-<h2>AUTHOR</h2>
-Bill Brown,
-U.S. Army Construction Engineering Research Laboratories
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.out.mpeg/r.out.mpeg.html (from rev 32770, grass/trunk/raster/r.out.mpeg/description.html)
===================================================================
--- grass/trunk/raster/r.out.mpeg/r.out.mpeg.html (rev 0)
+++ grass/trunk/raster/r.out.mpeg/r.out.mpeg.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,104 @@
+<h2>DESCRIPTION</h2>
+
+<em>r.out.mpeg</em> is a tool for combining a series of GRASS raster maps
+into a single MPEG-1 (Motion Pictures Expert Group) format file. MPEG-1 is
+a "lossy" video compression format, so the quality of each resulting frame
+of the animation will be much diminished from the original raster image.
+The resulting output file may then be viewed using your favorite mpeg-format
+viewing program.
+MPEG-2 and MPEG-4 provide much better quality animations.
+
+<p>
+The user may define up to four "views", or sub-windows, to animate
+simultaneously. e.g., View 1 could be rainfall, View 2 flooded areas, View
+3 damage to bridges or levees, View 4 other economic damage, all animated as
+a time series. A black border 2 pixels wide is drawn around each view. There
+is an arbitrary limit of 400 files per view (400 animation frames).
+Temporary files are created in the conversion process, so lack of adequate
+tmp space could also limit the number of frames you are able to convert.
+<!-- flag to keep these to feed into another more modern encoder? -->
+
+<p>
+The environment variable GMPEG_SIZE is checked for a value to use as the
+dimension, in pixels, of the longest dimension of the animation image. If
+GMPEG_SIZE is not set, the animation size defaults to the rows & columns
+in the current GRASS region, scaling if necessary to a default minimum size
+of 200 and maximum of 500. These size defaults are overridden when using
+the -c flag (see below). The resolution of the current GRASS region is
+maintained, independent of image size. Playback programs have to decode the
+compressed data "on-the-fly", therefore smaller dimensioned animations will
+provide higher frame rates and smoother animations.
+
+<p>
+UNIX - style wild cards may be used with the command line version in place
+of a raster map name, but wild cards must be quoted.
+
+<h2>Example:</h2>
+<div class="code"><pre>
+r.out.mpeg view1="rain[1-9]","rain1[0-2]" view2="temp*"
+</pre></div>
+
+<p>
+If the number of files differs for each view, the view with the fewest files
+will determine the number of frames in the animation.
+
+<p>
+With <b>-c</b> flag the module converts "on the fly", uses less disk space
+by using <em>r.out.ppm</em> with stdout option to convert frames as needed
+instead of converting all frames to ppm before encoding. Only use when
+encoding a single view. Use of this option also overrides any size
+defaults, using the <b>CURRENTLY DEFINED GRASS REGION for the output size</b>.
+So be careful to set region to a reasonable size prior to encoding.
+
+<p>
+A quality value of <em>qual=1</em> will yield higher quality images, but
+with less compression (larger MPEG file size). Compression ratios will vary
+depending on the number of frames in the animation, but an MPEG produced
+using <em>qual=5</em> will usually be about 60% the size of the MPEG
+produced using <em>qual=1</em>.
+
+<h2>BUGS</h2>
+MPEG images must be 16-pixel aligned for successful compression, so if the
+rows & columns of the calculated image size (scaled, with borders added)
+are not evenly divisible by 16, a few rows/columns will be cut off the
+bottom & right sides of the image. The MPEG format is optimized to
+recognize image MOTION, so abrupt changes from one frame to another will
+cause a "noisy" encoding.
+
+<h2>NOTES</h2>
+This program requires the program <em>mpeg_encode</em> (aka <em>ppmtompeg</em>):
+<p>
+MPEG-1 Video Software Encoder<br>
+(Version 1.3; March 14, 1994)
+<p>
+Lawrence A. Rowe, Kevin Gong, Ketan Patel, and Dan Wallach Computer Science
+Division-EECS, <dd>Univ. of Calif. at Berkeley</dd>
+<p>
+Available from Berkeley:
+<a href="http://bmrc.berkeley.edu/frame/research/mpeg/mpeg_encode.html">http://bmrc.berkeley.edu/frame/research/mpeg/mpeg_encode.html</a>
+<br>or as part of the netpbm package (<em>ppmtompeg</em>):
+<a href="http://netpbm.sourceforge.net">http://netpbm.sourceforge.net</a>
+
+<p>
+Playback may be done with many viewers; <em>mpeg_encode</em>'s official companion
+is <em>mpeg_play</em> available from Berkeley at
+<a href="ftp://mm-ftp.cs.berkeley.edu/pub/multimedia/mpeg/play/">ftp://mm-ftp.cs.berkeley.edu/pub/multimedia/mpeg/play/</a>
+or a precompiled Debian package from
+<a href="http://packages.debian.org/ucbmpeg-play">http://packages.debian.org/ucbmpeg-play</a>
+(includes maintained source code).
+
+<p>
+Use of the <em>-c</em> flag requires the <em>r.out.ppm</em> GRASS module
+with the <em>stdout</em> option.
+
+
+<h2>SEE ALSO</h2>
+<em><a href="r.out.ppm.html">r.out.ppm</a></em>
+<br>
+
+
+<h2>AUTHOR</h2>
+Bill Brown,
+U.S. Army Construction Engineering Research Laboratories
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.out.png/description.html
===================================================================
--- grass/trunk/raster/r.out.png/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.out.png/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,16 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-
-<em>r.out.png</em> exports a GRASS raster map as non-georeferenced PNG image
-format
-
-<h2>SEE ALSO</h2>
-
-<em><a href="r.out.tiff.html">r.out.tiff</a>,</em>
-<em><a href="r.out.ascii.html">r.out.ascii</a></em>
-
-<h2>AUTHOR</h2>
-
-Alex Shevlakov
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.out.png/r.out.png.html (from rev 32770, grass/trunk/raster/r.out.png/description.html)
===================================================================
--- grass/trunk/raster/r.out.png/r.out.png.html (rev 0)
+++ grass/trunk/raster/r.out.png/r.out.png.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,16 @@
+<h2>DESCRIPTION</h2>
+
+
+<em>r.out.png</em> exports a GRASS raster map as non-georeferenced PNG image
+format
+
+<h2>SEE ALSO</h2>
+
+<em><a href="r.out.tiff.html">r.out.tiff</a>,</em>
+<em><a href="r.out.ascii.html">r.out.ascii</a></em>
+
+<h2>AUTHOR</h2>
+
+Alex Shevlakov
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.out.pov/description.html
===================================================================
--- grass/trunk/raster/r.out.pov/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.out.pov/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,64 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-r.out.pov converts a user-specified raster map layer (map==name) into a
-height-field file for POVray (tga==name). The hftype==value option (where
-value is either 0 or 1) specifies the height-field type. When the user
-enters 0 the output will be actual heights. If entered 1 the cell-values
-will be normalized. If hftype is 0 (actual heights) the bias==value can
-be used to add or substract a value from heights. Use scale==value to scale
-your heights by value. The GRASS program r.out.pov can be used to create
-height- field files for Persistence of Vision (POV) raytracer. POV can
-use a height-field defined in Targa (.TGA) image file format where the
-RGB pixel values are 24 bits (3 bytes). A 16 bit unsigned integer height-field
-value is assigned as follows: RED = high byte, GREEN = low byte, BLUE =
-empty.
-
-<h2>EXAMPLE</h2>
-
-An example Povray script file may look like this:
-<p>
-<div class="code"><pre>
-#include "shapes.inc"
-#include "colors.inc"
-#include "textures.inc"
-
-#declare Scale = 7;
-
-light_source { <40000, Scale*3000, 5000> color MainLight }
-
-camera {
- location < 23000, Scale*2000, 0>
- angle 90
- look_at < 23000, Scale*1400, 5000>
-}
-
-height_field {
- tga "dem.lr.tga"
- smooth
- water_level 0.11 // 726 / 6553.6 = 0.111
- texture {
- pigment {
- image_map { // image is always projected from -z, with front facing +z, top to +Y
- ppm "map.lr.ppm"
- once
- }
- rotate x*90 // align map to height_field
- }
- }
- finish {
- ambient 0.2 // Very dark shadows
- diffuse 0.8 // Whiten the whites
- phong 0.2 // shiny
- phong_size 100.0 // with tight highlights
- specular 0.5
- roughness 0.05
- }
- scale < 14500, Scale*6553.6, 13000 >
- translate <18300, 0, 1100>
-}
-</pre></div>
-
-<h2>AUTHOR</h2>
-Klaus D. Meyer, GEUM.tec GbR, eMail: <i>GEUM.tec at geum.de</i>
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.out.pov/r.out.pov.html (from rev 32770, grass/trunk/raster/r.out.pov/description.html)
===================================================================
--- grass/trunk/raster/r.out.pov/r.out.pov.html (rev 0)
+++ grass/trunk/raster/r.out.pov/r.out.pov.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,64 @@
+<h2>DESCRIPTION</h2>
+
+r.out.pov converts a user-specified raster map layer (map==name) into a
+height-field file for POVray (tga==name). The hftype==value option (where
+value is either 0 or 1) specifies the height-field type. When the user
+enters 0 the output will be actual heights. If entered 1 the cell-values
+will be normalized. If hftype is 0 (actual heights) the bias==value can
+be used to add or substract a value from heights. Use scale==value to scale
+your heights by value. The GRASS program r.out.pov can be used to create
+height- field files for Persistence of Vision (POV) raytracer. POV can
+use a height-field defined in Targa (.TGA) image file format where the
+RGB pixel values are 24 bits (3 bytes). A 16 bit unsigned integer height-field
+value is assigned as follows: RED = high byte, GREEN = low byte, BLUE =
+empty.
+
+<h2>EXAMPLE</h2>
+
+An example Povray script file may look like this:
+<p>
+<div class="code"><pre>
+#include "shapes.inc"
+#include "colors.inc"
+#include "textures.inc"
+
+#declare Scale = 7;
+
+light_source { <40000, Scale*3000, 5000> color MainLight }
+
+camera {
+ location < 23000, Scale*2000, 0>
+ angle 90
+ look_at < 23000, Scale*1400, 5000>
+}
+
+height_field {
+ tga "dem.lr.tga"
+ smooth
+ water_level 0.11 // 726 / 6553.6 = 0.111
+ texture {
+ pigment {
+ image_map { // image is always projected from -z, with front facing +z, top to +Y
+ ppm "map.lr.ppm"
+ once
+ }
+ rotate x*90 // align map to height_field
+ }
+ }
+ finish {
+ ambient 0.2 // Very dark shadows
+ diffuse 0.8 // Whiten the whites
+ phong 0.2 // shiny
+ phong_size 100.0 // with tight highlights
+ specular 0.5
+ roughness 0.05
+ }
+ scale < 14500, Scale*6553.6, 13000 >
+ translate <18300, 0, 1100>
+}
+</pre></div>
+
+<h2>AUTHOR</h2>
+Klaus D. Meyer, GEUM.tec GbR, eMail: <i>GEUM.tec at geum.de</i>
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.out.ppm/description.html
===================================================================
--- grass/trunk/raster/r.out.ppm/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.out.ppm/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,61 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>r.out.ppm</em> converts a GRASS raster map into a PPM image
-at the pixel resolution of the CURRENTLY DEFINED REGION.
-To get the resolution and region settings of the raster map, run:<p>
-
-<div class="code"><pre>
-g.region -p rast=[mapname]
-</pre></div>
-
-<p>
-
-before running <em>r.out.ppm</em>.<p>
-
-By default the PPM file created is 24-bit color, rawbits storage.
-You can use the <b>-G</b> flag to force <em>r.out.ppm</em> to
-output an 8-bit greyscale instead.
-The greyscale conversion uses the NTSC conversion:<p>
-
-<div class="code"><pre>
-Y = .30*Red + .59*Green + .11*Blue
-</pre></div>
-
-<p>
-One pixel is written for each cell value, so if <tt>ew_res</tt> and
-<tt>ns_res</tt> differ, the aspect ratio of the resulting image will be off.
-
-
-<h2>NOTES</h2>
-A few ppm file comments are written: the name of the GRASS
-raster map, resolution, etc. Although these are perfectly legal,
-I've found one PD image utility that chokes on them, so if you need
-a commentless PPM file, use '<tt>out=- > outfile.ppm</tt>'. (When sending
-output to stdout, no comments are written.)
-
-<h2>HINTS</h2>
-
-You can create a PNG image with NULL values represented by a transparent
-background by using the <a href="pngdriver.html">PNG driver</a> with
-<a href="variables.html">GRASS_TRANSPARENT</a> set to TRUE.
-Alternatively, you can use the <em>pnmtopng</em> program from
-<a href="http://netpbm.sourceforge.net">netpbm</a> to do this:
-
-<div class="code"><pre>
-r.out.ppm raster
-pnmtopng -transparent white raster.ppm > raster.png
-</pre></div>
-
-<h2>SEE ALSO</h2>
-<em><a href="d.out.png.html">d.out.png</a></em><br>
-<em><a href="r.out.ascii.html">r.out.ascii</a></em><br>
-<em><a href="r.out.mpeg.html">r.out.mpeg</a></em><br>
-<em><a href="r.out.png.html">r.out.png</a></em><br>
-<em><a href="r.out.ppm3.html">r.out.ppm3</a></em><br>
-<em><a href="r.out.tiff.html">r.out.tiff</a></em>
-
-<h2>AUTHOR</h2>
-
-Bill Brown, UIUC
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.out.ppm/r.out.ppm.html (from rev 32770, grass/trunk/raster/r.out.ppm/description.html)
===================================================================
--- grass/trunk/raster/r.out.ppm/r.out.ppm.html (rev 0)
+++ grass/trunk/raster/r.out.ppm/r.out.ppm.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,61 @@
+<h2>DESCRIPTION</h2>
+
+<em>r.out.ppm</em> converts a GRASS raster map into a PPM image
+at the pixel resolution of the CURRENTLY DEFINED REGION.
+To get the resolution and region settings of the raster map, run:<p>
+
+<div class="code"><pre>
+g.region -p rast=[mapname]
+</pre></div>
+
+<p>
+
+before running <em>r.out.ppm</em>.<p>
+
+By default the PPM file created is 24-bit color, rawbits storage.
+You can use the <b>-G</b> flag to force <em>r.out.ppm</em> to
+output an 8-bit greyscale instead.
+The greyscale conversion uses the NTSC conversion:<p>
+
+<div class="code"><pre>
+Y = .30*Red + .59*Green + .11*Blue
+</pre></div>
+
+<p>
+One pixel is written for each cell value, so if <tt>ew_res</tt> and
+<tt>ns_res</tt> differ, the aspect ratio of the resulting image will be off.
+
+
+<h2>NOTES</h2>
+A few ppm file comments are written: the name of the GRASS
+raster map, resolution, etc. Although these are perfectly legal,
+I've found one PD image utility that chokes on them, so if you need
+a commentless PPM file, use '<tt>out=- > outfile.ppm</tt>'. (When sending
+output to stdout, no comments are written.)
+
+<h2>HINTS</h2>
+
+You can create a PNG image with NULL values represented by a transparent
+background by using the <a href="pngdriver.html">PNG driver</a> with
+<a href="variables.html">GRASS_TRANSPARENT</a> set to TRUE.
+Alternatively, you can use the <em>pnmtopng</em> program from
+<a href="http://netpbm.sourceforge.net">netpbm</a> to do this:
+
+<div class="code"><pre>
+r.out.ppm raster
+pnmtopng -transparent white raster.ppm > raster.png
+</pre></div>
+
+<h2>SEE ALSO</h2>
+<em><a href="d.out.png.html">d.out.png</a></em><br>
+<em><a href="r.out.ascii.html">r.out.ascii</a></em><br>
+<em><a href="r.out.mpeg.html">r.out.mpeg</a></em><br>
+<em><a href="r.out.png.html">r.out.png</a></em><br>
+<em><a href="r.out.ppm3.html">r.out.ppm3</a></em><br>
+<em><a href="r.out.tiff.html">r.out.tiff</a></em>
+
+<h2>AUTHOR</h2>
+
+Bill Brown, UIUC
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.out.ppm3/description.html
===================================================================
--- grass/trunk/raster/r.out.ppm3/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.out.ppm3/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,36 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<b>r.out.ppm3</b> converts 3 GRASS raster layers (R,G,B) to a PPM
-image file, using the current region.
-
-<p>
-This program converts a GRASS raster map to a PPM image file
-using the the current region settings.
-
-<p>
-To get the full area and resolutin of the raster map, run:
-
-<div class="code"><pre>
-g.region rast=[mapname]
-</pre></div>
-
-<p>before running <em>r.out.ppm3</em>.</p>
-
-<h2>NOTES</h2>
-
-One pixel is written for each cell value, so if ew_res and ns_res
-differ, the aspect ratio of the resulting image will be off.
-
-
-<h2>SEE ALSO</h2>
-
-<em><a href="r.out.ppm.html">r.out.ppm</a>,</em>
-<em><a href="r.in.gdal.html">r.in.gdal</a>,</em>
-<em><a href="d.rgb.html">d.rgb</a></em>
-
-<h2>AUTHOR</h2>
-
-Glynn Clements <glynn.clements at virgin.net><br>
-Based upon <em>r.out.ppm</em> and <em>d.rgb</em>.
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.out.ppm3/r.out.ppm3.html (from rev 32770, grass/trunk/raster/r.out.ppm3/description.html)
===================================================================
--- grass/trunk/raster/r.out.ppm3/r.out.ppm3.html (rev 0)
+++ grass/trunk/raster/r.out.ppm3/r.out.ppm3.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,36 @@
+<h2>DESCRIPTION</h2>
+
+<b>r.out.ppm3</b> converts 3 GRASS raster layers (R,G,B) to a PPM
+image file, using the current region.
+
+<p>
+This program converts a GRASS raster map to a PPM image file
+using the the current region settings.
+
+<p>
+To get the full area and resolutin of the raster map, run:
+
+<div class="code"><pre>
+g.region rast=[mapname]
+</pre></div>
+
+<p>before running <em>r.out.ppm3</em>.</p>
+
+<h2>NOTES</h2>
+
+One pixel is written for each cell value, so if ew_res and ns_res
+differ, the aspect ratio of the resulting image will be off.
+
+
+<h2>SEE ALSO</h2>
+
+<em><a href="r.out.ppm.html">r.out.ppm</a>,</em>
+<em><a href="r.in.gdal.html">r.in.gdal</a>,</em>
+<em><a href="d.rgb.html">d.rgb</a></em>
+
+<h2>AUTHOR</h2>
+
+Glynn Clements <glynn.clements at virgin.net><br>
+Based upon <em>r.out.ppm</em> and <em>d.rgb</em>.
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.out.tiff/description.html
===================================================================
--- grass/trunk/raster/r.out.tiff/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.out.tiff/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,45 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<p>This program converts a GRASS raster map to a TIFF raster map. Output may
-be 8 or 24 bit (TrueColor). Optionally, a TIFF World file compatible with
-ESRI's and other's products may be output.</p>
-
-<p>
-The program prompts the user for the name of a GRASS raster map, an output
-TIFF file, whether an 8 or 24 bit format is desired, and whether or not to
-create a TIFF world file. Currently only uncompressed, packpit, or deflate
-TIFF files are written. These output formats are known to be compatible
-with r.in.tiff.</p>
-
-<p>
-The output filename will always have the suffix <code>.tif</code>, and the Tiff World
-file (if requested) <code>.tfw</code>. Any <code>.tif</code> or
-<code>.tiff</code> suffix (case insensitive) specified in the output filename
-will be discarded.</p>
-
-<p>
-When writing with "-l" option, tiles are written at 128x128 pixels. For
-programs that can utilize tiles, it can help speed up some drawing
-operations.</p>
-
-<p>
-The user may adjust region and resolution before export using
-<a href="g.region.html">g.region</a>.</p>
-
-<p>
-A better choice to export GRASS raster data might be
-<a href="r.out.gdal.html">r.out.gdal</a>.
-
-<h2>SEE ALSO</h2>
-
-<em><a href="g.region.html">g.region</a>,</em>
-<em><a href="r.in.gdal.html">r.in.gdal</a>,</em>
-<em><a href="r.out.gdal.html">r.out.gdal</a></em>
-
-<h2>AUTHOR</h2>
-Michael Shapiro,
-U.S. Army Construction Engineering Research Laboratory
-<p>
-GRASS 5.0 team
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.out.tiff/r.out.tiff.html (from rev 32770, grass/trunk/raster/r.out.tiff/description.html)
===================================================================
--- grass/trunk/raster/r.out.tiff/r.out.tiff.html (rev 0)
+++ grass/trunk/raster/r.out.tiff/r.out.tiff.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,45 @@
+<h2>DESCRIPTION</h2>
+
+<p>This program converts a GRASS raster map to a TIFF raster map. Output may
+be 8 or 24 bit (TrueColor). Optionally, a TIFF World file compatible with
+ESRI's and other's products may be output.</p>
+
+<p>
+The program prompts the user for the name of a GRASS raster map, an output
+TIFF file, whether an 8 or 24 bit format is desired, and whether or not to
+create a TIFF world file. Currently only uncompressed, packpit, or deflate
+TIFF files are written. These output formats are known to be compatible
+with r.in.tiff.</p>
+
+<p>
+The output filename will always have the suffix <code>.tif</code>, and the Tiff World
+file (if requested) <code>.tfw</code>. Any <code>.tif</code> or
+<code>.tiff</code> suffix (case insensitive) specified in the output filename
+will be discarded.</p>
+
+<p>
+When writing with "-l" option, tiles are written at 128x128 pixels. For
+programs that can utilize tiles, it can help speed up some drawing
+operations.</p>
+
+<p>
+The user may adjust region and resolution before export using
+<a href="g.region.html">g.region</a>.</p>
+
+<p>
+A better choice to export GRASS raster data might be
+<a href="r.out.gdal.html">r.out.gdal</a>.
+
+<h2>SEE ALSO</h2>
+
+<em><a href="g.region.html">g.region</a>,</em>
+<em><a href="r.in.gdal.html">r.in.gdal</a>,</em>
+<em><a href="r.out.gdal.html">r.out.gdal</a></em>
+
+<h2>AUTHOR</h2>
+Michael Shapiro,
+U.S. Army Construction Engineering Research Laboratory
+<p>
+GRASS 5.0 team
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.out.vrml/description.html
===================================================================
--- grass/trunk/raster/r.out.vrml/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.out.vrml/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,69 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-This module exports a GRASS raster map to the Virtual Reality Modeling
-Language (VRML) format for 3D visualization.
-<p>
-This version only outputs raster maps in VRML 1.0 format.
-The newer VRML 2.0 format will be more efficient for geographic
-applications, as it introduces an "ElevationGrid" node so that
-only the elevation points will have to be written instead
-of the whole geometry. The vast majority of VRML viewers
-currently only support VRML 1.0.
-
-If the extension "wrl" (world) is not present in the he
-<em>output</em> parameter, it will be added.
-
-
-<h2>WARNING</h2>
-VRML is not well suited for large geometrys which can result from even
-a small geographic region. Most viewers seem to bog down with more
-than 12,000 polygons, depending on your hardware & specific
-viewer. Each grid cell results in two polygons, so a reasonable size
-region would be something less than about 75x75. For improved
-performance and smaller file size, leave off a color map. Since VRML
-is ascii text, gzip works very well to significantly compress file
-size.<p>
-
-
-<h2>NOTE</h2>
-This is a preliminary release of "<em>r.out.vrml</em>".
-
-For further information about VRML and available viewers for various platforms, see:<p>
-<a href="http://www.w3.org/MarkUp/VRML/">VRML Virtual Reality Modeling Language</a>
-
-
-<h2>BUGS:</h2>
-Currently the region is transformed to a unit size, so real geographic
-location is lost. Side effects when working in a lat-lon location are
-that besides general distortion due to projection, a very small
-exaggeration factor (on order of .001) must be used to compensate for
-vertical units expected to be the same as map units.
-
-
-<h2>TODO</h2>
-
-Update to the more modern <a href="http://www.geovrml.org">GeoVRML format</a>,
-or probably better the next generation
- <a href="http://www.web3d.org">X3D format</a>.
-See also the <a href="http://www.xj3d.org">Xj3D project</a>.
-
-<p>
-Future plans for this module are to allow draping of sites objects and
-vector maps and using the new sites format available in floating
-point GRASS to embed WWW links into site objects. It will also be
-upgraded to support VRML 2.0 and will allow entering multiple preset
-"views" using the existing GRASS 3d_view file format.<p>
-
-Other possible additions:
-<ul>
- <li> Allow animation of elevation, color, or sites based on
- user interaction.
- <li> Degradation of the raster to produce TINs for improved
- performance.
-</ul>
-
-<h2>AUTHOR</h2>
- Bill Brown, US Army Construction Engineering Research Laboratory
-
-<p>
-<i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.out.vrml/r.out.vrml.html (from rev 32770, grass/trunk/raster/r.out.vrml/description.html)
===================================================================
--- grass/trunk/raster/r.out.vrml/r.out.vrml.html (rev 0)
+++ grass/trunk/raster/r.out.vrml/r.out.vrml.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,69 @@
+<h2>DESCRIPTION</h2>
+
+This module exports a GRASS raster map to the Virtual Reality Modeling
+Language (VRML) format for 3D visualization.
+<p>
+This version only outputs raster maps in VRML 1.0 format.
+The newer VRML 2.0 format will be more efficient for geographic
+applications, as it introduces an "ElevationGrid" node so that
+only the elevation points will have to be written instead
+of the whole geometry. The vast majority of VRML viewers
+currently only support VRML 1.0.
+
+If the extension "wrl" (world) is not present in the he
+<em>output</em> parameter, it will be added.
+
+
+<h2>WARNING</h2>
+VRML is not well suited for large geometrys which can result from even
+a small geographic region. Most viewers seem to bog down with more
+than 12,000 polygons, depending on your hardware & specific
+viewer. Each grid cell results in two polygons, so a reasonable size
+region would be something less than about 75x75. For improved
+performance and smaller file size, leave off a color map. Since VRML
+is ascii text, gzip works very well to significantly compress file
+size.<p>
+
+
+<h2>NOTE</h2>
+This is a preliminary release of "<em>r.out.vrml</em>".
+
+For further information about VRML and available viewers for various platforms, see:<p>
+<a href="http://www.w3.org/MarkUp/VRML/">VRML Virtual Reality Modeling Language</a>
+
+
+<h2>BUGS:</h2>
+Currently the region is transformed to a unit size, so real geographic
+location is lost. Side effects when working in a lat-lon location are
+that besides general distortion due to projection, a very small
+exaggeration factor (on order of .001) must be used to compensate for
+vertical units expected to be the same as map units.
+
+
+<h2>TODO</h2>
+
+Update to the more modern <a href="http://www.geovrml.org">GeoVRML format</a>,
+or probably better the next generation
+ <a href="http://www.web3d.org">X3D format</a>.
+See also the <a href="http://www.xj3d.org">Xj3D project</a>.
+
+<p>
+Future plans for this module are to allow draping of sites objects and
+vector maps and using the new sites format available in floating
+point GRASS to embed WWW links into site objects. It will also be
+upgraded to support VRML 2.0 and will allow entering multiple preset
+"views" using the existing GRASS 3d_view file format.<p>
+
+Other possible additions:
+<ul>
+ <li> Allow animation of elevation, color, or sites based on
+ user interaction.
+ <li> Degradation of the raster to produce TINs for improved
+ performance.
+</ul>
+
+<h2>AUTHOR</h2>
+ Bill Brown, US Army Construction Engineering Research Laboratory
+
+<p>
+<i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.out.vtk/description.html
===================================================================
--- grass/trunk/raster/r.out.vtk/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.out.vtk/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,124 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-Outputs <i>Raster</i> maps in <i>VTK-ASCII</i> format. <i>Map's</i> are
-valid Raster map's in the current mapset. <i>output</i> is the name of
-an VTK-ASCII file which will be written in the current working directory.
-If <i>output</i> is not specified then <b>stdout</b> is used.
-The module is sensitive to region settings (set with g.region).
-<br>
-<br>
-Elevation, scaling, point/celldata, vector and RGB Data are supported.
-If the map is in LL projection, the elevation values will automatically scaled to
-degrees. It is supposed that the elevation values are provided in meters.
-If the elevation values are in a different unit than meters, use
-the scale parameter to convert the units.
-<br>
-<br>
-If no elevation map is given, the user can set the hight of the map by one value.
-Point or cell data are available. Also scaling is supported for this elevation value.
-The elevation value must be provided in meters.
-<br>
-<br>
-The RGB input requires three raster maps: red, green, blue - in this order.
-The maps must have values between 0 and 255, otherwise you will get lots of warnings
-and the values are set to 0.
-More than one RGB dataset (3 maps) is not supported.
-<br>
-<br>
-The vector input requires three raster maps: x, y, z -- defining the vector coordinates - in this order.
-More than one vector dataset (3 maps) is not supported.
-<h2>NOTES</h2>
-This filter generates:
-<ul>
-<li><i>structured points</i> with <i>celldata</i> or <i>pointdata</i> if no elevationfile is given</li>
-
-<li><i>structured grid</i> (not recommendet) with <i>pointdata</i> if an elevationfile is given</li>
-<li><i>polydataset</i> with <i>pointdata</i> if an elevationfile is given (default)</li>
-</ul>
-and puts this in a simple VTK-ASCII file. Nor XML or
-binary output are supported. It is possible to choose more then one raster map
-to be written to the VTK-ASCII file. Each cell-/pointdata is named like the raster map it represents.
-You can visualize this file with the
-<em><a href="http://www.vtk.org">VTK Toolkit</a></em>,
-<em><a href="http://www.paraview.org">Paraview</a></em> and
-<em><a href="http://mayavi.sourceforge.net">MayaVi</a></em> which are based on VTK.
-If you have a raster map with partly no data, use the threshold filter in paraview to
-visualize the valid data. Just filter all data which is greater/lesser than the
-choosen null value in the VTK-ASCII file.
-<br>
-If elevation map is choosen, a polygonal grid is created with <i>quads</i>,
-but the user can choose also <i>triangle strips</i> or <i>vertices</i>.
-These dataformats a documented at <em><a href="http://www.vtk.org">VTK Toolkit</a></em>.
-<br>
-<br>
-If the "-c" flag is used and the data should be visualised together with other data exported via *.out.vtk
-modules, be sure the "-c" flag was also set in these modules.
-But this will only work with data from the SAME location
-(The reference point for the coordinates transformation is based on the center point of the default region).
-<br>
-<br>
-
-
-
-<h3>Difference between point- and celldata</h3>
-r.out.vtk can export raster cells with different representations.
-<ul>
- <li>
- <i>pointdata</i> -- the cells/values are represented by the center of the cell.
- Instead of cells, points are created. Each point can hold different values,
- but the user can only visualize one value at a time. These points can
- be connected in different ways.
- </li>
- <li>
- <i>celldata</i> -- is only provided if no elevation map is given.
- The cells are created with the same hight and width as in GRASS. Each cell
- can hold different values, but the user can only visualize one value at a time.
- </li>
-</ul>
-<h2>EXAMPLE</h2>
-
-<h3>Simple Spearfish example</h3>
-
-<div class="code"><pre>
-#set a nice region
-g.region -d
-g.region n=4926970 s=4914857 w=591583 e=607793 res=50
-
-#export the data
-r.out.vtk input=elevation.10m,slope,aspect elevation=elevation.10m output=/tmp/out.vtk
-
-# visualize in paraview or other VTK viewer:
-paraview --data=/tmp/out.vtk
-</pre></div>
-
-<h3>Spearfish example with RGB data</h3>
-
-<div class="code"><pre>
-#set the region
-g.region -d
-g.region n=4926970 s=4914857 w=591583 e=607793 res=50
-
-#we are using r.in.onearth (available from the grass addon wiki) to create rgb data
-#get some satellite images with r.in.onearth
-r.in.onearth -l output=Sat tmband=Red
-r.in.onearth -l output=Sat tmband=IR1
-r.in.onearth -l output=Sat tmband=IR2
-
-#export the data
-r.out.vtk rgbmaps=SatLandsatTM_IR1,SatLandsatTM_IR2,SatLandsatTM_Red elevation=elevation.10m output=/tmp/out.vtk
-
-# visualize in paraview or other VTK viewer:
-paraview --data=/tmp/out.vtk
-</pre></div>
-
-<br>
-<h2>SEE ALSO</h2>
-
-<em><a href="r3.out.vtk.html">r3.out.vtk</a></em><br>
-<em><a href="r.out.ascii.html">r.out.ascii</a></em><br>
-<em><a href="g.region.html">g.region</a></em><br>
-
-<h2>AUTHORS</h2>
-Soeren Gebbert
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.out.vtk/r.out.vtk.html (from rev 32770, grass/trunk/raster/r.out.vtk/description.html)
===================================================================
--- grass/trunk/raster/r.out.vtk/r.out.vtk.html (rev 0)
+++ grass/trunk/raster/r.out.vtk/r.out.vtk.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,124 @@
+<h2>DESCRIPTION</h2>
+
+Outputs <i>Raster</i> maps in <i>VTK-ASCII</i> format. <i>Map's</i> are
+valid Raster map's in the current mapset. <i>output</i> is the name of
+an VTK-ASCII file which will be written in the current working directory.
+If <i>output</i> is not specified then <b>stdout</b> is used.
+The module is sensitive to region settings (set with g.region).
+<br>
+<br>
+Elevation, scaling, point/celldata, vector and RGB Data are supported.
+If the map is in LL projection, the elevation values will automatically scaled to
+degrees. It is supposed that the elevation values are provided in meters.
+If the elevation values are in a different unit than meters, use
+the scale parameter to convert the units.
+<br>
+<br>
+If no elevation map is given, the user can set the hight of the map by one value.
+Point or cell data are available. Also scaling is supported for this elevation value.
+The elevation value must be provided in meters.
+<br>
+<br>
+The RGB input requires three raster maps: red, green, blue - in this order.
+The maps must have values between 0 and 255, otherwise you will get lots of warnings
+and the values are set to 0.
+More than one RGB dataset (3 maps) is not supported.
+<br>
+<br>
+The vector input requires three raster maps: x, y, z -- defining the vector coordinates - in this order.
+More than one vector dataset (3 maps) is not supported.
+<h2>NOTES</h2>
+This filter generates:
+<ul>
+<li><i>structured points</i> with <i>celldata</i> or <i>pointdata</i> if no elevationfile is given</li>
+
+<li><i>structured grid</i> (not recommendet) with <i>pointdata</i> if an elevationfile is given</li>
+<li><i>polydataset</i> with <i>pointdata</i> if an elevationfile is given (default)</li>
+</ul>
+and puts this in a simple VTK-ASCII file. Nor XML or
+binary output are supported. It is possible to choose more then one raster map
+to be written to the VTK-ASCII file. Each cell-/pointdata is named like the raster map it represents.
+You can visualize this file with the
+<em><a href="http://www.vtk.org">VTK Toolkit</a></em>,
+<em><a href="http://www.paraview.org">Paraview</a></em> and
+<em><a href="http://mayavi.sourceforge.net">MayaVi</a></em> which are based on VTK.
+If you have a raster map with partly no data, use the threshold filter in paraview to
+visualize the valid data. Just filter all data which is greater/lesser than the
+choosen null value in the VTK-ASCII file.
+<br>
+If elevation map is choosen, a polygonal grid is created with <i>quads</i>,
+but the user can choose also <i>triangle strips</i> or <i>vertices</i>.
+These dataformats a documented at <em><a href="http://www.vtk.org">VTK Toolkit</a></em>.
+<br>
+<br>
+If the "-c" flag is used and the data should be visualised together with other data exported via *.out.vtk
+modules, be sure the "-c" flag was also set in these modules.
+But this will only work with data from the SAME location
+(The reference point for the coordinates transformation is based on the center point of the default region).
+<br>
+<br>
+
+
+
+<h3>Difference between point- and celldata</h3>
+r.out.vtk can export raster cells with different representations.
+<ul>
+ <li>
+ <i>pointdata</i> -- the cells/values are represented by the center of the cell.
+ Instead of cells, points are created. Each point can hold different values,
+ but the user can only visualize one value at a time. These points can
+ be connected in different ways.
+ </li>
+ <li>
+ <i>celldata</i> -- is only provided if no elevation map is given.
+ The cells are created with the same hight and width as in GRASS. Each cell
+ can hold different values, but the user can only visualize one value at a time.
+ </li>
+</ul>
+<h2>EXAMPLE</h2>
+
+<h3>Simple Spearfish example</h3>
+
+<div class="code"><pre>
+#set a nice region
+g.region -d
+g.region n=4926970 s=4914857 w=591583 e=607793 res=50
+
+#export the data
+r.out.vtk input=elevation.10m,slope,aspect elevation=elevation.10m output=/tmp/out.vtk
+
+# visualize in paraview or other VTK viewer:
+paraview --data=/tmp/out.vtk
+</pre></div>
+
+<h3>Spearfish example with RGB data</h3>
+
+<div class="code"><pre>
+#set the region
+g.region -d
+g.region n=4926970 s=4914857 w=591583 e=607793 res=50
+
+#we are using r.in.onearth (available from the grass addon wiki) to create rgb data
+#get some satellite images with r.in.onearth
+r.in.onearth -l output=Sat tmband=Red
+r.in.onearth -l output=Sat tmband=IR1
+r.in.onearth -l output=Sat tmband=IR2
+
+#export the data
+r.out.vtk rgbmaps=SatLandsatTM_IR1,SatLandsatTM_IR2,SatLandsatTM_Red elevation=elevation.10m output=/tmp/out.vtk
+
+# visualize in paraview or other VTK viewer:
+paraview --data=/tmp/out.vtk
+</pre></div>
+
+<br>
+<h2>SEE ALSO</h2>
+
+<em><a href="r3.out.vtk.html">r3.out.vtk</a></em><br>
+<em><a href="r.out.ascii.html">r.out.ascii</a></em><br>
+<em><a href="g.region.html">g.region</a></em><br>
+
+<h2>AUTHORS</h2>
+Soeren Gebbert
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.param.scale/description.html
===================================================================
--- grass/trunk/raster/r.param.scale/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.param.scale/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,110 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<b>r.param.scale</b> extracts terrain parameters from a DEM. Uses a
-multi-scale approach by fitting a bivariate quadratic polynomial to a given
-window size using least squares.
-
-<p>
-The module calculates the following parameters (terminology is from Wood,
-1996 with related terminology used in other GRASS modules listed in
-brackets):
-<ul>
-<li>
-<i>elev</i>: Generalised elevation value (for resampling purposes at different
-scale)</li>
-
-<li>
-<i>slope</i>: Magnitude of maximum gradient (steepest slope angle)</li>
-
-<li>
-<i>aspect</i>: Direction of maximum gradient (steepest slope direction=flow direction)</li>
-
-<li>
-<i>profc</i> or profile curvature (curvature intersecting with the plane
-defined by <i>Z</i> axis and maximum gradient direction). Positive values
-describe convex profile curvature, negative values concave profile
-curvature.</li>
-
-<li>
-<i>planc</i> or plan curvature (horizontal curvature, intersecting with
-the <i>XY</i> plane)</li>
-
-<li>
-<i>longc</i> or longitudinal curvature (profile curvature intersecting
-with the plane defined by the surface normal and maximum gradient direction)</li>
-
-<li>
-<i>crosc</i> or cross-sectional curvature (tangential curvature intersecting
-with the plane defined by the surface normal and a tangent to the contour
-- perpendicular to maximum gradient direction)</li>
-
-<li>
-<i>maxic</i> or maximum curvature (can be in any direction)</li>
-
-<li>
-<i>minic</i> or minimum curvature (in direction perpendicular to the direction
-of of maximum curvature)</li>
-
-<!--
-<li>
-<i>meanc</i> or mean curvature (average of maximum and minimum curvatures).</li>
--->
-
-<li>
-<i>feature</i>: Morphometric features: peaks, ridges, passes, channels, pits and planes</li>
-</ul>
-
-<h2>NOTES</h2>
-In <i>r.param.scale</i> the direction of maximum gradient (considered
-downslope) is stored as (West is 0 degree, East is +/- 180 degree):
-
-<ul>
-<li>
-0..+180 degree from West to North to East</li>
-
-<li>
-0..-180 degree from West to South to East</li>
-</ul>
-
-Note that the aspect map is calculated differently from
-<a href="r.slope.aspect.html">r.slope.aspect</a>.
-
-<h2>Still to do</h2>
-
-Fix bug when `constrain through central cell' option selected. Create color
-tables for all output files (presently only on features).
-
-<h2>EXAMPLE</h2>
-
-The next commands will create a morphology map of the Spearfish region:
-
-<div class="code"><pre>
-g.region rast=elevation.10m -p
-r.param.scale in=elevation.10m output=morphology param=feature
-</pre></div>
-
-<h2>SEE ALSO</h2>
-<!-- not ported to GRASS 6 due to non-GPLness of numerical recipes.
-<i><a href="d.param.scale.html">d.param.scale</a></i>
--->
-<p>Java Code in
-<a href="http://www.geog.le.ac.uk/jwo/research/LandSerf">LandSerf</a>
-that implements the same procedure
-
-<h2>REFERENCE</h2>
-
-Wood, J. (1996): The Geomorphological characterisation of Digital Elevation
-Models. Diss., Department of Geography, University of Leicester, U.K.
-
-<br>online at:
-<br><a href="http://www.soi.city.ac.uk/~jwo/phd/">http://www.soi.city.ac.uk/~jwo/phd/</a>
-
-<h2>AUTHOR</h2>
-
-<address>
-<a href="MAILTO:jwo at le.ac.uk">jwo at le.ac.uk</a>
-- <a href="http://www.geog.le.ac.uk/assist/index.html">ASSIST's home</a></address>
-
-<p>Update to FP 3/2002: L. Potrich, M. Neteler, S. Menegon (ITC-irst)
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.param.scale/r.param.scale.html (from rev 32770, grass/trunk/raster/r.param.scale/description.html)
===================================================================
--- grass/trunk/raster/r.param.scale/r.param.scale.html (rev 0)
+++ grass/trunk/raster/r.param.scale/r.param.scale.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,110 @@
+<h2>DESCRIPTION</h2>
+
+<b>r.param.scale</b> extracts terrain parameters from a DEM. Uses a
+multi-scale approach by fitting a bivariate quadratic polynomial to a given
+window size using least squares.
+
+<p>
+The module calculates the following parameters (terminology is from Wood,
+1996 with related terminology used in other GRASS modules listed in
+brackets):
+<ul>
+<li>
+<i>elev</i>: Generalised elevation value (for resampling purposes at different
+scale)</li>
+
+<li>
+<i>slope</i>: Magnitude of maximum gradient (steepest slope angle)</li>
+
+<li>
+<i>aspect</i>: Direction of maximum gradient (steepest slope direction=flow direction)</li>
+
+<li>
+<i>profc</i> or profile curvature (curvature intersecting with the plane
+defined by <i>Z</i> axis and maximum gradient direction). Positive values
+describe convex profile curvature, negative values concave profile
+curvature.</li>
+
+<li>
+<i>planc</i> or plan curvature (horizontal curvature, intersecting with
+the <i>XY</i> plane)</li>
+
+<li>
+<i>longc</i> or longitudinal curvature (profile curvature intersecting
+with the plane defined by the surface normal and maximum gradient direction)</li>
+
+<li>
+<i>crosc</i> or cross-sectional curvature (tangential curvature intersecting
+with the plane defined by the surface normal and a tangent to the contour
+- perpendicular to maximum gradient direction)</li>
+
+<li>
+<i>maxic</i> or maximum curvature (can be in any direction)</li>
+
+<li>
+<i>minic</i> or minimum curvature (in direction perpendicular to the direction
+of of maximum curvature)</li>
+
+<!--
+<li>
+<i>meanc</i> or mean curvature (average of maximum and minimum curvatures).</li>
+-->
+
+<li>
+<i>feature</i>: Morphometric features: peaks, ridges, passes, channels, pits and planes</li>
+</ul>
+
+<h2>NOTES</h2>
+In <i>r.param.scale</i> the direction of maximum gradient (considered
+downslope) is stored as (West is 0 degree, East is +/- 180 degree):
+
+<ul>
+<li>
+0..+180 degree from West to North to East</li>
+
+<li>
+0..-180 degree from West to South to East</li>
+</ul>
+
+Note that the aspect map is calculated differently from
+<a href="r.slope.aspect.html">r.slope.aspect</a>.
+
+<h2>Still to do</h2>
+
+Fix bug when `constrain through central cell' option selected. Create color
+tables for all output files (presently only on features).
+
+<h2>EXAMPLE</h2>
+
+The next commands will create a morphology map of the Spearfish region:
+
+<div class="code"><pre>
+g.region rast=elevation.10m -p
+r.param.scale in=elevation.10m output=morphology param=feature
+</pre></div>
+
+<h2>SEE ALSO</h2>
+<!-- not ported to GRASS 6 due to non-GPLness of numerical recipes.
+<i><a href="d.param.scale.html">d.param.scale</a></i>
+-->
+<p>Java Code in
+<a href="http://www.geog.le.ac.uk/jwo/research/LandSerf">LandSerf</a>
+that implements the same procedure
+
+<h2>REFERENCE</h2>
+
+Wood, J. (1996): The Geomorphological characterisation of Digital Elevation
+Models. Diss., Department of Geography, University of Leicester, U.K.
+
+<br>online at:
+<br><a href="http://www.soi.city.ac.uk/~jwo/phd/">http://www.soi.city.ac.uk/~jwo/phd/</a>
+
+<h2>AUTHOR</h2>
+
+<address>
+<a href="MAILTO:jwo at le.ac.uk">jwo at le.ac.uk</a>
+- <a href="http://www.geog.le.ac.uk/assist/index.html">ASSIST's home</a></address>
+
+<p>Update to FP 3/2002: L. Potrich, M. Neteler, S. Menegon (ITC-irst)
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.patch/description.html
===================================================================
--- grass/trunk/raster/r.patch/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.patch/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,115 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-The GRASS program <em>r.patch</em> allows the user to build a new
-raster map the size and resolution of the current region by assigning
-known data values from input raster maps to the cells in this region.
-This is done by filling in "no data" cells, those that do not yet
-contain data, contain NULL data, or, optionally contain 0 data,
-with the data from the first input map.
-Once this is done the remaining holes are filled in by the next input map,
-and so on.
-This program
-is useful for making a composite raster map layer from two or more adjacent
-map layers, for filling in "holes" in a raster map layer's data (e.g., in
-digital elevation data), or for updating an older map layer with more recent
-data. The current geographic region definition and mask settings are
-respected.
-<p>
-The first <em>name</em> listed in the string
-<b>input=</b><em>name</em>,<em>name</em>,<em>name</em>, ... is the name of
-the first map whose data values will be used to fill in "no data" cells
-in the current region. The second through 200 (max) input <em>name</em>
-maps will be used, in order, to supply data values for for the remaining
-"no data" cells.
-
-<h2>EXAMPLE</h2>
-
-Below, the raster map layer on the far left is <b>patched</b>
-with the middle (<em>patching</em>) raster map layer,
-to produce the <em>composite</em> raster map layer on the right.
-
-<pre>
- 1 1 1 0 2 2 0 0 0 0 1 1 0 0 0 0 1 1 1 1 2 2 0 0
- 1 1 0 2 2 2 0 0 0 0 1 1 0 0 0 0 1 1 1 2 2 2 0 0
- 3 3 3 3 2 2 0 0 0 0 0 0 0 0 0 0 3 3 3 3 2 2 0 0
- 3 3 3 3 0 0 0 0 4 4 4 4 4 4 4 4 3 3 3 3 4 4 4 4
- 3 3 3 0 0 0 0 0 4 4 4 4 4 4 4 4 3 3 3 4 4 4 4 4
- 0 0 0 0 0 0 0 0 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4
-</pre>
-
-Switching the <em>patched</em> and the <em>patching</em> raster map layers
-produces the following results:
-
-<pre>
- 0 0 1 1 0 0 0 0 1 1 1 0 2 2 0 0 1 1 1 1 2 2 0 0
- 0 0 1 1 0 0 0 0 1 1 0 2 2 2 0 0 1 1 1 1 2 2 0 0
- 0 0 0 0 0 0 0 0 3 3 3 3 2 2 0 0 3 3 3 3 2 2 0 0
- 4 4 4 4 4 4 4 4 3 3 3 3 0 0 0 0 4 4 4 4 4 4 4 4
- 4 4 4 4 4 4 4 4 3 3 3 0 0 0 0 0 4 4 4 4 4 4 4 4
- 4 4 4 4 4 4 4 4 0 0 0 0 0 0 0 0 4 4 4 4 4 4 4 4
-</pre>
-
-<h2>NOTES</h2>
-
-Frequently, this program is used to patch together adjacent map layers which
-have been digitized separately. The program
-<em><a href="v.mkgrid.html">v.mkgrid</a></em> can be used to make adjacent
-maps align neatly.
-
-<p>
-The user should check the current geographic region settings before running
-<em>r.patch</em>, to ensure that the region boundaries encompass all
-of the data desired to be included in the composite map and to ensure that the
-region resolution is the resolution of the desired data. To set the
-geographic region settings to one or several raster maps, the <em>g.region</em>
-program can be used:
-
-<div class="code"><pre>
-g.region rast=map1[,map2[,...]]
-</pre></div>
-
-<p>
-
-Use of <em>r.patch</em> is generally followed by use of the GRASS programs
-<em><a href="g.remove.html">g.remove</a></em> and
-<em><a href="g.rename.html">g.rename</a></em>;
-<em>g.remove</em> is used to remove the original (un-patched) raster map
-layers, while <em>g.rename</em> is used to then assign to the newly-created
-composite (patched) raster map layer the name of the original raster map
-layer.
-
-<p>
-<em>r.patch</em> creates support files for the patched, composite output map.
-
-
-<h2>EXAMPLE</h2>
-
-Create a list of maps matching a pattern, extend the region to include them
-all, and patch them together to create a mosaic. Overlapping maps will be
-used in the order listed.
-
-<div class="code"><pre>
-MAPS=`g.mlist type=rast sep=, pat="map_*"`
-g.region rast=$MAPS
-r.patch in=$MAPS out=mosaic
-</pre></div>
-<br>
-
-
-<h2>SEE ALSO</h2>
-
-<em><a href="g.region.html">g.region</a></em>,
-<em><a href="g.remove.html">g.remove</a></em>,
-<em><a href="g.rename.html">g.rename</a></em>,
-<em><a href="r.mapcalc.html">r.mapcalc</a></em>,
-<em><a href="r.support.html">r.support</a></em>,
-<em><a href="v.mkgrid.html">v.mkgrid</a></em>
-
-<h2>AUTHOR</h2>
-
-Michael Shapiro,
-U.S. Army Construction Engineering Research Laboratory
-<br>
--z flag by Huidae Cho
-
-<p><i>Last changed: $Date$</i></p>
Copied: grass/trunk/raster/r.patch/r.patch.html (from rev 32770, grass/trunk/raster/r.patch/description.html)
===================================================================
--- grass/trunk/raster/r.patch/r.patch.html (rev 0)
+++ grass/trunk/raster/r.patch/r.patch.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,115 @@
+<h2>DESCRIPTION</h2>
+
+The GRASS program <em>r.patch</em> allows the user to build a new
+raster map the size and resolution of the current region by assigning
+known data values from input raster maps to the cells in this region.
+This is done by filling in "no data" cells, those that do not yet
+contain data, contain NULL data, or, optionally contain 0 data,
+with the data from the first input map.
+Once this is done the remaining holes are filled in by the next input map,
+and so on.
+This program
+is useful for making a composite raster map layer from two or more adjacent
+map layers, for filling in "holes" in a raster map layer's data (e.g., in
+digital elevation data), or for updating an older map layer with more recent
+data. The current geographic region definition and mask settings are
+respected.
+<p>
+The first <em>name</em> listed in the string
+<b>input=</b><em>name</em>,<em>name</em>,<em>name</em>, ... is the name of
+the first map whose data values will be used to fill in "no data" cells
+in the current region. The second through 200 (max) input <em>name</em>
+maps will be used, in order, to supply data values for for the remaining
+"no data" cells.
+
+<h2>EXAMPLE</h2>
+
+Below, the raster map layer on the far left is <b>patched</b>
+with the middle (<em>patching</em>) raster map layer,
+to produce the <em>composite</em> raster map layer on the right.
+
+<pre>
+ 1 1 1 0 2 2 0 0 0 0 1 1 0 0 0 0 1 1 1 1 2 2 0 0
+ 1 1 0 2 2 2 0 0 0 0 1 1 0 0 0 0 1 1 1 2 2 2 0 0
+ 3 3 3 3 2 2 0 0 0 0 0 0 0 0 0 0 3 3 3 3 2 2 0 0
+ 3 3 3 3 0 0 0 0 4 4 4 4 4 4 4 4 3 3 3 3 4 4 4 4
+ 3 3 3 0 0 0 0 0 4 4 4 4 4 4 4 4 3 3 3 4 4 4 4 4
+ 0 0 0 0 0 0 0 0 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4
+</pre>
+
+Switching the <em>patched</em> and the <em>patching</em> raster map layers
+produces the following results:
+
+<pre>
+ 0 0 1 1 0 0 0 0 1 1 1 0 2 2 0 0 1 1 1 1 2 2 0 0
+ 0 0 1 1 0 0 0 0 1 1 0 2 2 2 0 0 1 1 1 1 2 2 0 0
+ 0 0 0 0 0 0 0 0 3 3 3 3 2 2 0 0 3 3 3 3 2 2 0 0
+ 4 4 4 4 4 4 4 4 3 3 3 3 0 0 0 0 4 4 4 4 4 4 4 4
+ 4 4 4 4 4 4 4 4 3 3 3 0 0 0 0 0 4 4 4 4 4 4 4 4
+ 4 4 4 4 4 4 4 4 0 0 0 0 0 0 0 0 4 4 4 4 4 4 4 4
+</pre>
+
+<h2>NOTES</h2>
+
+Frequently, this program is used to patch together adjacent map layers which
+have been digitized separately. The program
+<em><a href="v.mkgrid.html">v.mkgrid</a></em> can be used to make adjacent
+maps align neatly.
+
+<p>
+The user should check the current geographic region settings before running
+<em>r.patch</em>, to ensure that the region boundaries encompass all
+of the data desired to be included in the composite map and to ensure that the
+region resolution is the resolution of the desired data. To set the
+geographic region settings to one or several raster maps, the <em>g.region</em>
+program can be used:
+
+<div class="code"><pre>
+g.region rast=map1[,map2[,...]]
+</pre></div>
+
+<p>
+
+Use of <em>r.patch</em> is generally followed by use of the GRASS programs
+<em><a href="g.remove.html">g.remove</a></em> and
+<em><a href="g.rename.html">g.rename</a></em>;
+<em>g.remove</em> is used to remove the original (un-patched) raster map
+layers, while <em>g.rename</em> is used to then assign to the newly-created
+composite (patched) raster map layer the name of the original raster map
+layer.
+
+<p>
+<em>r.patch</em> creates support files for the patched, composite output map.
+
+
+<h2>EXAMPLE</h2>
+
+Create a list of maps matching a pattern, extend the region to include them
+all, and patch them together to create a mosaic. Overlapping maps will be
+used in the order listed.
+
+<div class="code"><pre>
+MAPS=`g.mlist type=rast sep=, pat="map_*"`
+g.region rast=$MAPS
+r.patch in=$MAPS out=mosaic
+</pre></div>
+<br>
+
+
+<h2>SEE ALSO</h2>
+
+<em><a href="g.region.html">g.region</a></em>,
+<em><a href="g.remove.html">g.remove</a></em>,
+<em><a href="g.rename.html">g.rename</a></em>,
+<em><a href="r.mapcalc.html">r.mapcalc</a></em>,
+<em><a href="r.support.html">r.support</a></em>,
+<em><a href="v.mkgrid.html">v.mkgrid</a></em>
+
+<h2>AUTHOR</h2>
+
+Michael Shapiro,
+U.S. Army Construction Engineering Research Laboratory
+<br>
+-z flag by Huidae Cho
+
+<p><i>Last changed: $Date$</i></p>
Deleted: grass/trunk/raster/r.profile/description.html
===================================================================
--- grass/trunk/raster/r.profile/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.profile/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,146 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-This program outputs two or four column (with <b>-g</b>) data to stdout or
-an ASCII file. The default two column output consists of cumulative profile
-length (in meters) and raster value. The optional four column output consists
-of easting, northing, cumlative profile length (m), and raster value. Profile
-end or "turning" points can be set manually with the <b>profile</b>
-argument or selected interactively from the GRASS monitor by setting the
-<b>-i</b> flag. The profile resolution, or distance between profile
-points, is obtained from the current region resolution, or can be manually
-set with the <b>res</b> argument.
-<p>
-The <b>-i</b> flag allows the user for selecting the profile from the GRASS
-monitor by clicking the left mouse button along the profile; clicking the
-right mouse button ends the profile.
-<p>
-The <b>profile</b> parameter can be set to comma separated geographic
-coordinates for profile line endpoints. The interactive flag (<b>-i</b>)
-overrides this option. Alternatively the coordinate pairs can be piped
-from stdin, one comma separated pair per line.
-<p>
-The <b>res</b> parameter sets the distance between each profile point
-(resolution). The resolution must be provided in GRASS database units (i.e.
-decimal degrees for Lat Long databases and meters for UTM). By default
-<em>r.profile</em> uses the resolution of the current GRASS region.
-<p>
-The <b>null</b> parameter can optionally be set to change the character
-string representing null values.
-
-<h2>OUTPUT FORMAT</h2>
-
-The multi column output from <em>r.profile</em> is intended for easy use in
-other programs. The output can be piped (|) directly into other programs or
-saved to a file for later use. Output with geographic coordinates (<em>-g</em>)
-is compatible with <em><a href="v.in.ascii.html">v.in.ascii</a></em> and can
-be piped direcly into this program.
-
-<div class="code"><pre>
-r.profile -ig input=elev.rast | v.in.ascii output=elev.profile fs=space
-</pre></div>
-
-The 2 column output is compatible with most plotting programs.
-<p>
-The optional RGB output provides the associated GRASS colour value for
-each profile point.
-
-<h2>EXAMPLES</h2>
-
-<b>Example 1</b><br>
-Extract a profile with coordinates provided on the command line:
-
-<div class="code"><pre>
-r.profile input=elev.rast output=profile.pts profile=562517,7779433,562984,7779533,563875,7779800
-</pre></div>
-This will extract a profile along the track defined by the three coordinate
-pairs.
-<p><br>
-
-
-<b>Example 2</b><br>
-Extract a profile by interactively selecting the profile route from the GRASS
-monitor:
-
-<div class="code"><pre>
-r.profile -i input=elev.rast output=profile.pts
-</pre></div>
-Use the left mouse button to select the profile route in the GRASS monitor. Use the
-right mouse button to end the profile.
-<p><br>
-
-
-<b>Example 3</b><br>
-Extract a profile with coordinates provided from standard input or an external file:
-<p>
-First create a points file with <em><a href="d.where.html">d.where</a></em>
-
-<div class="code"><pre>
-d.where > saved.points
-</pre></div>
-
-Then pipe the points file into r.profile
-
-<div class="code"><pre>
-cat saved.points | r.profile input=elev.rast output=profile.pts
-</pre></div>
-
-The advantage of this method is that the same profile points can be piped into
-different GRASS rasters by changing the input parameter.
-<p>
-With this method the coordinates must be given as space or tab seperated easting
-and northing. Labels after these values are ignored.
-<p>
-Another example using d.where:
-
-<div class="code"><pre>
-d.where | r.profile elevation.dem
-</pre></div>
-
-<p><br>
-
-
-<b>Example 4</b><br>
-Pipe coordinates into r.profile
-<div class="code"><pre>
-r.profile elevation.dem res=1000 << EOF
- 591243,4926344
- 592509,4922156
- 594100,4920793
- 599910,4919365
- 602929,4919235
- 604844,4918391
- 606468,4917190
- 607766,4915664
-EOF
-</pre></div>
-
-
-<h2>NOTES</h2>
-
-The profile resolution is measured exactly from the supplied end or
-"turning" point along the profile. The end of a profile segment will be an
-exact multiple of the profile resolution and will therefore not always match
-the end point coordinates entered for the segmanet.
-
-<p>
-To extract the numbers in scripts, following parameters can be used:
-<div class="code"><pre>
-r.profile input=dgm12.5 profile=3570631,5763556 2>/dev/null
-</pre></div>
-
-This filters out the everything except the numbers.
-
-<h2>SEE ALSO</h2>
-
-<em><a href="v.in.ascii.html">v.in.ascii</a></em>,
-<em><a href="d.where.html">d.where</a></em>,
-<em><a href="d.profile.html">d.profile</a></em>,
-<em><a href="r.what.html">r.what</a></em>,
-<em><a href="r.transect.html">r.transect</a></em>,
-<em><a href="gm_profile.html">gis.m: PROFILE TOOL</a></em>
-
-<h2>AUTHOR</h2>
-<a href=mailto:bcovill at tekmap.ns.ca>Bob Covill</a>
-
-<p>
-<i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.profile/r.profile.html (from rev 32770, grass/trunk/raster/r.profile/description.html)
===================================================================
--- grass/trunk/raster/r.profile/r.profile.html (rev 0)
+++ grass/trunk/raster/r.profile/r.profile.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,146 @@
+<h2>DESCRIPTION</h2>
+
+This program outputs two or four column (with <b>-g</b>) data to stdout or
+an ASCII file. The default two column output consists of cumulative profile
+length (in meters) and raster value. The optional four column output consists
+of easting, northing, cumlative profile length (m), and raster value. Profile
+end or "turning" points can be set manually with the <b>profile</b>
+argument or selected interactively from the GRASS monitor by setting the
+<b>-i</b> flag. The profile resolution, or distance between profile
+points, is obtained from the current region resolution, or can be manually
+set with the <b>res</b> argument.
+<p>
+The <b>-i</b> flag allows the user for selecting the profile from the GRASS
+monitor by clicking the left mouse button along the profile; clicking the
+right mouse button ends the profile.
+<p>
+The <b>profile</b> parameter can be set to comma separated geographic
+coordinates for profile line endpoints. The interactive flag (<b>-i</b>)
+overrides this option. Alternatively the coordinate pairs can be piped
+from stdin, one comma separated pair per line.
+<p>
+The <b>res</b> parameter sets the distance between each profile point
+(resolution). The resolution must be provided in GRASS database units (i.e.
+decimal degrees for Lat Long databases and meters for UTM). By default
+<em>r.profile</em> uses the resolution of the current GRASS region.
+<p>
+The <b>null</b> parameter can optionally be set to change the character
+string representing null values.
+
+<h2>OUTPUT FORMAT</h2>
+
+The multi column output from <em>r.profile</em> is intended for easy use in
+other programs. The output can be piped (|) directly into other programs or
+saved to a file for later use. Output with geographic coordinates (<em>-g</em>)
+is compatible with <em><a href="v.in.ascii.html">v.in.ascii</a></em> and can
+be piped direcly into this program.
+
+<div class="code"><pre>
+r.profile -ig input=elev.rast | v.in.ascii output=elev.profile fs=space
+</pre></div>
+
+The 2 column output is compatible with most plotting programs.
+<p>
+The optional RGB output provides the associated GRASS colour value for
+each profile point.
+
+<h2>EXAMPLES</h2>
+
+<b>Example 1</b><br>
+Extract a profile with coordinates provided on the command line:
+
+<div class="code"><pre>
+r.profile input=elev.rast output=profile.pts profile=562517,7779433,562984,7779533,563875,7779800
+</pre></div>
+This will extract a profile along the track defined by the three coordinate
+pairs.
+<p><br>
+
+
+<b>Example 2</b><br>
+Extract a profile by interactively selecting the profile route from the GRASS
+monitor:
+
+<div class="code"><pre>
+r.profile -i input=elev.rast output=profile.pts
+</pre></div>
+Use the left mouse button to select the profile route in the GRASS monitor. Use the
+right mouse button to end the profile.
+<p><br>
+
+
+<b>Example 3</b><br>
+Extract a profile with coordinates provided from standard input or an external file:
+<p>
+First create a points file with <em><a href="d.where.html">d.where</a></em>
+
+<div class="code"><pre>
+d.where > saved.points
+</pre></div>
+
+Then pipe the points file into r.profile
+
+<div class="code"><pre>
+cat saved.points | r.profile input=elev.rast output=profile.pts
+</pre></div>
+
+The advantage of this method is that the same profile points can be piped into
+different GRASS rasters by changing the input parameter.
+<p>
+With this method the coordinates must be given as space or tab seperated easting
+and northing. Labels after these values are ignored.
+<p>
+Another example using d.where:
+
+<div class="code"><pre>
+d.where | r.profile elevation.dem
+</pre></div>
+
+<p><br>
+
+
+<b>Example 4</b><br>
+Pipe coordinates into r.profile
+<div class="code"><pre>
+r.profile elevation.dem res=1000 << EOF
+ 591243,4926344
+ 592509,4922156
+ 594100,4920793
+ 599910,4919365
+ 602929,4919235
+ 604844,4918391
+ 606468,4917190
+ 607766,4915664
+EOF
+</pre></div>
+
+
+<h2>NOTES</h2>
+
+The profile resolution is measured exactly from the supplied end or
+"turning" point along the profile. The end of a profile segment will be an
+exact multiple of the profile resolution and will therefore not always match
+the end point coordinates entered for the segmanet.
+
+<p>
+To extract the numbers in scripts, following parameters can be used:
+<div class="code"><pre>
+r.profile input=dgm12.5 profile=3570631,5763556 2>/dev/null
+</pre></div>
+
+This filters out the everything except the numbers.
+
+<h2>SEE ALSO</h2>
+
+<em><a href="v.in.ascii.html">v.in.ascii</a></em>,
+<em><a href="d.where.html">d.where</a></em>,
+<em><a href="d.profile.html">d.profile</a></em>,
+<em><a href="r.what.html">r.what</a></em>,
+<em><a href="r.transect.html">r.transect</a></em>,
+<em><a href="gm_profile.html">gis.m: PROFILE TOOL</a></em>
+
+<h2>AUTHOR</h2>
+<a href=mailto:bcovill at tekmap.ns.ca>Bob Covill</a>
+
+<p>
+<i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.proj/description.html
===================================================================
--- grass/trunk/raster/r.proj/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.proj/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,197 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-
-<em>r.proj</em> projects a raster map in a specified mapset of a
-specified location from the projection of the input location to a raster map
-in the current location. The projection information is taken from the
-current PROJ_INFO files, as set with <i><a href="g.setproj.html">g.setproj</a>
-</i> and viewed with <i><a href="g.proj.html">g.proj</a></i>.
-
-<h4>Introduction</h4>
-
-<h5>Map projections</h5>
-
-Map projections are a method of representing information from a
-curved surface (usually a spheroid) in two dimensions, typically to allow
-indexing through cartesian coordinates. There are a wide variety of
-projections, with common ones divided into a number of classes, including
-cylindrical and pseudo-cylindrical, conic and pseudo-conic, and azimuthal
-methods, each of which may be conformal, equal-area, or neither.
-<p>
-The particular projection chosen depends on the purpose of the project,
-and the size, shape and location of the area of interest. For example,
-normal cylindrical projections are good for maps which are of greater extent
-east-west than north-south and in equatorial regions, while conic
-projections are better in mid-latitudes; transverse cylindrical projections
-are used for maps which are of greater extent north-south than east-west;
-azimuthal projections are used for polar regions. Oblique versions of any
-of these may also be used. Conformal projections preserve angular
-relationships, and better preserve arc-length, while equal-area projections
-are more appropriate for statistical studies and work in which the amount of
-material is important.
-<p>
-Projections are defined by precise mathematical relations, so the method
-of projecting coordinates from a geographic reference frame
-(latitude-longitude) into a projected cartesian reference frame (eg metres)
-is governed by these equations. Inverse projections can also be achieved.
-The public-domain Unix software package <i>PROJ</i> [1] has been designed to
-perform these transformations, and the user's manual contains a detailed
-description of over 100 useful projections. This also includes a
-programmers library of the projection methods to support other software
-development.
-<p>
-Thus, converting a vector map - in which objects are located
-with arbitrary spatial precision - from one projection into another is
-usually accomplished by a simple two-step process: first the location of
-all the points in the map are converted from the source through an inverse
-projection into latitude-longitude, and then through a forward projection
-into the target. (Of course the procedure will be one-step if either the
-source or target is in geographic coordinates.)
-<p>
-Converting a raster map, or image, between different projections,
-however, involves additional considerations.
-A raster may be considered to represent a sampling of a
-process at a regular, ordered set of locations. The set of locations that
-lie at the intersections of a cartesian grid in one projection will not, in
-general, coincide with the sample points in another projection. Thus, the
-conversion of raster maps involves an interpolation step in which the values
-of points at intermediate locations relative to the source grid are
-estimated.
-
-<h5>Projecting vector maps within the GRASS GIS</h5>
-<!-- move this into v.proj.html !! -->
-GIS data capture, import and transfer often requires a projection
-step, since the source or client will frequently be in a different
-projection to the working projection.
-<p>
-In some cases it is convenient to do the conversion outside the package,
-prior to import or after export, using software such as <i>PROJ.4</i>'s
-<i><a href="http://proj.maptools.org/">cs2cs</a></i> [1]. This is an easy
-method for converting an ASCII file containing a list of coordinate points,
-since there is no topology to be preserved and <i>cs2cs</i> can be used to
-process simple lists using a one-line command.
-<p>
-The format of files containg vector maps with <b>lines</b> and <b>arcs</b> is
-generally more complex, as parts of the data stored in the files will describe
-topology, and not just coordinates. In GRASS GIS the
-<i><a href="v.proj.html">v.proj</a></i> module is provided to reproject
-vector maps, transferring topology and attributes as well as node coordinates.
-This program uses the projection definition and parameters which are stored in
-the PROJ_INFO and PROJ_UNITS files in the PERMANENT mapset directory for every
-GRASS location.
-<br><br>
-
-<h4>Design of r.proj</h4>
-
-As discussed briefly above, the fundamental step in re-projecting a
-raster is resampling the source grid at locations corresponding to the
-intersections of a grid in the target projection. The basic procedure for
-accomplishing this, therefore, is as follows:
-<p>
-<em>r.proj</em> converts a map to a new geographic projection. It reads a
-map from a different location, projects it and write it out to the current
-location.
-<br>
-The projected data is resampled with one of three different methods:
-nearest neighbor, bilinear and cubic convolution.
-<p>
-The <em>method=nearest</em>, which performs a nearest neighbor assignment,
-is the fastest of the three resampling methods. It is primarily used for
-categorical data such as a land use classification, since it will not change
-the values of the data cells. The <em>method=bilinear</em> determines the new
-value of the cell based on a weighted distance average of the 4 surrounding
-cells in the input map. The <em>method=cubic</em> determines the new value of
-the cell based on a weighted distance average of the 16 surrounding cells in
-the input map.
-<p>
-The bilinear and cubic interpolation methods are most appropriate for
-continuous data and cause some smoothing. Both options should not be used
-with categorical data, since the cell values will be altered.
-<p>
-If nearest neighbor assignment is used, the output map has the same raster
-format as the input map. If any of the both interpolations is used, the
-output map is written as floating point.
-
-<p>
-Note that, following normal GRASS conventions, the coverage and
-resolution of the resulting grid is set by the current region settings,
-which may be adjusted using <i>g.region</i>. The target raster will be
-relatively unbiased for all cases if its grid has a similar resolution to
-the source, so that the resampling/interpolation step is only a local
-operation. If the resolution is changed significantly, then the behaviour
-of the generalisation or refinement will depend on the model of the process
-being represented. This will be very different for categorical versus
-numerical data. Note that three methods for the local interpolation step
-are provided.
-
-<p>
-<em>r.proj</em> supports general datum transformations, making use of the
-<em>PROJ.4</em> co-ordinate system translation library.
-</p>
-
-<h2>NOTES</h2>
-
-To avoid excessive time consumption when reprojecting a map the region and
-resolution of the target location should be set appropriately beforehand.
-A simple way to do this is to generate a vector "box" map of the region in
-the source location using <em><a href="v.in.region.html">v.in.region</a></em>.
-This "box" map is then reprojected into the target location with
-<em><a href="v.proj.html">v.proj</a></em>.
-Next the region in the target location is set to the extent of the new vector
-map with <em><a href="g.region.html">g.region</a></em> along with the desired
-raster resolution (<em>g.region -m</em> can be used in Latitude/Longitude
-locations to measure the geodetic length of a pixel).
-<em>r.proj</em> is then run for the raster map the user wants to reproject.
-In this case a little preparation goes a long way.
-<p>
-When reprojecting whole-world maps the user should disable map-trimming with
-the <em>-n</em> flag. Trimming is not useful here because the module has the
-whole map in memory anyway. Besides that, world "edges" are hard (or
-impossible) to find in projections other than latitude-longitude so results
-may be odd with trimming.
-
-<h2>REFERENCES</h2>
-
-[1] Evenden, G.I. (1990) <a href="http://proj.maptools.org/">Cartographic projection procedures for
-the UNIX environment - a user's manual.</a> USGS Open-File Report 90-284 (OF90-284.pdf)
-See also there: Interim Report and 2nd Interim Report on Release 4, Evenden 1994).
-<p>
-Richards, John A. (1993), Remote Sensing Digital Image Analysis,
-Springer-Verlag, Berlin, 2nd edition.
-<p>
-<a href=http://proj.maptools.org/>PROJ.4</a>: Projection/datum support library.
-<p>
-<b>Further reading</b>
-<ul>
-<li> <a href="http://www.asprs.org/resources/grids/">ASPRS Grids and Datum</a>
-<li> <a href="http://www.remotesensing.org/geotiff/proj_list/">Projections Transform List</a> (PROJ.4)
-<li> <a href="http://www.mapref.org">MapRef - The Collection of Map Projections and Reference Systems for Europe</a>
-<li> <a href="http://crs.bkg.bund.de/crs-eu/">Information and Service System for European Coordinate Reference Systems - CRS</a>
-</ul>
-
-<h2>SEE ALSO</h2>
-
-<em>
-<a href="g.region.html">g.region</a>,
-<a href="g.proj.html">g.proj</a>,
-<a href="g.setproj.html">g.setproj</a>,
-<a href="i.rectify.html">i.rectify</a>,
-<a href="r.support.html">r.support</a>,
-<a href="r.stats.html">r.stats</a>,
-<a href="v.proj.html">v.proj</a>,
-<a href="v.in.region.html">v.in.region</a>
-</em>
-<p>
-The 'gdalwarp' and 'gdal_translate' utilities are available from the
-<a href="http://www.gdal.org">GDAL</a> project.
-
-<h2>AUTHORS</h2>
-
-Martin Schroeder, University of Heidelberg, Germany<p>
-Man page text from S.J.D. Cox, AGCRC, CSIRO Exploration & Mining, Nedlands, WA
-<p>
-Updated by <a href="mailto:morten at ngb.se">Morten Hulden</a>
-<p>
-Datum tranformation support and cleanup by Paul Kelly
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.proj/r.proj.html (from rev 32770, grass/trunk/raster/r.proj/description.html)
===================================================================
--- grass/trunk/raster/r.proj/r.proj.html (rev 0)
+++ grass/trunk/raster/r.proj/r.proj.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,197 @@
+<h2>DESCRIPTION</h2>
+
+
+<em>r.proj</em> projects a raster map in a specified mapset of a
+specified location from the projection of the input location to a raster map
+in the current location. The projection information is taken from the
+current PROJ_INFO files, as set with <i><a href="g.setproj.html">g.setproj</a>
+</i> and viewed with <i><a href="g.proj.html">g.proj</a></i>.
+
+<h4>Introduction</h4>
+
+<h5>Map projections</h5>
+
+Map projections are a method of representing information from a
+curved surface (usually a spheroid) in two dimensions, typically to allow
+indexing through cartesian coordinates. There are a wide variety of
+projections, with common ones divided into a number of classes, including
+cylindrical and pseudo-cylindrical, conic and pseudo-conic, and azimuthal
+methods, each of which may be conformal, equal-area, or neither.
+<p>
+The particular projection chosen depends on the purpose of the project,
+and the size, shape and location of the area of interest. For example,
+normal cylindrical projections are good for maps which are of greater extent
+east-west than north-south and in equatorial regions, while conic
+projections are better in mid-latitudes; transverse cylindrical projections
+are used for maps which are of greater extent north-south than east-west;
+azimuthal projections are used for polar regions. Oblique versions of any
+of these may also be used. Conformal projections preserve angular
+relationships, and better preserve arc-length, while equal-area projections
+are more appropriate for statistical studies and work in which the amount of
+material is important.
+<p>
+Projections are defined by precise mathematical relations, so the method
+of projecting coordinates from a geographic reference frame
+(latitude-longitude) into a projected cartesian reference frame (eg metres)
+is governed by these equations. Inverse projections can also be achieved.
+The public-domain Unix software package <i>PROJ</i> [1] has been designed to
+perform these transformations, and the user's manual contains a detailed
+description of over 100 useful projections. This also includes a
+programmers library of the projection methods to support other software
+development.
+<p>
+Thus, converting a vector map - in which objects are located
+with arbitrary spatial precision - from one projection into another is
+usually accomplished by a simple two-step process: first the location of
+all the points in the map are converted from the source through an inverse
+projection into latitude-longitude, and then through a forward projection
+into the target. (Of course the procedure will be one-step if either the
+source or target is in geographic coordinates.)
+<p>
+Converting a raster map, or image, between different projections,
+however, involves additional considerations.
+A raster may be considered to represent a sampling of a
+process at a regular, ordered set of locations. The set of locations that
+lie at the intersections of a cartesian grid in one projection will not, in
+general, coincide with the sample points in another projection. Thus, the
+conversion of raster maps involves an interpolation step in which the values
+of points at intermediate locations relative to the source grid are
+estimated.
+
+<h5>Projecting vector maps within the GRASS GIS</h5>
+<!-- move this into v.proj.html !! -->
+GIS data capture, import and transfer often requires a projection
+step, since the source or client will frequently be in a different
+projection to the working projection.
+<p>
+In some cases it is convenient to do the conversion outside the package,
+prior to import or after export, using software such as <i>PROJ.4</i>'s
+<i><a href="http://proj.maptools.org/">cs2cs</a></i> [1]. This is an easy
+method for converting an ASCII file containing a list of coordinate points,
+since there is no topology to be preserved and <i>cs2cs</i> can be used to
+process simple lists using a one-line command.
+<p>
+The format of files containg vector maps with <b>lines</b> and <b>arcs</b> is
+generally more complex, as parts of the data stored in the files will describe
+topology, and not just coordinates. In GRASS GIS the
+<i><a href="v.proj.html">v.proj</a></i> module is provided to reproject
+vector maps, transferring topology and attributes as well as node coordinates.
+This program uses the projection definition and parameters which are stored in
+the PROJ_INFO and PROJ_UNITS files in the PERMANENT mapset directory for every
+GRASS location.
+<br><br>
+
+<h4>Design of r.proj</h4>
+
+As discussed briefly above, the fundamental step in re-projecting a
+raster is resampling the source grid at locations corresponding to the
+intersections of a grid in the target projection. The basic procedure for
+accomplishing this, therefore, is as follows:
+<p>
+<em>r.proj</em> converts a map to a new geographic projection. It reads a
+map from a different location, projects it and write it out to the current
+location.
+<br>
+The projected data is resampled with one of three different methods:
+nearest neighbor, bilinear and cubic convolution.
+<p>
+The <em>method=nearest</em>, which performs a nearest neighbor assignment,
+is the fastest of the three resampling methods. It is primarily used for
+categorical data such as a land use classification, since it will not change
+the values of the data cells. The <em>method=bilinear</em> determines the new
+value of the cell based on a weighted distance average of the 4 surrounding
+cells in the input map. The <em>method=cubic</em> determines the new value of
+the cell based on a weighted distance average of the 16 surrounding cells in
+the input map.
+<p>
+The bilinear and cubic interpolation methods are most appropriate for
+continuous data and cause some smoothing. Both options should not be used
+with categorical data, since the cell values will be altered.
+<p>
+If nearest neighbor assignment is used, the output map has the same raster
+format as the input map. If any of the both interpolations is used, the
+output map is written as floating point.
+
+<p>
+Note that, following normal GRASS conventions, the coverage and
+resolution of the resulting grid is set by the current region settings,
+which may be adjusted using <i>g.region</i>. The target raster will be
+relatively unbiased for all cases if its grid has a similar resolution to
+the source, so that the resampling/interpolation step is only a local
+operation. If the resolution is changed significantly, then the behaviour
+of the generalisation or refinement will depend on the model of the process
+being represented. This will be very different for categorical versus
+numerical data. Note that three methods for the local interpolation step
+are provided.
+
+<p>
+<em>r.proj</em> supports general datum transformations, making use of the
+<em>PROJ.4</em> co-ordinate system translation library.
+</p>
+
+<h2>NOTES</h2>
+
+To avoid excessive time consumption when reprojecting a map the region and
+resolution of the target location should be set appropriately beforehand.
+A simple way to do this is to generate a vector "box" map of the region in
+the source location using <em><a href="v.in.region.html">v.in.region</a></em>.
+This "box" map is then reprojected into the target location with
+<em><a href="v.proj.html">v.proj</a></em>.
+Next the region in the target location is set to the extent of the new vector
+map with <em><a href="g.region.html">g.region</a></em> along with the desired
+raster resolution (<em>g.region -m</em> can be used in Latitude/Longitude
+locations to measure the geodetic length of a pixel).
+<em>r.proj</em> is then run for the raster map the user wants to reproject.
+In this case a little preparation goes a long way.
+<p>
+When reprojecting whole-world maps the user should disable map-trimming with
+the <em>-n</em> flag. Trimming is not useful here because the module has the
+whole map in memory anyway. Besides that, world "edges" are hard (or
+impossible) to find in projections other than latitude-longitude so results
+may be odd with trimming.
+
+<h2>REFERENCES</h2>
+
+[1] Evenden, G.I. (1990) <a href="http://proj.maptools.org/">Cartographic projection procedures for
+the UNIX environment - a user's manual.</a> USGS Open-File Report 90-284 (OF90-284.pdf)
+See also there: Interim Report and 2nd Interim Report on Release 4, Evenden 1994).
+<p>
+Richards, John A. (1993), Remote Sensing Digital Image Analysis,
+Springer-Verlag, Berlin, 2nd edition.
+<p>
+<a href=http://proj.maptools.org/>PROJ.4</a>: Projection/datum support library.
+<p>
+<b>Further reading</b>
+<ul>
+<li> <a href="http://www.asprs.org/resources/grids/">ASPRS Grids and Datum</a>
+<li> <a href="http://www.remotesensing.org/geotiff/proj_list/">Projections Transform List</a> (PROJ.4)
+<li> <a href="http://www.mapref.org">MapRef - The Collection of Map Projections and Reference Systems for Europe</a>
+<li> <a href="http://crs.bkg.bund.de/crs-eu/">Information and Service System for European Coordinate Reference Systems - CRS</a>
+</ul>
+
+<h2>SEE ALSO</h2>
+
+<em>
+<a href="g.region.html">g.region</a>,
+<a href="g.proj.html">g.proj</a>,
+<a href="g.setproj.html">g.setproj</a>,
+<a href="i.rectify.html">i.rectify</a>,
+<a href="r.support.html">r.support</a>,
+<a href="r.stats.html">r.stats</a>,
+<a href="v.proj.html">v.proj</a>,
+<a href="v.in.region.html">v.in.region</a>
+</em>
+<p>
+The 'gdalwarp' and 'gdal_translate' utilities are available from the
+<a href="http://www.gdal.org">GDAL</a> project.
+
+<h2>AUTHORS</h2>
+
+Martin Schroeder, University of Heidelberg, Germany<p>
+Man page text from S.J.D. Cox, AGCRC, CSIRO Exploration & Mining, Nedlands, WA
+<p>
+Updated by <a href="mailto:morten at ngb.se">Morten Hulden</a>
+<p>
+Datum tranformation support and cleanup by Paul Kelly
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.proj.seg/description.html
===================================================================
--- grass/trunk/raster/r.proj.seg/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.proj.seg/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,197 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-
-<em>r.proj</em> projects a raster map in a specified mapset of a
-specified location from the projection of the input location to a raster map
-in the current location. The projection information is taken from the
-current PROJ_INFO files, as set with <i><a href="g.setproj.html">g.setproj</a>
-</i> and viewed with <i><a href="g.proj.html">g.proj</a></i>.
-
-<h4>Introduction</h4>
-
-<h5>Map projections</h5>
-
-Map projections are a method of representing information from a
-curved surface (usually a spheroid) in two dimensions, typically to allow
-indexing through cartesian coordinates. There are a wide variety of
-projections, with common ones divided into a number of classes, including
-cylindrical and pseudo-cylindrical, conic and pseudo-conic, and azimuthal
-methods, each of which may be conformal, equal-area, or neither.
-<p>
-The particular projection chosen depends on the purpose of the project,
-and the size, shape and location of the area of interest. For example,
-normal cylindrical projections are good for maps which are of greater extent
-east-west than north-south and in equatorial regions, while conic
-projections are better in mid-latitudes; transverse cylindrical projections
-are used for maps which are of greater extent north-south than east-west;
-azimuthal projections are used for polar regions. Oblique versions of any
-of these may also be used. Conformal projections preserve angular
-relationships, and better preserve arc-length, while equal-area projections
-are more appropriate for statistical studies and work in which the amount of
-material is important.
-<p>
-Projections are defined by precise mathematical relations, so the method
-of projecting coordinates from a geographic reference frame
-(latitude-longitude) into a projected cartesian reference frame (eg metres)
-is governed by these equations. Inverse projections can also be achieved.
-The public-domain Unix software package <i>PROJ</i> [1] has been designed to
-perform these transformations, and the user's manual contains a detailed
-description of over 100 useful projections. This also includes a
-programmers library of the projection methods to support other software
-development.
-<p>
-Thus, converting a vector map - in which objects are located
-with arbitrary spatial precision - from one projection into another is
-usually accomplished by a simple two-step process: first the location of
-all the points in the map are converted from the source through an inverse
-projection into latitude-longitude, and then through a forward projection
-into the target. (Of course the procedure will be one-step if either the
-source or target is in geographic coordinates.)
-<p>
-Converting a raster map, or image, between different projections,
-however, involves additional considerations.
-A raster may be considered to represent a sampling of a
-process at a regular, ordered set of locations. The set of locations that
-lie at the intersections of a cartesian grid in one projection will not, in
-general, coincide with the sample points in another projection. Thus, the
-conversion of raster maps involves an interpolation step in which the values
-of points at intermediate locations relative to the source grid are
-estimated.
-
-<h5>Projecting vector maps within the GRASS GIS</h5>
-<!-- move this into v.proj.html !! -->
-GIS data capture, import and transfer often requires a projection
-step, since the source or client will frequently be in a different
-projection to the working projection.
-<p>
-In some cases it is convenient to do the conversion outside the package,
-prior to import or after export, using software such as <i>PROJ.4</i>'s
-<i><a href="http://proj.maptools.org/">cs2cs</a></i> [1]. This is an easy
-method for converting an ASCII file containing a list of coordinate points,
-since there is no topology to be preserved and <i>cs2cs</i> can be used to
-process simple lists using a one-line command.
-<p>
-The format of files containing vector maps with <b>lines</b> and <b>arcs</b> is
-generally more complex, as parts of the data stored in the files will describe
-topology, and not just coordinates. In GRASS GIS the
-<i><a href="v.proj.html">v.proj</a></i> module is provided to reproject
-vector maps, transferring topology and attributes as well as node coordinates.
-This program uses the projection definition and parameters which are stored in
-the PROJ_INFO and PROJ_UNITS files in the PERMANENT mapset directory for every
-GRASS location.
-<br><br>
-
-<h4>Design of r.proj</h4>
-
-As discussed briefly above, the fundamental step in re-projecting a
-raster is resampling the source grid at locations corresponding to the
-intersections of a grid in the target projection. The basic procedure for
-accomplishing this, therefore, is as follows:
-<p>
-<em>r.proj</em> converts a map to a new geographic projection. It reads a
-map from a different location, projects it and write it out to the current
-location.
-<br>
-The projected data is resampled with one of three different methods:
-nearest neighbor, bilinear and cubic convolution.
-<p>
-The <em>method=nearest</em> method, which performs a nearest neighbor assignment,
-is the fastest of the three resampling methods. It is primarily used for
-categorical data such as a land use classification, since it will not change
-the values of the data cells. The <em>method=bilinear</em> method determines the new
-value of the cell based on a weighted distance average of the 4 surrounding
-cells in the input map. The <em>method=cubic</em> method determines the new value of
-the cell based on a weighted distance average of the 16 surrounding cells in
-the input map.
-<p>
-The bilinear and cubic interpolation methods are most appropriate for
-continuous data and cause some smoothing. Both options should not be used
-with categorical data, since the cell values will be altered.
-<p>
-If nearest neighbor assignment is used, the output map has the same raster
-format as the input map. If any of the both interpolations is used, the
-output map is written as floating point.
-
-<p>
-Note that, following normal GRASS conventions, the coverage and
-resolution of the resulting grid is set by the current region settings,
-which may be adjusted using <i>g.region</i>. The target raster will be
-relatively unbiased for all cases if its grid has a similar resolution to
-the source, so that the resampling/interpolation step is only a local
-operation. If the resolution is changed significantly, then the behaviour
-of the generalisation or refinement will depend on the model of the process
-being represented. This will be very different for categorical versus
-numerical data. Note that three methods for the local interpolation step
-are provided.
-
-<p>
-<em>r.proj</em> supports general datum transformations, making use of the
-<em>PROJ.4</em> co-ordinate system translation library.
-</p>
-
-<h2>NOTES</h2>
-
-To avoid excessive time consumption when reprojecting a map the region and
-resolution of the target location should be set appropriately beforehand.
-A simple way to do this is to generate a vector "box" map of the region in
-the source location using <em><a href="v.in.region.html">v.in.region</a></em>.
-This "box" map is then reprojected into the target location with
-<em><a href="v.proj.html">v.proj</a></em>.
-Next the region in the target location is set to the extent of the new vector
-map with <em><a href="g.region.html">g.region</a></em> along with the desired
-raster resolution (<em>g.region -m</em> can be used in Latitude/Longitude
-locations to measure the geodetic length of a pixel).
-<em>r.proj</em> is then run for the raster map the user wants to reproject.
-In this case a little preparation goes a long way.
-<p>
-When reprojecting whole-world maps the user should disable map-trimming with
-the <em>-n</em> flag. Trimming is not useful here because the module has the
-whole map in memory anyway. Besides that, world "edges" are hard (or
-impossible) to find in projections other than latitude-longitude so results
-may be odd with trimming.
-
-<h2>REFERENCES</h2>
-
-[1] Evenden, G.I. (1990) <a href="http://proj.maptools.org/">Cartographic projection procedures for
-the UNIX environment - a user's manual.</a> USGS Open-File Report 90-284 (OF90-284.pdf)
-See also there: Interim Report and 2nd Interim Report on Release 4, Evenden 1994).
-<p>
-Richards, John A. (1993), Remote Sensing Digital Image Analysis,
-Springer-Verlag, Berlin, 2nd edition.
-<p>
-<a href=http://proj.maptools.org/>PROJ.4</a>: Projection/datum support library.
-<p>
-<b>Further reading</b>
-<ul>
-<li> <a href="http://www.asprs.org/resources/grids/">ASPRS Grids and Datum</a>
-<li> <a href="http://www.remotesensing.org/geotiff/proj_list/">Projections Transform List</a> (PROJ.4)
-<li> <a href="http://www.mapref.org">MapRef - The Collection of Map Projections and Reference Systems for Europe</a>
-<li> <a href="http://crs.bkg.bund.de/crs-eu/">Information and Service System for European Coordinate Reference Systems - CRS</a>
-</ul>
-
-<h2>SEE ALSO</h2>
-
-<em>
-<a href="g.region.html">g.region</a>,
-<a href="g.proj.html">g.proj</a>,
-<a href="g.setproj.html">g.setproj</a>,
-<a href="i.rectify.html">i.rectify</a>,
-<a href="r.support.html">r.support</a>,
-<a href="r.stats.html">r.stats</a>,
-<a href="v.proj.html">v.proj</a>,
-<a href="v.in.region.html">v.in.region</a>
-</em>
-<p>
-The 'gdalwarp' and 'gdal_translate' utilities are available from the
-<a href="http://www.gdal.org">GDAL</a> project.
-
-<h2>AUTHORS</h2>
-
-Martin Schroeder, University of Heidelberg, Germany<p>
-Man page text from S.J.D. Cox, AGCRC, CSIRO Exploration & Mining, Nedlands, WA
-<p>
-Updated by <a href="mailto:morten at ngb.se">Morten Hulden</a>
-<p>
-Datum tranformation support and cleanup by Paul Kelly
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.proj.seg/r.proj.html (from rev 32770, grass/trunk/raster/r.proj.seg/description.html)
===================================================================
--- grass/trunk/raster/r.proj.seg/r.proj.html (rev 0)
+++ grass/trunk/raster/r.proj.seg/r.proj.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,197 @@
+<h2>DESCRIPTION</h2>
+
+
+<em>r.proj</em> projects a raster map in a specified mapset of a
+specified location from the projection of the input location to a raster map
+in the current location. The projection information is taken from the
+current PROJ_INFO files, as set with <i><a href="g.setproj.html">g.setproj</a>
+</i> and viewed with <i><a href="g.proj.html">g.proj</a></i>.
+
+<h4>Introduction</h4>
+
+<h5>Map projections</h5>
+
+Map projections are a method of representing information from a
+curved surface (usually a spheroid) in two dimensions, typically to allow
+indexing through cartesian coordinates. There are a wide variety of
+projections, with common ones divided into a number of classes, including
+cylindrical and pseudo-cylindrical, conic and pseudo-conic, and azimuthal
+methods, each of which may be conformal, equal-area, or neither.
+<p>
+The particular projection chosen depends on the purpose of the project,
+and the size, shape and location of the area of interest. For example,
+normal cylindrical projections are good for maps which are of greater extent
+east-west than north-south and in equatorial regions, while conic
+projections are better in mid-latitudes; transverse cylindrical projections
+are used for maps which are of greater extent north-south than east-west;
+azimuthal projections are used for polar regions. Oblique versions of any
+of these may also be used. Conformal projections preserve angular
+relationships, and better preserve arc-length, while equal-area projections
+are more appropriate for statistical studies and work in which the amount of
+material is important.
+<p>
+Projections are defined by precise mathematical relations, so the method
+of projecting coordinates from a geographic reference frame
+(latitude-longitude) into a projected cartesian reference frame (eg metres)
+is governed by these equations. Inverse projections can also be achieved.
+The public-domain Unix software package <i>PROJ</i> [1] has been designed to
+perform these transformations, and the user's manual contains a detailed
+description of over 100 useful projections. This also includes a
+programmers library of the projection methods to support other software
+development.
+<p>
+Thus, converting a vector map - in which objects are located
+with arbitrary spatial precision - from one projection into another is
+usually accomplished by a simple two-step process: first the location of
+all the points in the map are converted from the source through an inverse
+projection into latitude-longitude, and then through a forward projection
+into the target. (Of course the procedure will be one-step if either the
+source or target is in geographic coordinates.)
+<p>
+Converting a raster map, or image, between different projections,
+however, involves additional considerations.
+A raster may be considered to represent a sampling of a
+process at a regular, ordered set of locations. The set of locations that
+lie at the intersections of a cartesian grid in one projection will not, in
+general, coincide with the sample points in another projection. Thus, the
+conversion of raster maps involves an interpolation step in which the values
+of points at intermediate locations relative to the source grid are
+estimated.
+
+<h5>Projecting vector maps within the GRASS GIS</h5>
+<!-- move this into v.proj.html !! -->
+GIS data capture, import and transfer often requires a projection
+step, since the source or client will frequently be in a different
+projection to the working projection.
+<p>
+In some cases it is convenient to do the conversion outside the package,
+prior to import or after export, using software such as <i>PROJ.4</i>'s
+<i><a href="http://proj.maptools.org/">cs2cs</a></i> [1]. This is an easy
+method for converting an ASCII file containing a list of coordinate points,
+since there is no topology to be preserved and <i>cs2cs</i> can be used to
+process simple lists using a one-line command.
+<p>
+The format of files containing vector maps with <b>lines</b> and <b>arcs</b> is
+generally more complex, as parts of the data stored in the files will describe
+topology, and not just coordinates. In GRASS GIS the
+<i><a href="v.proj.html">v.proj</a></i> module is provided to reproject
+vector maps, transferring topology and attributes as well as node coordinates.
+This program uses the projection definition and parameters which are stored in
+the PROJ_INFO and PROJ_UNITS files in the PERMANENT mapset directory for every
+GRASS location.
+<br><br>
+
+<h4>Design of r.proj</h4>
+
+As discussed briefly above, the fundamental step in re-projecting a
+raster is resampling the source grid at locations corresponding to the
+intersections of a grid in the target projection. The basic procedure for
+accomplishing this, therefore, is as follows:
+<p>
+<em>r.proj</em> converts a map to a new geographic projection. It reads a
+map from a different location, projects it and write it out to the current
+location.
+<br>
+The projected data is resampled with one of three different methods:
+nearest neighbor, bilinear and cubic convolution.
+<p>
+The <em>method=nearest</em> method, which performs a nearest neighbor assignment,
+is the fastest of the three resampling methods. It is primarily used for
+categorical data such as a land use classification, since it will not change
+the values of the data cells. The <em>method=bilinear</em> method determines the new
+value of the cell based on a weighted distance average of the 4 surrounding
+cells in the input map. The <em>method=cubic</em> method determines the new value of
+the cell based on a weighted distance average of the 16 surrounding cells in
+the input map.
+<p>
+The bilinear and cubic interpolation methods are most appropriate for
+continuous data and cause some smoothing. Both options should not be used
+with categorical data, since the cell values will be altered.
+<p>
+If nearest neighbor assignment is used, the output map has the same raster
+format as the input map. If any of the both interpolations is used, the
+output map is written as floating point.
+
+<p>
+Note that, following normal GRASS conventions, the coverage and
+resolution of the resulting grid is set by the current region settings,
+which may be adjusted using <i>g.region</i>. The target raster will be
+relatively unbiased for all cases if its grid has a similar resolution to
+the source, so that the resampling/interpolation step is only a local
+operation. If the resolution is changed significantly, then the behaviour
+of the generalisation or refinement will depend on the model of the process
+being represented. This will be very different for categorical versus
+numerical data. Note that three methods for the local interpolation step
+are provided.
+
+<p>
+<em>r.proj</em> supports general datum transformations, making use of the
+<em>PROJ.4</em> co-ordinate system translation library.
+</p>
+
+<h2>NOTES</h2>
+
+To avoid excessive time consumption when reprojecting a map the region and
+resolution of the target location should be set appropriately beforehand.
+A simple way to do this is to generate a vector "box" map of the region in
+the source location using <em><a href="v.in.region.html">v.in.region</a></em>.
+This "box" map is then reprojected into the target location with
+<em><a href="v.proj.html">v.proj</a></em>.
+Next the region in the target location is set to the extent of the new vector
+map with <em><a href="g.region.html">g.region</a></em> along with the desired
+raster resolution (<em>g.region -m</em> can be used in Latitude/Longitude
+locations to measure the geodetic length of a pixel).
+<em>r.proj</em> is then run for the raster map the user wants to reproject.
+In this case a little preparation goes a long way.
+<p>
+When reprojecting whole-world maps the user should disable map-trimming with
+the <em>-n</em> flag. Trimming is not useful here because the module has the
+whole map in memory anyway. Besides that, world "edges" are hard (or
+impossible) to find in projections other than latitude-longitude so results
+may be odd with trimming.
+
+<h2>REFERENCES</h2>
+
+[1] Evenden, G.I. (1990) <a href="http://proj.maptools.org/">Cartographic projection procedures for
+the UNIX environment - a user's manual.</a> USGS Open-File Report 90-284 (OF90-284.pdf)
+See also there: Interim Report and 2nd Interim Report on Release 4, Evenden 1994).
+<p>
+Richards, John A. (1993), Remote Sensing Digital Image Analysis,
+Springer-Verlag, Berlin, 2nd edition.
+<p>
+<a href=http://proj.maptools.org/>PROJ.4</a>: Projection/datum support library.
+<p>
+<b>Further reading</b>
+<ul>
+<li> <a href="http://www.asprs.org/resources/grids/">ASPRS Grids and Datum</a>
+<li> <a href="http://www.remotesensing.org/geotiff/proj_list/">Projections Transform List</a> (PROJ.4)
+<li> <a href="http://www.mapref.org">MapRef - The Collection of Map Projections and Reference Systems for Europe</a>
+<li> <a href="http://crs.bkg.bund.de/crs-eu/">Information and Service System for European Coordinate Reference Systems - CRS</a>
+</ul>
+
+<h2>SEE ALSO</h2>
+
+<em>
+<a href="g.region.html">g.region</a>,
+<a href="g.proj.html">g.proj</a>,
+<a href="g.setproj.html">g.setproj</a>,
+<a href="i.rectify.html">i.rectify</a>,
+<a href="r.support.html">r.support</a>,
+<a href="r.stats.html">r.stats</a>,
+<a href="v.proj.html">v.proj</a>,
+<a href="v.in.region.html">v.in.region</a>
+</em>
+<p>
+The 'gdalwarp' and 'gdal_translate' utilities are available from the
+<a href="http://www.gdal.org">GDAL</a> project.
+
+<h2>AUTHORS</h2>
+
+Martin Schroeder, University of Heidelberg, Germany<p>
+Man page text from S.J.D. Cox, AGCRC, CSIRO Exploration & Mining, Nedlands, WA
+<p>
+Updated by <a href="mailto:morten at ngb.se">Morten Hulden</a>
+<p>
+Datum tranformation support and cleanup by Paul Kelly
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.quant/description.html
===================================================================
--- grass/trunk/raster/r.quant/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.quant/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,36 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>r.quant</em> produces the quantization file for a floating-point map.
-<p>
-
-The <em>map</em> parameter defines the map for which the rules be to be
-created. If more than one map is specified, then this implies that the
-floating-point range is the miniumum and maximum of all the maps together,
-unless either basemap=map or fprange=min,max is specified.
-
-<h2> Quant rules </h2>
-
-The quant rules have to be entered interactively.
-<p>
-If rules is specified, the input has the form: <p>
-
- value1:value2:cat1:[cat2] <p>
-
-where value1 and value2 are floating point values and cat1 cand cat2 are
-integers. If cat2 is missing, it is taken to be equal to cat1. All values
-can be "*" which means infinity.
-
-<h2>NOTE</h2>
-It is an error for both basemap and fprange to be specified.
-
-<h2>SEE ALSO</h2>
-
-<em><a href="r.support.html">r.support</a></em>,
-<em><a href="r.null.html">r.null</a></em>
-
-<h2>AUTHOR</h2>
-
-Michael Shapiro, Olga Waupotitsch,
-U.S.Army Construction Engineering Research Laboratory
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.quant/r.quant.html (from rev 32770, grass/trunk/raster/r.quant/description.html)
===================================================================
--- grass/trunk/raster/r.quant/r.quant.html (rev 0)
+++ grass/trunk/raster/r.quant/r.quant.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,36 @@
+<h2>DESCRIPTION</h2>
+
+<em>r.quant</em> produces the quantization file for a floating-point map.
+<p>
+
+The <em>map</em> parameter defines the map for which the rules be to be
+created. If more than one map is specified, then this implies that the
+floating-point range is the miniumum and maximum of all the maps together,
+unless either basemap=map or fprange=min,max is specified.
+
+<h2> Quant rules </h2>
+
+The quant rules have to be entered interactively.
+<p>
+If rules is specified, the input has the form: <p>
+
+ value1:value2:cat1:[cat2] <p>
+
+where value1 and value2 are floating point values and cat1 cand cat2 are
+integers. If cat2 is missing, it is taken to be equal to cat1. All values
+can be "*" which means infinity.
+
+<h2>NOTE</h2>
+It is an error for both basemap and fprange to be specified.
+
+<h2>SEE ALSO</h2>
+
+<em><a href="r.support.html">r.support</a></em>,
+<em><a href="r.null.html">r.null</a></em>
+
+<h2>AUTHOR</h2>
+
+Michael Shapiro, Olga Waupotitsch,
+U.S.Army Construction Engineering Research Laboratory
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.quantile/description.html
===================================================================
--- grass/trunk/raster/r.quantile/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.quantile/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,17 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>r.quantile</em> computes quantiles in a manner suitable for use with large amounts of data.
-It is using two passes.
-
-<h2>SEE ALSO</h2>
-
-<em>
-<a href="r.quant.html">r.quant</a>
-</em>
-
-
-<h2>AUTHOR</h2>
-
-Glynn Clements <glynn gclements.plus.com>
-<p>
-<i>Last changed: $Date: 2007-04-06 21:49:26 +0200 (Fri, 06 Apr 2007) $</i>
Copied: grass/trunk/raster/r.quantile/r.quantile.html (from rev 32770, grass/trunk/raster/r.quantile/description.html)
===================================================================
--- grass/trunk/raster/r.quantile/r.quantile.html (rev 0)
+++ grass/trunk/raster/r.quantile/r.quantile.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,17 @@
+<h2>DESCRIPTION</h2>
+
+<em>r.quantile</em> computes quantiles in a manner suitable for use with large amounts of data.
+It is using two passes.
+
+<h2>SEE ALSO</h2>
+
+<em>
+<a href="r.quant.html">r.quant</a>
+</em>
+
+
+<h2>AUTHOR</h2>
+
+Glynn Clements <glynn gclements.plus.com>
+<p>
+<i>Last changed: $Date: 2007-04-06 21:49:26 +0200 (Fri, 06 Apr 2007) $</i>
Deleted: grass/trunk/raster/r.random/description.html
===================================================================
--- grass/trunk/raster/r.random/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.random/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,127 +0,0 @@
-<h2>DESCRIPTION</h2>
-<p>
-The program <em>r.random</em> allows the user to create a
-raster map layer and/or a vector points map containing
-coordinates of points whose locations have been randomly
-determined. The program locates these randomly generated
-vector points (sites) within the current geographic region and mask (if
-any), on non-NULL category value data areas within a
-user-specified raster map layer. If the user sets the
-<b>-z</b> flag, points will be randomly generated across all
-cells (even those with NULL values).
-
-<p>
-The category values and
-corresponding category names already associated with the
-random point locations in the <em>input</em> map layer are
-assigned to these points in the <em>raster_output</em> map
-layer. If the <b>-z</b> is specified, then a unique entry
-is made for the value used where the <em>input</em> was NULL.
-This value is at least 1 less than the smallest value in the
-<em>input</em> raster and is given a medium gray color.
-
-<h2>NOTES</h2>
-<p>
-If a <em>cover</em> raster map is specified and the <em>cover</em> map
-contains NULL (no data) values, these points are suppressed in the
-resulting <em>vector_output</em> or <em>raster_output</em> map.
-
-<p>
-The <em>vector_output</em> file created by <em>r.random</em>
-contains vector points that represent the <em>center points</em> of the
-randomly generated cells. A <em>value</em> attribute contains the cell value
-of the <em>input</em> raster (or the assigned value
-when <b>-z</b> is used). <br>
-If a <em>cover</em> map is additionally specified, a second
-column <em>covervalue</em> is populated with raster values from
-the <em>cover</em> map.
-
-<p>
-The user may specify the quantity of random locations to be
-generated either as a <em>positive integer</em> (e.g., 10),
-or as a <em>percentage of the raster map layer's cells</em>
-(e.g., 10%, or 3.05%). The number of cells considered for
-the percentage reflects whether or not the <b>-z</b> flag
-was given. Options are 0-100; percentages less than
-one percent may be stated as decimals.
-
-<p>
-Flag <b>-i</b> prints the raster map's name and location,
-the total number of cells under the current region settings, and
-the number of NULL valued cells under the current region settings.
-Then module exits without doing anything. Useful for deciding on the number
-of sites to have <em>r.random</em> create.
-<b>WARNING:</b> this feature may be removed in future. Use
-<a href="g.region.html">g.region</a> and
-<a href="r.report.html">r.report</a>
-instead.
-<div class="code"><pre>
-g.region -p
-r.report map=inputmap units=c null=* nsteps=1
-</pre></div>
-
-<p>
-To create random vector point locations within some, but not all,
-non-zero categories of the input raster map layer,
-the user must first create a reclassified raster map layer
-of the original raster map layer (e.g., using the GRASS
-program <em><a href="r.reclass.html">r.reclass</a></em>)
-that contains only the desired categories,
-and then use the reclassed raster map layer as input to <em>r.random</em>.
-
-<h2>EXAMPLES</h2>
-<p>
-Random vector elevation points sampled from elevation map in the
-Spearfish region, result stored in 2D vector map:
-
-<div class="code"><pre>
-g.region rast=elevation.10m -p
-r.random elevation.10m vector_output=elevrand n=100
-v.db.select elevrand
-v.univar elevrand col=value type=point
-</pre></div>
-
-
-<p>
-Random vector elevation points sampled from elevation map in the
-Spearfish region with collocated values sampled from landuse map,
-result stored in 3D vector map:
-
-<div class="code"><pre>
-g.region rast=elevation.10m -p
-r.random -d elevation.10m cover=landcover.30m vector_output=luserand3d n=100
-
-# data output (value: elevation, covervalue: landuse class):
-v.db.select luserand3d
-cat|value|covervalue
-1|1151.406616|81
-2|1172.121216|71
-3|1183.219604|71
-...
-</pre></div>
-
-<h2>BUGS</h2>
-
-It's not possible to use the <b>-i</b> flag and not also specify the <b>n</b>
-parameter.
-
-
-<h2>SEE ALSO</h2>
-
-<em><a href="g.region.html">g.region</a></em><br>
-<em><a href="r.reclass.html">r.reclass</a></em><br>
-<em><a href="v.random.html">v.random</a></em><br>
-
-
-<h2>AUTHOR</h2>
-
-Dr. James Hinthorne,
-GIS Laboratory,
-Central Washington University
-<p>
-Modified for GRASS 5.0 by Eric G. Miller
-<p>
-Cover map support by Markus Neteler, 2007
-
-<p>
-<i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.random/r.random.html (from rev 32770, grass/trunk/raster/r.random/description.html)
===================================================================
--- grass/trunk/raster/r.random/r.random.html (rev 0)
+++ grass/trunk/raster/r.random/r.random.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,127 @@
+<h2>DESCRIPTION</h2>
+<p>
+The program <em>r.random</em> allows the user to create a
+raster map layer and/or a vector points map containing
+coordinates of points whose locations have been randomly
+determined. The program locates these randomly generated
+vector points (sites) within the current geographic region and mask (if
+any), on non-NULL category value data areas within a
+user-specified raster map layer. If the user sets the
+<b>-z</b> flag, points will be randomly generated across all
+cells (even those with NULL values).
+
+<p>
+The category values and
+corresponding category names already associated with the
+random point locations in the <em>input</em> map layer are
+assigned to these points in the <em>raster_output</em> map
+layer. If the <b>-z</b> is specified, then a unique entry
+is made for the value used where the <em>input</em> was NULL.
+This value is at least 1 less than the smallest value in the
+<em>input</em> raster and is given a medium gray color.
+
+<h2>NOTES</h2>
+<p>
+If a <em>cover</em> raster map is specified and the <em>cover</em> map
+contains NULL (no data) values, these points are suppressed in the
+resulting <em>vector_output</em> or <em>raster_output</em> map.
+
+<p>
+The <em>vector_output</em> file created by <em>r.random</em>
+contains vector points that represent the <em>center points</em> of the
+randomly generated cells. A <em>value</em> attribute contains the cell value
+of the <em>input</em> raster (or the assigned value
+when <b>-z</b> is used). <br>
+If a <em>cover</em> map is additionally specified, a second
+column <em>covervalue</em> is populated with raster values from
+the <em>cover</em> map.
+
+<p>
+The user may specify the quantity of random locations to be
+generated either as a <em>positive integer</em> (e.g., 10),
+or as a <em>percentage of the raster map layer's cells</em>
+(e.g., 10%, or 3.05%). The number of cells considered for
+the percentage reflects whether or not the <b>-z</b> flag
+was given. Options are 0-100; percentages less than
+one percent may be stated as decimals.
+
+<p>
+Flag <b>-i</b> prints the raster map's name and location,
+the total number of cells under the current region settings, and
+the number of NULL valued cells under the current region settings.
+Then module exits without doing anything. Useful for deciding on the number
+of sites to have <em>r.random</em> create.
+<b>WARNING:</b> this feature may be removed in future. Use
+<a href="g.region.html">g.region</a> and
+<a href="r.report.html">r.report</a>
+instead.
+<div class="code"><pre>
+g.region -p
+r.report map=inputmap units=c null=* nsteps=1
+</pre></div>
+
+<p>
+To create random vector point locations within some, but not all,
+non-zero categories of the input raster map layer,
+the user must first create a reclassified raster map layer
+of the original raster map layer (e.g., using the GRASS
+program <em><a href="r.reclass.html">r.reclass</a></em>)
+that contains only the desired categories,
+and then use the reclassed raster map layer as input to <em>r.random</em>.
+
+<h2>EXAMPLES</h2>
+<p>
+Random vector elevation points sampled from elevation map in the
+Spearfish region, result stored in 2D vector map:
+
+<div class="code"><pre>
+g.region rast=elevation.10m -p
+r.random elevation.10m vector_output=elevrand n=100
+v.db.select elevrand
+v.univar elevrand col=value type=point
+</pre></div>
+
+
+<p>
+Random vector elevation points sampled from elevation map in the
+Spearfish region with collocated values sampled from landuse map,
+result stored in 3D vector map:
+
+<div class="code"><pre>
+g.region rast=elevation.10m -p
+r.random -d elevation.10m cover=landcover.30m vector_output=luserand3d n=100
+
+# data output (value: elevation, covervalue: landuse class):
+v.db.select luserand3d
+cat|value|covervalue
+1|1151.406616|81
+2|1172.121216|71
+3|1183.219604|71
+...
+</pre></div>
+
+<h2>BUGS</h2>
+
+It's not possible to use the <b>-i</b> flag and not also specify the <b>n</b>
+parameter.
+
+
+<h2>SEE ALSO</h2>
+
+<em><a href="g.region.html">g.region</a></em><br>
+<em><a href="r.reclass.html">r.reclass</a></em><br>
+<em><a href="v.random.html">v.random</a></em><br>
+
+
+<h2>AUTHOR</h2>
+
+Dr. James Hinthorne,
+GIS Laboratory,
+Central Washington University
+<p>
+Modified for GRASS 5.0 by Eric G. Miller
+<p>
+Cover map support by Markus Neteler, 2007
+
+<p>
+<i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.random.cells/description.html
===================================================================
--- grass/trunk/raster/r.random.cells/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.random.cells/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,79 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>r.random.cells</em> generates a random sets of cells that are at
-least <var>distance</var> apart. The cells are numbered from 1 to the
-numbers of cells generated. Random cells will not be generated in areas
-masked off.
-
-<h2>PARAMETERS</h2>
-
-<b>output </b> Output map: Random cells. Each random cell has a unique
-non-zero cell value ranging from 1 to the number of cells generated. The
-heuristic for this algorithm is to randomly pick cells until there are no
-cells outside of the chosen cell's buffer of radius <b>distance</b>.
-<p>
-
-<b>distance</b> Input value(s) [default 0.0]: <b>distance</b> determines the
-minimum distance the centers of the random cells will be apart.
-<p>
-<b>seed</b> Input value [default: random]: Specifies the random seed that
-<em>r.random.cells</em> will use to generate the cells. If the random seed
-is not given,<em> r.random.cells</em> will get a seed from the process ID
-number.
-
-<h2>NOTES</h2>
-
-The original purpose for this program was to generate independent random
-samples of cells in a study area. The <b>distance</b> value is the amount of
-spatial autocorrelation for the map being studied. The amount of spatial
-autocorrelation can be determined by using <em>r.2Dcorrelogram</em> with
-<em>r.2Dto1D</em>, or <em>r.1Dcorrelogram</em>. With <b>distance</b> set to
-zero, the <b>output</b> map will number each non-masked cell from 1 to the
-number of non-masked cells in the study region.
-
-<h2>REFERENCES</h2>
-Random Field Software for GRASS by Chuck Ehlschlaeger<p>
-
-<p>As part of my dissertation, I put together several programs that help
-GRASS (4.1 and beyond) develop uncertainty models of spatial data. I hope
-you find it useful and dependable. The following papers might clarify their
-use: </p>
-
-<p>"<a href="http://www.wiu.edu/users/cre111/older/CGFinal/paper.htm">Visualizing Spatial Data
-Uncertainty Using Animation (final draft)</a>," by Charles R.
-Ehlschlaeger, Ashton M. Shortridge, and Michael F. Goodchild. Submitted to
-Computers in GeoSciences in September, 1996, accepted October, 1996 for
-publication in June, 1997. </p>
-
-<p>"<a href="http://www.wiu.edu/users/cre111/older/SDH96/paper.html">Modeling Uncertainty in Elevation Data for
-Geographical Analysis</a>", by Charles R. Ehlschlaeger, and Ashton M.
-Shortridge. Proceedings of the 7th International Symposium on Spatial Data
-Handling, Delft, Netherlands, August 1996. </p>
-
-<p>"<a href="http://www.wiu.edu/users/cre111/older/acm/paper.html">Dealing with Uncertainty in
-Categorical Coverage Maps: Defining, Visualizing, and Managing Data
-Errors</a>", by Charles Ehlschlaeger and Michael Goodchild.
-Proceedings, Workshop on Geographic Information Systems at the Conference on
-Information and Knowledge Management, Gaithersburg MD, 1994. </p>
-
-<p>"<a href="http://www.wiu.edu/users/cre111/older/gislis/gislis.html">Uncertainty in Spatial Data:
-Defining, Visualizing, and Managing Data Errors</a>", by Charles
-Ehlschlaeger and Michael Goodchild. Proceedings, GIS/LIS'94, pp. 246-253,
-Phoenix AZ, 1994. </p>
-
-<h2>SEE ALSO</h2>
-
-<em>
-r.1Dcorrelogram,
-r.2Dcorrelogram,
-r.2Dto1D,
-<a href="r.random.surface.html">r.random.surface</a>,
-r.random.model,
-<a href="r.random.html">r.random</a>
-</em>
-
-<h2>AUTHOR</h2>
-<p>Charles Ehlschlaeger; National Center for Geographic Information and
-Analysis, University of California, Santa Barbara.
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.random.cells/r.random.cells.html (from rev 32770, grass/trunk/raster/r.random.cells/description.html)
===================================================================
--- grass/trunk/raster/r.random.cells/r.random.cells.html (rev 0)
+++ grass/trunk/raster/r.random.cells/r.random.cells.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,79 @@
+<h2>DESCRIPTION</h2>
+
+<em>r.random.cells</em> generates a random sets of cells that are at
+least <var>distance</var> apart. The cells are numbered from 1 to the
+numbers of cells generated. Random cells will not be generated in areas
+masked off.
+
+<h2>PARAMETERS</h2>
+
+<b>output </b> Output map: Random cells. Each random cell has a unique
+non-zero cell value ranging from 1 to the number of cells generated. The
+heuristic for this algorithm is to randomly pick cells until there are no
+cells outside of the chosen cell's buffer of radius <b>distance</b>.
+<p>
+
+<b>distance</b> Input value(s) [default 0.0]: <b>distance</b> determines the
+minimum distance the centers of the random cells will be apart.
+<p>
+<b>seed</b> Input value [default: random]: Specifies the random seed that
+<em>r.random.cells</em> will use to generate the cells. If the random seed
+is not given,<em> r.random.cells</em> will get a seed from the process ID
+number.
+
+<h2>NOTES</h2>
+
+The original purpose for this program was to generate independent random
+samples of cells in a study area. The <b>distance</b> value is the amount of
+spatial autocorrelation for the map being studied. The amount of spatial
+autocorrelation can be determined by using <em>r.2Dcorrelogram</em> with
+<em>r.2Dto1D</em>, or <em>r.1Dcorrelogram</em>. With <b>distance</b> set to
+zero, the <b>output</b> map will number each non-masked cell from 1 to the
+number of non-masked cells in the study region.
+
+<h2>REFERENCES</h2>
+Random Field Software for GRASS by Chuck Ehlschlaeger<p>
+
+<p>As part of my dissertation, I put together several programs that help
+GRASS (4.1 and beyond) develop uncertainty models of spatial data. I hope
+you find it useful and dependable. The following papers might clarify their
+use: </p>
+
+<p>"<a href="http://www.wiu.edu/users/cre111/older/CGFinal/paper.htm">Visualizing Spatial Data
+Uncertainty Using Animation (final draft)</a>," by Charles R.
+Ehlschlaeger, Ashton M. Shortridge, and Michael F. Goodchild. Submitted to
+Computers in GeoSciences in September, 1996, accepted October, 1996 for
+publication in June, 1997. </p>
+
+<p>"<a href="http://www.wiu.edu/users/cre111/older/SDH96/paper.html">Modeling Uncertainty in Elevation Data for
+Geographical Analysis</a>", by Charles R. Ehlschlaeger, and Ashton M.
+Shortridge. Proceedings of the 7th International Symposium on Spatial Data
+Handling, Delft, Netherlands, August 1996. </p>
+
+<p>"<a href="http://www.wiu.edu/users/cre111/older/acm/paper.html">Dealing with Uncertainty in
+Categorical Coverage Maps: Defining, Visualizing, and Managing Data
+Errors</a>", by Charles Ehlschlaeger and Michael Goodchild.
+Proceedings, Workshop on Geographic Information Systems at the Conference on
+Information and Knowledge Management, Gaithersburg MD, 1994. </p>
+
+<p>"<a href="http://www.wiu.edu/users/cre111/older/gislis/gislis.html">Uncertainty in Spatial Data:
+Defining, Visualizing, and Managing Data Errors</a>", by Charles
+Ehlschlaeger and Michael Goodchild. Proceedings, GIS/LIS'94, pp. 246-253,
+Phoenix AZ, 1994. </p>
+
+<h2>SEE ALSO</h2>
+
+<em>
+r.1Dcorrelogram,
+r.2Dcorrelogram,
+r.2Dto1D,
+<a href="r.random.surface.html">r.random.surface</a>,
+r.random.model,
+<a href="r.random.html">r.random</a>
+</em>
+
+<h2>AUTHOR</h2>
+<p>Charles Ehlschlaeger; National Center for Geographic Information and
+Analysis, University of California, Santa Barbara.
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.random.surface/description.html
===================================================================
--- grass/trunk/raster/r.random.surface/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.random.surface/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,174 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>r.random.surface</em> generates a spatially dependent random surface.
-The random surface is composed of values representing the deviation from the
-mean of the initial random values driving the algorithm. The initial random
-values are independent Gaussian random deviates with a mean of 0 and
-standard deviation of 1. The initial values are spread over each output map
-using filter(s) of diameter distance. The influence of each random value on
-nearby cells is determined by a distance decay function based on exponent.
-If multiple filters are passed over the output maps, each filter is given a
-weight based on the weight inputs. The resulting random surface can have
-"any" mean and variance, but the theoretical mean of an infinitely
-large map is 0.0 and a variance of 1.0. Description of the algorithm is in
-the <b>NOTES</b> section.
-
-<p>
-The random surface generated are composed of floating point numbers, and
-saved in the category description files of the output map(s). Cell values
-are uniformly or normally distributed between 1 and high values inclusive
-(determined by whether the <em>-u</em> flag is used). The category names
-indicate the average floating point value and the range of floating point
-values that each cell value represents.
-
-<p>
-<em>r.random.surface's</em> original goal is to generate random fields for
-spatial error modeling. A procedure to use <em>r.random.surface</em> in
-spatial error modeling is given in the <b>NOTES</b> section.
-
-<h3>Parameters:</h3>
-<dl>
-<dt><b>output</b>
-<dd>Output map(s): Random surface(s). The cell values are a random
-distribution between the low and high values inclusive. The category values
-of the output map(s) are in the form "#.# #.# to #.#" where each
-#.# is a floating point number. The first number is the average of the
-random values the cell value represents. The other two numbers are the range
-of random values for that cell value. The "average" mean value of
-generated <tt>output</tt> map(s) is 0. The "average"
-variance of map(s) generated is 1. The random values represent the standard
-deviation from the mean of that random surface.
-
-<dt><b>distance</b>
-<dd>Input value(s) [default 0.0]: distance determines the spatial dependence
-of the output map(s). The distance value indicates the minimum distance at
-which two map cells have no relationship to each other. A distance value of
-0.0 indicates that there is no spatial dependence (i.e., adjacent cell
-values have no relationship to each other). As the distance value increases,
-adjacent cell values will have values closer to each other. But the range
-and distribution of cell values over the output map(s) will remain the same.
-Visually, the clumps of lower and higher values gets larger as distance
-increases. If multiple values are given, each output map will have multiple
-filters, one for each set of distance, exponent, and weight values.
-
-<dt><b>exponent</b>
-<dd>Input value(s) [default 1.0]: exponent determines the distance decay
-exponent for a particular filter. The exponent value(s) have the property of
-determining the "texture" of the random surface. Texture will
-decrease as the exponent value(s) get closer to 1.0. Normally, exponent will
-be 1.0 or less. If there are no exponent values given, each filter will be
-given an exponent value of 1.0. If there is at least one exponent value
-given, there must be one exponent value for each distance value.
-
-<dt><b>flat</b>
-<dd>Input value(s) [default 0.0]: flat determines the distance at which the
-filter
-
-<dt><b>weight</b>
-<dd>Input value(s) [default 1.0]: weight determines the relative importance
-of each filter. For example, if there were two filters driving the algorithm
-and weight=1.0, 2.0 was given in the command line: The second filter would
-be twice as important as the first filter. If no weight values are given,
-each filter will be just as important as the other filters defining the
-random field. If weight values exist, there must be a weight value for each
-filter of the random field.
-
-<dt><b>high</b>
-<dd>Input value [default 255]: Specifies the high end of the range of cell
-values in the output map(s). Specifying a very large high value will
-minimize the "errors" caused by the random surface's
-discretization. The word errors is in quotes because errors in
-discretization are often going to cancel each other out and the spatial
-statistics are far more sensitive to the initial independent random deviates
-than any potential discretization errors.
-
-<dt><b>seed</b>
-<dd>Input value(s) [default random]: Specifies the random seed(s), one for
-each map, that <em>r.random.surface</em> will use to generate the initial
-set of random values that the resulting map is based on. If the random seed
-is not given, <em>r.random.surface</em> will get a seed from the process ID
-number.
-
-</dl>
-
-<h2>NOTES</h2>
-
-While most literature uses the term random field instead of random surface,
-this algorithm always generates a surface. Thus, its use of random surface.
-
-<p>
-<em>r.random.surface</em> builds the random surface using a filter algorithm
-smoothing a map of independent random deviates. The size of the filter is
-determined by the largest distance of spatial dependence. The shape of the
-filter is determined by the distance decay exponent(s), and the various
-weights if different sets of spatial parameters are used. The map of
-independent random deviates will be as large as the current region PLUS the
-extent of the filter. This will eliminate edge effects caused by the
-reduction of degrees of freedom. The map of independent random deviates will
-ignore the current mask for the same reason.
-
-<p>
-One of the most important uses for <em>r.random.surface</em> is to determine
-how the error inherent in raster maps might effect the analyses done with
-those maps. If you wanted to check to see how sensitive your analysis is to
-the errors in the DEMs in your study area, see:
-
-<p>"<a href="http://www.geo.hunter.cuny.edu/~chuck/CGFinal/paper.htm">Visualizing Spatial Data Uncertainty Using Animation (final draft)</a>," by Charles R. Ehlschlaeger, Ashton M. Shortridge, and Michael F. Goodchild. Submitted to Computers in GeoSciences in September, 1996, accepted October, 1996 for publication in June, 1997.
-
-<p>
-"<a href="http://www.geo.hunter.cuny.edu/~chuck/SDH96/paper.html">Modeling Uncertainty in Elevation Data for Geographical Analysis</a>", by Charles R. Ehlschlaeger, and Ashton M. Shortridge. Proceedings of the 7th International Symposium on Spatial Data Handling, Delft, Netherlands, August 1996. </p>
-
-<p>
-"<a href="http://www.geo.hunter.cuny.edu/~chuck/acm/paper.html">Dealing with Uncertainty in Categorical Coverage Maps: Defining, Visualizing, and Managing Data Errors</a>", by Charles Ehlschlaeger and Michael Goodchild. Proceedings, Workshop on Geographic Information Systems at the Conference on Information and Knowledge Management, Gaithersburg MD, 1994.
-
-<p>
-"<a href="http://www.geo.hunter.cuny.edu/~chuck/gislis/gislis.html>Uncertainty in Spatial Data: Defining, Visualizing, and Managing Data Errors</a>", by Charles Ehlschlaeger and Michael Goodchild. Proceedings, GIS/LIS'94, pp. 246-253, Phoenix AZ,
-1994.
-
-<p>
-If you are interested in creating potential realizations of categorical
-coverage maps, see <em>r.random.model</em>.
-
-<h2>SEE ALSO</h2>
-
-<em><a href="r.random.html">r.random</a>,
-<a href="r.mapcalc.html">r.mapcalc</a>
-</em>
-
-<h2>REFERENCES</h2>
-Random Field Software for GRASS by Chuck Ehlschlaeger<p>
-
-<p>As part of my dissertation, I put together several programs that help
-GRASS (4.1 and beyond) develop uncertainty models of spatial data. I hope
-you find it useful and dependable. The following papers might clarify their
-use: </p>
-
-<p>"<a href="../../CGFinal/paper.htm">Visualizing Spatial Data
-Uncertainty Using Animation (final draft)</a>," by Charles R.
-Ehlschlaeger, Ashton M. Shortridge, and Michael F. Goodchild. Submitted to
-Computers in GeoSciences in September, 1996, accepted October, 1996 for
-publication in June, 1997. </p>
-
-<p>"<a href="http://www.geo.hunter.cuny.edu/~chuck/paper.html">Modeling Uncertainty in Elevation Data for
-Geographical Analysis</a>", by Charles R. Ehlschlaeger, and Ashton M.
-Shortridge. Proceedings of the 7th International Symposium on Spatial Data
-Handling, Delft, Netherlands, August 1996. </p>
-
-<p>"<a href="http://www.geo.hunter.cuny.edu/~chuck/acm/paper.html">Dealing with Uncertainty in
-Categorical Coverage Maps: Defining, Visualizing, and Managing Data
-Errors</a>", by Charles Ehlschlaeger and Michael Goodchild.
-Proceedings, Workshop on Geographic Information Systems at the Conference on
-Information and Knowledge Management, Gaithersburg MD, 1994. </p>
-
-<p>"<a href="http://www.geo.hunter.cuny.edu/~chuck/gislis/gislis.html">Uncertainty in Spatial Data:
-Defining, Visualizing, and Managing Data Errors</a>", by Charles
-Ehlschlaeger and Michael Goodchild. Proceedings, GIS/LIS'94, pp. 246-253,
-Phoenix AZ, 1994. </p>
-
-
-<h2>AUTHORS</h2>
-Charles Ehlschlaeger, Michael Goodchild, and Chih-chang Lin; National Center
-for Geographic Information and Analysis, University of California, Santa
-Barbara.
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.random.surface/r.random.surface.html (from rev 32770, grass/trunk/raster/r.random.surface/description.html)
===================================================================
--- grass/trunk/raster/r.random.surface/r.random.surface.html (rev 0)
+++ grass/trunk/raster/r.random.surface/r.random.surface.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,174 @@
+<h2>DESCRIPTION</h2>
+
+<em>r.random.surface</em> generates a spatially dependent random surface.
+The random surface is composed of values representing the deviation from the
+mean of the initial random values driving the algorithm. The initial random
+values are independent Gaussian random deviates with a mean of 0 and
+standard deviation of 1. The initial values are spread over each output map
+using filter(s) of diameter distance. The influence of each random value on
+nearby cells is determined by a distance decay function based on exponent.
+If multiple filters are passed over the output maps, each filter is given a
+weight based on the weight inputs. The resulting random surface can have
+"any" mean and variance, but the theoretical mean of an infinitely
+large map is 0.0 and a variance of 1.0. Description of the algorithm is in
+the <b>NOTES</b> section.
+
+<p>
+The random surface generated are composed of floating point numbers, and
+saved in the category description files of the output map(s). Cell values
+are uniformly or normally distributed between 1 and high values inclusive
+(determined by whether the <em>-u</em> flag is used). The category names
+indicate the average floating point value and the range of floating point
+values that each cell value represents.
+
+<p>
+<em>r.random.surface's</em> original goal is to generate random fields for
+spatial error modeling. A procedure to use <em>r.random.surface</em> in
+spatial error modeling is given in the <b>NOTES</b> section.
+
+<h3>Parameters:</h3>
+<dl>
+<dt><b>output</b>
+<dd>Output map(s): Random surface(s). The cell values are a random
+distribution between the low and high values inclusive. The category values
+of the output map(s) are in the form "#.# #.# to #.#" where each
+#.# is a floating point number. The first number is the average of the
+random values the cell value represents. The other two numbers are the range
+of random values for that cell value. The "average" mean value of
+generated <tt>output</tt> map(s) is 0. The "average"
+variance of map(s) generated is 1. The random values represent the standard
+deviation from the mean of that random surface.
+
+<dt><b>distance</b>
+<dd>Input value(s) [default 0.0]: distance determines the spatial dependence
+of the output map(s). The distance value indicates the minimum distance at
+which two map cells have no relationship to each other. A distance value of
+0.0 indicates that there is no spatial dependence (i.e., adjacent cell
+values have no relationship to each other). As the distance value increases,
+adjacent cell values will have values closer to each other. But the range
+and distribution of cell values over the output map(s) will remain the same.
+Visually, the clumps of lower and higher values gets larger as distance
+increases. If multiple values are given, each output map will have multiple
+filters, one for each set of distance, exponent, and weight values.
+
+<dt><b>exponent</b>
+<dd>Input value(s) [default 1.0]: exponent determines the distance decay
+exponent for a particular filter. The exponent value(s) have the property of
+determining the "texture" of the random surface. Texture will
+decrease as the exponent value(s) get closer to 1.0. Normally, exponent will
+be 1.0 or less. If there are no exponent values given, each filter will be
+given an exponent value of 1.0. If there is at least one exponent value
+given, there must be one exponent value for each distance value.
+
+<dt><b>flat</b>
+<dd>Input value(s) [default 0.0]: flat determines the distance at which the
+filter
+
+<dt><b>weight</b>
+<dd>Input value(s) [default 1.0]: weight determines the relative importance
+of each filter. For example, if there were two filters driving the algorithm
+and weight=1.0, 2.0 was given in the command line: The second filter would
+be twice as important as the first filter. If no weight values are given,
+each filter will be just as important as the other filters defining the
+random field. If weight values exist, there must be a weight value for each
+filter of the random field.
+
+<dt><b>high</b>
+<dd>Input value [default 255]: Specifies the high end of the range of cell
+values in the output map(s). Specifying a very large high value will
+minimize the "errors" caused by the random surface's
+discretization. The word errors is in quotes because errors in
+discretization are often going to cancel each other out and the spatial
+statistics are far more sensitive to the initial independent random deviates
+than any potential discretization errors.
+
+<dt><b>seed</b>
+<dd>Input value(s) [default random]: Specifies the random seed(s), one for
+each map, that <em>r.random.surface</em> will use to generate the initial
+set of random values that the resulting map is based on. If the random seed
+is not given, <em>r.random.surface</em> will get a seed from the process ID
+number.
+
+</dl>
+
+<h2>NOTES</h2>
+
+While most literature uses the term random field instead of random surface,
+this algorithm always generates a surface. Thus, its use of random surface.
+
+<p>
+<em>r.random.surface</em> builds the random surface using a filter algorithm
+smoothing a map of independent random deviates. The size of the filter is
+determined by the largest distance of spatial dependence. The shape of the
+filter is determined by the distance decay exponent(s), and the various
+weights if different sets of spatial parameters are used. The map of
+independent random deviates will be as large as the current region PLUS the
+extent of the filter. This will eliminate edge effects caused by the
+reduction of degrees of freedom. The map of independent random deviates will
+ignore the current mask for the same reason.
+
+<p>
+One of the most important uses for <em>r.random.surface</em> is to determine
+how the error inherent in raster maps might effect the analyses done with
+those maps. If you wanted to check to see how sensitive your analysis is to
+the errors in the DEMs in your study area, see:
+
+<p>"<a href="http://www.geo.hunter.cuny.edu/~chuck/CGFinal/paper.htm">Visualizing Spatial Data Uncertainty Using Animation (final draft)</a>," by Charles R. Ehlschlaeger, Ashton M. Shortridge, and Michael F. Goodchild. Submitted to Computers in GeoSciences in September, 1996, accepted October, 1996 for publication in June, 1997.
+
+<p>
+"<a href="http://www.geo.hunter.cuny.edu/~chuck/SDH96/paper.html">Modeling Uncertainty in Elevation Data for Geographical Analysis</a>", by Charles R. Ehlschlaeger, and Ashton M. Shortridge. Proceedings of the 7th International Symposium on Spatial Data Handling, Delft, Netherlands, August 1996. </p>
+
+<p>
+"<a href="http://www.geo.hunter.cuny.edu/~chuck/acm/paper.html">Dealing with Uncertainty in Categorical Coverage Maps: Defining, Visualizing, and Managing Data Errors</a>", by Charles Ehlschlaeger and Michael Goodchild. Proceedings, Workshop on Geographic Information Systems at the Conference on Information and Knowledge Management, Gaithersburg MD, 1994.
+
+<p>
+"<a href="http://www.geo.hunter.cuny.edu/~chuck/gislis/gislis.html>Uncertainty in Spatial Data: Defining, Visualizing, and Managing Data Errors</a>", by Charles Ehlschlaeger and Michael Goodchild. Proceedings, GIS/LIS'94, pp. 246-253, Phoenix AZ,
+1994.
+
+<p>
+If you are interested in creating potential realizations of categorical
+coverage maps, see <em>r.random.model</em>.
+
+<h2>SEE ALSO</h2>
+
+<em><a href="r.random.html">r.random</a>,
+<a href="r.mapcalc.html">r.mapcalc</a>
+</em>
+
+<h2>REFERENCES</h2>
+Random Field Software for GRASS by Chuck Ehlschlaeger<p>
+
+<p>As part of my dissertation, I put together several programs that help
+GRASS (4.1 and beyond) develop uncertainty models of spatial data. I hope
+you find it useful and dependable. The following papers might clarify their
+use: </p>
+
+<p>"<a href="../../CGFinal/paper.htm">Visualizing Spatial Data
+Uncertainty Using Animation (final draft)</a>," by Charles R.
+Ehlschlaeger, Ashton M. Shortridge, and Michael F. Goodchild. Submitted to
+Computers in GeoSciences in September, 1996, accepted October, 1996 for
+publication in June, 1997. </p>
+
+<p>"<a href="http://www.geo.hunter.cuny.edu/~chuck/paper.html">Modeling Uncertainty in Elevation Data for
+Geographical Analysis</a>", by Charles R. Ehlschlaeger, and Ashton M.
+Shortridge. Proceedings of the 7th International Symposium on Spatial Data
+Handling, Delft, Netherlands, August 1996. </p>
+
+<p>"<a href="http://www.geo.hunter.cuny.edu/~chuck/acm/paper.html">Dealing with Uncertainty in
+Categorical Coverage Maps: Defining, Visualizing, and Managing Data
+Errors</a>", by Charles Ehlschlaeger and Michael Goodchild.
+Proceedings, Workshop on Geographic Information Systems at the Conference on
+Information and Knowledge Management, Gaithersburg MD, 1994. </p>
+
+<p>"<a href="http://www.geo.hunter.cuny.edu/~chuck/gislis/gislis.html">Uncertainty in Spatial Data:
+Defining, Visualizing, and Managing Data Errors</a>", by Charles
+Ehlschlaeger and Michael Goodchild. Proceedings, GIS/LIS'94, pp. 246-253,
+Phoenix AZ, 1994. </p>
+
+
+<h2>AUTHORS</h2>
+Charles Ehlschlaeger, Michael Goodchild, and Chih-chang Lin; National Center
+for Geographic Information and Analysis, University of California, Santa
+Barbara.
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.reclass/description.html
===================================================================
--- grass/trunk/raster/r.reclass/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.reclass/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,291 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>r.reclass</em> creates an <em>output</em> map layer
-based on an <em>input</em> raster map layer. The output
-map layer will be a reclassification of the input map layer
-based on reclass rules input to <em>r.reclass</em>, and can
-be treated in much the same way that raster maps are
-treated. A <em>TITLE</em> for the output map layer may be
-(optionally) specified by the user.
-
-<p>
-The reclass rules are read from standard input (i.e., from
-the keyboard, redirected from a file, or piped through
-another program).
-
-<p>
-Before using <em>r.reclass</em> the user must know the following:
-
-<ol>
-<li>The new categories desired; and, which old categories fit into
-which new categories.
-<li>The names of the new categories.
-</ol>
-
-<h2>INTERACTIVE PROGRAM USE: EXAMPLE</h2>
-
-Suppose we want to reclassify the raster map layer
-<em>roads</em>, consisting of five categories, into the
-three new categories: paved roads, unpaved roads, and
-railroad tracks. The user is asked whether the reclass
-table is to be established with each category value
-initially set to 0, or with each category value initially
-set to its own value. A screen like that shown below then
-appears, listing the categories of the <em>roads</em>
-raster map layer to be reclassified and prompting the user
-for the new category values to be assigned them.
-<p>
-<pre>
- ENTER NEW CATEGORY NUMBERS FOR THESE CATEGORIES
-
- OLD CATEGORY NAME OLD NEW
- NUM NUM
- no data 0 0___
- Hard Surface, 2 lanes 1 0___
- Loose Surface, 1 lane 2 0___
- Improved Dirt 3 0___
- Unimproved Dirt Trail 4 0___
- Railroad, single track 5 0___
-
- AFTER COMPLETING ALL ANSWERS, HIT <ESC> TO CONTINUE
- (OR <Ctrl-C> TO CANCEL)
-</pre>
-
-In the following screen the new category values have been
-entered beside the appropriate old category names. Cells
-assigned category values 2, 3, and 4 in the old raster map
-layer are now assigned the new category value 2 in the
-reclassed map; cell data formerly assigned to category
-value 5 in the old raster map map are now assigned the new
-category value 3 in the reclassed map.
-<pre>
- ENTER NEW CATEGORY NUMBERS FOR THESE CATEGORIES
-
-
- OLD CATEGORY NAME OLD NEW
- NUM NUM
- no data 0 0___
- Hard Surface, 2 lanes 1 1___
- Loose Surface, 1 lane 2 2___
- Improved Dirt 3 2___
- Unimproved Dirt Trail 4 2___
- Railroad, single track 5 3___
-
- AFTER COMPLETING ALL ANSWERS, HIT <ESC> TO CONTINUE
- (OR <Ctrl-C> TO CANCEL)
-</pre>
-
-Hitting the escape key <ESC> will bring up the
-following screen, which prompts the user to enter a new
-TITLE and category label for the newly <b>reclassed</b>
-categories.
-<pre>
- ENTER NEW CATEGORY NAMES FOR THESE CATEGORIES
-
- TITLE: Roads Reclassified
- CAT NEW CATEGORY NAME
- NUM
- 0 no data
- 1 Paved Roads
- 2 Unpaved Roads
- 3 Railroad, single track
-
- AFTER COMPLETING ALL ANSWERS, HIT <ESC> TO CONTINUE
- (OR <Ctrl-C> TO CANCEL)
-</pre>
-Based upon the information supplied by the user in the above sample screens,
-the new output map, supporting category, color, history, and header files
-are created.
-
-<h2>NON-INTERACTIVE PROGRAM USE: RECLASS RULES</h2>
-
-In non-interactive program use, the names of an input map, output map,
-and output map TITLE are given on the command line.
-However, the reclass rules are still read from standard input
-(i.e., from the keyboard, redirected
-from a file, or piped through another program).
-
-<p>
-
-Once the user has specified an input raster map layer,
-output map layer name, and (optionally) output map layer
-TITLE by typing
-
-<dl>
-<dd>
-<b>r.reclass input=</b><em>name </em><b>output=</b><em>name </em>[<b>TITLE=</b><em>name</em>]
-</dl>
-
-Each line of input must have the following format:
-
-<dl>
-<dd><b>input_categories=</b><em>output_category </em>[<em>label</em>]
-</dl>
-
-<p>
-where the input lines specify the category values in the
-input raster map layer to be reclassified to the new
-<em>output_category</em> category value. Specification of
-a <em>label</em> to be associated with the new output map
-layer category is optional. If specified, it is recorded
-as the category label for the new category value. The
-equal sign = is required. The <em>input_category(ies)</em>
-may consist of single category values or a range of such
-values in the format "<em>low</em> thru <em>high</em>." The
-word "thru" must be present.
-<p>
-To include all (remaining) values the asterix "*" can be used. This
-rule has to be set as last rule. No further rules are accepted after
-setting this rule.
-<p>
-No data have to be spcified with NULL.
-<p>
-
-A line containing only the word <b>end</b> terminates the
-input.
-
-<h2>NON-INTERACTIVE PROGRAM USE: EXAMPLES</h2>
-
-The following examples may help clarify the reclass rules.
-<p>
-<dt>
-<dd>1. This example reclassifies categories 1, 2 and 3 in the input raster
-map layer "roads" to category 1 with category label "good quality" in the output map
-layer, and reclassifies input raster map layer categories 4 and 5 to
-category 2 with the label "poor quality" in the output map layer.
-
-<pre>
- 1 2 3 = 1 good quality
- 4 5 = 2 poor quality
-</pre>
-<p>
-<dd>2. This example reclassifies input raster map layer categories 1 thru 10 to output
-map layer category 1, input map layer categories 11 thru 20 to output map layer
-category 2, and input map layer categories 21 thru 30 to output map layer
-category 3, all without labels. The range from 30 to 40 is reclassified as
-NULL.
-<pre>
- 1 thru 10 = 1
- 11 thru 20 = 2
- 21 thru 30 = 3
- 30 thru 40 = NULL
-</pre>
-
-<dd>3. Subsequent rules override previous rules. Therefore, the below example
-reclassifies input raster map layer categories 1 thru 19 and 51 thru 100
-to category 1 in the output map layer,
-input raster map layer categories 20 thru 24 and 26 thru 50 to
-the output map layer category 2, and input raster map layer category 25
-to the output category 3.
-<pre>
- 1 thru 100 = 1 poor quality
- 20 thru 50 = 2 medium quality
- 25 = 3 good quality
-</pre>
-
-<dd>4. This example reclassifies categories 1, 3 and 5 in the input raster map layer to category 1 with category label "poor quality" in the output map layer,
-and reclassifies input raster map layer categories 2, 4, and 6
-to category 2 with the label "good quality" in the output map layer.
-All other values are reclassified to NULL.
-<pre>
- 1 3 5 = 1 poor quality
- 2 4 6 = 2 good quality
- * = NULL
-</pre>
-<p>
-
-<dd>5. The previous example could also have been entered as:
-<pre>
- 1 thru 19 51 thru 100 = 1 poor quality
- 20 thru 24 26 thru 50 = 2 medium quality
- 25 = 3 good quality
-</pre>
-or as:
-<pre>
- 1 thru 19 = 1 poor quality
- 51 thru 100 = 1
- 20 thru 24 = 2
- 26 thru 50 = 2 medium quality
- 25 = 3 good quality
-</pre>
-</dd>
-<p>
-
-The final example was given to show how the labels are handled. If a new
-category value appears in more than one rule (as is the case with new
-category values 1 and 2),
-the last label which was specified becomes the label for that category.
-In this case the labels are assigned exactly as in the two previous examples.
-
-<h2>NOTES</h2>
-
-In fact, the <em>r.reclass</em> program does <em>not</em> generate any new
-raster map layers (in the interests of disk space conservation). Instead, a
-<b>reclass table</b> is stored which will be used to reclassify the
-original raster map layer each time the new (reclassed) map name
-is requested. As far as the user (and programmer) is concerned, that
-raster map has been created.
-Also note that although the user can generate a <em>r.reclass</em> map
-which is based on another <em>r.reclass</em> map,
-the new <em>r.reclass</em> map map will be stored in GRASS as a reclass
-of the <em>original</em> raster map on which the first reclassed map was
-based. Therefore, while GRASS allows the user to provide <em>r.reclass</em>
-map layer information which is based on an already reclassified map
-(for the user's convenience), no <em>r.reclass</em> map layer
-(i.e., <em>reclass table</em>) will ever be <em>stored</em>
-as a <em>r.reclass</em> of a <em>r.reclass</em>.
-
-<p>
-To convert a reclass map to a regular raster map layer, set your
-geographic region settings to match the settings in the header for the
-reclass map (an ASCII file found under the <em>cellhd</em> directory, or
-viewable by running <em><a href="r.support.html">r.support</a></em>) and then run <em><a href="r.resample.html">r.resample</a></em>.
-
-<p>
-<em><a href="r.mapcalc.html">r.mapcalc</a></em> can be used to convert
-a reclass map to a regular raster map layer:
-
-<div class="code"><pre>
- r.mapcalc raster_map=reclass_map
-</pre></div>
-
-
-<p>
-where <em>raster_map</em> is the name to be given to the new raster map,
-and <em>reclass_map</em> is an existing reclass map.
-
-<h2>BEWARE</h2>
-
-Because <em>r.reclass</em> generates a table referencing some original
-raster map layer rather than creating a reclassed raster map layer,
-a <em>r.reclass</em> map layer will no longer be accessible if
-the original raster map layer upon which it was based is later removed.
-
-<p>
-A <em>r.reclass</em> map is not a true raster map layer.
-Rather, it is a table of reclassification values which reference the
-input raster map layer. Therefore, users who wish to retain reclassified
-map layers must also save the original input raster map layers
-from which they were generated. Alternatively r.recode can be used.
-
-<p>
-Category values which are not explicitly reclassified to a new value
-by the user will be reclassified to NULL.
-
-<h2>SEE ALSO</h2>
-
-<em><a href="r.resample.html">r.resample</a></em>,
-<em><a href="r.rescale.html">r.rescale</a></em>,
-<em><a href="r.recode.html">r.recode</a></em>
-
-<h2>AUTHORS</h2>
-
-James Westervelt,
-<br>
-
-Michael Shapiro,
-<br>
-U.S.Army Construction Engineering Research Laboratory
-
-<p>
-<i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.reclass/r.reclass.html (from rev 32770, grass/trunk/raster/r.reclass/description.html)
===================================================================
--- grass/trunk/raster/r.reclass/r.reclass.html (rev 0)
+++ grass/trunk/raster/r.reclass/r.reclass.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,291 @@
+<h2>DESCRIPTION</h2>
+
+<em>r.reclass</em> creates an <em>output</em> map layer
+based on an <em>input</em> raster map layer. The output
+map layer will be a reclassification of the input map layer
+based on reclass rules input to <em>r.reclass</em>, and can
+be treated in much the same way that raster maps are
+treated. A <em>TITLE</em> for the output map layer may be
+(optionally) specified by the user.
+
+<p>
+The reclass rules are read from standard input (i.e., from
+the keyboard, redirected from a file, or piped through
+another program).
+
+<p>
+Before using <em>r.reclass</em> the user must know the following:
+
+<ol>
+<li>The new categories desired; and, which old categories fit into
+which new categories.
+<li>The names of the new categories.
+</ol>
+
+<h2>INTERACTIVE PROGRAM USE: EXAMPLE</h2>
+
+Suppose we want to reclassify the raster map layer
+<em>roads</em>, consisting of five categories, into the
+three new categories: paved roads, unpaved roads, and
+railroad tracks. The user is asked whether the reclass
+table is to be established with each category value
+initially set to 0, or with each category value initially
+set to its own value. A screen like that shown below then
+appears, listing the categories of the <em>roads</em>
+raster map layer to be reclassified and prompting the user
+for the new category values to be assigned them.
+<p>
+<pre>
+ ENTER NEW CATEGORY NUMBERS FOR THESE CATEGORIES
+
+ OLD CATEGORY NAME OLD NEW
+ NUM NUM
+ no data 0 0___
+ Hard Surface, 2 lanes 1 0___
+ Loose Surface, 1 lane 2 0___
+ Improved Dirt 3 0___
+ Unimproved Dirt Trail 4 0___
+ Railroad, single track 5 0___
+
+ AFTER COMPLETING ALL ANSWERS, HIT <ESC> TO CONTINUE
+ (OR <Ctrl-C> TO CANCEL)
+</pre>
+
+In the following screen the new category values have been
+entered beside the appropriate old category names. Cells
+assigned category values 2, 3, and 4 in the old raster map
+layer are now assigned the new category value 2 in the
+reclassed map; cell data formerly assigned to category
+value 5 in the old raster map map are now assigned the new
+category value 3 in the reclassed map.
+<pre>
+ ENTER NEW CATEGORY NUMBERS FOR THESE CATEGORIES
+
+
+ OLD CATEGORY NAME OLD NEW
+ NUM NUM
+ no data 0 0___
+ Hard Surface, 2 lanes 1 1___
+ Loose Surface, 1 lane 2 2___
+ Improved Dirt 3 2___
+ Unimproved Dirt Trail 4 2___
+ Railroad, single track 5 3___
+
+ AFTER COMPLETING ALL ANSWERS, HIT <ESC> TO CONTINUE
+ (OR <Ctrl-C> TO CANCEL)
+</pre>
+
+Hitting the escape key <ESC> will bring up the
+following screen, which prompts the user to enter a new
+TITLE and category label for the newly <b>reclassed</b>
+categories.
+<pre>
+ ENTER NEW CATEGORY NAMES FOR THESE CATEGORIES
+
+ TITLE: Roads Reclassified
+ CAT NEW CATEGORY NAME
+ NUM
+ 0 no data
+ 1 Paved Roads
+ 2 Unpaved Roads
+ 3 Railroad, single track
+
+ AFTER COMPLETING ALL ANSWERS, HIT <ESC> TO CONTINUE
+ (OR <Ctrl-C> TO CANCEL)
+</pre>
+Based upon the information supplied by the user in the above sample screens,
+the new output map, supporting category, color, history, and header files
+are created.
+
+<h2>NON-INTERACTIVE PROGRAM USE: RECLASS RULES</h2>
+
+In non-interactive program use, the names of an input map, output map,
+and output map TITLE are given on the command line.
+However, the reclass rules are still read from standard input
+(i.e., from the keyboard, redirected
+from a file, or piped through another program).
+
+<p>
+
+Once the user has specified an input raster map layer,
+output map layer name, and (optionally) output map layer
+TITLE by typing
+
+<dl>
+<dd>
+<b>r.reclass input=</b><em>name </em><b>output=</b><em>name </em>[<b>TITLE=</b><em>name</em>]
+</dl>
+
+Each line of input must have the following format:
+
+<dl>
+<dd><b>input_categories=</b><em>output_category </em>[<em>label</em>]
+</dl>
+
+<p>
+where the input lines specify the category values in the
+input raster map layer to be reclassified to the new
+<em>output_category</em> category value. Specification of
+a <em>label</em> to be associated with the new output map
+layer category is optional. If specified, it is recorded
+as the category label for the new category value. The
+equal sign = is required. The <em>input_category(ies)</em>
+may consist of single category values or a range of such
+values in the format "<em>low</em> thru <em>high</em>." The
+word "thru" must be present.
+<p>
+To include all (remaining) values the asterix "*" can be used. This
+rule has to be set as last rule. No further rules are accepted after
+setting this rule.
+<p>
+No data have to be spcified with NULL.
+<p>
+
+A line containing only the word <b>end</b> terminates the
+input.
+
+<h2>NON-INTERACTIVE PROGRAM USE: EXAMPLES</h2>
+
+The following examples may help clarify the reclass rules.
+<p>
+<dt>
+<dd>1. This example reclassifies categories 1, 2 and 3 in the input raster
+map layer "roads" to category 1 with category label "good quality" in the output map
+layer, and reclassifies input raster map layer categories 4 and 5 to
+category 2 with the label "poor quality" in the output map layer.
+
+<pre>
+ 1 2 3 = 1 good quality
+ 4 5 = 2 poor quality
+</pre>
+<p>
+<dd>2. This example reclassifies input raster map layer categories 1 thru 10 to output
+map layer category 1, input map layer categories 11 thru 20 to output map layer
+category 2, and input map layer categories 21 thru 30 to output map layer
+category 3, all without labels. The range from 30 to 40 is reclassified as
+NULL.
+<pre>
+ 1 thru 10 = 1
+ 11 thru 20 = 2
+ 21 thru 30 = 3
+ 30 thru 40 = NULL
+</pre>
+
+<dd>3. Subsequent rules override previous rules. Therefore, the below example
+reclassifies input raster map layer categories 1 thru 19 and 51 thru 100
+to category 1 in the output map layer,
+input raster map layer categories 20 thru 24 and 26 thru 50 to
+the output map layer category 2, and input raster map layer category 25
+to the output category 3.
+<pre>
+ 1 thru 100 = 1 poor quality
+ 20 thru 50 = 2 medium quality
+ 25 = 3 good quality
+</pre>
+
+<dd>4. This example reclassifies categories 1, 3 and 5 in the input raster map layer to category 1 with category label "poor quality" in the output map layer,
+and reclassifies input raster map layer categories 2, 4, and 6
+to category 2 with the label "good quality" in the output map layer.
+All other values are reclassified to NULL.
+<pre>
+ 1 3 5 = 1 poor quality
+ 2 4 6 = 2 good quality
+ * = NULL
+</pre>
+<p>
+
+<dd>5. The previous example could also have been entered as:
+<pre>
+ 1 thru 19 51 thru 100 = 1 poor quality
+ 20 thru 24 26 thru 50 = 2 medium quality
+ 25 = 3 good quality
+</pre>
+or as:
+<pre>
+ 1 thru 19 = 1 poor quality
+ 51 thru 100 = 1
+ 20 thru 24 = 2
+ 26 thru 50 = 2 medium quality
+ 25 = 3 good quality
+</pre>
+</dd>
+<p>
+
+The final example was given to show how the labels are handled. If a new
+category value appears in more than one rule (as is the case with new
+category values 1 and 2),
+the last label which was specified becomes the label for that category.
+In this case the labels are assigned exactly as in the two previous examples.
+
+<h2>NOTES</h2>
+
+In fact, the <em>r.reclass</em> program does <em>not</em> generate any new
+raster map layers (in the interests of disk space conservation). Instead, a
+<b>reclass table</b> is stored which will be used to reclassify the
+original raster map layer each time the new (reclassed) map name
+is requested. As far as the user (and programmer) is concerned, that
+raster map has been created.
+Also note that although the user can generate a <em>r.reclass</em> map
+which is based on another <em>r.reclass</em> map,
+the new <em>r.reclass</em> map map will be stored in GRASS as a reclass
+of the <em>original</em> raster map on which the first reclassed map was
+based. Therefore, while GRASS allows the user to provide <em>r.reclass</em>
+map layer information which is based on an already reclassified map
+(for the user's convenience), no <em>r.reclass</em> map layer
+(i.e., <em>reclass table</em>) will ever be <em>stored</em>
+as a <em>r.reclass</em> of a <em>r.reclass</em>.
+
+<p>
+To convert a reclass map to a regular raster map layer, set your
+geographic region settings to match the settings in the header for the
+reclass map (an ASCII file found under the <em>cellhd</em> directory, or
+viewable by running <em><a href="r.support.html">r.support</a></em>) and then run <em><a href="r.resample.html">r.resample</a></em>.
+
+<p>
+<em><a href="r.mapcalc.html">r.mapcalc</a></em> can be used to convert
+a reclass map to a regular raster map layer:
+
+<div class="code"><pre>
+ r.mapcalc raster_map=reclass_map
+</pre></div>
+
+
+<p>
+where <em>raster_map</em> is the name to be given to the new raster map,
+and <em>reclass_map</em> is an existing reclass map.
+
+<h2>BEWARE</h2>
+
+Because <em>r.reclass</em> generates a table referencing some original
+raster map layer rather than creating a reclassed raster map layer,
+a <em>r.reclass</em> map layer will no longer be accessible if
+the original raster map layer upon which it was based is later removed.
+
+<p>
+A <em>r.reclass</em> map is not a true raster map layer.
+Rather, it is a table of reclassification values which reference the
+input raster map layer. Therefore, users who wish to retain reclassified
+map layers must also save the original input raster map layers
+from which they were generated. Alternatively r.recode can be used.
+
+<p>
+Category values which are not explicitly reclassified to a new value
+by the user will be reclassified to NULL.
+
+<h2>SEE ALSO</h2>
+
+<em><a href="r.resample.html">r.resample</a></em>,
+<em><a href="r.rescale.html">r.rescale</a></em>,
+<em><a href="r.recode.html">r.recode</a></em>
+
+<h2>AUTHORS</h2>
+
+James Westervelt,
+<br>
+
+Michael Shapiro,
+<br>
+U.S.Army Construction Engineering Research Laboratory
+
+<p>
+<i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.recode/description.html
===================================================================
--- grass/trunk/raster/r.recode/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.recode/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,78 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>r.recode</em> creates an output map layer based on an input raster map
-layer. The output map layer will be a recoding of the input map layer based
-on recode rules input to <em>r.recode</em>. A <em>title</em> for the output
-map layer may be (optionally) specified by the user.<p>
-
-The recode rules are read from standard input (i.e., from the keyboard,
-redirected from a file, or piped through another program).<p>
-
-The program will be run non-interactively if the user specifies the name of
-the raster map layer to be recoded, the <em>name</em> of an output layer to
-hold recoded map, and (optionally) the name of a title for the output map.
-
-Rules are defined in one of these formats:
-<pre>
- old_low:old_high:new_low:new_high
- old_low:old_high:new_val (i.e. new_high == new_low)
- *:old_val:new_val (interval [inf, old_val])
- old_val:*:new_val (interval [old_val, inf])
-</pre>
-
-<em>r.recode</em> is loosely based on r.reclass and uses the GRASS reclass
-library to convert the rasters. It has routines for converting to every
-possible combination of raster (eg. int to double, double to float, etc).
-Standard floating point raster precision is float, with <em>-d</em> double
-precision will be written.<br>
-There are four basic routines that it accepts:
-
-<ol>
-<li>old-low to old-high is reclassed to new-low to new high , where the
-user provides all four values. The program figures on the fly what type of
-raster should be created.
-
-<li>old-low to old-high is reclassed to a single new value. Anything outside
-the range is null.
-
-<li> * to old-high will reclass everything less than old-high to a single
-new value.
-
-<li> old-low to * will reclass everything greater than old-low to a single
-new value.
-</ol>
-
-These four sets of arguments can be given on the command line, or piped via
-stdin or a file. More than one set of arguments is accepted.
-
-<h2>EXAMPLES</h2>
-
-<b>Map type conversion</b><br>
-
-To simply convert a raster between formats (eg. int to float) the user would
-use the first argument. For example <br>
-
-<tt>10:1500:0.1:15.0</tt><br>
-
- would convert an old raster with range between 10 and 1500 to a float
-raster with range bewteen 0.1 and 15.0. <p>
-
-<b>Value replacement</b><br>
-
-r.recode can be used to replace existing cell values by others. The
-formatting is as described above. In following example the values 1, 2 and
-3 are replaced by 1.1, 7.5 resp. 0.4:<br>
-
-<pre>
- r.recode in=oldmap out=newmap << EOF
- 1:1:1.1:1.1
- 2:2:7.5:7.5
- 3:3:0.4:0.4
- EOF
-</pre>
-
-
-<h2>AUTHOR</h2>
-CERL
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.recode/r.recode.html (from rev 32770, grass/trunk/raster/r.recode/description.html)
===================================================================
--- grass/trunk/raster/r.recode/r.recode.html (rev 0)
+++ grass/trunk/raster/r.recode/r.recode.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,78 @@
+<h2>DESCRIPTION</h2>
+
+<em>r.recode</em> creates an output map layer based on an input raster map
+layer. The output map layer will be a recoding of the input map layer based
+on recode rules input to <em>r.recode</em>. A <em>title</em> for the output
+map layer may be (optionally) specified by the user.<p>
+
+The recode rules are read from standard input (i.e., from the keyboard,
+redirected from a file, or piped through another program).<p>
+
+The program will be run non-interactively if the user specifies the name of
+the raster map layer to be recoded, the <em>name</em> of an output layer to
+hold recoded map, and (optionally) the name of a title for the output map.
+
+Rules are defined in one of these formats:
+<pre>
+ old_low:old_high:new_low:new_high
+ old_low:old_high:new_val (i.e. new_high == new_low)
+ *:old_val:new_val (interval [inf, old_val])
+ old_val:*:new_val (interval [old_val, inf])
+</pre>
+
+<em>r.recode</em> is loosely based on r.reclass and uses the GRASS reclass
+library to convert the rasters. It has routines for converting to every
+possible combination of raster (eg. int to double, double to float, etc).
+Standard floating point raster precision is float, with <em>-d</em> double
+precision will be written.<br>
+There are four basic routines that it accepts:
+
+<ol>
+<li>old-low to old-high is reclassed to new-low to new high , where the
+user provides all four values. The program figures on the fly what type of
+raster should be created.
+
+<li>old-low to old-high is reclassed to a single new value. Anything outside
+the range is null.
+
+<li> * to old-high will reclass everything less than old-high to a single
+new value.
+
+<li> old-low to * will reclass everything greater than old-low to a single
+new value.
+</ol>
+
+These four sets of arguments can be given on the command line, or piped via
+stdin or a file. More than one set of arguments is accepted.
+
+<h2>EXAMPLES</h2>
+
+<b>Map type conversion</b><br>
+
+To simply convert a raster between formats (eg. int to float) the user would
+use the first argument. For example <br>
+
+<tt>10:1500:0.1:15.0</tt><br>
+
+ would convert an old raster with range between 10 and 1500 to a float
+raster with range bewteen 0.1 and 15.0. <p>
+
+<b>Value replacement</b><br>
+
+r.recode can be used to replace existing cell values by others. The
+formatting is as described above. In following example the values 1, 2 and
+3 are replaced by 1.1, 7.5 resp. 0.4:<br>
+
+<pre>
+ r.recode in=oldmap out=newmap << EOF
+ 1:1:1.1:1.1
+ 2:2:7.5:7.5
+ 3:3:0.4:0.4
+ EOF
+</pre>
+
+
+<h2>AUTHOR</h2>
+CERL
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.region/description.html
===================================================================
--- grass/trunk/raster/r.region/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.region/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,35 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-The <em>r.region</em> program allows the user to manage the boundaries
-of a raster map. These boundaries can be set by the user directly
-and/or set from a region definition file (stored under the
-<kbd>windows</kbd> directory in the user's current mapset), a raster
-or vector map, or a 3dview file.
-<p>
-
-The <b>align</b> parameter allows to set the current resolution equal to
-that of the named raster map, and align the boundaries to a row and column
-edge in the named map. Alignment only moves the existing boundaries outward
-to the edges of the next nearest cell in the named raster map -- not to the
-named map's edges. To perform the latter function, use the
-<b>raster=</b><em>name</em> option.
-
-<h2>NOTE</h2>
-
-After all updates have been applied, the raster map's resolution
-settings are recomputed from the boundaries and the number of rows and
-columns in the raster map.
-
-<h2>SEE ALSO</h2>
-
-<em><a href="r.support.html">r.support</a></em><br>
-<em><a href="g.region.html">g.region</a></em>
-
-<h2>AUTHOR</h2>
-
-Glynn Clements
-
-<br>
-Based upon g.region
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.region/r.region.html (from rev 32770, grass/trunk/raster/r.region/description.html)
===================================================================
--- grass/trunk/raster/r.region/r.region.html (rev 0)
+++ grass/trunk/raster/r.region/r.region.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,35 @@
+<h2>DESCRIPTION</h2>
+
+The <em>r.region</em> program allows the user to manage the boundaries
+of a raster map. These boundaries can be set by the user directly
+and/or set from a region definition file (stored under the
+<kbd>windows</kbd> directory in the user's current mapset), a raster
+or vector map, or a 3dview file.
+<p>
+
+The <b>align</b> parameter allows to set the current resolution equal to
+that of the named raster map, and align the boundaries to a row and column
+edge in the named map. Alignment only moves the existing boundaries outward
+to the edges of the next nearest cell in the named raster map -- not to the
+named map's edges. To perform the latter function, use the
+<b>raster=</b><em>name</em> option.
+
+<h2>NOTE</h2>
+
+After all updates have been applied, the raster map's resolution
+settings are recomputed from the boundaries and the number of rows and
+columns in the raster map.
+
+<h2>SEE ALSO</h2>
+
+<em><a href="r.support.html">r.support</a></em><br>
+<em><a href="g.region.html">g.region</a></em>
+
+<h2>AUTHOR</h2>
+
+Glynn Clements
+
+<br>
+Based upon g.region
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.report/description.html
===================================================================
--- grass/trunk/raster/r.report/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.report/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,98 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>r.report</em> allows the user to set up a series of report parameters to
-be applied to a raster map layer, and creates a report. If invoked with
-command line arguments, the report will print out to the screen only.
-However, output may be redirected to a file or another program using the
-UNIX redirection mechanism. If invoked without command line arguments, the
-user is given the option of printing out each report and/or saving output to
-a file.
-
-<p>
-The report itself consists of two parts, a header section and the main body
-of the report.
-
-<p>
-The header section of the report identifies the raster map layer(s) (by map
-layer name and TITLE), location, mapset, report date, and the region of
-interest. The area of interest is described in two parts: the user's current
-geographic region is presented, and the mask is presented (if any is used).
-
-<p>
-The main body of the report consists of from one to three tables which
-present the statistics for each category and the totals for each unit
-column.
-
-<p>
-Note that, unlike <em><a href="r.stats.html">r.stats</a></em>,
-<em>r.report</em> allows the user to select the specific units of measure in
-which statistics will be reported.
-
-<p>
-Following is the result of a <em>r.report</em> run on the raster map layer
-<em>geology</em> (located in the Spearfish, SD sample data base), with the
-units expressed in square miles and acres. Here, <em>r.report</em> output is
-directed into the file <em>report.file</em>.
-
-<h2>EXAMPLE:</h2>
-<dl>
-<dd>
-<b>r.report map=</b><em>geology</em> <b>units=</b><em>miles,acres</em> > <em>report.file </em>
-</dl>
-
-<pre>
- ____________________________________________________________
-| RASTER MAP CATEGORY REPORT |
-| LOCATION: spearfish Fri Sep 2 09:20:09|
-|____________________________________________________________|
-| north: 4928000.00 east: 609000.00 |
-| REGION: south: 4914000.00 west: 590000.00 |
-| res: 100.00 res: 100.00 |
-|____________________________________________________________|
-| MASK: none |
-|____________________________________________________________|
-| MAP: geology in PERMANENT |
-|____________________________________________________________|
-| Category Information | Acres Square |
-| # description | Miles |
-|________|_________________________|_________________________|
-| 0 | no data | 415.13| 0.65 |
-| 1 | metamorphic | 2597.02| 4.06 |
-| 2 | transition | 32.12| 0.05 |
-| 3 | igneous | 8117.24| 12.68 |
-| 4 | sandstone | 16691.60| 26.08 |
-| 5 | limestone | 13681.93| 21.38 |
-| 6 | shale | 10304.07| 16.10 |
-| 7 | sandy shale | 2517.95| 3.93 |
-| 8 | claysand | 3229.60| 5.05 |
-| 9 | sand | 8141.95| 12.72 |
-|__________________________________|___________|_____________|
-| TOTAL | 65728.60| 102.70 |
-|__________________________________|___________|_____________|
-</pre>
-
-<h2>NOTES</h2>
-If the user runs <em>r.report</em> interactively and saves the report output
-in a file, this file will be placed into the user's current working
-directory.
-
-<p>
-If the user runs <em>r.report</em> non-interactively, report output can be
-saved by redirecting it to a file or a printer using the UNIX redirection
-mechanism.
-
-<h2>SEE ALSO</h2>
-
-<em><a href="g.region.html">g.region</a>,
-<a href="r.coin.html">r.coin</a>,
-<a href="r.describe.html">r.describe</a>,
-<a href="r.info.html">r.info</a>,
-<a href="r.stats.html">r.stats</a>,
-<a href="r.univar.html">r.univar</a>
-</em>
-
-<h2>AUTHOR</h2>
-Michael Shapiro,
-U.S. Army Construction Engineering Research Laboratory
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.report/r.report.html (from rev 32770, grass/trunk/raster/r.report/description.html)
===================================================================
--- grass/trunk/raster/r.report/r.report.html (rev 0)
+++ grass/trunk/raster/r.report/r.report.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,98 @@
+<h2>DESCRIPTION</h2>
+
+<em>r.report</em> allows the user to set up a series of report parameters to
+be applied to a raster map layer, and creates a report. If invoked with
+command line arguments, the report will print out to the screen only.
+However, output may be redirected to a file or another program using the
+UNIX redirection mechanism. If invoked without command line arguments, the
+user is given the option of printing out each report and/or saving output to
+a file.
+
+<p>
+The report itself consists of two parts, a header section and the main body
+of the report.
+
+<p>
+The header section of the report identifies the raster map layer(s) (by map
+layer name and TITLE), location, mapset, report date, and the region of
+interest. The area of interest is described in two parts: the user's current
+geographic region is presented, and the mask is presented (if any is used).
+
+<p>
+The main body of the report consists of from one to three tables which
+present the statistics for each category and the totals for each unit
+column.
+
+<p>
+Note that, unlike <em><a href="r.stats.html">r.stats</a></em>,
+<em>r.report</em> allows the user to select the specific units of measure in
+which statistics will be reported.
+
+<p>
+Following is the result of a <em>r.report</em> run on the raster map layer
+<em>geology</em> (located in the Spearfish, SD sample data base), with the
+units expressed in square miles and acres. Here, <em>r.report</em> output is
+directed into the file <em>report.file</em>.
+
+<h2>EXAMPLE:</h2>
+<dl>
+<dd>
+<b>r.report map=</b><em>geology</em> <b>units=</b><em>miles,acres</em> > <em>report.file </em>
+</dl>
+
+<pre>
+ ____________________________________________________________
+| RASTER MAP CATEGORY REPORT |
+| LOCATION: spearfish Fri Sep 2 09:20:09|
+|____________________________________________________________|
+| north: 4928000.00 east: 609000.00 |
+| REGION: south: 4914000.00 west: 590000.00 |
+| res: 100.00 res: 100.00 |
+|____________________________________________________________|
+| MASK: none |
+|____________________________________________________________|
+| MAP: geology in PERMANENT |
+|____________________________________________________________|
+| Category Information | Acres Square |
+| # description | Miles |
+|________|_________________________|_________________________|
+| 0 | no data | 415.13| 0.65 |
+| 1 | metamorphic | 2597.02| 4.06 |
+| 2 | transition | 32.12| 0.05 |
+| 3 | igneous | 8117.24| 12.68 |
+| 4 | sandstone | 16691.60| 26.08 |
+| 5 | limestone | 13681.93| 21.38 |
+| 6 | shale | 10304.07| 16.10 |
+| 7 | sandy shale | 2517.95| 3.93 |
+| 8 | claysand | 3229.60| 5.05 |
+| 9 | sand | 8141.95| 12.72 |
+|__________________________________|___________|_____________|
+| TOTAL | 65728.60| 102.70 |
+|__________________________________|___________|_____________|
+</pre>
+
+<h2>NOTES</h2>
+If the user runs <em>r.report</em> interactively and saves the report output
+in a file, this file will be placed into the user's current working
+directory.
+
+<p>
+If the user runs <em>r.report</em> non-interactively, report output can be
+saved by redirecting it to a file or a printer using the UNIX redirection
+mechanism.
+
+<h2>SEE ALSO</h2>
+
+<em><a href="g.region.html">g.region</a>,
+<a href="r.coin.html">r.coin</a>,
+<a href="r.describe.html">r.describe</a>,
+<a href="r.info.html">r.info</a>,
+<a href="r.stats.html">r.stats</a>,
+<a href="r.univar.html">r.univar</a>
+</em>
+
+<h2>AUTHOR</h2>
+Michael Shapiro,
+U.S. Army Construction Engineering Research Laboratory
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.resamp.interp/description.html
===================================================================
--- grass/trunk/raster/r.resamp.interp/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.resamp.interp/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,50 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>r.resamp.interp</em> resamples an input raster map by interpolating between
-the neighboring cells via a selectable resampling algorithm. All cells
-present in the neighborhood of the input raster cell must be non-null to
-generate a non-null cell in the output raster map. A choice of three
-interpolation methods is available; each uses the weighted values of a different
-number of adjacent cells in the input map to determine the value of each
-cell in the output map as follows:
-<ul>
-<li>nearest neighbour (1 cell)</li>
-<li>bilinear (4 cells)</li>
-<li>bicubic (16 cells)</li>
-</ul>
-
-This module is intended for reinterpolation of continuous data
-to a different resolution rather than for interpolation from scattered data
-(use the <em>v.surf.*</em> modules for that purpose).
-</p>
-
-
-<p>
-Note that for bilinear and bicubic interpolation,
-cells of the output raster that cannot be bounded by the appropriate number
-of input cell centers are set to NULL (NULL propagation). This could occur
-due to the input cells being outside the current region, being NULL or MASKed.
-</p>
-
-<h2>NOTES</h2>
-
-<p>
-For longitude-latitude databases, the interpolation algorithm is based on
-degree fractions, not on the absolute distances between cell centers. Any
-attempt to implement the latter would violate the integrity of the
-interpolation method.
-</p>
-
-
-<h2>SEE ALSO</h2>
-
-<em><a href="g.region.html">g.region</a></em>,
-<em><a href="r.resample.html">r.resample</a></em>,
-<em><a href="r.resamp.rst.html">r.resamp.rst</a></em>
-<em><a href="r.resamp.stats.html">r.resamp.stats</a></em>
-
-<h2>AUTHOR</h2>
-
-Glynn Clements
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.resamp.interp/r.resamp.interp.html (from rev 32770, grass/trunk/raster/r.resamp.interp/description.html)
===================================================================
--- grass/trunk/raster/r.resamp.interp/r.resamp.interp.html (rev 0)
+++ grass/trunk/raster/r.resamp.interp/r.resamp.interp.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,50 @@
+<h2>DESCRIPTION</h2>
+
+<em>r.resamp.interp</em> resamples an input raster map by interpolating between
+the neighboring cells via a selectable resampling algorithm. All cells
+present in the neighborhood of the input raster cell must be non-null to
+generate a non-null cell in the output raster map. A choice of three
+interpolation methods is available; each uses the weighted values of a different
+number of adjacent cells in the input map to determine the value of each
+cell in the output map as follows:
+<ul>
+<li>nearest neighbour (1 cell)</li>
+<li>bilinear (4 cells)</li>
+<li>bicubic (16 cells)</li>
+</ul>
+
+This module is intended for reinterpolation of continuous data
+to a different resolution rather than for interpolation from scattered data
+(use the <em>v.surf.*</em> modules for that purpose).
+</p>
+
+
+<p>
+Note that for bilinear and bicubic interpolation,
+cells of the output raster that cannot be bounded by the appropriate number
+of input cell centers are set to NULL (NULL propagation). This could occur
+due to the input cells being outside the current region, being NULL or MASKed.
+</p>
+
+<h2>NOTES</h2>
+
+<p>
+For longitude-latitude databases, the interpolation algorithm is based on
+degree fractions, not on the absolute distances between cell centers. Any
+attempt to implement the latter would violate the integrity of the
+interpolation method.
+</p>
+
+
+<h2>SEE ALSO</h2>
+
+<em><a href="g.region.html">g.region</a></em>,
+<em><a href="r.resample.html">r.resample</a></em>,
+<em><a href="r.resamp.rst.html">r.resamp.rst</a></em>
+<em><a href="r.resamp.stats.html">r.resamp.stats</a></em>
+
+<h2>AUTHOR</h2>
+
+Glynn Clements
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.resamp.rst/description.html
===================================================================
--- grass/trunk/raster/r.resamp.rst/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.resamp.rst/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,148 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<i>r.resamp.rst</i> reinterpolates the values a from given raster map (named
-<i>input</i>) to a new raster map (named <i>elev</i>).
-This module is intended for reinterpolation of continuous data
-to a different resolution rather than for interpolation from scattered data
-(use the <em>v.surf.*</em> modules for that purpose).
-
-Reinterpolation (resampling) is done to higher, same or lower resolution
-specified by the <i>ew_res</i> and <i>ns_res</i> parameters.
-<p>
-All resulting raster maps are created using the settings of the current
-region (which may be different from that of the <i>input</i> raster map).
-<p>
-Optionally, and simultaneously with interpolation, topographic parameters
-are computed from an input raster map containing z-values of elevation/depth: slope,
-aspect, profile curvature (measured in the direction of steepest
-slope), tangential curvature (measured in the direction of a tangent to
-contour line) and/or mean curvature are computed from and saved as raster maps
-as specified by the options <i>slope, aspect, pcurv, tcurv, mcurv</i> respectively.
-<p>
-If the <i>-d</i> flag is set the program outputs partial derivatives fx, fy,
-fxx, fxy, and fyy instead of slope, aspect and curvatures.
-<p>
-For noisy data it is possible to define spatially variable smoothing
-by providing a raster map named by the <i>smooth</i> option containing
-smoothing parameters.
-
-With the smoothing parameter set to zero (<i>smooth</i> is not given or
-contains zero data), the resulting surface passes exactly through the data
-points.
-<p>
-The user can also define a raster map (named with <i>maskmap</i>) which will
-be used as a mask. The interpolation is skipped for cells which have zero
-or NULL value in the mask.
-<p>
-Zero values will be assigned to these cells in all output raster maps.
-<!-- is this still true???? -->
-<p>
-The <i>zmult</i> parameter allows the user to rescale the z-values which may
-be useful, e.g., for transformation of elevations given in feet to meters,
-so that the proper values of slopes and curvatures can be computed.
-The default value is 1.
-<p>
-A regularized spline with tension method is used for the interpolation.
-The <i>tension</i> parameter tunes the character of the resulting surface
-from thin plate to membrane. Higher values of tension parameter reduce the
-overshoots that can appear in surfaces with rapid change of gradient.
-<p>
-The <i>-t</i> flag can be set to use "dnorm independent tension".
-<!-- but what is "dnorm independent tension" ??? -->
-<p>
-The interpolation is performed for overlapping rectangular segments.
-The user can define the width of overlap (in number of cells) with
-the <i>overlap</i> option. The default value is 3.
-<br>
-
-
-<h2>NOTES</h2>
-
-<i>r.resamp.rst</i> uses regularized spline with tension for interpolation
-(as described in Mitasova and Mitas, 1993).
-<p>
-The region is temporarily changed while writing output files with desired
-resolution. Topographic parameters are computed in the same way as in
-the <i>v.surf.rst</i> module. (See also Mitasova and Hofierka, 1993)
-<p>
-The raster map used with the <i>smooth</i> option should contain variable
-smoothing parameters. These can be derived from errors, slope, etc. using
-the <i>r.mapcalc</i> module.
-<p>
-The program gives warning when significant overshoots appear and higher
-tension should be used. However, with tension set too high the resulting surface
-changes its behavior to a membrane (rubber sheet stretched over the data
-points resulting in a peak or pit in each given point and everywhere else
-the surface goes rapidly to trend). Smoothing can be used to reduce
-the overshoots. When overshoots occur the resulting <i>elev</i> file will
-have white color in the locations of overshoots since the color table for
-the output file is the same as colortable for raster input file.
-<p>
-The program checks the numerical stability of the algorithm by computation
-of values at given points, and prints the maximum difference found into the
-history file of raster map <i>elev</i> (view with <i>r.info</i>).
-An increase in tension is suggested if the difference is unacceptable.
-For computations with smoothing set to 0 this difference should be 0.
-With a smoothing parameter greater than zero the surface will not pass through
-the data points exactly, and the higher the parameter the closer the surface
-will be to the trend.
-
-<p>
-The program writes the values of parameters used in computation into
-the comment part of the <i>elev</i> map history file. Additionally the
-following values are also written to assist in the evaluation of results
-and choosing of suitable parameters:
-<ul>
-<li>minimum and maximum z values in the data file (zmin_data, zmax_data) and
-in the interpolated raster map (zmin_int, zmax_int),</li>
-<li>maximum difference between the given and interpolated z value at a given
-point (errtotal),</li>
-<li>rescaling parameter used for normalization (dnorm), which influences the
-tension.</li>
-</ul>
-<p>
-The program gives a warning when the user wants to interpolate outside
-the region given by the <i>input</i> raster map's header data. Zooming into the
-area where the points are is suggested in this case.
-<p>
-When a mask is used, the program uses all points in the given region for
-interpolation, including those in the area which is masked out, to ensure
-proper interpolation along the border of the mask. It therefore does not
-mask out the data points; if this is desirable, it must be done outside
-<i>r.resamp.rst</i> before processing.
-
-<h2>SEE ALSO</h2>
-
-<a href="g.region.html">g.region</a>,
-<a href="r.info.html">r.info</a>,
-<a href="r.resample.html">r.resample</a>,
-<a href="r.mapcalc.html">r.mapcalc</a>,
-<a href="r.surf.contour.html">r.surf.contour</a>,
-<a href="v.surf.rst.html">v.surf.rst</a>
-
-<h2>AUTHORS</h2>
-
-<i>Original version of program (in FORTRAN):</i>
-<br>Lubos Mitas, NCSA, University of Illinois at Urbana Champaign, Il
-<br>Helena Mitasova, US Army CERL, Champaign, Illinois
-<p><i>Modified program (translated to C, adapted for GRASS , segmentation
-procedure):</i>
-<br>Irina Kosinovsky, US Army CERL.
-<br>Dave Gerdes, US Army CERL.
-
-<h2>REFERENCES</h2>
-
-Mitas, L., Mitasova, H., 1999, Spatial Interpolation. In: P.Longley, M.F.
-Goodchild, D.J. Maguire, D.W.Rhind (Eds.), Geographical Information Systems:
-Principles, Techniques, Management and Applications, Wiley, 481-492.
-<p>Mitasova, H. and Mitas, L., 1993. Interpolation by regularized spline
-with tension: I. Theory and implementation, Mathematical Geology No.25
-p.641-656.
-<p>Mitasova, H. and Hofierka, L., 1993. Interpolation by regularized spline
-with tension: II. Application to terrain modeling and surface geometry
-analysis, Mathematical Geology No.25 p.657-667.
-<p>Talmi, A. and Gilat, G., 1977. Method for smooth approximation
-of data, Journal of Computational Physics , 23, pp 93-123.
-<p>Wahba, G., 1990. Spline models for observational data, CNMS-NSF Regional
-Conference series in applied mathematics, 59, SIAM, Philadelphia, Pennsylvania.
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.resamp.rst/r.resamp.rst.html (from rev 32770, grass/trunk/raster/r.resamp.rst/description.html)
===================================================================
--- grass/trunk/raster/r.resamp.rst/r.resamp.rst.html (rev 0)
+++ grass/trunk/raster/r.resamp.rst/r.resamp.rst.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,148 @@
+<h2>DESCRIPTION</h2>
+
+<i>r.resamp.rst</i> reinterpolates the values a from given raster map (named
+<i>input</i>) to a new raster map (named <i>elev</i>).
+This module is intended for reinterpolation of continuous data
+to a different resolution rather than for interpolation from scattered data
+(use the <em>v.surf.*</em> modules for that purpose).
+
+Reinterpolation (resampling) is done to higher, same or lower resolution
+specified by the <i>ew_res</i> and <i>ns_res</i> parameters.
+<p>
+All resulting raster maps are created using the settings of the current
+region (which may be different from that of the <i>input</i> raster map).
+<p>
+Optionally, and simultaneously with interpolation, topographic parameters
+are computed from an input raster map containing z-values of elevation/depth: slope,
+aspect, profile curvature (measured in the direction of steepest
+slope), tangential curvature (measured in the direction of a tangent to
+contour line) and/or mean curvature are computed from and saved as raster maps
+as specified by the options <i>slope, aspect, pcurv, tcurv, mcurv</i> respectively.
+<p>
+If the <i>-d</i> flag is set the program outputs partial derivatives fx, fy,
+fxx, fxy, and fyy instead of slope, aspect and curvatures.
+<p>
+For noisy data it is possible to define spatially variable smoothing
+by providing a raster map named by the <i>smooth</i> option containing
+smoothing parameters.
+
+With the smoothing parameter set to zero (<i>smooth</i> is not given or
+contains zero data), the resulting surface passes exactly through the data
+points.
+<p>
+The user can also define a raster map (named with <i>maskmap</i>) which will
+be used as a mask. The interpolation is skipped for cells which have zero
+or NULL value in the mask.
+<p>
+Zero values will be assigned to these cells in all output raster maps.
+<!-- is this still true???? -->
+<p>
+The <i>zmult</i> parameter allows the user to rescale the z-values which may
+be useful, e.g., for transformation of elevations given in feet to meters,
+so that the proper values of slopes and curvatures can be computed.
+The default value is 1.
+<p>
+A regularized spline with tension method is used for the interpolation.
+The <i>tension</i> parameter tunes the character of the resulting surface
+from thin plate to membrane. Higher values of tension parameter reduce the
+overshoots that can appear in surfaces with rapid change of gradient.
+<p>
+The <i>-t</i> flag can be set to use "dnorm independent tension".
+<!-- but what is "dnorm independent tension" ??? -->
+<p>
+The interpolation is performed for overlapping rectangular segments.
+The user can define the width of overlap (in number of cells) with
+the <i>overlap</i> option. The default value is 3.
+<br>
+
+
+<h2>NOTES</h2>
+
+<i>r.resamp.rst</i> uses regularized spline with tension for interpolation
+(as described in Mitasova and Mitas, 1993).
+<p>
+The region is temporarily changed while writing output files with desired
+resolution. Topographic parameters are computed in the same way as in
+the <i>v.surf.rst</i> module. (See also Mitasova and Hofierka, 1993)
+<p>
+The raster map used with the <i>smooth</i> option should contain variable
+smoothing parameters. These can be derived from errors, slope, etc. using
+the <i>r.mapcalc</i> module.
+<p>
+The program gives warning when significant overshoots appear and higher
+tension should be used. However, with tension set too high the resulting surface
+changes its behavior to a membrane (rubber sheet stretched over the data
+points resulting in a peak or pit in each given point and everywhere else
+the surface goes rapidly to trend). Smoothing can be used to reduce
+the overshoots. When overshoots occur the resulting <i>elev</i> file will
+have white color in the locations of overshoots since the color table for
+the output file is the same as colortable for raster input file.
+<p>
+The program checks the numerical stability of the algorithm by computation
+of values at given points, and prints the maximum difference found into the
+history file of raster map <i>elev</i> (view with <i>r.info</i>).
+An increase in tension is suggested if the difference is unacceptable.
+For computations with smoothing set to 0 this difference should be 0.
+With a smoothing parameter greater than zero the surface will not pass through
+the data points exactly, and the higher the parameter the closer the surface
+will be to the trend.
+
+<p>
+The program writes the values of parameters used in computation into
+the comment part of the <i>elev</i> map history file. Additionally the
+following values are also written to assist in the evaluation of results
+and choosing of suitable parameters:
+<ul>
+<li>minimum and maximum z values in the data file (zmin_data, zmax_data) and
+in the interpolated raster map (zmin_int, zmax_int),</li>
+<li>maximum difference between the given and interpolated z value at a given
+point (errtotal),</li>
+<li>rescaling parameter used for normalization (dnorm), which influences the
+tension.</li>
+</ul>
+<p>
+The program gives a warning when the user wants to interpolate outside
+the region given by the <i>input</i> raster map's header data. Zooming into the
+area where the points are is suggested in this case.
+<p>
+When a mask is used, the program uses all points in the given region for
+interpolation, including those in the area which is masked out, to ensure
+proper interpolation along the border of the mask. It therefore does not
+mask out the data points; if this is desirable, it must be done outside
+<i>r.resamp.rst</i> before processing.
+
+<h2>SEE ALSO</h2>
+
+<a href="g.region.html">g.region</a>,
+<a href="r.info.html">r.info</a>,
+<a href="r.resample.html">r.resample</a>,
+<a href="r.mapcalc.html">r.mapcalc</a>,
+<a href="r.surf.contour.html">r.surf.contour</a>,
+<a href="v.surf.rst.html">v.surf.rst</a>
+
+<h2>AUTHORS</h2>
+
+<i>Original version of program (in FORTRAN):</i>
+<br>Lubos Mitas, NCSA, University of Illinois at Urbana Champaign, Il
+<br>Helena Mitasova, US Army CERL, Champaign, Illinois
+<p><i>Modified program (translated to C, adapted for GRASS , segmentation
+procedure):</i>
+<br>Irina Kosinovsky, US Army CERL.
+<br>Dave Gerdes, US Army CERL.
+
+<h2>REFERENCES</h2>
+
+Mitas, L., Mitasova, H., 1999, Spatial Interpolation. In: P.Longley, M.F.
+Goodchild, D.J. Maguire, D.W.Rhind (Eds.), Geographical Information Systems:
+Principles, Techniques, Management and Applications, Wiley, 481-492.
+<p>Mitasova, H. and Mitas, L., 1993. Interpolation by regularized spline
+with tension: I. Theory and implementation, Mathematical Geology No.25
+p.641-656.
+<p>Mitasova, H. and Hofierka, L., 1993. Interpolation by regularized spline
+with tension: II. Application to terrain modeling and surface geometry
+analysis, Mathematical Geology No.25 p.657-667.
+<p>Talmi, A. and Gilat, G., 1977. Method for smooth approximation
+of data, Journal of Computational Physics , 23, pp 93-123.
+<p>Wahba, G., 1990. Spline models for observational data, CNMS-NSF Regional
+Conference series in applied mathematics, 59, SIAM, Philadelphia, Pennsylvania.
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.resamp.stats/description.html
===================================================================
--- grass/trunk/raster/r.resamp.stats/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.resamp.stats/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,32 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<p>
-<em>r.resamp.stats</em> fills a grid cell (raster) matrix with
-aggregated values generated from a set of input layer data points.
-</p>
-
-<p>
-Without the <em>-w</em> switch, the aggregate is computed over all of
-the input cells whose centers lie within the output cell.
-</p>
-<p>
-With the <em>-w</em> switch, the aggregate uses the values from all
-input cells which intersect the output cell, weighted according to the
-proportion of the source cell which lies inside the output cell. This
-is slower, but produces a more accurate result.
-</p>
-
-<h2>NOTES</h2>
-
-<h2>SEE ALSO</h2>
-
-<em><a href="g.region.html">g.region</a></em>,
-<em><a href="r.resample.html">r.resample</a></em>,
-<em><a href="r.resamp.rst.html">r.resamp.rst</a></em>
-<em><a href="r.resamp.interp.html">r.resamp.interp</a></em>
-
-<h2>AUTHOR</h2>
-
-Glynn Clements
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.resamp.stats/r.resamp.stats.html (from rev 32770, grass/trunk/raster/r.resamp.stats/description.html)
===================================================================
--- grass/trunk/raster/r.resamp.stats/r.resamp.stats.html (rev 0)
+++ grass/trunk/raster/r.resamp.stats/r.resamp.stats.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,32 @@
+<h2>DESCRIPTION</h2>
+
+<p>
+<em>r.resamp.stats</em> fills a grid cell (raster) matrix with
+aggregated values generated from a set of input layer data points.
+</p>
+
+<p>
+Without the <em>-w</em> switch, the aggregate is computed over all of
+the input cells whose centers lie within the output cell.
+</p>
+<p>
+With the <em>-w</em> switch, the aggregate uses the values from all
+input cells which intersect the output cell, weighted according to the
+proportion of the source cell which lies inside the output cell. This
+is slower, but produces a more accurate result.
+</p>
+
+<h2>NOTES</h2>
+
+<h2>SEE ALSO</h2>
+
+<em><a href="g.region.html">g.region</a></em>,
+<em><a href="r.resample.html">r.resample</a></em>,
+<em><a href="r.resamp.rst.html">r.resamp.rst</a></em>
+<em><a href="r.resamp.interp.html">r.resamp.interp</a></em>
+
+<h2>AUTHOR</h2>
+
+Glynn Clements
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.resample/description.html
===================================================================
--- grass/trunk/raster/r.resample/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.resample/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,49 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>r.resample</em> resamples the data values in a user-specified raster
-input map layer <em>name</em> (bounded by the current geographic region
-and masked by the current mask), and produces a new raster output map layer
-<em>name</em> containing the results of the resampling.
-The category values in the new raster output map layer will be the same
-as those in the original, except that the resolution and extent of the
-new raster output map layer will match those of the current geographic region
-settings (see <em><a href="g.region.html">g.region</a></em>).
-<em>r.resample</em> is intended for reinterpolation of continuous data
-to a different resolution rather than for interpolation from scattered data
-(use the <em>v.surf.*</em> modules for that purpose).
-
-<h2>NOTES</h2>
-
-The method by which resampling is conducted is "nearest neighbor"
-(see <em><a href="r.neighbors.html">r.neighbors</a></em>).
-The resulting raster map layer will have the same
-resolution as the resolution of the current geographic region
-(set using <em><a href="g.region.html">g.region</a></em>).
-
-<p>
-The resulting raster map layer may be identical to the original raster
-map layer. The <em>r.resample</em> program will copy the color table
-and history file associated with the original raster map
-layer for the resulting raster map layer and will create a modified
-category file which contains description of only those categories
-which appear in resampled file.
-
-<p>
-
-When the user resamples a GRASS <em>reclass</em> file, a true raster map
-is created by <em>r.resample</em>.
-
-<h2>SEE ALSO</h2>
-
-<em><a href="g.region.html">g.region</a></em>,
-<em><a href="r.mapcalc.html">r.mapcalc</a></em>,
-<em><a href="r.mfilter.html">r.mfilter</a></em>,
-<em><a href="r.neighbors.html">r.neighbors</a></em>,
-<em><a href="r.rescale.html">r.rescale</a></em>
-
-<h2>AUTHOR</h2>
-
-Michael Shapiro,
-U.S.Army Construction Engineering Research Laboratory
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.resample/r.resample.html (from rev 32770, grass/trunk/raster/r.resample/description.html)
===================================================================
--- grass/trunk/raster/r.resample/r.resample.html (rev 0)
+++ grass/trunk/raster/r.resample/r.resample.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,49 @@
+<h2>DESCRIPTION</h2>
+
+<em>r.resample</em> resamples the data values in a user-specified raster
+input map layer <em>name</em> (bounded by the current geographic region
+and masked by the current mask), and produces a new raster output map layer
+<em>name</em> containing the results of the resampling.
+The category values in the new raster output map layer will be the same
+as those in the original, except that the resolution and extent of the
+new raster output map layer will match those of the current geographic region
+settings (see <em><a href="g.region.html">g.region</a></em>).
+<em>r.resample</em> is intended for reinterpolation of continuous data
+to a different resolution rather than for interpolation from scattered data
+(use the <em>v.surf.*</em> modules for that purpose).
+
+<h2>NOTES</h2>
+
+The method by which resampling is conducted is "nearest neighbor"
+(see <em><a href="r.neighbors.html">r.neighbors</a></em>).
+The resulting raster map layer will have the same
+resolution as the resolution of the current geographic region
+(set using <em><a href="g.region.html">g.region</a></em>).
+
+<p>
+The resulting raster map layer may be identical to the original raster
+map layer. The <em>r.resample</em> program will copy the color table
+and history file associated with the original raster map
+layer for the resulting raster map layer and will create a modified
+category file which contains description of only those categories
+which appear in resampled file.
+
+<p>
+
+When the user resamples a GRASS <em>reclass</em> file, a true raster map
+is created by <em>r.resample</em>.
+
+<h2>SEE ALSO</h2>
+
+<em><a href="g.region.html">g.region</a></em>,
+<em><a href="r.mapcalc.html">r.mapcalc</a></em>,
+<em><a href="r.mfilter.html">r.mfilter</a></em>,
+<em><a href="r.neighbors.html">r.neighbors</a></em>,
+<em><a href="r.rescale.html">r.rescale</a></em>
+
+<h2>AUTHOR</h2>
+
+Michael Shapiro,
+U.S.Army Construction Engineering Research Laboratory
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.rescale/description.html
===================================================================
--- grass/trunk/raster/r.rescale/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.rescale/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,60 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-The <em>r.rescale</em> program rescales the range of
-category values appearing in a raster map layer. A new
-raster map layer, and an appropriate category file and
-color table based upon the original raster map layer, are
-generated with category labels that reflect the original
-category values that produced each category. This command
-is useful for producing representations with a reduced
-number of categories from a raster map layer with a large
-range of category values (e.g., elevation).
-<em>Rescaled</em> map layers are appropriate for use in
-such GRASS programs as
-
-<em><a href="r.stats.html">r.stats</a></em>,
-<em><a href="r.report.html">r.report</a></em>, and
-<em><a href="r.coin.html">r.coin</a></em>.
-
-<h2>EXAMPLE</h2>
-
-To rescale an elevation raster map layer with category
-values ranging from 1090 meters to 1800 meters into the
-range 0-255, the following command line could be used:
-
-<dl>
-<dd>
-<b>r.rescale input=</b>elevation <b>from=</b>1090,1800 <b>output=</b>elevation.255 <b>to=</b>0,255
-</dl>
-
-<h2>NOTES</h2>
-
-Category values that fall beyond the input range will
-become NULL. This allows the user to select a subset of
-the full category value range for rescaling if desired.
-This also means that the user should know the category
-value range for the input raster map layer. The user can
-request the </b><em>r.rescale</em> program to determine
-this range, or can obtain it using the
-<em><a href="r.describe.html">r.describe</a></em> or <em><a href="r.info.html">r.info</a></em>
-command. If the category value range is determined using
-<em>r.rescale</em>, the input raster map layer is examined,
-and the minimum and maximum non-NULL category values are
-selected as the input range.
-
-<h2>SEE ALSO</h2>
-
-<em><a href="r.coin.html">r.coin</a></em>,
-<em><a href="r.describe.html">r.describe</a></em>,
-<em><a href="r.info.html">r.info</a></em>,
-<em><a href="r.mapcalc.html">r.mapcalc</a></em>,
-<em><a href="r.reclass.html">r.reclass</a></em>,
-<em><a href="r.report.html">r.report</a></em>,
-<em><a href="r.resample.html">r.resample</a></em>,
-<em><a href="r.stats.html">r.stats</a></em>
-
-<h2>AUTHOR</h2>
-Michael Shapiro,
-U.S.Army Construction Engineering Research Laboratory
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.rescale/r.rescale.html (from rev 32770, grass/trunk/raster/r.rescale/description.html)
===================================================================
--- grass/trunk/raster/r.rescale/r.rescale.html (rev 0)
+++ grass/trunk/raster/r.rescale/r.rescale.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,60 @@
+<h2>DESCRIPTION</h2>
+
+The <em>r.rescale</em> program rescales the range of
+category values appearing in a raster map layer. A new
+raster map layer, and an appropriate category file and
+color table based upon the original raster map layer, are
+generated with category labels that reflect the original
+category values that produced each category. This command
+is useful for producing representations with a reduced
+number of categories from a raster map layer with a large
+range of category values (e.g., elevation).
+<em>Rescaled</em> map layers are appropriate for use in
+such GRASS programs as
+
+<em><a href="r.stats.html">r.stats</a></em>,
+<em><a href="r.report.html">r.report</a></em>, and
+<em><a href="r.coin.html">r.coin</a></em>.
+
+<h2>EXAMPLE</h2>
+
+To rescale an elevation raster map layer with category
+values ranging from 1090 meters to 1800 meters into the
+range 0-255, the following command line could be used:
+
+<dl>
+<dd>
+<b>r.rescale input=</b>elevation <b>from=</b>1090,1800 <b>output=</b>elevation.255 <b>to=</b>0,255
+</dl>
+
+<h2>NOTES</h2>
+
+Category values that fall beyond the input range will
+become NULL. This allows the user to select a subset of
+the full category value range for rescaling if desired.
+This also means that the user should know the category
+value range for the input raster map layer. The user can
+request the </b><em>r.rescale</em> program to determine
+this range, or can obtain it using the
+<em><a href="r.describe.html">r.describe</a></em> or <em><a href="r.info.html">r.info</a></em>
+command. If the category value range is determined using
+<em>r.rescale</em>, the input raster map layer is examined,
+and the minimum and maximum non-NULL category values are
+selected as the input range.
+
+<h2>SEE ALSO</h2>
+
+<em><a href="r.coin.html">r.coin</a></em>,
+<em><a href="r.describe.html">r.describe</a></em>,
+<em><a href="r.info.html">r.info</a></em>,
+<em><a href="r.mapcalc.html">r.mapcalc</a></em>,
+<em><a href="r.reclass.html">r.reclass</a></em>,
+<em><a href="r.report.html">r.report</a></em>,
+<em><a href="r.resample.html">r.resample</a></em>,
+<em><a href="r.stats.html">r.stats</a></em>
+
+<h2>AUTHOR</h2>
+Michael Shapiro,
+U.S.Army Construction Engineering Research Laboratory
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.rescale.eq/description.html
===================================================================
--- grass/trunk/raster/r.rescale.eq/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.rescale.eq/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,61 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-The <em>r.rescale.eq</em> program rescales the range of
-category values appearing in a raster map layer with equalized histogram.
-A new raster map layer, and an appropriate category file and
-color table based upon the original raster map layer, are
-generated with category labels that reflect the original
-category values that produced each category. This command
-is useful for producing representations with a reduced
-number of categories from a raster map layer with a large
-range of category values (e.g., elevation).
-<em>Rescaled</em> map layers are appropriate for use in
-such GRASS programs as
-
-<em><a href="r.stats.html">r.stats</a></em>,
-<em><a href="r.report.html">r.report</a></em>, and
-<em><a href="r.coin.html">r.coin</a></em>.
-
-<h2>EXAMPLE</h2>
-
-To rescale an elevation raster map layer with category
-values ranging from 1090 meters to 1800 meters into the
-range 0-255, the following command line could be used:
-
-<dl>
-<dd>
-<b>r.rescale.eq input=</b>elevation <b>from=</b>1090,1800 <b>output=</b>elevation.255 <b>to=</b>0,255
-</dl>
-
-<h2>NOTES</h2>
-
-Category values that fall beyond the input range will
-become NULL. This allows the user to select a subset of
-the full category value range for rescaling if desired.
-This also means that the user should know the category
-value range for the input raster map layer. The user can
-request the </b><em>r.rescale.eq</em> program to determine
-this range, or can obtain it using the
-<em><a href="r.describe.html">r.describe</a></em> or
-<em><a href="r.info.html">r.info</a></em>
-command. If the category value range is determined using
-<em>r.rescale.eq</em>, the input raster map layer is examined,
-and the minimum and maximum non-NULL category values are
-selected as the input range.
-
-<h2>SEE ALSO</h2>
-
-<em><a href="r.coin.html">r.coin</a></em>,
-<em><a href="r.describe.html">r.describe</a></em>,
-<em><a href="r.info.html">r.info</a></em>,
-<em><a href="r.mapcalc.html">r.mapcalc</a></em>,
-<em><a href="r.reclass.html">r.reclass</a></em>,
-<em><a href="r.report.html">r.report</a></em>,
-<em><a href="r.resample.html">r.resample</a></em>,
-<em><a href="r.stats.html">r.stats</a></em>
-
-<h2>AUTHOR</h2>
-Michael Shapiro,
-U.S.Army Construction Engineering Research Laboratory
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.rescale.eq/r.rescale.eq.html (from rev 32770, grass/trunk/raster/r.rescale.eq/description.html)
===================================================================
--- grass/trunk/raster/r.rescale.eq/r.rescale.eq.html (rev 0)
+++ grass/trunk/raster/r.rescale.eq/r.rescale.eq.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,61 @@
+<h2>DESCRIPTION</h2>
+
+The <em>r.rescale.eq</em> program rescales the range of
+category values appearing in a raster map layer with equalized histogram.
+A new raster map layer, and an appropriate category file and
+color table based upon the original raster map layer, are
+generated with category labels that reflect the original
+category values that produced each category. This command
+is useful for producing representations with a reduced
+number of categories from a raster map layer with a large
+range of category values (e.g., elevation).
+<em>Rescaled</em> map layers are appropriate for use in
+such GRASS programs as
+
+<em><a href="r.stats.html">r.stats</a></em>,
+<em><a href="r.report.html">r.report</a></em>, and
+<em><a href="r.coin.html">r.coin</a></em>.
+
+<h2>EXAMPLE</h2>
+
+To rescale an elevation raster map layer with category
+values ranging from 1090 meters to 1800 meters into the
+range 0-255, the following command line could be used:
+
+<dl>
+<dd>
+<b>r.rescale.eq input=</b>elevation <b>from=</b>1090,1800 <b>output=</b>elevation.255 <b>to=</b>0,255
+</dl>
+
+<h2>NOTES</h2>
+
+Category values that fall beyond the input range will
+become NULL. This allows the user to select a subset of
+the full category value range for rescaling if desired.
+This also means that the user should know the category
+value range for the input raster map layer. The user can
+request the </b><em>r.rescale.eq</em> program to determine
+this range, or can obtain it using the
+<em><a href="r.describe.html">r.describe</a></em> or
+<em><a href="r.info.html">r.info</a></em>
+command. If the category value range is determined using
+<em>r.rescale.eq</em>, the input raster map layer is examined,
+and the minimum and maximum non-NULL category values are
+selected as the input range.
+
+<h2>SEE ALSO</h2>
+
+<em><a href="r.coin.html">r.coin</a></em>,
+<em><a href="r.describe.html">r.describe</a></em>,
+<em><a href="r.info.html">r.info</a></em>,
+<em><a href="r.mapcalc.html">r.mapcalc</a></em>,
+<em><a href="r.reclass.html">r.reclass</a></em>,
+<em><a href="r.report.html">r.report</a></em>,
+<em><a href="r.resample.html">r.resample</a></em>,
+<em><a href="r.stats.html">r.stats</a></em>
+
+<h2>AUTHOR</h2>
+Michael Shapiro,
+U.S.Army Construction Engineering Research Laboratory
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.series/description.html
===================================================================
--- grass/trunk/raster/r.series/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.series/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,66 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-
-<em>r.series</em> makes each output cell value a function of the values
-assigned to the corresponding cells in the input raster map layers.
-Following methods are available:
-
-<ul>
- <li>average: average value
- <li>count: count of non-NULL cells
- <li>median: median value
- <li>mode: most frequently occuring value
- <li>minimum: lowest value
- <li>maximum: highest value
- <li>range: range of values (max - min)
- <li>stddev: standard deviation
- <li>sum: sum of values
- <li>variance: statistical variance
- <li>diversity: number of different values
- <li>slope: linear regression slope
- <li>offset: linear regression offset
- <li>detcoeff: linear regression coefficient of determination
- <li>min_raster: raster map number with the minimum time-series value
- <li>max_raster: raster map number with the maximum time-series value
- </ul>
-
-<h2>NOTES</h2>
-
-With <em>-n</em> flag, any cell for which any of the corresponding input cells are
-NULL is automatically set to NULL (NULL propagation). The aggregate function is not
-called, so all methods behave this way with respect to the <em>-n</em> flag.
-<p>
-Without <em>-n</em> flag, the complete list of inputs for each cell (including
-NULLs) is passed to the aggregate function. Individual aggregates can
-handle data as they choose. Mostly, they just compute the aggregate
-over the non-NULL values, producing a NULL result only if all inputs
-are NULL.
-<p>
-The <em>min_raster</em> and <em>max_raster</em> methods generate a map with the
-number of the raster map that holds the minimum/maximum value of the
-time-series. The numbering starts at <em>0</em> up to <em>n</em> for the
-first and the last raster listed in <em>input=</em>, respectively.
-
-
-
-<h2>EXAMPLE</h2>
-
-Using <em>r.series</em> with wildcards:
-<br>
-<tt>r.series input="`g.mlist pattern='insitu_data.*' sep=,`"
- output=insitu_data.stddev method=stddev</tt>
-<p>
-
-Note the <em>g.mlist</em> script also supports regular expressions for
-selecting map names.
-
-<h2>SEE ALSO</h2>
-
-<em><a href="g.mlist.html">g.mlist</a></em>,
-<em><a href="g.region.html">g.region</a></em>
-
-<h2>AUTHOR</h2>
-
-Glynn Clements
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.series/r.series.html (from rev 32770, grass/trunk/raster/r.series/description.html)
===================================================================
--- grass/trunk/raster/r.series/r.series.html (rev 0)
+++ grass/trunk/raster/r.series/r.series.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,66 @@
+<h2>DESCRIPTION</h2>
+
+
+<em>r.series</em> makes each output cell value a function of the values
+assigned to the corresponding cells in the input raster map layers.
+Following methods are available:
+
+<ul>
+ <li>average: average value
+ <li>count: count of non-NULL cells
+ <li>median: median value
+ <li>mode: most frequently occuring value
+ <li>minimum: lowest value
+ <li>maximum: highest value
+ <li>range: range of values (max - min)
+ <li>stddev: standard deviation
+ <li>sum: sum of values
+ <li>variance: statistical variance
+ <li>diversity: number of different values
+ <li>slope: linear regression slope
+ <li>offset: linear regression offset
+ <li>detcoeff: linear regression coefficient of determination
+ <li>min_raster: raster map number with the minimum time-series value
+ <li>max_raster: raster map number with the maximum time-series value
+ </ul>
+
+<h2>NOTES</h2>
+
+With <em>-n</em> flag, any cell for which any of the corresponding input cells are
+NULL is automatically set to NULL (NULL propagation). The aggregate function is not
+called, so all methods behave this way with respect to the <em>-n</em> flag.
+<p>
+Without <em>-n</em> flag, the complete list of inputs for each cell (including
+NULLs) is passed to the aggregate function. Individual aggregates can
+handle data as they choose. Mostly, they just compute the aggregate
+over the non-NULL values, producing a NULL result only if all inputs
+are NULL.
+<p>
+The <em>min_raster</em> and <em>max_raster</em> methods generate a map with the
+number of the raster map that holds the minimum/maximum value of the
+time-series. The numbering starts at <em>0</em> up to <em>n</em> for the
+first and the last raster listed in <em>input=</em>, respectively.
+
+
+
+<h2>EXAMPLE</h2>
+
+Using <em>r.series</em> with wildcards:
+<br>
+<tt>r.series input="`g.mlist pattern='insitu_data.*' sep=,`"
+ output=insitu_data.stddev method=stddev</tt>
+<p>
+
+Note the <em>g.mlist</em> script also supports regular expressions for
+selecting map names.
+
+<h2>SEE ALSO</h2>
+
+<em><a href="g.mlist.html">g.mlist</a></em>,
+<em><a href="g.region.html">g.region</a></em>
+
+<h2>AUTHOR</h2>
+
+Glynn Clements
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.slope.aspect/description.html
===================================================================
--- grass/trunk/raster/r.slope.aspect/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.slope.aspect/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,174 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<b>r.slope.aspect </b>generates raster maps of slope, aspect, curvatures and
-first and second order partial derivatives from a raster map of true
-elevation values. The user must specify the input <i>elevation</i> file name
-and at least one output file name. The user can also specify the
-<i>format</i> for slope (degrees, percent; default=degrees), and the
-<i>zfactor</i>: multiplicative factor to convert elevation units to meters;
-(default 1.0).
-<p>
-The <i>elevation</i> input raster map specified by the user must contain true
-elevation values, <b>not</b> rescaled or categorized data. If the elevation
-values are in feet or other units than meters (with a conversion factor
-<i>meters:</i>, defined in PROJ_UNITS), they must be converted to meters using
-the parameter <i>zfactor</i>.
-<p>
-The <i>aspect</i> output raster map indicates the direction that slopes are
-facing. The aspect categories represent the number degrees of east. Category
-and color table files are also generated for the aspect map layer. The aspect
-categories represent the number degrees of east and they increase
-counterclockwise: 90deg is North, 180 is West, 270 is South 360 is East. The
-aspect value 0 is used to indicate undefined aspect in flat areas with slope=0.
-<p>
-The <i>slope</i> output raster map contains slope values, stated in degrees of
-inclination from the horizontal if <i>format</i>=degrees option (the default)
-is chosen, and in percent rise if <i>format</i>=percent option is chosen.
-Category and color table files are generated.
-<p>
-Profile and tangential curvatures are the curvatures in the direction of
-steepest slope and in the direction of the contour tangent respectively. The
-curvatures are expressed as 1/metres, e.g. a curvature of 0.05 corresponds to a
-radius of curvature of 20m.
-
-<p>
-<table width="100%" border="0">
- <tr valign="baseline">
- <td>
- <div align="center">
- <img src="dem.png" border="1">
- <P>
- Example DEM
- <BR><BR>
- </div>
- </td>
- <td>
- </td>
- </tr>
-
- <tr valign="baseline">
- <td>
- <div align="center">
- <img src="slope.png" border="1">
- <P>
- Slope (degree) from example DEM
- <BR><BR>
- </div>
- </td>
- <td>
- <div align="center">
- <img src="aspect.png" border="1">
- <P>
- Aspect (degree) from example DEM
- <BR><BR>
- </div>
- </td>
- </tr>
-
- <tr valign="baseline">
- <td>
- <div align="center">
- <img src="tcurv.png" border="1">
- <P>
- Tangential curvature (m<sup>-1</sup>) from example DEM
- <BR><BR>
- </div>
- </td>
- <td>
- <div align="center">
- <img src="pcurv.png" border="1">
- <P>
- Profile curvature (m<sup>-1</sup>) from example DEM
- <BR><BR>
- </div>
- </td>
- <td>
- </td>
- </tr>
-</table>
-
-<p>
-For some applications, the user will wish to use a reclassified raster map
-of slope that groups slope values into ranges of slope. This can be done using
-<i><a href="r.reclass.html">r.reclass</a></i>. An example of a useful
-reclassification is given below:
-<div class="code"><pre> category range category labels
- (in degrees) (in percent)
-
- 1 0- 1 0- 2%
- 2 2- 3 3- 5%
- 3 4- 5 6- 10%
- 4 6- 8 11- 15%
- 5 9- 11 16- 20%
- 6 12- 14 21- 25%
- 7 15- 90 26% and higher
-
- The following color table works well with the above
- reclassification.
-
- category red green blue
-
- 0 179 179 179
- 1 0 102 0
- 2 0 153 0
- 3 128 153 0
- 4 204 179 0
- 5 128 51 51
- 6 255 0 0
- 7 0 0 0</pre></div>
-
-<h2>NOTES</h2>
-
-To ensure that the raster elevation map layer is not inappropriately resampled,
-the settings for the current region are modified slightly (for the execution
-of the program only): the resolution is set to match the resolution of
-the elevation map and the edges of the region (i.e. the north, south, east
-and west) are shifted, if necessary, to line up along edges of the nearest
-cells in the elevation map. If the user really wants the elevation map
-resampled to the current region resolution, the -a flag should be specified.
-
-<p>
-The current mask is ignored.
-
-<p>
-The algorithm used to determine slope and aspect uses a 3x3 neighborhood
-around each cell in the elevation file. Thus, it is not possible to determine
-slope and aspect for the cells adjacent to the edges in the elevation map
-layer. These cells are assigned a "zero slope" value (category 0) in both
-the slope and aspect raster map layers.
-
-<p>
-Horn's formula is used to find the derivatives in x and y directions.
-
-<p>
-Only when using integer elevation models, the aspect is biased in 0,
-45, 90, 180, 225, 270, 315, and 360 directions; i.e., the distribution
-of aspect categories is very uneven, with peaks at 0, 45,..., 360 categories.
-When working with floating point elevation models, no such aspect bias occurs.
-
-<p>
-Because most cells with a very small slope end up having category 0,
-45, ..., 360, it is sometimes possible to reduce the bias in these directions
-by filtering out the aspect in areas where the terrain is almost flat. A new
-option <i>min_slp_allowed</i> was added to specify the minimum slope for which
-aspect is computed. The aspect for all cells with slope <
-<i>min_slp_allowed</i> is set to <b>null</b>.
-
-
-<h2>REFERENCE</h2>
-
-Horn, B. K. P. (1981). Hill Shading and the Reflectance Map, Proceedings
-of the IEEE, 69(1):14-47.
-
-<h2>SEE ALSO</h2>
-<em><a href="r.mapcalc.html">r.mapcalc</a></em>,
-<em><a href="r.neighbors.html">r.neighbors</a></em>,
-<em><a href="r.reclass.html">r.reclass</a></em>,
-<em><a href="r.rescale.html">r.rescale</a></em>
-
-<h2>AUTHORS</h2>
-Michael Shapiro, U.S.Army Construction Engineering Research Laboratory<BR>
-Olga Waupotitsch, U.S.Army Construction Engineering Research Laboratory
-
-<p>
-<i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.slope.aspect/r.slope.aspect.html (from rev 32770, grass/trunk/raster/r.slope.aspect/description.html)
===================================================================
--- grass/trunk/raster/r.slope.aspect/r.slope.aspect.html (rev 0)
+++ grass/trunk/raster/r.slope.aspect/r.slope.aspect.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,174 @@
+<h2>DESCRIPTION</h2>
+
+<b>r.slope.aspect </b>generates raster maps of slope, aspect, curvatures and
+first and second order partial derivatives from a raster map of true
+elevation values. The user must specify the input <i>elevation</i> file name
+and at least one output file name. The user can also specify the
+<i>format</i> for slope (degrees, percent; default=degrees), and the
+<i>zfactor</i>: multiplicative factor to convert elevation units to meters;
+(default 1.0).
+<p>
+The <i>elevation</i> input raster map specified by the user must contain true
+elevation values, <b>not</b> rescaled or categorized data. If the elevation
+values are in feet or other units than meters (with a conversion factor
+<i>meters:</i>, defined in PROJ_UNITS), they must be converted to meters using
+the parameter <i>zfactor</i>.
+<p>
+The <i>aspect</i> output raster map indicates the direction that slopes are
+facing. The aspect categories represent the number degrees of east. Category
+and color table files are also generated for the aspect map layer. The aspect
+categories represent the number degrees of east and they increase
+counterclockwise: 90deg is North, 180 is West, 270 is South 360 is East. The
+aspect value 0 is used to indicate undefined aspect in flat areas with slope=0.
+<p>
+The <i>slope</i> output raster map contains slope values, stated in degrees of
+inclination from the horizontal if <i>format</i>=degrees option (the default)
+is chosen, and in percent rise if <i>format</i>=percent option is chosen.
+Category and color table files are generated.
+<p>
+Profile and tangential curvatures are the curvatures in the direction of
+steepest slope and in the direction of the contour tangent respectively. The
+curvatures are expressed as 1/metres, e.g. a curvature of 0.05 corresponds to a
+radius of curvature of 20m.
+
+<p>
+<table width="100%" border="0">
+ <tr valign="baseline">
+ <td>
+ <div align="center">
+ <img src="dem.png" border="1">
+ <P>
+ Example DEM
+ <BR><BR>
+ </div>
+ </td>
+ <td>
+ </td>
+ </tr>
+
+ <tr valign="baseline">
+ <td>
+ <div align="center">
+ <img src="slope.png" border="1">
+ <P>
+ Slope (degree) from example DEM
+ <BR><BR>
+ </div>
+ </td>
+ <td>
+ <div align="center">
+ <img src="aspect.png" border="1">
+ <P>
+ Aspect (degree) from example DEM
+ <BR><BR>
+ </div>
+ </td>
+ </tr>
+
+ <tr valign="baseline">
+ <td>
+ <div align="center">
+ <img src="tcurv.png" border="1">
+ <P>
+ Tangential curvature (m<sup>-1</sup>) from example DEM
+ <BR><BR>
+ </div>
+ </td>
+ <td>
+ <div align="center">
+ <img src="pcurv.png" border="1">
+ <P>
+ Profile curvature (m<sup>-1</sup>) from example DEM
+ <BR><BR>
+ </div>
+ </td>
+ <td>
+ </td>
+ </tr>
+</table>
+
+<p>
+For some applications, the user will wish to use a reclassified raster map
+of slope that groups slope values into ranges of slope. This can be done using
+<i><a href="r.reclass.html">r.reclass</a></i>. An example of a useful
+reclassification is given below:
+<div class="code"><pre> category range category labels
+ (in degrees) (in percent)
+
+ 1 0- 1 0- 2%
+ 2 2- 3 3- 5%
+ 3 4- 5 6- 10%
+ 4 6- 8 11- 15%
+ 5 9- 11 16- 20%
+ 6 12- 14 21- 25%
+ 7 15- 90 26% and higher
+
+ The following color table works well with the above
+ reclassification.
+
+ category red green blue
+
+ 0 179 179 179
+ 1 0 102 0
+ 2 0 153 0
+ 3 128 153 0
+ 4 204 179 0
+ 5 128 51 51
+ 6 255 0 0
+ 7 0 0 0</pre></div>
+
+<h2>NOTES</h2>
+
+To ensure that the raster elevation map layer is not inappropriately resampled,
+the settings for the current region are modified slightly (for the execution
+of the program only): the resolution is set to match the resolution of
+the elevation map and the edges of the region (i.e. the north, south, east
+and west) are shifted, if necessary, to line up along edges of the nearest
+cells in the elevation map. If the user really wants the elevation map
+resampled to the current region resolution, the -a flag should be specified.
+
+<p>
+The current mask is ignored.
+
+<p>
+The algorithm used to determine slope and aspect uses a 3x3 neighborhood
+around each cell in the elevation file. Thus, it is not possible to determine
+slope and aspect for the cells adjacent to the edges in the elevation map
+layer. These cells are assigned a "zero slope" value (category 0) in both
+the slope and aspect raster map layers.
+
+<p>
+Horn's formula is used to find the derivatives in x and y directions.
+
+<p>
+Only when using integer elevation models, the aspect is biased in 0,
+45, 90, 180, 225, 270, 315, and 360 directions; i.e., the distribution
+of aspect categories is very uneven, with peaks at 0, 45,..., 360 categories.
+When working with floating point elevation models, no such aspect bias occurs.
+
+<p>
+Because most cells with a very small slope end up having category 0,
+45, ..., 360, it is sometimes possible to reduce the bias in these directions
+by filtering out the aspect in areas where the terrain is almost flat. A new
+option <i>min_slp_allowed</i> was added to specify the minimum slope for which
+aspect is computed. The aspect for all cells with slope <
+<i>min_slp_allowed</i> is set to <b>null</b>.
+
+
+<h2>REFERENCE</h2>
+
+Horn, B. K. P. (1981). Hill Shading and the Reflectance Map, Proceedings
+of the IEEE, 69(1):14-47.
+
+<h2>SEE ALSO</h2>
+<em><a href="r.mapcalc.html">r.mapcalc</a></em>,
+<em><a href="r.neighbors.html">r.neighbors</a></em>,
+<em><a href="r.reclass.html">r.reclass</a></em>,
+<em><a href="r.rescale.html">r.rescale</a></em>
+
+<h2>AUTHORS</h2>
+Michael Shapiro, U.S.Army Construction Engineering Research Laboratory<BR>
+Olga Waupotitsch, U.S.Army Construction Engineering Research Laboratory
+
+<p>
+<i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.statistics/description.html
===================================================================
--- grass/trunk/raster/r.statistics/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.statistics/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,98 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>r.statistics</em> is a tool to analyse exploratory statistics of a "cover
-layer" according to how it intersects with objects in a "base layer". A
-variety of standard statistical measures are possible (called "zonal statistics"
-in some GIS).
-
-All cells in the base layer are considered one object for the analysis. For
-some applications, one will first want to prepare the input data so that
-all areas of contiguous cell category values in the base layer are uniquely
-identified, which can be done with <em>r.clump</em>.
-<br>
-
-The available methods are the following (english - german):
-<ul>
-<li>distribution - Verteilung in Prozent</li>
-<li>average - Durchschnitt</li>
-<li>mode - Modalwert</li>
-<li>median - Median</li>
-<li>average deviation - Durchschnittliche Abweichung</li>
-<li>standard deviation - Standardabweichung</li>
-<li>variance - Varianz</li>
-<li>skewness - Schiefe der Verteilung</li>
-<li>kurtosis - Relative Abflachung (-) oder Zuspitzung (+)</li>
-<li>minimum - Minimum</li>
-<li>maximum - Maximum</li>
-<li>sum - Summe</li>
-</ul>
-
-The calculations will be performed on each area of data of the
-cover layers which fall within each unique value, or category, of the base layer.
-<p>
-Setting the <em>-c</em> flag the category lables of the covering raster
-layer will be used. This is nice to avoid the GRASS limitation to interger
-in raster maps because using category values floating point numbers can be
-stored.
-
-<p>
-All calculations except "distribution" create an output layer. The output
-layer is a reclassified version of the base layer with identical
-category values, but modified category labels - the results of the calculations
-are stored in the category labels of the output layer.
-
-<p>
-For distributions, the output is printed to the user interface (stdout).
-If an output file name was specified, it will be ignored. The result will
-be a text table with three columns.
-In the first column are the category values of the base layer (a), in the second
-column the associated value of the cover layers (b), and in the third column the
-percentage of area in that base layer category (a) that falls into that row's
-value in the cover layer(b). Example:
-
-<div class="code"><pre>
-1 124 23
-1 201 47
-1 273 30
-2 101 5
-2 152 16
-2 167 60
-2 187 19
- .
- .
- .
-</pre></div>
-
-So for the first line in the output above, we see that 23% of the cells of the
-base layer category 1 have a value of 124 in the cover layer.
-
-To transfer the values stored as category labels into cell values,
-<em>r.mapcalc</em> can be used ('@' operator).
-
-<h2>EXAMPLES</h2>
-
-Calculation of average elevation of each field in the Spearfish region:
-
-<div class="code"><pre>
-r.statistics base=fields cover=elevation.dem out=elevstats method=average
-r.category elevstats
-r.mapcalc "fieldelev=@elevstats"
-r.univar fieldelev
-</pre></div>
-
-<h2>SEE ALSO</h2>
-<em>
-<a href="r.average.html">r.average</a>,
-<a href="r.clump.html">r.clump</a>,
-<a href="r.mode.html">r.mode</a>,
-<a href="r.median.html">r.median</a>,
-<a href="r.mapcalc.html">r.mapcalc</a>,
-<a href="r.neighbors.html">r.neighbors</a>,
-<a href="r.univar.html">r.univar</a>
-<a href="r.category.html">r.category</a>
-</em>
-
-<h2>AUTHOR</h2>
-Martin Schroeder, Geographisches Institut Heidelberg, Germany
-
-<p><i>Last changed: $Date$</i></p>
Copied: grass/trunk/raster/r.statistics/r.statistics.html (from rev 32770, grass/trunk/raster/r.statistics/description.html)
===================================================================
--- grass/trunk/raster/r.statistics/r.statistics.html (rev 0)
+++ grass/trunk/raster/r.statistics/r.statistics.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,98 @@
+<h2>DESCRIPTION</h2>
+
+<em>r.statistics</em> is a tool to analyse exploratory statistics of a "cover
+layer" according to how it intersects with objects in a "base layer". A
+variety of standard statistical measures are possible (called "zonal statistics"
+in some GIS).
+
+All cells in the base layer are considered one object for the analysis. For
+some applications, one will first want to prepare the input data so that
+all areas of contiguous cell category values in the base layer are uniquely
+identified, which can be done with <em>r.clump</em>.
+<br>
+
+The available methods are the following (english - german):
+<ul>
+<li>distribution - Verteilung in Prozent</li>
+<li>average - Durchschnitt</li>
+<li>mode - Modalwert</li>
+<li>median - Median</li>
+<li>average deviation - Durchschnittliche Abweichung</li>
+<li>standard deviation - Standardabweichung</li>
+<li>variance - Varianz</li>
+<li>skewness - Schiefe der Verteilung</li>
+<li>kurtosis - Relative Abflachung (-) oder Zuspitzung (+)</li>
+<li>minimum - Minimum</li>
+<li>maximum - Maximum</li>
+<li>sum - Summe</li>
+</ul>
+
+The calculations will be performed on each area of data of the
+cover layers which fall within each unique value, or category, of the base layer.
+<p>
+Setting the <em>-c</em> flag the category lables of the covering raster
+layer will be used. This is nice to avoid the GRASS limitation to interger
+in raster maps because using category values floating point numbers can be
+stored.
+
+<p>
+All calculations except "distribution" create an output layer. The output
+layer is a reclassified version of the base layer with identical
+category values, but modified category labels - the results of the calculations
+are stored in the category labels of the output layer.
+
+<p>
+For distributions, the output is printed to the user interface (stdout).
+If an output file name was specified, it will be ignored. The result will
+be a text table with three columns.
+In the first column are the category values of the base layer (a), in the second
+column the associated value of the cover layers (b), and in the third column the
+percentage of area in that base layer category (a) that falls into that row's
+value in the cover layer(b). Example:
+
+<div class="code"><pre>
+1 124 23
+1 201 47
+1 273 30
+2 101 5
+2 152 16
+2 167 60
+2 187 19
+ .
+ .
+ .
+</pre></div>
+
+So for the first line in the output above, we see that 23% of the cells of the
+base layer category 1 have a value of 124 in the cover layer.
+
+To transfer the values stored as category labels into cell values,
+<em>r.mapcalc</em> can be used ('@' operator).
+
+<h2>EXAMPLES</h2>
+
+Calculation of average elevation of each field in the Spearfish region:
+
+<div class="code"><pre>
+r.statistics base=fields cover=elevation.dem out=elevstats method=average
+r.category elevstats
+r.mapcalc "fieldelev=@elevstats"
+r.univar fieldelev
+</pre></div>
+
+<h2>SEE ALSO</h2>
+<em>
+<a href="r.average.html">r.average</a>,
+<a href="r.clump.html">r.clump</a>,
+<a href="r.mode.html">r.mode</a>,
+<a href="r.median.html">r.median</a>,
+<a href="r.mapcalc.html">r.mapcalc</a>,
+<a href="r.neighbors.html">r.neighbors</a>,
+<a href="r.univar.html">r.univar</a>
+<a href="r.category.html">r.category</a>
+</em>
+
+<h2>AUTHOR</h2>
+Martin Schroeder, Geographisches Institut Heidelberg, Germany
+
+<p><i>Last changed: $Date$</i></p>
Deleted: grass/trunk/raster/r.stats/description.html
===================================================================
--- grass/trunk/raster/r.stats/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.stats/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,89 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>r.stats</em> calculates the area present in each of the categories of
-user-selected raster map layer(s). Area statistics are given in units of
-square meters and/or cell counts. This analysis uses the current geographic
-region and mask settings. Output can be sent to a file in the user's current
-working directory.
-
-If a single map layer is specified on the command line, a list of areas in
-square meters (assuming the map's coordinate system is in meters) for each
-category in the raster map layer will be printed. (If the <em>-c</em> option
-is chosen, areas will be stated in number of cells.) If multiple raster map
-layers are specified on the command line, a cross-tabulation table of areas
-for each combination of categories in the map layers will be printed.
-
-<p>
-For example, if one raster map layer were specified, the output would look like:
-<pre>
- 1:1350000.00
- 2:4940000.00
- 3:8870000.00
-</pre>
-If three raster map layers <em>a, b</em>, and <em>c</em>, were specified,
-the output would look like:
-<pre>
- 0:0:0:8027500.00
- 0:1:0:1152500.00
- 1:0:0:164227500.00
- 1:0:1:2177500.00
- 1:1:0:140092500.00
- 1:1:1:3355000.00
- 2:0:0:31277500.00
- 2:0:1:2490000.00
- 2:1:0:24207500.00
- 2:1:1:1752500.00
- 3:0:0:17140000.00
- 3:1:0:11270000.00
- 3:1:1:2500.00
-</pre>
-Within each grouping, the first field represents the category value of map
-layer <em>a</em>, the second represents the category values associated with
-map layer <em>b</em>, the third represents category values for map layer
-<em>c</em>, and the last field gives the area in square meters for the
-particular combination of these three map layers' categories. For example,
-above, combination 3,1,1 covered 2500 square meters. Fields are separated by
-colons.
-
-<h2>NOTES</h2>
-<em>r.stats</em> works in the current geographic region with the current mask.
-
-<p>
-If a nicely formatted output is desired, pipe the output into a command
-which can create columnar output. For example, the command:
-
-<p>
- <b>r.stats input=</b>a,b,c | pr -3 | cat -s
-
-<p>
-will create a three-column output
-<pre>
-1:4:4:10000.00 2:1:5:290000.00 2:4:5:2090000.00
-1:4:5:1340000.00 2:2:5:350000.00 3:1:2:450000.00
-2:1:1:1090000.00 2:4:1:700000.00 3:1:3:5280000.00
-2:1:3:410000.00 2:4:3:10000.00 3:1:5:3140000.00
-</pre>
-
-The output from <em>r.stats</em> on more than one map layer is sorted.
-
-<p>
-Note that the user has only the option of printing out cell statistics in
-terms of cell counts and/or area totals. Users wishing to use different
-units than are available here should use the GRASS program
-<em><a href="r.report.html">r.report</a></em>.
-
-<h2>SEE ALSO</h2>
-
-<em>
-<a href="g.region.html">g.region</a>,
-<a href="r.coin.html">r.coin</a>,
-<a href="r.describe.html">r.describe</a>,
-<a href="r.report.html">r.report</a>,
-<a href="r.statistics.html">r.statistics</a>,
-<a href="r.univar.html">r.univar</a>
-</em>
-
-<h2>AUTHOR</h2>
-Michael Shapiro, U.S. Army Construction Engineering Research Laboratory
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.stats/r.stats.html (from rev 32770, grass/trunk/raster/r.stats/description.html)
===================================================================
--- grass/trunk/raster/r.stats/r.stats.html (rev 0)
+++ grass/trunk/raster/r.stats/r.stats.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,89 @@
+<h2>DESCRIPTION</h2>
+
+<em>r.stats</em> calculates the area present in each of the categories of
+user-selected raster map layer(s). Area statistics are given in units of
+square meters and/or cell counts. This analysis uses the current geographic
+region and mask settings. Output can be sent to a file in the user's current
+working directory.
+
+If a single map layer is specified on the command line, a list of areas in
+square meters (assuming the map's coordinate system is in meters) for each
+category in the raster map layer will be printed. (If the <em>-c</em> option
+is chosen, areas will be stated in number of cells.) If multiple raster map
+layers are specified on the command line, a cross-tabulation table of areas
+for each combination of categories in the map layers will be printed.
+
+<p>
+For example, if one raster map layer were specified, the output would look like:
+<pre>
+ 1:1350000.00
+ 2:4940000.00
+ 3:8870000.00
+</pre>
+If three raster map layers <em>a, b</em>, and <em>c</em>, were specified,
+the output would look like:
+<pre>
+ 0:0:0:8027500.00
+ 0:1:0:1152500.00
+ 1:0:0:164227500.00
+ 1:0:1:2177500.00
+ 1:1:0:140092500.00
+ 1:1:1:3355000.00
+ 2:0:0:31277500.00
+ 2:0:1:2490000.00
+ 2:1:0:24207500.00
+ 2:1:1:1752500.00
+ 3:0:0:17140000.00
+ 3:1:0:11270000.00
+ 3:1:1:2500.00
+</pre>
+Within each grouping, the first field represents the category value of map
+layer <em>a</em>, the second represents the category values associated with
+map layer <em>b</em>, the third represents category values for map layer
+<em>c</em>, and the last field gives the area in square meters for the
+particular combination of these three map layers' categories. For example,
+above, combination 3,1,1 covered 2500 square meters. Fields are separated by
+colons.
+
+<h2>NOTES</h2>
+<em>r.stats</em> works in the current geographic region with the current mask.
+
+<p>
+If a nicely formatted output is desired, pipe the output into a command
+which can create columnar output. For example, the command:
+
+<p>
+ <b>r.stats input=</b>a,b,c | pr -3 | cat -s
+
+<p>
+will create a three-column output
+<pre>
+1:4:4:10000.00 2:1:5:290000.00 2:4:5:2090000.00
+1:4:5:1340000.00 2:2:5:350000.00 3:1:2:450000.00
+2:1:1:1090000.00 2:4:1:700000.00 3:1:3:5280000.00
+2:1:3:410000.00 2:4:3:10000.00 3:1:5:3140000.00
+</pre>
+
+The output from <em>r.stats</em> on more than one map layer is sorted.
+
+<p>
+Note that the user has only the option of printing out cell statistics in
+terms of cell counts and/or area totals. Users wishing to use different
+units than are available here should use the GRASS program
+<em><a href="r.report.html">r.report</a></em>.
+
+<h2>SEE ALSO</h2>
+
+<em>
+<a href="g.region.html">g.region</a>,
+<a href="r.coin.html">r.coin</a>,
+<a href="r.describe.html">r.describe</a>,
+<a href="r.report.html">r.report</a>,
+<a href="r.statistics.html">r.statistics</a>,
+<a href="r.univar.html">r.univar</a>
+</em>
+
+<h2>AUTHOR</h2>
+Michael Shapiro, U.S. Army Construction Engineering Research Laboratory
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.sum/description.html
===================================================================
--- grass/trunk/raster/r.sum/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.sum/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,14 +0,0 @@
-<h2>DESCRIPTION</h2>
-<b><em>r.sum</em></b> sums up the raster cell values.
-For example, it can be used to summarize the population
-of a country. Using a raster MASK, raster areas can be
-easily selected for the summary.
-
-<h2>SEE ALSO</h2>
-
-<em><a href="r.surf.area.html">r.surf.area</a></em>
-
-<h2>AUTHOR</h2>
-<a href=mailto:brown at gis.uiuc.edu>Bill Brown</a>, UIUC GIS Laboratory
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.sum/r.sum.html (from rev 32770, grass/trunk/raster/r.sum/description.html)
===================================================================
--- grass/trunk/raster/r.sum/r.sum.html (rev 0)
+++ grass/trunk/raster/r.sum/r.sum.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,14 @@
+<h2>DESCRIPTION</h2>
+<b><em>r.sum</em></b> sums up the raster cell values.
+For example, it can be used to summarize the population
+of a country. Using a raster MASK, raster areas can be
+easily selected for the summary.
+
+<h2>SEE ALSO</h2>
+
+<em><a href="r.surf.area.html">r.surf.area</a></em>
+
+<h2>AUTHOR</h2>
+<a href=mailto:brown at gis.uiuc.edu>Bill Brown</a>, UIUC GIS Laboratory
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.sun/description.html
===================================================================
--- grass/trunk/raster/r.sun/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.sun/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,272 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<b>r.sun</b> computes beam (direct), diffuse and ground reflected solar
-irradiation raster maps for given day, latitude, surface and atmospheric
-conditions. Solar parameters (e.g. time of sunrise and sunset, declination,
-extraterrestrial irradiance, daylight length) are stored in the resultant maps'
-history files. Alternatively, the local time can be specified to compute solar
-incidence angle and/or irradiance raster maps. The shadowing effect of the
-topography is optionally incorporated, a correction factor for shadowing to account
-for the earth curvature is internally calucated.<br>
-The units of the parameters are specified in brackets, a hyphen in the brackets
-explains that the parameter has no units.
-<p>
-For latitude-longitude coordinates it requires that the elevation map is in meters.
-The rules are:
-<ul>
-<li> lat/lon coordinates: elevation in meters;
-<li> Other coordinates: elevation in the same unit as the easting-northing coordinates.
-</ul>
-
-<p>
-The solar geometry of the model is based on the works of Krcho (1990), later
-improved by Jenco (1992). The equations describing Sun – Earth position as
-well as an interaction of the solar radiation with atmosphere were originally
-based on the formulas suggested by Kitler and Mikler (1986). This component
-was considerably updated by the results and suggestions of the working group
-co-ordinated by Scharmer and Greif (2000) (this algorithm might be replaced
-by SOLPOS algorithm-library included in GRASS within <a href="r.sunmask.html">
-r.sunmask</a>
- command). The model computes all three components of global radiation (beam,
-diffuse and reflected) for the clear sky conditions, i.e. not taking into
-consideration the spatial and temporal variation of clouds. The extent and
-spatial resolution of the modelled area, as well as integration over time,
-are limited only by the memory and data storage resources. The model is built
-to fulfil user needs in various fields of science (hydrology, climatology,
-ecology and environmental sciences, photovoltaics, engineering, etc.) for
-continental, regional up to the landscape scales.
-<p>As an option the model considers a shadowing effect of the local topography.
-The r.sun program works in two modes. In the first mode it calculates for the set
-local time a solar incidence angle [degrees] and solar irradiance values [W.m-2].
-In the second mode daily sums of solar radiation [Wh.m-2.day-1] are computed
-within a set day. By a scripting the two modes can be used separately or
-in a combination to provide estimates for any desired time interval. The
-model accounts for sky obstruction by local relief features. Several solar
-parameters are saved in the resultant maps' history files, which may be viewed
-with the <a href="r.info.html">r.info</a> command.
-</p>
-<p>The solar incidence angle raster map <i>incidout</i> is computed specifying
-elevation raster map <i>elevin</i>, aspect raster map <i>aspin</i>, slope
-steepness raster map <i>slopin,</i> given the day <i>day</i> and local time
-<i>time</i>. There is no need to define latitude for locations with known
-and defined projection/coordinate system (check it with the <a href="g.proj.html">
-g.proj</a>
- command). If you have undefined projection, (x,y) system, etc. then the latitude
-can be defined explicitely for large areas by input raster map <i>latin</i>
- with interpolated latitude values or, for smaller areas, a single region
-latitude value <i>lat</i> can be used instead. All input raster maps must
-be floating point (FCELL) raster maps. Null data in maps are excluded from
-the computation (and also speeding-up the computation), so each output raster
-map will contain null data in cells according to all input raster maps. The
-user can use <a href="r.null.html">r.null</a>
- command to create/reset null file for your input raster maps. <br>
-The specified day <i>day</i> is the number of the day of the general year
-where January 1 is day no.1 and December 31 is 365. Time <i>time</i> must
-be a local (solar) time (i.e. NOT a zone time, e.g. GMT, CET) in decimal system,
-e.g. 7.5 (= 7h 30m A.M.), 16.1 = 4h 6m P.M.. </p>
-<p>Setting the solar declination <i>declin</i> by user is an option to override
-the value computed by the internal routine for the day of the year. The value
-of geographical latitude can be set as a constant for the whole computed
-region or, as an option, a grid representing spatially distributed values
-over a large region. The geographical latitude must be also in decimal system
-with positive values for northern hemisphere and negative for southern one.
-In similar principle the Linke turbidity factor (<i>linkein</i>, <i>lin</i>
-) and ground albedo (<i>albedo</i>, <i>alb</i>) can be set. </p>
-<p>Besides clear-sky radiations, user can compute a real-sky radiation (beam,
-diffuse) using <i>coefbh</i> and <i>coefdh </i>input raster maps defining
-the fraction of the respective clear-sky radiations reduced by atmospheric
-factors (e.g. cloudiness). The value is between 0-1. Usually these
-coefficients can be obtained from a long-terms meteorological measurements.</p>
-<p>The solar irradiation or irradiance raster maps <i>beam_rad</i>, <i>diff_rad</i>
-, <i>refl_rad</i> are computed for a given day <i>day,</i> latitude <i>lat
-(latin), </i>elevation <i>elevin</i>, slope <i>slopein</i> and aspect <i>
-aspin</i> raster maps. The program uses the Linke atmosphere turbidity factor
-and ground albedo coefficient. A default, single value of Linke factor is
-<i>lin</i>=3.0 and is near the annual average for rural-city areas. The Linke
-factor for an absolutely clear atmosphere is <i>lin</i>=1.0. See notes below
-to learn more about this factor. The incidence solar angle is the angle between
-horizon and solar beam vector. The solar radiation maps for given day are
-computed integrating the relevant irradiance between sunrise and sunset times
-for given day. The user can set finer or coarser time step <i>step</i> used
-for all-day radiation calculations. A default value of <i>step</i> is 0.5
-hour. Larger steps (e.g. 1.0-2.0) can speed-up calculations but produce less
-reliable results. The output units are in Wh per squared meter per given
-day [Wh/(m*m)/day]. The incidence angle and irradiance/irradiation maps can
-be computed without shadowing influence of relief by default or they can
-be computed with this influence using the flag <i>-s</i>. In mountainous areas
-this can lead to very different results! The user should be aware that taken
-into account the shadowing effect of relief can slow
-down the speed of computing especially when the sun altitude is low.
- When considering shadowing effect (flag <i>-s</i>) speed and precision computing
-can be controlled by a parameter <i>dist</i> which defines the sampling density
-at which the visibility of a grid cell is computed in the direction of a
-path of the solar flow. It also defines the method by which the obstacle's
-altitude is computed. When choosing <i>dist</i> less than 1.0 (i.e. sampling
-points will be computed at <i>dist</i> * cellsize distance), r.sun takes
-altitude from the nearest grid point. Values above 1.0 will use the maximum
-altitude value found in the nearest 4 surrounding grid points. The default
-value <i>dist</i>=1.0 should give reasonable results for most cases (e.g.
-on DEM). <i>Dist</i> value defines a multiplying coefficient for sampling
-distance. This basic sampling distance equals to the arithmetic average of
-both cell sizes. The reasonable values are in the range 0.5-1.5. The values
-below 0.5 will decrease and values above 1.0 will increase the computing
-speed. Values greater than 2.0 may produce estimates with lower accuracy
-in highly dissected relief. The fully shadowed areas are written to the ouput
-maps as zero values. Areas with NULL data are considered as no barrier with
-shadowing effect .</p>
-<p>The maps' history files are generated containing the following listed
-parameters used in the computation: <br>
-- Solar constant 1367 W.m-2 <br>
-- Extraterrestrial irradiance on a plane perpendicular to the solar beam
-[W.m-2] <br>
-- Day of the year <br>
-- Declination [radians] <br>
-- Decimal hour (Alternative 1 only) <br>
-- Sunrise and sunset (min-max) over a horizontal plane <br>
-- Daylight lengths <br>
-- Geographical latitude (min-max) <br>
-- Linke turbidity factor (min-max) <br>
-- Ground albedo (min-max) </p>
-<p>The user can use a nice shellcript with variable
-day to compute radiation for some time interval within the year (e.g. vegetation
-or winter period). Elevation, aspect and slope input values should not be
-reclassified into coarser categories. This could lead to incorrect results.
-</p>
-
-<h2> OPTIONS</h2>
-<p>Currently, there are two modes of r.sun.
-In the first mode it calculates solar incidence angle and solar irradiance
-raster maps using the set local time. In the second mode daily sums of solar
-irradiation [Wh.m-2.day-1] are computed for a specified day.</p>
-
-<h2>
-NOTES</h2>
-
-Solar energy is an important input parameter in different models concerning
-energy industry, landscape, vegetation, evapotranspiration, snowmelt or remote
-sensing. Solar rays incidence angle maps can be effectively used in radiometric
-and topographic corrections in mountainous and hilly terrain where very accurate
-investigations should be performed.
-<p>
-The clear-sky solar radiation model applied in the r.sun is based on the
-work undertaken for development of European Solar Radiation Atlas (Scharmer
-and Greif 2000, Page et al. 2001, Rigollier 2001). The clear sky model estimates
-the global radiation from the sum of its beam, diffuse and reflected components.
-The main difference between solar radiation models for inclined surfaces
-in Europe is the treatment of the diffuse component. In the European climate
-this component is often the largest source of estimation error. Taking into
-consideration the existing models and their limitation the European Solar
-Radiation Atlas team selected the Muneer (1990) model as it has a sound theoretical
-basis and thus more potential for later improvement. </p>
-<p>
-Details of underlying equations used in this program can be found in the
-reference literature cited below or book published by Neteler and Mitasova:
-Open Source GIS: A GRASS GIS Approach (published in Kluwer Academic Publishers
-in 2002). </p>
-<p>
-Average monthly values of the Linke turbidity coefficient for a mild climate
-(see reference literature for your study area): </p>
-<pre>
-Month Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec annual<br>
-mountains 1.5 1.6 1.8 1.9 2.0 2.3 2.3 2.3 2.1 1.8 1.6 1.5 1.90 <br>
-rural 2.1 2.2 2.5 2.9 3.2 3.4 3.5 3.3 2.9 2.6 2.3 2.2 2.75 <br>
-city 3.1 3.2 3.5 4.0 4.2 4.3 4.4 4.3 4.0 3.6 3.3 3.1 3.75 <br>
-industrial 4.1 4.3 4.7 5.3 5.5 5.7 5.8 5.7 5.3 4.9 4.5 4.2 5.00
-</pre>
-<p>
-Planned improvements include the use of the SOLPOS algorithm for solar
-geometry calculations and internal computation of aspect and slope.
-
-<h3>Shadow maps</h3>
-A map of shadows can be extracted from the solar incidence angle map
-(incidout). Areas with zero values are shadowed. The <em>-s</em> flag
-has to be used.
-
-<h2>EXAMPLE</h2>
-
-Nice looking maps can be created with the model's output as follows:
-<div class="code"><pre>
-
-g.region rast=elevation.dem
-r.sun -s elev=elevation.dem slop=slope asp=aspect beam=beam_map day=180
-r.colors beam_map col=grey
-d.his i_map=beam_map h_map=elevation.dem
-
-</pre></div>
-
-
-<h2>SEE ALSO</h2>
-<a href="r.slope.aspect.html">r.slope.aspect</a>,
-<a href="r.sunmask.html">r.sunmask</a>,
-<a href="g.proj.html">g.proj</a>,
-<a href="r.null.html">r.null</a>,
-<a href="v.surf.rst.html">v.surf.rst</a>
-
-
-<h2>REFERENCES</h2>
-
-Hofierka, J., Suri, M. (2002): The solar radiation model for Open source
-GIS: implementation and applications. Manuscript submitted to the International
-GRASS users conference in Trento, Italy, September 2002.
-<p>
-Hofierka, J. (1997). Direct solar radiation modelling within an open GIS
-environment. Proceedings of JEC-GI'97 conference in Vienna, Austria, IOS
-Press Amsterdam, 575-584. </p>
-<p>
-Jenco, M. (1992). Distribution of direct solar radiation on georelief and
-its modelling by means of complex digital model of terrain (in Slovak). Geograficky
-casopis, 44, 342-355. </p>
-<p>
-Kasten, F. (1996). The Linke turbidity factor based on improved values of
-the integral Rayleigh optical thickness. Solar Energy, 56 (3), 239-244. </p>
-<p>
-Kasten, F., Young, A. T. (1989). Revised optical air mass tables and approximation
-formula. Applied Optics, 28, 4735-4738. </p>
-<p>
-Kittler, R., Mikler, J. (1986): Basis of the utilization of solar radiation
-(in Slovak). VEDA, Bratislava, p. 150. </p>
-<p>
-Krcho, J. (1990). Morfometrická analza a digitálne modely georeliéfu
-(Morphometric analysis and digital models of georelief, in Slovak).
-VEDA, Bratislava.</p>
-<p>
-Muneer, T. (1990). Solar radiation model for Europe. Building services engineering
-research and technology, 11, 4, 153-163. </p>
-<p>
-Neteler, M., Mitasova, H. (2002): Open Source GIS: A GRASS GIS Approach, Kluwer
-Academic Publishers. </p>
-<p>
-Page, J. ed. (1986). Prediction of solar radiation on inclined surfaces. Solar
-energy R&D in the European Community, series F – Solar radiation data,
-Dordrecht (D. Reidel), 3, 71, 81-83. </p>
-<p>
-Page, J., Albuisson, M., Wald, L. (2001). The European solar radiation atlas:
-a valuable digital tool. Solar Energy, 71, 81-83. </p>
-<p>
-Rigollier, Ch., Bauer, O., Wald, L. (2000). On the clear sky model of the
-ESRA - European Solar radiation Atlas - with respect to the Heliosat method.
-Solar energy, 68, 33-48. </p>
-<p>
-Scharmer, K., Greif, J., eds., (2000). The European solar radiation atlas,
-Vol. 2: Database and exploitation software. Paris (Les Presses de l’ École
-des Mines). </p>
-
-<p>Joint Research Centre: <a href="http://re.jrc.ec.europa.eu/pvgis/">GIS solar radiation database for Europe</a> and
-<a href="http://re.jrc.ec.europa.eu/pvgis/solres/solmod3.htm">Solar radiation and GIS</a>
-</p>
-
-<h2>AUTHORS</h2>
-
-Jaroslav Hofierka, GeoModel, s.r.o. Bratislava, Slovakia <br>
-
-Marcel Suri, GeoModel, s.r.o. Bratislava, Slovakia <br>
-
-Thomas Huld, JRC, Italy <br>
-
-© 2002, Jaroslav Hofierka, Marcel Suri
-<address>
-<a href="MAILTO:hofi at geomodel.sk">hofierka at geomodel.sk</a>
-<a href="MAILTO:suri at geomodel.sk">suri at geomodel.sk</a>
-</address>
-
-<p><i>Last changed: $Date$</i> </p>
Copied: grass/trunk/raster/r.sun/r.sun.html (from rev 32770, grass/trunk/raster/r.sun/description.html)
===================================================================
--- grass/trunk/raster/r.sun/r.sun.html (rev 0)
+++ grass/trunk/raster/r.sun/r.sun.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,272 @@
+<h2>DESCRIPTION</h2>
+
+<b>r.sun</b> computes beam (direct), diffuse and ground reflected solar
+irradiation raster maps for given day, latitude, surface and atmospheric
+conditions. Solar parameters (e.g. time of sunrise and sunset, declination,
+extraterrestrial irradiance, daylight length) are stored in the resultant maps'
+history files. Alternatively, the local time can be specified to compute solar
+incidence angle and/or irradiance raster maps. The shadowing effect of the
+topography is optionally incorporated, a correction factor for shadowing to account
+for the earth curvature is internally calucated.<br>
+The units of the parameters are specified in brackets, a hyphen in the brackets
+explains that the parameter has no units.
+<p>
+For latitude-longitude coordinates it requires that the elevation map is in meters.
+The rules are:
+<ul>
+<li> lat/lon coordinates: elevation in meters;
+<li> Other coordinates: elevation in the same unit as the easting-northing coordinates.
+</ul>
+
+<p>
+The solar geometry of the model is based on the works of Krcho (1990), later
+improved by Jenco (1992). The equations describing Sun – Earth position as
+well as an interaction of the solar radiation with atmosphere were originally
+based on the formulas suggested by Kitler and Mikler (1986). This component
+was considerably updated by the results and suggestions of the working group
+co-ordinated by Scharmer and Greif (2000) (this algorithm might be replaced
+by SOLPOS algorithm-library included in GRASS within <a href="r.sunmask.html">
+r.sunmask</a>
+ command). The model computes all three components of global radiation (beam,
+diffuse and reflected) for the clear sky conditions, i.e. not taking into
+consideration the spatial and temporal variation of clouds. The extent and
+spatial resolution of the modelled area, as well as integration over time,
+are limited only by the memory and data storage resources. The model is built
+to fulfil user needs in various fields of science (hydrology, climatology,
+ecology and environmental sciences, photovoltaics, engineering, etc.) for
+continental, regional up to the landscape scales.
+<p>As an option the model considers a shadowing effect of the local topography.
+The r.sun program works in two modes. In the first mode it calculates for the set
+local time a solar incidence angle [degrees] and solar irradiance values [W.m-2].
+In the second mode daily sums of solar radiation [Wh.m-2.day-1] are computed
+within a set day. By a scripting the two modes can be used separately or
+in a combination to provide estimates for any desired time interval. The
+model accounts for sky obstruction by local relief features. Several solar
+parameters are saved in the resultant maps' history files, which may be viewed
+with the <a href="r.info.html">r.info</a> command.
+</p>
+<p>The solar incidence angle raster map <i>incidout</i> is computed specifying
+elevation raster map <i>elevin</i>, aspect raster map <i>aspin</i>, slope
+steepness raster map <i>slopin,</i> given the day <i>day</i> and local time
+<i>time</i>. There is no need to define latitude for locations with known
+and defined projection/coordinate system (check it with the <a href="g.proj.html">
+g.proj</a>
+ command). If you have undefined projection, (x,y) system, etc. then the latitude
+can be defined explicitely for large areas by input raster map <i>latin</i>
+ with interpolated latitude values or, for smaller areas, a single region
+latitude value <i>lat</i> can be used instead. All input raster maps must
+be floating point (FCELL) raster maps. Null data in maps are excluded from
+the computation (and also speeding-up the computation), so each output raster
+map will contain null data in cells according to all input raster maps. The
+user can use <a href="r.null.html">r.null</a>
+ command to create/reset null file for your input raster maps. <br>
+The specified day <i>day</i> is the number of the day of the general year
+where January 1 is day no.1 and December 31 is 365. Time <i>time</i> must
+be a local (solar) time (i.e. NOT a zone time, e.g. GMT, CET) in decimal system,
+e.g. 7.5 (= 7h 30m A.M.), 16.1 = 4h 6m P.M.. </p>
+<p>Setting the solar declination <i>declin</i> by user is an option to override
+the value computed by the internal routine for the day of the year. The value
+of geographical latitude can be set as a constant for the whole computed
+region or, as an option, a grid representing spatially distributed values
+over a large region. The geographical latitude must be also in decimal system
+with positive values for northern hemisphere and negative for southern one.
+In similar principle the Linke turbidity factor (<i>linkein</i>, <i>lin</i>
+) and ground albedo (<i>albedo</i>, <i>alb</i>) can be set. </p>
+<p>Besides clear-sky radiations, user can compute a real-sky radiation (beam,
+diffuse) using <i>coefbh</i> and <i>coefdh </i>input raster maps defining
+the fraction of the respective clear-sky radiations reduced by atmospheric
+factors (e.g. cloudiness). The value is between 0-1. Usually these
+coefficients can be obtained from a long-terms meteorological measurements.</p>
+<p>The solar irradiation or irradiance raster maps <i>beam_rad</i>, <i>diff_rad</i>
+, <i>refl_rad</i> are computed for a given day <i>day,</i> latitude <i>lat
+(latin), </i>elevation <i>elevin</i>, slope <i>slopein</i> and aspect <i>
+aspin</i> raster maps. The program uses the Linke atmosphere turbidity factor
+and ground albedo coefficient. A default, single value of Linke factor is
+<i>lin</i>=3.0 and is near the annual average for rural-city areas. The Linke
+factor for an absolutely clear atmosphere is <i>lin</i>=1.0. See notes below
+to learn more about this factor. The incidence solar angle is the angle between
+horizon and solar beam vector. The solar radiation maps for given day are
+computed integrating the relevant irradiance between sunrise and sunset times
+for given day. The user can set finer or coarser time step <i>step</i> used
+for all-day radiation calculations. A default value of <i>step</i> is 0.5
+hour. Larger steps (e.g. 1.0-2.0) can speed-up calculations but produce less
+reliable results. The output units are in Wh per squared meter per given
+day [Wh/(m*m)/day]. The incidence angle and irradiance/irradiation maps can
+be computed without shadowing influence of relief by default or they can
+be computed with this influence using the flag <i>-s</i>. In mountainous areas
+this can lead to very different results! The user should be aware that taken
+into account the shadowing effect of relief can slow
+down the speed of computing especially when the sun altitude is low.
+ When considering shadowing effect (flag <i>-s</i>) speed and precision computing
+can be controlled by a parameter <i>dist</i> which defines the sampling density
+at which the visibility of a grid cell is computed in the direction of a
+path of the solar flow. It also defines the method by which the obstacle's
+altitude is computed. When choosing <i>dist</i> less than 1.0 (i.e. sampling
+points will be computed at <i>dist</i> * cellsize distance), r.sun takes
+altitude from the nearest grid point. Values above 1.0 will use the maximum
+altitude value found in the nearest 4 surrounding grid points. The default
+value <i>dist</i>=1.0 should give reasonable results for most cases (e.g.
+on DEM). <i>Dist</i> value defines a multiplying coefficient for sampling
+distance. This basic sampling distance equals to the arithmetic average of
+both cell sizes. The reasonable values are in the range 0.5-1.5. The values
+below 0.5 will decrease and values above 1.0 will increase the computing
+speed. Values greater than 2.0 may produce estimates with lower accuracy
+in highly dissected relief. The fully shadowed areas are written to the ouput
+maps as zero values. Areas with NULL data are considered as no barrier with
+shadowing effect .</p>
+<p>The maps' history files are generated containing the following listed
+parameters used in the computation: <br>
+- Solar constant 1367 W.m-2 <br>
+- Extraterrestrial irradiance on a plane perpendicular to the solar beam
+[W.m-2] <br>
+- Day of the year <br>
+- Declination [radians] <br>
+- Decimal hour (Alternative 1 only) <br>
+- Sunrise and sunset (min-max) over a horizontal plane <br>
+- Daylight lengths <br>
+- Geographical latitude (min-max) <br>
+- Linke turbidity factor (min-max) <br>
+- Ground albedo (min-max) </p>
+<p>The user can use a nice shellcript with variable
+day to compute radiation for some time interval within the year (e.g. vegetation
+or winter period). Elevation, aspect and slope input values should not be
+reclassified into coarser categories. This could lead to incorrect results.
+</p>
+
+<h2> OPTIONS</h2>
+<p>Currently, there are two modes of r.sun.
+In the first mode it calculates solar incidence angle and solar irradiance
+raster maps using the set local time. In the second mode daily sums of solar
+irradiation [Wh.m-2.day-1] are computed for a specified day.</p>
+
+<h2>
+NOTES</h2>
+
+Solar energy is an important input parameter in different models concerning
+energy industry, landscape, vegetation, evapotranspiration, snowmelt or remote
+sensing. Solar rays incidence angle maps can be effectively used in radiometric
+and topographic corrections in mountainous and hilly terrain where very accurate
+investigations should be performed.
+<p>
+The clear-sky solar radiation model applied in the r.sun is based on the
+work undertaken for development of European Solar Radiation Atlas (Scharmer
+and Greif 2000, Page et al. 2001, Rigollier 2001). The clear sky model estimates
+the global radiation from the sum of its beam, diffuse and reflected components.
+The main difference between solar radiation models for inclined surfaces
+in Europe is the treatment of the diffuse component. In the European climate
+this component is often the largest source of estimation error. Taking into
+consideration the existing models and their limitation the European Solar
+Radiation Atlas team selected the Muneer (1990) model as it has a sound theoretical
+basis and thus more potential for later improvement. </p>
+<p>
+Details of underlying equations used in this program can be found in the
+reference literature cited below or book published by Neteler and Mitasova:
+Open Source GIS: A GRASS GIS Approach (published in Kluwer Academic Publishers
+in 2002). </p>
+<p>
+Average monthly values of the Linke turbidity coefficient for a mild climate
+(see reference literature for your study area): </p>
+<pre>
+Month Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec annual<br>
+mountains 1.5 1.6 1.8 1.9 2.0 2.3 2.3 2.3 2.1 1.8 1.6 1.5 1.90 <br>
+rural 2.1 2.2 2.5 2.9 3.2 3.4 3.5 3.3 2.9 2.6 2.3 2.2 2.75 <br>
+city 3.1 3.2 3.5 4.0 4.2 4.3 4.4 4.3 4.0 3.6 3.3 3.1 3.75 <br>
+industrial 4.1 4.3 4.7 5.3 5.5 5.7 5.8 5.7 5.3 4.9 4.5 4.2 5.00
+</pre>
+<p>
+Planned improvements include the use of the SOLPOS algorithm for solar
+geometry calculations and internal computation of aspect and slope.
+
+<h3>Shadow maps</h3>
+A map of shadows can be extracted from the solar incidence angle map
+(incidout). Areas with zero values are shadowed. The <em>-s</em> flag
+has to be used.
+
+<h2>EXAMPLE</h2>
+
+Nice looking maps can be created with the model's output as follows:
+<div class="code"><pre>
+
+g.region rast=elevation.dem
+r.sun -s elev=elevation.dem slop=slope asp=aspect beam=beam_map day=180
+r.colors beam_map col=grey
+d.his i_map=beam_map h_map=elevation.dem
+
+</pre></div>
+
+
+<h2>SEE ALSO</h2>
+<a href="r.slope.aspect.html">r.slope.aspect</a>,
+<a href="r.sunmask.html">r.sunmask</a>,
+<a href="g.proj.html">g.proj</a>,
+<a href="r.null.html">r.null</a>,
+<a href="v.surf.rst.html">v.surf.rst</a>
+
+
+<h2>REFERENCES</h2>
+
+Hofierka, J., Suri, M. (2002): The solar radiation model for Open source
+GIS: implementation and applications. Manuscript submitted to the International
+GRASS users conference in Trento, Italy, September 2002.
+<p>
+Hofierka, J. (1997). Direct solar radiation modelling within an open GIS
+environment. Proceedings of JEC-GI'97 conference in Vienna, Austria, IOS
+Press Amsterdam, 575-584. </p>
+<p>
+Jenco, M. (1992). Distribution of direct solar radiation on georelief and
+its modelling by means of complex digital model of terrain (in Slovak). Geograficky
+casopis, 44, 342-355. </p>
+<p>
+Kasten, F. (1996). The Linke turbidity factor based on improved values of
+the integral Rayleigh optical thickness. Solar Energy, 56 (3), 239-244. </p>
+<p>
+Kasten, F., Young, A. T. (1989). Revised optical air mass tables and approximation
+formula. Applied Optics, 28, 4735-4738. </p>
+<p>
+Kittler, R., Mikler, J. (1986): Basis of the utilization of solar radiation
+(in Slovak). VEDA, Bratislava, p. 150. </p>
+<p>
+Krcho, J. (1990). Morfometrická analza a digitálne modely georeliéfu
+(Morphometric analysis and digital models of georelief, in Slovak).
+VEDA, Bratislava.</p>
+<p>
+Muneer, T. (1990). Solar radiation model for Europe. Building services engineering
+research and technology, 11, 4, 153-163. </p>
+<p>
+Neteler, M., Mitasova, H. (2002): Open Source GIS: A GRASS GIS Approach, Kluwer
+Academic Publishers. </p>
+<p>
+Page, J. ed. (1986). Prediction of solar radiation on inclined surfaces. Solar
+energy R&D in the European Community, series F – Solar radiation data,
+Dordrecht (D. Reidel), 3, 71, 81-83. </p>
+<p>
+Page, J., Albuisson, M., Wald, L. (2001). The European solar radiation atlas:
+a valuable digital tool. Solar Energy, 71, 81-83. </p>
+<p>
+Rigollier, Ch., Bauer, O., Wald, L. (2000). On the clear sky model of the
+ESRA - European Solar radiation Atlas - with respect to the Heliosat method.
+Solar energy, 68, 33-48. </p>
+<p>
+Scharmer, K., Greif, J., eds., (2000). The European solar radiation atlas,
+Vol. 2: Database and exploitation software. Paris (Les Presses de l’ École
+des Mines). </p>
+
+<p>Joint Research Centre: <a href="http://re.jrc.ec.europa.eu/pvgis/">GIS solar radiation database for Europe</a> and
+<a href="http://re.jrc.ec.europa.eu/pvgis/solres/solmod3.htm">Solar radiation and GIS</a>
+</p>
+
+<h2>AUTHORS</h2>
+
+Jaroslav Hofierka, GeoModel, s.r.o. Bratislava, Slovakia <br>
+
+Marcel Suri, GeoModel, s.r.o. Bratislava, Slovakia <br>
+
+Thomas Huld, JRC, Italy <br>
+
+© 2002, Jaroslav Hofierka, Marcel Suri
+<address>
+<a href="MAILTO:hofi at geomodel.sk">hofierka at geomodel.sk</a>
+<a href="MAILTO:suri at geomodel.sk">suri at geomodel.sk</a>
+</address>
+
+<p><i>Last changed: $Date$</i> </p>
Deleted: grass/trunk/raster/r.sunmask/description.html
===================================================================
--- grass/trunk/raster/r.sunmask/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.sunmask/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,74 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>r.sunmask</em> creates an output map layer based on an input elevation
-raster map layer and the sun position. The output map layer contains the
-cast shadow areas arising from sun shine and elevations. The user can define
-the sun position either directly or the module calculates it from given
-location and date/time parameters using the
-<a href=http://rredc.nrel.gov/>NREL</a> sun position algorithm. So either
-"A:"-parameters to specify the exact known sun position or "B:-parameters"
-to specify date/time for sun position calculation by r.sunmask itself have
-to be used.
-
-<p>
-The module performs sunset/sunrise checks and refraction correction for sun
-position calculation. Local coordinate systems are internally transformed to
-latitude/longitude for the SOLPOS algorithm. The elevation is not considered
-in the sunset/sunrise calculations.
-
-<h2>Notes</h2>
-
-r.sunmask and daylight savings: Rather than convert time to GMT, the solpos
-algorithm uses what is called Local Standard Time, which is generally
-defined politically as an offset from GMT. So the key is the offset from
-GMT, which the solpos Time Zone parameter. If the user specifies clock time
-(different for winter and summer), he/she would have to change the Time Zone
-parameter seasonally in r.sunmask (timezone parameter).
-<p>
-
-Note: In latitude/longitude locations the position coordinates pair
-(east/west) has to be specified in decimal degree (not D:M:S). If
-not specified, the map center's coordinates will be used.
-Also <em>g.region -l</em> displays the map center's coordinates.
-
-<p>
-Note for module usage with <em>-g</em> flag and calculations
-close to sunset/sunrise:
-
-<pre>
- [...]
- sunangleabovehorizont=0.434240
- sunrise=07:59:19
- sunset=16:25:17
- Time (07:59:02) is before sunrise (07:59:19)!
- WARNING: Nothing to calculate. Please verify settings.
- No map calculation requested. Finished.
-</pre>
-
-In above calculation appears to be a mistake as
-the program indicates that we are before sunrise while
-the <i>sun angle above horizon</i> is already positive.
-The reason is that <i>sun angle above horizon</i> is
-calculated with correction for atmosphere refraction while
-<i>sunrise</i> and <i>sunset</i> are calculated <b>without</b>
-correction for atmosphere refraction. The output without
-<em>-g</em> flag contains related indications.
-
-
-<h2>Acknowledgements</h2>
-Acknowledgements: National Renewable Energy Laboratory for their <a href=http://rredc.nrel.gov/solar/codes_algs/solpos/>SOLPOS 2.0</a> sun position
-algorithm.
-
-<h2>SEE ALSO</h2>
-<em>
-<a href="g.region.html">g.region</a>,
-<a href="r.sun.html">r.sun</a>,
-<a href="r.slope.aspect.html">r.slope.aspect</a>
-</em>
-
-<h2>AUTHOR</h2>
-Janne Soimasuo, Finland 1994<br>
-update to FP by Huidae Cho 2001<br>
-added solpos algorithm feature by Markus Neteler 2001
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.sunmask/r.sunmask.html (from rev 32770, grass/trunk/raster/r.sunmask/description.html)
===================================================================
--- grass/trunk/raster/r.sunmask/r.sunmask.html (rev 0)
+++ grass/trunk/raster/r.sunmask/r.sunmask.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,74 @@
+<h2>DESCRIPTION</h2>
+
+<em>r.sunmask</em> creates an output map layer based on an input elevation
+raster map layer and the sun position. The output map layer contains the
+cast shadow areas arising from sun shine and elevations. The user can define
+the sun position either directly or the module calculates it from given
+location and date/time parameters using the
+<a href=http://rredc.nrel.gov/>NREL</a> sun position algorithm. So either
+"A:"-parameters to specify the exact known sun position or "B:-parameters"
+to specify date/time for sun position calculation by r.sunmask itself have
+to be used.
+
+<p>
+The module performs sunset/sunrise checks and refraction correction for sun
+position calculation. Local coordinate systems are internally transformed to
+latitude/longitude for the SOLPOS algorithm. The elevation is not considered
+in the sunset/sunrise calculations.
+
+<h2>Notes</h2>
+
+r.sunmask and daylight savings: Rather than convert time to GMT, the solpos
+algorithm uses what is called Local Standard Time, which is generally
+defined politically as an offset from GMT. So the key is the offset from
+GMT, which the solpos Time Zone parameter. If the user specifies clock time
+(different for winter and summer), he/she would have to change the Time Zone
+parameter seasonally in r.sunmask (timezone parameter).
+<p>
+
+Note: In latitude/longitude locations the position coordinates pair
+(east/west) has to be specified in decimal degree (not D:M:S). If
+not specified, the map center's coordinates will be used.
+Also <em>g.region -l</em> displays the map center's coordinates.
+
+<p>
+Note for module usage with <em>-g</em> flag and calculations
+close to sunset/sunrise:
+
+<pre>
+ [...]
+ sunangleabovehorizont=0.434240
+ sunrise=07:59:19
+ sunset=16:25:17
+ Time (07:59:02) is before sunrise (07:59:19)!
+ WARNING: Nothing to calculate. Please verify settings.
+ No map calculation requested. Finished.
+</pre>
+
+In above calculation appears to be a mistake as
+the program indicates that we are before sunrise while
+the <i>sun angle above horizon</i> is already positive.
+The reason is that <i>sun angle above horizon</i> is
+calculated with correction for atmosphere refraction while
+<i>sunrise</i> and <i>sunset</i> are calculated <b>without</b>
+correction for atmosphere refraction. The output without
+<em>-g</em> flag contains related indications.
+
+
+<h2>Acknowledgements</h2>
+Acknowledgements: National Renewable Energy Laboratory for their <a href=http://rredc.nrel.gov/solar/codes_algs/solpos/>SOLPOS 2.0</a> sun position
+algorithm.
+
+<h2>SEE ALSO</h2>
+<em>
+<a href="g.region.html">g.region</a>,
+<a href="r.sun.html">r.sun</a>,
+<a href="r.slope.aspect.html">r.slope.aspect</a>
+</em>
+
+<h2>AUTHOR</h2>
+Janne Soimasuo, Finland 1994<br>
+update to FP by Huidae Cho 2001<br>
+added solpos algorithm feature by Markus Neteler 2001
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.support/description.html
===================================================================
--- grass/trunk/raster/r.support/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.support/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,42 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<b>r.support</b> allows the user to create and/or edit raster map support
-information. Editing of raster map color tables, category labels, header,
-history, and title is supported. Category labels can also be copied from
-another raster map.
-
-<h2>NOTES</h2>
-
-If metadata options such as <b>title</b> or <b>history</b> are given the
-module will run non-interactively. If only the map name is given
-<em>r.support</em> will run interactively within a terminal shell and the
-user with be prompted for input.
-<p>
-Freeform metadata information is stored in a "<tt>hist</tt>" file which may be
-appended to by using the <b>history</b> option. Currently this is limited to
-50 lines of text with a maximum line length of 78 characters. Any input
-larger than this will be wrapped to the next line.
-All other metadata strings available as standard options are limited to
-79 characters.
-
-<h2>SEE ALSO</h2>
-<em>
-<a href="r.category.html">r.category</a>,
-<a href="r.describe.html">r.describe</a>,
-<a href="r.info.html">r.info</a>,
-<a href="r.null.html">r.null</a>,
-<a href="r.region.html">r.region</a>,
-<a href="r.report.html">r.report</a>,
-<a href="r.timestamp.html">r.timestamp</a>
-</em>
-
-<h2>AUTHORS</h2>
-
-Micharl Shapiro, CERL: Original author<br>
-<a href="MAILTO:rez at touchofmadness.com">Brad Douglas</a>: GRASS 6 Port<br>
-M. Hamish Bowman: command line enhancements<br>
-Markus Neteler: category copy from other map
-
-<p>
-<i>Last changed: $Date$</i>
-</p>
Copied: grass/trunk/raster/r.support/r.support.html (from rev 32770, grass/trunk/raster/r.support/description.html)
===================================================================
--- grass/trunk/raster/r.support/r.support.html (rev 0)
+++ grass/trunk/raster/r.support/r.support.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,42 @@
+<h2>DESCRIPTION</h2>
+
+<b>r.support</b> allows the user to create and/or edit raster map support
+information. Editing of raster map color tables, category labels, header,
+history, and title is supported. Category labels can also be copied from
+another raster map.
+
+<h2>NOTES</h2>
+
+If metadata options such as <b>title</b> or <b>history</b> are given the
+module will run non-interactively. If only the map name is given
+<em>r.support</em> will run interactively within a terminal shell and the
+user with be prompted for input.
+<p>
+Freeform metadata information is stored in a "<tt>hist</tt>" file which may be
+appended to by using the <b>history</b> option. Currently this is limited to
+50 lines of text with a maximum line length of 78 characters. Any input
+larger than this will be wrapped to the next line.
+All other metadata strings available as standard options are limited to
+79 characters.
+
+<h2>SEE ALSO</h2>
+<em>
+<a href="r.category.html">r.category</a>,
+<a href="r.describe.html">r.describe</a>,
+<a href="r.info.html">r.info</a>,
+<a href="r.null.html">r.null</a>,
+<a href="r.region.html">r.region</a>,
+<a href="r.report.html">r.report</a>,
+<a href="r.timestamp.html">r.timestamp</a>
+</em>
+
+<h2>AUTHORS</h2>
+
+Micharl Shapiro, CERL: Original author<br>
+<a href="MAILTO:rez at touchofmadness.com">Brad Douglas</a>: GRASS 6 Port<br>
+M. Hamish Bowman: command line enhancements<br>
+Markus Neteler: category copy from other map
+
+<p>
+<i>Last changed: $Date$</i>
+</p>
Deleted: grass/trunk/raster/r.support.stats/description.html
===================================================================
--- grass/trunk/raster/r.support.stats/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.support.stats/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,22 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<b>r.support.stats</b> allows the user to update raster map statistics
-information.
-
-
-<h2>NOTES</h2>
-
-None
-
-
-<h2>SEE ALSO</h2>
-<a href="r.support.html">r.support</a>,
-<a href="r.report.html">r.report</a>
-
-
-<h2>AUTHORS</h2>
-
-Micharl Shapiro, CERL: Original author<br>
-<a href="MAILTO:rez at touchofmadness.com">Brad Douglas</a>: GRASS 6 Port<br>
-
-<p><i>Last changed: $Date$</i> </p>
Copied: grass/trunk/raster/r.support.stats/r.support.stats.html (from rev 32770, grass/trunk/raster/r.support.stats/description.html)
===================================================================
--- grass/trunk/raster/r.support.stats/r.support.stats.html (rev 0)
+++ grass/trunk/raster/r.support.stats/r.support.stats.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,22 @@
+<h2>DESCRIPTION</h2>
+
+<b>r.support.stats</b> allows the user to update raster map statistics
+information.
+
+
+<h2>NOTES</h2>
+
+None
+
+
+<h2>SEE ALSO</h2>
+<a href="r.support.html">r.support</a>,
+<a href="r.report.html">r.report</a>
+
+
+<h2>AUTHORS</h2>
+
+Micharl Shapiro, CERL: Original author<br>
+<a href="MAILTO:rez at touchofmadness.com">Brad Douglas</a>: GRASS 6 Port<br>
+
+<p><i>Last changed: $Date$</i> </p>
Deleted: grass/trunk/raster/r.surf.area/description.html
===================================================================
--- grass/trunk/raster/r.surf.area/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.surf.area/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,66 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>r.surf.area</em> Calculates area of regular 3D triangulated points
-(centers of cells) in current region by adding areas of triangles.
-Therefore, area of a flat surface will be reported as
-(rows + cols -1)*(area of cell) less than area of
-flat region due to a half row and half column missing around the
-perimeter.
-
-<h2>NOTE</h2>
-
-This calculation is heavily dependent on
-data resolution (think of it as a fractal shoreline problem, the more
-resolution the more detail, the more area, etc). This program uses the
-<em>CURRENT GRASS REGION</em>, not the resolution of the map. This is
-especially important for surfaces with <tt>NULL</tt> values and highly
-irregular edges. The program does not [currently] attempt to correct for
-the error introduced by this <em>edge effect</em>.
-
-<p>
-
-This version actually calculates area twice for each triangle pair,
-keeping a running minimum and maximum area depending on the
-direction of the diagonal used.
-
-<p>
-
-<ol>
-<lh>Reported totals are:
-<li>"Plan" area of <tt>NULL</tt> values within the current GRASS region
-<li>"Plan" area within calculation region (rows-1 * cols-1 * cellarea)
-<li>Average of the minimum and maximum calculated 3d triangle area
-within this region
-<li>"Plan" area within current GRASS region (rows * cols * cellarea)
-<li>Scaling of calculated area to current GRASS region (see
-<a href="#note">NOTE</a>)
-</ol>
-
-<h2>NOTES</h2>
-
-<em>r.surf.area</em> works best when the surface being evaluated extends
-to the edges of the current GRASS region and the cell resolution is small.
-Surfaces which are especially long and thin and have highly irregular
-boudaries will tend to have underestimated surface areas. Setting a
-high cell resolution (small area) will greatly reduce this impact, but will
-cause longer processing times.
-
-<h2>SEE ALSO</h2>
-
-<em><a href="r.sum.html">r.sum</a></em>,
-<em><a href="r.surf.idw.html">r.surf.idw</a></em>,
-<em><a href="r.surf.idw2.html">r.surf.idw2</a></em>,
-<em><a href="r.surf.fractal.html">r.surf.fractal</a></em>,
-<em><a href="r.surf.gauss.html">r.surf.gauss</a></em>,
-<em><a href="r.volume.html">r.volume</a></em>,
-<em><a href="v.to.rast.html">v.to.rast</a></em>,
-<em><a href="r.slope.aspect.html">r.slope.aspect</a></em>,
-<em><a href="g.region.html">g.region</a></em>
-
-<h2>AUTHOR</h2>
-Bill Brown, USACERL December 21, 1994
-<p>
-Modified for floating point rasters and <tt>NULL</tt> values by
-Eric G. Miller (October 17, 2000)
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.surf.area/r.surf.area.html (from rev 32770, grass/trunk/raster/r.surf.area/description.html)
===================================================================
--- grass/trunk/raster/r.surf.area/r.surf.area.html (rev 0)
+++ grass/trunk/raster/r.surf.area/r.surf.area.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,66 @@
+<h2>DESCRIPTION</h2>
+
+<em>r.surf.area</em> Calculates area of regular 3D triangulated points
+(centers of cells) in current region by adding areas of triangles.
+Therefore, area of a flat surface will be reported as
+(rows + cols -1)*(area of cell) less than area of
+flat region due to a half row and half column missing around the
+perimeter.
+
+<h2>NOTE</h2>
+
+This calculation is heavily dependent on
+data resolution (think of it as a fractal shoreline problem, the more
+resolution the more detail, the more area, etc). This program uses the
+<em>CURRENT GRASS REGION</em>, not the resolution of the map. This is
+especially important for surfaces with <tt>NULL</tt> values and highly
+irregular edges. The program does not [currently] attempt to correct for
+the error introduced by this <em>edge effect</em>.
+
+<p>
+
+This version actually calculates area twice for each triangle pair,
+keeping a running minimum and maximum area depending on the
+direction of the diagonal used.
+
+<p>
+
+<ol>
+<lh>Reported totals are:
+<li>"Plan" area of <tt>NULL</tt> values within the current GRASS region
+<li>"Plan" area within calculation region (rows-1 * cols-1 * cellarea)
+<li>Average of the minimum and maximum calculated 3d triangle area
+within this region
+<li>"Plan" area within current GRASS region (rows * cols * cellarea)
+<li>Scaling of calculated area to current GRASS region (see
+<a href="#note">NOTE</a>)
+</ol>
+
+<h2>NOTES</h2>
+
+<em>r.surf.area</em> works best when the surface being evaluated extends
+to the edges of the current GRASS region and the cell resolution is small.
+Surfaces which are especially long and thin and have highly irregular
+boudaries will tend to have underestimated surface areas. Setting a
+high cell resolution (small area) will greatly reduce this impact, but will
+cause longer processing times.
+
+<h2>SEE ALSO</h2>
+
+<em><a href="r.sum.html">r.sum</a></em>,
+<em><a href="r.surf.idw.html">r.surf.idw</a></em>,
+<em><a href="r.surf.idw2.html">r.surf.idw2</a></em>,
+<em><a href="r.surf.fractal.html">r.surf.fractal</a></em>,
+<em><a href="r.surf.gauss.html">r.surf.gauss</a></em>,
+<em><a href="r.volume.html">r.volume</a></em>,
+<em><a href="v.to.rast.html">v.to.rast</a></em>,
+<em><a href="r.slope.aspect.html">r.slope.aspect</a></em>,
+<em><a href="g.region.html">g.region</a></em>
+
+<h2>AUTHOR</h2>
+Bill Brown, USACERL December 21, 1994
+<p>
+Modified for floating point rasters and <tt>NULL</tt> values by
+Eric G. Miller (October 17, 2000)
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.surf.contour/description.html
===================================================================
--- grass/trunk/raster/r.surf.contour/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.surf.contour/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,101 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-
-<em>r.surf.contour</em> creates a raster elevation map from a rasterized
-contour map. Elevation values are determined using procedures similar
-to a manual methods.
-To determine the elevation of a point on a contour map, an individual
-might interpolate its value from those of the two nearest contour lines
-(uphill and downhill).
-
-
-<p>
-
-<em>r.surf.contour</em> works in a similar way. Initially, a vector map of
-the contour lines is made with the elevation of each line as an attribute.
-When the program <em><a href="v.to.rast.html">v.to.rast</a></em>
-is run on the vector map, continuous "lines" of rasters containing the
-contour line values will be the input for <em>r.surf.contour</em>. For each
-cell in the input map, either the cell is a contour line cell (which is
-given that value), or a flood fill is generated from that spot until the
-fill comes to two unique values. So the <em>r.surf.contour</em> algorithm
-<strong>linearly interpolates</strong> between contour lines. The flood fill
-is not allowed to cross over
-the rasterized contour lines, thus ensuring that an uphill and downhill
-contour value will be the two values chosen. <em>r.surf.contour</em>
-interpolates from the uphill and downhill values by the true distance.
-
-
-<h3>Parameters:</h3>
-
-<dl>
-
-<dt><b>input=</b><em>name</em>
-
-<dd>Name of an existing raster map that contains a set of
-initial category values (i.e., some cells contain known elevation
-values (denoting contours) while the rest contain NULL values or zeros (0)).
-
-<dt><b>output=</b><em>name</em>
-
-<dd>Name to be assigned to new output raster map that represents
-a smooth (e.g., elevation) surface generated from
-the known category values in the input raster map layer.
-</dl>
-
-<h2>NOTES</h2>
-
-<em>r.surf.contour</em> works well under the following circumstances:
-1) the contour lines extend to the the edge of the current region,
-2) the program is run at the same resolution as that of the input map,
-3) there are no disjointed contour lines,
-and 4) no spot elevation data BETWEEN contour lines exist. Spot elevations at
-the tops of hills and the bottoms of depressions, on the other hand, improve
-the output greatly.
-Violating these constraints will cause non-intuitive anomalies to appear in
-the output map. Run <em> <a href="r.slope.aspect.html">r.slope.aspect</a>
-</em> on <em>r.surf.contour</em> results to locate potential anomalies.
-
-
-<p>
-The running of <em>r.surf.contour</em> is very sensitive to the resolution of
-rasterized vector map. If multiple contour lines go through the same raster,
-slight anomalies may occur. The speed of <em>r.surf.contour</em> is dependent
-on how far "apart" the contour lines are from each other (as measured in
-raster cells). Since a flood fill algorithm is used, the program's running
-time will grow exponentially with the distance between contour lines.
-
-<h2>BUGS</h2>
-
-<em>r.surf.contour</em> has not been fully updated for NULL support and still
-considers a value of "<tt>0</tt>" to be NULL. Thus any contour lines at 0
-elevation (e.g. the coastline) will be ignored. In such cases converting any
-0 values in the input map to -1 with <em>r.mapcalc</em> may be a suitable
-work-around.
-<p>
-Currently <em>r.surf.contour</em> will only produce CELL (integer) map output.
-If you would like a finer grade output map (i.e. floating point) it is
-recommended to multiply the <b>input</b> map by 1000 (for example) using
-<em>r.mapcalc</em>, then divide the resultant <em>r.surf.contour</em>
-<b>output</b> map by 1000.0, again with <em>r.mapcalc</em>.
-<p>
-Volunteers are sought to remedy both these issues.
-
-<h2>SEE ALSO</h2>
-
-<em><a href="r.mapcalc.html">r.mapcalc</a></em>,
-<em><a href="r.slope.aspect.html">r.slope.aspect</a></em>,
-<em><a href="r.surf.idw.html">r.surf.idw</a></em>,
-<em><a href="r.surf.idw2.html">r.surf.idw2</a></em>,
-<em><a href="v.digit.html">v.digit</a></em>,
-<em><a href="v.surf.idw.html">v.surf.idw</a></em>,
-<em><a href="v.surf.rst.html">v.surf.rst</a></em>,
-<em><a href="v.to.rast.html">v.to.rast</a></em>
-
-
-<h2>AUTHOR</h2>
-
-Chuck Ehlschlaeger, U.S. Army Construction Engineering Research Laboratory
-
-<p>
-<i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.surf.contour/r.surf.contour.html (from rev 32770, grass/trunk/raster/r.surf.contour/description.html)
===================================================================
--- grass/trunk/raster/r.surf.contour/r.surf.contour.html (rev 0)
+++ grass/trunk/raster/r.surf.contour/r.surf.contour.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,101 @@
+<h2>DESCRIPTION</h2>
+
+
+<em>r.surf.contour</em> creates a raster elevation map from a rasterized
+contour map. Elevation values are determined using procedures similar
+to a manual methods.
+To determine the elevation of a point on a contour map, an individual
+might interpolate its value from those of the two nearest contour lines
+(uphill and downhill).
+
+
+<p>
+
+<em>r.surf.contour</em> works in a similar way. Initially, a vector map of
+the contour lines is made with the elevation of each line as an attribute.
+When the program <em><a href="v.to.rast.html">v.to.rast</a></em>
+is run on the vector map, continuous "lines" of rasters containing the
+contour line values will be the input for <em>r.surf.contour</em>. For each
+cell in the input map, either the cell is a contour line cell (which is
+given that value), or a flood fill is generated from that spot until the
+fill comes to two unique values. So the <em>r.surf.contour</em> algorithm
+<strong>linearly interpolates</strong> between contour lines. The flood fill
+is not allowed to cross over
+the rasterized contour lines, thus ensuring that an uphill and downhill
+contour value will be the two values chosen. <em>r.surf.contour</em>
+interpolates from the uphill and downhill values by the true distance.
+
+
+<h3>Parameters:</h3>
+
+<dl>
+
+<dt><b>input=</b><em>name</em>
+
+<dd>Name of an existing raster map that contains a set of
+initial category values (i.e., some cells contain known elevation
+values (denoting contours) while the rest contain NULL values or zeros (0)).
+
+<dt><b>output=</b><em>name</em>
+
+<dd>Name to be assigned to new output raster map that represents
+a smooth (e.g., elevation) surface generated from
+the known category values in the input raster map layer.
+</dl>
+
+<h2>NOTES</h2>
+
+<em>r.surf.contour</em> works well under the following circumstances:
+1) the contour lines extend to the the edge of the current region,
+2) the program is run at the same resolution as that of the input map,
+3) there are no disjointed contour lines,
+and 4) no spot elevation data BETWEEN contour lines exist. Spot elevations at
+the tops of hills and the bottoms of depressions, on the other hand, improve
+the output greatly.
+Violating these constraints will cause non-intuitive anomalies to appear in
+the output map. Run <em> <a href="r.slope.aspect.html">r.slope.aspect</a>
+</em> on <em>r.surf.contour</em> results to locate potential anomalies.
+
+
+<p>
+The running of <em>r.surf.contour</em> is very sensitive to the resolution of
+rasterized vector map. If multiple contour lines go through the same raster,
+slight anomalies may occur. The speed of <em>r.surf.contour</em> is dependent
+on how far "apart" the contour lines are from each other (as measured in
+raster cells). Since a flood fill algorithm is used, the program's running
+time will grow exponentially with the distance between contour lines.
+
+<h2>BUGS</h2>
+
+<em>r.surf.contour</em> has not been fully updated for NULL support and still
+considers a value of "<tt>0</tt>" to be NULL. Thus any contour lines at 0
+elevation (e.g. the coastline) will be ignored. In such cases converting any
+0 values in the input map to -1 with <em>r.mapcalc</em> may be a suitable
+work-around.
+<p>
+Currently <em>r.surf.contour</em> will only produce CELL (integer) map output.
+If you would like a finer grade output map (i.e. floating point) it is
+recommended to multiply the <b>input</b> map by 1000 (for example) using
+<em>r.mapcalc</em>, then divide the resultant <em>r.surf.contour</em>
+<b>output</b> map by 1000.0, again with <em>r.mapcalc</em>.
+<p>
+Volunteers are sought to remedy both these issues.
+
+<h2>SEE ALSO</h2>
+
+<em><a href="r.mapcalc.html">r.mapcalc</a></em>,
+<em><a href="r.slope.aspect.html">r.slope.aspect</a></em>,
+<em><a href="r.surf.idw.html">r.surf.idw</a></em>,
+<em><a href="r.surf.idw2.html">r.surf.idw2</a></em>,
+<em><a href="v.digit.html">v.digit</a></em>,
+<em><a href="v.surf.idw.html">v.surf.idw</a></em>,
+<em><a href="v.surf.rst.html">v.surf.rst</a></em>,
+<em><a href="v.to.rast.html">v.to.rast</a></em>
+
+
+<h2>AUTHOR</h2>
+
+Chuck Ehlschlaeger, U.S. Army Construction Engineering Research Laboratory
+
+<p>
+<i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.surf.fractal/description.html
===================================================================
--- grass/trunk/raster/r.surf.fractal/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.surf.fractal/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,41 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<b>r.surf.fractal</b> creates a fractal surface of a given fractal
-dimension. Uses spectral synthesis method. Can create intermediate layers
-showing the build up of different spectral coefficients (see Saupe,
-pp.106-107 for an example of this).
-
-<p>
-Use this module to generate naturally looking synthetical elevation models
-(DEM).
-
-
-<h2>NOTE</h2>
-This module requires the <a href="http://www.fftw.org">FFTW library</a>
-for computing Discrete Fourier Transforms.
-
-
-<h2>REFERENCE</h2>
- Saupe, D. (1988) Algorithms for random fractals, in Barnsley M.,
- Devaney R., Mandelbrot B., Peitgen, H-O., Saupe D., and Voss R.
- (1988) The Science of Fractal Images, Ch. 2, pp.71-136. London:
- Springer-Verlag.
-
-<h2>SEE ALSO</h2>
-
-<em><a href="r.surf.contour.html">r.surf.contour</a></em>,
-<em><a href="r.surf.idw.html">r.surf.idw</a></em>,
-<em><a href="r.surf.gauss.html">r.surf.gauss</a></em>,
-<em><a href="r.surf.random.html">r.surf.random</a></em>,
-<em><a href="r.surf.idw2.html">r.surf.idw2</a></em>,
-<em><a href="v.surf.idw.html">v.surf.idw</a></em>,
-<em><a href="v.surf.rst.html">v.surf.rst</a></em>
-
-
-<address>
-<a href="MAILTO:jwo at le.ac.uk">jwo at le.ac.uk</a></address>
-
-<br><a href="http://www.geog.le.ac.uk/assist/index.html">ASSIST's home</a>
-
-<p>
-<i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.surf.fractal/r.surf.fractal.html (from rev 32770, grass/trunk/raster/r.surf.fractal/description.html)
===================================================================
--- grass/trunk/raster/r.surf.fractal/r.surf.fractal.html (rev 0)
+++ grass/trunk/raster/r.surf.fractal/r.surf.fractal.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,41 @@
+<h2>DESCRIPTION</h2>
+
+<b>r.surf.fractal</b> creates a fractal surface of a given fractal
+dimension. Uses spectral synthesis method. Can create intermediate layers
+showing the build up of different spectral coefficients (see Saupe,
+pp.106-107 for an example of this).
+
+<p>
+Use this module to generate naturally looking synthetical elevation models
+(DEM).
+
+
+<h2>NOTE</h2>
+This module requires the <a href="http://www.fftw.org">FFTW library</a>
+for computing Discrete Fourier Transforms.
+
+
+<h2>REFERENCE</h2>
+ Saupe, D. (1988) Algorithms for random fractals, in Barnsley M.,
+ Devaney R., Mandelbrot B., Peitgen, H-O., Saupe D., and Voss R.
+ (1988) The Science of Fractal Images, Ch. 2, pp.71-136. London:
+ Springer-Verlag.
+
+<h2>SEE ALSO</h2>
+
+<em><a href="r.surf.contour.html">r.surf.contour</a></em>,
+<em><a href="r.surf.idw.html">r.surf.idw</a></em>,
+<em><a href="r.surf.gauss.html">r.surf.gauss</a></em>,
+<em><a href="r.surf.random.html">r.surf.random</a></em>,
+<em><a href="r.surf.idw2.html">r.surf.idw2</a></em>,
+<em><a href="v.surf.idw.html">v.surf.idw</a></em>,
+<em><a href="v.surf.rst.html">v.surf.rst</a></em>
+
+
+<address>
+<a href="MAILTO:jwo at le.ac.uk">jwo at le.ac.uk</a></address>
+
+<br><a href="http://www.geog.le.ac.uk/assist/index.html">ASSIST's home</a>
+
+<p>
+<i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.surf.gauss/description.html
===================================================================
--- grass/trunk/raster/r.surf.gauss/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.surf.gauss/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,27 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<b>r.surf.gauss</b> produces a raster map layer of Gaussian deviates whose
-mean and standard deviation can be expressed by the user. It uses a Gaussian
-random number generator. It is essentialy the same as <em>r.surf.random</em>,
-but uses a Gaussian random number generator instead.
-
-<p>
-<center>
-<img src="r_surf_gauss_hist.png" alt="r.surf.gauss map histogram"><br>
-<i>Histogram of map generated with r.surf.gauss (mean=0, sigma=10)</i>
-</center>
-
-<h2>SEE ALSO</h2>
-<em><a href="r.surf.contour.html">r.surf.contour</a></em>,
-<em><a href="r.surf.fractal.html">r.surf.fractal</a></em>,
-<em><a href="r.surf.idw.html">r.surf.idw</a></em>,
-<em><a href="r.surf.idw2.html">r.surf.idw2</a></em>,
-<em><a href="r.surf.random.html">r.surf.random</a></em>,
-<em><a href="v.surf.rst.html">v.surf.rst</a></em>
-
-<h2>AUTHOR</h2>
-
-Jo Wood
-<br><a href="http://www.geog.le.ac.uk/assist/index.html">ASSIST's home</a>
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.surf.gauss/r.surf.gauss.html (from rev 32770, grass/trunk/raster/r.surf.gauss/description.html)
===================================================================
--- grass/trunk/raster/r.surf.gauss/r.surf.gauss.html (rev 0)
+++ grass/trunk/raster/r.surf.gauss/r.surf.gauss.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,27 @@
+<h2>DESCRIPTION</h2>
+
+<b>r.surf.gauss</b> produces a raster map layer of Gaussian deviates whose
+mean and standard deviation can be expressed by the user. It uses a Gaussian
+random number generator. It is essentialy the same as <em>r.surf.random</em>,
+but uses a Gaussian random number generator instead.
+
+<p>
+<center>
+<img src="r_surf_gauss_hist.png" alt="r.surf.gauss map histogram"><br>
+<i>Histogram of map generated with r.surf.gauss (mean=0, sigma=10)</i>
+</center>
+
+<h2>SEE ALSO</h2>
+<em><a href="r.surf.contour.html">r.surf.contour</a></em>,
+<em><a href="r.surf.fractal.html">r.surf.fractal</a></em>,
+<em><a href="r.surf.idw.html">r.surf.idw</a></em>,
+<em><a href="r.surf.idw2.html">r.surf.idw2</a></em>,
+<em><a href="r.surf.random.html">r.surf.random</a></em>,
+<em><a href="v.surf.rst.html">v.surf.rst</a></em>
+
+<h2>AUTHOR</h2>
+
+Jo Wood
+<br><a href="http://www.geog.le.ac.uk/assist/index.html">ASSIST's home</a>
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.surf.idw/description.html
===================================================================
--- grass/trunk/raster/r.surf.idw/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.surf.idw/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,110 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-
-<em>r.surf.idw</em> fills a grid cell (raster) matrix with
-interpolated values generated from a set of input layer
-data points. It uses a numerical approximation technique
-based on distance squared weighting of the values of
-nearest data points. The number of nearest data points used
-to determined the interpolated value of a cell can be
-specified by the user (default: 12 nearest data points).
-
-<p>
-
-If there is a current working mask, it applies to the output
-raster map. Only those cells falling within the mask will be
-assigned interpolated values. The search procedure for the
-selection of nearest neighboring points will consider all
-input data, without regard to the mask.
-
-The <b>-e</b> flag is the error analysis option that interpolates values
-only for those cells of the input raster map which have non-zero values and
-outputs the difference (see <a href="#minuse.html">NOTES</a> below).
-<p>
-The <b>npoints</b> parameter defines the number of nearest data points used
-to determine the interpolated value of an output raster cell.
-
-<A NAME="notes.html"><h2>NOTES</h2></a>
-
-<em>r.surf.idw</em> is a surface generation utility which
-uses inverse distance squared weighting (as described in
-<b>Applied Geostatistics</b> by E. H. Isaaks and R. M.
-Srivastava, Oxford University Press, 1989) to assign
-interpolated values. The implementation includes a
-customized data structure somewhat akin to a sparse matrix
-which enhances the efficiency with which nearest data
-points are selected. For latitude/longitude projections,
-distances are calculated from point to point along a
-geodesic.
-
-<p>
-
-Unlike <em><a href="r.surf.idw2.html">r.surf.idw2</a></em>, which processes
-all input data points in each interpolation cycle, <em>r.surf.idw</em>
-attempts to minimize the number of input data for which distances must be
-calculated. Execution speed is therefore a function of the search effort,
-and does not increase appreciably with the number of input data points.
-
-<p>
-
-<em>r.surf.idw</em> will generally outperform <em><A
-HREF="r.surf.idw2.html">r.surf.idw2</a></em> except when the input data
-layer contains few non-zero data, i.e. when the cost of the search exceeds
-the cost of the additional distance calculations performed by <em><A
-HREF="r.surf.idw2.html">r.surf.idw2</a></em>. The relative performance of
-these utilities will depend on the comparative speed of boolean, integer and
-floating point operations on a particular platform.
-
-<p>
-
-Worst case search performance by <em>r.surf.idw</em> occurs
-when the interpolated cell is located outside of the region
-in which input data are distributed. It therefore behooves
-the user to employ a mask when geographic region boundaries
-include large areas outside the general extent of the input
-data.
-
-<p>
-
-The degree of smoothing produced by the interpolation will
-increase relative to the number of nearest data points
-considered. The utility may be used with regularly or
-irregularly spaced input data. However, the output result
-for the former may include unacceptable nonconformities in
-the surface pattern.
-
-<p>
-
-The <A NAME="minuse.html"><b>-e</b></a> flag option provides a standard
-surface-generation error analysis facility. It produces an output raster map
-of the difference of interpolated values minus input values for those cells
-whose input data are non-zero. For each interpolation cycle, the known value
-of the cell under consideration is ignored, and the remaining input values
-are used to interpolate a result. The output raster map may be compared to
-the input raster map to analyze the distribution of interpolation error.
-This procedure may be helpful in choosing the number of nearest neighbors
-considered for surface generation.
-
-<h2>SEE ALSO</h2>
-
-<em><a href="r.surf.contour.html">r.surf.contour</a></em>,
-<em><a href="r.surf.idw2.html">r.surf.idw2</a></em>,
-<em><a href="r.surf.gauss.html">r.surf.gauss</a></em>,
-<em><a href="r.surf.fractal.html">r.surf.fractal</a></em>,
-<em><a href="r.surf.random.html">r.surf.random</a></em>,
-<em><a href="v.surf.idw.html">v.surf.idw</a></em>,
-<em><a href="v.surf.rst.html">v.surf.rst</a></em>
-
-<h2>AUTHOR</h2>
-
-Greg Koerper
-<br>
-Global Climate Research Project
-<br>
-U.S. EPA Environmental Research Laboratory
-<br>
-200 S.W. 35th Street, JSB
-<br>
-Corvallis, OR 97333
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.surf.idw/r.surf.idw.html (from rev 32770, grass/trunk/raster/r.surf.idw/description.html)
===================================================================
--- grass/trunk/raster/r.surf.idw/r.surf.idw.html (rev 0)
+++ grass/trunk/raster/r.surf.idw/r.surf.idw.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,110 @@
+<h2>DESCRIPTION</h2>
+
+
+<em>r.surf.idw</em> fills a grid cell (raster) matrix with
+interpolated values generated from a set of input layer
+data points. It uses a numerical approximation technique
+based on distance squared weighting of the values of
+nearest data points. The number of nearest data points used
+to determined the interpolated value of a cell can be
+specified by the user (default: 12 nearest data points).
+
+<p>
+
+If there is a current working mask, it applies to the output
+raster map. Only those cells falling within the mask will be
+assigned interpolated values. The search procedure for the
+selection of nearest neighboring points will consider all
+input data, without regard to the mask.
+
+The <b>-e</b> flag is the error analysis option that interpolates values
+only for those cells of the input raster map which have non-zero values and
+outputs the difference (see <a href="#minuse.html">NOTES</a> below).
+<p>
+The <b>npoints</b> parameter defines the number of nearest data points used
+to determine the interpolated value of an output raster cell.
+
+<A NAME="notes.html"><h2>NOTES</h2></a>
+
+<em>r.surf.idw</em> is a surface generation utility which
+uses inverse distance squared weighting (as described in
+<b>Applied Geostatistics</b> by E. H. Isaaks and R. M.
+Srivastava, Oxford University Press, 1989) to assign
+interpolated values. The implementation includes a
+customized data structure somewhat akin to a sparse matrix
+which enhances the efficiency with which nearest data
+points are selected. For latitude/longitude projections,
+distances are calculated from point to point along a
+geodesic.
+
+<p>
+
+Unlike <em><a href="r.surf.idw2.html">r.surf.idw2</a></em>, which processes
+all input data points in each interpolation cycle, <em>r.surf.idw</em>
+attempts to minimize the number of input data for which distances must be
+calculated. Execution speed is therefore a function of the search effort,
+and does not increase appreciably with the number of input data points.
+
+<p>
+
+<em>r.surf.idw</em> will generally outperform <em><A
+HREF="r.surf.idw2.html">r.surf.idw2</a></em> except when the input data
+layer contains few non-zero data, i.e. when the cost of the search exceeds
+the cost of the additional distance calculations performed by <em><A
+HREF="r.surf.idw2.html">r.surf.idw2</a></em>. The relative performance of
+these utilities will depend on the comparative speed of boolean, integer and
+floating point operations on a particular platform.
+
+<p>
+
+Worst case search performance by <em>r.surf.idw</em> occurs
+when the interpolated cell is located outside of the region
+in which input data are distributed. It therefore behooves
+the user to employ a mask when geographic region boundaries
+include large areas outside the general extent of the input
+data.
+
+<p>
+
+The degree of smoothing produced by the interpolation will
+increase relative to the number of nearest data points
+considered. The utility may be used with regularly or
+irregularly spaced input data. However, the output result
+for the former may include unacceptable nonconformities in
+the surface pattern.
+
+<p>
+
+The <A NAME="minuse.html"><b>-e</b></a> flag option provides a standard
+surface-generation error analysis facility. It produces an output raster map
+of the difference of interpolated values minus input values for those cells
+whose input data are non-zero. For each interpolation cycle, the known value
+of the cell under consideration is ignored, and the remaining input values
+are used to interpolate a result. The output raster map may be compared to
+the input raster map to analyze the distribution of interpolation error.
+This procedure may be helpful in choosing the number of nearest neighbors
+considered for surface generation.
+
+<h2>SEE ALSO</h2>
+
+<em><a href="r.surf.contour.html">r.surf.contour</a></em>,
+<em><a href="r.surf.idw2.html">r.surf.idw2</a></em>,
+<em><a href="r.surf.gauss.html">r.surf.gauss</a></em>,
+<em><a href="r.surf.fractal.html">r.surf.fractal</a></em>,
+<em><a href="r.surf.random.html">r.surf.random</a></em>,
+<em><a href="v.surf.idw.html">v.surf.idw</a></em>,
+<em><a href="v.surf.rst.html">v.surf.rst</a></em>
+
+<h2>AUTHOR</h2>
+
+Greg Koerper
+<br>
+Global Climate Research Project
+<br>
+U.S. EPA Environmental Research Laboratory
+<br>
+200 S.W. 35th Street, JSB
+<br>
+Corvallis, OR 97333
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.surf.idw2/description.html
===================================================================
--- grass/trunk/raster/r.surf.idw2/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.surf.idw2/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,68 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>r.surf.idw2</em> fills a raster matrix with
-interpolated values generated from a set of irregularly
-spaced data points using numerical approximation (weighted
-averaging) techniques. The interpolated value of a cell is
-determined by values of nearby data points and the distance
-of the cell from those input points. In comparison with
-other methods, numerical approximation allows
-representation of more complex surfaces (particularly those
-with anomalous features), restricts the spatial influence
-of any errors, and generates the interpolated surface from
-the data points. It is the most appropriate method to
-apply to most spatial data.
-
-
-The <b>npoints</b> parameter defines the number of points to use for
-interpolation. The default is to use the 12 nearest points when
-interpolating the value for a particular cell.
-
-<h2>NOTES</h2>
-
-The amount of memory used by this program is related to the
-number of non-zero data values in the input map layer. If
-the input raster map layer is very dense (i.e., contains
-many non-zero data points), the program may not be able to
-get all the memory it needs from the system. The time
-required to execute increases with the number of input data
-points.
-
-<p>
-
-If the user has a mask set, then interpolation is only done
-for those cells that fall within the mask. However, all
-non-zero data points in the input layer are used even if
-they fall outside the mask.
-
-<p>
-
-This program does not work with latitude/longitude data
-bases. Another surface generation program, named
-<em><a href="r.surf.idw.html">r.surf.idw</a></em>,
-should be used with latitude/longitude data bases.
-
-
-<p>
-
-The user should refer to the manual entries for <br>
-<em><a href="r.surf.idw.html">r.surf.idw</a></em><br>
-<em><a href="r.surf.contour.html">r.surf.contour</a></em><br>
-<em><a href="v.surf.rst.html">v.surf.rst</a></em> <br>to
-compare this surface generation program with others available in GRASS.
-
-<h2>SEE ALSO</h2>
-
-<em><a href="r.surf.contour.html">r.surf.contour</a></em>,
-<em><a href="r.surf.idw.html">r.surf.idw</a></em>,
-<em><a href="r.surf.gauss.html">r.surf.gauss</a></em>,
-<em><a href="r.surf.fractal.html">r.surf.fractal</a></em>,
-<em><a href="r.surf.random.html">r.surf.random</a></em>,
-<em><a href="r.surf.idw2.html">r.surf.idw2</a></em>,
-<em><a href="v.surf.rst.html">v.surf.rst</a></em>
-
-<h2>AUTHOR</h2>
-
-Michael Shapiro, U.S.Army Construction Engineering Research Laboratory
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.surf.idw2/r.surf.idw2.html (from rev 32770, grass/trunk/raster/r.surf.idw2/description.html)
===================================================================
--- grass/trunk/raster/r.surf.idw2/r.surf.idw2.html (rev 0)
+++ grass/trunk/raster/r.surf.idw2/r.surf.idw2.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,68 @@
+<h2>DESCRIPTION</h2>
+
+<em>r.surf.idw2</em> fills a raster matrix with
+interpolated values generated from a set of irregularly
+spaced data points using numerical approximation (weighted
+averaging) techniques. The interpolated value of a cell is
+determined by values of nearby data points and the distance
+of the cell from those input points. In comparison with
+other methods, numerical approximation allows
+representation of more complex surfaces (particularly those
+with anomalous features), restricts the spatial influence
+of any errors, and generates the interpolated surface from
+the data points. It is the most appropriate method to
+apply to most spatial data.
+
+
+The <b>npoints</b> parameter defines the number of points to use for
+interpolation. The default is to use the 12 nearest points when
+interpolating the value for a particular cell.
+
+<h2>NOTES</h2>
+
+The amount of memory used by this program is related to the
+number of non-zero data values in the input map layer. If
+the input raster map layer is very dense (i.e., contains
+many non-zero data points), the program may not be able to
+get all the memory it needs from the system. The time
+required to execute increases with the number of input data
+points.
+
+<p>
+
+If the user has a mask set, then interpolation is only done
+for those cells that fall within the mask. However, all
+non-zero data points in the input layer are used even if
+they fall outside the mask.
+
+<p>
+
+This program does not work with latitude/longitude data
+bases. Another surface generation program, named
+<em><a href="r.surf.idw.html">r.surf.idw</a></em>,
+should be used with latitude/longitude data bases.
+
+
+<p>
+
+The user should refer to the manual entries for <br>
+<em><a href="r.surf.idw.html">r.surf.idw</a></em><br>
+<em><a href="r.surf.contour.html">r.surf.contour</a></em><br>
+<em><a href="v.surf.rst.html">v.surf.rst</a></em> <br>to
+compare this surface generation program with others available in GRASS.
+
+<h2>SEE ALSO</h2>
+
+<em><a href="r.surf.contour.html">r.surf.contour</a></em>,
+<em><a href="r.surf.idw.html">r.surf.idw</a></em>,
+<em><a href="r.surf.gauss.html">r.surf.gauss</a></em>,
+<em><a href="r.surf.fractal.html">r.surf.fractal</a></em>,
+<em><a href="r.surf.random.html">r.surf.random</a></em>,
+<em><a href="r.surf.idw2.html">r.surf.idw2</a></em>,
+<em><a href="v.surf.rst.html">v.surf.rst</a></em>
+
+<h2>AUTHOR</h2>
+
+Michael Shapiro, U.S.Army Construction Engineering Research Laboratory
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.surf.random/description.html
===================================================================
--- grass/trunk/raster/r.surf.random/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.surf.random/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,41 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<b>r.surf.random</b> produces a raster map layer of uniform random deviates
-whose range can be expressed by the user. It is essentialy the same as
-<em>r.surf.gauss</em>, but uses a linear random number generator instead.
-It uses the random number generator drand48() or rand()<!-- cite? -->,
-depending on the user's platform.
-
-<p>
-<center>
-<img src="r_surf_random_hist.png" alt="r.surf.random map histogram"><br>
-<i>Histogram of map generated with r.surf.random</i>
-</center>
-
-<h2>SEE ALSO</h2>
-
-<em>
-<a href="r.surf.contour.html">r.surf.contour</a>,
-<a href="r.surf.fractal.html">r.surf.fractal</a>,
-<a href="r.surf.gauss.html">r.surf.gauss</a>,
-<a href="r.surf.idw.html">r.surf.idw</a>,
-<a href="r.surf.idw2.html">r.surf.idw2</a>,
-<a href="v.surf.rst.html">v.surf.rst</a>
-</em>
-
-<h2>AUTHOR</h2>
-
-Jo Wood<br>
-Midlands Regional Research Laboratory (ASSIST)<br>
-University of Leicester<br>
-<i>October 1991</i>
-<br>
-
-<!-- almost certainly no longer valid
-<address>jwo at le.ac.uk</address>
-
-<br><a href="http://www.geog.le.ac.uk/assist/index.html">ASSIST's home</a>
--->
-
-<p>
-<i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.surf.random/r.surf.random.html (from rev 32770, grass/trunk/raster/r.surf.random/description.html)
===================================================================
--- grass/trunk/raster/r.surf.random/r.surf.random.html (rev 0)
+++ grass/trunk/raster/r.surf.random/r.surf.random.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,41 @@
+<h2>DESCRIPTION</h2>
+
+<b>r.surf.random</b> produces a raster map layer of uniform random deviates
+whose range can be expressed by the user. It is essentialy the same as
+<em>r.surf.gauss</em>, but uses a linear random number generator instead.
+It uses the random number generator drand48() or rand()<!-- cite? -->,
+depending on the user's platform.
+
+<p>
+<center>
+<img src="r_surf_random_hist.png" alt="r.surf.random map histogram"><br>
+<i>Histogram of map generated with r.surf.random</i>
+</center>
+
+<h2>SEE ALSO</h2>
+
+<em>
+<a href="r.surf.contour.html">r.surf.contour</a>,
+<a href="r.surf.fractal.html">r.surf.fractal</a>,
+<a href="r.surf.gauss.html">r.surf.gauss</a>,
+<a href="r.surf.idw.html">r.surf.idw</a>,
+<a href="r.surf.idw2.html">r.surf.idw2</a>,
+<a href="v.surf.rst.html">v.surf.rst</a>
+</em>
+
+<h2>AUTHOR</h2>
+
+Jo Wood<br>
+Midlands Regional Research Laboratory (ASSIST)<br>
+University of Leicester<br>
+<i>October 1991</i>
+<br>
+
+<!-- almost certainly no longer valid
+<address>jwo at le.ac.uk</address>
+
+<br><a href="http://www.geog.le.ac.uk/assist/index.html">ASSIST's home</a>
+-->
+
+<p>
+<i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.terraflow/description.html
===================================================================
--- grass/trunk/raster/r.terraflow/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.terraflow/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,249 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<p><em>r.terraflow</em> takes as input a raster digital elevation
-model (DEM) and computes the flow direction raster and the flow
-accumulation raster, as well as the flooded elevation raster,
-sink-watershed raster (partition into watersheds around sinks) and tci
-(topographic convergence index) raster.
-
-<p><em>r.terraflow</em> computes these rasters using well-known
-approaches, with the difference that its emphasis is on the
-computational complexity of the algorithms, rather than on modeling
-realistic flow. <em>r.terraflow</em> emerged from the necessity of
-having scalable software able to process efficiently very large
-terrains. It is based on theoretically optimal algorithms developed
-in the framework of I/O-efficient algorithms. <em>r.terraflow</em>
-was designed and optimized especially for massive grids and is able to
-process terrains which were impractical with similar functions
-existing in other GIS systems.
-
-<p>Flow directions are computed using either the MFD (Multiple Flow
-Direction) model or the SFD (Single Flow Direction, or D8) model,
-illustrated below. Both methods compute downslope flow directions by
-inspecting the 3-by-3 window around the current cell. The SFD method
-assigns a unique flow direction towards the steepest downslope
-neighbor. The MFD method assigns multiple flow directions towards all
-downslope neighbors.
-
-<p>
-<table width=80% align=center>
- <tr>
- <th><img src="rterraflow_dir2.png" alt="[SFD]" border=0></th>
- <th><img src="rterraflow_dir3.png" alt="[SFD]" border=0></th>
- </tr>
- <tr>
- <th>Flow direction to steepest<br> downslope neighbor (SFD).</th>
- <th>Flow direction to all<br> downslope neighbors (MFD).</th>
- </tr>
-</table>
-
-
-<p>The SFD and the MFD method cannot compute flow directions for
-cells which have the same height as all their neighbors (flat areas)
-or cells which do not have downslope neighbors (one-cell pits).
-<ul>
- <li>On plateaus (flat areas that spill out) <em>r.terraflow</em>
-routes flow so that globally the flow goes towards the spill cells of
-the plateaus.
-
- <li>On sinks (flat areas that do not spill out, including one-cell
-pits) <em>r.terraflow</em> assigns flow by flooding the terrain until
-all the sinks are filled and assigning flow directions on the filled
-terrain.
-
-</ul>
-
-<p>
-In order to flood the terrain, <em>r.terraflow</em> identifies all
-sinks and partitions the terrain into sink-watersheds (a
-sink-watershed contains all the cells that flow into that sink),
-builds a graph representing the adjacency information of the
-sink-watersheds, and uses this sink-watershed graph to merge
-watersheds into each other along their lowest common boundary until
-all watersheds have a flow path outside the terrain. Flooding produces
-a sink-less terrain in which every cell has a downslope flow path
-leading outside the terrain and therefore every cell in the terrain
-can be assigned SFD/MFD flow directions as above.
-
-<p>
-Once flow directions are computed for every cell in the terrain,
-<em>r.terraflow</em> computes flow accumulation by routing water using
-the flow directions and keeping track of how much water flows through
-each cell.
-
-<p>
-If flow accumulation of a cell is larger than the value given by the
-<b>d8cut</b> option, then
-the flow of this cell is routed to its neighbors using the SFD (D8)
-model. This option affects only the flow accumulation raster and is
-meaningfull only for MFD flow (i.e. if the -s flag is not used); If
-this option is used for SFD flow it is ignored. The default value of
-<b>d8cut</b> is <i>infinity</i>.
-
-<p>
-<em>r.terraflow</em> also computes the tci raster (topographic convergence
-index, defined as the logarithm of the ratio of flow accumulation and
-local slope).
-
-<p>
-For more details on the algorithms see [1,2,3] below.
-
-
-
-<h2>NOTES</h2>
-
-One of the techniques used by <em>r.terraflow</em> is the
-space-time trade-off. In particular, in order to avoid searches, which
-are I/O-expensive, <em>r.terraflow</em> computes and works with an
-augmented elevation raster in which each cell stores relevant
-information about its 8 neighbors, in total up to 80B per cell. As a
-result <em>r.terraflow</em> works with intermediate temporary files
-that may be up to 80N bytes, where N is the number of cells (rows x
-columns) in the elevation raster (more precisely, 80K bytes, where K
-is the number of valid (not no-data) cells in the input elevation
-raster).
-<p>
-All these intermediate temporary files are stored in the path specified
-by the <b>STREAM_DIR</b> option. Note: <b>STREAM_DIR</b> must contain
-enough free disk space in order to store up to 2 x 80N bytes.
-
-<p>
-The <b>memory</b> option can be used to set the maximum amount of main
-memory (RAM) the module will use during processing. In practice its
-<i>value</i> should be an underestimate of the amount of available
-(free) main memory on the machine. <em>r.terraflow</em> will use at
-all times at most this much memory, and the virtual memory system
-(swap space) will never be used. The default value is 300 MB.
-
-<p>
-The internal type used by <em>r.terraflow</em> to store elevations
-can be defined at compile-time. By default, <em>r.terraflow</em> is
-compiled to store elevations internally as floats.
-A version which is compiled to store elevations internally as
-shorts is available as <em>r.terraflow.short</em>. Other versions can
-be created by the user if needed.
-
-<p>
-<em>r.terraflow.short</em> uses less space (up to 60B per cell, up
-to 60N intermediate file) and therefore is more space and time
-efficient. <em>r.terraflow</em> is intended for use with floating
-point raster data (FCELL), and <em>r.terraflow.short</em> with integer
-raster data (CELL) in which the maximum elevation does not exceed the
-value of a short SHRT_MAX=32767 (this is not a constraint for any
-terrain data of the Earth, if elevation is stored in meters).
-
-<p>
-Both <em>r.terraflow</em> and <em>r.terraflow.short</em> work with
-input elevation rasters which can be either integer, floating point or
-double (CELL, FCELL, DCELL). If the input raster contains a value that
-exceeds the allowed internal range (short for
-<em>r.terraflow.short</em>, float for <em>r.terraflow</em>), the
-program exits with a warning message. Otherwise, if all values in the
-input elevation raster are in range, they will be converted
-(truncated) to the internal elevation type (short for
-<em>r.terraflow.short</em>, float for <em>r.terraflow</em>). In this
-case precision may be lost and artificial flat areas may be created.
-
-<p>
-For instance, if <em>r.terraflow.short</em> is used with floating
-point raster data (FCELL or DCELL), the values of the elevation will
-be truncated as shorts. This may create artificial flat areas, and the
-outpus of <em>r.terraflow.short</em> may be less realistic than those
-of <em>r.terraflow</em> on floating point raster data.
-
-The outputs of <em>r.terraflow.short</em> and <em>r.terraflow</em> are
-identical for integer raster data (CELL maps).
-
-<p>
-The <b>stats</b> option defines the name of the file that contains the
-statistics (stats) of the run. The default name is <tt>stats.out</tt>
-(in the current directory).
-
-
-<h2>EXAMPLES</h2>
-
-<div class="code"><pre>
- r.terraflow elev=spearfish filled=spearfish-filled \
- dir=spearfish-mfdir swatershed=spearfish-watershed \
- accumulation=spearfish-accu tci=spearfish-tci
-</pre></div>
-
-<div class="code"><pre>
- r.terraflow elev=spearfish filled=spearfish-filled \
- dir=spearfish-mfdir swatershed=spearfish-watershed \
- accumulation=spearfish-accu tci=spearfish-tci d8cut=500 memory=800 \
- STREAM-DIR=/var/tmp/ stats=spearfish-stats.txt
-</pre></div>
-
-
-
-<h2>SEE ALSO</h2>
-<ul>
- <li>The <a
-href="http://www.cs.duke.edu/geo*/terraflow/">TerraFlow</a> project at Duke University
-
- <li><a href=r.flow.html>r.flow</a>,
- <a href="r.basins.fill.html">r.basins.fill</a>,
- <a href="r.drain.html">r.drain</a>,
- <a href="r.topidx.html">r.topidx</a>,
- <a href="r.topmodel.html">r.topmodel</a>,
- <a href="r.water.outlet.html">r.water.outlet</a>,
- <a href="r.watershed.html">r.watershed</a>
-</ul>
-
-
-
-<h2>AUTHORS</h2>
-
-<dl>
- <dt>Original version of program: The <a
- href="http://www.cs.duke.edu/geo*/terraflow/">TerraFlow</a> project,
- 1999, Duke University.
- <dd><a href="http://www.cs.duke.edu/~large/">Lars Arge</a>,
- <a href="http://www.cs.duke.edu/~chase/">Jeff Chase</a>,
- <a href="http://www.env.duke.edu/faculty/bios/halpin.html">Pat Halpin</a>,
- <a href="http://www.cs.duke.edu/~laura/">Laura Toma</a>,
- <a href="http://www.env.duke.edu/faculty/bios/urban.html">Dean Urban</a>,
- <a href="http://www.cs.duke.edu/~jsv/">Jeff Vitter</a>,
- <a href="http://www.cs.duke.edu/~rajiv/">Rajiv Wickremesinghe</a>.
-
- <dt>Porting for GRASS, 2002:
- <dd> <a href="http://www.cs.duke.edu/~large/">Lars Arge</a>,
- <a href="http://skagit.meas.ncsu.edu/~helena/index.html">Helena Mitasova,</a>
- <a href="http://www.cs.duke.edu/~laura/">Laura Toma</a>.
-
- <dt>Contact: <a href="mailto:laura at cs.duke.edu"> Laura Toma</a></dt>
-</dl>
-
-
-<h2>REFERENCES</h2>
-
-<ol>
- <li><A NAME="arge:drainage"
- HREF="http://www.cs.duke.edu/geo*/terraflow/papers/alenex00_drainage.ps.gz">
- I/O-efficient algorithms for problems on grid-based
- terrains</a>. Lars Arge, Laura Toma, and Jeffrey S. Vitter. In
- <em>Proc. Workshop on Algorithm Engineering and Experimentation</em>,
- 2000. To appear in <em>Journal of Experimental Algorithms</em>.
-
- <li><A NAME="terraflow:acmgis01"
- HREF="http://www.cs.duke.edu/geo*/terraflow/papers/acmgis01_terraflow.pdf">
- Flow computation on massive grids</a>.
- Lars Arge, Jeffrey S. Chase, Patrick N. Halpin, Laura Toma,
- Jeffrey S. Vitter, Dean Urban and Rajiv Wickremesinghe. In
- <em>Proc. ACM Symposium on Advances in Geographic Information
- Systems</em>, 2001.
-
- <li><A NAME="terraflow:geoinformatica"
- HREF="http://www.cs.duke.edu/geo*/terraflow/papers/journal_terraflow.pdf">
- Flow computation on massive grid terrains</a>.
- Lars Arge, Jeffrey S. Chase, Patrick N. Halpin, Laura Toma,
- Jeffrey S. Vitter, Dean Urban and Rajiv Wickremesinghe.
- To appear in <em>GeoInformatica, International Journal on
- Advances of Computer Science for Geographic Information
- Systems</em>.
-
-</ol>
-
-<p>
-<i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.terraflow/r.terraflow.html (from rev 32770, grass/trunk/raster/r.terraflow/description.html)
===================================================================
--- grass/trunk/raster/r.terraflow/r.terraflow.html (rev 0)
+++ grass/trunk/raster/r.terraflow/r.terraflow.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,249 @@
+<h2>DESCRIPTION</h2>
+
+<p><em>r.terraflow</em> takes as input a raster digital elevation
+model (DEM) and computes the flow direction raster and the flow
+accumulation raster, as well as the flooded elevation raster,
+sink-watershed raster (partition into watersheds around sinks) and tci
+(topographic convergence index) raster.
+
+<p><em>r.terraflow</em> computes these rasters using well-known
+approaches, with the difference that its emphasis is on the
+computational complexity of the algorithms, rather than on modeling
+realistic flow. <em>r.terraflow</em> emerged from the necessity of
+having scalable software able to process efficiently very large
+terrains. It is based on theoretically optimal algorithms developed
+in the framework of I/O-efficient algorithms. <em>r.terraflow</em>
+was designed and optimized especially for massive grids and is able to
+process terrains which were impractical with similar functions
+existing in other GIS systems.
+
+<p>Flow directions are computed using either the MFD (Multiple Flow
+Direction) model or the SFD (Single Flow Direction, or D8) model,
+illustrated below. Both methods compute downslope flow directions by
+inspecting the 3-by-3 window around the current cell. The SFD method
+assigns a unique flow direction towards the steepest downslope
+neighbor. The MFD method assigns multiple flow directions towards all
+downslope neighbors.
+
+<p>
+<table width=80% align=center>
+ <tr>
+ <th><img src="rterraflow_dir2.png" alt="[SFD]" border=0></th>
+ <th><img src="rterraflow_dir3.png" alt="[SFD]" border=0></th>
+ </tr>
+ <tr>
+ <th>Flow direction to steepest<br> downslope neighbor (SFD).</th>
+ <th>Flow direction to all<br> downslope neighbors (MFD).</th>
+ </tr>
+</table>
+
+
+<p>The SFD and the MFD method cannot compute flow directions for
+cells which have the same height as all their neighbors (flat areas)
+or cells which do not have downslope neighbors (one-cell pits).
+<ul>
+ <li>On plateaus (flat areas that spill out) <em>r.terraflow</em>
+routes flow so that globally the flow goes towards the spill cells of
+the plateaus.
+
+ <li>On sinks (flat areas that do not spill out, including one-cell
+pits) <em>r.terraflow</em> assigns flow by flooding the terrain until
+all the sinks are filled and assigning flow directions on the filled
+terrain.
+
+</ul>
+
+<p>
+In order to flood the terrain, <em>r.terraflow</em> identifies all
+sinks and partitions the terrain into sink-watersheds (a
+sink-watershed contains all the cells that flow into that sink),
+builds a graph representing the adjacency information of the
+sink-watersheds, and uses this sink-watershed graph to merge
+watersheds into each other along their lowest common boundary until
+all watersheds have a flow path outside the terrain. Flooding produces
+a sink-less terrain in which every cell has a downslope flow path
+leading outside the terrain and therefore every cell in the terrain
+can be assigned SFD/MFD flow directions as above.
+
+<p>
+Once flow directions are computed for every cell in the terrain,
+<em>r.terraflow</em> computes flow accumulation by routing water using
+the flow directions and keeping track of how much water flows through
+each cell.
+
+<p>
+If flow accumulation of a cell is larger than the value given by the
+<b>d8cut</b> option, then
+the flow of this cell is routed to its neighbors using the SFD (D8)
+model. This option affects only the flow accumulation raster and is
+meaningfull only for MFD flow (i.e. if the -s flag is not used); If
+this option is used for SFD flow it is ignored. The default value of
+<b>d8cut</b> is <i>infinity</i>.
+
+<p>
+<em>r.terraflow</em> also computes the tci raster (topographic convergence
+index, defined as the logarithm of the ratio of flow accumulation and
+local slope).
+
+<p>
+For more details on the algorithms see [1,2,3] below.
+
+
+
+<h2>NOTES</h2>
+
+One of the techniques used by <em>r.terraflow</em> is the
+space-time trade-off. In particular, in order to avoid searches, which
+are I/O-expensive, <em>r.terraflow</em> computes and works with an
+augmented elevation raster in which each cell stores relevant
+information about its 8 neighbors, in total up to 80B per cell. As a
+result <em>r.terraflow</em> works with intermediate temporary files
+that may be up to 80N bytes, where N is the number of cells (rows x
+columns) in the elevation raster (more precisely, 80K bytes, where K
+is the number of valid (not no-data) cells in the input elevation
+raster).
+<p>
+All these intermediate temporary files are stored in the path specified
+by the <b>STREAM_DIR</b> option. Note: <b>STREAM_DIR</b> must contain
+enough free disk space in order to store up to 2 x 80N bytes.
+
+<p>
+The <b>memory</b> option can be used to set the maximum amount of main
+memory (RAM) the module will use during processing. In practice its
+<i>value</i> should be an underestimate of the amount of available
+(free) main memory on the machine. <em>r.terraflow</em> will use at
+all times at most this much memory, and the virtual memory system
+(swap space) will never be used. The default value is 300 MB.
+
+<p>
+The internal type used by <em>r.terraflow</em> to store elevations
+can be defined at compile-time. By default, <em>r.terraflow</em> is
+compiled to store elevations internally as floats.
+A version which is compiled to store elevations internally as
+shorts is available as <em>r.terraflow.short</em>. Other versions can
+be created by the user if needed.
+
+<p>
+<em>r.terraflow.short</em> uses less space (up to 60B per cell, up
+to 60N intermediate file) and therefore is more space and time
+efficient. <em>r.terraflow</em> is intended for use with floating
+point raster data (FCELL), and <em>r.terraflow.short</em> with integer
+raster data (CELL) in which the maximum elevation does not exceed the
+value of a short SHRT_MAX=32767 (this is not a constraint for any
+terrain data of the Earth, if elevation is stored in meters).
+
+<p>
+Both <em>r.terraflow</em> and <em>r.terraflow.short</em> work with
+input elevation rasters which can be either integer, floating point or
+double (CELL, FCELL, DCELL). If the input raster contains a value that
+exceeds the allowed internal range (short for
+<em>r.terraflow.short</em>, float for <em>r.terraflow</em>), the
+program exits with a warning message. Otherwise, if all values in the
+input elevation raster are in range, they will be converted
+(truncated) to the internal elevation type (short for
+<em>r.terraflow.short</em>, float for <em>r.terraflow</em>). In this
+case precision may be lost and artificial flat areas may be created.
+
+<p>
+For instance, if <em>r.terraflow.short</em> is used with floating
+point raster data (FCELL or DCELL), the values of the elevation will
+be truncated as shorts. This may create artificial flat areas, and the
+outpus of <em>r.terraflow.short</em> may be less realistic than those
+of <em>r.terraflow</em> on floating point raster data.
+
+The outputs of <em>r.terraflow.short</em> and <em>r.terraflow</em> are
+identical for integer raster data (CELL maps).
+
+<p>
+The <b>stats</b> option defines the name of the file that contains the
+statistics (stats) of the run. The default name is <tt>stats.out</tt>
+(in the current directory).
+
+
+<h2>EXAMPLES</h2>
+
+<div class="code"><pre>
+ r.terraflow elev=spearfish filled=spearfish-filled \
+ dir=spearfish-mfdir swatershed=spearfish-watershed \
+ accumulation=spearfish-accu tci=spearfish-tci
+</pre></div>
+
+<div class="code"><pre>
+ r.terraflow elev=spearfish filled=spearfish-filled \
+ dir=spearfish-mfdir swatershed=spearfish-watershed \
+ accumulation=spearfish-accu tci=spearfish-tci d8cut=500 memory=800 \
+ STREAM-DIR=/var/tmp/ stats=spearfish-stats.txt
+</pre></div>
+
+
+
+<h2>SEE ALSO</h2>
+<ul>
+ <li>The <a
+href="http://www.cs.duke.edu/geo*/terraflow/">TerraFlow</a> project at Duke University
+
+ <li><a href=r.flow.html>r.flow</a>,
+ <a href="r.basins.fill.html">r.basins.fill</a>,
+ <a href="r.drain.html">r.drain</a>,
+ <a href="r.topidx.html">r.topidx</a>,
+ <a href="r.topmodel.html">r.topmodel</a>,
+ <a href="r.water.outlet.html">r.water.outlet</a>,
+ <a href="r.watershed.html">r.watershed</a>
+</ul>
+
+
+
+<h2>AUTHORS</h2>
+
+<dl>
+ <dt>Original version of program: The <a
+ href="http://www.cs.duke.edu/geo*/terraflow/">TerraFlow</a> project,
+ 1999, Duke University.
+ <dd><a href="http://www.cs.duke.edu/~large/">Lars Arge</a>,
+ <a href="http://www.cs.duke.edu/~chase/">Jeff Chase</a>,
+ <a href="http://www.env.duke.edu/faculty/bios/halpin.html">Pat Halpin</a>,
+ <a href="http://www.cs.duke.edu/~laura/">Laura Toma</a>,
+ <a href="http://www.env.duke.edu/faculty/bios/urban.html">Dean Urban</a>,
+ <a href="http://www.cs.duke.edu/~jsv/">Jeff Vitter</a>,
+ <a href="http://www.cs.duke.edu/~rajiv/">Rajiv Wickremesinghe</a>.
+
+ <dt>Porting for GRASS, 2002:
+ <dd> <a href="http://www.cs.duke.edu/~large/">Lars Arge</a>,
+ <a href="http://skagit.meas.ncsu.edu/~helena/index.html">Helena Mitasova,</a>
+ <a href="http://www.cs.duke.edu/~laura/">Laura Toma</a>.
+
+ <dt>Contact: <a href="mailto:laura at cs.duke.edu"> Laura Toma</a></dt>
+</dl>
+
+
+<h2>REFERENCES</h2>
+
+<ol>
+ <li><A NAME="arge:drainage"
+ HREF="http://www.cs.duke.edu/geo*/terraflow/papers/alenex00_drainage.ps.gz">
+ I/O-efficient algorithms for problems on grid-based
+ terrains</a>. Lars Arge, Laura Toma, and Jeffrey S. Vitter. In
+ <em>Proc. Workshop on Algorithm Engineering and Experimentation</em>,
+ 2000. To appear in <em>Journal of Experimental Algorithms</em>.
+
+ <li><A NAME="terraflow:acmgis01"
+ HREF="http://www.cs.duke.edu/geo*/terraflow/papers/acmgis01_terraflow.pdf">
+ Flow computation on massive grids</a>.
+ Lars Arge, Jeffrey S. Chase, Patrick N. Halpin, Laura Toma,
+ Jeffrey S. Vitter, Dean Urban and Rajiv Wickremesinghe. In
+ <em>Proc. ACM Symposium on Advances in Geographic Information
+ Systems</em>, 2001.
+
+ <li><A NAME="terraflow:geoinformatica"
+ HREF="http://www.cs.duke.edu/geo*/terraflow/papers/journal_terraflow.pdf">
+ Flow computation on massive grid terrains</a>.
+ Lars Arge, Jeffrey S. Chase, Patrick N. Halpin, Laura Toma,
+ Jeffrey S. Vitter, Dean Urban and Rajiv Wickremesinghe.
+ To appear in <em>GeoInformatica, International Journal on
+ Advances of Computer Science for Geographic Information
+ Systems</em>.
+
+</ol>
+
+<p>
+<i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.texture/description.html
===================================================================
--- grass/trunk/raster/r.texture/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.texture/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,98 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>r.texture</em> - Creates map raster with textural features for
-user-specified raster map layer. The module calculates textural features
-based on spatial dependence matrices at 0, 45, 90, and 135
-degrees for a <em>distance</em> (default = 1).
-<p>
-<!--
-<em>r.texture</em> uses the algorithms of <a href="i.texture.html">i.texture</a>.
--->
-<em>r.texture</em> reads a GRASS raster map as input and calculates textural
-features based on spatial
-dependence matrices for north-south, east-west, northwest, and southwest
-directions using a side by side neighborhood (i.e., a distance of 1). Be
-sure to carefully set your resolution (using
-<a href="g.region.html">g.region</a>) before running this program, or else your
-computer could run out of memory. Also, make sure that your raster map has
-no more than 255 categories. The output consists into four images for each
-textural feature, one for every direction.</p>
-<p>
-A commonly used texture model is based on the so-called grey level co-occurrence
-matrix. This matrix is a two-dimensional histogram of grey levels
-for a pair of pixels which are separated by a fixed spatial relationship.
-The matrix approximates the joint probability distribution of a pair of pixels.
-Several texture measures are directly computed from the grey level co-occurrence
-matrix.
-<p>
-The following are brief explanations of texture measures:
-<p>
-<ul>
-<li> Angular Second Moment:
-This is a measure of local homogeneity and the opposite of Entropy.
-It is high when the local window a few pixels with high values; low,
-when the pixels are almost equal.
-
-<li> Contrast:
-This measure considers the amount of local variation and is the opposite of Homogeneity
-(when high pixel values concentrate along the diagonal).
-
-<li> Correlation:
-This measure analyses the linear dependency of grey levels of neighboring
-pixels. Typically high, when the scale of local texture is larger than the
-<em>distance</em>.
-
-<li> Entropy:
-This measure is high when the values of the local window have similar values.
-It is low when the values are close to either 0 or 1 (i.e. when the
-pixels in the local window are uniform).
-</ul>
-
-<h2>NOTES</h2>
-Algorithm taken from:<br>
-
-Haralick, R.M., K. Shanmugam, and I. Dinstein. 1973. Textural features for
- image classification. <em>IEEE Transactions on Systems, Man, and
- Cybernetics</em>, SMC-3(6):610-621.
-
-<p>The code was taken by permission from <em>pgmtexture</em>, part of
- PBMPLUS (Copyright 1991, Jef Poskanser and Texas Agricultural Experiment
- Station, employer for hire of James Darrell McCauley). <br>
- Man page of <a href="http://netpbm.sourceforge.net/doc/pgmtexture.html">pgmtexture</a></p>
-
-<h2>BUGS</h2>
-- The program can run incredibly slow for large raster maps.
-<p>
-- The method for finding the maximal correlation coefficient, which
- requires finding the second largest eigenvalue of a matrix Q, does not
- always converge.
-
-<h2>REFERENCES</h2>
-<b>Haralick, R.M., K. Shanmugam, and I. Dinstein</b> (1973). Textural features for
- image classification. <em>IEEE Transactions on Systems, Man, and
- Cybernetics</em>, SMC-3(6):610-621.
-<p>
-<b>Bouman C. A., Shapiro M.</b>,(March
- 1994).A Multiscale Random Field Model for Bayesian Image
- Segmentation, IEEE Trans. on Image Processing, vol. 3, no.2.
-
-<p>
-<b>Haralick R.</b>, (May 1979). <i>Statistical and structural approaches to texture</i>,
- Proceedings of the IEEE, vol. 67, No.5, pp. 786-804</p>
-
-
-<h2>SEE ALSO</h2>
-
-<em><a href="i.smap.html">i.smap</a></em>,
-<em><a href="i.gensigset.html">i.gensigset</a></em>,
-<em><a href="i.pca.html">i.pca</a></em>,
-<em><a href="r.digit.html">r.digit</a></em>,
-<em><a href="i.group.html">i.group</a></em>
-<!-- <em><a href="i.texture.html">i.texture</a></em> -->
-
-<h2>AUTHOR</h2>
-<a href="mailto:antoniol at ieee.org">G. Antoniol</a> - RCOST (Research Centre on Software Technology - Viale Traiano - 82100 Benevento)<br>
-<a href="mailto:basco at unisannio.it">C. Basco</a> - RCOST (Research Centre on Software Technology - Viale Traiano - 82100 Benevento)<br>
-<a href="mailto:ceccarelli at unisannio.it">M. Ceccarelli</a> - Facolta di Scienze, Universita del Sannio, Benevento
-
-<p><i>Last changed: $Date$</i></p>
Copied: grass/trunk/raster/r.texture/r.texture.html (from rev 32770, grass/trunk/raster/r.texture/description.html)
===================================================================
--- grass/trunk/raster/r.texture/r.texture.html (rev 0)
+++ grass/trunk/raster/r.texture/r.texture.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,98 @@
+<h2>DESCRIPTION</h2>
+
+<em>r.texture</em> - Creates map raster with textural features for
+user-specified raster map layer. The module calculates textural features
+based on spatial dependence matrices at 0, 45, 90, and 135
+degrees for a <em>distance</em> (default = 1).
+<p>
+<!--
+<em>r.texture</em> uses the algorithms of <a href="i.texture.html">i.texture</a>.
+-->
+<em>r.texture</em> reads a GRASS raster map as input and calculates textural
+features based on spatial
+dependence matrices for north-south, east-west, northwest, and southwest
+directions using a side by side neighborhood (i.e., a distance of 1). Be
+sure to carefully set your resolution (using
+<a href="g.region.html">g.region</a>) before running this program, or else your
+computer could run out of memory. Also, make sure that your raster map has
+no more than 255 categories. The output consists into four images for each
+textural feature, one for every direction.</p>
+<p>
+A commonly used texture model is based on the so-called grey level co-occurrence
+matrix. This matrix is a two-dimensional histogram of grey levels
+for a pair of pixels which are separated by a fixed spatial relationship.
+The matrix approximates the joint probability distribution of a pair of pixels.
+Several texture measures are directly computed from the grey level co-occurrence
+matrix.
+<p>
+The following are brief explanations of texture measures:
+<p>
+<ul>
+<li> Angular Second Moment:
+This is a measure of local homogeneity and the opposite of Entropy.
+It is high when the local window a few pixels with high values; low,
+when the pixels are almost equal.
+
+<li> Contrast:
+This measure considers the amount of local variation and is the opposite of Homogeneity
+(when high pixel values concentrate along the diagonal).
+
+<li> Correlation:
+This measure analyses the linear dependency of grey levels of neighboring
+pixels. Typically high, when the scale of local texture is larger than the
+<em>distance</em>.
+
+<li> Entropy:
+This measure is high when the values of the local window have similar values.
+It is low when the values are close to either 0 or 1 (i.e. when the
+pixels in the local window are uniform).
+</ul>
+
+<h2>NOTES</h2>
+Algorithm taken from:<br>
+
+Haralick, R.M., K. Shanmugam, and I. Dinstein. 1973. Textural features for
+ image classification. <em>IEEE Transactions on Systems, Man, and
+ Cybernetics</em>, SMC-3(6):610-621.
+
+<p>The code was taken by permission from <em>pgmtexture</em>, part of
+ PBMPLUS (Copyright 1991, Jef Poskanser and Texas Agricultural Experiment
+ Station, employer for hire of James Darrell McCauley). <br>
+ Man page of <a href="http://netpbm.sourceforge.net/doc/pgmtexture.html">pgmtexture</a></p>
+
+<h2>BUGS</h2>
+- The program can run incredibly slow for large raster maps.
+<p>
+- The method for finding the maximal correlation coefficient, which
+ requires finding the second largest eigenvalue of a matrix Q, does not
+ always converge.
+
+<h2>REFERENCES</h2>
+<b>Haralick, R.M., K. Shanmugam, and I. Dinstein</b> (1973). Textural features for
+ image classification. <em>IEEE Transactions on Systems, Man, and
+ Cybernetics</em>, SMC-3(6):610-621.
+<p>
+<b>Bouman C. A., Shapiro M.</b>,(March
+ 1994).A Multiscale Random Field Model for Bayesian Image
+ Segmentation, IEEE Trans. on Image Processing, vol. 3, no.2.
+
+<p>
+<b>Haralick R.</b>, (May 1979). <i>Statistical and structural approaches to texture</i>,
+ Proceedings of the IEEE, vol. 67, No.5, pp. 786-804</p>
+
+
+<h2>SEE ALSO</h2>
+
+<em><a href="i.smap.html">i.smap</a></em>,
+<em><a href="i.gensigset.html">i.gensigset</a></em>,
+<em><a href="i.pca.html">i.pca</a></em>,
+<em><a href="r.digit.html">r.digit</a></em>,
+<em><a href="i.group.html">i.group</a></em>
+<!-- <em><a href="i.texture.html">i.texture</a></em> -->
+
+<h2>AUTHOR</h2>
+<a href="mailto:antoniol at ieee.org">G. Antoniol</a> - RCOST (Research Centre on Software Technology - Viale Traiano - 82100 Benevento)<br>
+<a href="mailto:basco at unisannio.it">C. Basco</a> - RCOST (Research Centre on Software Technology - Viale Traiano - 82100 Benevento)<br>
+<a href="mailto:ceccarelli at unisannio.it">M. Ceccarelli</a> - Facolta di Scienze, Universita del Sannio, Benevento
+
+<p><i>Last changed: $Date$</i></p>
Deleted: grass/trunk/raster/r.thin/description.html
===================================================================
--- grass/trunk/raster/r.thin/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.thin/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,84 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>r.thin</em> scans the named <em>input</em> raster map
-layer and thins non-zero cells that denote linear features
-into linear features having a single cell width.
-
-<p>
-
-<em>r.thin</em> will thin only the non-zero cells of the
-named <em>input</em> raster map layer within the current
-geographic region settings. The cell width of the thinned
-<em>output</em> raster map layer will be equal to the cell
-resolution of the currently set geographic region. All of
-the thinned linear features will have the width of a single
-cell.
-
-<p>
-
-<em>r.thin</em> will create a new <em>output</em> raster
-data file containing the thinned linear features.
-<em>r.thin</em> assumes that linear features are encoded
-with positive values on a background of 0's in the
-<em>input</em> raster data file.
-
-<h2>NOTE</h2>
-
-<em>r.thin</em> only creates raster map layers. You will need to run
-<em><a href="r.to.vect.html">r.to.vect</a></em>
-on the resultant raster map to create a vector
-(<em><a href="v.digit.html">v.digit</a></em>) map layer.
-
-<p>
-<em>r.thin</em> may create small spurs or "dangling lines"
-during the thinning process. These spurs may be removed
-(after creating a vector map layer) by
-<em><a href="v.clean.html">v.clean</a></em>.
-
-<p>
-
-<em>r.thin</em> creates a 0/1 output map.
-
-<h2>NOTE</h2>
-
-This code implements the thinning algorithm described in
-"Analysis of Thinning Algorithms Using Mathematical
-Morphology" by Ben-Kwei Jang and Ronlad T. Chin in
-<em>Transactions on Pattern Analysis and Machine
-Intelligence</em>, vol. 12, No. 6, June 1990. The
-definition Jang and Chin give of the thinning process is
-"successive removal of outer layers of pixels from an
-object while retaining any pixels whose removal would alter
-the connectivity or shorten the legs of the sceleton."
-
-
-<p>
-
-The sceleton is finally thinned when the thinning process
-converges; i.e., "no further pixels can be removed without
-altering the connectivity or shortening the sceleton legs"
-(p. 541). The authors prove that the thinning process
-described always converges and produces one-pixel thick
-sceletons. The number of iterations depends on the
-original thickness of the object. Each iteration peels off
-the outside pixels from the object. Therefore, if the
-object is <= n pixels thick, the algorithm should
-converge in <= iterations.
-
-<h2>SEE ALSO</h2>
-
-<em><a href="g.region.html">g.region</a></em>,
-<em><a href="r.to.vect.html">r.to.vect</a></em>,
-<em><a href="v.clean.html">v.clean</a></em>,
-<em><a href="v.digit.html">v.digit</a></em>,
-<em><a href="v.build.html">v.build</a></em>
-
-<h2>AUTHOR</h2>
-
-Olga Waupotitsch, U.S.Army Construction Engineering Research Laboratory
-
-<p>
-The code for finding the bounding box as well as input/output code
-was written by Mike Baba (DBA Systems, 1990) and Jean Ezell (USACERL, 1988).
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.thin/r.thin.html (from rev 32770, grass/trunk/raster/r.thin/description.html)
===================================================================
--- grass/trunk/raster/r.thin/r.thin.html (rev 0)
+++ grass/trunk/raster/r.thin/r.thin.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,84 @@
+<h2>DESCRIPTION</h2>
+
+<em>r.thin</em> scans the named <em>input</em> raster map
+layer and thins non-zero cells that denote linear features
+into linear features having a single cell width.
+
+<p>
+
+<em>r.thin</em> will thin only the non-zero cells of the
+named <em>input</em> raster map layer within the current
+geographic region settings. The cell width of the thinned
+<em>output</em> raster map layer will be equal to the cell
+resolution of the currently set geographic region. All of
+the thinned linear features will have the width of a single
+cell.
+
+<p>
+
+<em>r.thin</em> will create a new <em>output</em> raster
+data file containing the thinned linear features.
+<em>r.thin</em> assumes that linear features are encoded
+with positive values on a background of 0's in the
+<em>input</em> raster data file.
+
+<h2>NOTE</h2>
+
+<em>r.thin</em> only creates raster map layers. You will need to run
+<em><a href="r.to.vect.html">r.to.vect</a></em>
+on the resultant raster map to create a vector
+(<em><a href="v.digit.html">v.digit</a></em>) map layer.
+
+<p>
+<em>r.thin</em> may create small spurs or "dangling lines"
+during the thinning process. These spurs may be removed
+(after creating a vector map layer) by
+<em><a href="v.clean.html">v.clean</a></em>.
+
+<p>
+
+<em>r.thin</em> creates a 0/1 output map.
+
+<h2>NOTE</h2>
+
+This code implements the thinning algorithm described in
+"Analysis of Thinning Algorithms Using Mathematical
+Morphology" by Ben-Kwei Jang and Ronlad T. Chin in
+<em>Transactions on Pattern Analysis and Machine
+Intelligence</em>, vol. 12, No. 6, June 1990. The
+definition Jang and Chin give of the thinning process is
+"successive removal of outer layers of pixels from an
+object while retaining any pixels whose removal would alter
+the connectivity or shorten the legs of the sceleton."
+
+
+<p>
+
+The sceleton is finally thinned when the thinning process
+converges; i.e., "no further pixels can be removed without
+altering the connectivity or shortening the sceleton legs"
+(p. 541). The authors prove that the thinning process
+described always converges and produces one-pixel thick
+sceletons. The number of iterations depends on the
+original thickness of the object. Each iteration peels off
+the outside pixels from the object. Therefore, if the
+object is <= n pixels thick, the algorithm should
+converge in <= iterations.
+
+<h2>SEE ALSO</h2>
+
+<em><a href="g.region.html">g.region</a></em>,
+<em><a href="r.to.vect.html">r.to.vect</a></em>,
+<em><a href="v.clean.html">v.clean</a></em>,
+<em><a href="v.digit.html">v.digit</a></em>,
+<em><a href="v.build.html">v.build</a></em>
+
+<h2>AUTHOR</h2>
+
+Olga Waupotitsch, U.S.Army Construction Engineering Research Laboratory
+
+<p>
+The code for finding the bounding box as well as input/output code
+was written by Mike Baba (DBA Systems, 1990) and Jean Ezell (USACERL, 1988).
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.timestamp/description.html
===================================================================
--- grass/trunk/raster/r.timestamp/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.timestamp/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,109 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-This command has 2 modes of operation. If no date argument is supplied, then
-the current timestamp for the raster map is printed. If a date argument is
-specified, then the timestamp for the raster map is set to the specified
-date(s). See EXAMPLES below.
-
-<h2>NOTES</h2>
-
-Strings containing spaces should be quoted. For specifying a range
-of time, the two timestamps should be separated by a forward slash.
-To remove the timestamp from a raster map, use <b>date=</b><em>none</em>.
-
-<h2>EXAMPLES</h2>
-
- <b>r.timestamp map=soils</b><br>
- Prints the timestamp for the "soils" raster map. If
- there is no timestamp for soils, nothing is printed. If
- there is a timestamp, one or two time strings are printed,
- depending on if the timestamp for the map consists of a
- single date or two dates (ie start and end dates).
-<p>
-<b> r.timestamp map=soils date='15 sep 1987'</b><br>
- Sets the timestamp for "soils" to the single date<br>
- "15 sep 1987"
-<p>
-<b> r.timestamp map=soils date='15 sep 1987/20 feb 1988'</b><br>
- Sets the timestamp for "soils" to have the start date<br>
- "15 sep 1987" and the end date "20 feb 1988"
-<p>
-<b> r.timestamp map=soils date=none</b><br>
- Removes the timestamp for the "soils" raster map
-
-
-<h2>TIMESTAMP FORMAT</h2>
- The timestamp values must use the format as described in the
- GRASS datetime library. The source tree for this library
- should have a description of the format. For convience, the
- formats as of Feb, 1996 are reproduced here:
-<p>
- There are two types of datetime values: absolute and
- relative. Absolute values specify exact dates and/or times.
- Relative values specify a span of time. Some examples will
- help clarify:
-<p>
-<b>Absolute</b><p>
- The general format for absolute values is:
-<p><tt>
- day month year [bc] hour:minute:seconds timezone
-<p>
- day is 1-31<br>
- month is jan,feb,...,dec<br>
- year is 4 digit year<br>
- [bc] if present, indicates dates is BC<br>
- hour is 0-23 (24 hour clock)<br>
- mintue is 0-59<br>
- second is 0-59.9999 (fractions of second allowed)<br>
- timezone is +hhmm or -hhmm (eg, -0600)<br>
-<p>
- parts can be missing
-<p>
- 1994 [bc]<br>
- Jan 1994 [bc]<br>
- 15 jan 1000 [bc]<br>
- 15 jan 1994 [bc] 10 [+0000]<br>
- 15 jan 1994 [bc] 10:00 [+0100]<br>
- 15 jan 1994 [bc] 10:00:23.34 [-0500]<br>
-<p>
-</tt>
-<b>Relative</b><p>
- There are two types of relative datetime values, year-
- month and day-second. The formats are:
-<p><tt>
- [-] # years # months<br>
- [-] # days # hours # minutes # seconds
-</tt><p>
- The words years, months, days, hours, minutes, seconds
- are literal words, and the # are the numeric values.<br>
- Examples:<p>
-<tt>
- 2 years<br>
- 5 months<br>
- 2 years 5 months<br>
- 100 days<br>
- 15 hours 25 minutes 35.34 seconds<br>
- 100 days 25 minutes<br>
- 1000 hours 35.34 seconds
-</tt><p>
- The following are <i>illegal</i> because it mixes year-month
- and day-second (because the number of days in a month
- or in a year vary):<p>
-<tt>
- 3 months 15 days<br>
- 3 years 10 days
-</tt>
-
-<h2>SEE ALSO</h2>
-
-<em><a HREF="v.timestamp.html">v.timestamp</a></em>
-
-<h2>BUGS</h2>
-Spaces in the timestamp value are required.
-
-<h2>AUTHOR</h2>
-
-Michael Shapiro, <br>
-U.S.Army Construction Engineering Research Laboratory
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.timestamp/r.timestamp.html (from rev 32770, grass/trunk/raster/r.timestamp/description.html)
===================================================================
--- grass/trunk/raster/r.timestamp/r.timestamp.html (rev 0)
+++ grass/trunk/raster/r.timestamp/r.timestamp.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,109 @@
+<h2>DESCRIPTION</h2>
+
+This command has 2 modes of operation. If no date argument is supplied, then
+the current timestamp for the raster map is printed. If a date argument is
+specified, then the timestamp for the raster map is set to the specified
+date(s). See EXAMPLES below.
+
+<h2>NOTES</h2>
+
+Strings containing spaces should be quoted. For specifying a range
+of time, the two timestamps should be separated by a forward slash.
+To remove the timestamp from a raster map, use <b>date=</b><em>none</em>.
+
+<h2>EXAMPLES</h2>
+
+ <b>r.timestamp map=soils</b><br>
+ Prints the timestamp for the "soils" raster map. If
+ there is no timestamp for soils, nothing is printed. If
+ there is a timestamp, one or two time strings are printed,
+ depending on if the timestamp for the map consists of a
+ single date or two dates (ie start and end dates).
+<p>
+<b> r.timestamp map=soils date='15 sep 1987'</b><br>
+ Sets the timestamp for "soils" to the single date<br>
+ "15 sep 1987"
+<p>
+<b> r.timestamp map=soils date='15 sep 1987/20 feb 1988'</b><br>
+ Sets the timestamp for "soils" to have the start date<br>
+ "15 sep 1987" and the end date "20 feb 1988"
+<p>
+<b> r.timestamp map=soils date=none</b><br>
+ Removes the timestamp for the "soils" raster map
+
+
+<h2>TIMESTAMP FORMAT</h2>
+ The timestamp values must use the format as described in the
+ GRASS datetime library. The source tree for this library
+ should have a description of the format. For convience, the
+ formats as of Feb, 1996 are reproduced here:
+<p>
+ There are two types of datetime values: absolute and
+ relative. Absolute values specify exact dates and/or times.
+ Relative values specify a span of time. Some examples will
+ help clarify:
+<p>
+<b>Absolute</b><p>
+ The general format for absolute values is:
+<p><tt>
+ day month year [bc] hour:minute:seconds timezone
+<p>
+ day is 1-31<br>
+ month is jan,feb,...,dec<br>
+ year is 4 digit year<br>
+ [bc] if present, indicates dates is BC<br>
+ hour is 0-23 (24 hour clock)<br>
+ mintue is 0-59<br>
+ second is 0-59.9999 (fractions of second allowed)<br>
+ timezone is +hhmm or -hhmm (eg, -0600)<br>
+<p>
+ parts can be missing
+<p>
+ 1994 [bc]<br>
+ Jan 1994 [bc]<br>
+ 15 jan 1000 [bc]<br>
+ 15 jan 1994 [bc] 10 [+0000]<br>
+ 15 jan 1994 [bc] 10:00 [+0100]<br>
+ 15 jan 1994 [bc] 10:00:23.34 [-0500]<br>
+<p>
+</tt>
+<b>Relative</b><p>
+ There are two types of relative datetime values, year-
+ month and day-second. The formats are:
+<p><tt>
+ [-] # years # months<br>
+ [-] # days # hours # minutes # seconds
+</tt><p>
+ The words years, months, days, hours, minutes, seconds
+ are literal words, and the # are the numeric values.<br>
+ Examples:<p>
+<tt>
+ 2 years<br>
+ 5 months<br>
+ 2 years 5 months<br>
+ 100 days<br>
+ 15 hours 25 minutes 35.34 seconds<br>
+ 100 days 25 minutes<br>
+ 1000 hours 35.34 seconds
+</tt><p>
+ The following are <i>illegal</i> because it mixes year-month
+ and day-second (because the number of days in a month
+ or in a year vary):<p>
+<tt>
+ 3 months 15 days<br>
+ 3 years 10 days
+</tt>
+
+<h2>SEE ALSO</h2>
+
+<em><a HREF="v.timestamp.html">v.timestamp</a></em>
+
+<h2>BUGS</h2>
+Spaces in the timestamp value are required.
+
+<h2>AUTHOR</h2>
+
+Michael Shapiro, <br>
+U.S.Army Construction Engineering Research Laboratory
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.to.rast3/description.html
===================================================================
--- grass/trunk/raster/r.to.rast3/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.to.rast3/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,56 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-Converts 2D raster map(s) into one G3D raster map.
-If the 2d and 3d region settings are different,
-the 2d resolution will be adjust to the 3d resolution.
-
-<center>
-<img src=r.to.rast3.png border=0><br>
-<table border=0 width=700>
-<tr><td><center>
-<i>How r.to.rast3 works</i>
-</center></td></tr>
-</table>
-</center>
-
-
-<h2>NOTES</h2>
-Every 2D raster map is copied as one slice to the G3D raster map. Slices
-are counted from bottom to the top, so the bottom slice has to be number 1.
-<br><br>
-If fewer 2D raster maps are provided than depths, the last give 2D map is
-used to fill up the G3D slices to the top.
-
-<h2>EXAMPLES</h2>
-
-<h3>EXAMPLE 1</h3>
-
-This example shows how to convert 6 maps into one 3d map with 6 layers.
-<br>
-
-<div class="code"><pre>
-# Mapset data in Location slovakia3d
-r.to.rast3 input=prec_1,prec_2,prec_3,prec_4,prec_5,prec_6 output=new_3dmap
-</pre></div>
-
-<h3>EXAMPLE 2</h3>
-This example shows how to convert 3 maps into one 3d map with 6 layers.
-<br>
-
-<div class="code"><pre>
-# Mapset data in Location slovakia3d
-r.to.rast3 input=prec_1,prec_2,prec_3 output=new_3dmap
-</pre></div>
-
-<h2>SEE ALSO</h2>
-
-<em>
-<a href="g.region.html">g.region</a>,
-<a href="r3.to.rast.html">r3.to.rast</a>,
-<a href="r.to.rast3elev.html">r.to.rast3elev</a>
-</em>
-
-<h2>AUTHOR</h2>
-Soeren Gebbert
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.to.rast3/r.to.rast3.html (from rev 32770, grass/trunk/raster/r.to.rast3/description.html)
===================================================================
--- grass/trunk/raster/r.to.rast3/r.to.rast3.html (rev 0)
+++ grass/trunk/raster/r.to.rast3/r.to.rast3.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,56 @@
+<h2>DESCRIPTION</h2>
+
+Converts 2D raster map(s) into one G3D raster map.
+If the 2d and 3d region settings are different,
+the 2d resolution will be adjust to the 3d resolution.
+
+<center>
+<img src=r.to.rast3.png border=0><br>
+<table border=0 width=700>
+<tr><td><center>
+<i>How r.to.rast3 works</i>
+</center></td></tr>
+</table>
+</center>
+
+
+<h2>NOTES</h2>
+Every 2D raster map is copied as one slice to the G3D raster map. Slices
+are counted from bottom to the top, so the bottom slice has to be number 1.
+<br><br>
+If fewer 2D raster maps are provided than depths, the last give 2D map is
+used to fill up the G3D slices to the top.
+
+<h2>EXAMPLES</h2>
+
+<h3>EXAMPLE 1</h3>
+
+This example shows how to convert 6 maps into one 3d map with 6 layers.
+<br>
+
+<div class="code"><pre>
+# Mapset data in Location slovakia3d
+r.to.rast3 input=prec_1,prec_2,prec_3,prec_4,prec_5,prec_6 output=new_3dmap
+</pre></div>
+
+<h3>EXAMPLE 2</h3>
+This example shows how to convert 3 maps into one 3d map with 6 layers.
+<br>
+
+<div class="code"><pre>
+# Mapset data in Location slovakia3d
+r.to.rast3 input=prec_1,prec_2,prec_3 output=new_3dmap
+</pre></div>
+
+<h2>SEE ALSO</h2>
+
+<em>
+<a href="g.region.html">g.region</a>,
+<a href="r3.to.rast.html">r3.to.rast</a>,
+<a href="r.to.rast3elev.html">r.to.rast3elev</a>
+</em>
+
+<h2>AUTHOR</h2>
+Soeren Gebbert
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.to.rast3elev/description.html
===================================================================
--- grass/trunk/raster/r.to.rast3elev/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.to.rast3elev/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,58 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-Creates a 3D volume map based on 2D elevation and value raster maps.
-If the 2d and 3d region settings are different,
-the 2d resolution will be adjust to the 3d resolution.
-
-<center>
-<img src=r.to.rast3elev.png border=0><br>
-<table border=0 width=700>
-<tr><td><center>
-<i>How r.to.rast3elev works</i>
-</center></td></tr>
-</table>
-</center>
-
-
-<h2>NOTES</h2>
-The hight of the 2D elevation maps will be used to verify the position
-within the 3D region. If the cell value of the elevation raster maps is located within the 3d region, the
-cell value of the appropriate 2D input raster maps will be written to the associated 3d cell.
-There are flags and options to fill the upper and lower 3D cells with a specific value, or the
-input raster maps values.
-
-<h2>Example</h2>
-Simple Spearfish example
-
-<div class="code"><pre>
-g.region -d
-g.region res=200 res3=200 t=5000 b=0 tbres=100
-
-# Write the values of raster map soils based on the elevation of elevation.10m
-# to the 3D map volev
-
-r.elev.to.rast3 in=soils elev=elevation.10m out=volev
-
-# Write the values of map soils based on the elevation of elevation.10m
-# to the 3D map volev_l and fill the lower cells with the soils map values
-
-r.elev.to.rast3 in=soils elev=elevation.10m out=volev_l -l
-
-# Write the values of map soils based on the elevation of elevation.10m
-# to the 3D map volev_u and fill the upper cells with the soils map values
-
-r.elev.to.rast3 in=soils elev=elevation.10m out=volev_u -u
-
-
-</pre></div>
-
-<h2>SEE ALSO</h2>
-
-<em><a href="r.to.rast3.html">r.to.rast3</a></em><br>
-<em><a href="r3.cross.rast.html">r3.cross.rast</a></em><br>
-<em><a href="g.region.html">g.region</a></em><br>
-
-<h2>AUTHOR</h2>
-Soeren Gebbert
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.to.rast3elev/r.to.rast3elev.html (from rev 32770, grass/trunk/raster/r.to.rast3elev/description.html)
===================================================================
--- grass/trunk/raster/r.to.rast3elev/r.to.rast3elev.html (rev 0)
+++ grass/trunk/raster/r.to.rast3elev/r.to.rast3elev.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,58 @@
+<h2>DESCRIPTION</h2>
+
+Creates a 3D volume map based on 2D elevation and value raster maps.
+If the 2d and 3d region settings are different,
+the 2d resolution will be adjust to the 3d resolution.
+
+<center>
+<img src=r.to.rast3elev.png border=0><br>
+<table border=0 width=700>
+<tr><td><center>
+<i>How r.to.rast3elev works</i>
+</center></td></tr>
+</table>
+</center>
+
+
+<h2>NOTES</h2>
+The hight of the 2D elevation maps will be used to verify the position
+within the 3D region. If the cell value of the elevation raster maps is located within the 3d region, the
+cell value of the appropriate 2D input raster maps will be written to the associated 3d cell.
+There are flags and options to fill the upper and lower 3D cells with a specific value, or the
+input raster maps values.
+
+<h2>Example</h2>
+Simple Spearfish example
+
+<div class="code"><pre>
+g.region -d
+g.region res=200 res3=200 t=5000 b=0 tbres=100
+
+# Write the values of raster map soils based on the elevation of elevation.10m
+# to the 3D map volev
+
+r.elev.to.rast3 in=soils elev=elevation.10m out=volev
+
+# Write the values of map soils based on the elevation of elevation.10m
+# to the 3D map volev_l and fill the lower cells with the soils map values
+
+r.elev.to.rast3 in=soils elev=elevation.10m out=volev_l -l
+
+# Write the values of map soils based on the elevation of elevation.10m
+# to the 3D map volev_u and fill the upper cells with the soils map values
+
+r.elev.to.rast3 in=soils elev=elevation.10m out=volev_u -u
+
+
+</pre></div>
+
+<h2>SEE ALSO</h2>
+
+<em><a href="r.to.rast3.html">r.to.rast3</a></em><br>
+<em><a href="r3.cross.rast.html">r3.cross.rast</a></em><br>
+<em><a href="g.region.html">g.region</a></em><br>
+
+<h2>AUTHOR</h2>
+Soeren Gebbert
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.to.vect/description.html
===================================================================
--- grass/trunk/raster/r.to.vect/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.to.vect/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,103 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>r.to.vect</em> scans the named <b>input</b> raster map
-layer, extracts points, lines or area edge features from it, converts data
-to GRASS vector format.
-
-<h3>Points</h3>
-
-The <em>r.to.vect</em> program extracts data from a GRASS raster map layer and stores output
-in a new GRASS <em>vector</em> file.
-
-<h3>Lines</h3>
-<em>r.to.vect</em> assumes that the <em>input</em> map has been thinned
-using <em><a href="r.thin.html">r.thin</a></em>.
-
-<p>
-
-<em>r.to.vect</em> extracts vectors (aka, "arcs") from a
-raster map. These arcs may represent linear features
-(like roads or streams), or may represent area edge
-features (like political boundaries, or soil mapping
-units).
-
-<p>
-
-<em><a href="r.thin.html">r.thin</a></em> and <em>r.to.vect</em>
-may create excessive nodes at every junction, and may create small spurs
-or "dangling lines" during the thinning and vectorization process.
-These excessive nodes and spurs may be removed using
-<em><a href="v.clean.html">v.clean</a></em>.
-
-
-<h3>Areas</h3>
-
-<em>r.to.vect</em> first traces the perimeter of each unique
-area in the raster map layer and creates vector data to
-represent it. The cell category values for the raster map
-layer will be used to create attribute information for the
-resultant vector area edge data.
-
-<p>
-
-A true vector tracing of the area edges might appear
-blocky, since the vectors outline the edges of raster data
-that are stored in rectangular cells. To produce a
-better-looking vector map, <em>r.to.vect</em> smoothes the
-corners of the vector data as they are being extracted. At
-each change in direction (i.e., each corner), the two
-midpoints of the corner cell (half the cell's height and
-width) are taken, and the line segment connecting them is
-used to outline this corner in the resultant vector map.
-(The cell's cornermost node is ignored.) Because vectors
-are smoothed by this program, the resulting vector map will
-not be "true" to the raster map from which it was created.
-The user should check the resolution of the geographic
-region (and the original data) to estimate the possible
-error introduced by smoothing.
-
-<p>
-
-<em>r.to.vect</em> extracts only area edges from the named raster input file.
-If the raster map contains other data (i.e., line edges, or point data) the
-output may be wrong.
-
-<h2>BUGS</h2>
-
-For feature=line the input raster map MUST be thinned by
-<em><a href="r.thin.html">r.thin</a></em>;
-if not, <em>r.to.vect</em> may crash.
-
-<h2>AUTHOR</h2>
-<b>Points</b><br>
-Bill Brown<br>
-<br>
-
-<b>Lines</b><br>
-Mike Baba<br>
-DBA Systems, Inc.<br>
-10560 Arrowhead Drive<br>
-Fairfax, Virginia 22030<br>
-<br>
-
-<b>Areas</b><br>
-<em>Original</em> version of <em>r.poly</em>:
-<br>
-Jean Ezell and Andrew Heekin,
-<br>
-U.S. Army Construction Engineering
-Research Laboratory
-
-<p>
-<em>Modified</em> program for smoothed lines:
-<br>
-David Satnik,
-Central Washington University
-<br>
-Updated 2001 by Andrea Aime, Modena, Italy<br>
-<br>
-
-<b>Update</b><br>
-Original r.to.sites, r.line and r.poly merged and updated to 5.7 by Radim Blazek
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.to.vect/r.to.vect.html (from rev 32770, grass/trunk/raster/r.to.vect/description.html)
===================================================================
--- grass/trunk/raster/r.to.vect/r.to.vect.html (rev 0)
+++ grass/trunk/raster/r.to.vect/r.to.vect.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,103 @@
+<h2>DESCRIPTION</h2>
+
+<em>r.to.vect</em> scans the named <b>input</b> raster map
+layer, extracts points, lines or area edge features from it, converts data
+to GRASS vector format.
+
+<h3>Points</h3>
+
+The <em>r.to.vect</em> program extracts data from a GRASS raster map layer and stores output
+in a new GRASS <em>vector</em> file.
+
+<h3>Lines</h3>
+<em>r.to.vect</em> assumes that the <em>input</em> map has been thinned
+using <em><a href="r.thin.html">r.thin</a></em>.
+
+<p>
+
+<em>r.to.vect</em> extracts vectors (aka, "arcs") from a
+raster map. These arcs may represent linear features
+(like roads or streams), or may represent area edge
+features (like political boundaries, or soil mapping
+units).
+
+<p>
+
+<em><a href="r.thin.html">r.thin</a></em> and <em>r.to.vect</em>
+may create excessive nodes at every junction, and may create small spurs
+or "dangling lines" during the thinning and vectorization process.
+These excessive nodes and spurs may be removed using
+<em><a href="v.clean.html">v.clean</a></em>.
+
+
+<h3>Areas</h3>
+
+<em>r.to.vect</em> first traces the perimeter of each unique
+area in the raster map layer and creates vector data to
+represent it. The cell category values for the raster map
+layer will be used to create attribute information for the
+resultant vector area edge data.
+
+<p>
+
+A true vector tracing of the area edges might appear
+blocky, since the vectors outline the edges of raster data
+that are stored in rectangular cells. To produce a
+better-looking vector map, <em>r.to.vect</em> smoothes the
+corners of the vector data as they are being extracted. At
+each change in direction (i.e., each corner), the two
+midpoints of the corner cell (half the cell's height and
+width) are taken, and the line segment connecting them is
+used to outline this corner in the resultant vector map.
+(The cell's cornermost node is ignored.) Because vectors
+are smoothed by this program, the resulting vector map will
+not be "true" to the raster map from which it was created.
+The user should check the resolution of the geographic
+region (and the original data) to estimate the possible
+error introduced by smoothing.
+
+<p>
+
+<em>r.to.vect</em> extracts only area edges from the named raster input file.
+If the raster map contains other data (i.e., line edges, or point data) the
+output may be wrong.
+
+<h2>BUGS</h2>
+
+For feature=line the input raster map MUST be thinned by
+<em><a href="r.thin.html">r.thin</a></em>;
+if not, <em>r.to.vect</em> may crash.
+
+<h2>AUTHOR</h2>
+<b>Points</b><br>
+Bill Brown<br>
+<br>
+
+<b>Lines</b><br>
+Mike Baba<br>
+DBA Systems, Inc.<br>
+10560 Arrowhead Drive<br>
+Fairfax, Virginia 22030<br>
+<br>
+
+<b>Areas</b><br>
+<em>Original</em> version of <em>r.poly</em>:
+<br>
+Jean Ezell and Andrew Heekin,
+<br>
+U.S. Army Construction Engineering
+Research Laboratory
+
+<p>
+<em>Modified</em> program for smoothed lines:
+<br>
+David Satnik,
+Central Washington University
+<br>
+Updated 2001 by Andrea Aime, Modena, Italy<br>
+<br>
+
+<b>Update</b><br>
+Original r.to.sites, r.line and r.poly merged and updated to 5.7 by Radim Blazek
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.topidx/description.html
===================================================================
--- grass/trunk/raster/r.topidx/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.topidx/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,42 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>r.topidx</em> creates topographic index (wetness index), ln(a/tan(beta)), map from
-elevation map
-<p>
-where
-<dl>
-<dd>a: the area of the hillslope per unit contour length that drains through any point,
-<p>
-<dd>tan(beta): the local surface topographic slope (delta vertical) / (delta horizontal).
-</dl>
-<p>
-Input maps may have NULL values. For example, if you have a MASK for
-a watershed (basin map from <em>r.water.outlet</em>), the
-following command will create a masked elevation map (belev):
-<div class="code"><pre>
-r.mapcalc "belev = if(isnull(basin), basin, elev)"
-</pre></div>
-<p>
-
-<em>r.stats -Anc</em> prints out averaged statistics for topographic index.
-
-<h2>SEE ALSO</h2>
-<em><a href="r.topmodel.html">r.topmodel</a></em>,
-<em><a href="r.water.outlet.html">r.water.outlet</a></em>,
-<em><a href="r.mapcalc.html">r.mapcalc</a></em>
-
-<h2>REFERENCE</h2>
-
-Moore, I.D., R.B. Grayson, and A.R. Ladson, 1991. Digital terrain
-modeling: A review of hydrological, geomorphological, and biological
-applications. Hydrol. Processes 5:3-30.
-
-<h2>AUTHORS</h2>
-Main algorithm sources are rewritten from GRIDATB.FOR.
-<br>
-Thanks to Keith Beven.
-<p>
-GRASS port by <a href=mailto:grass4u gmail com>Huidae Cho</a><br>
-Hydro Laboratory, Kyungpook National University, South Korea
-
-<p><i>Last changed: $Date$</i></p>
Copied: grass/trunk/raster/r.topidx/r.topidx.html (from rev 32770, grass/trunk/raster/r.topidx/description.html)
===================================================================
--- grass/trunk/raster/r.topidx/r.topidx.html (rev 0)
+++ grass/trunk/raster/r.topidx/r.topidx.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,42 @@
+<h2>DESCRIPTION</h2>
+
+<em>r.topidx</em> creates topographic index (wetness index), ln(a/tan(beta)), map from
+elevation map
+<p>
+where
+<dl>
+<dd>a: the area of the hillslope per unit contour length that drains through any point,
+<p>
+<dd>tan(beta): the local surface topographic slope (delta vertical) / (delta horizontal).
+</dl>
+<p>
+Input maps may have NULL values. For example, if you have a MASK for
+a watershed (basin map from <em>r.water.outlet</em>), the
+following command will create a masked elevation map (belev):
+<div class="code"><pre>
+r.mapcalc "belev = if(isnull(basin), basin, elev)"
+</pre></div>
+<p>
+
+<em>r.stats -Anc</em> prints out averaged statistics for topographic index.
+
+<h2>SEE ALSO</h2>
+<em><a href="r.topmodel.html">r.topmodel</a></em>,
+<em><a href="r.water.outlet.html">r.water.outlet</a></em>,
+<em><a href="r.mapcalc.html">r.mapcalc</a></em>
+
+<h2>REFERENCE</h2>
+
+Moore, I.D., R.B. Grayson, and A.R. Ladson, 1991. Digital terrain
+modeling: A review of hydrological, geomorphological, and biological
+applications. Hydrol. Processes 5:3-30.
+
+<h2>AUTHORS</h2>
+Main algorithm sources are rewritten from GRIDATB.FOR.
+<br>
+Thanks to Keith Beven.
+<p>
+GRASS port by <a href=mailto:grass4u gmail com>Huidae Cho</a><br>
+Hydro Laboratory, Kyungpook National University, South Korea
+
+<p><i>Last changed: $Date$</i></p>
Deleted: grass/trunk/raster/r.topmodel/description.html
===================================================================
--- grass/trunk/raster/r.topmodel/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.topmodel/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,60 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<b><em>r.topmodel</em></b> simulates TOPMODEL which is a physically based
-hydrologic model.
-<p>
-Note: (i) means input; (o) means output; (o/i) means input or output
-<p>
-The <b>-i</b> flag indicates that input data are given for (o/i). Without this
-flag, all inputs (i) and intermediate outputs (o/i) should be given. For
-example, [belevation] map will be created from [elevation] and [basin] in every
-run. However, given the same [elevation] and [basin], [belevation] output will
-be the same all the time, so r.topmodel can directly take [belevation] as an
-input with this flag to save time.
-<p>
-
-<h3>Selected Parameters:</h3>
-
-<dl>
-<dt><b>depressionless</b> map is created as follows:</dt>
-<dd><div class="code"><pre>
-r.fill.dir input=elevation elev=depressionless dir=direction type=grass
-</pre></div>
-This option can be omitted if [elevation] map is already depressionless.
-</dd>
-<p>
-
-<dt><b>belevation</b> map is created from [elevation] with [basin] mask applied:</dt>
-<dd><div class="code"><pre>
-r.mapcalc "belevation = if(basin == 0 || isnull(basin), null(), elevation)"
-</pre></div></dd>
-<p>
-
-<dt><b>topidx</b> map is created as follows:</dt>
-<dd><div class="code"><pre>
-r.topidx input=elevation output=topidx
-</pre></div></dd>
-<p>
-
-<dt><b>Qobs</b></dt>
-<dd>Compare simulated flows with observed flows and calculate model
-efficiency.
-</dd>
-<p>
-</dl>
-
-<h2>SEE ALSO</h2>
-<em><a href="r.fill.dir.html">r.fill.dir</a></em>,
-<em><a href="r.mapcalc.html">r.mapcalc</a></em>,
-<em><a href="r.topidx.html">r.topidx</a></em>,
-<em><a href="http://geni.ath.cx/r.topmodel.html">How to run r.topmodel</a></em>
-
-<h2>AUTHORS</h2>
-Main algorithm sources are rewritten in C based on TMOD9502.FOR.
-<br>
-Thanks to Keith Beven.
-<p>
-GRASS port by <a href=mailto:grass4u gmail com>Huidae Cho</a><br>
-Hydro Laboratory, Kyungpook National University, South Korea
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.topmodel/r.topmodel.html (from rev 32770, grass/trunk/raster/r.topmodel/description.html)
===================================================================
--- grass/trunk/raster/r.topmodel/r.topmodel.html (rev 0)
+++ grass/trunk/raster/r.topmodel/r.topmodel.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,60 @@
+<h2>DESCRIPTION</h2>
+
+<b><em>r.topmodel</em></b> simulates TOPMODEL which is a physically based
+hydrologic model.
+<p>
+Note: (i) means input; (o) means output; (o/i) means input or output
+<p>
+The <b>-i</b> flag indicates that input data are given for (o/i). Without this
+flag, all inputs (i) and intermediate outputs (o/i) should be given. For
+example, [belevation] map will be created from [elevation] and [basin] in every
+run. However, given the same [elevation] and [basin], [belevation] output will
+be the same all the time, so r.topmodel can directly take [belevation] as an
+input with this flag to save time.
+<p>
+
+<h3>Selected Parameters:</h3>
+
+<dl>
+<dt><b>depressionless</b> map is created as follows:</dt>
+<dd><div class="code"><pre>
+r.fill.dir input=elevation elev=depressionless dir=direction type=grass
+</pre></div>
+This option can be omitted if [elevation] map is already depressionless.
+</dd>
+<p>
+
+<dt><b>belevation</b> map is created from [elevation] with [basin] mask applied:</dt>
+<dd><div class="code"><pre>
+r.mapcalc "belevation = if(basin == 0 || isnull(basin), null(), elevation)"
+</pre></div></dd>
+<p>
+
+<dt><b>topidx</b> map is created as follows:</dt>
+<dd><div class="code"><pre>
+r.topidx input=elevation output=topidx
+</pre></div></dd>
+<p>
+
+<dt><b>Qobs</b></dt>
+<dd>Compare simulated flows with observed flows and calculate model
+efficiency.
+</dd>
+<p>
+</dl>
+
+<h2>SEE ALSO</h2>
+<em><a href="r.fill.dir.html">r.fill.dir</a></em>,
+<em><a href="r.mapcalc.html">r.mapcalc</a></em>,
+<em><a href="r.topidx.html">r.topidx</a></em>,
+<em><a href="http://geni.ath.cx/r.topmodel.html">How to run r.topmodel</a></em>
+
+<h2>AUTHORS</h2>
+Main algorithm sources are rewritten in C based on TMOD9502.FOR.
+<br>
+Thanks to Keith Beven.
+<p>
+GRASS port by <a href=mailto:grass4u gmail com>Huidae Cho</a><br>
+Hydro Laboratory, Kyungpook National University, South Korea
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.transect/description.html
===================================================================
--- grass/trunk/raster/r.transect/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.transect/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,46 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-This program outputs, in ASCII, the values in a raster map
-which lie along one or more user-defined transect lines.
-The transects are described by their starting coordinates,
-azimuth, and distance.
-
-<!-- The transects may be single-cell
- wide lines, or multiple-cell wide lines. The output, for
- each transect, may be the values at each of the cells, or a
- single aggregate value (e.g., average or median value). -->
-<p>
-
-The <b>line</b> parameter is a definition of (each) transect line,
-specified by the geographic coordinates of its starting point (<em>easting,
-northing</em>), the angle and direction of its travel (<em>azimuth</em>),
-and its distance (<em>distance</em>).
-
-<p>
-The <em>azimuth</em> is an angle, in degrees, measured to
-the east of north. The <em>distance</em> is in map units
-(meters for a metered database, like UTM).
-<p>
-The <b>null</b> parameter can optionally be set to change the character
-string representing null values.
-
-<h2>NOTES</h2>
-
-This program is a front-end to the <em>
-<a href="r.profile.html">r.profile</a></em> program. It simply converts the
-azimuth and distance to an ending coordinate and then runs <em>
-<a href="r.profile.html">r.profile</a></em>.
-
-There once were <b>width=</b> and <b>result=</b><em>raw|median|average</em>
- options which are not currently implemented.
-
-<h2>SEE ALSO</h2>
-
-<em><a href="r.profile.html">r.profile</a></em>,
-<em><a href="gm_profile.html">gis.m: PROFILE TOOL</a></em>
-
-<h2>AUTHOR</h2>
-
-Michael Shapiro, U.S. Army Construction Engineering Research Laboratory
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.transect/r.transect.html (from rev 32770, grass/trunk/raster/r.transect/description.html)
===================================================================
--- grass/trunk/raster/r.transect/r.transect.html (rev 0)
+++ grass/trunk/raster/r.transect/r.transect.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,46 @@
+<h2>DESCRIPTION</h2>
+
+This program outputs, in ASCII, the values in a raster map
+which lie along one or more user-defined transect lines.
+The transects are described by their starting coordinates,
+azimuth, and distance.
+
+<!-- The transects may be single-cell
+ wide lines, or multiple-cell wide lines. The output, for
+ each transect, may be the values at each of the cells, or a
+ single aggregate value (e.g., average or median value). -->
+<p>
+
+The <b>line</b> parameter is a definition of (each) transect line,
+specified by the geographic coordinates of its starting point (<em>easting,
+northing</em>), the angle and direction of its travel (<em>azimuth</em>),
+and its distance (<em>distance</em>).
+
+<p>
+The <em>azimuth</em> is an angle, in degrees, measured to
+the east of north. The <em>distance</em> is in map units
+(meters for a metered database, like UTM).
+<p>
+The <b>null</b> parameter can optionally be set to change the character
+string representing null values.
+
+<h2>NOTES</h2>
+
+This program is a front-end to the <em>
+<a href="r.profile.html">r.profile</a></em> program. It simply converts the
+azimuth and distance to an ending coordinate and then runs <em>
+<a href="r.profile.html">r.profile</a></em>.
+
+There once were <b>width=</b> and <b>result=</b><em>raw|median|average</em>
+ options which are not currently implemented.
+
+<h2>SEE ALSO</h2>
+
+<em><a href="r.profile.html">r.profile</a></em>,
+<em><a href="gm_profile.html">gis.m: PROFILE TOOL</a></em>
+
+<h2>AUTHOR</h2>
+
+Michael Shapiro, U.S. Army Construction Engineering Research Laboratory
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.volume/description.html
===================================================================
--- grass/trunk/raster/r.volume/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.volume/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,108 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>r.volume</em> is a tool for summing cell values within clumps
-and calculating volumes and centroids of patches or clumps.
-<p>
-<em>r.volume</em> generates a table containing the sum of all cells from
-a data_map layer sorted by category on a clump map, and optionally
-generates a vector points map of the centroids for each clump. If a
-clump map is not specified, the current MASK is used.
-The sum is multiplied by the area of a cell to give the volume
-occupied by that cell. See below for an example of the output
-table.
-
-<!-- The table is placed in the user's home directory in the
-file Gvol.report. (or not???)
-
-NOTE: I can't find any evidence of this in the source code, and I have tested
-the module out as of Jan 10, 2008. I'll leave the above comment about
-automatic report generation commented out from the manpage for now, unless I get
-notification otherwise. - EP
--->
-
-<h2>NOTES</h2>
-<p>
-If a clump map is not given and a MASK not set, the program exits
-with an error message.
-<p>
-<em>r.volume</em> works in the current region and respects the current MASK.
-<p>
-
-<h2>EXAMPLE</h2>
-
-The following report was generated by the command:
-(spearfish data base; fields.only is the fields layer without the
-National Forest category)
-<p>
-r.volume data=elevation clump=fields.only centroids=field.centers
-<p>
-
-<pre><tt>
-Volume report on data from elevation using clumps on fields.only map
-
- Cat Average Data # Cells Centroid Total
-Number in clump Total in clump Easting Northing Volume
-
- 1 1181.09 75590 64 595500.00 4927700.00 755900000.00
- 2 1163.50 69810 60 597100.00 4927700.00 698100000.00
- 3 1146.83 34405 30 598300.00 4927700.00 344050000.00
- 4 1193.20 366311 307 599400.00 4927300.00 3663110000.00
- .....
- .....
- .....
- 60 1260.08 351563 279 603100.00 4921000.00 3515630000.00
- 61 1213.93 35204 29 603700.00 4921500.00 352040000.00
- 62 1207.71 33816 28 604100.00 4921500.00 338160000.00
- Total Volume = 67226740000.00
-</tt></pre>
-
-
-The Data Total column is the sum of the elevations for each
-in each of the fields. The Total Volume is the sum multiplied
-by the e-w resolution times the n-s resolution. Note that
-the units on the volume may be difficult if the units of cell
-values on the data_map layer and the resolution units differ.
-<p>
-
-<h3>CENTROIDS</h3>
-The centroid coordinates are the same as those stored in the sites
-file (if one was requested). They are guaranteed to fall on a cell
-of the appropriate category, thus they are not always the true,
-mathematical centroid. They will always fall at a cell center.
-
-<h3>FORMAT OF CENTROIDS table<br></h3>
-For each line of above table the vector points table contains
-these columns:
-<tt>
-easting,
-northing,
-cat,
-volume,
-average,
-sum,
-count
-</tt>
-<p>
-This can be converted directly to a raster map with each point
-a separate category using <em>v.to.rast</em>.
-<p>
-
-<!-- As far as I can tell, no attributes are written to a table in Grass 6.3
-(Jan 2008), as this program hasn't been updated to use the Grass 6 vector library. - EP
--->
-
-
-<h3>APPLICATIONS</h3>
-By preprocessing the elevation layer with <em>r.mapcalc</em> and using
-suitable masking or clump maps, very interesting applications can
-be done with <em>r.volume</em>. Such as, calculating the volume of rock
-in a potential quarry; calculating cut/fill volumes for roads;
-finding water volumes in potential reservoirs. Data layers of
-other measures of real values.
-
-<h2>AUTHOR</h2>
-Dr. James Hinthorne, Central Washington University GIS Laboratory<br>
-December 1988.
-
-
-
Copied: grass/trunk/raster/r.volume/r.volume.html (from rev 32770, grass/trunk/raster/r.volume/description.html)
===================================================================
--- grass/trunk/raster/r.volume/r.volume.html (rev 0)
+++ grass/trunk/raster/r.volume/r.volume.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,108 @@
+<h2>DESCRIPTION</h2>
+
+<em>r.volume</em> is a tool for summing cell values within clumps
+and calculating volumes and centroids of patches or clumps.
+<p>
+<em>r.volume</em> generates a table containing the sum of all cells from
+a data_map layer sorted by category on a clump map, and optionally
+generates a vector points map of the centroids for each clump. If a
+clump map is not specified, the current MASK is used.
+The sum is multiplied by the area of a cell to give the volume
+occupied by that cell. See below for an example of the output
+table.
+
+<!-- The table is placed in the user's home directory in the
+file Gvol.report. (or not???)
+
+NOTE: I can't find any evidence of this in the source code, and I have tested
+the module out as of Jan 10, 2008. I'll leave the above comment about
+automatic report generation commented out from the manpage for now, unless I get
+notification otherwise. - EP
+-->
+
+<h2>NOTES</h2>
+<p>
+If a clump map is not given and a MASK not set, the program exits
+with an error message.
+<p>
+<em>r.volume</em> works in the current region and respects the current MASK.
+<p>
+
+<h2>EXAMPLE</h2>
+
+The following report was generated by the command:
+(spearfish data base; fields.only is the fields layer without the
+National Forest category)
+<p>
+r.volume data=elevation clump=fields.only centroids=field.centers
+<p>
+
+<pre><tt>
+Volume report on data from elevation using clumps on fields.only map
+
+ Cat Average Data # Cells Centroid Total
+Number in clump Total in clump Easting Northing Volume
+
+ 1 1181.09 75590 64 595500.00 4927700.00 755900000.00
+ 2 1163.50 69810 60 597100.00 4927700.00 698100000.00
+ 3 1146.83 34405 30 598300.00 4927700.00 344050000.00
+ 4 1193.20 366311 307 599400.00 4927300.00 3663110000.00
+ .....
+ .....
+ .....
+ 60 1260.08 351563 279 603100.00 4921000.00 3515630000.00
+ 61 1213.93 35204 29 603700.00 4921500.00 352040000.00
+ 62 1207.71 33816 28 604100.00 4921500.00 338160000.00
+ Total Volume = 67226740000.00
+</tt></pre>
+
+
+The Data Total column is the sum of the elevations for each
+in each of the fields. The Total Volume is the sum multiplied
+by the e-w resolution times the n-s resolution. Note that
+the units on the volume may be difficult if the units of cell
+values on the data_map layer and the resolution units differ.
+<p>
+
+<h3>CENTROIDS</h3>
+The centroid coordinates are the same as those stored in the sites
+file (if one was requested). They are guaranteed to fall on a cell
+of the appropriate category, thus they are not always the true,
+mathematical centroid. They will always fall at a cell center.
+
+<h3>FORMAT OF CENTROIDS table<br></h3>
+For each line of above table the vector points table contains
+these columns:
+<tt>
+easting,
+northing,
+cat,
+volume,
+average,
+sum,
+count
+</tt>
+<p>
+This can be converted directly to a raster map with each point
+a separate category using <em>v.to.rast</em>.
+<p>
+
+<!-- As far as I can tell, no attributes are written to a table in Grass 6.3
+(Jan 2008), as this program hasn't been updated to use the Grass 6 vector library. - EP
+-->
+
+
+<h3>APPLICATIONS</h3>
+By preprocessing the elevation layer with <em>r.mapcalc</em> and using
+suitable masking or clump maps, very interesting applications can
+be done with <em>r.volume</em>. Such as, calculating the volume of rock
+in a potential quarry; calculating cut/fill volumes for roads;
+finding water volumes in potential reservoirs. Data layers of
+other measures of real values.
+
+<h2>AUTHOR</h2>
+Dr. James Hinthorne, Central Washington University GIS Laboratory<br>
+December 1988.
+
+
+
Deleted: grass/trunk/raster/r.walk/description.html
===================================================================
--- grass/trunk/raster/r.walk/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.walk/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,133 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>r.walk</em> outputs a raster map layer showing the lowest
-cumulative cost of moving between each cell and the user-specified
-starting points. It uses an input elevation raster map layer whose
-cell category values represent elevation, combined with a second input
-raster map layer whose cell values represent friction costs.
-
-This function is similar to <em>r.cost</em>, but in addiction to a
-friction map, it considers an anisotropic travel time due to the
-different walking speed associated with downhill and uphill movements.
-<p>
-
-The formula from Aitken 1977/Langmuir 1984 (based on Naismith's rule
-for walking times) has been used to estimate the cost parameters of
-specific slope intervals:
-
-<p>
-T= [(a)*(Delta S)] + [(b)*(Delta H uphill)] + [(c)*(Delta H moderate downhill)] + [(d)*(Delta H steep downhill)]
-<p>
-where:<br>
-T is time of movement in seconds,<br>
-Delta S is the distance covered in meters,<br>
-Delta H is the altitude difference in meter.
-<p>
-
-The a, b, c, d parameters take in account movement speed in the different
-conditions and are linked to:
-
-<ul>
- <li>a: underfoot condition (a=1/walking_speed)</li>
- <li>b: underfoot condition and cost associated to movement uphill</li>
- <li>c: underfoot condition and cost associated to movement moderate downhill</li>
- <li>d: underfoot condition and cost associated to movement steep downhill</li>
-</ul>
-
-It has been proved that moving downhill is favourable up to a specific
-slope value threshold, after that it becomes unfavourable. The default
-slope value threshold (slope factor) is -0.2125, corresponding to
-tan(-12), calibrated on human behaviour (>5 and <12
-degrees: moderate downhill; >12 degrees: steep downhill). The
-default values for a, b, c, d are those proposed by Langmuir (0.72, 6.0,
-1.9998, -1.9998), based on man walking effort in standard
-conditions.<p>
-
-The lambda parameter of the linear equation combining movement and
-friction costs:<br>
-
-total cost = movement time cost + (lambda) * friction costs<br>
-must be set in the option section of <em>r.walk</em>.
-<p>
-
-For a more accurate result, the "knight's move" option can be used
-(although it is more time consuming). In the diagram below, the center
-location (O) represents a grid cell from which cumulative distances
-are calculated. Those neighbours marked with an x are always
-considered for cumulative cost updates. With the "knight's move"
-option, the neighbours marked with a K are also considered.
-
-<div class="code"><pre>
- K K
-K x x x K
- x O x
-K x x x K
- K K
-</pre></div>
-
-<p>
-The minimum cumulative costs are computed using Dijkstra's
-algorithm, that find an optimum solution (for more details see
-<em>r.cost</em>, that uses the same algorithm).
-<p>
-Once <em>r.walk</em> computes the cumulative cost map as a linear
-combination of friction cost (from friction map) and the altitude and
-distance covered (from the digital elevation model), <em>r.drain</em>
-can be used to find the minimum cost path.
-
-
-<h2>SEE ALSO</h2>
-
-<em><a href="r.cost.html">r.cost</a></em>,
-<em><a href="r.drain.html">r.drain</a></em>,
-<em><a href="r.in.ascii.html">r.in.ascii</a></em>,
-<em><a href="r.mapcalc.html">r.mapcalc</a></em>,
-<em><a href="r.out.ascii.html">r.out.ascii</a></em>
-
-
-<h2>REFERENCES</h2>
-
-<ul>
-<li>Aitken, R. 1977. Wilderness areas in Scotland. Unpublished Ph.D. thesis.
- University of Aberdeen.
-<li> Steno Fontanari, University of Trento, Italy, Ingegneria per l'Ambiente e
- il Territorio, 2000-2001.
- Svilluppo di metodologie GIS per la determinazione dell'accessibilità
- territoriale come supporto alle decisioni nella gestione ambientale.
-<li>Langmuir, E. 1984. Mountaincraft and leadership. The Scottish
- Sports Council/MLTB. Cordee, Leicester.
-</ul>
-
-<h2>AUTHORS</h2>
-
-<b>Based on r.cost written by :</b>
-<p>
-Antony Awaida,<br>
-Intelligent Engineering<br>
-Systems Laboratory,<br>
-M.I.T.<br>
-<br>
-James Westervelt,<br>
-U.S.Army Construction Engineering Research Laboratory
-
-<p>Updated for Grass 5<br>
-Pierre de Mouveaux (pmx at audiovu.com)
-
-<p>
-<b>Initial version of r.walk:</b>
-<p>
-Steno Fontanari, 2002
-
-<p>
-<b>Current version of r.walk:</b>
-<p>
-Franceschetti Simone, Sorrentino Diego, Mussi Fabiano and Pasolli Mattia<br>
-Correction by: Fontanari Steno, Napolitano Maurizio and Flor Roberto<br>
-In collaboration with: Franchi Matteo, Vaglia Beatrice, Bartucca Luisa, Fava Valentina and Tolotti Mathias, 2004
-
-<p>
-<b>Updated for Grass 6.1</b>
-<p>
-Roberto Flor and Markus Neteler
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.walk/r.walk.html (from rev 32770, grass/trunk/raster/r.walk/description.html)
===================================================================
--- grass/trunk/raster/r.walk/r.walk.html (rev 0)
+++ grass/trunk/raster/r.walk/r.walk.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,133 @@
+<h2>DESCRIPTION</h2>
+
+<em>r.walk</em> outputs a raster map layer showing the lowest
+cumulative cost of moving between each cell and the user-specified
+starting points. It uses an input elevation raster map layer whose
+cell category values represent elevation, combined with a second input
+raster map layer whose cell values represent friction costs.
+
+This function is similar to <em>r.cost</em>, but in addiction to a
+friction map, it considers an anisotropic travel time due to the
+different walking speed associated with downhill and uphill movements.
+<p>
+
+The formula from Aitken 1977/Langmuir 1984 (based on Naismith's rule
+for walking times) has been used to estimate the cost parameters of
+specific slope intervals:
+
+<p>
+T= [(a)*(Delta S)] + [(b)*(Delta H uphill)] + [(c)*(Delta H moderate downhill)] + [(d)*(Delta H steep downhill)]
+<p>
+where:<br>
+T is time of movement in seconds,<br>
+Delta S is the distance covered in meters,<br>
+Delta H is the altitude difference in meter.
+<p>
+
+The a, b, c, d parameters take in account movement speed in the different
+conditions and are linked to:
+
+<ul>
+ <li>a: underfoot condition (a=1/walking_speed)</li>
+ <li>b: underfoot condition and cost associated to movement uphill</li>
+ <li>c: underfoot condition and cost associated to movement moderate downhill</li>
+ <li>d: underfoot condition and cost associated to movement steep downhill</li>
+</ul>
+
+It has been proved that moving downhill is favourable up to a specific
+slope value threshold, after that it becomes unfavourable. The default
+slope value threshold (slope factor) is -0.2125, corresponding to
+tan(-12), calibrated on human behaviour (>5 and <12
+degrees: moderate downhill; >12 degrees: steep downhill). The
+default values for a, b, c, d are those proposed by Langmuir (0.72, 6.0,
+1.9998, -1.9998), based on man walking effort in standard
+conditions.<p>
+
+The lambda parameter of the linear equation combining movement and
+friction costs:<br>
+
+total cost = movement time cost + (lambda) * friction costs<br>
+must be set in the option section of <em>r.walk</em>.
+<p>
+
+For a more accurate result, the "knight's move" option can be used
+(although it is more time consuming). In the diagram below, the center
+location (O) represents a grid cell from which cumulative distances
+are calculated. Those neighbours marked with an x are always
+considered for cumulative cost updates. With the "knight's move"
+option, the neighbours marked with a K are also considered.
+
+<div class="code"><pre>
+ K K
+K x x x K
+ x O x
+K x x x K
+ K K
+</pre></div>
+
+<p>
+The minimum cumulative costs are computed using Dijkstra's
+algorithm, that find an optimum solution (for more details see
+<em>r.cost</em>, that uses the same algorithm).
+<p>
+Once <em>r.walk</em> computes the cumulative cost map as a linear
+combination of friction cost (from friction map) and the altitude and
+distance covered (from the digital elevation model), <em>r.drain</em>
+can be used to find the minimum cost path.
+
+
+<h2>SEE ALSO</h2>
+
+<em><a href="r.cost.html">r.cost</a></em>,
+<em><a href="r.drain.html">r.drain</a></em>,
+<em><a href="r.in.ascii.html">r.in.ascii</a></em>,
+<em><a href="r.mapcalc.html">r.mapcalc</a></em>,
+<em><a href="r.out.ascii.html">r.out.ascii</a></em>
+
+
+<h2>REFERENCES</h2>
+
+<ul>
+<li>Aitken, R. 1977. Wilderness areas in Scotland. Unpublished Ph.D. thesis.
+ University of Aberdeen.
+<li> Steno Fontanari, University of Trento, Italy, Ingegneria per l'Ambiente e
+ il Territorio, 2000-2001.
+ Svilluppo di metodologie GIS per la determinazione dell'accessibilità
+ territoriale come supporto alle decisioni nella gestione ambientale.
+<li>Langmuir, E. 1984. Mountaincraft and leadership. The Scottish
+ Sports Council/MLTB. Cordee, Leicester.
+</ul>
+
+<h2>AUTHORS</h2>
+
+<b>Based on r.cost written by :</b>
+<p>
+Antony Awaida,<br>
+Intelligent Engineering<br>
+Systems Laboratory,<br>
+M.I.T.<br>
+<br>
+James Westervelt,<br>
+U.S.Army Construction Engineering Research Laboratory
+
+<p>Updated for Grass 5<br>
+Pierre de Mouveaux (pmx at audiovu.com)
+
+<p>
+<b>Initial version of r.walk:</b>
+<p>
+Steno Fontanari, 2002
+
+<p>
+<b>Current version of r.walk:</b>
+<p>
+Franceschetti Simone, Sorrentino Diego, Mussi Fabiano and Pasolli Mattia<br>
+Correction by: Fontanari Steno, Napolitano Maurizio and Flor Roberto<br>
+In collaboration with: Franchi Matteo, Vaglia Beatrice, Bartucca Luisa, Fava Valentina and Tolotti Mathias, 2004
+
+<p>
+<b>Updated for Grass 6.1</b>
+<p>
+Roberto Flor and Markus Neteler
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.water.outlet/description.html
===================================================================
--- grass/trunk/raster/r.water.outlet/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.water.outlet/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,57 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>r.water.outlet</em> generates a watershed basin from a drainage
-direction map (from <em><a href="r.watershed.html">r.watershed</a></em>) and
-a set of coordinates representing the outlet point of watershed.
-
-<h3>Selected Parameters</h3>
-<dl>
-
-<dt><b>drainage=</b><em>name</em>
-
-<dd>Input map: drainage direction. Indicates the "aspect" for each
-cell. Multiplying positive values by 45 will give the direction in
-degrees that the surface runoff will travel from that cell. The
-value -1 indicates that the cell is a depression area.
-Other negative values indicate that
-surface runoff is leaving the boundaries of the current geographic
-region. The absolute value of these negative cells indicates the
-direction of flow. This map is generated from
-<em><a href="r.watershed.html">r.watershed</a></em>.
-
-<dt><b>basin=</b><em>name</em>
-
-<dd>Output map: Values of one (1) indicate the watershed
-basin. Values of zero are not in the watershed basin.
-
-<dt><b>easting=</b><em>value</em>
-
-<dd>Input value: Easting value of outlet point.
-
-<dt><b>northing=</b><em>value</em>
-
-<dd>Input value: Northing value of outlet point.
-
-</dl>
-
-<h2>NOTES</h2>
-
-In the context of this program, a watershed basin is the
-region upstream of an outlet point. Thus, if the user
-chooses an outlet point on a hill slope, the resulting map
-will be a thin silver of land representing the overland
-slope uphill of the point.
-
-<h2>SEE ALSO</h2>
-
-<em>
-<a href="d.where.html">d.where</a>,
-<a href="r.watershed.html">r.watershed</a>,
-<a href="r.topidx.html">r.topidx</a>
-</em>
-
-<h2>AUTHOR</h2>
-
-Charles Ehlschlaeger, U.S. Army Construction Engineering Research Laboratory
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.water.outlet/r.water.outlet.html (from rev 32770, grass/trunk/raster/r.water.outlet/description.html)
===================================================================
--- grass/trunk/raster/r.water.outlet/r.water.outlet.html (rev 0)
+++ grass/trunk/raster/r.water.outlet/r.water.outlet.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,57 @@
+<h2>DESCRIPTION</h2>
+
+<em>r.water.outlet</em> generates a watershed basin from a drainage
+direction map (from <em><a href="r.watershed.html">r.watershed</a></em>) and
+a set of coordinates representing the outlet point of watershed.
+
+<h3>Selected Parameters</h3>
+<dl>
+
+<dt><b>drainage=</b><em>name</em>
+
+<dd>Input map: drainage direction. Indicates the "aspect" for each
+cell. Multiplying positive values by 45 will give the direction in
+degrees that the surface runoff will travel from that cell. The
+value -1 indicates that the cell is a depression area.
+Other negative values indicate that
+surface runoff is leaving the boundaries of the current geographic
+region. The absolute value of these negative cells indicates the
+direction of flow. This map is generated from
+<em><a href="r.watershed.html">r.watershed</a></em>.
+
+<dt><b>basin=</b><em>name</em>
+
+<dd>Output map: Values of one (1) indicate the watershed
+basin. Values of zero are not in the watershed basin.
+
+<dt><b>easting=</b><em>value</em>
+
+<dd>Input value: Easting value of outlet point.
+
+<dt><b>northing=</b><em>value</em>
+
+<dd>Input value: Northing value of outlet point.
+
+</dl>
+
+<h2>NOTES</h2>
+
+In the context of this program, a watershed basin is the
+region upstream of an outlet point. Thus, if the user
+chooses an outlet point on a hill slope, the resulting map
+will be a thin silver of land representing the overland
+slope uphill of the point.
+
+<h2>SEE ALSO</h2>
+
+<em>
+<a href="d.where.html">d.where</a>,
+<a href="r.watershed.html">r.watershed</a>,
+<a href="r.topidx.html">r.topidx</a>
+</em>
+
+<h2>AUTHOR</h2>
+
+Charles Ehlschlaeger, U.S. Army Construction Engineering Research Laboratory
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.watershed/front/description.html
===================================================================
--- grass/trunk/raster/r.watershed/front/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.watershed/front/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,426 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>r.watershed</em> generates a set of maps indicating:
-1) the location of watershed basins, and
-2) the LS and S factors of the Revised Universal Soil Loss Equation (RUSLE).
-
-<p>
-<!-- Interactive mode not activated in GRASS 6.
-<em>r.watershed</em> can be run either interactively or non-interactively.
-If the user types <tt>r.watershed</tt>
-on the command line without program arguments, the program will prompt the user
-with a verbose description of the input maps. The interactive version of
-<em>r.watershed</em> can prepare inputs to lumped-parameter hydrologic models.
-After a verbose interactive session, <em>r.watershed</em> will query the user
-for a number of
-map layers. Each map layer's values will be tabulated by watershed basin and sent
-to an output file. This output file is organized to ease data entry into a
-lumped-parameter hydrologic model program. The non-interactive version of
-<em>r.watershed</em> cannot create this file.
-
-<p>
-The user can run the program non-interactively, by specifying input map names
-on the command line. Parameter names may be specified by their
-full names, or by any initial string that distinguish them from other parameter names.
-In <em>r.watershed</em>'s case, the first two letters of each name sufficiently
-distinguishes parameter names.
-For example, the two expressions below are equivalent inputs to <em>r.watershed</em>:
-<p>
-<pre>
- el=elev.map th=100 st=stream.map ba=basin.map
-
- elevation=elev.map threshold=100 stream=stream.map basin=basin.map
-</pre>
--->
-<h2>OPTIONS</h2>
-
-<dl>
-<dt><em>-m</em>
-
-<dd>Without this flag set, the entire analysis is run in memory
-maintained by the operating system. This can be limiting, but is
-relatively fast. Setting the flag causes the program to manage memory
-on disk which allows larger maps to be processes but is considerably
-slower.
-
-<dt><em>-4</em>
-
-<dd>Allow only horizontal and vertical flow of water.
-Stream and slope lengths are approximately the same as outputs from default surface
-flow (allows horizontal, vertical, and diagonal flow of water).
-This flag will also make the drainage basins look more homogeneous.
-
-<dt><em>elevation</em>
-
-<dd>Input map: Elevation on which entire analysis is based.
-
-<dt><em>depression</em>
-
-<dd>Input map: Map layer of actual depressions or sinkholes in the
-landscape that are large enough to slow and store surface runoff from
-a storm event. Any non-zero values indicate depressions.
-
-<dt><em>flow</em>
-
-<dd>Input map: amount of overland flow per cell. This map indicates the
-amount of overland flow units that each cell will contribute to the
-watershed basin model. Overland flow units represent the amount of
-overland flow each cell contributes to surface flow. If omitted, a
-value of one (1) is assumed. The algorithm is D8 flow accumulation.
-
-<dt><em>disturbed.land</em>
-
-<dd>Raster map input layer or value containing the percent of disturbed
-land (i.e., croplands, and construction sites) where the raster or input
-value of 17 equals 17%. If no map or value is given, <em>r.watershed</em>
-assumes no disturbed land. This input is used for the RUSLE calculations.
-
-<dt><em>blocking</em>
-
-<dd>Input map: terrain that will block overland surface flow. Terrain
-that will block overland surface flow and restart the slope length
-for the RUSLE. Any non-zero values indicate blocking terrain.
-
-<dt><em>threshold</em>
-
-<dd>The minimum size of an exterior watershed basin in cells, if no flow
-map is input, or overland flow units when a flow map is given.
-Warning: low threshold values will dramactically increase run time and
-generate difficult too read basin and half.basin results.
-This parameter also controls the level of detail in the <em>stream</em>
-segments map.
-
-<dt><em>max.slope.length</em>
-
-<dd>Input value indicating the maximum length of overland surface flow
-in meters. If overland flow travels greater than the maximum length,
-the program assumes the maximum length (it assumes that landscape
-characteristics not discernible in the digital elevation model exist
-that maximize the slope length). This input is used for the RUSLE calculations
-and is a sensitive parameter.
-
-<dt><em>accumulation</em>
-
-<dd>Output map: The absolute value of each cell in this output map layer is
-the amount of overland flow that traverses the cell. This value will be
-the number of upland cells plus one if no overland flow map is given. If
-the overland flow map is given, the value will be in overland flow units.
-Negative numbers indicate that those cells possibly have surface runoff
-from outside of the current geographic region. Thus, any cells with
-negative values cannot have their surface runoff and sedimentation yields
-calculated accurately.
-
-<dt><em>drainage</em>
-
-<dd>Output map: drainage direction. Provides the "aspect" for each
-cell. Multiplying positive values by 45 will give the direction in
-degrees that the surface runoff will travel from that cell. The
-value -1 indicates that the cell is a depression area (defined by
-the depression input map). Other negative values indicate that
-surface runoff is leaving the boundaries of the current geographic
-region. The absolute value of these negative cells indicates the
-direction of flow.
-
-<dt><em>basin</em>
-
-<dd>Output map: Unique label for each watershed basin. Each basin will
-be given a unique positive even integer. Areas along edges may not
-be large enough to create an exterior watershed basin. 0 values
-indicate that the cell is not part of a complete watershed basin
-in the current geographic region.
-
-<dt><em>stream</em>
-
-<dd>Output map: stream segments. Values correspond to the watershed
-basin values.
-
-<dt><em>half.basin</em>
-
-<dd>Output map: each half-basin is given a unique value. Watershed
-basins are divided into left and right sides. The right-hand side
-cell of the watershed basin (looking upstream) are given even values
-corresponding to the values in basin. The left-hand side
-cells of the watershed basin are given odd values which are one less
-than the value of the watershed basin.
-
-<dt><em>visual</em>
-
-<dd>Output map: useful for visual display of results.
-Surface runoff accumulation with the values
-modified to provide for easy display. All negative accumulation values
-are changed to zero. All positive values above the basin threshold
-are given the value of the <em>threshold</em> parameter.
-
-<dt><em>length.slope</em>
-
-<dd>Output map: slope length and steepness (LS) factor. Contains the LS
-factor for the Revised Universal Soil Loss Equation. Equations taken
-from <em>Revised Universal Soil Loss Equation for Western Rangelands</em>
-(Weltz et al. 1987).
-Since the LS factor is a small number, it is multiplied by 100 for the
-GRASS output map.
-
-<dt><em>slope.steepness</em>
-
-<dd>Output map: slope steepness (S) factor for RUSLE.
-Contains the revised S factor for the Universal Soil
-Loss Equation. Equations taken from article entitled
-<em>Revised Slope Steepness Factor for the Universal Soil
-Loss Equation</em> (McCool et al. 1987). Since the S factor
-is a small number (usually less than one), it is multiplied
-by 100 for the GRASS output map layer.
-</dd>
-</dl>
-
-
-<h2>NOTES</h2>
-
-<em>r.watershed</em> uses an algorithm designed to minimize the impact of
-DEM data errors. This algorithm works slower than <em>r.terraflow</em> but
-provides more accurate results in areas of low slope as well as DEMs
-constructed with techniques that mistake canopy tops as the ground elevation.
-Kinner et al. (2005), for example, used SRTM and IFSAR DEMs to compare
-<em>r.watershed</em> against <em>r.terraflow</em> results in Panama.
-<em>r.terraflow</em> was unable to replicate stream locations in the larger
-valleys while <em>r.watershed</em> performed much better. Thus, if forest
-canopy exists in valleys, SRTM, IFSAR, and similar data products will cause
-major errors in <em>r.terraflow</em> stream output. Under similar conditions,
-<em>r.watershed</em> will generate better <b>stream</b> and <b>half.basin</b>
-results. If watershed divides contain flat to low slope, <em>r.watershed</em>
-will generate better basin results than <em>r.terraflow</em>.
-(<em>r.terraflow</em> uses the same type of algorithm as ESRI's ArcGIS
-watershed software which fails under these conditions.) Also, if watershed
-divides contain forest canopy mixed with uncanopied areas using SRTM, IFSAR,
-and similar data products, <em>r.watershed</em> will generate better basin
-results than <em>r.terraflow</em>.
-
-<p>
-There are two versions of this program: <em>ram</em> and <em>seg</em>.
-Which is version is run depends on whether the <em>-m</em> flag is set.
-<br>
-The <em>ram</em> version uses virtual memory managed by the operating
-system to store all the data structures and is faster than the <em>seg</em>
-version;
-<em>seg</em> uses the GRASS segmentation library which manages data in disk
-files. Thus <em>seg</em> uses much less system memory (RAM) allowing other
-processes to operate on the same CPU, even when the current geographic
-region is huge.
-<br>
-Due to memory requirements of both programs, it is quite easy to run out of
-memory when working with huge map regions. If the <em>ram</em> version runs
-out of memory and the resolution size of the current geographic region
-cannot be increased, either more memory needs to be added to the computer,
-or the swap space size needs to be increased. If <em>seg</em> runs out of
-memory, additional disk space needs to be freed up for the program to run.
-
-<p>
-Both versions use the A<sup>T</sup> least-cost search algorithm to determine
-the flow of water over the landscape (see <a href="#seealso">SEE ALSO</a>
-section).
-The algorithm produces results similar to those obtained when running
-<em><a href="r.cost.html">r.cost</a></em> and
-<em><a href="r.drain.html">r.drain</a></em> on every cell on the map.
-
-<p>
-In many situations, the elevation data will be too finely detailed for
-the amount of time or memory available. Running <em>r.watershed</em> may
-require use of a coarser resolution. To make the results more closely
-resemble the finer terrain data, create a map layer containing the
-lowest elevation values at the coarser resolution. This is done by:
-1) Setting the current geographic region equal to the elevation map
-layer with <em>g.region</em>, and 2) Use the <em>r.neighbors</em> or
-<em>r.resamp.stats</em> command to find the lowest value for an area
-equal in size to the desired resolution. For example, if the resolution
-of the elevation data is 30 meters and the resolution of the geographic
-region for <em>r.watershed</em> will be 90 meters: use the minimum
-function for a 3 by 3 neighborhood. After changing to the resolution at
-which <em>r.watershed</em> will be run, <em>r.watershed</em> should be run
-using the values from the <em>neighborhood</em> output map layer that
-represents the minimum elevation within the region of the coarser cell.
-
-<p>
-The minimum size of drainage basins, defined by the <em>threshold</em>
-parameter, is only relevant for those watersheds with a single stream
-having at least the <em>threshold</em> of cells flowing into it.
-(These watersheds are called exterior basins.)
-Interior drainage basins contain stream segments below multiple tributaries.
-Interior drainage basins can be of any size because the length of
-an interior stream segment is determined by the distance between the
-tributaries flowing into it.
-
-<p>
-The <em>r.watershed</em> program does not require the user to have the
-current geographic region filled with elevation values. Areas without
-elevation data MUST be masked out, by creating a raster map (or raster
-reclassification) named <tt>MASK</tt>. Areas
-masked out will be treated as if they are off the edge of the region.
-MASKs will reduce the memory necessary to run the program. Masking out
-unimportant areas can significantly reduce processing time if the watersheds
-of interest occupy a small percentage of the overall area.
-
-<p>
-Zero data values will be treated as elevation data (not no_data).
-
-<p>
-To isolate an individual river network using the output of this module,
-a number of approaches may be considered.
-<ol>
-<li>Use a resample of the basins catchment raster map as a MASK.<br>
- The equivalent vector map method is similar using <em>v.select</em> or
- <em>v.overlay</em>.
-<li>Use the <em>r.cost</em> module with a point in the river as a starting
- point.
-<li>Use the <em>v.net.iso</em> module with a node in the river as a
- starting point.
-</ol>
-
-
-<p>
-To create <i>river mile</i> segmentation from a vectorized streams map,
-try the <em>v.net.iso</em> or <em>v.lrs.segment</em> modules.
-
-
-<h2>EXAMPLES</h2>
-<i>These examples use the Spearfish sample dataset.</i>
-<p>
-Convert <em>r.watershed</em> streams map output to a vector layer.
-<p>
-If you want a detailed stream network, set the threshold option
-small to create lots of catchment basins, as only one stream is
-presented per catchment. The r.to.vect -v flag preserves the
-catchment ID as the vector category number.
-
-<div class="code"><pre>
- r.watershed elev=elevation.dem stream=rwater.stream
- r.to.vect -v in=rwater.stream out=rwater_stream
-</pre></div>
-<br>
-
-<p>
-Set a nice color table for the accumulation map:
-<div class="code"><pre>
- MAP=rwater.accum
- r.watershed elev=elevation.dem accum=$MAP
-
- eval `r.univar -g "$MAP"`
- stddev_x_2=`echo $stddev | awk '{print $1 * 2}'`
- stddev_div_2=`echo $stddev | awk '{print $1 / 2}'`
-
- r.colors $MAP col=rules << EOF
- 0% red
- -$stddev_x_2 red
- -$stddev yellow
- -$stddev_div_2 cyan
- -$mean_of_abs blue
- 0 white
- $mean_of_abs blue
- $stddev_div_2 cyan
- $stddev yellow
- $stddev_x_2 red
- 100% red
- EOF
-</pre></div>
-<br>
-
-
-<p>
-Create a more detailed stream map using the accumulation map and convert
-it to a vector output map. The accumulation cut-off, and therefore fractal
-dimension, is arbitrary; in this example we use the map's mean number of
-upstream catchment cells (calculated in the above example by <em>r.univar</em>)
-as the cut-off value.
-<div class="code"><pre>
- r.watershed elev=elevation.dem accum=rwater.accum
-
- r.mapcalc 'MASK = if(!isnull(elevation.dem))'
- r.mapcalc "rwater.course = \
- if( abs(rwater.accum) > $mean_of_abs, \
- abs(rwater.accum), \
- null() )"
- r.colors -g rwater.course col=bcyr
- g.remove MASK
-
- # <i>Thinning is required before converting raster lines to vector</i>
- r.thin in=rwater.course out=rwater.course.Thin
- r.colors -gn rwater.course.Thin color=grey
- r.to.vect in=rwater.course.Thin out=rwater_course feature=line
- v.db.dropcol map=rwater_course column=label
-</pre></div>
-<!-- can't set line attribute to catchment it is in as v.what.rast and
- v.distance only work for point features. Could create endpoint node
- points map and upload to that ?? -->
-<!-- Note value column containing accumulation cells in output vector
- may not necessarily reference the downstream end of the line! drop it? -->
-<br>
-
-<p>
-Create watershed basins map and convert to a vector polygon map
-<div class="code"><pre>
- r.watershed elev=elevation.dem basin=rwater.basin thresh=15000
- r.to.vect -s in=rwater.basin out=rwater_basins feature=area
- v.db.dropcol map=rwater_basins column=label
- v.db.renamecol map=rwater_basins column=value,catchment
-</pre></div>
-<br>
-
-<p>
-Display output in a nice way
-<div class="code"><pre>
- r.shaded.relief map=elevation.dem
- d.shadedmap rel=elevation.dem.shade drape=rwater.basin bright=40
- d.vect rwater_course color=orange
-</pre></div>
-<br>
-
-<a name="references"></a>
-<h2>REFERENCES</h2>
-
-
-Ehlschlaeger, C. (1989). <i>Using the A<sup>T</sup> Search Algorithm
-to Develop Hydrologic Models from Digital Elevation Data</i>,
-<b>Proceedings of International Geographic Information Systems (IGIS)
-Symposium '89</b>, pp 275-281 (Baltimore, MD, 18-19 March 1989).<br>
-URL: <a href="http://faculty.wiu.edu/CR-Ehlschlaeger2/older/IGIS/paper.html">
-http://faculty.wiu.edu/CR-Ehlschlaeger2/older/IGIS/paper.html</a>
-
-<p>
-Kinner D., H. Mitasova, R. Harmon, L. Toma, R., Stallard. (2005).
-<i>GIS-based Stream Network Analysis for The Chagres River Basin,
-Republic of Panama</i>. <b>The Rio Chagres: A Multidisciplinary Profile of
-a Tropical Watershed</b>, R. Harmon (Ed.), Springer/Kluwer, p.83-95.<br>
-URL: <a href="http://skagit.meas.ncsu.edu/%7Ehelena/measwork/panama/panama.html">
-http://skagit.meas.ncsu.edu/~helena/measwork/panama/panama.html</a>
-
-<p>
-McCool et al. (1987). <i>Revised Slope Steepness Factor for the Universal
-Soil Loss Equation</i>, <b>Transactions of the ASAE</b> Vol 30(5).
-
-<p>
-Weltz M. A., K. G. Renard, J. R. Simanton (1987). <i>Revised Universal Soil
-Loss Equation for Western Rangelands</i>, <b>U.S.A./Mexico Symposium of
-Strategies for Classification and Management of Native Vegetation for
-Food Production In Arid Zones</b> (Tucson, AZ, 12-16 Oct. 1987).
-
-<a name="seealso"></a>
-<h2>SEE ALSO</h2>
-
-<em>
-<a href="g.region.html">g.region</a>,
-<a href="r.cost.html">r.cost</a>,
-<a href="r.drain.html">r.drain</a>,
-<a href="r.flow.html">r.flow</a>,
-<!-- <a href="r.flowmd.html">r.flowmd</a>, -->
-<a href="r.neighbors.html">r.neighbors</a>,
-<a href="r.param.scale.html">r.param.scale</a>,
-<a href="r.resamp.interp.html">r.resamp.interp</a>,
-<a href="r.terraflow.html">r.terraflow</a>,
-<a href="r.topidx.html">r.topidx</a>,
-<a href="r.water.outlet.html">r.water.outlet</a>
-</em>
-
-
-<h2>AUTHOR</h2>
-
-Charles Ehlschlaeger, U.S. Army Construction Engineering Research Laboratory
-<p>
-<i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.watershed/front/r.watershed.html (from rev 32770, grass/trunk/raster/r.watershed/front/description.html)
===================================================================
--- grass/trunk/raster/r.watershed/front/r.watershed.html (rev 0)
+++ grass/trunk/raster/r.watershed/front/r.watershed.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,426 @@
+<h2>DESCRIPTION</h2>
+
+<em>r.watershed</em> generates a set of maps indicating:
+1) the location of watershed basins, and
+2) the LS and S factors of the Revised Universal Soil Loss Equation (RUSLE).
+
+<p>
+<!-- Interactive mode not activated in GRASS 6.
+<em>r.watershed</em> can be run either interactively or non-interactively.
+If the user types <tt>r.watershed</tt>
+on the command line without program arguments, the program will prompt the user
+with a verbose description of the input maps. The interactive version of
+<em>r.watershed</em> can prepare inputs to lumped-parameter hydrologic models.
+After a verbose interactive session, <em>r.watershed</em> will query the user
+for a number of
+map layers. Each map layer's values will be tabulated by watershed basin and sent
+to an output file. This output file is organized to ease data entry into a
+lumped-parameter hydrologic model program. The non-interactive version of
+<em>r.watershed</em> cannot create this file.
+
+<p>
+The user can run the program non-interactively, by specifying input map names
+on the command line. Parameter names may be specified by their
+full names, or by any initial string that distinguish them from other parameter names.
+In <em>r.watershed</em>'s case, the first two letters of each name sufficiently
+distinguishes parameter names.
+For example, the two expressions below are equivalent inputs to <em>r.watershed</em>:
+<p>
+<pre>
+ el=elev.map th=100 st=stream.map ba=basin.map
+
+ elevation=elev.map threshold=100 stream=stream.map basin=basin.map
+</pre>
+-->
+<h2>OPTIONS</h2>
+
+<dl>
+<dt><em>-m</em>
+
+<dd>Without this flag set, the entire analysis is run in memory
+maintained by the operating system. This can be limiting, but is
+relatively fast. Setting the flag causes the program to manage memory
+on disk which allows larger maps to be processes but is considerably
+slower.
+
+<dt><em>-4</em>
+
+<dd>Allow only horizontal and vertical flow of water.
+Stream and slope lengths are approximately the same as outputs from default surface
+flow (allows horizontal, vertical, and diagonal flow of water).
+This flag will also make the drainage basins look more homogeneous.
+
+<dt><em>elevation</em>
+
+<dd>Input map: Elevation on which entire analysis is based.
+
+<dt><em>depression</em>
+
+<dd>Input map: Map layer of actual depressions or sinkholes in the
+landscape that are large enough to slow and store surface runoff from
+a storm event. Any non-zero values indicate depressions.
+
+<dt><em>flow</em>
+
+<dd>Input map: amount of overland flow per cell. This map indicates the
+amount of overland flow units that each cell will contribute to the
+watershed basin model. Overland flow units represent the amount of
+overland flow each cell contributes to surface flow. If omitted, a
+value of one (1) is assumed. The algorithm is D8 flow accumulation.
+
+<dt><em>disturbed.land</em>
+
+<dd>Raster map input layer or value containing the percent of disturbed
+land (i.e., croplands, and construction sites) where the raster or input
+value of 17 equals 17%. If no map or value is given, <em>r.watershed</em>
+assumes no disturbed land. This input is used for the RUSLE calculations.
+
+<dt><em>blocking</em>
+
+<dd>Input map: terrain that will block overland surface flow. Terrain
+that will block overland surface flow and restart the slope length
+for the RUSLE. Any non-zero values indicate blocking terrain.
+
+<dt><em>threshold</em>
+
+<dd>The minimum size of an exterior watershed basin in cells, if no flow
+map is input, or overland flow units when a flow map is given.
+Warning: low threshold values will dramactically increase run time and
+generate difficult too read basin and half.basin results.
+This parameter also controls the level of detail in the <em>stream</em>
+segments map.
+
+<dt><em>max.slope.length</em>
+
+<dd>Input value indicating the maximum length of overland surface flow
+in meters. If overland flow travels greater than the maximum length,
+the program assumes the maximum length (it assumes that landscape
+characteristics not discernible in the digital elevation model exist
+that maximize the slope length). This input is used for the RUSLE calculations
+and is a sensitive parameter.
+
+<dt><em>accumulation</em>
+
+<dd>Output map: The absolute value of each cell in this output map layer is
+the amount of overland flow that traverses the cell. This value will be
+the number of upland cells plus one if no overland flow map is given. If
+the overland flow map is given, the value will be in overland flow units.
+Negative numbers indicate that those cells possibly have surface runoff
+from outside of the current geographic region. Thus, any cells with
+negative values cannot have their surface runoff and sedimentation yields
+calculated accurately.
+
+<dt><em>drainage</em>
+
+<dd>Output map: drainage direction. Provides the "aspect" for each
+cell. Multiplying positive values by 45 will give the direction in
+degrees that the surface runoff will travel from that cell. The
+value -1 indicates that the cell is a depression area (defined by
+the depression input map). Other negative values indicate that
+surface runoff is leaving the boundaries of the current geographic
+region. The absolute value of these negative cells indicates the
+direction of flow.
+
+<dt><em>basin</em>
+
+<dd>Output map: Unique label for each watershed basin. Each basin will
+be given a unique positive even integer. Areas along edges may not
+be large enough to create an exterior watershed basin. 0 values
+indicate that the cell is not part of a complete watershed basin
+in the current geographic region.
+
+<dt><em>stream</em>
+
+<dd>Output map: stream segments. Values correspond to the watershed
+basin values.
+
+<dt><em>half.basin</em>
+
+<dd>Output map: each half-basin is given a unique value. Watershed
+basins are divided into left and right sides. The right-hand side
+cell of the watershed basin (looking upstream) are given even values
+corresponding to the values in basin. The left-hand side
+cells of the watershed basin are given odd values which are one less
+than the value of the watershed basin.
+
+<dt><em>visual</em>
+
+<dd>Output map: useful for visual display of results.
+Surface runoff accumulation with the values
+modified to provide for easy display. All negative accumulation values
+are changed to zero. All positive values above the basin threshold
+are given the value of the <em>threshold</em> parameter.
+
+<dt><em>length.slope</em>
+
+<dd>Output map: slope length and steepness (LS) factor. Contains the LS
+factor for the Revised Universal Soil Loss Equation. Equations taken
+from <em>Revised Universal Soil Loss Equation for Western Rangelands</em>
+(Weltz et al. 1987).
+Since the LS factor is a small number, it is multiplied by 100 for the
+GRASS output map.
+
+<dt><em>slope.steepness</em>
+
+<dd>Output map: slope steepness (S) factor for RUSLE.
+Contains the revised S factor for the Universal Soil
+Loss Equation. Equations taken from article entitled
+<em>Revised Slope Steepness Factor for the Universal Soil
+Loss Equation</em> (McCool et al. 1987). Since the S factor
+is a small number (usually less than one), it is multiplied
+by 100 for the GRASS output map layer.
+</dd>
+</dl>
+
+
+<h2>NOTES</h2>
+
+<em>r.watershed</em> uses an algorithm designed to minimize the impact of
+DEM data errors. This algorithm works slower than <em>r.terraflow</em> but
+provides more accurate results in areas of low slope as well as DEMs
+constructed with techniques that mistake canopy tops as the ground elevation.
+Kinner et al. (2005), for example, used SRTM and IFSAR DEMs to compare
+<em>r.watershed</em> against <em>r.terraflow</em> results in Panama.
+<em>r.terraflow</em> was unable to replicate stream locations in the larger
+valleys while <em>r.watershed</em> performed much better. Thus, if forest
+canopy exists in valleys, SRTM, IFSAR, and similar data products will cause
+major errors in <em>r.terraflow</em> stream output. Under similar conditions,
+<em>r.watershed</em> will generate better <b>stream</b> and <b>half.basin</b>
+results. If watershed divides contain flat to low slope, <em>r.watershed</em>
+will generate better basin results than <em>r.terraflow</em>.
+(<em>r.terraflow</em> uses the same type of algorithm as ESRI's ArcGIS
+watershed software which fails under these conditions.) Also, if watershed
+divides contain forest canopy mixed with uncanopied areas using SRTM, IFSAR,
+and similar data products, <em>r.watershed</em> will generate better basin
+results than <em>r.terraflow</em>.
+
+<p>
+There are two versions of this program: <em>ram</em> and <em>seg</em>.
+Which is version is run depends on whether the <em>-m</em> flag is set.
+<br>
+The <em>ram</em> version uses virtual memory managed by the operating
+system to store all the data structures and is faster than the <em>seg</em>
+version;
+<em>seg</em> uses the GRASS segmentation library which manages data in disk
+files. Thus <em>seg</em> uses much less system memory (RAM) allowing other
+processes to operate on the same CPU, even when the current geographic
+region is huge.
+<br>
+Due to memory requirements of both programs, it is quite easy to run out of
+memory when working with huge map regions. If the <em>ram</em> version runs
+out of memory and the resolution size of the current geographic region
+cannot be increased, either more memory needs to be added to the computer,
+or the swap space size needs to be increased. If <em>seg</em> runs out of
+memory, additional disk space needs to be freed up for the program to run.
+
+<p>
+Both versions use the A<sup>T</sup> least-cost search algorithm to determine
+the flow of water over the landscape (see <a href="#seealso">SEE ALSO</a>
+section).
+The algorithm produces results similar to those obtained when running
+<em><a href="r.cost.html">r.cost</a></em> and
+<em><a href="r.drain.html">r.drain</a></em> on every cell on the map.
+
+<p>
+In many situations, the elevation data will be too finely detailed for
+the amount of time or memory available. Running <em>r.watershed</em> may
+require use of a coarser resolution. To make the results more closely
+resemble the finer terrain data, create a map layer containing the
+lowest elevation values at the coarser resolution. This is done by:
+1) Setting the current geographic region equal to the elevation map
+layer with <em>g.region</em>, and 2) Use the <em>r.neighbors</em> or
+<em>r.resamp.stats</em> command to find the lowest value for an area
+equal in size to the desired resolution. For example, if the resolution
+of the elevation data is 30 meters and the resolution of the geographic
+region for <em>r.watershed</em> will be 90 meters: use the minimum
+function for a 3 by 3 neighborhood. After changing to the resolution at
+which <em>r.watershed</em> will be run, <em>r.watershed</em> should be run
+using the values from the <em>neighborhood</em> output map layer that
+represents the minimum elevation within the region of the coarser cell.
+
+<p>
+The minimum size of drainage basins, defined by the <em>threshold</em>
+parameter, is only relevant for those watersheds with a single stream
+having at least the <em>threshold</em> of cells flowing into it.
+(These watersheds are called exterior basins.)
+Interior drainage basins contain stream segments below multiple tributaries.
+Interior drainage basins can be of any size because the length of
+an interior stream segment is determined by the distance between the
+tributaries flowing into it.
+
+<p>
+The <em>r.watershed</em> program does not require the user to have the
+current geographic region filled with elevation values. Areas without
+elevation data MUST be masked out, by creating a raster map (or raster
+reclassification) named <tt>MASK</tt>. Areas
+masked out will be treated as if they are off the edge of the region.
+MASKs will reduce the memory necessary to run the program. Masking out
+unimportant areas can significantly reduce processing time if the watersheds
+of interest occupy a small percentage of the overall area.
+
+<p>
+Zero data values will be treated as elevation data (not no_data).
+
+<p>
+To isolate an individual river network using the output of this module,
+a number of approaches may be considered.
+<ol>
+<li>Use a resample of the basins catchment raster map as a MASK.<br>
+ The equivalent vector map method is similar using <em>v.select</em> or
+ <em>v.overlay</em>.
+<li>Use the <em>r.cost</em> module with a point in the river as a starting
+ point.
+<li>Use the <em>v.net.iso</em> module with a node in the river as a
+ starting point.
+</ol>
+
+
+<p>
+To create <i>river mile</i> segmentation from a vectorized streams map,
+try the <em>v.net.iso</em> or <em>v.lrs.segment</em> modules.
+
+
+<h2>EXAMPLES</h2>
+<i>These examples use the Spearfish sample dataset.</i>
+<p>
+Convert <em>r.watershed</em> streams map output to a vector layer.
+<p>
+If you want a detailed stream network, set the threshold option
+small to create lots of catchment basins, as only one stream is
+presented per catchment. The r.to.vect -v flag preserves the
+catchment ID as the vector category number.
+
+<div class="code"><pre>
+ r.watershed elev=elevation.dem stream=rwater.stream
+ r.to.vect -v in=rwater.stream out=rwater_stream
+</pre></div>
+<br>
+
+<p>
+Set a nice color table for the accumulation map:
+<div class="code"><pre>
+ MAP=rwater.accum
+ r.watershed elev=elevation.dem accum=$MAP
+
+ eval `r.univar -g "$MAP"`
+ stddev_x_2=`echo $stddev | awk '{print $1 * 2}'`
+ stddev_div_2=`echo $stddev | awk '{print $1 / 2}'`
+
+ r.colors $MAP col=rules << EOF
+ 0% red
+ -$stddev_x_2 red
+ -$stddev yellow
+ -$stddev_div_2 cyan
+ -$mean_of_abs blue
+ 0 white
+ $mean_of_abs blue
+ $stddev_div_2 cyan
+ $stddev yellow
+ $stddev_x_2 red
+ 100% red
+ EOF
+</pre></div>
+<br>
+
+
+<p>
+Create a more detailed stream map using the accumulation map and convert
+it to a vector output map. The accumulation cut-off, and therefore fractal
+dimension, is arbitrary; in this example we use the map's mean number of
+upstream catchment cells (calculated in the above example by <em>r.univar</em>)
+as the cut-off value.
+<div class="code"><pre>
+ r.watershed elev=elevation.dem accum=rwater.accum
+
+ r.mapcalc 'MASK = if(!isnull(elevation.dem))'
+ r.mapcalc "rwater.course = \
+ if( abs(rwater.accum) > $mean_of_abs, \
+ abs(rwater.accum), \
+ null() )"
+ r.colors -g rwater.course col=bcyr
+ g.remove MASK
+
+ # <i>Thinning is required before converting raster lines to vector</i>
+ r.thin in=rwater.course out=rwater.course.Thin
+ r.colors -gn rwater.course.Thin color=grey
+ r.to.vect in=rwater.course.Thin out=rwater_course feature=line
+ v.db.dropcol map=rwater_course column=label
+</pre></div>
+<!-- can't set line attribute to catchment it is in as v.what.rast and
+ v.distance only work for point features. Could create endpoint node
+ points map and upload to that ?? -->
+<!-- Note value column containing accumulation cells in output vector
+ may not necessarily reference the downstream end of the line! drop it? -->
+<br>
+
+<p>
+Create watershed basins map and convert to a vector polygon map
+<div class="code"><pre>
+ r.watershed elev=elevation.dem basin=rwater.basin thresh=15000
+ r.to.vect -s in=rwater.basin out=rwater_basins feature=area
+ v.db.dropcol map=rwater_basins column=label
+ v.db.renamecol map=rwater_basins column=value,catchment
+</pre></div>
+<br>
+
+<p>
+Display output in a nice way
+<div class="code"><pre>
+ r.shaded.relief map=elevation.dem
+ d.shadedmap rel=elevation.dem.shade drape=rwater.basin bright=40
+ d.vect rwater_course color=orange
+</pre></div>
+<br>
+
+<a name="references"></a>
+<h2>REFERENCES</h2>
+
+
+Ehlschlaeger, C. (1989). <i>Using the A<sup>T</sup> Search Algorithm
+to Develop Hydrologic Models from Digital Elevation Data</i>,
+<b>Proceedings of International Geographic Information Systems (IGIS)
+Symposium '89</b>, pp 275-281 (Baltimore, MD, 18-19 March 1989).<br>
+URL: <a href="http://faculty.wiu.edu/CR-Ehlschlaeger2/older/IGIS/paper.html">
+http://faculty.wiu.edu/CR-Ehlschlaeger2/older/IGIS/paper.html</a>
+
+<p>
+Kinner D., H. Mitasova, R. Harmon, L. Toma, R., Stallard. (2005).
+<i>GIS-based Stream Network Analysis for The Chagres River Basin,
+Republic of Panama</i>. <b>The Rio Chagres: A Multidisciplinary Profile of
+a Tropical Watershed</b>, R. Harmon (Ed.), Springer/Kluwer, p.83-95.<br>
+URL: <a href="http://skagit.meas.ncsu.edu/%7Ehelena/measwork/panama/panama.html">
+http://skagit.meas.ncsu.edu/~helena/measwork/panama/panama.html</a>
+
+<p>
+McCool et al. (1987). <i>Revised Slope Steepness Factor for the Universal
+Soil Loss Equation</i>, <b>Transactions of the ASAE</b> Vol 30(5).
+
+<p>
+Weltz M. A., K. G. Renard, J. R. Simanton (1987). <i>Revised Universal Soil
+Loss Equation for Western Rangelands</i>, <b>U.S.A./Mexico Symposium of
+Strategies for Classification and Management of Native Vegetation for
+Food Production In Arid Zones</b> (Tucson, AZ, 12-16 Oct. 1987).
+
+<a name="seealso"></a>
+<h2>SEE ALSO</h2>
+
+<em>
+<a href="g.region.html">g.region</a>,
+<a href="r.cost.html">r.cost</a>,
+<a href="r.drain.html">r.drain</a>,
+<a href="r.flow.html">r.flow</a>,
+<!-- <a href="r.flowmd.html">r.flowmd</a>, -->
+<a href="r.neighbors.html">r.neighbors</a>,
+<a href="r.param.scale.html">r.param.scale</a>,
+<a href="r.resamp.interp.html">r.resamp.interp</a>,
+<a href="r.terraflow.html">r.terraflow</a>,
+<a href="r.topidx.html">r.topidx</a>,
+<a href="r.water.outlet.html">r.water.outlet</a>
+</em>
+
+
+<h2>AUTHOR</h2>
+
+Charles Ehlschlaeger, U.S. Army Construction Engineering Research Laboratory
+<p>
+<i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.what/description.html
===================================================================
--- grass/trunk/raster/r.what/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.what/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,145 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>r.what</em> outputs the category values and (optionally) the category
-labels associated with user-specified locations on raster input map(s).
-Locations are specified as geographic x,y coordinate pairs (i.e., pair of
-eastings and northings); the user can also (optionally) associate a label
-with each location.
-
-<p>
-The input coordinates can be entered directly on the command line, or
-redirected via <tt>stdin</tt> from an input text file, script, or piped from
-another program (like <em><a href="d.where.html">d.where</a></em>).
-<p>
-If none of the above input methods are used and the module is run from the
-terminal prompt, the program will interactively query the user for point
-locations and labels.
-<p>
-Each line of the input consists of an easting, a northing, and an optional
-label, which are separated by spaces. In interactive mode, the word
-"<tt>end</tt>" must be typed after the last pair of input coordinates.
-<p>
-<em>r.what</em> output consists of the input geographic location and label,
-and, for each user-named raster map layer, the category value, and (if
-the <b>-f</b> label flag is specified) the category label associated with
-the cell(s) at this geographic location.
-
-
-<h2>EXAMPLES</h2>
-
-
-<h4>Input from <tt>stdin</tt> on the command line</h4>
-
-Input coordinates may be given directly from <tt>stdin</tt>, for example:
-<br> (input data appears between the "<tt>EOF</tt>" markers)
-
-<div class="code"><pre>
-r.what input=soils,aspect << EOF
-635342.21 7654321.09 site 1
-653324.88 7563412.42 site 2
-EOF
-
-635342.21|7654321.09|site 1|45|21
-653324.88|7563412.42|site 2|44|20
-</pre></div>
-
-<div class="code"><pre>
-echo "635342.21 7654321.09" | r.what input=soils,aspect
-
-635342.21|7654321.09|45|21
-</pre></div>
-
-
-<h4>Input from a text file containing coordinates</h4>
-
-The contents of an ASCII text file can be redirected to <em>r.what</em>
-as follows. If we have a file called <i>input_coord.txt</i> containing the
-coordinates and labels given in the example above:
-
-<div class="code"><pre>
-r.what input=soils,aspect < input_coord.txt
-
-635342.21|7654321.09|site 1|45|21
-653324.88|7563412.42|site 2|44|20
-</pre></div>
-
-
-<h4>Input coordinates given as a module option</h4>
-
-The module's <b>east_north</b> parameter can be used to enter coordinate
-pairs directly. The maximum number of pairs will be limited by your system's
-maximum input line length (e.g. 4096 characters).
-
-<div class="code"><pre>
-r.what input=soils,aspect east_north=635342.21,7654321.09,653324.88,7563412.42
-
-635342.21|7654321.09|45|21
-653324.88|7563412.42|44|20
-</pre></div>
-
-
-<h4>Input coordinates piped from another program</h4>
-
-The input coordinates may be "piped" from the <tt>stdout</tt> of another program.
-For example:
-
-<div class="code"><pre>
-d.where | r.what input=soils,aspect
-
-635342.21|7654321.09|45|21
-653324.88|7563412.42|44|20
-</pre></div>
-
-In the next example, vector point coordinates are piped from the
-<em>v.out.ascii</em> module . The standard UNIX program "<tt>tr</tt>" is
-used to convert the column separators in <em>v.out.ascii</em>'s output into
-spaces for <em>r.what</em>.
-
-
-<div class="code"><pre>
-v.out.ascii bugsites fs=' ' | r.what input=soils,aspect
-</pre></div>
-
-<h4>Output containing raster map category labels</h4>
-
-Here we use the <b>-f</b> label flag to enable the output of category labels
-associated with the raster cell(s), as well as values. (categorical maps only)
-
-<div class="code"><pre>
-r.what -f input=soils,aspect << EOF
-635342.21 7654321.09 site 1
-653324.88 7563412.42 site 2
-EOF
-
-635342.21|7654321.09|site 1|45|NaC|21|30 degrees NW
-653324.88|7563412.42|site 2|44|NdC|20|15 degrees NW
-</pre></div>
-
-
-
-<h2>NOTE</h2>
-
-The maximum number of raster map layers that can be queried at one time is 150.
-<!-- as given by raster/r.what/main.c "#define NFILES 150" -->
-
-
-<h2>SEE ALSO</h2>
-
-<em>
-<a href="d.where.html">d.where</a>,
-<a href="r.category.html">r.category</a>,
-<a href="r.report.html">r.report</a>,
-<a href="r.stats.html">r.stats</a>,
-<a href="r.series.html">r.series</a>,
-<a href="r.univar.html">r.univar</a>,
-<a href="v.what.html">v.what</a>,
-<a href="v.what.rast.html">v.what.rast</a>,
-<a href="v.what.vect.html">v.what.vect</a>
-</em>
-
-<h2>AUTHOR</h2>
-Michael Shapiro,
-U.S. Army Construction Engineering Research Laboratory
-
-<p>
-<i>Last changed: $Date$</i>
Copied: grass/trunk/raster/r.what/r.what.html (from rev 32770, grass/trunk/raster/r.what/description.html)
===================================================================
--- grass/trunk/raster/r.what/r.what.html (rev 0)
+++ grass/trunk/raster/r.what/r.what.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,145 @@
+<h2>DESCRIPTION</h2>
+
+<em>r.what</em> outputs the category values and (optionally) the category
+labels associated with user-specified locations on raster input map(s).
+Locations are specified as geographic x,y coordinate pairs (i.e., pair of
+eastings and northings); the user can also (optionally) associate a label
+with each location.
+
+<p>
+The input coordinates can be entered directly on the command line, or
+redirected via <tt>stdin</tt> from an input text file, script, or piped from
+another program (like <em><a href="d.where.html">d.where</a></em>).
+<p>
+If none of the above input methods are used and the module is run from the
+terminal prompt, the program will interactively query the user for point
+locations and labels.
+<p>
+Each line of the input consists of an easting, a northing, and an optional
+label, which are separated by spaces. In interactive mode, the word
+"<tt>end</tt>" must be typed after the last pair of input coordinates.
+<p>
+<em>r.what</em> output consists of the input geographic location and label,
+and, for each user-named raster map layer, the category value, and (if
+the <b>-f</b> label flag is specified) the category label associated with
+the cell(s) at this geographic location.
+
+
+<h2>EXAMPLES</h2>
+
+
+<h4>Input from <tt>stdin</tt> on the command line</h4>
+
+Input coordinates may be given directly from <tt>stdin</tt>, for example:
+<br> (input data appears between the "<tt>EOF</tt>" markers)
+
+<div class="code"><pre>
+r.what input=soils,aspect << EOF
+635342.21 7654321.09 site 1
+653324.88 7563412.42 site 2
+EOF
+
+635342.21|7654321.09|site 1|45|21
+653324.88|7563412.42|site 2|44|20
+</pre></div>
+
+<div class="code"><pre>
+echo "635342.21 7654321.09" | r.what input=soils,aspect
+
+635342.21|7654321.09|45|21
+</pre></div>
+
+
+<h4>Input from a text file containing coordinates</h4>
+
+The contents of an ASCII text file can be redirected to <em>r.what</em>
+as follows. If we have a file called <i>input_coord.txt</i> containing the
+coordinates and labels given in the example above:
+
+<div class="code"><pre>
+r.what input=soils,aspect < input_coord.txt
+
+635342.21|7654321.09|site 1|45|21
+653324.88|7563412.42|site 2|44|20
+</pre></div>
+
+
+<h4>Input coordinates given as a module option</h4>
+
+The module's <b>east_north</b> parameter can be used to enter coordinate
+pairs directly. The maximum number of pairs will be limited by your system's
+maximum input line length (e.g. 4096 characters).
+
+<div class="code"><pre>
+r.what input=soils,aspect east_north=635342.21,7654321.09,653324.88,7563412.42
+
+635342.21|7654321.09|45|21
+653324.88|7563412.42|44|20
+</pre></div>
+
+
+<h4>Input coordinates piped from another program</h4>
+
+The input coordinates may be "piped" from the <tt>stdout</tt> of another program.
+For example:
+
+<div class="code"><pre>
+d.where | r.what input=soils,aspect
+
+635342.21|7654321.09|45|21
+653324.88|7563412.42|44|20
+</pre></div>
+
+In the next example, vector point coordinates are piped from the
+<em>v.out.ascii</em> module . The standard UNIX program "<tt>tr</tt>" is
+used to convert the column separators in <em>v.out.ascii</em>'s output into
+spaces for <em>r.what</em>.
+
+
+<div class="code"><pre>
+v.out.ascii bugsites fs=' ' | r.what input=soils,aspect
+</pre></div>
+
+<h4>Output containing raster map category labels</h4>
+
+Here we use the <b>-f</b> label flag to enable the output of category labels
+associated with the raster cell(s), as well as values. (categorical maps only)
+
+<div class="code"><pre>
+r.what -f input=soils,aspect << EOF
+635342.21 7654321.09 site 1
+653324.88 7563412.42 site 2
+EOF
+
+635342.21|7654321.09|site 1|45|NaC|21|30 degrees NW
+653324.88|7563412.42|site 2|44|NdC|20|15 degrees NW
+</pre></div>
+
+
+
+<h2>NOTE</h2>
+
+The maximum number of raster map layers that can be queried at one time is 150.
+<!-- as given by raster/r.what/main.c "#define NFILES 150" -->
+
+
+<h2>SEE ALSO</h2>
+
+<em>
+<a href="d.where.html">d.where</a>,
+<a href="r.category.html">r.category</a>,
+<a href="r.report.html">r.report</a>,
+<a href="r.stats.html">r.stats</a>,
+<a href="r.series.html">r.series</a>,
+<a href="r.univar.html">r.univar</a>,
+<a href="v.what.html">v.what</a>,
+<a href="v.what.rast.html">v.what.rast</a>,
+<a href="v.what.vect.html">v.what.vect</a>
+</em>
+
+<h2>AUTHOR</h2>
+Michael Shapiro,
+U.S. Army Construction Engineering Research Laboratory
+
+<p>
+<i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/r.what.color/description.html
===================================================================
--- grass/trunk/raster/r.what.color/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/r.what.color/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,76 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>r.what.color</em> outputs the color associated with user-specified
-category values in a raster input map.
-<p>
-Values may be specified either using the <b>values=</b> option, or by
-specifying the <b>-i</b> flag and passing the values on
-<tt>stdin</tt>, one per line.
-<p>
-For each value which is specified, a line of output will be generated
-consisting of the category value followed by the color, e.g.:
-
-<div class="code"><pre>
-r.what.color input=elevation.dem value=1500
-1500: 223:127:31
-</pre></div>
-
-<p>
-If the input map is an integer (CELL) map, the category will be
-written as an integer (no decimal point), otherwise it will be written
-in floating point format (<i>printf("%f")</i> format).
-
-<p>
-If the lookup fails for a value, the color will be output as an
-asterisk, e.g.:
-
-<div class="code"><pre>
-r.what.color input=elevation.dem value=9999
-9999: *
-</pre></div>
-
-<p>
-If a value cannot be parsed, both the value and the color will be
-output as an asterisk, e.g.:
-
-<div class="code"><pre>
-r.what.color input=elevation.dem value=bogus
-*: *
-</pre></div>
-
-<p>
-The format can be changed using the <b>format=</b> option. The value
-should be a <i>printf()</i>-style format string containing three
-conversion specifiers for the red, green and blue values respectively,
-e.g.:
-
-<div class="code"><pre>
-r.what.color input=elevation.dem value=1500 format='%02x:%02x:%02x'
-1500: df:7f:1f
-</pre></div>
-
-<p>
-If your system supports the <i>%m$</i> syntax, you can change the
-ordering of the components, e.g.:
-
-<div class="code"><pre>
-r.what.color input=elevation.dem value=1500 format='%3$02x:%2$02x:%1$02x'
-1500: 1f:7f:df
-</pre></div>
-
-<p>
-Common formats:<br>
-<ul>
-<li>Tcl/Tk: <tt>format="#%02x%02x%02x"</tt>
-<li>WxPython: <tt>format='"#%02x%02x%02x"'</tt> or <tt>format='"(%d,%d,%d)"'</tt>
-</ul>
-
-
-<h2>SEE ALSO</h2>
-
-<em>
-<a href="r.what.html">r.what</a>
-</em>
-
-<h2>AUTHOR</h2>
-Glynn Clements
Copied: grass/trunk/raster/r.what.color/r.what.color.html (from rev 32770, grass/trunk/raster/r.what.color/description.html)
===================================================================
--- grass/trunk/raster/r.what.color/r.what.color.html (rev 0)
+++ grass/trunk/raster/r.what.color/r.what.color.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,76 @@
+<h2>DESCRIPTION</h2>
+
+<em>r.what.color</em> outputs the color associated with user-specified
+category values in a raster input map.
+<p>
+Values may be specified either using the <b>values=</b> option, or by
+specifying the <b>-i</b> flag and passing the values on
+<tt>stdin</tt>, one per line.
+<p>
+For each value which is specified, a line of output will be generated
+consisting of the category value followed by the color, e.g.:
+
+<div class="code"><pre>
+r.what.color input=elevation.dem value=1500
+1500: 223:127:31
+</pre></div>
+
+<p>
+If the input map is an integer (CELL) map, the category will be
+written as an integer (no decimal point), otherwise it will be written
+in floating point format (<i>printf("%f")</i> format).
+
+<p>
+If the lookup fails for a value, the color will be output as an
+asterisk, e.g.:
+
+<div class="code"><pre>
+r.what.color input=elevation.dem value=9999
+9999: *
+</pre></div>
+
+<p>
+If a value cannot be parsed, both the value and the color will be
+output as an asterisk, e.g.:
+
+<div class="code"><pre>
+r.what.color input=elevation.dem value=bogus
+*: *
+</pre></div>
+
+<p>
+The format can be changed using the <b>format=</b> option. The value
+should be a <i>printf()</i>-style format string containing three
+conversion specifiers for the red, green and blue values respectively,
+e.g.:
+
+<div class="code"><pre>
+r.what.color input=elevation.dem value=1500 format='%02x:%02x:%02x'
+1500: df:7f:1f
+</pre></div>
+
+<p>
+If your system supports the <i>%m$</i> syntax, you can change the
+ordering of the components, e.g.:
+
+<div class="code"><pre>
+r.what.color input=elevation.dem value=1500 format='%3$02x:%2$02x:%1$02x'
+1500: 1f:7f:df
+</pre></div>
+
+<p>
+Common formats:<br>
+<ul>
+<li>Tcl/Tk: <tt>format="#%02x%02x%02x"</tt>
+<li>WxPython: <tt>format='"#%02x%02x%02x"'</tt> or <tt>format='"(%d,%d,%d)"'</tt>
+</ul>
+
+
+<h2>SEE ALSO</h2>
+
+<em>
+<a href="r.what.html">r.what</a>
+</em>
+
+<h2>AUTHOR</h2>
+Glynn Clements
Deleted: grass/trunk/raster/simwe/r.sim.sediment/description.html
===================================================================
--- grass/trunk/raster/simwe/r.sim.sediment/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/simwe/r.sim.sediment/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,100 +0,0 @@
-<h2>DESCRIPTION</h2>
-<i>r.sim.sediment</i> is a landscape scale, simulation
-model of soil erosion, sediment transport and deposition caused by flowing
-water designed for spatially variable terrain, soil, cover and
-rainfall excess conditions. The soil erosion model is based on the theory
-used in the USDA WEPP hillslope erosion model, but it has been generalized
-to 2D flow. The solution is based on the concept of duality between fields and
-particles and the underlying equations are solved by Green's
-function Monte Carlo method, to provide robustness necessary for
-spatially variable conditions and high resolutions (Mitas and Mitasova
-1998). Key inputs of the model include the following raster maps:
- elevation (<i> elevin</i> [m]), flow gradient given by the first-order partial
-derivatives of elevation field (<i> dxin</i> and <i>dyin</i>),
-overland flow water depth (<i> wdepth</i> [m]), detachment capacity coefficient
-(<i>detin</i> [s/m]), transport capacity coefficient (<i>tranin</i> [s]),
-critical shear stress (<i>tauin</i> [Pa])
-and surface roughness coefficient called Manning's n (<i>manin</i> raster map).
-Partial derivatives can be computed by <a href="v.surf.rst.html">v.surf.rst</a>
-or <a href="r.slope.aspect.html">r.slope.aspect</a>
-module. The data are automatically converted from feet to metric
-system using database/projection information, so the elevation always should be in meters.
-The water depth file can be computed using <a href="r.sim.water.html">r.sim.water</a>
-module. Other parameters must be determined using field measurements or
-reference literature (see suggested values in Notes and References). <br>
-
-<p>
-Output includes transport capacity raster map <i>tc</i> in [kg/ms],
-transport capacity limited erosion/deposition raster map
-<i>et</i> [kg/m<sup>2</sup>s]i that are output almost immediately and
-can be viewed while the simulation continues. Sediment flow rate raster map
-<i>flux</i> [kg/ms], and net erosion/deposition raster map [kg/m<sup>2</sup>s]
-can take longer time depending on time step and simulation time.
-Simulation time is controled by <i> niter</i> [minutes] parameter.
-<!-- Output files can be saved during simulation using <i>outiter</i> parameter
-defining simulation time step for writing output files. This option requires
-time series flag <i>-t</i>. Files are saved with suffix containing
-iteration number (e.g. name.500, name.1000, etc.) representing time in seconds.
--->
-If the resulting erosion/deposition map is noisy, higher number of walkers,
-given by <i>nwalk</i> should be used.
-<br>
-
-<h2>NOTES</h2>
-<!--provide a table of suggested parameters for bare soil, grass, forest, pavement
-wetland or pond, provide links to movies that explain the impact of the parameters-->
-
-
-<h2>SEE ALSO</h2>
-<a href="v.surf.rst.html">v.surf.rst</a>,
-<a href="r.slope.aspect.html">r.slope.aspect</a>,
-<a href="r.sim.water.html">r.sim.water</a>
-
-<h2>
-AUTHORS</h2>
- Helena Mitasova, Lubos Mitas<br>
-North Carolina State University<br>
-<a href="mailto:hmitaso at unity.ncsu.edu">hmitaso at unity.ncsu.edu</a><br>
-<br>
-Jaroslav Hofierka<br>
-GeoModel, s.r.o. Bratislava, Slovakia<br><address>
-<a href="mailto:hofi at geomodel.sk">
-hofierka at geomodel.sk</a>
-</address>
-<br>
-Chris Thaxton<br>
-North Carolina State University<br>
-csthaxto at unity.ncsu.edu<br>
-<address><a href="mailto:csthaxto at unity.ncsu.edu">
-csthaxto at unity.ncsu.edu</a></address>
-<h2>
-REFERENCES</h2>
-<P>
-<a href="http://skagit.meas.ncsu.edu/~helena/gmslab/papers/II.6.8_Mitasova_044.pdf">
-Mitasova, H., Thaxton, C., Hofierka, J., McLaughlin, R., Moore, A., Mitas L., 2004,</a>
-Path sampling method for modeling overland water flow, sediment transport
-and short term terrain evolution in Open Source GIS.
-In: C.T. Miller, M.W. Farthing, V.G. Gray, G.F. Pinder eds.,
-Proceedings of the XVth International Conference on Computational Methods in Water
-Resources (CMWR XV), June 13-17 2004, Chapel Hill, NC, USA, Elsevier, pp. 1479-1490.
-<P>
-<a href="http://skagit.meas.ncsu.edu/~helena/gmslab/gisc00/duality.html">
-Mitasova H, Mitas, L., 2000, Modeling spatial processes in multiscale framework:
-exploring duality between particles and fields, </a>
-plenary talk at GIScience2000 conference, Savannah, GA.
-<P>
-Mitas, L., and Mitasova, H., 1998, Distributed soil erosion simulation
-for effective erosion prevention. Water Resources Research, 34(3), 505-516.
-<P>
-<a href="http://skagit.meas.ncsu.edu/~helena/gmslab/papers/LLEmiterev1.pdf">
- Mitasova, H., Mitas, L., 2001, Multiscale soil erosion simulations for land use management, </a>
-In: Landscape erosion and landscape evolution modeling, Harmon R. and Doe W. eds.,
-Kluwer Academic/Plenum Publishers, pp. 321-347.
-<p>
-<a href="http://www.grassbook.org">
-Neteler, M. and Mitasova, H., 2008, Open Source GIS: A GRASS GIS Approach. Third Edition.</a>
-The International Series in Engineering and Computer Science: Volume 773. Springer New York Inc, p. 406.
-<P>
-<p><br>
-Last changed: $Date$</p>
-
Copied: grass/trunk/raster/simwe/r.sim.sediment/r.sim.sediment.html (from rev 32770, grass/trunk/raster/simwe/r.sim.sediment/description.html)
===================================================================
--- grass/trunk/raster/simwe/r.sim.sediment/r.sim.sediment.html (rev 0)
+++ grass/trunk/raster/simwe/r.sim.sediment/r.sim.sediment.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,100 @@
+<h2>DESCRIPTION</h2>
+<i>r.sim.sediment</i> is a landscape scale, simulation
+model of soil erosion, sediment transport and deposition caused by flowing
+water designed for spatially variable terrain, soil, cover and
+rainfall excess conditions. The soil erosion model is based on the theory
+used in the USDA WEPP hillslope erosion model, but it has been generalized
+to 2D flow. The solution is based on the concept of duality between fields and
+particles and the underlying equations are solved by Green's
+function Monte Carlo method, to provide robustness necessary for
+spatially variable conditions and high resolutions (Mitas and Mitasova
+1998). Key inputs of the model include the following raster maps:
+ elevation (<i> elevin</i> [m]), flow gradient given by the first-order partial
+derivatives of elevation field (<i> dxin</i> and <i>dyin</i>),
+overland flow water depth (<i> wdepth</i> [m]), detachment capacity coefficient
+(<i>detin</i> [s/m]), transport capacity coefficient (<i>tranin</i> [s]),
+critical shear stress (<i>tauin</i> [Pa])
+and surface roughness coefficient called Manning's n (<i>manin</i> raster map).
+Partial derivatives can be computed by <a href="v.surf.rst.html">v.surf.rst</a>
+or <a href="r.slope.aspect.html">r.slope.aspect</a>
+module. The data are automatically converted from feet to metric
+system using database/projection information, so the elevation always should be in meters.
+The water depth file can be computed using <a href="r.sim.water.html">r.sim.water</a>
+module. Other parameters must be determined using field measurements or
+reference literature (see suggested values in Notes and References). <br>
+
+<p>
+Output includes transport capacity raster map <i>tc</i> in [kg/ms],
+transport capacity limited erosion/deposition raster map
+<i>et</i> [kg/m<sup>2</sup>s]i that are output almost immediately and
+can be viewed while the simulation continues. Sediment flow rate raster map
+<i>flux</i> [kg/ms], and net erosion/deposition raster map [kg/m<sup>2</sup>s]
+can take longer time depending on time step and simulation time.
+Simulation time is controled by <i> niter</i> [minutes] parameter.
+<!-- Output files can be saved during simulation using <i>outiter</i> parameter
+defining simulation time step for writing output files. This option requires
+time series flag <i>-t</i>. Files are saved with suffix containing
+iteration number (e.g. name.500, name.1000, etc.) representing time in seconds.
+-->
+If the resulting erosion/deposition map is noisy, higher number of walkers,
+given by <i>nwalk</i> should be used.
+<br>
+
+<h2>NOTES</h2>
+<!--provide a table of suggested parameters for bare soil, grass, forest, pavement
+wetland or pond, provide links to movies that explain the impact of the parameters-->
+
+
+<h2>SEE ALSO</h2>
+<a href="v.surf.rst.html">v.surf.rst</a>,
+<a href="r.slope.aspect.html">r.slope.aspect</a>,
+<a href="r.sim.water.html">r.sim.water</a>
+
+<h2>
+AUTHORS</h2>
+ Helena Mitasova, Lubos Mitas<br>
+North Carolina State University<br>
+<a href="mailto:hmitaso at unity.ncsu.edu">hmitaso at unity.ncsu.edu</a><br>
+<br>
+Jaroslav Hofierka<br>
+GeoModel, s.r.o. Bratislava, Slovakia<br><address>
+<a href="mailto:hofi at geomodel.sk">
+hofierka at geomodel.sk</a>
+</address>
+<br>
+Chris Thaxton<br>
+North Carolina State University<br>
+csthaxto at unity.ncsu.edu<br>
+<address><a href="mailto:csthaxto at unity.ncsu.edu">
+csthaxto at unity.ncsu.edu</a></address>
+<h2>
+REFERENCES</h2>
+<P>
+<a href="http://skagit.meas.ncsu.edu/~helena/gmslab/papers/II.6.8_Mitasova_044.pdf">
+Mitasova, H., Thaxton, C., Hofierka, J., McLaughlin, R., Moore, A., Mitas L., 2004,</a>
+Path sampling method for modeling overland water flow, sediment transport
+and short term terrain evolution in Open Source GIS.
+In: C.T. Miller, M.W. Farthing, V.G. Gray, G.F. Pinder eds.,
+Proceedings of the XVth International Conference on Computational Methods in Water
+Resources (CMWR XV), June 13-17 2004, Chapel Hill, NC, USA, Elsevier, pp. 1479-1490.
+<P>
+<a href="http://skagit.meas.ncsu.edu/~helena/gmslab/gisc00/duality.html">
+Mitasova H, Mitas, L., 2000, Modeling spatial processes in multiscale framework:
+exploring duality between particles and fields, </a>
+plenary talk at GIScience2000 conference, Savannah, GA.
+<P>
+Mitas, L., and Mitasova, H., 1998, Distributed soil erosion simulation
+for effective erosion prevention. Water Resources Research, 34(3), 505-516.
+<P>
+<a href="http://skagit.meas.ncsu.edu/~helena/gmslab/papers/LLEmiterev1.pdf">
+ Mitasova, H., Mitas, L., 2001, Multiscale soil erosion simulations for land use management, </a>
+In: Landscape erosion and landscape evolution modeling, Harmon R. and Doe W. eds.,
+Kluwer Academic/Plenum Publishers, pp. 321-347.
+<p>
+<a href="http://www.grassbook.org">
+Neteler, M. and Mitasova, H., 2008, Open Source GIS: A GRASS GIS Approach. Third Edition.</a>
+The International Series in Engineering and Computer Science: Volume 773. Springer New York Inc, p. 406.
+<P>
+<p><br>
+Last changed: $Date$</p>
+
Deleted: grass/trunk/raster/simwe/r.sim.water/description.html
===================================================================
--- grass/trunk/raster/simwe/r.sim.water/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/simwe/r.sim.water/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,172 +0,0 @@
-<h2>DESCRIPTION</h2>
-<i>r.sim.water</i> is a landscape scale simulation model
-of overland flow designed for spatially variable terrain, soil, cover
-and rainfall excess conditions. A 2D shallow water flow is described by
-the bivariate form of Saint Venant equations. The numerical solution is based
-on the concept of duality between the field and particle representation of
-the modeled quantity. Green's function Monte Carlo method, used to solve the equation,
-provides robustness necessary for spatially variable conditions and high
-resolutions (Mitas and Mitasova 1998). The key inputs of the model include
-elevation (<i>elevin</i> raster map), flow gradient vector given by
-first-order partial derivatives of elevation field (<i>dxin</i> and <i>dyin</i> raster maps), rainfall
-excess rate (<i>rain</i> raster map or <i>rain_val</i> single value)
-and a surface roughness coefficient given by Manning's n
-(<i>manin</i> raster map or <i>manin_val</i> single value). Partial
-derivatives raster maps can be computed along with interpolation of a DEM using
-the -d option in <a href="v.surf.rst.html">
-v.surf.rst</a> module. If elevation raster is already provided, partial derivatives
-can be computed using <a href="r.slope.aspect.html">r.slope.aspect</a> module.
-Partial derivatives are used to determine the direction and magnitude of water flow velocity.
-To include a predefined direction of flow, map algebra can be used
-to replace terrain-derived partial derivatives with pre-defined
-partial derivatives in selected grid cells such as man-made channels, ditches
-or culverts. Equations (2) and (3) from
-<a href="http://skagit.meas.ncsu.edu/~helena/gmslab/reports/cerl99/rep99.html">
-this report</a> can be used to compute partial derivates
-of the predefined flow using its direction given by aspect and slope.
-<br><p>
-The module automatically converts horizontal distances from feet to metric system using
-database/projection information. Rainfall excess is defined as rainfall intensity
-- infiltration rate and should be provided in [mm/hr].
-<!-- and can be computed using several available infiltration
-models (e.g. Green-Ampt, Holtan, etc.). (<font color="#ff0000"> find
-infiltration module in GRASS - topmodel, casc2d</font> )-->
- Rainfall intensities are usually available from meteorological stations.
-Infiltration rate depends on soil properties and land cover. It varies in space and time.
-For saturated soil and steady-state water flow it can be estimated using
-saturated hydraulic conductivity rates based on field measurements or using
-reference values which can be found in literature.
-Optionally, user can provide an overland flow infiltration rate map
-<i>infil</i> or a single value <i>infil_val</i> in [mm/hr]
-that control the rate of infiltration for the already flowing water, effectively
-reducing the flow depth and discharge.
-Overland flow can be further controled by permeable check dams or similar type of structures,
-the user can provide a map of these structures and their permeability ratio
-in the map <i>traps</i> that defines the probability of particles to pass
-through the structure (the values will be 0-1).
-<br> </p>
-<p>
-Output includes a water depth raster map <i>depth</i> in [m],
-anda water discharge raster map <i>disch</i> in [m3/s]. Error of the numerical
-solution can be analyzed using the <i>err</i> raster map (the resulting water depth is an average,
-and err is its RMSE). The output vector points map <i>outwalk</i> can be used to analyze and visualize
-spatial distribution of walkers at different simulation times (note that
-the resulting water depth is based on the density of these walkers). Number
-of the output walkers is controled by the <i>density</i> parameter, which controls
-how many walkers used in simulation should be written into the output.
-<!--(<font color="#ff0000"> toto treba upresnit/zmenit, lebo nwalk ide prec</font>). -->
-Duration of simulation is controled by the <i>niter</i> parameter. The default value
-is 10 minutes, reaching the steady-state may require much longer time,
-depending on the time step, complexity of terrain, land cover and size of the area.
-Output water depth and discharge maps can be saved during simulation using
-the time series flag <i>-t</i> and <i>outiter</i> parameter
-defining the time step in minutes for writing output files.
-Files are saved with a suffix representing time since the start of simulation in seconds
-(e.g. wdepth.500, wdepth.1000).<br>
-<P>
-Overland flow is routed based on partial derivatives of elevation
-field or other landscape features influencing water flow. Simulation
-equations include a diffusion term (<i>diffc</i> parameter) which enables
-water flow to overcome elevation depressions or obstacles when water depth exceeds
-a threshold water depth value (<i>hmax)</i>, given in [m]. When it is reached,
-diffusion term increases as given by <i>halpha</i> and advection term
-(direction of flow) is given as "prevailing" direction of flow computed
-as average of flow directions from the previous <i>hbeta</i> number of grid cells.
-<br>
-<h2>
-NOTES</h2>
-<p>
-A 2D shallow water flow is described by the bivariate form of Saint
-Venant equations (e.g., Julien et al., 1995). The continuity of water
-flow relation is coupled with the momentum conservation equation and
-for a shallow water overland flow, the hydraulic radius is approximated
-by the normal flow depth. The system of equations is closed using the
-Manning's relation. Model assumes that the flow is close to the kinematic
-wave approximation, but we include a diffusion-like term to incorporate the
-impact of diffusive wave effects. Such an incorporation of diffusion
-in the water flow simulation is not new and a similar term has been obtained
-in derivations of diffusion-advection equations for overland flow, e.g.,
- by Lettenmeier and Wood, (1992). In our reformulation, we simplify the
-diffusion coefficient to a constant and we use a modified diffusion term.
-The diffusion constant which we have used is rather small (approximately
-one order of magnitude smaller than the reciprocal Manning's coefficient)
-and therefore the resulting flow is close to the kinematic regime. However,
-the diffusion term improves the kinematic solution, by overcoming small
-shallow pits common in digital elevation models (DEM) and by smoothing out
-the flow over slope discontinuities or abrupt changes in Manning's coefficient
-(e.g., due to a road, or other anthropogenic changes in elevations or cover).
-</p>
-<p><b>
-Green's function stochastic method of solution.</b> The Saint Venant
-equations are solved by a stochastic method called Monte Carlo (very
-similar to Monte Carlo methods in computational fluid dynamics or to
-quantum Monte Carlo approaches for solving the Schrodinger equation (Schmidt
-and Ceperley, 1992, Hammond et al., 1994; Mitas, 1996)). It is assumed
-that these equations are a representation of stochastic processes with
-diffusion and drift components (Fokker-Planck equations). </p>
-The Monte Carlo technique has several unique advantages which are
-becoming even more important due to new developments in computer technology.
-Perhaps one of the most significant Monte Carlo properties is robustness
-which enables us to solve the equations for complex cases, such as discontinuities
-in the coefficients of differential operators (in our case, abrupt slope
-or cover changes, etc). Also, rough solutions can be estimated rather
-quickly, which allows us to carry out preliminary quantitative studies
-or to rapidly extract qualitative trends by parameter scans. In addition,
-the stochastic methods are tailored to the new generation of computers
-as they provide scalability from a single workstation to large parallel
-machines due to the independence of sampling points. Therefore, the methods
-are useful both for everyday exploratory work using a desktop computer and
-for large, cutting-edge applications using high performance computing. <br>
-<h2>
-SEE ALSO</h2>
-<a href="v.surf.rst.html">v.surf.rst</a>
-<a href="r.slope.aspect.html">r.slope.aspect</a>
-<a href="r.sim.sediment.html">r.sim.sediment</a>
-
-<h2>
-AUTHORS</h2>
-Helena Mitasova, Lubos Mitas<br>
-North Carolina State University<br>
-<a href="mailto:hmitaso at unity.ncsu.edu">hmitaso at unity.ncsu.edu</a><br>
-<br>
-Jaroslav Hofierka<br>
-GeoModel, s.r.o. Bratislava, Slovakia <br>
-<address><a href="mailto:hofi at geomodel.sk">
-hofierka at geomodel.sk</a>
-</address>
-<br>
-Chris Thaxton<br>
-North Carolina State University<br>
-csthaxto at unity.ncsu.edu<br>
-<address><a href="mailto:csthaxto at unity.ncsu.edu">
-csthaxto at unity.ncsu.edu</a>
-</address>
-<h2>
-REFERENCES</h2>
-<P>
-<a href="http://skagit.meas.ncsu.edu/~helena/gmslab/papers/II.6.8_Mitasova_044.pdf">
-Mitasova, H., Thaxton, C., Hofierka, J., McLaughlin, R., Moore, A., Mitas L., 2004,</a>
-Path sampling method for modeling overland water flow, sediment transport
-and short term terrain evolution in Open Source GIS.
-In: C.T. Miller, M.W. Farthing, V.G. Gray, G.F. Pinder eds.,
-Proceedings of the XVth International Conference on Computational Methods in Water
-Resources (CMWR XV), June 13-17 2004, Chapel Hill, NC, USA, Elsevier, pp. 1479-1490.
-<P>
-<a href="http://skagit.meas.ncsu.edu/~helena/gmslab/gisc00/duality.html">
-Mitasova H, Mitas, L., 2000, Modeling spatial processes in multiscale framework:
-exploring duality between particles and fields, </a>
-plenary talk at GIScience2000 conference, Savannah, GA.
-<P>
-Mitas, L., and Mitasova, H., 1998, Distributed soil erosion simulation
-for effective erosion prevention. Water Resources Research, 34(3), 505-516.
-<P>
-<a href="http://skagit.meas.ncsu.edu/~helena/gmslab/papers/LLEmiterev1.pdf">
- Mitasova, H., Mitas, L., 2001, Multiscale soil erosion simulations for land use management, </a>
-In: Landscape erosion and landscape evolution modeling, Harmon R. and Doe W. eds.,
-Kluwer Academic/Plenum Publishers, pp. 321-347.
-<p>
-<a href="http://www.grassbook.org">
-Neteler, M. and Mitasova, H., 2008, Open Source GIS: A GRASS GIS Approach. Third Edition.</a>
-The International Series in Engineering and Computer Science: Volume 773. Springer New York Inc, p. 406.
-<P>
-Last changed: Date: 2008/02/16 15:55:10 $<p></p>
Copied: grass/trunk/raster/simwe/r.sim.water/r.sim.water.html (from rev 32770, grass/trunk/raster/simwe/r.sim.water/description.html)
===================================================================
--- grass/trunk/raster/simwe/r.sim.water/r.sim.water.html (rev 0)
+++ grass/trunk/raster/simwe/r.sim.water/r.sim.water.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,172 @@
+<h2>DESCRIPTION</h2>
+<i>r.sim.water</i> is a landscape scale simulation model
+of overland flow designed for spatially variable terrain, soil, cover
+and rainfall excess conditions. A 2D shallow water flow is described by
+the bivariate form of Saint Venant equations. The numerical solution is based
+on the concept of duality between the field and particle representation of
+the modeled quantity. Green's function Monte Carlo method, used to solve the equation,
+provides robustness necessary for spatially variable conditions and high
+resolutions (Mitas and Mitasova 1998). The key inputs of the model include
+elevation (<i>elevin</i> raster map), flow gradient vector given by
+first-order partial derivatives of elevation field (<i>dxin</i> and <i>dyin</i> raster maps), rainfall
+excess rate (<i>rain</i> raster map or <i>rain_val</i> single value)
+and a surface roughness coefficient given by Manning's n
+(<i>manin</i> raster map or <i>manin_val</i> single value). Partial
+derivatives raster maps can be computed along with interpolation of a DEM using
+the -d option in <a href="v.surf.rst.html">
+v.surf.rst</a> module. If elevation raster is already provided, partial derivatives
+can be computed using <a href="r.slope.aspect.html">r.slope.aspect</a> module.
+Partial derivatives are used to determine the direction and magnitude of water flow velocity.
+To include a predefined direction of flow, map algebra can be used
+to replace terrain-derived partial derivatives with pre-defined
+partial derivatives in selected grid cells such as man-made channels, ditches
+or culverts. Equations (2) and (3) from
+<a href="http://skagit.meas.ncsu.edu/~helena/gmslab/reports/cerl99/rep99.html">
+this report</a> can be used to compute partial derivates
+of the predefined flow using its direction given by aspect and slope.
+<br><p>
+The module automatically converts horizontal distances from feet to metric system using
+database/projection information. Rainfall excess is defined as rainfall intensity
+- infiltration rate and should be provided in [mm/hr].
+<!-- and can be computed using several available infiltration
+models (e.g. Green-Ampt, Holtan, etc.). (<font color="#ff0000"> find
+infiltration module in GRASS - topmodel, casc2d</font> )-->
+ Rainfall intensities are usually available from meteorological stations.
+Infiltration rate depends on soil properties and land cover. It varies in space and time.
+For saturated soil and steady-state water flow it can be estimated using
+saturated hydraulic conductivity rates based on field measurements or using
+reference values which can be found in literature.
+Optionally, user can provide an overland flow infiltration rate map
+<i>infil</i> or a single value <i>infil_val</i> in [mm/hr]
+that control the rate of infiltration for the already flowing water, effectively
+reducing the flow depth and discharge.
+Overland flow can be further controled by permeable check dams or similar type of structures,
+the user can provide a map of these structures and their permeability ratio
+in the map <i>traps</i> that defines the probability of particles to pass
+through the structure (the values will be 0-1).
+<br> </p>
+<p>
+Output includes a water depth raster map <i>depth</i> in [m],
+anda water discharge raster map <i>disch</i> in [m3/s]. Error of the numerical
+solution can be analyzed using the <i>err</i> raster map (the resulting water depth is an average,
+and err is its RMSE). The output vector points map <i>outwalk</i> can be used to analyze and visualize
+spatial distribution of walkers at different simulation times (note that
+the resulting water depth is based on the density of these walkers). Number
+of the output walkers is controled by the <i>density</i> parameter, which controls
+how many walkers used in simulation should be written into the output.
+<!--(<font color="#ff0000"> toto treba upresnit/zmenit, lebo nwalk ide prec</font>). -->
+Duration of simulation is controled by the <i>niter</i> parameter. The default value
+is 10 minutes, reaching the steady-state may require much longer time,
+depending on the time step, complexity of terrain, land cover and size of the area.
+Output water depth and discharge maps can be saved during simulation using
+the time series flag <i>-t</i> and <i>outiter</i> parameter
+defining the time step in minutes for writing output files.
+Files are saved with a suffix representing time since the start of simulation in seconds
+(e.g. wdepth.500, wdepth.1000).<br>
+<P>
+Overland flow is routed based on partial derivatives of elevation
+field or other landscape features influencing water flow. Simulation
+equations include a diffusion term (<i>diffc</i> parameter) which enables
+water flow to overcome elevation depressions or obstacles when water depth exceeds
+a threshold water depth value (<i>hmax)</i>, given in [m]. When it is reached,
+diffusion term increases as given by <i>halpha</i> and advection term
+(direction of flow) is given as "prevailing" direction of flow computed
+as average of flow directions from the previous <i>hbeta</i> number of grid cells.
+<br>
+<h2>
+NOTES</h2>
+<p>
+A 2D shallow water flow is described by the bivariate form of Saint
+Venant equations (e.g., Julien et al., 1995). The continuity of water
+flow relation is coupled with the momentum conservation equation and
+for a shallow water overland flow, the hydraulic radius is approximated
+by the normal flow depth. The system of equations is closed using the
+Manning's relation. Model assumes that the flow is close to the kinematic
+wave approximation, but we include a diffusion-like term to incorporate the
+impact of diffusive wave effects. Such an incorporation of diffusion
+in the water flow simulation is not new and a similar term has been obtained
+in derivations of diffusion-advection equations for overland flow, e.g.,
+ by Lettenmeier and Wood, (1992). In our reformulation, we simplify the
+diffusion coefficient to a constant and we use a modified diffusion term.
+The diffusion constant which we have used is rather small (approximately
+one order of magnitude smaller than the reciprocal Manning's coefficient)
+and therefore the resulting flow is close to the kinematic regime. However,
+the diffusion term improves the kinematic solution, by overcoming small
+shallow pits common in digital elevation models (DEM) and by smoothing out
+the flow over slope discontinuities or abrupt changes in Manning's coefficient
+(e.g., due to a road, or other anthropogenic changes in elevations or cover).
+</p>
+<p><b>
+Green's function stochastic method of solution.</b> The Saint Venant
+equations are solved by a stochastic method called Monte Carlo (very
+similar to Monte Carlo methods in computational fluid dynamics or to
+quantum Monte Carlo approaches for solving the Schrodinger equation (Schmidt
+and Ceperley, 1992, Hammond et al., 1994; Mitas, 1996)). It is assumed
+that these equations are a representation of stochastic processes with
+diffusion and drift components (Fokker-Planck equations). </p>
+The Monte Carlo technique has several unique advantages which are
+becoming even more important due to new developments in computer technology.
+Perhaps one of the most significant Monte Carlo properties is robustness
+which enables us to solve the equations for complex cases, such as discontinuities
+in the coefficients of differential operators (in our case, abrupt slope
+or cover changes, etc). Also, rough solutions can be estimated rather
+quickly, which allows us to carry out preliminary quantitative studies
+or to rapidly extract qualitative trends by parameter scans. In addition,
+the stochastic methods are tailored to the new generation of computers
+as they provide scalability from a single workstation to large parallel
+machines due to the independence of sampling points. Therefore, the methods
+are useful both for everyday exploratory work using a desktop computer and
+for large, cutting-edge applications using high performance computing. <br>
+<h2>
+SEE ALSO</h2>
+<a href="v.surf.rst.html">v.surf.rst</a>
+<a href="r.slope.aspect.html">r.slope.aspect</a>
+<a href="r.sim.sediment.html">r.sim.sediment</a>
+
+<h2>
+AUTHORS</h2>
+Helena Mitasova, Lubos Mitas<br>
+North Carolina State University<br>
+<a href="mailto:hmitaso at unity.ncsu.edu">hmitaso at unity.ncsu.edu</a><br>
+<br>
+Jaroslav Hofierka<br>
+GeoModel, s.r.o. Bratislava, Slovakia <br>
+<address><a href="mailto:hofi at geomodel.sk">
+hofierka at geomodel.sk</a>
+</address>
+<br>
+Chris Thaxton<br>
+North Carolina State University<br>
+csthaxto at unity.ncsu.edu<br>
+<address><a href="mailto:csthaxto at unity.ncsu.edu">
+csthaxto at unity.ncsu.edu</a>
+</address>
+<h2>
+REFERENCES</h2>
+<P>
+<a href="http://skagit.meas.ncsu.edu/~helena/gmslab/papers/II.6.8_Mitasova_044.pdf">
+Mitasova, H., Thaxton, C., Hofierka, J., McLaughlin, R., Moore, A., Mitas L., 2004,</a>
+Path sampling method for modeling overland water flow, sediment transport
+and short term terrain evolution in Open Source GIS.
+In: C.T. Miller, M.W. Farthing, V.G. Gray, G.F. Pinder eds.,
+Proceedings of the XVth International Conference on Computational Methods in Water
+Resources (CMWR XV), June 13-17 2004, Chapel Hill, NC, USA, Elsevier, pp. 1479-1490.
+<P>
+<a href="http://skagit.meas.ncsu.edu/~helena/gmslab/gisc00/duality.html">
+Mitasova H, Mitas, L., 2000, Modeling spatial processes in multiscale framework:
+exploring duality between particles and fields, </a>
+plenary talk at GIScience2000 conference, Savannah, GA.
+<P>
+Mitas, L., and Mitasova, H., 1998, Distributed soil erosion simulation
+for effective erosion prevention. Water Resources Research, 34(3), 505-516.
+<P>
+<a href="http://skagit.meas.ncsu.edu/~helena/gmslab/papers/LLEmiterev1.pdf">
+ Mitasova, H., Mitas, L., 2001, Multiscale soil erosion simulations for land use management, </a>
+In: Landscape erosion and landscape evolution modeling, Harmon R. and Doe W. eds.,
+Kluwer Academic/Plenum Publishers, pp. 321-347.
+<p>
+<a href="http://www.grassbook.org">
+Neteler, M. and Mitasova, H., 2008, Open Source GIS: A GRASS GIS Approach. Third Edition.</a>
+The International Series in Engineering and Computer Science: Volume 773. Springer New York Inc, p. 406.
+<P>
+Last changed: Date: 2008/02/16 15:55:10 $<p></p>
Deleted: grass/trunk/raster/wildfire/r.ros/description.html
===================================================================
--- grass/trunk/raster/wildfire/r.ros/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/wildfire/r.ros/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,161 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-<P><I>r.ros</I> generates the base ROS value, maximum ROS value, direction
-of the maximum ROS, and optionally the maximum potential spotting distance
-of a wildfire for each raster cell in the current geographic region. The
-calculation of the two ROS values for each raster cell is based on the
-Fortran code by Pat Andrews (1983) of the Northern Forest Fire Laboratory,
-USDA Forest Service. The direction of the maximum ROS results from the
-vector addition of the forward ROS in wind direction and that in upslope
-direction. The spotting distance, if required, will be calculated by a
-separate function, spot_dist(), which is based on Lathrop and Xu (in preparation),
-Chase (1984) and Rothermel (1991). These three or four raster map layers
-serve as inputs for another GRASS raster program r.spread. More information
-on r.ros and r.spread can be found in Xu (1994).
-
-<H2>Parameters:</H2>
-<DL>
-<DT><B>model=</B>name
-<DD> Name of an
-existing raster map layer in the user's current mapset search path containing
-the standard fuel models defined by the USDA Forest Service. Valid values
-are 1-13; other numbers are recognized as barriers by r.ros.
-
-<DT><B>moisture_1h=</B>name
-<DD> Name of an existing raster map layer in
-the user's current mapset search path containing the 1-hour (<.25")
-fuel moisture (percentage content multiplied by 100).
-
-<DT><B>moisture_10h=</B>name
-<DD>Name of an existing raster map layer in the
-user's current mapset search path containing the 10-hour (.25-1") fuel
-moisture (percentage content multiplied by 100).
-
-<DT><B>moisture_100h=</B>name
-<DD>Name of an existing raster map layer in the
-user's current mapset search path containing the 100-hour (1-3") fuel moisture
-(percentage content multiplied by 100).
-
-<DT><B>moisture_live=</B>name
-<DD>Name of an existing raster map layer in the
-user's current mapset search path containing live (herbaceous) fuel fuel
-moisture (percentage content multiplied by 100).
-
-<DT><B>velocity=</B>name
-<DD>Name of an existing raster map layer in the user's
-current mapset search path containing wind velocities at half of the average
-flame height (feet/minute).
-
-<DT><B>direction=</B>name
-<DD>Name of an existing raster map
-layer in the user's current mapset search path containing wind direction,
-clockwise from north (degree).
-
-<DT><B>slope=</B>name
-<DD>Name of
-an existing raster map layer in the user's current mapset search path containing
-topographic slope (degree).
-
-<DT><B>aspect=</B>name
-<DD>Name of an existing
-raster map layer in the user's current mapset search path containing
-topographic aspect, counter-clockwise from east (GRASS convention)
-(degree).
-
-<DT><B>elevation=</B>name
-<DD>Name of an existing raster map
-layer in the user's current mapset search path containing elevation (meters).
-
-<DT><B>output=</B>name Prefix of new
-raster map layers in the user's current mapset to contain
-<BR> 1) the base (perpendicular) ROS
-(cm/minute);
-<BR> 2) the maximum (forward) ROS (cm/minute),
-<BR> 3) the direction of the maximum
-ROS, clockwise from north (degree), and optionally
-<BR> 4) the maximum potential
-spotting distance (meters).
-<BR>If 'my_ros' is given as the output name, then r.ros automatically
-assigns 'my_ros.base', 'my_ros.max', 'my_ros.maxdir', and optionally,
-'my_ros.spotdist' as the names for the actual output map layers.
-</DL>
-
-<H2>OPTIONS</H2>
-
-r.ros can be run either non-interactively or interactively. The program
-is run interactively if the user types r.ros without specifying flag settings
-and parameter values on the command line. In this case, the user will be
-prompted for input. The program will be run non-interactively if the user
-specifies the names of raster map layers and any desired options on the
-command line, using the form:
-<BR> r.ros [-vs] model=name [moisture_1h=name]
-[moisture_10h=name] [moisture_100h=name]
-moisture_live=name [velocity=name] [direction=name]
-[slope=name] [aspect=name] [elevation=name] output=name
-
-<P>If the options <B>moisture_1h=</B>name, <B>moisture_10h=</B>name, and
-<B>moisture_100h=</B>name are partially given, the program will assign
-values to the missing option using the formula:
-
-<P>
-moisture_100h = moisture_10h + 1 = moisture_1h + 2.
-
-<P>However at least one of them should be given. Options <B>velocity=</B>name
-and <B>direction=</B>name must be in pair, whether given or not. If none
-is given, the program will assume a no-wind condition. Options <B>slope=</B>name
-and <B>aspect=</B>name must be in pair, whether given or not. If none is
-given, the program will assume a topographically flat condition. Option
-<B>elevation=</B>name must be given if -s option is used.
-
-<H2>EXAMPLE</H2>
-Assume we have inputs, the following generates ROSes and spotting distances:
-
-<P>r.ros -vs model=fire_model moisture_1h=1hour_moisture moisture_live=live_moisture
-velocity=wind_speed direction=wind_direction
-slope=slope aspect=aspect elevation=elevation output=my_ros
-
-<H2>NOTES</H2>
-1. r.ros is supposed to be run before running another GRASS program r.spread.
-The combination of the two forms a simulation of the spread of wildfires.
-<BR>2. The inputs to r.ros should be in proper units.
-<BR>3. The output units for the base and maximum ROSes are in cm/minute
-rather than ft/minute, which is due to that a possible zero ft/minute base
-ROS value and a positive integer ft/minute maximum ROS would result in
-calculation failure in the r.spread program.
-<BR>4. The user needs to provide only ONE output name even the program
-actually generates THREE or FOUR map layers.
-<BR>5. The rules for optional parameters must be followed.
-
-<H2>SEE ALSO</H2>
-
-<EM><A HREF="g.region.html">g.region</A>,
-<!-- <A HREF="r.mask.html"> r.mask,</A> -->
-<A HREF="r.slope.aspect.html">r.slope.aspect</A>,
- <A HREF="r.spread.html">r.spread</A></EM>
-
-<H2>REFERENCES</H2>
-<B>Albini,</B> F. A., 1976, Computer-based models of wildland fire behavior:
-a user's manual, USDA Forest Service, Intermountain Forest and Range Experiment
-Station, Ogden, Utah.
-<BR><B>Andrews</B>, P. L., 1986, BEHAVE: fire behavior prediction and fuel
-modeling system -- BURN subsystem, Part 1, USDA Forest Service, Intermountain
-Research Station, Gen. Tech. Rep. INT-194, Ogden, Utah.
-<BR><B>Chase</B>, Carolyn, H., 1984, Spotting distance from wind-driven
-surface fires -- extensions of equations for pocket calculators, US Forest
-Service, Res. Note INT-346, Ogden, Utah.
-<BR><B>Lathrop</B>, Richard G. and Jianping Xu, A geographic information
-system-based approach for calculating spotting distance. (in preparation)
-<BR><B>Rothermel</B>, R. E., 1972, A mathematical model for predicting
-fire spread in wildland fuels, USDA Forest Service, Intermountain Forest
-and Range Experiment Station, Res. Pap. INT-115, Ogden, Utah.
-<BR><B>Rothermel</B>, Richard, 1991, Predicting behavior and size of crown
-fires in the northern Rocky Mountains, US Forest Service, Res. Paper INT-438,
-Ogden, Utah.
-<BR><B>Xu</B>, Jianping, 1994, Simulating the spread of wildfires using
-a geographic information system and remote sensing, Ph. D. Dissertation,
-Rutgers University, New Brunswick, New Jersey.
-
-<H2> AUTHOR</H2>
-Jianping Xu, Center for Remote Sensing and Spatial Analysis, Rutgers University.
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/raster/wildfire/r.ros/r.ros.html (from rev 32770, grass/trunk/raster/wildfire/r.ros/description.html)
===================================================================
--- grass/trunk/raster/wildfire/r.ros/r.ros.html (rev 0)
+++ grass/trunk/raster/wildfire/r.ros/r.ros.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,161 @@
+<H2>DESCRIPTION</H2>
+
+<P><I>r.ros</I> generates the base ROS value, maximum ROS value, direction
+of the maximum ROS, and optionally the maximum potential spotting distance
+of a wildfire for each raster cell in the current geographic region. The
+calculation of the two ROS values for each raster cell is based on the
+Fortran code by Pat Andrews (1983) of the Northern Forest Fire Laboratory,
+USDA Forest Service. The direction of the maximum ROS results from the
+vector addition of the forward ROS in wind direction and that in upslope
+direction. The spotting distance, if required, will be calculated by a
+separate function, spot_dist(), which is based on Lathrop and Xu (in preparation),
+Chase (1984) and Rothermel (1991). These three or four raster map layers
+serve as inputs for another GRASS raster program r.spread. More information
+on r.ros and r.spread can be found in Xu (1994).
+
+<H2>Parameters:</H2>
+<DL>
+<DT><B>model=</B>name
+<DD> Name of an
+existing raster map layer in the user's current mapset search path containing
+the standard fuel models defined by the USDA Forest Service. Valid values
+are 1-13; other numbers are recognized as barriers by r.ros.
+
+<DT><B>moisture_1h=</B>name
+<DD> Name of an existing raster map layer in
+the user's current mapset search path containing the 1-hour (<.25")
+fuel moisture (percentage content multiplied by 100).
+
+<DT><B>moisture_10h=</B>name
+<DD>Name of an existing raster map layer in the
+user's current mapset search path containing the 10-hour (.25-1") fuel
+moisture (percentage content multiplied by 100).
+
+<DT><B>moisture_100h=</B>name
+<DD>Name of an existing raster map layer in the
+user's current mapset search path containing the 100-hour (1-3") fuel moisture
+(percentage content multiplied by 100).
+
+<DT><B>moisture_live=</B>name
+<DD>Name of an existing raster map layer in the
+user's current mapset search path containing live (herbaceous) fuel fuel
+moisture (percentage content multiplied by 100).
+
+<DT><B>velocity=</B>name
+<DD>Name of an existing raster map layer in the user's
+current mapset search path containing wind velocities at half of the average
+flame height (feet/minute).
+
+<DT><B>direction=</B>name
+<DD>Name of an existing raster map
+layer in the user's current mapset search path containing wind direction,
+clockwise from north (degree).
+
+<DT><B>slope=</B>name
+<DD>Name of
+an existing raster map layer in the user's current mapset search path containing
+topographic slope (degree).
+
+<DT><B>aspect=</B>name
+<DD>Name of an existing
+raster map layer in the user's current mapset search path containing
+topographic aspect, counter-clockwise from east (GRASS convention)
+(degree).
+
+<DT><B>elevation=</B>name
+<DD>Name of an existing raster map
+layer in the user's current mapset search path containing elevation (meters).
+
+<DT><B>output=</B>name Prefix of new
+raster map layers in the user's current mapset to contain
+<BR> 1) the base (perpendicular) ROS
+(cm/minute);
+<BR> 2) the maximum (forward) ROS (cm/minute),
+<BR> 3) the direction of the maximum
+ROS, clockwise from north (degree), and optionally
+<BR> 4) the maximum potential
+spotting distance (meters).
+<BR>If 'my_ros' is given as the output name, then r.ros automatically
+assigns 'my_ros.base', 'my_ros.max', 'my_ros.maxdir', and optionally,
+'my_ros.spotdist' as the names for the actual output map layers.
+</DL>
+
+<H2>OPTIONS</H2>
+
+r.ros can be run either non-interactively or interactively. The program
+is run interactively if the user types r.ros without specifying flag settings
+and parameter values on the command line. In this case, the user will be
+prompted for input. The program will be run non-interactively if the user
+specifies the names of raster map layers and any desired options on the
+command line, using the form:
+<BR> r.ros [-vs] model=name [moisture_1h=name]
+[moisture_10h=name] [moisture_100h=name]
+moisture_live=name [velocity=name] [direction=name]
+[slope=name] [aspect=name] [elevation=name] output=name
+
+<P>If the options <B>moisture_1h=</B>name, <B>moisture_10h=</B>name, and
+<B>moisture_100h=</B>name are partially given, the program will assign
+values to the missing option using the formula:
+
+<P>
+moisture_100h = moisture_10h + 1 = moisture_1h + 2.
+
+<P>However at least one of them should be given. Options <B>velocity=</B>name
+and <B>direction=</B>name must be in pair, whether given or not. If none
+is given, the program will assume a no-wind condition. Options <B>slope=</B>name
+and <B>aspect=</B>name must be in pair, whether given or not. If none is
+given, the program will assume a topographically flat condition. Option
+<B>elevation=</B>name must be given if -s option is used.
+
+<H2>EXAMPLE</H2>
+Assume we have inputs, the following generates ROSes and spotting distances:
+
+<P>r.ros -vs model=fire_model moisture_1h=1hour_moisture moisture_live=live_moisture
+velocity=wind_speed direction=wind_direction
+slope=slope aspect=aspect elevation=elevation output=my_ros
+
+<H2>NOTES</H2>
+1. r.ros is supposed to be run before running another GRASS program r.spread.
+The combination of the two forms a simulation of the spread of wildfires.
+<BR>2. The inputs to r.ros should be in proper units.
+<BR>3. The output units for the base and maximum ROSes are in cm/minute
+rather than ft/minute, which is due to that a possible zero ft/minute base
+ROS value and a positive integer ft/minute maximum ROS would result in
+calculation failure in the r.spread program.
+<BR>4. The user needs to provide only ONE output name even the program
+actually generates THREE or FOUR map layers.
+<BR>5. The rules for optional parameters must be followed.
+
+<H2>SEE ALSO</H2>
+
+<EM><A HREF="g.region.html">g.region</A>,
+<!-- <A HREF="r.mask.html"> r.mask,</A> -->
+<A HREF="r.slope.aspect.html">r.slope.aspect</A>,
+ <A HREF="r.spread.html">r.spread</A></EM>
+
+<H2>REFERENCES</H2>
+<B>Albini,</B> F. A., 1976, Computer-based models of wildland fire behavior:
+a user's manual, USDA Forest Service, Intermountain Forest and Range Experiment
+Station, Ogden, Utah.
+<BR><B>Andrews</B>, P. L., 1986, BEHAVE: fire behavior prediction and fuel
+modeling system -- BURN subsystem, Part 1, USDA Forest Service, Intermountain
+Research Station, Gen. Tech. Rep. INT-194, Ogden, Utah.
+<BR><B>Chase</B>, Carolyn, H., 1984, Spotting distance from wind-driven
+surface fires -- extensions of equations for pocket calculators, US Forest
+Service, Res. Note INT-346, Ogden, Utah.
+<BR><B>Lathrop</B>, Richard G. and Jianping Xu, A geographic information
+system-based approach for calculating spotting distance. (in preparation)
+<BR><B>Rothermel</B>, R. E., 1972, A mathematical model for predicting
+fire spread in wildland fuels, USDA Forest Service, Intermountain Forest
+and Range Experiment Station, Res. Pap. INT-115, Ogden, Utah.
+<BR><B>Rothermel</B>, Richard, 1991, Predicting behavior and size of crown
+fires in the northern Rocky Mountains, US Forest Service, Res. Paper INT-438,
+Ogden, Utah.
+<BR><B>Xu</B>, Jianping, 1994, Simulating the spread of wildfires using
+a geographic information system and remote sensing, Ph. D. Dissertation,
+Rutgers University, New Brunswick, New Jersey.
+
+<H2> AUTHOR</H2>
+Jianping Xu, Center for Remote Sensing and Spatial Analysis, Rutgers University.
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/wildfire/r.spread/description.html
===================================================================
--- grass/trunk/raster/wildfire/r.spread/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/wildfire/r.spread/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,223 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-Spread phenomena usually show uneven movement over space. Such unevenness
-is due to two reasons:
-<BR>1) the uneven conditions from location to location, which can be called
-SPATIAL HETEROGENEITY, and
-<BR>2) the uneven conditions in different directions, which can be called
-ANISOTROPY.
-<BR>The anisotropy of spread occurs when any of the determining factors
-have directional components. For example, wind and topography cause anisotropic
-spread of wildfires.
-
-<P>One of the simplest spatial heterogeneous and anisotropic spread
-is elliptical spread, in which, each local spread shape can be thought
-as an ellipse. In a raster setting, cell centers are foci of the spread
-ellipses, and the spread phenomenon moves fastest toward apogees and slowest
-to perigees. The sizes and shapes of spread ellipses may vary cell by cell.
-So the overall spread shape is commonly not an ellipse.
-
-<P><I>r.spread </I>simulates elliptically anisotropic spread phenomena,
-given three raster map layers about ROS (base ROS, maximum ROS and direction
-of the maximum ROS) plus a raster map layer showing the starting sources.
-These ROS layers define unique ellipses for all cell locations in the current
-geographic region as if each cell center was a potential spread origin.
-For some wildfire spread, these ROS layers can be generated by another
-GRASS raster program r.ros. The actual locations reached by a spread event
-are constrained by the actual spread origins and the elapsed spread time.
-
-<P><I>r.spread </I>optionally produces raster maps to contain backlink
-UTM coordinates for each raster cell of the spread time map. The spread
-paths can be accurately traced based on the backlink information by another
-GRASS raster program r.spreadpath.
-
-<P>Part of the spotting function in r.spread is based on Chase (1984)
-and Rothermel (1983). More information on <I>r.spread</I>, <I><A HREF="r.ros.html">r.ros</A></I>
-and <I><A HREF="r.spreadpath.html">r.spreadpath</A></I> can be found in
-Xu (1994).
-
-<H2>Flags:</H2>
-<DL>
-
-<DT>-v
-<DD> Run verbosely, printing information about program progress to standard
-output.
-
-<DT>-d
-<DD> Display the "live" simulation on screen. A graphics window
-must be opened and selected before using this option.
-
-<DT>-s
-<DD> For wildfires, also consider spotting.
-</DL>
-
-<H2>Parameters</H2>
-<DL>
-
-<DT><B>max=</B>name
-<DD>Name of an existing raster map layer in the user's current
-mapset search path containing the maximum ROS values (cm/minute).
-
-<DT><B>dir=</B>name
-<DD>Name of an existing raster map layer in the user's
-current mapset search path containing directions of the maximum ROSes,
-clockwise from north (degree).
-
-<DT><B>base=</B>name
-<DD>Name of an existing raster map layer in the user's
-current mapset search path containing the ROS values in the directions
-perpendicular to maximum ROSes' (cm/minute). These ROSes are also the ones
-without the effect of directional factors.
-
-<DT><B>start=</B>name
-<DD>Name of an existing raster map layer in the
-user's current mapset search path containing starting locations of the
-spread phenomenon. Any positive integers in this map are recognized as
-starting sources.
-
-<DT><B>spot_dist=</B>name
-<DD>Name of an existing raster map layer in
-the user's current mapset search path containing the maximum potential
-spotting distances (meters).
-
-<DT><B>w_speed=</B>name
-<DD>Name of an existing raster map layer in the
-user's current mapset search path containing wind velocities at half of
-the average flame height (feet/minute).
-
-<DT><B>f_mois</B>=name
-<DD>Name of an existing raster map layer in the
-user's current mapset search path containing the 1-hour (<.25") fuel
-moisture (percentage content multiplied by 100).
-
-<DT><B>least_size=</B>odd int An odd integer ranging 3 - 15 indicating
-the basic sampling window size within which all cells will be considered
-to see whether they will be reached by the current spread cell. The default
-number is 3 which means a 3x3 window.
-
-<DT><B>comp_dens=</B>decimal A decimal number ranging 0.0 - 1.0 indicating
-additional sampling cells will be considered to see whether they will be
-reached by the current spread cell. The closer to 1.0 the decimal number
-is, the longer the program will run and the higher the simulation accuracy
-will be. The default number is 0.5.
-
-<DT><B>init_time=</B>int A non-negative number specifying the initial
-time for the current spread simulation (minutes). This is useful when multiple
-phase simulation is conducted. The default time is 0.
-
-<DT><B>lag=</B>int A non-negative integer specifying the simulating
-duration time lag (minutes). The default is infinite, but the program will
-terminate when the current geographic region/mask has been filled. It also
-controls the computational time, the shorter the time lag, the faster the
-program will run.
-
-<DT><B>backdrop=</B>name
-<DD>Name of an existing raster map layer in the
-user's current mapset search path to be used as the background on which
-the "live" movement will be shown.
-
-<DT><B>output=</B>name
-<DD>Name of the new raster map layer to contain
-the results of the cumulative spread time needed for a phenomenon to reach
-each cell from the starting sources (minutes).
-
-<DT><B>x_output=</B>name
-<DD>Name of the new raster map layer to contain
-the results of backlink information in UTM easting coordinates for each
-cell.
-
-<DT><B>y_output</B>=name
-<DD>Name of the new raster map layer to contain
-the results of backlink information in UTM northing coordinates for each
-cell.
-</DL>
-
-<H2>OPTIONS</H2>
-The user can run r.spread either interactively or non- interactively. The
-program is run interactively if the user types <I>r.spread</I> without
-specifying flag settings and parameter values on the command line. In this
-case, the user will be prompted for input.
-
-<P>Alternately, the user can run r.spread non-interactively, by specifying
-the names of raster map layers and desired options on the command line,
-using the form:
-
-<P>r.spread [-vds] max=name dir=name base=name start=name [spot_dist=name]
-[w_speed=name] [f_mois=name] [least_size=odds int] [comp_dens=decimal]
-[init_time=int (>=0)] [lag=int (>= 0)] [backdrop=name] output=name [x_output=name]
-[y_output=name] The -d option can only be used after a graphics window
-is opened and selected.
-
-<P>Options spot_dist=name, w_speed=name and f_mois=name must all
-be given if the -s option is used.
-
-
-<H2>EXAMPLE</H2>
-Assume we have inputs, the following simulates a spotting- involved wildfire
-on the graphics window and generates three raster maps to contain spread
-time, backlink information in UTM northing and easting coordinates:
-
-<P>r.spread -ds max=my_ros.max dir=my_ros.maxdir base=my_ros.base
-start=fire_origin spot_dist=my_ros.spotdist w_speed=wind_speed f_mois=1hour_moisture
-backdrop=image_burned output=my_spread x_output=my_spread.x y_output=my_spread.y
-
-<H2>NOTES</H2>
-1. r.spread is a specific implementation of the shortest path algorithm.
-r.cost GRASS program served as the starting point for the development of
-r.spread. One of the major differences between the two programs is that
-r.cost only simulates ISOTROPIC spread while r.spread can simulate ELLIPTICALLY
-ANISOTROPIC spread, including isotropic spread as a special case.
-
-<P>2. Before running r.spread, the user should prepare the ROS (base,
-max and direction) maps using appropriate models. For some wildfire spread,
-a separate GRASS program r.ros based on Rothermel's fire equation does
-such work. The combination of the two forms a simulation of wildfire spread.
-
-<P>3. The relationship of the start map and ROS maps should be logically
-correct, i.e. a starting source (a positive value in the start map) should
-not be located in a spread BARRIER (zero value in the ROS maps). Otherwise
-the program refuses to run.
-
-<P>4. r.spread uses the current geographic region settings. The output
-map layer will not go outside the boundaries set in the region, and will
-not be influenced by starting sources outside. So any change of the current
-region may influence the output. The recommendation is to use slightly
-larger region than needed. Refer to g.region to set an appropriate geographic
-region.
-
-<P>5. The inputs to r.spread should be in proper units.
-
-<P>6. r.spread is a computationally intensive program. The user may
-need to choose appropriate size of the geographic region and resolution.
-
-<P>7. A low and medium (i.e. <= 0.5) sampling density can improve
-accuracy for elliptical simulation significantly, without adding significantly
-extra running time. Further increasing the sample density will not gain
-much accuracy while requiring greatly additional running time.
-
-<H2>SEE ALSO</H2>
-
-<EM><A HREF="g.region.html">g.region</A></EM>,
-<EM><A HREF="r.cost.html">r.cost</A></EM>,
-<!-- <EM><A HREF="r.mask.html">r.mask</A></EM>, -->
-<EM><A HREF="r.spreadpath.html">r.spreadpath</A></EM>,
-<EM><A HREF="r.ros.html">r.ros</A></EM>
-
-<H2>REFERENCES</H2>
-Chase, Carolyn, H., 1984, Spotting distance from wind-driven surface fires
--- extensions of equations for pocket calculators, US Forest Service, Res.
-Note INT-346, Ogden, Utah.
-
-<P>Rothermel, R. C., 1983, How to predict the spread and intensity
-of forest and range fires. US Forest Service, Gen. Tech. Rep. INT-143.
-Ogden, Utah.
-
-<P>Xu, Jianping, 1994, Simulating the spread of wildfires using a
-geographic information system and remote sensing, Ph. D. Dissertation,
-Rutgers University, New Brunswick, New Jersey.
-
-<H2>AUTHOR</H2>
-Jianping Xu and Richard G. Lathrop, Jr., Center for Remote Sensing and
-Spatial Analysis, Rutgers University.
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/raster/wildfire/r.spread/r.spread.html (from rev 32770, grass/trunk/raster/wildfire/r.spread/description.html)
===================================================================
--- grass/trunk/raster/wildfire/r.spread/r.spread.html (rev 0)
+++ grass/trunk/raster/wildfire/r.spread/r.spread.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,223 @@
+<H2>DESCRIPTION</H2>
+
+Spread phenomena usually show uneven movement over space. Such unevenness
+is due to two reasons:
+<BR>1) the uneven conditions from location to location, which can be called
+SPATIAL HETEROGENEITY, and
+<BR>2) the uneven conditions in different directions, which can be called
+ANISOTROPY.
+<BR>The anisotropy of spread occurs when any of the determining factors
+have directional components. For example, wind and topography cause anisotropic
+spread of wildfires.
+
+<P>One of the simplest spatial heterogeneous and anisotropic spread
+is elliptical spread, in which, each local spread shape can be thought
+as an ellipse. In a raster setting, cell centers are foci of the spread
+ellipses, and the spread phenomenon moves fastest toward apogees and slowest
+to perigees. The sizes and shapes of spread ellipses may vary cell by cell.
+So the overall spread shape is commonly not an ellipse.
+
+<P><I>r.spread </I>simulates elliptically anisotropic spread phenomena,
+given three raster map layers about ROS (base ROS, maximum ROS and direction
+of the maximum ROS) plus a raster map layer showing the starting sources.
+These ROS layers define unique ellipses for all cell locations in the current
+geographic region as if each cell center was a potential spread origin.
+For some wildfire spread, these ROS layers can be generated by another
+GRASS raster program r.ros. The actual locations reached by a spread event
+are constrained by the actual spread origins and the elapsed spread time.
+
+<P><I>r.spread </I>optionally produces raster maps to contain backlink
+UTM coordinates for each raster cell of the spread time map. The spread
+paths can be accurately traced based on the backlink information by another
+GRASS raster program r.spreadpath.
+
+<P>Part of the spotting function in r.spread is based on Chase (1984)
+and Rothermel (1983). More information on <I>r.spread</I>, <I><A HREF="r.ros.html">r.ros</A></I>
+and <I><A HREF="r.spreadpath.html">r.spreadpath</A></I> can be found in
+Xu (1994).
+
+<H2>Flags:</H2>
+<DL>
+
+<DT>-v
+<DD> Run verbosely, printing information about program progress to standard
+output.
+
+<DT>-d
+<DD> Display the "live" simulation on screen. A graphics window
+must be opened and selected before using this option.
+
+<DT>-s
+<DD> For wildfires, also consider spotting.
+</DL>
+
+<H2>Parameters</H2>
+<DL>
+
+<DT><B>max=</B>name
+<DD>Name of an existing raster map layer in the user's current
+mapset search path containing the maximum ROS values (cm/minute).
+
+<DT><B>dir=</B>name
+<DD>Name of an existing raster map layer in the user's
+current mapset search path containing directions of the maximum ROSes,
+clockwise from north (degree).
+
+<DT><B>base=</B>name
+<DD>Name of an existing raster map layer in the user's
+current mapset search path containing the ROS values in the directions
+perpendicular to maximum ROSes' (cm/minute). These ROSes are also the ones
+without the effect of directional factors.
+
+<DT><B>start=</B>name
+<DD>Name of an existing raster map layer in the
+user's current mapset search path containing starting locations of the
+spread phenomenon. Any positive integers in this map are recognized as
+starting sources.
+
+<DT><B>spot_dist=</B>name
+<DD>Name of an existing raster map layer in
+the user's current mapset search path containing the maximum potential
+spotting distances (meters).
+
+<DT><B>w_speed=</B>name
+<DD>Name of an existing raster map layer in the
+user's current mapset search path containing wind velocities at half of
+the average flame height (feet/minute).
+
+<DT><B>f_mois</B>=name
+<DD>Name of an existing raster map layer in the
+user's current mapset search path containing the 1-hour (<.25") fuel
+moisture (percentage content multiplied by 100).
+
+<DT><B>least_size=</B>odd int An odd integer ranging 3 - 15 indicating
+the basic sampling window size within which all cells will be considered
+to see whether they will be reached by the current spread cell. The default
+number is 3 which means a 3x3 window.
+
+<DT><B>comp_dens=</B>decimal A decimal number ranging 0.0 - 1.0 indicating
+additional sampling cells will be considered to see whether they will be
+reached by the current spread cell. The closer to 1.0 the decimal number
+is, the longer the program will run and the higher the simulation accuracy
+will be. The default number is 0.5.
+
+<DT><B>init_time=</B>int A non-negative number specifying the initial
+time for the current spread simulation (minutes). This is useful when multiple
+phase simulation is conducted. The default time is 0.
+
+<DT><B>lag=</B>int A non-negative integer specifying the simulating
+duration time lag (minutes). The default is infinite, but the program will
+terminate when the current geographic region/mask has been filled. It also
+controls the computational time, the shorter the time lag, the faster the
+program will run.
+
+<DT><B>backdrop=</B>name
+<DD>Name of an existing raster map layer in the
+user's current mapset search path to be used as the background on which
+the "live" movement will be shown.
+
+<DT><B>output=</B>name
+<DD>Name of the new raster map layer to contain
+the results of the cumulative spread time needed for a phenomenon to reach
+each cell from the starting sources (minutes).
+
+<DT><B>x_output=</B>name
+<DD>Name of the new raster map layer to contain
+the results of backlink information in UTM easting coordinates for each
+cell.
+
+<DT><B>y_output</B>=name
+<DD>Name of the new raster map layer to contain
+the results of backlink information in UTM northing coordinates for each
+cell.
+</DL>
+
+<H2>OPTIONS</H2>
+The user can run r.spread either interactively or non- interactively. The
+program is run interactively if the user types <I>r.spread</I> without
+specifying flag settings and parameter values on the command line. In this
+case, the user will be prompted for input.
+
+<P>Alternately, the user can run r.spread non-interactively, by specifying
+the names of raster map layers and desired options on the command line,
+using the form:
+
+<P>r.spread [-vds] max=name dir=name base=name start=name [spot_dist=name]
+[w_speed=name] [f_mois=name] [least_size=odds int] [comp_dens=decimal]
+[init_time=int (>=0)] [lag=int (>= 0)] [backdrop=name] output=name [x_output=name]
+[y_output=name] The -d option can only be used after a graphics window
+is opened and selected.
+
+<P>Options spot_dist=name, w_speed=name and f_mois=name must all
+be given if the -s option is used.
+
+
+<H2>EXAMPLE</H2>
+Assume we have inputs, the following simulates a spotting- involved wildfire
+on the graphics window and generates three raster maps to contain spread
+time, backlink information in UTM northing and easting coordinates:
+
+<P>r.spread -ds max=my_ros.max dir=my_ros.maxdir base=my_ros.base
+start=fire_origin spot_dist=my_ros.spotdist w_speed=wind_speed f_mois=1hour_moisture
+backdrop=image_burned output=my_spread x_output=my_spread.x y_output=my_spread.y
+
+<H2>NOTES</H2>
+1. r.spread is a specific implementation of the shortest path algorithm.
+r.cost GRASS program served as the starting point for the development of
+r.spread. One of the major differences between the two programs is that
+r.cost only simulates ISOTROPIC spread while r.spread can simulate ELLIPTICALLY
+ANISOTROPIC spread, including isotropic spread as a special case.
+
+<P>2. Before running r.spread, the user should prepare the ROS (base,
+max and direction) maps using appropriate models. For some wildfire spread,
+a separate GRASS program r.ros based on Rothermel's fire equation does
+such work. The combination of the two forms a simulation of wildfire spread.
+
+<P>3. The relationship of the start map and ROS maps should be logically
+correct, i.e. a starting source (a positive value in the start map) should
+not be located in a spread BARRIER (zero value in the ROS maps). Otherwise
+the program refuses to run.
+
+<P>4. r.spread uses the current geographic region settings. The output
+map layer will not go outside the boundaries set in the region, and will
+not be influenced by starting sources outside. So any change of the current
+region may influence the output. The recommendation is to use slightly
+larger region than needed. Refer to g.region to set an appropriate geographic
+region.
+
+<P>5. The inputs to r.spread should be in proper units.
+
+<P>6. r.spread is a computationally intensive program. The user may
+need to choose appropriate size of the geographic region and resolution.
+
+<P>7. A low and medium (i.e. <= 0.5) sampling density can improve
+accuracy for elliptical simulation significantly, without adding significantly
+extra running time. Further increasing the sample density will not gain
+much accuracy while requiring greatly additional running time.
+
+<H2>SEE ALSO</H2>
+
+<EM><A HREF="g.region.html">g.region</A></EM>,
+<EM><A HREF="r.cost.html">r.cost</A></EM>,
+<!-- <EM><A HREF="r.mask.html">r.mask</A></EM>, -->
+<EM><A HREF="r.spreadpath.html">r.spreadpath</A></EM>,
+<EM><A HREF="r.ros.html">r.ros</A></EM>
+
+<H2>REFERENCES</H2>
+Chase, Carolyn, H., 1984, Spotting distance from wind-driven surface fires
+-- extensions of equations for pocket calculators, US Forest Service, Res.
+Note INT-346, Ogden, Utah.
+
+<P>Rothermel, R. C., 1983, How to predict the spread and intensity
+of forest and range fires. US Forest Service, Gen. Tech. Rep. INT-143.
+Ogden, Utah.
+
+<P>Xu, Jianping, 1994, Simulating the spread of wildfires using a
+geographic information system and remote sensing, Ph. D. Dissertation,
+Rutgers University, New Brunswick, New Jersey.
+
+<H2>AUTHOR</H2>
+Jianping Xu and Richard G. Lathrop, Jr., Center for Remote Sensing and
+Spatial Analysis, Rutgers University.
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/raster/wildfire/r.spreadpath/description.html
===================================================================
--- grass/trunk/raster/wildfire/r.spreadpath/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster/wildfire/r.spreadpath/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,48 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-<EM>r.spreadpath</EM> recursively traces the least cost path backwards to
-the origin, given backlink information input map layers and target locations
-from where paths are to be traced. The backlink information map layers
-record each cell's backlink UTM northing (the y_input) and easting (the
-x_input) coordinates from which the cell's cumulative cost was determined.
-
-<P>
-
-The backlink inputs can be generated from another GRASS raster program
-<EM>r.spread</EM>. One of the major applications of <EM>r.spreadpath</EM>
-along with <EM>r.spread</EM> is to accurately find the least cost corridors
-and/or paths on a raster setting. More information on <EM>r.spread</EM> and
-<EM>r.spreadpath</EM> can be found in Xu (1994).
-
-<H2>Parameters:</H2>
-<DL>
-<DT><B>x_input=</B><EM>name</EM>
-<DD>Name of input raster map layer containing backlink UTM easting
-coordinates.
-
-<DT><B>y_input=</B><EM>name</EM>
-<DD>Name of input raster map layer containing backlink UTM northing coordinates.
-
-<DT><B>coordinate=</B><EM>x,y[,x,y,x,y, ...]</EM>
-<DD>Each x,y coordinate pair gives the easting and northing (respectively) geographic coordinates of a target point from which to backwards trace the least cost path. As many
-points as desired can be entered by the user.
-
-<DT><B>output=</B><EM>name</EM>
-<DD>Name of raster map layer to contain output. Also can be used as the map layer of the input target points. If so used, the input target point map will be overwritten by the output.
-</DL>
-
-<H2>SEE ALSO</H2>
-<EM><A HREF="r.spread.html">r.spread</A></EM>,
-<EM><A HREF="r.ros.html">r.ros</A></EM>
-
-
-<H2>REFERENCES</H2>
-Xu, Jianping, 1994, Simulating the spread of wildfires using a geographic
-information system and remote sensing, Ph. D. Dissertation, Rutgers University,
-New Brunswick, New Jersey.
-
-<H2>AUTHOR</H2>
-Jianping Xu and Richard G. Lathrop, Jr., Center for Remote Sensing and
-Spatial Analysis, Rutgers University.
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/raster/wildfire/r.spreadpath/r.spreadpath.html (from rev 32770, grass/trunk/raster/wildfire/r.spreadpath/description.html)
===================================================================
--- grass/trunk/raster/wildfire/r.spreadpath/r.spreadpath.html (rev 0)
+++ grass/trunk/raster/wildfire/r.spreadpath/r.spreadpath.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,48 @@
+<H2>DESCRIPTION</H2>
+
+<EM>r.spreadpath</EM> recursively traces the least cost path backwards to
+the origin, given backlink information input map layers and target locations
+from where paths are to be traced. The backlink information map layers
+record each cell's backlink UTM northing (the y_input) and easting (the
+x_input) coordinates from which the cell's cumulative cost was determined.
+
+<P>
+
+The backlink inputs can be generated from another GRASS raster program
+<EM>r.spread</EM>. One of the major applications of <EM>r.spreadpath</EM>
+along with <EM>r.spread</EM> is to accurately find the least cost corridors
+and/or paths on a raster setting. More information on <EM>r.spread</EM> and
+<EM>r.spreadpath</EM> can be found in Xu (1994).
+
+<H2>Parameters:</H2>
+<DL>
+<DT><B>x_input=</B><EM>name</EM>
+<DD>Name of input raster map layer containing backlink UTM easting
+coordinates.
+
+<DT><B>y_input=</B><EM>name</EM>
+<DD>Name of input raster map layer containing backlink UTM northing coordinates.
+
+<DT><B>coordinate=</B><EM>x,y[,x,y,x,y, ...]</EM>
+<DD>Each x,y coordinate pair gives the easting and northing (respectively) geographic coordinates of a target point from which to backwards trace the least cost path. As many
+points as desired can be entered by the user.
+
+<DT><B>output=</B><EM>name</EM>
+<DD>Name of raster map layer to contain output. Also can be used as the map layer of the input target points. If so used, the input target point map will be overwritten by the output.
+</DL>
+
+<H2>SEE ALSO</H2>
+<EM><A HREF="r.spread.html">r.spread</A></EM>,
+<EM><A HREF="r.ros.html">r.ros</A></EM>
+
+
+<H2>REFERENCES</H2>
+Xu, Jianping, 1994, Simulating the spread of wildfires using a geographic
+information system and remote sensing, Ph. D. Dissertation, Rutgers University,
+New Brunswick, New Jersey.
+
+<H2>AUTHOR</H2>
+Jianping Xu and Richard G. Lathrop, Jr., Center for Remote Sensing and
+Spatial Analysis, Rutgers University.
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/raster3d/r3.cross.rast/description.html
===================================================================
--- grass/trunk/raster3d/r3.cross.rast/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster3d/r3.cross.rast/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,74 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-This module creates a cross section 2D map from one g3d raster volume
-map based on a 2D elevation map. It checks if the value of the
-elevation map is located in the z-coordinate space of the 3d map. If
-so, the 3D voxel value for this position is transferred to the related
-cross section output map cell, otherwise the NULL value is set.
-
-<center>
-<img src=r3.cross.rast.png border=0><BR>
-<table border=0 width=700>
-<tr><td><center>
-<i>How r3.cross.rast works</i>
-</center></td></tr>
-</table>
-</center>
-
-
-<br>
-<br>
-If the 2d and 3d region settings are different,
-the 2d resolution will be adjust to the 3d resolution.
-
-
-<H2>NOTES</H2>
-
-To create a cut plane elevation map use <em>r.mapcalc</em>. Some examples:
-<ul>
- <li>To create a cut plane elevation map in x direction type
- <br><i>r.mapcalc "cutplane = col()*x"</i>,<br> x be the value for
- the elevation. If the range of col() is 1 ... 10, the elevation map
- has the range 1 ... 10 if x == 1 and if x == 10 the range 10
- ... 100</li>
-
- <li>To create a cut plane elevation map in y direction type
- <br><i>r.mapcalc "cutplane = row()*x"</i>,<br> x be the value for
- the elevation. If the range of col() is 1 ... 10, the elevation map
- has the range 1 ... 10 if x == 1 and if x == 10 the range 10
- ... 100</li>
-
- <li>The user can also make a cut in y and x direction with <em>r.mapcalc</em> by
- using <br><i>r.mapcalc "cutplane = (row()+col())*x"</i></li>
-</ul>
-
-<H2>EXAMPLE</H2>
-
-<H3>Simple Spearfish example</H3>
-
-<div class="code"><pre>
-g.region -d
-g.region res=150 res3=150 t=1000 b=0 tbres=100
-
-# synthetic data, could be geological structures:
-r3.mapcalc "map3d=sin(row())+sin(col())+sin(depth()*depth())"
-
-#create a cutplane map
-r.mapcalc "cutplane = col()*10"
-
-#create the cross section map
-r3.cross.rast input=map3d elevation=cutplane output=crosssection
-</pre></div>
-
-
-<H2>SEE ALSO</H2>
-
-<EM><A HREF="g.region.html">g.region</A></EM><br>
-<EM><A HREF="r.mapcalc.html">r.mapcalc</A></EM><br>
-<EM><A HREF="r3.mapcalc.html">r3.mapcalc</A></EM><br>
-<EM><A HREF="r3.to.rast.html">r3.to.rast</A></EM><br>
-
-<H2>AUTHOR</H2>
-Soeren Gebbert
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/raster3d/r3.cross.rast/r3.cross.rast.html (from rev 32770, grass/trunk/raster3d/r3.cross.rast/description.html)
===================================================================
--- grass/trunk/raster3d/r3.cross.rast/r3.cross.rast.html (rev 0)
+++ grass/trunk/raster3d/r3.cross.rast/r3.cross.rast.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,74 @@
+<H2>DESCRIPTION</H2>
+
+This module creates a cross section 2D map from one g3d raster volume
+map based on a 2D elevation map. It checks if the value of the
+elevation map is located in the z-coordinate space of the 3d map. If
+so, the 3D voxel value for this position is transferred to the related
+cross section output map cell, otherwise the NULL value is set.
+
+<center>
+<img src=r3.cross.rast.png border=0><BR>
+<table border=0 width=700>
+<tr><td><center>
+<i>How r3.cross.rast works</i>
+</center></td></tr>
+</table>
+</center>
+
+
+<br>
+<br>
+If the 2d and 3d region settings are different,
+the 2d resolution will be adjust to the 3d resolution.
+
+
+<H2>NOTES</H2>
+
+To create a cut plane elevation map use <em>r.mapcalc</em>. Some examples:
+<ul>
+ <li>To create a cut plane elevation map in x direction type
+ <br><i>r.mapcalc "cutplane = col()*x"</i>,<br> x be the value for
+ the elevation. If the range of col() is 1 ... 10, the elevation map
+ has the range 1 ... 10 if x == 1 and if x == 10 the range 10
+ ... 100</li>
+
+ <li>To create a cut plane elevation map in y direction type
+ <br><i>r.mapcalc "cutplane = row()*x"</i>,<br> x be the value for
+ the elevation. If the range of col() is 1 ... 10, the elevation map
+ has the range 1 ... 10 if x == 1 and if x == 10 the range 10
+ ... 100</li>
+
+ <li>The user can also make a cut in y and x direction with <em>r.mapcalc</em> by
+ using <br><i>r.mapcalc "cutplane = (row()+col())*x"</i></li>
+</ul>
+
+<H2>EXAMPLE</H2>
+
+<H3>Simple Spearfish example</H3>
+
+<div class="code"><pre>
+g.region -d
+g.region res=150 res3=150 t=1000 b=0 tbres=100
+
+# synthetic data, could be geological structures:
+r3.mapcalc "map3d=sin(row())+sin(col())+sin(depth()*depth())"
+
+#create a cutplane map
+r.mapcalc "cutplane = col()*10"
+
+#create the cross section map
+r3.cross.rast input=map3d elevation=cutplane output=crosssection
+</pre></div>
+
+
+<H2>SEE ALSO</H2>
+
+<EM><A HREF="g.region.html">g.region</A></EM><br>
+<EM><A HREF="r.mapcalc.html">r.mapcalc</A></EM><br>
+<EM><A HREF="r3.mapcalc.html">r3.mapcalc</A></EM><br>
+<EM><A HREF="r3.to.rast.html">r3.to.rast</A></EM><br>
+
+<H2>AUTHOR</H2>
+Soeren Gebbert
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/raster3d/r3.gwflow/description.html
===================================================================
--- grass/trunk/raster3d/r3.gwflow/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster3d/r3.gwflow/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,94 +0,0 @@
-<H2>DESCRIPTION</H2>
-This numerical program calculates transient, confined groundwater flow in three dimensions
-based on volume maps and the current 3d region resolution.
-All initial- and boundary-conditions must be provided as
-volume maps.
-<br>
-<br>
-This module calculates the piezometric head and optionally the
-groundwater velocity field.
-The vector components can be visualized with paraview if they are exported
-with <em>r3.out.vtk</em>.
-<br>
-<br>
-The groundwater flow will always be calculated transient.
-If you want to calculate stady state, set the timestep
-to a large number (billions of seconds) or set the
-specific yield raster maps to zero.
-
-
-<H2>NOTES</H2>
-
-The groundwater flow calculation is based on Darcy's law and a
-finite volume discretization. The groundwater flow partial
-differential equation is of the following form:
-
-<p>
-(dh/dt)*S = Kxx * (d^2h/dx^2) + Kyy * (d^2h/dy^2) + Kzz * (d^2h/dz^2) + q
-
-<ul>
-<li>h -- the piezometric head im meters [m]</li>
-<li>dt -- the time step for transient calculation in seconds [s]</li>
-<li>S -- the specific yield [1/m]</li>
-<li>b -- the bottom surface of the aquifer meters [m]</li>
-<li>Kxx -- the hydraulic conductivity tensor part in x direction in meter per second [m/s]</li>
-<li>Kyy -- the hydraulic conductivity tensor part in y direction in meter per seconds [m/s]</li>
-<li>Kzz -- the hydraulic conductivity tensor part in z direction in meter per seconds [m/s]</li>
-<li>q - inner source in [1/s]</li>
-</ul>
-
-<br>
-<br>
-Two different boundary conditions are implemented,
-the Dirichlet and Neumann conditions. By default the calculation area is surrounded by homogeneous Neumann boundary conditions.
-The calculation and boundary status of single cells can be set with the status map,
-the following cell states are supportet:
-
-<ul>
-<li>0 == inactive - the cell with status 0 will not be calulated, active cells will have a no flow boundary to an inactive cell</li>
-<li>1 == active - this cell is used for groundwater calculation, inner sources can be defined for those cells</li>
-<li>2 == Dirichlet - cells of this type will have a fixed piezometric head value which do not change over time </li>
-</ul>
-
-<br>
-<br>
-The groundwater flow equation can be solved with several solvers.
-
-Aditionally a direct Gauss solver and LU solver are available. Those direct solvers
-only work with quadratic matrices, so be careful using them with large maps
-(maps of size 10.000 cells will need more than one gigabyte of ram).
-
-<H2>EXAMPLE</H2>
-Use this small script to create a working
-groundwater flow area and data. Make sure you are not in a lat/lon projection.
-
-<div class="code"><pre>
-# set the region accordingly
-g.region res=25 res3=25 t=100 b=0 n=1000 s=0 w=0 e=1000
-
-#now create the input raster maps for a confined aquifer
-r3.mapcalc "phead=if(row() == 1 && depth() == 4, 50, 40)"
-r3.mapcalc "status=if(row() == 1 && depth() == 4, 2, 1)"
-r3.mapcalc "well=if(row() == 20 && col() == 20 , -0.00025, 0)"
-r3.mapcalc "hydcond=0.00025"
-r3.mapcalc "syield=0.0001"
-r.mapcalc "recharge=0.0"
-
-r3.gwflow --o -s solver=cg phead=phead status=status hc_x=hydcond hc_y=hydcond \
-hc_z=hydcond q=well s=syield r=recharge output=gwresult dt=8640000 velocity=gwresult_velocity
-
-# The data can be visulaized with paraview when exported with r3.out.vtk
-r3.out.vtk -p in=gwresult,status vector=gwresult_velocity_x,gwresult_velocity_y,gwresult_velocity_z out=/tmp/gwdata3d.vtk
-
-#now load the data into paraview
-</pre></div>
-
-<H2>SEE ALSO</H2>
-
-<EM><A HREF="r.gwflow.html">r.gwflow</A></EM><br>
-<EM><A HREF="r3.out.vtk.html">r3.out.vtk</A></EM><br>
-
-<H2>AUTHOR</H2>
-Soeren Gebbert
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/raster3d/r3.gwflow/r3.gwflow.html (from rev 32770, grass/trunk/raster3d/r3.gwflow/description.html)
===================================================================
--- grass/trunk/raster3d/r3.gwflow/r3.gwflow.html (rev 0)
+++ grass/trunk/raster3d/r3.gwflow/r3.gwflow.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,94 @@
+<H2>DESCRIPTION</H2>
+This numerical program calculates transient, confined groundwater flow in three dimensions
+based on volume maps and the current 3d region resolution.
+All initial- and boundary-conditions must be provided as
+volume maps.
+<br>
+<br>
+This module calculates the piezometric head and optionally the
+groundwater velocity field.
+The vector components can be visualized with paraview if they are exported
+with <em>r3.out.vtk</em>.
+<br>
+<br>
+The groundwater flow will always be calculated transient.
+If you want to calculate stady state, set the timestep
+to a large number (billions of seconds) or set the
+specific yield raster maps to zero.
+
+
+<H2>NOTES</H2>
+
+The groundwater flow calculation is based on Darcy's law and a
+finite volume discretization. The groundwater flow partial
+differential equation is of the following form:
+
+<p>
+(dh/dt)*S = Kxx * (d^2h/dx^2) + Kyy * (d^2h/dy^2) + Kzz * (d^2h/dz^2) + q
+
+<ul>
+<li>h -- the piezometric head im meters [m]</li>
+<li>dt -- the time step for transient calculation in seconds [s]</li>
+<li>S -- the specific yield [1/m]</li>
+<li>b -- the bottom surface of the aquifer meters [m]</li>
+<li>Kxx -- the hydraulic conductivity tensor part in x direction in meter per second [m/s]</li>
+<li>Kyy -- the hydraulic conductivity tensor part in y direction in meter per seconds [m/s]</li>
+<li>Kzz -- the hydraulic conductivity tensor part in z direction in meter per seconds [m/s]</li>
+<li>q - inner source in [1/s]</li>
+</ul>
+
+<br>
+<br>
+Two different boundary conditions are implemented,
+the Dirichlet and Neumann conditions. By default the calculation area is surrounded by homogeneous Neumann boundary conditions.
+The calculation and boundary status of single cells can be set with the status map,
+the following cell states are supportet:
+
+<ul>
+<li>0 == inactive - the cell with status 0 will not be calulated, active cells will have a no flow boundary to an inactive cell</li>
+<li>1 == active - this cell is used for groundwater calculation, inner sources can be defined for those cells</li>
+<li>2 == Dirichlet - cells of this type will have a fixed piezometric head value which do not change over time </li>
+</ul>
+
+<br>
+<br>
+The groundwater flow equation can be solved with several solvers.
+
+Aditionally a direct Gauss solver and LU solver are available. Those direct solvers
+only work with quadratic matrices, so be careful using them with large maps
+(maps of size 10.000 cells will need more than one gigabyte of ram).
+
+<H2>EXAMPLE</H2>
+Use this small script to create a working
+groundwater flow area and data. Make sure you are not in a lat/lon projection.
+
+<div class="code"><pre>
+# set the region accordingly
+g.region res=25 res3=25 t=100 b=0 n=1000 s=0 w=0 e=1000
+
+#now create the input raster maps for a confined aquifer
+r3.mapcalc "phead=if(row() == 1 && depth() == 4, 50, 40)"
+r3.mapcalc "status=if(row() == 1 && depth() == 4, 2, 1)"
+r3.mapcalc "well=if(row() == 20 && col() == 20 , -0.00025, 0)"
+r3.mapcalc "hydcond=0.00025"
+r3.mapcalc "syield=0.0001"
+r.mapcalc "recharge=0.0"
+
+r3.gwflow --o -s solver=cg phead=phead status=status hc_x=hydcond hc_y=hydcond \
+hc_z=hydcond q=well s=syield r=recharge output=gwresult dt=8640000 velocity=gwresult_velocity
+
+# The data can be visulaized with paraview when exported with r3.out.vtk
+r3.out.vtk -p in=gwresult,status vector=gwresult_velocity_x,gwresult_velocity_y,gwresult_velocity_z out=/tmp/gwdata3d.vtk
+
+#now load the data into paraview
+</pre></div>
+
+<H2>SEE ALSO</H2>
+
+<EM><A HREF="r.gwflow.html">r.gwflow</A></EM><br>
+<EM><A HREF="r3.out.vtk.html">r3.out.vtk</A></EM><br>
+
+<H2>AUTHOR</H2>
+Soeren Gebbert
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/raster3d/r3.in.ascii/description.html
===================================================================
--- grass/trunk/raster3d/r3.in.ascii/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster3d/r3.in.ascii/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,117 +0,0 @@
-<H2>DESCRIPTION</H2>
-Convert a 3D ASCII raster text file into a (binary) 3D raster map layer.
-
-<H3>Parameters:</H3>
-<DL>
-<DT><B>type</B>
-<DD>Data type used in the output file
-<DD>Options: default, double, float
-
-<DT><B>precision</B>
-<DD>Precision used in the output file
-<DD>Options: default, max, 0-52
-
-<DT><B>compression</B>
-<DD>Note that the <EM>none</EM> option only specifies
-that neither LZW nor RLE is used for compression. It
-does not turn off the compression all together. G3D does
-not support non-compressed files.
-<DD>Options: default, rle, none
-
-<DT><B>tiledimension</B>
-<DD>The dimension of the tiles used in the output file. The format is: XxYxZ
-
-<DT><B>nv</B>
-<DD>Specifies which value to convert to NULL-value. If the specified value is
-<em>none</em>, no conversion is performed. Default is <em>none</em>.
-
-<DT><B>input</B>
-<DD>Path and name of ASCII file to be imported
-
-<DT><B>output</B>
-<DD>Name of the G3D output map
-</DL>
-
-<H2>NOTES</H2>
-The format for the ASCII file:
-<PRE>
-north: <EM>floating point</EM>
-south: <EM>floating point</EM>
-east: <EM>floating point</EM>
-west: <EM>floating point</EM>
-top: <EM>floating point</EM>
-bottom: <EM>floating point</EM>
-rows: <EM>integer</EM>
-cols: <EM>integer</EM>
-levels: <EM>integer</EM>
-</PRE>
-This header is followed by the cell values in <EM>floating point</EM> format
-organized in rows with constant <EM>col</EM> and <EM>level</EM> coordinate.
-The rows are organized by constant <EM>level</EM> coordinate. Individual cell
-values are separated by <EM>space</EM> or <EM>CR</EM>.
-<P>
-NOTE: Currently, after the file has been imported, the stored values are
-compared with the original data. This feature is used to find bugs in the
-library at an early stage and will be turned off as soon as confidence has
-built up.
-
-<H2>EXAMPLES</H2>
-
-4x3x2 sample. Note lower-left (SW) corner of the bottom level comes first!
-This array format, where EW is preserved but NS is flipped, is sometimes
-known as "ij" coordinates.
-This is opposite to <em>r.in.ascii</em>'s format, which places the SW corner
-at the beginning of the last row of data.
-
-<div class="code"><pre>
-north: 3.0
-south: 0.0
-east: 4.0
-west: 0.0
-top: 2.0
-bottom: 0.0
-rows: 3
-cols: 4
-levels: 2
-x1,y1,z1 x2,y1,z1 x3,y1,z1 x4,y1,z1
-x1,y2,z1 x2,y2,z1 x3,y2,z1 x4,y2,z1
-x1,y3,z1 x2,y3,z1 x3,y3,z1 x4,y3,z1
-x1,y1,z2 x2,y1,z2 x3,y1,z2 x4,y1,z2
-x1,y2,z2 x2,y2,z2 x3,y2,z2 x4,y2,z2
-x1,y3,z2 x2,y3,z2 x3,y3,z2 x4,y3,z2
-</pre></div>
-
-<P>
-
-Sample ASCII voxel map with one layer and several rows and columns (Spearfish area):
-
-<div class="code"><pre>
-north: 4925010.000000
-south: 4924890.000000
-east: 596760.000000
-west: 596610.000000
-top: 1.000000
-bottom: 0.000000
-rows: 4
-cols: 5
-levels: 1
-1204.74 1204.48 1204.19 1203.81 1203.39
-1203.89 1203.67 1203.34 1202.98 1202.43
-1203.05 1202.80 1202.51 1202.11 1201.48
-1202.10 1201.92 1201.62 1201.27 1200.68
-</pre></div>
-
-
-<H2>AUTHORS</H2>
-Roman Waupotitsch, Michael Shapiro,
-Helena Mitasova, Bill Brown, Lubos Mitas, Jaro Hofierka
-
-<H2>SEE ALSO</H2>
-<EM>
-<A HREF="r.in.ascii.html">r.in.ascii</A>,
-<A HREF="r3.out.ascii.html">r3.out.ascii</A>,
-<A HREF="v.to.rast3.html">v.to.rast3</A>
-</EM>
-
-<p>
-<i>Last changed: $Date$</i>
Copied: grass/trunk/raster3d/r3.in.ascii/r3.in.ascii.html (from rev 32770, grass/trunk/raster3d/r3.in.ascii/description.html)
===================================================================
--- grass/trunk/raster3d/r3.in.ascii/r3.in.ascii.html (rev 0)
+++ grass/trunk/raster3d/r3.in.ascii/r3.in.ascii.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,117 @@
+<H2>DESCRIPTION</H2>
+Convert a 3D ASCII raster text file into a (binary) 3D raster map layer.
+
+<H3>Parameters:</H3>
+<DL>
+<DT><B>type</B>
+<DD>Data type used in the output file
+<DD>Options: default, double, float
+
+<DT><B>precision</B>
+<DD>Precision used in the output file
+<DD>Options: default, max, 0-52
+
+<DT><B>compression</B>
+<DD>Note that the <EM>none</EM> option only specifies
+that neither LZW nor RLE is used for compression. It
+does not turn off the compression all together. G3D does
+not support non-compressed files.
+<DD>Options: default, rle, none
+
+<DT><B>tiledimension</B>
+<DD>The dimension of the tiles used in the output file. The format is: XxYxZ
+
+<DT><B>nv</B>
+<DD>Specifies which value to convert to NULL-value. If the specified value is
+<em>none</em>, no conversion is performed. Default is <em>none</em>.
+
+<DT><B>input</B>
+<DD>Path and name of ASCII file to be imported
+
+<DT><B>output</B>
+<DD>Name of the G3D output map
+</DL>
+
+<H2>NOTES</H2>
+The format for the ASCII file:
+<PRE>
+north: <EM>floating point</EM>
+south: <EM>floating point</EM>
+east: <EM>floating point</EM>
+west: <EM>floating point</EM>
+top: <EM>floating point</EM>
+bottom: <EM>floating point</EM>
+rows: <EM>integer</EM>
+cols: <EM>integer</EM>
+levels: <EM>integer</EM>
+</PRE>
+This header is followed by the cell values in <EM>floating point</EM> format
+organized in rows with constant <EM>col</EM> and <EM>level</EM> coordinate.
+The rows are organized by constant <EM>level</EM> coordinate. Individual cell
+values are separated by <EM>space</EM> or <EM>CR</EM>.
+<P>
+NOTE: Currently, after the file has been imported, the stored values are
+compared with the original data. This feature is used to find bugs in the
+library at an early stage and will be turned off as soon as confidence has
+built up.
+
+<H2>EXAMPLES</H2>
+
+4x3x2 sample. Note lower-left (SW) corner of the bottom level comes first!
+This array format, where EW is preserved but NS is flipped, is sometimes
+known as "ij" coordinates.
+This is opposite to <em>r.in.ascii</em>'s format, which places the SW corner
+at the beginning of the last row of data.
+
+<div class="code"><pre>
+north: 3.0
+south: 0.0
+east: 4.0
+west: 0.0
+top: 2.0
+bottom: 0.0
+rows: 3
+cols: 4
+levels: 2
+x1,y1,z1 x2,y1,z1 x3,y1,z1 x4,y1,z1
+x1,y2,z1 x2,y2,z1 x3,y2,z1 x4,y2,z1
+x1,y3,z1 x2,y3,z1 x3,y3,z1 x4,y3,z1
+x1,y1,z2 x2,y1,z2 x3,y1,z2 x4,y1,z2
+x1,y2,z2 x2,y2,z2 x3,y2,z2 x4,y2,z2
+x1,y3,z2 x2,y3,z2 x3,y3,z2 x4,y3,z2
+</pre></div>
+
+<P>
+
+Sample ASCII voxel map with one layer and several rows and columns (Spearfish area):
+
+<div class="code"><pre>
+north: 4925010.000000
+south: 4924890.000000
+east: 596760.000000
+west: 596610.000000
+top: 1.000000
+bottom: 0.000000
+rows: 4
+cols: 5
+levels: 1
+1204.74 1204.48 1204.19 1203.81 1203.39
+1203.89 1203.67 1203.34 1202.98 1202.43
+1203.05 1202.80 1202.51 1202.11 1201.48
+1202.10 1201.92 1201.62 1201.27 1200.68
+</pre></div>
+
+
+<H2>AUTHORS</H2>
+Roman Waupotitsch, Michael Shapiro,
+Helena Mitasova, Bill Brown, Lubos Mitas, Jaro Hofierka
+
+<H2>SEE ALSO</H2>
+<EM>
+<A HREF="r.in.ascii.html">r.in.ascii</A>,
+<A HREF="r3.out.ascii.html">r3.out.ascii</A>,
+<A HREF="v.to.rast3.html">v.to.rast3</A>
+</EM>
+
+<p>
+<i>Last changed: $Date$</i>
Deleted: grass/trunk/raster3d/r3.in.v5d/description.html
===================================================================
--- grass/trunk/raster3d/r3.in.v5d/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster3d/r3.in.v5d/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,21 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-<a href="http://www.ssec.wisc.edu/~billh/vis5d.html">Vis5D</a> is a system
-for interactive visualization of large 5-D gridded data sets such as those
-produced by numerical weather models. One can make isosurfaces, contour
-line slices, colored slices, volume renderings, etc of data in a 3-D grid,
-then rotate and animate the images in real time. There's also a feature
-for wind trajectory tracing, a way to make text anotations for publications,
-support for interactive data analysis, etc.
-<br>r3.in.v5d imports 3-dimensional files (i.e. the v5d file with 1 variable
-and 1 time step). Otherwise, only first variable and timestep from 4/5D
-v5d file will be imported.
-
-<h2>
-SEE ALSO</h2>
-<i><a href="r3.out.v5d.html">r3.out.v5d</a></i>
-
-<h2>
-AUTHOR</h2>
-Jaro Hofierka, GeoModel s.r.o., Slovakia
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/raster3d/r3.in.v5d/r3.in.v5d.html (from rev 32770, grass/trunk/raster3d/r3.in.v5d/description.html)
===================================================================
--- grass/trunk/raster3d/r3.in.v5d/r3.in.v5d.html (rev 0)
+++ grass/trunk/raster3d/r3.in.v5d/r3.in.v5d.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,21 @@
+<H2>DESCRIPTION</H2>
+
+<a href="http://www.ssec.wisc.edu/~billh/vis5d.html">Vis5D</a> is a system
+for interactive visualization of large 5-D gridded data sets such as those
+produced by numerical weather models. One can make isosurfaces, contour
+line slices, colored slices, volume renderings, etc of data in a 3-D grid,
+then rotate and animate the images in real time. There's also a feature
+for wind trajectory tracing, a way to make text anotations for publications,
+support for interactive data analysis, etc.
+<br>r3.in.v5d imports 3-dimensional files (i.e. the v5d file with 1 variable
+and 1 time step). Otherwise, only first variable and timestep from 4/5D
+v5d file will be imported.
+
+<h2>
+SEE ALSO</h2>
+<i><a href="r3.out.v5d.html">r3.out.v5d</a></i>
+
+<h2>
+AUTHOR</h2>
+Jaro Hofierka, GeoModel s.r.o., Slovakia
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/raster3d/r3.mkdspf/description.html
===================================================================
--- grass/trunk/raster3d/r3.mkdspf/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster3d/r3.mkdspf/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,68 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-Creates a display file from an existing grid3 file according to
-specified threshold levels. The display file is a display list
-of polygons that represent isosurfaces of the data volume. If
-specific <I>levels</I> are given, additional optional parameters
-are ignored. <I>Min</I> or <I>max</I> may be used alone or together
-to specify a sub-range of the data. The <I>step</I>
-parameter is given precedence over <I>tnum</I>.
-
-<H3>Flags:</H3>
-<DL>
-<DT><B>-q</B>
-<DD>Suppress progress report & min/max information
-
-<DT><B>-f</B>
-<DD>Use flat shading rather than gradient
-</DL>
-
-<H3>Parameters:</H3>
-<DL>
-<DT><B>grid3</B>
-<DD>Name of an existing 3d raster map
-
-<DT><B>dspf</B>
-<DD>Name of output display file
-
-<DT><B>levels</B>
-<DD>List of thresholds for isosurfaces
-
-<DT><B>min</B>
-<DD>Minimum isosurface level
-
-<DT><B>max</B>
-<DD>Maximum isosurface level
-
-<DT><B>step</B>
-<DD>Positive increment between isosurface levels
-
-<DT><B>tnum</B>
-<DD>Number of isosurface threshold levels
-<DD>Default: 7
-</DL>
-
-<H2>Example:</H2>
-With grid3 data (<I>phdata</I>) in the range 3-7,
-we only want to see isosurface values for the range 4-6.
-Any of these commands will produce the same results:<br>
-<pre>
-r3.mkdspf phdata dspf=iso min=4.0 max=6.0 tnum=5
-r3.mkdspf phdata dspf=iso levels=4.0,4.5,5.0,5.5,6.0
-r3.mkdspf phdata dspf=iso min=4.0 max=6.0 step=0.5
-</pre>
-
-<H2>NOTE</H2>
-Currently the grid3 file must be in the user's mapset since the
-display files being created are specific to particular grid3
-files and are contained in directories under them.
-We should create a mechanism where users
-may make display files from others' grid3 files without having to
-copy them to their mapset.
-
-<H2>AUTHOR</H2>
-<SIGNATURE>Bill Brown,
-<A HREF="mailto:brown at gis.uiuc.edu">bbrown at gis.uiuc.edu</A>
-</SIGNATURE>
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/raster3d/r3.mkdspf/r3.mkdspf.html (from rev 32770, grass/trunk/raster3d/r3.mkdspf/description.html)
===================================================================
--- grass/trunk/raster3d/r3.mkdspf/r3.mkdspf.html (rev 0)
+++ grass/trunk/raster3d/r3.mkdspf/r3.mkdspf.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,68 @@
+<H2>DESCRIPTION</H2>
+
+Creates a display file from an existing grid3 file according to
+specified threshold levels. The display file is a display list
+of polygons that represent isosurfaces of the data volume. If
+specific <I>levels</I> are given, additional optional parameters
+are ignored. <I>Min</I> or <I>max</I> may be used alone or together
+to specify a sub-range of the data. The <I>step</I>
+parameter is given precedence over <I>tnum</I>.
+
+<H3>Flags:</H3>
+<DL>
+<DT><B>-q</B>
+<DD>Suppress progress report & min/max information
+
+<DT><B>-f</B>
+<DD>Use flat shading rather than gradient
+</DL>
+
+<H3>Parameters:</H3>
+<DL>
+<DT><B>grid3</B>
+<DD>Name of an existing 3d raster map
+
+<DT><B>dspf</B>
+<DD>Name of output display file
+
+<DT><B>levels</B>
+<DD>List of thresholds for isosurfaces
+
+<DT><B>min</B>
+<DD>Minimum isosurface level
+
+<DT><B>max</B>
+<DD>Maximum isosurface level
+
+<DT><B>step</B>
+<DD>Positive increment between isosurface levels
+
+<DT><B>tnum</B>
+<DD>Number of isosurface threshold levels
+<DD>Default: 7
+</DL>
+
+<H2>Example:</H2>
+With grid3 data (<I>phdata</I>) in the range 3-7,
+we only want to see isosurface values for the range 4-6.
+Any of these commands will produce the same results:<br>
+<pre>
+r3.mkdspf phdata dspf=iso min=4.0 max=6.0 tnum=5
+r3.mkdspf phdata dspf=iso levels=4.0,4.5,5.0,5.5,6.0
+r3.mkdspf phdata dspf=iso min=4.0 max=6.0 step=0.5
+</pre>
+
+<H2>NOTE</H2>
+Currently the grid3 file must be in the user's mapset since the
+display files being created are specific to particular grid3
+files and are contained in directories under them.
+We should create a mechanism where users
+may make display files from others' grid3 files without having to
+copy them to their mapset.
+
+<H2>AUTHOR</H2>
+<SIGNATURE>Bill Brown,
+<A HREF="mailto:brown at gis.uiuc.edu">bbrown at gis.uiuc.edu</A>
+</SIGNATURE>
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/raster3d/r3.out.ascii/description.html
===================================================================
--- grass/trunk/raster3d/r3.out.ascii/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster3d/r3.out.ascii/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,56 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-Outputs <I>G3D</I> maps in <I>ascii</I> format. <I>map</I> is
-a valid G3D map in the current mapset. <I>output</I> is the name of
-an ascii file which will be written in the current working directory.
-If <I>output</I> is not specified then <B>stdout</B> is used. The
-<I>-h</I> flag may be used to suppress header information. The module is
-sensitive to region settings (set with g.region).
-
-
-<H2>NOTES</H2>
-The default format for the ascii file is equivalent to that required
-by <EM>r3.in.ascii</EM>. In particular, files output by
-<EM>r3.out.ascii</EM> with header information may be converted back to
-G3D maps with <EM>r3.in.ascii</EM>.
-
-<P>
-The format for the ascii file is:
-<pre>
-north: <i>floating point</i>
-south: <i>floating point</i>
-east: <i>floating point</i>
-west: <i>floating point</i>
-top: <i>floating point</i>
-bottom: <i>floating point</i>
-rows: <i>integer</i>
-cols: <i>integer</i>
-levels: <i>integer</i>
-</pre>
-
-The header is followed by cell values in <EM>floating point</EM> format.
-Cell values are output as a series of horizontal slices in row-major
-order. That is,
-
-<pre>
- (x, y, z) (x + 1, y, z) ... (x + cols, y, z)
-(x, y + 1, z) (x + 1, y + 1, z) ... (x + cols, y + 1, z)
-
- and so on
-
-</pre>
-
-
-<P>
-One level maps can be imported with r.in.ascii (Raster 2D) after removing
-the header lines "top", "bottom" and "levels".
-
-<H2>SEE ALSO</H2>
-<EM><A HREF="r3.in.ascii.html">r3.in.ascii</A></EM><br>
-<EM><A HREF="g.region.html">g.region</A></EM><br>
-
-<H2>AUTHORS</H2>
-Roman Waupotitsch, Michael Shapiro,
-Helena Mitasova, Bill Brown, Lubos Mitas, Jaro Hofierka
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/raster3d/r3.out.ascii/r3.out.ascii.html (from rev 32770, grass/trunk/raster3d/r3.out.ascii/description.html)
===================================================================
--- grass/trunk/raster3d/r3.out.ascii/r3.out.ascii.html (rev 0)
+++ grass/trunk/raster3d/r3.out.ascii/r3.out.ascii.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,56 @@
+<H2>DESCRIPTION</H2>
+
+Outputs <I>G3D</I> maps in <I>ascii</I> format. <I>map</I> is
+a valid G3D map in the current mapset. <I>output</I> is the name of
+an ascii file which will be written in the current working directory.
+If <I>output</I> is not specified then <B>stdout</B> is used. The
+<I>-h</I> flag may be used to suppress header information. The module is
+sensitive to region settings (set with g.region).
+
+
+<H2>NOTES</H2>
+The default format for the ascii file is equivalent to that required
+by <EM>r3.in.ascii</EM>. In particular, files output by
+<EM>r3.out.ascii</EM> with header information may be converted back to
+G3D maps with <EM>r3.in.ascii</EM>.
+
+<P>
+The format for the ascii file is:
+<pre>
+north: <i>floating point</i>
+south: <i>floating point</i>
+east: <i>floating point</i>
+west: <i>floating point</i>
+top: <i>floating point</i>
+bottom: <i>floating point</i>
+rows: <i>integer</i>
+cols: <i>integer</i>
+levels: <i>integer</i>
+</pre>
+
+The header is followed by cell values in <EM>floating point</EM> format.
+Cell values are output as a series of horizontal slices in row-major
+order. That is,
+
+<pre>
+ (x, y, z) (x + 1, y, z) ... (x + cols, y, z)
+(x, y + 1, z) (x + 1, y + 1, z) ... (x + cols, y + 1, z)
+
+ and so on
+
+</pre>
+
+
+<P>
+One level maps can be imported with r.in.ascii (Raster 2D) after removing
+the header lines "top", "bottom" and "levels".
+
+<H2>SEE ALSO</H2>
+<EM><A HREF="r3.in.ascii.html">r3.in.ascii</A></EM><br>
+<EM><A HREF="g.region.html">g.region</A></EM><br>
+
+<H2>AUTHORS</H2>
+Roman Waupotitsch, Michael Shapiro,
+Helena Mitasova, Bill Brown, Lubos Mitas, Jaro Hofierka
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/raster3d/r3.out.v5d/description.html
===================================================================
--- grass/trunk/raster3d/r3.out.v5d/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster3d/r3.out.v5d/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,18 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-Exports <i>G3D</i> grids to <i>v5d</i> format. <i>map</i> is a valid G3D
-grid in the current mapset. <i>output</i> is the name of a v5d file which
-will be written in the current working directory. <a href="http://www.ssec.wisc.edu/~billh/vis5d.html">VIS5D</a>
-is a system for interactive visualization of large 5-D gridded data sets
-such as those produced by numerical weather models. One can make isosurfaces,
-contour line slices, colored slices, volume renderings, etc of data in
-a 3-D grid, then rotate and animate the images in real time. There's also
-a feature for wind trajectory tracing, a way to make text anotations for
-publications, support for interactive data analysis, etc.
-
-<h2>SEE ALSO</h2>
-<i><a href="r3.in.v5d.html">r3.in.v5d</a></i>
-
-<h2>AUTHOR</h2>
-Jaro Hofierka, GeoModel s.r.o., Slovakia
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/raster3d/r3.out.v5d/r3.out.v5d.html (from rev 32770, grass/trunk/raster3d/r3.out.v5d/description.html)
===================================================================
--- grass/trunk/raster3d/r3.out.v5d/r3.out.v5d.html (rev 0)
+++ grass/trunk/raster3d/r3.out.v5d/r3.out.v5d.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,18 @@
+<H2>DESCRIPTION</H2>
+
+Exports <i>G3D</i> grids to <i>v5d</i> format. <i>map</i> is a valid G3D
+grid in the current mapset. <i>output</i> is the name of a v5d file which
+will be written in the current working directory. <a href="http://www.ssec.wisc.edu/~billh/vis5d.html">VIS5D</a>
+is a system for interactive visualization of large 5-D gridded data sets
+such as those produced by numerical weather models. One can make isosurfaces,
+contour line slices, colored slices, volume renderings, etc of data in
+a 3-D grid, then rotate and animate the images in real time. There's also
+a feature for wind trajectory tracing, a way to make text anotations for
+publications, support for interactive data analysis, etc.
+
+<h2>SEE ALSO</h2>
+<i><a href="r3.in.v5d.html">r3.in.v5d</a></i>
+
+<h2>AUTHOR</h2>
+Jaro Hofierka, GeoModel s.r.o., Slovakia
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/raster3d/r3.out.vtk/description.html
===================================================================
--- grass/trunk/raster3d/r3.out.vtk/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster3d/r3.out.vtk/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,174 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-Outputs <I>3D raster</I> maps into <I>VTK-ASCII</I> format. <I>Maps</I> are
-valid 3D raster maps in the current mapset. <I>output</I> is the name of
-a VTK-ASCII file which will be written in the current working directory.
-If <I>output</I> is not specified then <B>stdout</B> is used.
-The module is sensitive to region settings (set with <em>g.region</em>).
-
-<H2>NOTES</H2>
-This filter generates <I>structured points</I> with <I>celldata</I>
-(default) or <I>pointdata</I>. If top and bottom surfaces are requested
-a <I>unstructured grid</I> with <I>celldata</I> or a <I>structured grid</I>
-with <I>pointdata</I> is generated.
-This data is put in a simple VTK-ASCII file. Neither XML nor
-binary output are supported. It is possible to choose more then one G3D map
-to be written in the VTK-ASCII file. Each <I>celldata</I> is named as the
-3D raster map it represents. You can visualize this file with the
-<EM><A HREF="http://www.vtk.org">VTK Toolkit</A></EM>,
-<EM><A HREF="http://www.paraview.org">Paraview</A></EM> and
-<EM><A HREF="http://mayavi.sourceforge.net">MayaVi</A></EM> which are based on VTK.
-If you have a 3D raster map with partly no data, use the threshold filter in paraview to
-visualize the valid data. Just filter all data which is greater/lesser than the
-choosen null value in the VTK-ASCII file.
-
-<BR><BR>
-The top and bottom region settings are expected in meters.
-If a Latitude-Longitude (LL) coordinates are used, the elevation value for each voxel
-will be converted into degree.
-<BR><BR>
-The <I>input</I>, <I>rgbmaps</I> and <I>vectormaps</I> are optional,
-so only the geometry can be exported.
-<BR><BR>
-If you use <I>top</I> and <I>bottom</I> and the 2D and 3D region settings are different,
-the 2D resolution will be adjust to the 3D resolution. The elevation maps are expected
-in meters. If LL coordinates are used, the elevation will automatically converted into degree.
-If the surface and bottom maps are in a different unit than meters, use the scale parameter
-to convert them into meters.
-<BR><BR>
-The RGB voxel data can be created from 2D raster maps (Landsat TM images)
-with <EM><A HREF="r.to.rast3.html">r.to.rast3</A></EM>. The values of the RGB maps
-must be within 0 and 255. If not, the values are automatically set
-to 0 and warnings will be printed to stderr.
-<BR><BR>
-The vector data is created from three 3d raster maps. Each map represents a vector component.
-So x, y and z components are required in this order. This data can be visualized with Glyph3d or
-StreamTracer filters within Paraview.
-<br>
-<br>
-If the <em>-c</em> flag is used and the data should be visualised together with other
-data exported via <em>*.out.vtk</em> modules, be sure the <em>-c</em> flag was also
-set in these modules. But this will only work with data from the SAME location (the
-reference point for the coordinates transformation is based on the center point of
-the default region).
-
-<H3>Difference between point- and celldata</H3>
-
-<em>r3.out.vtk</em> can export 3D raster maps with different representations.
-<ul>
- <li>
- <I>pointdata</I> -- the cells/values are represented by the center of the cell.
- Instead of cells, points are created. Each point can hold different values,
- but the user can only visualize one value at a time.
- </li>
- <li>
- <I>celldata</I>
- The cells are created with the same hight, width and depth as in GRASS. Each cell
- can hold different values, but the user can only visualize one value at a time.
- </li>
-</ul>
-
-<H2>EXAMPLE</H2>
-
-<H3>Simple Spearfish example</H3>
-
-<div class="code"><pre>
-g.region -d
-g.region res=150 res3=150 t=80 b=0 tbres=10
-r.mapcalc "bottom=1800. - elevation.10m"
-
-# synthetic data, could be geological structures:
-r3.mapcalc "map3d=row()+col()+depth()"
-
-#export of volume to VTK:
-r3.out.vtk -s input=map3d top=elevation.10m bottom=bottom output=/tmp/out.vtk
-
-# visualize in paraview or other VTK viewer:
-paraview --data=/tmp/out.vtk
-</pre></div>
-
-<H3>Spearfish example with RGB data</H3>
-
-<div class="code"><pre>
-#set the region
-g.region -d
-g.region n=4926970 s=4914857 w=591583 e=607793 res=50 res3=50 t=80 b=0 tbres=10
-
-#create a bottom surface
-r.mapcalc "bottom=1800. - elevation.10m"
-
-# synthetic data, could be geological structures:
-r3.mapcalc "map3d=row()+col()+depth()"
-
-#get some satellite images with r.in.onearth
-r.in.onearth -l output=Sat tmband=Red
-r.in.onearth -l output=Sat tmband=IR1
-r.in.onearth -l output=Sat tmband=IR2
-
-#Convert the 2d maps to 3d raster maps with r.to.rast3
-r.to.rast3 input=SatLandsatTM_Red output=SatLandsatTM_Red
-r.to.rast3 input=SatLandsatTM_IR1 output=SatLandsatTM_IR1
-r.to.rast3 input=SatLandsatTM_IR2 output=SatLandsatTM_IR2
-
-#export of volume to VTK:
-r3.out.vtk -s rgbmaps=SatLandsatTM_IR1,SatLandsatTM_IR2,SatLandsatTM_Red input=map3d top=elevation.10m bottom=bottom output=/tmp/out.vtk
-
-# visualize in paraview or other VTK viewer:
-paraview --data=/tmp/out.vtk
-</pre></div>
-
-<H3>Spearfish example with vector data</H3>
-
-<div class="code"><pre>
-# set the region
-g.region -d
-g.region n=4926970 s=4914857 w=591583 e=607793 res=50 res3=50 t=80 b=0 tbres=10
-
-# create a bottom surface
-r.mapcalc "bottom=1800. - elevation.10m"
-
-# synthetic data, could be geological structures:
-r3.mapcalc "map3d=row()+col()+depth()"
-
-# synthetic vector data, could be groundwater stream vectors
-r3.mapcalc "x_part =sin(row())"
-r3.mapcalc "y_part =cos(col())"
-r3.mapcalc "z_part =sin(depth())"
-
-
-# export the stuff data to VTK:
-r3.out.vtk -s vectormaps=x_part,y_part,z_part input=map3d top=elevation.10m bottom=bottom output=/tmp/out.vtk
-
-# visualize in paraview or other VTK viewer:
-paraview --data=/tmp/out.vtk
-# Now use the Glyph and Stream-Trace Filter to get nice vectors and streamlines
-</pre></div>
-
-
-<H3>Slovakia3d example</H3>
-
-<div class="code"><pre>
-#reduce resolution:
-g.region -dp3 res=1000 res3=1000
-r.mapcalc "bottom=100"
-
-#export of volume to VTK:
-r3.out.vtk -s in=precip3d.500z50 top=dem500 bottom=bottom out=/tmp/slovakia3d.vtk
-
-# visualize in paraview or other VTK viewer:
-paraview --data=/tmp/slovakia3d.vtk
-# set Display style to 'surface#
-# set Actor Control z to 10
-</pre></div>
-
-
-<H2>SEE ALSO</H2>
-
-<EM><A HREF="r.out.vtk.html">r.out.vtk</A></EM><br>
-<EM><A HREF="r3.out.ascii.html">r3.out.ascii</A></EM><br>
-<EM><A HREF="g.region.html">g.region</A></EM><br>
-
-<H2>AUTHOR</H2>
-Soeren Gebbert
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/raster3d/r3.out.vtk/r3.out.vtk.html (from rev 32770, grass/trunk/raster3d/r3.out.vtk/description.html)
===================================================================
--- grass/trunk/raster3d/r3.out.vtk/r3.out.vtk.html (rev 0)
+++ grass/trunk/raster3d/r3.out.vtk/r3.out.vtk.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,174 @@
+<H2>DESCRIPTION</H2>
+
+Outputs <I>3D raster</I> maps into <I>VTK-ASCII</I> format. <I>Maps</I> are
+valid 3D raster maps in the current mapset. <I>output</I> is the name of
+a VTK-ASCII file which will be written in the current working directory.
+If <I>output</I> is not specified then <B>stdout</B> is used.
+The module is sensitive to region settings (set with <em>g.region</em>).
+
+<H2>NOTES</H2>
+This filter generates <I>structured points</I> with <I>celldata</I>
+(default) or <I>pointdata</I>. If top and bottom surfaces are requested
+a <I>unstructured grid</I> with <I>celldata</I> or a <I>structured grid</I>
+with <I>pointdata</I> is generated.
+This data is put in a simple VTK-ASCII file. Neither XML nor
+binary output are supported. It is possible to choose more then one G3D map
+to be written in the VTK-ASCII file. Each <I>celldata</I> is named as the
+3D raster map it represents. You can visualize this file with the
+<EM><A HREF="http://www.vtk.org">VTK Toolkit</A></EM>,
+<EM><A HREF="http://www.paraview.org">Paraview</A></EM> and
+<EM><A HREF="http://mayavi.sourceforge.net">MayaVi</A></EM> which are based on VTK.
+If you have a 3D raster map with partly no data, use the threshold filter in paraview to
+visualize the valid data. Just filter all data which is greater/lesser than the
+choosen null value in the VTK-ASCII file.
+
+<BR><BR>
+The top and bottom region settings are expected in meters.
+If a Latitude-Longitude (LL) coordinates are used, the elevation value for each voxel
+will be converted into degree.
+<BR><BR>
+The <I>input</I>, <I>rgbmaps</I> and <I>vectormaps</I> are optional,
+so only the geometry can be exported.
+<BR><BR>
+If you use <I>top</I> and <I>bottom</I> and the 2D and 3D region settings are different,
+the 2D resolution will be adjust to the 3D resolution. The elevation maps are expected
+in meters. If LL coordinates are used, the elevation will automatically converted into degree.
+If the surface and bottom maps are in a different unit than meters, use the scale parameter
+to convert them into meters.
+<BR><BR>
+The RGB voxel data can be created from 2D raster maps (Landsat TM images)
+with <EM><A HREF="r.to.rast3.html">r.to.rast3</A></EM>. The values of the RGB maps
+must be within 0 and 255. If not, the values are automatically set
+to 0 and warnings will be printed to stderr.
+<BR><BR>
+The vector data is created from three 3d raster maps. Each map represents a vector component.
+So x, y and z components are required in this order. This data can be visualized with Glyph3d or
+StreamTracer filters within Paraview.
+<br>
+<br>
+If the <em>-c</em> flag is used and the data should be visualised together with other
+data exported via <em>*.out.vtk</em> modules, be sure the <em>-c</em> flag was also
+set in these modules. But this will only work with data from the SAME location (the
+reference point for the coordinates transformation is based on the center point of
+the default region).
+
+<H3>Difference between point- and celldata</H3>
+
+<em>r3.out.vtk</em> can export 3D raster maps with different representations.
+<ul>
+ <li>
+ <I>pointdata</I> -- the cells/values are represented by the center of the cell.
+ Instead of cells, points are created. Each point can hold different values,
+ but the user can only visualize one value at a time.
+ </li>
+ <li>
+ <I>celldata</I>
+ The cells are created with the same hight, width and depth as in GRASS. Each cell
+ can hold different values, but the user can only visualize one value at a time.
+ </li>
+</ul>
+
+<H2>EXAMPLE</H2>
+
+<H3>Simple Spearfish example</H3>
+
+<div class="code"><pre>
+g.region -d
+g.region res=150 res3=150 t=80 b=0 tbres=10
+r.mapcalc "bottom=1800. - elevation.10m"
+
+# synthetic data, could be geological structures:
+r3.mapcalc "map3d=row()+col()+depth()"
+
+#export of volume to VTK:
+r3.out.vtk -s input=map3d top=elevation.10m bottom=bottom output=/tmp/out.vtk
+
+# visualize in paraview or other VTK viewer:
+paraview --data=/tmp/out.vtk
+</pre></div>
+
+<H3>Spearfish example with RGB data</H3>
+
+<div class="code"><pre>
+#set the region
+g.region -d
+g.region n=4926970 s=4914857 w=591583 e=607793 res=50 res3=50 t=80 b=0 tbres=10
+
+#create a bottom surface
+r.mapcalc "bottom=1800. - elevation.10m"
+
+# synthetic data, could be geological structures:
+r3.mapcalc "map3d=row()+col()+depth()"
+
+#get some satellite images with r.in.onearth
+r.in.onearth -l output=Sat tmband=Red
+r.in.onearth -l output=Sat tmband=IR1
+r.in.onearth -l output=Sat tmband=IR2
+
+#Convert the 2d maps to 3d raster maps with r.to.rast3
+r.to.rast3 input=SatLandsatTM_Red output=SatLandsatTM_Red
+r.to.rast3 input=SatLandsatTM_IR1 output=SatLandsatTM_IR1
+r.to.rast3 input=SatLandsatTM_IR2 output=SatLandsatTM_IR2
+
+#export of volume to VTK:
+r3.out.vtk -s rgbmaps=SatLandsatTM_IR1,SatLandsatTM_IR2,SatLandsatTM_Red input=map3d top=elevation.10m bottom=bottom output=/tmp/out.vtk
+
+# visualize in paraview or other VTK viewer:
+paraview --data=/tmp/out.vtk
+</pre></div>
+
+<H3>Spearfish example with vector data</H3>
+
+<div class="code"><pre>
+# set the region
+g.region -d
+g.region n=4926970 s=4914857 w=591583 e=607793 res=50 res3=50 t=80 b=0 tbres=10
+
+# create a bottom surface
+r.mapcalc "bottom=1800. - elevation.10m"
+
+# synthetic data, could be geological structures:
+r3.mapcalc "map3d=row()+col()+depth()"
+
+# synthetic vector data, could be groundwater stream vectors
+r3.mapcalc "x_part =sin(row())"
+r3.mapcalc "y_part =cos(col())"
+r3.mapcalc "z_part =sin(depth())"
+
+
+# export the stuff data to VTK:
+r3.out.vtk -s vectormaps=x_part,y_part,z_part input=map3d top=elevation.10m bottom=bottom output=/tmp/out.vtk
+
+# visualize in paraview or other VTK viewer:
+paraview --data=/tmp/out.vtk
+# Now use the Glyph and Stream-Trace Filter to get nice vectors and streamlines
+</pre></div>
+
+
+<H3>Slovakia3d example</H3>
+
+<div class="code"><pre>
+#reduce resolution:
+g.region -dp3 res=1000 res3=1000
+r.mapcalc "bottom=100"
+
+#export of volume to VTK:
+r3.out.vtk -s in=precip3d.500z50 top=dem500 bottom=bottom out=/tmp/slovakia3d.vtk
+
+# visualize in paraview or other VTK viewer:
+paraview --data=/tmp/slovakia3d.vtk
+# set Display style to 'surface#
+# set Actor Control z to 10
+</pre></div>
+
+
+<H2>SEE ALSO</H2>
+
+<EM><A HREF="r.out.vtk.html">r.out.vtk</A></EM><br>
+<EM><A HREF="r3.out.ascii.html">r3.out.ascii</A></EM><br>
+<EM><A HREF="g.region.html">g.region</A></EM><br>
+
+<H2>AUTHOR</H2>
+Soeren Gebbert
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/raster3d/r3.showdspf/description.html
===================================================================
--- grass/trunk/raster3d/r3.showdspf/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster3d/r3.showdspf/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,151 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-
-Visualization program which loads the isosurfaces previously calculated
-using r3.mkdspf and displays them according to commands given at the prompt.
-r3.mkdspf creates a dspf file from the 3D raster and r3.showdspf uses this
-dspf file to draw isosurfaces and 3d raster map to draw planes and everything
-related (boxes, etc).<br>
-
-Upon initialization of the program, two graphics windows are
-opened, one for the color table and the other for data display. The
-display window initially contains a red bounding box. Command options
-are then printed to the terminal and user is prompted for drawing
-instructions:
-
-<BR>
-<pre>
-THE INTERACTIVE OPTIONS ARE:
-
-?, (l #), L, (t #), (T # #), I, +, -
-(x #) (y #) (z #) r (X #) (Y #) (Z #)
-(B(x,y,z)#), (E(x,y,z)#), S, R, F, C, c, s, b, g, n, p[#], d, D, w, Q, h
-
- USAGE AND MEANING:
-
- <B>?</B> lists available thresholds
- <B>l index# [index#...]</B> add threshold to display list
- <B>L</B> Draw current display list
- <B>t index#</B> reset so only this threshold is displayed
- <B>T index# index#</B> show thresholds between hi & lo
- <B>I</B> toggle thresholds INSIDE hi/lo or OUTSIDE hi/lo
- <B>+(+++)</B> display thresholds with consecutively increasing index#
- <B>-(---)</B> display thresholds with consecutively decreasing index#
-
- <B>x int#</B> absolute rotation around x-axis in degrees(int)
- <B>y int#</B> absolute rotation around y-axis in degrees(int)
- <B>z int#</B> absolute rotation around z-axis in degrees(int)
- <B>r</B> rotate_model
- <B>X int#</B> scale model in x
- <B>Y int#</B> scale model in y
- <B>Z int#</B> scale model in z
-
- <B>B(x,y,z)int#</B> begin display along (x,y,z) axis at #
- <B>E(x,y,z)int#</B> end display along (x,y,z)axis #
- <B>S int#</B> specular highlight control
- <B>R</B> resets display along axis to show all data
- <B>F <I>grid3name colortablename</I></B> load new color file
-
- <B>C</B> toggles the clear flag
- <B>c</B> clears the display (no thresholds)
- <B>s</B> swap buffers
- <B>b</B> toggles draw a box
- <B>g</B> toggles grid
- <B>n</B> toggle surface normal direction
-
- <B>p</B> draw all walls
- <B>p#</B> draw a wall: 1-top, 2-bottom, 3-east, 4-west, 5-north, 6-south
-
- <B>d</B> draw (implement the option)
- <B>D</B> draw a solid defined by T(isosurface + parts of walls)
-
- <B>w</B> dump image to a file
- <B>Q</B> QUIT
- <B>h</B> help
-
- enter desired manipulations then press return
- >>
-
-</pre>
-<p>
-
-<H3>Hints:</H3>
-<UL>
-<LI>To navigate around the data, use the <B>r</B> command, then place
-the mouse pointer in the graphics window and drag with the left mouse
-to rotate the bounding box. To zoom in and out, drag right or left
-with the middle mouse. When satisfied with the new viewing
-position, click with the right mouse.
-
-<LI>To quickly view a series of isosurfaces, enter a series of + or -
-characters, i.e. <B>+++++++</B>
-
-<LI>Scripts using above commands on separate lines may be
-directed to r3.showdspf as standard input.
-Use the <B>#</B> sign as the first character on a line to indicate a comment.
-</UL>
-
-<H2>EXAMPLE</H2>
-
-After generating a "dspf" control file with <em>r3.mkdspf</em> start
-<em>r3.showdspf</em>. Display/add the layers using "+".<br>
-
-List available thresholds with "?". Use "l" to select isosurfaces (available
-number can be adjusted with <em>r3.mkdspf</em>) and "L" to display:<br>
-<tt>l 1 2 3 4 5<br> L </tt> <p>
-
-To select and display a single threshold (here: 2), use:<br>
-<tt>t 2</tt> <p>
-
-To select and display a range of thresholds (here: 3-5), use:<br>
-<tt>T 3 5<br>
-D</tt> <p>
-
-To draw a box, enter<br>
-<tt>p</tt><br>
-the p# to plot a selected wall (here top wall):<br>
-<tt>p1</tt><p>
-
-Tp draw a cut-off box, define it's position<br>
-<tt>Ex20</tt><br>
-<tt>p</tt><br>
-Here Ex20 defines the x coordinate of the end of the box.<p>
-
-In general - p draws a side of a box, E, B, define where that box starts or
-ends, so to make a fence diagram, the user draws sides of a series of boxes
-which have their starting (or ending) side shifting by a given interval.
-(this way the user can draw even more complex fence diagrams which have
-perpendicular fences, by using Ey or By). It is sufficient to use only E or
-B depending whether fence are drawn by using the end side or front side of a
-box).<br>
-
-To draw a fence, a sequence like this would be needed<br>
-<tt>Ex10<br>
-p5<br>
-Ex15<br>
-p5<br>
-Ex20<br>
-p5<br>
-Ex25<br>
-p5<br>
-</tt>
-
-or the same would be<br>
-<tt>Bx10<br>
-p6<br>
-Bx15<br>
-p6<br>
-Bx20<br>
-p6</tt>
-<p>
-
-The <em>p</em> is needed for the fence diagram, solids and boxes.
-
-<H2>SEE ALSO</H2>
-<EM><A HREF="r3.mkdspf.html">r3.mkdspf</A></EM>
-<H2>AUTHORS</H2>
-<SIGNATURE>Bill Brown,
-<A HREF="mailto:brown at gis.uiuc.edu">brown at gis.uiuc.edu</A>
-</SIGNATURE>
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/raster3d/r3.showdspf/r3.showdspf.html (from rev 32770, grass/trunk/raster3d/r3.showdspf/description.html)
===================================================================
--- grass/trunk/raster3d/r3.showdspf/r3.showdspf.html (rev 0)
+++ grass/trunk/raster3d/r3.showdspf/r3.showdspf.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,151 @@
+<H2>DESCRIPTION</H2>
+
+
+Visualization program which loads the isosurfaces previously calculated
+using r3.mkdspf and displays them according to commands given at the prompt.
+r3.mkdspf creates a dspf file from the 3D raster and r3.showdspf uses this
+dspf file to draw isosurfaces and 3d raster map to draw planes and everything
+related (boxes, etc).<br>
+
+Upon initialization of the program, two graphics windows are
+opened, one for the color table and the other for data display. The
+display window initially contains a red bounding box. Command options
+are then printed to the terminal and user is prompted for drawing
+instructions:
+
+<BR>
+<pre>
+THE INTERACTIVE OPTIONS ARE:
+
+?, (l #), L, (t #), (T # #), I, +, -
+(x #) (y #) (z #) r (X #) (Y #) (Z #)
+(B(x,y,z)#), (E(x,y,z)#), S, R, F, C, c, s, b, g, n, p[#], d, D, w, Q, h
+
+ USAGE AND MEANING:
+
+ <B>?</B> lists available thresholds
+ <B>l index# [index#...]</B> add threshold to display list
+ <B>L</B> Draw current display list
+ <B>t index#</B> reset so only this threshold is displayed
+ <B>T index# index#</B> show thresholds between hi & lo
+ <B>I</B> toggle thresholds INSIDE hi/lo or OUTSIDE hi/lo
+ <B>+(+++)</B> display thresholds with consecutively increasing index#
+ <B>-(---)</B> display thresholds with consecutively decreasing index#
+
+ <B>x int#</B> absolute rotation around x-axis in degrees(int)
+ <B>y int#</B> absolute rotation around y-axis in degrees(int)
+ <B>z int#</B> absolute rotation around z-axis in degrees(int)
+ <B>r</B> rotate_model
+ <B>X int#</B> scale model in x
+ <B>Y int#</B> scale model in y
+ <B>Z int#</B> scale model in z
+
+ <B>B(x,y,z)int#</B> begin display along (x,y,z) axis at #
+ <B>E(x,y,z)int#</B> end display along (x,y,z)axis #
+ <B>S int#</B> specular highlight control
+ <B>R</B> resets display along axis to show all data
+ <B>F <I>grid3name colortablename</I></B> load new color file
+
+ <B>C</B> toggles the clear flag
+ <B>c</B> clears the display (no thresholds)
+ <B>s</B> swap buffers
+ <B>b</B> toggles draw a box
+ <B>g</B> toggles grid
+ <B>n</B> toggle surface normal direction
+
+ <B>p</B> draw all walls
+ <B>p#</B> draw a wall: 1-top, 2-bottom, 3-east, 4-west, 5-north, 6-south
+
+ <B>d</B> draw (implement the option)
+ <B>D</B> draw a solid defined by T(isosurface + parts of walls)
+
+ <B>w</B> dump image to a file
+ <B>Q</B> QUIT
+ <B>h</B> help
+
+ enter desired manipulations then press return
+ >>
+
+</pre>
+<p>
+
+<H3>Hints:</H3>
+<UL>
+<LI>To navigate around the data, use the <B>r</B> command, then place
+the mouse pointer in the graphics window and drag with the left mouse
+to rotate the bounding box. To zoom in and out, drag right or left
+with the middle mouse. When satisfied with the new viewing
+position, click with the right mouse.
+
+<LI>To quickly view a series of isosurfaces, enter a series of + or -
+characters, i.e. <B>+++++++</B>
+
+<LI>Scripts using above commands on separate lines may be
+directed to r3.showdspf as standard input.
+Use the <B>#</B> sign as the first character on a line to indicate a comment.
+</UL>
+
+<H2>EXAMPLE</H2>
+
+After generating a "dspf" control file with <em>r3.mkdspf</em> start
+<em>r3.showdspf</em>. Display/add the layers using "+".<br>
+
+List available thresholds with "?". Use "l" to select isosurfaces (available
+number can be adjusted with <em>r3.mkdspf</em>) and "L" to display:<br>
+<tt>l 1 2 3 4 5<br> L </tt> <p>
+
+To select and display a single threshold (here: 2), use:<br>
+<tt>t 2</tt> <p>
+
+To select and display a range of thresholds (here: 3-5), use:<br>
+<tt>T 3 5<br>
+D</tt> <p>
+
+To draw a box, enter<br>
+<tt>p</tt><br>
+the p# to plot a selected wall (here top wall):<br>
+<tt>p1</tt><p>
+
+Tp draw a cut-off box, define it's position<br>
+<tt>Ex20</tt><br>
+<tt>p</tt><br>
+Here Ex20 defines the x coordinate of the end of the box.<p>
+
+In general - p draws a side of a box, E, B, define where that box starts or
+ends, so to make a fence diagram, the user draws sides of a series of boxes
+which have their starting (or ending) side shifting by a given interval.
+(this way the user can draw even more complex fence diagrams which have
+perpendicular fences, by using Ey or By). It is sufficient to use only E or
+B depending whether fence are drawn by using the end side or front side of a
+box).<br>
+
+To draw a fence, a sequence like this would be needed<br>
+<tt>Ex10<br>
+p5<br>
+Ex15<br>
+p5<br>
+Ex20<br>
+p5<br>
+Ex25<br>
+p5<br>
+</tt>
+
+or the same would be<br>
+<tt>Bx10<br>
+p6<br>
+Bx15<br>
+p6<br>
+Bx20<br>
+p6</tt>
+<p>
+
+The <em>p</em> is needed for the fence diagram, solids and boxes.
+
+<H2>SEE ALSO</H2>
+<EM><A HREF="r3.mkdspf.html">r3.mkdspf</A></EM>
+<H2>AUTHORS</H2>
+<SIGNATURE>Bill Brown,
+<A HREF="mailto:brown at gis.uiuc.edu">brown at gis.uiuc.edu</A>
+</SIGNATURE>
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/raster3d/r3.stats/description.html
===================================================================
--- grass/trunk/raster3d/r3.stats/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster3d/r3.stats/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,105 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-<EM>r3.stats</EM> calculates volume statistics for raster3d maps.
-Volumes are created on base of value subranges or groups of equal values.
-The default number of subranges is 20 and can vary from 1 to infinite.
-Larger subranges will result in larger memory consumption.
-The volumes are calculated in qubic meters. Null values are marked with "*".
-If the flag <em>-e</em> is set, the number of subrange will be ignored.
-
-<H2>NOTES</H2>
-
-As with most GRASS raster3d modules, <EM>r3.univar</EM> operates on the cell
-array defined by the current 3d region settings, not the original extent and
-resolution of the input map. See <em><A HREF="g.region.html">g.region</A></em>.
-<P>
-The region setting will not effect the memory consumption of this module.
-The number of subranges in case of value range calculation or the number of
-equal value groups effect the memory consumption and the calculation time.
-You can expect a huge time consumption to calculate the equal value groups (flag <em>-e</em>)
-if you use large region settings + maps which have many equal value groups (> 100000).
-
-<H2>EXAMPLES</H2>
-<H3>Lausanne FOSS4G 2006 3d demo dataset example</H3>
-
-The 3d raster map <em>geology</em> has three values. Each value represents
-a specific geological layer, clay = 1, sand = 2 and bedrock = 3. To calculate
-the volume of each geological layer, we can use the flag <em>-e</em> to group
-equal values into single volumes.
-<em>r3.stats geology -e</em> will produce the following output:<br><br>
-
-<div class="code"><pre>
- num | value | volume | perc | count
- 1 1.000000 300822000.000 50.13700 50137
- 2 2.000000 101400000.000 16.90000 16900
- 3 3.000000 197778000.000 32.96300 32963
- 4 * 0.000 0.00000 0
-
-Number of groups with equal values: 3
-Sum of non Null cells:
- Volume = 600000000.000
- Percentage = 100.000
- Count = 100000
-
-Sum of all cells:
- Volume = 600000000.000
- Percentage = 100.000
- Count = 100000
-
-</pre></div>
-<H3>Generic example</H3>
-
-<div class="code"><pre>
-#create a small 3d region
-g.region n=1000 s=0 e=2000 w=0 t=300 b=0 res3=100
-
-#create a raster3d map with row() and null values
-r3.mapcalc "volmap = if(row() == 5, null(), row())"
-
-#run r3.stats with a subrange of 10
-r3.stats input=volmap nsteps=10
-
-#the result should look like this
- num | minimum <= value | value < maximum | volume | perc | cell count
- 1 1.000000000 1.900000000 60000000.000 10.00000 60
- 2 1.900000000 2.800000000 60000000.000 10.00000 60
- 3 2.800000000 3.700000000 60000000.000 10.00000 60
- 4 3.700000000 4.600000000 60000000.000 10.00000 60
- 5 4.600000000 5.500000000 0.000 0.00000 0
- 6 5.500000000 6.400000000 60000000.000 10.00000 60
- 7 6.400000000 7.300000000 60000000.000 10.00000 60
- 8 7.300000000 8.200000000 60000000.000 10.00000 60
- 9 8.200000000 9.100000000 60000000.000 10.00000 60
- 10 9.100000000 10.000000001 60000000.000 10.00000 60
- 11 * * 60000000.000 10.00000 60
-
-Sum of non Null cells:
- Volume = 540000000.000
- Percentage = 90.000
- Cell count = 540
-
-Sum of all cells:
- Volume = 600000000.000
- Percentage = 100.000
- Cell count = 600
-
-
-</pre></div>
-
-<H2>SEE ALSO</H2>
-
-<em>
-<A HREF="g.region.html">g.region</A><br>
-<A HREF="r3.univar.html">r3.univar</A><br>
-<A HREF="r.stats.html">r.stats</A><br>
-<A HREF="r.statistics.html">r.statistics</A><br>
-<A HREF="v.univar.html">v.univar</A><br>
-</em>
-
-
-<H2>AUTHORS</H2>
-
-Soeren Gebbert<br>
-
-<p>
-<i>Last changed: $Date$</i>
Copied: grass/trunk/raster3d/r3.stats/r3.stats.html (from rev 32770, grass/trunk/raster3d/r3.stats/description.html)
===================================================================
--- grass/trunk/raster3d/r3.stats/r3.stats.html (rev 0)
+++ grass/trunk/raster3d/r3.stats/r3.stats.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,105 @@
+<H2>DESCRIPTION</H2>
+
+<EM>r3.stats</EM> calculates volume statistics for raster3d maps.
+Volumes are created on base of value subranges or groups of equal values.
+The default number of subranges is 20 and can vary from 1 to infinite.
+Larger subranges will result in larger memory consumption.
+The volumes are calculated in qubic meters. Null values are marked with "*".
+If the flag <em>-e</em> is set, the number of subrange will be ignored.
+
+<H2>NOTES</H2>
+
+As with most GRASS raster3d modules, <EM>r3.univar</EM> operates on the cell
+array defined by the current 3d region settings, not the original extent and
+resolution of the input map. See <em><A HREF="g.region.html">g.region</A></em>.
+<P>
+The region setting will not effect the memory consumption of this module.
+The number of subranges in case of value range calculation or the number of
+equal value groups effect the memory consumption and the calculation time.
+You can expect a huge time consumption to calculate the equal value groups (flag <em>-e</em>)
+if you use large region settings + maps which have many equal value groups (> 100000).
+
+<H2>EXAMPLES</H2>
+<H3>Lausanne FOSS4G 2006 3d demo dataset example</H3>
+
+The 3d raster map <em>geology</em> has three values. Each value represents
+a specific geological layer, clay = 1, sand = 2 and bedrock = 3. To calculate
+the volume of each geological layer, we can use the flag <em>-e</em> to group
+equal values into single volumes.
+<em>r3.stats geology -e</em> will produce the following output:<br><br>
+
+<div class="code"><pre>
+ num | value | volume | perc | count
+ 1 1.000000 300822000.000 50.13700 50137
+ 2 2.000000 101400000.000 16.90000 16900
+ 3 3.000000 197778000.000 32.96300 32963
+ 4 * 0.000 0.00000 0
+
+Number of groups with equal values: 3
+Sum of non Null cells:
+ Volume = 600000000.000
+ Percentage = 100.000
+ Count = 100000
+
+Sum of all cells:
+ Volume = 600000000.000
+ Percentage = 100.000
+ Count = 100000
+
+</pre></div>
+<H3>Generic example</H3>
+
+<div class="code"><pre>
+#create a small 3d region
+g.region n=1000 s=0 e=2000 w=0 t=300 b=0 res3=100
+
+#create a raster3d map with row() and null values
+r3.mapcalc "volmap = if(row() == 5, null(), row())"
+
+#run r3.stats with a subrange of 10
+r3.stats input=volmap nsteps=10
+
+#the result should look like this
+ num | minimum <= value | value < maximum | volume | perc | cell count
+ 1 1.000000000 1.900000000 60000000.000 10.00000 60
+ 2 1.900000000 2.800000000 60000000.000 10.00000 60
+ 3 2.800000000 3.700000000 60000000.000 10.00000 60
+ 4 3.700000000 4.600000000 60000000.000 10.00000 60
+ 5 4.600000000 5.500000000 0.000 0.00000 0
+ 6 5.500000000 6.400000000 60000000.000 10.00000 60
+ 7 6.400000000 7.300000000 60000000.000 10.00000 60
+ 8 7.300000000 8.200000000 60000000.000 10.00000 60
+ 9 8.200000000 9.100000000 60000000.000 10.00000 60
+ 10 9.100000000 10.000000001 60000000.000 10.00000 60
+ 11 * * 60000000.000 10.00000 60
+
+Sum of non Null cells:
+ Volume = 540000000.000
+ Percentage = 90.000
+ Cell count = 540
+
+Sum of all cells:
+ Volume = 600000000.000
+ Percentage = 100.000
+ Cell count = 600
+
+
+</pre></div>
+
+<H2>SEE ALSO</H2>
+
+<em>
+<A HREF="g.region.html">g.region</A><br>
+<A HREF="r3.univar.html">r3.univar</A><br>
+<A HREF="r.stats.html">r.stats</A><br>
+<A HREF="r.statistics.html">r.statistics</A><br>
+<A HREF="v.univar.html">v.univar</A><br>
+</em>
+
+
+<H2>AUTHORS</H2>
+
+Soeren Gebbert<br>
+
+<p>
+<i>Last changed: $Date$</i>
Deleted: grass/trunk/raster3d/r3.to.rast/description.html
===================================================================
--- grass/trunk/raster3d/r3.to.rast/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/raster3d/r3.to.rast/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,36 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-Converts one G3D raster map into several 2D raster maps (depends on depths).
-If the 2d and 3d region settings are different,
-the 3d resolution will be adjust to the 2d resolution (the depths are not touched!).
-You can force r3.to.rast to use the 2d resolution of the input G3D map for the output maps,
-independently from the current region settings.
-
-<center>
-<img src=r3.to.rast.png border=0><BR>
-<table border=0 width=700>
-<tr><td><center>
-<i>How r3.to.rast works</i>
-</center></td></tr>
-</table>
-</center>
-
-
-<H2>NOTES</H2>
-Every slice of the G3D map is copied to one 2D raster map. The maps
-are named like <B>output</B><I>_slicenumber</I>. Slices are counted from bottom
-to the top, so the bottom slice has number 1.
-
-The number of slices is equal to the number of depths.
-
-<H2>SEE ALSO</H2>
-
-<EM><A HREF="r3.cross.rast.html">r3.cross.rast</A></EM><br>
-<EM><A HREF="r3.out.vtk.html">r3.out.vtk</A></EM><br>
-<EM><A HREF="r3.out.ascii.html">r3.out.ascii</A></EM><br>
-<EM><A HREF="g.region.html">g.region</A></EM><br>
-
-<H2>AUTHOR</H2>
-Soeren Gebbert
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/raster3d/r3.to.rast/r3.to.rast.html (from rev 32770, grass/trunk/raster3d/r3.to.rast/description.html)
===================================================================
--- grass/trunk/raster3d/r3.to.rast/r3.to.rast.html (rev 0)
+++ grass/trunk/raster3d/r3.to.rast/r3.to.rast.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,36 @@
+<H2>DESCRIPTION</H2>
+
+Converts one G3D raster map into several 2D raster maps (depends on depths).
+If the 2d and 3d region settings are different,
+the 3d resolution will be adjust to the 2d resolution (the depths are not touched!).
+You can force r3.to.rast to use the 2d resolution of the input G3D map for the output maps,
+independently from the current region settings.
+
+<center>
+<img src=r3.to.rast.png border=0><BR>
+<table border=0 width=700>
+<tr><td><center>
+<i>How r3.to.rast works</i>
+</center></td></tr>
+</table>
+</center>
+
+
+<H2>NOTES</H2>
+Every slice of the G3D map is copied to one 2D raster map. The maps
+are named like <B>output</B><I>_slicenumber</I>. Slices are counted from bottom
+to the top, so the bottom slice has number 1.
+
+The number of slices is equal to the number of depths.
+
+<H2>SEE ALSO</H2>
+
+<EM><A HREF="r3.cross.rast.html">r3.cross.rast</A></EM><br>
+<EM><A HREF="r3.out.vtk.html">r3.out.vtk</A></EM><br>
+<EM><A HREF="r3.out.ascii.html">r3.out.ascii</A></EM><br>
+<EM><A HREF="g.region.html">g.region</A></EM><br>
+
+<H2>AUTHOR</H2>
+Soeren Gebbert
+
+<p><i>Last changed: $Date$</i>
Copied: grass/trunk/scripts/d.correlate/d.correlate.html (from rev 32770, grass/trunk/scripts/d.correlate/description.html)
===================================================================
--- grass/trunk/scripts/d.correlate/d.correlate.html (rev 0)
+++ grass/trunk/scripts/d.correlate/d.correlate.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,73 @@
+<H2>DESCRIPTION</H2>
+
+<EM>d.correlate</EM> is a shell (sh(1)) script that
+graphically displays the results of an
+
+<EM><A HREF="r.stats.html">r.stats</A></EM>
+
+run on two raster map layers. This shell script is useful
+for highlighting the correlation (or lack of it) among data
+layers (scattergram).
+
+<P>
+
+The results are displayed in the active display frame on
+the user's graphics monitor. <EM>d.correlate</EM> erases
+the active frame before displaying results.
+
+<H2>OPTIONS</H2>
+
+<H3>Parameters:</H3>
+
+<DL>
+
+<DT><EM>layer1 layer2 </EM>[<EM>layer3</EM> [<EM>layer4</EM>]]
+
+<DD>The names of from two to four existing raster map layers
+to be included in the correlation.
+</DL>
+
+<H2>NOTES</H2>
+
+This is a shell script that uses
+<EM><A HREF="r.stats.html">r.stats</A></EM>
+and the UNIX <EM>awk</EM> command
+to calculate the correlation among data layers,
+and uses
+<EM><A HREF="d.text.html">d.text</A></EM> and
+<EM><A HREF="d.graph.html">d.graph</A></EM> to display the results.
+
+<P>
+
+If three or four map layers are specified, the correlation
+among each combination of two data layers is displayed.
+
+<H2>FILES</H2>
+
+This program is simply a shell script. Users are
+encouraged to make their own shell script programs using
+similar techniques. See <KBD>$GISBASE/scripts/d.correlate</KBD>.
+
+<H2>SEE ALSO</H2>
+
+The UNIX <EM>awk</EM> command.
+
+
+<P>
+
+<EM>
+<A HREF="d.text.html">d.text</A>,
+<A HREF="d.graph.html">d.graph</A>,
+<A HREF="r.coin.html">r.coin</A>,
+<A HREF="r.regression.line.html">r.regression.line</A>,
+<A HREF="r.stats.html">r.stats</A>
+</EM>
+
+<H2>AUTHOR</H2>
+
+Michael Shapiro,
+<A HREF="http://www.cecer.army.mil/">U.S.Army Construction Engineering
+Research Laboratory</A>
+<p>
+Rewritten to GRASS 6 (from csh to sh) by Markus Neteler
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/scripts/d.correlate/description.html
===================================================================
--- grass/trunk/scripts/d.correlate/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/scripts/d.correlate/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,73 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-<EM>d.correlate</EM> is a shell (sh(1)) script that
-graphically displays the results of an
-
-<EM><A HREF="r.stats.html">r.stats</A></EM>
-
-run on two raster map layers. This shell script is useful
-for highlighting the correlation (or lack of it) among data
-layers (scattergram).
-
-<P>
-
-The results are displayed in the active display frame on
-the user's graphics monitor. <EM>d.correlate</EM> erases
-the active frame before displaying results.
-
-<H2>OPTIONS</H2>
-
-<H3>Parameters:</H3>
-
-<DL>
-
-<DT><EM>layer1 layer2 </EM>[<EM>layer3</EM> [<EM>layer4</EM>]]
-
-<DD>The names of from two to four existing raster map layers
-to be included in the correlation.
-</DL>
-
-<H2>NOTES</H2>
-
-This is a shell script that uses
-<EM><A HREF="r.stats.html">r.stats</A></EM>
-and the UNIX <EM>awk</EM> command
-to calculate the correlation among data layers,
-and uses
-<EM><A HREF="d.text.html">d.text</A></EM> and
-<EM><A HREF="d.graph.html">d.graph</A></EM> to display the results.
-
-<P>
-
-If three or four map layers are specified, the correlation
-among each combination of two data layers is displayed.
-
-<H2>FILES</H2>
-
-This program is simply a shell script. Users are
-encouraged to make their own shell script programs using
-similar techniques. See <KBD>$GISBASE/scripts/d.correlate</KBD>.
-
-<H2>SEE ALSO</H2>
-
-The UNIX <EM>awk</EM> command.
-
-
-<P>
-
-<EM>
-<A HREF="d.text.html">d.text</A>,
-<A HREF="d.graph.html">d.graph</A>,
-<A HREF="r.coin.html">r.coin</A>,
-<A HREF="r.regression.line.html">r.regression.line</A>,
-<A HREF="r.stats.html">r.stats</A>
-</EM>
-
-<H2>AUTHOR</H2>
-
-Michael Shapiro,
-<A HREF="http://www.cecer.army.mil/">U.S.Army Construction Engineering
-Research Laboratory</A>
-<p>
-Rewritten to GRASS 6 (from csh to sh) by Markus Neteler
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/scripts/d.out.gpsdrive/d.out.gpsdrive.html (from rev 32770, grass/trunk/scripts/d.out.gpsdrive/description.html)
===================================================================
--- grass/trunk/scripts/d.out.gpsdrive/d.out.gpsdrive.html (rev 0)
+++ grass/trunk/scripts/d.out.gpsdrive/d.out.gpsdrive.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,138 @@
+<H2>DESCRIPTION</H2>
+
+<EM>d.out.gpsdrive</EM> exports the current GRASS display monitor to a
+<A HREF="http://www.gpsdrive.de">GpsDrive</a> compatible backdrop
+image and updates the GpsDrive image list with the appropriate geo-referencing
+information.
+
+<P>
+<b><em>Use at your own risk. Do not use as a primary means of navigation.
+This software comes with absolutely no warranty.</em></b>
+
+
+<P>
+<H2>NOTES</H2>
+
+Maps are saved in the user's <tt>~/.gpsdrive</tt> directory. Geo-referencing
+information is added to the user's <tt>~/.gpsdrive/map_koord.txt</tt> file.
+
+<P>
+JPEG output requires the <tt>pngtopnm</tt> and <tt>pnmtojpeg</tt> programs
+from the <a href="http://netpbm.sourceforge.net">NetPBM tools</a>.
+
+<P>
+GpsDrive assumes northings are not rotated compared to true-geographic north.
+If you are using a projection with significant curvature away from the central
+meridian, or a map datum with a significant rotational component, then you will
+likely end up with a distorted or inexact background map!
+Keeping the area small will lessen the error, but not eliminate it.
+<P>
+Best output is created from a Lat/Lon location or by keeping the output area
+small (1:50,000). This translates to approx a 22.7km x 18.2km image window in the
+GIS. [<tt>x_ext=scale*(1280/2817.95)</tt>]
+<P>
+For your convenience (calculations are rough, but nominal):
+<div class="code"><pre>
+1:50,000 uses a region 22.7km x 18.2km.
+1:75,000 uses a region 34.1km x 27.3km.
+1:100,000 uses a region 45.4km x 36.3km.
+1:175,000 uses a region 79.5km x 63.6km.
+</pre></div>
+<BR>
+
+
+Maps exported from lat-lon locations will be given a "<tt>top_</tt>" prefix.
+Maps exported from locations of other projections will be given a
+"<tt>map_</tt>" prefix. This is done so GpsDrive knows how to scale the
+image correctly.
+<P>
+GpsDrive requires backdrop images to be 1280x1024 pixels in size. While this
+script takes care of that automatically, to avoid annoying bands on the sides
+of your image you may want to set up your display monitor at half-scale (same
+aspect ratio) and use d.zoom to select the full frame. For example:
+<P>
+<div class="code"><pre>
+export GRASS_WIDTH=640
+export GRASS_HEIGHT=512
+d.mon x0
+</pre></div>
+
+<BR>
+Map scaling is set from the region settings so should work correctly even
+when the display's aspect ratio does not match that of the output image.
+
+
+<h3>Batch export</h3>
+
+It may be desirable to create a series of image tiles covering a large area.
+An easy way to do this is to run <em>d.out.gpsdrive</em> in a shell loop.
+Here is an example Bash script contributed by Manuel Morales:
+<P>
+<div class="code"><pre>
+#!/bin/bash
+
+# map scale is determined by "panels" by dividing the N-S
+# region extent into that number of maps. Note that the
+# generated maps overlap by 1/2 along the N-S axis and by
+# approximately 1/2 along the E-W axis.
+panels=3
+iter=$((panels*2-1))
+
+eval `g.region -eg`
+eval `g.region -g`
+north=$n
+south=$s
+west=$w
+east=$e
+
+unit_ns=$(echo "scale=8; $ns_extent / $panels" | bc)
+unit_ew=$(echo "scale=8; $unit_ns * 4/3" | bc)
+
+panels_ew=$(echo "((2*$ew_extent / $unit_ew +.5 ) -1) / 1" | bc)
+
+for i in `seq 1 $panels_ew`;
+do
+ east=$(echo "scale=8; $west+$unit_ew" | bc)
+ for j in `seq 1 $iter`;
+ do
+ g.region n=$(echo "scale=8; $north-($j-1) * $unit_ns/2" | bc) \
+ s=$(echo "scale=8; $north-($j-1) * $unit_ns/2-$unit_ns" | bc ) \
+ w=$west e=$east ewres=$ewres nsres=$nsres
+ d.redraw
+ d.out.gpsdrive -j tile_${i}_${j}
+ done
+ shift_west=$(echo "scale=8; ($ew_extent-$unit_ew)/($panels_ew-1)" | bc)
+ west=$(echo "scale=8; $west+$shift_west" | bc)
+done
+</pre></div>
+
+<BR>
+Note that to get a smoother transition between backdrop maps this script
+creates overlapping tiles.
+
+
+<BR><BR>
+<H2>SEE ALSO</H2>
+
+<EM><A HREF="d.info.html">d.info</A></EM>,
+<EM><A HREF="d.grid.html">d.grid</A></EM>,
+<EM><A HREF="d.out.file.html">d.out.file</A></EM>,
+<EM><A HREF="d.out.png.html">d.out.png</A></EM>,
+<EM><A HREF="d.save.html">d.save</A></EM>,
+<EM><A HREF="g.region.html">g.region</A></EM>,
+<EM><A HREF="v.in.garmin.html">v.in.garmin</A></EM>
+<BR><BR>
+The GRASS <A HREF="pngdriver.html">PNG driver</A><BR>
+
+The <A HREF="http://www.gpsdrive.de">GpsDrive</a> project<BR>
+The <A HREF="http://gpsd.berlios.de">gpsd</a> personal GPS server project
+<BR><BR>
+
+<H2>AUTHOR</H2>
+Hamish Bowman<BR> <i>
+Department of Marine Science<BR>
+University of Otago<BR>
+New Zealand</i><BR>
+<BR>
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/scripts/d.out.gpsdrive/description.html
===================================================================
--- grass/trunk/scripts/d.out.gpsdrive/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/scripts/d.out.gpsdrive/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,138 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-<EM>d.out.gpsdrive</EM> exports the current GRASS display monitor to a
-<A HREF="http://www.gpsdrive.de">GpsDrive</a> compatible backdrop
-image and updates the GpsDrive image list with the appropriate geo-referencing
-information.
-
-<P>
-<b><em>Use at your own risk. Do not use as a primary means of navigation.
-This software comes with absolutely no warranty.</em></b>
-
-
-<P>
-<H2>NOTES</H2>
-
-Maps are saved in the user's <tt>~/.gpsdrive</tt> directory. Geo-referencing
-information is added to the user's <tt>~/.gpsdrive/map_koord.txt</tt> file.
-
-<P>
-JPEG output requires the <tt>pngtopnm</tt> and <tt>pnmtojpeg</tt> programs
-from the <a href="http://netpbm.sourceforge.net">NetPBM tools</a>.
-
-<P>
-GpsDrive assumes northings are not rotated compared to true-geographic north.
-If you are using a projection with significant curvature away from the central
-meridian, or a map datum with a significant rotational component, then you will
-likely end up with a distorted or inexact background map!
-Keeping the area small will lessen the error, but not eliminate it.
-<P>
-Best output is created from a Lat/Lon location or by keeping the output area
-small (1:50,000). This translates to approx a 22.7km x 18.2km image window in the
-GIS. [<tt>x_ext=scale*(1280/2817.95)</tt>]
-<P>
-For your convenience (calculations are rough, but nominal):
-<div class="code"><pre>
-1:50,000 uses a region 22.7km x 18.2km.
-1:75,000 uses a region 34.1km x 27.3km.
-1:100,000 uses a region 45.4km x 36.3km.
-1:175,000 uses a region 79.5km x 63.6km.
-</pre></div>
-<BR>
-
-
-Maps exported from lat-lon locations will be given a "<tt>top_</tt>" prefix.
-Maps exported from locations of other projections will be given a
-"<tt>map_</tt>" prefix. This is done so GpsDrive knows how to scale the
-image correctly.
-<P>
-GpsDrive requires backdrop images to be 1280x1024 pixels in size. While this
-script takes care of that automatically, to avoid annoying bands on the sides
-of your image you may want to set up your display monitor at half-scale (same
-aspect ratio) and use d.zoom to select the full frame. For example:
-<P>
-<div class="code"><pre>
-export GRASS_WIDTH=640
-export GRASS_HEIGHT=512
-d.mon x0
-</pre></div>
-
-<BR>
-Map scaling is set from the region settings so should work correctly even
-when the display's aspect ratio does not match that of the output image.
-
-
-<h3>Batch export</h3>
-
-It may be desirable to create a series of image tiles covering a large area.
-An easy way to do this is to run <em>d.out.gpsdrive</em> in a shell loop.
-Here is an example Bash script contributed by Manuel Morales:
-<P>
-<div class="code"><pre>
-#!/bin/bash
-
-# map scale is determined by "panels" by dividing the N-S
-# region extent into that number of maps. Note that the
-# generated maps overlap by 1/2 along the N-S axis and by
-# approximately 1/2 along the E-W axis.
-panels=3
-iter=$((panels*2-1))
-
-eval `g.region -eg`
-eval `g.region -g`
-north=$n
-south=$s
-west=$w
-east=$e
-
-unit_ns=$(echo "scale=8; $ns_extent / $panels" | bc)
-unit_ew=$(echo "scale=8; $unit_ns * 4/3" | bc)
-
-panels_ew=$(echo "((2*$ew_extent / $unit_ew +.5 ) -1) / 1" | bc)
-
-for i in `seq 1 $panels_ew`;
-do
- east=$(echo "scale=8; $west+$unit_ew" | bc)
- for j in `seq 1 $iter`;
- do
- g.region n=$(echo "scale=8; $north-($j-1) * $unit_ns/2" | bc) \
- s=$(echo "scale=8; $north-($j-1) * $unit_ns/2-$unit_ns" | bc ) \
- w=$west e=$east ewres=$ewres nsres=$nsres
- d.redraw
- d.out.gpsdrive -j tile_${i}_${j}
- done
- shift_west=$(echo "scale=8; ($ew_extent-$unit_ew)/($panels_ew-1)" | bc)
- west=$(echo "scale=8; $west+$shift_west" | bc)
-done
-</pre></div>
-
-<BR>
-Note that to get a smoother transition between backdrop maps this script
-creates overlapping tiles.
-
-
-<BR><BR>
-<H2>SEE ALSO</H2>
-
-<EM><A HREF="d.info.html">d.info</A></EM>,
-<EM><A HREF="d.grid.html">d.grid</A></EM>,
-<EM><A HREF="d.out.file.html">d.out.file</A></EM>,
-<EM><A HREF="d.out.png.html">d.out.png</A></EM>,
-<EM><A HREF="d.save.html">d.save</A></EM>,
-<EM><A HREF="g.region.html">g.region</A></EM>,
-<EM><A HREF="v.in.garmin.html">v.in.garmin</A></EM>
-<BR><BR>
-The GRASS <A HREF="pngdriver.html">PNG driver</A><BR>
-
-The <A HREF="http://www.gpsdrive.de">GpsDrive</a> project<BR>
-The <A HREF="http://gpsd.berlios.de">gpsd</a> personal GPS server project
-<BR><BR>
-
-<H2>AUTHOR</H2>
-Hamish Bowman<BR> <i>
-Department of Marine Science<BR>
-University of Otago<BR>
-New Zealand</i><BR>
-<BR>
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/scripts/d.polar/d.polar.html (from rev 32770, grass/trunk/scripts/d.polar/description.html)
===================================================================
--- grass/trunk/scripts/d.polar/d.polar.html (rev 0)
+++ grass/trunk/scripts/d.polar/d.polar.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,72 @@
+<H2>DESCRIPTION</H2>
+
+<EM>d.polar</EM> calculates and displays a polar diagram of an
+angle raster map such as aspect, wind direction, or flow.
+The input angle map orientation must be counter-clockwise (CCW)
+from east, and the angle map units must be degrees. This refers
+to the standard orientation of GRASS (e.g., see <em>r.slope.aspect</em>).
+<P>
+The radius of the outer circle is defined by the total number
+of pixels in the map. If the polar diagram does not reach the
+outer circle, no data (NULL) pixels were found in the map.
+<P>
+The vector in the diagram indicates a prevailing direction, its length
+the strength of such direction. In case all angle vectors are oriented
+along the same direction, the length for the vector is maximal (in fact
+it is equal to length of the most populated bin of the underlying histogram).
+<P>
+As a side effect, the quality of the angle map can be derived from
+the diagram. Strong spikes may indicate an over-representation of
+the related angle(s) which happens in particular if integer maps
+are used.
+
+<H2>NOTES</H2>
+
+If the <b>eps</b> parameter is used, the diagram is generated
+as EPS file. If the <b>-x</b> flag is used <EM>xgraph</EM> is lauched.
+Otherwise <em>d.polar</em> will use <em>d.graph</em> to draw the plot
+in the current display frame.
+<P>
+If <EM>d.polar</EM> is used on an aspect map generated by
+<EM>r.slope.aspect</EM>, the <b>undef</b> parameter should be
+set to 0 to distinguish NO DATA (NULL) areas from areas where
+aspect is undefined (i.e. flat areas).
+<P>
+
+<center>
+<img src="d_polar_aspect.png" alt="Polar diagram of aspect map">
+<BR>
+<i>Polar diagram of aspect map</i>
+</center>
+
+<h2>EXAMPLE</h2>
+
+In this example, the polar diagram of the 'aspect' angle map in the
+Spearfish location is generated:
+
+<div class="code"><pre>
+d.polar aspect
+</pre></div>
+
+
+<H2>SEE ALSO</H2>
+
+<EM><A HREF="d.graph.html">d.graph</A></EM>,
+<EM><A HREF="d.histogram.html">d.histogram</A></EM>,
+<EM><A HREF="d.rast.arrow.html">d.rast.arrow</A></EM>,
+<EM><A HREF="r.slope.aspect.html">r.slope.aspect</A></EM>
+
+
+<H2>XGRAPH REQUIREMENT</H2>
+
+<A HREF="http://www.xgraph.org">Xgraph</a> must be installed for the
+<b>-x</b> flag to function.
+
+
+<H2>AUTHORS</H2>
+
+Markus Neteler, ITC-irst, Italy<BR>
+Bruno Caprile, ITC-irst, Italy<BR>
+Hamish Bowman, Otago University, New Zealand<BR>
+
+<p><i>Last changed: $Date$</i></p>
Deleted: grass/trunk/scripts/d.polar/description.html
===================================================================
--- grass/trunk/scripts/d.polar/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/scripts/d.polar/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,72 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-<EM>d.polar</EM> calculates and displays a polar diagram of an
-angle raster map such as aspect, wind direction, or flow.
-The input angle map orientation must be counter-clockwise (CCW)
-from east, and the angle map units must be degrees. This refers
-to the standard orientation of GRASS (e.g., see <em>r.slope.aspect</em>).
-<P>
-The radius of the outer circle is defined by the total number
-of pixels in the map. If the polar diagram does not reach the
-outer circle, no data (NULL) pixels were found in the map.
-<P>
-The vector in the diagram indicates a prevailing direction, its length
-the strength of such direction. In case all angle vectors are oriented
-along the same direction, the length for the vector is maximal (in fact
-it is equal to length of the most populated bin of the underlying histogram).
-<P>
-As a side effect, the quality of the angle map can be derived from
-the diagram. Strong spikes may indicate an over-representation of
-the related angle(s) which happens in particular if integer maps
-are used.
-
-<H2>NOTES</H2>
-
-If the <b>eps</b> parameter is used, the diagram is generated
-as EPS file. If the <b>-x</b> flag is used <EM>xgraph</EM> is lauched.
-Otherwise <em>d.polar</em> will use <em>d.graph</em> to draw the plot
-in the current display frame.
-<P>
-If <EM>d.polar</EM> is used on an aspect map generated by
-<EM>r.slope.aspect</EM>, the <b>undef</b> parameter should be
-set to 0 to distinguish NO DATA (NULL) areas from areas where
-aspect is undefined (i.e. flat areas).
-<P>
-
-<center>
-<img src="d_polar_aspect.png" alt="Polar diagram of aspect map">
-<BR>
-<i>Polar diagram of aspect map</i>
-</center>
-
-<h2>EXAMPLE</h2>
-
-In this example, the polar diagram of the 'aspect' angle map in the
-Spearfish location is generated:
-
-<div class="code"><pre>
-d.polar aspect
-</pre></div>
-
-
-<H2>SEE ALSO</H2>
-
-<EM><A HREF="d.graph.html">d.graph</A></EM>,
-<EM><A HREF="d.histogram.html">d.histogram</A></EM>,
-<EM><A HREF="d.rast.arrow.html">d.rast.arrow</A></EM>,
-<EM><A HREF="r.slope.aspect.html">r.slope.aspect</A></EM>
-
-
-<H2>XGRAPH REQUIREMENT</H2>
-
-<A HREF="http://www.xgraph.org">Xgraph</a> must be installed for the
-<b>-x</b> flag to function.
-
-
-<H2>AUTHORS</H2>
-
-Markus Neteler, ITC-irst, Italy<BR>
-Bruno Caprile, ITC-irst, Italy<BR>
-Hamish Bowman, Otago University, New Zealand<BR>
-
-<p><i>Last changed: $Date$</i></p>
Copied: grass/trunk/scripts/d.rast.edit/d.rast.edit.html (from rev 32770, grass/trunk/scripts/d.rast.edit/description.html)
===================================================================
--- grass/trunk/scripts/d.rast.edit/d.rast.edit.html (rev 0)
+++ grass/trunk/scripts/d.rast.edit/d.rast.edit.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,16 @@
+<H2>DESCRIPTION</H2>
+
+The <EM>d.rast.edit</EM> program allows users to interactively
+edit cell category values in a raster map layer displayed to the
+graphics monitor using a mouse cursor.
+
+<H2>SEE ALSO</H2>
+
+<em><a href="d.rast.arrow.html">d.rast.arrow</a></em>,
+<em><a href="d.rast.num.html">d.rast.num</a></em>
+
+<H2>AUTHOR</H2>
+
+Glynn Clements
+<p>
+<i>Last changed: $Date$</i>
Deleted: grass/trunk/scripts/d.rast.edit/description.html
===================================================================
--- grass/trunk/scripts/d.rast.edit/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/scripts/d.rast.edit/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,16 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-The <EM>d.rast.edit</EM> program allows users to interactively
-edit cell category values in a raster map layer displayed to the
-graphics monitor using a mouse cursor.
-
-<H2>SEE ALSO</H2>
-
-<em><a href="d.rast.arrow.html">d.rast.arrow</a></em>,
-<em><a href="d.rast.num.html">d.rast.num</a></em>
-
-<H2>AUTHOR</H2>
-
-Glynn Clements
-<p>
-<i>Last changed: $Date$</i>
Copied: grass/trunk/scripts/d.rast.leg/d.rast.leg.html (from rev 32770, grass/trunk/scripts/d.rast.leg/description.html)
===================================================================
--- grass/trunk/scripts/d.rast.leg/d.rast.leg.html (rev 0)
+++ grass/trunk/scripts/d.rast.leg/d.rast.leg.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,35 @@
+<H2>DESCRIPTION</H2>
+
+<EM>d.rast.leg</EM>
+is a GRASS script which clears the entire screen, divides it
+into a main (left) and a minor (right) frames, and then displays a raster
+map in the main frame and the map legend in the minor frame. The main
+frame remains active when the program finishs.
+
+
+<H2>NOTES</H2>
+
+
+If the <B>num_of_lines</B> parameter is not given then the legend frame will
+display as many lines as number of categories in the map, otherwise, it
+will display the first <B>num_of_lines</B> minus 1 categories with the
+rest being truncated.
+<P>
+The user may adjust the <B>num_of_lines</B> parameter or
+the size of graphics window to get an appropriate result.
+<P>
+To remove all frames when clearing the display, use
+"<em><tt>d.erase -f</tt></em>".
+
+<H2>SEE ALSO</H2>
+
+<EM><A HREF="d.legend.html">d.legend</A></EM><BR>
+<EM><A HREF="d.erase.html">d.erase</A></EM><BR>
+<EM><A HREF="d.rast.html">d.rast</A></EM>
+
+<H2>AUTHORS</H2>
+
+Jianping Xu, Scott Madry, Rutgers University<BR>
+Markus Neteler
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/scripts/d.rast.leg/description.html
===================================================================
--- grass/trunk/scripts/d.rast.leg/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/scripts/d.rast.leg/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,35 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-<EM>d.rast.leg</EM>
-is a GRASS script which clears the entire screen, divides it
-into a main (left) and a minor (right) frames, and then displays a raster
-map in the main frame and the map legend in the minor frame. The main
-frame remains active when the program finishs.
-
-
-<H2>NOTES</H2>
-
-
-If the <B>num_of_lines</B> parameter is not given then the legend frame will
-display as many lines as number of categories in the map, otherwise, it
-will display the first <B>num_of_lines</B> minus 1 categories with the
-rest being truncated.
-<P>
-The user may adjust the <B>num_of_lines</B> parameter or
-the size of graphics window to get an appropriate result.
-<P>
-To remove all frames when clearing the display, use
-"<em><tt>d.erase -f</tt></em>".
-
-<H2>SEE ALSO</H2>
-
-<EM><A HREF="d.legend.html">d.legend</A></EM><BR>
-<EM><A HREF="d.erase.html">d.erase</A></EM><BR>
-<EM><A HREF="d.rast.html">d.rast</A></EM>
-
-<H2>AUTHORS</H2>
-
-Jianping Xu, Scott Madry, Rutgers University<BR>
-Markus Neteler
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/scripts/d.shadedmap/d.shadedmap.html (from rev 32770, grass/trunk/scripts/d.shadedmap/description.html)
===================================================================
--- grass/trunk/scripts/d.shadedmap/d.shadedmap.html (rev 0)
+++ grass/trunk/scripts/d.shadedmap/d.shadedmap.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,29 @@
+<H2>DESCRIPTION</H2>
+
+<EM>d.shadedmap</EM> will drape a color raster map over a shaded relief map.
+
+
+<H2>NOTES</H2>
+
+Refer to the <em>d.his</em> help page for more details; <EM>d.shadedmap</EM>
+is simply a frontend to that module.
+<P>
+<EM>(GRASS Shell Script)</EM>
+
+
+<H2>SEE ALSO</H2>
+
+<em>
+<A HREF="d.his.html">d.his</A>,
+<A HREF="g.pnmcomp.html">g.pnmcomp</A>,
+<A HREF="nviz.html">NVIZ</A>,
+<A HREF="r.slope.aspect.html">r.slope.aspect</A>,
+<A HREF="r.shaded.relief.html">r.shaded.relief</A>
+</em>
+
+<H2>AUTHORS</H2>
+
+Unknown; updated to GRASS 5.7 by Michael Barton
+
+<P>
+<i>Last changed: $Date$</i>
Deleted: grass/trunk/scripts/d.shadedmap/description.html
===================================================================
--- grass/trunk/scripts/d.shadedmap/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/scripts/d.shadedmap/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,29 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-<EM>d.shadedmap</EM> will drape a color raster map over a shaded relief map.
-
-
-<H2>NOTES</H2>
-
-Refer to the <em>d.his</em> help page for more details; <EM>d.shadedmap</EM>
-is simply a frontend to that module.
-<P>
-<EM>(GRASS Shell Script)</EM>
-
-
-<H2>SEE ALSO</H2>
-
-<em>
-<A HREF="d.his.html">d.his</A>,
-<A HREF="g.pnmcomp.html">g.pnmcomp</A>,
-<A HREF="nviz.html">NVIZ</A>,
-<A HREF="r.slope.aspect.html">r.slope.aspect</A>,
-<A HREF="r.shaded.relief.html">r.shaded.relief</A>
-</em>
-
-<H2>AUTHORS</H2>
-
-Unknown; updated to GRASS 5.7 by Michael Barton
-
-<P>
-<i>Last changed: $Date$</i>
Copied: grass/trunk/scripts/d.vect.thematic/d.vect.thematic.html (from rev 32770, grass/trunk/scripts/d.vect.thematic/description.html)
===================================================================
--- grass/trunk/scripts/d.vect.thematic/d.vect.thematic.html (rev 0)
+++ grass/trunk/scripts/d.vect.thematic/d.vect.thematic.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,88 @@
+<h2>DESCRIPTION</h2>
+
+<p><em><b>d.vect.thematic</b></em> - Creates thematic maps from vectors of
+ all types and numeric attributes (stored in the data table connected to a vector
+ map). Thematic maps can be displayed by either a graduated color scheme (for
+ all vector types), as graduated icon sizes (for point and centroid types), or
+graduated line widths (for lines and boundaries with associated
+attributes).
+ The user selects the vector map to be mapped and attribute column from which
+ to derive mapping intervals, and (optionally) the layer for attribute data. </p>
+
+<p>In thematic maps, the color or point size changes for each range of attribute
+ values. Value ranges for thematic mapping can be
+ set at regular intervals, standard deviation units on either
+ side of the mean, quartiles, or delimited by user-defined breakpoints. User-defined
+ breakpoints also can be entered, or piped into d.vect.thematic from standard input or
+ other external source. </p>
+
+<p>There are options to define the color scheme (graduated
+ colors) and range of point sizes (graduated points) for thematic maps. A
+ simple text legend is printed. Optionally, a graphic legend can be drawn in
+ the selected display monitor. Thematic colors can be uploaded to a GRASSRGB
+ column for later display, and thematic map display commands can
+ be saved to a group file (*.dm) that can be opened, edited, and displayed in
+the GIS Manager.</p>
+
+<p>When the psmap option is set to 'name', two psmap instruction files are created (in the current directory if no path is given), one for the map ('name.psmap') and one for the legend ('name_legend.psmap'). The map file also contains 'label' commands which allow to create a legend directly in the map by adding a 'vlegend' command. See the <em><a href="ps.map">ps.map</a></em> man page for more details.</p>
+
+<p><em>(GRASS Shell Script)</em></p>
+
+<h2>ATTENTION</h2>
+
+
+The algorithm currently uses the script <em><a href="v.univar.sh.html">v.univar.sh</a></em>
+to calculate basic descriptive statistics needed for thematic mapping (minimum,
+maximum, mean, standard deviation, and quartiles).
+
+<h2>EXAMPLES</h2>
+
+Earthquake points with color gradient:
+
+<div class="code"><pre>
+d.vect.thematic -l recent_earthquakes column=magnitude type=point
+</pre></div>
+
+<p>
+Earthquake points with different sizes:
+
+<div class="code"><pre>
+d.vect.thematic -l recent_earthquakes column=magnitude type=point \
+ themetype=graduated_points maxsize=15
+</pre></div>
+
+<p>
+Spearfish: differences between 'elevation.10m' and 'elevation.dem':
+
+<div class="code"><pre>
+# random sampling of elevation points:
+g.region rast=elevation.10m -p
+v.random random n=200
+v.db.addtable random col="el10 double precision"
+# transfer elevations to attribute table of random points map:
+v.what.rast random rast=elevation.10m col=elev
+v.db.select random
+
+# comparative sampling of second map, incl. differences:
+v.sample in=random col=el10 rast=elevation.dem out=elev_sample
+v.db.select elev_sample
+
+# thematic map:
+d.mon x0
+d.vect.thematic -l elev_sample column=diff type=point
+</pre></div>
+
+
+<h2>SEE ALSO</h2>
+
+<em>
+<a href="d.vect.html">d.vect</a>,
+<a href="d.vect.chart.html">d.vect.chart</a>,
+<a href="v.univar.sh.html">v.univar.sh</a></em>
+
+<h2>AUTHORS</h2>
+
+ Michael Barton, Arizona State University, Daniel Cavelo Aros,
+ Martin Landa, and Jachym Cepicky.
+
+<p><i>Last changed: $Date$</i></p>
Deleted: grass/trunk/scripts/d.vect.thematic/description.html
===================================================================
--- grass/trunk/scripts/d.vect.thematic/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/scripts/d.vect.thematic/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,88 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<p><em><b>d.vect.thematic</b></em> - Creates thematic maps from vectors of
- all types and numeric attributes (stored in the data table connected to a vector
- map). Thematic maps can be displayed by either a graduated color scheme (for
- all vector types), as graduated icon sizes (for point and centroid types), or
-graduated line widths (for lines and boundaries with associated
-attributes).
- The user selects the vector map to be mapped and attribute column from which
- to derive mapping intervals, and (optionally) the layer for attribute data. </p>
-
-<p>In thematic maps, the color or point size changes for each range of attribute
- values. Value ranges for thematic mapping can be
- set at regular intervals, standard deviation units on either
- side of the mean, quartiles, or delimited by user-defined breakpoints. User-defined
- breakpoints also can be entered, or piped into d.vect.thematic from standard input or
- other external source. </p>
-
-<p>There are options to define the color scheme (graduated
- colors) and range of point sizes (graduated points) for thematic maps. A
- simple text legend is printed. Optionally, a graphic legend can be drawn in
- the selected display monitor. Thematic colors can be uploaded to a GRASSRGB
- column for later display, and thematic map display commands can
- be saved to a group file (*.dm) that can be opened, edited, and displayed in
-the GIS Manager.</p>
-
-<p>When the psmap option is set to 'name', two psmap instruction files are created (in the current directory if no path is given), one for the map ('name.psmap') and one for the legend ('name_legend.psmap'). The map file also contains 'label' commands which allow to create a legend directly in the map by adding a 'vlegend' command. See the <em><a href="ps.map">ps.map</a></em> man page for more details.</p>
-
-<p><em>(GRASS Shell Script)</em></p>
-
-<h2>ATTENTION</h2>
-
-
-The algorithm currently uses the script <em><a href="v.univar.sh.html">v.univar.sh</a></em>
-to calculate basic descriptive statistics needed for thematic mapping (minimum,
-maximum, mean, standard deviation, and quartiles).
-
-<h2>EXAMPLES</h2>
-
-Earthquake points with color gradient:
-
-<div class="code"><pre>
-d.vect.thematic -l recent_earthquakes column=magnitude type=point
-</pre></div>
-
-<p>
-Earthquake points with different sizes:
-
-<div class="code"><pre>
-d.vect.thematic -l recent_earthquakes column=magnitude type=point \
- themetype=graduated_points maxsize=15
-</pre></div>
-
-<p>
-Spearfish: differences between 'elevation.10m' and 'elevation.dem':
-
-<div class="code"><pre>
-# random sampling of elevation points:
-g.region rast=elevation.10m -p
-v.random random n=200
-v.db.addtable random col="el10 double precision"
-# transfer elevations to attribute table of random points map:
-v.what.rast random rast=elevation.10m col=elev
-v.db.select random
-
-# comparative sampling of second map, incl. differences:
-v.sample in=random col=el10 rast=elevation.dem out=elev_sample
-v.db.select elev_sample
-
-# thematic map:
-d.mon x0
-d.vect.thematic -l elev_sample column=diff type=point
-</pre></div>
-
-
-<h2>SEE ALSO</h2>
-
-<em>
-<a href="d.vect.html">d.vect</a>,
-<a href="d.vect.chart.html">d.vect.chart</a>,
-<a href="v.univar.sh.html">v.univar.sh</a></em>
-
-<h2>AUTHORS</h2>
-
- Michael Barton, Arizona State University, Daniel Cavelo Aros,
- Martin Landa, and Jachym Cepicky.
-
-<p><i>Last changed: $Date$</i></p>
Copied: grass/trunk/scripts/db.dropcol/db.dropcol.html (from rev 32770, grass/trunk/scripts/db.dropcol/description.html)
===================================================================
--- grass/trunk/scripts/db.dropcol/db.dropcol.html (rev 0)
+++ grass/trunk/scripts/db.dropcol/db.dropcol.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,42 @@
+<h2>DESCRIPTION</h2>
+
+<em>db.dropcol</em> drops a column from an attribute table.
+If the <b>-f</b> force flag is not given then nothing is removed, instead
+a preview of the action to be taken is printed.
+
+<h2>NOTES</h2>
+
+<em>db.dropcol</em> is a front-end to <em>db.execute</em> to allow easier
+usage with a special workaround for the SQLite driver to support column
+drop.
+
+<h2>EXAMPLES</h2>
+
+Dropping a column (Spearfish):
+<p>
+<div class="code"><pre>
+# work on own copy
+g.copy vect=roads,myroads
+db.describe -c myroads
+
+# only shows what would happen:
+db.dropcol myroads column=label
+
+# actually drops the column
+db.dropcol -f myroads column=label
+
+db.describe -c myroads
+</pre></div>
+
+<h2>SEE ALSO</h2>
+
+<em><a HREF="db.droptable.html">db.droptable</a></em>,
+<em><a HREF="db.execute.html">db.execute</a></em>,
+<em><a HREF="v.db.dropcol.html">v.db.dropcol</a></em>
+
+
+<h2>AUTHOR</h2>
+
+Markus Neteler
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/scripts/db.dropcol/description.html
===================================================================
--- grass/trunk/scripts/db.dropcol/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/scripts/db.dropcol/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,42 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>db.dropcol</em> drops a column from an attribute table.
-If the <b>-f</b> force flag is not given then nothing is removed, instead
-a preview of the action to be taken is printed.
-
-<h2>NOTES</h2>
-
-<em>db.dropcol</em> is a front-end to <em>db.execute</em> to allow easier
-usage with a special workaround for the SQLite driver to support column
-drop.
-
-<h2>EXAMPLES</h2>
-
-Dropping a column (Spearfish):
-<p>
-<div class="code"><pre>
-# work on own copy
-g.copy vect=roads,myroads
-db.describe -c myroads
-
-# only shows what would happen:
-db.dropcol myroads column=label
-
-# actually drops the column
-db.dropcol -f myroads column=label
-
-db.describe -c myroads
-</pre></div>
-
-<h2>SEE ALSO</h2>
-
-<em><a HREF="db.droptable.html">db.droptable</a></em>,
-<em><a HREF="db.execute.html">db.execute</a></em>,
-<em><a HREF="v.db.dropcol.html">v.db.dropcol</a></em>
-
-
-<h2>AUTHOR</h2>
-
-Markus Neteler
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/scripts/db.droptable/db.droptable.html (from rev 32770, grass/trunk/scripts/db.droptable/description.html)
===================================================================
--- grass/trunk/scripts/db.droptable/db.droptable.html (rev 0)
+++ grass/trunk/scripts/db.droptable/db.droptable.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,38 @@
+<h2>DESCRIPTION</h2>
+
+<em>db.droptable</em> drops an attribute table.
+If the <b>-f</b> force flag is not given then nothing is removed, instead
+a preview of the action to be taken is printed.
+
+<h2>NOTES</h2>
+
+<em>db.droptable</em> is a front-end to <em>db.execute</em> to allow easier
+usage. To some extent it is verified if the table is connected to a vector map.
+
+<h2>EXAMPLES</h2>
+
+Dropping a table (Spearfish):
+<p>
+<div class="code"><pre>
+# work on own copy
+g.copy vect=roads,myroads
+
+# only shows what would happen
+db.droptable myroads
+
+# actually drop the table
+db.droptable -f myroads
+
+db.tables -p
+</pre></div>
+
+<h2>SEE ALSO</h2>
+
+<em><a HREF="db.execute.html">db.execute</a></em>,
+<em><a HREF="v.db.droptable.html">v.db.droptable</a></em>
+
+<h2>AUTHOR</h2>
+
+Markus Neteler
+
+<p><i>Last changed: $Date: 2007-07-14 12:59:51 +0200 (Sat, 14 Jul 2007) $</i>
Deleted: grass/trunk/scripts/db.droptable/description.html
===================================================================
--- grass/trunk/scripts/db.droptable/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/scripts/db.droptable/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,38 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>db.droptable</em> drops an attribute table.
-If the <b>-f</b> force flag is not given then nothing is removed, instead
-a preview of the action to be taken is printed.
-
-<h2>NOTES</h2>
-
-<em>db.droptable</em> is a front-end to <em>db.execute</em> to allow easier
-usage. To some extent it is verified if the table is connected to a vector map.
-
-<h2>EXAMPLES</h2>
-
-Dropping a table (Spearfish):
-<p>
-<div class="code"><pre>
-# work on own copy
-g.copy vect=roads,myroads
-
-# only shows what would happen
-db.droptable myroads
-
-# actually drop the table
-db.droptable -f myroads
-
-db.tables -p
-</pre></div>
-
-<h2>SEE ALSO</h2>
-
-<em><a HREF="db.execute.html">db.execute</a></em>,
-<em><a HREF="v.db.droptable.html">v.db.droptable</a></em>
-
-<h2>AUTHOR</h2>
-
-Markus Neteler
-
-<p><i>Last changed: $Date: 2007-07-14 12:59:51 +0200 (Sat, 14 Jul 2007) $</i>
Copied: grass/trunk/scripts/db.in.ogr/db.in.ogr.html (from rev 32770, grass/trunk/scripts/db.in.ogr/description.html)
===================================================================
--- grass/trunk/scripts/db.in.ogr/db.in.ogr.html (rev 0)
+++ grass/trunk/scripts/db.in.ogr/db.in.ogr.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,59 @@
+<h2>DESCRIPTION</h2>
+
+<em>db.in.ogr</em> imports attribute tables in various formats as
+supported by the OGR driver on the local system (DBF, CSV,
+PostgreSQL, SQLite, MySQL, ODBC, etc.). Optionally a unique key (ID)
+column can be added to the table.
+
+<h2>NOTES</h2>
+
+
+<h2>EXAMPLES</h2>
+
+Import of a CSV table file:<br>
+Limited type recognition can be done for Integer, Real, String, Date, Time and DateTime
+columns through a descriptive file with same name as the CSV file, but .csvt extension
+(see details <a href="http://www.gdal.org/ogr/drv_csv.html">here</a>).
+<p>
+<div class="code"><pre>
+# NOTE: create koeppen_gridcode.csvt first for type recognition
+db.in.ogr dsn=koeppen_gridcode.csv output=koeppen_gridcode
+db.select koeppen_gridcode
+</pre></div>
+
+<p>
+Import of a DBF table with additional unique key column (e.g., needed for <em>v.in.db</em>):
+<p>
+<div class="code"><pre>
+db.in.ogr dsn=$HOME/mydata.dbf output=census_raleigh key=myid
+db.describe -c census_raleigh
+</pre></div>
+
+<p>
+Import of a SQLite table:
+<p>
+<div class="code"><pre>
+db.in.ogr dsn=$HOME/sqlite/sqlite.db db_table=census_raleigh output=census_raleigh
+</pre></div>
+
+<p>
+Import of a PostgreSQL table:
+<p>
+<div class="code"><pre>
+db.in.ogr dsn="PG:host=localhost dbname=ecad user=neteler" \
+ db_table=ecad_verona_tmean output=ecad_verona_tmean
+db.select ecad_verona_tmean
+db.describe -c ecad_verona_tmean
+</pre></div>
+
+
+<h2>SEE ALSO</h2>
+
+<em><a HREF="v.in.ogr.html">v.in.ogr</a></em><br>
+<em><a href="sql.html">GRASS SQL interface</a></em>
+
+<h2>AUTHOR</h2>
+
+Markus Neteler
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/scripts/db.in.ogr/description.html
===================================================================
--- grass/trunk/scripts/db.in.ogr/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/scripts/db.in.ogr/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,59 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>db.in.ogr</em> imports attribute tables in various formats as
-supported by the OGR driver on the local system (DBF, CSV,
-PostgreSQL, SQLite, MySQL, ODBC, etc.). Optionally a unique key (ID)
-column can be added to the table.
-
-<h2>NOTES</h2>
-
-
-<h2>EXAMPLES</h2>
-
-Import of a CSV table file:<br>
-Limited type recognition can be done for Integer, Real, String, Date, Time and DateTime
-columns through a descriptive file with same name as the CSV file, but .csvt extension
-(see details <a href="http://www.gdal.org/ogr/drv_csv.html">here</a>).
-<p>
-<div class="code"><pre>
-# NOTE: create koeppen_gridcode.csvt first for type recognition
-db.in.ogr dsn=koeppen_gridcode.csv output=koeppen_gridcode
-db.select koeppen_gridcode
-</pre></div>
-
-<p>
-Import of a DBF table with additional unique key column (e.g., needed for <em>v.in.db</em>):
-<p>
-<div class="code"><pre>
-db.in.ogr dsn=$HOME/mydata.dbf output=census_raleigh key=myid
-db.describe -c census_raleigh
-</pre></div>
-
-<p>
-Import of a SQLite table:
-<p>
-<div class="code"><pre>
-db.in.ogr dsn=$HOME/sqlite/sqlite.db db_table=census_raleigh output=census_raleigh
-</pre></div>
-
-<p>
-Import of a PostgreSQL table:
-<p>
-<div class="code"><pre>
-db.in.ogr dsn="PG:host=localhost dbname=ecad user=neteler" \
- db_table=ecad_verona_tmean output=ecad_verona_tmean
-db.select ecad_verona_tmean
-db.describe -c ecad_verona_tmean
-</pre></div>
-
-
-<h2>SEE ALSO</h2>
-
-<em><a HREF="v.in.ogr.html">v.in.ogr</a></em><br>
-<em><a href="sql.html">GRASS SQL interface</a></em>
-
-<h2>AUTHOR</h2>
-
-Markus Neteler
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/scripts/db.out.ogr/db.out.ogr.html (from rev 32770, grass/trunk/scripts/db.out.ogr/description.html)
===================================================================
--- grass/trunk/scripts/db.out.ogr/db.out.ogr.html (rev 0)
+++ grass/trunk/scripts/db.out.ogr/db.out.ogr.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,39 @@
+<h2>DESCRIPTION</h2>
+
+<em>db.out.ogr</em> exports GRASS attribute tables into various formats as
+supported by the OGR driver on the local system (CSV, DBF,
+PostgreSQL, SQLite, MySQL, ODBC, etc.).
+
+<h2>EXAMPLES</h2>
+
+Export of GRASS table to a DBF table (default format):
+<p>
+<div class="code"><pre>
+db.out.ogr points_tab dsn=/tmp/points_tab.dbf
+</pre></div>
+
+<p>
+Export of GRASS table to a CSV table file:<br>
+<p>
+<div class="code"><pre>
+db.out.ogr points_tab dsn=points.csv format=CSV
+</pre></div>
+
+<p>
+Export of GRASS table into a PostgreSQL table:
+<p>
+<div class="code"><pre>
+db.out.ogr points_tab dsn="PG:host=localhost dbname=postgres user=neteler" format=PostgreSQL
+echo "SELECT * FROM points_tab" | psql postgres
+</pre></div>
+
+
+<h2>SEE ALSO</h2>
+
+<em><a href="sql.html">GRASS SQL interface</a></em>
+
+<h2>AUTHOR</h2>
+
+Markus Neteler
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/scripts/db.out.ogr/description.html
===================================================================
--- grass/trunk/scripts/db.out.ogr/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/scripts/db.out.ogr/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,39 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>db.out.ogr</em> exports GRASS attribute tables into various formats as
-supported by the OGR driver on the local system (CSV, DBF,
-PostgreSQL, SQLite, MySQL, ODBC, etc.).
-
-<h2>EXAMPLES</h2>
-
-Export of GRASS table to a DBF table (default format):
-<p>
-<div class="code"><pre>
-db.out.ogr points_tab dsn=/tmp/points_tab.dbf
-</pre></div>
-
-<p>
-Export of GRASS table to a CSV table file:<br>
-<p>
-<div class="code"><pre>
-db.out.ogr points_tab dsn=points.csv format=CSV
-</pre></div>
-
-<p>
-Export of GRASS table into a PostgreSQL table:
-<p>
-<div class="code"><pre>
-db.out.ogr points_tab dsn="PG:host=localhost dbname=postgres user=neteler" format=PostgreSQL
-echo "SELECT * FROM points_tab" | psql postgres
-</pre></div>
-
-
-<h2>SEE ALSO</h2>
-
-<em><a href="sql.html">GRASS SQL interface</a></em>
-
-<h2>AUTHOR</h2>
-
-Markus Neteler
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/scripts/db.test/db.test.html (from rev 32770, grass/trunk/scripts/db.test/description.html)
===================================================================
--- grass/trunk/scripts/db.test/db.test.html (rev 0)
+++ grass/trunk/scripts/db.test/db.test.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,17 @@
+<H2>DESCRIPTION</H2>
+
+<EM>db.test</EM> tests database driver and database server running
+set of SQL queries. Database must exist and connection must be set
+by db.connect.
+
+<h2>SEE ALSO</h2>
+
+<em><a HREF="sql.html">GRASS SQL interface</a>,
+<a HREF="db.connect.html">db.connect</a>,
+<a HREF="db.describe.html">db.describe</a>,
+<a HREF="db.drivers.html">db.drivers</a>
+</em>
+
+<H2>AUTHOR</H2>
+Radim Blazek
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/scripts/db.test/description.html
===================================================================
--- grass/trunk/scripts/db.test/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/scripts/db.test/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,17 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-<EM>db.test</EM> tests database driver and database server running
-set of SQL queries. Database must exist and connection must be set
-by db.connect.
-
-<h2>SEE ALSO</h2>
-
-<em><a HREF="sql.html">GRASS SQL interface</a>,
-<a HREF="db.connect.html">db.connect</a>,
-<a HREF="db.describe.html">db.describe</a>,
-<a HREF="db.drivers.html">db.drivers</a>
-</em>
-
-<H2>AUTHOR</H2>
-Radim Blazek
-<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/scripts/g.manual/description.html
===================================================================
--- grass/trunk/scripts/g.manual/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/scripts/g.manual/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,30 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>g.manual</em> display the manual pages of GRASS in HTML and MAN
-format.
-
-<h2>NOTES</h2>
-
-The name of the HTML browser is defined in the environment variable
-<tt>GRASS_HTML_BROWSER</TT>. For most platforms this should be an
-executable in your PATH, or the full path to an executable. See
-<a href="variables.html">variables</a> for details.
-
-<h2>EXAMPLES</h2>
-
-<div class="code"><pre>
-# how index
-g.manual index
-
-# show module manual page in HTML browser
-g.manual d.vect
-
-# show module manual page in terminal
-g.manual -m d.vect
-</pre></div>
-
-<h2>AUTHOR</h2>
-
-Markus Neteler
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/scripts/g.manual/g.manual.html (from rev 32770, grass/trunk/scripts/g.manual/description.html)
===================================================================
--- grass/trunk/scripts/g.manual/g.manual.html (rev 0)
+++ grass/trunk/scripts/g.manual/g.manual.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,30 @@
+<h2>DESCRIPTION</h2>
+
+<em>g.manual</em> display the manual pages of GRASS in HTML and MAN
+format.
+
+<h2>NOTES</h2>
+
+The name of the HTML browser is defined in the environment variable
+<tt>GRASS_HTML_BROWSER</TT>. For most platforms this should be an
+executable in your PATH, or the full path to an executable. See
+<a href="variables.html">variables</a> for details.
+
+<h2>EXAMPLES</h2>
+
+<div class="code"><pre>
+# how index
+g.manual index
+
+# show module manual page in HTML browser
+g.manual d.vect
+
+# show module manual page in terminal
+g.manual -m d.vect
+</pre></div>
+
+<h2>AUTHOR</h2>
+
+Markus Neteler
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/scripts/g.mlist/description.html
===================================================================
--- grass/trunk/scripts/g.mlist/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/scripts/g.mlist/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,60 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-<EM>g.mlist</EM> is an extended version of
-<EM><A HREF="g.list.html">g.list</A></EM> which
-provides support for POSIX Basic Regular Expressions and wildcards.
-<EM>g.mlist</EM> will only print map names and an optional separator,
-without extraneous output. In addition, map search is also available.
-
-<H2>EXAMPLES</H2>
-
-List all available GRASS data base files:
-<BR>
-<TT>g.mlist type=all</TT>
-<P>
-
-List all raster and vector maps:
-<BR>
-<TT>g.mlist type=rast,vect</TT>
-<P>
-
-<H3>Wildcards:</H3>
-
-List all vector maps starting with letter "r":
-<BR>
-<TT>g.mlist type=vect pattern="r*"</TT>
-<P>
-
-List certain raster maps with one variable character/number:
-<BR>
-<TT>g.mlist type=rast pattern="N45E00?.meters"</TT>
-
-<H3>Regular expressions:</H3>
-
-Print out all soils map with "soils" in their name:<BR>
-<TT>g.mlist -r type=rast pattern='^soils'</TT>
-<P>
-
-Print out "tmp" if "tmp" raster map exists:<BR>
-<TT>g.mlist -r pattern='^tmp$'</TT>
-<P>
-
-Print out "tmp0" ..."tmp9" if corresponding vector map exists (each map name linewise):<BR>
-<TT>g.mlist -r type=vect pattern='^tmp[0-9]$'</TT>
-<P>
-
-Print out "tmp0" ..."tmp9" if corresponding vector map exists (each map name comma separated):<BR>
-<TT>g.mlist -r type=vect separator=, pattern='^tmp[0-9]$'</TT>
-<P>
-This may be useful for other programs' parameter input
-(e.g. <EM><A HREF="r.series.html">r.series</A></EM>).
-
-<H2>SEE ALSO</H2>
-
-<EM><A HREF="g.list.html">g.list</A></EM>
-<P>
-<A HREF="http://en.wikipedia.org/wiki/Regular_expression">Regular expression</A> (from Wikipedia, the free encyclopedia)
-
-<H2>AUTHOR</H2>
-Huidae Cho
-<P><I>Last changed: $Date$</I>
Copied: grass/trunk/scripts/g.mlist/g.mlist.html (from rev 32770, grass/trunk/scripts/g.mlist/description.html)
===================================================================
--- grass/trunk/scripts/g.mlist/g.mlist.html (rev 0)
+++ grass/trunk/scripts/g.mlist/g.mlist.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,60 @@
+<H2>DESCRIPTION</H2>
+
+<EM>g.mlist</EM> is an extended version of
+<EM><A HREF="g.list.html">g.list</A></EM> which
+provides support for POSIX Basic Regular Expressions and wildcards.
+<EM>g.mlist</EM> will only print map names and an optional separator,
+without extraneous output. In addition, map search is also available.
+
+<H2>EXAMPLES</H2>
+
+List all available GRASS data base files:
+<BR>
+<TT>g.mlist type=all</TT>
+<P>
+
+List all raster and vector maps:
+<BR>
+<TT>g.mlist type=rast,vect</TT>
+<P>
+
+<H3>Wildcards:</H3>
+
+List all vector maps starting with letter "r":
+<BR>
+<TT>g.mlist type=vect pattern="r*"</TT>
+<P>
+
+List certain raster maps with one variable character/number:
+<BR>
+<TT>g.mlist type=rast pattern="N45E00?.meters"</TT>
+
+<H3>Regular expressions:</H3>
+
+Print out all soils map with "soils" in their name:<BR>
+<TT>g.mlist -r type=rast pattern='^soils'</TT>
+<P>
+
+Print out "tmp" if "tmp" raster map exists:<BR>
+<TT>g.mlist -r pattern='^tmp$'</TT>
+<P>
+
+Print out "tmp0" ..."tmp9" if corresponding vector map exists (each map name linewise):<BR>
+<TT>g.mlist -r type=vect pattern='^tmp[0-9]$'</TT>
+<P>
+
+Print out "tmp0" ..."tmp9" if corresponding vector map exists (each map name comma separated):<BR>
+<TT>g.mlist -r type=vect separator=, pattern='^tmp[0-9]$'</TT>
+<P>
+This may be useful for other programs' parameter input
+(e.g. <EM><A HREF="r.series.html">r.series</A></EM>).
+
+<H2>SEE ALSO</H2>
+
+<EM><A HREF="g.list.html">g.list</A></EM>
+<P>
+<A HREF="http://en.wikipedia.org/wiki/Regular_expression">Regular expression</A> (from Wikipedia, the free encyclopedia)
+
+<H2>AUTHOR</H2>
+Huidae Cho
+<P><I>Last changed: $Date$</I>
Deleted: grass/trunk/scripts/g.mremove/description.html
===================================================================
--- grass/trunk/scripts/g.mremove/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/scripts/g.mremove/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,29 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>g.mremove</em> is an extended version of
-<em><a href="g.remove.html">g.remove</a></em> which
-provides support for POSIX Basic Regular Expressions and wildcards.
-If the <b>-f</b> force flag is not given then nothing is removed, instead
-a functional <em>g.remove</em> command string is printed to <tt>stdout</tt>
-as a preview of the action to be taken.
-
-<h2>EXAMPLE</h2>
-
-Delete all raster maps starting with "<tt>tmp_</tt>" in the current mapset:
-
-<div class="code"><pre>
- g.mremove -f "tmp_*"
-</pre></div>
-
-<h2>SEE ALSO</h2>
-
-<em><a HREF="g.remove.html">g.remove</a></em>
-<p>
-<a href="http://en.wikipedia.org/wiki/Regular_expression">Regular expression</a> (from Wikipedia, the free encyclopedia)
-
-<h2>AUTHOR</h2>
-
-Huidae Cho<br>
-grass4u at gmail.com
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/scripts/g.mremove/g.mremove.html (from rev 32770, grass/trunk/scripts/g.mremove/description.html)
===================================================================
--- grass/trunk/scripts/g.mremove/g.mremove.html (rev 0)
+++ grass/trunk/scripts/g.mremove/g.mremove.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,29 @@
+<h2>DESCRIPTION</h2>
+
+<em>g.mremove</em> is an extended version of
+<em><a href="g.remove.html">g.remove</a></em> which
+provides support for POSIX Basic Regular Expressions and wildcards.
+If the <b>-f</b> force flag is not given then nothing is removed, instead
+a functional <em>g.remove</em> command string is printed to <tt>stdout</tt>
+as a preview of the action to be taken.
+
+<h2>EXAMPLE</h2>
+
+Delete all raster maps starting with "<tt>tmp_</tt>" in the current mapset:
+
+<div class="code"><pre>
+ g.mremove -f "tmp_*"
+</pre></div>
+
+<h2>SEE ALSO</h2>
+
+<em><a HREF="g.remove.html">g.remove</a></em>
+<p>
+<a href="http://en.wikipedia.org/wiki/Regular_expression">Regular expression</a> (from Wikipedia, the free encyclopedia)
+
+<h2>AUTHOR</h2>
+
+Huidae Cho<br>
+grass4u at gmail.com
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/scripts/i.fusion.brovey/description.html
===================================================================
--- grass/trunk/scripts/i.fusion.brovey/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/scripts/i.fusion.brovey/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,56 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-<EM>i.fusion.brovey</EM> performs a Brovey transformation using
-three multispectral and the panchromatic satellite image scene
-channels. Three new channels are calculated according to the
-formula:
-
-<pre>
- DN_b1
- DN_fused = ------------------------------- * DN_pan
- DN_b1 + DN_b2 + DN_b3
-</pre>
-
-The assignment of the channels depends on the satellite.
-The module's help text (above) suggests for LANDSAT-7, QuickBird and SPOT.
-
-<H2>NOTES</H2>
-The command changes temporarily to the high resolution of the
-panchromatic channels for creating the three output channels,
-then restores the previous region settings. The current
-region coordinates are respected. The three pan-sharpened output
-channels may be combined with <em>d.rgb</em> or <em>r.composite</em>.
-
-<H2>SEE ALSO</H2>
-
-<EM>
-<A HREF="i.his.rgb.html">i.his.rgb</A>,
-<A HREF="i.rgb.his.html">i.rgb.his</A>,
-<A HREF="d.rgb.html">d.rgb</A>,
-<A HREF="r.composite.html">r.composite</A>
-</EM>
-
-<H2>REFERENCES</H2>
-
-<ul>
-<li>Original Brovey formula reference unknown, probably <br>
- Roller, N.E.G. and Cox, S., 1980. Comparison of Landsat MSS
- and merged MSS/RBV data for analysis of natural vegetation.
- Proc. of the 14th International Symposium on Remote Sensing
- of Environment, San Jose, Costa Rica, 23-30 April, pp. 1001-1007
-
-<li>Pohl, C., and J.L. van Genderen, 1998.
- Multisensor image fusion in remote sensing: concepts, methods and
- application. Int. J. of Rem. Sens., 19, 823-854.
-
-<li>M. Neteler, D. Grasso, I. Michelazzi, L. Miori, S. Merler, and C.
- Furlanello, 2005.
- An integrated toolbox for image registration, fusion and classification.
- International Journal of Geoinformatics, Special Issue
- on <a href="http://gisws.media.osaka-cu.ac.jp/grass04/viewabstract.php?id=37">FOSS/GRASS 2004 & GIS-IDEAS 2004</a> (in press)
-</ul>
-
-<H2>AUTHOR</H2>
-
-Markus Neteler, ITC-irst
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/scripts/i.fusion.brovey/i.fusion.brovey.html (from rev 32770, grass/trunk/scripts/i.fusion.brovey/description.html)
===================================================================
--- grass/trunk/scripts/i.fusion.brovey/i.fusion.brovey.html (rev 0)
+++ grass/trunk/scripts/i.fusion.brovey/i.fusion.brovey.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,56 @@
+<H2>DESCRIPTION</H2>
+
+<EM>i.fusion.brovey</EM> performs a Brovey transformation using
+three multispectral and the panchromatic satellite image scene
+channels. Three new channels are calculated according to the
+formula:
+
+<pre>
+ DN_b1
+ DN_fused = ------------------------------- * DN_pan
+ DN_b1 + DN_b2 + DN_b3
+</pre>
+
+The assignment of the channels depends on the satellite.
+The module's help text (above) suggests for LANDSAT-7, QuickBird and SPOT.
+
+<H2>NOTES</H2>
+The command changes temporarily to the high resolution of the
+panchromatic channels for creating the three output channels,
+then restores the previous region settings. The current
+region coordinates are respected. The three pan-sharpened output
+channels may be combined with <em>d.rgb</em> or <em>r.composite</em>.
+
+<H2>SEE ALSO</H2>
+
+<EM>
+<A HREF="i.his.rgb.html">i.his.rgb</A>,
+<A HREF="i.rgb.his.html">i.rgb.his</A>,
+<A HREF="d.rgb.html">d.rgb</A>,
+<A HREF="r.composite.html">r.composite</A>
+</EM>
+
+<H2>REFERENCES</H2>
+
+<ul>
+<li>Original Brovey formula reference unknown, probably <br>
+ Roller, N.E.G. and Cox, S., 1980. Comparison of Landsat MSS
+ and merged MSS/RBV data for analysis of natural vegetation.
+ Proc. of the 14th International Symposium on Remote Sensing
+ of Environment, San Jose, Costa Rica, 23-30 April, pp. 1001-1007
+
+<li>Pohl, C., and J.L. van Genderen, 1998.
+ Multisensor image fusion in remote sensing: concepts, methods and
+ application. Int. J. of Rem. Sens., 19, 823-854.
+
+<li>M. Neteler, D. Grasso, I. Michelazzi, L. Miori, S. Merler, and C.
+ Furlanello, 2005.
+ An integrated toolbox for image registration, fusion and classification.
+ International Journal of Geoinformatics, Special Issue
+ on <a href="http://gisws.media.osaka-cu.ac.jp/grass04/viewabstract.php?id=37">FOSS/GRASS 2004 & GIS-IDEAS 2004</a> (in press)
+</ul>
+
+<H2>AUTHOR</H2>
+
+Markus Neteler, ITC-irst
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/scripts/i.image.mosaic/description.html
===================================================================
--- grass/trunk/scripts/i.image.mosaic/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/scripts/i.image.mosaic/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,18 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-
-<EM>i.image.mosaic</EM> Mosaics up to 4 images or raster maps using map calculator, and extends colormap to range of all images.
-<br>
-
-
-<H2>SEE ALSO</H2>
-
-<EM><A HREF="r.patch.html">r.patch</A></EM>,
-<EM><A HREF="r.mapcalc.html">r.mapcalc</A></EM>,
-
-
-<H2>AUTHOR</H2>
-
-Markus Neteler, ITC-Irst, Trento, Italy
-Updated to GRASS 5.7 by Michael Barton, Arizona State University
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/scripts/i.image.mosaic/i.image.mosaic.html (from rev 32770, grass/trunk/scripts/i.image.mosaic/description.html)
===================================================================
--- grass/trunk/scripts/i.image.mosaic/i.image.mosaic.html (rev 0)
+++ grass/trunk/scripts/i.image.mosaic/i.image.mosaic.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,18 @@
+<H2>DESCRIPTION</H2>
+
+
+<EM>i.image.mosaic</EM> Mosaics up to 4 images or raster maps using map calculator, and extends colormap to range of all images.
+<br>
+
+
+<H2>SEE ALSO</H2>
+
+<EM><A HREF="r.patch.html">r.patch</A></EM>,
+<EM><A HREF="r.mapcalc.html">r.mapcalc</A></EM>,
+
+
+<H2>AUTHOR</H2>
+
+Markus Neteler, ITC-Irst, Trento, Italy
+Updated to GRASS 5.7 by Michael Barton, Arizona State University
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/scripts/i.in.spotvgt/description.html
===================================================================
--- grass/trunk/scripts/i.in.spotvgt/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/scripts/i.in.spotvgt/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,51 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>i.in.spotvgt</em> imports SPOT Vegetation (1km, global) NDVI data sets.
-After import the digital numbers (DN) are remapped to VEGETATION NDVI
-values and the NDVI color table is applied. The imported DN map is
-removed after remapping.
-<P>
-Apparently missing raster cells due to bad pixel quality are reconstructed
-by the SPOT operating team in the NDVI file. The differences between the
-filtered (-a flag) and raw NDVI map should be compared.
-
-<h2>NOTES</h2>
-
-The SPOT VGT files are delivered in HDF4 (Hierarchical Data Format Release 4)
-format. It is required to have the GDAL libraries installed with HDF4 support.
-
-<h3>Export of entire world SPOT VGT maps</h3>
-
-When working with SPOT VGT with entire world extent, it is recommended
-to zoom to <i>w=180W</i> and <i>e=180E</i> instead of using the map
-extent for map export. These entire world SPOT VGT data are exceeding
--180.0 degree which can lead to unhelpful large East-West coordinates in
-the exported file. It is also recommended to then use an export command
-which respects the user settings. Example:
-
-<div class="code"><pre>
-# import:
-i.in.spotvgt 0001_NDV.HDF
-
-# export:
-g.region w=180W e=180E n=75:00:16.071429N s=56:00:16.069919S res=0:00:32.142857 -p
-r.out.tiff -t 0001_NDV out=spotndvi
-</pre></div>
-
-<h2>SEE ALSO</h2>
-
-<em>
-<a HREF="r.in.gdal.html">r.in.gdal</a>
-</em>
-
-<H2>REFERENCES</H2>
-
-<a href="http://free.vgt.vito.be/">SPOT Vegetation (1km, global) NDVI data set server</a><br>
-<a href="http://www.vgt.vito.be/faq/faq.html">SPOT Vegetation FAQ</a><br>
-<a href="http://www.vgt.vito.be/faq/FAQS/faq15.html">SPOT Vegetation Status Map (SM)</a> - Quality map
-
-<h2>AUTHOR</h2>
-
-Markus Neteler</a>
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/scripts/i.in.spotvgt/i.in.spotvgt.html (from rev 32770, grass/trunk/scripts/i.in.spotvgt/description.html)
===================================================================
--- grass/trunk/scripts/i.in.spotvgt/i.in.spotvgt.html (rev 0)
+++ grass/trunk/scripts/i.in.spotvgt/i.in.spotvgt.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,51 @@
+<h2>DESCRIPTION</h2>
+
+<em>i.in.spotvgt</em> imports SPOT Vegetation (1km, global) NDVI data sets.
+After import the digital numbers (DN) are remapped to VEGETATION NDVI
+values and the NDVI color table is applied. The imported DN map is
+removed after remapping.
+<P>
+Apparently missing raster cells due to bad pixel quality are reconstructed
+by the SPOT operating team in the NDVI file. The differences between the
+filtered (-a flag) and raw NDVI map should be compared.
+
+<h2>NOTES</h2>
+
+The SPOT VGT files are delivered in HDF4 (Hierarchical Data Format Release 4)
+format. It is required to have the GDAL libraries installed with HDF4 support.
+
+<h3>Export of entire world SPOT VGT maps</h3>
+
+When working with SPOT VGT with entire world extent, it is recommended
+to zoom to <i>w=180W</i> and <i>e=180E</i> instead of using the map
+extent for map export. These entire world SPOT VGT data are exceeding
+-180.0 degree which can lead to unhelpful large East-West coordinates in
+the exported file. It is also recommended to then use an export command
+which respects the user settings. Example:
+
+<div class="code"><pre>
+# import:
+i.in.spotvgt 0001_NDV.HDF
+
+# export:
+g.region w=180W e=180E n=75:00:16.071429N s=56:00:16.069919S res=0:00:32.142857 -p
+r.out.tiff -t 0001_NDV out=spotndvi
+</pre></div>
+
+<h2>SEE ALSO</h2>
+
+<em>
+<a HREF="r.in.gdal.html">r.in.gdal</a>
+</em>
+
+<H2>REFERENCES</H2>
+
+<a href="http://free.vgt.vito.be/">SPOT Vegetation (1km, global) NDVI data set server</a><br>
+<a href="http://www.vgt.vito.be/faq/faq.html">SPOT Vegetation FAQ</a><br>
+<a href="http://www.vgt.vito.be/faq/FAQS/faq15.html">SPOT Vegetation Status Map (SM)</a> - Quality map
+
+<h2>AUTHOR</h2>
+
+Markus Neteler</a>
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/scripts/i.landsat.rgb/description.html
===================================================================
--- grass/trunk/scripts/i.landsat.rgb/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/scripts/i.landsat.rgb/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,58 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-<EM>i.landsat.rgb</EM> auto-balances and enhances the color channels of a
-LANDSAT RGB image to provide a more natural color mixture. Only the color
-table of each image band is modified, the base data remains untouched.
-<P>
-The module works by calculating a histogram for each color channel and
-removing an adjustable amount of outliers from either end before recalibrating
-the color scale with <em>r.colors</em>.
-<P>
-It will work with any 8-bit RGB imagery set and the script is easily modified
-to work with other datasets of greater band-depth.
-
-<H2>NOTES</H2>
-
-Depending on the image, it may or may not be advantageous to use the <B>-p</B>
-flag to preserve the relative color scaling. You will have to experiment
-with the different options to find a setting that works best for your
-particular imagery.
-<P>
-The <b>strength</b> option should generally be set in the 90-99 range. The
-lower the number, the more saturated the image becomes. It represents the
-percentage cut-off for the top end of the color histogram curve. The lower
-end is fixed at 2% of the area under the curve.
-<P>
-For quicker execution of this module on large images you can achieve largely
-similar results by switching to a coarser resolution before the running of
-the module (using <EM>g.region</EM>) and then back to the original resolution
-afterwards.
-
-
-<H2>EXAMPLE</H2>
-
-<div class="code"><pre>
-i.landsat.rgb red=tm.3 green=tm.2 blue=tm.1
-</pre></div>
-
-<H2>TODO</H2>
-
-The <b>strength</b> option requires further refinement.
-
-
-<H2>SEE ALSO</H2>
-
-<EM><A HREF="d.rgb.html">d.rgb</A></EM>,
-<EM><A HREF="g.region.html">g.region</A></EM>,
-<EM><A HREF="i.oif.html">i.oif</A></EM>,
-<EM><A HREF="r.colors.html">r.colors</A></EM>,
-<EM><A HREF="r.composite.html">r.composite</A></EM>,
-<EM><A HREF="r.univar.html">r.univar</A></EM>,
-
-
-<H2>AUTHORS</H2>
-
-Markus Neteler<BR>
-M. Hamish Bowman, Dept. Marine Science, Otago University, New Zealand
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/scripts/i.landsat.rgb/i.landsat.rgb.html (from rev 32770, grass/trunk/scripts/i.landsat.rgb/description.html)
===================================================================
--- grass/trunk/scripts/i.landsat.rgb/i.landsat.rgb.html (rev 0)
+++ grass/trunk/scripts/i.landsat.rgb/i.landsat.rgb.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,58 @@
+<H2>DESCRIPTION</H2>
+
+<EM>i.landsat.rgb</EM> auto-balances and enhances the color channels of a
+LANDSAT RGB image to provide a more natural color mixture. Only the color
+table of each image band is modified, the base data remains untouched.
+<P>
+The module works by calculating a histogram for each color channel and
+removing an adjustable amount of outliers from either end before recalibrating
+the color scale with <em>r.colors</em>.
+<P>
+It will work with any 8-bit RGB imagery set and the script is easily modified
+to work with other datasets of greater band-depth.
+
+<H2>NOTES</H2>
+
+Depending on the image, it may or may not be advantageous to use the <B>-p</B>
+flag to preserve the relative color scaling. You will have to experiment
+with the different options to find a setting that works best for your
+particular imagery.
+<P>
+The <b>strength</b> option should generally be set in the 90-99 range. The
+lower the number, the more saturated the image becomes. It represents the
+percentage cut-off for the top end of the color histogram curve. The lower
+end is fixed at 2% of the area under the curve.
+<P>
+For quicker execution of this module on large images you can achieve largely
+similar results by switching to a coarser resolution before the running of
+the module (using <EM>g.region</EM>) and then back to the original resolution
+afterwards.
+
+
+<H2>EXAMPLE</H2>
+
+<div class="code"><pre>
+i.landsat.rgb red=tm.3 green=tm.2 blue=tm.1
+</pre></div>
+
+<H2>TODO</H2>
+
+The <b>strength</b> option requires further refinement.
+
+
+<H2>SEE ALSO</H2>
+
+<EM><A HREF="d.rgb.html">d.rgb</A></EM>,
+<EM><A HREF="g.region.html">g.region</A></EM>,
+<EM><A HREF="i.oif.html">i.oif</A></EM>,
+<EM><A HREF="r.colors.html">r.colors</A></EM>,
+<EM><A HREF="r.composite.html">r.composite</A></EM>,
+<EM><A HREF="r.univar.html">r.univar</A></EM>,
+
+
+<H2>AUTHORS</H2>
+
+Markus Neteler<BR>
+M. Hamish Bowman, Dept. Marine Science, Otago University, New Zealand
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/scripts/i.oif/description.html
===================================================================
--- grass/trunk/scripts/i.oif/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/scripts/i.oif/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,50 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-<EM>i.oif</EM> calculates the Optimum Index Factor for LANDSAT TM bands 1,2,3,4,5 and 7.
-<P>
-The Optimum Index Factor is calculated to determine the band combination which
-shows the maximum information when combined into a composite image. The bands
-comprising the highest scoring combination from <EM>i.oif</EM> are used as the
-three color channels required for <EM><A HREF="d.rgb.html">d.rgb</A></EM> or
-<EM><A HREF="r.composite.html">r.composite</A></EM>.
-<P>
-The analysis is saved to a file in the current directory called "i.oif.result".
-
-<H2>NOTES</H2>
-
-Colour Composits in BGR order: important band combinations (example:
-234 in BGR order means: B=2, G=3, R=4):
-
-<ul>
-<li> 123: near natural ("true") colour; however, because of correlation of the 3 bands in visible
- spectrum, this combination contains not much more info than is contained in single band.
-<li> 234: sensitive to green vegetation (portrayed as red), coniferous as distinctly darker
- red than deciduous forests. Roads and water bodies are clear.
-<li> 243: green vegetation is green but coniferous forests aren't as clear as in the 234 combination
-<li> 247: one of the best for info pertaining to forestry. Good for operation scale mapping of
- recent harvest areas and road construction.
-<li> 345: contains one band from each of the main reflective units (vis, nir, shortwave infra).
- Green vegetation is green and the shortwave band shows vegetational stress and mortality.
- Roads are less evident as band 3 is blue.
-<li> 347: similar to 345 but depicts burned areas better.
-<li> 354: appears more like a colour infrared photo.
-<li> 374: similar to 354.
-<li> 457: shows soil texture classes (clay, loam, sandy).
-</ul>
-
-
-<H2>REFERENCES</H2>
-
-Jensen, 1996. Introductory digital image processing, p.98. ISBN 0-13-205840-5
-
-<H2>SEE ALSO</H2>
-<EM><A HREF="d.rgb.html">d.rgb</A></EM><BR>
-<EM><A HREF="r.composite.html">r.composite</A></EM><BR>
-<EM><A HREF="r.covar.html">r.covar</A></EM><BR>
-<EM><A HREF="r.univar.html">r.univar</A></EM><BR>
-<BR>
-<H2>AUTHOR</H2>
-
-Markus Neteler, ITC-Irst, Trento, Italy<br>
-Updated to GRASS 5.7 by Michael Barton, Arizona State University
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/scripts/i.oif/i.oif.html (from rev 32770, grass/trunk/scripts/i.oif/description.html)
===================================================================
--- grass/trunk/scripts/i.oif/i.oif.html (rev 0)
+++ grass/trunk/scripts/i.oif/i.oif.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,50 @@
+<H2>DESCRIPTION</H2>
+
+<EM>i.oif</EM> calculates the Optimum Index Factor for LANDSAT TM bands 1,2,3,4,5 and 7.
+<P>
+The Optimum Index Factor is calculated to determine the band combination which
+shows the maximum information when combined into a composite image. The bands
+comprising the highest scoring combination from <EM>i.oif</EM> are used as the
+three color channels required for <EM><A HREF="d.rgb.html">d.rgb</A></EM> or
+<EM><A HREF="r.composite.html">r.composite</A></EM>.
+<P>
+The analysis is saved to a file in the current directory called "i.oif.result".
+
+<H2>NOTES</H2>
+
+Colour Composits in BGR order: important band combinations (example:
+234 in BGR order means: B=2, G=3, R=4):
+
+<ul>
+<li> 123: near natural ("true") colour; however, because of correlation of the 3 bands in visible
+ spectrum, this combination contains not much more info than is contained in single band.
+<li> 234: sensitive to green vegetation (portrayed as red), coniferous as distinctly darker
+ red than deciduous forests. Roads and water bodies are clear.
+<li> 243: green vegetation is green but coniferous forests aren't as clear as in the 234 combination
+<li> 247: one of the best for info pertaining to forestry. Good for operation scale mapping of
+ recent harvest areas and road construction.
+<li> 345: contains one band from each of the main reflective units (vis, nir, shortwave infra).
+ Green vegetation is green and the shortwave band shows vegetational stress and mortality.
+ Roads are less evident as band 3 is blue.
+<li> 347: similar to 345 but depicts burned areas better.
+<li> 354: appears more like a colour infrared photo.
+<li> 374: similar to 354.
+<li> 457: shows soil texture classes (clay, loam, sandy).
+</ul>
+
+
+<H2>REFERENCES</H2>
+
+Jensen, 1996. Introductory digital image processing, p.98. ISBN 0-13-205840-5
+
+<H2>SEE ALSO</H2>
+<EM><A HREF="d.rgb.html">d.rgb</A></EM><BR>
+<EM><A HREF="r.composite.html">r.composite</A></EM><BR>
+<EM><A HREF="r.covar.html">r.covar</A></EM><BR>
+<EM><A HREF="r.univar.html">r.univar</A></EM><BR>
+<BR>
+<H2>AUTHOR</H2>
+
+Markus Neteler, ITC-Irst, Trento, Italy<br>
+Updated to GRASS 5.7 by Michael Barton, Arizona State University
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/scripts/i.spectral/description.html
===================================================================
--- grass/trunk/scripts/i.spectral/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/scripts/i.spectral/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,38 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>i.spectral</em> displays spectral response at user specified
-locations in images.
-
-<h2>NOTES</h2>
-
-This script needs gnuplot to be installed.
-
-
-<H2>EXAMPLE</H2>
-
-To analyze a time series of maps, run:
-
-<div class="code"><pre>
-d.rast map_1
-LIST=`g.mlist type=rast mapset=timeseries pat="map_*" | sort -t '_' -k 2 -n | tr '\n' ','| sed 's+,$++g'`
-i.spectral -i rast=$LIST
-</pre></div>
-
-This will search all maps in the mapset 'timeseries' which match have
-the 'map_' prefix and order by a number following this prefix (day of the
-year etc). The user is then asked to click into a map position and the
-resulting pixel values of all matching maps are drawn in the gnuplot
-output.
-
-<h2>SEE ALSO</h2>
-
-<em><a HREF="d.what.rast.html">d.what.rast</a></em><br>
-<em><a HREF="d.where.html">d.where</a></em><br>
-<em><a HREF="r.what.html">r.what</a></em><br>
-
-<h2>AUTHOR</h2>
-
-Markus Neteler<br>
-Francesco Pirotti
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/scripts/i.spectral/i.spectral.html (from rev 32770, grass/trunk/scripts/i.spectral/description.html)
===================================================================
--- grass/trunk/scripts/i.spectral/i.spectral.html (rev 0)
+++ grass/trunk/scripts/i.spectral/i.spectral.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,38 @@
+<h2>DESCRIPTION</h2>
+
+<em>i.spectral</em> displays spectral response at user specified
+locations in images.
+
+<h2>NOTES</h2>
+
+This script needs gnuplot to be installed.
+
+
+<H2>EXAMPLE</H2>
+
+To analyze a time series of maps, run:
+
+<div class="code"><pre>
+d.rast map_1
+LIST=`g.mlist type=rast mapset=timeseries pat="map_*" | sort -t '_' -k 2 -n | tr '\n' ','| sed 's+,$++g'`
+i.spectral -i rast=$LIST
+</pre></div>
+
+This will search all maps in the mapset 'timeseries' which match have
+the 'map_' prefix and order by a number following this prefix (day of the
+year etc). The user is then asked to click into a map position and the
+resulting pixel values of all matching maps are drawn in the gnuplot
+output.
+
+<h2>SEE ALSO</h2>
+
+<em><a HREF="d.what.rast.html">d.what.rast</a></em><br>
+<em><a HREF="d.where.html">d.where</a></em><br>
+<em><a HREF="r.what.html">r.what</a></em><br>
+
+<h2>AUTHOR</h2>
+
+Markus Neteler<br>
+Francesco Pirotti
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/scripts/i.tasscap/description.html
===================================================================
--- grass/trunk/scripts/i.tasscap/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/scripts/i.tasscap/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,27 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-
-<EM>i.tasscap</EM> calculates Tasseled Cap (Kauth Thomas) transformation for
-LANDSAT-TM data (TM4, TM5, TM7).
-
-<H2>REFERENCES</H2>
-
-<ul>
-<li>LANDSAT-4/LANDSAT-5: TC-factor changed to CRIST et al. 1986,
- Proc. IGARSS 1986, p.1467
-<li>LANDSAT-7: TASSCAP factors cited from:
- DERIVATION OF A TASSELED CAP TRANSFORMATION BASED ON LANDSAT 7 AT-SATELLITE REFLECTANCE
- Chengquan Huang, Bruce Wylie, Limin Yang, Collin Homer and Gregory Zylstra Raytheon ITSS,
- USGS EROS Data Center Sioux Falls, SD 57198, USA
- http://landcover.usgs.gov/pdf/tasseled.pdf
-<br>
- This is published as well in INT. J. OF RS, 2002, VOL 23, NO. 8, 1741-1748.
-<br>
- Compare discussion:
- http://adis.cesnet.cz/cgi-bin/lwgate/IMAGRS-L/archives/imagrs-l.log0211/date/article-14.html
-</ul>
-
-<H2>AUTHOR</H2>
-
-Markus Neteler, ITC-irst
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/scripts/i.tasscap/i.tasscap.html (from rev 32770, grass/trunk/scripts/i.tasscap/description.html)
===================================================================
--- grass/trunk/scripts/i.tasscap/i.tasscap.html (rev 0)
+++ grass/trunk/scripts/i.tasscap/i.tasscap.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,27 @@
+<H2>DESCRIPTION</H2>
+
+
+<EM>i.tasscap</EM> calculates Tasseled Cap (Kauth Thomas) transformation for
+LANDSAT-TM data (TM4, TM5, TM7).
+
+<H2>REFERENCES</H2>
+
+<ul>
+<li>LANDSAT-4/LANDSAT-5: TC-factor changed to CRIST et al. 1986,
+ Proc. IGARSS 1986, p.1467
+<li>LANDSAT-7: TASSCAP factors cited from:
+ DERIVATION OF A TASSELED CAP TRANSFORMATION BASED ON LANDSAT 7 AT-SATELLITE REFLECTANCE
+ Chengquan Huang, Bruce Wylie, Limin Yang, Collin Homer and Gregory Zylstra Raytheon ITSS,
+ USGS EROS Data Center Sioux Falls, SD 57198, USA
+ http://landcover.usgs.gov/pdf/tasseled.pdf
+<br>
+ This is published as well in INT. J. OF RS, 2002, VOL 23, NO. 8, 1741-1748.
+<br>
+ Compare discussion:
+ http://adis.cesnet.cz/cgi-bin/lwgate/IMAGRS-L/archives/imagrs-l.log0211/date/article-14.html
+</ul>
+
+<H2>AUTHOR</H2>
+
+Markus Neteler, ITC-irst
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/scripts/m.proj/description.html
===================================================================
--- grass/trunk/scripts/m.proj/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/scripts/m.proj/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,189 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-This program allows a user to convert coordinates from one projection to
-another. Coordinates can be read from one file, converted, and results
-written to another file. Alternatively, if the <b>input</b> and/or
-<b>output</b> options are omitted, eastings and northings may be passed
-to the program directly from <tt>stdin</tt> and results sent directly
-to <tt>stdout</tt>. In this way <em>m.proj</em> can be used as a simple
-frontend to the <tt><a href="http://proj.maptools.org">PROJ.4</a></tt>
-<em>cs2cs</em> utility. The <b>-i</b> or <b>-o</b> flags make the task
-especially easy for the common problem of converting to or from lat/long
-WGS84.
-<P>
-<i>Note</i>: This program does not transform GRASS maps, it is designed to determine
-the equivalent coordinate values of an individual position or list of
-positions. Use <em>v.proj</em> or <em>r.proj</em> to reproject GRASS maps.
-
-
-<H2>NOTES</H2>
-
-<em>cs2cs</em> expects input data to formatted as "<tt>x y</tt>", so if working
-with latitude-longitude data be sure to send the <tt>x</tt> value first,
-i.e., "<tt>longitude latitude</tt>". Output data will be exported using
-the same convention.
-<P>
-<em>cs2cs</em> will treat a third data column as a <tt>z</tt> value (elevation)
-and will modify the value accordingly. This usually translates into small but
-real differences in that data column.
-<P>
-<em>cs2cs</em> does not expect the input stream to contain column headings,
-only numbers. If your data file has lines you wish to have passed through
-without being processed, they must start with the '<tt>#</tt>' character.
-<P>
-If sending <em>m.proj</em> data from <tt>stdin</tt>, be aware that the data is
-first stored to a temporary file before being processed with <em>cs2cs</em>.
-It is therefore not advisable to send <em>m.proj</em> data from an open data
-stream. The module will stop listening for incoming data after 2 seconds of
-inactivity. You may use the projection parameters gleaned from <em>m.proj</em>'s
-verbose mode (<b>-v</b>) with <em>cs2cs</em> directly in this case.
-<P>
-Custom projection parameters can be used via the <b>proj_in</b> and
-<b>proj_out</b> options. Full documentation of the projection parameter
-format may be found on the <tt><a href="http://proj.maptools.org">PROJ.4</a></tt>
-website. Using these options will fully override the default parameters the
-module would normally use.
-<P>
-By using the <b>-v</b> verbose flag, the user can see exactly what projection
-parameters will be used in the conversion as well as some other informative
-messages.
-<P>
-If output is to lat/long, it will be formatted using <tt>PROJ.4</tt>'s
-Degree:Minute:Second (DMS) convention of <tt>DDDdMM'SSS.SS"H</tt>. This can be handy
-if you wish to quickly convert lat/long decimal degree data into its DMS
-equivalent.<BR>
-Alternatively, to have <em>m.proj</em> output data in decimal degrees, use the
-<b>-d</b> flag. This flag can also be used with non-lat/long data to force a
-higher number of decimal places (the <em>cs2cs</em> default is 2).
-<P>
-Lat/long output can be converted to GRASS's DMS convention (<tt>DDD:MM:SSS.SSSH</tt>)
-by piping the results of <em>m.proj</em> through the <em>sed</em> stream
-editor as follows.
-<div class="code"><pre>
-m.proj -o | sed -e 's/d/:/g' -e "s/'/:/g" -e 's/"//g'
-</pre></div>
-<P>
-The <em>m.proj</em> module is designed to work seamlessly with point data
-exported from the GIS with <em>v.out.ascii</em>, as the following example
-shows.
-<div class="code"><pre>
-v.out.ascii bugsites | m.proj -o
-</pre></div>
-
-
-<H2>EXAMPLES</H2>
-
-To convert a WGS84 long/lat coordinate to the current map projection using
-the <b>-i</b> flag to set projection parameters automaticlly:
-<div class="code"><pre>
-GRASS> echo "170.510125 -45.868537" | m.proj -i
-2316541.70 5479193.51 1.23
-</pre></div>
-
-<P><BR>
-The same, but load points from a file named "<tt>waypoints.txt</tt>" and
-continue on to import the results into a GRASS vector points map in the
-current map projection:
-<div class="code"><pre>
-m.proj -i in=waypoints.txt | cut -f1 -d' ' | v.in.ascii out=test_pt fs=tab
-</pre></div>
-Here the standard UNIX <em>cut</em> tool is used to discard the <tt>z</tt>
-residual.
-
-<P><BR>
-To convert all coordinates from a vector points map in the current projection
-to WGS84 long/lat, with output in decimal form:
-<div class="code"><pre>
-v.out.ascii bugsites | m.proj -od
-</pre></div>
-
-<P><BR>
-To transform points from a UTM projection into the Gauss-Krüger Grid
-System, importing and exporting to files:
-
-<div class="code"><pre>
-m.proj <b>proj_in</b>="+proj=utm +name=utm +a=6378137.0 +es=0.006694380 \
- +zone=32 +unfact=1.0" <b>proj_out</b>="+proj=tmerc +name=tmerc \
- +a=6377397.155 +es=0.0066743720 +lat_0=0.0 +lon_0=9.0 +k=1.0 \
- +x_0=3500000.0" <b>input</b>=utm.coord.txt <b>output</b>=new.gk.coord.txt
-</pre></div>
-
-<P>
-Projection parameters provided in the above case: "<tt>+proj</tt>" (projection
-type), "<tt>+name</tt>" (projection name), "<tt>+a</tt>" (ellipsoid: equatorial
-radius), "<tt>+es</tt>" (ellipsoid: eccentricity squared), "<tt>+zone</tt>"
-(zone for the area), "<tt>+unfact</tt>" (conversion factor from meters to other
-units, e.g. feet), "<tt>+lat_0</tt>" (standard parallel), "<tt>+lon_0</tt>"
-(central meridian), "<tt>+k</tt>" (scale factor) and "<tt>+x_0</tt>" (false
-easting). Sometimes false northing is needed which is coded as "<tt>+y_0</tt>".
-Internally, the underlying
-<a href="http://www.remotesensing.org/proj/"><tt>PROJ.4</tt> projection library</a>
-performs an inverse projection to latitude-longitude and then projects the
-coordinate list to the target projection.
-<P><BR>
-<!-- HB 4/2006: I'm leaving this in from the GRASS 5 help page, but is it accurate? -->
-Datum conversions are automatically handled by the <tt>PROJ.4</tt> library if
-"<tt>+datum</tt>" setings are specified on <b>both</b> the input <b>and</b> output
-projections on the command line. The "<tt>+towgs84</tt>" parameter can be used to
-define either 3 or 7 term datum transform coefficients, satisfying this requirement.
-<P>
-If a datum is specified there is no need for the '<tt>+ellps=</tt>' or underlying
-parameters, '<tt>+a=</tt>', '<tt>+es=</tt>', etc.
-<p>
-<h4>Another custom parameter usage example:</h4>
-
-<div class="code"><pre>
-m.proj <B>proj_in</B>="+proj=tmerc +datum=ire65 +lat_0=53.5 +lon_0=-8 +x_0=200000 \
- +y_0=250000 +k=1.000035" <B>proj_out</B>="+proj=ll +datum=wgs84" <B>input</B>=wpt.txt
-</pre></div>
-
-or without datum transformation:
-
-<div class="code"><pre>
-m.proj <B>proj_in</B>="+proj=tmerc +ellps=modif_airy +lat_0=53.5 +lon_0=-8 +x_0=200000 \
- +y_0=250000 +k=1.000035" <B>proj_out</B>="+proj=ll +datum=wgs84" <B>input</B>=wpt.txt
-</pre></div>
-
-<P>
-In this example no datum transformation will take place as a datum was not
-specified for the input projection. The datum specified for the output
-projection will thus be silently ignored and may be left out; all that is
-achieved a simple conversion from projected to geodetic co-ordinates,
-keeping the same datum (and thus also the same ellipsoid).</p>
-
-<p>
-For more usage examples, see the documentation for the
-<tt><a href="http://proj.maptools.org">PROJ.4</a></tt> <em>cs2cs</em> program.
-
-
-<H2>REFERENCES</H2>
-
-[1] Evenden, G.I. (1990) <a href="http://proj.maptools.org/">Cartographic projection procedures for
-the UNIX environment - a user's manual.</a> USGS Open-File Report 90-284 (OF90-284.pdf)
-See also there: Interim Report and 2nd Interim Report on Release 4, Evenden 1994).
-<P>
-[2] <tt><a href="http://proj.maptools.org">PROJ.4</a></tt> Cartographic Projection Library
-
-
-<H2>SEE ALSO</H2>
-
-<EM>
-<A HREF="v.proj.html">v.proj</A>,
-<A HREF="r.proj.html">r.proj</A>,
-<A HREF="g.proj.html">g.proj</A>,
-<A HREF="g.setproj.html">g.setproj</A>,
-<A HREF="i.rectify.html">i.rectify</A>,
-<!-- <A HREF="i.rectify3.html">i.rectify3</A> -->
-<A HREF="v.in.ascii.html">v.in.ascii</A>,
-<A HREF="v.out.ascii.html">v.out.ascii</A>
-</EM>
-
-
-<H2>AUTHOR</H2>
-
-M. Hamish Bowman, Dept. Marine Science, Otago University, New Zealand<BR>
-Functionality inspired by the <em>m.proj</em> and <em>m.proj2</em> modules for
-GRASS GIS 5.
-
-<p><i>Last changed: $Date$</i></p>
-
Copied: grass/trunk/scripts/m.proj/m.proj.html (from rev 32770, grass/trunk/scripts/m.proj/description.html)
===================================================================
--- grass/trunk/scripts/m.proj/m.proj.html (rev 0)
+++ grass/trunk/scripts/m.proj/m.proj.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,189 @@
+<H2>DESCRIPTION</H2>
+
+This program allows a user to convert coordinates from one projection to
+another. Coordinates can be read from one file, converted, and results
+written to another file. Alternatively, if the <b>input</b> and/or
+<b>output</b> options are omitted, eastings and northings may be passed
+to the program directly from <tt>stdin</tt> and results sent directly
+to <tt>stdout</tt>. In this way <em>m.proj</em> can be used as a simple
+frontend to the <tt><a href="http://proj.maptools.org">PROJ.4</a></tt>
+<em>cs2cs</em> utility. The <b>-i</b> or <b>-o</b> flags make the task
+especially easy for the common problem of converting to or from lat/long
+WGS84.
+<P>
+<i>Note</i>: This program does not transform GRASS maps, it is designed to determine
+the equivalent coordinate values of an individual position or list of
+positions. Use <em>v.proj</em> or <em>r.proj</em> to reproject GRASS maps.
+
+
+<H2>NOTES</H2>
+
+<em>cs2cs</em> expects input data to formatted as "<tt>x y</tt>", so if working
+with latitude-longitude data be sure to send the <tt>x</tt> value first,
+i.e., "<tt>longitude latitude</tt>". Output data will be exported using
+the same convention.
+<P>
+<em>cs2cs</em> will treat a third data column as a <tt>z</tt> value (elevation)
+and will modify the value accordingly. This usually translates into small but
+real differences in that data column.
+<P>
+<em>cs2cs</em> does not expect the input stream to contain column headings,
+only numbers. If your data file has lines you wish to have passed through
+without being processed, they must start with the '<tt>#</tt>' character.
+<P>
+If sending <em>m.proj</em> data from <tt>stdin</tt>, be aware that the data is
+first stored to a temporary file before being processed with <em>cs2cs</em>.
+It is therefore not advisable to send <em>m.proj</em> data from an open data
+stream. The module will stop listening for incoming data after 2 seconds of
+inactivity. You may use the projection parameters gleaned from <em>m.proj</em>'s
+verbose mode (<b>-v</b>) with <em>cs2cs</em> directly in this case.
+<P>
+Custom projection parameters can be used via the <b>proj_in</b> and
+<b>proj_out</b> options. Full documentation of the projection parameter
+format may be found on the <tt><a href="http://proj.maptools.org">PROJ.4</a></tt>
+website. Using these options will fully override the default parameters the
+module would normally use.
+<P>
+By using the <b>-v</b> verbose flag, the user can see exactly what projection
+parameters will be used in the conversion as well as some other informative
+messages.
+<P>
+If output is to lat/long, it will be formatted using <tt>PROJ.4</tt>'s
+Degree:Minute:Second (DMS) convention of <tt>DDDdMM'SSS.SS"H</tt>. This can be handy
+if you wish to quickly convert lat/long decimal degree data into its DMS
+equivalent.<BR>
+Alternatively, to have <em>m.proj</em> output data in decimal degrees, use the
+<b>-d</b> flag. This flag can also be used with non-lat/long data to force a
+higher number of decimal places (the <em>cs2cs</em> default is 2).
+<P>
+Lat/long output can be converted to GRASS's DMS convention (<tt>DDD:MM:SSS.SSSH</tt>)
+by piping the results of <em>m.proj</em> through the <em>sed</em> stream
+editor as follows.
+<div class="code"><pre>
+m.proj -o | sed -e 's/d/:/g' -e "s/'/:/g" -e 's/"//g'
+</pre></div>
+<P>
+The <em>m.proj</em> module is designed to work seamlessly with point data
+exported from the GIS with <em>v.out.ascii</em>, as the following example
+shows.
+<div class="code"><pre>
+v.out.ascii bugsites | m.proj -o
+</pre></div>
+
+
+<H2>EXAMPLES</H2>
+
+To convert a WGS84 long/lat coordinate to the current map projection using
+the <b>-i</b> flag to set projection parameters automaticlly:
+<div class="code"><pre>
+GRASS> echo "170.510125 -45.868537" | m.proj -i
+2316541.70 5479193.51 1.23
+</pre></div>
+
+<P><BR>
+The same, but load points from a file named "<tt>waypoints.txt</tt>" and
+continue on to import the results into a GRASS vector points map in the
+current map projection:
+<div class="code"><pre>
+m.proj -i in=waypoints.txt | cut -f1 -d' ' | v.in.ascii out=test_pt fs=tab
+</pre></div>
+Here the standard UNIX <em>cut</em> tool is used to discard the <tt>z</tt>
+residual.
+
+<P><BR>
+To convert all coordinates from a vector points map in the current projection
+to WGS84 long/lat, with output in decimal form:
+<div class="code"><pre>
+v.out.ascii bugsites | m.proj -od
+</pre></div>
+
+<P><BR>
+To transform points from a UTM projection into the Gauss-Krüger Grid
+System, importing and exporting to files:
+
+<div class="code"><pre>
+m.proj <b>proj_in</b>="+proj=utm +name=utm +a=6378137.0 +es=0.006694380 \
+ +zone=32 +unfact=1.0" <b>proj_out</b>="+proj=tmerc +name=tmerc \
+ +a=6377397.155 +es=0.0066743720 +lat_0=0.0 +lon_0=9.0 +k=1.0 \
+ +x_0=3500000.0" <b>input</b>=utm.coord.txt <b>output</b>=new.gk.coord.txt
+</pre></div>
+
+<P>
+Projection parameters provided in the above case: "<tt>+proj</tt>" (projection
+type), "<tt>+name</tt>" (projection name), "<tt>+a</tt>" (ellipsoid: equatorial
+radius), "<tt>+es</tt>" (ellipsoid: eccentricity squared), "<tt>+zone</tt>"
+(zone for the area), "<tt>+unfact</tt>" (conversion factor from meters to other
+units, e.g. feet), "<tt>+lat_0</tt>" (standard parallel), "<tt>+lon_0</tt>"
+(central meridian), "<tt>+k</tt>" (scale factor) and "<tt>+x_0</tt>" (false
+easting). Sometimes false northing is needed which is coded as "<tt>+y_0</tt>".
+Internally, the underlying
+<a href="http://www.remotesensing.org/proj/"><tt>PROJ.4</tt> projection library</a>
+performs an inverse projection to latitude-longitude and then projects the
+coordinate list to the target projection.
+<P><BR>
+<!-- HB 4/2006: I'm leaving this in from the GRASS 5 help page, but is it accurate? -->
+Datum conversions are automatically handled by the <tt>PROJ.4</tt> library if
+"<tt>+datum</tt>" setings are specified on <b>both</b> the input <b>and</b> output
+projections on the command line. The "<tt>+towgs84</tt>" parameter can be used to
+define either 3 or 7 term datum transform coefficients, satisfying this requirement.
+<P>
+If a datum is specified there is no need for the '<tt>+ellps=</tt>' or underlying
+parameters, '<tt>+a=</tt>', '<tt>+es=</tt>', etc.
+<p>
+<h4>Another custom parameter usage example:</h4>
+
+<div class="code"><pre>
+m.proj <B>proj_in</B>="+proj=tmerc +datum=ire65 +lat_0=53.5 +lon_0=-8 +x_0=200000 \
+ +y_0=250000 +k=1.000035" <B>proj_out</B>="+proj=ll +datum=wgs84" <B>input</B>=wpt.txt
+</pre></div>
+
+or without datum transformation:
+
+<div class="code"><pre>
+m.proj <B>proj_in</B>="+proj=tmerc +ellps=modif_airy +lat_0=53.5 +lon_0=-8 +x_0=200000 \
+ +y_0=250000 +k=1.000035" <B>proj_out</B>="+proj=ll +datum=wgs84" <B>input</B>=wpt.txt
+</pre></div>
+
+<P>
+In this example no datum transformation will take place as a datum was not
+specified for the input projection. The datum specified for the output
+projection will thus be silently ignored and may be left out; all that is
+achieved a simple conversion from projected to geodetic co-ordinates,
+keeping the same datum (and thus also the same ellipsoid).</p>
+
+<p>
+For more usage examples, see the documentation for the
+<tt><a href="http://proj.maptools.org">PROJ.4</a></tt> <em>cs2cs</em> program.
+
+
+<H2>REFERENCES</H2>
+
+[1] Evenden, G.I. (1990) <a href="http://proj.maptools.org/">Cartographic projection procedures for
+the UNIX environment - a user's manual.</a> USGS Open-File Report 90-284 (OF90-284.pdf)
+See also there: Interim Report and 2nd Interim Report on Release 4, Evenden 1994).
+<P>
+[2] <tt><a href="http://proj.maptools.org">PROJ.4</a></tt> Cartographic Projection Library
+
+
+<H2>SEE ALSO</H2>
+
+<EM>
+<A HREF="v.proj.html">v.proj</A>,
+<A HREF="r.proj.html">r.proj</A>,
+<A HREF="g.proj.html">g.proj</A>,
+<A HREF="g.setproj.html">g.setproj</A>,
+<A HREF="i.rectify.html">i.rectify</A>,
+<!-- <A HREF="i.rectify3.html">i.rectify3</A> -->
+<A HREF="v.in.ascii.html">v.in.ascii</A>,
+<A HREF="v.out.ascii.html">v.out.ascii</A>
+</EM>
+
+
+<H2>AUTHOR</H2>
+
+M. Hamish Bowman, Dept. Marine Science, Otago University, New Zealand<BR>
+Functionality inspired by the <em>m.proj</em> and <em>m.proj2</em> modules for
+GRASS GIS 5.
+
+<p><i>Last changed: $Date$</i></p>
+
Deleted: grass/trunk/scripts/r.blend/description.html
===================================================================
--- grass/trunk/scripts/r.blend/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/scripts/r.blend/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,21 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-<EM>r.blend</EM> blends color components of 2 raster maps by a
-specificed percentage of the first map.
-
-<H2>SEE ALSO</H2>
-
-<EM>
-<A HREF="g.region.html">g.region</A>,
-<A HREF="r.mapcalc.html">r.mapcalc</A>,
-<A HREF="r.color.html">r.color</A>,
-<A HREF="r.support.html">r.support</A>,
-</EM>
-
-<H2>AUTHOR</H2>
-
-Unknown: probably CERL<br>
-Updated to GRASS 5.7 by Michael Barton, Arizona State University
-
-<p>
-<i>Last changed: $Date$</i>
Copied: grass/trunk/scripts/r.blend/r.blend.html (from rev 32770, grass/trunk/scripts/r.blend/description.html)
===================================================================
--- grass/trunk/scripts/r.blend/r.blend.html (rev 0)
+++ grass/trunk/scripts/r.blend/r.blend.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,21 @@
+<H2>DESCRIPTION</H2>
+
+<EM>r.blend</EM> blends color components of 2 raster maps by a
+specificed percentage of the first map.
+
+<H2>SEE ALSO</H2>
+
+<EM>
+<A HREF="g.region.html">g.region</A>,
+<A HREF="r.mapcalc.html">r.mapcalc</A>,
+<A HREF="r.color.html">r.color</A>,
+<A HREF="r.support.html">r.support</A>,
+</EM>
+
+<H2>AUTHOR</H2>
+
+Unknown: probably CERL<br>
+Updated to GRASS 5.7 by Michael Barton, Arizona State University
+
+<p>
+<i>Last changed: $Date$</i>
Deleted: grass/trunk/scripts/r.fillnulls/description.html
===================================================================
--- grass/trunk/scripts/r.fillnulls/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/scripts/r.fillnulls/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,80 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-
-<EM><b>r.fillnulls</b></EM> - Fills NULL (no data areas) in input map and
-stores filled map to a new output map. The fill data are interpolated
-from the no data area boundaries buffer using <EM>v.surf.rst</EM>
-spline interpolation.<br>
-
-<EM>(GRASS Shell Script)</EM>
-
-<H2>NOTES</H2>
-
-Each area boundary buffer is set to three times the map resolution to get nominally
-three points around the edge. This way the algorithm interpolates into the hole with
-a trained slope and curvature at the edges, in order to avoid that such a flat plane
-is generated in a hole.
-<P>
-During the interpolation following warning may occur:<p>
-
-<tt>
-Warning: strip exists with insufficient data<br>
-Warning: taking too long to find points for interpolation--please change
-the region to area where your points are</tt>
-<p>
-
-This warning is generated if large data holes exist within the surface.
-As the idea of <em>r.fillnulls</em> is to fill such holes, the user may
-ignore the warning. The interpolation will be continued. However, the user
-may pay attention to below notes.
-
-<H2>ATTENTION</H2>
-
-The algorithm is based on <EM><A HREF="v.surf.rst.html">v.surf.rst</A></EM>
-regularized splines with tension interpolation module which interpolates the
-raster cell values for NULL data areas from the boundary values of the NULL
-data area. An eventual raster MASK is respected during the NULL data area(s)
-filling. The interpolated values are patched into the NULL data area(s) of
-the input map and saved into a new raster map.
-
-<H2>WARNING</H2>
-
-Depending on the shape of the NULL data area(s) problems may occur due to an
-insufficient number of input cell values for the interpolation process. Most
-problems will occur if a NULL data area reaches a large amount of the map
-boundary. The user will have to carefully check the result using
-<EM><a href="r.mapcalc.html">r.mapcalc</A></EM> (generating a difference map to the
-input map) and/or <EM><A HREF="d.what.rast.html">d.what.rast</A></EM> to
-query individual cell values.<p>
-
-<H2>SEE ALSO</H2>
-
-<EM><A HREF="r.fill.dir.html">r.fill.dir</A>,
-<A HREF="v.surf.rst.html">v.surf.rst</A></EM>
-
-<P> Mitas, L., Mitasova, H., 1999, Spatial Interpolation. In: P.Longley,
-M.F. Goodchild, D.J. Maguire, D.W.Rhind (Eds.), Geographical Information
-Systems: Principles, Techniques, Management and Applications, Wiley,
-pp.481-492
-
-<p>Mitasova H., Mitas L., Brown W.M., D.P. Gerdes, I.
-Kosinovsky, Baker, T.1995, Modeling spatially and temporally distributed
-phenomena: New methods and tools for GRASS GIS. <i>International Journal of
-GIS</i>, 9 (4), special issue on Integrating GIS and Environmental modeling,
-433-446.
-
-<p><a href="http://skagit.meas.ncsu.edu/~helena/gmslab/papers/lmg.rev1.ps">Mitasova H.
-and Mitas L. 1993</a>: Interpolation by Regularized Spline with Tension: I.
-Theory and Implementation, <i>Mathematical Geology</i> 25, 641-655.
-
-<p><a href="http://skagit.meas.ncsu.edu/~helena/gmslab/papers/hmg.rev1.ps">Mitasova H.
-and Hofierka L. 1993</a>: Interpolation by Regularized Spline with Tension:
-II. Application to Terrain Modeling and Surface Geometry Analysis,
-<i>Mathematical Geology</i> 25, 657-667.
-
-<H2>AUTHORS</H2>
-r.fillnulls: Markus Neteler, University of Hannover<p>
-and authors of v.surf.rst<br>
-Improvement by Hamish Bowman, NZ
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/scripts/r.fillnulls/r.fillnulls.html (from rev 32770, grass/trunk/scripts/r.fillnulls/description.html)
===================================================================
--- grass/trunk/scripts/r.fillnulls/r.fillnulls.html (rev 0)
+++ grass/trunk/scripts/r.fillnulls/r.fillnulls.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,80 @@
+<H2>DESCRIPTION</H2>
+
+
+<EM><b>r.fillnulls</b></EM> - Fills NULL (no data areas) in input map and
+stores filled map to a new output map. The fill data are interpolated
+from the no data area boundaries buffer using <EM>v.surf.rst</EM>
+spline interpolation.<br>
+
+<EM>(GRASS Shell Script)</EM>
+
+<H2>NOTES</H2>
+
+Each area boundary buffer is set to three times the map resolution to get nominally
+three points around the edge. This way the algorithm interpolates into the hole with
+a trained slope and curvature at the edges, in order to avoid that such a flat plane
+is generated in a hole.
+<P>
+During the interpolation following warning may occur:<p>
+
+<tt>
+Warning: strip exists with insufficient data<br>
+Warning: taking too long to find points for interpolation--please change
+the region to area where your points are</tt>
+<p>
+
+This warning is generated if large data holes exist within the surface.
+As the idea of <em>r.fillnulls</em> is to fill such holes, the user may
+ignore the warning. The interpolation will be continued. However, the user
+may pay attention to below notes.
+
+<H2>ATTENTION</H2>
+
+The algorithm is based on <EM><A HREF="v.surf.rst.html">v.surf.rst</A></EM>
+regularized splines with tension interpolation module which interpolates the
+raster cell values for NULL data areas from the boundary values of the NULL
+data area. An eventual raster MASK is respected during the NULL data area(s)
+filling. The interpolated values are patched into the NULL data area(s) of
+the input map and saved into a new raster map.
+
+<H2>WARNING</H2>
+
+Depending on the shape of the NULL data area(s) problems may occur due to an
+insufficient number of input cell values for the interpolation process. Most
+problems will occur if a NULL data area reaches a large amount of the map
+boundary. The user will have to carefully check the result using
+<EM><a href="r.mapcalc.html">r.mapcalc</A></EM> (generating a difference map to the
+input map) and/or <EM><A HREF="d.what.rast.html">d.what.rast</A></EM> to
+query individual cell values.<p>
+
+<H2>SEE ALSO</H2>
+
+<EM><A HREF="r.fill.dir.html">r.fill.dir</A>,
+<A HREF="v.surf.rst.html">v.surf.rst</A></EM>
+
+<P> Mitas, L., Mitasova, H., 1999, Spatial Interpolation. In: P.Longley,
+M.F. Goodchild, D.J. Maguire, D.W.Rhind (Eds.), Geographical Information
+Systems: Principles, Techniques, Management and Applications, Wiley,
+pp.481-492
+
+<p>Mitasova H., Mitas L., Brown W.M., D.P. Gerdes, I.
+Kosinovsky, Baker, T.1995, Modeling spatially and temporally distributed
+phenomena: New methods and tools for GRASS GIS. <i>International Journal of
+GIS</i>, 9 (4), special issue on Integrating GIS and Environmental modeling,
+433-446.
+
+<p><a href="http://skagit.meas.ncsu.edu/~helena/gmslab/papers/lmg.rev1.ps">Mitasova H.
+and Mitas L. 1993</a>: Interpolation by Regularized Spline with Tension: I.
+Theory and Implementation, <i>Mathematical Geology</i> 25, 641-655.
+
+<p><a href="http://skagit.meas.ncsu.edu/~helena/gmslab/papers/hmg.rev1.ps">Mitasova H.
+and Hofierka L. 1993</a>: Interpolation by Regularized Spline with Tension:
+II. Application to Terrain Modeling and Surface Geometry Analysis,
+<i>Mathematical Geology</i> 25, 657-667.
+
+<H2>AUTHORS</H2>
+r.fillnulls: Markus Neteler, University of Hannover<p>
+and authors of v.surf.rst<br>
+Improvement by Hamish Bowman, NZ
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/scripts/r.in.aster/description.html
===================================================================
--- grass/trunk/scripts/r.in.aster/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/scripts/r.in.aster/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,22 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-<em>r.in.aster</em> rectifies, georeferences, and imports Terra-ASTER imagery
-to current location using gdalwarp, hdf 4, and r.in.gdal, using projection parameters
-from g.proj. It can import Level 1A, Level 1B, and relative DEM products.
-<p>The program may be run interactively or non-interactively from the command
- line. In either case, the user must specify an <b>input</b> *.hdf file name,
- the <b>type</b> of processing used, the image <b>band</b> to import, and an
- <b>output</b> GRASS raster map name. </p>
-<p>The <b>type</b> paremeter can take values of L1A, L1B, or DEM. </p>
-<p>The <B>band</B> parameter can take values of 1, 2, 3n, 3b, 4-14</p>
-
-
-<h2>NOTES</h2>
-
-<em>r.in.aster</em> requires gdal to be in the user's path and the hdf 4 to be installed. Gdal must be compiled with hdf support.
-
-<h2>AUTHORS</h2>
-
-Michael Barton, Arizona State University and Paul Kelly
-<p><i>Last changed: $Date: 2004/12/20</i>
-
Copied: grass/trunk/scripts/r.in.aster/r.in.aster.html (from rev 32770, grass/trunk/scripts/r.in.aster/description.html)
===================================================================
--- grass/trunk/scripts/r.in.aster/r.in.aster.html (rev 0)
+++ grass/trunk/scripts/r.in.aster/r.in.aster.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,22 @@
+<H2>DESCRIPTION</H2>
+
+<em>r.in.aster</em> rectifies, georeferences, and imports Terra-ASTER imagery
+to current location using gdalwarp, hdf 4, and r.in.gdal, using projection parameters
+from g.proj. It can import Level 1A, Level 1B, and relative DEM products.
+<p>The program may be run interactively or non-interactively from the command
+ line. In either case, the user must specify an <b>input</b> *.hdf file name,
+ the <b>type</b> of processing used, the image <b>band</b> to import, and an
+ <b>output</b> GRASS raster map name. </p>
+<p>The <b>type</b> paremeter can take values of L1A, L1B, or DEM. </p>
+<p>The <B>band</B> parameter can take values of 1, 2, 3n, 3b, 4-14</p>
+
+
+<h2>NOTES</h2>
+
+<em>r.in.aster</em> requires gdal to be in the user's path and the hdf 4 to be installed. Gdal must be compiled with hdf support.
+
+<h2>AUTHORS</h2>
+
+Michael Barton, Arizona State University and Paul Kelly
+<p><i>Last changed: $Date: 2004/12/20</i>
+
Deleted: grass/trunk/scripts/r.in.srtm/description.html
===================================================================
--- grass/trunk/scripts/r.in.srtm/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/scripts/r.in.srtm/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,43 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-<EM>r.in.srtm</EM> imports SRTM hgt files into GRASS.
-
-SRTM data sets can be downloaded from NASA at this FTP site (Version 1 and the
-improved Version 2):<br>
-<a href="ftp://e0srp01u.ecs.nasa.gov/srtm/">ftp://e0srp01u.ecs.nasa.gov/srtm/</a>
-
-<H2>NOTES</H2>
-
-SRTM tiles are of 1 degree by 1 degree size. The SRTM filename contains the
-coordinates which refer to the <b>center</b> of the lower left pixel (e.g., N51E010:
-lower left cell center at 10E, 51N). To itentify a tile name, a grid can be easily
-visualized in the GRASS monitor:
-
-<div class="code"><pre>
-d.grid size=1
-</pre></div>
-
-To import TOPEX/SRTM30 PLUS data, use <em>r.in.bin</em>.
-
-<H2>SEE ALSO</H2>
-
-<EM>
-<a href="r.in.bin.html">r.in.bin</A>
-</EM>
-<p>
-The <a href="http://www2.jpl.nasa.gov/srtm/">Shuttle Radar Topography Mission</a>
-homepage at NASA's JPL.
-<br>
-The <a href="http://pub7.bravenet.com/forum/537683448/">SRTM Web Forum</a>
-
-<H2>REFERENCES</H2>
-
-M. Neteler, 2005. <a href="http://grass.itc.it/newsletter/GRASSNews_vol3.pdf">SRTM and VMAP0 data in OGR and GRASS.</a> <i><a href="http://grass.itc.it/newsletter/">GRASS Newsletter</a></i>, Vol.3, pp. 2-6, June 2005. ISSN 1614-8746.
-
-
-<H2>AUTHORS</H2>
-
-Markus Neteler<br>
-Improved by W. Kyngesburye and H. Bowman
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/scripts/r.in.srtm/r.in.srtm.html (from rev 32770, grass/trunk/scripts/r.in.srtm/description.html)
===================================================================
--- grass/trunk/scripts/r.in.srtm/r.in.srtm.html (rev 0)
+++ grass/trunk/scripts/r.in.srtm/r.in.srtm.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,43 @@
+<H2>DESCRIPTION</H2>
+
+<EM>r.in.srtm</EM> imports SRTM hgt files into GRASS.
+
+SRTM data sets can be downloaded from NASA at this FTP site (Version 1 and the
+improved Version 2):<br>
+<a href="ftp://e0srp01u.ecs.nasa.gov/srtm/">ftp://e0srp01u.ecs.nasa.gov/srtm/</a>
+
+<H2>NOTES</H2>
+
+SRTM tiles are of 1 degree by 1 degree size. The SRTM filename contains the
+coordinates which refer to the <b>center</b> of the lower left pixel (e.g., N51E010:
+lower left cell center at 10E, 51N). To itentify a tile name, a grid can be easily
+visualized in the GRASS monitor:
+
+<div class="code"><pre>
+d.grid size=1
+</pre></div>
+
+To import TOPEX/SRTM30 PLUS data, use <em>r.in.bin</em>.
+
+<H2>SEE ALSO</H2>
+
+<EM>
+<a href="r.in.bin.html">r.in.bin</A>
+</EM>
+<p>
+The <a href="http://www2.jpl.nasa.gov/srtm/">Shuttle Radar Topography Mission</a>
+homepage at NASA's JPL.
+<br>
+The <a href="http://pub7.bravenet.com/forum/537683448/">SRTM Web Forum</a>
+
+<H2>REFERENCES</H2>
+
+M. Neteler, 2005. <a href="http://grass.itc.it/newsletter/GRASSNews_vol3.pdf">SRTM and VMAP0 data in OGR and GRASS.</a> <i><a href="http://grass.itc.it/newsletter/">GRASS Newsletter</a></i>, Vol.3, pp. 2-6, June 2005. ISSN 1614-8746.
+
+
+<H2>AUTHORS</H2>
+
+Markus Neteler<br>
+Improved by W. Kyngesburye and H. Bowman
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/scripts/r.in.wms/description.html
===================================================================
--- grass/trunk/scripts/r.in.wms/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/scripts/r.in.wms/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,147 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-<EM>r.in.wms</EM> handles all of downloading and importing raster data from
-an <a href="http://www.opengeospatial.org/specs/?page=specs">OpenGIS</a>
-"WMS" web mapping server. It need only be told the desired data to collect
-(bounds and resolution) via a region, the server to get the data from, and
-the layer or layers to get. It downloads the data in tiles, reprojects it,
-imports it, and patches it back together.
-
-<H2>NOTES</H2>
-
-By default data is downloaded to $GISDBASE/wms_download. This can be changed
-by setting the <EM>folder=</EM> option when using <EM>r.in.wms</EM>.
-<P>
-To understand the data you are getting it is necessary to look at the
-capabilities of the WMS server. This should be available via a capabilities
-request. This is an
-<a href="http://wms.jpl.nasa.gov/wms.cgi?request=GetCapabilities">example
-capabilities request to NASA's OnEarth server</a>.
-<P>
-Some brain-dead servers will only talk to certain web browsers. You can
-fool these by adding "<tt>--user-agent=MSIE5.5</tt>" to <b>wgetoptions</b>
-or for curl adding "<tt>-A "MSIE5.5</tt>" to <b>curloptions</b>.
-Other brain-dead servers will not accept queries in the form of POST data.
-If you get an error try using the <b>-g</b> flag to force <em>r.in.wms</em>
-to send an atomic GET request instead.
-
-
-<H2>EXAMPLES</H2>
-
-<H3>General Get Capabilities Request</H3>
-
-A capabilities request like
-<a href="http://wms.jpl.nasa.gov/wms.cgi?request=GetCapabilities">http://wms.jpl.nasa.gov/wms.cgi?request=GetCapabilities</a>
-is where you should start. It tells you what data is offered, the projections
-it is in, where to find meta data, resolutions, scales, and bounds for
-data, etc.
-
-<H3>NASA OnEarth server: Get Capabilities Request</H3>
-
-<div class="code"><pre>
-r.in.wms mapserver=http://wms.jpl.nasa.gov/wms.cgi -l
-</pre></div>
-
-Lists the layers available from the NASA OnEarth server. The output is
-more reliable if <a href="http://ofb.net/~egnor/xml2/">xml2</a> is installed.
-
-
-<H3>US NED Elevation from OnEarth server download (metric units)</H3>
-
-Set the resolution to 30 (assuming you're in metric units):
-<div class="code"><pre>
-g.region res=30 -ap
-r.in.wms output=elevation_meters mapserver=http://wms.jpl.nasa.gov/wms.cgi \
- layers=us_ned styles=real -o
-</pre></div>
-
-Downloads real number meter elevation from OnEarth to cover the current
-region. Uses -o for opaque to get smaller download.
-
-<H3>US NED Elevation from OnEarth server download (feet units)</H3>
-
-Set the resolution to 90 (assuming you're in feet units) a save this
-region with a name; this makes resuming downloads possible or rather
-easier:
-
-<div class="code"><pre>
-g.region res=90 -ap
-g.region save=panhandle-90ft
-
-r.in.wms output=elevation_feet mapserver=http://wms.jpl.nasa.gov/wms.cgi \
- layers=us_ned styles=feet_real -o region=panhandle-90ft
-</pre></div>
-
-Downloads real number feet elevation from OnEarth to cover the current
-region. Uses <B>-o</B> for opaque to get smaller download. Using a named
-region lets us resume later easily.
-
-<div class="code"><pre>
-r.in.wms output=elevation_feet mapserver=http://wms.jpl.nasa.gov/wms.cgi \
- layers=us_ned styles=feet_real -o region=panhandle-90ft -d method=cubic
-</pre></div>
-
-<dd><b>-d</b> skips ahead to downloading. This could be used to try
-downloading again (if some files failed last time) or to import the data
-differently. Since downloaded files are remembered those already received
-successfully are not re-requested. In this case we are reimporting the
-data using the cubic interpolation method instead of nearest neighbor.
-</dd>
-
-<H3>LANDSAT from OnEarth server download</H3>
-
-Set the resolution to 30 meters for LANDSAT:
-<div class="code"><pre>
-g.region res=30 -ap
-r.in.wms layers=global_mosaic mapserver=http://wms.jpl.nasa.gov/wms.cgi \
- output=wms_global_mosaic
-</pre></div>
-Downloads LANDSAT color scene.
-
-
-<H3>DRG from Terraserver server download</H3>
-
-Set the resolution to 1.2 meters for DRGs. Their native resolution is
-2.4 meters, so this is some pretty hefty oversampling:
-
-<div class="code"><pre>
-g.region res=1.2 -ap
-g.region save=drg-resolution
-
-r.in.wms output=terraserver-drg mapserver=http://terraserver.microsoft.com/ogcmap6.ashx \
- layers=DRG region=drg-resolution format=jpeg srs=EPSG:26910
-</pre></div>
-
-Downloads digital raster graphics from Microsoft TerraServer. Note that
-srs will need to be changed to a projection that is appropriate for your
-region.
-
-
-<H2>REQUIRED PROGRAMS</H2>
-
-<EM>r.in.wms</EM> requires the following programs to work:
-
-<ul>
-<li>wget: An http download program, or
-<li>curl: Alternate http download program
-<li>bc: A calculator program
-<li>sed, grep: Unix string processing and search programs
-<li><a href="http://www.gdal.org">gdalwarp</a>: A reprojection tool,
- needed only if data is projected into this location.
-<li><a href="http://ofb.net/~egnor/xml2/">xml2</a>: An xml parser.
- Enables more accurate listing of layers on the server.
-</ul>
-
-
-<H2>SEE ALSO</H2>
-<a href="r.tileset.html">r.tileset</a>,
-<a href="r.in.gdal.html">r.in.gdal</a>,
-<a href="r.patch.html">r.patch</a>
-
-
-<H2>AUTHORS</H2>
-
-Soeren Gebbert, Jachym Cepicky, and Cedric Shock
-
-<p>
-<i>Last changed: $Date$</i>
Copied: grass/trunk/scripts/r.in.wms/r.in.wms.html (from rev 32770, grass/trunk/scripts/r.in.wms/description.html)
===================================================================
--- grass/trunk/scripts/r.in.wms/r.in.wms.html (rev 0)
+++ grass/trunk/scripts/r.in.wms/r.in.wms.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,147 @@
+<H2>DESCRIPTION</H2>
+
+<EM>r.in.wms</EM> handles all of downloading and importing raster data from
+an <a href="http://www.opengeospatial.org/specs/?page=specs">OpenGIS</a>
+"WMS" web mapping server. It need only be told the desired data to collect
+(bounds and resolution) via a region, the server to get the data from, and
+the layer or layers to get. It downloads the data in tiles, reprojects it,
+imports it, and patches it back together.
+
+<H2>NOTES</H2>
+
+By default data is downloaded to $GISDBASE/wms_download. This can be changed
+by setting the <EM>folder=</EM> option when using <EM>r.in.wms</EM>.
+<P>
+To understand the data you are getting it is necessary to look at the
+capabilities of the WMS server. This should be available via a capabilities
+request. This is an
+<a href="http://wms.jpl.nasa.gov/wms.cgi?request=GetCapabilities">example
+capabilities request to NASA's OnEarth server</a>.
+<P>
+Some brain-dead servers will only talk to certain web browsers. You can
+fool these by adding "<tt>--user-agent=MSIE5.5</tt>" to <b>wgetoptions</b>
+or for curl adding "<tt>-A "MSIE5.5</tt>" to <b>curloptions</b>.
+Other brain-dead servers will not accept queries in the form of POST data.
+If you get an error try using the <b>-g</b> flag to force <em>r.in.wms</em>
+to send an atomic GET request instead.
+
+
+<H2>EXAMPLES</H2>
+
+<H3>General Get Capabilities Request</H3>
+
+A capabilities request like
+<a href="http://wms.jpl.nasa.gov/wms.cgi?request=GetCapabilities">http://wms.jpl.nasa.gov/wms.cgi?request=GetCapabilities</a>
+is where you should start. It tells you what data is offered, the projections
+it is in, where to find meta data, resolutions, scales, and bounds for
+data, etc.
+
+<H3>NASA OnEarth server: Get Capabilities Request</H3>
+
+<div class="code"><pre>
+r.in.wms mapserver=http://wms.jpl.nasa.gov/wms.cgi -l
+</pre></div>
+
+Lists the layers available from the NASA OnEarth server. The output is
+more reliable if <a href="http://ofb.net/~egnor/xml2/">xml2</a> is installed.
+
+
+<H3>US NED Elevation from OnEarth server download (metric units)</H3>
+
+Set the resolution to 30 (assuming you're in metric units):
+<div class="code"><pre>
+g.region res=30 -ap
+r.in.wms output=elevation_meters mapserver=http://wms.jpl.nasa.gov/wms.cgi \
+ layers=us_ned styles=real -o
+</pre></div>
+
+Downloads real number meter elevation from OnEarth to cover the current
+region. Uses -o for opaque to get smaller download.
+
+<H3>US NED Elevation from OnEarth server download (feet units)</H3>
+
+Set the resolution to 90 (assuming you're in feet units) a save this
+region with a name; this makes resuming downloads possible or rather
+easier:
+
+<div class="code"><pre>
+g.region res=90 -ap
+g.region save=panhandle-90ft
+
+r.in.wms output=elevation_feet mapserver=http://wms.jpl.nasa.gov/wms.cgi \
+ layers=us_ned styles=feet_real -o region=panhandle-90ft
+</pre></div>
+
+Downloads real number feet elevation from OnEarth to cover the current
+region. Uses <B>-o</B> for opaque to get smaller download. Using a named
+region lets us resume later easily.
+
+<div class="code"><pre>
+r.in.wms output=elevation_feet mapserver=http://wms.jpl.nasa.gov/wms.cgi \
+ layers=us_ned styles=feet_real -o region=panhandle-90ft -d method=cubic
+</pre></div>
+
+<dd><b>-d</b> skips ahead to downloading. This could be used to try
+downloading again (if some files failed last time) or to import the data
+differently. Since downloaded files are remembered those already received
+successfully are not re-requested. In this case we are reimporting the
+data using the cubic interpolation method instead of nearest neighbor.
+</dd>
+
+<H3>LANDSAT from OnEarth server download</H3>
+
+Set the resolution to 30 meters for LANDSAT:
+<div class="code"><pre>
+g.region res=30 -ap
+r.in.wms layers=global_mosaic mapserver=http://wms.jpl.nasa.gov/wms.cgi \
+ output=wms_global_mosaic
+</pre></div>
+Downloads LANDSAT color scene.
+
+
+<H3>DRG from Terraserver server download</H3>
+
+Set the resolution to 1.2 meters for DRGs. Their native resolution is
+2.4 meters, so this is some pretty hefty oversampling:
+
+<div class="code"><pre>
+g.region res=1.2 -ap
+g.region save=drg-resolution
+
+r.in.wms output=terraserver-drg mapserver=http://terraserver.microsoft.com/ogcmap6.ashx \
+ layers=DRG region=drg-resolution format=jpeg srs=EPSG:26910
+</pre></div>
+
+Downloads digital raster graphics from Microsoft TerraServer. Note that
+srs will need to be changed to a projection that is appropriate for your
+region.
+
+
+<H2>REQUIRED PROGRAMS</H2>
+
+<EM>r.in.wms</EM> requires the following programs to work:
+
+<ul>
+<li>wget: An http download program, or
+<li>curl: Alternate http download program
+<li>bc: A calculator program
+<li>sed, grep: Unix string processing and search programs
+<li><a href="http://www.gdal.org">gdalwarp</a>: A reprojection tool,
+ needed only if data is projected into this location.
+<li><a href="http://ofb.net/~egnor/xml2/">xml2</a>: An xml parser.
+ Enables more accurate listing of layers on the server.
+</ul>
+
+
+<H2>SEE ALSO</H2>
+<a href="r.tileset.html">r.tileset</a>,
+<a href="r.in.gdal.html">r.in.gdal</a>,
+<a href="r.patch.html">r.patch</a>
+
+
+<H2>AUTHORS</H2>
+
+Soeren Gebbert, Jachym Cepicky, and Cedric Shock
+
+<p>
+<i>Last changed: $Date$</i>
Deleted: grass/trunk/scripts/r.mapcalculator/description.html
===================================================================
--- grass/trunk/scripts/r.mapcalculator/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/scripts/r.mapcalculator/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,16 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-
-<EM>r.mapcalculator</EM> Provides a GUI frontend to r.mapcalc. Up to 5 maps can be combined using simple expressions. Expert mode runs r.mapcalc for more complex expressions.
-<br>
-
-<H2>SEE ALSO</H2>
-
-<EM><A HREF="r.mapcalc.html">r.mapcalc</A></EM>,
-
-
-<H2>AUTHOR</H2>
-
-R. Brunzema (r.brunzema at web.de)<BR>
-Updated to GRASS 5.7 by Michael Barton, Arizona State University
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/scripts/r.mapcalculator/r.mapcalculator.html (from rev 32770, grass/trunk/scripts/r.mapcalculator/description.html)
===================================================================
--- grass/trunk/scripts/r.mapcalculator/r.mapcalculator.html (rev 0)
+++ grass/trunk/scripts/r.mapcalculator/r.mapcalculator.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,16 @@
+<H2>DESCRIPTION</H2>
+
+
+<EM>r.mapcalculator</EM> Provides a GUI frontend to r.mapcalc. Up to 5 maps can be combined using simple expressions. Expert mode runs r.mapcalc for more complex expressions.
+<br>
+
+<H2>SEE ALSO</H2>
+
+<EM><A HREF="r.mapcalc.html">r.mapcalc</A></EM>,
+
+
+<H2>AUTHOR</H2>
+
+R. Brunzema (r.brunzema at web.de)<BR>
+Updated to GRASS 5.7 by Michael Barton, Arizona State University
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/scripts/r.mask/description.html
===================================================================
--- grass/trunk/scripts/r.mask/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/scripts/r.mask/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,106 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em><b>r.mask</b></em> - Facilitates creation of a raster "MASK" map to
-control raster operations.
-
-<p>
-The MASK is only applied when <em>reading</em> an existing GRASS raster map,
-for example when used in a module as an input map.
-
-The MASK will block out certain areas of a raster map from analysis and/or display, by
-"hiding" them from sight of other GRASS modules. Data falling within the bounaries of the MASK
-can be modified and operated upon by other GRASS raster modules; data
-falling outside the MASK is treated as if it were NULL.
-<p>
-Because the MASK is actually only a reclass map named "MASK", it can be
-copied, renamed, removed, and used in analyses, just like other GRASS
-raster map layers. The user should be aware that a MASK remains in
-place until a user renames it to something other than "MASK", or removes
-it using "<tt>r.mask -r</tt>" or <em><a HREF="g.remove.html">g.remove</a></em>.
-
-<p>
-Grid cells in the MASK map containing <tt>0</tt> or <tt>NULL</tt>
-will replace data with NULL, while cells containing other values will allow
-data to pass through unaltered.
-
-<p>
-To restore raster operations to normal (i.e., all cells of the current region),
-remove the MASK file by setting the <b>-r</b> remove MASK flag. In this case, a
-dummy value must also be given for the input parameter.
-A MASK also can be removed by using <em><a href="g.remove.html">g.remove</a></em>
-or by renaming it to any other name with <em><a href="g.rename.html">g.rename</a></em>.
-
-
-<h2>NOTES</h2>
-
-The above method for specifying a "mask" may seem
-counterintuitive. Areas inside the MASK are not hidden;
-areas outside the MASK will be ignored until the MASK file
-is removed.
-<p>
-
-The mask is read as an integer map. If MASK is actually a
-floating-point map, the values will be converted to integers using the
-map's quantisation rules (this defaults to round-to-nearest, but can
-be changed with r.quant).
-<p>
-
-<em>r.mask</em> uses <em>r.reclass</em> to create a reclassification of an
-existing raster map and name it MASK. A reclass map takes up less space, but
-is affected by any changes to the underlying map from which it was created. The user
-can select category values from the input raster to use in the MASK with the <em>maskcats</em> parameter;
-if <em>r.mask</em> is run from the command line, the category values listed in <em>maskcats</em>
-must be quoted (see example below).
-<p>
-
-Somewhat similar program functions to those performed by
-<em>r.mask</em> can be done using
-<em><a HREF="r.mapcalc.html">r.mapcalc</a></em>,
-<em><a HREF="g.region.html">g.region</a></em>,
-and other programs.
-
-<p>
-<em>(GRASS Shell Script)</em>
-
-<h2>EXAMPLES</h2>
-Creating a raster mask:
-<div class="code"><pre>
-<b>r.mask input=</b>geology
-MASK created. All subsequent raster operations
-will be limited to MASK area
-Removing or renaming raster file named MASK will
-restore raster operations to normal
-[Raster MASK present]
-</pre></div>
-
-Removing a raster mask with the -r flag:
-<div class="code"><pre>
-<b>r.mask -r input=</b>anything_you_wish
-Removing raster <MASK>
-Raster MASK removed
-</pre></div>
-
-Creating a mask from categories 3 through 6 in the spearfish 'geology' raster map:
-<div class="code"><pre>
-<b>r.mask input=</b>geology <b>maskcats=</b>"3 thru 6"
-MASK created. All subsequent raster operations
-will be limited to MASK area
-Removing or renaming raster file named MASK will
-restore raster operations to normal
-[Raster MASK present]
-
-<h2>SEE ALSO</h2>
-<em>
-<a HREF="g.region.html">g.region</a>,
-<a HREF="r.mapcalc.html">r.mapcalc</a>,
-<a href="r.reclass.html">r.reclass</a>
-<a href="g.remove.html">g.remove</a>
-<a href="g.rename.html">g.rename</a>
-</em>
-
-<h2>AUTHOR</h2>
-
-Michael Barton, Arizona State University
-
-<p>
-<i>Last changed: $Date$</i></p>
Copied: grass/trunk/scripts/r.mask/r.mask.html (from rev 32770, grass/trunk/scripts/r.mask/description.html)
===================================================================
--- grass/trunk/scripts/r.mask/r.mask.html (rev 0)
+++ grass/trunk/scripts/r.mask/r.mask.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,106 @@
+<h2>DESCRIPTION</h2>
+
+<em><b>r.mask</b></em> - Facilitates creation of a raster "MASK" map to
+control raster operations.
+
+<p>
+The MASK is only applied when <em>reading</em> an existing GRASS raster map,
+for example when used in a module as an input map.
+
+The MASK will block out certain areas of a raster map from analysis and/or display, by
+"hiding" them from sight of other GRASS modules. Data falling within the bounaries of the MASK
+can be modified and operated upon by other GRASS raster modules; data
+falling outside the MASK is treated as if it were NULL.
+<p>
+Because the MASK is actually only a reclass map named "MASK", it can be
+copied, renamed, removed, and used in analyses, just like other GRASS
+raster map layers. The user should be aware that a MASK remains in
+place until a user renames it to something other than "MASK", or removes
+it using "<tt>r.mask -r</tt>" or <em><a HREF="g.remove.html">g.remove</a></em>.
+
+<p>
+Grid cells in the MASK map containing <tt>0</tt> or <tt>NULL</tt>
+will replace data with NULL, while cells containing other values will allow
+data to pass through unaltered.
+
+<p>
+To restore raster operations to normal (i.e., all cells of the current region),
+remove the MASK file by setting the <b>-r</b> remove MASK flag. In this case, a
+dummy value must also be given for the input parameter.
+A MASK also can be removed by using <em><a href="g.remove.html">g.remove</a></em>
+or by renaming it to any other name with <em><a href="g.rename.html">g.rename</a></em>.
+
+
+<h2>NOTES</h2>
+
+The above method for specifying a "mask" may seem
+counterintuitive. Areas inside the MASK are not hidden;
+areas outside the MASK will be ignored until the MASK file
+is removed.
+<p>
+
+The mask is read as an integer map. If MASK is actually a
+floating-point map, the values will be converted to integers using the
+map's quantisation rules (this defaults to round-to-nearest, but can
+be changed with r.quant).
+<p>
+
+<em>r.mask</em> uses <em>r.reclass</em> to create a reclassification of an
+existing raster map and name it MASK. A reclass map takes up less space, but
+is affected by any changes to the underlying map from which it was created. The user
+can select category values from the input raster to use in the MASK with the <em>maskcats</em> parameter;
+if <em>r.mask</em> is run from the command line, the category values listed in <em>maskcats</em>
+must be quoted (see example below).
+<p>
+
+Somewhat similar program functions to those performed by
+<em>r.mask</em> can be done using
+<em><a HREF="r.mapcalc.html">r.mapcalc</a></em>,
+<em><a HREF="g.region.html">g.region</a></em>,
+and other programs.
+
+<p>
+<em>(GRASS Shell Script)</em>
+
+<h2>EXAMPLES</h2>
+Creating a raster mask:
+<div class="code"><pre>
+<b>r.mask input=</b>geology
+MASK created. All subsequent raster operations
+will be limited to MASK area
+Removing or renaming raster file named MASK will
+restore raster operations to normal
+[Raster MASK present]
+</pre></div>
+
+Removing a raster mask with the -r flag:
+<div class="code"><pre>
+<b>r.mask -r input=</b>anything_you_wish
+Removing raster <MASK>
+Raster MASK removed
+</pre></div>
+
+Creating a mask from categories 3 through 6 in the spearfish 'geology' raster map:
+<div class="code"><pre>
+<b>r.mask input=</b>geology <b>maskcats=</b>"3 thru 6"
+MASK created. All subsequent raster operations
+will be limited to MASK area
+Removing or renaming raster file named MASK will
+restore raster operations to normal
+[Raster MASK present]
+
+<h2>SEE ALSO</h2>
+<em>
+<a HREF="g.region.html">g.region</a>,
+<a HREF="r.mapcalc.html">r.mapcalc</a>,
+<a href="r.reclass.html">r.reclass</a>
+<a href="g.remove.html">g.remove</a>
+<a href="g.rename.html">g.rename</a>
+</em>
+
+<h2>AUTHOR</h2>
+
+Michael Barton, Arizona State University
+
+<p>
+<i>Last changed: $Date$</i></p>
Deleted: grass/trunk/scripts/r.out.gdal/description.html
===================================================================
--- grass/trunk/scripts/r.out.gdal/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/scripts/r.out.gdal/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,96 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-
-WARNING: <B>This module is superseded and will be removed in future versions of GRASS.
-Use the much faster <em><A HREF="r.out.gdal.html">r.out.gdal</a></em> instead.</b>
-
-<EM>r.out.gdal.sh</EM> outputs GRASS raster maps into various GIS formats
-as supported by GDAL. This script is based on 'gdal_translate',
-it's parameters are similar to those of
-'<a href="http://www.gdal.org/gdal_utilities.html">gdal_translate</a>'.
-It requires the installation of either GDAL with GRASS support or
-of the GDAL-OGR-GRASS plugin which is available from the
-<a href="http://www.gdal.org">GDAL web site</a>.
-<p>
-For possible <em>metaopt</em> parameters see the 'supported formats' pages
-of GDAL.
-The <em>createopt</em> may be used to create TFW or World files ("TFW=YES",
-"WORLDFILE=ON").
-
-<H2>SUPPORTED FORMATS</H2>
-
-The set of <a href="http://www.gdal.org/formats_list.html">supported
-formats</a> written by <EM>r.out.gdal.sh</EM> depend on the
-local GDAL installation. Available may be (incomplete list):<P>
-
-<pre>
- AAIGrid: Arc/Info ASCII Grid
- BMP: MS Windows Device Independent Bitmap
- BSB: Maptech BSB Nautical Charts
- DTED: DTED Elevation Raster
- ELAS: ELAS
- ENVI: ENVI .hdr Labelled
- FIT: FIT Image
- GIF: Graphics Interchange Format (.gif)
- GTiff: GeoTIFF
- HDF4Image: HDF4 Dataset
- HFA: Erdas Imagine Images (.img)
- JPEG2000: JPEG-2000 part 1 (ISO/IEC 15444-1)
- JPEG: JPEG JFIF
- MEM: In Memory Raster
- MFF2: Atlantis MFF2 (HKV) Raster
- MFF: Atlantis MFF Raster
- NITF: National Imagery Transmission Format
- PAux: PCI .aux Labelled
- PCIDSK: PCIDSK Database File
- PNG: Portable Network Graphics
- PNM: Portable Pixmap Format (netpbm)
- VRT: Virtual Raster
- XPM: X11 PixMap Format
-</pre>
-
-<H2>NOTES</H2>
-
-When writing out GeoTIFF format for users of ESRI software or ImageMagick,
-the band interleaving should be switched to pixel interleaving using
-<em>createopt="INTERLEAVE=PIXEL"</em>. Multiple options have to be
-specified as comma separated list (<em>createopt=TFW=YES,COMPRESS=DEFLATE</em>).
-<p>
-Out of the GDAL data types, the closest match for GRASS CELL, FCELL and DCELL
-rasters are respectively Int32, Float32 and Float64. These are not exact
-equivalents, but they will preserve the max possible data range and number of
-decimal places for each respective GRASS raster data type. Please keep in mind, that
-not all CELL rasters will require Int32 - e.g., 0-255 CELL raster are covered
-by the Byte <em>type</em> as well. Moreover, some GDAL-supported formats do not
-support all the data types possible in GDAL and GRASS. Use
-<em><a href="r.info">r.info</a></em> to check the data type and range for your
-GRASS raster, refer to specific format documentation
-(<a href="http://www.gdal.org/">GDAL website</a>, format vendor's docs) and
-e.g. the Wikipedia article
-<em><a href="http://en.wikipedia.org/wiki/C_syntax#Typical_boundaries_of_primitive_integral_types">Typical boundaries of primitive integral types</a></em>
-for details.
-
-<H2>EXAMPLE</H2>
-
-Export of the map 'elevation.dem' from the Spearfish data set:
-
-<div class="code"><pre>
-r.out.gdal.sh elevation.dem format=GTiff type=Int16 output=elev_dem.tif
-</pre></div>
-
-<H2>REFERENCES</H2>
-
-<a href="http://www.gdal.org/">GDAL library</a>
-<p>
-<a href="http://grass.gdf-hannover.de/wiki/Compile_and_install_GRASS_and_QGIS_with_GDAL/OGR_Plugin">Compile and install GRASS and QGIS with GDAL/OGR Plugin</a>
-
-<H2>SEE ALSO</H2>
-
-<EM><A HREF="r.out.arc.html">r.out.arc</A></EM>,
-<EM><A HREF="r.out.ascii.html">r.out.ascii</A></EM>,
-<EM><A HREF="r.out.tiff.html">r.out.tiff</A></EM>
-
-<H2>AUTHOR</H2>
-
-Markus Neteler, ITC-irst, Italy
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/scripts/r.out.gdal/r.out.gdal.sh.html (from rev 32770, grass/trunk/scripts/r.out.gdal/description.html)
===================================================================
--- grass/trunk/scripts/r.out.gdal/r.out.gdal.sh.html (rev 0)
+++ grass/trunk/scripts/r.out.gdal/r.out.gdal.sh.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,96 @@
+<H2>DESCRIPTION</H2>
+
+
+WARNING: <B>This module is superseded and will be removed in future versions of GRASS.
+Use the much faster <em><A HREF="r.out.gdal.html">r.out.gdal</a></em> instead.</b>
+
+<EM>r.out.gdal.sh</EM> outputs GRASS raster maps into various GIS formats
+as supported by GDAL. This script is based on 'gdal_translate',
+it's parameters are similar to those of
+'<a href="http://www.gdal.org/gdal_utilities.html">gdal_translate</a>'.
+It requires the installation of either GDAL with GRASS support or
+of the GDAL-OGR-GRASS plugin which is available from the
+<a href="http://www.gdal.org">GDAL web site</a>.
+<p>
+For possible <em>metaopt</em> parameters see the 'supported formats' pages
+of GDAL.
+The <em>createopt</em> may be used to create TFW or World files ("TFW=YES",
+"WORLDFILE=ON").
+
+<H2>SUPPORTED FORMATS</H2>
+
+The set of <a href="http://www.gdal.org/formats_list.html">supported
+formats</a> written by <EM>r.out.gdal.sh</EM> depend on the
+local GDAL installation. Available may be (incomplete list):<P>
+
+<pre>
+ AAIGrid: Arc/Info ASCII Grid
+ BMP: MS Windows Device Independent Bitmap
+ BSB: Maptech BSB Nautical Charts
+ DTED: DTED Elevation Raster
+ ELAS: ELAS
+ ENVI: ENVI .hdr Labelled
+ FIT: FIT Image
+ GIF: Graphics Interchange Format (.gif)
+ GTiff: GeoTIFF
+ HDF4Image: HDF4 Dataset
+ HFA: Erdas Imagine Images (.img)
+ JPEG2000: JPEG-2000 part 1 (ISO/IEC 15444-1)
+ JPEG: JPEG JFIF
+ MEM: In Memory Raster
+ MFF2: Atlantis MFF2 (HKV) Raster
+ MFF: Atlantis MFF Raster
+ NITF: National Imagery Transmission Format
+ PAux: PCI .aux Labelled
+ PCIDSK: PCIDSK Database File
+ PNG: Portable Network Graphics
+ PNM: Portable Pixmap Format (netpbm)
+ VRT: Virtual Raster
+ XPM: X11 PixMap Format
+</pre>
+
+<H2>NOTES</H2>
+
+When writing out GeoTIFF format for users of ESRI software or ImageMagick,
+the band interleaving should be switched to pixel interleaving using
+<em>createopt="INTERLEAVE=PIXEL"</em>. Multiple options have to be
+specified as comma separated list (<em>createopt=TFW=YES,COMPRESS=DEFLATE</em>).
+<p>
+Out of the GDAL data types, the closest match for GRASS CELL, FCELL and DCELL
+rasters are respectively Int32, Float32 and Float64. These are not exact
+equivalents, but they will preserve the max possible data range and number of
+decimal places for each respective GRASS raster data type. Please keep in mind, that
+not all CELL rasters will require Int32 - e.g., 0-255 CELL raster are covered
+by the Byte <em>type</em> as well. Moreover, some GDAL-supported formats do not
+support all the data types possible in GDAL and GRASS. Use
+<em><a href="r.info">r.info</a></em> to check the data type and range for your
+GRASS raster, refer to specific format documentation
+(<a href="http://www.gdal.org/">GDAL website</a>, format vendor's docs) and
+e.g. the Wikipedia article
+<em><a href="http://en.wikipedia.org/wiki/C_syntax#Typical_boundaries_of_primitive_integral_types">Typical boundaries of primitive integral types</a></em>
+for details.
+
+<H2>EXAMPLE</H2>
+
+Export of the map 'elevation.dem' from the Spearfish data set:
+
+<div class="code"><pre>
+r.out.gdal.sh elevation.dem format=GTiff type=Int16 output=elev_dem.tif
+</pre></div>
+
+<H2>REFERENCES</H2>
+
+<a href="http://www.gdal.org/">GDAL library</a>
+<p>
+<a href="http://grass.gdf-hannover.de/wiki/Compile_and_install_GRASS_and_QGIS_with_GDAL/OGR_Plugin">Compile and install GRASS and QGIS with GDAL/OGR Plugin</a>
+
+<H2>SEE ALSO</H2>
+
+<EM><A HREF="r.out.arc.html">r.out.arc</A></EM>,
+<EM><A HREF="r.out.ascii.html">r.out.ascii</A></EM>,
+<EM><A HREF="r.out.tiff.html">r.out.tiff</A></EM>
+
+<H2>AUTHOR</H2>
+
+Markus Neteler, ITC-irst, Italy
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/scripts/r.out.xyz/description.html
===================================================================
--- grass/trunk/scripts/r.out.xyz/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/scripts/r.out.xyz/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,42 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-The <EM>r.out.xyz</EM> module will export a raster map as a list of x,y,z
-values into an ASCII text file.
-<P>
-<EM>(GRASS Shell Script)</EM>
-
-<H2>NOTES</H2>
-
-This module will not export x,y coordinates for raster cells containing
-a NULL value. This includes cells masked by a raster MASK.
-<P>
-This module, as all GRASS raster modules, will export cells based on the
-current region settings. See the <EM>g.region</EM> module for details.
-<P>
-The <EM>r.out.ascii</EM> module should be used to export an array (of
-size row x column) containing z values.
-<P>
-<EM>r.out.xyz</EM> is simply a front-end to "<tt>r.stats -1gn</tt>".
-
-<H2>TODO</H2>
-
-Implement this script as a <EM>r.out.ascii</EM> option?
-
-
-<H2>SEE ALSO</H2>
-
-<EM>
-<A HREF="g.region.html">g.region</A>,
-<A HREF="r.mask">r.mask</A>
-<A HREF="r.out.ascii.html">r.out.ascii</A>,
-<A HREF="r.stats">r.stats</A>
-</EM>
-
-<H2>AUTHOR</H2>
-
-M. Hamish Bowman<BR>
-<i>Dept. Marine Science<BR>
-Otago University, New Zealand</i>
-
-<P>
-<i>Last changed: $Date$</i>
Copied: grass/trunk/scripts/r.out.xyz/r.out.xyz.html (from rev 32770, grass/trunk/scripts/r.out.xyz/description.html)
===================================================================
--- grass/trunk/scripts/r.out.xyz/r.out.xyz.html (rev 0)
+++ grass/trunk/scripts/r.out.xyz/r.out.xyz.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,42 @@
+<H2>DESCRIPTION</H2>
+
+The <EM>r.out.xyz</EM> module will export a raster map as a list of x,y,z
+values into an ASCII text file.
+<P>
+<EM>(GRASS Shell Script)</EM>
+
+<H2>NOTES</H2>
+
+This module will not export x,y coordinates for raster cells containing
+a NULL value. This includes cells masked by a raster MASK.
+<P>
+This module, as all GRASS raster modules, will export cells based on the
+current region settings. See the <EM>g.region</EM> module for details.
+<P>
+The <EM>r.out.ascii</EM> module should be used to export an array (of
+size row x column) containing z values.
+<P>
+<EM>r.out.xyz</EM> is simply a front-end to "<tt>r.stats -1gn</tt>".
+
+<H2>TODO</H2>
+
+Implement this script as a <EM>r.out.ascii</EM> option?
+
+
+<H2>SEE ALSO</H2>
+
+<EM>
+<A HREF="g.region.html">g.region</A>,
+<A HREF="r.mask">r.mask</A>
+<A HREF="r.out.ascii.html">r.out.ascii</A>,
+<A HREF="r.stats">r.stats</A>
+</EM>
+
+<H2>AUTHOR</H2>
+
+M. Hamish Bowman<BR>
+<i>Dept. Marine Science<BR>
+Otago University, New Zealand</i>
+
+<P>
+<i>Last changed: $Date$</i>
Deleted: grass/trunk/scripts/r.plane/description.html
===================================================================
--- grass/trunk/scripts/r.plane/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/scripts/r.plane/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,37 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-
-<EM>r.plane</EM> creates a tilted plane raster map given user-specified
-parameters for inclination, azimuth, and the geographic location of a
-point on the plane.<BR>
-The angle orientations of the <em>azimuth</em> parameter increase counter-clockwise,
-i.e., 0 degree = N, 45 degree = NW, 90 degree = W etc.
-<P>
-Increasing values of the <em>dip</em> parameter progressively lower (or dip) the northern
-half of the plane, and incline the southern half, assuming the <em>azimuth</em> parameter
-is held constant at 0 degrees.
-
-
-<H2>NOTES</H2>
-<tt>g.region -c</tt> provides the easting and northing coordinates for
-the center of the current region.
-<P>
-<em>int</em> maps take less disk space than <em>float</em>s, which in turn
-take up less space than <em>double</em>s (but can be less exact).
-
-
-<H2>EXAMPLE</H2>
-
-A tilted plane in the Spearfish region:
-
-<div class="code"><pre>
-r.plane myplane45 dip=45 az=90 east=599490 north=4920855 \
- elev=1000 type=float
-</pre></div>
-
-
-<H2>AUTHOR</H2>
-
-Unknown<br>
-Updated to GRASS 5.7 by Michael Barton, Arizona State University
-<p><i>Last changed: $Date$</i></p>
Copied: grass/trunk/scripts/r.plane/r.plane.html (from rev 32770, grass/trunk/scripts/r.plane/description.html)
===================================================================
--- grass/trunk/scripts/r.plane/r.plane.html (rev 0)
+++ grass/trunk/scripts/r.plane/r.plane.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,37 @@
+<H2>DESCRIPTION</H2>
+
+
+<EM>r.plane</EM> creates a tilted plane raster map given user-specified
+parameters for inclination, azimuth, and the geographic location of a
+point on the plane.<BR>
+The angle orientations of the <em>azimuth</em> parameter increase counter-clockwise,
+i.e., 0 degree = N, 45 degree = NW, 90 degree = W etc.
+<P>
+Increasing values of the <em>dip</em> parameter progressively lower (or dip) the northern
+half of the plane, and incline the southern half, assuming the <em>azimuth</em> parameter
+is held constant at 0 degrees.
+
+
+<H2>NOTES</H2>
+<tt>g.region -c</tt> provides the easting and northing coordinates for
+the center of the current region.
+<P>
+<em>int</em> maps take less disk space than <em>float</em>s, which in turn
+take up less space than <em>double</em>s (but can be less exact).
+
+
+<H2>EXAMPLE</H2>
+
+A tilted plane in the Spearfish region:
+
+<div class="code"><pre>
+r.plane myplane45 dip=45 az=90 east=599490 north=4920855 \
+ elev=1000 type=float
+</pre></div>
+
+
+<H2>AUTHOR</H2>
+
+Unknown<br>
+Updated to GRASS 5.7 by Michael Barton, Arizona State University
+<p><i>Last changed: $Date$</i></p>
Deleted: grass/trunk/scripts/r.reclass.area/description.html
===================================================================
--- grass/trunk/scripts/r.reclass.area/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/scripts/r.reclass.area/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,17 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>r.reclass.area</em> reclasses a raster map greater or
-less than a user specified area size (in hectares).
-
-<h2>SEE ALSO</h2>
-
-<em><a HREF="r.reclass.html">r.reclass</a></em><br>
-<em><a HREF="r.clump.html">r.clump</a></em><br>
-<em><a HREF="r.stats.html">r.stats</a></em><br>
-
-<h2>AUTHORS</h2>
-
-NRCS,<br>
-Markus Neteler
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/scripts/r.reclass.area/r.reclass.area.html (from rev 32770, grass/trunk/scripts/r.reclass.area/description.html)
===================================================================
--- grass/trunk/scripts/r.reclass.area/r.reclass.area.html (rev 0)
+++ grass/trunk/scripts/r.reclass.area/r.reclass.area.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,17 @@
+<h2>DESCRIPTION</h2>
+
+<em>r.reclass.area</em> reclasses a raster map greater or
+less than a user specified area size (in hectares).
+
+<h2>SEE ALSO</h2>
+
+<em><a HREF="r.reclass.html">r.reclass</a></em><br>
+<em><a HREF="r.clump.html">r.clump</a></em><br>
+<em><a HREF="r.stats.html">r.stats</a></em><br>
+
+<h2>AUTHORS</h2>
+
+NRCS,<br>
+Markus Neteler
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/scripts/r.regression.line/description.html
===================================================================
--- grass/trunk/scripts/r.regression.line/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/scripts/r.regression.line/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,49 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-<EM>r.regression.line</EM> Calculates linear regression from two raster maps,
-according to the formula y = a + b*x, where x and y represent raster maps.
-Optionally saves regression coefficients to an ASCII file.
-The result includes the following coefficients:
-offset/intercept (a) and gain/slope (b), residuals (R),
-number of elements (N), means (medX, medY), standard deviations
-(sdX, sdY), and the F test for testing the significance of the
-regression model as a whole (F).
-
-<H2>NOTES</H2>
-The flag <em>-s</em> select the slower method (applies to FP maps only)
-which writes out all pixel values individually to the temporary file.
-The results for offset/intercept (a) and gain/slope (b) are then
-identical to that obtained from R-stats's lm() function.
-
-<H2>EXAMPLE</H2>
-
-Comparison of the old and the new DEM in Spearfish:
-<div class="code"><pre>
-g.region rast=elevation.10m -p
-r.regression.line map1=elevation.dem map2=elevation.10m
-</pre></div>
-<p>
-
-Using the script style flag AND <em>eval</em> to make results
-available in the shell:
-<div class="code"><pre>
-g.region rast=elevation.10m -p
-eval `r.regression.line -g map1=elevation.dem map2=elevation.10m`
-echo $a
-479.615
-
-echo $b
-0.645631
-
-echo $R
-0.804441
-</pre></div>
-
-
-<H2>AUTHOR</H2>
-
-Dr. Agustin Lobo - alobo at ija.csic.es<BR>
-Updated to GRASS 5.7 Michael Barton, Arizona State University<BR>
-Script style output Markus Neteler
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/scripts/r.regression.line/r.regression.line.html (from rev 32770, grass/trunk/scripts/r.regression.line/description.html)
===================================================================
--- grass/trunk/scripts/r.regression.line/r.regression.line.html (rev 0)
+++ grass/trunk/scripts/r.regression.line/r.regression.line.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,49 @@
+<H2>DESCRIPTION</H2>
+
+<EM>r.regression.line</EM> Calculates linear regression from two raster maps,
+according to the formula y = a + b*x, where x and y represent raster maps.
+Optionally saves regression coefficients to an ASCII file.
+The result includes the following coefficients:
+offset/intercept (a) and gain/slope (b), residuals (R),
+number of elements (N), means (medX, medY), standard deviations
+(sdX, sdY), and the F test for testing the significance of the
+regression model as a whole (F).
+
+<H2>NOTES</H2>
+The flag <em>-s</em> select the slower method (applies to FP maps only)
+which writes out all pixel values individually to the temporary file.
+The results for offset/intercept (a) and gain/slope (b) are then
+identical to that obtained from R-stats's lm() function.
+
+<H2>EXAMPLE</H2>
+
+Comparison of the old and the new DEM in Spearfish:
+<div class="code"><pre>
+g.region rast=elevation.10m -p
+r.regression.line map1=elevation.dem map2=elevation.10m
+</pre></div>
+<p>
+
+Using the script style flag AND <em>eval</em> to make results
+available in the shell:
+<div class="code"><pre>
+g.region rast=elevation.10m -p
+eval `r.regression.line -g map1=elevation.dem map2=elevation.10m`
+echo $a
+479.615
+
+echo $b
+0.645631
+
+echo $R
+0.804441
+</pre></div>
+
+
+<H2>AUTHOR</H2>
+
+Dr. Agustin Lobo - alobo at ija.csic.es<BR>
+Updated to GRASS 5.7 Michael Barton, Arizona State University<BR>
+Script style output Markus Neteler
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/scripts/r.shaded.relief/description.html
===================================================================
--- grass/trunk/scripts/r.shaded.relief/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/scripts/r.shaded.relief/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,100 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-
-<EM>r.shaded.relief</EM> is a Bourne shell script that
-creates a raster shaded relief map based on current
-resolution settings and on sun altitude, azimuth, and z-exaggeration values
-entered by the user. If no output shademap name is given, the new shaded
-relief map is named <EM><input_map>.shade</EM>.
-The map is assigned a grey-scale color table.
-
-
-<P>
-If no parameters are provided on startup, this program is interactive;
-thus if the user enters the command:
-
-<DL>
-<DD>
-<B>r.shaded.relief</B>
-</DL>
-
-The program then prompts the user to enter values for:
-<OL>
-<LI>The <B>altitude</B> of the sun in degrees above the horizon
-(a value between 0 and 90 degrees), and
-
-<LI>The <B>azimuth</B> of the sun in degrees to the east of north
-(a value between 0 and 360 degrees).
-
-<LI>The name of a raster map layer to provide elevation values for the
-shaded relief map. Typically, this would be a map layer of elevation;
-however, any raster map layer can be named.
-
-<LI>The scaling parameter, which compensates for a different horizontal
-<B>scale</B> than vertical scale. If 'scale' is a number then the ewres
-and nsres are multiplied by that scale to calculate the shading. (Default=1.0
-for equivalent horizontal and vertical scales.)
-
-<LI>For the special case when a latitude-longitude projection is used with an
-elevation map measured in meters (e.g., SRTM, ETOPO2 etc.) or feet, the
-<b>units</b> can be set to automatically set the horizontal scale to the the number of
-meters (scale=111120) or feet (scale=370400) in a degree of latitude. The script scales
-latitude and longitude equally, so it's only approximately right, but for shading
-it's close enough. It makes the difference between a usable and unusable shade.
-The <b>units</b> parameter overrides the <b>scale</b> parameter.
-
-<LI>The <b>zmult</b> exaggeration factor that changes the apparent relief
-for the shaded relief map. This can be any positive (or negative) floating
-point value. (Default=1.0)
-
-</OL>
-
-Specifically, <EM>r.shaded.relief</EM> executes a
-<EM><A HREF="r.mapcalc.html">r.mapcalc</A></EM>
-statement. Refer to the manual entry for
-<EM><A HREF="r.mapcalc.html">r.mapcalc</A></EM> for an explanation
-of the filtering syntax shown in the above expression.
-See, for example, the section on "The Neighborhood Modifier".
-
-<P>
-<EM>r.shaded.relief</EM> then runs <EM><a href="r.colors.html">r.colors</A></EM>
-to assign a grey-scale color table to the new shaded relief map.
-
-<H2>NOTES</H2>
-
-To visually improve the result of shade maps from low resolution elevation
-models, use <em>r.resamp.interp</em> with bilinear or bicubic method to
-resample the DEM at higher resolution. <EM>r.shaded.relief</EM> is then
-run on the resampled DEM.
-
-<H2>FILES</H2>
-
-This program is simply a shell script. Users are encouraged to make their
-own shell scripts using similar techniques.
-See <KBD>$GISBASE/scripts/r.shaded.relief</KBD>.
-
-<H2>SEE ALSO</H2>
-
-<i>An Algebra for GIS and Image Processing</i>, by Michael Shapiro and Jim
-Westervelt, U.S. Army Construction Engineering Research Laboratory
-(March/1991) (get from GRASS web site).
-
-<P>
-<!-- RGB version not ported to GRASS 6:
- <EM><A HREF="shade.clr.sh.html">shade.clr.sh</A></EM><BR>
- -->
-<EM>
-<A HREF="d.his.html">d.his</A>,<br>
-<A HREF="g.region.html">g.region</A>,<br>
-<A HREF="r.blend.html">r.blend</A>,<br>
-<A HREF="r.colors.html">r.colors</A>,<br>
-<A HREF="r.mapcalc.html">r.mapcalc</A>,<br>
-<A HREF="r.resamp.interp.html">r.resamp.interp</A>
-</EM>
-
-<H2>AUTHOR</H2>
-
-Jim Westervelt, U.S. Army Construction Engineering
-Research Laboratory
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/scripts/r.shaded.relief/r.shaded.relief.html (from rev 32770, grass/trunk/scripts/r.shaded.relief/description.html)
===================================================================
--- grass/trunk/scripts/r.shaded.relief/r.shaded.relief.html (rev 0)
+++ grass/trunk/scripts/r.shaded.relief/r.shaded.relief.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,100 @@
+<H2>DESCRIPTION</H2>
+
+
+<EM>r.shaded.relief</EM> is a Bourne shell script that
+creates a raster shaded relief map based on current
+resolution settings and on sun altitude, azimuth, and z-exaggeration values
+entered by the user. If no output shademap name is given, the new shaded
+relief map is named <EM><input_map>.shade</EM>.
+The map is assigned a grey-scale color table.
+
+
+<P>
+If no parameters are provided on startup, this program is interactive;
+thus if the user enters the command:
+
+<DL>
+<DD>
+<B>r.shaded.relief</B>
+</DL>
+
+The program then prompts the user to enter values for:
+<OL>
+<LI>The <B>altitude</B> of the sun in degrees above the horizon
+(a value between 0 and 90 degrees), and
+
+<LI>The <B>azimuth</B> of the sun in degrees to the east of north
+(a value between 0 and 360 degrees).
+
+<LI>The name of a raster map layer to provide elevation values for the
+shaded relief map. Typically, this would be a map layer of elevation;
+however, any raster map layer can be named.
+
+<LI>The scaling parameter, which compensates for a different horizontal
+<B>scale</B> than vertical scale. If 'scale' is a number then the ewres
+and nsres are multiplied by that scale to calculate the shading. (Default=1.0
+for equivalent horizontal and vertical scales.)
+
+<LI>For the special case when a latitude-longitude projection is used with an
+elevation map measured in meters (e.g., SRTM, ETOPO2 etc.) or feet, the
+<b>units</b> can be set to automatically set the horizontal scale to the the number of
+meters (scale=111120) or feet (scale=370400) in a degree of latitude. The script scales
+latitude and longitude equally, so it's only approximately right, but for shading
+it's close enough. It makes the difference between a usable and unusable shade.
+The <b>units</b> parameter overrides the <b>scale</b> parameter.
+
+<LI>The <b>zmult</b> exaggeration factor that changes the apparent relief
+for the shaded relief map. This can be any positive (or negative) floating
+point value. (Default=1.0)
+
+</OL>
+
+Specifically, <EM>r.shaded.relief</EM> executes a
+<EM><A HREF="r.mapcalc.html">r.mapcalc</A></EM>
+statement. Refer to the manual entry for
+<EM><A HREF="r.mapcalc.html">r.mapcalc</A></EM> for an explanation
+of the filtering syntax shown in the above expression.
+See, for example, the section on "The Neighborhood Modifier".
+
+<P>
+<EM>r.shaded.relief</EM> then runs <EM><a href="r.colors.html">r.colors</A></EM>
+to assign a grey-scale color table to the new shaded relief map.
+
+<H2>NOTES</H2>
+
+To visually improve the result of shade maps from low resolution elevation
+models, use <em>r.resamp.interp</em> with bilinear or bicubic method to
+resample the DEM at higher resolution. <EM>r.shaded.relief</EM> is then
+run on the resampled DEM.
+
+<H2>FILES</H2>
+
+This program is simply a shell script. Users are encouraged to make their
+own shell scripts using similar techniques.
+See <KBD>$GISBASE/scripts/r.shaded.relief</KBD>.
+
+<H2>SEE ALSO</H2>
+
+<i>An Algebra for GIS and Image Processing</i>, by Michael Shapiro and Jim
+Westervelt, U.S. Army Construction Engineering Research Laboratory
+(March/1991) (get from GRASS web site).
+
+<P>
+<!-- RGB version not ported to GRASS 6:
+ <EM><A HREF="shade.clr.sh.html">shade.clr.sh</A></EM><BR>
+ -->
+<EM>
+<A HREF="d.his.html">d.his</A>,<br>
+<A HREF="g.region.html">g.region</A>,<br>
+<A HREF="r.blend.html">r.blend</A>,<br>
+<A HREF="r.colors.html">r.colors</A>,<br>
+<A HREF="r.mapcalc.html">r.mapcalc</A>,<br>
+<A HREF="r.resamp.interp.html">r.resamp.interp</A>
+</EM>
+
+<H2>AUTHOR</H2>
+
+Jim Westervelt, U.S. Army Construction Engineering
+Research Laboratory
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/scripts/r.tileset/description.html
===================================================================
--- grass/trunk/scripts/r.tileset/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/scripts/r.tileset/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,103 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-<EM>r.tileset</EM> generates sets of tiles in another projection that cover a region in this projection with adequate resolution. By default the current region and its resolution are used, the bounds and resolution of another region can be used via the region option.
-
-<H2>NOTES</H2>
-
-<EM>r.tileset</EM> does not make "optimal" tilings (as few tiles of the largest size less than the maximums). This means that from latitude longitude projection to an appropriate projection for a region, in the degenerate case, it may create tiles demanding up to twice the necessary information. Furthermore, generating a tiling near a divergant point of a source projection, such as the poles of a cylindrical source projections, results in divergence of the tile set.
-
-<p>Not generating "optimal" tilings may have another consequence; the aspect ratio of cells in the destination region will not necessarily carry over to the source region and generated tiles may have cells of strange aspect ratios. This might be a problem for some map request services presenting data in an inappropriate projection or with strict constraints on cell aspect ratio.
-
-<H2>OUTPUT FORMAT</H2>
-
-Each tile is listed on a seperate line in the output. The lines are formatted as follows:
-
-<dl>
-<dt>
-<div class="code"><pre>
-5|125|45|175|80|100
-</pre></div>
-
-<dd>
-This is the default output format. It is the tile's minimum x coordinate, minimum y coordinate, maximum x coordinate, maximum y coordinate, width in cells, and height in cells seperated by the "|" character. The fields can be seperated by a different character by changing the fs option.
-
-<p>
-
-<dt>
-<div class="code"><pre>
-w=5;s=125;e=45;n=175;cols=80;rows=100;
-</pre></div>
-
-<dd>
-This is output in a format convinent for setting variables in a shell script.
-
-<p>
-
-<dt>
-<div class="code"><pre>
-bbox=5,125,45,175&width=80&height=100
-</pre></div>
-
-<dd>
-This is output in a format convinent for requesting data from some http services.
-
-<p>
-</dl>
-
-
-<H2>EXAMPLES</H2>
-
-<dl>
-<dt>
-<div class="code"><pre>
-r.tileset sourceproj=+init=epsg:4326 maxrows=1024 maxcols=2048
-</pre></div>
-<dd> Generates tiles in latitude longitude that cover the current region, each tile will be less than 1024 cells high and 2048 cells across. The bounds and sizes of tiles in the output are seperated by |
-
-<p>
-
-<dt>
-<div class="code"><pre>
-r.tileset sourceproj=+init=epsg:4326 overlap=2 -w region=ne-rio
-</pre></div>
-<dd>Generates tiles in latitude longitude projection that cover the named region "ne-rio". The tiles will have 2 cells of overlap. The output format will be strings like the bbox requests for WMS servers.
-
-<p>
-
-<dt>
-<div class="code"><pre>
-r.tileset sourceproj=`g.proj -j location=IrishGrid` maxrows=400 maxcols=300 overlap=3 -g
-</pre></div>
-<dd>Generates tiles in the projection of the location "IrishGrid". Each tile will be less than 300x400 cells in size, with 3 cells of overlap in the top and right sides of each tile. The output is in a format where each line is in shell script style. The substitution <code>`g.proj -j location=IrishGrid`</code> will only work in a unix style shell.
-
-</dl>
-
-<H2>REQUIRED PROGRAMS</H2>
-
-<EM>r.tileset</EM> requires the following programs to work:
-
-<dl>
-<dt>cs2cs
-<dd>The coordinate system transformation program from Proj4.
-
-<dt>bc
-<dd>A calculator program
-
-<dt>sed, grep
-<dd>Unix string processing and search programs
-
-</dl>
-
-
-<H2>BUGS</H2>
-
-<ul>
-<li><EM>r.tileset</EM> does not know about meridians that "wrap-around" in projections.
-</ul>
-
-
-<H2>AUTHORS</H2>
-
-Cedric Shock
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/scripts/r.tileset/r.tileset.html (from rev 32770, grass/trunk/scripts/r.tileset/description.html)
===================================================================
--- grass/trunk/scripts/r.tileset/r.tileset.html (rev 0)
+++ grass/trunk/scripts/r.tileset/r.tileset.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,103 @@
+<H2>DESCRIPTION</H2>
+
+<EM>r.tileset</EM> generates sets of tiles in another projection that cover a region in this projection with adequate resolution. By default the current region and its resolution are used, the bounds and resolution of another region can be used via the region option.
+
+<H2>NOTES</H2>
+
+<EM>r.tileset</EM> does not make "optimal" tilings (as few tiles of the largest size less than the maximums). This means that from latitude longitude projection to an appropriate projection for a region, in the degenerate case, it may create tiles demanding up to twice the necessary information. Furthermore, generating a tiling near a divergant point of a source projection, such as the poles of a cylindrical source projections, results in divergence of the tile set.
+
+<p>Not generating "optimal" tilings may have another consequence; the aspect ratio of cells in the destination region will not necessarily carry over to the source region and generated tiles may have cells of strange aspect ratios. This might be a problem for some map request services presenting data in an inappropriate projection or with strict constraints on cell aspect ratio.
+
+<H2>OUTPUT FORMAT</H2>
+
+Each tile is listed on a seperate line in the output. The lines are formatted as follows:
+
+<dl>
+<dt>
+<div class="code"><pre>
+5|125|45|175|80|100
+</pre></div>
+
+<dd>
+This is the default output format. It is the tile's minimum x coordinate, minimum y coordinate, maximum x coordinate, maximum y coordinate, width in cells, and height in cells seperated by the "|" character. The fields can be seperated by a different character by changing the fs option.
+
+<p>
+
+<dt>
+<div class="code"><pre>
+w=5;s=125;e=45;n=175;cols=80;rows=100;
+</pre></div>
+
+<dd>
+This is output in a format convinent for setting variables in a shell script.
+
+<p>
+
+<dt>
+<div class="code"><pre>
+bbox=5,125,45,175&width=80&height=100
+</pre></div>
+
+<dd>
+This is output in a format convinent for requesting data from some http services.
+
+<p>
+</dl>
+
+
+<H2>EXAMPLES</H2>
+
+<dl>
+<dt>
+<div class="code"><pre>
+r.tileset sourceproj=+init=epsg:4326 maxrows=1024 maxcols=2048
+</pre></div>
+<dd> Generates tiles in latitude longitude that cover the current region, each tile will be less than 1024 cells high and 2048 cells across. The bounds and sizes of tiles in the output are seperated by |
+
+<p>
+
+<dt>
+<div class="code"><pre>
+r.tileset sourceproj=+init=epsg:4326 overlap=2 -w region=ne-rio
+</pre></div>
+<dd>Generates tiles in latitude longitude projection that cover the named region "ne-rio". The tiles will have 2 cells of overlap. The output format will be strings like the bbox requests for WMS servers.
+
+<p>
+
+<dt>
+<div class="code"><pre>
+r.tileset sourceproj=`g.proj -j location=IrishGrid` maxrows=400 maxcols=300 overlap=3 -g
+</pre></div>
+<dd>Generates tiles in the projection of the location "IrishGrid". Each tile will be less than 300x400 cells in size, with 3 cells of overlap in the top and right sides of each tile. The output is in a format where each line is in shell script style. The substitution <code>`g.proj -j location=IrishGrid`</code> will only work in a unix style shell.
+
+</dl>
+
+<H2>REQUIRED PROGRAMS</H2>
+
+<EM>r.tileset</EM> requires the following programs to work:
+
+<dl>
+<dt>cs2cs
+<dd>The coordinate system transformation program from Proj4.
+
+<dt>bc
+<dd>A calculator program
+
+<dt>sed, grep
+<dd>Unix string processing and search programs
+
+</dl>
+
+
+<H2>BUGS</H2>
+
+<ul>
+<li><EM>r.tileset</EM> does not know about meridians that "wrap-around" in projections.
+</ul>
+
+
+<H2>AUTHORS</H2>
+
+Cedric Shock
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/scripts/r3.mapcalculator/description.html
===================================================================
--- grass/trunk/scripts/r3.mapcalculator/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/scripts/r3.mapcalculator/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,21 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-
-<EM>r3.mapcalculator</EM> Provides a GUI frontend to r3.mapcalc. Up to 5 maps can be combined using simple expressions.
-
-Enter an r3.mapcalc expression in the formula field using the format: A+C or exp(A+C)+(B-2)*7 where A, B, C are grid3D volumes entered in the A field, B field, and C field.
-
-Do not enter output file in the formula field: correct: A+B; incorrect: newfile = A+B. Use no spaces or blanks.
-
-Expert mode runs r.mapcalc for more complex expressions.
-<br>
-
-<H2>SEE ALSO</H2>
-
-<EM><A HREF="r3.mapcalc.html">r.mapcalc</A></EM>,
-
-
-<H2>AUTHOR</H2>
-
-Michael Barton, Arizona State University. Based on r.mapcalculator by R. Brunzema (r.brunzema at web.de)
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/scripts/r3.mapcalculator/r3.mapcalculator.html (from rev 32770, grass/trunk/scripts/r3.mapcalculator/description.html)
===================================================================
--- grass/trunk/scripts/r3.mapcalculator/r3.mapcalculator.html (rev 0)
+++ grass/trunk/scripts/r3.mapcalculator/r3.mapcalculator.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,21 @@
+<H2>DESCRIPTION</H2>
+
+
+<EM>r3.mapcalculator</EM> Provides a GUI frontend to r3.mapcalc. Up to 5 maps can be combined using simple expressions.
+
+Enter an r3.mapcalc expression in the formula field using the format: A+C or exp(A+C)+(B-2)*7 where A, B, C are grid3D volumes entered in the A field, B field, and C field.
+
+Do not enter output file in the formula field: correct: A+B; incorrect: newfile = A+B. Use no spaces or blanks.
+
+Expert mode runs r.mapcalc for more complex expressions.
+<br>
+
+<H2>SEE ALSO</H2>
+
+<EM><A HREF="r3.mapcalc.html">r.mapcalc</A></EM>,
+
+
+<H2>AUTHOR</H2>
+
+Michael Barton, Arizona State University. Based on r.mapcalculator by R. Brunzema (r.brunzema at web.de)
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/scripts/v.build.all/description.html
===================================================================
--- grass/trunk/scripts/v.build.all/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/scripts/v.build.all/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,9 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-<EM>v.build.all</EM> will run <em><a href="v.build.html">v.build</a></em>
-for all vectors in the current mapset.
-
-<H2>AUTHOR</H2>
-Radim Blazek
-<p>
-<i>Last changed: $Date$</i>
Copied: grass/trunk/scripts/v.build.all/v.build.all.html (from rev 32770, grass/trunk/scripts/v.build.all/description.html)
===================================================================
--- grass/trunk/scripts/v.build.all/v.build.all.html (rev 0)
+++ grass/trunk/scripts/v.build.all/v.build.all.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,9 @@
+<H2>DESCRIPTION</H2>
+
+<EM>v.build.all</EM> will run <em><a href="v.build.html">v.build</a></em>
+for all vectors in the current mapset.
+
+<H2>AUTHOR</H2>
+Radim Blazek
+<p>
+<i>Last changed: $Date$</i>
Deleted: grass/trunk/scripts/v.centroids/description.html
===================================================================
--- grass/trunk/scripts/v.centroids/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/scripts/v.centroids/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,37 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-GRASS defines vector areas as composite entities consisting of a set of
-closed boundaries and a centroid. The attribute information associated
-with that area is linked to the centroid. The <EM>v.centroids</EM> module
-adds centroids to closed boundaries in the <b>input</b> file and assigns a
-category number to them. The starting value as well as the increment size
-may be set using optional parameters.
-<P>
-Multiple attributes may be linked to a single vector entity through
-numbered fields referred to as layers. Refer to <em>v.category</em>
-for more details, as <EM>v.centroids</EM> is simply a frontend to that
-module.
-<P>
-The boundary itself is often stored without any category reference as it
-can mark the border between two adjacent areas. Thus it would be ambiguous
-as to which feature the attribute would belong. In some cases it may, for
-example, represent a road between two parcels of land. In this case it
-is entirely appropriate for the boundary to contain category information.
-<p>
-
-<EM>(GRASS Shell Script)</EM>
-
-<H2>SEE ALSO</H2>
-
-<em>
-<A HREF="v.category.html">v.category</A>
-</em>
-
-<H2>AUTHORS</H2>
-
-module: M. Hamish Bowman, Dept. Marine Science, Otago University, New Zealand
-<BR>
-help page: Trevor Wiens
-
-<P>
-<i>Last changed: $Date$</i>
Copied: grass/trunk/scripts/v.centroids/v.centroids.html (from rev 32770, grass/trunk/scripts/v.centroids/description.html)
===================================================================
--- grass/trunk/scripts/v.centroids/v.centroids.html (rev 0)
+++ grass/trunk/scripts/v.centroids/v.centroids.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,37 @@
+<H2>DESCRIPTION</H2>
+
+GRASS defines vector areas as composite entities consisting of a set of
+closed boundaries and a centroid. The attribute information associated
+with that area is linked to the centroid. The <EM>v.centroids</EM> module
+adds centroids to closed boundaries in the <b>input</b> file and assigns a
+category number to them. The starting value as well as the increment size
+may be set using optional parameters.
+<P>
+Multiple attributes may be linked to a single vector entity through
+numbered fields referred to as layers. Refer to <em>v.category</em>
+for more details, as <EM>v.centroids</EM> is simply a frontend to that
+module.
+<P>
+The boundary itself is often stored without any category reference as it
+can mark the border between two adjacent areas. Thus it would be ambiguous
+as to which feature the attribute would belong. In some cases it may, for
+example, represent a road between two parcels of land. In this case it
+is entirely appropriate for the boundary to contain category information.
+<p>
+
+<EM>(GRASS Shell Script)</EM>
+
+<H2>SEE ALSO</H2>
+
+<em>
+<A HREF="v.category.html">v.category</A>
+</em>
+
+<H2>AUTHORS</H2>
+
+module: M. Hamish Bowman, Dept. Marine Science, Otago University, New Zealand
+<BR>
+help page: Trevor Wiens
+
+<P>
+<i>Last changed: $Date$</i>
Deleted: grass/trunk/scripts/v.convert.all/description.html
===================================================================
--- grass/trunk/scripts/v.convert.all/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/scripts/v.convert.all/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,44 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>v.convert.all</em> converts all GRASS 5.0/5.3/5.4 vectors in the current
-mapset into GRASS 6.0 vectors.
-
-<h2>NOTES</h2>
-
-Vector maps from 5.0/5.3/5.4 and 6.0 do not interfere. They are stored in different
-directories, so you can use the same names. Old vector maps can be listed with
-<em>g.list oldvect</em>.
-
-<P>
-If you need to convert back from 6.0 into the 5.0/5.3/5.4 vector format,
-use <em>v.out.ogr</em> (to SHAPE format) and then <em>v.in.shape</em>
-in the old GRASS program.
-Alternatively use "<em>v.out.ascii -o</em>" and <em>v.in.ascii</em>.
-<P>
-As this GRASS version uses SQL for attribute management, there are
-some <a href=sql.html>SQL restrictings concerning the file names</a>.
-This script changes dots (e.g. "foo.bar") in old vector map names into
-underline(s) (e.g. "foo_bar").
-
-<h2>EXAMPLE</h2>
-
-To convert all old vector maps in the current mapset to the new vector format:
-<br>
-<tt>
-v.convert.all -r
-</tt>
-
-<h2>SEE ALSO</h2>
-
-<em><A HREF="g.list.html">g.list</A>,
-<A HREF="v.convert.html">v.convert</A>,
-<A HREF="v.out.ascii.html">v.out.ascii</A>,
-<A HREF="v.out.ogr.html">v.out.ogr</A></em>
-
-
-<h2>AUTHOR</h2>
-
-Markus Neteler, ITC-Irst, Trento, Italy
-
-<p>
-<i>Last changed: $Date$</i>
Copied: grass/trunk/scripts/v.convert.all/v.convert.all.html (from rev 32770, grass/trunk/scripts/v.convert.all/description.html)
===================================================================
--- grass/trunk/scripts/v.convert.all/v.convert.all.html (rev 0)
+++ grass/trunk/scripts/v.convert.all/v.convert.all.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,44 @@
+<h2>DESCRIPTION</h2>
+
+<em>v.convert.all</em> converts all GRASS 5.0/5.3/5.4 vectors in the current
+mapset into GRASS 6.0 vectors.
+
+<h2>NOTES</h2>
+
+Vector maps from 5.0/5.3/5.4 and 6.0 do not interfere. They are stored in different
+directories, so you can use the same names. Old vector maps can be listed with
+<em>g.list oldvect</em>.
+
+<P>
+If you need to convert back from 6.0 into the 5.0/5.3/5.4 vector format,
+use <em>v.out.ogr</em> (to SHAPE format) and then <em>v.in.shape</em>
+in the old GRASS program.
+Alternatively use "<em>v.out.ascii -o</em>" and <em>v.in.ascii</em>.
+<P>
+As this GRASS version uses SQL for attribute management, there are
+some <a href=sql.html>SQL restrictings concerning the file names</a>.
+This script changes dots (e.g. "foo.bar") in old vector map names into
+underline(s) (e.g. "foo_bar").
+
+<h2>EXAMPLE</h2>
+
+To convert all old vector maps in the current mapset to the new vector format:
+<br>
+<tt>
+v.convert.all -r
+</tt>
+
+<h2>SEE ALSO</h2>
+
+<em><A HREF="g.list.html">g.list</A>,
+<A HREF="v.convert.html">v.convert</A>,
+<A HREF="v.out.ascii.html">v.out.ascii</A>,
+<A HREF="v.out.ogr.html">v.out.ogr</A></em>
+
+
+<h2>AUTHOR</h2>
+
+Markus Neteler, ITC-Irst, Trento, Italy
+
+<p>
+<i>Last changed: $Date$</i>
Deleted: grass/trunk/scripts/v.db.addcol/description.html
===================================================================
--- grass/trunk/scripts/v.db.addcol/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/scripts/v.db.addcol/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,47 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>v.db.addcol</em> adds one or more column(s) to the attribute table
-connected to a given vector map. It automatically checks the connection for the
-specified layer.
-
-<h2>NOTES</h2>
-
-v.db.addcol is a front-end to <em>db.execute</em> to allow easier usage.
-
-The supported types of columns depend on the database backend. However, all
-backends should support VARCHAR, INT, DOUBLE PRECISION and DATE. The default
-dbf backend supports only these types.
-
-The existing database connection(s) can be verified with <em>v.db.connect</em>.
-
-<h2>EXAMPLES</h2>
-
-Adding a single column:<br>
-<div class="code"><pre>
-v.db.addcol sentiero_brenta_points columns="slope double precision"
-v.info -c sentiero_brenta_points
-</pre></div>
-
-<p>
-Adding two columns:<br>
-<div class="code"><pre>
-v.db.addcol sentiero_brenta_points columns="slope double precision,myname varchar(15)"
-v.info -c sentiero_brenta_points
-</pre></div>
-
-<h2>SEE ALSO</h2>
-
-<em><a HREF="db.execute.html">db.execute</a></em>,
-<em><a HREF="v.db.addtable.html">v.db.addtable</a></em>,
-<em><a HREF="v.db.connect.html">v.db.connect</a></em>,
-<em><a HREF="v.db.dropcol.html">v.db.dropcol</a></em>,
-<em><a HREF="v.db.droptable.html">v.db.droptable</a></em>,
-<em><a HREF="v.db.select.html">v.db.select</a></em>,
-<em><a HREF="v.db.update.html">v.db.update</a></em>
-
-
-<h2>AUTHOR</h2>
-
-Moritz Lennert (mlennert at club.worldonline.be)
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/scripts/v.db.addcol/v.db.addcol.html (from rev 32770, grass/trunk/scripts/v.db.addcol/description.html)
===================================================================
--- grass/trunk/scripts/v.db.addcol/v.db.addcol.html (rev 0)
+++ grass/trunk/scripts/v.db.addcol/v.db.addcol.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,47 @@
+<h2>DESCRIPTION</h2>
+
+<em>v.db.addcol</em> adds one or more column(s) to the attribute table
+connected to a given vector map. It automatically checks the connection for the
+specified layer.
+
+<h2>NOTES</h2>
+
+v.db.addcol is a front-end to <em>db.execute</em> to allow easier usage.
+
+The supported types of columns depend on the database backend. However, all
+backends should support VARCHAR, INT, DOUBLE PRECISION and DATE. The default
+dbf backend supports only these types.
+
+The existing database connection(s) can be verified with <em>v.db.connect</em>.
+
+<h2>EXAMPLES</h2>
+
+Adding a single column:<br>
+<div class="code"><pre>
+v.db.addcol sentiero_brenta_points columns="slope double precision"
+v.info -c sentiero_brenta_points
+</pre></div>
+
+<p>
+Adding two columns:<br>
+<div class="code"><pre>
+v.db.addcol sentiero_brenta_points columns="slope double precision,myname varchar(15)"
+v.info -c sentiero_brenta_points
+</pre></div>
+
+<h2>SEE ALSO</h2>
+
+<em><a HREF="db.execute.html">db.execute</a></em>,
+<em><a HREF="v.db.addtable.html">v.db.addtable</a></em>,
+<em><a HREF="v.db.connect.html">v.db.connect</a></em>,
+<em><a HREF="v.db.dropcol.html">v.db.dropcol</a></em>,
+<em><a HREF="v.db.droptable.html">v.db.droptable</a></em>,
+<em><a HREF="v.db.select.html">v.db.select</a></em>,
+<em><a HREF="v.db.update.html">v.db.update</a></em>
+
+
+<h2>AUTHOR</h2>
+
+Moritz Lennert (mlennert at club.worldonline.be)
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/scripts/v.db.addtable/description.html
===================================================================
--- grass/trunk/scripts/v.db.addtable/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/scripts/v.db.addtable/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,55 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>v.db.addtable</em> creates and adds a new attribute table to a given vector
-map. It links the table to the specified layer of the vector map. If the vector
-map is not yet linked to any table, new a database link is established based on
-the MAPSET database settings (see <em>db.connect</em>).
-
-<h2>NOTES</h2>
-
-<em>v.db.addtable</em> is a front-end to <em>db.execute</em> to allow easier
-usage.
-
-The supported types of columns depend on the database backend. However, all
-backends should support VARCHAR, INT, DOUBLE PRECISION and DATE. The default
-dbf backend supports only these types.
-
-The existing database connection(s) can be verified with <em>v.db.connect</em>.
-
-<h2>EXAMPLE</h2>
-
-Adding a new attribute table with a single column to default layer 1:<br>
-<div class="code"><pre>
-v.db.addtable sentiero_brenta_points columns="slope double precision"
-v.db.connect -p sentiero_brenta_points
-v.info -c sentiero_brenta_points
-</pre></div>
-
-<p>
-Adding a new attribute table with two columns to layer 2:<br>
-<div class="code"><pre>
-v.db.addtable sentiero_brenta_points columns="slope double precision,myname varchar(15)" layer=2
-v.db.connect -p sentiero_brenta_points
-v.info -c sentiero_brenta_points
-</pre></div>
-
-<h2>SEE ALSO</h2>
-
-<em><a HREF="db.connect.html">db.connect</a></em>,
-<em><a HREF="db.droptable.html">db.droptable</a></em>,
-<em><a HREF="db.execute.html">db.execute</a></em>,
-<em><a HREF="v.db.addcol.html">v.db.addcol</a></em>,
-<em><a HREF="v.db.connect.html">v.db.connect</a></em>,
-<em><a HREF="v.db.dropcol.html">v.db.dropcol</a></em>,
-<em><a HREF="v.db.droptable.html">v.db.droptable</a></em>,
-<em><a HREF="v.db.select.html">v.db.select</a></em>,
-<em><a HREF="v.db.update.html">v.db.update</a></em><br>
-<em><a href="sql.html">GRASS SQL interface</a></em>
-
-
-<h2>AUTHOR</h2>
-
-Markus Neteler
-
-<p>
-<i>Last changed: $Date$</i>
Copied: grass/trunk/scripts/v.db.addtable/v.db.addtable.html (from rev 32770, grass/trunk/scripts/v.db.addtable/description.html)
===================================================================
--- grass/trunk/scripts/v.db.addtable/v.db.addtable.html (rev 0)
+++ grass/trunk/scripts/v.db.addtable/v.db.addtable.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,55 @@
+<h2>DESCRIPTION</h2>
+
+<em>v.db.addtable</em> creates and adds a new attribute table to a given vector
+map. It links the table to the specified layer of the vector map. If the vector
+map is not yet linked to any table, new a database link is established based on
+the MAPSET database settings (see <em>db.connect</em>).
+
+<h2>NOTES</h2>
+
+<em>v.db.addtable</em> is a front-end to <em>db.execute</em> to allow easier
+usage.
+
+The supported types of columns depend on the database backend. However, all
+backends should support VARCHAR, INT, DOUBLE PRECISION and DATE. The default
+dbf backend supports only these types.
+
+The existing database connection(s) can be verified with <em>v.db.connect</em>.
+
+<h2>EXAMPLE</h2>
+
+Adding a new attribute table with a single column to default layer 1:<br>
+<div class="code"><pre>
+v.db.addtable sentiero_brenta_points columns="slope double precision"
+v.db.connect -p sentiero_brenta_points
+v.info -c sentiero_brenta_points
+</pre></div>
+
+<p>
+Adding a new attribute table with two columns to layer 2:<br>
+<div class="code"><pre>
+v.db.addtable sentiero_brenta_points columns="slope double precision,myname varchar(15)" layer=2
+v.db.connect -p sentiero_brenta_points
+v.info -c sentiero_brenta_points
+</pre></div>
+
+<h2>SEE ALSO</h2>
+
+<em><a HREF="db.connect.html">db.connect</a></em>,
+<em><a HREF="db.droptable.html">db.droptable</a></em>,
+<em><a HREF="db.execute.html">db.execute</a></em>,
+<em><a HREF="v.db.addcol.html">v.db.addcol</a></em>,
+<em><a HREF="v.db.connect.html">v.db.connect</a></em>,
+<em><a HREF="v.db.dropcol.html">v.db.dropcol</a></em>,
+<em><a HREF="v.db.droptable.html">v.db.droptable</a></em>,
+<em><a HREF="v.db.select.html">v.db.select</a></em>,
+<em><a HREF="v.db.update.html">v.db.update</a></em><br>
+<em><a href="sql.html">GRASS SQL interface</a></em>
+
+
+<h2>AUTHOR</h2>
+
+Markus Neteler
+
+<p>
+<i>Last changed: $Date$</i>
Deleted: grass/trunk/scripts/v.db.dropcol/description.html
===================================================================
--- grass/trunk/scripts/v.db.dropcol/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/scripts/v.db.dropcol/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,38 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>v.db.dropcol</em> drops a column from the attribute table connected
-to a given vector map. It automatically checks the connection for the specified
-layer. <em>v.db.dropcol</em> omits to delete the 'cat' column which is
-relevant to keep the connection between vector map and table.
-
-<h2>NOTES</h2>
-
-v.db.dropcol is a front-end to <em>db.execute</em> to allow easier usage.
-
-The existing database connection(s) can be verified with <em>v.db.connect</em>.
-
-<h2>EXAMPLES</h2>
-
-Dropping a column:<br>
-<div class="code"><pre>
-v.db.dropcol sentiero_brenta_points column=slope
-v.info -c sentiero_brenta_points
-</pre></div>
-
-<h2>SEE ALSO</h2>
-
-<em><a HREF="db.droptable.html">db.droptable</a></em>,
-<em><a HREF="db.execute.html">db.execute</a></em>,
-<em><a HREF="v.db.addcol.html">v.db.addcol</a></em>,
-<em><a HREF="v.db.addtable.html">v.db.addtable</a></em>,
-<em><a HREF="v.db.connect.html">v.db.connect</a></em>,
-<em><a HREF="v.db.droptable.html">v.db.droptable</a></em>,
-<em><a HREF="v.db.select.html">v.db.select</a></em>,
-<em><a HREF="v.db.update.html">v.db.update</a></em>
-
-
-<h2>AUTHOR</h2>
-
-Markus Neteler
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/scripts/v.db.dropcol/v.db.dropcol.html (from rev 32770, grass/trunk/scripts/v.db.dropcol/description.html)
===================================================================
--- grass/trunk/scripts/v.db.dropcol/v.db.dropcol.html (rev 0)
+++ grass/trunk/scripts/v.db.dropcol/v.db.dropcol.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,38 @@
+<h2>DESCRIPTION</h2>
+
+<em>v.db.dropcol</em> drops a column from the attribute table connected
+to a given vector map. It automatically checks the connection for the specified
+layer. <em>v.db.dropcol</em> omits to delete the 'cat' column which is
+relevant to keep the connection between vector map and table.
+
+<h2>NOTES</h2>
+
+v.db.dropcol is a front-end to <em>db.execute</em> to allow easier usage.
+
+The existing database connection(s) can be verified with <em>v.db.connect</em>.
+
+<h2>EXAMPLES</h2>
+
+Dropping a column:<br>
+<div class="code"><pre>
+v.db.dropcol sentiero_brenta_points column=slope
+v.info -c sentiero_brenta_points
+</pre></div>
+
+<h2>SEE ALSO</h2>
+
+<em><a HREF="db.droptable.html">db.droptable</a></em>,
+<em><a HREF="db.execute.html">db.execute</a></em>,
+<em><a HREF="v.db.addcol.html">v.db.addcol</a></em>,
+<em><a HREF="v.db.addtable.html">v.db.addtable</a></em>,
+<em><a HREF="v.db.connect.html">v.db.connect</a></em>,
+<em><a HREF="v.db.droptable.html">v.db.droptable</a></em>,
+<em><a HREF="v.db.select.html">v.db.select</a></em>,
+<em><a HREF="v.db.update.html">v.db.update</a></em>
+
+
+<h2>AUTHOR</h2>
+
+Markus Neteler
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/scripts/v.db.droptable/description.html
===================================================================
--- grass/trunk/scripts/v.db.droptable/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/scripts/v.db.droptable/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,37 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>v.db.droptable</em> removes an existing attribute table from a
-given vector map linked at given layer. If the <b>-f</b> force flag is not
-given then nothing is removed.
-
-<h2>NOTES</h2>
-
-<em>v.db.droptable</em> is a front-end to <em>db.execute</em> to allow easier usage.
-
-The existing database connection(s) can be verified with <em>v.db.connect</em>.
-
-<h2>EXAMPLE</h2>
-
-Removing attribute table connected to layer 2:<br>
-<div class="code"><pre>
-v.db.droptable sentiero_brenta_points layer=2
-v.db.connect -p sentiero_brenta_points
-</pre></div>
-
-<h2>SEE ALSO</h2>
-
-<em><a HREF="db.droptable.html">db.droptable</a></em>,
-<em><a HREF="db.execute.html">db.execute</a></em>,
-<em><a HREF="v.db.addcol.html">v.db.addcol</a></em>,
-<em><a HREF="v.db.addtable.html">v.db.addtable</a></em>,
-<em><a HREF="v.db.connect.html">v.db.connect</a></em>,
-<em><a HREF="v.db.dropcol.html">v.db.dropcol</a></em>,
-<em><a HREF="v.db.select.html">v.db.select</a></em>,
-<em><a HREF="v.db.update.html">v.db.update</a></em>
-
-
-<h2>AUTHOR</h2>
-
-Markus Neteler
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/scripts/v.db.droptable/v.db.droptable.html (from rev 32770, grass/trunk/scripts/v.db.droptable/description.html)
===================================================================
--- grass/trunk/scripts/v.db.droptable/v.db.droptable.html (rev 0)
+++ grass/trunk/scripts/v.db.droptable/v.db.droptable.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,37 @@
+<h2>DESCRIPTION</h2>
+
+<em>v.db.droptable</em> removes an existing attribute table from a
+given vector map linked at given layer. If the <b>-f</b> force flag is not
+given then nothing is removed.
+
+<h2>NOTES</h2>
+
+<em>v.db.droptable</em> is a front-end to <em>db.execute</em> to allow easier usage.
+
+The existing database connection(s) can be verified with <em>v.db.connect</em>.
+
+<h2>EXAMPLE</h2>
+
+Removing attribute table connected to layer 2:<br>
+<div class="code"><pre>
+v.db.droptable sentiero_brenta_points layer=2
+v.db.connect -p sentiero_brenta_points
+</pre></div>
+
+<h2>SEE ALSO</h2>
+
+<em><a HREF="db.droptable.html">db.droptable</a></em>,
+<em><a HREF="db.execute.html">db.execute</a></em>,
+<em><a HREF="v.db.addcol.html">v.db.addcol</a></em>,
+<em><a HREF="v.db.addtable.html">v.db.addtable</a></em>,
+<em><a HREF="v.db.connect.html">v.db.connect</a></em>,
+<em><a HREF="v.db.dropcol.html">v.db.dropcol</a></em>,
+<em><a HREF="v.db.select.html">v.db.select</a></em>,
+<em><a HREF="v.db.update.html">v.db.update</a></em>
+
+
+<h2>AUTHOR</h2>
+
+Markus Neteler
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/scripts/v.db.join/description.html
===================================================================
--- grass/trunk/scripts/v.db.join/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/scripts/v.db.join/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,78 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>v.db.join</em> joins the content of another table into the connected
-attribute table of a vector map.
-
-<h2>NOTES</h2>
-
-<em>v.db.join</em> is a front-end to <em>db.execute</em> to allow easier usage.
-
-The vector attribute table must be stored in a SQL database (SQLite, PostgreSQL,
-MySQL, ODBC, ...). The DBF backend is not supported. Tables can be
-imported with <em>db.in.ogr</em>.
-<p>
-The vector map-database connection(s) can be verified with <em>v.db.connect</em>.
-
-<h2>EXAMPLE</h2>
-
-Joining the soil type explanations from table <em>soils_legend</em>
-into the Spearfish soils map (<a href="http://www.grassbook.org/examples_menu.php">download legend)</a>:
-
-<div class="code"><pre>
-g.copy vect=soils,mysoils
-
-# import legend table
-db.in.ogr soils_legend.csv out=soils_legend
-
-# get join column names
-v.info -c mysoils
-db.describe -c soils_legend
-
-# look at original table
-v.db.select mysoils
-cat|label
-1|Aab
-2|Ba
-3|Bb
-4|BcB
-5|BcC
-...
-
-# look at legend
-db.select soils_legend
-db.select soils_legend | head -7
-id|shortname|longname
-0|no data|no data
-0|AaB|Alice fine sandy loam, 0 to 6
-0|Ba|Barnum silt loam
-0|Bb|Barnum silt loam, channeled
-0|BcB|Boneek silt loam, 2 to 6
-0|BcC|Boneek silt loam, 6 to 9
-...
-
-# join soils_legend into mysoils attribute table
-v.db.join mysoils col=label otable=soils_legend ocol=shortname
-
-# verification of join
-v.db.select mysoils
-cat|label|id|shortname|longname
-1|Aab|||
-2|Ba|2|Ba|Barnum silt loam
-3|Bb|3|Bb|Barnum silt loam, channeled
-4|BcB|4|BcB|Boneek silt loam, 2 to 6
-5|BcC|5|BcC|Boneek silt loam, 6 to 9
-...
-</pre></div>
-
-<h2>SEE ALSO</h2>
-
-<em><a HREF="db.execute.html">db.execute</a></em>,
-<em><a HREF="db.in.ogr.html">db.in.ogr</a></em>,
-<em><a HREF="v.db.update.html">v.db.update</a></em><br>
-<em><a href="sql.html">GRASS SQL interface</a></em>
-
-<h2>AUTHOR</h2>
-
-Markus Neteler
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/scripts/v.db.join/v.db.join.html (from rev 32770, grass/trunk/scripts/v.db.join/description.html)
===================================================================
--- grass/trunk/scripts/v.db.join/v.db.join.html (rev 0)
+++ grass/trunk/scripts/v.db.join/v.db.join.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,78 @@
+<h2>DESCRIPTION</h2>
+
+<em>v.db.join</em> joins the content of another table into the connected
+attribute table of a vector map.
+
+<h2>NOTES</h2>
+
+<em>v.db.join</em> is a front-end to <em>db.execute</em> to allow easier usage.
+
+The vector attribute table must be stored in a SQL database (SQLite, PostgreSQL,
+MySQL, ODBC, ...). The DBF backend is not supported. Tables can be
+imported with <em>db.in.ogr</em>.
+<p>
+The vector map-database connection(s) can be verified with <em>v.db.connect</em>.
+
+<h2>EXAMPLE</h2>
+
+Joining the soil type explanations from table <em>soils_legend</em>
+into the Spearfish soils map (<a href="http://www.grassbook.org/examples_menu.php">download legend)</a>:
+
+<div class="code"><pre>
+g.copy vect=soils,mysoils
+
+# import legend table
+db.in.ogr soils_legend.csv out=soils_legend
+
+# get join column names
+v.info -c mysoils
+db.describe -c soils_legend
+
+# look at original table
+v.db.select mysoils
+cat|label
+1|Aab
+2|Ba
+3|Bb
+4|BcB
+5|BcC
+...
+
+# look at legend
+db.select soils_legend
+db.select soils_legend | head -7
+id|shortname|longname
+0|no data|no data
+0|AaB|Alice fine sandy loam, 0 to 6
+0|Ba|Barnum silt loam
+0|Bb|Barnum silt loam, channeled
+0|BcB|Boneek silt loam, 2 to 6
+0|BcC|Boneek silt loam, 6 to 9
+...
+
+# join soils_legend into mysoils attribute table
+v.db.join mysoils col=label otable=soils_legend ocol=shortname
+
+# verification of join
+v.db.select mysoils
+cat|label|id|shortname|longname
+1|Aab|||
+2|Ba|2|Ba|Barnum silt loam
+3|Bb|3|Bb|Barnum silt loam, channeled
+4|BcB|4|BcB|Boneek silt loam, 2 to 6
+5|BcC|5|BcC|Boneek silt loam, 6 to 9
+...
+</pre></div>
+
+<h2>SEE ALSO</h2>
+
+<em><a HREF="db.execute.html">db.execute</a></em>,
+<em><a HREF="db.in.ogr.html">db.in.ogr</a></em>,
+<em><a HREF="v.db.update.html">v.db.update</a></em><br>
+<em><a href="sql.html">GRASS SQL interface</a></em>
+
+<h2>AUTHOR</h2>
+
+Markus Neteler
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/scripts/v.db.reconnect.all/description.html
===================================================================
--- grass/trunk/scripts/v.db.reconnect.all/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/scripts/v.db.reconnect.all/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,11 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-<EM>v.db.reconnect.all</EM> changes database connection of all layers of
-all vectors in the current mapset from old_database to database. If a link
-does not match the old_database it is left untouched.
-
-<H2>AUTHOR</H2>
-Radim Blazek
-
-<p>
-<i>Last changed: $Date$</i>
Copied: grass/trunk/scripts/v.db.reconnect.all/v.db.reconnect.all.html (from rev 32770, grass/trunk/scripts/v.db.reconnect.all/description.html)
===================================================================
--- grass/trunk/scripts/v.db.reconnect.all/v.db.reconnect.all.html (rev 0)
+++ grass/trunk/scripts/v.db.reconnect.all/v.db.reconnect.all.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,11 @@
+<H2>DESCRIPTION</H2>
+
+<EM>v.db.reconnect.all</EM> changes database connection of all layers of
+all vectors in the current mapset from old_database to database. If a link
+does not match the old_database it is left untouched.
+
+<H2>AUTHOR</H2>
+Radim Blazek
+
+<p>
+<i>Last changed: $Date$</i>
Deleted: grass/trunk/scripts/v.db.renamecol/description.html
===================================================================
--- grass/trunk/scripts/v.db.renamecol/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/scripts/v.db.renamecol/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,50 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>v.db.renamecol</em> renames a column in the attribute table connected
-to a given vector map. It automatically checks the connection for the specified
-layer.
-
-<h2>NOTES</h2>
-
-If the map table is connected through the DBF or SQLite drivers, the renaming
-is internally done by adding a new column with new name, transferring the contents
-of the old column to the new column and dropping the old column. This is needed
-as DBF or SQLite do not support "ALTER TABLE" command to rename columns. Due to
-this the renamed column is found as last column of the table, it's original position
-cannot be maintained.
-
-<p>
-The SQLite driver will exit with an error if the column rename involves only a change of
-case, i.e., upper-to-lowercase, or lower-to-uppercase. The SQLite protocol considers "NAME"
-and "name" to be identical column names. In cases like these, the user should rename the original
-column to an intermediary name, then rename the intermediary to the final name.
-
-<p>
-
-
-<h2>EXAMPLES</h2>
-
-Renaming a column:<br>
-<div class="code"><pre>
-v.info -c myroads
-v.db.renamecol myroads column=label,roadtype
-v.info -c myroads
-</pre></div>
-
-<h2>SEE ALSO</h2>
-
-<em><a HREF="db.execute.html">db.execute</a></em>,
-<em><a HREF="v.db.addcol.html">v.db.addcol</a></em>,
-<em><a HREF="v.db.addtable.html">v.db.addtable</a></em>,
-<em><a HREF="v.db.connect.html">v.db.connect</a></em>,
-<em><a HREF="v.db.dropcol.html">v.db.dropcol</a></em>,
-<em><a HREF="v.db.droptable.html">v.db.droptable</a></em>,
-<em><a HREF="v.db.select.html">v.db.select</a></em>,
-<em><a HREF="v.db.update.html">v.db.update</a></em>
-
-
-<h2>AUTHOR</h2>
-
-Markus Neteler
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/scripts/v.db.renamecol/v.db.renamecol.html (from rev 32770, grass/trunk/scripts/v.db.renamecol/description.html)
===================================================================
--- grass/trunk/scripts/v.db.renamecol/v.db.renamecol.html (rev 0)
+++ grass/trunk/scripts/v.db.renamecol/v.db.renamecol.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,50 @@
+<h2>DESCRIPTION</h2>
+
+<em>v.db.renamecol</em> renames a column in the attribute table connected
+to a given vector map. It automatically checks the connection for the specified
+layer.
+
+<h2>NOTES</h2>
+
+If the map table is connected through the DBF or SQLite drivers, the renaming
+is internally done by adding a new column with new name, transferring the contents
+of the old column to the new column and dropping the old column. This is needed
+as DBF or SQLite do not support "ALTER TABLE" command to rename columns. Due to
+this the renamed column is found as last column of the table, it's original position
+cannot be maintained.
+
+<p>
+The SQLite driver will exit with an error if the column rename involves only a change of
+case, i.e., upper-to-lowercase, or lower-to-uppercase. The SQLite protocol considers "NAME"
+and "name" to be identical column names. In cases like these, the user should rename the original
+column to an intermediary name, then rename the intermediary to the final name.
+
+<p>
+
+
+<h2>EXAMPLES</h2>
+
+Renaming a column:<br>
+<div class="code"><pre>
+v.info -c myroads
+v.db.renamecol myroads column=label,roadtype
+v.info -c myroads
+</pre></div>
+
+<h2>SEE ALSO</h2>
+
+<em><a HREF="db.execute.html">db.execute</a></em>,
+<em><a HREF="v.db.addcol.html">v.db.addcol</a></em>,
+<em><a HREF="v.db.addtable.html">v.db.addtable</a></em>,
+<em><a HREF="v.db.connect.html">v.db.connect</a></em>,
+<em><a HREF="v.db.dropcol.html">v.db.dropcol</a></em>,
+<em><a HREF="v.db.droptable.html">v.db.droptable</a></em>,
+<em><a HREF="v.db.select.html">v.db.select</a></em>,
+<em><a HREF="v.db.update.html">v.db.update</a></em>
+
+
+<h2>AUTHOR</h2>
+
+Markus Neteler
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/scripts/v.db.univar/description.html
===================================================================
--- grass/trunk/scripts/v.db.univar/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/scripts/v.db.univar/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,42 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-
-<EM><b>v.db.univar</b></EM> - Calculates basic univariate statistics for numeric
-attributes in a data table. It will calculate minimum, maximum, range, mean,
-standard deviation, variance, coefficient of variation, quartiles, median, and
-90th percentile.
-It uses <em>db.select</em> to create list values for statistical calculations.
-
-<EM>(GRASS Shell Script)</EM>
-
-<H2>NOTES</H2>
-
-If the database and driver are not specified, the default values set in
-<em>db.connect</em> will be used.
-
-<H2>EXAMPLE</H2>
-
-<div class="code"><pre>
-g.region rast=elevation.10m -p
-v.random out=samples n=100
-v.db.addtable samples col="heights double precision"
-v.what.rast samples rast=elevation.10m col=heights
-v.db.select samples
-
-v.db.univar samples col=heights
-</pre></div>
-
-<H2>SEE ALSO</H2>
-
-<EM>
-<A HREF="r.univar.html">r.univar</A>,
-<A HREF="v.univar.html">v.univar,</A>,
-<A HREF="db.select.html">db.select</A>,
-<A HREF="d.vect.thematic.html">d.vect.thematic</A></EM>
-
-<H2>AUTHOR</H2>
- Michael Barton, Arizona State University
-<p>
-and authors of <em>r.univar.sh</em>
-<p>
-<i>Last changed: $Date$</i>
Copied: grass/trunk/scripts/v.db.univar/v.db.univar.html (from rev 32770, grass/trunk/scripts/v.db.univar/description.html)
===================================================================
--- grass/trunk/scripts/v.db.univar/v.db.univar.html (rev 0)
+++ grass/trunk/scripts/v.db.univar/v.db.univar.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,42 @@
+<H2>DESCRIPTION</H2>
+
+
+<EM><b>v.db.univar</b></EM> - Calculates basic univariate statistics for numeric
+attributes in a data table. It will calculate minimum, maximum, range, mean,
+standard deviation, variance, coefficient of variation, quartiles, median, and
+90th percentile.
+It uses <em>db.select</em> to create list values for statistical calculations.
+
+<EM>(GRASS Shell Script)</EM>
+
+<H2>NOTES</H2>
+
+If the database and driver are not specified, the default values set in
+<em>db.connect</em> will be used.
+
+<H2>EXAMPLE</H2>
+
+<div class="code"><pre>
+g.region rast=elevation.10m -p
+v.random out=samples n=100
+v.db.addtable samples col="heights double precision"
+v.what.rast samples rast=elevation.10m col=heights
+v.db.select samples
+
+v.db.univar samples col=heights
+</pre></div>
+
+<H2>SEE ALSO</H2>
+
+<EM>
+<A HREF="r.univar.html">r.univar</A>,
+<A HREF="v.univar.html">v.univar,</A>,
+<A HREF="db.select.html">db.select</A>,
+<A HREF="d.vect.thematic.html">d.vect.thematic</A></EM>
+
+<H2>AUTHOR</H2>
+ Michael Barton, Arizona State University
+<p>
+and authors of <em>r.univar.sh</em>
+<p>
+<i>Last changed: $Date$</i>
Deleted: grass/trunk/scripts/v.db.update/description.html
===================================================================
--- grass/trunk/scripts/v.db.update/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/scripts/v.db.update/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,55 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>v.db.update</em> allows to assign a new value to a column in the
-attribute table connected to a given map. Alternatively, values can
-be copied from another column in the table.
-
-<h2>NOTES</h2>
-
-<em>v.db.update</em> is just a front-end to <em>db.execute</em> to allow easier usage.
-For complex SQL UPDATE statements, <em>db.execute</em> should be used.
-
-<h2>EXAMPLES</h2>
-
-Spearfish: adding new column, inserting selectively a specified value:
-<div class="code"><pre>
-g.copy vect=fields,myfields
-v.db.addcol myfields col="polynum integer"
-v.db.update myfields col=polynum val=42 where="label='V. White#1'"
-v.db.select myfields
-</pre></div>
-
-<p>
-Spearfish: adding new column, copying values from other table column with
-on the fly calculation:
-<div class="code"><pre>
-g.copy vect=fields,myfields
-v.db.addcol myfields col="polynum integer"
-v.db.update myfields col=polynum qcol="cat*2"
-v.db.select myfields
-</pre></div>
-
-<p>
-Type cast (type conversion) of strings to double precision (unsupported by DBF driver):
-<div class="code"><pre>
-v.db.update mygeodetic_pts col=zval qcol="CAST(z_value AS double precision)" \
- where="z_value <> 'N/A'"
-</pre></div>
-
-<h2>SEE ALSO</h2>
-
-<em><a HREF="db.execute.html">db.execute</a></em>,
-<em><a HREF="v.db.addcol.html">v.db.addcol</a></em>,
-<em><a HREF="v.db.addtable.html">v.db.addtable</a></em>,
-<em><a HREF="v.db.connect.html">v.db.connect</a></em>,
-<em><a HREF="v.db.droptable.html">v.db.droptable</a></em>,
-<em><a HREF="v.db.join.html">v.db.join</a></em>,
-<em><a HREF="v.db.select.html">v.db.select</a></em><br>
-<em><a href="sql.html">GRASS SQL interface</a></em>
-
-
-<h2>AUTHOR</h2>
-
-Moritz Lennert (mlennert at club.worldonline.be)
-
-<p><i>Last changed: $Date$</i></p>
Copied: grass/trunk/scripts/v.db.update/v.db.update.html (from rev 32770, grass/trunk/scripts/v.db.update/description.html)
===================================================================
--- grass/trunk/scripts/v.db.update/v.db.update.html (rev 0)
+++ grass/trunk/scripts/v.db.update/v.db.update.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,55 @@
+<h2>DESCRIPTION</h2>
+
+<em>v.db.update</em> allows to assign a new value to a column in the
+attribute table connected to a given map. Alternatively, values can
+be copied from another column in the table.
+
+<h2>NOTES</h2>
+
+<em>v.db.update</em> is just a front-end to <em>db.execute</em> to allow easier usage.
+For complex SQL UPDATE statements, <em>db.execute</em> should be used.
+
+<h2>EXAMPLES</h2>
+
+Spearfish: adding new column, inserting selectively a specified value:
+<div class="code"><pre>
+g.copy vect=fields,myfields
+v.db.addcol myfields col="polynum integer"
+v.db.update myfields col=polynum val=42 where="label='V. White#1'"
+v.db.select myfields
+</pre></div>
+
+<p>
+Spearfish: adding new column, copying values from other table column with
+on the fly calculation:
+<div class="code"><pre>
+g.copy vect=fields,myfields
+v.db.addcol myfields col="polynum integer"
+v.db.update myfields col=polynum qcol="cat*2"
+v.db.select myfields
+</pre></div>
+
+<p>
+Type cast (type conversion) of strings to double precision (unsupported by DBF driver):
+<div class="code"><pre>
+v.db.update mygeodetic_pts col=zval qcol="CAST(z_value AS double precision)" \
+ where="z_value <> 'N/A'"
+</pre></div>
+
+<h2>SEE ALSO</h2>
+
+<em><a HREF="db.execute.html">db.execute</a></em>,
+<em><a HREF="v.db.addcol.html">v.db.addcol</a></em>,
+<em><a HREF="v.db.addtable.html">v.db.addtable</a></em>,
+<em><a HREF="v.db.connect.html">v.db.connect</a></em>,
+<em><a HREF="v.db.droptable.html">v.db.droptable</a></em>,
+<em><a HREF="v.db.join.html">v.db.join</a></em>,
+<em><a HREF="v.db.select.html">v.db.select</a></em><br>
+<em><a href="sql.html">GRASS SQL interface</a></em>
+
+
+<h2>AUTHOR</h2>
+
+Moritz Lennert (mlennert at club.worldonline.be)
+
+<p><i>Last changed: $Date$</i></p>
Deleted: grass/trunk/scripts/v.dissolve/description.html
===================================================================
--- grass/trunk/scripts/v.dissolve/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/scripts/v.dissolve/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,75 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-The <EM>v.dissolve</EM> module is used to merge adjacent areas in a vector
-map which share the same category value. The resulting merged area(s) retains
-this category value. Optionally, a column can be defined which is used
-to find adjacent polygons with identical attribute for common boundary
-dissolving.
-
-GRASS defines a vector area as composite entity consisting of a set of
-closed boundaries and a centroid. The centroids must contain a
-category number
-(see <em><a href="v.centroids.html">v.centroids</a></em>), this number
-is linked to area attributes and database links.
-
-Multiple attributes may be linked to a single vector entity through
-numbered fields referred to as layers. Refer
-to <em><a href="v.category.html">v.category</a></em> for more details.
-
-<P>
-Merging of areas can also be accomplished using
-"<em>v.extract <b>-d</b></em>" which provides some additional options.
-In fact, <a href="v.dissolve.html">v.dissolve</a> is simply a
-front-end to that module. The use of the <EM>column</EM> parameter
-adds a call to <em><a href="v.reclass.html">v.reclass</a></em> before.
-
-<h2>EXAMPLES</h2>
-
-<h3>Basic use</h3>
-<div class="code"><pre>
-v.dissolve input=undissolved output=dissolved
-</pre></div>
-
-<h3>Dissolving based on column attributes</h3>
-<div class="code"><pre>
-# check column names:
-v.info -c polbnda_italy
-
-# dissolve based on column attributes:
-v.dissolve input=polbnda_italy output=pol_italy_regions col=vmap_nam
-</pre></div>
-
-<h3>Dissolving adjacent SHAPE files to remove tile boundaries</h3>
-
-If tile boundaries of adjacent maps (e.g. CORINE Landcover SHAPE files)
-have to be removed, an extra step is required to remove duplicated
-boundaries:
-
-<div class="code"><pre>
-# patch tiles after import:
-v.patch -e `g.mlist type=vect pat="clc2000_*" sep=,` out=clc2000_patched
-
-# remove duplicated tile boundaries:
-v.clean clc2000_patched out=clc2000_clean tool=snap,break,rmdupl thresh=.01
-
-# dissolve based on column attributes:
-v.dissolve input=clc2000_clean output=clc2000_final col=CODE_00
-</pre></div>
-
-<H2>SEE ALSO</H2>
-
-<EM>
-<A HREF="v.category.html">v.category</A>,
-<A HREF="v.centroids.html">v.centroids</A>,
-<A HREF="v.extract.html">v.extract</A>,
-<A HREF="v.reclass.html">v.reclass</A>
-</EM>
-
-<H2>AUTHORS</H2>
-
-module: M. Hamish Bowman, Dept. Marine Science, Otago University, New Zealand<br>
-Markus Neteler for column support<BR>
-help page: Trevor Wiens
-
-<P>
-<i>Last changed: $Date$</i>
Copied: grass/trunk/scripts/v.dissolve/v.dissolve.html (from rev 32770, grass/trunk/scripts/v.dissolve/description.html)
===================================================================
--- grass/trunk/scripts/v.dissolve/v.dissolve.html (rev 0)
+++ grass/trunk/scripts/v.dissolve/v.dissolve.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,75 @@
+<H2>DESCRIPTION</H2>
+
+The <EM>v.dissolve</EM> module is used to merge adjacent areas in a vector
+map which share the same category value. The resulting merged area(s) retains
+this category value. Optionally, a column can be defined which is used
+to find adjacent polygons with identical attribute for common boundary
+dissolving.
+
+GRASS defines a vector area as composite entity consisting of a set of
+closed boundaries and a centroid. The centroids must contain a
+category number
+(see <em><a href="v.centroids.html">v.centroids</a></em>), this number
+is linked to area attributes and database links.
+
+Multiple attributes may be linked to a single vector entity through
+numbered fields referred to as layers. Refer
+to <em><a href="v.category.html">v.category</a></em> for more details.
+
+<P>
+Merging of areas can also be accomplished using
+"<em>v.extract <b>-d</b></em>" which provides some additional options.
+In fact, <a href="v.dissolve.html">v.dissolve</a> is simply a
+front-end to that module. The use of the <EM>column</EM> parameter
+adds a call to <em><a href="v.reclass.html">v.reclass</a></em> before.
+
+<h2>EXAMPLES</h2>
+
+<h3>Basic use</h3>
+<div class="code"><pre>
+v.dissolve input=undissolved output=dissolved
+</pre></div>
+
+<h3>Dissolving based on column attributes</h3>
+<div class="code"><pre>
+# check column names:
+v.info -c polbnda_italy
+
+# dissolve based on column attributes:
+v.dissolve input=polbnda_italy output=pol_italy_regions col=vmap_nam
+</pre></div>
+
+<h3>Dissolving adjacent SHAPE files to remove tile boundaries</h3>
+
+If tile boundaries of adjacent maps (e.g. CORINE Landcover SHAPE files)
+have to be removed, an extra step is required to remove duplicated
+boundaries:
+
+<div class="code"><pre>
+# patch tiles after import:
+v.patch -e `g.mlist type=vect pat="clc2000_*" sep=,` out=clc2000_patched
+
+# remove duplicated tile boundaries:
+v.clean clc2000_patched out=clc2000_clean tool=snap,break,rmdupl thresh=.01
+
+# dissolve based on column attributes:
+v.dissolve input=clc2000_clean output=clc2000_final col=CODE_00
+</pre></div>
+
+<H2>SEE ALSO</H2>
+
+<EM>
+<A HREF="v.category.html">v.category</A>,
+<A HREF="v.centroids.html">v.centroids</A>,
+<A HREF="v.extract.html">v.extract</A>,
+<A HREF="v.reclass.html">v.reclass</A>
+</EM>
+
+<H2>AUTHORS</H2>
+
+module: M. Hamish Bowman, Dept. Marine Science, Otago University, New Zealand<br>
+Markus Neteler for column support<BR>
+help page: Trevor Wiens
+
+<P>
+<i>Last changed: $Date$</i>
Deleted: grass/trunk/scripts/v.in.e00/description.html
===================================================================
--- grass/trunk/scripts/v.in.e00/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/scripts/v.in.e00/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,25 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>v.in.e00</em> imports ASCII and binary E00 vector maps into GRASS.
-
-<h2>NOTES</h2>
-
-Sometimes an .e00 coverage consists of multiple files, where a single
-data set is contained as a series of files named filename.e00, filename.e01,
-filename.e02 etc. The user must take care to download them all, the scripts
-automatically detects the presence of such multiple files.
-
-<H2>REFERENCES</H2>
-
-<a href="http://avce00.maptools.org">AVCE00 library</a> (providing 'avcimport' and 'e00conv')<br>
-<a href="http://www.remotesensing.org/gdal/ogr/">OGR vector library</a>
-
-<h2>SEE ALSO</h2>
-
-<em><a HREF="v.in.ogr.html">v.in.ogr</a></em>
-
-<h2>AUTHOR</h2>
-
-Markus Neteler, Otto Dassau, <a href=http://www.gdf-hannover.de>GDF Hannover bR</a>, Germany
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/scripts/v.in.e00/v.in.e00.html (from rev 32770, grass/trunk/scripts/v.in.e00/description.html)
===================================================================
--- grass/trunk/scripts/v.in.e00/v.in.e00.html (rev 0)
+++ grass/trunk/scripts/v.in.e00/v.in.e00.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,25 @@
+<h2>DESCRIPTION</h2>
+
+<em>v.in.e00</em> imports ASCII and binary E00 vector maps into GRASS.
+
+<h2>NOTES</h2>
+
+Sometimes an .e00 coverage consists of multiple files, where a single
+data set is contained as a series of files named filename.e00, filename.e01,
+filename.e02 etc. The user must take care to download them all, the scripts
+automatically detects the presence of such multiple files.
+
+<H2>REFERENCES</H2>
+
+<a href="http://avce00.maptools.org">AVCE00 library</a> (providing 'avcimport' and 'e00conv')<br>
+<a href="http://www.remotesensing.org/gdal/ogr/">OGR vector library</a>
+
+<h2>SEE ALSO</h2>
+
+<em><a HREF="v.in.ogr.html">v.in.ogr</a></em>
+
+<h2>AUTHOR</h2>
+
+Markus Neteler, Otto Dassau, <a href=http://www.gdf-hannover.de>GDF Hannover bR</a>, Germany
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/scripts/v.in.garmin/description.html
===================================================================
--- grass/trunk/scripts/v.in.garmin/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/scripts/v.in.garmin/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,76 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-<EM>v.in.garmin</EM> allows the user to import waypoint, route, and track
- data from a locally connected Garmin GPS receiver via the
-<EM><A HREF="http://gpstrans.sourceforge.net">gpstrans</a></EM>
- program by Carsten Tschach or the
-<EM><A HREF="http://www.snafu.org">gardump</a></EM>
- program by Marc Hyman.
-
-<P>
-Use at your own risk. This software comes with absolutely no warranty.
-
-<P>
-<H2>NOTES</H2>
-If the GPS is set up to output WGS84 Lat/Lon, <em>v.in.garmin</em> will
-attempt to automatically transform the coordinates to the current projection.
-In all other cases, no checks are performed for datum, projection and format of data.
-You must check for yourself that your receiver, gpstrans and GRASS
-use the same map datum and projection.
-The automatic transform may be skipped by using the <b>-k</b> flag.
-
-<P>
-Route and Track data may be uploaded as points by using the <B>-p</B> flag,
-otherwise they will be imported as a line. You can run <EM>v.in.garmin</EM>
-multiple times and merge the line and point vectors with the <EM>v.patch</EM>
-command if you want, but take care when merging dissimilar attribute tables.
-
-<P>
-Future versions of GRASS will use <em>gardump</em> as the default download
-program. It can talk to newer Garmin GPSs, while <em>gpstrans</em> seems to
-be mostly abandoned these days and only works with older GPSs. The current
-version of <em>gardump</em> (ver 2.5) will not yet talk to USB-only GPSs, but
-you can try the <em>v.in.gpsbabel</em> module for those. The <em>gardump</em>
-code has been tested with an older Garmin GPS 45 and a newer GPS V and is
-expected to work with everything in between.
-
-<P>
-Before running <EM>v.in.garmin</EM>, <em>gpstrans</em> should be set up
-to output WGS84 latitude-longitude, as follows: <BR>
-<tt>
-$ <B>gpstrans -s</B><BR>
-datum: 100 (WGS84)<BR>
-format: 2 - lat/lon ddd.ddddd<BR>
-</tt>
-
-<P>
-<H2>SEE ALSO</H2>
-<EM>
-<A HREF="db.execute.html">db.execute</A><BR>
-<A HREF="v.in.ascii.html">v.in.ascii</A><BR>
-<A HREF="v.in.gpsbabel.html">v.in.gpsbabel</A><BR>
-<A HREF="v.db.connect.html">v.db.connect</A><BR>
-<A HREF="v.patch.html">v.patch</A>
-</EM>
-<BR>
-<BR>
-
-<A HREF="http://gpstrans.sourceforge.net">gpstrans</a> manual<BR>
-<A HREF="http://www.snafu.org">gardump</a> from the "garmin-utils" package<BR>
-cs2cs from <A HREF="http://proj.maptools.org">PROJ.4</a><BR>
-The <tt>awk</tt> user manual
-
-<P>
-<H2>AUTHORS</H2>
-Based on <em>v.in.garmin.sh</em> for GRASS 5.0 by Andreas Lange
-<BR>
-with bug fixes by Glynn Clements and Markus Neteler
-<BR>Rewritten for GRASS 5.3 and 5.7 by Hamish Bowman
-<BR><tt>gardump</tt> and 3D track support by Hamish Bowman
-<P>
-gpstrans was written by Carsten Tschach<BR>
-gardump was written by Marc Hyman<BR>
-<BR>
-
-<p>
-<i>Last changed: $Date$</i>
Copied: grass/trunk/scripts/v.in.garmin/v.in.garmin.html (from rev 32770, grass/trunk/scripts/v.in.garmin/description.html)
===================================================================
--- grass/trunk/scripts/v.in.garmin/v.in.garmin.html (rev 0)
+++ grass/trunk/scripts/v.in.garmin/v.in.garmin.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,76 @@
+<H2>DESCRIPTION</H2>
+
+<EM>v.in.garmin</EM> allows the user to import waypoint, route, and track
+ data from a locally connected Garmin GPS receiver via the
+<EM><A HREF="http://gpstrans.sourceforge.net">gpstrans</a></EM>
+ program by Carsten Tschach or the
+<EM><A HREF="http://www.snafu.org">gardump</a></EM>
+ program by Marc Hyman.
+
+<P>
+Use at your own risk. This software comes with absolutely no warranty.
+
+<P>
+<H2>NOTES</H2>
+If the GPS is set up to output WGS84 Lat/Lon, <em>v.in.garmin</em> will
+attempt to automatically transform the coordinates to the current projection.
+In all other cases, no checks are performed for datum, projection and format of data.
+You must check for yourself that your receiver, gpstrans and GRASS
+use the same map datum and projection.
+The automatic transform may be skipped by using the <b>-k</b> flag.
+
+<P>
+Route and Track data may be uploaded as points by using the <B>-p</B> flag,
+otherwise they will be imported as a line. You can run <EM>v.in.garmin</EM>
+multiple times and merge the line and point vectors with the <EM>v.patch</EM>
+command if you want, but take care when merging dissimilar attribute tables.
+
+<P>
+Future versions of GRASS will use <em>gardump</em> as the default download
+program. It can talk to newer Garmin GPSs, while <em>gpstrans</em> seems to
+be mostly abandoned these days and only works with older GPSs. The current
+version of <em>gardump</em> (ver 2.5) will not yet talk to USB-only GPSs, but
+you can try the <em>v.in.gpsbabel</em> module for those. The <em>gardump</em>
+code has been tested with an older Garmin GPS 45 and a newer GPS V and is
+expected to work with everything in between.
+
+<P>
+Before running <EM>v.in.garmin</EM>, <em>gpstrans</em> should be set up
+to output WGS84 latitude-longitude, as follows: <BR>
+<tt>
+$ <B>gpstrans -s</B><BR>
+datum: 100 (WGS84)<BR>
+format: 2 - lat/lon ddd.ddddd<BR>
+</tt>
+
+<P>
+<H2>SEE ALSO</H2>
+<EM>
+<A HREF="db.execute.html">db.execute</A><BR>
+<A HREF="v.in.ascii.html">v.in.ascii</A><BR>
+<A HREF="v.in.gpsbabel.html">v.in.gpsbabel</A><BR>
+<A HREF="v.db.connect.html">v.db.connect</A><BR>
+<A HREF="v.patch.html">v.patch</A>
+</EM>
+<BR>
+<BR>
+
+<A HREF="http://gpstrans.sourceforge.net">gpstrans</a> manual<BR>
+<A HREF="http://www.snafu.org">gardump</a> from the "garmin-utils" package<BR>
+cs2cs from <A HREF="http://proj.maptools.org">PROJ.4</a><BR>
+The <tt>awk</tt> user manual
+
+<P>
+<H2>AUTHORS</H2>
+Based on <em>v.in.garmin.sh</em> for GRASS 5.0 by Andreas Lange
+<BR>
+with bug fixes by Glynn Clements and Markus Neteler
+<BR>Rewritten for GRASS 5.3 and 5.7 by Hamish Bowman
+<BR><tt>gardump</tt> and 3D track support by Hamish Bowman
+<P>
+gpstrans was written by Carsten Tschach<BR>
+gardump was written by Marc Hyman<BR>
+<BR>
+
+<p>
+<i>Last changed: $Date$</i>
Deleted: grass/trunk/scripts/v.in.geonames/description.html
===================================================================
--- grass/trunk/scripts/v.in.geonames/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/scripts/v.in.geonames/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,61 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>v.in.geonames</em> imports Geonames.org country
-files (Gazetteer data) into a GRASS vector points map. The country files
-can be downloaded from the
-<a href="http://download.geonames.org/export/dump/">GeoNames Data Dump Server</a>.
-The script generates a vector point map. Only original files can be processed
-(unzip compressed file first). These Geonames files are encoded in UTF-8 which
-is maintained in the GRASS database.
-
-<h2>NOTES</h2>
-
-The current DB connection is used to write the database table.
-<P>
-If importing into a DBF database, the original column names longer that 10 characters
-are shortened to 10 characters to meet the DBF column name restrictions. If this is a
-problem consider choosing another database driver with <em>db.connect</em>.
-
-The main 'geoname' table has the following fields
-
-<pre>
-geonameid : integer id of record in geonames database
-name : name of geographical point (utf8) varchar(200)
-asciiname : name of geographical point in plain ascii characters, varchar(200)
-alternatenames : alternatenames, comma separated varchar(4000)
-latitude : latitude in decimal degrees (wgs84)
-longitude : longitude in decimal degrees (wgs84)
-feature class : see http://www.geonames.org/export/codes.html, char(1)
-feature code : see http://www.geonames.org/export/codes.html, varchar(10)
-country code : ISO-3166 2-letter country code, 2 characters
-cc2 : alternate country codes, comma separated, ISO-3166 2-letter country code, 60 characters
-admin1 code : fipscode (subject to change to iso code), isocode for the us and ch, see file admin1Codes.txt for display names of this code; varchar(20)
-admin2 code : code for the second administrative division, a county in the US, see file admin2Codes.txt; varchar(80)
-admin3 code : code for third level administrative division, varchar(20)
-admin4 code : code for fourth level administrative division, varchar(20)
-population : integer
-elevation : in meters, integer
-gtopo30 : average elevation of 30'x30' (ca 900mx900m) area in meters, integer
-timezone : the timezone id (see file http://download.geonames.org/export/dump/timeZones.txt)
-modification date : date of last modification in yyyy-MM-dd format
-</pre>
-
-
-<h2>SEE ALSO</h2>
-
-<em>
-<a HREF="db.connect.html">db.connect</a>,
-<a HREF="v.select.html">v.select</a>
-</em>
-
-<H2>REFERENCES</H2>
-
-<a href="http://www.geonames.org">GeoNames Web site</a><br>
-<a href="http://download.geonames.org/export/dump/">GeoNames Data Dump Server</a>
-
-<h2>AUTHOR</h2>
-
-<a href="http://www.grassbook.org/">Markus Neteler</a>
-
-<p>
-<i>Last changed: $Date: 2008-03-13 09:01:14 +0100 (Thu, 13 Mar 2008) $</i>
Copied: grass/trunk/scripts/v.in.geonames/v.in.geonames.html (from rev 32770, grass/trunk/scripts/v.in.geonames/description.html)
===================================================================
--- grass/trunk/scripts/v.in.geonames/v.in.geonames.html (rev 0)
+++ grass/trunk/scripts/v.in.geonames/v.in.geonames.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,61 @@
+<h2>DESCRIPTION</h2>
+
+<em>v.in.geonames</em> imports Geonames.org country
+files (Gazetteer data) into a GRASS vector points map. The country files
+can be downloaded from the
+<a href="http://download.geonames.org/export/dump/">GeoNames Data Dump Server</a>.
+The script generates a vector point map. Only original files can be processed
+(unzip compressed file first). These Geonames files are encoded in UTF-8 which
+is maintained in the GRASS database.
+
+<h2>NOTES</h2>
+
+The current DB connection is used to write the database table.
+<P>
+If importing into a DBF database, the original column names longer that 10 characters
+are shortened to 10 characters to meet the DBF column name restrictions. If this is a
+problem consider choosing another database driver with <em>db.connect</em>.
+
+The main 'geoname' table has the following fields
+
+<pre>
+geonameid : integer id of record in geonames database
+name : name of geographical point (utf8) varchar(200)
+asciiname : name of geographical point in plain ascii characters, varchar(200)
+alternatenames : alternatenames, comma separated varchar(4000)
+latitude : latitude in decimal degrees (wgs84)
+longitude : longitude in decimal degrees (wgs84)
+feature class : see http://www.geonames.org/export/codes.html, char(1)
+feature code : see http://www.geonames.org/export/codes.html, varchar(10)
+country code : ISO-3166 2-letter country code, 2 characters
+cc2 : alternate country codes, comma separated, ISO-3166 2-letter country code, 60 characters
+admin1 code : fipscode (subject to change to iso code), isocode for the us and ch, see file admin1Codes.txt for display names of this code; varchar(20)
+admin2 code : code for the second administrative division, a county in the US, see file admin2Codes.txt; varchar(80)
+admin3 code : code for third level administrative division, varchar(20)
+admin4 code : code for fourth level administrative division, varchar(20)
+population : integer
+elevation : in meters, integer
+gtopo30 : average elevation of 30'x30' (ca 900mx900m) area in meters, integer
+timezone : the timezone id (see file http://download.geonames.org/export/dump/timeZones.txt)
+modification date : date of last modification in yyyy-MM-dd format
+</pre>
+
+
+<h2>SEE ALSO</h2>
+
+<em>
+<a HREF="db.connect.html">db.connect</a>,
+<a HREF="v.select.html">v.select</a>
+</em>
+
+<H2>REFERENCES</H2>
+
+<a href="http://www.geonames.org">GeoNames Web site</a><br>
+<a href="http://download.geonames.org/export/dump/">GeoNames Data Dump Server</a>
+
+<h2>AUTHOR</h2>
+
+<a href="http://www.grassbook.org/">Markus Neteler</a>
+
+<p>
+<i>Last changed: $Date: 2008-03-13 09:01:14 +0100 (Thu, 13 Mar 2008) $</i>
Deleted: grass/trunk/scripts/v.in.gns/description.html
===================================================================
--- grass/trunk/scripts/v.in.gns/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/scripts/v.in.gns/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,40 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>v.in.gns</em> imports US-NGA GEOnet Names Server (GNS) country
-files (Gazetteer data) into a GRASS vector points map. The country files
-can be downloaded from the NGA GNS Web Server (see below). The script
-generates a vector point map. Only original files can be processed
-(unzip compressed file first). These GNS files are encoded in UTF-8 which
-is maintained in the GRASS database.
-
-<h2>NOTES</h2>
-
-The current DB connection is used to write the database table.
-<P>
-Generally, column names longer that 10 characters are shortened to
-10 characters to meet the DBF column name restrictions. If this is a
-problem consider choosing another database driver with <em>db.connect</em>.
-<P>
-To filter outliers (points outside of a country), the <em>v.select</em>
-module can be used to perform point-in-polygon tests. <em>v.select</em>
-saves only the GNS points falling into a country polygon into the new
-points map.
-
-<h2>SEE ALSO</h2>
-
-<em>
-<a HREF="db.connect.html">db.connect</a>,
-<a HREF="v.select.html">v.select</a>
-</em>
-
-<H2>REFERENCES</H2>
-
-<a href="http://earth-info.nga.mil/gns/html/">GEOnet Names Server files for countries and territories</a><br>
-<a href="http://earth-info.nga.mil/gns/html/help.htm">Column names explanations</a>
-
-<h2>AUTHOR</h2>
-
-Markus Neteler, <a href=http://mpa.itc.it>MPBA Group, ITC-irst</a>
-
-<p>
-<i>Last changed: $Date$</i>
Copied: grass/trunk/scripts/v.in.gns/v.in.gns.html (from rev 32770, grass/trunk/scripts/v.in.gns/description.html)
===================================================================
--- grass/trunk/scripts/v.in.gns/v.in.gns.html (rev 0)
+++ grass/trunk/scripts/v.in.gns/v.in.gns.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,40 @@
+<h2>DESCRIPTION</h2>
+
+<em>v.in.gns</em> imports US-NGA GEOnet Names Server (GNS) country
+files (Gazetteer data) into a GRASS vector points map. The country files
+can be downloaded from the NGA GNS Web Server (see below). The script
+generates a vector point map. Only original files can be processed
+(unzip compressed file first). These GNS files are encoded in UTF-8 which
+is maintained in the GRASS database.
+
+<h2>NOTES</h2>
+
+The current DB connection is used to write the database table.
+<P>
+Generally, column names longer that 10 characters are shortened to
+10 characters to meet the DBF column name restrictions. If this is a
+problem consider choosing another database driver with <em>db.connect</em>.
+<P>
+To filter outliers (points outside of a country), the <em>v.select</em>
+module can be used to perform point-in-polygon tests. <em>v.select</em>
+saves only the GNS points falling into a country polygon into the new
+points map.
+
+<h2>SEE ALSO</h2>
+
+<em>
+<a HREF="db.connect.html">db.connect</a>,
+<a HREF="v.select.html">v.select</a>
+</em>
+
+<H2>REFERENCES</H2>
+
+<a href="http://earth-info.nga.mil/gns/html/">GEOnet Names Server files for countries and territories</a><br>
+<a href="http://earth-info.nga.mil/gns/html/help.htm">Column names explanations</a>
+
+<h2>AUTHOR</h2>
+
+Markus Neteler, <a href=http://mpa.itc.it>MPBA Group, ITC-irst</a>
+
+<p>
+<i>Last changed: $Date$</i>
Deleted: grass/trunk/scripts/v.in.gpsbabel/description.html
===================================================================
--- grass/trunk/scripts/v.in.gpsbabel/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/scripts/v.in.gpsbabel/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,100 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-<EM>v.in.gpsbabel</EM> allows the user to import waypoint, route, and track
-data from a locally connected GPS receiver or a text file containing
-GPS data of many common formats. Translation is done via the
-<EM><A HREF="http://www.gpsbabel.org">gpsbabel</a></EM> program.
-
-<P>
-This software is not intended as a primary means of navigation.
-
-<H2>NOTES</H2>
-
-<em>v.in.gpsbabel</em> automatically reprojects data using the
-projection settings of the current location.
-
-The default input data projection is lat/lon WGS84. If your GPS outputs data
-using another projection or map datum, you may include the
-<EM><A HREF="http://proj.maptools.org">PROJ.4</a></EM>
-parameters defining your projection in the <b>proj</b> option and
-<em>v.in.gpsbabel</em> will reproject your data accordingly.
-Great care must be taken to get these parameters correct!
-
-The automatic transform may be skipped by using the <b>-k</b> flag in which
-case the data will be imported unprojected, as it appears in the <b>input</b>.
-
-<P>
-Route and Track data may be uploaded as a series of points by using the <B>-p</B>
-flag, otherwise they will be imported as lines. You can run <EM>v.in.gpsbabel</EM>
-multiple times and merge the line and point vectors with the <EM>v.patch</EM>
-command if you want, but take care when merging dissimilar attribute tables.
-
-<H2>EXAMPLES</H2>
-
-<h3>GPS device connected via USB adapter</h3>
-
-Import waypoints, tracks, routes from /dev/ttyUSB0 and save
-to a GRASS vector map:
-<div class="code"><pre>
-v.in.gpsbabel -w input=/dev/ttyUSB0 format=garmin output=waypoints
-v.in.gpsbabel -t input=/dev/ttyUSB0 format=garmin output=tracks
-v.in.gpsbabel -r input=/dev/ttyUSB0 format=garmin output=routes
-</pre></div>
-
-<h3>GPS device connected via serial adapter</h3>
-
-Import waypoint data from a Garmin GPS connected at /dev/ttyS0 and save
-to a GRASS vector map named <i>waypoints</i>:
-<div class="code"><pre>
-v.in.gpsbabel -w input=/dev/ttyS0 format=garmin output=waypoints
-</pre></div>
-
-<h3>Import track data from a GPX</h3>
-
-Import track data from a GPX text file and save to a GRASS vector map
-named <i>tracks</i>.
-<!-- (currently buggy) The gpxlogger program distributed with
-<a href="http://gpsd.berlios.de/">GPSd</a> >2.30 is a good program for
-creating these logs. -->
-<div class="code"><pre>
-v.in.gpsbabel -t input=gpslog.gpx format=gpx output=tracks
-</pre></div>
-
-<h3>Import route data from GPS connected at /dev/gps</h3>
-
-Import route data as a series of points from a Garmin GPS connected at
-/dev/gps and save to a GRASS vector map named <i>routePoints</i>:
-<div class="code"><pre>
-v.in.gpsbabel -r -p file=/dev/gps format=garmin output=routePoints
-</pre></div>
-
-
-<H2>SEE ALSO</H2>
-<EM><A HREF="db.execute.html">db.execute</A></EM><BR>
-<EM><A HREF="v.in.ascii.html">v.in.ascii</A></EM><BR>
-<EM><A HREF="v.in.garmin.html">v.in.garmin</A></EM><BR>
-<EM><A HREF="v.db.connect.html">v.db.connect</A></EM><BR>
-<EM><A HREF="v.patch.html">v.patch</A></EM><BR>
-<BR>
-
-<A HREF="http://www.gpsbabel.org">gpsbabel</a> from gpsbabel.org<BR>
-cs2cs from <A HREF="http://proj.maptools.org">PROJ.4</a><BR>
-
-<P>
-<H2>AUTHORS</H2>
-Claudio Porta and Lucio Davide Spano, students of Computer Science at
-University of Pisa (Italy).<br>
-Commission from Faunalia Pontedera (PI)<br><br>
-Based on <em>v.in.garmin</em> for GRASS 6.0 by Hamish Bowman<br>
-and <em>v.in.garmin.sh</em> for GRASS 5 by Andreas Lange
-<BR>
-
-<!--
-When we tested the script with a Garmin GPS we noticed that importing waypoints
-the <i>time</i> field is not correctly set. The data reported is
-a default system time, while with a gpx text file this thing did not
-happen. We believe that is a <i>gpsbabel</i> trouble in translating
-from <i>garmin</i> to <i>xcsv</i> ...
--->
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/scripts/v.in.gpsbabel/v.in.gpsbabel.html (from rev 32770, grass/trunk/scripts/v.in.gpsbabel/description.html)
===================================================================
--- grass/trunk/scripts/v.in.gpsbabel/v.in.gpsbabel.html (rev 0)
+++ grass/trunk/scripts/v.in.gpsbabel/v.in.gpsbabel.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,100 @@
+<H2>DESCRIPTION</H2>
+
+<EM>v.in.gpsbabel</EM> allows the user to import waypoint, route, and track
+data from a locally connected GPS receiver or a text file containing
+GPS data of many common formats. Translation is done via the
+<EM><A HREF="http://www.gpsbabel.org">gpsbabel</a></EM> program.
+
+<P>
+This software is not intended as a primary means of navigation.
+
+<H2>NOTES</H2>
+
+<em>v.in.gpsbabel</em> automatically reprojects data using the
+projection settings of the current location.
+
+The default input data projection is lat/lon WGS84. If your GPS outputs data
+using another projection or map datum, you may include the
+<EM><A HREF="http://proj.maptools.org">PROJ.4</a></EM>
+parameters defining your projection in the <b>proj</b> option and
+<em>v.in.gpsbabel</em> will reproject your data accordingly.
+Great care must be taken to get these parameters correct!
+
+The automatic transform may be skipped by using the <b>-k</b> flag in which
+case the data will be imported unprojected, as it appears in the <b>input</b>.
+
+<P>
+Route and Track data may be uploaded as a series of points by using the <B>-p</B>
+flag, otherwise they will be imported as lines. You can run <EM>v.in.gpsbabel</EM>
+multiple times and merge the line and point vectors with the <EM>v.patch</EM>
+command if you want, but take care when merging dissimilar attribute tables.
+
+<H2>EXAMPLES</H2>
+
+<h3>GPS device connected via USB adapter</h3>
+
+Import waypoints, tracks, routes from /dev/ttyUSB0 and save
+to a GRASS vector map:
+<div class="code"><pre>
+v.in.gpsbabel -w input=/dev/ttyUSB0 format=garmin output=waypoints
+v.in.gpsbabel -t input=/dev/ttyUSB0 format=garmin output=tracks
+v.in.gpsbabel -r input=/dev/ttyUSB0 format=garmin output=routes
+</pre></div>
+
+<h3>GPS device connected via serial adapter</h3>
+
+Import waypoint data from a Garmin GPS connected at /dev/ttyS0 and save
+to a GRASS vector map named <i>waypoints</i>:
+<div class="code"><pre>
+v.in.gpsbabel -w input=/dev/ttyS0 format=garmin output=waypoints
+</pre></div>
+
+<h3>Import track data from a GPX</h3>
+
+Import track data from a GPX text file and save to a GRASS vector map
+named <i>tracks</i>.
+<!-- (currently buggy) The gpxlogger program distributed with
+<a href="http://gpsd.berlios.de/">GPSd</a> >2.30 is a good program for
+creating these logs. -->
+<div class="code"><pre>
+v.in.gpsbabel -t input=gpslog.gpx format=gpx output=tracks
+</pre></div>
+
+<h3>Import route data from GPS connected at /dev/gps</h3>
+
+Import route data as a series of points from a Garmin GPS connected at
+/dev/gps and save to a GRASS vector map named <i>routePoints</i>:
+<div class="code"><pre>
+v.in.gpsbabel -r -p file=/dev/gps format=garmin output=routePoints
+</pre></div>
+
+
+<H2>SEE ALSO</H2>
+<EM><A HREF="db.execute.html">db.execute</A></EM><BR>
+<EM><A HREF="v.in.ascii.html">v.in.ascii</A></EM><BR>
+<EM><A HREF="v.in.garmin.html">v.in.garmin</A></EM><BR>
+<EM><A HREF="v.db.connect.html">v.db.connect</A></EM><BR>
+<EM><A HREF="v.patch.html">v.patch</A></EM><BR>
+<BR>
+
+<A HREF="http://www.gpsbabel.org">gpsbabel</a> from gpsbabel.org<BR>
+cs2cs from <A HREF="http://proj.maptools.org">PROJ.4</a><BR>
+
+<P>
+<H2>AUTHORS</H2>
+Claudio Porta and Lucio Davide Spano, students of Computer Science at
+University of Pisa (Italy).<br>
+Commission from Faunalia Pontedera (PI)<br><br>
+Based on <em>v.in.garmin</em> for GRASS 6.0 by Hamish Bowman<br>
+and <em>v.in.garmin.sh</em> for GRASS 5 by Andreas Lange
+<BR>
+
+<!--
+When we tested the script with a Garmin GPS we noticed that importing waypoints
+the <i>time</i> field is not correctly set. The data reported is
+a default system time, while with a gpx text file this thing did not
+happen. We believe that is a <i>gpsbabel</i> trouble in translating
+from <i>garmin</i> to <i>xcsv</i> ...
+-->
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/scripts/v.in.mapgen/description.html
===================================================================
--- grass/trunk/scripts/v.in.mapgen/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/scripts/v.in.mapgen/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,37 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-<EM>v.in.mapgen</EM> allows the user to import Mapgen or Matlab vector maps
-into GRASS.
-
-<H2>NOTES</H2>
-
-This module only imports data into vector lines.
-<P>
-You can get coastline data in Mapgen or Matlab format from NOAA's Coastline
-Extractor at <a href="http://www.ngdc.noaa.gov/mgg/shorelines/shorelines.html">http://www.ngdc.noaa.gov/mgg/shorelines/shorelines.html</a>.
-<P>
-Matlab vector line maps are simply a series of "x y" data points. Lines
-are separated by a row containing <tt>NaN NaN</tt>.
-
-Output from Matlab with this command:
-<BR>
-<div class="code"><pre>
- save filename.txt arrayname -ASCII
-</pre></div>
-<P>
-You can import 3D lines from Matlab by exporting a 3 column array and
-using the <B>-z</B> flag.
-
-
-<H2>SEE ALSO</H2>
-<EM><A HREF="v.in.ascii.html">v.in.ascii</A></EM><BR>
-<BR>
-
-<P>
-<H2>AUTHORS</H2>
-Based on <em>v.in.mapgen.sh</em> for GRASS 5.0 by Andreas Lange
-<BR>Rewritten for GRASS 6 by Hamish Bowman
-<BR>
-
-<p>
-<i>Last changed: $Date$</i>
Copied: grass/trunk/scripts/v.in.mapgen/v.in.mapgen.html (from rev 32770, grass/trunk/scripts/v.in.mapgen/description.html)
===================================================================
--- grass/trunk/scripts/v.in.mapgen/v.in.mapgen.html (rev 0)
+++ grass/trunk/scripts/v.in.mapgen/v.in.mapgen.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,37 @@
+<H2>DESCRIPTION</H2>
+
+<EM>v.in.mapgen</EM> allows the user to import Mapgen or Matlab vector maps
+into GRASS.
+
+<H2>NOTES</H2>
+
+This module only imports data into vector lines.
+<P>
+You can get coastline data in Mapgen or Matlab format from NOAA's Coastline
+Extractor at <a href="http://www.ngdc.noaa.gov/mgg/shorelines/shorelines.html">http://www.ngdc.noaa.gov/mgg/shorelines/shorelines.html</a>.
+<P>
+Matlab vector line maps are simply a series of "x y" data points. Lines
+are separated by a row containing <tt>NaN NaN</tt>.
+
+Output from Matlab with this command:
+<BR>
+<div class="code"><pre>
+ save filename.txt arrayname -ASCII
+</pre></div>
+<P>
+You can import 3D lines from Matlab by exporting a 3 column array and
+using the <B>-z</B> flag.
+
+
+<H2>SEE ALSO</H2>
+<EM><A HREF="v.in.ascii.html">v.in.ascii</A></EM><BR>
+<BR>
+
+<P>
+<H2>AUTHORS</H2>
+Based on <em>v.in.mapgen.sh</em> for GRASS 5.0 by Andreas Lange
+<BR>Rewritten for GRASS 6 by Hamish Bowman
+<BR>
+
+<p>
+<i>Last changed: $Date$</i>
Deleted: grass/trunk/scripts/v.in.sites.all/description.html
===================================================================
--- grass/trunk/scripts/v.in.sites.all/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/scripts/v.in.sites.all/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,39 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>v.in.sites.all</em> converts all GRASS 5.0/5.3/5.4 sites files in the current
-mapset into 6.0 vectors.
-
-<h2>NOTES</h2>
-
-Sites maps from 5.0/5.3/5.4 and vector maps from 6.0 do not interfere.
-They are stored in different directories, so you can use the same names.
-Old sites maps can be listed with <em>g.list sites</em>.
-<br>
-As this GRASS version uses SQL for attribute management, there are
-some <a href=sql.html>SQL restrictings concerning the file names</a>.
-This script changes dots (e.g. "foo.bar") in old vector map names into
-underline(s) (e.g. "foo_bar"). It also adds the extension '_points' to the
-new vector map name.
-
-<h2>EXAMPLE</h2>
-
-To convert all old vector maps in the current mapset to the new vector format:
-<br>
-<tt>
-v.in.sites.all -r
-</tt>
-
-<h2>SEE ALSO</h2>
-
-<em>
-<A HREF="g.list.html">g.list</A>,
-<A HREF="v.in.sites.html">v.in.sites</A>
-</em>
-
-
-<h2>AUTHOR</h2>
-
-Markus Neteler, ITC-Irst, Trento, Italy
-
-<p>
-<i>Last changed: $Date$</i>
Copied: grass/trunk/scripts/v.in.sites.all/v.in.sites.all.html (from rev 32770, grass/trunk/scripts/v.in.sites.all/description.html)
===================================================================
--- grass/trunk/scripts/v.in.sites.all/v.in.sites.all.html (rev 0)
+++ grass/trunk/scripts/v.in.sites.all/v.in.sites.all.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,39 @@
+<h2>DESCRIPTION</h2>
+
+<em>v.in.sites.all</em> converts all GRASS 5.0/5.3/5.4 sites files in the current
+mapset into 6.0 vectors.
+
+<h2>NOTES</h2>
+
+Sites maps from 5.0/5.3/5.4 and vector maps from 6.0 do not interfere.
+They are stored in different directories, so you can use the same names.
+Old sites maps can be listed with <em>g.list sites</em>.
+<br>
+As this GRASS version uses SQL for attribute management, there are
+some <a href=sql.html>SQL restrictings concerning the file names</a>.
+This script changes dots (e.g. "foo.bar") in old vector map names into
+underline(s) (e.g. "foo_bar"). It also adds the extension '_points' to the
+new vector map name.
+
+<h2>EXAMPLE</h2>
+
+To convert all old vector maps in the current mapset to the new vector format:
+<br>
+<tt>
+v.in.sites.all -r
+</tt>
+
+<h2>SEE ALSO</h2>
+
+<em>
+<A HREF="g.list.html">g.list</A>,
+<A HREF="v.in.sites.html">v.in.sites</A>
+</em>
+
+
+<h2>AUTHOR</h2>
+
+Markus Neteler, ITC-Irst, Trento, Italy
+
+<p>
+<i>Last changed: $Date$</i>
Deleted: grass/trunk/scripts/v.in.wfs/description.html
===================================================================
--- grass/trunk/scripts/v.in.wfs/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/scripts/v.in.wfs/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,32 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>v.in.wfs</em> imports OGC WFS maps (Web Feature Service) from
-external servers.
-
-<h2>EXAMPLES</h2>
-
-Import of GRASS user map:
-<p>
-<div class="code"><pre>
-# run in LatLong location:
-v.in.wfs \
- wfs="http://mapserver.gdf-hannover.de/cgi-bin/grassuserwfs?REQUEST=GetFeature&SERVICE=WFS&VERSION=1.0.0" out=grass_users
-
-v.db.select grass_users where="name ~ 'Markus'"
-</pre></div>
-
-
-<h2>REQUIREMENTS</h2>
-
-The OGR library on the system needs to be compiled with Xerces C++ XML
-Parser support (for GML).
-
-<h2>SEE ALSO</h2>
-
-<em><a HREF="v.in.ogr.html">v.in.ogr</a></em>
-
-<h2>AUTHORS</h2>
-
-Markus Neteler, Hamish Bowman
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/scripts/v.in.wfs/v.in.wfs.html (from rev 32770, grass/trunk/scripts/v.in.wfs/description.html)
===================================================================
--- grass/trunk/scripts/v.in.wfs/v.in.wfs.html (rev 0)
+++ grass/trunk/scripts/v.in.wfs/v.in.wfs.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,32 @@
+<h2>DESCRIPTION</h2>
+
+<em>v.in.wfs</em> imports OGC WFS maps (Web Feature Service) from
+external servers.
+
+<h2>EXAMPLES</h2>
+
+Import of GRASS user map:
+<p>
+<div class="code"><pre>
+# run in LatLong location:
+v.in.wfs \
+ wfs="http://mapserver.gdf-hannover.de/cgi-bin/grassuserwfs?REQUEST=GetFeature&SERVICE=WFS&VERSION=1.0.0" out=grass_users
+
+v.db.select grass_users where="name ~ 'Markus'"
+</pre></div>
+
+
+<h2>REQUIREMENTS</h2>
+
+The OGR library on the system needs to be compiled with Xerces C++ XML
+Parser support (for GML).
+
+<h2>SEE ALSO</h2>
+
+<em><a HREF="v.in.ogr.html">v.in.ogr</a></em>
+
+<h2>AUTHORS</h2>
+
+Markus Neteler, Hamish Bowman
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/scripts/v.rast.stats/description.html
===================================================================
--- grass/trunk/scripts/v.rast.stats/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/scripts/v.rast.stats/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,75 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-<EM><b>v.rast.stats</b></EM> - Calculates basic univariate statistics from
-a raster map only for the parts covered by the specified vector map.
-The vector map will be rasterized according to the raster map resolution.
-Then univariate statistics are calculated per vector category (cat) from
-the raster map and the results uploaded to the vector map attribute table.
-New columns are generated in the attribute table if not already present.
-<p>
-Nine columns are generated (n, min, max, range, mean, stddev, variance,
-coeff_var, sum) according to the output of <em>r.univar</em>.
-If the <B>-e</B> extended statistics flag is given the 1st quartile,
-median, 3rd quartile, and given percentile are also calculated.
-
-
-<H2>NOTES</H2>
-
-The module may take a long time to run if the raster region contains a large
-number of cells. In this case the <B>--verbose</B> flag may be used to track
-progress.
-<p>
-The script stops if a (prefixed) upload column is already present in the
-vector map attribute table, unless otherwise instructed with the <B>-c</B>
-continue flag. The column prefix will be separated from the statistic name
-with an underscore. For example with a prefix of "<tt>elev</tt>" the sum
-column will be named <tt>elev_sum</tt>.
-<P>
-If a DBF database is being used, note that column names are restricted by the
-DBF specification to 10 characters. Therefore it is advised to be economical
-in the use of the column prefix when using DBF as any additional characters
-will be chopped off.
-<p>
-If a MASK is present, it will be restored after the script finished.
-The script changes temporarily to the resolution of the given raster map.
-<P>
-<!-- r.univar limitation -->
-Large amounts of system memory can be used when the <B>-e</B> extended
-statistics flag is used with a very large region setting. If the region
-is too large the module should display memory allocation errors.
-Basic statistics can be calculated using any size input region.
-
-
-<H2>EXAMPLES</H2>
-
-Example to upload DEM statistics to vector field patches:
-
-<div class="code"><pre>
-# work on copy of original map:
-g.copy vect=fields,myfields
-# if needed, zoom to raster map:
-g.region rast=elevation.dem -p
-# calculate DEM statistics, upload to vector map table:
-v.rast.stats myfields raster=elevation.dem colprefix=dem
-# verify results:
-v.info -c myfields
-v.db.select myfields
-v.univar myfields column=dem_range type=centroid
-</pre></div>
-
-
-<H2>SEE ALSO</H2>
-
-<EM>
-<A HREF="r.univar.html">r.univar</A>,
-<A HREF="v.univar.html">v.univar</A>,
-<a HREF="v.what.rast.html">v.what.rast</a>,
-<a href="v.what.vect.html">v.what.vect</a>
-</EM>
-
-<H2>AUTHOR</H2>
-
-Markus Neteler, CEA (<a href="http://www.eden-fp6project.net/">EDEN Project</a>)
-
-<p>
-<i>Last changed: $Date$</i>
Copied: grass/trunk/scripts/v.rast.stats/v.rast.stats.html (from rev 32770, grass/trunk/scripts/v.rast.stats/description.html)
===================================================================
--- grass/trunk/scripts/v.rast.stats/v.rast.stats.html (rev 0)
+++ grass/trunk/scripts/v.rast.stats/v.rast.stats.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,75 @@
+<H2>DESCRIPTION</H2>
+
+<EM><b>v.rast.stats</b></EM> - Calculates basic univariate statistics from
+a raster map only for the parts covered by the specified vector map.
+The vector map will be rasterized according to the raster map resolution.
+Then univariate statistics are calculated per vector category (cat) from
+the raster map and the results uploaded to the vector map attribute table.
+New columns are generated in the attribute table if not already present.
+<p>
+Nine columns are generated (n, min, max, range, mean, stddev, variance,
+coeff_var, sum) according to the output of <em>r.univar</em>.
+If the <B>-e</B> extended statistics flag is given the 1st quartile,
+median, 3rd quartile, and given percentile are also calculated.
+
+
+<H2>NOTES</H2>
+
+The module may take a long time to run if the raster region contains a large
+number of cells. In this case the <B>--verbose</B> flag may be used to track
+progress.
+<p>
+The script stops if a (prefixed) upload column is already present in the
+vector map attribute table, unless otherwise instructed with the <B>-c</B>
+continue flag. The column prefix will be separated from the statistic name
+with an underscore. For example with a prefix of "<tt>elev</tt>" the sum
+column will be named <tt>elev_sum</tt>.
+<P>
+If a DBF database is being used, note that column names are restricted by the
+DBF specification to 10 characters. Therefore it is advised to be economical
+in the use of the column prefix when using DBF as any additional characters
+will be chopped off.
+<p>
+If a MASK is present, it will be restored after the script finished.
+The script changes temporarily to the resolution of the given raster map.
+<P>
+<!-- r.univar limitation -->
+Large amounts of system memory can be used when the <B>-e</B> extended
+statistics flag is used with a very large region setting. If the region
+is too large the module should display memory allocation errors.
+Basic statistics can be calculated using any size input region.
+
+
+<H2>EXAMPLES</H2>
+
+Example to upload DEM statistics to vector field patches:
+
+<div class="code"><pre>
+# work on copy of original map:
+g.copy vect=fields,myfields
+# if needed, zoom to raster map:
+g.region rast=elevation.dem -p
+# calculate DEM statistics, upload to vector map table:
+v.rast.stats myfields raster=elevation.dem colprefix=dem
+# verify results:
+v.info -c myfields
+v.db.select myfields
+v.univar myfields column=dem_range type=centroid
+</pre></div>
+
+
+<H2>SEE ALSO</H2>
+
+<EM>
+<A HREF="r.univar.html">r.univar</A>,
+<A HREF="v.univar.html">v.univar</A>,
+<a HREF="v.what.rast.html">v.what.rast</a>,
+<a href="v.what.vect.html">v.what.vect</a>
+</EM>
+
+<H2>AUTHOR</H2>
+
+Markus Neteler, CEA (<a href="http://www.eden-fp6project.net/">EDEN Project</a>)
+
+<p>
+<i>Last changed: $Date$</i>
Deleted: grass/trunk/scripts/v.report/description.html
===================================================================
--- grass/trunk/scripts/v.report/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/scripts/v.report/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,42 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-<em>v.report</em> generates a table showing the area present in
-each of the categories of a user-selected data layer.
-<P>
-Area is given in hectares, square meters, and square kilometers.
-If the units option is used, area is given in acres, square feet,
-and square miles.
-<P>
-Feet and acre units are always reported in their common versions
-(i.e. the International Foot, exactly 5280 feet in a mile), even
-when the location's standard map unit is the US Survey foot.
-<P>
-<EM>v.report</EM> works on the full map data; therefore, the current
-region is ignored. If you wish to spatially limit the statistics,
-a map subset must be created with <EM>v.in.region</EM> and
-<EM>v.overlay</EM>, and then run <EM>v.report</EM> on the new map.
-
-
-<h2>EXAMPLE</h2>
-
-Spearfish example:
-<div class="code"><pre>
-v.report fields option=area units=hectares
-</pre></div>
-
-
-<h2>SEE ALSO</h2>
-
-<em>
-<a HREF="v.in.region.html">v.in.region</a>,
-<a HREF="v.to.db.html">v.to.db</a>,
-<a HREF="v.overlay.html">v.overlay</a>
-</em>
-
-
-<H2>AUTHOR</H2>
-
-Markus Neteler, GDF Hannover
-
-<p>
-<i>Last changed: $Date$</i>
Copied: grass/trunk/scripts/v.report/v.report.html (from rev 32770, grass/trunk/scripts/v.report/description.html)
===================================================================
--- grass/trunk/scripts/v.report/v.report.html (rev 0)
+++ grass/trunk/scripts/v.report/v.report.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,42 @@
+<H2>DESCRIPTION</H2>
+
+<em>v.report</em> generates a table showing the area present in
+each of the categories of a user-selected data layer.
+<P>
+Area is given in hectares, square meters, and square kilometers.
+If the units option is used, area is given in acres, square feet,
+and square miles.
+<P>
+Feet and acre units are always reported in their common versions
+(i.e. the International Foot, exactly 5280 feet in a mile), even
+when the location's standard map unit is the US Survey foot.
+<P>
+<EM>v.report</EM> works on the full map data; therefore, the current
+region is ignored. If you wish to spatially limit the statistics,
+a map subset must be created with <EM>v.in.region</EM> and
+<EM>v.overlay</EM>, and then run <EM>v.report</EM> on the new map.
+
+
+<h2>EXAMPLE</h2>
+
+Spearfish example:
+<div class="code"><pre>
+v.report fields option=area units=hectares
+</pre></div>
+
+
+<h2>SEE ALSO</h2>
+
+<em>
+<a HREF="v.in.region.html">v.in.region</a>,
+<a HREF="v.to.db.html">v.to.db</a>,
+<a HREF="v.overlay.html">v.overlay</a>
+</em>
+
+
+<H2>AUTHOR</H2>
+
+Markus Neteler, GDF Hannover
+
+<p>
+<i>Last changed: $Date$</i>
Deleted: grass/trunk/scripts/v.what.vect/description.html
===================================================================
--- grass/trunk/scripts/v.what.vect/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/scripts/v.what.vect/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,52 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>v.what.vect</em> transfers attributes from the <b>qvector</b>'s map
-attribute table into the attribute table of <u>points</u> present in the
-<b>vector</b> map. The script is based on <em>v.distance</em>.
-
-<h2>NOTES</h2>
-
-The upload <b>column</b>, into which the query results are stored, must be
-present in the <b>vector</b> map. Use <em>v.db.addcol</em> to add one if needed.
-<p>
-Use dmax parameter to control query distance tolerance (how far points can be from
-<b>qvector</b> features). For more options, use
-<em>v.distance</em> instead.
-<P>
-In case of a multipoint input <b>vector</b> map, with several points having the
-same category number, it can happen, that the query result is NULL, if the same
-category number falls into different <b>qvector</b> polygons.
-
-<h2>EXAMPLE</h2>
-
-In this example, the 'archsites' point map in the Spearfish location is copied
-to the current mapset, a new attribute column is added and the owner
-names from the 'fields' polygon map are transferred to the 'myarchsites'
-map at points' locations:
-
-<div class="code"><pre>
-g.copy vect=archsites,myarchsites
-v.db.addcol myarchsites col="owner varchar(25)"
-v.what.vect myarchsites qvect=fields column=owner qcolumn=label
-# verification:
-v.db.select myarchsites
-</pre></div>
-
-
-<h2>SEE ALSO</h2>
-
-<em>
-<a HREF="v.db.addcol.html">v.db.addcol</a>,
-<a HREF="v.db.select.html">v.db.select</a>,
-<a HREF="v.distance.html">v.distance</a>,
-<a HREF="v.rast.stats.html">v.rast.stats</a>,
-<a HREF="v.what.rast.html">v.what.rast</a>
-</em>
-
-
-<h2>AUTHOR</h2>
-
-Markus Neteler
-
-<p>
-<i>Last changed: $Date$</i></p>
Copied: grass/trunk/scripts/v.what.vect/v.what.vect.html (from rev 32770, grass/trunk/scripts/v.what.vect/description.html)
===================================================================
--- grass/trunk/scripts/v.what.vect/v.what.vect.html (rev 0)
+++ grass/trunk/scripts/v.what.vect/v.what.vect.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,52 @@
+<h2>DESCRIPTION</h2>
+
+<em>v.what.vect</em> transfers attributes from the <b>qvector</b>'s map
+attribute table into the attribute table of <u>points</u> present in the
+<b>vector</b> map. The script is based on <em>v.distance</em>.
+
+<h2>NOTES</h2>
+
+The upload <b>column</b>, into which the query results are stored, must be
+present in the <b>vector</b> map. Use <em>v.db.addcol</em> to add one if needed.
+<p>
+Use dmax parameter to control query distance tolerance (how far points can be from
+<b>qvector</b> features). For more options, use
+<em>v.distance</em> instead.
+<P>
+In case of a multipoint input <b>vector</b> map, with several points having the
+same category number, it can happen, that the query result is NULL, if the same
+category number falls into different <b>qvector</b> polygons.
+
+<h2>EXAMPLE</h2>
+
+In this example, the 'archsites' point map in the Spearfish location is copied
+to the current mapset, a new attribute column is added and the owner
+names from the 'fields' polygon map are transferred to the 'myarchsites'
+map at points' locations:
+
+<div class="code"><pre>
+g.copy vect=archsites,myarchsites
+v.db.addcol myarchsites col="owner varchar(25)"
+v.what.vect myarchsites qvect=fields column=owner qcolumn=label
+# verification:
+v.db.select myarchsites
+</pre></div>
+
+
+<h2>SEE ALSO</h2>
+
+<em>
+<a HREF="v.db.addcol.html">v.db.addcol</a>,
+<a HREF="v.db.select.html">v.db.select</a>,
+<a HREF="v.distance.html">v.distance</a>,
+<a HREF="v.rast.stats.html">v.rast.stats</a>,
+<a HREF="v.what.rast.html">v.what.rast</a>
+</em>
+
+
+<h2>AUTHOR</h2>
+
+Markus Neteler
+
+<p>
+<i>Last changed: $Date$</i></p>
Deleted: grass/trunk/sites/s.in.ascii/description.html
===================================================================
--- grass/trunk/sites/s.in.ascii/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/sites/s.in.ascii/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,148 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-
-<EM>s.in.ascii</EM> converts an ASCII listing of site
-locations and category labels into GRASS vector format.
-
-<P>
-
-Input can be entered via standard input or from the file
-<B>input=</B><EM>name</EM>. Each line of input should
-contain the easting, northing, and either the category value
-or category label associated with a site. The
-<B>fs=</B><EM>name</EM> option (where <EM>name</EM> is
-either a character, a space, or a tab) can be used to
-specify the use of a particular field separator between
-these three input fields. This is useful when input is
-obtained from other programs (see NOTES, below). Output is
-stored in the vector map <B>output=</B><EM>name</EM>.
-
-<P>
-
-The GRASS program <EM><a href="s.out.ascii.html">s.out.ascii</a></EM>
-can be used to perform the reverse function, converting a file in GRASS
-vector sites format into an ASCII listing of eastings, northings, and
-category labels associated with site locations.
-
-
-<H3>Parameters:</H3>
-
-<DL>
-<DT><B>output=</B><EM>name</EM>
-<DD>Name of the new GRASS site list file to be output.
-<DT><B>input=</B><EM>name</EM>
-<DD>Name of an existing ASCII file containing site locations and labels.
-<DT><B>d=</B><EM>value</EM>
-<DD>number of dimensions (default=2)
-<DT><B>fs=</B><EM>character|space|tab</EM>
-<DD>The field separator separating the easting, northing, and category label
- in each line of the <EM>input</EM> file.
- The field separator can be a character, a space, or a tab.
-<BR>
- Default: space
-<DT><B>date=</B><EM>timestamp</EM>[/<EM>timestamp</EM>]
-<DD>String specifying timestamp or timestamp range.
-</DL>
-
-<P>
-
-<EM>s.in.ascii</EM> can be run either non-interactively or
-interactively. The program will be run non-interactively
-if the user specifies a name to be assigned to the
-<B>sites</B> file output, the name of an existing ASCII
-file containing <B>input</B>, and (optionally) a field
-separator <B>fs</B> appearing in the <B>input</B> file.
-
-<P>
-
-Alternately, the user can simply type <B>s.in.ascii</B> on
-the command line, without program arguments. In this case,
-the user will be prompted for parameter values using the
-standard GRASS parser interface described in the manual
-entry for <EM><a href="parser.html">parser</a></EM>. If
-the user does not specify the name of an <B>input</B>
-file containing site locations and category attributes,
-these should be entered to the program via standard input.
-The <B>d</B> parameter allows the user to specify that more
-than 2 dimensions will be imported. Otherwise the third (or
-further) column in the <B>input</B> file will be treated as an attribute.
-
-<P>To define a <B>date</B> (timestamp), several date strings are accepted.
-Please see <EM><A HREF="r.timestamp.html">r.timestamp</A></EM> for details.
-
-<p>
-<H2>NOTES</H2>
-
-<B>Importing from other GRASS programs</B>
-<p>
-Other GRASS programs can be used to produce output in a
-format suitable for input to <EM>s.in.ascii</EM>. For
-example, the user might pipe output produced by
-<EM><a href="d.where.html">d.where</a></EM> into
-<EM>s.in.ascii</EM> to create a site
-list file called <EM>my.sites</EM> containing site
-locations pointed to with the mouse, as illustrated below.
-In this example it is unnecessary to specify the field
-separator used in the input, since <EM>d.where</EM> output
-separates the easting and northing values with spaces, and
-spaces are the default field separator assumed by
-<EM>s.in.ascii</EM>.
-<P>
-<DL>
-<DD><B>d.where</B> | <B>s.in.ascii output=</B>my.sites
-</DL>
-<p>
-<B>Importing from a spreadsheet</B>
-<p>
-Data may be imported from many spreadsheet programs by saving the spreadsheet
-as a comma separated variable (.csv) text file, and then using
-the "<b>fs=</b><EM>,</EM>" command line parameter with <EM>s.in.ascii</EM>.
-<p>
-<b>Importing latitude/longitude data</b>
-<p>
-Latitude/longitude data may be imported either in decimal degree format:<br>
-
-<pre>
- 8.314824 54.921730 site1
- 8.897605 54.872353 site2
- 9.549371 54.834080 site3
-</pre>
-
-or in DMS (degree, minutes, seconds) format:<br>
-
-<pre>
- 8:18:53.3664E 54:55:18.228N site1
- 8:53:51.378E 54:52:20.4708N site2
- 9:32:57.7356E 54:50:02.688N site3
-</pre>
-
-<p>
-<b>Time as String Attributes</b>
-<p>
-
-In this example, we will work with the following site list:
-
-<pre>
- 10.8 0 9.8 Fri Sep 13 10:00:00 1986 31.4
- 11 5.5 9.9 Fri Sep 14 00:20:00 1985 36.4
- 5.1 3.9 10 Fri Sep 15 00:00:30 1984 28.4
-</pre>
-
-This data has three dimensions (assume easting, northing, and
-elevation), five string attributes, and one decimal attribute.
-
-<H2>SEE ALSO</H2>
-
-<EM><A HREF="d.vect.html">d.sites</A></EM>,
-<EM><A HREF="d.what.vect.html">d.what.vect</A></EM>,
-<EM><A HREF="d.where.html">d.where</A></EM>,
-<EM><A HREF="r.timestamp.html">r.timestamp</A></EM>,
-<EM><A HREF="s.out.ascii.html">s.out.ascii</A></EM>
-
-<H2>AUTHOR</H2>
-
-Michael Shapiro,
-U.S. Army Construction Engineering
-Research Laboratory
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/sites/s.in.ascii/s.in.ascii.html (from rev 32770, grass/trunk/sites/s.in.ascii/description.html)
===================================================================
--- grass/trunk/sites/s.in.ascii/s.in.ascii.html (rev 0)
+++ grass/trunk/sites/s.in.ascii/s.in.ascii.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,148 @@
+<H2>DESCRIPTION</H2>
+
+
+<EM>s.in.ascii</EM> converts an ASCII listing of site
+locations and category labels into GRASS vector format.
+
+<P>
+
+Input can be entered via standard input or from the file
+<B>input=</B><EM>name</EM>. Each line of input should
+contain the easting, northing, and either the category value
+or category label associated with a site. The
+<B>fs=</B><EM>name</EM> option (where <EM>name</EM> is
+either a character, a space, or a tab) can be used to
+specify the use of a particular field separator between
+these three input fields. This is useful when input is
+obtained from other programs (see NOTES, below). Output is
+stored in the vector map <B>output=</B><EM>name</EM>.
+
+<P>
+
+The GRASS program <EM><a href="s.out.ascii.html">s.out.ascii</a></EM>
+can be used to perform the reverse function, converting a file in GRASS
+vector sites format into an ASCII listing of eastings, northings, and
+category labels associated with site locations.
+
+
+<H3>Parameters:</H3>
+
+<DL>
+<DT><B>output=</B><EM>name</EM>
+<DD>Name of the new GRASS site list file to be output.
+<DT><B>input=</B><EM>name</EM>
+<DD>Name of an existing ASCII file containing site locations and labels.
+<DT><B>d=</B><EM>value</EM>
+<DD>number of dimensions (default=2)
+<DT><B>fs=</B><EM>character|space|tab</EM>
+<DD>The field separator separating the easting, northing, and category label
+ in each line of the <EM>input</EM> file.
+ The field separator can be a character, a space, or a tab.
+<BR>
+ Default: space
+<DT><B>date=</B><EM>timestamp</EM>[/<EM>timestamp</EM>]
+<DD>String specifying timestamp or timestamp range.
+</DL>
+
+<P>
+
+<EM>s.in.ascii</EM> can be run either non-interactively or
+interactively. The program will be run non-interactively
+if the user specifies a name to be assigned to the
+<B>sites</B> file output, the name of an existing ASCII
+file containing <B>input</B>, and (optionally) a field
+separator <B>fs</B> appearing in the <B>input</B> file.
+
+<P>
+
+Alternately, the user can simply type <B>s.in.ascii</B> on
+the command line, without program arguments. In this case,
+the user will be prompted for parameter values using the
+standard GRASS parser interface described in the manual
+entry for <EM><a href="parser.html">parser</a></EM>. If
+the user does not specify the name of an <B>input</B>
+file containing site locations and category attributes,
+these should be entered to the program via standard input.
+The <B>d</B> parameter allows the user to specify that more
+than 2 dimensions will be imported. Otherwise the third (or
+further) column in the <B>input</B> file will be treated as an attribute.
+
+<P>To define a <B>date</B> (timestamp), several date strings are accepted.
+Please see <EM><A HREF="r.timestamp.html">r.timestamp</A></EM> for details.
+
+<p>
+<H2>NOTES</H2>
+
+<B>Importing from other GRASS programs</B>
+<p>
+Other GRASS programs can be used to produce output in a
+format suitable for input to <EM>s.in.ascii</EM>. For
+example, the user might pipe output produced by
+<EM><a href="d.where.html">d.where</a></EM> into
+<EM>s.in.ascii</EM> to create a site
+list file called <EM>my.sites</EM> containing site
+locations pointed to with the mouse, as illustrated below.
+In this example it is unnecessary to specify the field
+separator used in the input, since <EM>d.where</EM> output
+separates the easting and northing values with spaces, and
+spaces are the default field separator assumed by
+<EM>s.in.ascii</EM>.
+<P>
+<DL>
+<DD><B>d.where</B> | <B>s.in.ascii output=</B>my.sites
+</DL>
+<p>
+<B>Importing from a spreadsheet</B>
+<p>
+Data may be imported from many spreadsheet programs by saving the spreadsheet
+as a comma separated variable (.csv) text file, and then using
+the "<b>fs=</b><EM>,</EM>" command line parameter with <EM>s.in.ascii</EM>.
+<p>
+<b>Importing latitude/longitude data</b>
+<p>
+Latitude/longitude data may be imported either in decimal degree format:<br>
+
+<pre>
+ 8.314824 54.921730 site1
+ 8.897605 54.872353 site2
+ 9.549371 54.834080 site3
+</pre>
+
+or in DMS (degree, minutes, seconds) format:<br>
+
+<pre>
+ 8:18:53.3664E 54:55:18.228N site1
+ 8:53:51.378E 54:52:20.4708N site2
+ 9:32:57.7356E 54:50:02.688N site3
+</pre>
+
+<p>
+<b>Time as String Attributes</b>
+<p>
+
+In this example, we will work with the following site list:
+
+<pre>
+ 10.8 0 9.8 Fri Sep 13 10:00:00 1986 31.4
+ 11 5.5 9.9 Fri Sep 14 00:20:00 1985 36.4
+ 5.1 3.9 10 Fri Sep 15 00:00:30 1984 28.4
+</pre>
+
+This data has three dimensions (assume easting, northing, and
+elevation), five string attributes, and one decimal attribute.
+
+<H2>SEE ALSO</H2>
+
+<EM><A HREF="d.vect.html">d.sites</A></EM>,
+<EM><A HREF="d.what.vect.html">d.what.vect</A></EM>,
+<EM><A HREF="d.where.html">d.where</A></EM>,
+<EM><A HREF="r.timestamp.html">r.timestamp</A></EM>,
+<EM><A HREF="s.out.ascii.html">s.out.ascii</A></EM>
+
+<H2>AUTHOR</H2>
+
+Michael Shapiro,
+U.S. Army Construction Engineering
+Research Laboratory
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/sites/s.out.ascii/description.html
===================================================================
--- grass/trunk/sites/s.out.ascii/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/sites/s.out.ascii/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,152 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-<EM>s.out.ascii</EM> converts an existing site list file
-(<B>input=</B><EM>name</EM>) into an ASCII listing of site
-locations and (optionally) their category labels, in a
-format suitable for input to other program).
-
-<P>
-
-Each line of output consists of the easting, northing, and
-category label for a site listed in the named <B>vector points</B> (sites)
-file. The <B>fs=</B><EM>name</EM> option (where
-<EM>name</EM> is either a character, a space, or a tab) can
-be used to place a particular field separator between these
-three output fields. This is useful when output is to be
-manipulated by other programs, like <EM>awk</EM> or
-<EM>sed</EM>.
-
-<P>
-
-The GRASS program <EM>s.in.ascii</EM> can be used to
-perform the reverse function, converting a UNIX file
-containing eastings, northings, and category labels
-associated with site locations into GRASS site list file
-format.
-
-<H2>OPTIONS</H2>
-
-<H3>Flags:</H3>
-
-<DL>
-<DT><B>-a</B>
-<DD>Output all sites found in the named <B>vector points</B>
-file, rather than limiting output to sites falling within
-the current geographic region.
-
-<DT><B>-d</B>
-<DD>Include site descriptions (category labels) in the output.
-
-<DT><B>-i</B>
-<DD>Include site attribute identifiers in the output
-
-</DL>
-
-<H3>Parameters:</H3>
-
-<DL>
-
-<DT><B>input=</B><EM>name</EM>
-
-<DD>Name of an existing site list file.
-
-<DT><B>fs=</B>character|space|tab
-
-<DD>The field separator to be placed between the easting,
-northing, and (optionally) category label on each line of
-output. The field separator can be a character, a space,
-or a tab.
-
-<BR>
-Default: space
-</DL>
-
-<EM>s.out.ascii</EM> can be run either non-interactively or
-interactively. The program will be run non-interactively
-if the user specifies the name of an existing site list
-file and (optionally) a value for <B>fs</B>, using the form
-
-<P>
-<DL>
-<DD>
-<B>s.out.ascii</B>
-[<B>-adi</B>]
-<B>input=</B><EM>name</EM>
-[<B>fs=</B>character|space|tab]
-</DL>
-
-
-where <EM>name</EM> is the name of an existing site list
-file to be converted to a brief ASCII listing, and
-<B>fs</B> is the field separator to be placed between
-output fields. The user can also the <B>-a</B> and
-<B>-d</B> options to use all sites in the named
-<B>sites</B> file and to include site descriptions in the
-output.
-
-<P>
-
-Alternately, the user can simply type <B>s.out.ascii</B> on
-the command line, without program arguments. In this case,
-the user will be prompted for parameter values using the
-standard GRASS
-
-<A HREF="parser.html">parser</A>
-
-interface.
-
-<H2>NOTES</H2>
-
-To output GRASS data in x,y,z ASCII style, the s.out.ascii may be used:
-<p>
-<DL>
-<DD>
-<B>s.out.ascii -d input=</B>sitesmap
-</DL>
-Resulting to:
-
-<pre>
- 3566393.75 5773293.75 168.3
- 3566818.75 5773293.75 158.8
- 3568843.75 5773293.75 114.3
- 3568981.25 5773293.75 117.5
- [...]
-</pre>
-
-To export raster maps into this x,y,z format, the raster map can be
-converted to sites format using <em>r.to.sites</em> and <em>s.out.ascii</em>
-subsequently as described above.
-
-<p>
-The output from <EM>s.out.ascii</EM> may be placed into a
-file by using the UNIX redirection mechanism; e.g.:
-
-<P>
-<DL>
-<DD>
-<B>s.out.ascii input=</B>archsites > out.file
-</DL>
-
-<EM>s.out.ascii</EM> output may also be redirected into
-other programs; e.g.:
-
-<P>
-<DL>
-<DD>
-<B>s.out.ascii input=</B>archsites | d.points <B>color=</B>red <B>size=</B>10 <B>type=</B>diamond
-</DL>
-
-<H2>SEE ALSO</H2>
-
-<EM><A HREF="d.points.html">d.points</A></EM><br>
-<EM><A HREF="d.vect.html">d.vect</A></EM><br>
-<EM><A HREF="s.in.ascii.html">s.in.ascii</A></EM><br>
-<EM><A HREF="r.to.vect.html">r.to.vect</A></EM>
-
-<H2>AUTHOR</H2>
-
-Michael Shapiro,
-U.S. Army Construction Engineering
-Research Laboratory
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/sites/s.out.ascii/s.out.ascii.html (from rev 32770, grass/trunk/sites/s.out.ascii/description.html)
===================================================================
--- grass/trunk/sites/s.out.ascii/s.out.ascii.html (rev 0)
+++ grass/trunk/sites/s.out.ascii/s.out.ascii.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,152 @@
+<H2>DESCRIPTION</H2>
+
+<EM>s.out.ascii</EM> converts an existing site list file
+(<B>input=</B><EM>name</EM>) into an ASCII listing of site
+locations and (optionally) their category labels, in a
+format suitable for input to other program).
+
+<P>
+
+Each line of output consists of the easting, northing, and
+category label for a site listed in the named <B>vector points</B> (sites)
+file. The <B>fs=</B><EM>name</EM> option (where
+<EM>name</EM> is either a character, a space, or a tab) can
+be used to place a particular field separator between these
+three output fields. This is useful when output is to be
+manipulated by other programs, like <EM>awk</EM> or
+<EM>sed</EM>.
+
+<P>
+
+The GRASS program <EM>s.in.ascii</EM> can be used to
+perform the reverse function, converting a UNIX file
+containing eastings, northings, and category labels
+associated with site locations into GRASS site list file
+format.
+
+<H2>OPTIONS</H2>
+
+<H3>Flags:</H3>
+
+<DL>
+<DT><B>-a</B>
+<DD>Output all sites found in the named <B>vector points</B>
+file, rather than limiting output to sites falling within
+the current geographic region.
+
+<DT><B>-d</B>
+<DD>Include site descriptions (category labels) in the output.
+
+<DT><B>-i</B>
+<DD>Include site attribute identifiers in the output
+
+</DL>
+
+<H3>Parameters:</H3>
+
+<DL>
+
+<DT><B>input=</B><EM>name</EM>
+
+<DD>Name of an existing site list file.
+
+<DT><B>fs=</B>character|space|tab
+
+<DD>The field separator to be placed between the easting,
+northing, and (optionally) category label on each line of
+output. The field separator can be a character, a space,
+or a tab.
+
+<BR>
+Default: space
+</DL>
+
+<EM>s.out.ascii</EM> can be run either non-interactively or
+interactively. The program will be run non-interactively
+if the user specifies the name of an existing site list
+file and (optionally) a value for <B>fs</B>, using the form
+
+<P>
+<DL>
+<DD>
+<B>s.out.ascii</B>
+[<B>-adi</B>]
+<B>input=</B><EM>name</EM>
+[<B>fs=</B>character|space|tab]
+</DL>
+
+
+where <EM>name</EM> is the name of an existing site list
+file to be converted to a brief ASCII listing, and
+<B>fs</B> is the field separator to be placed between
+output fields. The user can also the <B>-a</B> and
+<B>-d</B> options to use all sites in the named
+<B>sites</B> file and to include site descriptions in the
+output.
+
+<P>
+
+Alternately, the user can simply type <B>s.out.ascii</B> on
+the command line, without program arguments. In this case,
+the user will be prompted for parameter values using the
+standard GRASS
+
+<A HREF="parser.html">parser</A>
+
+interface.
+
+<H2>NOTES</H2>
+
+To output GRASS data in x,y,z ASCII style, the s.out.ascii may be used:
+<p>
+<DL>
+<DD>
+<B>s.out.ascii -d input=</B>sitesmap
+</DL>
+Resulting to:
+
+<pre>
+ 3566393.75 5773293.75 168.3
+ 3566818.75 5773293.75 158.8
+ 3568843.75 5773293.75 114.3
+ 3568981.25 5773293.75 117.5
+ [...]
+</pre>
+
+To export raster maps into this x,y,z format, the raster map can be
+converted to sites format using <em>r.to.sites</em> and <em>s.out.ascii</em>
+subsequently as described above.
+
+<p>
+The output from <EM>s.out.ascii</EM> may be placed into a
+file by using the UNIX redirection mechanism; e.g.:
+
+<P>
+<DL>
+<DD>
+<B>s.out.ascii input=</B>archsites > out.file
+</DL>
+
+<EM>s.out.ascii</EM> output may also be redirected into
+other programs; e.g.:
+
+<P>
+<DL>
+<DD>
+<B>s.out.ascii input=</B>archsites | d.points <B>color=</B>red <B>size=</B>10 <B>type=</B>diamond
+</DL>
+
+<H2>SEE ALSO</H2>
+
+<EM><A HREF="d.points.html">d.points</A></EM><br>
+<EM><A HREF="d.vect.html">d.vect</A></EM><br>
+<EM><A HREF="s.in.ascii.html">s.in.ascii</A></EM><br>
+<EM><A HREF="r.to.vect.html">r.to.vect</A></EM>
+
+<H2>AUTHOR</H2>
+
+Michael Shapiro,
+U.S. Army Construction Engineering
+Research Laboratory
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/vector/lidar/v.lidar.correction/description.html
===================================================================
--- grass/trunk/vector/lidar/v.lidar.correction/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/vector/lidar/v.lidar.correction/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,107 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>v.lidar.correction</em> is the last of three steps to filter LiDAR
-data. The filter aims to recognize and extract attached and
-detached object (such as buildings, bridges, power lines, trees, etc.)
-in order to create a Digital Terrain Model.
-<br>
-<br>
-The module, which could be iterated several times, makes a comparison
-between the LiDAR observations and a bilinear spline interpolation with
-a Tychonov regularization parameter performed on the TERRAIN SINGLE PULSE
-points only. The gradient is minimized by the regularization parameter.
-Analysis of the residuals between the observations and the interpolated
-values results in four cases (the next classification is referred to that
-of the v.lidar.growing output vector):
-<br>
-<br>
-<b>a)</b> Points classified as TERRAIN differing more than a threshold
- value are interpreted and reclassified as OBJECT, for both single and
- double pulse points.
-<br>
-<br>
-<b>b)</b> Points classified as OBJECT and closed enough to the
- interpolated surface are interpreted and reclassified as TERRAIN, for
- both single and double pulse points.
-
-<h2>NOTES</h2>
-
-The input should be the output of <em>v.lidar.growing</em> module or the
-output of this <em>v.lidar.correction</em> itself. That means, this module
-could be applied more times (although, two are usually enough) for a better
-filter solution. The outputs are a vector map with a final point classification
-as as TERRAIN SINGLE PULSE, TERRAIN DOUBLE PULSE, OBJECT SINGLE PULSE or
-OBJECT DOUBLE PULSE; and an vector map with only the points classified as
-TERRAIN SINGLE PULSE or TERRAIN DOUBLE PULSE.
-
-The final result of the whole procedure (v.lidar.edgedetection,
-v.lidar.growing, v.lidar.correction) will be a point classification in
-four categories:
-<br>
-<br>
-TERRAIN SINGLE PULSE (cat = 1, layer = 2)
-<br>
-TERRAIN DOUBLE PULSE (cat = 2, layer = 2)
-<br>
-OBJECT SINGLE PULSE (cat = 3, layer = 2)
-<br>
-OBJECT DOUBLE PULSE (cat = 4, layer = 2)
-
-
-<h2>EXAMPLES</h2>
-
-<h4>Basic correction procedure</h4>
-<div class="code"><pre>
-v.lidar.correction input=growing output=correction out_terrain=only_terrain
-</pre></div>
-
-<h4>Second correction procedure</h4>
-<div class="code"><pre>
-v.lidar.correction input=correction output=correction_bis out_terrain=only_terrain_bis
-</pre></div>
-
-<h2>SEE ALSO</h2>
-<em><a HREF="v.lidar.edgedetection.html">v.lidar.edgedetection</a></em>,
-<em><a HREF="v.lidar.growing.html">v.lidar.growing</a></em>,
-<em><a HREF="v.surf.bspline.html">v.surf.bspline</a></em>
-
-<h2>AUTHORS</h2>
-Original version of program in GRASS 5.4:
-<BR>
-Maria Antonia Brovelli, Massimiliano Cannata, Ulisse Longoni and Mirko Reguzzoni
-<BR><BR>
-Update for GRASS 6.X:
-<BR>
-Roberto Antolin and Gonzalo Moreno
-
-<h2>REFERENCES</h2>
-
-Antolin, R. et al., 2006. Digital terrain models determination by LiDAR
-technology: Po basin experimentation. Bolletino di Geodesia e Scienze
-Affini, anno LXV, n. 2, pp. 69-89.
-<br>
-<br>
-Brovelli M. A., Cannata M., Longoni U.M., 2004. LIDAR Data Filtering and
-DTM Interpolation Within GRASS, Transactions in GIS, April 2004, vol. 8,
-iss. 2, pp. 155-174(20), Blackwell Publishing Ltd.
-<br>
-<br>
-Brovelli M. A., Cannata M., 2004. Digital Terrain model reconstruction in
-urban areas from airborne laser scanning data: the method and an example
-for Pavia (Northern Italy). Computers and Geosciences 30 (2004) pp.325-331
-<br>
-<br>
-Brovelli M. A. and Longoni U.M., 2003. Software per il filtraggio di dati
-LIDAR, Rivista dell?Agenzia del Territorio, n. 3-2003, pp. 11-22 (ISSN 1593-2192).
-<br>
-<br>
-Brovelli M. A., Cannata M. and Longoni U.M., 2002. DTM LIDAR in area urbana,
-Bollettino SIFET N.2, pp. 7-26.
-<br>
-<br>
-Performances of the filter can be seen in the
-<a HREF="http://www.itc.nl/isprswgIII-3/filtertest/MainDoc.htm">ISPRS WG III/3 Comparison of Filters</a>
-report by Sithole, G. and Vosselman, G., 2003.
-
-<p><i>Last changed: $Date$</i>
-
Copied: grass/trunk/vector/lidar/v.lidar.correction/v.lidar.correction.html (from rev 32770, grass/trunk/vector/lidar/v.lidar.correction/description.html)
===================================================================
--- grass/trunk/vector/lidar/v.lidar.correction/v.lidar.correction.html (rev 0)
+++ grass/trunk/vector/lidar/v.lidar.correction/v.lidar.correction.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,107 @@
+<h2>DESCRIPTION</h2>
+
+<em>v.lidar.correction</em> is the last of three steps to filter LiDAR
+data. The filter aims to recognize and extract attached and
+detached object (such as buildings, bridges, power lines, trees, etc.)
+in order to create a Digital Terrain Model.
+<br>
+<br>
+The module, which could be iterated several times, makes a comparison
+between the LiDAR observations and a bilinear spline interpolation with
+a Tychonov regularization parameter performed on the TERRAIN SINGLE PULSE
+points only. The gradient is minimized by the regularization parameter.
+Analysis of the residuals between the observations and the interpolated
+values results in four cases (the next classification is referred to that
+of the v.lidar.growing output vector):
+<br>
+<br>
+<b>a)</b> Points classified as TERRAIN differing more than a threshold
+ value are interpreted and reclassified as OBJECT, for both single and
+ double pulse points.
+<br>
+<br>
+<b>b)</b> Points classified as OBJECT and closed enough to the
+ interpolated surface are interpreted and reclassified as TERRAIN, for
+ both single and double pulse points.
+
+<h2>NOTES</h2>
+
+The input should be the output of <em>v.lidar.growing</em> module or the
+output of this <em>v.lidar.correction</em> itself. That means, this module
+could be applied more times (although, two are usually enough) for a better
+filter solution. The outputs are a vector map with a final point classification
+as as TERRAIN SINGLE PULSE, TERRAIN DOUBLE PULSE, OBJECT SINGLE PULSE or
+OBJECT DOUBLE PULSE; and an vector map with only the points classified as
+TERRAIN SINGLE PULSE or TERRAIN DOUBLE PULSE.
+
+The final result of the whole procedure (v.lidar.edgedetection,
+v.lidar.growing, v.lidar.correction) will be a point classification in
+four categories:
+<br>
+<br>
+TERRAIN SINGLE PULSE (cat = 1, layer = 2)
+<br>
+TERRAIN DOUBLE PULSE (cat = 2, layer = 2)
+<br>
+OBJECT SINGLE PULSE (cat = 3, layer = 2)
+<br>
+OBJECT DOUBLE PULSE (cat = 4, layer = 2)
+
+
+<h2>EXAMPLES</h2>
+
+<h4>Basic correction procedure</h4>
+<div class="code"><pre>
+v.lidar.correction input=growing output=correction out_terrain=only_terrain
+</pre></div>
+
+<h4>Second correction procedure</h4>
+<div class="code"><pre>
+v.lidar.correction input=correction output=correction_bis out_terrain=only_terrain_bis
+</pre></div>
+
+<h2>SEE ALSO</h2>
+<em><a HREF="v.lidar.edgedetection.html">v.lidar.edgedetection</a></em>,
+<em><a HREF="v.lidar.growing.html">v.lidar.growing</a></em>,
+<em><a HREF="v.surf.bspline.html">v.surf.bspline</a></em>
+
+<h2>AUTHORS</h2>
+Original version of program in GRASS 5.4:
+<BR>
+Maria Antonia Brovelli, Massimiliano Cannata, Ulisse Longoni and Mirko Reguzzoni
+<BR><BR>
+Update for GRASS 6.X:
+<BR>
+Roberto Antolin and Gonzalo Moreno
+
+<h2>REFERENCES</h2>
+
+Antolin, R. et al., 2006. Digital terrain models determination by LiDAR
+technology: Po basin experimentation. Bolletino di Geodesia e Scienze
+Affini, anno LXV, n. 2, pp. 69-89.
+<br>
+<br>
+Brovelli M. A., Cannata M., Longoni U.M., 2004. LIDAR Data Filtering and
+DTM Interpolation Within GRASS, Transactions in GIS, April 2004, vol. 8,
+iss. 2, pp. 155-174(20), Blackwell Publishing Ltd.
+<br>
+<br>
+Brovelli M. A., Cannata M., 2004. Digital Terrain model reconstruction in
+urban areas from airborne laser scanning data: the method and an example
+for Pavia (Northern Italy). Computers and Geosciences 30 (2004) pp.325-331
+<br>
+<br>
+Brovelli M. A. and Longoni U.M., 2003. Software per il filtraggio di dati
+LIDAR, Rivista dell?Agenzia del Territorio, n. 3-2003, pp. 11-22 (ISSN 1593-2192).
+<br>
+<br>
+Brovelli M. A., Cannata M. and Longoni U.M., 2002. DTM LIDAR in area urbana,
+Bollettino SIFET N.2, pp. 7-26.
+<br>
+<br>
+Performances of the filter can be seen in the
+<a HREF="http://www.itc.nl/isprswgIII-3/filtertest/MainDoc.htm">ISPRS WG III/3 Comparison of Filters</a>
+report by Sithole, G. and Vosselman, G., 2003.
+
+<p><i>Last changed: $Date$</i>
+
Deleted: grass/trunk/vector/lidar/v.lidar.edgedetection/description.html
===================================================================
--- grass/trunk/vector/lidar/v.lidar.edgedetection/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/vector/lidar/v.lidar.edgedetection/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,111 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>v.lidar.edgedetection</em> is the first of three steps to filter
-LiDAR data. The filter aims to recognize and extract attached and
-detached object (such as buildings, bridges, power lines, trees, etc.)
-in order to create a Digital Terrain Model.
-<br>
-<br>
-In particular, this module detects the edge of each single feature over
-the terrain surface of a LIDAR point surface. First of all, a bilinear
-spline interpolation with a Tychonov regularization parameter is
-performed. The gradient is minimized and the low Tychonov regularization
-parameter brings the interpolated functions as close as possible to the
-observations. Bicubic spline interpolation with Tychonov regularization
-is then performed. However, now the curvature is minimized and the
-regularization parameter is set to a high value. For each point, an
-interpolated value is computed from the bicubic surface and an interpolated
-gradient is computed from the bilinear surface. At each point the gradient
-magnitude and the direction of the edge vector are calculated, and the
-residual between interpolated and observed values is computed. Two thresholds
-are defined on the gradient, a high threshold <b>tgh</b> and a low one
-<b>tgl</b>. For each point, if the gradient magnitude is greater than or
-equal to the high threshold and its residual is greater than or equal to
-zero, it is labeled as an EDGE point. Similarly a point is labeled as
-being an EDGE point if the gradient magnitude is greater than or equal to
-the low threshold, its residual is greater than or equal to zero, and the
-gradient to two of eight neighboring points is greater than the high
-threshold. Other points are classified as TERRAIN.
-<br>
-<br>
-The output eill be a vector map in which points has been classified as
-TERRAIN, EDGE or UNKNOWN. This vector map should be the input of
-<em>v.lidar.growing</em> module.
-
-<h2>NOTES</h2>
-
-In this module, an external table will be created which will be useful for
-the next module of the procedure of LiDAR data filtering. In this table
-the interpolated height values of each point will be recorded. Also points
-in the output vector map will be classified as:
-<br>
-<br>
-EDGE (cat = 1, layer = 1)
-<br>
-TERRAIN (cat = 2, layer = 1)
-<br>
-<br>
-The final result of the whole procedure (v.lidar.edgedetection,
-v.lidar.growing, v.lidar.correction) will be a point classification in
-four categories:
-<br>
-<br>
-TERRAIN SINGLE PULSE (cat = 1, layer = 2)
-<br>
-TERRAIN DOUBLE PULSE (cat = 2, layer = 2)
-<br>
-OBJECT SINGLE PULSE (cat = 3, layer = 2)
-<br>
-OBJECT DOUBLE PULSE (cat = 4, layer = 2)
-
-<h2>EXAMPLES</h2>
-
-<h4>Basic edge detection</h4>
-<div class="code"><pre>
-v.lidar.edgedetection input=vector_last output=edge see=8 sen=8 lambda_g=0.5
-</pre></div>
-
-<h2>SEE ALSO</h2>
-<em><a HREF="v.lidar.growing.html">v.lidar.growing</a></em>,
-<em><a HREF="v.lidar.correction.html">v.lidar.correction</a></em>,
-<em><a HREF="v.surf.bspline.html">v.surf.bspline</a></em>
-
-<h2>AUTHORS</h2>
-Original version of program in GRASS 5.4:
-<BR>
-Maria Antonia Brovelli, Massimiliano Cannata, Ulisse Longoni and Mirko Reguzzoni
-<BR><BR>
-Update for GRASS 6.X:
-<BR>
-Roberto Antolin and Gonzalo Moreno
-
-<h2>REFERENCES</h2>
-
-Antolin, R. et al., 2006. Digital terrain models determination by LiDAR
-technology: Po basin experimentation. Bolletino di Geodesia e Scienze
-Affini, anno LXV, n. 2, pp. 69-89.
-<br>
-<br>
-Brovelli M. A., Cannata M., Longoni U.M., 2004. LIDAR Data Filtering and
-DTM Interpolation Within GRASS, Transactions in GIS, April 2004, vol. 8,
-iss. 2, pp. 155-174(20), Blackwell Publishing Ltd.
-<br>
-<br>
-Brovelli M. A., Cannata M., 2004. Digital Terrain model reconstruction in
-urban areas from airborne laser scanning data: the method and an example
-for Pavia (Northern Italy). Computers and Geosciences 30 (2004) pp.325-331
-<br>
-<br>
-Brovelli M. A. and Longoni U.M., 2003. Software per il filtraggio di dati
-LIDAR, Rivista dell?Agenzia del Territorio, n. 3-2003, pp. 11-22 (ISSN 1593-2192).
-<br>
-<br>
-Brovelli M. A., Cannata M. and Longoni U.M., 2002. DTM LIDAR in area urbana,
-Bollettino SIFET N.2, pp. 7-26.
-<br>
-<br>
-Performances of the filter can be seen in the
-<a HREF="http://www.itc.nl/isprswgIII-3/filtertest/MainDoc.htm">ISPRS WG III/3 Comparison of Filters</a>
-report by Sithole, G. and Vosselman, G., 2003.
-<br>
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/vector/lidar/v.lidar.edgedetection/v.lidar.edgedetection.html (from rev 32770, grass/trunk/vector/lidar/v.lidar.edgedetection/description.html)
===================================================================
--- grass/trunk/vector/lidar/v.lidar.edgedetection/v.lidar.edgedetection.html (rev 0)
+++ grass/trunk/vector/lidar/v.lidar.edgedetection/v.lidar.edgedetection.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,111 @@
+<h2>DESCRIPTION</h2>
+
+<em>v.lidar.edgedetection</em> is the first of three steps to filter
+LiDAR data. The filter aims to recognize and extract attached and
+detached object (such as buildings, bridges, power lines, trees, etc.)
+in order to create a Digital Terrain Model.
+<br>
+<br>
+In particular, this module detects the edge of each single feature over
+the terrain surface of a LIDAR point surface. First of all, a bilinear
+spline interpolation with a Tychonov regularization parameter is
+performed. The gradient is minimized and the low Tychonov regularization
+parameter brings the interpolated functions as close as possible to the
+observations. Bicubic spline interpolation with Tychonov regularization
+is then performed. However, now the curvature is minimized and the
+regularization parameter is set to a high value. For each point, an
+interpolated value is computed from the bicubic surface and an interpolated
+gradient is computed from the bilinear surface. At each point the gradient
+magnitude and the direction of the edge vector are calculated, and the
+residual between interpolated and observed values is computed. Two thresholds
+are defined on the gradient, a high threshold <b>tgh</b> and a low one
+<b>tgl</b>. For each point, if the gradient magnitude is greater than or
+equal to the high threshold and its residual is greater than or equal to
+zero, it is labeled as an EDGE point. Similarly a point is labeled as
+being an EDGE point if the gradient magnitude is greater than or equal to
+the low threshold, its residual is greater than or equal to zero, and the
+gradient to two of eight neighboring points is greater than the high
+threshold. Other points are classified as TERRAIN.
+<br>
+<br>
+The output eill be a vector map in which points has been classified as
+TERRAIN, EDGE or UNKNOWN. This vector map should be the input of
+<em>v.lidar.growing</em> module.
+
+<h2>NOTES</h2>
+
+In this module, an external table will be created which will be useful for
+the next module of the procedure of LiDAR data filtering. In this table
+the interpolated height values of each point will be recorded. Also points
+in the output vector map will be classified as:
+<br>
+<br>
+EDGE (cat = 1, layer = 1)
+<br>
+TERRAIN (cat = 2, layer = 1)
+<br>
+<br>
+The final result of the whole procedure (v.lidar.edgedetection,
+v.lidar.growing, v.lidar.correction) will be a point classification in
+four categories:
+<br>
+<br>
+TERRAIN SINGLE PULSE (cat = 1, layer = 2)
+<br>
+TERRAIN DOUBLE PULSE (cat = 2, layer = 2)
+<br>
+OBJECT SINGLE PULSE (cat = 3, layer = 2)
+<br>
+OBJECT DOUBLE PULSE (cat = 4, layer = 2)
+
+<h2>EXAMPLES</h2>
+
+<h4>Basic edge detection</h4>
+<div class="code"><pre>
+v.lidar.edgedetection input=vector_last output=edge see=8 sen=8 lambda_g=0.5
+</pre></div>
+
+<h2>SEE ALSO</h2>
+<em><a HREF="v.lidar.growing.html">v.lidar.growing</a></em>,
+<em><a HREF="v.lidar.correction.html">v.lidar.correction</a></em>,
+<em><a HREF="v.surf.bspline.html">v.surf.bspline</a></em>
+
+<h2>AUTHORS</h2>
+Original version of program in GRASS 5.4:
+<BR>
+Maria Antonia Brovelli, Massimiliano Cannata, Ulisse Longoni and Mirko Reguzzoni
+<BR><BR>
+Update for GRASS 6.X:
+<BR>
+Roberto Antolin and Gonzalo Moreno
+
+<h2>REFERENCES</h2>
+
+Antolin, R. et al., 2006. Digital terrain models determination by LiDAR
+technology: Po basin experimentation. Bolletino di Geodesia e Scienze
+Affini, anno LXV, n. 2, pp. 69-89.
+<br>
+<br>
+Brovelli M. A., Cannata M., Longoni U.M., 2004. LIDAR Data Filtering and
+DTM Interpolation Within GRASS, Transactions in GIS, April 2004, vol. 8,
+iss. 2, pp. 155-174(20), Blackwell Publishing Ltd.
+<br>
+<br>
+Brovelli M. A., Cannata M., 2004. Digital Terrain model reconstruction in
+urban areas from airborne laser scanning data: the method and an example
+for Pavia (Northern Italy). Computers and Geosciences 30 (2004) pp.325-331
+<br>
+<br>
+Brovelli M. A. and Longoni U.M., 2003. Software per il filtraggio di dati
+LIDAR, Rivista dell?Agenzia del Territorio, n. 3-2003, pp. 11-22 (ISSN 1593-2192).
+<br>
+<br>
+Brovelli M. A., Cannata M. and Longoni U.M., 2002. DTM LIDAR in area urbana,
+Bollettino SIFET N.2, pp. 7-26.
+<br>
+<br>
+Performances of the filter can be seen in the
+<a HREF="http://www.itc.nl/isprswgIII-3/filtertest/MainDoc.htm">ISPRS WG III/3 Comparison of Filters</a>
+report by Sithole, G. and Vosselman, G., 2003.
+<br>
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/vector/lidar/v.lidar.growing/description.html
===================================================================
--- grass/trunk/vector/lidar/v.lidar.growing/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/vector/lidar/v.lidar.growing/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,95 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>v.lidar.growing</em> is the second of three steps to filter LiDAR data.
-The filter aims to recognize and extract attached and detached object
-(such as buildings, bridges, power lines, trees, etc.) in order to create
-a Digital Terrain Model.
-<br>
-<br>
-The modules identifies which is the internal area of every object on a
-LiDAR point surface. The classification categories from
-<em>v.lidar.edgedetection</em> are now rasterized. For each cell, it is
-evaluated if it (the cell) contains a point with double impulse (difference
-between the first and last pulse greater than a given threshold). Starting
-from cells classified as OBJECT and with only one pulse all linked cells
-are selected and a convex hull algorithm is applied to them. Simultaneously,
-the mean of the corresponding heights (mean edge height) are computed.
-Points inside the convex hull are classified as OBJECT if their height is
-greater than or equal to the previously mean computed edge height. This
-last step is done only in case of high planimetric resolution.
-
-<h2>NOTES</h2>
-
-The input data should be the output result of the <em>v.lidar.correction</em>
-module. Otherwise, it goes to error! The output of this module will be
-the input of <em>v.lidar.correction</em> module. The output will be a vector
-map which points are pre-classified as:
-<br>
-<br>
-TERRAIN SINGLE PULSE (cat = 1, layer = 2)
-<br>
-TERRAIN DOUBLE PULSE (cat = 2, layer = 2)
-<br>
-OBJECT SINGLE PULSE (cat = 3, layer = 2)
-<br>
-OBJECT DOUBLE PULSE (cat = 4, layer = 2)
-<br>
-<br>
-
-The final result of the whole procedure (v.lidar.edgedetection,
-v.lidar.growing, v.lidar.correction) will be a point classification in the
-same categories as above.
-
-<h2>EXAMPLES</h2>
-
-<h4>Basic region growing procedure</h4>
-<div class="code"><pre>
-v.lidar.growing input=edge output=growing
-</pre></div>
-
-<h2>SEE ALSO</h2>
-<em><a HREF="v.lidar.edgedetection.html">v.lidar.edgedetection</a></em>,
-<em><a HREF="v.lidar.correction.html">v.lidar.correction</a></em>,
-<em><a HREF="v.surf.bspline.html">v.surf.bspline</a></em>
-
-<h2>AUTHOR</h2>
-Original version of program in GRASS 5.4:
-<BR>
-Maria Antonia Brovelli, Massimiliano Cannata, Ulisse Longoni and Mirko Reguzzoni
-<BR><BR>
-Update for GRASS 6.X:
-<BR>
-Roberto Antolin and Gonzalo Moreno
-
-<h2>REFERENCES</h2>
-
-Antolin, R. et al., 2006. Digital terrain models determination by LiDAR
-technology: Po basin experimentation. Bolletino di Geodesia e Scienze
-Affini, anno LXV, n. 2, pp. 69-89.
-<br>
-<br>
-Brovelli M. A., Cannata M., Longoni U.M., 2004. LIDAR Data Filtering and
-DTM Interpolation Within GRASS, Transactions in GIS, April 2004, vol. 8,
-iss. 2, pp. 155-174(20), Blackwell Publishing Ltd.
-<br>
-<br>
-Brovelli M. A., Cannata M., 2004. Digital Terrain model reconstruction in
-urban areas from airborne laser scanning data: the method and an example
-for Pavia (Northern Italy). Computers and Geosciences 30 (2004) pp.325-331
-<br>
-<br>
-Brovelli M. A. and Longoni U.M., 2003. Software per il filtraggio di dati
-LIDAR, Rivista dell?Agenzia del Territorio, n. 3-2003, pp. 11-22 (ISSN 1593-2192).
-<br>
-<br>
-Brovelli M. A., Cannata M. and Longoni U.M., 2002. DTM LIDAR in area urbana,
-Bollettino SIFET N.2, pp. 7-26.
-<br>
-<br>
-Performances of the filter can be seen in the
-<a HREF="http://www.itc.nl/isprswgIII-3/filtertest/MainDoc.htm">ISPRS WG III/3 Comparison of Filters</a>
-report by Sithole, G. and Vosselman, G., 2003.
-<br>
-
-<p><i>Last changed: $Date$</i>
-
Copied: grass/trunk/vector/lidar/v.lidar.growing/v.lidar.growing.html (from rev 32770, grass/trunk/vector/lidar/v.lidar.growing/description.html)
===================================================================
--- grass/trunk/vector/lidar/v.lidar.growing/v.lidar.growing.html (rev 0)
+++ grass/trunk/vector/lidar/v.lidar.growing/v.lidar.growing.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,95 @@
+<h2>DESCRIPTION</h2>
+
+<em>v.lidar.growing</em> is the second of three steps to filter LiDAR data.
+The filter aims to recognize and extract attached and detached object
+(such as buildings, bridges, power lines, trees, etc.) in order to create
+a Digital Terrain Model.
+<br>
+<br>
+The modules identifies which is the internal area of every object on a
+LiDAR point surface. The classification categories from
+<em>v.lidar.edgedetection</em> are now rasterized. For each cell, it is
+evaluated if it (the cell) contains a point with double impulse (difference
+between the first and last pulse greater than a given threshold). Starting
+from cells classified as OBJECT and with only one pulse all linked cells
+are selected and a convex hull algorithm is applied to them. Simultaneously,
+the mean of the corresponding heights (mean edge height) are computed.
+Points inside the convex hull are classified as OBJECT if their height is
+greater than or equal to the previously mean computed edge height. This
+last step is done only in case of high planimetric resolution.
+
+<h2>NOTES</h2>
+
+The input data should be the output result of the <em>v.lidar.correction</em>
+module. Otherwise, it goes to error! The output of this module will be
+the input of <em>v.lidar.correction</em> module. The output will be a vector
+map which points are pre-classified as:
+<br>
+<br>
+TERRAIN SINGLE PULSE (cat = 1, layer = 2)
+<br>
+TERRAIN DOUBLE PULSE (cat = 2, layer = 2)
+<br>
+OBJECT SINGLE PULSE (cat = 3, layer = 2)
+<br>
+OBJECT DOUBLE PULSE (cat = 4, layer = 2)
+<br>
+<br>
+
+The final result of the whole procedure (v.lidar.edgedetection,
+v.lidar.growing, v.lidar.correction) will be a point classification in the
+same categories as above.
+
+<h2>EXAMPLES</h2>
+
+<h4>Basic region growing procedure</h4>
+<div class="code"><pre>
+v.lidar.growing input=edge output=growing
+</pre></div>
+
+<h2>SEE ALSO</h2>
+<em><a HREF="v.lidar.edgedetection.html">v.lidar.edgedetection</a></em>,
+<em><a HREF="v.lidar.correction.html">v.lidar.correction</a></em>,
+<em><a HREF="v.surf.bspline.html">v.surf.bspline</a></em>
+
+<h2>AUTHOR</h2>
+Original version of program in GRASS 5.4:
+<BR>
+Maria Antonia Brovelli, Massimiliano Cannata, Ulisse Longoni and Mirko Reguzzoni
+<BR><BR>
+Update for GRASS 6.X:
+<BR>
+Roberto Antolin and Gonzalo Moreno
+
+<h2>REFERENCES</h2>
+
+Antolin, R. et al., 2006. Digital terrain models determination by LiDAR
+technology: Po basin experimentation. Bolletino di Geodesia e Scienze
+Affini, anno LXV, n. 2, pp. 69-89.
+<br>
+<br>
+Brovelli M. A., Cannata M., Longoni U.M., 2004. LIDAR Data Filtering and
+DTM Interpolation Within GRASS, Transactions in GIS, April 2004, vol. 8,
+iss. 2, pp. 155-174(20), Blackwell Publishing Ltd.
+<br>
+<br>
+Brovelli M. A., Cannata M., 2004. Digital Terrain model reconstruction in
+urban areas from airborne laser scanning data: the method and an example
+for Pavia (Northern Italy). Computers and Geosciences 30 (2004) pp.325-331
+<br>
+<br>
+Brovelli M. A. and Longoni U.M., 2003. Software per il filtraggio di dati
+LIDAR, Rivista dell?Agenzia del Territorio, n. 3-2003, pp. 11-22 (ISSN 1593-2192).
+<br>
+<br>
+Brovelli M. A., Cannata M. and Longoni U.M., 2002. DTM LIDAR in area urbana,
+Bollettino SIFET N.2, pp. 7-26.
+<br>
+<br>
+Performances of the filter can be seen in the
+<a HREF="http://www.itc.nl/isprswgIII-3/filtertest/MainDoc.htm">ISPRS WG III/3 Comparison of Filters</a>
+report by Sithole, G. and Vosselman, G., 2003.
+<br>
+
+<p><i>Last changed: $Date$</i>
+
Deleted: grass/trunk/vector/lidar/v.outlier/description.html
===================================================================
--- grass/trunk/vector/lidar/v.outlier/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/vector/lidar/v.outlier/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,55 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>v.outlier</em> removes outlier points. By default, the outlier
-identification is done by a bicubic spline interpolation of the
-observation with a high regularization parameter and a low resolution
-in south-north and east-west directions. Those points that differ in
-an absolute value more than the given threshold from a fixed value,
-reckoned from its surroundings by the interpolation, are considered as
-an outlier, and hence are removed.
-
-There is a flag to create a vector that can be visualizated by
-qgis. That means that topology is build and the z coordinate is
-considered as a category.
-
-<h2>EXAMPLES</h2>
-
-<h4>Basic outlier removal</h4>
-
-<div class="code"><pre>
-v.outlier input=vector_map output=vector_output outlier=vector_outlier thres_O=25
-</pre></div>
-
-In this case, a basic outlier removal is done with a threshold of 25 m.
-
-<h4>Basic outlier removal</h4>
-
-<div class="code"><pre>
-v.outlier -q input=vector_map output=vector_output outlier=vector_outlier qgis=vector_qgis
-</pre></div>
-
-Now, the outlier removal uses the default threshold and there is also
-an output vector available for visualizaton in QGIS
- (<a href="http://www.qgis.org">http://www.qgis.org</a>).
-
-<h2>NOTES</h2>
-
-This module is designed to work with LIDAR data, so not topology is
-built but in the QGIS output.
-
-<h2>SEE ALSO</h2>
-
-<em><a HREF="v.surf.bspline.html">v.surf.bspline</a></em>
-
-<h2>AUTHORS</h2>
-
-Original version of the program in GRASS 5.4:
-<BR>
-Maria Antonia Brovelli, Massimiliano Cannata, Ulisse Longoni and Mirko Reguzzoni
-<BR><BR>
-Updates for GRASS 6:
-<BR>
-Roberto Antolin
-
-<p>
-<i>Last changed: $Date$</i>
Copied: grass/trunk/vector/lidar/v.outlier/v.outlier.html (from rev 32770, grass/trunk/vector/lidar/v.outlier/description.html)
===================================================================
--- grass/trunk/vector/lidar/v.outlier/v.outlier.html (rev 0)
+++ grass/trunk/vector/lidar/v.outlier/v.outlier.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,55 @@
+<h2>DESCRIPTION</h2>
+
+<em>v.outlier</em> removes outlier points. By default, the outlier
+identification is done by a bicubic spline interpolation of the
+observation with a high regularization parameter and a low resolution
+in south-north and east-west directions. Those points that differ in
+an absolute value more than the given threshold from a fixed value,
+reckoned from its surroundings by the interpolation, are considered as
+an outlier, and hence are removed.
+
+There is a flag to create a vector that can be visualizated by
+qgis. That means that topology is build and the z coordinate is
+considered as a category.
+
+<h2>EXAMPLES</h2>
+
+<h4>Basic outlier removal</h4>
+
+<div class="code"><pre>
+v.outlier input=vector_map output=vector_output outlier=vector_outlier thres_O=25
+</pre></div>
+
+In this case, a basic outlier removal is done with a threshold of 25 m.
+
+<h4>Basic outlier removal</h4>
+
+<div class="code"><pre>
+v.outlier -q input=vector_map output=vector_output outlier=vector_outlier qgis=vector_qgis
+</pre></div>
+
+Now, the outlier removal uses the default threshold and there is also
+an output vector available for visualizaton in QGIS
+ (<a href="http://www.qgis.org">http://www.qgis.org</a>).
+
+<h2>NOTES</h2>
+
+This module is designed to work with LIDAR data, so not topology is
+built but in the QGIS output.
+
+<h2>SEE ALSO</h2>
+
+<em><a HREF="v.surf.bspline.html">v.surf.bspline</a></em>
+
+<h2>AUTHORS</h2>
+
+Original version of the program in GRASS 5.4:
+<BR>
+Maria Antonia Brovelli, Massimiliano Cannata, Ulisse Longoni and Mirko Reguzzoni
+<BR><BR>
+Updates for GRASS 6:
+<BR>
+Roberto Antolin
+
+<p>
+<i>Last changed: $Date$</i>
Deleted: grass/trunk/vector/lidar/v.surf.bspline/description.html
===================================================================
--- grass/trunk/vector/lidar/v.surf.bspline/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/vector/lidar/v.surf.bspline/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,166 +0,0 @@
-<h2>DESCRIPTION</h2>
-<em>v.surf.bspline</em> makes a bilinear/bicubic spline interpolation
-with Tykhonov regularization. The required input is an only 3d points
-vector map that will be used to interpolate a reference surface.
-<br>
-<br>
-Interpolation is carried out by adjusting a Least-Squares (LS) system
-in which the parameters to estime are spline functions. The number of
-splines doesn't depend on the resolution region, but it depends on the
-spline steps values in the north-south and west-east directions. These
-spline steps are set by "<b><i>sin=</i></b>" and "<b><i>sie=</i></b>",
-respectively. If the number of splines is bigger than the number of
-points, the LS system is bad conditioned because there are more unkowns
-than observations. In that case the LS normal matrix can't be inverted.
-To allow the inversion of the normal matrix a Tykhonov regularization
-is done. The minimizing function is the gradient in the case of a bilinear
-interpolation, and the curvature in the bicubic interpolation. The
-lambda_i parameter associated with the regularization smooths the
-interpolation. The higher the lambda_i parameter, the smoother the
-interpolation.
-<br>
-<br>
-The number of splines has a great influence on two things, mainly. The
-first thing is the module's execution time. The second is the RAM use.
-The higher the number of splines, the longer the time of execution and
-the higher RAM use. A numerical example: 100 splines in each direction
-imply 10e4 splines in total, that is, a square LS normal matrix of 10e4
-size. Inverting this matrix means inverting 100 millions elements!
-To improve this problems a Tcholebsky method with triangulars matrixes
-is used in the normal matrix inversion. It has also fixed a maximum number
-of splines for each direction. However, it is also possible running the
-module with a higher number of splines. For a number of spline higher than
-the fixed maximum, the whole region is divided into smaller regions. Each
-subregion is 150x150 splines wide. To avoid contour problems, the subregions
-are overlaped one to each other. To estimate a single value within the
-overlaped zones, a weighted mean considering the point positions into each
-subregion is carried out.
-<br>
-<br>
-The required input is a 3d points vector. If nothing is specified z-coordinates
-will be used in the interpolation. It could be also possible to consider
-an attribute value by specifying "<b><i>layer=</i></b>" and "<b><i>column=</i></b>"
-parameters. If a vector map with another type of features is used, only
-points will be considered. If the "<b><i>sparse=</i></b>" vector is
-used, the "<b><i>input=</i></b>" vector map will be used to create a
-reference surface. This surface will be used to make an estimation on the
-points within the "<b><i>sparse=</i></b>". In this case a vector output
-("<b><i>output=</i></b>") must be specify. If the "<b><i>sparse=</i></b>"
-is not supplied, the final interpolation output will be the interpolated
-reference surface from the "<b><i>input=</i></b>" vector map. In this case,
-one of both the raster or vector output format can be choosen. For raster
-format ("<b><i>raster=</i></b>"), the point estimation will be done
-on a regular grid with a resolution equal to the GRASS region. For vector
-format, the estimation will be done on the sparse points of the
-"<b><i>input=</i></b>" vector supplied. Both, vector and raster output,
-are not allowed simultaneously.
-<br>
-<br>
-A cross validation method has been implemented. It helps to find the optimal
-lambda_i value that fits the data. It shows the <i>mean</i> and <i>rms</i>
-of the residuals from the true point value and the estimated from the
-interpolation made with all the data without the point itself. This procedure
-is done for fixed lambda_i values. The results of the cross validation will
-appear in the stdout and no vector nor raster output will be created. The
-external input ("<b><i>sparse=</i></b>") will be not considered. Due to
-the nature of the algorithm, it is advised the user no to try the cross-
-validation with more than 100 points at a time because it will take too long.
-The execution time could be reduced by considering a lower number of splines.
-Although, as seen, it is possible to use a high number of splines, more than
-150x150 splines is not recommended.
-<br>
-<br>
-In a raster map output ("<b><i>raster=</i></b>"), region resolution implying
-more than 2000x2000 (4 mill) cells are not allowed. If the user tries with a
-more than those cells an error message will ask for a lower region resolution.
-
-<h2>EXAMPLES</h2>
-
-<h4>Basic interpolation</h4>
-
-<div class="code"><pre>
-v.surf.bspline input=point_vector output=interpolate_surface type=bicubic
-</pre></div>
-
-In this case, a bicubic spline interpolation will be done and an
-estimation on the points of point_vector will be the output.
-
-<h4>Basic interpolation and raster output with a long spline step</h4>
-
-<div class="code"><pre>
-v.surf.bspline input=point_vector raster=interpolate_surface sie=25 sin=25
-</pre></div>
-
-Now, a bilinear spline interpolation will be done on a grid. The spline steps
-are set to 25. It doesn't mean that the grid will have a resolution equal to 25,
-but that each 25 units there will be a spline.
-
-<h4> Estimation of lambda_i parameter with a cross validation proccess</h4>
-
-<div class="code"><pre>
-v.surf.bspline -c input=point_vector
-</pre></div>
-
-
-<h4>Estimation on sparse points</h4>
-
-<div class="code"><pre>
-v.surf.bspline input=point_vector sparse=sparse_points output=interpolate_surface
-</pre></div>
-
-In this last case, an estimation on the points of the sparse_points vector
-will be done. The reference surface used for this estimation will be that
-interpolated using the point_vector vector.
-
-<h4>Using attribute values instead Z-coordinates</h4>
-<div class="code"><pre>
-v.surf.bspline input=point_vector raster=interpolate_surface layer=1 column=attrib_column
-</pre></div>
-
-This last case, the module uses the attribute values in attrib_column
-in the table associated to layer 1.
-
-<h2>BUGS</h2>
-Known issues:
-<br>
-<br>
-In order to avoid RAM memory problems, an auxiliar table will be needed for
-recording some intermediate calculi. Since the "<b>GROUP BY</b>" SQL function is used,
-which is not supported by the "<b>dbf</b>" driver, this driver is not
-allowed with the vector map output "<b><i>output=</i></b>". There is no problem
-with the raster map output.
-<br>
-<br>
-At this time, using the external vector input ("<b><i>sparse=</i></b>") implies
-interpoling with Z-coordinates. Updates to allow using attribute values
-will be done in a near future (I hope).
-<br>
-<br>
-
-
-<h2>SEE ALSO</h2>
-<em><a HREF="v.surf.rst.html">v.surf.rst</a></em>
-
-<h2>AUTHORS</h2>
-Original version in GRASS 5.4: (s.bspline.reg)
-<BR>
-Maria Antonia Brovelli, Massimiliano Cannata, Ulisse Longoni, Mirko Reguzzoni
-<BR><BR>
-Update for GRASS 6.X and improvements:
-<BR>
-Roberto Antolin
-
-<h2>REFERENCES</h2>
-Brovelli M. A., Cannata M., and Longoni U.M., 2004, LIDAR Data Filtering and DTM Interpolation Within GRASS, Transactions in GIS, April 2004, vol. 8, iss. 2, pp. 155-174(20), Blackwell Publishing Ltd
-<br>
-<br>
-Brovelli M. A. and Cannata M., 2004, Digital Terrain model reconstruction in urban areas from airborne laser scanning data: the method and an example for Pavia (Northern Italy). Computers and Geosciences 30, pp.325-331
-<br>
-<br>
-Brovelli M. A e Longoni U.M., 2003, Software per il filtraggio di dati LIDAR, Rivista dell'Agenzia del Territorio, n. 3-2003, pp. 11-22 (ISSN 1593-2192)
-<br>
-<br>
-Brovelli M. A., Cannata M. and Longoni U.M., 2002, DTM LIDAR in area urbana, Bollettino SIFET N.2, 2002, pp. 7-26
-<br>
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/vector/lidar/v.surf.bspline/v.surf.bspline.html (from rev 32770, grass/trunk/vector/lidar/v.surf.bspline/description.html)
===================================================================
--- grass/trunk/vector/lidar/v.surf.bspline/v.surf.bspline.html (rev 0)
+++ grass/trunk/vector/lidar/v.surf.bspline/v.surf.bspline.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,166 @@
+<h2>DESCRIPTION</h2>
+<em>v.surf.bspline</em> makes a bilinear/bicubic spline interpolation
+with Tykhonov regularization. The required input is an only 3d points
+vector map that will be used to interpolate a reference surface.
+<br>
+<br>
+Interpolation is carried out by adjusting a Least-Squares (LS) system
+in which the parameters to estime are spline functions. The number of
+splines doesn't depend on the resolution region, but it depends on the
+spline steps values in the north-south and west-east directions. These
+spline steps are set by "<b><i>sin=</i></b>" and "<b><i>sie=</i></b>",
+respectively. If the number of splines is bigger than the number of
+points, the LS system is bad conditioned because there are more unkowns
+than observations. In that case the LS normal matrix can't be inverted.
+To allow the inversion of the normal matrix a Tykhonov regularization
+is done. The minimizing function is the gradient in the case of a bilinear
+interpolation, and the curvature in the bicubic interpolation. The
+lambda_i parameter associated with the regularization smooths the
+interpolation. The higher the lambda_i parameter, the smoother the
+interpolation.
+<br>
+<br>
+The number of splines has a great influence on two things, mainly. The
+first thing is the module's execution time. The second is the RAM use.
+The higher the number of splines, the longer the time of execution and
+the higher RAM use. A numerical example: 100 splines in each direction
+imply 10e4 splines in total, that is, a square LS normal matrix of 10e4
+size. Inverting this matrix means inverting 100 millions elements!
+To improve this problems a Tcholebsky method with triangulars matrixes
+is used in the normal matrix inversion. It has also fixed a maximum number
+of splines for each direction. However, it is also possible running the
+module with a higher number of splines. For a number of spline higher than
+the fixed maximum, the whole region is divided into smaller regions. Each
+subregion is 150x150 splines wide. To avoid contour problems, the subregions
+are overlaped one to each other. To estimate a single value within the
+overlaped zones, a weighted mean considering the point positions into each
+subregion is carried out.
+<br>
+<br>
+The required input is a 3d points vector. If nothing is specified z-coordinates
+will be used in the interpolation. It could be also possible to consider
+an attribute value by specifying "<b><i>layer=</i></b>" and "<b><i>column=</i></b>"
+parameters. If a vector map with another type of features is used, only
+points will be considered. If the "<b><i>sparse=</i></b>" vector is
+used, the "<b><i>input=</i></b>" vector map will be used to create a
+reference surface. This surface will be used to make an estimation on the
+points within the "<b><i>sparse=</i></b>". In this case a vector output
+("<b><i>output=</i></b>") must be specify. If the "<b><i>sparse=</i></b>"
+is not supplied, the final interpolation output will be the interpolated
+reference surface from the "<b><i>input=</i></b>" vector map. In this case,
+one of both the raster or vector output format can be choosen. For raster
+format ("<b><i>raster=</i></b>"), the point estimation will be done
+on a regular grid with a resolution equal to the GRASS region. For vector
+format, the estimation will be done on the sparse points of the
+"<b><i>input=</i></b>" vector supplied. Both, vector and raster output,
+are not allowed simultaneously.
+<br>
+<br>
+A cross validation method has been implemented. It helps to find the optimal
+lambda_i value that fits the data. It shows the <i>mean</i> and <i>rms</i>
+of the residuals from the true point value and the estimated from the
+interpolation made with all the data without the point itself. This procedure
+is done for fixed lambda_i values. The results of the cross validation will
+appear in the stdout and no vector nor raster output will be created. The
+external input ("<b><i>sparse=</i></b>") will be not considered. Due to
+the nature of the algorithm, it is advised the user no to try the cross-
+validation with more than 100 points at a time because it will take too long.
+The execution time could be reduced by considering a lower number of splines.
+Although, as seen, it is possible to use a high number of splines, more than
+150x150 splines is not recommended.
+<br>
+<br>
+In a raster map output ("<b><i>raster=</i></b>"), region resolution implying
+more than 2000x2000 (4 mill) cells are not allowed. If the user tries with a
+more than those cells an error message will ask for a lower region resolution.
+
+<h2>EXAMPLES</h2>
+
+<h4>Basic interpolation</h4>
+
+<div class="code"><pre>
+v.surf.bspline input=point_vector output=interpolate_surface type=bicubic
+</pre></div>
+
+In this case, a bicubic spline interpolation will be done and an
+estimation on the points of point_vector will be the output.
+
+<h4>Basic interpolation and raster output with a long spline step</h4>
+
+<div class="code"><pre>
+v.surf.bspline input=point_vector raster=interpolate_surface sie=25 sin=25
+</pre></div>
+
+Now, a bilinear spline interpolation will be done on a grid. The spline steps
+are set to 25. It doesn't mean that the grid will have a resolution equal to 25,
+but that each 25 units there will be a spline.
+
+<h4> Estimation of lambda_i parameter with a cross validation proccess</h4>
+
+<div class="code"><pre>
+v.surf.bspline -c input=point_vector
+</pre></div>
+
+
+<h4>Estimation on sparse points</h4>
+
+<div class="code"><pre>
+v.surf.bspline input=point_vector sparse=sparse_points output=interpolate_surface
+</pre></div>
+
+In this last case, an estimation on the points of the sparse_points vector
+will be done. The reference surface used for this estimation will be that
+interpolated using the point_vector vector.
+
+<h4>Using attribute values instead Z-coordinates</h4>
+<div class="code"><pre>
+v.surf.bspline input=point_vector raster=interpolate_surface layer=1 column=attrib_column
+</pre></div>
+
+This last case, the module uses the attribute values in attrib_column
+in the table associated to layer 1.
+
+<h2>BUGS</h2>
+Known issues:
+<br>
+<br>
+In order to avoid RAM memory problems, an auxiliar table will be needed for
+recording some intermediate calculi. Since the "<b>GROUP BY</b>" SQL function is used,
+which is not supported by the "<b>dbf</b>" driver, this driver is not
+allowed with the vector map output "<b><i>output=</i></b>". There is no problem
+with the raster map output.
+<br>
+<br>
+At this time, using the external vector input ("<b><i>sparse=</i></b>") implies
+interpoling with Z-coordinates. Updates to allow using attribute values
+will be done in a near future (I hope).
+<br>
+<br>
+
+
+<h2>SEE ALSO</h2>
+<em><a HREF="v.surf.rst.html">v.surf.rst</a></em>
+
+<h2>AUTHORS</h2>
+Original version in GRASS 5.4: (s.bspline.reg)
+<BR>
+Maria Antonia Brovelli, Massimiliano Cannata, Ulisse Longoni, Mirko Reguzzoni
+<BR><BR>
+Update for GRASS 6.X and improvements:
+<BR>
+Roberto Antolin
+
+<h2>REFERENCES</h2>
+Brovelli M. A., Cannata M., and Longoni U.M., 2004, LIDAR Data Filtering and DTM Interpolation Within GRASS, Transactions in GIS, April 2004, vol. 8, iss. 2, pp. 155-174(20), Blackwell Publishing Ltd
+<br>
+<br>
+Brovelli M. A. and Cannata M., 2004, Digital Terrain model reconstruction in urban areas from airborne laser scanning data: the method and an example for Pavia (Northern Italy). Computers and Geosciences 30, pp.325-331
+<br>
+<br>
+Brovelli M. A e Longoni U.M., 2003, Software per il filtraggio di dati LIDAR, Rivista dell'Agenzia del Territorio, n. 3-2003, pp. 11-22 (ISSN 1593-2192)
+<br>
+<br>
+Brovelli M. A., Cannata M. and Longoni U.M., 2002, DTM LIDAR in area urbana, Bollettino SIFET N.2, 2002, pp. 7-26
+<br>
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/vector/v.buffer/description.html
===================================================================
--- grass/trunk/vector/v.buffer/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/vector/v.buffer/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,69 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>v.buffer</em> creates a buffer around features of given <b>type</b>, which
-have a category in the given <b>layer</b>. The <b>tolerance</b> controls
-the number of vector segments being generated (the smaller the value, the more
-vector segments are generated).
-
-<h2>NOTES</h2>
-
-Attributes are not transferred due to potential buffer overlap, which
-cannot be resolved automatically.
-
-<h2>EXAMPLES</h2>
-
-<h3>Buffer around input lines</h3>
-
-<div class="code"><pre>
-v.buffer input=map output=buffer type=line buffer=100
-</pre></div>
-
-<h3>Circles around input points</h3>
-
-<div class="code"><pre>
-v.buffer input=pointsmap output=circles type=point buffer=1000
-</pre></div>
-
-<h3>Non-overlapping circles around input points with attribute transfer</h3>
-
-<div class="code"><pre>
-v.buffer input=archsites output=circles type=point buffer=200
-# change original points to centroids:
-v.type in=archsites out=archcentroids type=point,centroid
-# patch circles and centroids:
-v.patch in=archcentroids,circles out=circles_db
-# attach attributes, either use
-# db.copy ...
-# or link to the original table:
-v.db.connect map=circles_db table=archsites field=1 key=cat driver=dbf \
-database='$GISDBASE/$LOCATION_NAME/$MAPSET/dbf'
-</pre></div>
-
-<h2>BUGS</h2>
-
-For some data <em>v.buffer</em> can produce strange results, especially if
-the buffer size is bigger than input features. Usually you can solve the
-problem if you run <em>v.buffer</em> more times with smaller buffer.
-<P>
-The <b>bufcol</b> dynamic buffer distance parameter has problems cleaning
-complex features (holes left filled, etc.). If you experience problems, try
-running <em>v.buffer</em> multiple times with a single buffer distance, patch
-the results with <em>v.patch</em> and remove any overlaps with
-<em>v.extract -d</em>.
-
-<h2>SEE ALSO</h2>
-
-<em>
-<a HREF="r.buffer.html">r.buffer</a>,
-<a HREF="v.extract.html">v.extract</a>,
-<a HREF="v.type.html">v.type</a>,
-<a HREF="v.patch.html">v.patch</a>,
-<a HREF="v.db.connect.html">v.db.connect</a>
-</em>
-
-<h2>AUTHOR</h2>
-
-Radim Blazek
-
-<p>
-<i>Last changed: $Date$</i>
Copied: grass/trunk/vector/v.buffer/v.buffer.html (from rev 32770, grass/trunk/vector/v.buffer/description.html)
===================================================================
--- grass/trunk/vector/v.buffer/v.buffer.html (rev 0)
+++ grass/trunk/vector/v.buffer/v.buffer.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,69 @@
+<h2>DESCRIPTION</h2>
+
+<em>v.buffer</em> creates a buffer around features of given <b>type</b>, which
+have a category in the given <b>layer</b>. The <b>tolerance</b> controls
+the number of vector segments being generated (the smaller the value, the more
+vector segments are generated).
+
+<h2>NOTES</h2>
+
+Attributes are not transferred due to potential buffer overlap, which
+cannot be resolved automatically.
+
+<h2>EXAMPLES</h2>
+
+<h3>Buffer around input lines</h3>
+
+<div class="code"><pre>
+v.buffer input=map output=buffer type=line buffer=100
+</pre></div>
+
+<h3>Circles around input points</h3>
+
+<div class="code"><pre>
+v.buffer input=pointsmap output=circles type=point buffer=1000
+</pre></div>
+
+<h3>Non-overlapping circles around input points with attribute transfer</h3>
+
+<div class="code"><pre>
+v.buffer input=archsites output=circles type=point buffer=200
+# change original points to centroids:
+v.type in=archsites out=archcentroids type=point,centroid
+# patch circles and centroids:
+v.patch in=archcentroids,circles out=circles_db
+# attach attributes, either use
+# db.copy ...
+# or link to the original table:
+v.db.connect map=circles_db table=archsites field=1 key=cat driver=dbf \
+database='$GISDBASE/$LOCATION_NAME/$MAPSET/dbf'
+</pre></div>
+
+<h2>BUGS</h2>
+
+For some data <em>v.buffer</em> can produce strange results, especially if
+the buffer size is bigger than input features. Usually you can solve the
+problem if you run <em>v.buffer</em> more times with smaller buffer.
+<P>
+The <b>bufcol</b> dynamic buffer distance parameter has problems cleaning
+complex features (holes left filled, etc.). If you experience problems, try
+running <em>v.buffer</em> multiple times with a single buffer distance, patch
+the results with <em>v.patch</em> and remove any overlaps with
+<em>v.extract -d</em>.
+
+<h2>SEE ALSO</h2>
+
+<em>
+<a HREF="r.buffer.html">r.buffer</a>,
+<a HREF="v.extract.html">v.extract</a>,
+<a HREF="v.type.html">v.type</a>,
+<a HREF="v.patch.html">v.patch</a>,
+<a HREF="v.db.connect.html">v.db.connect</a>
+</em>
+
+<h2>AUTHOR</h2>
+
+Radim Blazek
+
+<p>
+<i>Last changed: $Date$</i>
Deleted: grass/trunk/vector/v.build/description.html
===================================================================
--- grass/trunk/vector/v.build/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/vector/v.build/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,43 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>v.build</em> builds support files for (binary)
-GRASS vector data files. These support files supply
-topology and category information that are needed by other
-GRASS modules.
-<p>
-GRASS is generating these support files automatically,
-only in rare cases the user has to (re)build them.
-<p>
-Refer to
-<em><a href="vectorintro.html">Vector data processing in GRASS GIS</a></em>
-for more information on GRASS GIS vector data model.
-
-<h2>NOTES</h2>
-
-<em>v.build</em> creates support files only for binary
-vector maps located in the user's current mapset. If vector map
-is located in another mapset, you need to specify this:
-
-<p>
-<div class="code"><pre>
-v.build map=geology at PERMANENT
-</pre></div>
-
-<P>
-In case of errors, the user can optionally generate an <em>error</em>
-vector map containing the erroneous vectors for later inspection.
-
-<h2>SEE ALSO</h2>
-
-<em><a href="v.build.polylines.html">v.build.polylines</a></em>
-
-<h2>AUTHORS</h2>
-
-Dave Gerdes, U.S.Army Construction Engineering
-Research Laboratory,<br>
-Michael Higgins,
-U.S.Army Construction Engineering
-Research Laboratory,<br>
-Radim Blazek, ITC-irst, Trento, Italy
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/vector/v.build/v.build.html (from rev 32770, grass/trunk/vector/v.build/description.html)
===================================================================
--- grass/trunk/vector/v.build/v.build.html (rev 0)
+++ grass/trunk/vector/v.build/v.build.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,43 @@
+<h2>DESCRIPTION</h2>
+
+<em>v.build</em> builds support files for (binary)
+GRASS vector data files. These support files supply
+topology and category information that are needed by other
+GRASS modules.
+<p>
+GRASS is generating these support files automatically,
+only in rare cases the user has to (re)build them.
+<p>
+Refer to
+<em><a href="vectorintro.html">Vector data processing in GRASS GIS</a></em>
+for more information on GRASS GIS vector data model.
+
+<h2>NOTES</h2>
+
+<em>v.build</em> creates support files only for binary
+vector maps located in the user's current mapset. If vector map
+is located in another mapset, you need to specify this:
+
+<p>
+<div class="code"><pre>
+v.build map=geology at PERMANENT
+</pre></div>
+
+<P>
+In case of errors, the user can optionally generate an <em>error</em>
+vector map containing the erroneous vectors for later inspection.
+
+<h2>SEE ALSO</h2>
+
+<em><a href="v.build.polylines.html">v.build.polylines</a></em>
+
+<h2>AUTHORS</h2>
+
+Dave Gerdes, U.S.Army Construction Engineering
+Research Laboratory,<br>
+Michael Higgins,
+U.S.Army Construction Engineering
+Research Laboratory,<br>
+Radim Blazek, ITC-irst, Trento, Italy
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/vector/v.build.polylines/description.html
===================================================================
--- grass/trunk/vector/v.build.polylines/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/vector/v.build.polylines/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,74 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>v.build.polylines</em> builds polylines from the lines or
-boundaries in a vector map. <!-- ???? and copies the attribute
-and category files from the original file. -->
-<P>
-A line is a single straight line segment defined by one start node, one end
-node and no other nodes. A polyline is also defined by one start node, one end
-node and no other nodes, but is made of two or more consecutive straight line
-segments. The connections between the constituent line segments of a polyline
-do not appear as nodes in the vector map.
-<P>
-Polylines provide the most appropriate representation of curved lines when it
-is important that nodes serve to define topology rather than geometry. Curved
-lines are usually digitized as polylines, but these are sometimes broken into
-their constituent straight line segments during conversion from one data
-format to another. <em>v.build.polylines</em> can be used to rebuild such broken
-polylines.
-
-<h2>NOTES</h2>
-<p>
-
-If the lines that make up a polyline are of different types, then
-<i>v.build.polylines</i> will set the type from the first constituent line.
-<!--
-<i>v.build.polylines </i> will issue a warning unless the flag <b>-q</b> has
-been set. It is possible to keep a list of all such warnings by redirecting
-standard output to a file.
--->
-<p>
-
-Category number(s) are assigned to a polyline based on <b>cats</b> parameter.
-
-<ul>
- <li>cats=no - No category number is assigned to a polyline. Also
- attributes tables linked to the input vector map are not copied to
- the output vector map.</li>
- <li>cats=first - Assign to a polyline category number of the first
-line. All linked attributes tables are copied to the output vector map.</li>
- <li>cats=multi - If the lines that make up a polyline have different category numbers
- then <em>v.build.polylines</em> will set the multiple catetory numbers to a polyline.
- Also all linked attributes tables are copied to the output vector map.</li>
-</ul>
-
-<p>
-<em>v.build.polylines</em> correctly handles <b>input</b> vector maps
-containing lines, boundaries, centroids and points. Lines and
-boundaries will be converted to polylines of the desired type. Areas
-are only guaranteed to be preserved if the constituent lines of the
-polylines that define them are all boundaries in the input vector map.
-
-<!-- Points will remain points provided that <b>type</b> has been set to `source'.
-It is possible to convert lines and area edges to points or vice versa, but this
-is rarely useful. [type no longer exists, other behaviour still true??] -->
-
-
-<h2>ACKNOWLEDGEMENTS</h2>
-This program was originally written during Mark Lake's tenure of a
-Leverhulme Special Research Fellowship at University College London.
-
-<h2>SEE ALSO</h2>
-<em>
-<a href=v.build.html>v.build</a>,
-<a href=v.in.ascii.html>v.in.ascii</a>,
-<a href="v.split.html">v.split</a>,
-<a href="v.edit.html">v.edit</a>
-</em>
-
-<h2>AUTHORS</h2>
-Mark Lake, Institute of Archaeology, University College London.<br>
-Major rewrite by Radim Blazek, October 2002<br>
-Category mode added by Martin Landa, FBK-irst, Trento, Italy, October 2007
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/vector/v.build.polylines/v.build.polylines.html (from rev 32770, grass/trunk/vector/v.build.polylines/description.html)
===================================================================
--- grass/trunk/vector/v.build.polylines/v.build.polylines.html (rev 0)
+++ grass/trunk/vector/v.build.polylines/v.build.polylines.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,74 @@
+<h2>DESCRIPTION</h2>
+
+<em>v.build.polylines</em> builds polylines from the lines or
+boundaries in a vector map. <!-- ???? and copies the attribute
+and category files from the original file. -->
+<P>
+A line is a single straight line segment defined by one start node, one end
+node and no other nodes. A polyline is also defined by one start node, one end
+node and no other nodes, but is made of two or more consecutive straight line
+segments. The connections between the constituent line segments of a polyline
+do not appear as nodes in the vector map.
+<P>
+Polylines provide the most appropriate representation of curved lines when it
+is important that nodes serve to define topology rather than geometry. Curved
+lines are usually digitized as polylines, but these are sometimes broken into
+their constituent straight line segments during conversion from one data
+format to another. <em>v.build.polylines</em> can be used to rebuild such broken
+polylines.
+
+<h2>NOTES</h2>
+<p>
+
+If the lines that make up a polyline are of different types, then
+<i>v.build.polylines</i> will set the type from the first constituent line.
+<!--
+<i>v.build.polylines </i> will issue a warning unless the flag <b>-q</b> has
+been set. It is possible to keep a list of all such warnings by redirecting
+standard output to a file.
+-->
+<p>
+
+Category number(s) are assigned to a polyline based on <b>cats</b> parameter.
+
+<ul>
+ <li>cats=no - No category number is assigned to a polyline. Also
+ attributes tables linked to the input vector map are not copied to
+ the output vector map.</li>
+ <li>cats=first - Assign to a polyline category number of the first
+line. All linked attributes tables are copied to the output vector map.</li>
+ <li>cats=multi - If the lines that make up a polyline have different category numbers
+ then <em>v.build.polylines</em> will set the multiple catetory numbers to a polyline.
+ Also all linked attributes tables are copied to the output vector map.</li>
+</ul>
+
+<p>
+<em>v.build.polylines</em> correctly handles <b>input</b> vector maps
+containing lines, boundaries, centroids and points. Lines and
+boundaries will be converted to polylines of the desired type. Areas
+are only guaranteed to be preserved if the constituent lines of the
+polylines that define them are all boundaries in the input vector map.
+
+<!-- Points will remain points provided that <b>type</b> has been set to `source'.
+It is possible to convert lines and area edges to points or vice versa, but this
+is rarely useful. [type no longer exists, other behaviour still true??] -->
+
+
+<h2>ACKNOWLEDGEMENTS</h2>
+This program was originally written during Mark Lake's tenure of a
+Leverhulme Special Research Fellowship at University College London.
+
+<h2>SEE ALSO</h2>
+<em>
+<a href=v.build.html>v.build</a>,
+<a href=v.in.ascii.html>v.in.ascii</a>,
+<a href="v.split.html">v.split</a>,
+<a href="v.edit.html">v.edit</a>
+</em>
+
+<h2>AUTHORS</h2>
+Mark Lake, Institute of Archaeology, University College London.<br>
+Major rewrite by Radim Blazek, October 2002<br>
+Category mode added by Martin Landa, FBK-irst, Trento, Italy, October 2007
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/vector/v.category/description.html
===================================================================
--- grass/trunk/vector/v.category/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/vector/v.category/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,103 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>v.category</em> attaches, deletes or reports vector categories to
-map geometry. These categories (IDs) are used to link geometry
-object(s) to attribute record (from attribute table linked to vector map).
-
-<h2>NOTES</h2>
-
-Use <em><a href="v.to.db.html">v.to.db</a></em> to upload related categories to
-a linked attribute table.
-
-<p>
-The <b>type</b> parameter specifies the type of geometry objects to which the category is added;
-it is similar to an input filter - only the geometry specified in 'type' is processed.
-
-<p>
-If the <b>type</b> parameter is set to <b>centroid</b> and
-the <b>option</b> parameter set to <b>add</b>, new categories will be
-added to existing centroids. Note however, that new centroids cannot
-be created this way. To do so, they must be added manually
-using <em><a href="v.digit.html">v.digit</a></em> or by
-running <em>v.category</em> with the type parameter set to area (see
-below also).
-
-<p>
-Areas are a special case because it is impossible to attach a cat to an area without a centroid;
-in this case, the module places new centroids in areas automatically.
-
-<p>
-The <b>id</b> parameter specifies the list of feature ids to which the
-operation is performed. By default all vector features are processed.
-
-<h2>EXAMPLES</h2>
-
-<h3>Report vector categories</h3>
-
-<div class="code"><pre>
-v.category input=testmap option=report
-
-LAYER/TABLE 1/testmap:
-type count min max
-point 0 0 0
-line 1379 1 1379
-boundary 0 0 0
-centroid 0 0 0
-area 0 0 0
-all 1379 1 1379
-</pre></div>
-
-<h3>Delete all vector categories in layer 1</h3>
-
-<div class="code"><pre>
-v.category input=testmap output=outmap option=del
-</pre></div>
-
-<h3>Add vector categories in layer 1 with step=2</h3>
-
-<div class="code"><pre>
-v.category input=outmap output=stepmap option=add step=2
-
-# report
-v.category input=stepmap option=report
-LAYER/TABLE 1/outmap:
-type count min max
-point 0 0 0
-line 1379 1 2757
-boundary 0 0 0
-centroid 0 0 0
-area 0 0 0
-all 1379 1 2757
-</pre></div>
-
-<h3>Add categories/centroids to a vector map without categories</h3>
-
-<div class="code"><pre>
-v.category input=wkt output=wktnew option=add
-</pre></div>
-
-Results can be tested
-using <em><a HREF="d.what.vect.html">d.what.vect</a></em>.
-
-<h3>Print vector categories of given layer</h3>
-
-Print vector categories from the first layer, only for feature ids 1-50.
-
-<div class="code"><pre>
-v.category input=roads option=print layer=1 id=1-50
-</pre></div>
-
-<h2>SEE ALSO</h2>
-
-<em>
-<a href="v.db.connect.html">v.db.connect</a>,
-<a href="v.to.db.html">v.to.db</a>
-</em>
-
-<h2>AUTHOR</h2>
-
-Radim Blazek, ITC-irst, Trento, Italy<br>
-Modified (the id parameter) by Martin Landa, FBK-irst (formerly ITC-irst), Trento, Italy, 2008/02
-
-<p>
-<i>Last changed: $Date$</i>
Copied: grass/trunk/vector/v.category/v.category.html (from rev 32770, grass/trunk/vector/v.category/description.html)
===================================================================
--- grass/trunk/vector/v.category/v.category.html (rev 0)
+++ grass/trunk/vector/v.category/v.category.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,103 @@
+<h2>DESCRIPTION</h2>
+
+<em>v.category</em> attaches, deletes or reports vector categories to
+map geometry. These categories (IDs) are used to link geometry
+object(s) to attribute record (from attribute table linked to vector map).
+
+<h2>NOTES</h2>
+
+Use <em><a href="v.to.db.html">v.to.db</a></em> to upload related categories to
+a linked attribute table.
+
+<p>
+The <b>type</b> parameter specifies the type of geometry objects to which the category is added;
+it is similar to an input filter - only the geometry specified in 'type' is processed.
+
+<p>
+If the <b>type</b> parameter is set to <b>centroid</b> and
+the <b>option</b> parameter set to <b>add</b>, new categories will be
+added to existing centroids. Note however, that new centroids cannot
+be created this way. To do so, they must be added manually
+using <em><a href="v.digit.html">v.digit</a></em> or by
+running <em>v.category</em> with the type parameter set to area (see
+below also).
+
+<p>
+Areas are a special case because it is impossible to attach a cat to an area without a centroid;
+in this case, the module places new centroids in areas automatically.
+
+<p>
+The <b>id</b> parameter specifies the list of feature ids to which the
+operation is performed. By default all vector features are processed.
+
+<h2>EXAMPLES</h2>
+
+<h3>Report vector categories</h3>
+
+<div class="code"><pre>
+v.category input=testmap option=report
+
+LAYER/TABLE 1/testmap:
+type count min max
+point 0 0 0
+line 1379 1 1379
+boundary 0 0 0
+centroid 0 0 0
+area 0 0 0
+all 1379 1 1379
+</pre></div>
+
+<h3>Delete all vector categories in layer 1</h3>
+
+<div class="code"><pre>
+v.category input=testmap output=outmap option=del
+</pre></div>
+
+<h3>Add vector categories in layer 1 with step=2</h3>
+
+<div class="code"><pre>
+v.category input=outmap output=stepmap option=add step=2
+
+# report
+v.category input=stepmap option=report
+LAYER/TABLE 1/outmap:
+type count min max
+point 0 0 0
+line 1379 1 2757
+boundary 0 0 0
+centroid 0 0 0
+area 0 0 0
+all 1379 1 2757
+</pre></div>
+
+<h3>Add categories/centroids to a vector map without categories</h3>
+
+<div class="code"><pre>
+v.category input=wkt output=wktnew option=add
+</pre></div>
+
+Results can be tested
+using <em><a HREF="d.what.vect.html">d.what.vect</a></em>.
+
+<h3>Print vector categories of given layer</h3>
+
+Print vector categories from the first layer, only for feature ids 1-50.
+
+<div class="code"><pre>
+v.category input=roads option=print layer=1 id=1-50
+</pre></div>
+
+<h2>SEE ALSO</h2>
+
+<em>
+<a href="v.db.connect.html">v.db.connect</a>,
+<a href="v.to.db.html">v.to.db</a>
+</em>
+
+<h2>AUTHOR</h2>
+
+Radim Blazek, ITC-irst, Trento, Italy<br>
+Modified (the id parameter) by Martin Landa, FBK-irst (formerly ITC-irst), Trento, Italy, 2008/02
+
+<p>
+<i>Last changed: $Date$</i>
Deleted: grass/trunk/vector/v.class/description.html
===================================================================
--- grass/trunk/vector/v.class/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/vector/v.class/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,50 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-<em>v.class</em> classifies vector attribute data into classes, for example for thematic mapping. Classification can be on a column or on an expression including several columns, all in the table linked to the vector map. The user indicates the number of classes desired and the algorithm to use for classification.
-
-Several algorithms are implemented for classification: equal interval, standard deviation, quantiles, equal probabilities, and a discontinuities algorithm developed by Jean-Pierre Grimmeau at the Free University of Brussels (ULB).
-
-It can be used to pipe class breaks into thematic mapping modules such as d.thematic.area (see example below);
-
-<H2>NOTES</H2>
-
-<P>The <em>equal interval</em> algorithm simply divides the range max-min by the number of breaks to determine the interval between class breaks.</P>
-
-<P>The <em>quantiles</em> algorithm creates classes which all contain approximately the same number of observations.</P>
-
-<P>The <em>standard deviations</em> algorithm creates class breaks which are a combination of the mean +/- the standard deviation. It calculates a scale factor (<1) by which to multiply the standard deviation in order for all of the class breaks to fall into the range min-max of the data values.</P>
-
-<P>The <em>equiprobabilites</em> algorithm creates classes that would be equiprobable if the distribution was normal. If some of the class breaks fall outside the range min-max of the data values, the algorithm prints a warning and reduces the number of breaks, but the probabilities used are those of the number of breaks asked for.</P>
-
-<P>The <em>discont</em> algorithm systematically searches discontinuities in the slope of the cumulated frequencies curve, by approximating this curve through straight line segments whose vertices define the class breaks. The first approximation is a straight line which links the two end nodes of the curve. This line is then replaced by a two-segmented polyline whose central node is the point on the curve which is farthest from the preceding straight line. The point on the curve furthest from this new polyline is then chosen as a new node to create break up one of the two preceding segments, and so forth. The problem of the difference in terms of units between the two axes is solved by rescaling both amplitudes to an interval between 0 and 1. In the original algorithm, the process is stopped when the difference between the slopes of the two new segments is no longer significant (alpha = 0.05). As the slope is the ratio between the frequency and the amplitude of the corresponding interval, i.e. its density, this effectively tests whether the frequencies of the two newly proposed classes are different from those obtained by simply distributing the sum of their frequencies amongst them in proportion to the class amplitudes. In the GRASS implementation, the algorithm continues, but a warning is printed.</P>
-
-<H2>EXAMPLE</H2>
-
-Classify column pop of map communes into 5 classes using quantiles:
-
-<div class="code"><pre>
-v.class map=communes column=pop algo=qua nbclasses=5
-</pre></div>
-
-This example uses population and area to calculate a population density and to determine the density classes:
-
-<div class="code"><pre>
-v.class map=communes column=pop/area algo=std nbclasses=5
-</pre></div>
-
-
-The following example uses the output of d.class and feeds it directly into d.area.thematic:
-<div class="code"><pre>
-d.thematic.area -l map=communes2 data=pop/area breaks=`v.class -g map=communes2 column=pop/area algo=std nbcla=5` colors=0:0:255,50:100:255,255:100:50,255:0:0,156:0:0
-</pre></div>
-
-<H2>SEE ALSO</H2>
-
-<EM><A HREF="v.univar.html">v.univar</A></EM>
-<EM><A HREF="d.thematic.area.html">d.area.thematic</A></EM>
-
-
-<H2>AUTHOR</H2>
-
-Moritz Lennert
-
Copied: grass/trunk/vector/v.class/v.class.html (from rev 32770, grass/trunk/vector/v.class/description.html)
===================================================================
--- grass/trunk/vector/v.class/v.class.html (rev 0)
+++ grass/trunk/vector/v.class/v.class.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,50 @@
+<H2>DESCRIPTION</H2>
+
+<em>v.class</em> classifies vector attribute data into classes, for example for thematic mapping. Classification can be on a column or on an expression including several columns, all in the table linked to the vector map. The user indicates the number of classes desired and the algorithm to use for classification.
+
+Several algorithms are implemented for classification: equal interval, standard deviation, quantiles, equal probabilities, and a discontinuities algorithm developed by Jean-Pierre Grimmeau at the Free University of Brussels (ULB).
+
+It can be used to pipe class breaks into thematic mapping modules such as d.thematic.area (see example below);
+
+<H2>NOTES</H2>
+
+<P>The <em>equal interval</em> algorithm simply divides the range max-min by the number of breaks to determine the interval between class breaks.</P>
+
+<P>The <em>quantiles</em> algorithm creates classes which all contain approximately the same number of observations.</P>
+
+<P>The <em>standard deviations</em> algorithm creates class breaks which are a combination of the mean +/- the standard deviation. It calculates a scale factor (<1) by which to multiply the standard deviation in order for all of the class breaks to fall into the range min-max of the data values.</P>
+
+<P>The <em>equiprobabilites</em> algorithm creates classes that would be equiprobable if the distribution was normal. If some of the class breaks fall outside the range min-max of the data values, the algorithm prints a warning and reduces the number of breaks, but the probabilities used are those of the number of breaks asked for.</P>
+
+<P>The <em>discont</em> algorithm systematically searches discontinuities in the slope of the cumulated frequencies curve, by approximating this curve through straight line segments whose vertices define the class breaks. The first approximation is a straight line which links the two end nodes of the curve. This line is then replaced by a two-segmented polyline whose central node is the point on the curve which is farthest from the preceding straight line. The point on the curve furthest from this new polyline is then chosen as a new node to create break up one of the two preceding segments, and so forth. The problem of the difference in terms of units between the two axes is solved by rescaling both amplitudes to an interval between 0 and 1. In the original algorithm, the process is stopped when the difference between the slopes of the two new segments is no longer significant (alpha = 0.05). As the slope is the ratio between the frequency and the amplitude of the corresponding interval, i.e. its density, this effectively tests whether the frequencies of the two newly proposed classes are different from those obtained by simply distributing the sum of their frequencies amongst them in proportion to the class amplitudes. In the GRASS implementation, the algorithm continues, but a warning is printed.</P>
+
+<H2>EXAMPLE</H2>
+
+Classify column pop of map communes into 5 classes using quantiles:
+
+<div class="code"><pre>
+v.class map=communes column=pop algo=qua nbclasses=5
+</pre></div>
+
+This example uses population and area to calculate a population density and to determine the density classes:
+
+<div class="code"><pre>
+v.class map=communes column=pop/area algo=std nbclasses=5
+</pre></div>
+
+
+The following example uses the output of d.class and feeds it directly into d.area.thematic:
+<div class="code"><pre>
+d.thematic.area -l map=communes2 data=pop/area breaks=`v.class -g map=communes2 column=pop/area algo=std nbcla=5` colors=0:0:255,50:100:255,255:100:50,255:0:0,156:0:0
+</pre></div>
+
+<H2>SEE ALSO</H2>
+
+<EM><A HREF="v.univar.html">v.univar</A></EM>
+<EM><A HREF="d.thematic.area.html">d.area.thematic</A></EM>
+
+
+<H2>AUTHOR</H2>
+
+Moritz Lennert
+
Deleted: grass/trunk/vector/v.clean/description.html
===================================================================
--- grass/trunk/vector/v.clean/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/vector/v.clean/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,121 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>v.clean</em> allows the user to automatically fix topology of vector maps.
-
-<h2>NOTES</h2>
-
-The user does <b>not</b> have to run <em><a HREF="v.build.html">v.build</a></em>
-on the <em>output</em> vector, unless the <em>-b</em> flag was used. The
-<em>-b</em> flag affects <b>only</b> the <em>output</em> vector - topology is
-always built for <em>error</em> vector.
-
-<h3>Removing small angles between lines at nodes</h3>
-
-The <em>rmsa</em> tool only concerns angles which are so small that the calculated angle
-is 0. The user cannot change this threshold. The following figure should help
-demonstrate what the tool does.
-<P>
-<ul>
-<table><tr><td>
-<img src="v_clean_rmsa.png" border=1>
-</td></tr>
-<tr><td align=center>
-<font size=-1><em>tool=rmsa</em></font>
-</td></tr>
-</table>
-</ul>
-
-<h3>What is a bridge?</h3>
-A bridge is an area type connection of an island (polygon in a polygon) to the outer
-polygon. This is topologically incorrect (but OGC Simple Features allow it). <em>v.clean</em>
-can be used to optionally change the line type to fulfill the topology rules or to
-remove the bridge from the map:
-
-<div class="code"><pre>
- +-------------+ +-------------+ +-------------+
- | P| P: polygon | P| | P|
- | +---+ | I: island | +---+ | | +---+ |
- | | I | | B: bridge | | I | | | | I | |
- | | | | L: line | | | | | | | |
- | +-+-+ | | +---+ | | +-.-+ |
- | | | | | | . |
- | | B | | | | . L |
- | | | | | | . |
- +------+------+ +-------------+ +-------------+
-</pre></div>
-
-<h2>EXAMPLES</h2>
-
-<h3>Snap lines to vertex in threshold</h3>
-<div class="code"><pre>
-v.clean input=testmap output=cleanmap tool=snap thresh=1
-</pre></div>
-
-
-<h3>Cleaning OGR imported data (Simple Feature data)</h3>
-
-The import of areas with <em><a HREF="v.in.ogr.html">v.in.ogr</a></em>
-requires a subsequent run of <em>v.clean</em> to update the map to a
-topologically valid structure (removal of duplicate collinear lines etc). The
-tools used for that are 'rmdupl' and 'bpol':
-<div class="code"><pre>
-v.clean input=areamap output=areamap_clean tool=rmdupl,bpol
-</pre></div>
-
-
-<h3>Extracting intersection points of vector lines</h3>
-<div class="code"><pre>
-v.clean input=lines1 output=lines2 err=points tool=break
-</pre></div>
-
-Intersection points are written to 'points' map.
-
-<h3>Break lines</h3>
-
-<em>v.clean</em> will break the lines where they cross,
-creating new node if needed. Example:
-
-<div class="code"><pre>
-v.in.ascii -n out=crossed_lines format=standard << EOF
-L 2
- 0 5
- 10 5
-L 2
- 5 0
- 5 10
-EOF
-
-v.clean in=crossed_lines out=crossed_lines_brk \
- error=intersection tool=break
-</pre></div>
-
-<h3>Remove all lines of zero length</h3>
-
-<div class="code"><pre>
-v.out.ascii zero format=standard
-L 2 1
- -819832.09065589 -987825.2187231
- -806227.28362601 -971104.80702988
- 1 1
-L 2 1
- -799165.24638913 -972974.16982788
- -799165.24638913 -972974.16982788
- 1 2
-
-v.clean input=zero output=zero_clean tool=rmline type=line
-
-v.out.ascii zero_clean format=standard
-L 2 1
- -819832.09065589 -987825.2187231
- -806227.28362601 -971104.80702988
- 1 1
-</pre></div>
-
-
-<h2>AUTHORS</h2>
-
-David Gerdes, U.S. Army Construction Engineering Research Laboratory<br>
-Radim Blazek, ITC-irst, Trento, Italy<br>
-Martin Landa, FBK-irst (formerly ITC-irst), Trento, Italy<br>
-
-<p><i>Last changed: $Date$</i></p>
Copied: grass/trunk/vector/v.clean/v.clean.html (from rev 32770, grass/trunk/vector/v.clean/description.html)
===================================================================
--- grass/trunk/vector/v.clean/v.clean.html (rev 0)
+++ grass/trunk/vector/v.clean/v.clean.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,121 @@
+<h2>DESCRIPTION</h2>
+
+<em>v.clean</em> allows the user to automatically fix topology of vector maps.
+
+<h2>NOTES</h2>
+
+The user does <b>not</b> have to run <em><a HREF="v.build.html">v.build</a></em>
+on the <em>output</em> vector, unless the <em>-b</em> flag was used. The
+<em>-b</em> flag affects <b>only</b> the <em>output</em> vector - topology is
+always built for <em>error</em> vector.
+
+<h3>Removing small angles between lines at nodes</h3>
+
+The <em>rmsa</em> tool only concerns angles which are so small that the calculated angle
+is 0. The user cannot change this threshold. The following figure should help
+demonstrate what the tool does.
+<P>
+<ul>
+<table><tr><td>
+<img src="v_clean_rmsa.png" border=1>
+</td></tr>
+<tr><td align=center>
+<font size=-1><em>tool=rmsa</em></font>
+</td></tr>
+</table>
+</ul>
+
+<h3>What is a bridge?</h3>
+A bridge is an area type connection of an island (polygon in a polygon) to the outer
+polygon. This is topologically incorrect (but OGC Simple Features allow it). <em>v.clean</em>
+can be used to optionally change the line type to fulfill the topology rules or to
+remove the bridge from the map:
+
+<div class="code"><pre>
+ +-------------+ +-------------+ +-------------+
+ | P| P: polygon | P| | P|
+ | +---+ | I: island | +---+ | | +---+ |
+ | | I | | B: bridge | | I | | | | I | |
+ | | | | L: line | | | | | | | |
+ | +-+-+ | | +---+ | | +-.-+ |
+ | | | | | | . |
+ | | B | | | | . L |
+ | | | | | | . |
+ +------+------+ +-------------+ +-------------+
+</pre></div>
+
+<h2>EXAMPLES</h2>
+
+<h3>Snap lines to vertex in threshold</h3>
+<div class="code"><pre>
+v.clean input=testmap output=cleanmap tool=snap thresh=1
+</pre></div>
+
+
+<h3>Cleaning OGR imported data (Simple Feature data)</h3>
+
+The import of areas with <em><a HREF="v.in.ogr.html">v.in.ogr</a></em>
+requires a subsequent run of <em>v.clean</em> to update the map to a
+topologically valid structure (removal of duplicate collinear lines etc). The
+tools used for that are 'rmdupl' and 'bpol':
+<div class="code"><pre>
+v.clean input=areamap output=areamap_clean tool=rmdupl,bpol
+</pre></div>
+
+
+<h3>Extracting intersection points of vector lines</h3>
+<div class="code"><pre>
+v.clean input=lines1 output=lines2 err=points tool=break
+</pre></div>
+
+Intersection points are written to 'points' map.
+
+<h3>Break lines</h3>
+
+<em>v.clean</em> will break the lines where they cross,
+creating new node if needed. Example:
+
+<div class="code"><pre>
+v.in.ascii -n out=crossed_lines format=standard << EOF
+L 2
+ 0 5
+ 10 5
+L 2
+ 5 0
+ 5 10
+EOF
+
+v.clean in=crossed_lines out=crossed_lines_brk \
+ error=intersection tool=break
+</pre></div>
+
+<h3>Remove all lines of zero length</h3>
+
+<div class="code"><pre>
+v.out.ascii zero format=standard
+L 2 1
+ -819832.09065589 -987825.2187231
+ -806227.28362601 -971104.80702988
+ 1 1
+L 2 1
+ -799165.24638913 -972974.16982788
+ -799165.24638913 -972974.16982788
+ 1 2
+
+v.clean input=zero output=zero_clean tool=rmline type=line
+
+v.out.ascii zero_clean format=standard
+L 2 1
+ -819832.09065589 -987825.2187231
+ -806227.28362601 -971104.80702988
+ 1 1
+</pre></div>
+
+
+<h2>AUTHORS</h2>
+
+David Gerdes, U.S. Army Construction Engineering Research Laboratory<br>
+Radim Blazek, ITC-irst, Trento, Italy<br>
+Martin Landa, FBK-irst (formerly ITC-irst), Trento, Italy<br>
+
+<p><i>Last changed: $Date$</i></p>
Deleted: grass/trunk/vector/v.convert/description.html
===================================================================
--- grass/trunk/vector/v.convert/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/vector/v.convert/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,40 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>v.convert</em> converts GRASS 5.0/5.3/5.4 vectors into 5.7/6.x vectors.
-
-<h2>NOTES</h2>
-
-Vector maps from 5.0/5.3/5.4 and 5.7/6.x do not interfere. They are stored in different
-directories, so you can use the same names. Old vector maps can be listed with
-<em>g.list oldvect</em>.
-<P>
-If you need to convert back from 5.7/6.x into the 5.0/5.3/5.4 vector format,
-use <em>v.out.ogr</em> (to SHAPE format) and then <em>v.in.shape</em>
-in the old GRASS program.
-Alternatively use "<em>v.out.ascii -o</em>" and <em>v.in.ascii</em>.
-<P>
-As this GRASS version uses SQL for attribute management, there are
-some <a href=sql.html>SQL restrictings concerning the file names</a>.
-<P>
-Missing centroids can be added with <em>v.category</em>.
-
-<h2>EXAMPLE</h2>
-<div class="code"><pre>
-v.convert in=vectormap_from_50 out=vectormap_60
-</pre></div>
-
-<h2>SEE ALSO</h2>
-
-<A HREF="g.list.html">g.list</A>,
-<A HREF="v.category.html">v.category</A>,
-<A HREF="v.convert.all.html">v.convert.all</A>,
-<A HREF="v.out.ascii.html">v.out.ascii</A>,
-<A HREF="v.in.ascii.html">v.in.ascii</A>,
-<A HREF="v.out.ogr.html">v.out.ogr</A>
-
-
-<h2>AUTHOR</h2>
-
-Radim Blazek, ITC-Irst, Trento, Italy
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/vector/v.convert/v.convert.html (from rev 32770, grass/trunk/vector/v.convert/description.html)
===================================================================
--- grass/trunk/vector/v.convert/v.convert.html (rev 0)
+++ grass/trunk/vector/v.convert/v.convert.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,40 @@
+<h2>DESCRIPTION</h2>
+
+<em>v.convert</em> converts GRASS 5.0/5.3/5.4 vectors into 5.7/6.x vectors.
+
+<h2>NOTES</h2>
+
+Vector maps from 5.0/5.3/5.4 and 5.7/6.x do not interfere. They are stored in different
+directories, so you can use the same names. Old vector maps can be listed with
+<em>g.list oldvect</em>.
+<P>
+If you need to convert back from 5.7/6.x into the 5.0/5.3/5.4 vector format,
+use <em>v.out.ogr</em> (to SHAPE format) and then <em>v.in.shape</em>
+in the old GRASS program.
+Alternatively use "<em>v.out.ascii -o</em>" and <em>v.in.ascii</em>.
+<P>
+As this GRASS version uses SQL for attribute management, there are
+some <a href=sql.html>SQL restrictings concerning the file names</a>.
+<P>
+Missing centroids can be added with <em>v.category</em>.
+
+<h2>EXAMPLE</h2>
+<div class="code"><pre>
+v.convert in=vectormap_from_50 out=vectormap_60
+</pre></div>
+
+<h2>SEE ALSO</h2>
+
+<A HREF="g.list.html">g.list</A>,
+<A HREF="v.category.html">v.category</A>,
+<A HREF="v.convert.all.html">v.convert.all</A>,
+<A HREF="v.out.ascii.html">v.out.ascii</A>,
+<A HREF="v.in.ascii.html">v.in.ascii</A>,
+<A HREF="v.out.ogr.html">v.out.ogr</A>
+
+
+<h2>AUTHOR</h2>
+
+Radim Blazek, ITC-Irst, Trento, Italy
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/vector/v.db.connect/description.html
===================================================================
--- grass/trunk/vector/v.db.connect/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/vector/v.db.connect/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,187 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>v.db.connect</em> prints or sets database connection for a vector
-map. The user can add or remove link to attribute table on the certain
-layer.
-
-<h2>NOTE</h2>
-
-If parameters for database connection are already set with
-<a HREF="db.connect.html">db.connect</a>, they are taken as default values and
-do not need to be spcified each time.
-
-<p>
-When printing database connection (<em>p</em> or <em>g</em> flag) the parameter
-<em>layer</em> is ignored, i.e. <b>all</b> connections are printed to the
-output.
-
-<p>
-<b>Attention:</b> Removing a vector map will also delete all tables
-linked to it! If you use <a HREF="db.connect.html">v.db.connect </a>to
-link further tables to your map, it is advisable to make a copy from
-those tables first and connect the copied tables to the vector map
-(see also <a HREF="v.overlay.html">v.overlay</a>).
-
-<h2>EXAMPLE</h2>
-
-<h3>Print database connection</h3>
-
-Print all database connection parameters for vector map.
-
-<div class="code"><pre>
-v.db.connect -p map=roads
-</pre></div>
-
-<p>
-Print column types and names of table linked to vector map.
-
-<div class="code"><pre>
-v.db.connect -c map=roads
-</pre></div>
-
-<h3>Connect vector map to database (DBF driver)</h3>
-
-Connect vector map to DBF table without or with variables.<br>
-
-<p>
-Using default DB connection:
-<div class="code"><pre>
-v.db.connect map=vectormap table=table
-</pre></div>
-
-<p>
-Using hardcoded path to DBF directory (not recommended):<br>
-<div class="code"><pre>
-v.db.connect map=vectormap table=table database=/home/user/grassdata/spearfish60/PERMANENT/dbf
-</pre></div>
-
-<p>
-Using variable as DBF directory definition, single quotes must be used:<br>
-<div class="code"><pre>
-v.db.connect map=vectormap table=table database='$GISDBASE/$LOCATION_NAME/$MAPSET/dbf/'
-</pre></div>
-
-<p>
-Connect vector map layer 2 and key ID to database with variables (note: if needed, single quotes must be used for the <em>database</em> parameter):
-<div class="code"><pre>
-v.db.connect map=vectormap table=table layer=2 key=ID
-</pre></div>
-
-<h3>Connect vector map to database (MySQL driver)</h3>
-
-<div class="code"><pre>
-# note: connection which requires password
-db.connect driver=mysql database="host=dbserver.foo.org,dbname=my_database"
-db.login user=joshua [password=xxx]
-# ... or enter password interactively.
-
-db.tables -p
-
-# connect external table to layer 2:
-v.db.connect map=my_map table=my_mysql_table key=baz layer=2
-v.db.connect -p my_map
-</pre></div>
-
-
-<h3>Connect vector map to database (PostgreSQL driver)</h3>
-
-<div class="code"><pre>
-# note: connection without password being asked
-v.db.connect map=vectormap table=table layer=1 key=oid driver=pg \
- database="host=myserver.itc.it,dbname=mydb,user=name" \
- table=mytable key=id
-</pre></div>
-
-<H3>Store geometry in GRASS but attributes in PostgreSQL</H3>
-
-This example illustrated a mixed data storage with possibility
-top update attributes in external PostgreSQL database:
-
-<div class="code"><pre>
-# Check current settings for attribute storage:
-db.connect -p
-
-# Import table from PostgreSQL to new map
-# (NOTE: output map name needs to be different from table name in
-# case that GRASS is connected to PostgreSQL):
-v.in.db driver=pg database="host=localhost,dbname=meteo" \
- table=mytable x=lon y=lat key=cat out=mytable
-
-v.db.connect map=mytable -p
-
-# Cancel table connection between map and attribute table:
-v.db.connect map=mytable -d
-v.db.connect map=mytable -p
-
-# Drop table which was replicated due to import:
-db.tables -p
-echo "DROP TABLE mytable" | db.execute
-db.tables -p
-
-# reconnect map to table in PostgreSQL:
-v.db.connect map=mytable driver=pg database="host=localhost,dbname=meteo" \
- table=mytable key=cat
-
-# Now the geometry is stored in GRASS while the attributes are stored
-# in PostgreSQL.
-</pre></div>
-
-An alternative is to create a "view" of only ID, x, y [,z] columns and
-to use <a HREF="v.in.db.html">v.in.db</a> on this view, then connect the original
-table to the geometry. This will be faster if the original table
-is very large.
-
-
-<H3>Store geometry in GRASS but attributes in PostGIS</H3>
-
-This example illustrated a mixed data storage with possibility
-top update attributes in external PostGIS database:
-
-<div class="code"><pre>
-# Check current settings for attribute storage:
-db.connect -p
-
-# Import table from PostGIS to new map
-# (NOTE: output map name needs to be different from table name in
-# case that GRASS is connected to PostGIS):
-v.in.db driver=pg database="host=localhost,dbname=meteo" \
- table=mytable x="x(geom)" y="y(geom)" key=cat out=mytable
-
-v.db.connect map=mytable -p
-
-# Cancel table connection between map and attribute table:
-v.db.connect map=mytable -d
-v.db.connect map=mytable -p
-
-# Drop table which was replicated due to import:
-db.tables -p
-echo "DROP TABLE mytable" | db.execute
-db.tables -p
-
-# reconnect map to table in PostGIS:
-v.db.connect map=mytable driver=pg database="host=localhost,dbname=meteo" \
- table=mytable key=cat
-
-# Now the geometry is stored in GRASS while the attributes are stored
-# in PostGIS.
-</pre></div>
-
-
-<h2>SEE ALSO</h2>
-
-<a HREF="db.connect.html">db.connect</a>,
-<a HREF="db.copy.html">db.copy</a>,
-<a HREF="db.tables.html">db.tables</a>,
-<a HREF="v.db.addtable.html">v.db.addtable</a>,
-<a HREF="v.db.droptable.html">v.db.droptable</a>,
-<a HREF="v.db.addcol.html">v.db.addcol</a>,
-<a HREF="v.db.dropcol.html">v.db.dropcol</a>,
-<a HREF="v.external.html">v.external</a>,
-<a HREF="v.in.db.html">v.in.db</a>,
-<a HREF="v.overlay.html">v.overlay</a>
-
-<h2>AUTHOR</h2>
-
-Radim Blazek, ITC-Irst, Trento, Italy
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/vector/v.db.connect/v.db.connect.html (from rev 32770, grass/trunk/vector/v.db.connect/description.html)
===================================================================
--- grass/trunk/vector/v.db.connect/v.db.connect.html (rev 0)
+++ grass/trunk/vector/v.db.connect/v.db.connect.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,187 @@
+<h2>DESCRIPTION</h2>
+
+<em>v.db.connect</em> prints or sets database connection for a vector
+map. The user can add or remove link to attribute table on the certain
+layer.
+
+<h2>NOTE</h2>
+
+If parameters for database connection are already set with
+<a HREF="db.connect.html">db.connect</a>, they are taken as default values and
+do not need to be spcified each time.
+
+<p>
+When printing database connection (<em>p</em> or <em>g</em> flag) the parameter
+<em>layer</em> is ignored, i.e. <b>all</b> connections are printed to the
+output.
+
+<p>
+<b>Attention:</b> Removing a vector map will also delete all tables
+linked to it! If you use <a HREF="db.connect.html">v.db.connect </a>to
+link further tables to your map, it is advisable to make a copy from
+those tables first and connect the copied tables to the vector map
+(see also <a HREF="v.overlay.html">v.overlay</a>).
+
+<h2>EXAMPLE</h2>
+
+<h3>Print database connection</h3>
+
+Print all database connection parameters for vector map.
+
+<div class="code"><pre>
+v.db.connect -p map=roads
+</pre></div>
+
+<p>
+Print column types and names of table linked to vector map.
+
+<div class="code"><pre>
+v.db.connect -c map=roads
+</pre></div>
+
+<h3>Connect vector map to database (DBF driver)</h3>
+
+Connect vector map to DBF table without or with variables.<br>
+
+<p>
+Using default DB connection:
+<div class="code"><pre>
+v.db.connect map=vectormap table=table
+</pre></div>
+
+<p>
+Using hardcoded path to DBF directory (not recommended):<br>
+<div class="code"><pre>
+v.db.connect map=vectormap table=table database=/home/user/grassdata/spearfish60/PERMANENT/dbf
+</pre></div>
+
+<p>
+Using variable as DBF directory definition, single quotes must be used:<br>
+<div class="code"><pre>
+v.db.connect map=vectormap table=table database='$GISDBASE/$LOCATION_NAME/$MAPSET/dbf/'
+</pre></div>
+
+<p>
+Connect vector map layer 2 and key ID to database with variables (note: if needed, single quotes must be used for the <em>database</em> parameter):
+<div class="code"><pre>
+v.db.connect map=vectormap table=table layer=2 key=ID
+</pre></div>
+
+<h3>Connect vector map to database (MySQL driver)</h3>
+
+<div class="code"><pre>
+# note: connection which requires password
+db.connect driver=mysql database="host=dbserver.foo.org,dbname=my_database"
+db.login user=joshua [password=xxx]
+# ... or enter password interactively.
+
+db.tables -p
+
+# connect external table to layer 2:
+v.db.connect map=my_map table=my_mysql_table key=baz layer=2
+v.db.connect -p my_map
+</pre></div>
+
+
+<h3>Connect vector map to database (PostgreSQL driver)</h3>
+
+<div class="code"><pre>
+# note: connection without password being asked
+v.db.connect map=vectormap table=table layer=1 key=oid driver=pg \
+ database="host=myserver.itc.it,dbname=mydb,user=name" \
+ table=mytable key=id
+</pre></div>
+
+<H3>Store geometry in GRASS but attributes in PostgreSQL</H3>
+
+This example illustrated a mixed data storage with possibility
+top update attributes in external PostgreSQL database:
+
+<div class="code"><pre>
+# Check current settings for attribute storage:
+db.connect -p
+
+# Import table from PostgreSQL to new map
+# (NOTE: output map name needs to be different from table name in
+# case that GRASS is connected to PostgreSQL):
+v.in.db driver=pg database="host=localhost,dbname=meteo" \
+ table=mytable x=lon y=lat key=cat out=mytable
+
+v.db.connect map=mytable -p
+
+# Cancel table connection between map and attribute table:
+v.db.connect map=mytable -d
+v.db.connect map=mytable -p
+
+# Drop table which was replicated due to import:
+db.tables -p
+echo "DROP TABLE mytable" | db.execute
+db.tables -p
+
+# reconnect map to table in PostgreSQL:
+v.db.connect map=mytable driver=pg database="host=localhost,dbname=meteo" \
+ table=mytable key=cat
+
+# Now the geometry is stored in GRASS while the attributes are stored
+# in PostgreSQL.
+</pre></div>
+
+An alternative is to create a "view" of only ID, x, y [,z] columns and
+to use <a HREF="v.in.db.html">v.in.db</a> on this view, then connect the original
+table to the geometry. This will be faster if the original table
+is very large.
+
+
+<H3>Store geometry in GRASS but attributes in PostGIS</H3>
+
+This example illustrated a mixed data storage with possibility
+top update attributes in external PostGIS database:
+
+<div class="code"><pre>
+# Check current settings for attribute storage:
+db.connect -p
+
+# Import table from PostGIS to new map
+# (NOTE: output map name needs to be different from table name in
+# case that GRASS is connected to PostGIS):
+v.in.db driver=pg database="host=localhost,dbname=meteo" \
+ table=mytable x="x(geom)" y="y(geom)" key=cat out=mytable
+
+v.db.connect map=mytable -p
+
+# Cancel table connection between map and attribute table:
+v.db.connect map=mytable -d
+v.db.connect map=mytable -p
+
+# Drop table which was replicated due to import:
+db.tables -p
+echo "DROP TABLE mytable" | db.execute
+db.tables -p
+
+# reconnect map to table in PostGIS:
+v.db.connect map=mytable driver=pg database="host=localhost,dbname=meteo" \
+ table=mytable key=cat
+
+# Now the geometry is stored in GRASS while the attributes are stored
+# in PostGIS.
+</pre></div>
+
+
+<h2>SEE ALSO</h2>
+
+<a HREF="db.connect.html">db.connect</a>,
+<a HREF="db.copy.html">db.copy</a>,
+<a HREF="db.tables.html">db.tables</a>,
+<a HREF="v.db.addtable.html">v.db.addtable</a>,
+<a HREF="v.db.droptable.html">v.db.droptable</a>,
+<a HREF="v.db.addcol.html">v.db.addcol</a>,
+<a HREF="v.db.dropcol.html">v.db.dropcol</a>,
+<a HREF="v.external.html">v.external</a>,
+<a HREF="v.in.db.html">v.in.db</a>,
+<a HREF="v.overlay.html">v.overlay</a>
+
+<h2>AUTHOR</h2>
+
+Radim Blazek, ITC-Irst, Trento, Italy
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/vector/v.db.select/description.html
===================================================================
--- grass/trunk/vector/v.db.select/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/vector/v.db.select/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,42 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>v.db.select</em> prints attributes of a vector map from one or several
-user selected attribute table columns.
-
-<h2>EXAMPLE</h2>
-
-Select and show entire table:
-<div class="code"><pre>
-v.db.select roads
-cat|label
-0|no data
-1|interstate
-2|primary highway, hard surface
-3|secondary highway, hard surface
-4|light-duty road, improved surface
-5|unimproved road
-</pre></div>
-
-<p>
-Select and show single column from table (multiple columns can be specified as comma separated list):
-<div class="code"><pre>
-v.db.select roads col=label
-label
-no data
-interstate
-primary highway, hard surface
-secondary highway, hard surface
-light-duty road, improved surface
-unimproved road
-</pre></div>
-
-
-<h2>SEE ALSO</h2>
-
-<em><a HREF="db.select.html">db.select</a></em>
-
-<h2>AUTHOR</h2>
-
-Radim Blazek, ITC-Irst, Trento, Italy
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/vector/v.db.select/v.db.select.html (from rev 32770, grass/trunk/vector/v.db.select/description.html)
===================================================================
--- grass/trunk/vector/v.db.select/v.db.select.html (rev 0)
+++ grass/trunk/vector/v.db.select/v.db.select.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,42 @@
+<h2>DESCRIPTION</h2>
+
+<em>v.db.select</em> prints attributes of a vector map from one or several
+user selected attribute table columns.
+
+<h2>EXAMPLE</h2>
+
+Select and show entire table:
+<div class="code"><pre>
+v.db.select roads
+cat|label
+0|no data
+1|interstate
+2|primary highway, hard surface
+3|secondary highway, hard surface
+4|light-duty road, improved surface
+5|unimproved road
+</pre></div>
+
+<p>
+Select and show single column from table (multiple columns can be specified as comma separated list):
+<div class="code"><pre>
+v.db.select roads col=label
+label
+no data
+interstate
+primary highway, hard surface
+secondary highway, hard surface
+light-duty road, improved surface
+unimproved road
+</pre></div>
+
+
+<h2>SEE ALSO</h2>
+
+<em><a HREF="db.select.html">db.select</a></em>
+
+<h2>AUTHOR</h2>
+
+Radim Blazek, ITC-Irst, Trento, Italy
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/vector/v.digit/description.html
===================================================================
--- grass/trunk/vector/v.digit/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/vector/v.digit/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,98 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>v.digit</em> is a vector map digitizer with TCL/TK-based graphical
-user interface. Attribute tables can be directly generated while
-digitizing (define in "Settings" first).
-
-<h2>NOTES</h2>
-
-The <b>bgcmd</b> option is intended to be used with display (d.*) commands.
-If several display commands are to be used to render the background
-they should be separated with the semi-colon ';' character.
-When run from the command line, these display commands will generally
-need to be "quoted" as they will contain spaces (see examples).
-
-<p>
-<b>Dead (deleted) lines</b>: If a user deletes a line in <em>v.digit</em>,
-it is internally only marked in the geometry file as 'dead' but it remains
-there and occupies space. Any vector module used afterwards on this map
-which really reads and writes vector geometry (so
-not <em><a href="g.copy.html">g.copy</a></em>) will writes only lines
-which are 'alive'.
-
-<h2>EXAMPLES</h2>
-
-<h3>Start a monitor and display a raster to help setup and zoom to area of interest</h3>
-
-<div class="code"><pre>
-d.mon x0
-d.rast name_of_raster
-</pre></div>
-
-<h3>Digitizing an area based on a existing raster map; creating a new vector map</h3>
-
-<div class="code"><pre>
-v.digit -n map=name_of_new_vector_map bgcmd="d.rast map=name_of_raster"
-</pre></div>
-
-<p>
-The <b>-n</b> flag specifies that your vector map does not yet exist and
-thus will be created with the name given by <b>map</b>. The <b>bgcmd</b>
-specifies a display (d.*) command and is set in "quotes" as it contains a space.
-
-<p>
-The <em>v.digit</em> GUI appears and vector map "name_of_new_vector_map" is created.
-
-<p>
-After leaving <em>v.digit</em>, run:
-
-<div class="code"><pre>
-d.erase
-d.vect "name_of_new_vector_map"
-</pre></div>
-
-The display should be cleared and the newly created vector should appear in
-the monitor.
-
-<h3>Digitizing a second vector, using your first vector and the raster image
-as background</h3>
-
-<div class="code"><pre>
-v.digit -n map=name_of_second_vector \
-bgcmd="d.rast map=name_of_your_raster; d.vect map=name_of_new_vector_map"
-</pre></div>
-
-The <em>v.digit</em> GUI appears and the layers defined with <b>bgcmd</b>
-are displayed in the background. As the <b>bgcmd</b> commands are executed
-as a series of commands (separated by a ";"), the last command (d.vect)
-displays over the top of the earlier raster image.
-
-
-<h3>Combining <b>bgcmd</b> with <em>d.save</em> to use the existing
-display as a backdrop</h3>
-
-<div class="code"><pre>
-v.digit map=name bgcmd="`d.save -o | cut -f1 -d'#' | tr '\n' ';'`"
-</pre></div>
-
-<em><a href="d.save.html"><em>d.save</em></a></em> will list the commands used to draw
-the current display; <em>cut</em> and <em>tr</em> are UNIX commands which are
-used to remove comments and trade newlines for semi-colons, respectively.
-
-<h2>SEE ALSO</h2>
-
-<em>
- <a href="r.digit.html">r.digit</a>,
- <a href="v.clean.html">v.clean</a>,
- <a href="v.edit.html">v.edit</a>
-</em>
-
-<p>
-See also <em><a href="wxGUI.Vector_Digitizing_Tool.html">wxGUI vector digitizing tool</a></em>.
-
-<h2>AUTHOR</h2>
-
-Radim Blazek, ITC-Irst, Trento, Italy
-
-<p>
-<i>Last changed: $Date$</i>
Copied: grass/trunk/vector/v.digit/v.digit.html (from rev 32770, grass/trunk/vector/v.digit/description.html)
===================================================================
--- grass/trunk/vector/v.digit/v.digit.html (rev 0)
+++ grass/trunk/vector/v.digit/v.digit.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,98 @@
+<h2>DESCRIPTION</h2>
+
+<em>v.digit</em> is a vector map digitizer with TCL/TK-based graphical
+user interface. Attribute tables can be directly generated while
+digitizing (define in "Settings" first).
+
+<h2>NOTES</h2>
+
+The <b>bgcmd</b> option is intended to be used with display (d.*) commands.
+If several display commands are to be used to render the background
+they should be separated with the semi-colon ';' character.
+When run from the command line, these display commands will generally
+need to be "quoted" as they will contain spaces (see examples).
+
+<p>
+<b>Dead (deleted) lines</b>: If a user deletes a line in <em>v.digit</em>,
+it is internally only marked in the geometry file as 'dead' but it remains
+there and occupies space. Any vector module used afterwards on this map
+which really reads and writes vector geometry (so
+not <em><a href="g.copy.html">g.copy</a></em>) will writes only lines
+which are 'alive'.
+
+<h2>EXAMPLES</h2>
+
+<h3>Start a monitor and display a raster to help setup and zoom to area of interest</h3>
+
+<div class="code"><pre>
+d.mon x0
+d.rast name_of_raster
+</pre></div>
+
+<h3>Digitizing an area based on a existing raster map; creating a new vector map</h3>
+
+<div class="code"><pre>
+v.digit -n map=name_of_new_vector_map bgcmd="d.rast map=name_of_raster"
+</pre></div>
+
+<p>
+The <b>-n</b> flag specifies that your vector map does not yet exist and
+thus will be created with the name given by <b>map</b>. The <b>bgcmd</b>
+specifies a display (d.*) command and is set in "quotes" as it contains a space.
+
+<p>
+The <em>v.digit</em> GUI appears and vector map "name_of_new_vector_map" is created.
+
+<p>
+After leaving <em>v.digit</em>, run:
+
+<div class="code"><pre>
+d.erase
+d.vect "name_of_new_vector_map"
+</pre></div>
+
+The display should be cleared and the newly created vector should appear in
+the monitor.
+
+<h3>Digitizing a second vector, using your first vector and the raster image
+as background</h3>
+
+<div class="code"><pre>
+v.digit -n map=name_of_second_vector \
+bgcmd="d.rast map=name_of_your_raster; d.vect map=name_of_new_vector_map"
+</pre></div>
+
+The <em>v.digit</em> GUI appears and the layers defined with <b>bgcmd</b>
+are displayed in the background. As the <b>bgcmd</b> commands are executed
+as a series of commands (separated by a ";"), the last command (d.vect)
+displays over the top of the earlier raster image.
+
+
+<h3>Combining <b>bgcmd</b> with <em>d.save</em> to use the existing
+display as a backdrop</h3>
+
+<div class="code"><pre>
+v.digit map=name bgcmd="`d.save -o | cut -f1 -d'#' | tr '\n' ';'`"
+</pre></div>
+
+<em><a href="d.save.html"><em>d.save</em></a></em> will list the commands used to draw
+the current display; <em>cut</em> and <em>tr</em> are UNIX commands which are
+used to remove comments and trade newlines for semi-colons, respectively.
+
+<h2>SEE ALSO</h2>
+
+<em>
+ <a href="r.digit.html">r.digit</a>,
+ <a href="v.clean.html">v.clean</a>,
+ <a href="v.edit.html">v.edit</a>
+</em>
+
+<p>
+See also <em><a href="wxGUI.Vector_Digitizing_Tool.html">wxGUI vector digitizing tool</a></em>.
+
+<h2>AUTHOR</h2>
+
+Radim Blazek, ITC-Irst, Trento, Italy
+
+<p>
+<i>Last changed: $Date$</i>
Deleted: grass/trunk/vector/v.distance/description.html
===================================================================
--- grass/trunk/vector/v.distance/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/vector/v.distance/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,146 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-<EM>v.distance</EM> finds the nearest element in vector map
-(<em>to</em>) for elements in vector map (<em>from</em>). Various
-information about the vectors' relationships (distance, category, etc.) may be uploaded
-to the attribute table attached to the first vector map, or printed to
-'stdout'. A new vector map may be created where lines connecting
-nearest points on features are written. <em>dmin</em> and/or <em>dmax</em> can be used to limit the search radius.
-
-<H2>NOTES</H2>
-
-If a nearest feature does not have a category, the attribute column is updated
-to <em>null</em>. This is true also for areas, which means for example,
-that if a point is in an island (area WITHOUT category), <EM>v.distance</EM>
-does not search for the nearest area WITH category; the island is identified
-as the nearest and category updated to null.
-<p>
-The upload <em>column</em>(s) must already exist. Create one with <em>v.db.addcol</em>.
-<p>
-In lat-long locations <em>v.distance</em> gives distances (<em>dist</em>
-and <em>to_along</em>) in meters not in degrees calculated as geodesic
-distances on a sphere.
-
-<h2>EXAMPLES</H2>
-
-<H3>Find nearest lines</H3>
-
-Find <EM>nearest lines</EM> in vector map <B>ln</B> for points from
-vector map <B>pnt</B> within the given threshold and write related
-line categories to column <B>linecat</B> in an attribute table attached
-to vector map <B>pnt</B>:
-
-<div class="code"><pre>
-v.distance from=pnt to=ln upload=cat column=linecat
-</pre></div>
-
-<H3>Find nearest area</H3>
-
-For each point from vector map <B>pnt</B>, find <EM>nearest area</EM>
-from map <B>ar</B> within the given threshold and write the related
-area categories to column <B>areacat</B> in an attribute table attached
-to vector map <B>pnt</B> (in the case that a point falls into a polygon area,
-the distance is zero):
-
-<div class="code"><pre>
-v.distance from=pnt to=ar upload=cat column=areacat
-</pre></div>
-
-<H3>Create a new vector map</H3>
-
-Create a new vector map which contains <EM>lines connecting nearest
-features</EM> of maps <B>pnt</B> and map <B>ln</B>. The resulting
-vector map can be used for example to connect points to a network as
-needed for network analysis:
-
-<div class="code"><pre>
-v.distance -p from=pnt to=ln out=connections upload=dist column=dist
-</pre></div>
-
-<H3>Query information</H3>
-
-Query information from selected point(s). <EM>v.distance</EM> takes
-points from a vector map as input instead of stdin. A new vector map
-with query points has to be created before the map can be analysed.
-<p>
-
-Create query map (if not present):
-
-<div class="code"><pre>
-echo "123456|654321|1" | v.in.ascii output=pnt
-</pre></div>
-
-Find nearest features:
-
-<div class="code"><pre>
-v.distance from=pnt to=map_to_query upload=cat col=somecol -p
-</pre></div>
-
-<H3>Point-in-polygon</H3>
-
-Find <EM>area</EM> from vector map <B>ar</B> for each point from
-vector map <B>pnt</B> in which the individual point falls, and
-write the related area categories to column <B>areacat</B> into
-the attribute table attached to vector map <B>pnt</B>:
-
-<div class="code"><pre>
-v.distance from=pnt to=ar dmax=0 upload=cat column=areacat
-</pre></div>
-
-<H3>Univariate statistics on results</H3>
-
-Create a vector map containing connecting lines and investigate mean
-distance to targets. An alternative solution is to use
-the <tt>v.distance upload=dist</tt> option to upload distances into
-the <i>bugs</i> vector directly, then run v.univar on that. Also note
-you can upload two columns at a time, e.g. <tt>v.distance
-upload=cat,dist column=nearest_id,dist_to_nr</tt>.
-
-<div class="code"><pre>
-# create working copy
-g.copy vect=bugsites,bugs
-
-# add new attribute column to hold nearest archsite category number
-v.db.addcol map=bugs column="nrst_arch INTEGER"
-
-v.distance from=bugs to=archsites to_type=point upload=to_attr \
- to_column=cat column=nrst_arch out=vdistance_vectors_raw
-
-# we need to give the lines category numbers, create a table, and create
-# a column in that table to hold the distance data.
-v.category vdistance_vectors_raw out=vdistance_vectors type=line op=add
-g.remove v=vdistance_vectors_raw
-
-v.db.addtable map=vdistance_vectors column="length DOUBLE"
-v.to.db map=vdistance_vectors option=length column=length
-
-# calculcate statistics. Use v.univar.sh for extended statistics.
-v.univar vdistance_vectors column=length
-</pre></div>
-
-<H3>Print distance matrix</H3>
-
-<div class="code"><pre>
-v.distance -pa from=archsites to=archsites upload=dist col=dist
-</pre></div>
-
-Note: Matrix-like output is enabled only for flag <EM>-a</EM> and one
-given upload option.
-
-<H2>SEE ALSO</H2>
-
-<EM>
-<a href="r.distance.html">r.distance</a>,
-<a href="v.db.addcol.html">v.db.addcol</a>,
-<a href="v.what.vect.html">v.what.vect</a>
-</EM>
-
-
-<H2>AUTHOR</H2>
-
-Janne Soimasuo 1994, University of Joensuu, Faculty of Forestry, Finland<BR>
-Cmd line coordinates support: Markus Neteler, ITC-irst, Trento, Italy<BR>
-Updated for 5.1: Radim Blazek, ITC-irst, Trento, Italy<BR>
-Martix-like output by Martin Landa, FBK-irst, Trento, Italy
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/vector/v.distance/v.distance.html (from rev 32770, grass/trunk/vector/v.distance/description.html)
===================================================================
--- grass/trunk/vector/v.distance/v.distance.html (rev 0)
+++ grass/trunk/vector/v.distance/v.distance.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,146 @@
+<H2>DESCRIPTION</H2>
+
+<EM>v.distance</EM> finds the nearest element in vector map
+(<em>to</em>) for elements in vector map (<em>from</em>). Various
+information about the vectors' relationships (distance, category, etc.) may be uploaded
+to the attribute table attached to the first vector map, or printed to
+'stdout'. A new vector map may be created where lines connecting
+nearest points on features are written. <em>dmin</em> and/or <em>dmax</em> can be used to limit the search radius.
+
+<H2>NOTES</H2>
+
+If a nearest feature does not have a category, the attribute column is updated
+to <em>null</em>. This is true also for areas, which means for example,
+that if a point is in an island (area WITHOUT category), <EM>v.distance</EM>
+does not search for the nearest area WITH category; the island is identified
+as the nearest and category updated to null.
+<p>
+The upload <em>column</em>(s) must already exist. Create one with <em>v.db.addcol</em>.
+<p>
+In lat-long locations <em>v.distance</em> gives distances (<em>dist</em>
+and <em>to_along</em>) in meters not in degrees calculated as geodesic
+distances on a sphere.
+
+<h2>EXAMPLES</H2>
+
+<H3>Find nearest lines</H3>
+
+Find <EM>nearest lines</EM> in vector map <B>ln</B> for points from
+vector map <B>pnt</B> within the given threshold and write related
+line categories to column <B>linecat</B> in an attribute table attached
+to vector map <B>pnt</B>:
+
+<div class="code"><pre>
+v.distance from=pnt to=ln upload=cat column=linecat
+</pre></div>
+
+<H3>Find nearest area</H3>
+
+For each point from vector map <B>pnt</B>, find <EM>nearest area</EM>
+from map <B>ar</B> within the given threshold and write the related
+area categories to column <B>areacat</B> in an attribute table attached
+to vector map <B>pnt</B> (in the case that a point falls into a polygon area,
+the distance is zero):
+
+<div class="code"><pre>
+v.distance from=pnt to=ar upload=cat column=areacat
+</pre></div>
+
+<H3>Create a new vector map</H3>
+
+Create a new vector map which contains <EM>lines connecting nearest
+features</EM> of maps <B>pnt</B> and map <B>ln</B>. The resulting
+vector map can be used for example to connect points to a network as
+needed for network analysis:
+
+<div class="code"><pre>
+v.distance -p from=pnt to=ln out=connections upload=dist column=dist
+</pre></div>
+
+<H3>Query information</H3>
+
+Query information from selected point(s). <EM>v.distance</EM> takes
+points from a vector map as input instead of stdin. A new vector map
+with query points has to be created before the map can be analysed.
+<p>
+
+Create query map (if not present):
+
+<div class="code"><pre>
+echo "123456|654321|1" | v.in.ascii output=pnt
+</pre></div>
+
+Find nearest features:
+
+<div class="code"><pre>
+v.distance from=pnt to=map_to_query upload=cat col=somecol -p
+</pre></div>
+
+<H3>Point-in-polygon</H3>
+
+Find <EM>area</EM> from vector map <B>ar</B> for each point from
+vector map <B>pnt</B> in which the individual point falls, and
+write the related area categories to column <B>areacat</B> into
+the attribute table attached to vector map <B>pnt</B>:
+
+<div class="code"><pre>
+v.distance from=pnt to=ar dmax=0 upload=cat column=areacat
+</pre></div>
+
+<H3>Univariate statistics on results</H3>
+
+Create a vector map containing connecting lines and investigate mean
+distance to targets. An alternative solution is to use
+the <tt>v.distance upload=dist</tt> option to upload distances into
+the <i>bugs</i> vector directly, then run v.univar on that. Also note
+you can upload two columns at a time, e.g. <tt>v.distance
+upload=cat,dist column=nearest_id,dist_to_nr</tt>.
+
+<div class="code"><pre>
+# create working copy
+g.copy vect=bugsites,bugs
+
+# add new attribute column to hold nearest archsite category number
+v.db.addcol map=bugs column="nrst_arch INTEGER"
+
+v.distance from=bugs to=archsites to_type=point upload=to_attr \
+ to_column=cat column=nrst_arch out=vdistance_vectors_raw
+
+# we need to give the lines category numbers, create a table, and create
+# a column in that table to hold the distance data.
+v.category vdistance_vectors_raw out=vdistance_vectors type=line op=add
+g.remove v=vdistance_vectors_raw
+
+v.db.addtable map=vdistance_vectors column="length DOUBLE"
+v.to.db map=vdistance_vectors option=length column=length
+
+# calculcate statistics. Use v.univar.sh for extended statistics.
+v.univar vdistance_vectors column=length
+</pre></div>
+
+<H3>Print distance matrix</H3>
+
+<div class="code"><pre>
+v.distance -pa from=archsites to=archsites upload=dist col=dist
+</pre></div>
+
+Note: Matrix-like output is enabled only for flag <EM>-a</EM> and one
+given upload option.
+
+<H2>SEE ALSO</H2>
+
+<EM>
+<a href="r.distance.html">r.distance</a>,
+<a href="v.db.addcol.html">v.db.addcol</a>,
+<a href="v.what.vect.html">v.what.vect</a>
+</EM>
+
+
+<H2>AUTHOR</H2>
+
+Janne Soimasuo 1994, University of Joensuu, Faculty of Forestry, Finland<BR>
+Cmd line coordinates support: Markus Neteler, ITC-irst, Trento, Italy<BR>
+Updated for 5.1: Radim Blazek, ITC-irst, Trento, Italy<BR>
+Martix-like output by Martin Landa, FBK-irst, Trento, Italy
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/vector/v.drape/description.html
===================================================================
--- grass/trunk/vector/v.drape/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/vector/v.drape/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,107 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>v.drape</em> converts 2D/3D vector data into 3D vector format via
-sampling of an elevation surface. Three sampling algorithms adapted
-from <a href="v.sample.html">v.sample</a> were incorporated into this
-module: nearest neighbor, bilinear, and cubic convultion.
-
-<h2>NOTES</h2>
-
-Please run beforehand
-
-<div class="code"><pre>
-g.region vect=2D_vector
-</pre></div>
-
-and make sure that the extent of the elevation raster is at least as
-big as the vector to convert.
-
-<P>
-Additional vertices can be added to the input 2D vector map
-with <a href="v.split.html">v.split</a>.
-
-<P>
-The module can be used in conjunction
-with <a href="v.out.pov.html">v.out.pov</a> and
-<a href="r.out.pov.html">r.out.pov</a> to export a complete set of
-vector and raster data for display in POVRAY.
-
-<h2>EXAMPLE</h2>
-
-Spearfish example:
-
-<div class="code"><pre>
-g.region -p vect=roads align=elevation.10m
-v.drape in=roads rast=elevation.10m method=bilinear out=roads3d
-v.info roads3d
-</pre></div>
-
-<h2>POVRAY EXAMPLE</h2>
-
-<div class="code"><pre>
-#setup the region
-g.region vect=roads align=elevation.10m -p
-#export the vector data
-v.drape in=roads out=roads3d rast=elevation.10m
-v.out.pov roads3d out=roads3d.pov
-#export the raster data
-r.out.pov elevation.10m tga=elevation.tga
-r.out.png landcover.30m out=landcover30m.png
-
-# now write a complete povray-script and launch povray
-</pre></div>
-
-<h2>ERROR MESSAGES</h2>
-
-If the following error message appears
-
-<div class="code"><pre>
-WARNING: Current region does not include the entire input vector map
-WARNING: Reading raster map request for row 466 is outside region
-ERROR: Problem reading raster map
-</pre></div>
-
-it indicates that the vector map is spatially larger than the current
-region settings. To avoid this problem, set region from the input
-vector map and re-run <em>v.drape</em>.
-
-<div class="code"><pre>
-g.region vect=vectmap
-</pre></div>
-
-If the following error message appears
-
-<div class="code"><pre>
-WARNING: Elevation raster map does not cover the entire area of the input vector map.
-</pre></div>
-
-it indicates that the vector map is spatially larger than the raster map.
-To avoid this problem, the vector map needs to be clipped to the raster
-map extent, for example:
-
-<div class="code"><pre>
-g.region rast=demname
-v.in.region clipbox
-v.overlay ain=clipbox bin=vectmap out=vectmap_clipped op=and
-v.drape vectmap_clipped out=vectdrape rast=demname
-</pre></div>
-
-Then <em>v.drape</em> should perform the draping.
-
-<h2>SEE ALSO</h2>
-
-<EM>
-<A HREF="r.out.pov.html">r.out.pov</A>,
-<A HREF="v.in.region.html">v.in.region</A>,
-<A HREF="v.out.pov.html">v.out.pov</A>,
-<A HREF="v.overlay.html">v.overlay</A>,
-<A HREF="v.split.html">v.split</A>,
-<A HREF="v.what.rast.html">v.what.rast</A>,
-<A HREF="v.extrude.html">v.extrude</A>
-</EM>
-
-<h2>AUTHOR</h2>
-
-Dylan Beaudette, University of California at Davis.
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/vector/v.drape/v.drape.html (from rev 32770, grass/trunk/vector/v.drape/description.html)
===================================================================
--- grass/trunk/vector/v.drape/v.drape.html (rev 0)
+++ grass/trunk/vector/v.drape/v.drape.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,107 @@
+<h2>DESCRIPTION</h2>
+
+<em>v.drape</em> converts 2D/3D vector data into 3D vector format via
+sampling of an elevation surface. Three sampling algorithms adapted
+from <a href="v.sample.html">v.sample</a> were incorporated into this
+module: nearest neighbor, bilinear, and cubic convultion.
+
+<h2>NOTES</h2>
+
+Please run beforehand
+
+<div class="code"><pre>
+g.region vect=2D_vector
+</pre></div>
+
+and make sure that the extent of the elevation raster is at least as
+big as the vector to convert.
+
+<P>
+Additional vertices can be added to the input 2D vector map
+with <a href="v.split.html">v.split</a>.
+
+<P>
+The module can be used in conjunction
+with <a href="v.out.pov.html">v.out.pov</a> and
+<a href="r.out.pov.html">r.out.pov</a> to export a complete set of
+vector and raster data for display in POVRAY.
+
+<h2>EXAMPLE</h2>
+
+Spearfish example:
+
+<div class="code"><pre>
+g.region -p vect=roads align=elevation.10m
+v.drape in=roads rast=elevation.10m method=bilinear out=roads3d
+v.info roads3d
+</pre></div>
+
+<h2>POVRAY EXAMPLE</h2>
+
+<div class="code"><pre>
+#setup the region
+g.region vect=roads align=elevation.10m -p
+#export the vector data
+v.drape in=roads out=roads3d rast=elevation.10m
+v.out.pov roads3d out=roads3d.pov
+#export the raster data
+r.out.pov elevation.10m tga=elevation.tga
+r.out.png landcover.30m out=landcover30m.png
+
+# now write a complete povray-script and launch povray
+</pre></div>
+
+<h2>ERROR MESSAGES</h2>
+
+If the following error message appears
+
+<div class="code"><pre>
+WARNING: Current region does not include the entire input vector map
+WARNING: Reading raster map request for row 466 is outside region
+ERROR: Problem reading raster map
+</pre></div>
+
+it indicates that the vector map is spatially larger than the current
+region settings. To avoid this problem, set region from the input
+vector map and re-run <em>v.drape</em>.
+
+<div class="code"><pre>
+g.region vect=vectmap
+</pre></div>
+
+If the following error message appears
+
+<div class="code"><pre>
+WARNING: Elevation raster map does not cover the entire area of the input vector map.
+</pre></div>
+
+it indicates that the vector map is spatially larger than the raster map.
+To avoid this problem, the vector map needs to be clipped to the raster
+map extent, for example:
+
+<div class="code"><pre>
+g.region rast=demname
+v.in.region clipbox
+v.overlay ain=clipbox bin=vectmap out=vectmap_clipped op=and
+v.drape vectmap_clipped out=vectdrape rast=demname
+</pre></div>
+
+Then <em>v.drape</em> should perform the draping.
+
+<h2>SEE ALSO</h2>
+
+<EM>
+<A HREF="r.out.pov.html">r.out.pov</A>,
+<A HREF="v.in.region.html">v.in.region</A>,
+<A HREF="v.out.pov.html">v.out.pov</A>,
+<A HREF="v.overlay.html">v.overlay</A>,
+<A HREF="v.split.html">v.split</A>,
+<A HREF="v.what.rast.html">v.what.rast</A>,
+<A HREF="v.extrude.html">v.extrude</A>
+</EM>
+
+<h2>AUTHOR</h2>
+
+Dylan Beaudette, University of California at Davis.
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/vector/v.edit/description.html
===================================================================
--- grass/trunk/vector/v.edit/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/vector/v.edit/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,435 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-The module <em>v.edit</em> allows the user to edit a vector map
-via command line interface.
-
-<p>
-<em>v.edit</em> supports only "simple" vector features: points,
-centroids, lines and boundaries. Currently, only 2D vector features
-(except of tool <b>zbulk</b>) are supported.
-
-<p>
-Provides editing features' geometry. Attribute data connected to the
-vector map are not modified at all.
-
-<p>
-Vector features can be selected either by internal <b>id</b>, category
-number <b>cats</b>, coordinates <b>coords</b>, bounding
-box <b>bbox</b>, <b>polygon</b>, <b>where</b> statement (attribute
-data) or by <b>query</b>. Selecting features by coordinates is
-affected by the current 2D resolution or by the threshold distance
-given by <b>thresh</b>. The options are <em>orthogonal</em>, i.e. can
-be used in various combinations. For example:
-
-<div class="code"><pre>
-v.edit map=roads tool=select \
- coord=599505,4921010,603389.0625,4918292.1875 \
- thresh=10000 where="label='interstate'"
-</pre></div>
-
-selects all features (and prints their id's to standard output)
-covered by two bounding boxes (center at 599505,4921010 and
-603389.0625,4918292.1875, size 2*10000) with attribute
-label='interstate'.
-
-<h2>NOTES</h2>
-
-If no vector features are selected or the flag <b>-t</b> is
-used, topology is not build at the end.
-
-<h2>USAGE</h2>
-
-<h3>Feature selection</h3>
-
-Vector features can be selected in several ways:
-<ul>
- <li><b>ids</b> - using internal (unique) feature id's</li>
- <li><b>cats</b> - using category numbers</li>
- <li><b>coords</b> - using x,y coordinate pairs (center of bounding
- box, size defined by <b>thresh</b>)</li>
- <li><b>bbox</b> - using bounding box</li>
- <li><b>polygon</b> - using polygon (at least 3 coordinate pairs have to be set)</li>
- <li><b>where</b> - using where statement (attribute data)
- <li><b>query</b> - special query (e.g. minimal vector line length)
-</ul>
-
-Additional parameters for vector feature specification are:
-<ul>
- <li><b>layer</b> - layer number (currently used only
- with <b>cats</b> or <b>where</b> option)</li>
- <li><b>thresh</b> - threshold distance used for selecting vector
- features by coordinates</li>
-</ul>
-
-<h3>Tool description</h3>
-
-<ul>
- <li><b>create</b> - Create new (empty) vector map
- (see <em><a href="v.in.ascii.html">v.in.ascii</a></em>). Optionally vector
- features (in GRASS ASCII standard format) can be read from
- standard input (<b>input=-</b>) or from the text file given by
- the <b>input</b> option.</li>
-
- <li><b>add</b> - Add new vector features (defined in GRASS ASCII
- standard format) to existing vector map. Features can be read from
- standard input or from the given text file (<b>input</b>
- option). If no header is given, the <b>-n</b> flag must be
- used. Added features can be snapped (defined by <b>snap</b>
- parameter) to nodes or vertices based on threshold
- distance <b>thresh</b>.</li>
-
- <li><b>delete</b> - Delete selected vector features from existing
- vector map.</li>
-
- <li><b>copy</b> - Make identical copy of selected vector
- features. If background map <b>bgmap</b> is given copy features
- from background map, not from currently modified vector map.</li>
-
- <li><b>move</b> - Move selected features of existing vector map
- relatively to their current location. This tool requires
- <b>move</b> option. The option defines coordinates of the movement
- direction. Moved features can be snapped (defined by <b>snap</b>
- parameter) to nodes or vertices based on threshold
- distance <b>thresh</b>.</li>
-
- <li><b>flip</b> - Flip direction of selected vector lines
- (lines or boundaries).</li>
-
- <li><b>catadd</b> - Add new layer category(ies) to selected vector
- feature(s). Category can be later used for new database
- entry.</li>
-
- <li><b>catdel</b> - Delete layer category(ies) of selected vector
- feature(s).</li>
-
- <li><b>merge</b> - Merge (at least two) selected vector lines or
- boundaries. The geometry of the merged vector lines can be
- changed. If the second line from two selected lines is in opposite
- direction to the first, it will be flipped. See also
- module <em><a href="v.build.polylines.html">v.build.polylines</a></em>.</li>
-
- <li><b>break</b> - Split given vector line or boundary into two
- lines on location given by <b>coords</b>. If <b>coords</b> not
- given, breaks all selected lines at each intersection (based
- on <em><a href="v.clean.html">v.clean</a></em>, tool=break).</li>
-
- <li><b>snap</b> - Snap vector features in given threshold. See
- also module <em><a href="v.clean.html">v.clean</a></em>. Note that this
- tool supports only snapping to nodes. Parameters <b>snap</b> and
- <b>bgmap</b> are ignored.</li>
-
- <li><b>connect</b> - Connect selected lines or boundaries, the
- first given line is connected to the second one. The second line
- is broken if necessary. The lines are connected only if distance
- between them is not greater than snapping threshold
- distance <b>thresh</b>.</li>
-
- <li><b>chtype</b> - Change feature type of selected geometry
- objects. Points are converted to centroids, centroids to points,
- lines to boundaries and boundaries to lines.
-
- <li><b>vertexadd</b> - Add vertex(ces) to the given vector lines
- or boundaries. Location of the new vertex is given by <b>coord</b>
- option. If <b>-1</b> is given only first found line or boundary in bounding
- box is modified.</li>
-
- <li><b>vertexdel</b> - Remove vertex(ces) specified by
- <b>coords</b> option. If <b>-1</b> is given only first found line or
- boundary in bounding box is modified.</li>
-
- <li><b>vertexmove</b> - Move vertex(ces) specified
- by <b>coords</b> option. Direction of the movement is specified by
- the <b>move</b> option. If <b>-1</b> is given only first found
- line or boundary in bounding box is modified. Moved vertex can be
- snapped (defined <b>snap</b>) to nodes or vertices based on
- threshold distance <b>thresh</b>.</li>
-
- <li><b>zbulk</b> - Assign z coordinate to 3D vector lines in given
- bounding box. The first found line will get z coordinate based on
- value given by <b>zbulk</b> parameter. Z coordinate of other
- selected lines will be increased by step given by <b>zbulk</b>
- parameter. This tool strictly requires <b>bbox</b>
- and <b>zbulk</b> parameter. Also input vector map must be 3D.</li>
-
- <li><b>select</b> - Print comma separated list of selected line
- id's. No editing is done.
-</ul>
-
-<h2>EXAMPLES</h2>
-
-<h3>Create new vector map</h3>
-
-Create new (empty) vector map:
-
-<div class="code"><pre>
-v.edit tool=create map=vectmap
-</pre></div>
-
-Create new vector map and read data from file 'roads.txt':
-
-<div class="code"><pre>
-v.out.ascii in=roads format=standard > roads.txt;
-v.edit tool=create map=vectmap input=roads.txt
-</pre></div>
-
-or alternatively
-
-<div class="code"><pre>
-cat roads.txt | v.edit tool=create map=vectmap input=-
-</pre></div>
-
-<h3>Add new features to existing vector map</h3>
-
-Add point to the vector map (without header):
-
-<div class="code"><pre>
-echo "P 1 1
- 640794 214874
- 1 1" | v.edit -n tool=add map=vectmap
-</pre></div>
-
-Add new features read from standard input:
-
-<div class="code"><pre>
-v.out.ascii in=railroads format=standard | v.edit tool=add map=vectmap
-</pre></div>
-
-<h3>Delete selected features from vector map layer</h3>
-
-Remove all vector features with category number 1 or 2:
-
-<div class="code"><pre>
-v.edit tool=delete map=roads cats=1,2
-</pre></div>
-
-Remove all vector features except of those with category number 1 or 2
-(reverse selection):
-
-<div class="code"><pre>
-v.edit -r tool=delete map=roads cats=1,2
-</pre></div>
-
-Remove features with category 1 or 2 located on coordinates
-600952.625,4926107 (bounding box based on the current 2D resolution):
-
-<div class="code"><pre>
-g.region -d;
-v.edit tool=delete map=roads cats=1,2 coords=600952.625,4926107
-</pre></div>
-
-Remove all features with category 1 and 2 covered by two bounding boxes
-(center coordinates 592542.892,4924766.996 and 603389.062,4918292.187,
-size 2000 map units):
-
-<div class="code"><pre>
-v.edit map=roads tool=delete \
- coord=592542.892,4924766.996,603389.062,4918292.187 \
- thresh=1000 cat=1,2
-</pre></div>
-
-<h3>Copy selected features from background map</h3>
-
-Copy all features with category number 1 from background map:
-
-<div class="code"><pre>
-v.edit map=roads tool=copy bgmap=archsites cat=1
-</pre></div>
-
-<h3>Move features</h3>
-
-Move feature (vector point) located on coordinates 602580,4918480 to
-coordinates 603580,4919480:
-
-<div class="code"><pre>
-v.edit tool=move map=archsites coord=602580,4918480 th=1e-2 move=1000,1000
-</pre></div>
-
-Move all features with category 1 1000 map units to the west and 1000
-map units to the south. Moved features snap to nodes in threshold
-distance 10 map units:
-
-<div class="code"><pre>
-v.edit tool=move map=roads cat=1 move=1000,-1000 snap=node thresh=-1,10
-</pre></div>
-
-Move all features defined by bounding box
-601530,4921560,602520,4922310 (W,S,E,N) 1000 map units to the
-east and 1000 map units to the north:
-
-<div class="code"><pre>
-v.edit tool=move map=roads bbox=601530,4921560,602520,4922310 move=-1000,1000
-</pre></div>
-
-<h3>Flip direction of vector lines</h3>
-
-Flip direction of all vector lines:
-
-<div class="code"><pre>
-v.edit tool=flip map=streams cats=1-9999 type=line
-</pre></div>
-
-<h3>Add / delete layer category number</h3>
-
-Add new layer/category 2/1, 2/3, 2/4, 2/5 to features covered by given polygon:
-
-<div class="code"><pre>
-v.edit tool=catadd map=roads \
- polygon=599877.75,4925088.375,597164.812,4922524.5,601338.562,4920914.625 \
- layer=2 cat=1,3-5
-</pre></div>
-
-Delete layer/category 1/1, line id 1:
-
-<div class="code"><pre>
-v.edit tool=catdel map=roads id=1 cats=5
-</pre></div>
-
-<h3>Merge lines</h3>
-
-Merge two lines with given category number:
-
-<div class="code"><pre>
-v.edit map=roads tool=merge cat=4
-</pre></div>
-
-<h3>Split line on given point</h3>
-
-Split line id 810 on coordinates 604268,4923570 in threshold 50 map units:
-
-<div class="code"><pre>
-v.edit map=roads tool=break coords=604268,4923570 id=810 thresh=50
-</pre></div>
-
-<h3>Break selected lines at each intersection</h3>
-
-Break selected lines (with category number 1) at each intersection:
-
-<div class="code"><pre>
-v.edit map=roads tool=break cat=1
-</pre></div>
-
-<h3>Snap lines</h3>
-
-Snap all lines using threshold distance 20 map units:
-
-<div class="code"><pre>
-v.edit map=roads id=1-9999 tool=snap thresh=-1,20 type=line
-</pre></div>
-
-<h3>Connect lines</h3>
-
-Connect line id 48 to line id 565:
-
-<div class="code"><pre>
-v.edit map=roads tool=connect id=48,565
-</pre></div>
-
-Connect line id 48 to line id 565; line id 60 to line id
-50. Maximum threshold distance is 700 map units:
-
-<div class="code"><pre>
-v.edit map=roads tool=connect id=48,565,60,50 thresh=-1,700
-</pre></div>
-
-<h3>Add vertex</h3>
-
-Add new vertex to the line located at 600952,4926107, threshold is
-set to 1 map unit:
-
-<div class="code"><pre>
-v.edit tool=vertexadd map=roads coords=600952,4926107 thresh=1
-</pre></div>
-
-<h3>Delete vertices</h3>
-
-Delete vertex located at 593191.608,4925684.849 (threshold set to 0.1 map units).
-Modify only lines with category 1:
-
-<div class="code"><pre>
-v.edit tool=vertexdel map=roads coord=593191.608,4925684.849 \
- thresh=1-e1 cats=1
-</pre></div>
-
-<h3>Move vertices</h3>
-
-Move vertices located at 604441,4921088 (threshold set to 100 map units).
-Modify only lines with categories 1-10:
-
-<div class="code"><pre>
-v.edit tool=vertexmove map=roads cats=1-10 coord=604441,4921088 \
- thresh=100 move=1000,1000
-</pre></div>
-
-<h3>Select features and print their id's</h3>
-
-Print id's of selected features, e.g.:
-
-<div class="code"><pre>
-v.edit map=soils at PERMANENT tool=select \
- bbox=595733.8125,4919781.75,598536.1875,4917396.75 --q
-</pre></div>
-
-Example with <em><a href="d.vect.html">d.vect</a></em>:
-
-<div class="code"><pre>
-d.erase;
-d.vect roads;
-d.vect -i map=roads cats=`v.edit map=roads tool=select \
- coord=592542.89243878,4924766.99622811,603389.0625,4918292.1875 \
- thresh=1000 --q` col=red
-</pre></div>
-
-Select all lines shorter (or equal) than 10 map units:
-
-<div class="code"><pre>
-v.edit map=roads tool=select query=length thresh=-1,0,-10
-</pre></div>
-
-Select from given bounding box all lines longer then 200 map units:
-
-<div class="code"><pre>
-v.edit map=roads tool=select bbox=598260,4919730,605100,4926240 query=length thresh=-1,0,1000
-</pre></div>
-
-<h3>Fix height of contours</h3>
-
-Intput vector map contains 2D lines representing contours. Height can
-be assign to the contours using tool <b>zbulk</b>. First of all 2D
-lines need to be converted to 3D lines:
-
-<div class="code"><pre>
-v.extrude input=line2 output=line3 height=0 type=line
-</pre></div>
-
-All lines which intersect with the line given by coordinates will be
-modified. First found line will get height 1000 map units, height of
-other selected lines will be increased by 10 map units.
-
-<div class="code"><pre>
-v.edit a2 tool=zbulk bbox=586121.25049368,4911970.21547109,603092.60466035,4927071.25713776 \
- zbulk=1000,10
-</pre></div>
-
-
-<h2>SEE ALSO</h2>
-
-<em>
-<a HREF="v.in.ascii.html">v.in.ascii</a>,
-<a HREF="v.info.html">v.info</a>,
-<a HREF="v.build.html">v.build</a>,
-<a HREF="v.clean.html">v.clean</a>,
-<a HREF="v.digit.html">v.digit</a>,
-<a HREF="v.extrude.html">v.extrude</a>
-</em>
-
-<p>
-See also <em><a href="wxGUI.Vector_Digitizing_Tool.html">wxGUI vector digitizing tool</a></em>.
-
-<h2>AUTHOR</h2>
-
-Original author: Wolf Bergenheim - independent developer<br>
-Various updates: Jachym Cepicky, Mendel University of Agriculture and Forestry in Brno, Czech Republic<br>
-Martin Landa, FBK-irst (formerly ITC-irst), Trento, Italy
-
-<p>
-<i>Last changed: $Date$</i>
Copied: grass/trunk/vector/v.edit/v.edit.html (from rev 32770, grass/trunk/vector/v.edit/description.html)
===================================================================
--- grass/trunk/vector/v.edit/v.edit.html (rev 0)
+++ grass/trunk/vector/v.edit/v.edit.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,435 @@
+<h2>DESCRIPTION</h2>
+
+The module <em>v.edit</em> allows the user to edit a vector map
+via command line interface.
+
+<p>
+<em>v.edit</em> supports only "simple" vector features: points,
+centroids, lines and boundaries. Currently, only 2D vector features
+(except of tool <b>zbulk</b>) are supported.
+
+<p>
+Provides editing features' geometry. Attribute data connected to the
+vector map are not modified at all.
+
+<p>
+Vector features can be selected either by internal <b>id</b>, category
+number <b>cats</b>, coordinates <b>coords</b>, bounding
+box <b>bbox</b>, <b>polygon</b>, <b>where</b> statement (attribute
+data) or by <b>query</b>. Selecting features by coordinates is
+affected by the current 2D resolution or by the threshold distance
+given by <b>thresh</b>. The options are <em>orthogonal</em>, i.e. can
+be used in various combinations. For example:
+
+<div class="code"><pre>
+v.edit map=roads tool=select \
+ coord=599505,4921010,603389.0625,4918292.1875 \
+ thresh=10000 where="label='interstate'"
+</pre></div>
+
+selects all features (and prints their id's to standard output)
+covered by two bounding boxes (center at 599505,4921010 and
+603389.0625,4918292.1875, size 2*10000) with attribute
+label='interstate'.
+
+<h2>NOTES</h2>
+
+If no vector features are selected or the flag <b>-t</b> is
+used, topology is not build at the end.
+
+<h2>USAGE</h2>
+
+<h3>Feature selection</h3>
+
+Vector features can be selected in several ways:
+<ul>
+ <li><b>ids</b> - using internal (unique) feature id's</li>
+ <li><b>cats</b> - using category numbers</li>
+ <li><b>coords</b> - using x,y coordinate pairs (center of bounding
+ box, size defined by <b>thresh</b>)</li>
+ <li><b>bbox</b> - using bounding box</li>
+ <li><b>polygon</b> - using polygon (at least 3 coordinate pairs have to be set)</li>
+ <li><b>where</b> - using where statement (attribute data)
+ <li><b>query</b> - special query (e.g. minimal vector line length)
+</ul>
+
+Additional parameters for vector feature specification are:
+<ul>
+ <li><b>layer</b> - layer number (currently used only
+ with <b>cats</b> or <b>where</b> option)</li>
+ <li><b>thresh</b> - threshold distance used for selecting vector
+ features by coordinates</li>
+</ul>
+
+<h3>Tool description</h3>
+
+<ul>
+ <li><b>create</b> - Create new (empty) vector map
+ (see <em><a href="v.in.ascii.html">v.in.ascii</a></em>). Optionally vector
+ features (in GRASS ASCII standard format) can be read from
+ standard input (<b>input=-</b>) or from the text file given by
+ the <b>input</b> option.</li>
+
+ <li><b>add</b> - Add new vector features (defined in GRASS ASCII
+ standard format) to existing vector map. Features can be read from
+ standard input or from the given text file (<b>input</b>
+ option). If no header is given, the <b>-n</b> flag must be
+ used. Added features can be snapped (defined by <b>snap</b>
+ parameter) to nodes or vertices based on threshold
+ distance <b>thresh</b>.</li>
+
+ <li><b>delete</b> - Delete selected vector features from existing
+ vector map.</li>
+
+ <li><b>copy</b> - Make identical copy of selected vector
+ features. If background map <b>bgmap</b> is given copy features
+ from background map, not from currently modified vector map.</li>
+
+ <li><b>move</b> - Move selected features of existing vector map
+ relatively to their current location. This tool requires
+ <b>move</b> option. The option defines coordinates of the movement
+ direction. Moved features can be snapped (defined by <b>snap</b>
+ parameter) to nodes or vertices based on threshold
+ distance <b>thresh</b>.</li>
+
+ <li><b>flip</b> - Flip direction of selected vector lines
+ (lines or boundaries).</li>
+
+ <li><b>catadd</b> - Add new layer category(ies) to selected vector
+ feature(s). Category can be later used for new database
+ entry.</li>
+
+ <li><b>catdel</b> - Delete layer category(ies) of selected vector
+ feature(s).</li>
+
+ <li><b>merge</b> - Merge (at least two) selected vector lines or
+ boundaries. The geometry of the merged vector lines can be
+ changed. If the second line from two selected lines is in opposite
+ direction to the first, it will be flipped. See also
+ module <em><a href="v.build.polylines.html">v.build.polylines</a></em>.</li>
+
+ <li><b>break</b> - Split given vector line or boundary into two
+ lines on location given by <b>coords</b>. If <b>coords</b> not
+ given, breaks all selected lines at each intersection (based
+ on <em><a href="v.clean.html">v.clean</a></em>, tool=break).</li>
+
+ <li><b>snap</b> - Snap vector features in given threshold. See
+ also module <em><a href="v.clean.html">v.clean</a></em>. Note that this
+ tool supports only snapping to nodes. Parameters <b>snap</b> and
+ <b>bgmap</b> are ignored.</li>
+
+ <li><b>connect</b> - Connect selected lines or boundaries, the
+ first given line is connected to the second one. The second line
+ is broken if necessary. The lines are connected only if distance
+ between them is not greater than snapping threshold
+ distance <b>thresh</b>.</li>
+
+ <li><b>chtype</b> - Change feature type of selected geometry
+ objects. Points are converted to centroids, centroids to points,
+ lines to boundaries and boundaries to lines.
+
+ <li><b>vertexadd</b> - Add vertex(ces) to the given vector lines
+ or boundaries. Location of the new vertex is given by <b>coord</b>
+ option. If <b>-1</b> is given only first found line or boundary in bounding
+ box is modified.</li>
+
+ <li><b>vertexdel</b> - Remove vertex(ces) specified by
+ <b>coords</b> option. If <b>-1</b> is given only first found line or
+ boundary in bounding box is modified.</li>
+
+ <li><b>vertexmove</b> - Move vertex(ces) specified
+ by <b>coords</b> option. Direction of the movement is specified by
+ the <b>move</b> option. If <b>-1</b> is given only first found
+ line or boundary in bounding box is modified. Moved vertex can be
+ snapped (defined <b>snap</b>) to nodes or vertices based on
+ threshold distance <b>thresh</b>.</li>
+
+ <li><b>zbulk</b> - Assign z coordinate to 3D vector lines in given
+ bounding box. The first found line will get z coordinate based on
+ value given by <b>zbulk</b> parameter. Z coordinate of other
+ selected lines will be increased by step given by <b>zbulk</b>
+ parameter. This tool strictly requires <b>bbox</b>
+ and <b>zbulk</b> parameter. Also input vector map must be 3D.</li>
+
+ <li><b>select</b> - Print comma separated list of selected line
+ id's. No editing is done.
+</ul>
+
+<h2>EXAMPLES</h2>
+
+<h3>Create new vector map</h3>
+
+Create new (empty) vector map:
+
+<div class="code"><pre>
+v.edit tool=create map=vectmap
+</pre></div>
+
+Create new vector map and read data from file 'roads.txt':
+
+<div class="code"><pre>
+v.out.ascii in=roads format=standard > roads.txt;
+v.edit tool=create map=vectmap input=roads.txt
+</pre></div>
+
+or alternatively
+
+<div class="code"><pre>
+cat roads.txt | v.edit tool=create map=vectmap input=-
+</pre></div>
+
+<h3>Add new features to existing vector map</h3>
+
+Add point to the vector map (without header):
+
+<div class="code"><pre>
+echo "P 1 1
+ 640794 214874
+ 1 1" | v.edit -n tool=add map=vectmap
+</pre></div>
+
+Add new features read from standard input:
+
+<div class="code"><pre>
+v.out.ascii in=railroads format=standard | v.edit tool=add map=vectmap
+</pre></div>
+
+<h3>Delete selected features from vector map layer</h3>
+
+Remove all vector features with category number 1 or 2:
+
+<div class="code"><pre>
+v.edit tool=delete map=roads cats=1,2
+</pre></div>
+
+Remove all vector features except of those with category number 1 or 2
+(reverse selection):
+
+<div class="code"><pre>
+v.edit -r tool=delete map=roads cats=1,2
+</pre></div>
+
+Remove features with category 1 or 2 located on coordinates
+600952.625,4926107 (bounding box based on the current 2D resolution):
+
+<div class="code"><pre>
+g.region -d;
+v.edit tool=delete map=roads cats=1,2 coords=600952.625,4926107
+</pre></div>
+
+Remove all features with category 1 and 2 covered by two bounding boxes
+(center coordinates 592542.892,4924766.996 and 603389.062,4918292.187,
+size 2000 map units):
+
+<div class="code"><pre>
+v.edit map=roads tool=delete \
+ coord=592542.892,4924766.996,603389.062,4918292.187 \
+ thresh=1000 cat=1,2
+</pre></div>
+
+<h3>Copy selected features from background map</h3>
+
+Copy all features with category number 1 from background map:
+
+<div class="code"><pre>
+v.edit map=roads tool=copy bgmap=archsites cat=1
+</pre></div>
+
+<h3>Move features</h3>
+
+Move feature (vector point) located on coordinates 602580,4918480 to
+coordinates 603580,4919480:
+
+<div class="code"><pre>
+v.edit tool=move map=archsites coord=602580,4918480 th=1e-2 move=1000,1000
+</pre></div>
+
+Move all features with category 1 1000 map units to the west and 1000
+map units to the south. Moved features snap to nodes in threshold
+distance 10 map units:
+
+<div class="code"><pre>
+v.edit tool=move map=roads cat=1 move=1000,-1000 snap=node thresh=-1,10
+</pre></div>
+
+Move all features defined by bounding box
+601530,4921560,602520,4922310 (W,S,E,N) 1000 map units to the
+east and 1000 map units to the north:
+
+<div class="code"><pre>
+v.edit tool=move map=roads bbox=601530,4921560,602520,4922310 move=-1000,1000
+</pre></div>
+
+<h3>Flip direction of vector lines</h3>
+
+Flip direction of all vector lines:
+
+<div class="code"><pre>
+v.edit tool=flip map=streams cats=1-9999 type=line
+</pre></div>
+
+<h3>Add / delete layer category number</h3>
+
+Add new layer/category 2/1, 2/3, 2/4, 2/5 to features covered by given polygon:
+
+<div class="code"><pre>
+v.edit tool=catadd map=roads \
+ polygon=599877.75,4925088.375,597164.812,4922524.5,601338.562,4920914.625 \
+ layer=2 cat=1,3-5
+</pre></div>
+
+Delete layer/category 1/1, line id 1:
+
+<div class="code"><pre>
+v.edit tool=catdel map=roads id=1 cats=5
+</pre></div>
+
+<h3>Merge lines</h3>
+
+Merge two lines with given category number:
+
+<div class="code"><pre>
+v.edit map=roads tool=merge cat=4
+</pre></div>
+
+<h3>Split line on given point</h3>
+
+Split line id 810 on coordinates 604268,4923570 in threshold 50 map units:
+
+<div class="code"><pre>
+v.edit map=roads tool=break coords=604268,4923570 id=810 thresh=50
+</pre></div>
+
+<h3>Break selected lines at each intersection</h3>
+
+Break selected lines (with category number 1) at each intersection:
+
+<div class="code"><pre>
+v.edit map=roads tool=break cat=1
+</pre></div>
+
+<h3>Snap lines</h3>
+
+Snap all lines using threshold distance 20 map units:
+
+<div class="code"><pre>
+v.edit map=roads id=1-9999 tool=snap thresh=-1,20 type=line
+</pre></div>
+
+<h3>Connect lines</h3>
+
+Connect line id 48 to line id 565:
+
+<div class="code"><pre>
+v.edit map=roads tool=connect id=48,565
+</pre></div>
+
+Connect line id 48 to line id 565; line id 60 to line id
+50. Maximum threshold distance is 700 map units:
+
+<div class="code"><pre>
+v.edit map=roads tool=connect id=48,565,60,50 thresh=-1,700
+</pre></div>
+
+<h3>Add vertex</h3>
+
+Add new vertex to the line located at 600952,4926107, threshold is
+set to 1 map unit:
+
+<div class="code"><pre>
+v.edit tool=vertexadd map=roads coords=600952,4926107 thresh=1
+</pre></div>
+
+<h3>Delete vertices</h3>
+
+Delete vertex located at 593191.608,4925684.849 (threshold set to 0.1 map units).
+Modify only lines with category 1:
+
+<div class="code"><pre>
+v.edit tool=vertexdel map=roads coord=593191.608,4925684.849 \
+ thresh=1-e1 cats=1
+</pre></div>
+
+<h3>Move vertices</h3>
+
+Move vertices located at 604441,4921088 (threshold set to 100 map units).
+Modify only lines with categories 1-10:
+
+<div class="code"><pre>
+v.edit tool=vertexmove map=roads cats=1-10 coord=604441,4921088 \
+ thresh=100 move=1000,1000
+</pre></div>
+
+<h3>Select features and print their id's</h3>
+
+Print id's of selected features, e.g.:
+
+<div class="code"><pre>
+v.edit map=soils at PERMANENT tool=select \
+ bbox=595733.8125,4919781.75,598536.1875,4917396.75 --q
+</pre></div>
+
+Example with <em><a href="d.vect.html">d.vect</a></em>:
+
+<div class="code"><pre>
+d.erase;
+d.vect roads;
+d.vect -i map=roads cats=`v.edit map=roads tool=select \
+ coord=592542.89243878,4924766.99622811,603389.0625,4918292.1875 \
+ thresh=1000 --q` col=red
+</pre></div>
+
+Select all lines shorter (or equal) than 10 map units:
+
+<div class="code"><pre>
+v.edit map=roads tool=select query=length thresh=-1,0,-10
+</pre></div>
+
+Select from given bounding box all lines longer then 200 map units:
+
+<div class="code"><pre>
+v.edit map=roads tool=select bbox=598260,4919730,605100,4926240 query=length thresh=-1,0,1000
+</pre></div>
+
+<h3>Fix height of contours</h3>
+
+Intput vector map contains 2D lines representing contours. Height can
+be assign to the contours using tool <b>zbulk</b>. First of all 2D
+lines need to be converted to 3D lines:
+
+<div class="code"><pre>
+v.extrude input=line2 output=line3 height=0 type=line
+</pre></div>
+
+All lines which intersect with the line given by coordinates will be
+modified. First found line will get height 1000 map units, height of
+other selected lines will be increased by 10 map units.
+
+<div class="code"><pre>
+v.edit a2 tool=zbulk bbox=586121.25049368,4911970.21547109,603092.60466035,4927071.25713776 \
+ zbulk=1000,10
+</pre></div>
+
+
+<h2>SEE ALSO</h2>
+
+<em>
+<a HREF="v.in.ascii.html">v.in.ascii</a>,
+<a HREF="v.info.html">v.info</a>,
+<a HREF="v.build.html">v.build</a>,
+<a HREF="v.clean.html">v.clean</a>,
+<a HREF="v.digit.html">v.digit</a>,
+<a HREF="v.extrude.html">v.extrude</a>
+</em>
+
+<p>
+See also <em><a href="wxGUI.Vector_Digitizing_Tool.html">wxGUI vector digitizing tool</a></em>.
+
+<h2>AUTHOR</h2>
+
+Original author: Wolf Bergenheim - independent developer<br>
+Various updates: Jachym Cepicky, Mendel University of Agriculture and Forestry in Brno, Czech Republic<br>
+Martin Landa, FBK-irst (formerly ITC-irst), Trento, Italy
+
+<p>
+<i>Last changed: $Date$</i>
Deleted: grass/trunk/vector/v.external/description.html
===================================================================
--- grass/trunk/vector/v.external/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/vector/v.external/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,88 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>v.external</em> creates new vector as a link to external
-<a href="http://www.gdal.org/ogr/">OGR</a> layer (read only).
-OGR (Simple Features Library) is part of the
-<a href="http://www.gdal.org">GDAL</a> library, so you need to
-install GDAL to use <em>v.external</em> and external OGR layers.
-<P>
-
-<h3>Supported OGR Vector Formats</h3>
-
-<a href="http://www.gdal.org/ogr/drv_shapefile.html">ESRI
-Shapefile</a><br>
-<a href="http://www.gdal.org/ogr/drv_mitab.html">Mapinfo File</a>
-
-<p>
-Further available drivers such as UK .NTF, SDTS, TIGER, IHO S-57 (ENC),
-DGN, GML, AVCBin, REC, Memory, OGDI, and PostgreSQL depend on the local
-installation (OGR library), for details see
-<a href="http://www.gdal.org/ogr/ogr_formats.html">OGR web site</a>.
-
-<h2>EXAMPLES</h2>
-
-<B>SHAPE files</B><BR>
-<div class="code"><pre>
-v.external dsn=/home/user/shape_data layer=test_shape output=grass_map
-</pre></div>
-
-<P>
-<B>MapInfo files</B><BR>
-<div class="code"><pre>
-v.external dsn=./ layer=mapinfo_test output=grass_map
-</pre></div>
-<P>
-<B>SDTS files</B> (you have to select the CATD file)<BR>
-<div class="code"><pre>
-v.external dsn=CITXCATD.DDF output=cities
-</pre></div>
-
-<P>
-<B>TIGER files</B><BR>
-<div class="code"><pre>
-v.external dsn=input/2000/56015/ layer=CompleteChain,PIP output=t56015_all
-</pre></div>
-
-<P>
-<B>PostGIS maps (area example)</B><BR>
-<div class="code"><pre>
-v.external dsn="PG:host=localhost user=postgres dbname=postgis" layer=polymap \
-output=polygons
-</pre></div>
-
-<P>
-
-<H2>NOTES</H2>
-
-The simple feature data model used by OGR is very different from
-the topological format used by GRASS. Instead of true topology,
-so called 'pseudo topology' is created for data linked by v.external.
-User should learn the difference between those to formats, because
-some modules working correctly with GRASS native data,
-can produce wrong results with input layers created by <em>v.external</em>.
-<p>
-
-See <a HREF="v.db.connect.html">v.db.connect</a> for an example of
-maintaining attributes in external DBMS in also writeable mode.
-
-<H2>REFERENCES</H2>
-
-<a href="http://www.gdal.org/ogr/">OGR vector library</a>
-<br>
-<a href="http://www.gdal.org/ogr/ogr__api_8h.html">OGR vector library C API</a>
-documentation
-
-
-<h2>SEE ALSO</h2>
-
-<em><a HREF="v.clean.html">v.clean</a></em>,
-<em><a HREF="v.db.connect.html">v.db.connect</a></em>,
-<em><a HREF="v.in.db.html">v.in.db</a></em>,
-<em><a HREF="v.in.ogr.html">v.in.ogr</a></em>,
-<em><a HREF="v.out.ogr.html">v.out.ogr</a></em>
-
-<h2>AUTHOR</h2>
-
-Radim Blazek, ITC-Irst, Trento, Italy
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/vector/v.external/v.external.html (from rev 32770, grass/trunk/vector/v.external/description.html)
===================================================================
--- grass/trunk/vector/v.external/v.external.html (rev 0)
+++ grass/trunk/vector/v.external/v.external.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,88 @@
+<h2>DESCRIPTION</h2>
+
+<em>v.external</em> creates new vector as a link to external
+<a href="http://www.gdal.org/ogr/">OGR</a> layer (read only).
+OGR (Simple Features Library) is part of the
+<a href="http://www.gdal.org">GDAL</a> library, so you need to
+install GDAL to use <em>v.external</em> and external OGR layers.
+<P>
+
+<h3>Supported OGR Vector Formats</h3>
+
+<a href="http://www.gdal.org/ogr/drv_shapefile.html">ESRI
+Shapefile</a><br>
+<a href="http://www.gdal.org/ogr/drv_mitab.html">Mapinfo File</a>
+
+<p>
+Further available drivers such as UK .NTF, SDTS, TIGER, IHO S-57 (ENC),
+DGN, GML, AVCBin, REC, Memory, OGDI, and PostgreSQL depend on the local
+installation (OGR library), for details see
+<a href="http://www.gdal.org/ogr/ogr_formats.html">OGR web site</a>.
+
+<h2>EXAMPLES</h2>
+
+<B>SHAPE files</B><BR>
+<div class="code"><pre>
+v.external dsn=/home/user/shape_data layer=test_shape output=grass_map
+</pre></div>
+
+<P>
+<B>MapInfo files</B><BR>
+<div class="code"><pre>
+v.external dsn=./ layer=mapinfo_test output=grass_map
+</pre></div>
+<P>
+<B>SDTS files</B> (you have to select the CATD file)<BR>
+<div class="code"><pre>
+v.external dsn=CITXCATD.DDF output=cities
+</pre></div>
+
+<P>
+<B>TIGER files</B><BR>
+<div class="code"><pre>
+v.external dsn=input/2000/56015/ layer=CompleteChain,PIP output=t56015_all
+</pre></div>
+
+<P>
+<B>PostGIS maps (area example)</B><BR>
+<div class="code"><pre>
+v.external dsn="PG:host=localhost user=postgres dbname=postgis" layer=polymap \
+output=polygons
+</pre></div>
+
+<P>
+
+<H2>NOTES</H2>
+
+The simple feature data model used by OGR is very different from
+the topological format used by GRASS. Instead of true topology,
+so called 'pseudo topology' is created for data linked by v.external.
+User should learn the difference between those to formats, because
+some modules working correctly with GRASS native data,
+can produce wrong results with input layers created by <em>v.external</em>.
+<p>
+
+See <a HREF="v.db.connect.html">v.db.connect</a> for an example of
+maintaining attributes in external DBMS in also writeable mode.
+
+<H2>REFERENCES</H2>
+
+<a href="http://www.gdal.org/ogr/">OGR vector library</a>
+<br>
+<a href="http://www.gdal.org/ogr/ogr__api_8h.html">OGR vector library C API</a>
+documentation
+
+
+<h2>SEE ALSO</h2>
+
+<em><a HREF="v.clean.html">v.clean</a></em>,
+<em><a HREF="v.db.connect.html">v.db.connect</a></em>,
+<em><a HREF="v.in.db.html">v.in.db</a></em>,
+<em><a HREF="v.in.ogr.html">v.in.ogr</a></em>,
+<em><a HREF="v.out.ogr.html">v.out.ogr</a></em>
+
+<h2>AUTHOR</h2>
+
+Radim Blazek, ITC-Irst, Trento, Italy
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/vector/v.extract/description.html
===================================================================
--- grass/trunk/vector/v.extract/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/vector/v.extract/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,129 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>v.extract</em> allows a user to select vector objects from an existing
-vector map and creates a new map containing only the selected objects.
-Database tables can be queried with SQL statements, if a connection is
-established.
-Dissolving (optional) is based on the output categories. If 2 adjacent
-areas have the same output category, the boundary is removed.
-
-<p>
-If <b>list</b>, <b>file</b> and <b>where</b> options are not
-specified, all features of given type and layer are
-extracted. Categories are not changed in that case.
-
-<h2>NOTES</h2>
-
-Only features with a category number will be extracted. So if you want to
-extract boundaries (which are usually without category, as that information
-is normally held in the area's centroid) you must first use
-<em><a HREF="v.category.html">v.category</a></em> to add them.
-
-<h2>EXAMPLES</h2>
-
-<h3>Extract areas by category number with dissolving #1:</h3>
-<div class="code"><pre>
-v.extract -d list=1,2,3,4 input=soils output=soil_groupa type=area new=0
-</pre></div>
-
-<p>
-produces a new vector <b>soil_groupa</b>, containing those areas from vector
-<b>soils</b> which have category numbers <b>1 thru 4</b>; any common boundaries are
-dissolved, and all areas in the new map will be assigned category number 0.
-
-<h3>Extract areas by category number with dissolving #2:</h3>
-<div class="code"><pre>
-v.extract -d list=1-4 input=soils output=soil_groupa type=area new=-1
-</pre></div>
-<p>
-produces a new vector map <b>soil_groupa</b> containing the areas from vector
-<b>soils</b> which have categories <b>1 thru 4</b>. Any common boundaries are
-dissolved, all areas in the new map will retain their original category
-numbers 1 thru 4, since <b>new</b> was set to -1.
-
-<h3>Extract all areas and assign the same category to all:</h3>
-<div class="code"><pre>
-v.extract input=soils output=soil_groupa type=area new=1
-</pre></div>
-<p>
-
-produces a new vector map <b>soil_groupa</b> containing all areas from
-<b>soils</b>. No common boundaries are dissolved, all areas of the new
-map will be assigned category number 1.
-
-<h3>Extract vectors with SQL:</h3>
-<div class="code"><pre>
-v.extract input=markveggy.shp output=markveggy.1 new=13 where="(VEGTYPE = 'Wi') or (VEGTYPE = 'PS') or (PRIME_TYPE='Wi')"
-</pre></div>
-<p>
-
-produces a new vector map with category number 13 if the SQL statement is
-fulfilled.
-
-<h3>Extract vector features which have the given field empty:</h3>
-<div class="code"><pre>
-v.extract input=forest output=forest_gaps where="CANOPY is NULL"
-</pre></div>
-
-<h3>Extract vector features which have the given field not empty:</h3>
-<div class="code"><pre>
-v.extract input=forest output=forest_canopy where="CANOPY not NULL"
-</pre></div>
-
-<h3>Reverse extracting (behaves like selective vector objects deleting):</h3>
-
-Remove unreferenced stations from the GlobalSOD database:
-<div class="code"><pre>
-# check what to delete:
-v.db.select gsod_stationlist where="latitude < -91"
-
-# perform reverse selection
-v.extract -r gsod_stationlist out=gsod_stationlist_clean where="latitude < -91"
-
-v.db.select gsod_stationlist_clean
-</pre></div>
-
-
-<h3>Dissolving based on column attributes:</h3>
-<div class="code"><pre>
-# check column names:
-v.info -c polbnda_italy
-
-# reclass based on desired column:
-v.reclass polbnda_italy out=polbnda_italy_recl_nam col=vmap_nam
-
-# verify:
-v.info -c polbnda_italy_recl_nam
-v.db.select polbnda_italy_recl_nam
-
-# dissolve:
-v.extract -d polbnda_italy_recl_nam out=pol_italy_regions
-</pre></div>
-<p>
-
-produces a new vector map with common boundaries dissolved where the reclassed
-attributes of adjacent (left/right) areas are identical.
-
-<h3>Remove islands from polygon map</h3>
-<div class="code"><pre>
-v.extract in=map_with_islands out=maps_without_islands list=1-99999
-# and/or
-v.extract -d in=map_with_islands out=maps_without_islands
-</pre></div>
-
-<h2>SEE ALSO</h2>
-
-<em>
-<a HREF="v.category.html">v.category</a>,
-<a HREF="v.dissolve.html">v.dissolve</a>,
-<a HREF="v.reclass.html">v.reclass</a>,
-<a HREF="sql.html">GRASS SQL interface</a>
-</em>
-
-<h2>AUTHORS</h2>
-
-R.L. Glenn, USDA, SCS, NHQ-CGIS<br>
-GRASS 6 port by Radim Blazek
-
-<p>
-<i>Last changed: $Date$</i>
Copied: grass/trunk/vector/v.extract/v.extract.html (from rev 32770, grass/trunk/vector/v.extract/description.html)
===================================================================
--- grass/trunk/vector/v.extract/v.extract.html (rev 0)
+++ grass/trunk/vector/v.extract/v.extract.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,129 @@
+<h2>DESCRIPTION</h2>
+
+<em>v.extract</em> allows a user to select vector objects from an existing
+vector map and creates a new map containing only the selected objects.
+Database tables can be queried with SQL statements, if a connection is
+established.
+Dissolving (optional) is based on the output categories. If 2 adjacent
+areas have the same output category, the boundary is removed.
+
+<p>
+If <b>list</b>, <b>file</b> and <b>where</b> options are not
+specified, all features of given type and layer are
+extracted. Categories are not changed in that case.
+
+<h2>NOTES</h2>
+
+Only features with a category number will be extracted. So if you want to
+extract boundaries (which are usually without category, as that information
+is normally held in the area's centroid) you must first use
+<em><a HREF="v.category.html">v.category</a></em> to add them.
+
+<h2>EXAMPLES</h2>
+
+<h3>Extract areas by category number with dissolving #1:</h3>
+<div class="code"><pre>
+v.extract -d list=1,2,3,4 input=soils output=soil_groupa type=area new=0
+</pre></div>
+
+<p>
+produces a new vector <b>soil_groupa</b>, containing those areas from vector
+<b>soils</b> which have category numbers <b>1 thru 4</b>; any common boundaries are
+dissolved, and all areas in the new map will be assigned category number 0.
+
+<h3>Extract areas by category number with dissolving #2:</h3>
+<div class="code"><pre>
+v.extract -d list=1-4 input=soils output=soil_groupa type=area new=-1
+</pre></div>
+<p>
+produces a new vector map <b>soil_groupa</b> containing the areas from vector
+<b>soils</b> which have categories <b>1 thru 4</b>. Any common boundaries are
+dissolved, all areas in the new map will retain their original category
+numbers 1 thru 4, since <b>new</b> was set to -1.
+
+<h3>Extract all areas and assign the same category to all:</h3>
+<div class="code"><pre>
+v.extract input=soils output=soil_groupa type=area new=1
+</pre></div>
+<p>
+
+produces a new vector map <b>soil_groupa</b> containing all areas from
+<b>soils</b>. No common boundaries are dissolved, all areas of the new
+map will be assigned category number 1.
+
+<h3>Extract vectors with SQL:</h3>
+<div class="code"><pre>
+v.extract input=markveggy.shp output=markveggy.1 new=13 where="(VEGTYPE = 'Wi') or (VEGTYPE = 'PS') or (PRIME_TYPE='Wi')"
+</pre></div>
+<p>
+
+produces a new vector map with category number 13 if the SQL statement is
+fulfilled.
+
+<h3>Extract vector features which have the given field empty:</h3>
+<div class="code"><pre>
+v.extract input=forest output=forest_gaps where="CANOPY is NULL"
+</pre></div>
+
+<h3>Extract vector features which have the given field not empty:</h3>
+<div class="code"><pre>
+v.extract input=forest output=forest_canopy where="CANOPY not NULL"
+</pre></div>
+
+<h3>Reverse extracting (behaves like selective vector objects deleting):</h3>
+
+Remove unreferenced stations from the GlobalSOD database:
+<div class="code"><pre>
+# check what to delete:
+v.db.select gsod_stationlist where="latitude < -91"
+
+# perform reverse selection
+v.extract -r gsod_stationlist out=gsod_stationlist_clean where="latitude < -91"
+
+v.db.select gsod_stationlist_clean
+</pre></div>
+
+
+<h3>Dissolving based on column attributes:</h3>
+<div class="code"><pre>
+# check column names:
+v.info -c polbnda_italy
+
+# reclass based on desired column:
+v.reclass polbnda_italy out=polbnda_italy_recl_nam col=vmap_nam
+
+# verify:
+v.info -c polbnda_italy_recl_nam
+v.db.select polbnda_italy_recl_nam
+
+# dissolve:
+v.extract -d polbnda_italy_recl_nam out=pol_italy_regions
+</pre></div>
+<p>
+
+produces a new vector map with common boundaries dissolved where the reclassed
+attributes of adjacent (left/right) areas are identical.
+
+<h3>Remove islands from polygon map</h3>
+<div class="code"><pre>
+v.extract in=map_with_islands out=maps_without_islands list=1-99999
+# and/or
+v.extract -d in=map_with_islands out=maps_without_islands
+</pre></div>
+
+<h2>SEE ALSO</h2>
+
+<em>
+<a HREF="v.category.html">v.category</a>,
+<a HREF="v.dissolve.html">v.dissolve</a>,
+<a HREF="v.reclass.html">v.reclass</a>,
+<a HREF="sql.html">GRASS SQL interface</a>
+</em>
+
+<h2>AUTHORS</h2>
+
+R.L. Glenn, USDA, SCS, NHQ-CGIS<br>
+GRASS 6 port by Radim Blazek
+
+<p>
+<i>Last changed: $Date$</i>
Deleted: grass/trunk/vector/v.extrude/description.html
===================================================================
--- grass/trunk/vector/v.extrude/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/vector/v.extrude/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,46 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<p>
-<em>v.extrude</em> creates faces, kernels, volumes or 3D lines based
-on 2D vector objects, i.e. points become 3D vertical lines, lines to
-3D lines, boundaries to faces and areas to volumes (composition of
-faces and kernel).
-
-<p>
-If the flag <b>-t</b> is used then 3D vector objects follow the
-elevation model by using individual elevation values for the vertices
-and nodes. This can be useful for models of large objects (forest
-stands).
-
-<h2>EXAMPLES</h2>
-
-<h3>3D houses with fixed height</h3>
-
-<div class="code"><pre>
-v.extrude input=houses output=houses3D height=5 type=area
-</pre></div>
-
-<h3>3D houses with individual height</h3>
-
-<div class="code"><pre>
-v.extrude input=houses output=houses3D elevation=dem hcolumn=height type=area
-</pre></div>
-
-<h3>Convert 2D lines to 3D with fixed height</h3>
-<div class="code"><pre>
-v.extrude input=lines output=lines3D elevation=dem height=0 type=line
-</pre></div>
-
-<h2>SEE ALSO</h2>
-
-<em>
-<a href="nviz.html">nviz</a>
-</em>
-
-<h2>AUTHOR</h2>
-
-Jachym Cepicky,<br>
-Updated by Martin Landa, FBK-irst, Italy
-
-<p>
-<i>Last changed: $Date$</i>
Copied: grass/trunk/vector/v.extrude/v.extrude.html (from rev 32770, grass/trunk/vector/v.extrude/description.html)
===================================================================
--- grass/trunk/vector/v.extrude/v.extrude.html (rev 0)
+++ grass/trunk/vector/v.extrude/v.extrude.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,46 @@
+<h2>DESCRIPTION</h2>
+
+<p>
+<em>v.extrude</em> creates faces, kernels, volumes or 3D lines based
+on 2D vector objects, i.e. points become 3D vertical lines, lines to
+3D lines, boundaries to faces and areas to volumes (composition of
+faces and kernel).
+
+<p>
+If the flag <b>-t</b> is used then 3D vector objects follow the
+elevation model by using individual elevation values for the vertices
+and nodes. This can be useful for models of large objects (forest
+stands).
+
+<h2>EXAMPLES</h2>
+
+<h3>3D houses with fixed height</h3>
+
+<div class="code"><pre>
+v.extrude input=houses output=houses3D height=5 type=area
+</pre></div>
+
+<h3>3D houses with individual height</h3>
+
+<div class="code"><pre>
+v.extrude input=houses output=houses3D elevation=dem hcolumn=height type=area
+</pre></div>
+
+<h3>Convert 2D lines to 3D with fixed height</h3>
+<div class="code"><pre>
+v.extrude input=lines output=lines3D elevation=dem height=0 type=line
+</pre></div>
+
+<h2>SEE ALSO</h2>
+
+<em>
+<a href="nviz.html">nviz</a>
+</em>
+
+<h2>AUTHOR</h2>
+
+Jachym Cepicky,<br>
+Updated by Martin Landa, FBK-irst, Italy
+
+<p>
+<i>Last changed: $Date$</i>
Deleted: grass/trunk/vector/v.generalize/description.html
===================================================================
--- grass/trunk/vector/v.generalize/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/vector/v.generalize/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,249 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-<EM>v.generalize</EM>
-is module for generalization of GRASS vector maps. This module
-comprises a bunch of algortihms for line simplification, line smoothing,
-network generalization and displacemet. (New methods may be added later)
-Also, this document contains only the descriptions of module and implemented
-methods. For more examples and nice pictures, check
-<EM><A HREF="http://users.ox.ac.uk/~orie1848/tutorial.html">tutorial</A><BR></EM>
-
-<H2>NOTES</H2>
-(Line) simplification is a process of reducing the compexity of vector features.
-It transforms a line into another line which consists of fewer vertices but
-still approximates the original line. The most of the algorithms described below
-selects a subset of points of the original line.
-
-<P>
-On the other hand, (line) smoothing is a "reverse" process which takes as an
-input a line and produces smoother line which approximates the original line.
-In some cases, this is achieved by inserting new vertices into the line.
-Sometimes, the increase of the number of vertices is dramatical (4000%).
-When this situation occurs, it is always a good idea to simplify the line after
-smoothing.
-</P>
-
-<P>
-Smoothing and simplification algorithms implemented in this module work line by
-line. i.e simplification/smoothing of one line does not affect the other lines.
-They are treated separately. Also, the first and the last point of each line is
-never translated and/or deleted.
-</P>
-
-<H2>SIMPLIFICATION</H2>
-<P>
-<EM>v.generalize</EM> contains following line simplification algorithms
-<UL>
-<LI>Douglas-Peucker Algorithm</LI>
-<LI>"Douglas-Peucker Reduction Algorithm"</LI>
-<LI>Lang Algorithm</LI>
-<LI>Vertex Reduction</LI>
-<LI>Reumann-Witkam Algorithm</LI>
-<LI>Remove Small Lines/Areas</LI>
-</UL>
-
-Different algorithms require different parameters, but all the algorithms have
-one parameter in common. It is <B>threshold</B> parameter. In general, the degree
-of simplification increases with the increasing value of <B>threshold</B>.<BR>
-
-The following happens if <B>r</B> flag is presented.
-If some line is simplified and hence becomes shorter than <B>threshold</B> then it is
-removed. Also, if <B>type</B> contains <B>area</B> and a simplification algorithm is selected,
-the areas of area less than <B>threshold</B> are also removed.
-
-<H2>DETAIL DESCRIPTION</H2>
-<UL>
-<LI> <I>Douglas-Peucker</I> - "Quicksort" of line simplification, the most widely used
- algorithm. Input parameters: <B>input</B>, <B>threshold</B>. For more
- information, please check: <A href="http://geometryalgorithms.com/Archive/algorithm_0205/algorithm_0205.htm">http://geometryalgorithms.com/Archive/algorithm_0205/algorithm_0205.htm</A>.</LI>
-<LI> <I>Douglas-Peucker Reduction Algorithm</I> is essentially the same algorithm as the
- algorithm above. The difference is that it takes additional parameter <B>reduction</B>
- which denotes the percentage of the number of points on the new line with respect
- to the number of points on the original line. Input parameters: <B>input</B>,
- <B>threshold</B>, <B>reduction</B>.</LI>
-<LI> <I>Lang</I> - Another standard algorithm. Input parameters: <B>input</B>, <B>threshold</B>, <B>look_ahead</B>.
- For an excellent description, check: <A href="http://www.sli.unimelb.edu.au/gisweb/LGmodule/LGLangVisualisation.htm">http://www.sli.unimelb.edu.au/gisweb/LGmodule/LGLangVisualisation.htm</A>.</LI>
-<LI> <I>Vertex Reduction</I> - Simplest among the algorithms. Input parameters: <B>input</B>, <B>threshold</B>.
- Given line, this algorithm removes the points of this line which are closer to each other than <B>threshold</B>.
- Precisely, if p1 and p2 are two consecutive points and distance between p2 and p1 is less
- than <B>threshold</B>, it removes p2 and repeats the same
- process on the remaining points.</LI>
-<LI> <I>Reuman-Witkam</I> - Input parameters: <B>input</B>, <B>threshold</B>. This algorithm quite
- reasonably preserves the global characteristics of the lines. For more information
- check <A href="http://www.ifp.uni-stuttgart.de/lehre/vorlesungen/GIS1/Lernmodule/Lg/LG_de_6.html">http://www.ifp.uni-stuttgart.de/lehre/vorlesungen/GIS1/Lernmodule/Lg/LG_de_6.html</A>(german)</LI>
-<LI> <I>Remove Small Lines/Areas</I> - removes the lines (strictly) shorter than threshold and areas of area (strictly)less than threshold.
- Other lines/areas/boundaries are left unchanged. Input parameters: <B>input</B>, <B>threshold</B>
-</UL>
-
-<P>
-<I>Douglas-Peucker</I> and <I>Douglas-Peucker Reduction Algorithm</I> use the same method
-to simplify the lines. Note that
-<DIV class="code"><PRE>
-v.generalize input=in output=out method=douglas threshold=eps
-</PRE></DIV>
-is equivalent to
-<DIV class="code"><PRE>
-v.generalize input=in output=out method=douglas_reduction threshold=eps reduction=100
-</PRE></DIV>
-However, in this case, the first method is faster. Also observe that
-<I>douglas_reduction</I> never outputs more vertices than <I>douglas</I>. And that,
-in general, <I>douglas</I> is more efficient than <I>douglas_reduction</I>.
-More importantly, the effect of
-<DIV class="code"><PRE>
-v.generalize input=in output=out method=douglas_reduction threshold=0 reduction=X
-</PRE></DIV>
-is that 'out' contains approximately only X% of points of 'in'.
-</P>
-
-<H2>SMOOTHING</H2>
-<P>
-The following smoothing algorithms are implemented in <EM>v.generalize</EM>
-</P>
-<UL>
-<LI><I>Boyle's Forward-Looking Algorithm</I> - The position of each point depends on the
- position of the previous points and the point <B>look_ahead</B> ahead.
- <B>look_ahead</B> consecutive points. Input parameters: <B>input</B>, <B>look_ahead</B>.</LI>
-<LI><I>McMaster's Sliding Averaging Algorithm</I> - Input Parameters: <B>input</B>, <B>slide</B>, <B>look_ahead</B>.
- The new position of each point is the average of the <B>look_ahead</B> points around. Paremeter <B>slide</B>
- is used for linear interpolation between old and new position (see below).</LI>
-<LI><I>McMaster's Distance-Weighting Algorithm</I> - Works by taking the weighted average of <B>look_ahead</B> consecutive points
- where the weight is the reciprocal of the distance from the point to the currently smoothed point. And parameter <B>slide</B> is used
- for linear interpolation between the original position of the point and newly computed position where value 0 means the original position.
- Input parameters: <B>input</B>, <B>slide</B>, <B>look_ahead</B>.
- </LI>
-<LI><I>Chaiken's Algorithm</I> - "Inscribes" a line touching the original line such that the points on this new line
- are at least <I>threshold</I> apart. Input parameters: <B>input</B>, <B>threshold</B>. This algorithm
- approximates given line very well.</LI>
-<LI> <I>Hermite Interpolation</I> - This algorithm takes the points of the given line as the control
- points of hermite cubic spline and approximates this spline by the points approximatelly <B>threshold</B> apart.
- This method has excellent results for the small values of <B>threshold</B>, but in this case it produces
- a huge number of new points and some simplification is usually needed. Input parameters: <B>input</B>, <B>threshold</B>, <B>angle_thresh</B>.
- <B>Angle_thresh</B> is used for reducing the number of the outputed points. It denotes the minimal
- angle (in degrees) between two consecutive segements of line.</LI>
-<LI> <I>Snakes</I> is the method of minimization of the "energy" of the line. This method preserves the
- general characteristcs of the lines but smooths the "sharp corners" of the line. Input parameters <B>input</B>, <B>alpha</B>, <B>beta</B>.
- This algorithm works very well for small values of <B>alpha</B> and <B>beta</B> (between 0 and 5). These
- parameters affects the "sharpness" and the curvature of the computed line.</LI>
-</UL>
-<P>
-One of the key advantages of <I>Hermite Interpolation</I> is the fact that the computed line
-always passes throught the points of the original line whereas the lines produced by the
-remaining algorithms never pass through these points. In some sense, this algorithm outputs
-the line which "circumsrcibes" given line. On the other hand, <I>Chaiken's Algorithm</I> outputs
-the line which "inscribes" given line. Moreover this line always touches/intersects the centre
-of the line segment between two consecutive points. For more iterations, the property above does
-not hold, but the computed lines are very similar to the Bezier Splines. The disadvantage of these
-two algorithm is that they increase the number of points. However, <I>Hermite Interpolation</I> can be used
-as another simplification algorithm. To achieve this, it is necessary to set <I>angle_thresh</I> to higher values (15 or so).
-</P>
-<P>
-One restriction on both McMasters' Algorithms is that <I>look_ahead</I> parameter must be odd. Also
-note that these algorithms have no effect if <I>look_ahead = 1</I>.
-</P>
-<P>
-Note that <I>Boyle's</I>, <I>McMasters'</I> and <I>Snakes</I> algorithm are sometime used in the signal processing to smooth the signals.
-More importantly, these algorithms never change the number of points on the lines. i.e they only
-translate the points, they do not insert any new points.
-</P>
-<P>
-<I>Snakes</I> Algorithm is (asymptotically) the slowest among the algorithms presented above. Also,
-it requires quite a lot of memory. This means, that it is not very efficient
-for maps with the lines consisting of many segments.
-</P>
-
-<H2>DISPLACEMENT</H2>
-<P>
-The displacement is used when the lines (linear
-features) interact (overlap and/or are close to each other) at the current
-level of detail. In general, displacement methods, as name suggests, move the
-conflicting features apart so that they do not interact and can be distinguished.
-</P>
-<P>
-This module implements algorithm for displacement of linear features based on
-the <I>Snakes</I> approach. This method has very good results. However, it
-requires a lot of memory and is not very efficient.
-</P>
-<P>
-Displacement is selected by method=displacement. It uses following parameters:
-</P>
-<UL>
-<LI>
-<B>threshold</B> - specifies critical distance. Two features interact iff they are
-closer than <B>threshold</B> appart.
-</LI>
-<LI>
-<B>alpha</B>, <B>beta</B> - These parameters define the rigidity of lines. For greater
-values of <B>alpha</B>, <B>beta</B> (>=1), the algorithm better preserves the original
-shape of the lines. On the other hand, the lines may not
-be move enough. If the values of <B>alpha</B>, <B>beta</B> are too small (<=0.001)
-then the lines are moved sufficiently, but the geometry and topology of lines can
-be destroyed. Probably, the best way to find the good values of <B>alpha</B>, <B>beta</B>
-is by trial and error.
-</LI>
-<LI>
-<B>iterations</B> - denotes the number of iterations the interactions between
-the lines are resolved. Mostly, good values of <B>iterations</B> lies
-between 10 and 100.
-</LI>
-</UL>
-<P>
-The lines affected by the algorithm can be specified by the <B>layer</B>,
-<B>cats</B> and <B>where</B> parameters.
-</P>
-<!-- TODO: example(s) -->
-
-<H2>NETWORK GENERALIZATION</H2>
-<P>
-Is used for selecting "the most important" part of the network. This is based
-on the graph algorithms. Network generalization is applied if method=network.
-The algorithm calculates three centrality measures for each line in the
-network and only the lines with the values greater than thresholds are selected.
-The behaviour of algorithm can be altered by the following parameters:
-</P>
-
-<UL>
-<LI>
-<B>degree_thresh</B> - algorithm selects only the lines which share a point
-with at least <B>degree_thresh</B> different lines.
-</LI>
-<LI>
-<B>closeness_thresh</B> - is always in the range (0, 1]. Only the lines with
-the closeness centrality measure at least <B>closeness_thresh</B> are selcted.
-The lines in the centre of a network have greater values of this measure then
-the lines near the border of a network. This means,
-that this parameters can be used for selecting the centre(s) of a network. Note that
-if closeness_thresh=0 then everything is selected.
-</LI>
-<LI>
-<B>betweeness_thresh</B> - Again, only the lines with betweeness centrality
-measure at least <B>betweeness_thresh</B> are selected. This value is always
-positive and is larger for large networks. It denotes to what extent a line
-is in between the other lines in the network. This value is great for the lines
-which lie between other lines and lie on the paths between two parts of a network.
-In the terminology of the road neworks, these are highways, bypasses, main roads/streets....
-</LI>
-</UL>
-<P>
-All three parameters above can be presented at the same time. In that case,
-the algorithm selects only the lines which meet each criterion.
-</P>
-<P>
-Also, the outputed network may not be connected if the value of <B>betweeness_thresh</B>
-is too large.
-</P>
-<!-- TODO: example(s) -->
-<H2>SEE ALSO</H2>
-<EM><A HREF="http://users.ox.ac.uk/~orie1848/tutorial.html">v.generalize Tutorial</A><BR></EM>
-<EM><A HREF="v.clean.html">v.clean</A><BR></EM>
-<EM><A HREF="v.dissolve.html">v.dissolve</A><BR></EM>
-<BR><BR>
-
-
-<H2>AUTHORS</H2>
-Daniel Bundala, Google Summer of Code 2007, Student
-<BR>
-Wolf Bergenheim, Mentor
-
-<!-- TODO: references -->
-
-<P><I>Last changed: $Date$</I>
Copied: grass/trunk/vector/v.generalize/v.generalize.html (from rev 32770, grass/trunk/vector/v.generalize/description.html)
===================================================================
--- grass/trunk/vector/v.generalize/v.generalize.html (rev 0)
+++ grass/trunk/vector/v.generalize/v.generalize.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,249 @@
+<H2>DESCRIPTION</H2>
+
+<EM>v.generalize</EM>
+is module for generalization of GRASS vector maps. This module
+comprises a bunch of algortihms for line simplification, line smoothing,
+network generalization and displacemet. (New methods may be added later)
+Also, this document contains only the descriptions of module and implemented
+methods. For more examples and nice pictures, check
+<EM><A HREF="http://users.ox.ac.uk/~orie1848/tutorial.html">tutorial</A><BR></EM>
+
+<H2>NOTES</H2>
+(Line) simplification is a process of reducing the compexity of vector features.
+It transforms a line into another line which consists of fewer vertices but
+still approximates the original line. The most of the algorithms described below
+selects a subset of points of the original line.
+
+<P>
+On the other hand, (line) smoothing is a "reverse" process which takes as an
+input a line and produces smoother line which approximates the original line.
+In some cases, this is achieved by inserting new vertices into the line.
+Sometimes, the increase of the number of vertices is dramatical (4000%).
+When this situation occurs, it is always a good idea to simplify the line after
+smoothing.
+</P>
+
+<P>
+Smoothing and simplification algorithms implemented in this module work line by
+line. i.e simplification/smoothing of one line does not affect the other lines.
+They are treated separately. Also, the first and the last point of each line is
+never translated and/or deleted.
+</P>
+
+<H2>SIMPLIFICATION</H2>
+<P>
+<EM>v.generalize</EM> contains following line simplification algorithms
+<UL>
+<LI>Douglas-Peucker Algorithm</LI>
+<LI>"Douglas-Peucker Reduction Algorithm"</LI>
+<LI>Lang Algorithm</LI>
+<LI>Vertex Reduction</LI>
+<LI>Reumann-Witkam Algorithm</LI>
+<LI>Remove Small Lines/Areas</LI>
+</UL>
+
+Different algorithms require different parameters, but all the algorithms have
+one parameter in common. It is <B>threshold</B> parameter. In general, the degree
+of simplification increases with the increasing value of <B>threshold</B>.<BR>
+
+The following happens if <B>r</B> flag is presented.
+If some line is simplified and hence becomes shorter than <B>threshold</B> then it is
+removed. Also, if <B>type</B> contains <B>area</B> and a simplification algorithm is selected,
+the areas of area less than <B>threshold</B> are also removed.
+
+<H2>DETAIL DESCRIPTION</H2>
+<UL>
+<LI> <I>Douglas-Peucker</I> - "Quicksort" of line simplification, the most widely used
+ algorithm. Input parameters: <B>input</B>, <B>threshold</B>. For more
+ information, please check: <A href="http://geometryalgorithms.com/Archive/algorithm_0205/algorithm_0205.htm">http://geometryalgorithms.com/Archive/algorithm_0205/algorithm_0205.htm</A>.</LI>
+<LI> <I>Douglas-Peucker Reduction Algorithm</I> is essentially the same algorithm as the
+ algorithm above. The difference is that it takes additional parameter <B>reduction</B>
+ which denotes the percentage of the number of points on the new line with respect
+ to the number of points on the original line. Input parameters: <B>input</B>,
+ <B>threshold</B>, <B>reduction</B>.</LI>
+<LI> <I>Lang</I> - Another standard algorithm. Input parameters: <B>input</B>, <B>threshold</B>, <B>look_ahead</B>.
+ For an excellent description, check: <A href="http://www.sli.unimelb.edu.au/gisweb/LGmodule/LGLangVisualisation.htm">http://www.sli.unimelb.edu.au/gisweb/LGmodule/LGLangVisualisation.htm</A>.</LI>
+<LI> <I>Vertex Reduction</I> - Simplest among the algorithms. Input parameters: <B>input</B>, <B>threshold</B>.
+ Given line, this algorithm removes the points of this line which are closer to each other than <B>threshold</B>.
+ Precisely, if p1 and p2 are two consecutive points and distance between p2 and p1 is less
+ than <B>threshold</B>, it removes p2 and repeats the same
+ process on the remaining points.</LI>
+<LI> <I>Reuman-Witkam</I> - Input parameters: <B>input</B>, <B>threshold</B>. This algorithm quite
+ reasonably preserves the global characteristics of the lines. For more information
+ check <A href="http://www.ifp.uni-stuttgart.de/lehre/vorlesungen/GIS1/Lernmodule/Lg/LG_de_6.html">http://www.ifp.uni-stuttgart.de/lehre/vorlesungen/GIS1/Lernmodule/Lg/LG_de_6.html</A>(german)</LI>
+<LI> <I>Remove Small Lines/Areas</I> - removes the lines (strictly) shorter than threshold and areas of area (strictly)less than threshold.
+ Other lines/areas/boundaries are left unchanged. Input parameters: <B>input</B>, <B>threshold</B>
+</UL>
+
+<P>
+<I>Douglas-Peucker</I> and <I>Douglas-Peucker Reduction Algorithm</I> use the same method
+to simplify the lines. Note that
+<DIV class="code"><PRE>
+v.generalize input=in output=out method=douglas threshold=eps
+</PRE></DIV>
+is equivalent to
+<DIV class="code"><PRE>
+v.generalize input=in output=out method=douglas_reduction threshold=eps reduction=100
+</PRE></DIV>
+However, in this case, the first method is faster. Also observe that
+<I>douglas_reduction</I> never outputs more vertices than <I>douglas</I>. And that,
+in general, <I>douglas</I> is more efficient than <I>douglas_reduction</I>.
+More importantly, the effect of
+<DIV class="code"><PRE>
+v.generalize input=in output=out method=douglas_reduction threshold=0 reduction=X
+</PRE></DIV>
+is that 'out' contains approximately only X% of points of 'in'.
+</P>
+
+<H2>SMOOTHING</H2>
+<P>
+The following smoothing algorithms are implemented in <EM>v.generalize</EM>
+</P>
+<UL>
+<LI><I>Boyle's Forward-Looking Algorithm</I> - The position of each point depends on the
+ position of the previous points and the point <B>look_ahead</B> ahead.
+ <B>look_ahead</B> consecutive points. Input parameters: <B>input</B>, <B>look_ahead</B>.</LI>
+<LI><I>McMaster's Sliding Averaging Algorithm</I> - Input Parameters: <B>input</B>, <B>slide</B>, <B>look_ahead</B>.
+ The new position of each point is the average of the <B>look_ahead</B> points around. Paremeter <B>slide</B>
+ is used for linear interpolation between old and new position (see below).</LI>
+<LI><I>McMaster's Distance-Weighting Algorithm</I> - Works by taking the weighted average of <B>look_ahead</B> consecutive points
+ where the weight is the reciprocal of the distance from the point to the currently smoothed point. And parameter <B>slide</B> is used
+ for linear interpolation between the original position of the point and newly computed position where value 0 means the original position.
+ Input parameters: <B>input</B>, <B>slide</B>, <B>look_ahead</B>.
+ </LI>
+<LI><I>Chaiken's Algorithm</I> - "Inscribes" a line touching the original line such that the points on this new line
+ are at least <I>threshold</I> apart. Input parameters: <B>input</B>, <B>threshold</B>. This algorithm
+ approximates given line very well.</LI>
+<LI> <I>Hermite Interpolation</I> - This algorithm takes the points of the given line as the control
+ points of hermite cubic spline and approximates this spline by the points approximatelly <B>threshold</B> apart.
+ This method has excellent results for the small values of <B>threshold</B>, but in this case it produces
+ a huge number of new points and some simplification is usually needed. Input parameters: <B>input</B>, <B>threshold</B>, <B>angle_thresh</B>.
+ <B>Angle_thresh</B> is used for reducing the number of the outputed points. It denotes the minimal
+ angle (in degrees) between two consecutive segements of line.</LI>
+<LI> <I>Snakes</I> is the method of minimization of the "energy" of the line. This method preserves the
+ general characteristcs of the lines but smooths the "sharp corners" of the line. Input parameters <B>input</B>, <B>alpha</B>, <B>beta</B>.
+ This algorithm works very well for small values of <B>alpha</B> and <B>beta</B> (between 0 and 5). These
+ parameters affects the "sharpness" and the curvature of the computed line.</LI>
+</UL>
+<P>
+One of the key advantages of <I>Hermite Interpolation</I> is the fact that the computed line
+always passes throught the points of the original line whereas the lines produced by the
+remaining algorithms never pass through these points. In some sense, this algorithm outputs
+the line which "circumsrcibes" given line. On the other hand, <I>Chaiken's Algorithm</I> outputs
+the line which "inscribes" given line. Moreover this line always touches/intersects the centre
+of the line segment between two consecutive points. For more iterations, the property above does
+not hold, but the computed lines are very similar to the Bezier Splines. The disadvantage of these
+two algorithm is that they increase the number of points. However, <I>Hermite Interpolation</I> can be used
+as another simplification algorithm. To achieve this, it is necessary to set <I>angle_thresh</I> to higher values (15 or so).
+</P>
+<P>
+One restriction on both McMasters' Algorithms is that <I>look_ahead</I> parameter must be odd. Also
+note that these algorithms have no effect if <I>look_ahead = 1</I>.
+</P>
+<P>
+Note that <I>Boyle's</I>, <I>McMasters'</I> and <I>Snakes</I> algorithm are sometime used in the signal processing to smooth the signals.
+More importantly, these algorithms never change the number of points on the lines. i.e they only
+translate the points, they do not insert any new points.
+</P>
+<P>
+<I>Snakes</I> Algorithm is (asymptotically) the slowest among the algorithms presented above. Also,
+it requires quite a lot of memory. This means, that it is not very efficient
+for maps with the lines consisting of many segments.
+</P>
+
+<H2>DISPLACEMENT</H2>
+<P>
+The displacement is used when the lines (linear
+features) interact (overlap and/or are close to each other) at the current
+level of detail. In general, displacement methods, as name suggests, move the
+conflicting features apart so that they do not interact and can be distinguished.
+</P>
+<P>
+This module implements algorithm for displacement of linear features based on
+the <I>Snakes</I> approach. This method has very good results. However, it
+requires a lot of memory and is not very efficient.
+</P>
+<P>
+Displacement is selected by method=displacement. It uses following parameters:
+</P>
+<UL>
+<LI>
+<B>threshold</B> - specifies critical distance. Two features interact iff they are
+closer than <B>threshold</B> appart.
+</LI>
+<LI>
+<B>alpha</B>, <B>beta</B> - These parameters define the rigidity of lines. For greater
+values of <B>alpha</B>, <B>beta</B> (>=1), the algorithm better preserves the original
+shape of the lines. On the other hand, the lines may not
+be move enough. If the values of <B>alpha</B>, <B>beta</B> are too small (<=0.001)
+then the lines are moved sufficiently, but the geometry and topology of lines can
+be destroyed. Probably, the best way to find the good values of <B>alpha</B>, <B>beta</B>
+is by trial and error.
+</LI>
+<LI>
+<B>iterations</B> - denotes the number of iterations the interactions between
+the lines are resolved. Mostly, good values of <B>iterations</B> lies
+between 10 and 100.
+</LI>
+</UL>
+<P>
+The lines affected by the algorithm can be specified by the <B>layer</B>,
+<B>cats</B> and <B>where</B> parameters.
+</P>
+<!-- TODO: example(s) -->
+
+<H2>NETWORK GENERALIZATION</H2>
+<P>
+Is used for selecting "the most important" part of the network. This is based
+on the graph algorithms. Network generalization is applied if method=network.
+The algorithm calculates three centrality measures for each line in the
+network and only the lines with the values greater than thresholds are selected.
+The behaviour of algorithm can be altered by the following parameters:
+</P>
+
+<UL>
+<LI>
+<B>degree_thresh</B> - algorithm selects only the lines which share a point
+with at least <B>degree_thresh</B> different lines.
+</LI>
+<LI>
+<B>closeness_thresh</B> - is always in the range (0, 1]. Only the lines with
+the closeness centrality measure at least <B>closeness_thresh</B> are selcted.
+The lines in the centre of a network have greater values of this measure then
+the lines near the border of a network. This means,
+that this parameters can be used for selecting the centre(s) of a network. Note that
+if closeness_thresh=0 then everything is selected.
+</LI>
+<LI>
+<B>betweeness_thresh</B> - Again, only the lines with betweeness centrality
+measure at least <B>betweeness_thresh</B> are selected. This value is always
+positive and is larger for large networks. It denotes to what extent a line
+is in between the other lines in the network. This value is great for the lines
+which lie between other lines and lie on the paths between two parts of a network.
+In the terminology of the road neworks, these are highways, bypasses, main roads/streets....
+</LI>
+</UL>
+<P>
+All three parameters above can be presented at the same time. In that case,
+the algorithm selects only the lines which meet each criterion.
+</P>
+<P>
+Also, the outputed network may not be connected if the value of <B>betweeness_thresh</B>
+is too large.
+</P>
+<!-- TODO: example(s) -->
+<H2>SEE ALSO</H2>
+<EM><A HREF="http://users.ox.ac.uk/~orie1848/tutorial.html">v.generalize Tutorial</A><BR></EM>
+<EM><A HREF="v.clean.html">v.clean</A><BR></EM>
+<EM><A HREF="v.dissolve.html">v.dissolve</A><BR></EM>
+<BR><BR>
+
+
+<H2>AUTHORS</H2>
+Daniel Bundala, Google Summer of Code 2007, Student
+<BR>
+Wolf Bergenheim, Mentor
+
+<!-- TODO: references -->
+
+<P><I>Last changed: $Date$</I>
Deleted: grass/trunk/vector/v.hull/description.html
===================================================================
--- grass/trunk/vector/v.hull/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/vector/v.hull/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,56 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-v.hull computes the convex hull of a vector points map and outputs the
-convex hull polygon as a vector area map. The convex hull, or convex envelope,
-for an object or a set of objects is the minimal convex set containing the
-given objects. This module creates a vector polygon containing all vector
-points of the input map.
-<P>
-In the case of 3D input points, the hull will be a 3D hull as well, unless the
-user specifies the <b>-f</b> flag. The 3D hull will be composed of triangular
-faces.
-<P>
-
-<BR>
-Example of <em>v.hull</em> output:
-<center>
-<img src=v_hull.png border=1><BR>
-<table border=0 width=590>
-<tr><td><center>
-<i>Convex hull polygon created with v.hull</i>
-</center></td></tr>
-</table>
-</center>
-
-<H2>EXAMPLE</H2>
-
-Example of <em>v.hull</em> 3D output (using two random 3D point clouds):
-<div class="code"><pre>
-g.region rural_1m -p
-r.mapcalc zero=0
-v.random -z out=random3d_a n=10 zmin=0 zmax=200
-v.random -z out=random3d_b n=15 zmin=400 zmax=600
-v.hull random3d_a out=random3d_a_hull
-v.hull random3d_b out=random3d_b_hull
-nviz zero vect=random3d_a_hull,random3d_b_hull
-</pre></div>
-
-<H2>REFERENCES</H2>
-<EM>M. de Berg, M. van Kreveld, M. Overmars, O. Schwarzkopf, (2000).
- Computational geometry, chapter 1.1, 2-8.</EM>
-
-<BR>
-
-<EM>J. O'Rourke, (1998).
- Computational Geometry in C (Second Edition), chapter 4.</EM>
-
-<H2>SEE ALSO</H2>
-<EM>
-<A HREF="v.delaunay.html">v.delaunay</A></EM>
-
-<H2>AUTHOR</H2>
-Andrea Aime, Modena, Italy<br>
-Markus Neteler, ITC-irst (update to 5.7)<br>
-Benjamin Ducke, CAU Kiel (3D hull support)
-
-<p><i>Last changed: $Date$</i></p>
Copied: grass/trunk/vector/v.hull/v.hull.html (from rev 32770, grass/trunk/vector/v.hull/description.html)
===================================================================
--- grass/trunk/vector/v.hull/v.hull.html (rev 0)
+++ grass/trunk/vector/v.hull/v.hull.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,56 @@
+<H2>DESCRIPTION</H2>
+
+v.hull computes the convex hull of a vector points map and outputs the
+convex hull polygon as a vector area map. The convex hull, or convex envelope,
+for an object or a set of objects is the minimal convex set containing the
+given objects. This module creates a vector polygon containing all vector
+points of the input map.
+<P>
+In the case of 3D input points, the hull will be a 3D hull as well, unless the
+user specifies the <b>-f</b> flag. The 3D hull will be composed of triangular
+faces.
+<P>
+
+<BR>
+Example of <em>v.hull</em> output:
+<center>
+<img src=v_hull.png border=1><BR>
+<table border=0 width=590>
+<tr><td><center>
+<i>Convex hull polygon created with v.hull</i>
+</center></td></tr>
+</table>
+</center>
+
+<H2>EXAMPLE</H2>
+
+Example of <em>v.hull</em> 3D output (using two random 3D point clouds):
+<div class="code"><pre>
+g.region rural_1m -p
+r.mapcalc zero=0
+v.random -z out=random3d_a n=10 zmin=0 zmax=200
+v.random -z out=random3d_b n=15 zmin=400 zmax=600
+v.hull random3d_a out=random3d_a_hull
+v.hull random3d_b out=random3d_b_hull
+nviz zero vect=random3d_a_hull,random3d_b_hull
+</pre></div>
+
+<H2>REFERENCES</H2>
+<EM>M. de Berg, M. van Kreveld, M. Overmars, O. Schwarzkopf, (2000).
+ Computational geometry, chapter 1.1, 2-8.</EM>
+
+<BR>
+
+<EM>J. O'Rourke, (1998).
+ Computational Geometry in C (Second Edition), chapter 4.</EM>
+
+<H2>SEE ALSO</H2>
+<EM>
+<A HREF="v.delaunay.html">v.delaunay</A></EM>
+
+<H2>AUTHOR</H2>
+Andrea Aime, Modena, Italy<br>
+Markus Neteler, ITC-irst (update to 5.7)<br>
+Benjamin Ducke, CAU Kiel (3D hull support)
+
+<p><i>Last changed: $Date$</i></p>
Deleted: grass/trunk/vector/v.in.ascii/description.html
===================================================================
--- grass/trunk/vector/v.in.ascii/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/vector/v.in.ascii/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,378 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>v.in.ascii</em> converts a vector map in ASCII format to a vector map in
-binary format. The module may import two formats:
-<ul>
-<li><b>standard</b> contains all data types, each coordinate on one row</li>
-<li><b>point</b> (default) reads only points, each point defined on
- one row. Values are separated by a user definable deliminator. If
- the <b>columns</b> option is not defined, default names are used. It
- is possible to specify the column order for the x,y,z coordinates
- and category values.</li>
-</ul>
-
-<p>
-The <a HREF="v.out.ascii.html">v.out.ascii</a> GRASS module performs
-the function of <em>v.in.ascii</em> in reverse; i.e., it converts
-vector maps in binary format to ASCII format. These two companion
-programs are useful both for importing and exporting vector maps
-between GRASS and other software, and for transferring data between
-machines.
-
-<h2>NOTES</h2>
-
-The input is read from the file specified by the <b>input</b> option or
-from standard input.
-
-<p>
-The field separator may be a character, the word '<tt>tab</tt>'
-(or '<tt>\t</tt>') for tab, '<tt>space</tt>' (or ' ') for a blank,
-or '<tt>comma</tt>' (or ',') for a comma.
-
-<p>
-Attribute table is only created if it is needed, i.e. when at
-least one attribute column is present in the input file besides
-geometry columns. The attribute column will be auto-scanned for type, but
-may be explicitly declared along with the geometry columns using the
-<b>columns</b> parameter.
-
-<p>
-Latitude/Longitude data may be given in a number of ways.
-Decimal degrees must be positive or negative instead of using a hemisphere
-letter. Mixed coordinates must use a hemisphere letter. Whole minutes and
-seconds must always contain two digits (example: use <tt>167:03:04.567</tt>;
-and not <tt>167:3:4.567</tt>).
-<br><br>
-Acceptable formats:<br>
-<i>key: D=Degrees; M=Minutes; S=Seconds; h=Hemisphere (N,S,E,W)</i>
-<ul>
- <li><tt>(+/-)DDD.DDDDD</tt>
- <li><tt>DDDh</tt>
- <li><tt>DDD:MMh</tt>
- <li><tt>DDD:MM.MMMMMh</tt>
- <li><tt>DDD:MM:SSh</tt>
- <li><tt>DDD:MM:SS.SSSSSh</tt>
-</ul>
-
-<p>
-Use the <b>-z</b> flag to convert ASCII data into a 3D vector map.
-
-<p>
-In special cases of data import, such as the import of large LIDAR datasets
-(millions of data points), it may be necessary to disable topology support
-(creating a GRASS vector level 1 vector map) due to memory constraints.
-This is done with the <b>-b</b> flag. As only very few vector modules
-support points data processing at vector level 1, usually topology is
-required (vector level 2). Therefore it is recommened that the user first
-try to import the data without creating a database (the <b>-t</b> flag)
-or within a subregion (the <b>-r</b> flag) before resorting the to
-disabling of topology.
-
-<p>
-A GRASS ASCII vector map (in <B>standard</B> mode) may contain a mix
-of primitives including points, lines, boundaries, centroids, areas,
-faces, and kernels.
-<!--This format is described in the
-<a HREF="http://freegis.org/cgi-bin/viewcvs.cgi/~checkout~/grass6/doc/vector/vector.html#ascii">GRASS
-Vector ASCII Format Specification</a>.--> On top a header can be
-defined (see example below). The header is not required if
-the <b>-n</b> flag is used.
-
-<p>The header is similar as the head file of vector binary format but
-contains bounding box also. Key words are:
-
-<pre>
-ORGANIZATION
-DIGIT DATE
-DIGIT NAME
-MAP NAME
-MAP DATE
-MAP SCALE
-OTHER INFO
-ZONE
-WEST EDGE
-EAST EDGE
-SOUTH EDGE
-NORTH EDGE
-MAP THRESH
-</pre>
-
-<p>The body begins with the row:
-
-<pre>
-VERTI:
-</pre>
-
-followed by records of primitives:
-
-<pre>
-TYPE NUMBER_OF_COORDINATES [NUMBER_OF_CATEGORIES]
- X Y [Z]
-....
- X Y [Z]
-[ LAYER CATEGORY]
-....
-[ LAYER CATEGORY]
-</pre>
-
-Everything above in <tt>[ ]</tt> is optional.
-
-<p>
-The primitive codes are as follows:
-<ul>
-<li>'P': point</li>
-<li>'L': line</li>
-<li>'B': boundary</li>
-<li>'C': centroid</li>
-<li>'F': face (3D boundary)</li>
-<li>'K': kernel (3D centroid)</li>
-<li>'A': area (boundary) - better use 'B'; kept only for backward
-compatibility</li>
-</ul>
-
-The coordinates are listed following the initial line containing the
-primitive code, the total number of vectors in the series, and (optionally)
-the number of categories (1 for a single layer, higher for multiple layers).
-Below that 1 or several lines follow to indicate the layer number and
-the category number (ID).
-<br>
-The order of coordinates is
-<pre>
- X Y [Z]
-</pre>
-
-<h3>Import of files without category ID column</h3>
-
-If the input file does not contain a vector ID column,
-there is the possibility to auto-generate these IDs (categories).
-To automatically add an additional column named 'cat', the
-<b>cat</b> parameter must be set to the virtual column number 0
-(<tt>cat=0</tt>). This is the default action if the <b>cat</b> parameter
-is not set.
-
-<h3>Importing from a spreadsheet</h3>
-
-Data may be imported from many spreadsheet programs by saving the
-spreadsheet as a comma separated variable (.csv) text file, and then
-using the <b>fs=','</b> option with <em>v.in.ascii</em> in <b>points</b> mode.
-If the input file contains any header lines, such as column headings, the
-<b>skip</b> parameter should be used. These skipped header lines will be
-written to the map's history file for later reference (read with
-<tt>v.info -h</tt>). The skip option only works in <tt>points</tt> mode.
-<P>
-Any line starting with the hash character ('<tt>#</tt>') will be treated as
-a comment and skipped completely if located in the main data file. If located
-in the header, as defined by the <b>skip</b> parameter, it will be treated as
-a header line and written to the history file.
-
-<h3>Import of sexagesimal degree (degree, minutes, seconds, DMS)</h3>
-
-The import of DMS formatted degrees is supported (in this case no
-sign but N/S, E/W characters are used to indicate the hemispheres).
-While the positions are internally translated into decimal degrees
-during the import, the original DMS values are maintained in the
-attribute table. This requires both the latitude and
-the longitude columns to be defined as varchars(), not as numbers.
-A warning will be issued which can be ignored.
-
-<h3>Importing only selected columns</h3>
-Although <em>v.in.ascii</em> doesn't have an option to specify which columns
-should be imported, you can use a shell filter to achieve the same effect,
-e.g.:
-
-<div class="code"><pre>
-# Print out the column number for each field, supposing the file has a header
-head -1 input_file | tr '<the_field_separator_character>' '\n' | cat -n
-# From the listing, select the columns you want and feed them to v.in.ascii
-# do not use the input= option
-cut -d<the_field_separator_character> -f<comma-separated_list_of_columns> input_file | v.in.ascii <your_options>
-</pre></div>
-
-
-<h2>EXAMPLES</h2>
-
-<h3>Example 1a) - standard mode</h3>
-Sample ASCII polygon vector map for 'standard' mode.
-The two areas will be assigned categories 20 and 21.
-The example can be tested in the Spearfish sample dataset:
-<p>
-<div class="code"><pre>
-ORGANIZATION: GRASS Development Team
-DIGIT DATE: 1/9/2005
-DIGIT NAME: -
-MAP NAME: test
-MAP DATE: 2005
-MAP SCALE: 10000
-OTHER INFO: Test polygons
-ZONE: 0
-MAP THRESH: 0.500000
-VERTI:
-B 6
- 5958812.48844435 3400828.84221011
- 5958957.29887089 3400877.11235229
- 5959021.65906046 3400930.7458436
- 5959048.47580612 3400973.65263665
- 5959069.92920264 3401032.64947709
- 5958812.48844435 3400828.84221011
-C 1 1
- 5958952.42189184 3400918.23126419
- 1 20
-B 4
- 5959010.9323622 3401338.36037757
- 5959096.7459483 3401370.54047235
- 5959091.38259917 3401450.99070932
- 5959010.9323622 3401338.36037757
-C 1 1
- 5959063.08352122 3401386.98533277
- 1 21
-</pre></div>
-
-<h3>Example 1b) - standard mode</h3>
-Sample ASCII 3D line vector map for 'standard' mode with simplified input
-(no header). The example can be tested in the Spearfish sample dataset:
-
-<div class="code"><pre>
-echo "L 5 1
-591336 4927369 1224
-594317 4925341 1292
-599356 4925162 1469
-602396 4926653 1235
-607524 4925431 1216
-1 321 " | v.in.ascii -zn out=line3d format=standard
-</pre></div>
-
-This can be used to create a vector line of a GPS track: the GPS points have
-to be stored into a file with a preceding 'L' and the number of points (per line).
-
-<h3>Example 2</h3>
-
-Generate a 2D points vector map 'coords.txt' as ASCII file:
-<div class="code"><pre>
-1664619|5103481
-1664473|5095782
-1664273|5101919
-1663427|5105234
-1663709|5102614
-</pre></div>
-
-<p>
-Import into GRASS:
-<div class="code"><pre>
-v.in.ascii input=coords.txt output=mymap
-</pre></div>
-As the <b>cat</b> option is set to 0 by default, an extra column 'cat'
-containing the IDs will be auto-generated.
-
-<h3>Example 3</h3>
-
-Generate a 2D points vector map 'points.dat' as ASCII file:
-<div class="code"><pre>
-1|1664619|5103481|studna
-2|1664473|5095782|kadibudka
-3|1664273|5101919|hruska
-4|1663427|5105234|mysi dira
-5|1663709|5102614|mineralni pramen
-</pre></div>
-
-<p>
-Import into GRASS:
-<div class="code"><pre>
-cat points.dat | v.in.ascii out=mypoints x=2 y=3 cat=1 \
- columns='cat int, x double precision, y double precision, label varchar(20)'
-</pre></div>
-
-<p>
-The module is reading from standard input, using the default '|' (pipe) delimiter.
-
-<h3>Example 4</h3>
-
-Generating a 3D points vector map from DBMS (idcol must be an integer column):<br>
-<div class="code"><pre>
-echo "select east,north,elev,idcol from mytable" | db.select -c | v.in.ascii -z out=mymap
-</pre></div>
-
-The module is reading from standard input, using the default '|' (pipe) delimiter.
-<br>
-The import works for 2D maps as well (no elev column and no '-z' flag).
-
-
-<h3>Example 5</h3>
-
-Generate a 3D points vector map 'points3d.dat' with attributes as ASCII file:
-<div class="code"><pre>
-593493.1|4914730.2|123.1|studna|well
-591950.2|4923000.5|222.3|kadibudka|closet
-589860.5|4922000.0|232.3|hruska|pear
-590400.5|4922820.8|143.2|mysi dira|mouse hole
-593549.3|4925500.7|442.6|mineralni pramen|mineral spring
-600375.7|4925235.6|342.2|kozi stezka|goat path
-</pre></div>
-<P>
-Import into GRASS:
-<div class="code"><pre>
-#As the 'cat' option is set to 0 by default, an extra column 'cat'
-#containing the IDs will be auto-generated (no need to define that):
-cat points3d.dat | v.in.ascii -z z=3 cat=0 out=mypoints3D \
- columns='x double precision, y double precision, z double precision, \
- label_cz varchar(20), label_en varchar(20)'
-v.info -c mypoints3D
-v.info mypoints3D
-</pre></div>
-
-
-<h3>Example 6</h3>
-
-Generate points file by clicking onto the map:
-<div class="code"><pre>
-#For LatLong locations:
-d.where -d -l | awk '{printf "%f|%f|point\n", $1, $2}' | v.in.ascii out=points \
- columns='x double precision, y double precision, label varchar(20)'
-
-#For other projections:
-d.where | awk '{printf "%f|%f|point\n", $1, $2}' | v.in.ascii out=points \
- columns='x double precision, y double precision, label varchar(20)'
-</pre></div>
-
-The 'point' string (or some similar entry) is required to generate a database table.
-When simply piping the coordinates (and optionally height) without additional column(s)
-into <em>v.in.ascii</em>, only the vector map geometry will be generated.
-
-<h3>Example 7</h3>
-
-Convert ground control points from i.points into vector points:
-<div class="code"><pre>
-cat $MAPSET/group/$GROUP/POINTS | v.in.ascii out=$GROUP_gcp fs=space skip=3 \
- col='x double precision, y double precision, x_target double precision, \
- y_target double precision, ok int'
-</pre></div>
-
-<h2>REFERENCES</h2>
-
-<a HREF="sql.html">SQL command notes</a> for creating databases
-
-<h2>SEE ALSO</h2>
-
-<em>
-<a HREF="db.execute.html">db.execute</a>,
-<a HREF="r.in.ascii.html">r.in.ascii</a>,
-<a HREF="r.in.xyz.html">r.in.xyz</a>,
-<a HREF="v.db.connect.html">v.db.connect</a>,
-<a HREF="v.out.ascii.html">v.out.ascii</a>,
-<a HREF="v.info.html">v.info</a>,
-<a HREF="v.build.html">v.build</a>,
-<a HREF="v.build.polylines.html">v.build.polylines</a>,
-<a HREF="v.centroids.html">v.centroids</a>,
-<a HREF="v.clean.html">v.clean</a>
-</em>
-
-<h2>AUTHORS</h2>
-
-Michael Higgins,
-U.S.Army Construction Engineering
-Research Laboratory<br>
-James Westervelt, U.S.Army Construction Engineering
-Research Laboratory<br>
-Radim Blazek, ITC-Irst, Trento, Italy
-
-<p>
-<i>Last changed: $Date$</i>
Copied: grass/trunk/vector/v.in.ascii/v.in.ascii.html (from rev 32770, grass/trunk/vector/v.in.ascii/description.html)
===================================================================
--- grass/trunk/vector/v.in.ascii/v.in.ascii.html (rev 0)
+++ grass/trunk/vector/v.in.ascii/v.in.ascii.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,378 @@
+<h2>DESCRIPTION</h2>
+
+<em>v.in.ascii</em> converts a vector map in ASCII format to a vector map in
+binary format. The module may import two formats:
+<ul>
+<li><b>standard</b> contains all data types, each coordinate on one row</li>
+<li><b>point</b> (default) reads only points, each point defined on
+ one row. Values are separated by a user definable deliminator. If
+ the <b>columns</b> option is not defined, default names are used. It
+ is possible to specify the column order for the x,y,z coordinates
+ and category values.</li>
+</ul>
+
+<p>
+The <a HREF="v.out.ascii.html">v.out.ascii</a> GRASS module performs
+the function of <em>v.in.ascii</em> in reverse; i.e., it converts
+vector maps in binary format to ASCII format. These two companion
+programs are useful both for importing and exporting vector maps
+between GRASS and other software, and for transferring data between
+machines.
+
+<h2>NOTES</h2>
+
+The input is read from the file specified by the <b>input</b> option or
+from standard input.
+
+<p>
+The field separator may be a character, the word '<tt>tab</tt>'
+(or '<tt>\t</tt>') for tab, '<tt>space</tt>' (or ' ') for a blank,
+or '<tt>comma</tt>' (or ',') for a comma.
+
+<p>
+Attribute table is only created if it is needed, i.e. when at
+least one attribute column is present in the input file besides
+geometry columns. The attribute column will be auto-scanned for type, but
+may be explicitly declared along with the geometry columns using the
+<b>columns</b> parameter.
+
+<p>
+Latitude/Longitude data may be given in a number of ways.
+Decimal degrees must be positive or negative instead of using a hemisphere
+letter. Mixed coordinates must use a hemisphere letter. Whole minutes and
+seconds must always contain two digits (example: use <tt>167:03:04.567</tt>;
+and not <tt>167:3:4.567</tt>).
+<br><br>
+Acceptable formats:<br>
+<i>key: D=Degrees; M=Minutes; S=Seconds; h=Hemisphere (N,S,E,W)</i>
+<ul>
+ <li><tt>(+/-)DDD.DDDDD</tt>
+ <li><tt>DDDh</tt>
+ <li><tt>DDD:MMh</tt>
+ <li><tt>DDD:MM.MMMMMh</tt>
+ <li><tt>DDD:MM:SSh</tt>
+ <li><tt>DDD:MM:SS.SSSSSh</tt>
+</ul>
+
+<p>
+Use the <b>-z</b> flag to convert ASCII data into a 3D vector map.
+
+<p>
+In special cases of data import, such as the import of large LIDAR datasets
+(millions of data points), it may be necessary to disable topology support
+(creating a GRASS vector level 1 vector map) due to memory constraints.
+This is done with the <b>-b</b> flag. As only very few vector modules
+support points data processing at vector level 1, usually topology is
+required (vector level 2). Therefore it is recommened that the user first
+try to import the data without creating a database (the <b>-t</b> flag)
+or within a subregion (the <b>-r</b> flag) before resorting the to
+disabling of topology.
+
+<p>
+A GRASS ASCII vector map (in <B>standard</B> mode) may contain a mix
+of primitives including points, lines, boundaries, centroids, areas,
+faces, and kernels.
+<!--This format is described in the
+<a HREF="http://freegis.org/cgi-bin/viewcvs.cgi/~checkout~/grass6/doc/vector/vector.html#ascii">GRASS
+Vector ASCII Format Specification</a>.--> On top a header can be
+defined (see example below). The header is not required if
+the <b>-n</b> flag is used.
+
+<p>The header is similar as the head file of vector binary format but
+contains bounding box also. Key words are:
+
+<pre>
+ORGANIZATION
+DIGIT DATE
+DIGIT NAME
+MAP NAME
+MAP DATE
+MAP SCALE
+OTHER INFO
+ZONE
+WEST EDGE
+EAST EDGE
+SOUTH EDGE
+NORTH EDGE
+MAP THRESH
+</pre>
+
+<p>The body begins with the row:
+
+<pre>
+VERTI:
+</pre>
+
+followed by records of primitives:
+
+<pre>
+TYPE NUMBER_OF_COORDINATES [NUMBER_OF_CATEGORIES]
+ X Y [Z]
+....
+ X Y [Z]
+[ LAYER CATEGORY]
+....
+[ LAYER CATEGORY]
+</pre>
+
+Everything above in <tt>[ ]</tt> is optional.
+
+<p>
+The primitive codes are as follows:
+<ul>
+<li>'P': point</li>
+<li>'L': line</li>
+<li>'B': boundary</li>
+<li>'C': centroid</li>
+<li>'F': face (3D boundary)</li>
+<li>'K': kernel (3D centroid)</li>
+<li>'A': area (boundary) - better use 'B'; kept only for backward
+compatibility</li>
+</ul>
+
+The coordinates are listed following the initial line containing the
+primitive code, the total number of vectors in the series, and (optionally)
+the number of categories (1 for a single layer, higher for multiple layers).
+Below that 1 or several lines follow to indicate the layer number and
+the category number (ID).
+<br>
+The order of coordinates is
+<pre>
+ X Y [Z]
+</pre>
+
+<h3>Import of files without category ID column</h3>
+
+If the input file does not contain a vector ID column,
+there is the possibility to auto-generate these IDs (categories).
+To automatically add an additional column named 'cat', the
+<b>cat</b> parameter must be set to the virtual column number 0
+(<tt>cat=0</tt>). This is the default action if the <b>cat</b> parameter
+is not set.
+
+<h3>Importing from a spreadsheet</h3>
+
+Data may be imported from many spreadsheet programs by saving the
+spreadsheet as a comma separated variable (.csv) text file, and then
+using the <b>fs=','</b> option with <em>v.in.ascii</em> in <b>points</b> mode.
+If the input file contains any header lines, such as column headings, the
+<b>skip</b> parameter should be used. These skipped header lines will be
+written to the map's history file for later reference (read with
+<tt>v.info -h</tt>). The skip option only works in <tt>points</tt> mode.
+<P>
+Any line starting with the hash character ('<tt>#</tt>') will be treated as
+a comment and skipped completely if located in the main data file. If located
+in the header, as defined by the <b>skip</b> parameter, it will be treated as
+a header line and written to the history file.
+
+<h3>Import of sexagesimal degree (degree, minutes, seconds, DMS)</h3>
+
+The import of DMS formatted degrees is supported (in this case no
+sign but N/S, E/W characters are used to indicate the hemispheres).
+While the positions are internally translated into decimal degrees
+during the import, the original DMS values are maintained in the
+attribute table. This requires both the latitude and
+the longitude columns to be defined as varchars(), not as numbers.
+A warning will be issued which can be ignored.
+
+<h3>Importing only selected columns</h3>
+Although <em>v.in.ascii</em> doesn't have an option to specify which columns
+should be imported, you can use a shell filter to achieve the same effect,
+e.g.:
+
+<div class="code"><pre>
+# Print out the column number for each field, supposing the file has a header
+head -1 input_file | tr '<the_field_separator_character>' '\n' | cat -n
+# From the listing, select the columns you want and feed them to v.in.ascii
+# do not use the input= option
+cut -d<the_field_separator_character> -f<comma-separated_list_of_columns> input_file | v.in.ascii <your_options>
+</pre></div>
+
+
+<h2>EXAMPLES</h2>
+
+<h3>Example 1a) - standard mode</h3>
+Sample ASCII polygon vector map for 'standard' mode.
+The two areas will be assigned categories 20 and 21.
+The example can be tested in the Spearfish sample dataset:
+<p>
+<div class="code"><pre>
+ORGANIZATION: GRASS Development Team
+DIGIT DATE: 1/9/2005
+DIGIT NAME: -
+MAP NAME: test
+MAP DATE: 2005
+MAP SCALE: 10000
+OTHER INFO: Test polygons
+ZONE: 0
+MAP THRESH: 0.500000
+VERTI:
+B 6
+ 5958812.48844435 3400828.84221011
+ 5958957.29887089 3400877.11235229
+ 5959021.65906046 3400930.7458436
+ 5959048.47580612 3400973.65263665
+ 5959069.92920264 3401032.64947709
+ 5958812.48844435 3400828.84221011
+C 1 1
+ 5958952.42189184 3400918.23126419
+ 1 20
+B 4
+ 5959010.9323622 3401338.36037757
+ 5959096.7459483 3401370.54047235
+ 5959091.38259917 3401450.99070932
+ 5959010.9323622 3401338.36037757
+C 1 1
+ 5959063.08352122 3401386.98533277
+ 1 21
+</pre></div>
+
+<h3>Example 1b) - standard mode</h3>
+Sample ASCII 3D line vector map for 'standard' mode with simplified input
+(no header). The example can be tested in the Spearfish sample dataset:
+
+<div class="code"><pre>
+echo "L 5 1
+591336 4927369 1224
+594317 4925341 1292
+599356 4925162 1469
+602396 4926653 1235
+607524 4925431 1216
+1 321 " | v.in.ascii -zn out=line3d format=standard
+</pre></div>
+
+This can be used to create a vector line of a GPS track: the GPS points have
+to be stored into a file with a preceding 'L' and the number of points (per line).
+
+<h3>Example 2</h3>
+
+Generate a 2D points vector map 'coords.txt' as ASCII file:
+<div class="code"><pre>
+1664619|5103481
+1664473|5095782
+1664273|5101919
+1663427|5105234
+1663709|5102614
+</pre></div>
+
+<p>
+Import into GRASS:
+<div class="code"><pre>
+v.in.ascii input=coords.txt output=mymap
+</pre></div>
+As the <b>cat</b> option is set to 0 by default, an extra column 'cat'
+containing the IDs will be auto-generated.
+
+<h3>Example 3</h3>
+
+Generate a 2D points vector map 'points.dat' as ASCII file:
+<div class="code"><pre>
+1|1664619|5103481|studna
+2|1664473|5095782|kadibudka
+3|1664273|5101919|hruska
+4|1663427|5105234|mysi dira
+5|1663709|5102614|mineralni pramen
+</pre></div>
+
+<p>
+Import into GRASS:
+<div class="code"><pre>
+cat points.dat | v.in.ascii out=mypoints x=2 y=3 cat=1 \
+ columns='cat int, x double precision, y double precision, label varchar(20)'
+</pre></div>
+
+<p>
+The module is reading from standard input, using the default '|' (pipe) delimiter.
+
+<h3>Example 4</h3>
+
+Generating a 3D points vector map from DBMS (idcol must be an integer column):<br>
+<div class="code"><pre>
+echo "select east,north,elev,idcol from mytable" | db.select -c | v.in.ascii -z out=mymap
+</pre></div>
+
+The module is reading from standard input, using the default '|' (pipe) delimiter.
+<br>
+The import works for 2D maps as well (no elev column and no '-z' flag).
+
+
+<h3>Example 5</h3>
+
+Generate a 3D points vector map 'points3d.dat' with attributes as ASCII file:
+<div class="code"><pre>
+593493.1|4914730.2|123.1|studna|well
+591950.2|4923000.5|222.3|kadibudka|closet
+589860.5|4922000.0|232.3|hruska|pear
+590400.5|4922820.8|143.2|mysi dira|mouse hole
+593549.3|4925500.7|442.6|mineralni pramen|mineral spring
+600375.7|4925235.6|342.2|kozi stezka|goat path
+</pre></div>
+<P>
+Import into GRASS:
+<div class="code"><pre>
+#As the 'cat' option is set to 0 by default, an extra column 'cat'
+#containing the IDs will be auto-generated (no need to define that):
+cat points3d.dat | v.in.ascii -z z=3 cat=0 out=mypoints3D \
+ columns='x double precision, y double precision, z double precision, \
+ label_cz varchar(20), label_en varchar(20)'
+v.info -c mypoints3D
+v.info mypoints3D
+</pre></div>
+
+
+<h3>Example 6</h3>
+
+Generate points file by clicking onto the map:
+<div class="code"><pre>
+#For LatLong locations:
+d.where -d -l | awk '{printf "%f|%f|point\n", $1, $2}' | v.in.ascii out=points \
+ columns='x double precision, y double precision, label varchar(20)'
+
+#For other projections:
+d.where | awk '{printf "%f|%f|point\n", $1, $2}' | v.in.ascii out=points \
+ columns='x double precision, y double precision, label varchar(20)'
+</pre></div>
+
+The 'point' string (or some similar entry) is required to generate a database table.
+When simply piping the coordinates (and optionally height) without additional column(s)
+into <em>v.in.ascii</em>, only the vector map geometry will be generated.
+
+<h3>Example 7</h3>
+
+Convert ground control points from i.points into vector points:
+<div class="code"><pre>
+cat $MAPSET/group/$GROUP/POINTS | v.in.ascii out=$GROUP_gcp fs=space skip=3 \
+ col='x double precision, y double precision, x_target double precision, \
+ y_target double precision, ok int'
+</pre></div>
+
+<h2>REFERENCES</h2>
+
+<a HREF="sql.html">SQL command notes</a> for creating databases
+
+<h2>SEE ALSO</h2>
+
+<em>
+<a HREF="db.execute.html">db.execute</a>,
+<a HREF="r.in.ascii.html">r.in.ascii</a>,
+<a HREF="r.in.xyz.html">r.in.xyz</a>,
+<a HREF="v.db.connect.html">v.db.connect</a>,
+<a HREF="v.out.ascii.html">v.out.ascii</a>,
+<a HREF="v.info.html">v.info</a>,
+<a HREF="v.build.html">v.build</a>,
+<a HREF="v.build.polylines.html">v.build.polylines</a>,
+<a HREF="v.centroids.html">v.centroids</a>,
+<a HREF="v.clean.html">v.clean</a>
+</em>
+
+<h2>AUTHORS</h2>
+
+Michael Higgins,
+U.S.Army Construction Engineering
+Research Laboratory<br>
+James Westervelt, U.S.Army Construction Engineering
+Research Laboratory<br>
+Radim Blazek, ITC-Irst, Trento, Italy
+
+<p>
+<i>Last changed: $Date$</i>
Deleted: grass/trunk/vector/v.in.db/description.html
===================================================================
--- grass/trunk/vector/v.in.db/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/vector/v.in.db/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,90 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-<em>v.in.db</em>
-creates new vector (points) map from database table containing coordinates.
-
-<H2>EXAMPLE</H2>
-
-<h3>1) Creating a map from PostgreSQL table:</h3>
-
-<div class="code"><pre>
-v.in.db driver=pg database="host=myserver.itc.it,dbname=mydb" \
- table=pat_stazioni x=east y=north z=quota key=id output=pat_stazioni
-</pre></div>
-<P>
-If an ID column is not not present in the PostgreSQL table,
-a new column should be added. See <a href="grass-pg.html">pg</a> driver
-page for detail.
-
-<h3>2) Creating a map from PostGIS:</h3>
-
-To extract coordinate values from PostGIS, functions have to be used:
-<div class="code"><pre>
-v.in.db driver=pg database="host=myserver.itc.it,dbname=mydb" \
- table=station x="x(geom)" y="y(geom)" z="z(geom)" key=id out=meteostations
-</pre></div>
-<P>
-If an ID column is not not present in the PostgreSQL table,
-a new column should be added. See <a href="grass-pg.html">pg</a> driver
-page for detail.
-
-<h3>3) Import of a points table (x, y, z) from DBF file to vector points map:</h3>
-
-<div class="code"><pre>
-#create vector map from DBF table (here, 'idcol' contains unique row IDs, 'z' is optional):
-#the 'database' parameter is the directory where the DBF file is stored:
-v.in.db driver=dbf database=/home/user/tables/ table=pointsfile x=x y=y z=z \
- key=idcol out=dtmpoints
-
-#check result:
-v.info dtmpoints
-v.info -c dtmpoints
-</pre></div>
-<P>
-If an ID column is missing in the DBF file, it has to be added beforehand, e.g. with OpenOffice.
-Alternatively, import the table with <em>db.in.ogr</em> into GRASS and then with <em>v.in.db</em>
-from the imported table (<em>db.in.ogr</em> optionally adds an unique ID column).
-
-<h3>4) Import of a points table (x, y, z) from SQLite file to vector points map:</h3>
-
-<div class="code"><pre>
-#create vector map from table in SQLITE database file (here, 'idcol' contains unique row IDs, 'z' is optional):
-#the 'database' parameter is the the SQLite database file with path:
-v.in.db driver=sqlite database=/home/user/tables/mysqlite.db table=pointsfile x=x y=y z=z \
- key=idcol out=dtmpoints
-
-#check result:
-v.info dtmpoints
-v.info -c dtmpoints
-</pre></div>
-<P>
-If an ID column is missing in the table, it has to be added beforehand with 'sqlite3' or
-<em>db.execute</em>.
-
-
-<h3>5) Import of a points table (x, y, z) from DBF file to vector points map for selected points only:</h3>
-<P>
-The user can import only selected vector points from a table using the <em>where</em> parameter
-(see above for general DBF handling):<P>
-<div class="code"><pre>
-v.in.db driver=dbf database=/home/user/tables/ table=pointsfile x=x y=y z=z \
- key=idcol out=dtmpoints where="x NOT NULL and z > 100"
-</pre></div>
-
-<h2>SEE ALSO</h2>
-
-<em>
-<a href="db.execute.html">db.execute</a>,
-<a href="db.in.ogr.html">db.in.ogr</a>,
-<a href="v.info.html">v.info</a>,
-<a href="v.in.ogr.html">v.in.ogr</a>,
-<a href="v.to.db.html">v.to.db</a>,<br>
-<a HREF="sql.html">SQL support in GRASS GIS</a>
-</em>
-
-
-<H2>AUTHOR</H2>
-
-Radim Blazek
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/vector/v.in.db/v.in.db.html (from rev 32770, grass/trunk/vector/v.in.db/description.html)
===================================================================
--- grass/trunk/vector/v.in.db/v.in.db.html (rev 0)
+++ grass/trunk/vector/v.in.db/v.in.db.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,90 @@
+<H2>DESCRIPTION</H2>
+
+<em>v.in.db</em>
+creates new vector (points) map from database table containing coordinates.
+
+<H2>EXAMPLE</H2>
+
+<h3>1) Creating a map from PostgreSQL table:</h3>
+
+<div class="code"><pre>
+v.in.db driver=pg database="host=myserver.itc.it,dbname=mydb" \
+ table=pat_stazioni x=east y=north z=quota key=id output=pat_stazioni
+</pre></div>
+<P>
+If an ID column is not not present in the PostgreSQL table,
+a new column should be added. See <a href="grass-pg.html">pg</a> driver
+page for detail.
+
+<h3>2) Creating a map from PostGIS:</h3>
+
+To extract coordinate values from PostGIS, functions have to be used:
+<div class="code"><pre>
+v.in.db driver=pg database="host=myserver.itc.it,dbname=mydb" \
+ table=station x="x(geom)" y="y(geom)" z="z(geom)" key=id out=meteostations
+</pre></div>
+<P>
+If an ID column is not not present in the PostgreSQL table,
+a new column should be added. See <a href="grass-pg.html">pg</a> driver
+page for detail.
+
+<h3>3) Import of a points table (x, y, z) from DBF file to vector points map:</h3>
+
+<div class="code"><pre>
+#create vector map from DBF table (here, 'idcol' contains unique row IDs, 'z' is optional):
+#the 'database' parameter is the directory where the DBF file is stored:
+v.in.db driver=dbf database=/home/user/tables/ table=pointsfile x=x y=y z=z \
+ key=idcol out=dtmpoints
+
+#check result:
+v.info dtmpoints
+v.info -c dtmpoints
+</pre></div>
+<P>
+If an ID column is missing in the DBF file, it has to be added beforehand, e.g. with OpenOffice.
+Alternatively, import the table with <em>db.in.ogr</em> into GRASS and then with <em>v.in.db</em>
+from the imported table (<em>db.in.ogr</em> optionally adds an unique ID column).
+
+<h3>4) Import of a points table (x, y, z) from SQLite file to vector points map:</h3>
+
+<div class="code"><pre>
+#create vector map from table in SQLITE database file (here, 'idcol' contains unique row IDs, 'z' is optional):
+#the 'database' parameter is the the SQLite database file with path:
+v.in.db driver=sqlite database=/home/user/tables/mysqlite.db table=pointsfile x=x y=y z=z \
+ key=idcol out=dtmpoints
+
+#check result:
+v.info dtmpoints
+v.info -c dtmpoints
+</pre></div>
+<P>
+If an ID column is missing in the table, it has to be added beforehand with 'sqlite3' or
+<em>db.execute</em>.
+
+
+<h3>5) Import of a points table (x, y, z) from DBF file to vector points map for selected points only:</h3>
+<P>
+The user can import only selected vector points from a table using the <em>where</em> parameter
+(see above for general DBF handling):<P>
+<div class="code"><pre>
+v.in.db driver=dbf database=/home/user/tables/ table=pointsfile x=x y=y z=z \
+ key=idcol out=dtmpoints where="x NOT NULL and z > 100"
+</pre></div>
+
+<h2>SEE ALSO</h2>
+
+<em>
+<a href="db.execute.html">db.execute</a>,
+<a href="db.in.ogr.html">db.in.ogr</a>,
+<a href="v.info.html">v.info</a>,
+<a href="v.in.ogr.html">v.in.ogr</a>,
+<a href="v.to.db.html">v.to.db</a>,<br>
+<a HREF="sql.html">SQL support in GRASS GIS</a>
+</em>
+
+
+<H2>AUTHOR</H2>
+
+Radim Blazek
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/vector/v.in.dwg/description.html
===================================================================
--- grass/trunk/vector/v.in.dwg/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/vector/v.in.dwg/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,36 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>v.in.dwg</em> imports DWG/DXF file into GRASS.
-
-<h2>EXAMPLE</h2>
-<div class="code"><pre>
-v.in.dwg input=map.dwg output=map
-</pre></div>
-
-<h2>NOTES</h2>
-
-v.in.dwg requires OpenDWG toolkit. To get this toolkit you must become at
-least "Associate Member" of OpenDWG Alliance (http://www.opendesign.com/).
-<P>
-The toolkit, for example <tt>ad27linx.tar</tt>, unpack in a directory
-(e.g. /home/usr1/opendwg27) and use the related <tt>configure</tt> options
-to tell GRASS about it:
-
-<div class="code"><pre>
- ./configure \
- ... \
- --with-opendwg \
- --with-opendwg-includes=/home/usr1/opendwg27 \
- --with-opendwg-libs=/home/usr1/opendwg27
-</pre></div>
-
-Then you can compile this module.
-<P>
-Not all entity types are supported (warning printed).
-
-
-<h2>AUTHOR</h2>
-
-Radim Blazek, ITC-Irst, Trento, Italy
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/vector/v.in.dwg/v.in.dwg.html (from rev 32770, grass/trunk/vector/v.in.dwg/description.html)
===================================================================
--- grass/trunk/vector/v.in.dwg/v.in.dwg.html (rev 0)
+++ grass/trunk/vector/v.in.dwg/v.in.dwg.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,36 @@
+<h2>DESCRIPTION</h2>
+
+<em>v.in.dwg</em> imports DWG/DXF file into GRASS.
+
+<h2>EXAMPLE</h2>
+<div class="code"><pre>
+v.in.dwg input=map.dwg output=map
+</pre></div>
+
+<h2>NOTES</h2>
+
+v.in.dwg requires OpenDWG toolkit. To get this toolkit you must become at
+least "Associate Member" of OpenDWG Alliance (http://www.opendesign.com/).
+<P>
+The toolkit, for example <tt>ad27linx.tar</tt>, unpack in a directory
+(e.g. /home/usr1/opendwg27) and use the related <tt>configure</tt> options
+to tell GRASS about it:
+
+<div class="code"><pre>
+ ./configure \
+ ... \
+ --with-opendwg \
+ --with-opendwg-includes=/home/usr1/opendwg27 \
+ --with-opendwg-libs=/home/usr1/opendwg27
+</pre></div>
+
+Then you can compile this module.
+<P>
+Not all entity types are supported (warning printed).
+
+
+<h2>AUTHOR</h2>
+
+Radim Blazek, ITC-Irst, Trento, Italy
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/vector/v.in.dxf/description.html
===================================================================
--- grass/trunk/vector/v.in.dxf/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/vector/v.in.dxf/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,48 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-Standard DXF is imported. The following graphical objects are supported:
-
-<ul>
-<li>GRASS point type:</li>
- <ul>
- <li><B>DXF POINT</B></li>
- </ul>
-<li>GRASS line type:</li>
- <ul>
- <li><B>DXF LINE</B></li>
- <li><B>DXF POLYLINE</B></li>
- <li><B>DXF LWPOLYLINE</B></li>
- <li><B>DXF ARC</B></li>
- <li><B>DXF CIRCLE</B></li>
- <li><B>DXF TEXT</B></li>
- </ul>
-<li>GRASS face type:</li>
- <ul>
- <li><B>DXF POLYFACE MESHES</B></li>
- <li><B>DXF 3DFACE</B></li>
- </ul>
-</ul>
-
-Capital column names are changed to lowercase characters as for easier
-SQL usage (lowercase column names avoid the need to quote them if the
-attribute table is stored in a SQL DBMS such as PostgreSQL).
-
-<H2>REFERENCES</H2>
-
-<a href="http://en.wikipedia.org/wiki/AutoCAD_DXF">AutoCad DXF</a> (from Wikipedia, the free encyclopedia)
-
-<H2>SEE ALSO</H2>
-
-<EM><A HREF="v.out.dxf.html">v.out.dxf</A></EM>,
-<EM><a href="vectorintro.html">Introduction to GRASS vector map processing</a></EM>
-
-
-<H2>AUTHORS</H2>
-
-Original written by Chuck Ehlschlaeger, 6/1989<BR>
-Revised by Dave Gerdes, 12/1989<BR>
-US Army Construction Engineering Research Lab
-<P>
-Updated for GRASS 6 and 3D support. Huidae Cho, 3/2006
-
-<P><I>Last changed: $Date$</I>
Copied: grass/trunk/vector/v.in.dxf/v.in.dxf.html (from rev 32770, grass/trunk/vector/v.in.dxf/description.html)
===================================================================
--- grass/trunk/vector/v.in.dxf/v.in.dxf.html (rev 0)
+++ grass/trunk/vector/v.in.dxf/v.in.dxf.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,48 @@
+<h2>DESCRIPTION</h2>
+
+Standard DXF is imported. The following graphical objects are supported:
+
+<ul>
+<li>GRASS point type:</li>
+ <ul>
+ <li><B>DXF POINT</B></li>
+ </ul>
+<li>GRASS line type:</li>
+ <ul>
+ <li><B>DXF LINE</B></li>
+ <li><B>DXF POLYLINE</B></li>
+ <li><B>DXF LWPOLYLINE</B></li>
+ <li><B>DXF ARC</B></li>
+ <li><B>DXF CIRCLE</B></li>
+ <li><B>DXF TEXT</B></li>
+ </ul>
+<li>GRASS face type:</li>
+ <ul>
+ <li><B>DXF POLYFACE MESHES</B></li>
+ <li><B>DXF 3DFACE</B></li>
+ </ul>
+</ul>
+
+Capital column names are changed to lowercase characters as for easier
+SQL usage (lowercase column names avoid the need to quote them if the
+attribute table is stored in a SQL DBMS such as PostgreSQL).
+
+<H2>REFERENCES</H2>
+
+<a href="http://en.wikipedia.org/wiki/AutoCAD_DXF">AutoCad DXF</a> (from Wikipedia, the free encyclopedia)
+
+<H2>SEE ALSO</H2>
+
+<EM><A HREF="v.out.dxf.html">v.out.dxf</A></EM>,
+<EM><a href="vectorintro.html">Introduction to GRASS vector map processing</a></EM>
+
+
+<H2>AUTHORS</H2>
+
+Original written by Chuck Ehlschlaeger, 6/1989<BR>
+Revised by Dave Gerdes, 12/1989<BR>
+US Army Construction Engineering Research Lab
+<P>
+Updated for GRASS 6 and 3D support. Huidae Cho, 3/2006
+
+<P><I>Last changed: $Date$</I>
Deleted: grass/trunk/vector/v.in.ogr/description.html
===================================================================
--- grass/trunk/vector/v.in.ogr/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/vector/v.in.ogr/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,232 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>v.in.ogr</em> converts
-<a href="http://www.gdal.org/ogr/">OGR</a> vectors to GRASS.
-OGR (Simple Features Library) is part of the
-<a href="http://www.gdal.org">GDAL</a> library, so you need to
-install GDAL to use <em>v.in.ogr</em>.
-<P>
-If the <b>layer</b> parameter is not given, all available layers
-are imported.
-<P>
-The optional <b>spatial</b> parameter defines spatial query extents.
-This parameter allows the user to restrict the region to a spatial subset
-while importing the data. All vector features completely or partially
-falling into this rectangle subregion are imported.
-The <b>-r</b> current region flag is identical, but uses the current region
-settings as the spatial bounds (see <em><a href="g.region.html">g.region</a></em>).
-<P>
-Topology cleaning on areas is automatically performed, but may fail in
-special cases (then use <a href="v.clean.html">v.clean</a>).
-
-<h3>Supported OGR Vector Formats</h3>
-
-<a href="http://www.gdal.org/ogr/drv_shapefile.html">ESRI
-Shapefile</a><br>
-<a href="http://www.gdal.org/ogr/drv_mitab.html">Mapinfo File</a>
-
-<p>
-Further available drivers such as UK .NTF, SDTS, TIGER, IHO S-57 (ENC),
-DGN, GML, AVCBin, REC, Memory, OGDI, and PostgreSQL depend on the local
-installation (OGR library), for details see
-<a href="http://www.gdal.org/ogr/ogr_formats.html">OGR web site</a>.
-
-
-<H2>Location Creation</H2>
-
-<em>v.in.ogr</em> attempts to preserve projection information when importing
-datasets if the source format includes projection information, and if
-the OGR driver supports it. If the projection of the source dataset does
-not match the projection of the current location <em>v.in.ogr</em> will
-report an error message ("<tt>Projection of dataset does not appear to
-match current location</tt>") and then report the PROJ_INFO parameters of
-the source dataset.
-
-<P>
-If the user wishes to ignore the difference between the apparent coordinate
-system of the source data and the current location, they may pass the
-<b>-o</b> flag to override the projection check.
-
-<P>
-If the user wishes to import the data with the full projection definition,
-it is possible to have <em>v.in.ogr</em> automatically create a new location based
-on the projection and extents of the file being read. This is accomplished
-by passing the name to be used for the new location via the <b>location</b>
-parameter. Upon completion of the command, a new location will have been
-created (with only a PERMANENT mapset), and the vector map will have been
-imported with the indicated <b>output</b> name into the PERMANENT mapset.
-
-
-<h2>EXAMPLES</h2>
-
-The command imports various vector formats:
-
-<ul>
-<li><B>SHAPE files</B>
-<div class="code"><pre>
-v.in.ogr dsn=/home/user/shape_data/test_shape.shp output=grass_map
-</pre></div>
-
-Alternate method:
-<div class="code"><pre>
-v.in.ogr dsn=/home/user/shape_data layer=test_shape output=grass_map
-</pre></div>
-<BR>
-
-<li><B>MapInfo files</B>
-<div class="code"><pre>
-v.in.ogr dsn=./ layer=mapinfo_test output=grass_map
-</pre></div>
-<BR>
-
-<li><B>Arc Coverage</B><BR>
- We import the Arcs and Label points, the module takes care to
- build areas:<br>
-<div class="code"><pre>
-v.in.ogr dsn=gemeinden layer=LAB,ARC type=centroid,boundary output=mymap
-</pre></div>
-<BR>
-
-<li><B>E00 file</B> (see also <em><a href="v.in.e00.html">v.in.e00</a></em>)<BR>
- First we have to convert the E00 file to an Arc Coverage with 'avcimport'
- (<a href="http://avce00.maptools.org/avce00/index.html">AVCE00 tools</a>,
- use <em>e00conv</em> first in case that <em>avcimport</em> fails):<br>
-<div class="code"><pre>
-avcimport e00file coverage
-v.in.ogr dsn=coverage layer=LAB,ARC type=centroid,boundary output=mymap
-</pre></div>
-<BR>
-
-<li><B>SDTS files</B> (you have to select the CATD file)<BR>
-<div class="code"><pre>
-v.in.ogr dsn=CITXCATD.DDF output=cities
-</pre></div>
-<BR>
-
-<li><B>TIGER files</B><BR>
-<div class="code"><pre>
-v.in.ogr dsn=input/2000/56015/ layer=CompleteChain,PIP output=t56015_all \
-type=boundary,centroid snap=-1
-</pre></div>
-<BR>
-
-<li><B>PostGIS maps</B> (area example)<BR>
-<div class="code"><pre>
-v.in.ogr dsn="PG:host=localhost dbname=postgis user=postgres" layer=polymap \
-output=polygons type=boundary,centroid
-</pre></div>
-<BR>
-
-<li><B>Oracle Spatial maps </B><BR>
-Note that you have to set the environment-variables <tt>ORACLE_BASE,
-ORACLE_SID, ORACLE_HOME</tt> and <tt>TNS_ADMIN</tt> accordingly.
-<div class="code"><pre>
-v.in.ogr dsn=OCI:username/password at database_instance output=grasslayer layer=roads_oci
-</pre></div>
-</ul>
-
-<h3>Support of database schema:</h3>
-
-<P>
-For schema support, first set a default schema with
-<em><a href="db.connect.html">db.connect</a></em>. If schema support is
-used the schema name must be specified whenever a db.* module is called.
-<P>
-Example:
-<div class="code"><pre>
-db.connect driver=pg database=test schema=user1 group=group1
-db.login driver=pg database=test user=user1 password=pwd1
-v.in.ogr dsn=./ layer=river output=river # -> table user1.river
-db.select table=user1.river
-</pre></div>
-
-The user can ignore schemas, if desired:
-<div class="code"><pre>
-db.connect driver=pg database=test
-db.login driver=pg database=test user=user1 password=pwd1
-v.in.ogr dsn=./ layer=river output=river # -> table public.river
-db.select table=river
-</pre></div>
-
-
-<h2>NOTES</h2>
-
-The characters used for table column names are limited. Supported are:<br>
-<div class="code"><pre>
-[A-Za-z][A-Za-z0-9_]*
-</pre></div>
-
-This means that SQL neither supports '.' (dots) nor '-' (minus) nor '#' in table
-column names. Also a table name must start with a character, not a number.
-<br>
-<em>v.in.ogr</em> converts '.', '-' and '#' to '_' (underscore) during import.
-The <em>-w</em> flag changes capital column names to lowercase characters as
-a convenience for SQL usage (lowercase column names avoid the need to quote them
-if the attribute table is stored in a SQL DBMS such as PostgreSQL).
-The <b>cnames</b> parameter is used to define new column names during import.
-
-<P>
-The DBF database specification limits column names to 10 characters.
-If the default DB is set to DBF and the input data contains longer
-column/field names, they will be truncated. If this results in multiple
-columns with the same name then <em>v.in.ogr</em> will produce an error.
-In this case you will either have to modify the input data or use
-<em>v.in.ogr</em>'s <b>cnames</b> parameter to rename columns to something
-unique. (hint: copy and modify the list given with the error message).
-Alternatively, change the local DB with
-<em><a href="db.connect.html">db.connect</a></em>.
-
-
-<h2>WARNINGS</h2>
-
-If a message like "<tt>WARNING: Area size 1.3e-06, area not imported.</tt>"
-appears, the <b>min_area</b> may be adjusted to a smaller value so that all
-areas are imported. Otherwise tiny areas are filtered out during import
-(useful to polish digitization errors or non-topological data).
-
-<h2>ERROR MESSAGES</h2>
-
-<i>"ERROR: DBMI-DBF driver error:
-SQL parser error: syntax error, unexpected DESC, expecting NAME processing 'DESC'"</i><br>
-
-indicates that a column name corresponds to a reserved SQL word (here: 'DESC').
-A different column name should be used. The <em>cnames</em> parameter can be used
-to assign different column names on the fly.
-
-<p>
-<i>"ERROR: Projection of dataset does not appear to match the current location."</i><br>
-
-You need to create a location whose projection matches the data you
-wish to import. Try using <em>location</em> parameter to create a new location based
-upon the projection information in the file. If desired, you can then re-project
-it to another location with <em>v.proj</em>.
-
-<H2>REFERENCES</H2>
-
-<a href="http://www.gdal.org/ogr/">OGR vector library</a> <br>
-<a href="http://www.gdal.org/ogr/ogr__api_8h.html">OGR vector library C API</a> documentation
-
-
-<h2>SEE ALSO</h2>
-
-<em>
-<a HREF="db.connect.html">db.connect</a>,
-<a HREF="v.clean.html">v.clean</a>,
-<a HREF="v.build.polylines.html">v.build.polylines</a>,
-<a HREF="v.edit.html">v.edit</a>,
-<a HREF="v.external.html">v.external</a>,
-<a href="v.in.db.html">v.in.db</a>,
-<a href="v.in.e00.html">v.in.e00</a>,
-<a HREF="v.out.ogr.html">v.out.ogr</a>,<br>
-<a HREF="grass-pg.html">PostGIS driver</a>
-</em>
-
-
-<h2>AUTHOR</h2>
-
-Radim Blazek, ITC-irst, Trento, Italy
-<br>
-Location and spatial extent support by Markus Neteler and Paul Kelly
-
-<p>
-<i>Last changed: $Date$</i>
Copied: grass/trunk/vector/v.in.ogr/v.in.ogr.html (from rev 32770, grass/trunk/vector/v.in.ogr/description.html)
===================================================================
--- grass/trunk/vector/v.in.ogr/v.in.ogr.html (rev 0)
+++ grass/trunk/vector/v.in.ogr/v.in.ogr.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,232 @@
+<h2>DESCRIPTION</h2>
+
+<em>v.in.ogr</em> converts
+<a href="http://www.gdal.org/ogr/">OGR</a> vectors to GRASS.
+OGR (Simple Features Library) is part of the
+<a href="http://www.gdal.org">GDAL</a> library, so you need to
+install GDAL to use <em>v.in.ogr</em>.
+<P>
+If the <b>layer</b> parameter is not given, all available layers
+are imported.
+<P>
+The optional <b>spatial</b> parameter defines spatial query extents.
+This parameter allows the user to restrict the region to a spatial subset
+while importing the data. All vector features completely or partially
+falling into this rectangle subregion are imported.
+The <b>-r</b> current region flag is identical, but uses the current region
+settings as the spatial bounds (see <em><a href="g.region.html">g.region</a></em>).
+<P>
+Topology cleaning on areas is automatically performed, but may fail in
+special cases (then use <a href="v.clean.html">v.clean</a>).
+
+<h3>Supported OGR Vector Formats</h3>
+
+<a href="http://www.gdal.org/ogr/drv_shapefile.html">ESRI
+Shapefile</a><br>
+<a href="http://www.gdal.org/ogr/drv_mitab.html">Mapinfo File</a>
+
+<p>
+Further available drivers such as UK .NTF, SDTS, TIGER, IHO S-57 (ENC),
+DGN, GML, AVCBin, REC, Memory, OGDI, and PostgreSQL depend on the local
+installation (OGR library), for details see
+<a href="http://www.gdal.org/ogr/ogr_formats.html">OGR web site</a>.
+
+
+<H2>Location Creation</H2>
+
+<em>v.in.ogr</em> attempts to preserve projection information when importing
+datasets if the source format includes projection information, and if
+the OGR driver supports it. If the projection of the source dataset does
+not match the projection of the current location <em>v.in.ogr</em> will
+report an error message ("<tt>Projection of dataset does not appear to
+match current location</tt>") and then report the PROJ_INFO parameters of
+the source dataset.
+
+<P>
+If the user wishes to ignore the difference between the apparent coordinate
+system of the source data and the current location, they may pass the
+<b>-o</b> flag to override the projection check.
+
+<P>
+If the user wishes to import the data with the full projection definition,
+it is possible to have <em>v.in.ogr</em> automatically create a new location based
+on the projection and extents of the file being read. This is accomplished
+by passing the name to be used for the new location via the <b>location</b>
+parameter. Upon completion of the command, a new location will have been
+created (with only a PERMANENT mapset), and the vector map will have been
+imported with the indicated <b>output</b> name into the PERMANENT mapset.
+
+
+<h2>EXAMPLES</h2>
+
+The command imports various vector formats:
+
+<ul>
+<li><B>SHAPE files</B>
+<div class="code"><pre>
+v.in.ogr dsn=/home/user/shape_data/test_shape.shp output=grass_map
+</pre></div>
+
+Alternate method:
+<div class="code"><pre>
+v.in.ogr dsn=/home/user/shape_data layer=test_shape output=grass_map
+</pre></div>
+<BR>
+
+<li><B>MapInfo files</B>
+<div class="code"><pre>
+v.in.ogr dsn=./ layer=mapinfo_test output=grass_map
+</pre></div>
+<BR>
+
+<li><B>Arc Coverage</B><BR>
+ We import the Arcs and Label points, the module takes care to
+ build areas:<br>
+<div class="code"><pre>
+v.in.ogr dsn=gemeinden layer=LAB,ARC type=centroid,boundary output=mymap
+</pre></div>
+<BR>
+
+<li><B>E00 file</B> (see also <em><a href="v.in.e00.html">v.in.e00</a></em>)<BR>
+ First we have to convert the E00 file to an Arc Coverage with 'avcimport'
+ (<a href="http://avce00.maptools.org/avce00/index.html">AVCE00 tools</a>,
+ use <em>e00conv</em> first in case that <em>avcimport</em> fails):<br>
+<div class="code"><pre>
+avcimport e00file coverage
+v.in.ogr dsn=coverage layer=LAB,ARC type=centroid,boundary output=mymap
+</pre></div>
+<BR>
+
+<li><B>SDTS files</B> (you have to select the CATD file)<BR>
+<div class="code"><pre>
+v.in.ogr dsn=CITXCATD.DDF output=cities
+</pre></div>
+<BR>
+
+<li><B>TIGER files</B><BR>
+<div class="code"><pre>
+v.in.ogr dsn=input/2000/56015/ layer=CompleteChain,PIP output=t56015_all \
+type=boundary,centroid snap=-1
+</pre></div>
+<BR>
+
+<li><B>PostGIS maps</B> (area example)<BR>
+<div class="code"><pre>
+v.in.ogr dsn="PG:host=localhost dbname=postgis user=postgres" layer=polymap \
+output=polygons type=boundary,centroid
+</pre></div>
+<BR>
+
+<li><B>Oracle Spatial maps </B><BR>
+Note that you have to set the environment-variables <tt>ORACLE_BASE,
+ORACLE_SID, ORACLE_HOME</tt> and <tt>TNS_ADMIN</tt> accordingly.
+<div class="code"><pre>
+v.in.ogr dsn=OCI:username/password at database_instance output=grasslayer layer=roads_oci
+</pre></div>
+</ul>
+
+<h3>Support of database schema:</h3>
+
+<P>
+For schema support, first set a default schema with
+<em><a href="db.connect.html">db.connect</a></em>. If schema support is
+used the schema name must be specified whenever a db.* module is called.
+<P>
+Example:
+<div class="code"><pre>
+db.connect driver=pg database=test schema=user1 group=group1
+db.login driver=pg database=test user=user1 password=pwd1
+v.in.ogr dsn=./ layer=river output=river # -> table user1.river
+db.select table=user1.river
+</pre></div>
+
+The user can ignore schemas, if desired:
+<div class="code"><pre>
+db.connect driver=pg database=test
+db.login driver=pg database=test user=user1 password=pwd1
+v.in.ogr dsn=./ layer=river output=river # -> table public.river
+db.select table=river
+</pre></div>
+
+
+<h2>NOTES</h2>
+
+The characters used for table column names are limited. Supported are:<br>
+<div class="code"><pre>
+[A-Za-z][A-Za-z0-9_]*
+</pre></div>
+
+This means that SQL neither supports '.' (dots) nor '-' (minus) nor '#' in table
+column names. Also a table name must start with a character, not a number.
+<br>
+<em>v.in.ogr</em> converts '.', '-' and '#' to '_' (underscore) during import.
+The <em>-w</em> flag changes capital column names to lowercase characters as
+a convenience for SQL usage (lowercase column names avoid the need to quote them
+if the attribute table is stored in a SQL DBMS such as PostgreSQL).
+The <b>cnames</b> parameter is used to define new column names during import.
+
+<P>
+The DBF database specification limits column names to 10 characters.
+If the default DB is set to DBF and the input data contains longer
+column/field names, they will be truncated. If this results in multiple
+columns with the same name then <em>v.in.ogr</em> will produce an error.
+In this case you will either have to modify the input data or use
+<em>v.in.ogr</em>'s <b>cnames</b> parameter to rename columns to something
+unique. (hint: copy and modify the list given with the error message).
+Alternatively, change the local DB with
+<em><a href="db.connect.html">db.connect</a></em>.
+
+
+<h2>WARNINGS</h2>
+
+If a message like "<tt>WARNING: Area size 1.3e-06, area not imported.</tt>"
+appears, the <b>min_area</b> may be adjusted to a smaller value so that all
+areas are imported. Otherwise tiny areas are filtered out during import
+(useful to polish digitization errors or non-topological data).
+
+<h2>ERROR MESSAGES</h2>
+
+<i>"ERROR: DBMI-DBF driver error:
+SQL parser error: syntax error, unexpected DESC, expecting NAME processing 'DESC'"</i><br>
+
+indicates that a column name corresponds to a reserved SQL word (here: 'DESC').
+A different column name should be used. The <em>cnames</em> parameter can be used
+to assign different column names on the fly.
+
+<p>
+<i>"ERROR: Projection of dataset does not appear to match the current location."</i><br>
+
+You need to create a location whose projection matches the data you
+wish to import. Try using <em>location</em> parameter to create a new location based
+upon the projection information in the file. If desired, you can then re-project
+it to another location with <em>v.proj</em>.
+
+<H2>REFERENCES</H2>
+
+<a href="http://www.gdal.org/ogr/">OGR vector library</a> <br>
+<a href="http://www.gdal.org/ogr/ogr__api_8h.html">OGR vector library C API</a> documentation
+
+
+<h2>SEE ALSO</h2>
+
+<em>
+<a HREF="db.connect.html">db.connect</a>,
+<a HREF="v.clean.html">v.clean</a>,
+<a HREF="v.build.polylines.html">v.build.polylines</a>,
+<a HREF="v.edit.html">v.edit</a>,
+<a HREF="v.external.html">v.external</a>,
+<a href="v.in.db.html">v.in.db</a>,
+<a href="v.in.e00.html">v.in.e00</a>,
+<a HREF="v.out.ogr.html">v.out.ogr</a>,<br>
+<a HREF="grass-pg.html">PostGIS driver</a>
+</em>
+
+
+<h2>AUTHOR</h2>
+
+Radim Blazek, ITC-irst, Trento, Italy
+<br>
+Location and spatial extent support by Markus Neteler and Paul Kelly
+
+<p>
+<i>Last changed: $Date$</i>
Deleted: grass/trunk/vector/v.in.region/description.html
===================================================================
--- grass/trunk/vector/v.in.region/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/vector/v.in.region/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,14 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>v.in.region</em> creates a new vector map from current region.
-
-<h2>SEE ALSO</h2>
-
-<em><a HREF="g.region.html">g.region</a></em><br>
-<em><a HREF="d.vect.html">d.vect</a></em><br>
-
-<h2>AUTHOR</h2>
-
-Radim Blazek
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/vector/v.in.region/v.in.region.html (from rev 32770, grass/trunk/vector/v.in.region/description.html)
===================================================================
--- grass/trunk/vector/v.in.region/v.in.region.html (rev 0)
+++ grass/trunk/vector/v.in.region/v.in.region.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,14 @@
+<h2>DESCRIPTION</h2>
+
+<em>v.in.region</em> creates a new vector map from current region.
+
+<h2>SEE ALSO</h2>
+
+<em><a HREF="g.region.html">g.region</a></em><br>
+<em><a HREF="d.vect.html">d.vect</a></em><br>
+
+<h2>AUTHOR</h2>
+
+Radim Blazek
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/vector/v.in.sites/description.html
===================================================================
--- grass/trunk/vector/v.in.sites/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/vector/v.in.sites/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,37 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>v.in.sites</em> converts GRASS site_lists file into vector format.
-<em>Site_lists</em> file values are used as category values.
-
-<h2>NOTE</h2>
-
-The requirements of the site_lists file are standard
-(i.e., a regular site_lists file format is required)
-
-<div class="code"><pre>
-name|test
-desc|Imported from points shapefile test.shp.
-time|3 Feb 2003 15:09:11 +0000
-3571629.904|5943214.399|#1
-3571323.64|5944517.464|#2
-</pre></div>
-
-<b>Format example of old GRASS site_lists</b><br>
-<div class="code"><pre>
-easting|northing|[z|[d4|]...][#category_int] [ [@attr_text OR %flt] ... ]
-</pre></div>
-
-In case of a 3D sites file, the module generates a 3D vector map.
-Attributes are written into an attribute table.
-
-<h2>EXAMPLE</h2>
-<div class="code"><pre>
-v.in.sites in=sites_file out=vector_map
-</pre></div>
-
-<h2>AUTHOR</h2>
-
-R.L. Glenn, USDA, SCS, NHQ-CGIS <br>
-Radim Blazek, ITC-Irst, Trento, Italy
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/vector/v.in.sites/v.in.sites.html (from rev 32770, grass/trunk/vector/v.in.sites/description.html)
===================================================================
--- grass/trunk/vector/v.in.sites/v.in.sites.html (rev 0)
+++ grass/trunk/vector/v.in.sites/v.in.sites.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,37 @@
+<h2>DESCRIPTION</h2>
+
+<em>v.in.sites</em> converts GRASS site_lists file into vector format.
+<em>Site_lists</em> file values are used as category values.
+
+<h2>NOTE</h2>
+
+The requirements of the site_lists file are standard
+(i.e., a regular site_lists file format is required)
+
+<div class="code"><pre>
+name|test
+desc|Imported from points shapefile test.shp.
+time|3 Feb 2003 15:09:11 +0000
+3571629.904|5943214.399|#1
+3571323.64|5944517.464|#2
+</pre></div>
+
+<b>Format example of old GRASS site_lists</b><br>
+<div class="code"><pre>
+easting|northing|[z|[d4|]...][#category_int] [ [@attr_text OR %flt] ... ]
+</pre></div>
+
+In case of a 3D sites file, the module generates a 3D vector map.
+Attributes are written into an attribute table.
+
+<h2>EXAMPLE</h2>
+<div class="code"><pre>
+v.in.sites in=sites_file out=vector_map
+</pre></div>
+
+<h2>AUTHOR</h2>
+
+R.L. Glenn, USDA, SCS, NHQ-CGIS <br>
+Radim Blazek, ITC-Irst, Trento, Italy
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/vector/v.info/description.html
===================================================================
--- grass/trunk/vector/v.info/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/vector/v.info/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,45 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>v.info</em> reports some basic information about a
-user-specified vector map layer and the topology status.
-
-<h2>EXAMPLE</h2>
-
-<div class="code"><pre>
-v.info map=test
-
- +----------------------------------------------------------------------------+
- | Mapset: PERMANENT Organization: GRASS Team |
- | Layer: test Source Date: |
- | Orig. Scale: 1:1 |
- | Location: spearfish Name of creator: GRASSUSER |
- | DataBase: /home/user/grassdata |
- | Title: |
- | Map format: native |
- |----------------------------------------------------------------------------|
- | Type of Map: Vector (level: 2) |
- | Number of points: 7 |
- | Number of lines: 1386 |
- | Number of centroids: 0 |
- | Number of areas: 0 |
- | Number of faces: 0 |
- | Number of kernels: 0 |
- | Number of islands: 0 |
- | Map is 3D: 0 |
- | Number of dblinks: 1 |
- | Projection: Transverse Mercator (zone 0) |
- | N: 5945486.383 S: 5941117.075 |
- | E: 3573006.924 W: 3567822.941 |
- | B: 0.000 T: 0.000 |
- | |
- | Digitize threshold: 0.00000 |
- | Comments: |
- | |
- +----------------------------------------------------------------------------+
-</pre></div>
-
-<h2>AUTHOR</h2>
-
-Radim Blazek, ITC-Irst, Trento, Italy
-
-<p><i>Last changed: $Date$</i></p>
Copied: grass/trunk/vector/v.info/v.info.html (from rev 32770, grass/trunk/vector/v.info/description.html)
===================================================================
--- grass/trunk/vector/v.info/v.info.html (rev 0)
+++ grass/trunk/vector/v.info/v.info.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,45 @@
+<h2>DESCRIPTION</h2>
+
+<em>v.info</em> reports some basic information about a
+user-specified vector map layer and the topology status.
+
+<h2>EXAMPLE</h2>
+
+<div class="code"><pre>
+v.info map=test
+
+ +----------------------------------------------------------------------------+
+ | Mapset: PERMANENT Organization: GRASS Team |
+ | Layer: test Source Date: |
+ | Orig. Scale: 1:1 |
+ | Location: spearfish Name of creator: GRASSUSER |
+ | DataBase: /home/user/grassdata |
+ | Title: |
+ | Map format: native |
+ |----------------------------------------------------------------------------|
+ | Type of Map: Vector (level: 2) |
+ | Number of points: 7 |
+ | Number of lines: 1386 |
+ | Number of centroids: 0 |
+ | Number of areas: 0 |
+ | Number of faces: 0 |
+ | Number of kernels: 0 |
+ | Number of islands: 0 |
+ | Map is 3D: 0 |
+ | Number of dblinks: 1 |
+ | Projection: Transverse Mercator (zone 0) |
+ | N: 5945486.383 S: 5941117.075 |
+ | E: 3573006.924 W: 3567822.941 |
+ | B: 0.000 T: 0.000 |
+ | |
+ | Digitize threshold: 0.00000 |
+ | Comments: |
+ | |
+ +----------------------------------------------------------------------------+
+</pre></div>
+
+<h2>AUTHOR</h2>
+
+Radim Blazek, ITC-Irst, Trento, Italy
+
+<p><i>Last changed: $Date$</i></p>
Deleted: grass/trunk/vector/v.kcv/description.html
===================================================================
--- grass/trunk/vector/v.kcv/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/vector/v.kcv/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,48 +0,0 @@
-<H2>DESCRIPTION</H2>
- <I>v.kcv</I> randomly divides a points lists into <I>k</I> sets of
- test/train data (for <B>k</B>-fold <B>c</B>ross <B>v</B>alidation).
- Test partitions are mutually exclusive. That is, a point will
- appear in only one test partition and <I>k-1</I> training partitions.
-
- The program generates a random point using the selected
- random number generator and then finds the closest point to
- it. This site is removed from the candidate list (meaning
- that it will not be selected for any other test set) and
- saved in the first test partition file. This is repeated
- until enough points have been selected for the test partition.
- The number of points chosen for test partitions
- depends upon the number of sites available and the number
- of partitions chosen (this number is made as consistent as
- possible while ensuring that all sites will be chosen for
- testing). This process of filling up a test partition is
- done <I>k</I> times.
-
-<H2>NOTES</H2>
- An ideal random sites generator will follow a Poisson dis
- <!-- BUG: missing text -->
- only be as random as the original points. This program
- simply divides points up in a random manner.<p>
-
- Be warned that random number generation occurs over the
- intervals defined by the region of the map.<p>
-
- This program may not work properly with Lat-long data.
-
-<H2>SEE ALSO</H2>
-<I><a href=v.random.html>v.random</a></I> and
-<I><a href=g.region.html>g.region</a></I>
-
-
-<H2>AUTHOR</H2>
-
-<A HREF="http://mccauley-usa.com/">James Darrell McCauley</A>
-<A HREF="mailto:darrell at mccauley-usa.com"><darrell at mccauley-usa.com></A>,
-<br>when he was at:
-<A HREF="http://ABE.www.ecn.purdue.edu/ABE/">Agricultural
-Engineering</A>
-<A HREF="http://www.purdue.edu/">Purdue University</A>
-
-<P>
-Update to 5.7 Radim Blazek 10 / 2004
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/vector/v.kcv/v.kcv.html (from rev 32770, grass/trunk/vector/v.kcv/description.html)
===================================================================
--- grass/trunk/vector/v.kcv/v.kcv.html (rev 0)
+++ grass/trunk/vector/v.kcv/v.kcv.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,48 @@
+<H2>DESCRIPTION</H2>
+ <I>v.kcv</I> randomly divides a points lists into <I>k</I> sets of
+ test/train data (for <B>k</B>-fold <B>c</B>ross <B>v</B>alidation).
+ Test partitions are mutually exclusive. That is, a point will
+ appear in only one test partition and <I>k-1</I> training partitions.
+
+ The program generates a random point using the selected
+ random number generator and then finds the closest point to
+ it. This site is removed from the candidate list (meaning
+ that it will not be selected for any other test set) and
+ saved in the first test partition file. This is repeated
+ until enough points have been selected for the test partition.
+ The number of points chosen for test partitions
+ depends upon the number of sites available and the number
+ of partitions chosen (this number is made as consistent as
+ possible while ensuring that all sites will be chosen for
+ testing). This process of filling up a test partition is
+ done <I>k</I> times.
+
+<H2>NOTES</H2>
+ An ideal random sites generator will follow a Poisson dis
+ <!-- BUG: missing text -->
+ only be as random as the original points. This program
+ simply divides points up in a random manner.<p>
+
+ Be warned that random number generation occurs over the
+ intervals defined by the region of the map.<p>
+
+ This program may not work properly with Lat-long data.
+
+<H2>SEE ALSO</H2>
+<I><a href=v.random.html>v.random</a></I> and
+<I><a href=g.region.html>g.region</a></I>
+
+
+<H2>AUTHOR</H2>
+
+<A HREF="http://mccauley-usa.com/">James Darrell McCauley</A>
+<A HREF="mailto:darrell at mccauley-usa.com"><darrell at mccauley-usa.com></A>,
+<br>when he was at:
+<A HREF="http://ABE.www.ecn.purdue.edu/ABE/">Agricultural
+Engineering</A>
+<A HREF="http://www.purdue.edu/">Purdue University</A>
+
+<P>
+Update to 5.7 Radim Blazek 10 / 2004
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/vector/v.kernel/description.html
===================================================================
--- grass/trunk/vector/v.kernel/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/vector/v.kernel/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,33 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-Generates a raster density map from vector points data using
-a moving 2D isotropic Gaussian kernel or
-optionally generates a vector density map on vector network
-with a 1D kernel.
-
-<H2>NOTES</H2>
-
-The <em>mult</em> option is needed to overcome the limitation that
-the resulting density in case of a vector map output is stored as category
-(Integer). The density result stored as category may be multiplied by this number.
-<P>
-With the <em>-o</em> flag (experimental) the command tries to calculate an
-optimal standard deviation. The value of <em>stddeviation</em> is taken
-as maximum value. Standard deviation is calculated using ALL points,
-not just those in the current region.
-
-
-<H2>LIMITATIONS</H2>
-The modules only considers the presence of point, but not
-(yet) any attribute values.
-
-<H2>SEE ALSO</H2>
-<A HREF="v.surf.rst.html">v.surf.rst</A>
-
-<H2>AUTHOR</H2>
-
-Stefano Menegon, <a href=http://mpa.itc.it>ITC-irst</a>, Trento, Italy
-<BR>
-Radim Blazek (network part)
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/vector/v.kernel/v.kernel.html (from rev 32770, grass/trunk/vector/v.kernel/description.html)
===================================================================
--- grass/trunk/vector/v.kernel/v.kernel.html (rev 0)
+++ grass/trunk/vector/v.kernel/v.kernel.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,33 @@
+<H2>DESCRIPTION</H2>
+
+Generates a raster density map from vector points data using
+a moving 2D isotropic Gaussian kernel or
+optionally generates a vector density map on vector network
+with a 1D kernel.
+
+<H2>NOTES</H2>
+
+The <em>mult</em> option is needed to overcome the limitation that
+the resulting density in case of a vector map output is stored as category
+(Integer). The density result stored as category may be multiplied by this number.
+<P>
+With the <em>-o</em> flag (experimental) the command tries to calculate an
+optimal standard deviation. The value of <em>stddeviation</em> is taken
+as maximum value. Standard deviation is calculated using ALL points,
+not just those in the current region.
+
+
+<H2>LIMITATIONS</H2>
+The modules only considers the presence of point, but not
+(yet) any attribute values.
+
+<H2>SEE ALSO</H2>
+<A HREF="v.surf.rst.html">v.surf.rst</A>
+
+<H2>AUTHOR</H2>
+
+Stefano Menegon, <a href=http://mpa.itc.it>ITC-irst</a>, Trento, Italy
+<BR>
+Radim Blazek (network part)
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/vector/v.label/description.html
===================================================================
--- grass/trunk/vector/v.label/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/vector/v.label/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,237 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-<EM>v.label</EM> makes a label-file from a GRASS vector map
-with labels created from attributes in the attached table.
-If no label file name is given, the name of the source map is used.
-
-
-<H2>NOTES</H2>
-
-If the <em>fontsize</em> option is given then the <em>space</em> option
-is determined automatically <em>from the current display window</em>,
-otherwise the <em>space</em> option should be set roughly the same
-as the <em>size</em> option.
-<P>
-
-<BR>
-A description of the labels file follows.<P>
-The file is located in <tt>$MAPSET/paint/labels/</tt>.
-The file is a plain-text ASCII file containing the following fields:
-<BR>
-<h4>Caution: The following information may be incomplete, out of date,
-and wrong!</h4>
-<P>
-The label information that must be provided in the <em>labels</em> file is:
-
-<DL>
-<DT><B>TEXT</B>:
-
-<DD><!--Up to four lines of text.-->
-Lines in multiple line labels will appear one above the next.
-More than one line of text can be specified by notating the end of a
-line with a '<b><tt>\n</tt></b>'.<BR>
-(e.g. <tt>SPEARFISH<b>\n</b>SOUTH DAKOTA)</tt>.
-
-
-<!-- I don't think it exists. -HB 6/2005
-<DT><B>SKIP</B>:
-
-<DD>yes|no. If <EM>no</EM>, label will be printed. If
-<EM>yes</EM>, the label will be retained in the file but
-not printed.
--->
-
-<DT><B>LOCATION</B>:
-
-<DD>Determines where the text will be located on the
-image. The user specifies the easting and northing, and
-(optionally) specifies a vertical and horizontal
-offset from the specified easting/northing.
-These offsets are provided to allow finer placement of labels and
-are measured in local pixels. Thus in
-<a href="d.labels.html"><i>d.labels</i></a> the offset is
-measured in screen pixels, and in <a href="ps.map.html"><i>ps.map</i></a>
-the offset is measured in PostScript points (i.e. 1/72" steps).
-
-
-<DT><B>PLACEMENT</B>:
-
-<DD>Determines which part of the label to which the
-location refers. If placement is unspecified, the label is
-centered (<EM>center</EM>), by default. Label placement
-may be specified as:
-
-<PRE>
- lower left (lower left corner of the text)
- lower right (lower right corner of the text)
- lower center (bottom center of the text)
-
- upper left (upper left corner of the text)
- upper right (upper right corner of the text)
- upper center (top center of the text)
-
- center (center of the text)
-
-</PRE>
-
-
-<DT><B>FONT</B>:
-
-<DD>This specifies the font to use.
-<P>
-The following fonts are available for use with
- <a href="d.labels.html"><i>d.labels</i></a>:
-<P><pre>
- cyrilc gothgbt gothgrt gothitt greekc greekcs greekp greeks
- italicc italiccs italict romanc romancs romand romans romant
- scriptc scripts
-</pre>
-<P>
-Alternatively the path to a FreeType (.ttf) font may be given.
-(for <em>d.labels</em> only)
-<P>
-The word <EM>standard</EM> can be used to specify the default font
-(which is <EM>romans</EM>).
-<P>
-Note <a href="ps.map.html"><em>ps.map</em></a> can override this setting
-to use other fonts. Its default font is Helvetica.
-
-
-<DT><B>TEXT SIZE</B>:
-
-<DD>This determines the size of the letters. The <em>size</em>
-specifies the vertical height of the letters in meters on
-the ground. Thus text will grow or shrink depending on the
-scale at which the map is drawn.
-Alternatively <em>fontsize</em> can set the font size in normal font points.
-
-
-<DT><A NAME="textcolor"><B>TEXT COLOR</B></A>:
-
-<DD>This selects the text color. If unspecified, the
-label's text is drawn in <EM>black</EM>, by default. The
-text color can be specified in one of several ways:
-
-<OL>
-<LI>By color name:
-
-<BR>
-<tt>aqua black blue brown cyan gray green grey indigo
-magenta orange purple red violet white yellow</tt>
-
-<LI>As red, green, blue component values. (0-255)<BR>
-for example: <tt>128:100:200</tt>
-
-<!-- eh?
-<LI>As red, green, blue percentages.
-for example: .5 .4 .7
-<BR>
-(This form is not supported by
-<EM><A HREF="d.labels.html">d.labels</A></EM>.)
-
-<LI>By printer color number to get the exact printer color.
-<BR>
-(This form is not supported by
-<EM><A HREF="d.labels.html">d.labels</A></EM>.)
--->
-
-<LI>Specify "<tt>none</tt>" to suppress the lettering.
-</OL>
-
-
-<DT><B>WIDTH</B>:
-
-<DD>This determines the line thickness of the border box.<BR>
-The maximum value is 25.0.
-
-<DT><B>HIGHLIGHT COLOR</B>:
-
-<DD>The text can be highlighted in another color so that it
-appears to be in two colors. The text is drawn first in
-this color at a wider line width, and then redrawn in the
-text color at the regular line width. No highlight color
-("<tt>none</tt>") is used by default, if unspecified by the
-user. To specify use of no highlight color, specify
-"<tt>none</tt>".
-(See <A HREF="#textcolor">TEXT COLOR</A>
-above for a list of permissible color names.)
-
-
-<DT><B>HIGHLIGHT WIDTH</B>:
-
-<DD>Specifies how far from the text lines (in units of
-pixels) the highlight color should extend. The default
-highlight width is set to <EM>0</EM> (i.e., no highlight
-color).
-
-
-<DT><B>BACKGROUND COLOR</B>:
-
-<DD>Text may be boxed in a solid color by specifying a background color.
-Specify "<tt>none</tt>" for no background. The default background color
-setting, if unspecified by the user, is <EM>white</EM>.
-(See <A HREF="#textcolor">TEXT COLOR</A>
-above for a list of permissible color names.)
-
-
-<DT><B>BORDER COLOR</B>:
-
-<DD>Select a color for the border around the background.
-Specify "<tt>none</tt>" to suppress the border.
-The default border color used, if unspecified, is <EM>black</EM>.
-(See <A HREF="#textcolor">TEXT COLOR</A>
-above for a list of permissible color names.)
-
-
-<DT><B>OPAQUE TO VECTORS</B>:
-
-<DD><EM>yes|no</EM>. This field only has meaning if a
-background color is selected. <EM>yes</EM> will prevent
-vector lines from entering the background. <EM>no</EM>
-will allow vector lines to enter the background. The
-default setting, if unspecified by the user, is
-<EM>yes</EM>.
-
-</DL>
-<BR>
-
-
-<H2>EXAMPLE</H2>
-
-Spearfish example with TrueType font (path may differ):
-
-<div class="code"><pre>
-v.label -a map=roads column=label labels=lroads \
- font=/usr/X11R6/lib/X11/fonts/TTF/luximri.ttf
-d.vect roads
-d.labels lroads
-</pre></div>
-
-Since the label files are simple text files, you can merge them together
-if you like. For example if you set the label colors based on database
-attributes using multiple runs with the <b>where</b> option.
-This example uses the standard UNIX <tt>cat</tt> program.
-
-<div class="code"><pre>
-cd $MAPSET/paint/labels/
-cat file1 file2 file3 file4 > file_all
-</pre></div>
-
-
-
-<H2>SEE ALSO</H2>
-<EM>
-<A HREF="d.labels.html">d.labels</A><br>
-<A HREF="ps.map.html">ps.map</A>
-</EM>
-<br>
-
-
-<H2>AUTHORS</H2>
-
-Philip Verhagen (original s.label)<br>
-Radim Blazek (GRASS 6 port)<br>
-Hamish Bowman (enhancements)<BR>
-
-<p>
-<i>Last changed: $Date$</i>
Copied: grass/trunk/vector/v.label/v.label.html (from rev 32770, grass/trunk/vector/v.label/description.html)
===================================================================
--- grass/trunk/vector/v.label/v.label.html (rev 0)
+++ grass/trunk/vector/v.label/v.label.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,237 @@
+<H2>DESCRIPTION</H2>
+
+<EM>v.label</EM> makes a label-file from a GRASS vector map
+with labels created from attributes in the attached table.
+If no label file name is given, the name of the source map is used.
+
+
+<H2>NOTES</H2>
+
+If the <em>fontsize</em> option is given then the <em>space</em> option
+is determined automatically <em>from the current display window</em>,
+otherwise the <em>space</em> option should be set roughly the same
+as the <em>size</em> option.
+<P>
+
+<BR>
+A description of the labels file follows.<P>
+The file is located in <tt>$MAPSET/paint/labels/</tt>.
+The file is a plain-text ASCII file containing the following fields:
+<BR>
+<h4>Caution: The following information may be incomplete, out of date,
+and wrong!</h4>
+<P>
+The label information that must be provided in the <em>labels</em> file is:
+
+<DL>
+<DT><B>TEXT</B>:
+
+<DD><!--Up to four lines of text.-->
+Lines in multiple line labels will appear one above the next.
+More than one line of text can be specified by notating the end of a
+line with a '<b><tt>\n</tt></b>'.<BR>
+(e.g. <tt>SPEARFISH<b>\n</b>SOUTH DAKOTA)</tt>.
+
+
+<!-- I don't think it exists. -HB 6/2005
+<DT><B>SKIP</B>:
+
+<DD>yes|no. If <EM>no</EM>, label will be printed. If
+<EM>yes</EM>, the label will be retained in the file but
+not printed.
+-->
+
+<DT><B>LOCATION</B>:
+
+<DD>Determines where the text will be located on the
+image. The user specifies the easting and northing, and
+(optionally) specifies a vertical and horizontal
+offset from the specified easting/northing.
+These offsets are provided to allow finer placement of labels and
+are measured in local pixels. Thus in
+<a href="d.labels.html"><i>d.labels</i></a> the offset is
+measured in screen pixels, and in <a href="ps.map.html"><i>ps.map</i></a>
+the offset is measured in PostScript points (i.e. 1/72" steps).
+
+
+<DT><B>PLACEMENT</B>:
+
+<DD>Determines which part of the label to which the
+location refers. If placement is unspecified, the label is
+centered (<EM>center</EM>), by default. Label placement
+may be specified as:
+
+<PRE>
+ lower left (lower left corner of the text)
+ lower right (lower right corner of the text)
+ lower center (bottom center of the text)
+
+ upper left (upper left corner of the text)
+ upper right (upper right corner of the text)
+ upper center (top center of the text)
+
+ center (center of the text)
+
+</PRE>
+
+
+<DT><B>FONT</B>:
+
+<DD>This specifies the font to use.
+<P>
+The following fonts are available for use with
+ <a href="d.labels.html"><i>d.labels</i></a>:
+<P><pre>
+ cyrilc gothgbt gothgrt gothitt greekc greekcs greekp greeks
+ italicc italiccs italict romanc romancs romand romans romant
+ scriptc scripts
+</pre>
+<P>
+Alternatively the path to a FreeType (.ttf) font may be given.
+(for <em>d.labels</em> only)
+<P>
+The word <EM>standard</EM> can be used to specify the default font
+(which is <EM>romans</EM>).
+<P>
+Note <a href="ps.map.html"><em>ps.map</em></a> can override this setting
+to use other fonts. Its default font is Helvetica.
+
+
+<DT><B>TEXT SIZE</B>:
+
+<DD>This determines the size of the letters. The <em>size</em>
+specifies the vertical height of the letters in meters on
+the ground. Thus text will grow or shrink depending on the
+scale at which the map is drawn.
+Alternatively <em>fontsize</em> can set the font size in normal font points.
+
+
+<DT><A NAME="textcolor"><B>TEXT COLOR</B></A>:
+
+<DD>This selects the text color. If unspecified, the
+label's text is drawn in <EM>black</EM>, by default. The
+text color can be specified in one of several ways:
+
+<OL>
+<LI>By color name:
+
+<BR>
+<tt>aqua black blue brown cyan gray green grey indigo
+magenta orange purple red violet white yellow</tt>
+
+<LI>As red, green, blue component values. (0-255)<BR>
+for example: <tt>128:100:200</tt>
+
+<!-- eh?
+<LI>As red, green, blue percentages.
+for example: .5 .4 .7
+<BR>
+(This form is not supported by
+<EM><A HREF="d.labels.html">d.labels</A></EM>.)
+
+<LI>By printer color number to get the exact printer color.
+<BR>
+(This form is not supported by
+<EM><A HREF="d.labels.html">d.labels</A></EM>.)
+-->
+
+<LI>Specify "<tt>none</tt>" to suppress the lettering.
+</OL>
+
+
+<DT><B>WIDTH</B>:
+
+<DD>This determines the line thickness of the border box.<BR>
+The maximum value is 25.0.
+
+<DT><B>HIGHLIGHT COLOR</B>:
+
+<DD>The text can be highlighted in another color so that it
+appears to be in two colors. The text is drawn first in
+this color at a wider line width, and then redrawn in the
+text color at the regular line width. No highlight color
+("<tt>none</tt>") is used by default, if unspecified by the
+user. To specify use of no highlight color, specify
+"<tt>none</tt>".
+(See <A HREF="#textcolor">TEXT COLOR</A>
+above for a list of permissible color names.)
+
+
+<DT><B>HIGHLIGHT WIDTH</B>:
+
+<DD>Specifies how far from the text lines (in units of
+pixels) the highlight color should extend. The default
+highlight width is set to <EM>0</EM> (i.e., no highlight
+color).
+
+
+<DT><B>BACKGROUND COLOR</B>:
+
+<DD>Text may be boxed in a solid color by specifying a background color.
+Specify "<tt>none</tt>" for no background. The default background color
+setting, if unspecified by the user, is <EM>white</EM>.
+(See <A HREF="#textcolor">TEXT COLOR</A>
+above for a list of permissible color names.)
+
+
+<DT><B>BORDER COLOR</B>:
+
+<DD>Select a color for the border around the background.
+Specify "<tt>none</tt>" to suppress the border.
+The default border color used, if unspecified, is <EM>black</EM>.
+(See <A HREF="#textcolor">TEXT COLOR</A>
+above for a list of permissible color names.)
+
+
+<DT><B>OPAQUE TO VECTORS</B>:
+
+<DD><EM>yes|no</EM>. This field only has meaning if a
+background color is selected. <EM>yes</EM> will prevent
+vector lines from entering the background. <EM>no</EM>
+will allow vector lines to enter the background. The
+default setting, if unspecified by the user, is
+<EM>yes</EM>.
+
+</DL>
+<BR>
+
+
+<H2>EXAMPLE</H2>
+
+Spearfish example with TrueType font (path may differ):
+
+<div class="code"><pre>
+v.label -a map=roads column=label labels=lroads \
+ font=/usr/X11R6/lib/X11/fonts/TTF/luximri.ttf
+d.vect roads
+d.labels lroads
+</pre></div>
+
+Since the label files are simple text files, you can merge them together
+if you like. For example if you set the label colors based on database
+attributes using multiple runs with the <b>where</b> option.
+This example uses the standard UNIX <tt>cat</tt> program.
+
+<div class="code"><pre>
+cd $MAPSET/paint/labels/
+cat file1 file2 file3 file4 > file_all
+</pre></div>
+
+
+
+<H2>SEE ALSO</H2>
+<EM>
+<A HREF="d.labels.html">d.labels</A><br>
+<A HREF="ps.map.html">ps.map</A>
+</EM>
+<br>
+
+
+<H2>AUTHORS</H2>
+
+Philip Verhagen (original s.label)<br>
+Radim Blazek (GRASS 6 port)<br>
+Hamish Bowman (enhancements)<BR>
+
+<p>
+<i>Last changed: $Date$</i>
Deleted: grass/trunk/vector/v.label.sa/description.html
===================================================================
--- grass/trunk/vector/v.label.sa/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/vector/v.label.sa/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,40 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-<EM>v.label.sa</EM> makes a label-file from a GRASS vector map
-with labels created from attributes in the attached table. The labels are
-placed in as optimal place as possible. The label file has the same syntax
-as the one created by <A HREF="v.label.html">v.label</A>
-
-
-<H2>EXAMPLE</H2>
-
-Spearfish example:
-<p>
-<div class="code"><pre>
-d.font -L
-v.label.sa roads font=Vera labels=roads_labels column=label
-g.region vect=roads
-d.erase
-d.vect roads
-d.labels roads_labels
-</pre></div>
-
-<H2>REFERENCES</H2>
-Edmondson, Christensen, Marks and Shieber: A General Cartographic
-Labeling Algorithm, Cartographica, Vol. 33, No. 4, Winter 1996, pp. 13-23
-The algorithm works by the principle of Simulated Annealing.
-
-<H2>SEE ALSO</H2>
-<EM>
-<A HREF="v.labels.html">d.label</A><br>
-<A HREF="d.labels.html">d.labels</A><br>
-<A HREF="ps.map.html">ps.map</A>
-<A href="http://en.wikipedia.org/Simulated_Annealing">Wikipedia article on
-simulated annealing</A>
-</EM><br>
-
-<H2>AUTHOR</H2>
-Wolf Bergenheim
-<br>
-<p><i>Last changed: $Date$</i>
-
Copied: grass/trunk/vector/v.label.sa/v.label.sa.html (from rev 32770, grass/trunk/vector/v.label.sa/description.html)
===================================================================
--- grass/trunk/vector/v.label.sa/v.label.sa.html (rev 0)
+++ grass/trunk/vector/v.label.sa/v.label.sa.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,40 @@
+<H2>DESCRIPTION</H2>
+
+<EM>v.label.sa</EM> makes a label-file from a GRASS vector map
+with labels created from attributes in the attached table. The labels are
+placed in as optimal place as possible. The label file has the same syntax
+as the one created by <A HREF="v.label.html">v.label</A>
+
+
+<H2>EXAMPLE</H2>
+
+Spearfish example:
+<p>
+<div class="code"><pre>
+d.font -L
+v.label.sa roads font=Vera labels=roads_labels column=label
+g.region vect=roads
+d.erase
+d.vect roads
+d.labels roads_labels
+</pre></div>
+
+<H2>REFERENCES</H2>
+Edmondson, Christensen, Marks and Shieber: A General Cartographic
+Labeling Algorithm, Cartographica, Vol. 33, No. 4, Winter 1996, pp. 13-23
+The algorithm works by the principle of Simulated Annealing.
+
+<H2>SEE ALSO</H2>
+<EM>
+<A HREF="v.labels.html">d.label</A><br>
+<A HREF="d.labels.html">d.labels</A><br>
+<A HREF="ps.map.html">ps.map</A>
+<A href="http://en.wikipedia.org/Simulated_Annealing">Wikipedia article on
+simulated annealing</A>
+</EM><br>
+
+<H2>AUTHOR</H2>
+Wolf Bergenheim
+<br>
+<p><i>Last changed: $Date$</i>
+
Deleted: grass/trunk/vector/v.lrs/v.lrs.create/description.html
===================================================================
--- grass/trunk/vector/v.lrs/v.lrs.create/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/vector/v.lrs/v.lrs.create/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,157 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>v.lrs.create</em> generates a LRS (Linear Reference System) from
-vector line and point data.
-<p>
-It is highly recommended to work with polylines instead of segmented vector
-lines. The command <em>v.build.polylines</em> creates this map structure.
-
-<h2>NOTES</h2>
-
-The mileposts (point) vector map columns <em>start_mp</em>, <em>start_off</em>,
-<em>end_mp</em>, <em>end_off</em> must be of 'double precision' type. For
-milepost ordering, it is sufficient to enter increasing numbers into the
-<em>start_mp</em> column indicating the order along the vector line.
-<p>
-The <em>lidcol</em> and <em>pidcol</em> columns contain the line IDs which
-relate mileposts and vector line(s) to each other.
-<p>
-When creating a LRS with this module, any existing <em>rstable</em> will be
-replaced.
-
-<h2>EXAMPLE</h2>
-
-This example is written for the Spearfish dataset.
-<p>
-
-As first step, bus route data are prepared.
-
-<div class="code"><pre>
-# break into segments for correct route selection
-v.clean roads_net out=busroute_tmp tool=break
-
-# make polyline for easier line selection by coordinate pairs
-v.build.polylines busroute_tmp out=busroute_tmp2
-
-# reverse delete: reduce route map to bus route (enter in one line)
-v.edit -r busroute_tmp2 tool=delete coords=590273,4927304,\
-590346,4927246,590414,4927210,590438,4927096,590468,4926966,\
-590491,4926848,590566,4926798,590637,4926753,590701,4926698,\
-590830,4926726,590935,4926751,590993,4926830,590972,4926949,\
-590948,4927066,590922,4927182,590957,4927251 thresh=5
-
-# vector line needs to be polyline
-v.build.polylines busroute_tmp2 out=busroute_tmp3
-v.category busroute_tmp3 out=busroute op=add
-g.remove vect=busroute_tmp,busroute_tmp2,busroute_tmp3
-</pre></div>
-
-The result can be visualized:
-<div class="code"><pre>
-g.region vect=busroute n=n+100 s=s-100 w=w-100 e=e+100
-d.mon x0
-d.vect roads_net
-d.vect busroute col=red width=2
-</pre></div>
-
-The vector map 'busroute' needs have an attribute table which contain an integer column
-<em>lidcol</em> with value be '22' for this example (bus route):
-
-<div class="code"><pre>
-v.db.addtable busroute col="lid integer"
-v.db.update busroute col=lid value=22
-v.db.select busroute
-cat|lid
-1|22
-</pre></div>
-
-A new point map 'busstops' shall contain mileposts (bus stops) along
-this line (use <em>thresh</em> to define maximal accepted deviation from this line):
-
-<div class="code"><pre>
-# generate points map
-echo "590263|4927361
-590432|4927120
-590505|4926776
-590660|4926687
-590905|4926742
-590972|4926949
-591019|4927263" | v.in.ascii out=busstops
-
-d.vect busstops icon=basic/triangle col=blue
-d.vect busstops disp=cat lcol=blue
-</pre></div>
-
-The milepost attributes table needs to be created with specific columns:
-
-<div class="code"><pre>
-v.db.addtable busstops col="lid integer, start_mp double precision, \
- start_off double precision, end_mp double precision, \
- end_off double precision"
-v.db.update busstops col=lid value=22
-</pre></div>
-
-Since the digitizing order of v.in.ascii above reflects the bus stop
-order along the route, we can simply copy the category number as milepost
-order number in column <em>start_mp</em>:
-
-<div class="code"><pre>
-v.db.update busstops col=start_mp qcol=cat
-# verify table
-v.db.select busstops
-cat|lid|start_mp|start_off|end_mp|end_off
-1|22|1|||
-2|22|2|||
-3|22|3|||
-4|22|4|||
-5|22|5|||
-6|22|6|||
-7|22|7|||
-
-# visualize with start_mp to check order
-d.erase
-d.vect roads_net
-d.vect busroute col=red width=2
-d.vect busstops icon=basic/triangle col=blue
-d.vect busstops disp=attr attrcol=start_mp lcol=blue
-</pre></div>
-
-Offsets (<em>start_off</em>, <em>end_off</em>) can be later used in case the route or
-mileposts get modified.
-<p>
-
-As second step, the linear reference network is created:
-
-<div class="code"><pre>
-v.lrs.create busroute points=busstops out=route_lrs err=lrs_error \
- lidcol=lid pidcol=lid rstable=route_lrs thresh=50
-</pre></div>
-
-This creates the maps 'route_lrs' containing the LRS and 'lrs_error'
-containing the errors if any. The resulting LRS table and map can
-be shown:
-
-<div class="code"><pre>
-# show LRS table
-db.select route_lrs
-
-d.vect route_lrs col=blue width=2
-</pre></div>
-
-
-<h2>SEE ALSO</h2>
-
-<em><a HREF="lrs.html">LRS tutorial</a></em>,<br>
-<em><a HREF="http://gisws.media.osaka-cu.ac.jp/grass04/viewpaper.php?id=50">Introducing the Linear Reference System in GRASS</a></em>,
-<p>
-<em><a HREF="v.build.polylines.html">v.build.polylines</a></em>,
-<em><a HREF="v.lrs.segment.html">v.lrs.segment</a></em>,
-<em><a HREF="v.lrs.where.html">v.lrs.where</a></em>,
-<em><a HREF="v.lrs.label.html">v.lrs.label</a></em>
-
-<h2>AUTHOR</h2>
-
-Radim Blazek, ITC-irst/MPA Solutions<br>
-Documentation update (based on above journal article and available fragments): Markus Neteler
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/vector/v.lrs/v.lrs.create/v.lrs.create.html (from rev 32770, grass/trunk/vector/v.lrs/v.lrs.create/description.html)
===================================================================
--- grass/trunk/vector/v.lrs/v.lrs.create/v.lrs.create.html (rev 0)
+++ grass/trunk/vector/v.lrs/v.lrs.create/v.lrs.create.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,157 @@
+<h2>DESCRIPTION</h2>
+
+<em>v.lrs.create</em> generates a LRS (Linear Reference System) from
+vector line and point data.
+<p>
+It is highly recommended to work with polylines instead of segmented vector
+lines. The command <em>v.build.polylines</em> creates this map structure.
+
+<h2>NOTES</h2>
+
+The mileposts (point) vector map columns <em>start_mp</em>, <em>start_off</em>,
+<em>end_mp</em>, <em>end_off</em> must be of 'double precision' type. For
+milepost ordering, it is sufficient to enter increasing numbers into the
+<em>start_mp</em> column indicating the order along the vector line.
+<p>
+The <em>lidcol</em> and <em>pidcol</em> columns contain the line IDs which
+relate mileposts and vector line(s) to each other.
+<p>
+When creating a LRS with this module, any existing <em>rstable</em> will be
+replaced.
+
+<h2>EXAMPLE</h2>
+
+This example is written for the Spearfish dataset.
+<p>
+
+As first step, bus route data are prepared.
+
+<div class="code"><pre>
+# break into segments for correct route selection
+v.clean roads_net out=busroute_tmp tool=break
+
+# make polyline for easier line selection by coordinate pairs
+v.build.polylines busroute_tmp out=busroute_tmp2
+
+# reverse delete: reduce route map to bus route (enter in one line)
+v.edit -r busroute_tmp2 tool=delete coords=590273,4927304,\
+590346,4927246,590414,4927210,590438,4927096,590468,4926966,\
+590491,4926848,590566,4926798,590637,4926753,590701,4926698,\
+590830,4926726,590935,4926751,590993,4926830,590972,4926949,\
+590948,4927066,590922,4927182,590957,4927251 thresh=5
+
+# vector line needs to be polyline
+v.build.polylines busroute_tmp2 out=busroute_tmp3
+v.category busroute_tmp3 out=busroute op=add
+g.remove vect=busroute_tmp,busroute_tmp2,busroute_tmp3
+</pre></div>
+
+The result can be visualized:
+<div class="code"><pre>
+g.region vect=busroute n=n+100 s=s-100 w=w-100 e=e+100
+d.mon x0
+d.vect roads_net
+d.vect busroute col=red width=2
+</pre></div>
+
+The vector map 'busroute' needs have an attribute table which contain an integer column
+<em>lidcol</em> with value be '22' for this example (bus route):
+
+<div class="code"><pre>
+v.db.addtable busroute col="lid integer"
+v.db.update busroute col=lid value=22
+v.db.select busroute
+cat|lid
+1|22
+</pre></div>
+
+A new point map 'busstops' shall contain mileposts (bus stops) along
+this line (use <em>thresh</em> to define maximal accepted deviation from this line):
+
+<div class="code"><pre>
+# generate points map
+echo "590263|4927361
+590432|4927120
+590505|4926776
+590660|4926687
+590905|4926742
+590972|4926949
+591019|4927263" | v.in.ascii out=busstops
+
+d.vect busstops icon=basic/triangle col=blue
+d.vect busstops disp=cat lcol=blue
+</pre></div>
+
+The milepost attributes table needs to be created with specific columns:
+
+<div class="code"><pre>
+v.db.addtable busstops col="lid integer, start_mp double precision, \
+ start_off double precision, end_mp double precision, \
+ end_off double precision"
+v.db.update busstops col=lid value=22
+</pre></div>
+
+Since the digitizing order of v.in.ascii above reflects the bus stop
+order along the route, we can simply copy the category number as milepost
+order number in column <em>start_mp</em>:
+
+<div class="code"><pre>
+v.db.update busstops col=start_mp qcol=cat
+# verify table
+v.db.select busstops
+cat|lid|start_mp|start_off|end_mp|end_off
+1|22|1|||
+2|22|2|||
+3|22|3|||
+4|22|4|||
+5|22|5|||
+6|22|6|||
+7|22|7|||
+
+# visualize with start_mp to check order
+d.erase
+d.vect roads_net
+d.vect busroute col=red width=2
+d.vect busstops icon=basic/triangle col=blue
+d.vect busstops disp=attr attrcol=start_mp lcol=blue
+</pre></div>
+
+Offsets (<em>start_off</em>, <em>end_off</em>) can be later used in case the route or
+mileposts get modified.
+<p>
+
+As second step, the linear reference network is created:
+
+<div class="code"><pre>
+v.lrs.create busroute points=busstops out=route_lrs err=lrs_error \
+ lidcol=lid pidcol=lid rstable=route_lrs thresh=50
+</pre></div>
+
+This creates the maps 'route_lrs' containing the LRS and 'lrs_error'
+containing the errors if any. The resulting LRS table and map can
+be shown:
+
+<div class="code"><pre>
+# show LRS table
+db.select route_lrs
+
+d.vect route_lrs col=blue width=2
+</pre></div>
+
+
+<h2>SEE ALSO</h2>
+
+<em><a HREF="lrs.html">LRS tutorial</a></em>,<br>
+<em><a HREF="http://gisws.media.osaka-cu.ac.jp/grass04/viewpaper.php?id=50">Introducing the Linear Reference System in GRASS</a></em>,
+<p>
+<em><a HREF="v.build.polylines.html">v.build.polylines</a></em>,
+<em><a HREF="v.lrs.segment.html">v.lrs.segment</a></em>,
+<em><a HREF="v.lrs.where.html">v.lrs.where</a></em>,
+<em><a HREF="v.lrs.label.html">v.lrs.label</a></em>
+
+<h2>AUTHOR</h2>
+
+Radim Blazek, ITC-irst/MPA Solutions<br>
+Documentation update (based on above journal article and available fragments): Markus Neteler
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/vector/v.lrs/v.lrs.label/description.html
===================================================================
--- grass/trunk/vector/v.lrs/v.lrs.label/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/vector/v.lrs/v.lrs.label/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,36 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>v.lrs.label</em> generates LRS labels for pretty-printing of a LRS.
-
-This example is written for the Spearfish dataset (it continues the example
-from <em>v.lrs.create</em>).
-<p>
-
-
-<div class="code"><pre>
-v.lrs.label route_lrs rstable=route_lrs output=route_lrs_labels \
- labels=labels col=red size=50 xoffset=100
-
-g.region vect=route_lrs n=n+100 s=s-100 -p
-d.erase
-d.vect route_lrs
-d.vect route_lrs_labels col=grey type=line
-d.vect busstops disp=attr attr=cat size=10 bg=white lcol=green yref=bottom
-d.vect busstops icon=basic/circle fcol=green
-d.labels labels
-</pre></div>
-
-<h2>SEE ALSO</h2>
-
-<em><a HREF="lrs.html">LRS tutorial</a></em>,<br>
-<em><a HREF="http://gisws.media.osaka-cu.ac.jp/grass04/viewpaper.php?id=50">Introducing the Linear Reference System in GRASS</a></em>,<br>
-<em><a HREF="v.lrs.create.html">v.lrs.create</a></em>,
-<em><a HREF="v.lrs.segment.html">v.lrs.segment</a></em>,
-<em><a HREF="v.lrs.where.html">v.lrs.where</a></em>
-
-<h2>AUTHOR</h2>
-
-Radim Blazek, ITC-irst/MPA Solutions<br>
-Documentation update (based on above journal article and available fragments): Markus Neteler
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/vector/v.lrs/v.lrs.label/v.lrs.label.html (from rev 32770, grass/trunk/vector/v.lrs/v.lrs.label/description.html)
===================================================================
--- grass/trunk/vector/v.lrs/v.lrs.label/v.lrs.label.html (rev 0)
+++ grass/trunk/vector/v.lrs/v.lrs.label/v.lrs.label.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,36 @@
+<h2>DESCRIPTION</h2>
+
+<em>v.lrs.label</em> generates LRS labels for pretty-printing of a LRS.
+
+This example is written for the Spearfish dataset (it continues the example
+from <em>v.lrs.create</em>).
+<p>
+
+
+<div class="code"><pre>
+v.lrs.label route_lrs rstable=route_lrs output=route_lrs_labels \
+ labels=labels col=red size=50 xoffset=100
+
+g.region vect=route_lrs n=n+100 s=s-100 -p
+d.erase
+d.vect route_lrs
+d.vect route_lrs_labels col=grey type=line
+d.vect busstops disp=attr attr=cat size=10 bg=white lcol=green yref=bottom
+d.vect busstops icon=basic/circle fcol=green
+d.labels labels
+</pre></div>
+
+<h2>SEE ALSO</h2>
+
+<em><a HREF="lrs.html">LRS tutorial</a></em>,<br>
+<em><a HREF="http://gisws.media.osaka-cu.ac.jp/grass04/viewpaper.php?id=50">Introducing the Linear Reference System in GRASS</a></em>,<br>
+<em><a HREF="v.lrs.create.html">v.lrs.create</a></em>,
+<em><a HREF="v.lrs.segment.html">v.lrs.segment</a></em>,
+<em><a HREF="v.lrs.where.html">v.lrs.where</a></em>
+
+<h2>AUTHOR</h2>
+
+Radim Blazek, ITC-irst/MPA Solutions<br>
+Documentation update (based on above journal article and available fragments): Markus Neteler
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/vector/v.lrs/v.lrs.segment/description.html
===================================================================
--- grass/trunk/vector/v.lrs/v.lrs.segment/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/vector/v.lrs/v.lrs.segment/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,63 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>v.lrs.segment</em> creates points/segments from input lines,
-linear reference system and positions read from <tt>standard in</tt>
-or a file.
-<P>
-The format is as follows:<BR>
-
-<div class="code"><pre>
-P <point_id> <line_id> <milepost>+<offset> [<side offset>]
-L <segment_id> <line_id> <milepost>+<offset> <milepost>+<offset> [<side offset>]
-</pre></div>
-
-<h2>NOTES</h2>
-
-For more information and examples see the help page for <em>v.lrs.segment</em>'s
-sister module, <em><a href="v.segment.html">v.segment</a></em>.
-
-<h2>EXAMPLE</h2>
-
-This example is written for the Spearfish dataset (it continues the example
-from <em>v.lrs.create</em>).
-<p>
-In this example, the 'route_lrs' shall be extended for a new
-position (point) along the LRS after bus stop 4:
-
-<div class="code"><pre>
-# new point on LRS
-echo "P 7 22 4+180" | v.lrs.segment route_lrs out=route_lrs_new rstable=route_lrs
-
-g.region vect=route_lrs n=n+100 s=s-100 -p
-d.erase
-# existing LRS
-d.vect route_lrs
-d.vect busstops disp=attr attr=cat size=10 bg=white lcol=blue yref=bottom
-d.vect busstops icon=basic/circle fcol=blue
-db.select route_lrs
-
-# show modified map
-d.vect route_lrs_new col=red
-</pre></div>
-
-<h2>TODO</h2>
-
-Figure out how to merge result into existing LRS map and table.
-
-<h2>SEE ALSO</h2>
-
-<em>
-<a HREF="lrs.html">LRS tutorial</a>,<br>
-<a HREF="http://gisws.media.osaka-cu.ac.jp/grass04/viewpaper.php?id=50">Introducing the Linear Reference System in GRASS</a>,<br>
-<a HREF="v.lrs.create.html">v.lrs.create</a>,
-<a HREF="v.lrs.where.html">v.lrs.where</a>,
-<a HREF="v.lrs.label.html">v.lrs.label</a>,
-<a HREF="v.segment.html">v.segment</a>
-</em>
-
-<h2>AUTHOR</h2>
-
-Radim Blazek
-
-<p>
-<i>Last changed: $Date$</i>
Copied: grass/trunk/vector/v.lrs/v.lrs.segment/v.lrs.segment.html (from rev 32770, grass/trunk/vector/v.lrs/v.lrs.segment/description.html)
===================================================================
--- grass/trunk/vector/v.lrs/v.lrs.segment/v.lrs.segment.html (rev 0)
+++ grass/trunk/vector/v.lrs/v.lrs.segment/v.lrs.segment.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,63 @@
+<h2>DESCRIPTION</h2>
+
+<em>v.lrs.segment</em> creates points/segments from input lines,
+linear reference system and positions read from <tt>standard in</tt>
+or a file.
+<P>
+The format is as follows:<BR>
+
+<div class="code"><pre>
+P <point_id> <line_id> <milepost>+<offset> [<side offset>]
+L <segment_id> <line_id> <milepost>+<offset> <milepost>+<offset> [<side offset>]
+</pre></div>
+
+<h2>NOTES</h2>
+
+For more information and examples see the help page for <em>v.lrs.segment</em>'s
+sister module, <em><a href="v.segment.html">v.segment</a></em>.
+
+<h2>EXAMPLE</h2>
+
+This example is written for the Spearfish dataset (it continues the example
+from <em>v.lrs.create</em>).
+<p>
+In this example, the 'route_lrs' shall be extended for a new
+position (point) along the LRS after bus stop 4:
+
+<div class="code"><pre>
+# new point on LRS
+echo "P 7 22 4+180" | v.lrs.segment route_lrs out=route_lrs_new rstable=route_lrs
+
+g.region vect=route_lrs n=n+100 s=s-100 -p
+d.erase
+# existing LRS
+d.vect route_lrs
+d.vect busstops disp=attr attr=cat size=10 bg=white lcol=blue yref=bottom
+d.vect busstops icon=basic/circle fcol=blue
+db.select route_lrs
+
+# show modified map
+d.vect route_lrs_new col=red
+</pre></div>
+
+<h2>TODO</h2>
+
+Figure out how to merge result into existing LRS map and table.
+
+<h2>SEE ALSO</h2>
+
+<em>
+<a HREF="lrs.html">LRS tutorial</a>,<br>
+<a HREF="http://gisws.media.osaka-cu.ac.jp/grass04/viewpaper.php?id=50">Introducing the Linear Reference System in GRASS</a>,<br>
+<a HREF="v.lrs.create.html">v.lrs.create</a>,
+<a HREF="v.lrs.where.html">v.lrs.where</a>,
+<a HREF="v.lrs.label.html">v.lrs.label</a>,
+<a HREF="v.segment.html">v.segment</a>
+</em>
+
+<h2>AUTHOR</h2>
+
+Radim Blazek
+
+<p>
+<i>Last changed: $Date$</i>
Deleted: grass/trunk/vector/v.lrs/v.lrs.where/description.html
===================================================================
--- grass/trunk/vector/v.lrs/v.lrs.where/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/vector/v.lrs/v.lrs.where/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,50 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>v.lrs.where</em> identifies line id and real milepost+offset for
-points in vector map using linear reference system.
-
-<h2>EXAMPLE</h2>
-
-This example is written for the Spearfish dataset (it continues the example
-from <em>v.lrs.create</em>).
-<p>
-In this example, the 'route_lrs' shall be queried for unknown
-positions (points, stored in the map <em>newpoints</em>) along the LRS:
-
-<div class="code"><pre>
-# generate query points
-echo "590866.15|4926737.0
-590933|4927133" | v.in.ascii out=newpoints
-
-v.lrs.where lines=route_lrs points=newpoints rstable=route_lrs
-pcat|lid|mpost|offset
-pcat|lid|mpost|offset
-1|22|4.000000+212.091461
-2|22|6.000000+188.112093
-
-# verification
-g.region vect=route_lrs n=n+100 s=s-100 -p
-d.erase
-d.vect route_lrs
-d.vect busstops disp=attr attr=cat size=10 bg=white lcol=blue yref=bottom
-d.vect busstops icon=basic/circle fcol=blue
-d.vect newpoints col=red
-
-# measure distance to previous bus stop
-d.measure
-</pre></div>
-
-<h2>SEE ALSO</h2>
-
-<em><a HREF="lrs.html">LRS tutorial</a></em>,<br>
-<em><a HREF="http://gisws.media.osaka-cu.ac.jp/grass04/viewpaper.php?id=50">Introducing the Linear Reference System in GRASS</a></em>,<br>
-<em><a HREF="v.lrs.create.html">v.lrs.where</a></em>,
-<em><a HREF="v.lrs.segment.html">v.lrs.segment</a></em>,
-<em><a HREF="v.lrs.label.html">v.lrs.label</a></em>
-
-<h2>AUTHOR</h2>
-
-Radim Blazek, ITC-irst/MPA Solutions<br>
-Documentation update (based on above journal article and available fragments): Markus Neteler
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/vector/v.lrs/v.lrs.where/v.lrs.where.html (from rev 32770, grass/trunk/vector/v.lrs/v.lrs.where/description.html)
===================================================================
--- grass/trunk/vector/v.lrs/v.lrs.where/v.lrs.where.html (rev 0)
+++ grass/trunk/vector/v.lrs/v.lrs.where/v.lrs.where.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,50 @@
+<h2>DESCRIPTION</h2>
+
+<em>v.lrs.where</em> identifies line id and real milepost+offset for
+points in vector map using linear reference system.
+
+<h2>EXAMPLE</h2>
+
+This example is written for the Spearfish dataset (it continues the example
+from <em>v.lrs.create</em>).
+<p>
+In this example, the 'route_lrs' shall be queried for unknown
+positions (points, stored in the map <em>newpoints</em>) along the LRS:
+
+<div class="code"><pre>
+# generate query points
+echo "590866.15|4926737.0
+590933|4927133" | v.in.ascii out=newpoints
+
+v.lrs.where lines=route_lrs points=newpoints rstable=route_lrs
+pcat|lid|mpost|offset
+pcat|lid|mpost|offset
+1|22|4.000000+212.091461
+2|22|6.000000+188.112093
+
+# verification
+g.region vect=route_lrs n=n+100 s=s-100 -p
+d.erase
+d.vect route_lrs
+d.vect busstops disp=attr attr=cat size=10 bg=white lcol=blue yref=bottom
+d.vect busstops icon=basic/circle fcol=blue
+d.vect newpoints col=red
+
+# measure distance to previous bus stop
+d.measure
+</pre></div>
+
+<h2>SEE ALSO</h2>
+
+<em><a HREF="lrs.html">LRS tutorial</a></em>,<br>
+<em><a HREF="http://gisws.media.osaka-cu.ac.jp/grass04/viewpaper.php?id=50">Introducing the Linear Reference System in GRASS</a></em>,<br>
+<em><a HREF="v.lrs.create.html">v.lrs.where</a></em>,
+<em><a HREF="v.lrs.segment.html">v.lrs.segment</a></em>,
+<em><a HREF="v.lrs.label.html">v.lrs.label</a></em>
+
+<h2>AUTHOR</h2>
+
+Radim Blazek, ITC-irst/MPA Solutions<br>
+Documentation update (based on above journal article and available fragments): Markus Neteler
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/vector/v.mkgrid/description.html
===================================================================
--- grass/trunk/vector/v.mkgrid/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/vector/v.mkgrid/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,30 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-<EM>v.mkgrid</EM> will create a vector map representation of a regular coordinate grid.
-
-<H2>NOTES</H2>
-
-This is NOT to be used to generate a vector map of USGS quadrangles,
-because USGS quads are not exact rectangles.
-
-<H2>EXAMPLE</H2>
-
-Make a 4x3 grid, cells 20km a side, with lower left corner at 2716500,6447000:
-<div class="code"><pre>
-v.mkgrid map=coro_grid grid=4,3 position=coor coor=2716500,6447000 box=20000,20000
-</pre></div>
-
-<H2>SEE ALSO</H2>
-
-<A HREF="v.patch.html">v.patch</A>,
-<A HREF="d.grid.html">d.grid</A>
-
-<H2>AUTHOR</H2>
-
-Michael Higgins,
-U.S.Army Construction Engineering
-Research Laboratory
-<P>
-Update for new vectors Radim Blazek 10/2004
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/vector/v.mkgrid/v.mkgrid.html (from rev 32770, grass/trunk/vector/v.mkgrid/description.html)
===================================================================
--- grass/trunk/vector/v.mkgrid/v.mkgrid.html (rev 0)
+++ grass/trunk/vector/v.mkgrid/v.mkgrid.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,30 @@
+<H2>DESCRIPTION</H2>
+
+<EM>v.mkgrid</EM> will create a vector map representation of a regular coordinate grid.
+
+<H2>NOTES</H2>
+
+This is NOT to be used to generate a vector map of USGS quadrangles,
+because USGS quads are not exact rectangles.
+
+<H2>EXAMPLE</H2>
+
+Make a 4x3 grid, cells 20km a side, with lower left corner at 2716500,6447000:
+<div class="code"><pre>
+v.mkgrid map=coro_grid grid=4,3 position=coor coor=2716500,6447000 box=20000,20000
+</pre></div>
+
+<H2>SEE ALSO</H2>
+
+<A HREF="v.patch.html">v.patch</A>,
+<A HREF="d.grid.html">d.grid</A>
+
+<H2>AUTHOR</H2>
+
+Michael Higgins,
+U.S.Army Construction Engineering
+Research Laboratory
+<P>
+Update for new vectors Radim Blazek 10/2004
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/vector/v.neighbors/description.html
===================================================================
--- grass/trunk/vector/v.neighbors/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/vector/v.neighbors/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,15 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-Makes each cell value a function of the attribute values assigned to the
-vector points or centroids around it, and stores new cell values in
-an output raster map layer.
-
-<H2>SEE ALSO</H2>
-
-<A HREF="r.neighbors.html">r.neighbors</A>
-
-<H2>AUTHOR</H2>
-
-Radim Blazek
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/vector/v.neighbors/v.neighbors.html (from rev 32770, grass/trunk/vector/v.neighbors/description.html)
===================================================================
--- grass/trunk/vector/v.neighbors/v.neighbors.html (rev 0)
+++ grass/trunk/vector/v.neighbors/v.neighbors.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,15 @@
+<H2>DESCRIPTION</H2>
+
+Makes each cell value a function of the attribute values assigned to the
+vector points or centroids around it, and stores new cell values in
+an output raster map layer.
+
+<H2>SEE ALSO</H2>
+
+<A HREF="r.neighbors.html">r.neighbors</A>
+
+<H2>AUTHOR</H2>
+
+Radim Blazek
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/vector/v.net/description.html
===================================================================
--- grass/trunk/vector/v.net/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/vector/v.net/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,52 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>v.net</em> is used for vector network maps maintenance.
-It reports about the current network graph status.
-It also permits to globally insert missing nodes and to connect
-unconnected nodes to the graph within a given distance threshold.
-
-<h3>NOTES</h3>
-
-If vector editing is required to modify the graph, <em>v.digit</em>
-or <em>v.edit</em> can be used. Separately,
-<a HREF="lrs.html">Linear Referencing System</a> is available
-in GRASS.
-
-<h3>EXAMPLES</h3>
-
-Spearfish based examples:<P>
-
-Create nodes globally for all line ends and intersections:
-<br>
-<div class="code"><pre>
-v.net in=streams out=streams_node
-</pre></div>
-
-<P>
-Merge in nodes from a separate map within given threshold:
-<br>
-<div class="code"><pre>
-echo "1|601653.5|4922869.2|start
-2|593330.8|4924096.6|end" | v.in.ascii cat=1 x=2 y=3 out=startend col="cat integer, \
- east double precision, north double precision, label varchar(43)"
-
-#create lines map connecting points to network (on layer 2)
-v.net myroads points=startend out=myroads_net op=connect thresh=200
-</pre></div>
-
-
-<h2>SEE ALSO</h2>
-
-<em><a HREF="v.digit.html">v.digit</a></em>,
-<em><a HREF="v.edit.html">v.edit</a></em>,
-<em><a HREF="v.net.iso.html">v.net.iso</a></em>,
-<em><a HREF="v.net.path.html">v.net.path</a></em>,
-<em><a HREF="v.net.steiner.html">v.net.steiner</a></em>,
-<em><a HREF="v.net.salesman.html">v.net.salesman</a></em>
-
-<h2>AUTHORS</h2>
-
-Radim Blazek, ITC-Irst, Trento, Italy<BR>
-Martin Landa, FBK-Irst, Trento, Italy
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/vector/v.net/v.net.html (from rev 32770, grass/trunk/vector/v.net/description.html)
===================================================================
--- grass/trunk/vector/v.net/v.net.html (rev 0)
+++ grass/trunk/vector/v.net/v.net.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,52 @@
+<h2>DESCRIPTION</h2>
+
+<em>v.net</em> is used for vector network maps maintenance.
+It reports about the current network graph status.
+It also permits to globally insert missing nodes and to connect
+unconnected nodes to the graph within a given distance threshold.
+
+<h3>NOTES</h3>
+
+If vector editing is required to modify the graph, <em>v.digit</em>
+or <em>v.edit</em> can be used. Separately,
+<a HREF="lrs.html">Linear Referencing System</a> is available
+in GRASS.
+
+<h3>EXAMPLES</h3>
+
+Spearfish based examples:<P>
+
+Create nodes globally for all line ends and intersections:
+<br>
+<div class="code"><pre>
+v.net in=streams out=streams_node
+</pre></div>
+
+<P>
+Merge in nodes from a separate map within given threshold:
+<br>
+<div class="code"><pre>
+echo "1|601653.5|4922869.2|start
+2|593330.8|4924096.6|end" | v.in.ascii cat=1 x=2 y=3 out=startend col="cat integer, \
+ east double precision, north double precision, label varchar(43)"
+
+#create lines map connecting points to network (on layer 2)
+v.net myroads points=startend out=myroads_net op=connect thresh=200
+</pre></div>
+
+
+<h2>SEE ALSO</h2>
+
+<em><a HREF="v.digit.html">v.digit</a></em>,
+<em><a HREF="v.edit.html">v.edit</a></em>,
+<em><a HREF="v.net.iso.html">v.net.iso</a></em>,
+<em><a HREF="v.net.path.html">v.net.path</a></em>,
+<em><a HREF="v.net.steiner.html">v.net.steiner</a></em>,
+<em><a HREF="v.net.salesman.html">v.net.salesman</a></em>
+
+<h2>AUTHORS</h2>
+
+Radim Blazek, ITC-Irst, Trento, Italy<BR>
+Martin Landa, FBK-Irst, Trento, Italy
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/vector/v.net.alloc/description.html
===================================================================
--- grass/trunk/vector/v.net.alloc/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/vector/v.net.alloc/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,55 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>v.net.alloc</em> allocates subnets for nearest centres (direction from
-centre). Centre node must be opened (costs >= 0). Costs of centre node are
-used in calculation. Supported are cost assignments for both arcs and nodes,
-and also different in both directions of a vector line. For areas cost will
-be calculated along boundary lines.
-
-<h2>NOTES</h2>
-
-Center nodes have to be assigned to vector nodes using <em>v.digit</em>.
-Nodes and arcs can be closed using cost = -1.
-
-<h2>EXAMPLE</h2>
-
-<div class="code"><pre>
-# nlayer=1 if no extra table for nodes:
-v.net.alloc network out=network_alloc ccats=0-13 nlayer=1
-
-# the result has to be selected by category number of the relevant node:
-d.vect network_alloc cat=9 col=red
-d.vect network_alloc cat=11 col=green
-d.vect network_alloc cat=2492 col=yellow
-</pre></div>
-<p>
-
-<em>Calculating subnets for 7 centre nodes using cost assigned to vector length
-</em><br>
-<div class="code"><pre>
-v.net.alloc in=vectmap out=vectmap.alloc ccats=1-7
-</pre></div>
-
-<p>
-
-<em>Calculating subnets for 7 centre nodes using cost assignments in both
-directions</em><br>
-<div class="code"><pre>
-v.net.alloc in=vectmap afcol=INDEX abcol=INDEXBACK out=vectmap.alloc ccats=1-7
-</pre></div>
-
-<h2>SEE ALSO</h2>
-
-<em><a HREF="d.path.html">d.path</a></em>,
-<em><a HREF="v.net.html">v.net</a></em>,
-<em><a HREF="v.net.iso.html">v.net.iso</a></em>,
-<em><a HREF="v.net.path.html">v.net.path</a></em>,
-<em><a HREF="v.net.steiner.html">v.net.steiner</a></em>,
-<em><a HREF="v.net.salesman.html">v.net.salesman</a></em>
-
-<h2>AUTHOR</h2>
-
-Radim Blazek, ITC-Irst, Trento, Italy
-
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/vector/v.net.alloc/v.net.alloc.html (from rev 32770, grass/trunk/vector/v.net.alloc/description.html)
===================================================================
--- grass/trunk/vector/v.net.alloc/v.net.alloc.html (rev 0)
+++ grass/trunk/vector/v.net.alloc/v.net.alloc.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,55 @@
+<h2>DESCRIPTION</h2>
+
+<em>v.net.alloc</em> allocates subnets for nearest centres (direction from
+centre). Centre node must be opened (costs >= 0). Costs of centre node are
+used in calculation. Supported are cost assignments for both arcs and nodes,
+and also different in both directions of a vector line. For areas cost will
+be calculated along boundary lines.
+
+<h2>NOTES</h2>
+
+Center nodes have to be assigned to vector nodes using <em>v.digit</em>.
+Nodes and arcs can be closed using cost = -1.
+
+<h2>EXAMPLE</h2>
+
+<div class="code"><pre>
+# nlayer=1 if no extra table for nodes:
+v.net.alloc network out=network_alloc ccats=0-13 nlayer=1
+
+# the result has to be selected by category number of the relevant node:
+d.vect network_alloc cat=9 col=red
+d.vect network_alloc cat=11 col=green
+d.vect network_alloc cat=2492 col=yellow
+</pre></div>
+<p>
+
+<em>Calculating subnets for 7 centre nodes using cost assigned to vector length
+</em><br>
+<div class="code"><pre>
+v.net.alloc in=vectmap out=vectmap.alloc ccats=1-7
+</pre></div>
+
+<p>
+
+<em>Calculating subnets for 7 centre nodes using cost assignments in both
+directions</em><br>
+<div class="code"><pre>
+v.net.alloc in=vectmap afcol=INDEX abcol=INDEXBACK out=vectmap.alloc ccats=1-7
+</pre></div>
+
+<h2>SEE ALSO</h2>
+
+<em><a HREF="d.path.html">d.path</a></em>,
+<em><a HREF="v.net.html">v.net</a></em>,
+<em><a HREF="v.net.iso.html">v.net.iso</a></em>,
+<em><a HREF="v.net.path.html">v.net.path</a></em>,
+<em><a HREF="v.net.steiner.html">v.net.steiner</a></em>,
+<em><a HREF="v.net.salesman.html">v.net.salesman</a></em>
+
+<h2>AUTHOR</h2>
+
+Radim Blazek, ITC-Irst, Trento, Italy
+
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/vector/v.net.iso/description.html
===================================================================
--- grass/trunk/vector/v.net.iso/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/vector/v.net.iso/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,86 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>v.net.iso</em> splits net to bands between cost isolines (direction from
-centre). Centre node must be opened (costs >= 0). Costs of centre node are
-used in calculation. Supported are cost assignments for both arcs and nodes,
-and also different in both directions of a vector line. For areas cost will
-be calculated along boundary lines.
-
-<h2>NOTES</h2>
-
-Nodes must be on the isolines.<P>
-
-Center nodes have to be assigned to vector nodes. Nodes and arcs can be closed
-using cost = -1.
-
-<h2>EXAMPLE</h2>
-
-Subdivision of a network into areas:<br>
-
-The map must contain at least one center
-(point) on the vector network which can be patched into with
-<a HREF="v.patch.html">v.patch</a>.
-
-<div class="code"><pre>
-# Spearfish
-
-# start node:
-echo "591280.5|4926396.0|1" | v.in.ascii out=startnode
-g.copy vect=roads,myroads
-
-#connect point to network
-v.net myroads points=startnode out=myroads_net op=connect thresh=200
-
-g.region vect=myroads_net
-d.mon x0
-d.vect myroads_net
-d.vect myroads_net col=red icon=basic/triangle fcol=green size=12 layer=2
-v.category myroads_net layer=2 op=print
-
-# specify range of center cats (easier to catch all):
-v.net.iso input=myroads_net output=myroads_net_iso ccats=1-100000 costs=1000,2000,5000
-v.category myroads_net_iso option=report
-# ... reports 4 categories:
-</pre></div>
-
-The network is 4 categories:
-
-<div class="code"><pre>
-cat | distance from point
-1 0 - 1000
-2 1000 - 2000
-3 2000 - 5000
-4 > 5000
-</pre></div>
-
-To see the result, run for example:
-
-<div class="code"><pre>
-g.region n=4928200 s=4922300 w=589200 e=596500
-d.erase
-d.vect myroads_net_iso
-d.vect myroads_net_iso col=blue cats=1
-d.vect myroads_net_iso col=green cats=2
-d.vect myroads_net_iso col=orange cats=3
-d.vect myroads_net_iso col=magenta cats=4
-d.vect myroads_net col=red icon=basic/triangle fcol=green size=12 layer=2
-</pre></div>
-
-<img src="vnetiso.png" alt="v.net.iso example" border="1">
-
-<h2>SEE ALSO</h2>
-
-<em><a HREF="d.path.html">d.path</a></em>,
-<em><a HREF="v.net.html">v.net</a></em>,
-<em><a HREF="v.net.alloc.html">v.net.alloc</a></em>,
-<em><a HREF="v.net.path.html">v.net.path</a></em>,
-<em><a HREF="v.net.salesman.html">v.net.salesman</a></em>,
-<em><a HREF="v.net.steiner.html">v.net.steiner</a></em>,
-<em><a HREF="v.patch.html">v.patch</a></em>
-
-<h2>AUTHOR</h2>
-
-Radim Blazek, ITC-Irst, Trento, Italy<br>
-Documentation: Markus Neteler
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/vector/v.net.iso/v.net.iso.html (from rev 32770, grass/trunk/vector/v.net.iso/description.html)
===================================================================
--- grass/trunk/vector/v.net.iso/v.net.iso.html (rev 0)
+++ grass/trunk/vector/v.net.iso/v.net.iso.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,86 @@
+<h2>DESCRIPTION</h2>
+
+<em>v.net.iso</em> splits net to bands between cost isolines (direction from
+centre). Centre node must be opened (costs >= 0). Costs of centre node are
+used in calculation. Supported are cost assignments for both arcs and nodes,
+and also different in both directions of a vector line. For areas cost will
+be calculated along boundary lines.
+
+<h2>NOTES</h2>
+
+Nodes must be on the isolines.<P>
+
+Center nodes have to be assigned to vector nodes. Nodes and arcs can be closed
+using cost = -1.
+
+<h2>EXAMPLE</h2>
+
+Subdivision of a network into areas:<br>
+
+The map must contain at least one center
+(point) on the vector network which can be patched into with
+<a HREF="v.patch.html">v.patch</a>.
+
+<div class="code"><pre>
+# Spearfish
+
+# start node:
+echo "591280.5|4926396.0|1" | v.in.ascii out=startnode
+g.copy vect=roads,myroads
+
+#connect point to network
+v.net myroads points=startnode out=myroads_net op=connect thresh=200
+
+g.region vect=myroads_net
+d.mon x0
+d.vect myroads_net
+d.vect myroads_net col=red icon=basic/triangle fcol=green size=12 layer=2
+v.category myroads_net layer=2 op=print
+
+# specify range of center cats (easier to catch all):
+v.net.iso input=myroads_net output=myroads_net_iso ccats=1-100000 costs=1000,2000,5000
+v.category myroads_net_iso option=report
+# ... reports 4 categories:
+</pre></div>
+
+The network is 4 categories:
+
+<div class="code"><pre>
+cat | distance from point
+1 0 - 1000
+2 1000 - 2000
+3 2000 - 5000
+4 > 5000
+</pre></div>
+
+To see the result, run for example:
+
+<div class="code"><pre>
+g.region n=4928200 s=4922300 w=589200 e=596500
+d.erase
+d.vect myroads_net_iso
+d.vect myroads_net_iso col=blue cats=1
+d.vect myroads_net_iso col=green cats=2
+d.vect myroads_net_iso col=orange cats=3
+d.vect myroads_net_iso col=magenta cats=4
+d.vect myroads_net col=red icon=basic/triangle fcol=green size=12 layer=2
+</pre></div>
+
+<img src="vnetiso.png" alt="v.net.iso example" border="1">
+
+<h2>SEE ALSO</h2>
+
+<em><a HREF="d.path.html">d.path</a></em>,
+<em><a HREF="v.net.html">v.net</a></em>,
+<em><a HREF="v.net.alloc.html">v.net.alloc</a></em>,
+<em><a HREF="v.net.path.html">v.net.path</a></em>,
+<em><a HREF="v.net.salesman.html">v.net.salesman</a></em>,
+<em><a HREF="v.net.steiner.html">v.net.steiner</a></em>,
+<em><a HREF="v.patch.html">v.patch</a></em>
+
+<h2>AUTHOR</h2>
+
+Radim Blazek, ITC-Irst, Trento, Italy<br>
+Documentation: Markus Neteler
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/vector/v.net.path/description.html
===================================================================
--- grass/trunk/vector/v.net.path/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/vector/v.net.path/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,120 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>v.net.path</em> can find shortest path(s) on the vector network.
-Costs may be either line lengths, or attributes saved in a database
-table. These attributes values are taken as costs of whole segments. If read
-from the table, arcs' costs may be different in both directions.
-Shortest paths are written to output vector map and attached attribute table.
-<P>
-
-Nodes can be piped into the program from file or from stdin. The
-syntax is as follows:
-<div class="code"><pre>
-id start_point_category end_point_category
-</pre></div>
-
-or
-
-<div class="code"><pre>
-id start_point_x start_point_y end_point_x end_point_y
-</pre></div>
-
-<p>
-Points specified by category must be exactly on network nodes,
-while, when specifying coordinates, the next node to a given
-coordinate pair is used.
-</p>
-<p>
-Attribute table will contain following attributes:
-</p>
-<ul>
- <li>cat - path unique category assigned by module</li>
- <li>id - path id (read from input)</li>
- <li>fcat - from point category</li>
- <li>tcat - to point category</li>
- <li>sp - result status:
- <ul>
- <li> 0 - OK, path found</li>
- <li> 1 - node is not reachable</li>
- <li> 2 - point of given category does not exist</li>
- </ul></li>
- <li>cost - travelling costs (on the network, not to/from network)</li>
- <li>fdist - the distance from first point to the network</li>
- <li>tdist - the distance from the network to second point</li>
-</ul>
-
-<h2>NOTE</h2>
-
-If the columns 'afcol', 'abcol' and 'ncol' costs are not
-specified, the length of network segments is measured and
-zero costs are assumed for nodes.
-<P>
-When using attributes, the length of segments is not used. To get
-more precise results, length should be taken indirectly into account
-by attributes. For example, to get the <b>fastest path</b> the columns
-'max_speed' and 'length' are required. The correct fastest path can then
-be found by specifying <tt>afcol=length/max_speed</tt> (pg driver). If needed,
-the line length can be calculated and written to the attributes table
-by <em>v.to.db</em>.
-
-<h2>EXAMPLE</h2>
-
-Shortest path from two digitized nodes (Spearfish):
-
-<div class="code"><pre>
-g.copy vect=roads,myroads
-v.db.addcol myroads col="forward double precision, backward double precision"
-
-# define traveling costs as inverse of speed limit:
-v.db.update myroads col=forward val=1/50
-v.db.update myroads col=backward val=1/50
-v.db.update myroads col=forward val=1/75 where="label='interstate'"
-v.db.update myroads col=backward val=1/75 where="label='interstate'"
-v.db.update myroads col=forward val=1/5 where="label='unimproved road'"
-v.db.update myroads col=backward val=1/5 where="label='unimproved road'"
-v.db.update myroads col=forward val=1/25 where="label='light-duty road, improved surface'"
-v.db.update myroads col=backward val=1/25 where="label='light-duty road, improved surface'"
-v.db.select myroads
-echo "1|601653.5|4922869.2|start
-2|593330.8|4924096.6|end" | v.in.ascii cat=1 x=2 y=3 out=startend col="cat integer, \
- east double precision, north double precision, label varchar(43)"
-
-v.db.select startend
-
-#create lines map connecting points to network (on layer 2)
-v.net myroads points=startend out=myroads_net op=connect thresh=200
-g.region vect=myroads_net
-d.mon x0
-d.vect myroads_net
-d.vect startend col=red
-
-v.db.select myroads_net
-
-d.vect myroads_net icon=basic/triangle fcol=green size=12 layer=2
-d.vect myroads_net disp=cat type=point lsize=14 layer=2
-# ... the 'start' and 'end' nodes have category number 1 and 2
-
-# ID as first number, then cat1 and cat2
-echo "1 1 2" | v.net.path myroads_net afcol=forward abcol=backward out=mypath
-d.vect mypath col=red width=2
-</pre></div>
-
-<img src="vnetpath.png" alt="v.net.path example" border="1">
-
-
-<h2>SEE ALSO</h2>
-
-<em><a HREF="d.path.html">d.path</a></em>,
-<em><a HREF="v.net.html">v.net</a></em>,
-<em><a HREF="v.net.alloc.html">v.net.alloc</a></em>,
-<em><a HREF="v.net.iso.html">v.net.iso</a></em>,
-<em><a HREF="v.net.salesman.html">v.net.salesman</a></em>,
-<em><a HREF="v.net.steiner.html">v.net.steiner</a></em>,
-<em><a HREF="v.to.db.html">v.to.db</a></em>
-
-<h2>AUTHOR</h2>
-
-Radim Blazek, ITC-Irst, Trento, Italy<br>
-Documentation: Markus Neteler
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/vector/v.net.path/v.net.path.html (from rev 32770, grass/trunk/vector/v.net.path/description.html)
===================================================================
--- grass/trunk/vector/v.net.path/v.net.path.html (rev 0)
+++ grass/trunk/vector/v.net.path/v.net.path.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,120 @@
+<h2>DESCRIPTION</h2>
+
+<em>v.net.path</em> can find shortest path(s) on the vector network.
+Costs may be either line lengths, or attributes saved in a database
+table. These attributes values are taken as costs of whole segments. If read
+from the table, arcs' costs may be different in both directions.
+Shortest paths are written to output vector map and attached attribute table.
+<P>
+
+Nodes can be piped into the program from file or from stdin. The
+syntax is as follows:
+<div class="code"><pre>
+id start_point_category end_point_category
+</pre></div>
+
+or
+
+<div class="code"><pre>
+id start_point_x start_point_y end_point_x end_point_y
+</pre></div>
+
+<p>
+Points specified by category must be exactly on network nodes,
+while, when specifying coordinates, the next node to a given
+coordinate pair is used.
+</p>
+<p>
+Attribute table will contain following attributes:
+</p>
+<ul>
+ <li>cat - path unique category assigned by module</li>
+ <li>id - path id (read from input)</li>
+ <li>fcat - from point category</li>
+ <li>tcat - to point category</li>
+ <li>sp - result status:
+ <ul>
+ <li> 0 - OK, path found</li>
+ <li> 1 - node is not reachable</li>
+ <li> 2 - point of given category does not exist</li>
+ </ul></li>
+ <li>cost - travelling costs (on the network, not to/from network)</li>
+ <li>fdist - the distance from first point to the network</li>
+ <li>tdist - the distance from the network to second point</li>
+</ul>
+
+<h2>NOTE</h2>
+
+If the columns 'afcol', 'abcol' and 'ncol' costs are not
+specified, the length of network segments is measured and
+zero costs are assumed for nodes.
+<P>
+When using attributes, the length of segments is not used. To get
+more precise results, length should be taken indirectly into account
+by attributes. For example, to get the <b>fastest path</b> the columns
+'max_speed' and 'length' are required. The correct fastest path can then
+be found by specifying <tt>afcol=length/max_speed</tt> (pg driver). If needed,
+the line length can be calculated and written to the attributes table
+by <em>v.to.db</em>.
+
+<h2>EXAMPLE</h2>
+
+Shortest path from two digitized nodes (Spearfish):
+
+<div class="code"><pre>
+g.copy vect=roads,myroads
+v.db.addcol myroads col="forward double precision, backward double precision"
+
+# define traveling costs as inverse of speed limit:
+v.db.update myroads col=forward val=1/50
+v.db.update myroads col=backward val=1/50
+v.db.update myroads col=forward val=1/75 where="label='interstate'"
+v.db.update myroads col=backward val=1/75 where="label='interstate'"
+v.db.update myroads col=forward val=1/5 where="label='unimproved road'"
+v.db.update myroads col=backward val=1/5 where="label='unimproved road'"
+v.db.update myroads col=forward val=1/25 where="label='light-duty road, improved surface'"
+v.db.update myroads col=backward val=1/25 where="label='light-duty road, improved surface'"
+v.db.select myroads
+echo "1|601653.5|4922869.2|start
+2|593330.8|4924096.6|end" | v.in.ascii cat=1 x=2 y=3 out=startend col="cat integer, \
+ east double precision, north double precision, label varchar(43)"
+
+v.db.select startend
+
+#create lines map connecting points to network (on layer 2)
+v.net myroads points=startend out=myroads_net op=connect thresh=200
+g.region vect=myroads_net
+d.mon x0
+d.vect myroads_net
+d.vect startend col=red
+
+v.db.select myroads_net
+
+d.vect myroads_net icon=basic/triangle fcol=green size=12 layer=2
+d.vect myroads_net disp=cat type=point lsize=14 layer=2
+# ... the 'start' and 'end' nodes have category number 1 and 2
+
+# ID as first number, then cat1 and cat2
+echo "1 1 2" | v.net.path myroads_net afcol=forward abcol=backward out=mypath
+d.vect mypath col=red width=2
+</pre></div>
+
+<img src="vnetpath.png" alt="v.net.path example" border="1">
+
+
+<h2>SEE ALSO</h2>
+
+<em><a HREF="d.path.html">d.path</a></em>,
+<em><a HREF="v.net.html">v.net</a></em>,
+<em><a HREF="v.net.alloc.html">v.net.alloc</a></em>,
+<em><a HREF="v.net.iso.html">v.net.iso</a></em>,
+<em><a HREF="v.net.salesman.html">v.net.salesman</a></em>,
+<em><a HREF="v.net.steiner.html">v.net.steiner</a></em>,
+<em><a HREF="v.to.db.html">v.to.db</a></em>
+
+<h2>AUTHOR</h2>
+
+Radim Blazek, ITC-Irst, Trento, Italy<br>
+Documentation: Markus Neteler
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/vector/v.net.salesman/description.html
===================================================================
--- grass/trunk/vector/v.net.salesman/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/vector/v.net.salesman/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,83 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>v.net.salesman</em> calculates the optimal route to visit nodes on a
-vector network.
-
-<h2>EXAMPLE</h2>
-
-Traveling salesman for 6 digitized nodes (Spearfish):
-
-<div class="code"><pre>
-g.copy vect=roads,myroads
-v.db.addcol myroads col="cost double precision"
-
-# define traveling costs as inverse of speed limit:
-v.db.update myroads col=cost val=1/50
-v.db.update myroads col=cost val=1/75 where="label='interstate'"
-v.db.update myroads col=cost val=1/5 where="label='unimproved road'"
-v.db.update myroads col=cost val=1/25 where="label='light-duty road, improved surface'"
-v.db.select myroads
-
-# we have 6 locations to visit on our trip
-echo "1|601653.5|4922869.2|a
-2|608284|4923776.6|b
-3|601845|4914981.9|c
-4|596270|4917456.3|d
-5|593330.8|4924096.6|e
-6|598005.5|4921439.2|f" | v.in.ascii cat=1 x=2 y=3 out=centers col="cat integer, \
- east double precision, north double precision, label varchar(43)"
-
-v.db.select centers
-v.category centers op=report
-# type count min max
-# point 6 1 6
-
-
-#create lines map connecting points to network (on layer 2)
-v.net myroads points=centers out=myroads_net op=connect thresh=500
-v.category myroads_net op=report
-# Layer / table: 1 / myroads_net
-# type count min max
-# line 837 1 5
-#
-# Layer: 2
-# type count min max
-# point 6 1 5
-
-# The network is now prepared.
-g.region vect=myroads_net
-d.mon x0
-d.vect myroads_net
-d.vect -c centers icon=basic/triangle
-d.font verdana
-d.vect centers col=red disp=attr attrcol=label lsize=12
-
-# due to the costs (?, TODO), the result looks like a Steiner tree:
-# v.net.salesman myroads_net acol=cost ccats=1-6 out=mysalesman
-
-# run without traveling costs
-v.net.salesman myroads_net ccats=1-6 out=mysalesman
-d.vect mysalesman col=green width=2
-d.vect centers col=red disp=attr attrcol=label lsize=12
-</pre></div>
-
-
-<img src="vnetsalesman.png" alt="v.net.salesman example" border="1">
-
-
-<h2>SEE ALSO</h2>
-
-<em><a HREF="d.path.html">d.path</a></em>,
-<em><a HREF="v.net.html">v.net</a></em>,
-<em><a HREF="v.net.alloc.html">v.net.alloc</a></em>,
-<em><a HREF="v.net.iso.html">v.net.iso</a></em>,
-<em><a HREF="v.net.path.html">v.net.path</a></em>,
-<em><a HREF="v.net.steiner.html">v.net.steiner</a></em>
-
-<h2>AUTHOR</h2>
-
-Radim Blazek, ITC-Irst, Trento, Italy<br>
-Documentation: Markus Neteler
-
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/vector/v.net.salesman/v.net.salesman.html (from rev 32770, grass/trunk/vector/v.net.salesman/description.html)
===================================================================
--- grass/trunk/vector/v.net.salesman/v.net.salesman.html (rev 0)
+++ grass/trunk/vector/v.net.salesman/v.net.salesman.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,83 @@
+<h2>DESCRIPTION</h2>
+
+<em>v.net.salesman</em> calculates the optimal route to visit nodes on a
+vector network.
+
+<h2>EXAMPLE</h2>
+
+Traveling salesman for 6 digitized nodes (Spearfish):
+
+<div class="code"><pre>
+g.copy vect=roads,myroads
+v.db.addcol myroads col="cost double precision"
+
+# define traveling costs as inverse of speed limit:
+v.db.update myroads col=cost val=1/50
+v.db.update myroads col=cost val=1/75 where="label='interstate'"
+v.db.update myroads col=cost val=1/5 where="label='unimproved road'"
+v.db.update myroads col=cost val=1/25 where="label='light-duty road, improved surface'"
+v.db.select myroads
+
+# we have 6 locations to visit on our trip
+echo "1|601653.5|4922869.2|a
+2|608284|4923776.6|b
+3|601845|4914981.9|c
+4|596270|4917456.3|d
+5|593330.8|4924096.6|e
+6|598005.5|4921439.2|f" | v.in.ascii cat=1 x=2 y=3 out=centers col="cat integer, \
+ east double precision, north double precision, label varchar(43)"
+
+v.db.select centers
+v.category centers op=report
+# type count min max
+# point 6 1 6
+
+
+#create lines map connecting points to network (on layer 2)
+v.net myroads points=centers out=myroads_net op=connect thresh=500
+v.category myroads_net op=report
+# Layer / table: 1 / myroads_net
+# type count min max
+# line 837 1 5
+#
+# Layer: 2
+# type count min max
+# point 6 1 5
+
+# The network is now prepared.
+g.region vect=myroads_net
+d.mon x0
+d.vect myroads_net
+d.vect -c centers icon=basic/triangle
+d.font verdana
+d.vect centers col=red disp=attr attrcol=label lsize=12
+
+# due to the costs (?, TODO), the result looks like a Steiner tree:
+# v.net.salesman myroads_net acol=cost ccats=1-6 out=mysalesman
+
+# run without traveling costs
+v.net.salesman myroads_net ccats=1-6 out=mysalesman
+d.vect mysalesman col=green width=2
+d.vect centers col=red disp=attr attrcol=label lsize=12
+</pre></div>
+
+
+<img src="vnetsalesman.png" alt="v.net.salesman example" border="1">
+
+
+<h2>SEE ALSO</h2>
+
+<em><a HREF="d.path.html">d.path</a></em>,
+<em><a HREF="v.net.html">v.net</a></em>,
+<em><a HREF="v.net.alloc.html">v.net.alloc</a></em>,
+<em><a HREF="v.net.iso.html">v.net.iso</a></em>,
+<em><a HREF="v.net.path.html">v.net.path</a></em>,
+<em><a HREF="v.net.steiner.html">v.net.steiner</a></em>
+
+<h2>AUTHOR</h2>
+
+Radim Blazek, ITC-Irst, Trento, Italy<br>
+Documentation: Markus Neteler
+
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/vector/v.net.steiner/description.html
===================================================================
--- grass/trunk/vector/v.net.steiner/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/vector/v.net.steiner/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,85 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>v.net.steiner</em> calculates the optimal connection of nodes on a
-vector network.
-
-<P>
-A Steiner tree is used to calculate the minimum-cost vector network
-connecting some number of end nodes in a network framework.
-For example it could be used to find the path following a road system
-which will minimize the amount of fibre optic cable needed to connect
-a series of satellite offices.
-
-
-<h2>EXAMPLE</h2>
-
-Steiner tree for for 6 digitized nodes (Spearfish):
-
-<div class="code"><pre>
-g.copy vect=roads,myroads
-v.db.addcol myroads col="cost double precision"
-
-# define traveling costs as inverse of speed limit:
-v.db.update myroads col=cost val=1/50
-v.db.update myroads col=cost val=1/75 where="label='interstate'"
-v.db.update myroads col=cost val=1/5 where="label='unimproved road'"
-v.db.update myroads col=cost val=1/25 where="label='light-duty road, improved surface'"
-v.db.select myroads
-
-# we have 6 locations to allocate
-echo "1|601653.5|4922869.2|a
-2|608284|4923776.6|b
-3|601845|4914981.9|c
-4|596270|4917456.3|d
-5|593330.8|4924096.6|e
-6|598005.5|4921439.2|f" | v.in.ascii cat=1 x=2 y=3 out=centers col="cat integer, \
- east double precision, north double precision, label varchar(43)"
-
-v.db.select centers
-v.category centers op=report
-# type count min max
-# point 6 1 6
-
-
-#create lines map connecting points to network (on layer 2)
-v.net myroads points=centers out=myroads_net op=connect thresh=500
-v.category myroads_net op=report
-# Layer / table: 1 / myroads_net
-# type count min max
-# line 837 1 5
-#
-# Layer: 2
-# type count min max
-# point 6 1 5
-
-# The network is now prepared.
-g.region vect=myroads_net
-d.mon x0
-d.vect myroads_net
-d.vect -c centers icon=basic/triangle
-d.font verdana
-d.vect centers col=red disp=attr attrcol=label lsize=12
-
-v.net.steiner myroads_net acol=cost tcats=1-6 out=mysteiner
-d.vect mysteiner col=blue width=2
-</pre></div>
-
-<img src="vnetsteiner.png" alt="v.net.steiner example" border="1">
-
-
-<h2>SEE ALSO</h2>
-
-<em><a HREF="d.path.html">d.path</a></em>,
-<em><a HREF="v.net.html">v.net</a></em>,
-<em><a HREF="v.net.alloc.html">v.net.alloc</a></em>,
-<em><a HREF="v.net.iso.html">v.net.iso</a></em>,
-<em><a HREF="v.net.path.html">v.net.path</a></em>,
-<em><a HREF="v.net.salesman.html">v.net.salesman</a></em>
-
-<h2>AUTHOR</h2>
-
-Radim Blazek, ITC-Irst, Trento, Italy<br>
-Documentation: Markus Neteler
-
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/vector/v.net.steiner/v.net.steiner.html (from rev 32770, grass/trunk/vector/v.net.steiner/description.html)
===================================================================
--- grass/trunk/vector/v.net.steiner/v.net.steiner.html (rev 0)
+++ grass/trunk/vector/v.net.steiner/v.net.steiner.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,85 @@
+<h2>DESCRIPTION</h2>
+
+<em>v.net.steiner</em> calculates the optimal connection of nodes on a
+vector network.
+
+<P>
+A Steiner tree is used to calculate the minimum-cost vector network
+connecting some number of end nodes in a network framework.
+For example it could be used to find the path following a road system
+which will minimize the amount of fibre optic cable needed to connect
+a series of satellite offices.
+
+
+<h2>EXAMPLE</h2>
+
+Steiner tree for for 6 digitized nodes (Spearfish):
+
+<div class="code"><pre>
+g.copy vect=roads,myroads
+v.db.addcol myroads col="cost double precision"
+
+# define traveling costs as inverse of speed limit:
+v.db.update myroads col=cost val=1/50
+v.db.update myroads col=cost val=1/75 where="label='interstate'"
+v.db.update myroads col=cost val=1/5 where="label='unimproved road'"
+v.db.update myroads col=cost val=1/25 where="label='light-duty road, improved surface'"
+v.db.select myroads
+
+# we have 6 locations to allocate
+echo "1|601653.5|4922869.2|a
+2|608284|4923776.6|b
+3|601845|4914981.9|c
+4|596270|4917456.3|d
+5|593330.8|4924096.6|e
+6|598005.5|4921439.2|f" | v.in.ascii cat=1 x=2 y=3 out=centers col="cat integer, \
+ east double precision, north double precision, label varchar(43)"
+
+v.db.select centers
+v.category centers op=report
+# type count min max
+# point 6 1 6
+
+
+#create lines map connecting points to network (on layer 2)
+v.net myroads points=centers out=myroads_net op=connect thresh=500
+v.category myroads_net op=report
+# Layer / table: 1 / myroads_net
+# type count min max
+# line 837 1 5
+#
+# Layer: 2
+# type count min max
+# point 6 1 5
+
+# The network is now prepared.
+g.region vect=myroads_net
+d.mon x0
+d.vect myroads_net
+d.vect -c centers icon=basic/triangle
+d.font verdana
+d.vect centers col=red disp=attr attrcol=label lsize=12
+
+v.net.steiner myroads_net acol=cost tcats=1-6 out=mysteiner
+d.vect mysteiner col=blue width=2
+</pre></div>
+
+<img src="vnetsteiner.png" alt="v.net.steiner example" border="1">
+
+
+<h2>SEE ALSO</h2>
+
+<em><a HREF="d.path.html">d.path</a></em>,
+<em><a HREF="v.net.html">v.net</a></em>,
+<em><a HREF="v.net.alloc.html">v.net.alloc</a></em>,
+<em><a HREF="v.net.iso.html">v.net.iso</a></em>,
+<em><a HREF="v.net.path.html">v.net.path</a></em>,
+<em><a HREF="v.net.salesman.html">v.net.salesman</a></em>
+
+<h2>AUTHOR</h2>
+
+Radim Blazek, ITC-Irst, Trento, Italy<br>
+Documentation: Markus Neteler
+
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/vector/v.net.visibility/description.html
===================================================================
--- grass/trunk/vector/v.net.visibility/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/vector/v.net.visibility/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,95 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<p><em>v.net.visibility</em> Computes the visibility graph of a vector map containing lines, areas ( boundaries ) and points. The visibility graph is the graph where the nodes are the end point of the lines, boundaries or simply the points. There is an edge between two nodes if they are 'visible'. Two nodes are visibible if there is no segments in between them, i.e. the edge doesn't intersect any line or boundary in the vector map. This is useful to compute the sortest path in a vector map from any two points. To do this, first you need to compute the visibility graph and from it compute the shortest path using v.net.path or d.path.
-</p>
-
-<b>IMPORTANT : the algorithm doesn't work well with intersecting lines ( that includes overlapping )</b>
-
-<p>
-If you compute a shortest path after computing the visibility graph you will notice that this path might go through a vertix of a line. If this is not wanted you might to run the map through <em>v.buffer</em> first whith a small value. Example:
-<div class="code"><pre>
-v.buffer input=map output=bufferedmap buffer=1 type=point,line,area,boundary
-</pre></div>
-</p>
-
-
-<p>
-The first argument is the input map. It supports lines, boudaries ( so areas ) and points. For the algorithm to work lines and boundaries must not be intersecting ( that includes overlapping ).
-<div class="code"><pre>
-input=map
-</pre></div>
-
-
-The result map containing the visibility graph is given in the output map
-<div class="code"><pre>
-output=map2
-</pre></div>
-
-
-If you need to add additional points to compute a shortest path between them afterwards you can use the <em>coordinate</em> parameter.
-<div class="code"><pre>
-coordinate=25556200,6686400,25556400,6686600
-</pre></div>
-where 25556200,6686400 are the coordinate of the first point and 25556400,6686600 are the coordinates of the second point. Of course you can give as many points as you want. They will be added to the visibility graph and edges from them will be computed. You can always add those points after computing the visibility graph. Simply use the <em>vis</em> parameter. The input will be the original vector map, the vis will be the computed visibility graph and the output the new visibility graph which will be the vis + the new points given with coordinate ( edges will be computed as well ).
-<div class="code"><pre>
-v.net.visibility input=map vis=vis_map output=new_vis_map coordinate=25556200,6686400,25556400,6686600
-</pre></div>
-</p>
-
-<h2>EXAMPLE 1</h2>
-A simple example showing how to use the module
-<div class="code"><pre>
-v.net.visibility input=lines output=graph <br>
-d.vect graph <br>
-d.vect lines col=red <br>
-</pre></div>
-
-<h2>EXAMPLE 2</h2>
-An example on how to use <em>v.buffer</em> with the module
-<div class="code"><pre>
-v.buffer input=lines output=buffered_lines buffer=1
-v.net.visibility input=buffered_lines output=graph <br>
-d.vect graph <br>
-d.vect lines col=red <br>
-</pre></div>
-
-
-<h2>EXAMPLE 3</h2>
-An example on how to use the coordinate parameter. This will compute the visibility graph of the vector map lines with the point 2555678,6686343
-<div class="code"><pre>
-v.net.visibility input=lines output=graph coordinate=2555678,6686343<br>
-d.vect graph <br>
-d.vect lines col=red <br>
-</pre></div>
-
-<h2>EXAMPLE 4</h2>
-An example on how to use the coordinate parameter with the vis parameter. Here the vector map graph is computed then a new visibility graph is computed from it with the point 2555678,6686343 extra
-<div class="code"><pre>
-v.net.visibility input=lines output=graph <br>
-d.vect graph <br>
-d.vect lines col=red <br>
-v.net.visibility input=lines vis=graph output=new_graph coordinate=2555678,6686343<br>
-d.erase
-d.vect new_graph
-d.vect lines col=red
-</pre></div>
-
-<h2>KNOWN BUGS</h2>
-In some cases when 3 points or nodes are collinear, some wrong edges are added. This happens only really rarly and shouldn't be a big problem.
-When two points have the exact same x coordinate and are visible, some wrong edges are added.
-
-<h2>SEE ALSO</h2>
-
-<em><a HREF="d.path.html">d.path</a></em>,
-<em><a HREF="v.net.html">v.net</a></em>,
-<em><a HREF="v.net.alloc.html">v.net.alloc</a></em>,
-<em><a HREF="v.net.iso.html">v.net.iso</a></em>,
-<em><a HREF="v.net.salesman.html">v.net.salesman</a></em>,
-<em><a HREF="v.net.steiner.html">v.net.steiner</a></em>,
-<em><a HREF="v.to.db.html">v.to.db</a></em>
-
-<h2>AUTHOR</h2>
-Maximilian Maldacker<br>
-Mentor : Wolf Bergenheim
-
-<p><i>Last changed: $Date$ </i>
Copied: grass/trunk/vector/v.net.visibility/v.net.visibility.html (from rev 32770, grass/trunk/vector/v.net.visibility/description.html)
===================================================================
--- grass/trunk/vector/v.net.visibility/v.net.visibility.html (rev 0)
+++ grass/trunk/vector/v.net.visibility/v.net.visibility.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,95 @@
+<h2>DESCRIPTION</h2>
+
+<p><em>v.net.visibility</em> Computes the visibility graph of a vector map containing lines, areas ( boundaries ) and points. The visibility graph is the graph where the nodes are the end point of the lines, boundaries or simply the points. There is an edge between two nodes if they are 'visible'. Two nodes are visibible if there is no segments in between them, i.e. the edge doesn't intersect any line or boundary in the vector map. This is useful to compute the sortest path in a vector map from any two points. To do this, first you need to compute the visibility graph and from it compute the shortest path using v.net.path or d.path.
+</p>
+
+<b>IMPORTANT : the algorithm doesn't work well with intersecting lines ( that includes overlapping )</b>
+
+<p>
+If you compute a shortest path after computing the visibility graph you will notice that this path might go through a vertix of a line. If this is not wanted you might to run the map through <em>v.buffer</em> first whith a small value. Example:
+<div class="code"><pre>
+v.buffer input=map output=bufferedmap buffer=1 type=point,line,area,boundary
+</pre></div>
+</p>
+
+
+<p>
+The first argument is the input map. It supports lines, boudaries ( so areas ) and points. For the algorithm to work lines and boundaries must not be intersecting ( that includes overlapping ).
+<div class="code"><pre>
+input=map
+</pre></div>
+
+
+The result map containing the visibility graph is given in the output map
+<div class="code"><pre>
+output=map2
+</pre></div>
+
+
+If you need to add additional points to compute a shortest path between them afterwards you can use the <em>coordinate</em> parameter.
+<div class="code"><pre>
+coordinate=25556200,6686400,25556400,6686600
+</pre></div>
+where 25556200,6686400 are the coordinate of the first point and 25556400,6686600 are the coordinates of the second point. Of course you can give as many points as you want. They will be added to the visibility graph and edges from them will be computed. You can always add those points after computing the visibility graph. Simply use the <em>vis</em> parameter. The input will be the original vector map, the vis will be the computed visibility graph and the output the new visibility graph which will be the vis + the new points given with coordinate ( edges will be computed as well ).
+<div class="code"><pre>
+v.net.visibility input=map vis=vis_map output=new_vis_map coordinate=25556200,6686400,25556400,6686600
+</pre></div>
+</p>
+
+<h2>EXAMPLE 1</h2>
+A simple example showing how to use the module
+<div class="code"><pre>
+v.net.visibility input=lines output=graph <br>
+d.vect graph <br>
+d.vect lines col=red <br>
+</pre></div>
+
+<h2>EXAMPLE 2</h2>
+An example on how to use <em>v.buffer</em> with the module
+<div class="code"><pre>
+v.buffer input=lines output=buffered_lines buffer=1
+v.net.visibility input=buffered_lines output=graph <br>
+d.vect graph <br>
+d.vect lines col=red <br>
+</pre></div>
+
+
+<h2>EXAMPLE 3</h2>
+An example on how to use the coordinate parameter. This will compute the visibility graph of the vector map lines with the point 2555678,6686343
+<div class="code"><pre>
+v.net.visibility input=lines output=graph coordinate=2555678,6686343<br>
+d.vect graph <br>
+d.vect lines col=red <br>
+</pre></div>
+
+<h2>EXAMPLE 4</h2>
+An example on how to use the coordinate parameter with the vis parameter. Here the vector map graph is computed then a new visibility graph is computed from it with the point 2555678,6686343 extra
+<div class="code"><pre>
+v.net.visibility input=lines output=graph <br>
+d.vect graph <br>
+d.vect lines col=red <br>
+v.net.visibility input=lines vis=graph output=new_graph coordinate=2555678,6686343<br>
+d.erase
+d.vect new_graph
+d.vect lines col=red
+</pre></div>
+
+<h2>KNOWN BUGS</h2>
+In some cases when 3 points or nodes are collinear, some wrong edges are added. This happens only really rarly and shouldn't be a big problem.
+When two points have the exact same x coordinate and are visible, some wrong edges are added.
+
+<h2>SEE ALSO</h2>
+
+<em><a HREF="d.path.html">d.path</a></em>,
+<em><a HREF="v.net.html">v.net</a></em>,
+<em><a HREF="v.net.alloc.html">v.net.alloc</a></em>,
+<em><a HREF="v.net.iso.html">v.net.iso</a></em>,
+<em><a HREF="v.net.salesman.html">v.net.salesman</a></em>,
+<em><a HREF="v.net.steiner.html">v.net.steiner</a></em>,
+<em><a HREF="v.to.db.html">v.to.db</a></em>
+
+<h2>AUTHOR</h2>
+Maximilian Maldacker<br>
+Mentor : Wolf Bergenheim
+
+<p><i>Last changed: $Date$ </i>
Deleted: grass/trunk/vector/v.normal/description.html
===================================================================
--- grass/trunk/vector/v.normal/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/vector/v.normal/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,60 +0,0 @@
-<H2>DESCRIPTION</H2>
-<EM>v.normal</EM>
-computes tests of normality on vector points.
-
-<H2>NOTES</H2>
-
-The tests that <EM>v.normal</EM> performs are indexed
-below. The tests that are performed are specified by
-giving an index, ranges of indices, or multiple thereof.
-
-<OL>
-<LI> Sample skewness and kurtosis
-<LI> Geary's a-statistic and an approximate normal transformation
-<LI> Extreme normal deviates
-<LI> D'Agostino's D-statistic
-<LI> Modified Kuiper V-statistic
-<LI> Modified Watson U^2-statistic
-<LI> Durbin's Exact Test (modified Kolmogorov)
-<LI> Modified Anderson-Darling statistic
-<LI> Modified Cramer-Von Mises W^2-statistic
-<LI> Kolmogorov-Smirnov D-statistic (modified for normality testing)
-<LI> Chi-Square test statistic (equal probability classes) and
- the number of degrees of freedom
-<LI> Shapiro-Wilk W Test
-<LI> Weisberg-Binghams W'' (similar to Shapiro-Francia's W')
-<LI> Royston's extension of W for large samples
-<LI> Kotz Separate-Families Test for Lognormality vs. Normality
-</OL>
-
-<H2>EXAMPLE</H2>
-
-<!-- do a meaning ful example -->
-<div class="code"><pre>
-v.random random n=200
-v.db.addtable random col="elev double precision"
-v.what.rast random rast=elevation.10m col=elev
-v.normal random tests=1-3,14 col=elev
-</pre></div>
-
-computes the sample skewness and kurtosis, Geary's
-a-statistic and an approximate normal transformation,
-extreme normal deviates, and Royston's W for the
-<EM>random</EM> vector points.
-
-<!-- TODO: find references , e.g.
- http://www.itl.nist.gov/div898/handbook/eda/section3/eda35.htm
--->
-
-<H2>SEE ALSO</H2>
-<A HREF="v.univar.html">v.univar</A>
-
-<H2>AUTHOR</H2>
-
-<A HREF="http://mccauley-usa.com/">James Darrell McCauley</A>
-<A HREF="mailto:darrell at mccauley-usa.com"><darrell at mccauley-usa.com></A>,
-<br>when he was at:
-<A HREF="http://ABE.www.ecn.purdue.edu/ABE/">Agricultural
-Engineering</A>
-<A HREF="http://www.purdue.edu/">Purdue University</A>
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/vector/v.normal/v.normal.html (from rev 32770, grass/trunk/vector/v.normal/description.html)
===================================================================
--- grass/trunk/vector/v.normal/v.normal.html (rev 0)
+++ grass/trunk/vector/v.normal/v.normal.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,60 @@
+<H2>DESCRIPTION</H2>
+<EM>v.normal</EM>
+computes tests of normality on vector points.
+
+<H2>NOTES</H2>
+
+The tests that <EM>v.normal</EM> performs are indexed
+below. The tests that are performed are specified by
+giving an index, ranges of indices, or multiple thereof.
+
+<OL>
+<LI> Sample skewness and kurtosis
+<LI> Geary's a-statistic and an approximate normal transformation
+<LI> Extreme normal deviates
+<LI> D'Agostino's D-statistic
+<LI> Modified Kuiper V-statistic
+<LI> Modified Watson U^2-statistic
+<LI> Durbin's Exact Test (modified Kolmogorov)
+<LI> Modified Anderson-Darling statistic
+<LI> Modified Cramer-Von Mises W^2-statistic
+<LI> Kolmogorov-Smirnov D-statistic (modified for normality testing)
+<LI> Chi-Square test statistic (equal probability classes) and
+ the number of degrees of freedom
+<LI> Shapiro-Wilk W Test
+<LI> Weisberg-Binghams W'' (similar to Shapiro-Francia's W')
+<LI> Royston's extension of W for large samples
+<LI> Kotz Separate-Families Test for Lognormality vs. Normality
+</OL>
+
+<H2>EXAMPLE</H2>
+
+<!-- do a meaning ful example -->
+<div class="code"><pre>
+v.random random n=200
+v.db.addtable random col="elev double precision"
+v.what.rast random rast=elevation.10m col=elev
+v.normal random tests=1-3,14 col=elev
+</pre></div>
+
+computes the sample skewness and kurtosis, Geary's
+a-statistic and an approximate normal transformation,
+extreme normal deviates, and Royston's W for the
+<EM>random</EM> vector points.
+
+<!-- TODO: find references , e.g.
+ http://www.itl.nist.gov/div898/handbook/eda/section3/eda35.htm
+-->
+
+<H2>SEE ALSO</H2>
+<A HREF="v.univar.html">v.univar</A>
+
+<H2>AUTHOR</H2>
+
+<A HREF="http://mccauley-usa.com/">James Darrell McCauley</A>
+<A HREF="mailto:darrell at mccauley-usa.com"><darrell at mccauley-usa.com></A>,
+<br>when he was at:
+<A HREF="http://ABE.www.ecn.purdue.edu/ABE/">Agricultural
+Engineering</A>
+<A HREF="http://www.purdue.edu/">Purdue University</A>
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/vector/v.out.ascii/description.html
===================================================================
--- grass/trunk/vector/v.out.ascii/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/vector/v.out.ascii/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,144 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>v.out.ascii</em>
-converts a GRASS vector map in binary format to a GRASS vector map in ASCII
-format. Using flag <b>-o</b> <em>v.out.ascii</em> output will be in old
-(version 4) ASCII format.
-<P>
-If the <b>output</b> parameter is not given then the coordinates of any
-<em>point</em> data within the vector map is sent to stdout.
-
-<h2>NOTES</h2>
-
-The GRASS program <em><a HREF="v.in.ascii.html">v.in.ascii</a></em>
-performs the function of <em>v.out.ascii</em> in reverse; i.e., it
-converts vector maps in ASCII format to their binary format.
-These two companion programs are useful both for importing and exporting
-vector maps between GRASS and other software, and for transferring data
-between machines.
-
-<P>
-If the <b>format</b> parameter is set to <b>standard</b>, A GRASS ASCII vector map will be exported,
-which may contain a mix of primitives including points, lines, boundaries, centroids, areas, faces,
-and kernels. The beginning of the output ascii file will contain a header listing any metadata for the
-input vector, if such metadata exists. An example of the <b>standard</b> format is given below.
-<P>
-The primitive codes are as follows:
-<UL>
-<LI>'P': point</LI>
-<LI>'L': line</LI>
-<LI>'B': boundary</LI>
-<LI>'C': centroid</LI>
-<LI>'F': face (3D boundary)</LI>
-<LI>'K': kernel (3D centroid)</LI>
-<LI>'A': area (boundary) - better use 'B'; kept only for backward compatibility</LI>
-
-</UL>
-
-The coordinates are listed following the initial line containing the
-primitive code, the total number of vectors in the series, and the number
-of categories (1 for a single layer, higher for multiple layers).
-Below that 1 or several lines follow to indicate the layer number and
-the category number (ID).
-<BR>
-<p>
-The order of coordinates for new (standard) version of ASCII file is <BR><BR>
-X Y [Z]
-<BR><BR>
-the order of coordinates for old version of ASCII file is <BR><BR>
-Y X
-
-<p>
-If old version is requested, the <B>output</B> files from <em>v.out.ascii</em> will be placed
-in the <tt>$LOCATION/$MAPSET/dig_ascii/</tt> and <tt>$LOCATION/$MAPSET/dig_att</tt> directory.
-
-<p>
-Only features with a category number will be exported. Use <em>v.category</em>
-to add them if needed.
-
-<p>
-<em>v.out.ascii</em> does not copy the <em>dig_cats</em>
-file associated with the binary vector <em>input</em> map
-to the new <em>output</em> file name. The user must copy
-the <em>dig_cats</em> file to the new <em>output</em> name
-if this is desired (e.g., using the UNIX <em>cp</em>
-command).
-
-<p>
-It is possible to output the coordinates of vertices in a non-points vector
-feature by first converting the vector feature to a points map with
-<em>v.to.points</em> and then exporting with <em>v.out.ascii</em> in
-<em>points</em> mode.
-
-<h2>EXAMPLES</h2>
-
-<h3>Example 1a) - standard mode - using the 'quads' vector from Spearfish dataset:</h3>
-
-<p>
-<div class="code"><pre>
-v.out.ascii input=quads format=standard
-
-ORGANIZATION: US Army Const. Eng. Rsch. Lab
-DIGIT DATE: May 1987
-DIGIT NAME: grass
-MAP NAME: Quads
-MAP DATE: May 1987
-MAP SCALE: 24000
-OTHER INFO:
-ZONE: 13
-MAP THRESH: 18.288000
-VERTI:
-B 4
- 599587.1820962 4914067.53414294
- 589639.15126831 4913922.5687301
- 589440.96838162 4927803.62500018
- 599375.87959179 4927959.83330436
-B 2
- 599375.87959179 4927959.83330436
- 599587.1820962 4914067.53414294
-B 4
- 599587.1820962 4914067.53414294
- 609541.5508239 4914236.0597482
- 609316.10665227 4928116.8490555
- 599375.87959179 4927959.83330436
-C 1 1
- 594125.63 4921115.58
- 1 1
-C 1 1
- 604433.84 4921087.1
- 1 2
-</pre></div>
-
-<h3>Example 1b) - point mode</h3>
-
-<p>
-<div class="code"><pre>
-v.out.ascii input=quads format=point
-
-594125.63|4921115.58|1
-604433.84|4921087.1|2
-</pre></div>
-
-<h2>SEE ALSO</h2>
-
-<em>
-<a HREF="v.category.html">v.category</a><BR>
-<a HREF="v.in.ascii.html">v.in.ascii</a><BR>
-<a HREF="v.to.points.html">v.to.points</a></em><BR>
-<a HREF="http://freegis.org/cgi-bin/viewcvs.cgi/~checkout~/grass6/doc/vector/vector.html#ascii">Vector ASCII Format Specification</a>
-<BR><BR>
-
-
-<h2>AUTHORS</h2>
-
-Michael Higgins,
-U.S. Army Construction Engineering
-Research Laboratory
-<br>
-James Westervelt,
-U.S. Army Construction Engineering
-Research Laboratory
-<br>
-Radim Blazek, ITC-Irst, Trento, Italy
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/vector/v.out.ascii/v.out.ascii.html (from rev 32770, grass/trunk/vector/v.out.ascii/description.html)
===================================================================
--- grass/trunk/vector/v.out.ascii/v.out.ascii.html (rev 0)
+++ grass/trunk/vector/v.out.ascii/v.out.ascii.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,144 @@
+<h2>DESCRIPTION</h2>
+
+<em>v.out.ascii</em>
+converts a GRASS vector map in binary format to a GRASS vector map in ASCII
+format. Using flag <b>-o</b> <em>v.out.ascii</em> output will be in old
+(version 4) ASCII format.
+<P>
+If the <b>output</b> parameter is not given then the coordinates of any
+<em>point</em> data within the vector map is sent to stdout.
+
+<h2>NOTES</h2>
+
+The GRASS program <em><a HREF="v.in.ascii.html">v.in.ascii</a></em>
+performs the function of <em>v.out.ascii</em> in reverse; i.e., it
+converts vector maps in ASCII format to their binary format.
+These two companion programs are useful both for importing and exporting
+vector maps between GRASS and other software, and for transferring data
+between machines.
+
+<P>
+If the <b>format</b> parameter is set to <b>standard</b>, A GRASS ASCII vector map will be exported,
+which may contain a mix of primitives including points, lines, boundaries, centroids, areas, faces,
+and kernels. The beginning of the output ascii file will contain a header listing any metadata for the
+input vector, if such metadata exists. An example of the <b>standard</b> format is given below.
+<P>
+The primitive codes are as follows:
+<UL>
+<LI>'P': point</LI>
+<LI>'L': line</LI>
+<LI>'B': boundary</LI>
+<LI>'C': centroid</LI>
+<LI>'F': face (3D boundary)</LI>
+<LI>'K': kernel (3D centroid)</LI>
+<LI>'A': area (boundary) - better use 'B'; kept only for backward compatibility</LI>
+
+</UL>
+
+The coordinates are listed following the initial line containing the
+primitive code, the total number of vectors in the series, and the number
+of categories (1 for a single layer, higher for multiple layers).
+Below that 1 or several lines follow to indicate the layer number and
+the category number (ID).
+<BR>
+<p>
+The order of coordinates for new (standard) version of ASCII file is <BR><BR>
+X Y [Z]
+<BR><BR>
+the order of coordinates for old version of ASCII file is <BR><BR>
+Y X
+
+<p>
+If old version is requested, the <B>output</B> files from <em>v.out.ascii</em> will be placed
+in the <tt>$LOCATION/$MAPSET/dig_ascii/</tt> and <tt>$LOCATION/$MAPSET/dig_att</tt> directory.
+
+<p>
+Only features with a category number will be exported. Use <em>v.category</em>
+to add them if needed.
+
+<p>
+<em>v.out.ascii</em> does not copy the <em>dig_cats</em>
+file associated with the binary vector <em>input</em> map
+to the new <em>output</em> file name. The user must copy
+the <em>dig_cats</em> file to the new <em>output</em> name
+if this is desired (e.g., using the UNIX <em>cp</em>
+command).
+
+<p>
+It is possible to output the coordinates of vertices in a non-points vector
+feature by first converting the vector feature to a points map with
+<em>v.to.points</em> and then exporting with <em>v.out.ascii</em> in
+<em>points</em> mode.
+
+<h2>EXAMPLES</h2>
+
+<h3>Example 1a) - standard mode - using the 'quads' vector from Spearfish dataset:</h3>
+
+<p>
+<div class="code"><pre>
+v.out.ascii input=quads format=standard
+
+ORGANIZATION: US Army Const. Eng. Rsch. Lab
+DIGIT DATE: May 1987
+DIGIT NAME: grass
+MAP NAME: Quads
+MAP DATE: May 1987
+MAP SCALE: 24000
+OTHER INFO:
+ZONE: 13
+MAP THRESH: 18.288000
+VERTI:
+B 4
+ 599587.1820962 4914067.53414294
+ 589639.15126831 4913922.5687301
+ 589440.96838162 4927803.62500018
+ 599375.87959179 4927959.83330436
+B 2
+ 599375.87959179 4927959.83330436
+ 599587.1820962 4914067.53414294
+B 4
+ 599587.1820962 4914067.53414294
+ 609541.5508239 4914236.0597482
+ 609316.10665227 4928116.8490555
+ 599375.87959179 4927959.83330436
+C 1 1
+ 594125.63 4921115.58
+ 1 1
+C 1 1
+ 604433.84 4921087.1
+ 1 2
+</pre></div>
+
+<h3>Example 1b) - point mode</h3>
+
+<p>
+<div class="code"><pre>
+v.out.ascii input=quads format=point
+
+594125.63|4921115.58|1
+604433.84|4921087.1|2
+</pre></div>
+
+<h2>SEE ALSO</h2>
+
+<em>
+<a HREF="v.category.html">v.category</a><BR>
+<a HREF="v.in.ascii.html">v.in.ascii</a><BR>
+<a HREF="v.to.points.html">v.to.points</a></em><BR>
+<a HREF="http://freegis.org/cgi-bin/viewcvs.cgi/~checkout~/grass6/doc/vector/vector.html#ascii">Vector ASCII Format Specification</a>
+<BR><BR>
+
+
+<h2>AUTHORS</h2>
+
+Michael Higgins,
+U.S. Army Construction Engineering
+Research Laboratory
+<br>
+James Westervelt,
+U.S. Army Construction Engineering
+Research Laboratory
+<br>
+Radim Blazek, ITC-Irst, Trento, Italy
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/vector/v.out.dxf/description.html
===================================================================
--- grass/trunk/vector/v.out.dxf/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/vector/v.out.dxf/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,30 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-The GRASS program <EM>v.out.dxf</EM> conversion program
-generates an ASCII DXF (AutoCAD) file from a GRASS vector.
-The output file is placed in the user's current
-working directory unless the user specifies a full pathname
-for the <EM>output</EM>.
-
-<H2>NOTES</H2>
-DXF files output by AutoCAD have the suffix <KBD>.dxf</KBD>
-
-<H2>REFERENCES</H2>
-
-<a href="http://en.wikipedia.org/wiki/AutoCAD_DXF">AutoCad DXF</a> (from Wikipedia, the free encyclopedia)
-
-<H2>SEE ALSO</H2>
-
-<EM><A HREF="v.in.dxf.html">v.in.dxf</A></EM>,
-<EM><a href="vectorintro.html">Introduction to GRASS vector map processing</a></EM>
-
-<H2>AUTHOR</H2>
-
-Charles Ehlschlaeger, U.S. Army Construction Engineering
-Research Laboratory,<br>
-wrote original <EM>v.out.dxf</EM> program in 4/89.
-<P>
-Update to GRASS 5.7 Radim Blazek, 10/2004
-
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/vector/v.out.dxf/v.out.dxf.html (from rev 32770, grass/trunk/vector/v.out.dxf/description.html)
===================================================================
--- grass/trunk/vector/v.out.dxf/v.out.dxf.html (rev 0)
+++ grass/trunk/vector/v.out.dxf/v.out.dxf.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,30 @@
+<H2>DESCRIPTION</H2>
+
+The GRASS program <EM>v.out.dxf</EM> conversion program
+generates an ASCII DXF (AutoCAD) file from a GRASS vector.
+The output file is placed in the user's current
+working directory unless the user specifies a full pathname
+for the <EM>output</EM>.
+
+<H2>NOTES</H2>
+DXF files output by AutoCAD have the suffix <KBD>.dxf</KBD>
+
+<H2>REFERENCES</H2>
+
+<a href="http://en.wikipedia.org/wiki/AutoCAD_DXF">AutoCad DXF</a> (from Wikipedia, the free encyclopedia)
+
+<H2>SEE ALSO</H2>
+
+<EM><A HREF="v.in.dxf.html">v.in.dxf</A></EM>,
+<EM><a href="vectorintro.html">Introduction to GRASS vector map processing</a></EM>
+
+<H2>AUTHOR</H2>
+
+Charles Ehlschlaeger, U.S. Army Construction Engineering
+Research Laboratory,<br>
+wrote original <EM>v.out.dxf</EM> program in 4/89.
+<P>
+Update to GRASS 5.7 Radim Blazek, 10/2004
+
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/vector/v.out.ogr/description.html
===================================================================
--- grass/trunk/vector/v.out.ogr/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/vector/v.out.ogr/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,119 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>v.out.ogr</em> converts GRASS vector data to
-<a href="http://www.gdal.org/ogr/">OGR</a> format.
-OGR (Simple Features Library) is part of the
-<a href="http://www.gdal.org">GDAL</a> library, so you need to
-install gdal to use <em>v.out.ogr</em>.
-
-<h3>Supported OGR Vector Formats</h3>
-
-<a href="http://www.gdal.org/ogr/drv_shapefile.html">ESRI Shapefile</a><br>
-<a href="http://www.gdal.org/ogr/drv_csv.html">CSV</a><br>
-<a href="http://www.gdal.org/ogr/drv_gml.html">GML</a><br>
-<a href="http://www.gdal.org/ogr/drv_kml.html">KML</a><br>
-<a href="http://www.gdal.org/ogr/drv_mitab.html">Mapinfo File</a><br>
-<a href="http://www.gdal.org/ogr/drv_pg.html">PostgreSQL/PostGIS</a><br>
-<a href="http://www.gdal.org/ogr/drv_tiger.html">TIGER</a>
-
-<p>
-
-For further available drivers go
-<a href="http://www.gdal.org/ogr/ogr_formats.html">here</a>.
-
-<h2>NOTES</h2>
-
-To export areas with holes into, e.g., a Shapefile, while keeping the
-holes as holes, the flag <em>-c</em> has to be used.
-
-
-<h2>EXAMPLES</h2>
-
-<h3>Export to Shapefile</h3>
-
-Export lines from GRASS vector map to Shapefile format (generates /tmp/testogr.shp and related files):
-<div class="code"><pre>
-v.out.ogr input=multi type=line dsn=/tmp olayer=testogr
-</pre></div>
-
-Export areas from GRASS vector map to Shapefile format (generates /tmp/testogr.shp and related files):
-<div class="code"><pre>
-v.out.ogr input=multi type=area dsn=/tmp olayer=testogr
-</pre></div>
-
-Export 3D lines from GRASS vector map to Shapefile format:
-<div class="code"><pre>
-v.out.ogr input=lines_3d type=line dsn=/tmp olayer=testogr lco="SHPT=ARCZ"
-</pre></div>
-
-<h3>Export to GML</h3>
-
-Export lines from GRASS vector map to GML format (generates /tmp/testogr.gml file with layer 'testogr'):
-<div class="code"><pre>
-v.out.ogr input=multi type=line dsn=/tmp/testogr.gml olayer=testogr format=GML
-</pre></div>
-
-<h3>Export to PostgreSQL/PostGIS</h3>
-
-Export areas from GRASS vector map directly to PostGIS:
-<div class="code"><pre>
-v.out.ogr input=polygons type=area \
- dsn="PG:host=localhost dbname=postgis user=postgres" \
- olayer=polymap format=PostgreSQL
-</pre></div>
-
-<h3>Export to KML (Google Earth)</h3>
-
-<b>Example 1 (Latitude-Longitude location):</b><br>
-Export faces (3D vectors) from GRASS vector map to KML format for Google Earth:
-<div class="code"><pre>
-v.out.ogr input=buildings_3d dsn=buildings_3d.kml olayer=buildings_3d \
- format=KML type=face
-</pre></div>
-
-<p>
-<b>Example 2 (Latitude-Longitude location):</b><br>
-Generate and export GRASS vector "asteroid" map (faces, 3D vectors) to KML format for Google Earth:
-<div class="code"><pre>
-# near Raleigh (NC, USA)
-g.region n=35.73952587 s=35.73279182 w=-78.68263928 e=-78.67499517
-
-# two layers of random points
-v.random -z output=random3d_a n=10 zmin=0 zmax=200
-v.random -z output=random3d_b n=15 zmin=400 zmax=600
-
-# merge into one 3D points map
-v.patch input=random3d_a,random3d_b output=random3d
-
-# generate 3D convex hull
-v.hull input=random3d output="random3d_hull"
-
-# export to KML 3D
-v.out.ogr input=random3d_hull dsn=random3d_hull.kml format=KML \
- type=face dsco="AltitudeMode=absolute"
-
-# now open KML file 'random3d_hull.kml' in Google Earth or NASA WorldWind or ...
-</pre></div>
-
-
-<H2>REFERENCES</H2>
-
-<a href="http://www.gdal.org/ogr/">OGR vector library</a>
-<br>
-<a href="http://www.gdal.org/ogr/ogr__api_8h.html">OGR vector library C API</a>
-documentation
-
-
-<h2>SEE ALSO</h2>
-
-<EM>
-<A HREF="db.out.ogr.html">db.out.ogr</A>,
-<A HREF="v.external.html">v.external</A>,
-<a HREF="v.in.ogr.html">v.in.ogr</a>
-</EM>
-
-<h2>AUTHORS</h2>
-
-Radim Blazek, ITC-Irst, Trento, Italy<br>
-Some contributions: Markus Neteler, Martin Landa
-<p><i>Last changed: $Date$</i></p>
Copied: grass/trunk/vector/v.out.ogr/v.out.ogr.html (from rev 32770, grass/trunk/vector/v.out.ogr/description.html)
===================================================================
--- grass/trunk/vector/v.out.ogr/v.out.ogr.html (rev 0)
+++ grass/trunk/vector/v.out.ogr/v.out.ogr.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,119 @@
+<h2>DESCRIPTION</h2>
+
+<em>v.out.ogr</em> converts GRASS vector data to
+<a href="http://www.gdal.org/ogr/">OGR</a> format.
+OGR (Simple Features Library) is part of the
+<a href="http://www.gdal.org">GDAL</a> library, so you need to
+install gdal to use <em>v.out.ogr</em>.
+
+<h3>Supported OGR Vector Formats</h3>
+
+<a href="http://www.gdal.org/ogr/drv_shapefile.html">ESRI Shapefile</a><br>
+<a href="http://www.gdal.org/ogr/drv_csv.html">CSV</a><br>
+<a href="http://www.gdal.org/ogr/drv_gml.html">GML</a><br>
+<a href="http://www.gdal.org/ogr/drv_kml.html">KML</a><br>
+<a href="http://www.gdal.org/ogr/drv_mitab.html">Mapinfo File</a><br>
+<a href="http://www.gdal.org/ogr/drv_pg.html">PostgreSQL/PostGIS</a><br>
+<a href="http://www.gdal.org/ogr/drv_tiger.html">TIGER</a>
+
+<p>
+
+For further available drivers go
+<a href="http://www.gdal.org/ogr/ogr_formats.html">here</a>.
+
+<h2>NOTES</h2>
+
+To export areas with holes into, e.g., a Shapefile, while keeping the
+holes as holes, the flag <em>-c</em> has to be used.
+
+
+<h2>EXAMPLES</h2>
+
+<h3>Export to Shapefile</h3>
+
+Export lines from GRASS vector map to Shapefile format (generates /tmp/testogr.shp and related files):
+<div class="code"><pre>
+v.out.ogr input=multi type=line dsn=/tmp olayer=testogr
+</pre></div>
+
+Export areas from GRASS vector map to Shapefile format (generates /tmp/testogr.shp and related files):
+<div class="code"><pre>
+v.out.ogr input=multi type=area dsn=/tmp olayer=testogr
+</pre></div>
+
+Export 3D lines from GRASS vector map to Shapefile format:
+<div class="code"><pre>
+v.out.ogr input=lines_3d type=line dsn=/tmp olayer=testogr lco="SHPT=ARCZ"
+</pre></div>
+
+<h3>Export to GML</h3>
+
+Export lines from GRASS vector map to GML format (generates /tmp/testogr.gml file with layer 'testogr'):
+<div class="code"><pre>
+v.out.ogr input=multi type=line dsn=/tmp/testogr.gml olayer=testogr format=GML
+</pre></div>
+
+<h3>Export to PostgreSQL/PostGIS</h3>
+
+Export areas from GRASS vector map directly to PostGIS:
+<div class="code"><pre>
+v.out.ogr input=polygons type=area \
+ dsn="PG:host=localhost dbname=postgis user=postgres" \
+ olayer=polymap format=PostgreSQL
+</pre></div>
+
+<h3>Export to KML (Google Earth)</h3>
+
+<b>Example 1 (Latitude-Longitude location):</b><br>
+Export faces (3D vectors) from GRASS vector map to KML format for Google Earth:
+<div class="code"><pre>
+v.out.ogr input=buildings_3d dsn=buildings_3d.kml olayer=buildings_3d \
+ format=KML type=face
+</pre></div>
+
+<p>
+<b>Example 2 (Latitude-Longitude location):</b><br>
+Generate and export GRASS vector "asteroid" map (faces, 3D vectors) to KML format for Google Earth:
+<div class="code"><pre>
+# near Raleigh (NC, USA)
+g.region n=35.73952587 s=35.73279182 w=-78.68263928 e=-78.67499517
+
+# two layers of random points
+v.random -z output=random3d_a n=10 zmin=0 zmax=200
+v.random -z output=random3d_b n=15 zmin=400 zmax=600
+
+# merge into one 3D points map
+v.patch input=random3d_a,random3d_b output=random3d
+
+# generate 3D convex hull
+v.hull input=random3d output="random3d_hull"
+
+# export to KML 3D
+v.out.ogr input=random3d_hull dsn=random3d_hull.kml format=KML \
+ type=face dsco="AltitudeMode=absolute"
+
+# now open KML file 'random3d_hull.kml' in Google Earth or NASA WorldWind or ...
+</pre></div>
+
+
+<H2>REFERENCES</H2>
+
+<a href="http://www.gdal.org/ogr/">OGR vector library</a>
+<br>
+<a href="http://www.gdal.org/ogr/ogr__api_8h.html">OGR vector library C API</a>
+documentation
+
+
+<h2>SEE ALSO</h2>
+
+<EM>
+<A HREF="db.out.ogr.html">db.out.ogr</A>,
+<A HREF="v.external.html">v.external</A>,
+<a HREF="v.in.ogr.html">v.in.ogr</a>
+</EM>
+
+<h2>AUTHORS</h2>
+
+Radim Blazek, ITC-Irst, Trento, Italy<br>
+Some contributions: Markus Neteler, Martin Landa
+<p><i>Last changed: $Date$</i></p>
Deleted: grass/trunk/vector/v.out.pov/description.html
===================================================================
--- grass/trunk/vector/v.out.pov/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/vector/v.out.pov/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,23 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>v.out.pov</em> converts GRASS vector data to POV-Ray format (www.povray.com)
-
-<h2>EXAMPLE</h2>
-<div class="code"><pre>
-v.out.pov input=tin output=tin.pov objmod="pigment { color red 0 green 1 blue 0 }"
-</pre></div>
-
-<H2>REFERENCES</H2>
-
-<a href="http://www.povray.com">POV-Ray</a>
-
-
-<h2>SEE ALSO</h2>
-
-<em><a HREF="r.out.pov.html">r.out.pov</a></em>,
-
-<h2>AUTHOR</h2>
-
-Radim Blazek, ITC-Irst, Trento, Italy
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/vector/v.out.pov/v.out.pov.html (from rev 32770, grass/trunk/vector/v.out.pov/description.html)
===================================================================
--- grass/trunk/vector/v.out.pov/v.out.pov.html (rev 0)
+++ grass/trunk/vector/v.out.pov/v.out.pov.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,23 @@
+<h2>DESCRIPTION</h2>
+
+<em>v.out.pov</em> converts GRASS vector data to POV-Ray format (www.povray.com)
+
+<h2>EXAMPLE</h2>
+<div class="code"><pre>
+v.out.pov input=tin output=tin.pov objmod="pigment { color red 0 green 1 blue 0 }"
+</pre></div>
+
+<H2>REFERENCES</H2>
+
+<a href="http://www.povray.com">POV-Ray</a>
+
+
+<h2>SEE ALSO</h2>
+
+<em><a HREF="r.out.pov.html">r.out.pov</a></em>,
+
+<h2>AUTHOR</h2>
+
+Radim Blazek, ITC-Irst, Trento, Italy
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/vector/v.out.svg/description.html
===================================================================
--- grass/trunk/vector/v.out.svg/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/vector/v.out.svg/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,52 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>v.out.svg</em> converts GRASS vector data to SVG (Scalable Vector Graphics) code notation.
-In particular, it
-<ul>
-<li>converts GRASS line, boundary, area, point, centroid objects to SVG
- <path />, <circle /> elements,</li>
-<li>reduces coordinate precision in SVG-output to save bandwidth,</li>
-<li>extracts GRASS attributes to gg:name="value" attributes.</li>
-</ul>
-
-The <em>precision</em> parameter controls the number of decimals for coordinates
-output (<em>precision=0</em> corresponds to integer precision in the output SVG file).
-
-<h2>EXAMPLE</h2>
-
-<p>
-Export <b>polygons</b> from GRASS vector map soils (Spearfish sample data) to SVG format:
-<div class="code"><pre>
-v.out.svg input=soils output=/tmp/output.svg type=poly
-</pre></div>
-
-<p>
-Export <b>lines</b> from GRASS vector map t_hydro (Spearfish sample
-data) to SVG format, set coordinate precision to 0:
-<div class="code"><pre>
-v.out.svg input=t_hydro output=/tmp/output.svg type=line precision=0
-</pre></div>
-
-<p>
-Export <b>points</b> from GRASS vector map archsites (Spearfish sample
-data) to SVG format, include attribute <b>str1</b> (name):
-<div class="code"><pre>
-v.out.svg input=archsites output=/tmp/output.svg type=point precision=0 attrib=str1
-</pre></div>
-
-<H2>REFERENCES</H2>
-
-<a href="http://svg.cc/grass/index.html">Modul v.out.svg at svg.cc</a>
-<br>
-<a href="http://www.w3.org/Graphics/SVG/">SVG (Scalable Vector Graphics) at w3c.org</a>
-
-
-<h2>SEE ALSO</h2>
-
-<em><A HREF="v.out.ogr.html">v.out.ogr</A></em>
-
-<h2>AUTHOR</h2>
-
-Klaus Foerster (klaus svg.cc), Innsbruck, Austria
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/vector/v.out.svg/v.out.svg.html (from rev 32770, grass/trunk/vector/v.out.svg/description.html)
===================================================================
--- grass/trunk/vector/v.out.svg/v.out.svg.html (rev 0)
+++ grass/trunk/vector/v.out.svg/v.out.svg.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,52 @@
+<h2>DESCRIPTION</h2>
+
+<em>v.out.svg</em> converts GRASS vector data to SVG (Scalable Vector Graphics) code notation.
+In particular, it
+<ul>
+<li>converts GRASS line, boundary, area, point, centroid objects to SVG
+ <path />, <circle /> elements,</li>
+<li>reduces coordinate precision in SVG-output to save bandwidth,</li>
+<li>extracts GRASS attributes to gg:name="value" attributes.</li>
+</ul>
+
+The <em>precision</em> parameter controls the number of decimals for coordinates
+output (<em>precision=0</em> corresponds to integer precision in the output SVG file).
+
+<h2>EXAMPLE</h2>
+
+<p>
+Export <b>polygons</b> from GRASS vector map soils (Spearfish sample data) to SVG format:
+<div class="code"><pre>
+v.out.svg input=soils output=/tmp/output.svg type=poly
+</pre></div>
+
+<p>
+Export <b>lines</b> from GRASS vector map t_hydro (Spearfish sample
+data) to SVG format, set coordinate precision to 0:
+<div class="code"><pre>
+v.out.svg input=t_hydro output=/tmp/output.svg type=line precision=0
+</pre></div>
+
+<p>
+Export <b>points</b> from GRASS vector map archsites (Spearfish sample
+data) to SVG format, include attribute <b>str1</b> (name):
+<div class="code"><pre>
+v.out.svg input=archsites output=/tmp/output.svg type=point precision=0 attrib=str1
+</pre></div>
+
+<H2>REFERENCES</H2>
+
+<a href="http://svg.cc/grass/index.html">Modul v.out.svg at svg.cc</a>
+<br>
+<a href="http://www.w3.org/Graphics/SVG/">SVG (Scalable Vector Graphics) at w3c.org</a>
+
+
+<h2>SEE ALSO</h2>
+
+<em><A HREF="v.out.ogr.html">v.out.ogr</A></em>
+
+<h2>AUTHOR</h2>
+
+Klaus Foerster (klaus svg.cc), Innsbruck, Austria
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/vector/v.out.vtk/description.html
===================================================================
--- grass/trunk/vector/v.out.vtk/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/vector/v.out.vtk/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,93 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>v.out.vtk</em>
-converts a GRASS vector map in binary format to the VTK ASCII
-output.
-<P>
-If the <b>output</b> parameter is not given, the output will be send to stdout.
-
-<h2>NOTES</h2>
-
-The following vector types can be exported together in one VTK ascii file:
-<ul>
- <li>point</li>
- <li>line</li>
- <li>centroid</li>
- <li>boundary</li>
- <li>area</li>
- <li>face</li>
-</ul>
-
-Category data (cat) for the selected vector type and layer will be written as scalar
-data with name "cat_{vectorname}". If no cat exists, the value will set to -1 as normal cat's are
-always positive.
-If a vector has more categories in one layer, only the first category
-will be exported.
-<br>
-<br>
-3d vectors are supported by default. The created VTK data always includes x, y and z coordinates
-(z = 0 if not a 3d vector map).
-Note that you can easily convert your 2d vectors into 3d vectors with v.drape.
-<br>
-<br>
-Because of the 32bit limits of OpenGL which is used by VTK, visualisation errors may occure if
-the grass region contains coordinates greater than 1.000.000 and vector coordinates
-with 0.01 - 0.001 meters precisison. For this reason, the flag "-c" was added. The coordinates are
-transformed to smaller coordinates (by decreasing the coordinates with the region center).
-<br>
-<br>
-If the "-c" flag is used and the data should be visualised together with other data exported via *.out.vtk
-modules, be sure the "-c" flag was also set in these modules.
-But this will only work with data from the SAME location
-(The reference point for the coordinates transformation is based on the default region).
-<br>
-<br>
-The GRASS vector data is converted into the polydata format of VTK:
-
-<ul>
- <li><i>vtk Vertices</i> -- representing points and centroids </li>
- <li><i>vtk lines</i> -- representing lines and boundaries </li>
- <li><i>vtk polygons</i> -- representing areas and faces </li>
-</li>
-</ul>
-<p>
-The VTK file can be visualized with
-<EM><A HREF="http://www.vtk.org">VTK Toolkit</A></EM>,
-<EM><A HREF="http://www.paraview.org">Paraview</A></EM> and
-<EM><A HREF="http://mayavi.sourceforge.net">MayaVi</A></EM>.
-
-<h3>Attention</h3>
-If areas or faces are exported, the data have to be triangulated within Paraview or
-MayaVi.
-</p>
-
-<h2>EXAMPLE</h2>
-
-Spearfish example:
-<P>
-Export the soils with cats in layer 1:
-<div class="code"><pre>
-v.out.vtk input=soils type=area layer=1 output=/tmp/soils.vtk
-</pre></div>
-Export the streams with cats in layer 1:
-<div class="code"><pre>
-v.out.vtk input=streams type=line layer=1 output=/tmp/streams.vtk
-</pre></div>
-Write the archsite vtk output to stdout with cats in layer 1:
-<div class="code"><pre>
-v.out.vtk input=archsites type=point layer=1
-</pre></div>
-
-<h2>SEE ALSO</h2>
-
-<em>
-<a HREF="v.out.ascii.html">v.out.ascii</a><BR>
-<a HREF="r.out.vtk.html">r.out.vtk</a><BR>
-<a HREF="r3.out.vtk.html">r3.out.vtk</a><BR>
-</em>
-
-
-<h2>AUTHOR</h2>
-
-Soeren Gebbert
-
Copied: grass/trunk/vector/v.out.vtk/v.out.vtk.html (from rev 32770, grass/trunk/vector/v.out.vtk/description.html)
===================================================================
--- grass/trunk/vector/v.out.vtk/v.out.vtk.html (rev 0)
+++ grass/trunk/vector/v.out.vtk/v.out.vtk.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,93 @@
+<h2>DESCRIPTION</h2>
+
+<em>v.out.vtk</em>
+converts a GRASS vector map in binary format to the VTK ASCII
+output.
+<P>
+If the <b>output</b> parameter is not given, the output will be send to stdout.
+
+<h2>NOTES</h2>
+
+The following vector types can be exported together in one VTK ascii file:
+<ul>
+ <li>point</li>
+ <li>line</li>
+ <li>centroid</li>
+ <li>boundary</li>
+ <li>area</li>
+ <li>face</li>
+</ul>
+
+Category data (cat) for the selected vector type and layer will be written as scalar
+data with name "cat_{vectorname}". If no cat exists, the value will set to -1 as normal cat's are
+always positive.
+If a vector has more categories in one layer, only the first category
+will be exported.
+<br>
+<br>
+3d vectors are supported by default. The created VTK data always includes x, y and z coordinates
+(z = 0 if not a 3d vector map).
+Note that you can easily convert your 2d vectors into 3d vectors with v.drape.
+<br>
+<br>
+Because of the 32bit limits of OpenGL which is used by VTK, visualisation errors may occure if
+the grass region contains coordinates greater than 1.000.000 and vector coordinates
+with 0.01 - 0.001 meters precisison. For this reason, the flag "-c" was added. The coordinates are
+transformed to smaller coordinates (by decreasing the coordinates with the region center).
+<br>
+<br>
+If the "-c" flag is used and the data should be visualised together with other data exported via *.out.vtk
+modules, be sure the "-c" flag was also set in these modules.
+But this will only work with data from the SAME location
+(The reference point for the coordinates transformation is based on the default region).
+<br>
+<br>
+The GRASS vector data is converted into the polydata format of VTK:
+
+<ul>
+ <li><i>vtk Vertices</i> -- representing points and centroids </li>
+ <li><i>vtk lines</i> -- representing lines and boundaries </li>
+ <li><i>vtk polygons</i> -- representing areas and faces </li>
+</li>
+</ul>
+<p>
+The VTK file can be visualized with
+<EM><A HREF="http://www.vtk.org">VTK Toolkit</A></EM>,
+<EM><A HREF="http://www.paraview.org">Paraview</A></EM> and
+<EM><A HREF="http://mayavi.sourceforge.net">MayaVi</A></EM>.
+
+<h3>Attention</h3>
+If areas or faces are exported, the data have to be triangulated within Paraview or
+MayaVi.
+</p>
+
+<h2>EXAMPLE</h2>
+
+Spearfish example:
+<P>
+Export the soils with cats in layer 1:
+<div class="code"><pre>
+v.out.vtk input=soils type=area layer=1 output=/tmp/soils.vtk
+</pre></div>
+Export the streams with cats in layer 1:
+<div class="code"><pre>
+v.out.vtk input=streams type=line layer=1 output=/tmp/streams.vtk
+</pre></div>
+Write the archsite vtk output to stdout with cats in layer 1:
+<div class="code"><pre>
+v.out.vtk input=archsites type=point layer=1
+</pre></div>
+
+<h2>SEE ALSO</h2>
+
+<em>
+<a HREF="v.out.ascii.html">v.out.ascii</a><BR>
+<a HREF="r.out.vtk.html">r.out.vtk</a><BR>
+<a HREF="r3.out.vtk.html">r3.out.vtk</a><BR>
+</em>
+
+
+<h2>AUTHOR</h2>
+
+Soeren Gebbert
+
Deleted: grass/trunk/vector/v.overlay/description.html
===================================================================
--- grass/trunk/vector/v.overlay/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/vector/v.overlay/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,59 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>v.overlay</em> allows the user to overlay two vector area maps.
-<!-- This is outdated
-There are 3 links attached to features in output map,
-<ul>
-<li><b>field 1</b>: link to the new table, new table has 3 columns
- <ul>
- <li><b>cat</b> - key column linking rows to features
- <li><b>cata</b> - category of <i>afield</i> from <i>ainput</i>
- <li><b>catb</b> - category of <i>bfield</i> from <i>binput</i>
- </ul>
-<li><b>field 2</b>: category of <i>afield</i> from <i>ainput</i>
-<li><b>field 3</b>: category of <i>bfield</i> from <i>binput</i>
-</ul>
--->
-The resulting output map has a merged attribute-table. The origin column-names
-have a prefix (<em>a_</em> and <em>b_</em>) which results from the ainput- and binput-map.
-
-<h2>NOTES</h2>
-Currently only areas are supported for the operators <em>or</em> and <em>xor</em>! See also <a href="v.select.html">v.select</a>.
-
-The operator defines what kind of operation will be done. Features are written to output,
-if the result of an operation 'ainput operator binput' is true.
-<p>
-Attributes of the tables from ainput and binput are joined into a new table
-linked to the output maps new cat-column.
-
-<!-- This is outdated
-<p>
-<div class="code"><pre>
-v.db.connect map=outputmap table=ainput.dbf field=2
-v.db.connect map=outputmap table=binput.dbf field=3
-
-</pre></div>
-
-<p>
-<b>Attention:</b> Removing the output map will also delete all tables linked to
-it! Therefore it is advisable to copy tables from ainput and binput first and
-connect the copied tables to the output map.-->
-
-<h2>EXAMPLE</h2>
-<div class="code"><pre>
-v.overlay ainput=lake binput=province output=lakeXprovince
-</pre></div>
-
-
-<h2>SEE ALSO</h2>
-
-<em>
-<a href="v.db.connect.html">v.db.connect</a>,
-<a href="v.select.html">v.select</a>,
-<a href="g.copy.html">g.copy</a></em>
-
-<h2>AUTHORS</h2>
-
-Radim Blazek, ITC-Irst, Trento, Italy
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/vector/v.overlay/v.overlay.html (from rev 32770, grass/trunk/vector/v.overlay/description.html)
===================================================================
--- grass/trunk/vector/v.overlay/v.overlay.html (rev 0)
+++ grass/trunk/vector/v.overlay/v.overlay.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,59 @@
+<h2>DESCRIPTION</h2>
+
+<em>v.overlay</em> allows the user to overlay two vector area maps.
+<!-- This is outdated
+There are 3 links attached to features in output map,
+<ul>
+<li><b>field 1</b>: link to the new table, new table has 3 columns
+ <ul>
+ <li><b>cat</b> - key column linking rows to features
+ <li><b>cata</b> - category of <i>afield</i> from <i>ainput</i>
+ <li><b>catb</b> - category of <i>bfield</i> from <i>binput</i>
+ </ul>
+<li><b>field 2</b>: category of <i>afield</i> from <i>ainput</i>
+<li><b>field 3</b>: category of <i>bfield</i> from <i>binput</i>
+</ul>
+-->
+The resulting output map has a merged attribute-table. The origin column-names
+have a prefix (<em>a_</em> and <em>b_</em>) which results from the ainput- and binput-map.
+
+<h2>NOTES</h2>
+Currently only areas are supported for the operators <em>or</em> and <em>xor</em>! See also <a href="v.select.html">v.select</a>.
+
+The operator defines what kind of operation will be done. Features are written to output,
+if the result of an operation 'ainput operator binput' is true.
+<p>
+Attributes of the tables from ainput and binput are joined into a new table
+linked to the output maps new cat-column.
+
+<!-- This is outdated
+<p>
+<div class="code"><pre>
+v.db.connect map=outputmap table=ainput.dbf field=2
+v.db.connect map=outputmap table=binput.dbf field=3
+
+</pre></div>
+
+<p>
+<b>Attention:</b> Removing the output map will also delete all tables linked to
+it! Therefore it is advisable to copy tables from ainput and binput first and
+connect the copied tables to the output map.-->
+
+<h2>EXAMPLE</h2>
+<div class="code"><pre>
+v.overlay ainput=lake binput=province output=lakeXprovince
+</pre></div>
+
+
+<h2>SEE ALSO</h2>
+
+<em>
+<a href="v.db.connect.html">v.db.connect</a>,
+<a href="v.select.html">v.select</a>,
+<a href="g.copy.html">g.copy</a></em>
+
+<h2>AUTHORS</h2>
+
+Radim Blazek, ITC-Irst, Trento, Italy
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/vector/v.parallel/description.html
===================================================================
--- grass/trunk/vector/v.parallel/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/vector/v.parallel/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,16 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-<EM>v.parallel</EM> create parallel line to input vector lines which
-can be used as half-buffers.
-
-<H2>SEE ALSO</H2>
-
-<EM>
-<A HREF="v.buffer.html">v.buffer</A>
-</EM>
-
-<H2>AUTHOR</H2>
-
-Radim Blazek
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/vector/v.parallel/v.parallel.html (from rev 32770, grass/trunk/vector/v.parallel/description.html)
===================================================================
--- grass/trunk/vector/v.parallel/v.parallel.html (rev 0)
+++ grass/trunk/vector/v.parallel/v.parallel.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,16 @@
+<H2>DESCRIPTION</H2>
+
+<EM>v.parallel</EM> create parallel line to input vector lines which
+can be used as half-buffers.
+
+<H2>SEE ALSO</H2>
+
+<EM>
+<A HREF="v.buffer.html">v.buffer</A>
+</EM>
+
+<H2>AUTHOR</H2>
+
+Radim Blazek
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/vector/v.patch/description.html
===================================================================
--- grass/trunk/vector/v.patch/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/vector/v.patch/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,49 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>v.patch</em> allows the user to combine any number of
-vector map layers together to create one composite vector
-map layer.
-If the table structures are identical, attributes are
-transferred to the new table.
-
-<h2>NOTES</h2>
-
-Any vectors that are duplicated among the maps being
-patched together (e.g., border lines) will have to be
-edited or removed after <em>v.patch</em> is run. Such
-editing can be done automatically using
-<em><a HREF="v.clean.html">v.clean</a></em> (tool=snap,break,rmdupl).
-
-
-<h2>EXAMPLES</h2>
-
-Patch together two maps with mixed feature types:
-<div class="code"><pre>
- v.patch input=geology,streams out=geol_streams
-</pre></div>
-
-<BR>
-Append one map to another:
-<div class="code"><pre>
- g.copy vect=roads,transport
- v.patch -a input=railroads output=transport --overwrite
-</pre></div>
-
-
-<h2>SEE ALSO</h2>
-
-<em><a HREF="v.clean.html">v.clean</a></em>,
-<em><a HREF="v.build.html">v.build</a></em>,
-<em><a HREF="v.select.html">v.select</a></em>,
-<em><a HREF="v.overlay.html">v.overlay</a></em>
-
-
-<h2>AUTHORS</h2>
-
-Dave Gerdes, U.S.Army Construction Engineering
-Research Laboratory
-<br>
-Radim Blazek, ITC-Irst, Trento, Italy
-
-<p>
-<i>Last changed: $Date$</i>
Copied: grass/trunk/vector/v.patch/v.patch.html (from rev 32770, grass/trunk/vector/v.patch/description.html)
===================================================================
--- grass/trunk/vector/v.patch/v.patch.html (rev 0)
+++ grass/trunk/vector/v.patch/v.patch.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,49 @@
+<h2>DESCRIPTION</h2>
+
+<em>v.patch</em> allows the user to combine any number of
+vector map layers together to create one composite vector
+map layer.
+If the table structures are identical, attributes are
+transferred to the new table.
+
+<h2>NOTES</h2>
+
+Any vectors that are duplicated among the maps being
+patched together (e.g., border lines) will have to be
+edited or removed after <em>v.patch</em> is run. Such
+editing can be done automatically using
+<em><a HREF="v.clean.html">v.clean</a></em> (tool=snap,break,rmdupl).
+
+
+<h2>EXAMPLES</h2>
+
+Patch together two maps with mixed feature types:
+<div class="code"><pre>
+ v.patch input=geology,streams out=geol_streams
+</pre></div>
+
+<BR>
+Append one map to another:
+<div class="code"><pre>
+ g.copy vect=roads,transport
+ v.patch -a input=railroads output=transport --overwrite
+</pre></div>
+
+
+<h2>SEE ALSO</h2>
+
+<em><a HREF="v.clean.html">v.clean</a></em>,
+<em><a HREF="v.build.html">v.build</a></em>,
+<em><a HREF="v.select.html">v.select</a></em>,
+<em><a HREF="v.overlay.html">v.overlay</a></em>
+
+
+<h2>AUTHORS</h2>
+
+Dave Gerdes, U.S.Army Construction Engineering
+Research Laboratory
+<br>
+Radim Blazek, ITC-Irst, Trento, Italy
+
+<p>
+<i>Last changed: $Date$</i>
Deleted: grass/trunk/vector/v.perturb/description.html
===================================================================
--- grass/trunk/vector/v.perturb/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/vector/v.perturb/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,45 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-<EM>v.perturb</EM>
-reads a vector map of points and writes the same points but
-<EM>perturbs</EM> the eastings and northings by
-adding either a uniform or normal delta value. Perturbation means that
-a variating spatial deviation is added to the coordinates.
-
-<H2>NOTES</H2>
-
-The uniform distribution is always centered about zero.
-The associated <em>parameter</em> is constrained to be positive and
-specifies the maximum of the distribution; the minimum is
-the negation of that parameter. Do perturb into a ring around the
-center, the <em>minimum</em> parameter can be used.
-
-<P>
-
-Usually, the mean (first parameter) of the normal
-distribution is zero (i.e., the distribution is centered at
-zero). The standard deviation (second parameter) is
-naturally constrained to be positive.
-
-<P>
-
-Output vector points are not guaranteed to be contained within the
-current geographic region.
-
-<H2>SEE ALSO</H2>
-
-<EM><A HREF="v.random.html">v.random</A></EM><br>
-<EM><A HREF="v.univar.html">v.univar</A></EM><br>
-
-
-<H2>AUTHOR</H2>
-
-<A HREF="http://mccauley-usa.com/">James Darrell McCauley</A>
-<br>when he was at:
-<A HREF="http://ABE.www.ecn.purdue.edu/ABE/">Agricultural Engineering</A>
-<A HREF="http://www.purdue.edu/">Purdue University</A>
-<P>
-Random number generators originally written in FORTRAN by Wes Peterson and
-translated to C using <i>f2c</i>.
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/vector/v.perturb/v.perturb.html (from rev 32770, grass/trunk/vector/v.perturb/description.html)
===================================================================
--- grass/trunk/vector/v.perturb/v.perturb.html (rev 0)
+++ grass/trunk/vector/v.perturb/v.perturb.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,45 @@
+<H2>DESCRIPTION</H2>
+
+<EM>v.perturb</EM>
+reads a vector map of points and writes the same points but
+<EM>perturbs</EM> the eastings and northings by
+adding either a uniform or normal delta value. Perturbation means that
+a variating spatial deviation is added to the coordinates.
+
+<H2>NOTES</H2>
+
+The uniform distribution is always centered about zero.
+The associated <em>parameter</em> is constrained to be positive and
+specifies the maximum of the distribution; the minimum is
+the negation of that parameter. Do perturb into a ring around the
+center, the <em>minimum</em> parameter can be used.
+
+<P>
+
+Usually, the mean (first parameter) of the normal
+distribution is zero (i.e., the distribution is centered at
+zero). The standard deviation (second parameter) is
+naturally constrained to be positive.
+
+<P>
+
+Output vector points are not guaranteed to be contained within the
+current geographic region.
+
+<H2>SEE ALSO</H2>
+
+<EM><A HREF="v.random.html">v.random</A></EM><br>
+<EM><A HREF="v.univar.html">v.univar</A></EM><br>
+
+
+<H2>AUTHOR</H2>
+
+<A HREF="http://mccauley-usa.com/">James Darrell McCauley</A>
+<br>when he was at:
+<A HREF="http://ABE.www.ecn.purdue.edu/ABE/">Agricultural Engineering</A>
+<A HREF="http://www.purdue.edu/">Purdue University</A>
+<P>
+Random number generators originally written in FORTRAN by Wes Peterson and
+translated to C using <i>f2c</i>.
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/vector/v.proj/description.html
===================================================================
--- grass/trunk/vector/v.proj/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/vector/v.proj/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,67 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-<em>v.proj</em> allows a user to convert a vector map in a specified mapset
-of a specified location (different from current) with projection of input
-location to the vector map in a current mapset of current location with
-projection of current location (both projections are defined by
-corresponding PROJ_INFO files).
-
-
-<H2>NOTES</H2>
-
-If <B>out</B> is not specified it is set to be the same as input map name.
-
-<BR>
-If <B>dbase</B> is not specified it is assumed to be the current database.
-The user only has to specify <B>dbase</B> if the source location is stored
-in another separate GRASS database.
-
-<BR>
-If <B>set</B> is not specified, its name is assumed to be the same as the current
- mapset's name.
-
-<P>
-<EM>v.proj</EM> supports general datum transformations, making use of the
-<EM>PROJ.4</EM> co-ordinate system translation library.
-</P>
-
-<H2>EXAMPLES</H2>
-
-<div class="code"><pre>
-v.proj in=mymap location=latlong mapset=user1
-</pre></div>
-
-<H2>REFERENCES</H2>
-
-<a href=http://proj.maptools.org/>PROJ 4</a>: Projection/datum support library.
-
-<P>
-<B>Further reading</B>
-<ul>
-<li> <a href="http://www.asprs.org/resources/grids/">ASPRS Grids and Datum</a>
-<li> <a href="http://www.mapref.org">MapRef - The Collection of Map Projections and Reference Systems for Europe</a>
-<li> <a href="http://www.remotesensing.org/geotiff/proj_list/">Projections Transform List</a> (PROJ4)
-</ul>
-
-<H2>SEE ALSO</H2>
-
-<EM>
-<A HREF="r.proj.html">r.proj</A>,
-<A HREF="g.proj.html">g.proj</A>,
-<A HREF="g.setproj.html">g.setproj</A>,
-<A HREF="i.rectify.html">i.rectify</A>,
-<A HREF="r.stats.html">r.stats</A>,
-<A HREF="v.sample.html">v.sample</A>,
-<A HREF="v.surf.idw.html">v.surf.idw</A>,
-<A HREF="v.surf.rst.html">v.surf.rst</A>
-</EM>
-
-<H2>AUTHORS</H2>
-
-Irina Kosinovsky, US ARMY CERL
-<BR>
-M.L. Holko, USDA, SCS, NHQ-CGIS
-<BR>
-R.L. Glenn, USDA, SCS, NHQ-CGIS
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/vector/v.proj/v.proj.html (from rev 32770, grass/trunk/vector/v.proj/description.html)
===================================================================
--- grass/trunk/vector/v.proj/v.proj.html (rev 0)
+++ grass/trunk/vector/v.proj/v.proj.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,67 @@
+<H2>DESCRIPTION</H2>
+
+<em>v.proj</em> allows a user to convert a vector map in a specified mapset
+of a specified location (different from current) with projection of input
+location to the vector map in a current mapset of current location with
+projection of current location (both projections are defined by
+corresponding PROJ_INFO files).
+
+
+<H2>NOTES</H2>
+
+If <B>out</B> is not specified it is set to be the same as input map name.
+
+<BR>
+If <B>dbase</B> is not specified it is assumed to be the current database.
+The user only has to specify <B>dbase</B> if the source location is stored
+in another separate GRASS database.
+
+<BR>
+If <B>set</B> is not specified, its name is assumed to be the same as the current
+ mapset's name.
+
+<P>
+<EM>v.proj</EM> supports general datum transformations, making use of the
+<EM>PROJ.4</EM> co-ordinate system translation library.
+</P>
+
+<H2>EXAMPLES</H2>
+
+<div class="code"><pre>
+v.proj in=mymap location=latlong mapset=user1
+</pre></div>
+
+<H2>REFERENCES</H2>
+
+<a href=http://proj.maptools.org/>PROJ 4</a>: Projection/datum support library.
+
+<P>
+<B>Further reading</B>
+<ul>
+<li> <a href="http://www.asprs.org/resources/grids/">ASPRS Grids and Datum</a>
+<li> <a href="http://www.mapref.org">MapRef - The Collection of Map Projections and Reference Systems for Europe</a>
+<li> <a href="http://www.remotesensing.org/geotiff/proj_list/">Projections Transform List</a> (PROJ4)
+</ul>
+
+<H2>SEE ALSO</H2>
+
+<EM>
+<A HREF="r.proj.html">r.proj</A>,
+<A HREF="g.proj.html">g.proj</A>,
+<A HREF="g.setproj.html">g.setproj</A>,
+<A HREF="i.rectify.html">i.rectify</A>,
+<A HREF="r.stats.html">r.stats</A>,
+<A HREF="v.sample.html">v.sample</A>,
+<A HREF="v.surf.idw.html">v.surf.idw</A>,
+<A HREF="v.surf.rst.html">v.surf.rst</A>
+</EM>
+
+<H2>AUTHORS</H2>
+
+Irina Kosinovsky, US ARMY CERL
+<BR>
+M.L. Holko, USDA, SCS, NHQ-CGIS
+<BR>
+R.L. Glenn, USDA, SCS, NHQ-CGIS
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/vector/v.qcount/description.html
===================================================================
--- grass/trunk/vector/v.qcount/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/vector/v.qcount/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,105 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-<EM>v.qcount</EM> chooses <B>n</B> circular quadrats of
-radius <B>r</B> such that they are completely within the
-bounds of the current region and no two quadrats overlap.
-The number of points falling within each quadrat are counted
-and indices are calculated to estimate the departure of
-point locations from complete spatial randomness.
-
-<H2>NOTES</H2>
-
-This program may not work properly with lat-long data. It uses
-<EM>hypot()</EM>
-in two files: <EM>count.c</EM> and <EM>findquads.c</EM>.
-
-<H2>SEE ALSO</H2>
-
-<EM><A HREF="v.random.html">v.random</A></EM>
-
-<P>
-
-<EM>Complete Spatial Randomness and Quadrat Methods</EM> -
-GRASS Tutorial on <EM>v.qcount</EM>
-(only available as older file s.qcount-tutorial.ps),
-
-<P>
-
-General references include:
-
-<BR>
-
-Noel A. C. Cressie.
-<EM>Statistics for Spatial Data</EM>.
-Wiley Series in Probability and Mathematical Statistics. John Wiley
-& Sons, New York, NY, 1st edition, 1991.
-
-<BR>
-
-Brian D. Ripley.
-<EM>Spatial Statistics</EM>.
-John Wiley \& Sons, New York, NY, 1981.
-
-
-<P>
-
-References to the indices include:
-
-<BR>
-
-F. N. David and P. G. Moore.
-Notes on contagious distributions in plant populations.
-<EM>Annals of Botany</EM>,
-18:47-53, 1954.
-
-<BR>
-
-J. B. Douglas. Clustering and aggregation.
-<EM>Sankhya B</EM>,
-37:398-417, 1975.
-
-<BR>
-
-R. A. Fisher, H. G. Thornton, and W. A. Mackenzie.
-The accuracy of the plating method of estimating the density of
-bacterial populations.
-<EM>Annals of Applied Biology</EM>,
-9:325-359, 1922.
-
-<BR>
-
-M. Lloyd.
-Mean crowding.
-<EM>Journal of Animal Ecology</EM>,
-36:1-30, 1967.
-
-<BR>
-
-M. Morista.
-Measuring the dispersion and analysis of distribution patterns.
-<EM>Memoires of the Faculty of Science, Kyushu University, Series E.
-Biology</EM>, 2:215-235, 1959.
-
-<H2>BUGS</H2>
-<P>
-Timestamp not working for header part of counts output. (2000-10-28)
-<P>
-Please send all bug fixes and comments to the author
-or the grass development team. <br>
-<a href="http://grass.itc.it"><tt>http://grass.itc.it</tt></a>.
-
-<H2>AUTHOR</H2>
-
-<A HREF="http://mccauley-usa.com/">James Darrell McCauley</A>
-<A HREF="mailto:darrell at mccauley-usa.com"><darrell at mccauley-usa.com></A>,
-<br>when he was at:
-<A HREF="http://ABE.www.ecn.purdue.edu/ABE/">Agricultural Engineering</A>
-<A HREF="http://www.purdue.edu/">Purdue University</A>
-
-<P>
-Modified for GRASS 5.0 by Eric G. Miller (2000-10-28)
-<BR>
-Modified for GRASS 5.7 by R. Blazek (2004-10-14)
-
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/vector/v.qcount/v.qcount.html (from rev 32770, grass/trunk/vector/v.qcount/description.html)
===================================================================
--- grass/trunk/vector/v.qcount/v.qcount.html (rev 0)
+++ grass/trunk/vector/v.qcount/v.qcount.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,105 @@
+<H2>DESCRIPTION</H2>
+
+<EM>v.qcount</EM> chooses <B>n</B> circular quadrats of
+radius <B>r</B> such that they are completely within the
+bounds of the current region and no two quadrats overlap.
+The number of points falling within each quadrat are counted
+and indices are calculated to estimate the departure of
+point locations from complete spatial randomness.
+
+<H2>NOTES</H2>
+
+This program may not work properly with lat-long data. It uses
+<EM>hypot()</EM>
+in two files: <EM>count.c</EM> and <EM>findquads.c</EM>.
+
+<H2>SEE ALSO</H2>
+
+<EM><A HREF="v.random.html">v.random</A></EM>
+
+<P>
+
+<EM>Complete Spatial Randomness and Quadrat Methods</EM> -
+GRASS Tutorial on <EM>v.qcount</EM>
+(only available as older file s.qcount-tutorial.ps),
+
+<P>
+
+General references include:
+
+<BR>
+
+Noel A. C. Cressie.
+<EM>Statistics for Spatial Data</EM>.
+Wiley Series in Probability and Mathematical Statistics. John Wiley
+& Sons, New York, NY, 1st edition, 1991.
+
+<BR>
+
+Brian D. Ripley.
+<EM>Spatial Statistics</EM>.
+John Wiley \& Sons, New York, NY, 1981.
+
+
+<P>
+
+References to the indices include:
+
+<BR>
+
+F. N. David and P. G. Moore.
+Notes on contagious distributions in plant populations.
+<EM>Annals of Botany</EM>,
+18:47-53, 1954.
+
+<BR>
+
+J. B. Douglas. Clustering and aggregation.
+<EM>Sankhya B</EM>,
+37:398-417, 1975.
+
+<BR>
+
+R. A. Fisher, H. G. Thornton, and W. A. Mackenzie.
+The accuracy of the plating method of estimating the density of
+bacterial populations.
+<EM>Annals of Applied Biology</EM>,
+9:325-359, 1922.
+
+<BR>
+
+M. Lloyd.
+Mean crowding.
+<EM>Journal of Animal Ecology</EM>,
+36:1-30, 1967.
+
+<BR>
+
+M. Morista.
+Measuring the dispersion and analysis of distribution patterns.
+<EM>Memoires of the Faculty of Science, Kyushu University, Series E.
+Biology</EM>, 2:215-235, 1959.
+
+<H2>BUGS</H2>
+<P>
+Timestamp not working for header part of counts output. (2000-10-28)
+<P>
+Please send all bug fixes and comments to the author
+or the grass development team. <br>
+<a href="http://grass.itc.it"><tt>http://grass.itc.it</tt></a>.
+
+<H2>AUTHOR</H2>
+
+<A HREF="http://mccauley-usa.com/">James Darrell McCauley</A>
+<A HREF="mailto:darrell at mccauley-usa.com"><darrell at mccauley-usa.com></A>,
+<br>when he was at:
+<A HREF="http://ABE.www.ecn.purdue.edu/ABE/">Agricultural Engineering</A>
+<A HREF="http://www.purdue.edu/">Purdue University</A>
+
+<P>
+Modified for GRASS 5.0 by Eric G. Miller (2000-10-28)
+<BR>
+Modified for GRASS 5.7 by R. Blazek (2004-10-14)
+
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/vector/v.random/description.html
===================================================================
--- grass/trunk/vector/v.random/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/vector/v.random/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,63 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-<EM>v.random</EM> randomly generates vector points within the
-current region using the selected random number generator.
-
-<p><em>v.random</em> can generate also 3D vector points or
-write random value to attribute table. Point height range or
-attribute value range is controlled by specifying zmin and zmax values.
-Both z values are included in range (<em>zmin >= z <= zmax</em>).
-Generated random attribute value type can be controlled by column
-data type. Use <b>INTEGER</b> column type for integers and
-<b>DOUBLE PRECISION</b> for floating point numbers. Integer values are
-calculated by rounding random floating point number.
-
-<h2>EXAMPLES</h2>
-Generate 20 random points with binary attribute (only 0 or 1):
-<div class="code"><pre>
-v.random output=binary_random n=20 zmin=0 zmax=1 column='binary INTEGER'
-</pre></div>
-
-Get 20 random samples from raster map:
-<div class="code"><pre>
-v.random output=random_samples n=20
-v.db.addtable map=random_samples layer=1 columns='cat INTEGER, sample DOUBLE PRECISION'
-v.what.rast vector=random_samples raster=elevation.10m at PERMANENT layer=1 column=sample
-</pre></div>
-
-Generate 20 random points and sample attribute data from geology (vector) map:
-<div class="code"><pre>
-v.random output=random_samples n=20
-v.db.addtable map=random_samples layer=1 columns='cat integer, geology varchar(100)'
-v.what.vect vector=random_samples layer=1 column=geology qvector=geology at PERMANENT qlayer=1 qcolumn=label
-</pre></div>
-
-<H2>SEE ALSO</H2>
-
-UNIX man pages for <EM>rand(3)</EM> and <EM>drand48(3)</EM>.
-<P>
-<EM>
-<A HREF="g.region.html">g.region</a>,
-<A HREF="r.random.html">r.random</a>,
-<A HREF="v.perturb.html">v.perturb</A>,
-<A HREF="v.sample.html">v.sample</A>
-<a href="v.what.rast.html">v.what.rast</a>
-<a href="v.what.vect.html">v.what.vect</a>
-</EM>
-
-<H2>BUGS</H2>
-
-The RNG used by
-<EM><A HREF="v.perturb.html">v.perturb</A></EM>
-should probably be added to this program.<BR>
-
-<H2>AUTHOR</H2>
-
-<A HREF="http://mccauley-usa.com/">James Darrell McCauley</A>
-<A HREF="mailto:darrell at mccauley-usa.com"><darrell at mccauley-usa.com></A>,
-<br>when he was at:
-<A HREF="http://ABE.www.ecn.purdue.edu/ABE/">Agricultural
-Engineering</A>
-<A HREF="http://www.purdue.edu/">Purdue University</A>
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/vector/v.random/v.random.html (from rev 32770, grass/trunk/vector/v.random/description.html)
===================================================================
--- grass/trunk/vector/v.random/v.random.html (rev 0)
+++ grass/trunk/vector/v.random/v.random.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,63 @@
+<H2>DESCRIPTION</H2>
+
+<EM>v.random</EM> randomly generates vector points within the
+current region using the selected random number generator.
+
+<p><em>v.random</em> can generate also 3D vector points or
+write random value to attribute table. Point height range or
+attribute value range is controlled by specifying zmin and zmax values.
+Both z values are included in range (<em>zmin >= z <= zmax</em>).
+Generated random attribute value type can be controlled by column
+data type. Use <b>INTEGER</b> column type for integers and
+<b>DOUBLE PRECISION</b> for floating point numbers. Integer values are
+calculated by rounding random floating point number.
+
+<h2>EXAMPLES</h2>
+Generate 20 random points with binary attribute (only 0 or 1):
+<div class="code"><pre>
+v.random output=binary_random n=20 zmin=0 zmax=1 column='binary INTEGER'
+</pre></div>
+
+Get 20 random samples from raster map:
+<div class="code"><pre>
+v.random output=random_samples n=20
+v.db.addtable map=random_samples layer=1 columns='cat INTEGER, sample DOUBLE PRECISION'
+v.what.rast vector=random_samples raster=elevation.10m at PERMANENT layer=1 column=sample
+</pre></div>
+
+Generate 20 random points and sample attribute data from geology (vector) map:
+<div class="code"><pre>
+v.random output=random_samples n=20
+v.db.addtable map=random_samples layer=1 columns='cat integer, geology varchar(100)'
+v.what.vect vector=random_samples layer=1 column=geology qvector=geology at PERMANENT qlayer=1 qcolumn=label
+</pre></div>
+
+<H2>SEE ALSO</H2>
+
+UNIX man pages for <EM>rand(3)</EM> and <EM>drand48(3)</EM>.
+<P>
+<EM>
+<A HREF="g.region.html">g.region</a>,
+<A HREF="r.random.html">r.random</a>,
+<A HREF="v.perturb.html">v.perturb</A>,
+<A HREF="v.sample.html">v.sample</A>
+<a href="v.what.rast.html">v.what.rast</a>
+<a href="v.what.vect.html">v.what.vect</a>
+</EM>
+
+<H2>BUGS</H2>
+
+The RNG used by
+<EM><A HREF="v.perturb.html">v.perturb</A></EM>
+should probably be added to this program.<BR>
+
+<H2>AUTHOR</H2>
+
+<A HREF="http://mccauley-usa.com/">James Darrell McCauley</A>
+<A HREF="mailto:darrell at mccauley-usa.com"><darrell at mccauley-usa.com></A>,
+<br>when he was at:
+<A HREF="http://ABE.www.ecn.purdue.edu/ABE/">Agricultural
+Engineering</A>
+<A HREF="http://www.purdue.edu/">Purdue University</A>
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/vector/v.reclass/description.html
===================================================================
--- grass/trunk/vector/v.reclass/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/vector/v.reclass/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,63 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-<EM>v.reclass</EM> allows user to create a new vector map based on the reclassification
-of an existing vector map.
-
-<p>
-Rules file may contain on each row either pair:
-<div class="code"><pre>
-keyword value
-</pre></div>
-(separated by space) or comment beginning by #(hash).
-Definition of new category begins with keyword <I>cat</I> followed by new category value.
-Keyword <I>where</I> specifies SQL where condition.
-
-<H2>EXAMPLE</H2>
-
-<div class="code"><pre>
-v.reclass input=land output=land_u type=boundary rules=land.rcl
-</pre></div>
-
-the rules file contains :
-
-<div class="code"><pre>
-# land reclass file
-cat 1
-where use = 'E13' and owner = 'Jara Cimrman'
-cat 2
-where use = 'E14'
-</pre></div>
-
-Produces a new vector area map <EM>land_u</EM> containing boundaries from <EM>land</EM> with area category values selected
-from database by SQL select statement: <br>
-<I>select id from tland where use = 'E13' and owner = 'Jara Cimrman' </I> changed to category 1;
-<br>
-values selected from database by SQL select statement: <br>
-<I>select id from tland where use = 'E14' </I> changed to category 2.
-
-<H2>NOTES</H2>
-No table is created for reclassed layer if <B>column</B> option is used and column type is
-integer (there is nothing which could be written to the table).
-<P>
-For dissolving common boundaries, see <em><a href="v.dissolve.html">v.dissolve</a></em>.
-
-<H2>BUGS</H2>
-
-No table is created for reclassed layer if <B>rules</B> option is used.
-
-<H2>SEE ALSO</H2>
-
-<em>
-<a HREF="v.dissolve.html">v.dissolve</a>,
-<A HREF="v.extract.html">v.extract</A>
-</em>
-<p>
-<em><a HREF="sql.html">GRASS SQL interface</a></em>
-
-<H2>AUTHOR</H2>
-
-R.L. Glenn, USDA, SCS, NHQ-CGIS<BR>
-from v.reclass to v.db.reclass and later to v.reclass in 5.7 rewritten by Radim Blazek
-
-<p>
-<i>Last changed: $Date$</i>
Copied: grass/trunk/vector/v.reclass/v.reclass.html (from rev 32770, grass/trunk/vector/v.reclass/description.html)
===================================================================
--- grass/trunk/vector/v.reclass/v.reclass.html (rev 0)
+++ grass/trunk/vector/v.reclass/v.reclass.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,63 @@
+<H2>DESCRIPTION</H2>
+
+<EM>v.reclass</EM> allows user to create a new vector map based on the reclassification
+of an existing vector map.
+
+<p>
+Rules file may contain on each row either pair:
+<div class="code"><pre>
+keyword value
+</pre></div>
+(separated by space) or comment beginning by #(hash).
+Definition of new category begins with keyword <I>cat</I> followed by new category value.
+Keyword <I>where</I> specifies SQL where condition.
+
+<H2>EXAMPLE</H2>
+
+<div class="code"><pre>
+v.reclass input=land output=land_u type=boundary rules=land.rcl
+</pre></div>
+
+the rules file contains :
+
+<div class="code"><pre>
+# land reclass file
+cat 1
+where use = 'E13' and owner = 'Jara Cimrman'
+cat 2
+where use = 'E14'
+</pre></div>
+
+Produces a new vector area map <EM>land_u</EM> containing boundaries from <EM>land</EM> with area category values selected
+from database by SQL select statement: <br>
+<I>select id from tland where use = 'E13' and owner = 'Jara Cimrman' </I> changed to category 1;
+<br>
+values selected from database by SQL select statement: <br>
+<I>select id from tland where use = 'E14' </I> changed to category 2.
+
+<H2>NOTES</H2>
+No table is created for reclassed layer if <B>column</B> option is used and column type is
+integer (there is nothing which could be written to the table).
+<P>
+For dissolving common boundaries, see <em><a href="v.dissolve.html">v.dissolve</a></em>.
+
+<H2>BUGS</H2>
+
+No table is created for reclassed layer if <B>rules</B> option is used.
+
+<H2>SEE ALSO</H2>
+
+<em>
+<a HREF="v.dissolve.html">v.dissolve</a>,
+<A HREF="v.extract.html">v.extract</A>
+</em>
+<p>
+<em><a HREF="sql.html">GRASS SQL interface</a></em>
+
+<H2>AUTHOR</H2>
+
+R.L. Glenn, USDA, SCS, NHQ-CGIS<BR>
+from v.reclass to v.db.reclass and later to v.reclass in 5.7 rewritten by Radim Blazek
+
+<p>
+<i>Last changed: $Date$</i>
Deleted: grass/trunk/vector/v.sample/description.html
===================================================================
--- grass/trunk/vector/v.sample/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/vector/v.sample/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,87 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-<EM>v.sample</EM> samples a GRASS raster map at the point
-locations in the input file by either cubic convolution
-interpolation, bilinear interpolation, or nearest neighbor
-sampling (default).
-
-<P>
-
-This program may be especially useful when sampling for
-cross validation of interpolations whose output is a raster
-map.
-
-<H2>NOTES</H2>
-
-The output points will have the easting and northing of the input points.
-The input category value is used. The input attribute, raster value
-and difference is written to output.
-
-<P>
-When NULL values are encountered for a cell, zero value is used
-instead. In these cases, more acurrate results may be obtained
-by using the default nearest neighbor comparisons.
-
-<P>
-
-This program may not work properly with lat-long data when
-the <B>-BC</B> flags are used.
-
-<P>
-
-When interpolation is done (i.e., the <B>-BC</B> flags are
-used), values are assumed to be located at the centroid of
-grid cells. Therefore, current resolution settings are
-important.
-
-<H2>EXAMPLE</H2>
-
-Comparison of "elevation.dem" and "elevation.10m" Spearfish maps
-at random places:
-
-<div class="code"><pre>
-#generate random points:
- v.random output=random n=100
-#add table with one column:
- v.db.addtable random col="el10 double"
-#transfer elevations at random points into table:
- v.what.rast rast=elevation.10m vect=random col=el10
-#verify:
- v.db.select random
-
-#generate sampling from other elevation map:
- v.sample in=random col=el10 rast=elevation.dem out=elev_sample
-
-#verify:
- v.db.select elev_sample
-
-#univariate statistics of differences between elevation maps:
- v.univar elev_sample col=diff type=point
-</pre></div>
-
-
-<H2>SEE ALSO</H2>
-
-<EM>
-<A HREF="v.random.html">v.random</A>,
-<A HREF="g.region.html">g.region</A>
-</EM>
-
-
-<EM>Image Sampling Methods</EM> - GRASS Tutorial on <EM>s.sample</EM>
-(available as
-<A HREF="http://grass.itc.it/gdp/sites/">s.sample-tutorial.ps.gz</A>)
-
-
-<H2>AUTHOR</H2>
-
-<A HREF="http://mccauley-usa.com/">James Darrell McCauley</A>
-<br>when he was at:
-<A HREF="http://ABE.www.ecn.purdue.edu/ABE/">Agricultural Engineering</A>
-<A HREF="http://www.purdue.edu/">Purdue University</A>
-<P>
-Updated for GRASS 5.0 by Eric G. Miller
-<BR>
-Updated for GRASS 5.7 by Radim Blazek
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/vector/v.sample/v.sample.html (from rev 32770, grass/trunk/vector/v.sample/description.html)
===================================================================
--- grass/trunk/vector/v.sample/v.sample.html (rev 0)
+++ grass/trunk/vector/v.sample/v.sample.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,87 @@
+<H2>DESCRIPTION</H2>
+
+<EM>v.sample</EM> samples a GRASS raster map at the point
+locations in the input file by either cubic convolution
+interpolation, bilinear interpolation, or nearest neighbor
+sampling (default).
+
+<P>
+
+This program may be especially useful when sampling for
+cross validation of interpolations whose output is a raster
+map.
+
+<H2>NOTES</H2>
+
+The output points will have the easting and northing of the input points.
+The input category value is used. The input attribute, raster value
+and difference is written to output.
+
+<P>
+When NULL values are encountered for a cell, zero value is used
+instead. In these cases, more acurrate results may be obtained
+by using the default nearest neighbor comparisons.
+
+<P>
+
+This program may not work properly with lat-long data when
+the <B>-BC</B> flags are used.
+
+<P>
+
+When interpolation is done (i.e., the <B>-BC</B> flags are
+used), values are assumed to be located at the centroid of
+grid cells. Therefore, current resolution settings are
+important.
+
+<H2>EXAMPLE</H2>
+
+Comparison of "elevation.dem" and "elevation.10m" Spearfish maps
+at random places:
+
+<div class="code"><pre>
+#generate random points:
+ v.random output=random n=100
+#add table with one column:
+ v.db.addtable random col="el10 double"
+#transfer elevations at random points into table:
+ v.what.rast rast=elevation.10m vect=random col=el10
+#verify:
+ v.db.select random
+
+#generate sampling from other elevation map:
+ v.sample in=random col=el10 rast=elevation.dem out=elev_sample
+
+#verify:
+ v.db.select elev_sample
+
+#univariate statistics of differences between elevation maps:
+ v.univar elev_sample col=diff type=point
+</pre></div>
+
+
+<H2>SEE ALSO</H2>
+
+<EM>
+<A HREF="v.random.html">v.random</A>,
+<A HREF="g.region.html">g.region</A>
+</EM>
+
+
+<EM>Image Sampling Methods</EM> - GRASS Tutorial on <EM>s.sample</EM>
+(available as
+<A HREF="http://grass.itc.it/gdp/sites/">s.sample-tutorial.ps.gz</A>)
+
+
+<H2>AUTHOR</H2>
+
+<A HREF="http://mccauley-usa.com/">James Darrell McCauley</A>
+<br>when he was at:
+<A HREF="http://ABE.www.ecn.purdue.edu/ABE/">Agricultural Engineering</A>
+<A HREF="http://www.purdue.edu/">Purdue University</A>
+<P>
+Updated for GRASS 5.0 by Eric G. Miller
+<BR>
+Updated for GRASS 5.7 by Radim Blazek
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/vector/v.segment/description.html
===================================================================
--- grass/trunk/vector/v.segment/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/vector/v.segment/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,131 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>v.segment</em> generates segments or points from input lines and from
-positions read from a text file or '<tt>stdin</tt>'.
-
-<P>
-The format is:
-<div class="code"><pre>
-P <point id> <line cat> <offset> [<side offset>]
-L <segment id> <line cat> <start offset> <end offset> [<side offset>]
-</pre></div>
-
-<h4>EXAMPLE</h4>
-
-The user could send to <tt>stdin</tt> something like:
-<div class="code"><pre>
-P 1 356 24.56
-P 2 495 12.31
-...
-</pre></div>
-(pipe or redirect from file into the command).<br>
-
-
-<H2>NOTES</H2>
-
-A segment is only created for the first line found of the specified category.
-<P>
-Points are generated along the lines at the given distance(s) from the
-beginning of the vector line.
-<p>
-The side offset is the orthogonal distance from the line. Positive side
-offsets are to the right side of the line going forward, negative offsets
-are to the left (<em>d.vect</em> with <em>display=shape,dir</em> shows
-the direction of vector lines). As the segment distance is measured along the
-original line, side-offset lines will be longer than the start-end segment distance
-for outside corners of curving lines, and shorter for inside corners.
-<P>
-All offsets are measured in map units (see "<em>g.proj -p</em>").
-<P>
-To place a point in the middle of a line, the <em>v.to.db</em> module may be
-used to find the line's length. Then half of that distance can be used as the
-along-line offset.
-
-
-<h2>EXAMPLES</h2>
-
-Spearfish location:
-
-<div class="code"><pre>
-# extract lines from railroad map:
-v.extract railroads out=myrr list=1
-
-# join segments into polyline and reassign category numbers
-v.build.polylines myrr out=myrr_pol
-v.category myrr_pol out=myrailroads option=add
-
-# zoom to an area of interest
-g.region n=4928200 s=4921100 w=605600 e=613200
-
-# show line, category, direction (to find the beginning)
-d.vect myrailroads disp=shape,cat,dir lsize=12
-
-# extract line segment from 400m to 5000m from beginning of line 1
-echo "L 1 1 400 5000" | v.segment myrailroads out=myrailroads_segl
-d.erase
-d.vect myrailroads
-d.vect myrailroads_segl col=green width=2
-
-# set node at 5000m from beginning of line 1
-echo "P 1 1 5000" | v.segment myrailroads out=myrailroads_segp
-d.vect myrailroads_segp icon=basic/circle color=red fcolor=red size=5
-
-# get points from a text file
-cat mypoints.txt | v.segment myrailroads out=myrailroads_mypoints
-
-# create parallel 1km long line segments along first 8km of track,
-# offset 500m to the left of the tracks.
-v.segment myrailroads out=myrailroads_segl_side << EOF
-L 1 1 1000 2000 -500
-L 2 1 3000 4000 -500
-L 3 1 5000 6000 -500
-L 4 1 7000 8000 -500
-EOF
-d.erase
-d.vect myrailroads disp=shape,dir
-d.vect -c myrailroads_segl_side width=2
-
-# A series of points, spaced every 2km along the tracks
-v.segment myrailroads out=myrailroads_pt2km << EOF
-P 1 1 1000
-P 2 1 3000
-P 3 1 5000
-P 4 1 7000
-EOF
-d.vect myrailroads_pt2km icon=basic/circle color=blue fcolor=blue size=5
-
-# A series of points, spaced every 2km along the tracks, offset 500m to the right
-v.segment myrailroads out=myrailroads_pt2kmO500m << EOF
-P 1 1 1000 500
-P 2 1 3000 500
-P 3 1 5000 500
-P 4 1 7000 500
-EOF
-d.vect myrailroads_pt2kmO500m icon=basic/circle color=aqua fcolor=aqua size=5
-</pre></div>
-
-
-<h2>BUGS</h2>
-There is a problem with side-offset parallel line generation for inside corners.
-<!-- in Vect_line_parallel(), v.parallel is also affected -->
-
-
-<h2>SEE ALSO</h2>
-
-<em>
-<a href="lrs.html">LRS tutorial</a> (Linear Referencing System),<BR>
-<a href="d.vect.html">d.vect</a>,
-<a href="v.build.polylines.html">v.build.polylines</a>,
-<a href="v.lrs.segment.html">v.lrs.segment</a>,
-<a href="v.parallel.html">v.parallel</a>,
-<a href="v.split.html">v.split</a>,
-<a HREF="v.to.db.html">v.to.db</a>,
-<a HREF="v.to.points.html">v.to.points</a>
-</em>
-
-<h2>AUTHOR</h2>
-
-Radim Blazek, ITC-Irst, Trento, Italy
-
-<p>
-<i>Last changed: $Date$</i>
Copied: grass/trunk/vector/v.segment/v.segment.html (from rev 32770, grass/trunk/vector/v.segment/description.html)
===================================================================
--- grass/trunk/vector/v.segment/v.segment.html (rev 0)
+++ grass/trunk/vector/v.segment/v.segment.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,131 @@
+<h2>DESCRIPTION</h2>
+
+<em>v.segment</em> generates segments or points from input lines and from
+positions read from a text file or '<tt>stdin</tt>'.
+
+<P>
+The format is:
+<div class="code"><pre>
+P <point id> <line cat> <offset> [<side offset>]
+L <segment id> <line cat> <start offset> <end offset> [<side offset>]
+</pre></div>
+
+<h4>EXAMPLE</h4>
+
+The user could send to <tt>stdin</tt> something like:
+<div class="code"><pre>
+P 1 356 24.56
+P 2 495 12.31
+...
+</pre></div>
+(pipe or redirect from file into the command).<br>
+
+
+<H2>NOTES</H2>
+
+A segment is only created for the first line found of the specified category.
+<P>
+Points are generated along the lines at the given distance(s) from the
+beginning of the vector line.
+<p>
+The side offset is the orthogonal distance from the line. Positive side
+offsets are to the right side of the line going forward, negative offsets
+are to the left (<em>d.vect</em> with <em>display=shape,dir</em> shows
+the direction of vector lines). As the segment distance is measured along the
+original line, side-offset lines will be longer than the start-end segment distance
+for outside corners of curving lines, and shorter for inside corners.
+<P>
+All offsets are measured in map units (see "<em>g.proj -p</em>").
+<P>
+To place a point in the middle of a line, the <em>v.to.db</em> module may be
+used to find the line's length. Then half of that distance can be used as the
+along-line offset.
+
+
+<h2>EXAMPLES</h2>
+
+Spearfish location:
+
+<div class="code"><pre>
+# extract lines from railroad map:
+v.extract railroads out=myrr list=1
+
+# join segments into polyline and reassign category numbers
+v.build.polylines myrr out=myrr_pol
+v.category myrr_pol out=myrailroads option=add
+
+# zoom to an area of interest
+g.region n=4928200 s=4921100 w=605600 e=613200
+
+# show line, category, direction (to find the beginning)
+d.vect myrailroads disp=shape,cat,dir lsize=12
+
+# extract line segment from 400m to 5000m from beginning of line 1
+echo "L 1 1 400 5000" | v.segment myrailroads out=myrailroads_segl
+d.erase
+d.vect myrailroads
+d.vect myrailroads_segl col=green width=2
+
+# set node at 5000m from beginning of line 1
+echo "P 1 1 5000" | v.segment myrailroads out=myrailroads_segp
+d.vect myrailroads_segp icon=basic/circle color=red fcolor=red size=5
+
+# get points from a text file
+cat mypoints.txt | v.segment myrailroads out=myrailroads_mypoints
+
+# create parallel 1km long line segments along first 8km of track,
+# offset 500m to the left of the tracks.
+v.segment myrailroads out=myrailroads_segl_side << EOF
+L 1 1 1000 2000 -500
+L 2 1 3000 4000 -500
+L 3 1 5000 6000 -500
+L 4 1 7000 8000 -500
+EOF
+d.erase
+d.vect myrailroads disp=shape,dir
+d.vect -c myrailroads_segl_side width=2
+
+# A series of points, spaced every 2km along the tracks
+v.segment myrailroads out=myrailroads_pt2km << EOF
+P 1 1 1000
+P 2 1 3000
+P 3 1 5000
+P 4 1 7000
+EOF
+d.vect myrailroads_pt2km icon=basic/circle color=blue fcolor=blue size=5
+
+# A series of points, spaced every 2km along the tracks, offset 500m to the right
+v.segment myrailroads out=myrailroads_pt2kmO500m << EOF
+P 1 1 1000 500
+P 2 1 3000 500
+P 3 1 5000 500
+P 4 1 7000 500
+EOF
+d.vect myrailroads_pt2kmO500m icon=basic/circle color=aqua fcolor=aqua size=5
+</pre></div>
+
+
+<h2>BUGS</h2>
+There is a problem with side-offset parallel line generation for inside corners.
+<!-- in Vect_line_parallel(), v.parallel is also affected -->
+
+
+<h2>SEE ALSO</h2>
+
+<em>
+<a href="lrs.html">LRS tutorial</a> (Linear Referencing System),<BR>
+<a href="d.vect.html">d.vect</a>,
+<a href="v.build.polylines.html">v.build.polylines</a>,
+<a href="v.lrs.segment.html">v.lrs.segment</a>,
+<a href="v.parallel.html">v.parallel</a>,
+<a href="v.split.html">v.split</a>,
+<a HREF="v.to.db.html">v.to.db</a>,
+<a HREF="v.to.points.html">v.to.points</a>
+</em>
+
+<h2>AUTHOR</h2>
+
+Radim Blazek, ITC-Irst, Trento, Italy
+
+<p>
+<i>Last changed: $Date$</i>
Deleted: grass/trunk/vector/v.select/description.html
===================================================================
--- grass/trunk/vector/v.select/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/vector/v.select/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,34 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>v.select</em> allows the user to select features from a vector
-by features from another one.
-
-<h2>NOTES</h2>
-
-<h2>EXAMPLES</h2>
-
-Extract forest fire points from larger fire map:
-
-<div class="code"><pre>
-v.select ainput=fire binput=forest output=forest_fire
-</pre></div>
-<P>
-
-Extract Italian rivers from VMAP0 watercourses map:
-
-<div class="code"><pre>
-v.select ain=watrcrsl_eurnasia_wgs84 bin=italy_area \
- out=watrcrsl_italy op=overlap
-</pre></div>
-
-<h2>SEE ALSO</h2>
-
-<em>
-<a HREF="v.overlay.html">v.overlay</a>,
-<a HREF="sql.html">GRASS SQL interface</a></em>
-
-<h2>AUTHORS</h2>
-
-Radim Blazek
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/vector/v.select/v.select.html (from rev 32770, grass/trunk/vector/v.select/description.html)
===================================================================
--- grass/trunk/vector/v.select/v.select.html (rev 0)
+++ grass/trunk/vector/v.select/v.select.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,34 @@
+<h2>DESCRIPTION</h2>
+
+<em>v.select</em> allows the user to select features from a vector
+by features from another one.
+
+<h2>NOTES</h2>
+
+<h2>EXAMPLES</h2>
+
+Extract forest fire points from larger fire map:
+
+<div class="code"><pre>
+v.select ainput=fire binput=forest output=forest_fire
+</pre></div>
+<P>
+
+Extract Italian rivers from VMAP0 watercourses map:
+
+<div class="code"><pre>
+v.select ain=watrcrsl_eurnasia_wgs84 bin=italy_area \
+ out=watrcrsl_italy op=overlap
+</pre></div>
+
+<h2>SEE ALSO</h2>
+
+<em>
+<a HREF="v.overlay.html">v.overlay</a>,
+<a HREF="sql.html">GRASS SQL interface</a></em>
+
+<h2>AUTHORS</h2>
+
+Radim Blazek
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/vector/v.split/description.html
===================================================================
--- grass/trunk/vector/v.split/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/vector/v.split/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,37 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>v.split</em> split vector lines into shorter segments using a
-maximal distance between nodes.
-
-<h2>EXAMPLE</h2>
-
-Spearfish location:
-
-<div class="code"><pre>
-# insert kilometric nodes to railroad map:
-v.extract railroads out=myrr list=1
-
-# join segments into polyline
-v.build.polylines myrr out=myrr_pol
-v.category myrr out=myrailroads option=add
-
-# show line, category, direction (to find the beginning)
-d.vect myrailroads disp=shape,cat,dir
-
-# insert nodes at 1000m distance (max)
-v.split railroads out=myrailroads_split length=1000
-d.vect myrailroads_split disp=shape,topo
-</pre></div>
-
-<h2>SEE ALSO</h2>
-
-<em>
-<a href="v.build.polylines.html">v.build.polylines</a>,
-<a href="v.segment.html">v.segment</a>
-</em>
-
-<h2>AUTHOR</h2>
-
-Radim Blazek
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/vector/v.split/v.split.html (from rev 32770, grass/trunk/vector/v.split/description.html)
===================================================================
--- grass/trunk/vector/v.split/v.split.html (rev 0)
+++ grass/trunk/vector/v.split/v.split.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,37 @@
+<h2>DESCRIPTION</h2>
+
+<em>v.split</em> split vector lines into shorter segments using a
+maximal distance between nodes.
+
+<h2>EXAMPLE</h2>
+
+Spearfish location:
+
+<div class="code"><pre>
+# insert kilometric nodes to railroad map:
+v.extract railroads out=myrr list=1
+
+# join segments into polyline
+v.build.polylines myrr out=myrr_pol
+v.category myrr out=myrailroads option=add
+
+# show line, category, direction (to find the beginning)
+d.vect myrailroads disp=shape,cat,dir
+
+# insert nodes at 1000m distance (max)
+v.split railroads out=myrailroads_split length=1000
+d.vect myrailroads_split disp=shape,topo
+</pre></div>
+
+<h2>SEE ALSO</h2>
+
+<em>
+<a href="v.build.polylines.html">v.build.polylines</a>,
+<a href="v.segment.html">v.segment</a>
+</em>
+
+<h2>AUTHOR</h2>
+
+Radim Blazek
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/vector/v.support/description.html
===================================================================
--- grass/trunk/vector/v.support/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/vector/v.support/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,27 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>v.support</em> is used to set/update vector map metadata.
-
-<h2>EXAMPLE</h2>
-
-<div class="code"><pre>
-# update scale to 1:24000
-v.support myvectmap scale=24000
-
-# update organization
-v.support myvectmap organization="OSGeo labs"
-v.info myvectmap
-</pre></div>
-
-<H2>SEE ALSO</H2>
-
-<EM>
- <A HREF="v.build.html">v.build</A>,
- <A HREF="v.info.html">v.info</A>
-</EM>
-
-<h2>AUTHOR</h2>
-
-Markus Neteler, Trento
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/vector/v.support/v.support.html (from rev 32770, grass/trunk/vector/v.support/description.html)
===================================================================
--- grass/trunk/vector/v.support/v.support.html (rev 0)
+++ grass/trunk/vector/v.support/v.support.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,27 @@
+<h2>DESCRIPTION</h2>
+
+<em>v.support</em> is used to set/update vector map metadata.
+
+<h2>EXAMPLE</h2>
+
+<div class="code"><pre>
+# update scale to 1:24000
+v.support myvectmap scale=24000
+
+# update organization
+v.support myvectmap organization="OSGeo labs"
+v.info myvectmap
+</pre></div>
+
+<H2>SEE ALSO</H2>
+
+<EM>
+ <A HREF="v.build.html">v.build</A>,
+ <A HREF="v.info.html">v.info</A>
+</EM>
+
+<h2>AUTHOR</h2>
+
+Markus Neteler, Trento
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/vector/v.surf.idw/description.html
===================================================================
--- grass/trunk/vector/v.surf.idw/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/vector/v.surf.idw/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,75 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-<p>
-<EM>v.surf.idw</EM> fills a raster matrix with interpolated
-values generated from a set of irregularly spaced data
-points using numerical approximation (weighted averaging)
-techniques. The interpolated value of a cell is determined
-by values of nearby data points and the distance of the
-cell from those input points. In comparison with other
-methods, numerical approximation allows representation of
-more complex surfaces (particularly those with anomalous
-features), restricts the spatial influence of any errors,
-and generates the interpolated surface from the data
-points.</p>
-
-<P>
-This program allows the user to use a GRASS vector point map file,
-rather than a raster map layer, as input.</p>
-
-
-<H2>NOTES</H2>
-
-<p>
-The amount of memory used by this program is related to the
-number of sites in the current region. If the vector point map is
-very dense (i.e., contains many data points), the program may
-not be able to get all the memory it needs from the
-system. The time required to execute is related to the
-resolution of the current region, after an initial delay
-determined by the time taken to read the input sites file.<p>
-
-<P>
-If the user has a mask set, then interpolation is only done
-for those cells that fall within the mask. However, all
-sites in the current region are used even
-if they fall outside the mask. Sites outside the current
-region are not used in the interpolation. A larger region may
-be set and a mask used to limit interpolation to a smaller area
-if it is desired to use sites from outside the region in the
-interpolation. The <em>-n</em> flag may also be used to
-achieve a similar result.</p>
-
-<p>
-If more than <EM>count</EM> sites fall into one target raster cell,
-the mean of all the site values will determine the cell value (unless
-the -n flag is specifed, in which case only the <EM>count</EM>
-sites closest to the centre of the cell will be interpolated).</p>
-
-<P>
-By setting <EM>npoints=1</EM>, the module can be used
-to calculate raster Voronoi diagrams (Thiessen polygons).</p>
-
-
-<H2>SEE ALSO</H2>
-
-<EM><A HREF="d.vect.html">d.vect</A></EM><br>
-<EM><A HREF="g.region.html">g.region</A></EM><br>
-<EM><A HREF="r.surf.contour.html">r.surf.contour</A></EM><br>
-<EM><A HREF="r.surf.idw.html">r.surf.idw</A></EM><br>
-<EM><A HREF="r.surf.idw2.html">r.surf.idw2</A></EM><br>
-<EM><A HREF="r.surf.gauss.html">r.surf.gauss</A></EM><br>
-<EM><A HREF="r.surf.fractal.html">r.surf.fractal</A></EM><br>
-<EM><A HREF="r.surf.random.html">r.surf.random</A></EM><br>
-<EM><A HREF="v.surf.rst.html">v.surf.rst</A></EM>
-
-<H2>AUTHOR</H2>
-
-Michael Shapiro,
-U.S. Army Construction Engineering
-Research Laboratory
-<BR>
-Improved algorithm (indexes points according to cell and ignores
-points outside current region) by Paul Kelly
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/vector/v.surf.idw/v.surf.idw.html (from rev 32770, grass/trunk/vector/v.surf.idw/description.html)
===================================================================
--- grass/trunk/vector/v.surf.idw/v.surf.idw.html (rev 0)
+++ grass/trunk/vector/v.surf.idw/v.surf.idw.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,75 @@
+<H2>DESCRIPTION</H2>
+
+<p>
+<EM>v.surf.idw</EM> fills a raster matrix with interpolated
+values generated from a set of irregularly spaced data
+points using numerical approximation (weighted averaging)
+techniques. The interpolated value of a cell is determined
+by values of nearby data points and the distance of the
+cell from those input points. In comparison with other
+methods, numerical approximation allows representation of
+more complex surfaces (particularly those with anomalous
+features), restricts the spatial influence of any errors,
+and generates the interpolated surface from the data
+points.</p>
+
+<P>
+This program allows the user to use a GRASS vector point map file,
+rather than a raster map layer, as input.</p>
+
+
+<H2>NOTES</H2>
+
+<p>
+The amount of memory used by this program is related to the
+number of sites in the current region. If the vector point map is
+very dense (i.e., contains many data points), the program may
+not be able to get all the memory it needs from the
+system. The time required to execute is related to the
+resolution of the current region, after an initial delay
+determined by the time taken to read the input sites file.<p>
+
+<P>
+If the user has a mask set, then interpolation is only done
+for those cells that fall within the mask. However, all
+sites in the current region are used even
+if they fall outside the mask. Sites outside the current
+region are not used in the interpolation. A larger region may
+be set and a mask used to limit interpolation to a smaller area
+if it is desired to use sites from outside the region in the
+interpolation. The <em>-n</em> flag may also be used to
+achieve a similar result.</p>
+
+<p>
+If more than <EM>count</EM> sites fall into one target raster cell,
+the mean of all the site values will determine the cell value (unless
+the -n flag is specifed, in which case only the <EM>count</EM>
+sites closest to the centre of the cell will be interpolated).</p>
+
+<P>
+By setting <EM>npoints=1</EM>, the module can be used
+to calculate raster Voronoi diagrams (Thiessen polygons).</p>
+
+
+<H2>SEE ALSO</H2>
+
+<EM><A HREF="d.vect.html">d.vect</A></EM><br>
+<EM><A HREF="g.region.html">g.region</A></EM><br>
+<EM><A HREF="r.surf.contour.html">r.surf.contour</A></EM><br>
+<EM><A HREF="r.surf.idw.html">r.surf.idw</A></EM><br>
+<EM><A HREF="r.surf.idw2.html">r.surf.idw2</A></EM><br>
+<EM><A HREF="r.surf.gauss.html">r.surf.gauss</A></EM><br>
+<EM><A HREF="r.surf.fractal.html">r.surf.fractal</A></EM><br>
+<EM><A HREF="r.surf.random.html">r.surf.random</A></EM><br>
+<EM><A HREF="v.surf.rst.html">v.surf.rst</A></EM>
+
+<H2>AUTHOR</H2>
+
+Michael Shapiro,
+U.S. Army Construction Engineering
+Research Laboratory
+<BR>
+Improved algorithm (indexes points according to cell and ignores
+points outside current region) by Paul Kelly
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/vector/v.surf.rst/description.html
===================================================================
--- grass/trunk/vector/v.surf.rst/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/vector/v.surf.rst/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,357 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>v.surf.rst</em>
-<br>This program performs spatial approximation based on z-values or attributes
-of point or isoline data given in a vector map named <em>input</em> to grid cells in the
-output raster map <em>elev</em> representing a surface. As an option, simultaneously
-with approximation, topographic parameters slope, aspect, profile curvature
-(measured in the direction of the steepest slope), tangential curvature (measured
-in the direction of a tangent to contour line) or mean curvature are computed
-and saved as raster maps specified by the options <em>slope, aspect, pcurv,
-tcurv, mcurv</em> respectively. If <b><em>-d</em></b> flag is set, the program
-outputs partial derivatives f<sub>x</sub>,f<sub>y</sub>,f<sub>xx</sub>,
-f<sub>yy</sub>,f<sub>xy</sub>
-instead of slope, aspect, profile, tangential and mean curvatures respectively.
-If the input data have time stamp, the program creates time stamp for all
-output files.
-
-<p>
-User can define a raster map named <em>maskmap</em>, which will be used
-as a mask. The approximation is skipped for cells which have zero or NULL
-value in mask. NULL values will be assigned to these cells in all output
-raster maps. Data points are checked for identical points and points that
-are closer to each other than the given <em>dmin</em> are removed.
-If sparsely digitized contours or isolines are used as input, additional
-points are computed between each 2 points on a line if the
-distance between them is greater than specified <em>dmax</em>. Parameter
-<em>zmult</em> allows user to rescale the values used for approximation
- (useful e.g. for transformation of
-elevations given in feet to meters, so that the proper values of slopes
-and curvatures can be computed).
-
-<p>
-
-Regularized spline with tension is used for the approximation. The
-<em>tension</em>
-parameter tunes the character of the resulting surface from thin plate
-to membrane.
-Smoothing parameter <em>smooth</em> controls the deviation between the given points
-and the resulting surface and it can be very effective in smoothing
-noisy data while preserving the geometrical properties of the surface.
-With the smoothing parameter set to zero (<em>smooth=0</em>)
-the resulting surface passes exactly through the data points (spatial interpolation
-is performed). When smoothing parameter
-is used, it is also possible to output a vector point file <em>devi</em> containing deviations
-of the resulting surface from the given data.
-
-<p>
-
-If the number of given points is greater than <em>segmax</em>, segmented
-processing is used . The region is split into quadtree-based rectangular segments, each
-having less than <em>segmax</em> points and approximation is performed on
-each segment of the region. To ensure smooth connection of segments
-the approximation function for each segment is computed using the points
-in the given segment and the points in its neighborhood which are in the rectangular
-window surrounding the given segment. The number of points taken for approximation
-is controlled by <em>npmin</em>, the value of which must be larger than <em>segmax</em>.
-User can choose to output vector maps <em>treefile</em> and <em>overfile</em>
-which represent the quad tree used for segmentation and overlapping neighborhoods
-from which additional points for approximation on each segment were taken.
-
-<P>
-
-Predictive error of surface approximation for given parameters can be computed using the
-<b>-c</b> flag. A crossvalidation procedure is then performed using the data given in the vector map
-<em>input</em> and the estimated predictive errors are stored in the vector point file
-<em>cvdev</em>. When using this flag, no raster output files are computed.
-
-Anisotropic surfaces can be interpolated by setting anisotropy angle <em>theta</em>
-and scaling factor <em>scalex</em>.
-The program writes values of selected input and internally computed parameters to
-the history file of raster map
-<b><em>elev</em></b>.
-
-<p>
-
-<h2>NOTES</h2>
-
-<em>v.surf.rst </em>uses regularized spline with tension for approximation
-from vector data. The module does not require input data with topology, therefore
-both level1 (no topology) and level2 (with topology) vector point data are supported.
-Additional points are used for approximation between
-each 2 points on a line if the distance between them is greater than specified
-<em>dmax</em>. If <em>dmax</em> is small (less than cell size) the number of
-added data points can be vary large and slow down approximation significantly.
-The implementation has a segmentation procedure based on quadtrees which
-enhances the efficiency for large data sets. Special color tables are created
-by the program for output raster maps.
-<p>Topographic parameters are computed directly from the approximation
-function so that the important relationships between these parameters are
-preserved. The equations for computation of these parameters and their
-interpretation is described in
-<a href="http://skagit.meas.ncsu.edu/~helena/gmslab/papers/hmg.rev1.ps">Mitasova and Hofierka, 1993</a>
-or Neteler and Mitasova, 2004).
-Slopes and aspect are computed in degrees (0-90 and 1-360 respectively).
-The aspect raster map has value 0 assigned to flat areas (with slope less
-than 0.1%) and to singular points with undefined aspect. Aspect points
-downslope and is 90 to the North, 180 to the West, 270 to the South and
-360 to the East, the values increase counterclockwise. Curvatures are positive
-for convex and negative for concave areas. Singular points with undefined
-curvatures have assigned zero values.
-</p><p><em>Tension</em> and <em>smooth</em>ing allow user to tune the surface character.
-For most landscape scale applications the default values should provide adequate results.
-The program gives warning when significant overshoots appear in the resulting
-surface and higher tension or smoothing should be used.
-
-<!--
-<br>While it is possible to automatize the selection of suitable <em>tension</em>
-and <em>smooth</em>ing, it has not been done yet, so here are some hints
-which may help to choose the proper parameters if the results look "weird".
--->
-To select parameters that will produce a surface with desired properties,
-it is useful to know that the method is scale dependent and the <em>tension</em>
-works as a rescaling parameter (high <em>tension</em> "increases the distances
-between the points" and reduces the range of impact of each point, low<em>
-tension</em> "decreases the distance" and the points influence each other
-over longer range). Surface with <em>tension</em> set too high behaves
-like a membrane (rubber sheet stretched over the data points) with peak
-or pit ("crater") in each given point and everywhere else the surface goes
-rapidly to trend. If digitized contours are used as input data, high tension
-can cause artificial waves along contours. Lower tension and higher smoothing
-is suggested for such a case.
-
-<br>Surface with <em>tension</em> set too low behaves like a stiff steel
-plate and overshoots can appear in areas with rapid change of gradient
-and segmentation can be visible. Increase in tension should solve the problems.
-<br>There are two options how <em>tension</em> can be applied in relation
-to <em>dnorm</em> (dnorm rescales the coordinates depending on the average
-data density so that the size of segments with <em>segmax=</em>40 points
-is around 1 - this ensures the numerical stability of the computation):
-</p><p>1. Default: the given <em>tension</em>
-is applied to normalized data (x/<em>dnorm</em>..), that means that
-the distances are multiplied (rescaled) by <em>tension/dnorm</em>. If density
-of points is changed, e.g., by using higher <em>dmin</em>, the <em>dnorm</em>
-
-changes and <em>tension</em> needs to be changed too to get the same result.
-Because the <em>tension</em> is applied to normalized data its suitable value
-is usually within the 10-100 range and does not depend on the actual scale
-(distances) of the original data (which can be km for regional applications
-or cm for field experiments).
-<br>2. Flag<b> -t </b>: </b>The given <em>tension</em>
-is applied to un-normalized data (rescaled tension = t<em>ension*dnorm</em>/1000
-is applied to normalized data (x/<em>dnorm</em>) and therefore <em>dnorm</em>
-
-cancels out) so here <em>tension</em> truly works as a rescaling parameter.
-For regional applications with distances between points in km. the suitable
-tension can be 500 or higher, for detailed field scale analysis it can
-be 0.1. To help select how much the data need to be rescaled the program
-writes
-<em>dnorm</em> and rescaled tension fi=<em>tension*dnorm</em>/1000 at the
-beginning of the program run. This rescaled <em>tension</em> should be around
-20-30. If it is lower or higher, the given <em>tension</em> parameter
-should be changed accordingly.
-
-</p><p>The default is a recommended choice, however for the applications where
-the user needs to change density of data and preserve the approximation
-character the <b>-t</b> flag can be helpful.</p>
-<p>Anisotropic data (e.g. geologic phenomena) can be interpolated using <em>theta</em>
-and <em>scalex</em> defining orientation
-and ratio of the perpendicular axes put on the longest/shortest side of the feature, respectively.
-<em>Theta</em> is measured in degrees from East, counterclockwise. <em>Scalex</em> is a ratio of axes sizes.
-Setting <em>scalex</em> in the range 0-1, results in a pattern prolonged in the
-direction defined by <em>theta</em>. <em>Scalex</em> value 0.5 means that modeled feature is approximately
-2 times longer in the direction of <em>theta</em> than in the perpendicular direction.
-<em>Scalex</em> value 2 means that axes ratio is reverse resulting in a pattern
-perpendicular to the previous example. Please note that anisotropy
-option has not been extensively tested and may include bugs (for example , topographic
-parameters may not be computed correctly) - if there are
-problems, please report to GRASS bugtracker
-(accessible from <a href="http://grass.itc.it/">http://grass.itc.it/</a>).<br>
-</p>
-
-<!--
-<p>The program gives warning when significant overshoots appear and higher
-tension should be used. However, with tension too high the resulting surface
-changes its behavior to membrane (rubber sheet stretched over the data
-points resulting in a peak or pit in each given point and everywhere else
-the surface goes rapidly to trend). Also smoothing can be used to reduce
-the overshoots.
--->
-
-<p>For data with values changing over several magnitudes (sometimes the
-concentration or density data) it is suggested to interpolate the log of
-the values rather than the original ones.
-</p>
-
-<p>The program checks the numerical stability of the algorithm by computing
-the values in given points, and prints the root mean square deviation (rms)
-found into the history file of raster map <em>elev</em>. For computation
-with smoothing set to 0. rms should be 0. Significant increase in <em>tension</em>
-is suggested if the rms is unexpectedly high for this case. With smoothing
-parameter greater than zero the surface will not pass exactly through the
-data points and the higher the parameter the closer the surface will be
-to the trend. The rms then represents a measure of smoothing effect on
-data. More detailed analysis of smoothing effects can be performed using
-the output deviations option.
-</p>
-
-<h3>SQL support</h3>
-
-Using the <em>where</em> parameter, the interpolation can be limited to use
-only a subset of the input vectors.
-
-<P>
-Spearfish example (we simulate randomly distributed elevation measures):
-
-<div class="code"><pre>
-g.region rast=elevation.10m -p
-# random elevation extraction
-r.random elevation.10m vector_output=elevrand n=200
-v.info -c elevrand
-v.db.select elevrand
-
-# interpolation based on all points
-v.surf.rst elevrand zcol=value elev=elev_full
-r.colors elev_full rast=elevation.10m
-d.rast elev_full
-d.vect elevrand
-
-# interpolation based on subset of points (only those over 1300m/asl)
-v.surf.rst elevrand zcol=value elev=elev_partial where="value > 1300"
-r.colors elev_partial rast=elevation.10m
-d.rast elev_partial
-d.vect elevrand where="value > 1300"
-</pre></div>
-
-
-<h3>Cross validation procedure</h3>
-
-The "optimal" approximation parameters for given data can be found using
-a cross-validation (CV) procedure (<b>-c </b>flag).
-The CV procedure is based on removing one input data point at a time,
-performing the approximation for the location of the removed point using
-the remaining data points and calculating the difference between the actual and approximated
-value for the removed data point. The procedure is repeated until every data point has been,
-in turn, removed. This form of CV is also known as the "leave-one-out" or "jack-knife" method
-(Hofierka et al., 2002; Hofierka, 2005). The differences (residuals) are then stored in
-the <em>cvdev</em> output vector map. Please note that during the CV procedure no other output
-files can be set, the approximation is performed only for locations defined by input data.
-To find "optimal parameters", the CV procedure must be iteratively performed for all reasonable
-combinations of the approximation parameters with small incremental steps (e.g. tension, smoothing)
-in order to find a combination with minimal statistical error (also called predictive error)
-defined by root mean squared error (RMSE), mean absolute error (MAE) or other error characteristics.
-A script with loops for tested RST parameters can do the job, necessary statistics can be calculated
-using e.g. <a href="v.univar.html">v.univar</a>. It should be noted that crossvalidation is a time-consuming procedure,
-usually reasonable for up to several thousands of points. For larger data sets, CV should be applied
-to a representative subset of the data. The cross-validation procedure works well only for well-sampled
-phenomena and when minimizing the predictive error is the goal.
-The parameters found by minimizing the predictive (CV) error may not not be the best for
-for poorly sampled phenomena (result could be strongly smoothed with lost details and fluctuations)
-or when significant noise is present that needs to be smoothed out.
-</p>
-
-<p>The program writes the values of parameters used in computation into
-the comment part of history file <em>elev</em> as well as the following values
-which help to evaluate the results and choose the suitable parameters:
-minimum and maximum z values in the data file (zmin_data, zmax_data) and
-in the interpolated raster map (zmin_int, zmax_int), rescaling parameter
-used for normalization (dnorm), which influences the tension.
-</p><p>If visible connection of segments appears, the program should be rerun
-with higher <em>npmin</em> to get more points from the neighborhood of given
-segment and/or with higher tension.
-
-</p><p>When the number of points in a vector map is not too large (less than
-800), the user can skip segmentation by setting <em>segmax</em> to the number
-of data points or <em>segmax=700</em>.
-</p><p>The program gives warning when user wants to interpolate outside the
-rectangle given by minimum and maximum coordinates in the vector map,
-zoom into the area where the given data are is suggested in this case.
-</p><p>When a mask is used, the program takes all points in the given region
-for approximation, including those in the area which is masked out, to
-ensure proper approximation along the border of the mask. It therefore
-does not mask out the data points, if this is desirable, it must be done
-outside <em>v.surf.rst</em>.
-</p>
-
-<p>For examples of applications see
-<a href="http://skagit.meas.ncsu.edu/~helena/gmslab/">GRASS4 implementation</a> and
-<a href="http://skagit.meas.ncsu.edu/~helena/">GRASS5 and GRASS6 implementation</a>
-</p><p>The user must run <a href="g.region.html">g.region</a> before the program
-to set the region and resolution for approximation.
-</p>
-
-<h2>
-SEE ALSO</h2>
-<a href="v.vol.rst.html">v.vol.rst</a>
-
-<h2>
-AUTHORS</h2>
-
-<p><br><em>Original version of program (in FORTRAN) and GRASS enhancements</em>:
-<br>Lubos Mitas, NCSA, University of Illinois at Urbana Champaign, Illinois,
-USA (1990-2000); Department of Physics, North Carolina State University, Raleigh
-<br>Helena Mitasova, USA CERL, Department of Geography, University of Illinois at
-Urbana-Champaign, USA (1990-2001); MEAS, North Carolina State University, Raleigh
-</p><p><em>Modified program (translated to C, adapted for GRASS, new segmentation
-procedure):</em>
-<br>Irina Kosinovsky, US Army CERL, Dave Gerdes, US Army CERL
-</p><p><em>Modifications for new sites format and timestamping:</em>
-<br>Darrel McCauley, Purdue University, Bill Brown, US Army CERL
-</p><p><em>Update for GRASS5.7, GRASS6 and addition of crossvalidation:</em>
-Jaroslav Hofierka, University of Presov; Radim Blazek, ITC-irst
-<br>
-</p>
-<h2> REFERENCES</h2>
-<P>
-<a href="http://skagit.meas.ncsu.edu/~helena/gmslab/papers/IEEEGRSL2005.pdf">
-Mitasova, H., Mitas, L. and Harmon, R.S., 2005,</a>
-Simultaneous spline approximation and topographic analysis for
-lidar elevation data in open source GIS, IEEE GRSL 2 (4), 375- 379.
-<P>
-Hofierka, J., 2005, Interpolation of Radioactivity Data Using Regularized Spline with Tension. Applied GIS, Vol. 1, No. 2,
-pp. 16-01 to 16-13. DOI: 10.2104/ag050016
-</P>
-<P>
-<a href="http://skagit.meas.ncsu.edu/~helena/gmslab/papers/TGIS2002_Hofierka_et_al.pdf">
-Hofierka J., Parajka J., Mitasova H., Mitas L., 2002,</a>
-Multivariate Interpolation of Precipitation Using Regularized Spline with Tension.
-Transactions in GIS 6(2), pp. 135-150.
-</P>
-<P>
-H. Mitasova, L. Mitas, B.M. Brown, D.P. Gerdes, I. Kosinovsky, 1995, Modeling
-spatially and temporally distributed phenomena: New methods and tools for
-GRASS GIS. International Journal of GIS, 9 (4), special issue on Integrating
-GIS and Environmental modeling, 433-446.
-</P>
-<p>
-<a href="http://skagit.meas.ncsu.edu/~helena/gmslab/papers/MG-I-93.pdf">
-Mitasova, H. and Mitas, L., 1993</a>:
-Interpolation by Regularized Spline with Tension:
-I. Theory and Implementation, Mathematical Geology ,25, 641-655.
-</p>
-<p>
-<a href="http://skagit.meas.ncsu.edu/~helena/gmslab/papers/MG-II-93.pdf">
-Mitasova, H. and Hofierka, J., 1993</a>: Interpolation
-by Regularized Spline with Tension: II. Application to Terrain Modeling
-and Surface Geometry Analysis, Mathematical Geology 25, 657-667.
-</p>
-<p>
-<a href="http://skagit.meas.ncsu.edu/~helena/gmslab/papers/CMA1988.pdf">
-Mitas, L., and Mitasova H., 1988, </a> General variational approach to the approximation
-problem, Computers and Mathematics with Applications, v.16, p. 983-992.
-</p>
-
-<p>
-<a href="http://mpa.itc.it/grasstutor/">
-Neteler, M. and Mitasova, H., 2004, Open Source GIS: A GRASS GIS Approach, Second Edition, </a>
-Kluwer International Series in Engineering and Computer Science, 773, Kluwer Academic Press / Springer,
-Boston, Dordrecht, 424 pages.
-</p>
-
-<p>Talmi, A. and Gilat, G., 1977 : Method for Smooth Approximation of Data,
-Journal of Computational Physics, 23, p.93-123.
-</p>
-<p>Wahba, G., 1990, : Spline Models for Observational Data, CNMS-NSF Regional
-Conference series in applied mathematics, 59, SIAM, Philadelphia, Pennsylvania.
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/vector/v.surf.rst/v.surf.rst.html (from rev 32770, grass/trunk/vector/v.surf.rst/description.html)
===================================================================
--- grass/trunk/vector/v.surf.rst/v.surf.rst.html (rev 0)
+++ grass/trunk/vector/v.surf.rst/v.surf.rst.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,357 @@
+<h2>DESCRIPTION</h2>
+
+<em>v.surf.rst</em>
+<br>This program performs spatial approximation based on z-values or attributes
+of point or isoline data given in a vector map named <em>input</em> to grid cells in the
+output raster map <em>elev</em> representing a surface. As an option, simultaneously
+with approximation, topographic parameters slope, aspect, profile curvature
+(measured in the direction of the steepest slope), tangential curvature (measured
+in the direction of a tangent to contour line) or mean curvature are computed
+and saved as raster maps specified by the options <em>slope, aspect, pcurv,
+tcurv, mcurv</em> respectively. If <b><em>-d</em></b> flag is set, the program
+outputs partial derivatives f<sub>x</sub>,f<sub>y</sub>,f<sub>xx</sub>,
+f<sub>yy</sub>,f<sub>xy</sub>
+instead of slope, aspect, profile, tangential and mean curvatures respectively.
+If the input data have time stamp, the program creates time stamp for all
+output files.
+
+<p>
+User can define a raster map named <em>maskmap</em>, which will be used
+as a mask. The approximation is skipped for cells which have zero or NULL
+value in mask. NULL values will be assigned to these cells in all output
+raster maps. Data points are checked for identical points and points that
+are closer to each other than the given <em>dmin</em> are removed.
+If sparsely digitized contours or isolines are used as input, additional
+points are computed between each 2 points on a line if the
+distance between them is greater than specified <em>dmax</em>. Parameter
+<em>zmult</em> allows user to rescale the values used for approximation
+ (useful e.g. for transformation of
+elevations given in feet to meters, so that the proper values of slopes
+and curvatures can be computed).
+
+<p>
+
+Regularized spline with tension is used for the approximation. The
+<em>tension</em>
+parameter tunes the character of the resulting surface from thin plate
+to membrane.
+Smoothing parameter <em>smooth</em> controls the deviation between the given points
+and the resulting surface and it can be very effective in smoothing
+noisy data while preserving the geometrical properties of the surface.
+With the smoothing parameter set to zero (<em>smooth=0</em>)
+the resulting surface passes exactly through the data points (spatial interpolation
+is performed). When smoothing parameter
+is used, it is also possible to output a vector point file <em>devi</em> containing deviations
+of the resulting surface from the given data.
+
+<p>
+
+If the number of given points is greater than <em>segmax</em>, segmented
+processing is used . The region is split into quadtree-based rectangular segments, each
+having less than <em>segmax</em> points and approximation is performed on
+each segment of the region. To ensure smooth connection of segments
+the approximation function for each segment is computed using the points
+in the given segment and the points in its neighborhood which are in the rectangular
+window surrounding the given segment. The number of points taken for approximation
+is controlled by <em>npmin</em>, the value of which must be larger than <em>segmax</em>.
+User can choose to output vector maps <em>treefile</em> and <em>overfile</em>
+which represent the quad tree used for segmentation and overlapping neighborhoods
+from which additional points for approximation on each segment were taken.
+
+<P>
+
+Predictive error of surface approximation for given parameters can be computed using the
+<b>-c</b> flag. A crossvalidation procedure is then performed using the data given in the vector map
+<em>input</em> and the estimated predictive errors are stored in the vector point file
+<em>cvdev</em>. When using this flag, no raster output files are computed.
+
+Anisotropic surfaces can be interpolated by setting anisotropy angle <em>theta</em>
+and scaling factor <em>scalex</em>.
+The program writes values of selected input and internally computed parameters to
+the history file of raster map
+<b><em>elev</em></b>.
+
+<p>
+
+<h2>NOTES</h2>
+
+<em>v.surf.rst </em>uses regularized spline with tension for approximation
+from vector data. The module does not require input data with topology, therefore
+both level1 (no topology) and level2 (with topology) vector point data are supported.
+Additional points are used for approximation between
+each 2 points on a line if the distance between them is greater than specified
+<em>dmax</em>. If <em>dmax</em> is small (less than cell size) the number of
+added data points can be vary large and slow down approximation significantly.
+The implementation has a segmentation procedure based on quadtrees which
+enhances the efficiency for large data sets. Special color tables are created
+by the program for output raster maps.
+<p>Topographic parameters are computed directly from the approximation
+function so that the important relationships between these parameters are
+preserved. The equations for computation of these parameters and their
+interpretation is described in
+<a href="http://skagit.meas.ncsu.edu/~helena/gmslab/papers/hmg.rev1.ps">Mitasova and Hofierka, 1993</a>
+or Neteler and Mitasova, 2004).
+Slopes and aspect are computed in degrees (0-90 and 1-360 respectively).
+The aspect raster map has value 0 assigned to flat areas (with slope less
+than 0.1%) and to singular points with undefined aspect. Aspect points
+downslope and is 90 to the North, 180 to the West, 270 to the South and
+360 to the East, the values increase counterclockwise. Curvatures are positive
+for convex and negative for concave areas. Singular points with undefined
+curvatures have assigned zero values.
+</p><p><em>Tension</em> and <em>smooth</em>ing allow user to tune the surface character.
+For most landscape scale applications the default values should provide adequate results.
+The program gives warning when significant overshoots appear in the resulting
+surface and higher tension or smoothing should be used.
+
+<!--
+<br>While it is possible to automatize the selection of suitable <em>tension</em>
+and <em>smooth</em>ing, it has not been done yet, so here are some hints
+which may help to choose the proper parameters if the results look "weird".
+-->
+To select parameters that will produce a surface with desired properties,
+it is useful to know that the method is scale dependent and the <em>tension</em>
+works as a rescaling parameter (high <em>tension</em> "increases the distances
+between the points" and reduces the range of impact of each point, low<em>
+tension</em> "decreases the distance" and the points influence each other
+over longer range). Surface with <em>tension</em> set too high behaves
+like a membrane (rubber sheet stretched over the data points) with peak
+or pit ("crater") in each given point and everywhere else the surface goes
+rapidly to trend. If digitized contours are used as input data, high tension
+can cause artificial waves along contours. Lower tension and higher smoothing
+is suggested for such a case.
+
+<br>Surface with <em>tension</em> set too low behaves like a stiff steel
+plate and overshoots can appear in areas with rapid change of gradient
+and segmentation can be visible. Increase in tension should solve the problems.
+<br>There are two options how <em>tension</em> can be applied in relation
+to <em>dnorm</em> (dnorm rescales the coordinates depending on the average
+data density so that the size of segments with <em>segmax=</em>40 points
+is around 1 - this ensures the numerical stability of the computation):
+</p><p>1. Default: the given <em>tension</em>
+is applied to normalized data (x/<em>dnorm</em>..), that means that
+the distances are multiplied (rescaled) by <em>tension/dnorm</em>. If density
+of points is changed, e.g., by using higher <em>dmin</em>, the <em>dnorm</em>
+
+changes and <em>tension</em> needs to be changed too to get the same result.
+Because the <em>tension</em> is applied to normalized data its suitable value
+is usually within the 10-100 range and does not depend on the actual scale
+(distances) of the original data (which can be km for regional applications
+or cm for field experiments).
+<br>2. Flag<b> -t </b>: </b>The given <em>tension</em>
+is applied to un-normalized data (rescaled tension = t<em>ension*dnorm</em>/1000
+is applied to normalized data (x/<em>dnorm</em>) and therefore <em>dnorm</em>
+
+cancels out) so here <em>tension</em> truly works as a rescaling parameter.
+For regional applications with distances between points in km. the suitable
+tension can be 500 or higher, for detailed field scale analysis it can
+be 0.1. To help select how much the data need to be rescaled the program
+writes
+<em>dnorm</em> and rescaled tension fi=<em>tension*dnorm</em>/1000 at the
+beginning of the program run. This rescaled <em>tension</em> should be around
+20-30. If it is lower or higher, the given <em>tension</em> parameter
+should be changed accordingly.
+
+</p><p>The default is a recommended choice, however for the applications where
+the user needs to change density of data and preserve the approximation
+character the <b>-t</b> flag can be helpful.</p>
+<p>Anisotropic data (e.g. geologic phenomena) can be interpolated using <em>theta</em>
+and <em>scalex</em> defining orientation
+and ratio of the perpendicular axes put on the longest/shortest side of the feature, respectively.
+<em>Theta</em> is measured in degrees from East, counterclockwise. <em>Scalex</em> is a ratio of axes sizes.
+Setting <em>scalex</em> in the range 0-1, results in a pattern prolonged in the
+direction defined by <em>theta</em>. <em>Scalex</em> value 0.5 means that modeled feature is approximately
+2 times longer in the direction of <em>theta</em> than in the perpendicular direction.
+<em>Scalex</em> value 2 means that axes ratio is reverse resulting in a pattern
+perpendicular to the previous example. Please note that anisotropy
+option has not been extensively tested and may include bugs (for example , topographic
+parameters may not be computed correctly) - if there are
+problems, please report to GRASS bugtracker
+(accessible from <a href="http://grass.itc.it/">http://grass.itc.it/</a>).<br>
+</p>
+
+<!--
+<p>The program gives warning when significant overshoots appear and higher
+tension should be used. However, with tension too high the resulting surface
+changes its behavior to membrane (rubber sheet stretched over the data
+points resulting in a peak or pit in each given point and everywhere else
+the surface goes rapidly to trend). Also smoothing can be used to reduce
+the overshoots.
+-->
+
+<p>For data with values changing over several magnitudes (sometimes the
+concentration or density data) it is suggested to interpolate the log of
+the values rather than the original ones.
+</p>
+
+<p>The program checks the numerical stability of the algorithm by computing
+the values in given points, and prints the root mean square deviation (rms)
+found into the history file of raster map <em>elev</em>. For computation
+with smoothing set to 0. rms should be 0. Significant increase in <em>tension</em>
+is suggested if the rms is unexpectedly high for this case. With smoothing
+parameter greater than zero the surface will not pass exactly through the
+data points and the higher the parameter the closer the surface will be
+to the trend. The rms then represents a measure of smoothing effect on
+data. More detailed analysis of smoothing effects can be performed using
+the output deviations option.
+</p>
+
+<h3>SQL support</h3>
+
+Using the <em>where</em> parameter, the interpolation can be limited to use
+only a subset of the input vectors.
+
+<P>
+Spearfish example (we simulate randomly distributed elevation measures):
+
+<div class="code"><pre>
+g.region rast=elevation.10m -p
+# random elevation extraction
+r.random elevation.10m vector_output=elevrand n=200
+v.info -c elevrand
+v.db.select elevrand
+
+# interpolation based on all points
+v.surf.rst elevrand zcol=value elev=elev_full
+r.colors elev_full rast=elevation.10m
+d.rast elev_full
+d.vect elevrand
+
+# interpolation based on subset of points (only those over 1300m/asl)
+v.surf.rst elevrand zcol=value elev=elev_partial where="value > 1300"
+r.colors elev_partial rast=elevation.10m
+d.rast elev_partial
+d.vect elevrand where="value > 1300"
+</pre></div>
+
+
+<h3>Cross validation procedure</h3>
+
+The "optimal" approximation parameters for given data can be found using
+a cross-validation (CV) procedure (<b>-c </b>flag).
+The CV procedure is based on removing one input data point at a time,
+performing the approximation for the location of the removed point using
+the remaining data points and calculating the difference between the actual and approximated
+value for the removed data point. The procedure is repeated until every data point has been,
+in turn, removed. This form of CV is also known as the "leave-one-out" or "jack-knife" method
+(Hofierka et al., 2002; Hofierka, 2005). The differences (residuals) are then stored in
+the <em>cvdev</em> output vector map. Please note that during the CV procedure no other output
+files can be set, the approximation is performed only for locations defined by input data.
+To find "optimal parameters", the CV procedure must be iteratively performed for all reasonable
+combinations of the approximation parameters with small incremental steps (e.g. tension, smoothing)
+in order to find a combination with minimal statistical error (also called predictive error)
+defined by root mean squared error (RMSE), mean absolute error (MAE) or other error characteristics.
+A script with loops for tested RST parameters can do the job, necessary statistics can be calculated
+using e.g. <a href="v.univar.html">v.univar</a>. It should be noted that crossvalidation is a time-consuming procedure,
+usually reasonable for up to several thousands of points. For larger data sets, CV should be applied
+to a representative subset of the data. The cross-validation procedure works well only for well-sampled
+phenomena and when minimizing the predictive error is the goal.
+The parameters found by minimizing the predictive (CV) error may not not be the best for
+for poorly sampled phenomena (result could be strongly smoothed with lost details and fluctuations)
+or when significant noise is present that needs to be smoothed out.
+</p>
+
+<p>The program writes the values of parameters used in computation into
+the comment part of history file <em>elev</em> as well as the following values
+which help to evaluate the results and choose the suitable parameters:
+minimum and maximum z values in the data file (zmin_data, zmax_data) and
+in the interpolated raster map (zmin_int, zmax_int), rescaling parameter
+used for normalization (dnorm), which influences the tension.
+</p><p>If visible connection of segments appears, the program should be rerun
+with higher <em>npmin</em> to get more points from the neighborhood of given
+segment and/or with higher tension.
+
+</p><p>When the number of points in a vector map is not too large (less than
+800), the user can skip segmentation by setting <em>segmax</em> to the number
+of data points or <em>segmax=700</em>.
+</p><p>The program gives warning when user wants to interpolate outside the
+rectangle given by minimum and maximum coordinates in the vector map,
+zoom into the area where the given data are is suggested in this case.
+</p><p>When a mask is used, the program takes all points in the given region
+for approximation, including those in the area which is masked out, to
+ensure proper approximation along the border of the mask. It therefore
+does not mask out the data points, if this is desirable, it must be done
+outside <em>v.surf.rst</em>.
+</p>
+
+<p>For examples of applications see
+<a href="http://skagit.meas.ncsu.edu/~helena/gmslab/">GRASS4 implementation</a> and
+<a href="http://skagit.meas.ncsu.edu/~helena/">GRASS5 and GRASS6 implementation</a>
+</p><p>The user must run <a href="g.region.html">g.region</a> before the program
+to set the region and resolution for approximation.
+</p>
+
+<h2>
+SEE ALSO</h2>
+<a href="v.vol.rst.html">v.vol.rst</a>
+
+<h2>
+AUTHORS</h2>
+
+<p><br><em>Original version of program (in FORTRAN) and GRASS enhancements</em>:
+<br>Lubos Mitas, NCSA, University of Illinois at Urbana Champaign, Illinois,
+USA (1990-2000); Department of Physics, North Carolina State University, Raleigh
+<br>Helena Mitasova, USA CERL, Department of Geography, University of Illinois at
+Urbana-Champaign, USA (1990-2001); MEAS, North Carolina State University, Raleigh
+</p><p><em>Modified program (translated to C, adapted for GRASS, new segmentation
+procedure):</em>
+<br>Irina Kosinovsky, US Army CERL, Dave Gerdes, US Army CERL
+</p><p><em>Modifications for new sites format and timestamping:</em>
+<br>Darrel McCauley, Purdue University, Bill Brown, US Army CERL
+</p><p><em>Update for GRASS5.7, GRASS6 and addition of crossvalidation:</em>
+Jaroslav Hofierka, University of Presov; Radim Blazek, ITC-irst
+<br>
+</p>
+<h2> REFERENCES</h2>
+<P>
+<a href="http://skagit.meas.ncsu.edu/~helena/gmslab/papers/IEEEGRSL2005.pdf">
+Mitasova, H., Mitas, L. and Harmon, R.S., 2005,</a>
+Simultaneous spline approximation and topographic analysis for
+lidar elevation data in open source GIS, IEEE GRSL 2 (4), 375- 379.
+<P>
+Hofierka, J., 2005, Interpolation of Radioactivity Data Using Regularized Spline with Tension. Applied GIS, Vol. 1, No. 2,
+pp. 16-01 to 16-13. DOI: 10.2104/ag050016
+</P>
+<P>
+<a href="http://skagit.meas.ncsu.edu/~helena/gmslab/papers/TGIS2002_Hofierka_et_al.pdf">
+Hofierka J., Parajka J., Mitasova H., Mitas L., 2002,</a>
+Multivariate Interpolation of Precipitation Using Regularized Spline with Tension.
+Transactions in GIS 6(2), pp. 135-150.
+</P>
+<P>
+H. Mitasova, L. Mitas, B.M. Brown, D.P. Gerdes, I. Kosinovsky, 1995, Modeling
+spatially and temporally distributed phenomena: New methods and tools for
+GRASS GIS. International Journal of GIS, 9 (4), special issue on Integrating
+GIS and Environmental modeling, 433-446.
+</P>
+<p>
+<a href="http://skagit.meas.ncsu.edu/~helena/gmslab/papers/MG-I-93.pdf">
+Mitasova, H. and Mitas, L., 1993</a>:
+Interpolation by Regularized Spline with Tension:
+I. Theory and Implementation, Mathematical Geology ,25, 641-655.
+</p>
+<p>
+<a href="http://skagit.meas.ncsu.edu/~helena/gmslab/papers/MG-II-93.pdf">
+Mitasova, H. and Hofierka, J., 1993</a>: Interpolation
+by Regularized Spline with Tension: II. Application to Terrain Modeling
+and Surface Geometry Analysis, Mathematical Geology 25, 657-667.
+</p>
+<p>
+<a href="http://skagit.meas.ncsu.edu/~helena/gmslab/papers/CMA1988.pdf">
+Mitas, L., and Mitasova H., 1988, </a> General variational approach to the approximation
+problem, Computers and Mathematics with Applications, v.16, p. 983-992.
+</p>
+
+<p>
+<a href="http://mpa.itc.it/grasstutor/">
+Neteler, M. and Mitasova, H., 2004, Open Source GIS: A GRASS GIS Approach, Second Edition, </a>
+Kluwer International Series in Engineering and Computer Science, 773, Kluwer Academic Press / Springer,
+Boston, Dordrecht, 424 pages.
+</p>
+
+<p>Talmi, A. and Gilat, G., 1977 : Method for Smooth Approximation of Data,
+Journal of Computational Physics, 23, p.93-123.
+</p>
+<p>Wahba, G., 1990, : Spline Models for Observational Data, CNMS-NSF Regional
+Conference series in applied mathematics, 59, SIAM, Philadelphia, Pennsylvania.
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/vector/v.to.db/description.html
===================================================================
--- grass/trunk/vector/v.to.db/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/vector/v.to.db/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,178 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-<em>v.to.db</em> loads vector map features or metrics into a database
-table, or prints them (or the SQL queries used to obtain them) in a
-form of a human-readable report. For uploaded/printed category values
-'-1' is used for 'no category' and 'null'/'-' if category cannot be
-found or multiple categories were found.
-
-<H2>NOTES</H2>
-The units <em>miles</em>, <em>feet</em>, <em>meters</em> and
-<em>kilometers</em> are square for <em>option=area</em>.
-<P>
-Feet and acre units are always reported in their common versions
-(i.e. the International Foot, exactly 5280 feet in a mile), even
-when the location's standard map unit is the US Survey foot.
-<p>
-When calculating perimeters in Latitude-Longitude locations, the geodesic
-distance between the vertices is used.
-<p>
-When using <em>option=coor</em> on a vector area map,
-only coordinates of centroids with unique category will be reported.
-<p>
-If the module is apparently slow <em>and</em> the map attributes are
-stored in an external DBMS such as PostgreSQL, it is highly recommended
-to create an index on the key (category) column.
-<p>
-Uploading the vector map attributes to a database requires a table attached to
-a given input vector <em>layer</em>. The <b>print only</b> (<b>-p</b>) mode
-doesn't require a table. Use <em><a href=db.execute.html>db.execute</a></em>
-or <em><a href=v.db.addtable.html>v.db.addtable</a></em> to create a table if
-needed.
-<p>
-Updating the table has to be done column-wise. The <em>column</em> must be
-present in the table, except when using the <b>print only</b> (<b>-p</b>)
-mode. Use <em><a href=db.execute.html>db.execute</a></em> or
-<em><a href=v.db.addcol.html>v.db.addcol</a></em> to add new columns if
-needed.
-
-<H2>EXAMPLES</H2>
-
-<h3>Updating attribute tables</h3>
-
-Upload category numbers to attribute table (used for new map):<br>
-<div class="code"><pre>
-v.to.db map=soils type=area option=cat
-</pre></div>
-
-<p>
-Upload area sizes of each polygon to attribute table:<br>
-<div class="code"><pre>
-v.to.db map=soils type=area option=area col=area_size unit=h
-</pre></div>
-
-<p>
-Upload line lengths (in meters) of each vector line to attribute table
-(use <em>v.category</em> in case of missing categories):<br>
-<div class="code"><pre>
-v.to.db map=roads option=length type=line col=linelength units=me
-</pre></div>
-
-<p>
-Upload x and y coordinates from vector geometry to attribute table:<br>
-<div class="code"><pre>
-v.to.db map=pointsmap option=coor col=x,y
-</pre></div>
-
-<p>
-Upload x, y and z coordinates from vector geometry to attribute table:<br>
-<div class="code"><pre>
-v.to.db map=pointsmap option=coor col=x,y,z
-</pre></div>
-
-<p>
-Transfer attributes from a character column (with numeric contents) to a new
-integer column:<br>
-<div class="code"><pre>
-v.db.addcol usa_income_employment2002 col="FIPS_NUM integer"
-v.to.db usa_income_employment2002 option=query col=FIPS_NUM qcol=STATE_FIPS
-</pre></div>
-
-<P>
-Upload category numbers of left and right area, to an attribute table of
-boundaries common for the areas:<br>
-<div class="code"><pre>
-# add categories for boundaries of the input vector map, in layer 2:
-v.category soils out=mysoils layer=2 type=boundary option=add
-# add a table with columns named "left" and "right" to layer 2 of the input
-# vector map:
-v.db.addtable mysoils layer=2 col="left integer,right integer"
-# upload categories of left and right areas:
-v.to.db mysoils option=sides col=left,right layer=2
-# display the result:
-v.db.select mysoils layer=2
-</pre></div>
-
-<p>
-Compute D<sub>L</sub>, the Fractal Dimension (Mandelbrot, 1982), of the boundary defining a polygon based on the formula:
-<br><tt>
-D = 2 * (log perimeter) / (log area):<br>
-</tt>
-<div class="code"><pre>
-g.copy vect=soils,mysoils
-v.db.addcol mysoils col="d double precision"
-v.to.db mysoils option=fd column="d"
-
-g.region vect=mysoils res=50
-v.to.rast in=mysoils out=soils_fd type=area use=attr column=d
-r.colors map=soils_fd color=gyr
-
-d.mon x0
-d.rast.leg soils_fd
-d.vect mysoils type=boundary
-</pre></div>
-
-<h3>Printing reports</h3>
-
-Report x,y,z coordinates of points in the input vector map:<br>
-<div class="code"><pre>
-v.to.db -p bugsites option=coor type=point
-</pre></div>
-
-Report all area sizes of the input vector map:<br>
-<div class="code"><pre>
-v.to.db -p soils option=area type=boundary units=h
-</pre></div>
-
-<p>
-Report all area sizes of the input vector map, in hectares, sorted by category
-number (requires GNU <em>sort</em> utility installed):<br>
-<div class="code"><pre>
-v.to.db -p soils option=area type=boundary units=h | sort -n
-</pre></div>
-
-<p>
-Report all line lengths of the input vector map, in kilometers:<br>
-<div class="code"><pre>
-v.to.db -p roads option=length type=line units=k
-</pre></div>
-
-<p>
-Report number of features for each category in the input vector map:<br>
-<div class="code"><pre>
-v.to.db -p roads option=count type=line
-</pre></div>
-
-
-<h2>SEE ALSO</h2>
-
-<em>
-<a href="d.what.vect.html">d.what.vect</a>,
-<a href="db.execute.html">db.execute</a>,
-<a href="v.category.html">v.category</a>,
-<a href="v.db.connect">v.db.connect</a>,
-<a href="v.db.addtable.html">v.db.addtable</a>,
-<a href="v.db.addcol.html">v.db.addcol</a>,
-<a href="v.db.connect">v.db.connect</a>,
-<a href="v.distance.html">v.distance</a>,
-<a href="v.report.html">v.report</a>,
-<a href="v.univar.html">v.univar</a>,
-<a href="v.what.html">v.what</a>
-</em>
-
-
-<h2>REFERENCES</h2>
-
-<ul>
- <li>Mandelbrot, B. B. (1982). The fractal geometry of nature. New York: W. H. Freeman.</li>
- <li>Xu, Y. F. & Sun, D. A. (2005). Geotechnique 55, No. 9, 691-695</li>
-</ul>
-
-
-<H2>AUTHOR</H2>
-
-Radim Blazek, ITC-irst, Trento, Italy<br>
-Line sinuousity implemented by Wolf Bergenheim
-
-<p>
-<i>Last changed: $Date$</i>
Copied: grass/trunk/vector/v.to.db/v.to.db.html (from rev 32770, grass/trunk/vector/v.to.db/description.html)
===================================================================
--- grass/trunk/vector/v.to.db/v.to.db.html (rev 0)
+++ grass/trunk/vector/v.to.db/v.to.db.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,178 @@
+<H2>DESCRIPTION</H2>
+
+<em>v.to.db</em> loads vector map features or metrics into a database
+table, or prints them (or the SQL queries used to obtain them) in a
+form of a human-readable report. For uploaded/printed category values
+'-1' is used for 'no category' and 'null'/'-' if category cannot be
+found or multiple categories were found.
+
+<H2>NOTES</H2>
+The units <em>miles</em>, <em>feet</em>, <em>meters</em> and
+<em>kilometers</em> are square for <em>option=area</em>.
+<P>
+Feet and acre units are always reported in their common versions
+(i.e. the International Foot, exactly 5280 feet in a mile), even
+when the location's standard map unit is the US Survey foot.
+<p>
+When calculating perimeters in Latitude-Longitude locations, the geodesic
+distance between the vertices is used.
+<p>
+When using <em>option=coor</em> on a vector area map,
+only coordinates of centroids with unique category will be reported.
+<p>
+If the module is apparently slow <em>and</em> the map attributes are
+stored in an external DBMS such as PostgreSQL, it is highly recommended
+to create an index on the key (category) column.
+<p>
+Uploading the vector map attributes to a database requires a table attached to
+a given input vector <em>layer</em>. The <b>print only</b> (<b>-p</b>) mode
+doesn't require a table. Use <em><a href=db.execute.html>db.execute</a></em>
+or <em><a href=v.db.addtable.html>v.db.addtable</a></em> to create a table if
+needed.
+<p>
+Updating the table has to be done column-wise. The <em>column</em> must be
+present in the table, except when using the <b>print only</b> (<b>-p</b>)
+mode. Use <em><a href=db.execute.html>db.execute</a></em> or
+<em><a href=v.db.addcol.html>v.db.addcol</a></em> to add new columns if
+needed.
+
+<H2>EXAMPLES</H2>
+
+<h3>Updating attribute tables</h3>
+
+Upload category numbers to attribute table (used for new map):<br>
+<div class="code"><pre>
+v.to.db map=soils type=area option=cat
+</pre></div>
+
+<p>
+Upload area sizes of each polygon to attribute table:<br>
+<div class="code"><pre>
+v.to.db map=soils type=area option=area col=area_size unit=h
+</pre></div>
+
+<p>
+Upload line lengths (in meters) of each vector line to attribute table
+(use <em>v.category</em> in case of missing categories):<br>
+<div class="code"><pre>
+v.to.db map=roads option=length type=line col=linelength units=me
+</pre></div>
+
+<p>
+Upload x and y coordinates from vector geometry to attribute table:<br>
+<div class="code"><pre>
+v.to.db map=pointsmap option=coor col=x,y
+</pre></div>
+
+<p>
+Upload x, y and z coordinates from vector geometry to attribute table:<br>
+<div class="code"><pre>
+v.to.db map=pointsmap option=coor col=x,y,z
+</pre></div>
+
+<p>
+Transfer attributes from a character column (with numeric contents) to a new
+integer column:<br>
+<div class="code"><pre>
+v.db.addcol usa_income_employment2002 col="FIPS_NUM integer"
+v.to.db usa_income_employment2002 option=query col=FIPS_NUM qcol=STATE_FIPS
+</pre></div>
+
+<P>
+Upload category numbers of left and right area, to an attribute table of
+boundaries common for the areas:<br>
+<div class="code"><pre>
+# add categories for boundaries of the input vector map, in layer 2:
+v.category soils out=mysoils layer=2 type=boundary option=add
+# add a table with columns named "left" and "right" to layer 2 of the input
+# vector map:
+v.db.addtable mysoils layer=2 col="left integer,right integer"
+# upload categories of left and right areas:
+v.to.db mysoils option=sides col=left,right layer=2
+# display the result:
+v.db.select mysoils layer=2
+</pre></div>
+
+<p>
+Compute D<sub>L</sub>, the Fractal Dimension (Mandelbrot, 1982), of the boundary defining a polygon based on the formula:
+<br><tt>
+D = 2 * (log perimeter) / (log area):<br>
+</tt>
+<div class="code"><pre>
+g.copy vect=soils,mysoils
+v.db.addcol mysoils col="d double precision"
+v.to.db mysoils option=fd column="d"
+
+g.region vect=mysoils res=50
+v.to.rast in=mysoils out=soils_fd type=area use=attr column=d
+r.colors map=soils_fd color=gyr
+
+d.mon x0
+d.rast.leg soils_fd
+d.vect mysoils type=boundary
+</pre></div>
+
+<h3>Printing reports</h3>
+
+Report x,y,z coordinates of points in the input vector map:<br>
+<div class="code"><pre>
+v.to.db -p bugsites option=coor type=point
+</pre></div>
+
+Report all area sizes of the input vector map:<br>
+<div class="code"><pre>
+v.to.db -p soils option=area type=boundary units=h
+</pre></div>
+
+<p>
+Report all area sizes of the input vector map, in hectares, sorted by category
+number (requires GNU <em>sort</em> utility installed):<br>
+<div class="code"><pre>
+v.to.db -p soils option=area type=boundary units=h | sort -n
+</pre></div>
+
+<p>
+Report all line lengths of the input vector map, in kilometers:<br>
+<div class="code"><pre>
+v.to.db -p roads option=length type=line units=k
+</pre></div>
+
+<p>
+Report number of features for each category in the input vector map:<br>
+<div class="code"><pre>
+v.to.db -p roads option=count type=line
+</pre></div>
+
+
+<h2>SEE ALSO</h2>
+
+<em>
+<a href="d.what.vect.html">d.what.vect</a>,
+<a href="db.execute.html">db.execute</a>,
+<a href="v.category.html">v.category</a>,
+<a href="v.db.connect">v.db.connect</a>,
+<a href="v.db.addtable.html">v.db.addtable</a>,
+<a href="v.db.addcol.html">v.db.addcol</a>,
+<a href="v.db.connect">v.db.connect</a>,
+<a href="v.distance.html">v.distance</a>,
+<a href="v.report.html">v.report</a>,
+<a href="v.univar.html">v.univar</a>,
+<a href="v.what.html">v.what</a>
+</em>
+
+
+<h2>REFERENCES</h2>
+
+<ul>
+ <li>Mandelbrot, B. B. (1982). The fractal geometry of nature. New York: W. H. Freeman.</li>
+ <li>Xu, Y. F. & Sun, D. A. (2005). Geotechnique 55, No. 9, 691-695</li>
+</ul>
+
+
+<H2>AUTHOR</H2>
+
+Radim Blazek, ITC-irst, Trento, Italy<br>
+Line sinuousity implemented by Wolf Bergenheim
+
+<p>
+<i>Last changed: $Date$</i>
Deleted: grass/trunk/vector/v.to.points/description.html
===================================================================
--- grass/trunk/vector/v.to.points/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/vector/v.to.points/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,86 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>v.to.points</em> creates points along input lines. The output is a vector with 2 layers.
-Layer 1 holds the category and attributes of the input lines; all points created along the
-same line have the same category, equal to the category of that line. In layer 2 each point
-has it's unique category; other attributes stored in layer 2 are <em>lcat</em> - the
-category of the input line and <em>along</em> - the distance from line's start.
-
-<h2>NOTES</h2>
-
-The <em>dmax</em> parameter is the maximum limit but not an exact
-distance. To place points with exact distance from the beginning
-of the vector line the user should use
-<a HREF="v.segment.html">v.segment</a>.
-
-<p>
-The <em>type</em> parameter is used to control which input vector
-geometry types to convert into points.
-Some caveats to consider about this parameter:
-</p>
-<ul>
-<li>
-Points and centroids can be considered as "lines" with only one
-node. Consequently, the result of selecting <em>point</em> or
-<em>centroid</em> as the type parameter is that all points/centroids
-get written into the output vector. The original category numbers of
-the input points/centroids get written to the '<em><i>lcat</i></em>'
-attribute in layer 2 of the output vector. All values for
-<em>along</em> are zero in the output vector, as only point geometry
-was used for input (there is no linear distance to calculate
-<i>along</i>, as each point/centroid is the start <em><i>and</i></em>
-end of its own "line".</li>
-<li>
-Boundaries are treated as lines, with points getting interpolated
-along the boundary perimeter according to <em>dmax</em>. If two
-adjoining polygons share a topological boundary, the boundary only
-gets converted to points once.</li>
-<li>
-If the <em>type</em> paramter is set to <em>area</em>, the boundary of
-each area is converted to points <i>regardless</i> of whether or not
-there is a topological boundary between adjacent areas. In other
-words, the common boundary of two adjoining areas, for example, gets
-converted to points twice. The centroid is not converted to a point in
-the output vector for <em>type=area</em>.</li>
-</ul>
-
-The -v flag is used to digitize points that fall on the line's vertices <em>only</em>.
-<em>dmax</em> is ignored in this case.
-<p>
-If the -i flag is used in conjunction with the -v flag,
-<em>v.to.points</em> will digitize points on the line vertices, as
-well as interpolate points between line vertices using <em>dmax</em>
-as the maximum allowable spacing.
-<p>
-To get points created for the beginning, middle and end only, use
-the -i switch and set <em>dmax</em> so that:
-<p>
- (length of input line / 2) <= <em>dmax</em> <= length of input line
-<p>
-So if <em>dmax</em> is between 0.5x and 1.0x the line length, you
-will always get points created at exactly the beginning, middle and
-end of the input line.
-
-<h2>EXAMPLE</h2>
-
-In this example, the 't_powerlines' vector lines map in the
-<a HREF="http://grass.itc.it/download/data6.php">Spearfish 6</a>
-location is used to create points along the input lines:
-
-<div class="code"><pre>
-v.to.points in=t_powerlines out=t_powerlines_points dmax=120
-d.vect t_powerlines_points
-</pre></div>
-
-<h2>SEE ALSO</h2>
-
-<em>
-<a HREF="v.segment.html">v.segment</a>,
-<a HREF="v.to.rast.html">v.to.rast</a>,
-<a HREF="v.to.db.html">v.to.db</a></em>
-
-<h2>AUTHOR</h2>
-
-Radim Blazek
-
-<p><i>Last changed: $Date$</i></p>
Copied: grass/trunk/vector/v.to.points/v.to.points.html (from rev 32770, grass/trunk/vector/v.to.points/description.html)
===================================================================
--- grass/trunk/vector/v.to.points/v.to.points.html (rev 0)
+++ grass/trunk/vector/v.to.points/v.to.points.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,86 @@
+<h2>DESCRIPTION</h2>
+
+<em>v.to.points</em> creates points along input lines. The output is a vector with 2 layers.
+Layer 1 holds the category and attributes of the input lines; all points created along the
+same line have the same category, equal to the category of that line. In layer 2 each point
+has it's unique category; other attributes stored in layer 2 are <em>lcat</em> - the
+category of the input line and <em>along</em> - the distance from line's start.
+
+<h2>NOTES</h2>
+
+The <em>dmax</em> parameter is the maximum limit but not an exact
+distance. To place points with exact distance from the beginning
+of the vector line the user should use
+<a HREF="v.segment.html">v.segment</a>.
+
+<p>
+The <em>type</em> parameter is used to control which input vector
+geometry types to convert into points.
+Some caveats to consider about this parameter:
+</p>
+<ul>
+<li>
+Points and centroids can be considered as "lines" with only one
+node. Consequently, the result of selecting <em>point</em> or
+<em>centroid</em> as the type parameter is that all points/centroids
+get written into the output vector. The original category numbers of
+the input points/centroids get written to the '<em><i>lcat</i></em>'
+attribute in layer 2 of the output vector. All values for
+<em>along</em> are zero in the output vector, as only point geometry
+was used for input (there is no linear distance to calculate
+<i>along</i>, as each point/centroid is the start <em><i>and</i></em>
+end of its own "line".</li>
+<li>
+Boundaries are treated as lines, with points getting interpolated
+along the boundary perimeter according to <em>dmax</em>. If two
+adjoining polygons share a topological boundary, the boundary only
+gets converted to points once.</li>
+<li>
+If the <em>type</em> paramter is set to <em>area</em>, the boundary of
+each area is converted to points <i>regardless</i> of whether or not
+there is a topological boundary between adjacent areas. In other
+words, the common boundary of two adjoining areas, for example, gets
+converted to points twice. The centroid is not converted to a point in
+the output vector for <em>type=area</em>.</li>
+</ul>
+
+The -v flag is used to digitize points that fall on the line's vertices <em>only</em>.
+<em>dmax</em> is ignored in this case.
+<p>
+If the -i flag is used in conjunction with the -v flag,
+<em>v.to.points</em> will digitize points on the line vertices, as
+well as interpolate points between line vertices using <em>dmax</em>
+as the maximum allowable spacing.
+<p>
+To get points created for the beginning, middle and end only, use
+the -i switch and set <em>dmax</em> so that:
+<p>
+ (length of input line / 2) <= <em>dmax</em> <= length of input line
+<p>
+So if <em>dmax</em> is between 0.5x and 1.0x the line length, you
+will always get points created at exactly the beginning, middle and
+end of the input line.
+
+<h2>EXAMPLE</h2>
+
+In this example, the 't_powerlines' vector lines map in the
+<a HREF="http://grass.itc.it/download/data6.php">Spearfish 6</a>
+location is used to create points along the input lines:
+
+<div class="code"><pre>
+v.to.points in=t_powerlines out=t_powerlines_points dmax=120
+d.vect t_powerlines_points
+</pre></div>
+
+<h2>SEE ALSO</h2>
+
+<em>
+<a HREF="v.segment.html">v.segment</a>,
+<a HREF="v.to.rast.html">v.to.rast</a>,
+<a HREF="v.to.db.html">v.to.db</a></em>
+
+<h2>AUTHOR</h2>
+
+Radim Blazek
+
+<p><i>Last changed: $Date$</i></p>
Deleted: grass/trunk/vector/v.to.rast/description.html
===================================================================
--- grass/trunk/vector/v.to.rast/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/vector/v.to.rast/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,117 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>v.to.rast</em> transforms GRASS vector map layers into GRASS raster map
-layer format. Optionally, attributes can be converted into raster category
-labels.
-
-
-<h2>NOTES</h2>
-
-<em>v.to.rast</em> will only affect data in areas lying
-inside the boundaries of the current geographic region.
-Before running <em>v.to.rast</em>, the user should
-therefore ensure that the current geographic region is
-correctly set and that the region resolution is at the
-desired level.
-<P>
-Either the <em><b>column</b></em> parameter or the <em><b>value</b></em>
-parameter must be specified. The <em><b>use</b></em> option may be
-specified alone when using the <em>dir</em> option.
-<P>
-<em><b>use</b></em> options are:
-<ul>
-<LI>
-<em>attr</em> - read values from attribute table (default)
-<LI>
-<em>cat</em> - read values from category
-<LI>
-<em>val</em> - use value specified by <em><b>value</b></em> option
-<LI>
-<em>z</em> - use z coordinate (points or contours only)
-<LI>
-<em>dir</em> - output as flow direction in degrees (lines only)
-</ul>
-<P>
-The <em><b>column</b></em> parameter uses an existing column from the vector map
-database table as the category value in the output raster map. Existing table
-columns can be shown by using <em><a href="db.describe.html">db.describe</a></em>.
-<P>
-An empty raster map layer will be created if the vector map layer has not
-been assigned category/attribute labels (e.g., through use of
-<a href="v.category.html">v.category option=add</a>).
-<P>
-Otherwise:
-<ul>
-<LI>
-Labeled areas and/or centroids will produce filled raster coverages with edges
-that straddle the original area boundary <b>as long as the boundary is NOT
-labeled</b>.
-<BR>(Use <tt>v.category option=del type=boundary</tt> to remove.)
-<LI>
-Labeled lines and boundaries will produce lines of raster cells which touch the
-original vector line. This tends to be more aggressive than area-only conversions.
-<LI>
-Points and orphaned centroids will be converted into single cells on the
-resultant raster map.
-</ul>
-<P>
-<P>
-<b>Flow directions</b> are given in degrees counterclockwise from east.
-<P>
-<P>
-Raster category labels are supported for all of <em>use=</em> except <em>use=z</em>.
-
-<h2>EXAMPLES</h2>
-
-<em>1. Convert a vector map and use column SPEED from attribute table</em><br>
-<div class="code"><pre>
-db.describe -c table=vect_map
-
-ncols:3
-Column 1: CAT
-Column 2: SPEED
-Column 3: WIDTH
-</pre></div>
-
-<div class="code"><pre>
-v.to.rast in=vect_map out=raster_map col=SPEED
-</pre></div>
-
-<P>
-<P>
-<em>2. Calculate stream directions from a river vector map (Spearfish)</em><br>
-<div class="code"><pre>
-v.to.rast in=streams out=streamsdir use=dir
-</pre></div>
-</p>
-
-<P>
-<P>
-<em>3. Convert a vector polygon map to raster including descriptive labels (Spearfish)</em><br>
-<div class="code"><pre>
-v.to.rast in=fields out=myfields use=attr col=cat labelcol=label
-r.category myfields
-</pre></div>
-</p>
-
-<h2>SEE ALSO</h2>
-<em>
-<a HREF="db.describe.html">db.describe</a>,
-<a HREF="v.category.html">v.category</a>
-</em>
-<br>
-
-<h2>AUTHORS</h2>
-
-Original code: Michael Shapiro, U.S. Army Construction Engineering Research Laboratory
-<br>
-GRASS 6.0 updates: Radim Blazek, ITC-irst, Trento, Italy
-<br>
-Stream directions: Jaro Hofierka and Helena Mitasova
-<br>
-GRASS 6.3 code cleanup and label support: Brad Douglas
-<p>
-<p>
-<i>Last changed: $Date$</i>
-</p>
-
Copied: grass/trunk/vector/v.to.rast/v.to.rast.html (from rev 32770, grass/trunk/vector/v.to.rast/description.html)
===================================================================
--- grass/trunk/vector/v.to.rast/v.to.rast.html (rev 0)
+++ grass/trunk/vector/v.to.rast/v.to.rast.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,117 @@
+<h2>DESCRIPTION</h2>
+
+<em>v.to.rast</em> transforms GRASS vector map layers into GRASS raster map
+layer format. Optionally, attributes can be converted into raster category
+labels.
+
+
+<h2>NOTES</h2>
+
+<em>v.to.rast</em> will only affect data in areas lying
+inside the boundaries of the current geographic region.
+Before running <em>v.to.rast</em>, the user should
+therefore ensure that the current geographic region is
+correctly set and that the region resolution is at the
+desired level.
+<P>
+Either the <em><b>column</b></em> parameter or the <em><b>value</b></em>
+parameter must be specified. The <em><b>use</b></em> option may be
+specified alone when using the <em>dir</em> option.
+<P>
+<em><b>use</b></em> options are:
+<ul>
+<LI>
+<em>attr</em> - read values from attribute table (default)
+<LI>
+<em>cat</em> - read values from category
+<LI>
+<em>val</em> - use value specified by <em><b>value</b></em> option
+<LI>
+<em>z</em> - use z coordinate (points or contours only)
+<LI>
+<em>dir</em> - output as flow direction in degrees (lines only)
+</ul>
+<P>
+The <em><b>column</b></em> parameter uses an existing column from the vector map
+database table as the category value in the output raster map. Existing table
+columns can be shown by using <em><a href="db.describe.html">db.describe</a></em>.
+<P>
+An empty raster map layer will be created if the vector map layer has not
+been assigned category/attribute labels (e.g., through use of
+<a href="v.category.html">v.category option=add</a>).
+<P>
+Otherwise:
+<ul>
+<LI>
+Labeled areas and/or centroids will produce filled raster coverages with edges
+that straddle the original area boundary <b>as long as the boundary is NOT
+labeled</b>.
+<BR>(Use <tt>v.category option=del type=boundary</tt> to remove.)
+<LI>
+Labeled lines and boundaries will produce lines of raster cells which touch the
+original vector line. This tends to be more aggressive than area-only conversions.
+<LI>
+Points and orphaned centroids will be converted into single cells on the
+resultant raster map.
+</ul>
+<P>
+<P>
+<b>Flow directions</b> are given in degrees counterclockwise from east.
+<P>
+<P>
+Raster category labels are supported for all of <em>use=</em> except <em>use=z</em>.
+
+<h2>EXAMPLES</h2>
+
+<em>1. Convert a vector map and use column SPEED from attribute table</em><br>
+<div class="code"><pre>
+db.describe -c table=vect_map
+
+ncols:3
+Column 1: CAT
+Column 2: SPEED
+Column 3: WIDTH
+</pre></div>
+
+<div class="code"><pre>
+v.to.rast in=vect_map out=raster_map col=SPEED
+</pre></div>
+
+<P>
+<P>
+<em>2. Calculate stream directions from a river vector map (Spearfish)</em><br>
+<div class="code"><pre>
+v.to.rast in=streams out=streamsdir use=dir
+</pre></div>
+</p>
+
+<P>
+<P>
+<em>3. Convert a vector polygon map to raster including descriptive labels (Spearfish)</em><br>
+<div class="code"><pre>
+v.to.rast in=fields out=myfields use=attr col=cat labelcol=label
+r.category myfields
+</pre></div>
+</p>
+
+<h2>SEE ALSO</h2>
+<em>
+<a HREF="db.describe.html">db.describe</a>,
+<a HREF="v.category.html">v.category</a>
+</em>
+<br>
+
+<h2>AUTHORS</h2>
+
+Original code: Michael Shapiro, U.S. Army Construction Engineering Research Laboratory
+<br>
+GRASS 6.0 updates: Radim Blazek, ITC-irst, Trento, Italy
+<br>
+Stream directions: Jaro Hofierka and Helena Mitasova
+<br>
+GRASS 6.3 code cleanup and label support: Brad Douglas
+<p>
+<p>
+<i>Last changed: $Date$</i>
+</p>
+
Deleted: grass/trunk/vector/v.to.rast3/description.html
===================================================================
--- grass/trunk/vector/v.to.rast3/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/vector/v.to.rast3/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,22 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-<EM>v.to.rast3</EM> converts a GRASS 3D vector point map to a GRASS 3dgrid raster
-volume (voxel) map.
-
-<H2>NOTES</H2>
-
-When converting from a 3D vector point layer to a 3dcell volume
-a vector point is converted into a single cube
-representing the location of the vector point.
-
-<H2>SEE ALSO</H2>
-
-<EM><A HREF="g.region.html">g.region</A></EM>
-
-
-<H2>AUTHOR</H2>
-
-Original s.to.rast3: Jaro Hofierka, Geomodel s.r.o.<br>
-Updated by Radim Blazek
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/vector/v.to.rast3/v.to.rast3.html (from rev 32770, grass/trunk/vector/v.to.rast3/description.html)
===================================================================
--- grass/trunk/vector/v.to.rast3/v.to.rast3.html (rev 0)
+++ grass/trunk/vector/v.to.rast3/v.to.rast3.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,22 @@
+<H2>DESCRIPTION</H2>
+
+<EM>v.to.rast3</EM> converts a GRASS 3D vector point map to a GRASS 3dgrid raster
+volume (voxel) map.
+
+<H2>NOTES</H2>
+
+When converting from a 3D vector point layer to a 3dcell volume
+a vector point is converted into a single cube
+representing the location of the vector point.
+
+<H2>SEE ALSO</H2>
+
+<EM><A HREF="g.region.html">g.region</A></EM>
+
+
+<H2>AUTHOR</H2>
+
+Original s.to.rast3: Jaro Hofierka, Geomodel s.r.o.<br>
+Updated by Radim Blazek
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/vector/v.transform/description.html
===================================================================
--- grass/trunk/vector/v.transform/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/vector/v.transform/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,115 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>v.transform</em> performs an affine transformation (translate and rotate) of a
-vector map. An affine transform includes one or several linear transformations
-(scaling, rotation) and translation (shifting). Several linear transformations
-can be combined in a single operation. The command can be used to georeference
-unreferenced vector maps or to modify existing geocoded maps.
-
-<h2>NOTES</h2>
-
-When using an ASCII table containing source and target coordinate pairs,
-in each row four coordinate values separated by white space have to be specified.
-Comments are permitted and have to be indicated by a '#' character.
-<p>
-Example for a points file of a linear transformation from XY to UTM coordinates
-(L: left, R: right, U: upper, L: lower, N, S, W, E):
-
-<div class="code"><pre>
-# Linear transformation from XY to UTM coordinates:
-# 4 maps corners defined
-# UL NW
-# UR NE
-# LR SW
-# LL SE
--584 585 598000 4920770
- 580 585 598020 4920770
- 580 -600 598020 4920750
--584 -600 598000 4920750
-</pre></div>
-
-<p>The ground control points may be also (ir)regularly distributed
-and can be more than four points.</p>
-
-<p>Transformation parameters (i.e. <em>xshift</em>, <em>yshift</em>,
-etc.) can be fetched from attribute table connected to the vector
-map. In this case vector objects can be transformed with different
-parameters based on their category number. If the parameter cannot be
-fetched from the table, default value is used instead.<p>
-
-<h3>Affine Transformation Matrix</h3>
-The affine transfomation matrix can optionally be printed with the '-m'
-flag. The format of the matrix is:
-<div class="code" style="width:30%;"><pre>
-| x_offset a b |
-| y_offset d e |
-</pre></div>
-
-This format can be used in the <a href="http://postgis.refractions.net/docs/ch06.html#id2904406">Affine() function of PostGIS</a>
-[Affine(geom, a, b, d, e, xoff, yoff)], or directly compared to the
-output of a similar operation performed in R.
-
-<h2>EXAMPLE</h2>
-
-<h3>DXF/DWG drawings</h3>
-
-<p>Most DXF/DWG drawings are done within XY coordinate space. To transform
-them to a national grid, we can use 'v.transform' with a 4 point
-transformation.</p>
-
-<div class="code"><pre>
-v.transform -t in=watertowerXY out=watertowerUTM points=wt.points zscale=0.04 zshift=1320
-</pre></div>
-
-<h3>Extrude 2D vector points to 3D based on attribute column values</h3>
-
-Spearfish example with manual table editing for vertical shift:
-
-<div class="code"><pre>
-# create table containing transformation parameters:
-echo "create table archsites_t (cat int, zs double)" | db.execute
-# insert transformation parameters for category 1:
-echo "insert into archsites_t values (1, 1000)" | db.execute
-# insert transformation parameters for category 2 (and so forth):
-echo "insert into archsites_t values (2, 2000)" | db.execute
-
-# perform z transformation:
-v.transform -t input=archsites output=myarchsites3d column="zshift:zs" table="archsites_t"
-# drop table containing transformation parameters:
-echo "drop table archsites_t" | db.execute
-</pre></div>
-The resulting map is a 3D vector map.
-
-<h3>Extrude 2D vector points to 3D based on attribute column values</h3>
-
-Spearfish example with automated elevation extraction for vertical shift:
-
-<div class="code"><pre>
-# work on own map copy:
-g.copy vect=archsites at PERMANENT,myarchsites
-# add new 'zs' column to later store height of each site:
-v.db.addcol myarchsites col="zs double precision"
-
-# set region to elevation map and fetch individual heights:
-g.region rast=elevation.10m -p
-v.what.rast myarchsites rast=elevation.10m col=zs
-# verify:
-v.db.select myarchsites
-
-# perform transformation to 3D
-v.transform -t myarchsites output=myarchsites3d column="zshift:zs" table=myarchsites
-# drop table containing transformation parameters
-v.db.dropcol myarchsites3d col=zs
-</pre></div>
-The resulting map is a 3D vector map.
-
-<h2>SEE ALSO</h2>
-
-<em><a HREF="v.in.ogr.html">v.in.ogr</a></em>
-
-<h2>AUTHOR</h2>
-
-Radim Blazek, ITC-irst, Trento, Italy,<br>
-Column support added by Martin Landa, FBK-irst (formerly ITC-irst), Trento, Italy (2007/09)
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/vector/v.transform/v.transform.html (from rev 32770, grass/trunk/vector/v.transform/description.html)
===================================================================
--- grass/trunk/vector/v.transform/v.transform.html (rev 0)
+++ grass/trunk/vector/v.transform/v.transform.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,115 @@
+<h2>DESCRIPTION</h2>
+
+<em>v.transform</em> performs an affine transformation (translate and rotate) of a
+vector map. An affine transform includes one or several linear transformations
+(scaling, rotation) and translation (shifting). Several linear transformations
+can be combined in a single operation. The command can be used to georeference
+unreferenced vector maps or to modify existing geocoded maps.
+
+<h2>NOTES</h2>
+
+When using an ASCII table containing source and target coordinate pairs,
+in each row four coordinate values separated by white space have to be specified.
+Comments are permitted and have to be indicated by a '#' character.
+<p>
+Example for a points file of a linear transformation from XY to UTM coordinates
+(L: left, R: right, U: upper, L: lower, N, S, W, E):
+
+<div class="code"><pre>
+# Linear transformation from XY to UTM coordinates:
+# 4 maps corners defined
+# UL NW
+# UR NE
+# LR SW
+# LL SE
+-584 585 598000 4920770
+ 580 585 598020 4920770
+ 580 -600 598020 4920750
+-584 -600 598000 4920750
+</pre></div>
+
+<p>The ground control points may be also (ir)regularly distributed
+and can be more than four points.</p>
+
+<p>Transformation parameters (i.e. <em>xshift</em>, <em>yshift</em>,
+etc.) can be fetched from attribute table connected to the vector
+map. In this case vector objects can be transformed with different
+parameters based on their category number. If the parameter cannot be
+fetched from the table, default value is used instead.<p>
+
+<h3>Affine Transformation Matrix</h3>
+The affine transfomation matrix can optionally be printed with the '-m'
+flag. The format of the matrix is:
+<div class="code" style="width:30%;"><pre>
+| x_offset a b |
+| y_offset d e |
+</pre></div>
+
+This format can be used in the <a href="http://postgis.refractions.net/docs/ch06.html#id2904406">Affine() function of PostGIS</a>
+[Affine(geom, a, b, d, e, xoff, yoff)], or directly compared to the
+output of a similar operation performed in R.
+
+<h2>EXAMPLE</h2>
+
+<h3>DXF/DWG drawings</h3>
+
+<p>Most DXF/DWG drawings are done within XY coordinate space. To transform
+them to a national grid, we can use 'v.transform' with a 4 point
+transformation.</p>
+
+<div class="code"><pre>
+v.transform -t in=watertowerXY out=watertowerUTM points=wt.points zscale=0.04 zshift=1320
+</pre></div>
+
+<h3>Extrude 2D vector points to 3D based on attribute column values</h3>
+
+Spearfish example with manual table editing for vertical shift:
+
+<div class="code"><pre>
+# create table containing transformation parameters:
+echo "create table archsites_t (cat int, zs double)" | db.execute
+# insert transformation parameters for category 1:
+echo "insert into archsites_t values (1, 1000)" | db.execute
+# insert transformation parameters for category 2 (and so forth):
+echo "insert into archsites_t values (2, 2000)" | db.execute
+
+# perform z transformation:
+v.transform -t input=archsites output=myarchsites3d column="zshift:zs" table="archsites_t"
+# drop table containing transformation parameters:
+echo "drop table archsites_t" | db.execute
+</pre></div>
+The resulting map is a 3D vector map.
+
+<h3>Extrude 2D vector points to 3D based on attribute column values</h3>
+
+Spearfish example with automated elevation extraction for vertical shift:
+
+<div class="code"><pre>
+# work on own map copy:
+g.copy vect=archsites at PERMANENT,myarchsites
+# add new 'zs' column to later store height of each site:
+v.db.addcol myarchsites col="zs double precision"
+
+# set region to elevation map and fetch individual heights:
+g.region rast=elevation.10m -p
+v.what.rast myarchsites rast=elevation.10m col=zs
+# verify:
+v.db.select myarchsites
+
+# perform transformation to 3D
+v.transform -t myarchsites output=myarchsites3d column="zshift:zs" table=myarchsites
+# drop table containing transformation parameters
+v.db.dropcol myarchsites3d col=zs
+</pre></div>
+The resulting map is a 3D vector map.
+
+<h2>SEE ALSO</h2>
+
+<em><a HREF="v.in.ogr.html">v.in.ogr</a></em>
+
+<h2>AUTHOR</h2>
+
+Radim Blazek, ITC-irst, Trento, Italy,<br>
+Column support added by Martin Landa, FBK-irst (formerly ITC-irst), Trento, Italy (2007/09)
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/vector/v.type/description.html
===================================================================
--- grass/trunk/vector/v.type/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/vector/v.type/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,19 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>v.type</em> changes the type of geometry primitives.
-
-<h2>EXAMPLES</h2>
-
-<em>Convert lines to area boundaries</em><br>
-<div class="code"><pre>
-v.type input=map_l output=map_b type=line,boundary
-</pre></div>
-
-<h2>SEE ALSO</h2>
-<EM><A HREF="v.to.points.html">v.to.points</A></EM>
-
-<h2>AUTHOR</h2>
-
-Radim Blazek, ITC-Irst, Trento, Italy
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/vector/v.type/v.type.html (from rev 32770, grass/trunk/vector/v.type/description.html)
===================================================================
--- grass/trunk/vector/v.type/v.type.html (rev 0)
+++ grass/trunk/vector/v.type/v.type.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,19 @@
+<h2>DESCRIPTION</h2>
+
+<em>v.type</em> changes the type of geometry primitives.
+
+<h2>EXAMPLES</h2>
+
+<em>Convert lines to area boundaries</em><br>
+<div class="code"><pre>
+v.type input=map_l output=map_b type=line,boundary
+</pre></div>
+
+<h2>SEE ALSO</h2>
+<EM><A HREF="v.to.points.html">v.to.points</A></EM>
+
+<h2>AUTHOR</h2>
+
+Radim Blazek, ITC-Irst, Trento, Italy
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/vector/v.univar/description.html
===================================================================
--- grass/trunk/vector/v.univar/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/vector/v.univar/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,36 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-<em>v.univar</em> calculates univariate statistics of vector map features.
-This includes the number of features counted, minimum and maximum values,
-and range.
-Variance and standard deviation is calculated only for points if
-<tt>type=point</tt> is defined.
-
-<P>
-
-Extended statistics adds median, 1st and 3rd quartiles, and 90th
-percentile.
-
-<H2>EXAMPLE</H2>
-
-<div class="code"><pre>
-g.region rast=elevation.10m -p
-v.random out=samples n=100
-v.db.addtable samples col="heights double precision"
-v.what.rast samples rast=elevation.10m col=heights
-v.db.select samples
-
-v.univar samples col=heights type=point
-</pre></div>
-
-
-<H2>SEE ALSO</H2>
-
-<EM><A HREF="v.neighbors.html">v.neighbors</A></EM>
-
-
-<H2>AUTHOR</H2>
-
-Radim Blazek, ITC-irst
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/vector/v.univar/v.univar.html (from rev 32770, grass/trunk/vector/v.univar/description.html)
===================================================================
--- grass/trunk/vector/v.univar/v.univar.html (rev 0)
+++ grass/trunk/vector/v.univar/v.univar.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,36 @@
+<H2>DESCRIPTION</H2>
+
+<em>v.univar</em> calculates univariate statistics of vector map features.
+This includes the number of features counted, minimum and maximum values,
+and range.
+Variance and standard deviation is calculated only for points if
+<tt>type=point</tt> is defined.
+
+<P>
+
+Extended statistics adds median, 1st and 3rd quartiles, and 90th
+percentile.
+
+<H2>EXAMPLE</H2>
+
+<div class="code"><pre>
+g.region rast=elevation.10m -p
+v.random out=samples n=100
+v.db.addtable samples col="heights double precision"
+v.what.rast samples rast=elevation.10m col=heights
+v.db.select samples
+
+v.univar samples col=heights type=point
+</pre></div>
+
+
+<H2>SEE ALSO</H2>
+
+<EM><A HREF="v.neighbors.html">v.neighbors</A></EM>
+
+
+<H2>AUTHOR</H2>
+
+Radim Blazek, ITC-irst
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/vector/v.vol.rst/description.html
===================================================================
--- grass/trunk/vector/v.vol.rst/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/vector/v.vol.rst/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,294 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<p><i>v.vol.rst</i> interpolates values to a 3-dimensional raster map from
-3-dimensional point data (e.g. temperature, rainfall data from climatic
-stations, concentrations from drill holes etc.) given in a 3-D vector
-point file named <i>input</i>. The size of the output
-3d raster map <i>elev</i> is given by the current 3D region. Sometimes, the
-user
-may want to get a 2-D map showing a modelled phenomenon at a
-crossection surface. In that case, <i>cellinp</i> and <i>cellout</i>
-options must be specified and then the output 2D raster map <i>cellout</i>
-contains crossection of the interpolated volume with a surface
-defined by <i>cellinp</i>
-2D raster map. As an option, simultaneously with interpolation,
-geometric parameters of the interpolated
-phenomenon can be computed (magnitude of gradient, direction of
-gradient defined by horizontal and vertical angles), change of gradient,
-Gauss-Kronecker curvature, or mean curvature). These geometric
-parameteres are saved as
-3d raster maps <i>gradient, aspect1, aspect2, ncurv, gcurv, mcurv</i>,
-respectively.
-</p>
-<p>At first, data points are checked for identical points and points
-that are closer to each other than given <i>dmin</i> are removed.
-Parameters <i>wmult</i> and <i>zmult</i> allow user to re-scale
-the w-values and z-coordinates of the point data (useful e.g. for
-transformation of elevations given in feet to meters, so that the
-proper values of gradient and curvatures can be computed).
-Rescaling of z-coordinates is also needed when the distances
-in vertical direction are much smaller than the horizontal
-distances, if that is the case, the value of <i>zmult</i>
-should be selected so that the vertical and horizontal distances
-have about the same magnitude.
-</p>
-<p>Regularized spline with tension method is used in the interpolation.
-The <i>tension</i> parameter controls the distance over which
-each given point influences the resulting volume (with very high tension,
-each point influences only its close neighborhood and the volume goes
-rapidly to trend between the points).
-Higher values of tension parameter reduce the overshoots that
-can appear in volumes with rapid change of gradient. For noisy data, it
-is possible to define a global smoothing parameter, <i>smooth</i>.
-With the
-smoothing parameter set to zero (<i>smooth=0</i>) the resulting volume
-passes exactly through the data points.
-When smoothing is used, it is possible to output a vector map <i>devi</i>
-containing deviations of the resulting volume from the given data. </p>
-<p>User can define a 2D raster map named <i>maskmap</i>, which will
-be used as a mask. The interpolation is skipped for 3-dimensional cells
-whose 2-dimensional projection has zero value in mask. Zero values will
-be assigned to these cells in all output 3d raster maps. </p>
-<p>If the number of given points is greater than 700, segmented
-processing is used. The region is split into 3-dimensional "box"
-segments, each having less than <i>segmax</i> points and interpolation
-is performed on each segment of the region. To ensure the smooth
-connection of segments the interpolation function for each segment is
-computed using the points in given segment
-and the points in its neighborhood. The minimum number of points taken
-for interpolation is controlled by <i>npmin</i> , the value of which
-must
-be larger than <i>segmax</i> and less than 700. This limit of 700 was
-selected to ensure the numerical stability and efficiency of the
-algorithm. </p>
-
-<h3>EXAMPLE</h3>
-
-<!-- TODO: find better data -->
-Spearfish example (we simulate 3D soil range data):
-
-<div class="code"><pre>
-g.region -dp
-# define volume
-g.region res=50 tbres=50 b=0 t=1500 -ap3
-
-# random elevation extraction (2D)
-r.random elevation.10m vector_output=elevrand n=200
-
-# conversion to 3D
-v.db.addcol elevrand col="x double precision, y double precision"
-v.to.db elevrand option=coor col=x,y
-v.db.select elevrand
-
-# create new 3D map
-v.in.db elevrand out=elevrand_3d x=x y=y z=value key=cat
-v.info -c elevrand_3d
-v.info -t elevrand_3d
-
-# remove the now superfluous 'x', 'y' and 'value' (z) columns
-v.db.dropcol elevrand_3d col=x
-v.db.dropcol elevrand_3d col=y
-v.db.dropcol elevrand_3d col=value
-
-# add attribute to interpolate
-# (Soil range types taken from the USDA Soil Survey)
-d.rast soils.range
-d.vect elevrand_3d
-v.db.addcol elevrand_3d col="soilrange integer"
-v.what.rast elevrand_3d col=soilrange rast=soils.range
-
-# fix 0 (no data in raster map) to NULL:
-v.db.update elevrand_3d col=soilrange value=NULL where="soilrange=0"
-v.db.select elevrand_3d
-
-# interpolate volume
-v.vol.rst elevrand_3d wcol=soilrange elev=soilrange zmult=100
-
-# visualize
-nviz elevation.10m vol=soilrange
-
-# export to Paraview
-r.out.vtk elevation.10m out=elev.vtk
-r3.out.vtk elevrand_3d out=volume.vtk
-paraview
-</pre></div>
-
-
-<h3>SQL support</h3>
-
-Using the <em>where</em> parameter, the interpolation can be limited to use
-only a subset of the input vectors.
-
-<div class="code"><pre>
-# preparation as in above example
-v.vol.rst elevrand_3d wcol=soilrange elev=soilrange zmult=100 where="soilrange > 3"
-</pre></div>
-
-
-<h3>Cross validation procedure</h3>
-
-Sometimes it can be difficult to figure out the proper values of
-interpolation parameters. In this case, the user can use a
-crossvalidation procedure using <i>-c</i> flag (a.k.a. "jack-knife"
-method) to find optimal parameters for given data. In this method,
-every point in the input point file is temporarily excluded from the
-computation and interpolation error for this point location is
-computed. During this procedure no output grid files can be
-simultanuously computed. The procedure for larger datasets may take a
-very long time, so it might be worth to use just a sample data
-representing the whole dataset.
-
-<P>
-<i>Example
- (<based on <a href="http://mpa.itc.it/grasstutor/data_menu2nd.phtml">Slovakia3d dataset</a>):</i>
-<P>
-<div class="code"><pre>
-v.info -c precip3d
-v.vol.rst -c input=precip3d wcolumn=precip zmult=50 segmax=700 cvdev=cvdevmap tension=10
-v.db.select cvdevmap
-v.univar cvdevmap col=flt1 type=point
-</pre></div>
-
-From the results, parameters have to be optimized. It is
-recommended to plot the CV error as curve while modifying
-the parameters.
-<P>
-The best approach is to start with <em>tension</em>, <em>smooth</em>
-and <em>zmult</em> with rough steps, or to set <em>zmult</em> to a
-constant somewhere between 30-60. This helps to find minimal RMSE
-values while then finer steps can be used in all parameters. The
-reasonable range is <em>tension</em>=10...100,
-<em>smooth</em>=0.1...1.0, <em>zmult</em>=10...100.
-<p>
-In <em>v.vol.rst</em> the tension parameter is much more sensitive to
-changes than in <em>v.surf.rst</em>,
-therefore the user should always check the
-result by visual inspection. Minimizing CV does not always provide the best
-result, especially when the density of data are insufficient. Then
-the optimal result found by CV is an oversmoothed surface.
-
-
-<h3>Further notes</h3>
-<p><em>v.vol.rst</em> uses regularized spline with tension for
-interpolation from point data (as described in Mitasova and Mitas,
-1993). The implementation has an improved segmentation procedure based
-on Oct-trees which enhances
-the efficiency for large data sets. </p>
-<p>Geometric parameters - magnitude of gradient (<i>gradient</i>),
-horizontal (<i>aspect1</i>) and vertical (<i>aspect2) </i>aspects,
-change of gradient (<i>ncurv</i>), Gauss-Kronecker (<i>gcurv</i>) and
-mean curvatures (<i>mcurv</i>) are computed directly from the
-interpolation function so that the important relationships between
-these parameters are preserved. More information on these parameters
-can be found in Mitasova et al., 1995 or Thorpe, 1979.</p>
-
-<p>The program gives warning when significant overshoots appear and
-higher tension should be used. However, with tension too high the
-resulting volume will have local maximum in each given point
-and everywhere else the volume goes rapidly to trend. With smoothing
-parameter greater than zero the volume
-will not pass through the data points and the higher the parameter the
-closer
-the volume will be to the trend. For theory on smoothing with splines
-see Talmi and Gilat, 1977 or Wahba, 1990. </p>
-<p>If a visible connection of segments appears, the program should be
-rerun with higher <i>npmin</i> to get more points from the
-neighborhood of given segment. </p>
-<p>If the number of points in a vector map is less then 400, <i>segmax</i>
-should be set to 400 so that segmentation is not performed when it is
-not necessary. </p>
-<p>The program gives warning when user wants to interpolate outside the
-"box" given by minimum and maximum coordinates in vector map, zoom into
-the area where the points are is suggested in this case. </p>
-<p>For large data sets (thousands of data points) it is suggested to
-zoom into a smaller representative area and test whether the parameters
-chosen (e.g. defaults) are appropriate. </p>
-<p>The user must run <i>g.region</i> before the program to set the
-3D region for interpolation. </p>
-
-<h2>NOTES</h2>
-The vector points map must be a 3D vector map (x, y, z as geometry).
-The module <a href="v.in.db.html">v.in.db</a> can be used to generate
-a 3D vector map from a table containing x,y,z columns.
-
-<h2>BUGS</h2>
-<b>devi</b> file is written as 2D and deviations are not written as attributes.
-
-<h2>SEE ALSO</h2>
-<a href="g.region.html">g.region</a>,
-<a href="v.in.ascii.html">v.in.ascii</a>,
-<a href="r3.mask.html">r3.mask</a>,
-<a href="v.in.db.html">v.in.db</a>,
-<a href="v.surf.rst.html">v.surf.rst</a>,
-<a href="v.univar.html">v.univar</a>
-
-<h2>AUTHOR</h2>
-<p>Original version of program (in FORTRAN) and GRASS enhancements: <br>
-Lubos Mitas, NCSA, University of Illinois at Urbana-Champaign,
-Illinois, USA, since 2000 at Department of Physics,
-North Carolina State University, Raleigh, USA
-<a href="mailto:lubos_mitas at ncsu.edu">lubos_mitas at ncsu.edu</a><br>
-Helena Mitasova, Department of Marine, Earth and Atmospheric Sciences,
-North Carolina State University, Raleigh, USA, <a
- href="mailto:hmitaso at unity.ncsu.edu">hmitaso at unity.ncsu.edu</a></p>
-<p>Modified program (translated to C, adapted for GRASS, new
-segmentation procedure): <br>
-Irina Kosinovsky, US Army CERL, Champaign, Illinois, USA <br>
-Dave Gerdes, US Army CERL, Champaign, Illinois, USA </p>
-<p>Modifications for g3d library, geometric parameters,
-cross-validation, deviations: <br>
-Jaro Hofierka, Department of Geography and Regional Development,
-University of Presov, Presov, Slovakia, <a
- href="MAILTO:hofierka at fhpv.unipo.sk">hofierka at fhpv.unipo.sk</a>, <a
- href="http://www.geomodel.sk">http://www.geomodel.sk</a> <br>
- </p>
-
-<h2>REFERENCES</h2>
-<p>Hofierka J., Parajka J., Mitasova H., Mitas L., 2002, Multivariate
-Interpolation of Precipitation Using Regularized Spline with Tension.
-Transactions in
-GIS 6, pp. 135-150. </p>
-<p><a href="http://skagit.meas.ncsu.edu/%7Ehelena/gmslab/">Mitas, L.,
-Mitasova, H.</a>, 1999, Spatial Interpolation. In: P.Longley, M.F.
-Goodchild, D.J. Maguire, D.W.Rhind (Eds.), Geographical Information
-Systems: Principles, Techniques, Management and Applications, Wiley,
-pp.481-492 </p>
-<p>Mitas L., Brown W. M., Mitasova H., 1997, <a
- href="http://skagit.meas.ncsu.edu/%7Ehelena/gmslab/lcgfin/cg-mitas.html">Role
-of dynamic cartography in simulations of landscape processes based on
-multi-variate fields.</a> Computers and Geosciences, Vol. 23, No. 4,
-pp. 437-446 (includes CDROM and WWW: www.elsevier.nl/locate/cgvis) </p>
-<p>Mitasova H., Mitas L., Brown W.M., D.P. Gerdes, I.
-Kosinovsky, Baker, T.1995, Modeling spatially and temporally
-distributed phenomena:
-New methods and tools for GRASS GIS. International Journal of GIS, 9
-(4),
-special issue on Integrating GIS and Environmental modeling, 433-446. </p>
-<p> Mitasova, H., Mitas, L., Brown, B., Kosinovsky, I., Baker, T.,
-Gerdes, D. (1994): <a
- href="http://skagit.meas.ncsu.edu/%7Ehelena/gmslab/viz/ches.html">Multidimensional
-interpolation and visualization in GRASS GIS</a> </p>
-<p><a
- href="http://skagit.meas.ncsu.edu/%7Ehelena/gmslab/papers/lmg.rev1.ps">Mitasova
-H. and Mitas L. 1993</a>: Interpolation by Regularized Spline with
-Tension: I. Theory and Implementation, <i>Mathematical Geology</i> 25,
-641-655. </p>
-<p><a
- href="http://skagit.meas.ncsu.edu/%7Ehelena/gmslab/papers/hmg.rev1.ps">Mitasova
-H. and Hofierka J. 1993</a>: Interpolation by Regularized Spline with
-Tension: II. Application to Terrain Modeling and Surface Geometry
-Analysis, <i>Mathematical Geology</i> 25, 657-667. </p>
-<p>Mitasova, H., 1992 : New capabilities for interpolation and
-topographic analysis in GRASS, GRASSclippings 6, No.2 (summer), p.13. </p>
-<p>Wahba, G., 1990 : Spline Models for Observational Data, CNMS-NSF
-Regional Conference series in applied mathematics, 59, SIAM,
-Philadelphia, Pennsylvania. </p>
-<p>Mitas, L., Mitasova H., 1988 : General variational approach to the
-interpolation problem, Computers and Mathematics with Applications 16,
-p. 983 </p>
-<p>Talmi, A. and Gilat, G., 1977 : Method for Smooth Approximation of
-Data, Journal of Computational Physics, 23, p.93-123. </p>
-<p>Thorpe, J. A. (1979): Elementary Topics in Differential Geometry.
-Springer-Verlag, New York, pp. 6-94.</p>
-
-<p><i>Last changed: $Date$</i> </p>
Copied: grass/trunk/vector/v.vol.rst/v.vol.rst.html (from rev 32770, grass/trunk/vector/v.vol.rst/description.html)
===================================================================
--- grass/trunk/vector/v.vol.rst/v.vol.rst.html (rev 0)
+++ grass/trunk/vector/v.vol.rst/v.vol.rst.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,294 @@
+<h2>DESCRIPTION</h2>
+
+<p><i>v.vol.rst</i> interpolates values to a 3-dimensional raster map from
+3-dimensional point data (e.g. temperature, rainfall data from climatic
+stations, concentrations from drill holes etc.) given in a 3-D vector
+point file named <i>input</i>. The size of the output
+3d raster map <i>elev</i> is given by the current 3D region. Sometimes, the
+user
+may want to get a 2-D map showing a modelled phenomenon at a
+crossection surface. In that case, <i>cellinp</i> and <i>cellout</i>
+options must be specified and then the output 2D raster map <i>cellout</i>
+contains crossection of the interpolated volume with a surface
+defined by <i>cellinp</i>
+2D raster map. As an option, simultaneously with interpolation,
+geometric parameters of the interpolated
+phenomenon can be computed (magnitude of gradient, direction of
+gradient defined by horizontal and vertical angles), change of gradient,
+Gauss-Kronecker curvature, or mean curvature). These geometric
+parameteres are saved as
+3d raster maps <i>gradient, aspect1, aspect2, ncurv, gcurv, mcurv</i>,
+respectively.
+</p>
+<p>At first, data points are checked for identical points and points
+that are closer to each other than given <i>dmin</i> are removed.
+Parameters <i>wmult</i> and <i>zmult</i> allow user to re-scale
+the w-values and z-coordinates of the point data (useful e.g. for
+transformation of elevations given in feet to meters, so that the
+proper values of gradient and curvatures can be computed).
+Rescaling of z-coordinates is also needed when the distances
+in vertical direction are much smaller than the horizontal
+distances, if that is the case, the value of <i>zmult</i>
+should be selected so that the vertical and horizontal distances
+have about the same magnitude.
+</p>
+<p>Regularized spline with tension method is used in the interpolation.
+The <i>tension</i> parameter controls the distance over which
+each given point influences the resulting volume (with very high tension,
+each point influences only its close neighborhood and the volume goes
+rapidly to trend between the points).
+Higher values of tension parameter reduce the overshoots that
+can appear in volumes with rapid change of gradient. For noisy data, it
+is possible to define a global smoothing parameter, <i>smooth</i>.
+With the
+smoothing parameter set to zero (<i>smooth=0</i>) the resulting volume
+passes exactly through the data points.
+When smoothing is used, it is possible to output a vector map <i>devi</i>
+containing deviations of the resulting volume from the given data. </p>
+<p>User can define a 2D raster map named <i>maskmap</i>, which will
+be used as a mask. The interpolation is skipped for 3-dimensional cells
+whose 2-dimensional projection has zero value in mask. Zero values will
+be assigned to these cells in all output 3d raster maps. </p>
+<p>If the number of given points is greater than 700, segmented
+processing is used. The region is split into 3-dimensional "box"
+segments, each having less than <i>segmax</i> points and interpolation
+is performed on each segment of the region. To ensure the smooth
+connection of segments the interpolation function for each segment is
+computed using the points in given segment
+and the points in its neighborhood. The minimum number of points taken
+for interpolation is controlled by <i>npmin</i> , the value of which
+must
+be larger than <i>segmax</i> and less than 700. This limit of 700 was
+selected to ensure the numerical stability and efficiency of the
+algorithm. </p>
+
+<h3>EXAMPLE</h3>
+
+<!-- TODO: find better data -->
+Spearfish example (we simulate 3D soil range data):
+
+<div class="code"><pre>
+g.region -dp
+# define volume
+g.region res=50 tbres=50 b=0 t=1500 -ap3
+
+# random elevation extraction (2D)
+r.random elevation.10m vector_output=elevrand n=200
+
+# conversion to 3D
+v.db.addcol elevrand col="x double precision, y double precision"
+v.to.db elevrand option=coor col=x,y
+v.db.select elevrand
+
+# create new 3D map
+v.in.db elevrand out=elevrand_3d x=x y=y z=value key=cat
+v.info -c elevrand_3d
+v.info -t elevrand_3d
+
+# remove the now superfluous 'x', 'y' and 'value' (z) columns
+v.db.dropcol elevrand_3d col=x
+v.db.dropcol elevrand_3d col=y
+v.db.dropcol elevrand_3d col=value
+
+# add attribute to interpolate
+# (Soil range types taken from the USDA Soil Survey)
+d.rast soils.range
+d.vect elevrand_3d
+v.db.addcol elevrand_3d col="soilrange integer"
+v.what.rast elevrand_3d col=soilrange rast=soils.range
+
+# fix 0 (no data in raster map) to NULL:
+v.db.update elevrand_3d col=soilrange value=NULL where="soilrange=0"
+v.db.select elevrand_3d
+
+# interpolate volume
+v.vol.rst elevrand_3d wcol=soilrange elev=soilrange zmult=100
+
+# visualize
+nviz elevation.10m vol=soilrange
+
+# export to Paraview
+r.out.vtk elevation.10m out=elev.vtk
+r3.out.vtk elevrand_3d out=volume.vtk
+paraview
+</pre></div>
+
+
+<h3>SQL support</h3>
+
+Using the <em>where</em> parameter, the interpolation can be limited to use
+only a subset of the input vectors.
+
+<div class="code"><pre>
+# preparation as in above example
+v.vol.rst elevrand_3d wcol=soilrange elev=soilrange zmult=100 where="soilrange > 3"
+</pre></div>
+
+
+<h3>Cross validation procedure</h3>
+
+Sometimes it can be difficult to figure out the proper values of
+interpolation parameters. In this case, the user can use a
+crossvalidation procedure using <i>-c</i> flag (a.k.a. "jack-knife"
+method) to find optimal parameters for given data. In this method,
+every point in the input point file is temporarily excluded from the
+computation and interpolation error for this point location is
+computed. During this procedure no output grid files can be
+simultanuously computed. The procedure for larger datasets may take a
+very long time, so it might be worth to use just a sample data
+representing the whole dataset.
+
+<P>
+<i>Example
+ (<based on <a href="http://mpa.itc.it/grasstutor/data_menu2nd.phtml">Slovakia3d dataset</a>):</i>
+<P>
+<div class="code"><pre>
+v.info -c precip3d
+v.vol.rst -c input=precip3d wcolumn=precip zmult=50 segmax=700 cvdev=cvdevmap tension=10
+v.db.select cvdevmap
+v.univar cvdevmap col=flt1 type=point
+</pre></div>
+
+From the results, parameters have to be optimized. It is
+recommended to plot the CV error as curve while modifying
+the parameters.
+<P>
+The best approach is to start with <em>tension</em>, <em>smooth</em>
+and <em>zmult</em> with rough steps, or to set <em>zmult</em> to a
+constant somewhere between 30-60. This helps to find minimal RMSE
+values while then finer steps can be used in all parameters. The
+reasonable range is <em>tension</em>=10...100,
+<em>smooth</em>=0.1...1.0, <em>zmult</em>=10...100.
+<p>
+In <em>v.vol.rst</em> the tension parameter is much more sensitive to
+changes than in <em>v.surf.rst</em>,
+therefore the user should always check the
+result by visual inspection. Minimizing CV does not always provide the best
+result, especially when the density of data are insufficient. Then
+the optimal result found by CV is an oversmoothed surface.
+
+
+<h3>Further notes</h3>
+<p><em>v.vol.rst</em> uses regularized spline with tension for
+interpolation from point data (as described in Mitasova and Mitas,
+1993). The implementation has an improved segmentation procedure based
+on Oct-trees which enhances
+the efficiency for large data sets. </p>
+<p>Geometric parameters - magnitude of gradient (<i>gradient</i>),
+horizontal (<i>aspect1</i>) and vertical (<i>aspect2) </i>aspects,
+change of gradient (<i>ncurv</i>), Gauss-Kronecker (<i>gcurv</i>) and
+mean curvatures (<i>mcurv</i>) are computed directly from the
+interpolation function so that the important relationships between
+these parameters are preserved. More information on these parameters
+can be found in Mitasova et al., 1995 or Thorpe, 1979.</p>
+
+<p>The program gives warning when significant overshoots appear and
+higher tension should be used. However, with tension too high the
+resulting volume will have local maximum in each given point
+and everywhere else the volume goes rapidly to trend. With smoothing
+parameter greater than zero the volume
+will not pass through the data points and the higher the parameter the
+closer
+the volume will be to the trend. For theory on smoothing with splines
+see Talmi and Gilat, 1977 or Wahba, 1990. </p>
+<p>If a visible connection of segments appears, the program should be
+rerun with higher <i>npmin</i> to get more points from the
+neighborhood of given segment. </p>
+<p>If the number of points in a vector map is less then 400, <i>segmax</i>
+should be set to 400 so that segmentation is not performed when it is
+not necessary. </p>
+<p>The program gives warning when user wants to interpolate outside the
+"box" given by minimum and maximum coordinates in vector map, zoom into
+the area where the points are is suggested in this case. </p>
+<p>For large data sets (thousands of data points) it is suggested to
+zoom into a smaller representative area and test whether the parameters
+chosen (e.g. defaults) are appropriate. </p>
+<p>The user must run <i>g.region</i> before the program to set the
+3D region for interpolation. </p>
+
+<h2>NOTES</h2>
+The vector points map must be a 3D vector map (x, y, z as geometry).
+The module <a href="v.in.db.html">v.in.db</a> can be used to generate
+a 3D vector map from a table containing x,y,z columns.
+
+<h2>BUGS</h2>
+<b>devi</b> file is written as 2D and deviations are not written as attributes.
+
+<h2>SEE ALSO</h2>
+<a href="g.region.html">g.region</a>,
+<a href="v.in.ascii.html">v.in.ascii</a>,
+<a href="r3.mask.html">r3.mask</a>,
+<a href="v.in.db.html">v.in.db</a>,
+<a href="v.surf.rst.html">v.surf.rst</a>,
+<a href="v.univar.html">v.univar</a>
+
+<h2>AUTHOR</h2>
+<p>Original version of program (in FORTRAN) and GRASS enhancements: <br>
+Lubos Mitas, NCSA, University of Illinois at Urbana-Champaign,
+Illinois, USA, since 2000 at Department of Physics,
+North Carolina State University, Raleigh, USA
+<a href="mailto:lubos_mitas at ncsu.edu">lubos_mitas at ncsu.edu</a><br>
+Helena Mitasova, Department of Marine, Earth and Atmospheric Sciences,
+North Carolina State University, Raleigh, USA, <a
+ href="mailto:hmitaso at unity.ncsu.edu">hmitaso at unity.ncsu.edu</a></p>
+<p>Modified program (translated to C, adapted for GRASS, new
+segmentation procedure): <br>
+Irina Kosinovsky, US Army CERL, Champaign, Illinois, USA <br>
+Dave Gerdes, US Army CERL, Champaign, Illinois, USA </p>
+<p>Modifications for g3d library, geometric parameters,
+cross-validation, deviations: <br>
+Jaro Hofierka, Department of Geography and Regional Development,
+University of Presov, Presov, Slovakia, <a
+ href="MAILTO:hofierka at fhpv.unipo.sk">hofierka at fhpv.unipo.sk</a>, <a
+ href="http://www.geomodel.sk">http://www.geomodel.sk</a> <br>
+ </p>
+
+<h2>REFERENCES</h2>
+<p>Hofierka J., Parajka J., Mitasova H., Mitas L., 2002, Multivariate
+Interpolation of Precipitation Using Regularized Spline with Tension.
+Transactions in
+GIS 6, pp. 135-150. </p>
+<p><a href="http://skagit.meas.ncsu.edu/%7Ehelena/gmslab/">Mitas, L.,
+Mitasova, H.</a>, 1999, Spatial Interpolation. In: P.Longley, M.F.
+Goodchild, D.J. Maguire, D.W.Rhind (Eds.), Geographical Information
+Systems: Principles, Techniques, Management and Applications, Wiley,
+pp.481-492 </p>
+<p>Mitas L., Brown W. M., Mitasova H., 1997, <a
+ href="http://skagit.meas.ncsu.edu/%7Ehelena/gmslab/lcgfin/cg-mitas.html">Role
+of dynamic cartography in simulations of landscape processes based on
+multi-variate fields.</a> Computers and Geosciences, Vol. 23, No. 4,
+pp. 437-446 (includes CDROM and WWW: www.elsevier.nl/locate/cgvis) </p>
+<p>Mitasova H., Mitas L., Brown W.M., D.P. Gerdes, I.
+Kosinovsky, Baker, T.1995, Modeling spatially and temporally
+distributed phenomena:
+New methods and tools for GRASS GIS. International Journal of GIS, 9
+(4),
+special issue on Integrating GIS and Environmental modeling, 433-446. </p>
+<p> Mitasova, H., Mitas, L., Brown, B., Kosinovsky, I., Baker, T.,
+Gerdes, D. (1994): <a
+ href="http://skagit.meas.ncsu.edu/%7Ehelena/gmslab/viz/ches.html">Multidimensional
+interpolation and visualization in GRASS GIS</a> </p>
+<p><a
+ href="http://skagit.meas.ncsu.edu/%7Ehelena/gmslab/papers/lmg.rev1.ps">Mitasova
+H. and Mitas L. 1993</a>: Interpolation by Regularized Spline with
+Tension: I. Theory and Implementation, <i>Mathematical Geology</i> 25,
+641-655. </p>
+<p><a
+ href="http://skagit.meas.ncsu.edu/%7Ehelena/gmslab/papers/hmg.rev1.ps">Mitasova
+H. and Hofierka J. 1993</a>: Interpolation by Regularized Spline with
+Tension: II. Application to Terrain Modeling and Surface Geometry
+Analysis, <i>Mathematical Geology</i> 25, 657-667. </p>
+<p>Mitasova, H., 1992 : New capabilities for interpolation and
+topographic analysis in GRASS, GRASSclippings 6, No.2 (summer), p.13. </p>
+<p>Wahba, G., 1990 : Spline Models for Observational Data, CNMS-NSF
+Regional Conference series in applied mathematics, 59, SIAM,
+Philadelphia, Pennsylvania. </p>
+<p>Mitas, L., Mitasova H., 1988 : General variational approach to the
+interpolation problem, Computers and Mathematics with Applications 16,
+p. 983 </p>
+<p>Talmi, A. and Gilat, G., 1977 : Method for Smooth Approximation of
+Data, Journal of Computational Physics, 23, p.93-123. </p>
+<p>Thorpe, J. A. (1979): Elementary Topics in Differential Geometry.
+Springer-Verlag, New York, pp. 6-94.</p>
+
+<p><i>Last changed: $Date$</i> </p>
Deleted: grass/trunk/vector/v.what/description.html
===================================================================
--- grass/trunk/vector/v.what/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/vector/v.what/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,25 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em>v.what</em>
-Outputs the category number value(s) associated with user-specified location(s)
-in user-specified vector map layer(s). This module was derived from the
-<em>d.what.vect</em> module by removing all interactive code and
-modification of the output for easy parsing.
-
-<h2>EXAMPLE</h2>
-
-Spearfish example:
-<div class="code"><pre>
-v.what fields east_north=599121.75,4922981.125
-</pre></div>
-
-<h2>SEE ALSO</h2>
-
-<em><a HREF="d.what.vect.html">d.what.vect</a></em>
-
-<h2>AUTHOR</h2>
-
-Trevor Wiens<br>
-Edmonton, Alberta, Canada
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/vector/v.what/v.what.html (from rev 32770, grass/trunk/vector/v.what/description.html)
===================================================================
--- grass/trunk/vector/v.what/v.what.html (rev 0)
+++ grass/trunk/vector/v.what/v.what.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,25 @@
+<h2>DESCRIPTION</h2>
+
+<em>v.what</em>
+Outputs the category number value(s) associated with user-specified location(s)
+in user-specified vector map layer(s). This module was derived from the
+<em>d.what.vect</em> module by removing all interactive code and
+modification of the output for easy parsing.
+
+<h2>EXAMPLE</h2>
+
+Spearfish example:
+<div class="code"><pre>
+v.what fields east_north=599121.75,4922981.125
+</pre></div>
+
+<h2>SEE ALSO</h2>
+
+<em><a HREF="d.what.vect.html">d.what.vect</a></em>
+
+<h2>AUTHOR</h2>
+
+Trevor Wiens<br>
+Edmonton, Alberta, Canada
+
+<p><i>Last changed: $Date$</i>
Deleted: grass/trunk/vector/v.what.rast/description.html
===================================================================
--- grass/trunk/vector/v.what.rast/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/vector/v.what.rast/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,61 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-<em>v.what.rast</em> reads raster value for each point in the vector and updates <b>col</b>
-column in vector attribute table by this value. The column should be type
-number (integer, float, double, ... ).
-<br>
-If more points have the same category, attribute value is set to NULL.
-If raster values is NULL, attribute value is set to NULL.
-
-<H2>NOTES</H2>
-
-<em>v.what.rast</em> operates on the attribute table. To modify the vector
-geometry instead, use <em>v.drape</em>.
-
-<H2>EXAMPLES</H2>
-
-A) Reading values from raster map at position of vector points, writing these values
- into column of vector map:
-<br>
-<div class="code"><pre>
-v.what.rast vect=pnts rast=elevation col=heights
-</pre></div>
-
-<P>
-B) In case of a vector map without attached attribute table, first add
-a new attribute table. This table is then populated with values
-queried from the raster map:
-<br>
-<div class="code"><pre>
-v.db.connect -p vectpoints
-# .. no table yet.
-
-# add new table, link to map:
-v.db.addtable vectpoints col="cat integer, myvalue integer, otherval double precision"
-
-# query raster map and upload values to vector table into specified column:
-v.what.rast vect=vectpoints rast=rastmap col=myvalue
-
-# verify new attribute table:
-v.db.select vectpoints
-
-# verify statistics of uploaded values:
-v.univar map=vectpoints col=myvalue type=point
-</pre></div>
-
-<H2>SEE ALSO</H2>
-
-<EM>
-<a href="v.db.addtable.html">v.db.addtable</a>,
-<a HREF="v.db.select.html">v.db.select</a>,
-<A HREF="v.drape.html">v.drape</a>,
-<A HREF="v.univar.html">v.univar</a>,
-<a HREF="v.rast.stats.html">v.rast.stats</a>,
-<a href="v.what.vect.html">v.what.vect</a>
-</EM>
-
-<H2>AUTHOR</H2>
-Radim Blazek
-
-<p>
-<i>Last changed: $Date$</i>
Copied: grass/trunk/vector/v.what.rast/v.what.rast.html (from rev 32770, grass/trunk/vector/v.what.rast/description.html)
===================================================================
--- grass/trunk/vector/v.what.rast/v.what.rast.html (rev 0)
+++ grass/trunk/vector/v.what.rast/v.what.rast.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,61 @@
+<H2>DESCRIPTION</H2>
+
+<em>v.what.rast</em> reads raster value for each point in the vector and updates <b>col</b>
+column in vector attribute table by this value. The column should be type
+number (integer, float, double, ... ).
+<br>
+If more points have the same category, attribute value is set to NULL.
+If raster values is NULL, attribute value is set to NULL.
+
+<H2>NOTES</H2>
+
+<em>v.what.rast</em> operates on the attribute table. To modify the vector
+geometry instead, use <em>v.drape</em>.
+
+<H2>EXAMPLES</H2>
+
+A) Reading values from raster map at position of vector points, writing these values
+ into column of vector map:
+<br>
+<div class="code"><pre>
+v.what.rast vect=pnts rast=elevation col=heights
+</pre></div>
+
+<P>
+B) In case of a vector map without attached attribute table, first add
+a new attribute table. This table is then populated with values
+queried from the raster map:
+<br>
+<div class="code"><pre>
+v.db.connect -p vectpoints
+# .. no table yet.
+
+# add new table, link to map:
+v.db.addtable vectpoints col="cat integer, myvalue integer, otherval double precision"
+
+# query raster map and upload values to vector table into specified column:
+v.what.rast vect=vectpoints rast=rastmap col=myvalue
+
+# verify new attribute table:
+v.db.select vectpoints
+
+# verify statistics of uploaded values:
+v.univar map=vectpoints col=myvalue type=point
+</pre></div>
+
+<H2>SEE ALSO</H2>
+
+<EM>
+<a href="v.db.addtable.html">v.db.addtable</a>,
+<a HREF="v.db.select.html">v.db.select</a>,
+<A HREF="v.drape.html">v.drape</a>,
+<A HREF="v.univar.html">v.univar</a>,
+<a HREF="v.rast.stats.html">v.rast.stats</a>,
+<a href="v.what.vect.html">v.what.vect</a>
+</EM>
+
+<H2>AUTHOR</H2>
+Radim Blazek
+
+<p>
+<i>Last changed: $Date$</i>
Modified: grass/trunk/visualization/nviz/Makefile
===================================================================
--- grass/trunk/visualization/nviz/Makefile 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/visualization/nviz/Makefile 2008-08-15 06:16:42 UTC (rev 32772)
@@ -6,9 +6,11 @@
VER=2.2
NV_VER=nviz$(VER)
-PROG=nviz
+PGM=nviz
INSTALL_DIR=$(GISBASE)/etc/$(NV_VER)
+include $(MODULE_TOPDIR)/include/Make/Html.make
+
SCRIPTS := \
scripts/script_get_line \
scripts/script_play \
@@ -23,13 +25,13 @@
$(MAKE) -C src
$(MAKE) install
$(MAKE) -C html
- $(MAKE) docs
+ $(MAKE) htmldir
# Install the scripts in the appropriate directory
install:
-$(MKDIR) $(INSTALL_DIR)
- $(INSTALL) src/nvwish$(EXE) $(INSTALL_DIR)/$(PROG)$(EXE)
- $(INSTALL) scripts/$(PROG) $(GISBASE)/bin
+ $(INSTALL) src/nvwish$(EXE) $(INSTALL_DIR)/$(PGM)$(EXE)
+ $(INSTALL) scripts/$(PGM) $(GISBASE)/bin
ifneq ($(strip $(MINGW)),)
$(INSTALL) scripts/nviz.bat $(GISBASE)/bin
endif
@@ -40,9 +42,5 @@
find -L bitmaps -path '*/.svn' -prune -o -type f -print | \
while read file ; do $(INSTALL_DATA) $$file $(INSTALL_DIR)/$$file ; done
-docs:
- -$(MKDIR) $(ARCH_DISTDIR)/docs/html
- $(INSTALL_DATA) description.html $(ARCH_DISTDIR)/docs/html/$(PROG).html
-
clean:
$(MAKE) -C src clean
Deleted: grass/trunk/visualization/nviz/description.html
===================================================================
--- grass/trunk/visualization/nviz/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/visualization/nviz/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,70 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html>
-<head>
-<title>nviz</title>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link rel="stylesheet" href="grassdocs.css" type="text/css">
-</head>
-<body bgcolor="white">
-
-<img src="grass_logo.png" alt="GRASS logo"><hr align=center size=6 noshade>
-
-<h2>NAME</h2>
-<em><b>nviz</b></em> - nviz - Visualization and animation tool for GRASS data
-
-<h2>KEYWORDS</h2>
-raster, vector, visualization
-
-<h2>SYNOPSIS</h2>
-<b>nviz</b><br>
-<b>nviz help</b><br>
-<b>nviz</b> [-<b>q</b>] [<b>elevation</b>=<em>string</em>] [<b>color</b>=<em>string</em>] [<b>vector</b>=<em>string</em>] [<b>points</b>=<em>string</em>] [<b>volume</b>=<em>string</em>] [<b>path</b>=<em>string</em>] [<b>script</b>=<em>string</em>] [<b>state</b>=<em>string</em>] [--<b>verbose</b>] [--<b>quiet</b>]
-
-<h3>Flags:</h3>
-<DL>
-<DT><b>-q</b></DT>
-<DD>Quickstart - Do not load any data</DD>
-
-<DT><b>--verbose</b></DT>
-<DD>Verbose module output</DD>
-<DT><b>--quiet</b></DT>
-<DD>Quiet module output</DD>
-</DL>
-
-<h3>Parameters:</h3>
-<DL>
-<DT><b>elevation</b>=<em>string</em></DT>
-<DD>Raster file(s) for elevation</DD>
-
-<DT><b>color</b>=<em>string</em></DT>
-<DD>Raster file(s) for color</DD>
-
-<DT><b>vector</b>=<em>string</em></DT>
-<DD>Vector lines/areas overlay file(s)</DD>
-
-<DT><b>points</b>=<em>string</em></DT>
-<DD>Vector points overlay file(s)</DD>
-
-<DT><b>volume</b>=<em>string</em></DT>
-<DD>Name of existing 3d raster map</DD>
-
-<DT><b>path</b>=<em>string</em></DT>
-<DD>Set alternative panel path</DD>
-
-<DT><b>script</b>=<em>string</em></DT>
-<DD>Execute script file at startup</DD>
-
-<DT><b>state</b>=<em>string</em></DT>
-<DD>Load previosly saved state file</DD>
-
-</DL>
-
-
-<h2>SEE ALSO</h2>
-
-Please refer to the detailed manual inside NVIZ (HELP menu) or see the
-<a href="nviz/index.html">NVIZ Tutorial</a>.
-<HR>
-<P><a href="index.html">Main index</a> - <a href="full_index.html">Full index</a></P>
-</body>
-</html>
Copied: grass/trunk/visualization/nviz/nviz.html (from rev 32770, grass/trunk/visualization/nviz/description.html)
===================================================================
--- grass/trunk/visualization/nviz/nviz.html (rev 0)
+++ grass/trunk/visualization/nviz/nviz.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,70 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<head>
+<title>nviz</title>
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
+<link rel="stylesheet" href="grassdocs.css" type="text/css">
+</head>
+<body bgcolor="white">
+
+<img src="grass_logo.png" alt="GRASS logo"><hr align=center size=6 noshade>
+
+<h2>NAME</h2>
+<em><b>nviz</b></em> - nviz - Visualization and animation tool for GRASS data
+
+<h2>KEYWORDS</h2>
+raster, vector, visualization
+
+<h2>SYNOPSIS</h2>
+<b>nviz</b><br>
+<b>nviz help</b><br>
+<b>nviz</b> [-<b>q</b>] [<b>elevation</b>=<em>string</em>] [<b>color</b>=<em>string</em>] [<b>vector</b>=<em>string</em>] [<b>points</b>=<em>string</em>] [<b>volume</b>=<em>string</em>] [<b>path</b>=<em>string</em>] [<b>script</b>=<em>string</em>] [<b>state</b>=<em>string</em>] [--<b>verbose</b>] [--<b>quiet</b>]
+
+<h3>Flags:</h3>
+<DL>
+<DT><b>-q</b></DT>
+<DD>Quickstart - Do not load any data</DD>
+
+<DT><b>--verbose</b></DT>
+<DD>Verbose module output</DD>
+<DT><b>--quiet</b></DT>
+<DD>Quiet module output</DD>
+</DL>
+
+<h3>Parameters:</h3>
+<DL>
+<DT><b>elevation</b>=<em>string</em></DT>
+<DD>Raster file(s) for elevation</DD>
+
+<DT><b>color</b>=<em>string</em></DT>
+<DD>Raster file(s) for color</DD>
+
+<DT><b>vector</b>=<em>string</em></DT>
+<DD>Vector lines/areas overlay file(s)</DD>
+
+<DT><b>points</b>=<em>string</em></DT>
+<DD>Vector points overlay file(s)</DD>
+
+<DT><b>volume</b>=<em>string</em></DT>
+<DD>Name of existing 3d raster map</DD>
+
+<DT><b>path</b>=<em>string</em></DT>
+<DD>Set alternative panel path</DD>
+
+<DT><b>script</b>=<em>string</em></DT>
+<DD>Execute script file at startup</DD>
+
+<DT><b>state</b>=<em>string</em></DT>
+<DD>Load previosly saved state file</DD>
+
+</DL>
+
+
+<h2>SEE ALSO</h2>
+
+Please refer to the detailed manual inside NVIZ (HELP menu) or see the
+<a href="nviz/index.html">NVIZ Tutorial</a>.
+<HR>
+<P><a href="index.html">Main index</a> - <a href="full_index.html">Full index</a></P>
+</body>
+</html>
Modified: grass/trunk/visualization/nviz/src/Makefile
===================================================================
--- grass/trunk/visualization/nviz/src/Makefile 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/visualization/nviz/src/Makefile 2008-08-15 06:16:42 UTC (rev 32772)
@@ -63,7 +63,3 @@
$(G3DLIB) $(GISLIB) $(XDRLIB) \
$(DATETIMELIB) $(TIFFLIBPATH) $(TIFFLIB) \
$(MATHLIB)
- -$(MKDIR) $(GISBASE)/docs/html
- -$(INSTALL_DATA) description.html $(GISBASE)/docs/html/nviz.html
- -$(INSTALL) *.png *.jpg $(GISBASE)/docs/html 2> /dev/null ; true
-
Deleted: grass/trunk/visualization/nviz/src/description.html
===================================================================
--- grass/trunk/visualization/nviz/src/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/visualization/nviz/src/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,8 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-<em><b>nviz</b></em> - nviz - Visualization and animation tool for GRASS data.
-
-<h2>SEE ALSO</h2>
-
-Please refer to the detailed manual inside NVIZ or see the
-<a href="nviz/index.html">NVIZ Tutorial</a>.
Deleted: grass/trunk/visualization/nviz2/cmd/description.html
===================================================================
--- grass/trunk/visualization/nviz2/cmd/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/visualization/nviz2/cmd/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,19 +0,0 @@
-<h2>DESCRIPTION</h2>
-
-Experimental CLI prototype of NVIZ.
-
-<p>
-TODO
-
-<h2>SEE ALSO</h2>
-
-<em>
-<a HREF="nviz.html">TCL/TK-based NVIZ</a>
-</em>
-
-<h2>AUTHOR</h2>
-
-Martin Landa (Google Summer of Code 2008)
-
-<p>
-<i>Last changed: $Date$</i>
Copied: grass/trunk/visualization/nviz2/cmd/nviz_cmd.html (from rev 32770, grass/trunk/visualization/nviz2/cmd/description.html)
===================================================================
--- grass/trunk/visualization/nviz2/cmd/nviz_cmd.html (rev 0)
+++ grass/trunk/visualization/nviz2/cmd/nviz_cmd.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,19 @@
+<h2>DESCRIPTION</h2>
+
+Experimental CLI prototype of NVIZ.
+
+<p>
+TODO
+
+<h2>SEE ALSO</h2>
+
+<em>
+<a HREF="nviz.html">TCL/TK-based NVIZ</a>
+</em>
+
+<h2>AUTHOR</h2>
+
+Martin Landa (Google Summer of Code 2008)
+
+<p>
+<i>Last changed: $Date$</i>
Deleted: grass/trunk/visualization/xganim/description.html
===================================================================
--- grass/trunk/visualization/xganim/description.html 2008-08-15 03:16:41 UTC (rev 32771)
+++ grass/trunk/visualization/xganim/description.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -1,77 +0,0 @@
-<H2>DESCRIPTION</H2>
-
-<EM>xganim</EM> is a tool for animating a series of GRASS raster
-files. At startup, a graphics window is opened containing VCR-like
-button controls for: rewind, reverse play, step back, stop, step
-forward, forward play, loop, swing, slower, faster, show filenames,
-current frame number, and Exit. The image is displayed above or to the
-left of the controls. Each raster map is read into memory, then the
-animation is played once beginning to end. The user may then replay
-the series or play continuous animation by using the buttons.
-<P>
-The user may define up to four "views", or sub-windows, to animate
-simultaneously. e.g., View 1 could be rainfall, View 2 flooded areas,
-View 3 damage to bridges or levees, View 4 other economic damage, all
-animated as a time series. There is an arbitrary limit of 400 files
-per view (400 animation frames), but the practical limit may be less
-depending on the window size and amount of available RAM.
-<P>
-The environment variable XGANIM_SIZE is checked for a value to use as
-the dimension, in pixels, of the longest dimension of the animation
-window. If XGANIM_SIZE is not set, the animation size defaults to the
-rows & columns in the current GRASS region, scaling if necessary
-to a default minimum size of 600 and maximum of 900. The resolution of
-the current GRASS region is maintained, independent of window size.
-Resizing the window after the program is running will have no effect
-on the animation size.
-<P>
-UNIX - style wild cards may be used with the command line version in
-place of a raster map name, but it must be quoted.
-<P>
-If the number of files differs for each view, the view with the fewest
-files will determine the number of frames in the animation.
-
-<H2>EXAMPLE</H2>
-
-<div class="code"><pre>
-export XGANIM_SIZE=800
-xganim view1="rain[1-9]","rain1[0-2]" view2="temp*"
-</pre></div>
-
-<H2>NOTES</H2>
-
-For wildcard matching, <EM>xganim</EM> understands whatever the shell
-understands (as it invokes "ls" via the shell to expand wildcards).
-E.g., a user can use "rast[0-9][0-9]" to match "rast00" through "rast99" inclusive.
-If the maps if interest have varying numbers of digits, multiple patterns
-can be combined, e.g.:
-
-<div class="code"><pre>
-export XGANIM_SIZE=1000
-xganim view1=rast[0-9],rast[1-9][0-9]
-</pre></div>
-
-to match rast0 through rast99 inclusive.
-
-
-<H2>BUGS</H2>
-On some displays that need to use private colormaps, the interface
-buttons may become difficult to see.
-
-<H2>SEE ALSO</H2>
-
-<em><a href="d.slide.show.html">d.slide.show</a></em>,
-<em><a href="gm_animate.html">gis.m: ANIMATE TOOL</a></em>
-
-<H2>AUTHOR</H2>
-
-Bill Brown, U.S. Army Construction Engineering Research Laboratories
-
-<!-- left in for historical purposes :)
-<H2>NOTICE</H2>
-This program is part of the contrib section of the GRASS distribution.
-As such, it is externally contributed code that has not been examined
-or tested by the Office of GRASS Integration.
--->
-
-<p><i>Last changed: $Date$</i>
Copied: grass/trunk/visualization/xganim/xganim.html (from rev 32770, grass/trunk/visualization/xganim/description.html)
===================================================================
--- grass/trunk/visualization/xganim/xganim.html (rev 0)
+++ grass/trunk/visualization/xganim/xganim.html 2008-08-15 06:16:42 UTC (rev 32772)
@@ -0,0 +1,77 @@
+<H2>DESCRIPTION</H2>
+
+<EM>xganim</EM> is a tool for animating a series of GRASS raster
+files. At startup, a graphics window is opened containing VCR-like
+button controls for: rewind, reverse play, step back, stop, step
+forward, forward play, loop, swing, slower, faster, show filenames,
+current frame number, and Exit. The image is displayed above or to the
+left of the controls. Each raster map is read into memory, then the
+animation is played once beginning to end. The user may then replay
+the series or play continuous animation by using the buttons.
+<P>
+The user may define up to four "views", or sub-windows, to animate
+simultaneously. e.g., View 1 could be rainfall, View 2 flooded areas,
+View 3 damage to bridges or levees, View 4 other economic damage, all
+animated as a time series. There is an arbitrary limit of 400 files
+per view (400 animation frames), but the practical limit may be less
+depending on the window size and amount of available RAM.
+<P>
+The environment variable XGANIM_SIZE is checked for a value to use as
+the dimension, in pixels, of the longest dimension of the animation
+window. If XGANIM_SIZE is not set, the animation size defaults to the
+rows & columns in the current GRASS region, scaling if necessary
+to a default minimum size of 600 and maximum of 900. The resolution of
+the current GRASS region is maintained, independent of window size.
+Resizing the window after the program is running will have no effect
+on the animation size.
+<P>
+UNIX - style wild cards may be used with the command line version in
+place of a raster map name, but it must be quoted.
+<P>
+If the number of files differs for each view, the view with the fewest
+files will determine the number of frames in the animation.
+
+<H2>EXAMPLE</H2>
+
+<div class="code"><pre>
+export XGANIM_SIZE=800
+xganim view1="rain[1-9]","rain1[0-2]" view2="temp*"
+</pre></div>
+
+<H2>NOTES</H2>
+
+For wildcard matching, <EM>xganim</EM> understands whatever the shell
+understands (as it invokes "ls" via the shell to expand wildcards).
+E.g., a user can use "rast[0-9][0-9]" to match "rast00" through "rast99" inclusive.
+If the maps if interest have varying numbers of digits, multiple patterns
+can be combined, e.g.:
+
+<div class="code"><pre>
+export XGANIM_SIZE=1000
+xganim view1=rast[0-9],rast[1-9][0-9]
+</pre></div>
+
+to match rast0 through rast99 inclusive.
+
+
+<H2>BUGS</H2>
+On some displays that need to use private colormaps, the interface
+buttons may become difficult to see.
+
+<H2>SEE ALSO</H2>
+
+<em><a href="d.slide.show.html">d.slide.show</a></em>,
+<em><a href="gm_animate.html">gis.m: ANIMATE TOOL</a></em>
+
+<H2>AUTHOR</H2>
+
+Bill Brown, U.S. Army Construction Engineering Research Laboratories
+
+<!-- left in for historical purposes :)
+<H2>NOTICE</H2>
+This program is part of the contrib section of the GRASS distribution.
+As such, it is externally contributed code that has not been examined
+or tested by the Office of GRASS Integration.
+-->
+
+<p><i>Last changed: $Date$</i>
More information about the grass-commit
mailing list