r.in.poly.html 3.0 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110
  1. <h2>DESCRIPTION</h2>
  2. <em>r.in.poly</em> allows the creation of GRASS binary
  3. raster maps from ASCII files in the current directory
  4. containing polygon, linear, and point features.
  5. <p>
  6. The <b>input</b> file is an ASCII text file containing the
  7. polygon, linear, and point feature definitions.
  8. The format of this file is described in the
  9. <a href="#format.html"><i>INPUT FORMAT</i></a> section below.
  10. <p>
  11. The number of raster <b>rows</b> to hold in memory is per default 4096.
  12. This parameter allows users with less memory (or more) on their
  13. system to control how much memory <em>r.in.poly</em> uses.
  14. Usually the default value is fine.
  15. <h2>NOTES</h2>
  16. <p>
  17. The data will be imported using the current region settings to set the
  18. new raster map's bounds and resolution. Any features falling outside
  19. the current region will be cropped. The region settings are contolled
  20. with the <em>g.region</em> module.
  21. <p>
  22. The format is a simplified version of the standard GRASS vector ASCII
  23. format used by <em>v.in.ascii</em>.
  24. <p>
  25. Polygons are filled, i.e. they define an area.
  26. <A NAME="format.html"></a>
  27. <h3>Input Format</h3>
  28. The input format for the <b>input</b> file consists of
  29. sections describing either polygonal areas, linear features, or
  30. point features. The basic format is:
  31. <div class="code"><pre>
  32. A &lt;for polygonal areas&gt;
  33. easting northing
  34. .
  35. .
  36. .
  37. = cat# label
  38. L &lt;for linear features&gt;
  39. easting northing
  40. .
  41. .
  42. .
  43. = cat# label
  44. P &lt;for single cell point features&gt;
  45. easting northing
  46. = cat# label
  47. </pre></div>
  48. The <tt>A</tt> signals the beginning of a filled polygon.
  49. It must appear in the first column.
  50. The <tt>L</tt> signals the beginning of a linear feature.
  51. It also must appear in the first column.
  52. The <tt>P</tt> signals the beginning of a single cell point feature.
  53. Again, it must appear in the first column.
  54. The coordinates of the vertices of the polygon, or the coordinates defining
  55. the linear or point feature follow and must have a space in the first
  56. column and at least one space between the <em>easting</em> and the
  57. <em>northing.</em> To give meaning to the features, the
  58. "<tt>=</tt>" indicates that the feature currently being
  59. processed has category value <em>cat#</em> (which must be
  60. an integer) and a <em>label</em> (which may be more than
  61. one word, or which may be omitted).
  62. <h2>EXAMPLE</h2>
  63. An area described by four points:
  64. <div class="code"><pre>
  65. A
  66. 591316.80 4926455.50
  67. 591410.25 4926482.40
  68. 591434.60 4926393.60
  69. 591341.20 4926368.70
  70. = 42 stadium
  71. </pre></div>
  72. <h2>SEE ALSO</h2>
  73. <em>
  74. <a href="r.colors.html">r.colors</a>,
  75. <a href="d.rast.edit.html">d.rast.edit</a>,
  76. <a href="g.region.html">g.region</a>,
  77. <a href="r.in.xyz.html">r.in.xyz</a>,
  78. <a href="r.patch.html">r.patch</a>,
  79. <a href="v.in.ascii.html">v.in.ascii</a>,
  80. <a href="wxGUI.vdigit.html">wxGUI vector digitizer</a>
  81. </em>
  82. <h2>AUTHOR</h2>
  83. Michael Shapiro, U.S.Army Construction Engineering Research Laboratory
  84. <p><i>Last changed: $Date$</i>