In the paper it lists a few commands to work with
* s.edgedetection
* s.growing
* s.correction
* s.bspline.reg
Which only appear in GRASS 5.3. Are they gone forever from the newer
versions, or has their functionality been folded into other commands?
I've also tried processing the data using s.surf.idw ( another 5.3
only command it seems ) and r.contour, but the processing time on a
1.6ghz system is measured in days. Is there a faster way of doing
this? I'm a bit at a loss for direction at the moment, any tips are
greatly appreciated.
At the moment the commands are not inside the 5.7 or 6 version of grass.
The commands you are referring works with old site format (5.3), that has been replaced with the new vector format.
When I'll be not so busy I'll reimplement them for the new version.... (hope soon).
in the newer version you have to refer to v.surf.idw and no more to s.surf.idw.
I suppose that r.countur running time depends on the raster resolution you are processing......
Good by,
Maxi
Kenneth Denson wrote:
I've been trying to figure out how to process LIDAR data using the
paper posted here:
In the paper it lists a few commands to work with
* s.edgedetection
* s.growing
* s.correction
* s.bspline.reg
Which only appear in GRASS 5.3. Are they gone forever from the newer
versions, or has their functionality been folded into other commands?
I've also tried processing the data using s.surf.idw ( another 5.3
only command it seems ) and r.contour, but the processing time on a
1.6ghz system is measured in days. Is there a faster way of doing
this? I'm a bit at a loss for direction at the moment, any tips are
greatly appreciated.
after consulting other Grass users it seems that I am the only one, who can
not read in ascii files with v.in.ascii. The same procedure (see below) works
perfectly on other computers (Debian too), but not on mine. I tried grass57,
grass60 and grass60cvs (all compiled from source). It's all the same.
I have no clue what I am doing wrong, so all hints are more than welcome.
cheers,
robert
Here is what I did:
I used emacs to write following Coordinates in to the file test.txt.
Maximum input row length: 15
Maximum number of columns: 2
Minimum number of columns: 2
Building topology ...
0 primitives registered
0 areas built
0 isles built
Attaching islands: Attaching centroids: Topology was built.
Number of nodes : 0
Number of primitives: 0
Number of points : 0
Number of lines : 0
Number of boundaries: 0
Number of centroids : 0
Number of areas : 0
Number of isles : 0
after consulting other Grass users it seems that I am the only one,
who can not read in ascii files with v.in.ascii. The same procedure
(see below) works perfectly on other computers (Debian too), but not
on mine. I tried grass57, grass60 and grass60cvs (all compiled from
source). It's all the same.
I have no clue what I am doing wrong, so all hints are more than
welcome.
Can you enter the command:
g.gisenv set="DEBUG=5"
then run the v.in.ascii command
then to turn debugging messages back off:
g.gisenv set="DEBUG=0"
That might give some more clues as to what is happening internally.
> cat test.txt | v.in.ascii fs='|' out=points6 x=1 y=2
Maximum input row length: 15
Maximum number of columns: 2
Minimum number of columns: 2
Building topology ...
0 primitives registered
0 areas built
0 isles built
Attaching islands: Attaching centroids: Topology was built.
Number of nodes : 0
Number of primitives: 0
Number of points : 0
Number of lines : 0
Number of boundaries: 0
Number of centroids : 0
Number of areas : 0
Number of isles : 0