Resources

This section has additional resources that one might find helpful.

Software

The GIS source code with installation instructions is available from the FTP site: Grass programs are available from: ftp://pasture.ecn.purdue.edu/pub/mccauley

Databases

A document that catalogs free database systems is available from: ftp://idiom.berkeley.ca.us This is also posted on various newsgroups as explained in the following grassu-list announcement (information on the mailing list is provided in Section 1.4.7: GRASS Mailing List):
  Date: Fri, 5 Aug 1994 21:35:07 -0500
  >From: James Darrell McCauley <mccauley@ecn.purdue.edu>
  To: grassu-list@max.cecer.army.mil
  Subject: FYI: free database systems
  
  >         Catalog of Free Database Systems
  >
  > This document attemts to catalog databases that are
  > available without payment and with source.
  >
  > The latest version of the document can be ftp'ed: get
  > pub/free-databases from idiom.berkeley.ca.us.
  >
  > I will post this document about once a month to
  comp.databases,
  > comp.databases.object, comp.answers, and news.answers.  I will
  > also post it to other groups somewhat randomly.
In addition here are some FTP sites with geospatial data: FTP sites:
    IP Number Host Name Description
  1. 130.11.48.107 - ridgisd.er.usgs.gov - USGS GILS (/pub/gils.txt)
  2. 130.11.48.2 - isdres.er.usgs.gov - USGS FGDC, SDTS, NSDI (gdc.documents)
  3. 130.11.51.171 - dis2qvarsa.er.usgs.gov - USGS Land use/cover data
  4. 130.11.51.187 - waisqvarsa.er.usgs.gov - USGS WAIS source
  5. 130.11.52.55 - resdgs1.er.usgs.gov - USGS GIS Lab FTP site
  6. 130.11.52.92 - nmdpow9.er.usgs.gov - USGS NMD Tech Inst Docs (/public)
  7. 130.11.54.41 - eomg.er.usgs.gov - USGS Office of Energy & Marine Geology
  8. 130.11.54.6 - ncrds.er.usgs.gov - USGS Natl Coal Rescources Data System
  9. 130.118.120.28 - garlock.wr.usgs.gov - USGS Seismology & Tectonophysics
  10. 130.118.120.30 - alum.wr.usgs.gov - USGS Fault Mapping Data
  11. 130.118.24.14 - walrus.wr.usgs.gov - USGS Pacific Marine Geology
  12. 131.247.143.100 - wayback.er.usgs.gov - USGS Coastal Center
  13. 136.177.40.102 - sedproc.cr.usgs.gov - USGS Branch of Sedimentary Process
  14. 152.61.192.70 - edcftp.cr.usgs.gov - USGS EDC FTP site
  15. 192.70.225.78 - spectrum.xerox.com - Xerox Selected USGS data (DLG, DEM, GNIS
  16. 136.177.20.9 - neis.cr.usgs.gov - USGS Global Seismology & Geomagnetism
  17. 128.111.105.65 - ncgia.ucsb.edu - NCGIA reports newsletter, bib, ...
  18. 128.128.40.24 - charon.er.usgs.gov - USGS COGS files, OzGIS & pointer data
  19. 136.177.48.5 - greenwood.cr.usgs.gov - USGS Digitial data, Open file reports
  20. 129.229.20.254 - moon.cecer.army.mil - GRASS (/grass)
  21. 131.118.70.11 - midget.towson.edu - IDRISI (/pub/gis)
  22. 148.129.129.10 - info.census.gov - US Bureau of Census
  23. 130.11.51.209 - srv1rvares.er.usgs.gov - USGS Stream Flow Data (/hcdn92)

Tutorials

A tutorial in WordPerfect format and Postcript is available at: ftp://ftp.nps.gov/tutorial.gis/

This document contains a tutorial on various aspects of GRASS (Section 1.3). This document, with the tutorial, is available on non-public NASA machine :

 
	~delgado/tutor/all
In addition, the appendix includes a tutorial originally included with a Stanford workshop on GRASS usage. This document is available on non-public NASA machine :
 ~delgado/tutor/stanford
There are several WWW homepages where you can get information:

Newsgroups

If you want a overview of GIS system, there is a Net News article posted monthly in net.answers called the GIS FAQ that answers Frequently Asked Questions (i.e. a FAQ using internet termininology) about GIS systems.

There is also a newsgroup devoted to GIs systems that frequently mentions GRASS: comp.infowsystems.gis

Programming notes

Capture files were used frequently in the writing of this document: This included a recording of the typing needed to interactively accomplished a desired result. These files, as well as graphic snapshots of various screens and display outputs are availble from non-public NASA machine in the directory:
	 ~schwehr/tutor/ 
This directory contains subdirectories with the capture and graphics snapshots needed for a particular procedure e.g.:

GIS Mailing Lists

Internet lists:
  
  List Name Host Name      Send Message To List
  -------------------------------------------------
  GIS-L          listserv@ubvm.cc.buffalo.edu  GIS-L@ubvm.cc.buffalo.edu
  MAPS-L         listserv@uga.bitnet      MAPS-L@uga.cc.uga.edu
  GOVDOC-L  listserv@psuvm.psu.edu        GOVDOC-L@psuvm.psu.edu
  COASTGIS  listserv@irlearn.ucd.edu.ie
  TGIS-L         listserv@ubvm.cc.buffalo.edu
  UIGIS-L        listserv@ubvm.cc.buffalo.edu
  GEOGRAPH  listserv@finhutc.hut.fi
  IMAGRS-L  listserv@csearn.earn
  INGRAFX        listserv@psuvm.psu.edu
  BIONET         biosci@net.bio.net
  ECOLOG-L  listserv@umdd.umd.edu
  CONSBIO        listserv@uwavm.u.washington.edu
  AQUA-L         listserv@vm.uoguelph.ca
  MARINE-L  listserv@vm.uoguelph.ca
  BEN       ben@cue.bc.ca            (botany/ecology news letter)
  CP        listserv@opus.hpl.hp.com
  NSDI-L         listproc@grouse.umesve.maine.edu NSDI-L@grouse.umesve.maine.edu
GRASS Mailing list
  
  Date: Thu, 1 Sep 1994 06:01:02 -0500
  To: grassp-list@max.cecer.army.mil
  Subject: Intro to the GRASShopper lists [posted once a month]
  
  -------------------------------------------
  
  About the OGI GRASS Mailing Lists
  Office of Grass Integration
  
  [This document is sent out to the GRASS Programmers' Electronic
  Mailing
   List once a month as a reminder and introduction to the list
  manager
   software.]
  
  November 25, 1991
  
  The Office of GRASS Integration has set up a service
that will be of interest especially to those GRASS users
who have access to electronic mail.  We have set up two
e-mail lists to foster communication between GRASS Users
and GRASS Programmers.  The lists work on the principle
of "mail exploding" -- a user mails a note to one
address, and the computer at that address "explodes" the
letter, re-mailing it to everyone who subscribes to the
list.  Replies to the original letter generally go to the
list as well (if there is general interest in the
answer), but can be directed solely to the original
author if desired.  Both lists are also automatically
preserved in an archive, and users may at any time
request a file containing an archive of list messages.
  
  These lists exist to foster communication between
parties interested in the GRASS software; many CERL
employees will participate in the lists, but on an
infrequent and informal basis.  The list will be
maintained and stored on CERL computers; however, CERL
will not officially monitor the content, intent, or
accuracy of any messages that pass through the list. The
point-of-contact for the list is:
  
        grass-lists-owner@moon.cecer.army.mil
  
  The list for GRASS users and friends is called "grassu"
(short for "GRASS users"), while the list for programmers
and system-level users is called "grassp" (short for
"GRASS programmers").  Topics for discussion on the
|grassu-list| may include questions about various GRASS
applications, sources of (or reviews of) third-party
support, and various and sundry other experiences with
GRASS.  |Grassp-list| topics will include discussion of
the algorithms and intricacies of current GRASS programs,
programming hints and ideas for new GRASS applications,
and other prorgrammer-oriented issues.  Note that the
grassp-list is |not| the best (nor even an appropriate)
place to report suspected bugs in GRASS code; the current
<bug.report.sh> program and correspondance with OGI
are the preferred problem-report procedures.
  
  
  Accessing the mailing lists
  
  Each mailing list has two addresses.  The first is the
destination of messages that should be "exploded" out to
all subscribers.  This address takes the form of
  
        grassu-list@moon.cecer.army.mil 
  
  for the user's list, and
  
        grassp-list@moon.cecer.army.mil 
  
  for the programmer's lists.{1}
  
  {footnote1:These, and all other e-mail addresses in
this article, are provided in an "Internet-standard"
format; different host computers might require different
specifications of the address.  The system administrator
at each site should be able to help if the addresses here
do not work as specified.}
  
  The other important address for each list is the
destination of commands to the list-management software
(such as subscribe, unsubscribe, etc.).  They should be
sent to
  
        grassu-request@moon.cecer.army.mil 
         or
        grassp-request@moon.cecer.army.mil 
  
  as appropriate.  Multiple commands may be included in
messages.  Commands may be located in the subject line or
in the body of the letter, but there should be only one
command per line.  Upper- or lower-case letters may be
used for commands, and they may be abbreviated to simply
the first three letters if desired.  All commands are
acknowledged with return e-mail.
  
  Commands that the server will accept are:
  
  HELp
  
       This command mails back a copy of the list's help
file from the archive directory.
  
  PINg
  
       This command "pings" the mailing list, causing a
simple "I'm alive" response to be returned.  This is a
good way to check the list's address, to check if the
list is reachable from your machine, and to check if the
list is up and running.  This command is meant to be an
alternative to mailing a message to the everyone on the
list asking "Is the list working" and so forth.
  
  SUBscribe [name]
  
       This command adds [name] to the mailing list.  The
subscriber's e-mail address is taken from the "From:"
line of the subscription letter, and this address is what
is added to the list.  The [name] parameter is is used to
specify the user's real name.
  
  UNSubscribe
  
       This command removes the user's subscription from
the list.  It relies on the "From:" field of the request
letter.  If this address does not match any name in the
list, the software will notify the sender and the CERL
list-maintainer, who will resolve the problem by hand.
  
  WHO [address]
  
       If no [address] option is given, this command
returns a sorted list of list subscribers.  If [address]
is supplied, the software searches for a user with that
address and returns that user's name.
  
  DIRectory
  
       This command returns the mailing list's archive
directory.  The primary purpose of this is to see which
list-archive files are available.  The list software will
mail back a list of available files.
  
  GET [file]
  
       This command returns the named [file] from the
list's archive directory.  Case and spelling are
important; the name must |exactly| match a file shown by
the "DIR" command.  A message acknowledging the request
will be mailed to the user.
  
       If the file is short, the user will simply receive
a copy of it in mail.  For example, the command "GET LOG"
(capitalization of "LOG" is important) will cause the
list-server to mail back a copy of the most recent
messages to the list (which are always stored in the file
named "LOG").
  
       If the file is very long, the list server software
will <uuencode> the file and split it into several
mail-sized chunks. ("Uuencode" and "uudecode" are common
UNIX programs to encode files for e-mail transport.  The
local computer must have the <uudecode> program in
order to decode these files.  The acknowledgement note
will inform the user how many chunks to expect, and each
chunk will have a subject line that specifies "filename:
part X of Y".
  
  
  Examples of List Usage
  
  To "ping" the list (i.e. check that it is functioning
and reachable from your computer):
  
   Send a mail message to:
  
       grassu-request@moon.cecer.army.mil
  
  In the subject or the message body, type "PING" or
"ping" or "pin" (without the quotes; case is unimportant
and only the first three letters of commands are
significant).  The list server will reply with a brief
"I'm here" message.  To ping the programmer's list,
substitute "grassp" for "grassu" in the address above.
  
  To subscribe to one of the lists:
  
  Send a mail message to either
  
       grassu-request@moon.cecer.army.mil
            or
       grassp-request@moon.cecer.army.mil
  
  with "subscribe [yourname]" in the subject or body.
Replace [yourname] with your real name.  The list will
add the e-mail address that it finds in the "From:" field
of your letter.
  
  
  Summary
  
  These two lists are provided by OGI as a service for
the GRASS community; we hope that they will prove to be
useful resources.  We encourage you to try several
commands to experiment with the lists.  If there are any
questions, feel free to send mail to
 
       grass-lists-owner@moon.cecer.army.mil
  
  or contact the OGI by phone or mail.
  

Useful Information obtained from the Mailing List Archive:

During the VPE GRASS installation, the programmer (Kurt Schwehr) made use of the GRASS mailing list to obtain good information on a variety of topics:
Compiling Grass on IRIX 5:
Compiled versions of GRASS can be found at the location: Notes on compiling it:
  
  Date: Thu, 11 Aug 1994 13:51:12 -0500
  >From: Bill Brown <brown@diego.cecer.army.mil>
  To: grassu-list@max.cecer.army.mil
  Subject: Re: IRIX 5 GRASS
  
  
  Kurt,
  
  I compiled GRASS for IRIX 5.2 a few weeks ago.  Here's my
  compilation
  notes:
  
  ----------------------------------------------------------------
  ----------
  A few compile problems:
  
  To fix the i.points, i.ortho.photo, i.vpoints problem:
  make the function "screen" in the files "mark.c" a non-static
  function.
  (Just delete the keyword "static" where the function is defined)
  These files need to get this fix:
  src/imagery/i.points/mark.c
  src.alpha/imagery/i.ortho.photo/photo.2image/mark.c
  src.alpha/imagery/i.ortho.photo/photo.2target/mark.c
  src.alpha/imagery/i.vpoints/mark.c
  
  To compile xgrass, I needed to use these XCFLAGS:
  XCFLAGS             = -D_NO_PROTO -DXM_1_1_BC -Umips
  
  To compile v.digit, I needed to remove this dependancy from the
  Gmakefile:
  menus.o: menus.i
  
  Everything else compiled OK.
  
  xdigit did not work correctly when run.  To fix I added this
  test in the
  function init_graphics() in the file src/xgrass/xdigit/draw.c :
  (~line 76)
  
      if(XtIsRealized(canvas)){
       /* ...body of function... */
      }
  
  
  ----------------------------------------------------------------
  ----------
  This is the head file I used:
  
  
  CC                  = cc
  ARCH                = sgi5
  
  GISBASE             = /GRASS.bin/4.1/sgi5
  UNIX_BIN            = /usr/local/bin
  
  DEFAULT_DATABASE    = /data/foghorn/4.0
  DEFAULT_LOCATION    = spearfish
  
  COMPILE_FLAGS       = -O -cckr
  LDFLAGS             = -s
  
  XCFLAGS             = -D_NO_PROTO -DXM_1_1_BC -Umips
  XLDFLAGS            = -lPW
  XINCPATH            =
  XMINCPATH           =
  XLIBPATH            =
  XTLIBPATH           = -L/usr/lib
  XMLIBPATH           = -L/usr/lib
  XLIB                = -lX11
  XTLIB               = -lXt
  XMLIB               = -lXm
  XEXTRALIBS          = -lPW
  
  TERMLIB             = -ltermlib
  CURSES              = -lcurses $(TERMLIB)
  MATHLIB             = -lm
  
  #                   LIBRULE = ar ruv $@ $?
  #                   LIBRULE = ar ruv $@ $?; ranlib $@
  #                   LIBRULE = ar ruv $@ $?; ar ts $@
  #                   LIBRULE = ar rc $@ `lorder $(OBJ) | tsort`
  LIBRULE             = ar ruv $@ $?
  
  USE_TERMIO          = -DUSE_TERMIO
  USE_MTIO            = -DUSE_MTIO
  USE_FTIME           =
  DIGITFLAGS          = -DUSE_SETREUID -DUSE_SETEUID -
  DUSE_SETPRIORITY
  VECTLIBFLAGS        =
  GETHOSTNAME         = -DGETHOSTNAME_OK
  
  XDRLIB = -lsun
  
Mars Data
  From: Bill Brown <brown@diego.cecer.army.mil>
  
  > Also, is there a way to let grass georeference stuff on mars
  > or will I have to stick to keeping the data in xy?
  
  I guess it depends somewhat on what it looks like now, but I had
  some Mars data in a lat-long location & it seemed to work OK.
  (see http://www.cecer.army.mil/grass/viz/global.html)
Searching through the grassu-list archives
  
  Newsgroups: info.grass.user
  >From: ront@picea.CNR.ColoState.EDU (Ronald Thomas)
  Subject: Re: Grassu archives searching?
  Date: Fri, 12 Aug 1994 13:09:12 GMT
  Apparently-To: grassu-list@max.cecer.army.mil
  
  >is there any way to search ?through the grassu-list archives at
  >the max.cecer.army.mil site?
  >Many problems haunting a grass novice were probably grilled
  there
  >zillions of times.
  >Cheerio, Ania
  
  Don't know about searching achives on the "moon"; best bet is to
  retrieve
  the achives and search at your own site.  Your comments about
  some
  questions being asked (& answered) over & over are right on.
  
  Here is a script I use to query a copy of the archives that I
  keep:
  ---------------------------------------
  #!/bin/sh
  #This script "grassu94" searches for a 'keyword' in the
  following
  # file:  grassu.92.gz.  If it finds whatever you requested, the
  # script then prints that line or lines out on the terminal.  If
  it doesn't
  # find what you asked for, the script will tell you that it
  can't be found.
  # usage: grassu94 'keyword'
  if test $# -gt 0
  then
    arg="$*"
    gzcat $HOME/mail/grassu.94.gz | grep -i -n "$arg" | more
    es=$?
    if test $es = '0'
    then
      exit 0
    else
      echo "$*" not found in grassu.94 file.
      exit 1
    fi
  else
    echo You have not entered anything to look up.
    exit 2
  fi
  -----------------------
  The following script file can be used to delete a LOT of
  extraneous header
  lines that unfortunately come with the archives -- I estimate
  this reduces
  the size of the achives by 30%.  Of course, UNIX compress of GNU
  gzip
  should be used to keep the 'cleaned' file as small as possible,
  but that's
  a personal decision.
  
  ----------------------
  #clean
  #usage: clean 'file'
  ex $1 << EOF
  :g/^Re/d
  :g/^ id/d
  :g/^  (/d
  :g/^Se/d
  :g/^Appar/d
  :g/^X/d
  :g/^In-Reply/d
  :g/^Status:/d
  :g/^Errors-To/d
  :g/^Pre/d
  :g/^From lists/d
  :g/^Message/d
  :g/^To:/d
  :g/^From grass/d
  :g/^Content/d
  :g/^Organization/d
  :g/^Received/d
  :wq
  EOF
Histograms
  
  Date: Sun, 21 Aug 1994 02:32:29 -0500
  >From: James Darrell McCauley <mccauley@ecn.purdue.edu>
  Subject: histograms
  
  >for a rast-based image on GRASS monitor, after running a GRASS
  d.histogram
  >command, colored pie-scale histogram with category values are
  shown, as
  >general process of GRASS. My question is .....
  >Anyway, anyone help me to printout histogram graphics ?
  
  an alternative for histograms may be to use g.gnuplot:
  
  GRASS 4.1 > r.stats -c sample > sample.dat
  GRASS 4.1 > g.gnuplot
  
  gnuplot> set term postscript
  gnuplot> set out 'sample.ps'
  gnuplot> plot [1:] 'sample.dat' w i
  gnuplot> quit
  
   GRASS 4.1 > lp sample.ps
Color display in GRASS explained
  
  Date: Mon, 22 Aug 1994 14:29:55 -0500
  >From: Bill Brown <brown@diego.cecer.army.mil>
  To: grassu-list@max.cecer.army.mil
  Subject: Re: GRASS colors
  
  
  > From: kilee@CC.UManitoba.CA
  > Date: Mon, 22 Aug 94 13:02:28 CDT
  > To: grassu-list@max.cecer.army.mil
  >
  > Q: In GRASS, just 0-255 integer rast-based color coding image
  is possible,
  
  Using GRASS color files, you can specify values from 0-255 for
  EACH
  of the three (red,green,blue) color components, yielding
  something
  like 16 million possible colors.  Of course, the problem comes
  in
  trying to display your map.  There are severe limitations with
  the
  GRASS X-driver and with 256 color 8-bit monitors.  But even with
  24-bit displays, the GRASS X-driver still limits you to
  something
  like 216 colors.  (I understand that the tcl/tk viewer will let
  you
  use all your available color depth).  But for now, if you have a
  display device capable of more colors, you could use r.out.ppm
  to
  convert the GRASS raster file into a 24-bit ppm image, then
  output
  that.
  
  And just a reminder that if you're running on an SGI with 24-bit
  graphics, don't overlook the IRIS monitor driver, which will
  give
  you 3840 colors.
Running GRASS programs without starting grass
  
  Date: Tue, 23 Aug 1994 13:11:41 +0100
  To: grassu-list@max.cecer.army.mil
  Subject: Re:  problems in interface
  
  >Does anyone knows how to excute GRASS command or scripts
  >in external?
  
  I wrote the following script a couple of years ago to see how
  this
  could be done (we didn't need to in the end).  I'm sure that it
  could
  be a lot prettier but at least it's a starting point !  To find
  out what
  the variables need to be set to on your system, it's easiest to
  start
  grass and type "printenv |more" (assuming you use csh).
  
  The files:
  
  ----------<<  grassrc_test  >>----------
  GISDBASE: /data/grass
  LOCATION_NAME: tyne
  MAPSET: phil
  
  ----------<<  exec_grass  >>----------
  #!/usr/bin/csh
  
  set path= (/user/grass/sun4/bin /user/grass/sun4/scripts
  /user/grass/sun4/garden/bin /user/grass/sun4/alpha/bin
  /usr/local/bin /usr/bin /usr/ucb /etc /usr/etc /usr/lib)
  setenv GISBASE /user/grass/sun4
  setenv GISDBASE /data/grass
  setenv GISRC grassrc_test
  setenv LOCATION /data/grass/tyne/phil
  setenv LOCATION_NAME tyne
  setenv MAPSET phil
  
  g.list rast
Sample usage of r.mapcalc
  
  >From: Firma Nieuwland <nieuwlnd@sci.kun.nl>
  Date: Thu, 25 Aug 1994 09:09:37 +0200
  To: grassu-list@max.cecer.army.mil
  Subject: Re:  thresholding in GRASS
  
  Try:
  
  rmapcalc   output=if(input > 110 && input < 140 , a + bx , if
  (input>160 && input < 200, c + dx,0)
  -Olga van de Veer
Autocad DXF files
  
  Date: Fri, 26 Aug 1994 10:21:20 -0400 (EDT)
  >From: preston@malibu.dst.battelle.org (Evan Preston)
  Subject: DXF Files??
  To: grassu-list@max.cecer.army.mil
  
  We are working on a project that is using GRASS as well as a
  package called
  World Toolkit (for 3D/animation).  An ideal way to display map
  data in this
  package is by importing DXF polygons and texturing them.
  So...we are looking
  for anyone who may have some DXF files they would like to share
  (preferably
  maps of the Korean Penninsula, but we'll take anything
  reasonable in order
  to test out this concept).
  
  Please post response or email me directly.
  Evan
  
  Evan B. Preston                            # Battelle
  #
  phone:     614.424.3983                    # National Security
  Division  #
  fax:       614.424.3776                    # 505 King Ave.
  #
  internet:  preston@malibu.dst.battelle.org # Columbus, Ohio
  43201       #
  
Databases and GRASS
  Date: Tue, 6 Sep 94 07:29:39 MDT
  >From: susan@its.nbs.gov (Susan Stitt)
  To: nsegura@halcon.dpi.udec.cl (Nelson Segura Nunez)
  Subject: Data Bases and GRASS
  
  Nelson,
  
  Another item you may wish to be aware of is the pending
  availability
  of L.A.S.'s version of GRASS in TCL-TK.  They have claimed that
  they
  have created a version with an implementation of a database
  capability
  built into the GRASS software.  This software is described below
  by
  Gilles Clement who is president of LAS.
  
  >Date: Fri, 8 Jul 1994 09:54:54 -0400
  >From: gc@copernic.lasinc.qc.ca (Gilles Clement)
  >To: grassu-list@max.cecer.army.mil
  >Subject: [ANNOUNCE] tcltkgrass
  >>
  >A lot of people are asking about the status of tcltkgrass.
  Initially, we
  >thought we could have a release for mid-May.  Unfortunately,
  financing for the
  >project was slightly delayed and we decided to redesign the
  software almost
  >completely.  This is why we haven't been able to release any
  new version so
  >far.  We've been working on this project for several months now
  and we believe
  >our final beta version will be available in September 1994.
  >
  >
  >This new version is entirely redesigned using object-oriented
  development
  >technique and will have a lot of very cool new features such
  as: an enhanced
  >bugfree superviewer, a WYSIWYG postscript output for the
  superviewer, a
  >completely rebuilded GUI for every GRASS function, a visual
  interactive
  >programming environment for GRASS, a new set of converters for
  vector, raster
  >and databases, an imbedded RDBMS and georelational link
  capability and a
  >simplification of the installation procedure.
  >
  
  >As promised, the UNIX version of tcltkgrass will be contributed
  to the public
  >domain but the long awaited MSWindows version will be a
  commercial product.
  >Presently, 8 sites have shown interest in acting as alpha and
  beta testers for
  >the new version but we would like to extend that to
  approximately 20
  >organisations.
  >
  >Anybody can have the opportunity to be one of the 20 alpha test
  sites, provided
  >that their organisation is active in either development,
  applications or
  >education of GRASS and is using either a PC with MS-Windows or
  a SUN
  >SparcStation running SUN OS 4.0.x or a DEC DecStation running
  Ultrix 4.x.  The
  >alpha version will be available at the end of July.
  >
  >
  >Of course, the sites using PC's will be provided with a free
  alpha and beta
  >version.
  >
  >For those interested, please contact Valerie DesRoches:
  >vader@copernic.lasinc.qc.ca
  >
  >
  >L.A.S. inc.
  >
  >Gilles Clement, president
  >
  >p.s.: list of organisations interested in acting as alpha and
  beta testers:
  >
  >Organisation  Scientific authority     E-mail
  >PNFI (Forestry Canada)  Tom Moore tmoore@pnfi.forestry.ca
  >DREV (National Defense) Dominic Roy    droy@jupiter.drev.dnd.ca
  >CAST (Un. of Arkansas)  Jim Farley     jim@cast.uark.edu
  >USACERL (US Army)  Kurt Buehler   kurt@zorro.cecer.army.mil
  >HQ (Qubec Hydro)   Guy Moisan     moisang@envir.hydro.qc.ca
  >and a few private companies we can't name... :-)
New r.in.hdf Command
  
  Date: Thu, 8 Sep 1994 14:33:36 -0500
  >From: Bill Brown <brown@diego.cecer.army.mil>
  To: grassu-list@max.cecer.army.mil
  Subject: new r.in.hdf
  
  
  I just put an updated version of r.in.hdf on moon in
  grass/incoming .
  
  This latest version adds features to correctly import NASA AVHRR
  data & other HDF format data that uses the HDF calibration
  feature.
  
  It also allows you to list the contents of the HDF file, and
  select
  random datasets from the file for importing to GRASS. (With the
  old
  version, you had to either import only the first dataset or all
  datasets.)
  
  This version also writes some of the HDF annotation & label info
  to
  the GRASS history file.
  
  Bill B.

[Prev] [Next]
Email to:
Kurt Schwehr schwehr@cs.stanford.edu -- Dan Delgado renata@eos.arc.nasa.gov

Tree Kurt's Homepage