r3.in.ascii.html 4.3 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115
  1. <h2>DESCRIPTION</h2>
  2. <em>r3.in.ascii</em> allows a user to create a (binary) GRASS 3D raster map
  3. layer from a 3D ASCII raster input file.
  4. <p>The <em>tiledimension</em> parameter defines the dimension of the tiles
  5. used in the output file. The format is: XxYxZ
  6. <p>The <em>nv</em> parameter specifies which value to convert to NULL-value.
  7. If the specified value is <em>none</em>, no conversion is performed.
  8. Default is <em>none</em>.
  9. <h2>NOTES</h2>
  10. A detailed description of the input format as well as the supported row/depth
  11. ordering is available in the <a href="r3.out.ascii.html">r3.out.ascii</a>.
  12. manual page. The order of the data in the input file does not specifiy the
  13. data order in the generated output 3D raster map which is in any case
  14. <em>north -> south, west -> east, bottom -> top</em> order.
  15. The data is automatically imported into the correct internal coordinate system,
  16. that is visualized in the following picture, independently from the specified
  17. ordering in the ASCII input file:
  18. <center>
  19. <img src="g3d_volume_layout.png" border=0><br>
  20. <table border=0 width=700>
  21. <tr><td><center>
  22. <i>The volume coordinate system and tile layout of the imported voxel map</i>
  23. </center></td></tr>
  24. </table>
  25. </center>
  26. <h2>NOTES</h2>
  27. The format of the 3D ASCII file:
  28. <div class="code"><pre>
  29. version: <i>"grass7"</i>
  30. order: <i>"nsbt" or "nstb" or "snbt" or "sntb"</i>
  31. north: <i>floating point</i>
  32. south: <i>floating point</i>
  33. east: <i>floating point</i>
  34. west: <i>floating point</i>
  35. top: <i>floating point</i>
  36. bottom: <i>floating point</i>
  37. rows: <i>integer</i>
  38. cols: <i>integer</i>
  39. levels: <i>integer</i>
  40. </pre></div>
  41. The version and order option have been introduced in GRASS 7 in June 2011.
  42. The version option is self explaining. The order option specifies the row
  43. and depth order of the data in the input file.
  44. The supported row/depth ordering is documented in the <em>r3.out.ascii</em>
  45. manual page. The order of the data in the input file does not specifiy the
  46. data order in the generated output 3D raster map which is in any case
  47. <em>north -> south, west -> east, bottom -> top</em> order.
  48. So dependent on the order information the data is automatically imported
  49. into the correct internal coordinate system.
  50. <p>The version and order options are not mandatory. In case no version and
  51. order option is specified, the default GRASS 6 ASCII format is assumed.
  52. <p>This header is followed by the cell values in <em>floating point</em> format
  53. organized in rows with constant <em>col</em> and <em>level</em> coordinate.
  54. The rows are organized by constant <em>level</em> coordinate. Individual cell
  55. values are separated by <em>space</em> or <em>CR</em>.
  56. <h2>EXAMPLES</h2>
  57. 4x3x2 sample. Note in case no specific ordering is specified in the input
  58. file the upper-left (NW) corner of the bottom level comes first. The according
  59. order option is: nsbt for north -> south, bottom -> top ordering. This is
  60. identical with <em>r.in.ascii</em> for single level data. So the y coordinate
  61. is 0 at the northern edge.
  62. <div class="code"><pre>
  63. north: 3.0
  64. south: 0.0
  65. east: 4.0
  66. west: 0.0
  67. top: 2.0
  68. bottom: 0.0
  69. rows: 3
  70. cols: 4
  71. levels: 2
  72. 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
  73. 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
  74. 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
  75. 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
  76. 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
  77. 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
  78. </pre></div>
  79. Note that unit tests for <em>r3.in.ascii</em> are implemented in the
  80. <em>test.r3.out.ascii.sh</em> script located in the
  81. <em>r3.out.ascii</em> directory.
  82. <h2>EXAMPLES</h2>
  83. Please refer to the detailed examples in
  84. <a href="r3.out.ascii.html">r3.out.ascii</a>.
  85. <h2>AUTHORS</h2>
  86. Roman Waupotitsch, Michael Shapiro,
  87. Helena Mitasova, Bill Brown, Lubos Mitas, Jaro Hofierka, S&ouml;ren Gebbert
  88. <h2>SEE ALSO</h2>
  89. <em>
  90. <a href="r.in.ascii.html">r.in.ascii</a>,
  91. <a href="r3.out.ascii.html">r3.out.ascii</a>,
  92. <a href="v.to.rast3.html">v.to.rast3</a>,
  93. <a href="g.region.html">g.region</a>
  94. </em>
  95. <p><i>Last changed: $Date$</i>