helptext.html 7.3 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170
  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. Startup of GRASS GIS</h2>
  12. After <a href="grass7.html">launching</a> GRASS GIS, the startup screen will open:
  13. <p>
  14. <center>
  15. <img src="grass_start.png" alt="[GRASS GIS start screen]">
  16. </center>
  17. <h3><img src="circle_1.png" alt="[(1)]">&nbsp;Selecting the GIS Database directory</h3>
  18. GRASS data are stored in a directory referred to as DATABASE
  19. (also called "GISDBASE"). This directory has to be created
  20. with a file manager or the <tt>mkdir</tt> command, before starting to work
  21. with GRASS. Within this DATABASE, the projects are organized
  22. by project areas stored in subdirectories called LOCATIONs.
  23. <h3><img src="circle_2.png" alt="[(2)]">&nbsp;Selecting the LOCATION (a project)</h3>
  24. A LOCATION is defined by its coordinate system, map projection and
  25. geographical boundaries. The subdirectories and files defining a
  26. LOCATION are created automatically when GRASS is started the first
  27. time with a new LOCATION. It is important to understand that each
  28. projection stays in its own LOCATION.
  29. <p>
  30. See the "Location Wizard"&nbsp;<img src="circle_4.png" alt="[(4)]"> to
  31. easily create a new LOCATION from scratch from a geocoded file, by
  32. defining the parameters or by selecting the corresponding EPSG projection
  33. code.
  34. <h3><img src="circle_3.png" alt="[(3)]">&nbsp;Selecting the MAPSET (a subproject)</h3>
  35. Each LOCATION can have many MAPSETs. Each MAPSET is a LOCATION's
  36. subdirectory. New MAPSET can be added at GRASS startup (see related
  37. button).
  38. <h3><img src="circle_4.png" alt="[(4)]">&nbsp;Location Wizard</h3>
  39. The "Location Wizard" let's you easily create a new LOCATION. You
  40. will be guided through a series of dialogues to browse and select
  41. predefined projections (also via EPSG code) or to define individual
  42. projections. Find below some rules to define the default raster
  43. resolution for a new LOCATION.
  44. <h3><img src="circle_5.png" alt="[(5)]">&nbsp;Start GRASS</h3>
  45. Once you have selected an existing LOCATION/MAPSET or defined a new
  46. one, you can enter GRASS. The graphical user interface
  47. <a href="wxGUI.html">wxGUI</a> will open and provide you with a
  48. menu system, map visualization tool, digitizer, and more.
  49. <h2>2. Background: GRASS GIS Location structure</h2>
  50. A LOCATION is simply a set of directories which contains the GRASS
  51. data of a project. Within each LOCATION, a mandatory "PERMANENT"
  52. MAPSET exists which contains projection information and some more
  53. definitions. It can be used to store the base cartography in it as
  54. "PERMANENT" is visible to all users accessing a LOCATION.
  55. <p>
  56. <center>
  57. <img src="help_loc_struct.png" alt="[GRASS GIS Location structure]"><br>
  58. <i>Fig. 1: GRASS GIS location structure</i>
  59. </center>
  60. <h3>Creating and maintaining MAPSETs</h3>
  61. One motivation to maintain different MAPSETs is to store maps
  62. related to project issues or subregions. Another motivation is to
  63. support simultaneous access of several users to the map layers
  64. stored within the same LOCATION, i.e. teams working on the same
  65. project. For teams a centralized GRASS DATABASE would be defined
  66. in a network file system (e.g. NFS). Besides access to his/her own
  67. MAPSET, each user can also read map layers in other users' MAPSETs,
  68. but s/he can modify or remove only the map layers in his/her own
  69. MAPSET.
  70. <p>
  71. You can learn more about mapsets and how to seamlessly access maps
  72. found in another MAPSET of the same LOCATION in the
  73. <a href="g.mapsets.html">g.mapsets</a> documentation.
  74. <h3>The role of the "PERMANENT" LOCATION</h3>
  75. When creating a new LOCATION, GRASS automatically creates a special
  76. MAPSET called PERMANENT where the core data for the project can be
  77. stored. Data in the PERMANENT MAPSET can only be added, modified or
  78. removed by the owner of the PERMANENT MAPSET; however, they can be
  79. accessed, analyzed, and copied into their own MAPSET by the other
  80. users. The PERMANENT MAPSET is useful for providing general spatial
  81. data (e.g. an elevation model), accessible but write-protected to all
  82. users who are working in the same LOCATION as the database owner.
  83. To manipulate or add data to PERMANENT, the owner would start
  84. GRASS and choose the relevant LOCATION and the PERMANENT MAPSET. This
  85. mapset also contains the DEFAULT_WIND file, which holds the default
  86. region boundary coordinate values for the location (which all users
  87. will inherit when they start using the database). Additionally, in
  88. all mapsets a WIND file is kept, for storing the current boundary
  89. coordinate values and the currently selected raster resolution. Users
  90. have the option of switching back to the default region at any time.
  91. <h2>3. Creating a GRASS Database with Sample Data</h2>
  92. To create the GRASS database:
  93. <ol>
  94. <li> Find a place on your disk where you have write access and that
  95. has enough disk space to hold your spatial data.</li>
  96. <li> Create a subdirectory that will hold the general GRASS database
  97. (e.g. using a file manager or with <tt>mkdir /data/grassdata</tt> or
  98. <tt>mkdir /home/yourlogin/grassdata</tt>).</li>
  99. </ol>
  100. <p>
  101. Sample data such as the &quot;North Carolina&quot; or the
  102. &quot;Spearfish&quot; sample datasets may be downloaded from
  103. <a href="http://grass.osgeo.org/download/sample-data/">http://grass.osgeo.org/download/sample-data/</a>
  104. and the compressed data package(s) extracted into this new database
  105. directory.
  106. <p>
  107. Now you are ready to select a sample dataset in the GRASS GIS startup screen
  108. (see above) and start the session.
  109. <h2>4. Creating A New Location with the Location Wizard</h2>
  110. The <a href="wxGUI.html">wxGUI</a> graphical user interface provides a
  111. graphical "Location Wizard" which let's you easily create a
  112. new LOCATION for own data. You will be guided through a series of dialogues to
  113. browse and select predefined projections (also via EPSG code) or to
  114. define individual projections. The rules to define the resolution as
  115. described above also apply here.
  116. <p>
  117. <i>Hint: You can create new location easily from a georeferenced data file.
  118. In this case you are asked whether the data itself should be imported
  119. into the new location. The default region is then set to match imported map
  120. and the GRASS GIS session is opened.</i>
  121. <p>
  122. After defining new location, wxGUI starts automatically.
  123. If data were already imported, you can add them into the Layer Manager now
  124. and display them. If your location is empty you can import your data from
  125. the menu: Go to "File" -&gt; "Import raster/vector data" (see also the
  126. related Wiki page on <a href="http://grasswiki.osgeo.org/wiki/Importing_data">Importing data</a>).
  127. <h2>Further Reading</h2>
  128. Please have a look at the GRASS GIS web site for tutorials and books:
  129. <a href="http://grass.osgeo.org/documentation/">http://grass.osgeo.org/documentation/</a>.
  130. <h2>See also</h2>
  131. <em>
  132. <a href="index.html">GRASS GIS 7 Reference Manual</a>
  133. <br>
  134. <a href="grass7.html">GRASS GIS 7 startup program manual page</a>
  135. </em>
  136. <p>
  137. <i>Last changed: $Date$</i>