1r3.in.ascii(1) GRASS GIS User's Manual r3.in.ascii(1)
2
3
4
6 r3.in.ascii - Converts a 3D ASCII raster text file into a (binary) 3D
7 raster map.
8
10 raster3d, import, voxel, conversion, ASCII
11
13 r3.in.ascii
14 r3.in.ascii --help
15 r3.in.ascii input=name output=name [null_value=string] [type=string]
16 [precision=string] [compression=string] [tiledimension=XxYxZ]
17 [--overwrite] [--help] [--verbose] [--quiet] [--ui]
18
19 Flags:
20 --overwrite
21 Allow output files to overwrite existing files
22
23 --help
24 Print usage summary
25
26 --verbose
27 Verbose module output
28
29 --quiet
30 Quiet module output
31
32 --ui
33 Force launching GUI dialog
34
35 Parameters:
36 input=name [required]
37 Name of input file to be imported
38 ’-’ for standard input
39
40 output=name [required]
41 Name for output 3D raster map
42
43 null_value=string
44 String representing NULL value data cell (use ’none’ if no such
45 value)
46 Default: *
47
48 type=string
49 Data type used in the output raster3d map
50 Options: default, double, float
51 Default: default
52
53 precision=string
54 Number of digits used as mantissa in the internal map storage, 0
55 -23 for float, 0 - 52 for double, max or default
56 Default: default
57
58 compression=string
59 The compression method used in the output raster3d map
60 Options: default, zip, none
61 Default: default
62
63 tiledimension=XxYxZ
64 The dimensions of the tiles used in the output raster3d map (XxYxZ
65 or default: 16x16x8)
66 Default: default
67
69 r3.in.ascii allows a user to create a (binary) GRASS 3D raster map
70 layer from a 3D ASCII raster input file.
71
72 The tiledimension parameter defines the dimension of the tiles used in
73 the output file. The format is: XxYxZ
74
75 The nv parameter specifies which value to convert to NULL-value. If
76 the specified value is none, no conversion is performed. Default is
77 none.
78
80 The data is automatically imported into the correct internal coordinate
81 system, that is visualized in the following picture, independently from
82 the specified ordering in the ASCII input file:
83
84 The volume coordinate system and tile layout of the imported
85 voxel map
86
87
88 Format
89 The format of the 3D ASCII file:
90 version: "grass7"
91 order: "nsbt" or "nstb" or "snbt" or "sntb"
92 north: floating point
93 south: floating point
94 east: floating point
95 west: floating point
96 top: floating point
97 bottom: floating point
98 rows: integer
99 cols: integer
100 levels: integer
101 The version and order option have been introduced in GRASS 7 in June
102 2011. The version option is self explaining. The order option speci‐
103 fies the row and depth order of the data in the input file. The sup‐
104 ported row/depth ordering is documented in the r3.out.ascii manual
105 page. The order of the data in the input file does not specify the data
106 order in the generated output 3D raster map which is in any case north
107 -> south, west -> east, bottom -> top order. So dependent on the order
108 information the data is automatically imported into the correct inter‐
109 nal coordinate system.
110
111 The version and order options are not mandatory. In case no version and
112 order option is specified, the default GRASS 6 ASCII format is assumed.
113
114 This header is followed by the cell values in floating point format or‐
115 ganized in rows with constant col and level coordinate. The rows are
116 organized by constant level coordinate. Individual cell values are sep‐
117 arated by space or CR.
118
120 4x3x2 sample. Note in case no specific ordering is specified in the in‐
121 put file the upper-left (NW) corner of the bottom level comes first.
122 The according order option is: nsbt for north -> south, bottom -> top
123 ordering. This is identical with r.in.ascii for single level data. So
124 the y coordinate is 0 at the northern edge. north: 3.0
125 south: 0.0
126 east: 4.0
127 west: 0.0
128 top: 2.0
129 bottom: 0.0
130 rows: 3
131 cols: 4
132 levels: 2
133 w111x1,y1,z1 w211x2,y1,z1 w311x3,y1,z1 w411x4,y1,z1
134 w121x1,y2,z1 w221x2,y2,z1 w321x3,y2,z1 w421x4,y2,z1
135 w131x1,y3,z1 w231x2,y3,z1 w331x3,y3,z1 w431x4,y3,z1
136 w112x1,y1,z2 w212x2,y1,z2 w312x3,y1,z2 w412x4,y1,z2
137 w122x1,y2,z2 w222x2,y2,z2 w322x3,y2,z2 w422x4,y2,z2
138 w132x1,y3,z2 w232x2,y3,z2 w332x3,y3,z2 w432x4,y3,z2
139
140 Note that unit tests for r3.in.ascii are implemented in the
141 test.r3.out.ascii.sh script located in the r3.out.ascii directory.
142
144 Please refer to the detailed examples in r3.out.ascii.
145
147 r.in.ascii, r3.out.ascii, v.to.rast3, g.region
148
150 Roman Waupotitsch, Michael Shapiro, Helena Mitasova, Bill Brown, Lubos
151 Mitas, Jaro Hofierka, Sören Gebbert
152
154 Available at: r3.in.ascii source code (history)
155
156 Accessed: Saturday Oct 28 18:18:21 2023
157
158 Main index | 3D raster index | Topics index | Keywords index | Graphi‐
159 cal index | Full index
160
161 © 2003-2023 GRASS Development Team, GRASS GIS 8.3.1 Reference Manual
162
163
164
165GRASS 8.3.1 r3.in.ascii(1)