3
<em>r3.in.ascii</em> allows a user to create a (binary) GRASS 3D raster map
4
layer from a 3D ASCII raster input file.
6
<p>The <em>tiledimension</em> parameter defines the dimension of the tiles
7
used in the output file. The format is: XxYxZ
9
<p>The <em>nv</em> parameter specifies which value to convert to NULL-value.
10
If the specified value is <em>none</em>, no conversion is performed.
11
Default is <em>none</em>.
16
The data is automatically imported into the correct internal coordinate system,
17
that is visualized in the following picture, independently from the specified
18
ordering in the ASCII input file:
20
<img src="r3_volume_layout.png" border=0><br>
21
<table border=0 width=700>
23
<i>The volume coordinate system and tile layout of the imported voxel map</i>
30
The format of the 3D ASCII file:
31
<div class="code"><pre>
32
version: <i>"grass7"</i>
33
order: <i>"nsbt" or "nstb" or "snbt" or "sntb"</i>
34
north: <i>floating point</i>
35
south: <i>floating point</i>
36
east: <i>floating point</i>
37
west: <i>floating point</i>
38
top: <i>floating point</i>
39
bottom: <i>floating point</i>
42
levels: <i>integer</i>
45
The version and order option have been introduced in GRASS 7 in June 2011.
46
The version option is self explaining. The order option specifies the row
47
and depth order of the data in the input file.
48
The supported row/depth ordering is documented in the <em>r3.out.ascii</em>
49
manual page. The order of the data in the input file does not specifiy the
50
data order in the generated output 3D raster map which is in any case
51
<em>north -> south, west -> east, bottom -> top</em> order.
52
So dependent on the order information the data is automatically imported
53
into the correct internal coordinate system.
54
<p>The version and order options are not mandatory. In case no version and
55
order option is specified, the default GRASS 6 ASCII format is assumed.
56
<p>This header is followed by the cell values in <em>floating point</em> format
57
organized in rows with constant <em>col</em> and <em>level</em> coordinate.
58
The rows are organized by constant <em>level</em> coordinate. Individual cell
59
values are separated by <em>space</em> or <em>CR</em>.
63
4x3x2 sample. Note in case no specific ordering is specified in the input
64
file the upper-left (NW) corner of the bottom level comes first. The according
65
order option is: nsbt for north -> south, bottom -> top ordering. This is
66
identical with <em>r.in.ascii</em> for single level data. So the y coordinate
67
is 0 at the northern edge.
69
<!-- TODO: beautify HTML -->
79
w<sub>111</sub>x1,y1,z1 w<sub>211</sub>x2,y1,z1 w<sub>311</sub>x3,y1,z1 w<sub>411</sub>x4,y1,z1<br>
80
w<sub>121</sub>x1,y2,z1 w<sub>221</sub>x2,y2,z1 w<sub>321</sub>x3,y2,z1 w<sub>421</sub>x4,y2,z1<br>
81
w<sub>131</sub>x1,y3,z1 w<sub>231</sub>x2,y3,z1 w<sub>331</sub>x3,y3,z1 w<sub>431</sub>x4,y3,z1<br>
82
w<sub>112</sub>x1,y1,z2 w<sub>212</sub>x2,y1,z2 w<sub>312</sub>x3,y1,z2 w<sub>412</sub>x4,y1,z2<br>
83
w<sub>122</sub>x1,y2,z2 w<sub>222</sub>x2,y2,z2 w<sub>322</sub>x3,y2,z2 w<sub>422</sub>x4,y2,z2<br>
84
w<sub>132</sub>x1,y3,z2 w<sub>232</sub>x2,y3,z2 w<sub>332</sub>x3,y3,z2 w<sub>432</sub>x4,y3,z2<br>
87
Note that unit tests for <em>r3.in.ascii</em> are implemented in the
88
<em>test.r3.out.ascii.sh</em> script located in the
89
<em>r3.out.ascii</em> directory.
93
Please refer to the detailed examples in
94
<a href="r3.out.ascii.html">r3.out.ascii</a>.
97
Roman Waupotitsch, Michael Shapiro,
98
Helena Mitasova, Bill Brown, Lubos Mitas, Jaro Hofierka, Sören Gebbert
103
<a href="r.in.ascii.html">r.in.ascii</a>,
104
<a href="r3.out.ascii.html">r3.out.ascii</a>,
105
<a href="v.to.rast3.html">v.to.rast3</a>,
106
<a href="g.region.html">g.region</a>
109
<p><i>Last changed: $Date: 2013-09-22 00:45:09 +0200 (Sun, 22 Sep 2013) $</i>