raster3dintro.html 5.0 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106
  1. <!-- meta page description: 3D raster data (voxel) processing in GRASS GIS -->
  2. <!-- meta page index: raster3D -->
  3. <h3>3D Raster maps (voxels) in general</h3>
  4. GRASS GIS is one of the few GIS software packages with volume data support.
  5. Here data are stored as a 3D raster with a unit volume called a voxel
  6. (volume pixel). Voxels are designed to support representations of
  7. trivariate continuous fields. The vertical dimension supports spatial and temporal units.
  8. Hence space time voxel cubes with different temporal resolutions can be created and processed.
  9. <p>
  10. GRASS GIS 3D raster maps use the same coordinate system as
  11. 2D raster maps (row count from north to south) with an additional z dimension (depth)
  12. counting from bottom to top. The upper left corner (NW) is the origin of the voxel.
  13. Volumes are stored using a tile cache based approach. This allows abritrary read
  14. and write operations in the created volume. The size of the tiles can be specified at import time
  15. with <a href="r3.in.ascii.html">r3.in.ascii</a> or the data can be retiled using
  16. <a href="r3.retile.html">r3.retile</a> after import or creation.
  17. <div align="center" style="margin: 10px">
  18. <img src="r3_volume_layout.png" border=0><br>
  19. <i>The volume coordinate system and tile layout of the RASTER3D library</i>
  20. </div>
  21. <h3>3D Raster (voxel) import</h3>
  22. The modules <a href="r3.in.ascii.html">r3.in.ascii</a> and
  23. <a href="r3.in.bin.html">r3.in.bin</a> supports
  24. generic x,y,z ASCII and binary array import. Alternatively, volumes can be generated
  25. from 3D point vector data (<a href="v.to.rast3.html">v.to.rast3</a>).
  26. Always the full map is imported.
  27. Volumes can also be created based on 2D elevation map(s) and value raster map(s)
  28. (<a href="r.to.rast3elev.html">r.to.rast3elev</a>). Alternatively,
  29. a volume can be composed of several 2D raster map slices which are
  30. merged into one 3D raster (voxel) map (<a href="r.to.rast3.html">r.to.rast3</a>).
  31. <h3>3D region settings and 3D MASK</h3>
  32. GRASS 3D raster map processing is always performed in the current 3D region
  33. settings (see <a href="g.region.html">g.region</a>, <em>-p3</em> flags), i.e.
  34. the current region extent, vertical extent and current 3D resolution are used.
  35. If the 3D resolution differs from that of the input raster map(s),
  36. on-the-fly resampling is performed (nearest neighbor resampling).
  37. If this is not desired, the input map(s) has/have to be reinterpolated
  38. beforehand with one of the dedicated modules.
  39. Masks can be set (<a href="r3.mask.html">r3.mask</a>).
  40. <h3>Volume operations</h3>
  41. Powerful 3D map algebra is implemented in <a href="r3.mapcalc.html">r3.mapcalc</a>.
  42. A 3D groundwater flow model is implemented in <a href="r3.gwflow.html">r3.gwflow</a>.
  43. <h3>3D raster conversion to vector or 2D raster maps</h3>
  44. 3D vector point data can be converted to a GRASS 3D raster map
  45. (<a href="v.to.rast3.html">v.to.rast3</a>).
  46. Layers from a 3D raster map can be converted to a 2D raster map
  47. (<a href="r3.to.rast.html">r3.to.rast</a>).
  48. Cross sectional 2D raster map can be extracted from 3D raster map based
  49. on a 2D elevation map (<a href="r3.cross.rast.html">r3.cross.rast</a>).
  50. <h3>3D raster statistics</h3>
  51. Volume statistics can be calculated with <a href="r3.stats.html">r3.stats</a>
  52. and <a href="r3.univar.html">r3.univar</a>.
  53. <h3>3D raster interpolation</h3>
  54. From 3D vector points, GRASS 3D raster maps can be interpolated
  55. (<a href="v.vol.rst.html">v.vol.rst</a>). Results are volumes,
  56. or 2D raster maps can be also extracted.
  57. <h3>3D raster export</h3>
  58. The modules <a href="r3.out.ascii.html">r3.out.ascii</a> and
  59. <a href="r3.out.bin.html">r3.out.bin</a> support the export of
  60. 3D raster maps as ASCII or binary files. The output of these modules
  61. can be imported with the coresponding import modules noted above.
  62. <p>
  63. NetCDF export of 3D raster maps can be performed using the module
  64. <a href="r3.out.netcdf.html">r3.out.netcdf</a>. It supports 3D raster maps
  65. with spatial and temporal vertical dimension (Space time voxel cubes).
  66. <p>
  67. GRASS 3D raster maps can be exported to VTK (<a href="r3.out.vtk.html">r3.out.vtk</a>).
  68. VTK files can be visualized with the
  69. <em><a href="http://www.vtk.org">VTK Toolkit</a></em>,
  70. <em><a href="http://www.paraview.org">Paraview</a></em> and
  71. <em><a href="http://mayavi.sourceforge.net">MayaVi</a></em>.
  72. GRASS 2D raster maps can be exported to VTK with <a href="r.out.vtk.html">r.out.vtk</a>,
  73. GRASS vector maps can be exported to VTK with <a href="v.out.vtk.html">v.out.vtk</a>.
  74. <p>
  75. Alternatively, GRASS 3D raster maps can be imported and exported from/to Vis5D
  76. (<a href="r3.in.v5d.html">r3.in.v5d</a>, <a href="r3.out.v5d.html">r3.out.v5d</a>).
  77. Note that Vis5D is limited in the number of supported volumes.
  78. <h3>See also</h3>
  79. <ul>
  80. <li><a href="rasterintro.html">Introduction into raster data processing</a></li>
  81. <li><a href="vectorintro.html">Introduction into vector data processing</a></li>
  82. <li><a href="imageryintro.html">Introduction into image processing</a></li>
  83. <li><a href="databaseintro.html">Database management</a></li>
  84. <li><a href="projectionintro.html">Projections and spatial transformations</a></li>
  85. </ul>