helptext.html 9.1 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213
  1. <!-- meta page description: GRASS GIS Quickstart -->
  2. <h2>Geographic Resources Analysis Support System</h2>
  3. GRASS GIS, commonly referred to as GRASS (Geographic Resources Analysis
  4. Support System), is a free Geographic Information System (GIS) software
  5. used for geospatial data management and analysis, image processing,
  6. graphics/maps production, spatial modeling, and visualization. GRASS GIS
  7. is currently used in academic and commercial settings around the world,
  8. as well as by many governmental agencies and environmental consulting
  9. companies. GRASS GIS is an official project of the Open Source Geospatial
  10. Foundation (OSGeo).
  11. <h2>1. Graphical startup of GRASS GIS</h2>
  12. <i>For text-based startup see below.</i>
  13. <p>
  14. After <a href="grass.html">launching</a> GRASS GIS, the startup screen will open:
  15. <p>
  16. <center>
  17. <img src="grass_start.png" alt="[GRASS GIS start screen]">
  18. </center>
  19. <h3><img src="circle_1.png" alt="[(1)]">&nbsp;Selecting the GIS Database directory</h3>
  20. GRASS data are stored in a directory referred to as DATABASE
  21. (also called "GISDBASE"). This directory has to be created
  22. with a file manager or the <tt>mkdir</tt> command, before starting to work
  23. with GRASS. Within this DATABASE, the projects are organized
  24. by project areas stored in subdirectories called LOCATIONs.
  25. <h3><img src="circle_2.png" alt="[(2)]">&nbsp;Selecting the LOCATION (a project)</h3>
  26. A LOCATION is defined by its coordinate system, map projection and
  27. geographical boundaries. The subdirectories and files defining a
  28. LOCATION are created automatically when GRASS is started the first
  29. time with a new LOCATION. It is important to understand that each
  30. projection stays in its own LOCATION.
  31. <p>
  32. See the "Location Wizard"&nbsp;<img src="circle_4.png" alt="[(4)]"> to
  33. easily create a new LOCATION from scratch from a geocoded file, by
  34. defining the parameters or by selecting the corresponding EPSG projection
  35. code.
  36. <p>
  37. See&nbsp;<img src="circle_5.png" alt="[(5)]"> to directly download a
  38. sample LOCATION into the DATABASE.
  39. <h3><img src="circle_3.png" alt="[(3)]">&nbsp;Selecting the MAPSET (a subproject)</h3>
  40. Each LOCATION can have many MAPSETs. Each MAPSET is a LOCATION's
  41. subdirectory. New MAPSET can be added at GRASS startup (see related
  42. button).
  43. <h3><img src="circle_4.png" alt="[(4)]">&nbsp;Location Wizard</h3>
  44. The "Location Wizard" let's you easily create a new LOCATION. You
  45. will be guided through a series of dialogues to browse and select
  46. predefined projections (also via EPSG code) or to define individual
  47. projections. You can also create new LOCATION easily from a georeferenced
  48. data file (e.g., SHAPE file or GeoTIFF, see below). Find below also some
  49. rules to define the default raster resolution for a new LOCATION.
  50. <h3><img src="circle_5.png" alt="[(5)]">&nbsp;Download a sample LOCATION</h3>
  51. In the "Location Wizard" there is also a Download button that allows you to
  52. directly download a ready-to-use LOCATION into the DATABASE. You can
  53. choose among different sample LOCATIONS that are currently available at the
  54. <a href="https://grass.osgeo.org/download/sample-data/">Download</a>
  55. section in the GRASS GIS website.
  56. <h3><img src="circle_6.png" alt="[(6)]">&nbsp;Start GRASS</h3>
  57. Once you have selected an existing LOCATION/MAPSET or defined a new
  58. one, you can enter GRASS. The graphical user interface
  59. <a href="wxGUI.html">wxGUI</a> will open and provide you with a
  60. menu system, map visualization tool, digitizer, and more.
  61. <h2>2. Background: GRASS GIS Location structure</h2>
  62. A LOCATION is simply a set of directories which contains the GRASS
  63. data of a project. Within each LOCATION, a mandatory "PERMANENT"
  64. MAPSET exists which contains projection information and some more
  65. definitions. It can be used to store the base cartography in it as
  66. "PERMANENT" is visible to all users accessing a LOCATION.
  67. <p>
  68. <!-- original drawing: ../../doc/grass_database.svg -->
  69. <center>
  70. <img src="grass_database.png" alt="[GRASS GIS Location structure]" style="padding:5px;" border="1"><br>
  71. <i>Fig. 1: GRASS GIS 8 location structure</i>
  72. </center>
  73. <h3>Creating and maintaining MAPSETs</h3>
  74. One motivation to maintain different MAPSETs is to store maps
  75. related to project issues or subregions. Another motivation is to
  76. support simultaneous access of several users to the map layers
  77. stored within the same LOCATION, i.e. teams working on the same
  78. project. For teams, a centralized GRASS DATABASE would be defined
  79. in a shared network file system (e.g. NFS). Besides access to his/her own
  80. MAPSET, each user can also read map layers in other users' MAPSETs,
  81. but s/he can modify or remove only the map layers in his/her own
  82. MAPSET.
  83. <p>
  84. You can learn more about mapsets and how to seamlessly access maps
  85. found in another MAPSET of the same LOCATION in the
  86. <a href="g.mapsets.html">g.mapsets</a> documentation.
  87. <h3>The role of the "PERMANENT" MAPSET</h3>
  88. When creating a new LOCATION, GRASS GIS automatically creates a special
  89. MAPSET called PERMANENT where the core data for the project can be
  90. stored. Data in the PERMANENT MAPSET can only be added, modified or
  91. removed by the owner of the PERMANENT MAPSET; however, they can be
  92. accessed, analyzed, and copied into their own MAPSET by the other
  93. users. The PERMANENT MAPSET is useful for providing general spatial
  94. data (e.g. an elevation model), accessible but write-protected to all
  95. users who are working in the same LOCATION as the database owner.
  96. To manipulate or add data to PERMANENT, the owner would start
  97. GRASS and choose the relevant LOCATION and the PERMANENT MAPSET. This
  98. mapset also contains the DEFAULT_WIND file, which holds the default
  99. region boundary coordinate values for the LOCATION (which all users
  100. will inherit when they start using the database). Additionally, in
  101. all mapsets a WIND file is kept, for storing the current boundary
  102. coordinate values and the currently selected raster resolution. Users
  103. have the option of switching back to the default region at any time.
  104. <h2>3. Creating a GRASS Database with Sample Data</h2>
  105. To create the GRASS database:
  106. <ol>
  107. <li> Find a place on your disk where you have write access and that
  108. has enough disk space to hold your spatial data.</li>
  109. <li> Create a subdirectory that will hold the general GRASS database
  110. (e.g. using a file manager or with <tt>mkdir /data/grassdata</tt> or
  111. <tt>mkdir /home/yourlogin/grassdata</tt>).</li>
  112. </ol>
  113. <p>
  114. Sample data such as the &quot;North Carolina&quot; or the
  115. &quot;Spearfish&quot; sample datasets may be downloaded from
  116. <a href="https://grass.osgeo.org/download/data/">https://grass.osgeo.org/download/data/</a>
  117. and the compressed data package(s) extracted into this new database
  118. directory.
  119. <p>
  120. Now you are ready to select a sample dataset in the GRASS GIS startup screen
  121. (see above) and start the session.
  122. <h2>4. Creating a New Location with the Location Wizard</h2>
  123. The <a href="wxGUI.html">wxGUI</a> graphical user interface provides a
  124. graphical "Location Wizard" which lets you easily create a
  125. new LOCATION for own data. You will be guided through a series of dialogues to
  126. browse and select predefined projections (also via EPSG code) or to
  127. define individual projections. The rules to define the resolution as
  128. described above also apply here.
  129. <p>
  130. <i>Hint: You can create new LOCATION easily from a georeferenced data file
  131. (e.g., SHAPE file or GeoTIFF file with the related metadata properly included).
  132. In this case you are asked whether the data itself should be imported
  133. into the new LOCATION. The default region is then set to match imported map
  134. and the GRASS GIS session is opened.</i>
  135. <p>
  136. After defining new LOCATION, wxGUI starts automatically.
  137. If data were already imported, you can add them into the Layer Manager now
  138. and display them. If your LOCATION is empty you can import your data from
  139. the menu: Go to "File" -&gt; "Import raster/vector data" (see also the
  140. related Wiki page on <a href="https://grasswiki.osgeo.org/wiki/Importing_data">Importing data</a>).
  141. <h2>5. Text-based startup and location creation</h2>
  142. GRASS GIS can be run entirely without using the graphical user interface.
  143. For a first time startup, the following steps have to be followed:
  144. <ol>
  145. <li> Create the GRASS GIS database directory (with a file manager; or on command line: <tt>mkdir /home/user/grassdata</tt></li>
  146. <li> Create a new location, including it's default PERMANENT mapset,
  147. without entering the new location:
  148. <ul>
  149. <li>Using an EPSG code:<br>
  150. &nbsp;<tt>grass -e -c EPSG:32630 /home/user/grassdata/mylocation</tt></li>
  151. <li>Using a georeferenced raster or vector file:<br>
  152. &nbsp;<tt>grass -e -c MyGeoReferenceFile.tif /home/user/grassdata/mylocation</tt></li>
  153. </ul></li>
  154. <li> Create new mapset within the new location and launch GRASS GIS within
  155. that mapset: <br>
  156. &nbsp;<tt>grass -c /home/user/grassdata/mylocation/mymapset</tt>
  157. </ol>
  158. <h2>Further Reading</h2>
  159. Please have a look at the GRASS GIS web site for tutorials and books:
  160. <a href="https://grass.osgeo.org/learn/">https://grass.osgeo.org/learn/</a>.
  161. <h2>See also</h2>
  162. <em>
  163. <a href="index.html">GRASS GIS 8 Reference Manual</a>
  164. <br>
  165. <a href="grass.html">GRASS GIS 8 startup program manual page</a>
  166. </em>
  167. <p>
  168. <a href="https://epsg.io/">List of EPSG codes</a> (Database of worldwide coordinate systems)
  169. <!--
  170. <p>
  171. <i>Last changed: $Date$</i>
  172. -->