All my fifos are in order (/gis/grass-5.0b3/dev)..... everytime I run the
d.mon command a lock file is generatet..... I delete the lock file, and
the next time I run the command a new lock file
is made.....
Kjell-Olav Bjerknes..............
Hi,
it may be required to specify a domain name for the
server. Then a subdirectory is required in locks/ named
like your machine (without domain). Set the permissions
in grass-5.0b3/ with
chmod -R 1777 locks/
The lockfile will be created automatically when starting
a monitor and deleted when stopping the monitor. No need
to edit anything there!
One other problem I know: If you run Linux based on libc5
you cannot use GRASS compiled on libc6 properly. The GRASS
Linux binaries are compiled on libc6 (glibc2). If you still
have a libc5-based system (Redhat 4.x, SuSe 5.x, Caldera 1.3,
Debian 1.x ...) you should compile the GRASS 5 yourself which
is quite easy now.
Best regards
Markus
Markus Neteler wrote:
One other problem I know: If you run Linux based on libc5
you cannot use GRASS compiled on libc6 properly. The GRASS
Linux binaries are compiled on libc6 (glibc2). If you still
have a libc5-based system (Redhat 4.x, SuSe 5.x, Caldera 1.3,
Debian 1.x ...) you should compile the GRASS 5 yourself which
is quite easy now.
That's true ! I attempted to run the grass bin directly on an old
slackware linux distribution, and I missed some libraries.
BTW, if somebody attempts to compile grass on an old distribution,
it will not works because the right curses.h file (for libncurses)
is in /usr/include/ncurses/curses.h.
I get rid of this by renaming curses.h and termcap.h in /usr/include
and moving the .h files from /usr/include/ncurses to /usr/include.
--
Michel Wurtz ENGEES - CEREG
1, quai Koch - BP 1039, F-67070 STRASBOURG cedex
Tel: +33 03.88.24.82.45 Fax: +33 03.88.37.04.97
Markus Neteler wrote:
One other problem I know: If you run Linux based on libc5
you cannot use GRASS compiled on libc6 properly. The GRASS
Linux binaries are compiled on libc6 (glibc2). If you still
have a libc5-based system (Redhat 4.x, SuSe 5.x, Caldera 1.3,
Debian 1.x ...) you should compile the GRASS 5 yourself which
is quite easy now.
Best regards
Markus
My problem with d.mon is that I get the next error message
d.mon: error in loading shared libraries
: undefined symbol: __bzero
It seems related with the libraries problem,
but I am running GRASS on a Redhat 5.2 Linux.
Any idea?
Thanks in advance
Hello !
I'm using the grass5.0b binary distribution on SuSE 6.0.
I cannot find v.digit. Does it still exist ?
Moritz
Hello !
I'm looking for a (statistical) program that helps classifying data into
intervals for use in thematical maps, i.e. I would like to be able to give
an input data file, tell the program how many class intevals and which
classification algorithm (equal distance, standard deviation, discontinuities, etc...) I
want and then get an output with the class ranges.
Soemone suggested r.reclass, but if I understand this module it only
reclassifies maps according to class intervals you already know.
Does anybody know of such a program ? I could try and write one myself,
but if it already exists why do the work again ? 
Moritz
Hello Moritz !
v.digit is now available under the name
v.digspline,
since it provides spline interpolation of vectors (the old v.digit is
though still in the release (src - binary i am not sure) but commented
out in the list of programs to be compiled).
Cheers, Michael
==============================================================
Michael Schulz
Christoph-Mang-Str.5 Geologisches Institut
79100 Freiburg Universitaet Freiburg
Albertstr. 23b
79104 Freiburg
On Sun, 12 Sep 1999, Moritz Lennert wrote:
Hello !
I'm using the grass5.0b binary distribution on SuSE 6.0.
I cannot find v.digit. Does it still exist ?
Moritz
Hi all,
I'm trying to develop a dem map, but instead of altitudes, I want to
display animal and plant population densities. I've tried with v.digit to
create a contour map, then v.to.rast, and then r.surf.contour. But I do not
get a good result. I think my problem is in the v.digit module, I don't
know exactly how to define the lines or areas regarding densities.
Thanks in advance
Antonio Rodríguez V
IRNAS-CSIC
Sevilla, Spain
Antonio Rodríguez Verdugo wrote:
Hi all,
I'm trying to develop a dem map, but instead of altitudes, I want to
display animal and plant population densities. I've tried with v.digit to
create a contour map, then v.to.rast, and then r.surf.contour. But I do not
get a good result. I think my problem is in the v.digit module, I don't
know exactly how to define the lines or areas regarding densities.
It depends on what you have as initial data : if you have some
"isolines" for the density, you can digitize them, giving each
line a density as attribute, then v.to.rast and r.surf.contour.
Your line contour map should be seen exactly as a altitude contour
map. So it is important that each line is labelled with the
number it represents.
If you have mesured the density at some places, you will find
easier to enter your mesures in a site file (x, y, value), then
run s.to.vect then v.to rast, and finaly s.surf.tps. You will
interpolate between points instead of lines.
--
Michel Wurtz ENGEES - CEREG
1, quai Koch - BP 1039, F-67070 STRASBOURG cedex
Tel: +33 03.88.24.82.45 Fax: +33 03.88.37.04.97
Hi Michael,
I'm trying to develop a dem map, but instead of altitudes, I want to
display animal and plant population densities. I've tried with v.digit to
create a contour map, then v.to.rast, and then r.surf.contour. But I do not
get a good result. I think my problem is in the v.digit module, I don't
know exactly how to define the lines or areas regarding densities.
It depends on what you have as initial data : if you have some
"isolines" for the density, you can digitize them, giving each
line a density as attribute, then v.to.rast and r.surf.contour.
Your line contour map should be seen exactly as a altitude contour
map. So it is important that each line is labelled with the
number it represents.
Yes it works. But I didn't know that I needed a lot of contour lines in
order to run fast the r.surf.contour module. With few isolines I get a very
poor performance ( I needed two or three hours), so in the beginnings of my
search I thought I was doing somenthing wrong (I used Ctrl-C in order to
stop those endless processes) . Maybe is my processor (pentium 166).
If you have mesured the density at some places, you will find
easier to enter your mesures in a site file (x, y, value), then
run s.to.vect then v.to rast, and finaly s.surf.tps. You will
interpolate between points instead of lines.
With s.surf.tps I only get a plain raster file with no appreciable data. I
tried with s.surf.idw, and it seems to fit my needs. But when I run the
d.3d module I get some "holes" or depression as if I put negative values,
but it isn't the case. So I think I must tune up something.
Thanks,
Antonio Rodríguez V.
IRNAS-CSIC
Sevilla, Spain
Does anybody have a problem with d.3d clipping what it's drawing? When I set
the observer position so that it is roughly directly north/south, east/west
of the map only about half of the map gets drawn - it gets clipped at about
the same northing/easting as the observer position. Any remedies?
Thanks,
gerard@bwn.net
At 5:50 PM +0200 9/17/99, Antonio Rodríguez Verdugo wrote:
With s.surf.tps I only get a plain raster file with no appreciable data. I
tried with s.surf.idw, and it seems to fit my needs. But when I run the
d.3d module I get some "holes" or depression as if I put negative values,
but it isn't the case. So I think I must tune up something.
You're simply running into the limitations of the interpolation schemes. Whenever you try to fill in holes in some data sets, you need to understand the algorithm being used and judge its appropriateness to your purpose. There are many many schemes for building surfaces from contours or points; none are correct for every problem.
It sounds to me like you're choosing among GRASS programs because they're readily available. What you should be doing instead is choosing a particular mathematical algorithm because it's the right one for your problem. Eventually you're going to need to write your own replacement for these GRASS modules, implementing the scheme you've chosen based on literature reviews or your own mathematical formulation.
I suggest you take a look at Noel Cressie's book "Statistics for Spatial Data", or perhaps spend some time hanging out on the Geostats mailing list (send subscribe/unsubscribe requests to ai-geostats-request@gis.psu.edu).
----
Hal Mueller
Seattle, Washington hal@seanet.com