1d.nviz(1) Grass User's Manual d.nviz(1)
2
3
4
6 d.nviz - Creates fly-through script to run in NVIZ.
7
9 display
10
12 d.nviz
13 d.nviz help
14 d.nviz [-ifckoe] input=name output=name [name=string]
15 [route=east,north[,east,north,...]] dist=float ht=float frames=integer
16 [start=integer] [--verbose] [--quiet]
17
18 Flags:
19 -i
20 Interactively select route
21
22 -f
23 Full render -- Save images
24
25 -c
26 Fly at constant elevation (ht)
27
28 -k
29 Include command in the script to output a KeyFrame file
30
31 -o
32 Render images off-screen
33
34 -e
35 Enable vector and sites drawing
36
37 --verbose
38 Verbose module output
39
40 --quiet
41 Quiet module output
42
43 Parameters:
44 input=name
45 Name of input raster map
46
47 output=name
48 Name of output script
49
50 name=string
51 Prefix of output images (default = NVIZ)
52
53 route=east,north[,east,north,...]
54 Route coordinates (east,north)
55
56 dist=float
57 Camera layback distance (in map units)
58
59 ht=float
60 Camera height above terrain
61
62 frames=integer
63 Number of frames
64
65 start=integer
66 Start frame number (default=0)
67
69 The d.nviz program allows the user to easily create a script that can
70 be run in NVIZ to fly through a terrain. The NVIZ flight path can be
71 chosen interactively from the GRASS monitor (-i) or supplied on the
72 command line as comma separated coordinates. The program optionally
73 allows a KeyFrame file to created (after running the script). This
74 KeyFrame file can be loaded into the Keyframe Animation panel for fine
75 tuning or editing.
76
77 The script generated by d.nviz can be run from the NVIZ command line
78 (nviz script=script_name) or after NVIZ is started by selecting Script‐
79 ing->Play Script.
80
82 Flags:
83 -i
84 Intercative mode
85 The user selects the camera path from the GRASS monitor by
86 clicking the left mouse button along the route. Click the right
87 mouse button to finish.
88
89 -f
90 Full render
91 The script will draw all loaded NVIZ data and save scene to PPM
92 image.
93
94 -c
95 Flay at constant elevation
96 With this flag the camera will be set to an elevation given by
97 the ht= parameter. The default is to fly at ht= above the topog‐
98 raphy (i.e. camera height = elevation + ht)
99
100 -k
101 Output KeyFrame file
102 Generate a KeyFrame file that can be loaded from the NVIZ
103 Keyframe Animation panel. The KeyFrame file is automatically
104 assigned the script name with a .kanimator extension.
105
106 -o
107 Render the animation in an off-screen context
108
109 -e
110 Enable vector and sites drawing
111
112 Parameters:
113 input
114 The name of the GRASS raster map with elevation data.
115 This should be the same file that will be loaded in NVIZ.
116
117 output
118 The name of the NVIZ script to create.
119
120 name
121 The prefix for output images if running in full render mode
122 (-f).
123 The defulat preifix is NVIZ (eg. NVIZ0000.ppm).
124
125 dist
126 The distance of the camera behind the center of view.
127
128 ht
129 The height of the camera above the center of view.
130 If the the -c flag is set, the height represents the actual cam‐
131 era height.
132
133 frames
134 The number of frames in the animation.
135
136 start
137 The starting frame number (default = 0).
138 This option may be useful in full render mode when creating an
139 animation in sections. For example the user may wish to start at
140 frame number 2000.
141
142 route
143 The comma seperated geographic coordinates for keyframe loca‐
144 tions.
145 The interactive flag (-i) overrides this option.
146
148 To interactively create an NVIZ animation from raster elev.rast with
149 500 frames and the camera set to 50 meters above and 250 meters behind
150 the scene, run the following:
151 d.nviz -ik input=elevation.dem output=nviz.script dist=2400 ht=1220
152 frames=1000
153 In the above the example the user is prompted to select the route from
154 the GRASS monitor. The output script, nviz.script, can then be run in
155 NVIZ:
156 nviz el=elevation.dem script=nviz.script
157
158
160 The user must select at least four key-frame locations (points) other‐
161 wise an error is generated.
162
163 If the GRASS region is changed the d.nviz command must be re-run.
164
165 The current GRASS region and the user supplied paramters are included
166 as a comment at the top of the output script. This information can be
167 used to easily re-create the animation.
168
169 The camera position is calculated backwards from the supplied posi‐
170 tion(s). It is possible that the camera position will lie outside the
171 current window, in which case a non-fatal error is generated (Error:
172 selected point is outside region). This error can result in jerky
173 movements during the animation. To correct this problem reduce the
174 dist= parameter or increase the current region.
175
176 Loading the script into NVIZ
177 The user can run the script at arbitrary resolution. To re-run it at
178 higher spatial resolution or different settings, the user first loads
179 the surface and sets the resolution, lighting, etc. Then internally the
180 script generated by d.nviz is run. Alternatively, the user can run nviz
181 with a previuosly saved state and the d.nviz generated script:
182 nviz state=saved.state script=nviz.script
183
184
185 Keyframe animator script
186 Running the script generated by d.nviz within NVIZ, a new script for
187 kanimator (keyframe animator) is created. The kanimator panel offers
188 fine tuning of the speed (frame rate) as well as editing individual
189 frames or inserting new frames. This new kanimator script has to be
190 loaded from the Kanimator panel in NVIZ. In the Kanimator panel there
191 are Save and Load button which allow the user to save and re-load a
192 kanimator script. Once loaded, the key frames will appear in the GUI
193 and can then be edited there.
194
196 nviz
197
199 Bob Covill
200
201 Last changed: $Date: 2006-12-13 15:21:43 +0100 (Wed, 13 Dec 2006) $
202
203 Full index
204
205 © 2003-2008 GRASS Development Team
206
207
208
209GRASS 6.3.0 d.nviz(1)