helptext.html 8.8 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200
  1. <!-- meta page description: GRASS Quickstart -->
  2. <h2>Geographic Resources Analysis Support System</h2>
  3. Commonly referred to as GRASS, this is a Geographic Information System
  4. (GIS) used for geospatial data management and analysis, image
  5. processing, graphics/map production, spatial modelling, and
  6. visualization. GRASS is currently used in academic and commercial
  7. settings around the world, as well as by many governmental agencies
  8. and environmental consulting companies.
  9. <h2>1. Startup of GRASS GIS</h2>
  10. <center>
  11. <img src="grass_start.png" alt="[GRASS start screen]">
  12. </center>
  13. <h3><img src="circle_1.png" alt="[(1)]">&nbsp;Selecting the GIS Database directory</h3>
  14. GRASS data are stored in a directory referred to as DATABASE
  15. (also called "GISDBASE"). This directory has to be created
  16. with a file manager or the <tt>mkdir</tt> command, before starting to work
  17. with GRASS. Within this DATABASE, the projects are organized
  18. by project areas stored in subdirectories called LOCATIONs.
  19. <h3><img src="circle_2.png" alt="[(2)]">&nbsp;Selecting the LOCATION (a project)</h3>
  20. A LOCATION is defined by its coordinate system, map projection and
  21. geographical boundaries. The subdirectories and files defining a
  22. LOCATION are created automatically when GRASS is started the first
  23. time with a new LOCATION. It is important to understand that each
  24. projection stays in its own LOCATION.
  25. <p>See <img src="circle_4.png" alt="[(4)]">&nbsp; the "Location Wizard" to
  26. easily create a new LOCATION from scratch from a geocoded file, by
  27. defining the parameters or by selecting the corresponding EPSG projection
  28. code.
  29. <h3><img src="circle_3.png" alt="[(3)]">&nbsp;Selecting the MAPSET (a subproject)</h3>
  30. Each LOCATION can have many MAPSETs. Each MAPSET is a LOCATION's
  31. subdirectory. New MAPSET can be added at GRASS startup (see related
  32. button).
  33. <h3><img src="circle_4.png" alt="[(4)]">&nbsp;Location Wizard</h3>
  34. The "Location Wizard" let's you easily create a new LOCATION. You
  35. will be guided through a series of dialogues to browse and select
  36. predefined projections (also via EPSG code) or to define individual
  37. projections. Find below some rules to define the default raster
  38. resolution for a new LOCATION.
  39. <h3><img src="circle_5.png" alt="[(5)]">&nbsp;Start GRASS</h3>
  40. Once you have selected an existing LOCATION/MAPSET or defined a new
  41. one, you can enter GRASS. The graphical user interface
  42. <a href="wxGUI.html">wxGUI</a> will open and provide you with a
  43. menu system, map visualization tool, digitizer, and more.
  44. <h2>2. Background GRASS Location structure</h2>
  45. <center>
  46. <img src="help_loc_struct.png" alt="[GRASS Location structure]"><br>
  47. <i>Fig. 1: GRASS Location structure</i>
  48. </center>
  49. <p>
  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. <h3>Creating and maintaining MAPSETs</h3>
  56. One motivation to maintain different MAPSETs is to store maps
  57. related to project issues or subregions. Another motivation is to
  58. support simultaneous access of several users to the map layers
  59. stored within the same LOCATION, i.e. teams working on the same
  60. project. For teams a centralized GRASS DATABASE would be defined
  61. in a network file system (e.g. NFS). Besides access to his/her own
  62. MAPSET, each user can also read map layers in other users' MAPSETs,
  63. but s/he can modify or remove only the map layers in his/her own
  64. MAPSET.
  65. <p>You can learn more about mapsets and how to seamlessly access maps
  66. found in another MAPSET of the same LOCATION in the
  67. <a href="g.mapsets.html">g.mapsets</a> documentation.
  68. <h3>The role of the "PERMANENT" LOCATION</h3>
  69. When creating a new LOCATION, GRASS automatically creates a special
  70. MAPSET called PERMANENT where the core data for the project can be
  71. stored. Data in the PERMANENT MAPSET can only be added, modified or
  72. removed by the owner of the PERMANENT MAPSET; however, they can be
  73. accessed, analyzed, and copied into their own MAPSET by the other
  74. users. The PERMANENT MAPSET is useful for providing general spatial
  75. data (e.g. an elevation model), accessible but write-protected to all
  76. users who are working in the same LOCATION as the database owner.
  77. To manipulate or add data to PERMANENT, the owner would start
  78. GRASS and choose the relevant LOCATION and the PERMANENT MAPSET. This
  79. mapset also contains the DEFAULT_WIND file, which holds the default
  80. region boundary coordinate values for the location (which all users
  81. will inherit when they start using the database). Additionally, in
  82. all mapsets a WIND file is kept, for storing the current boundary
  83. coordinate values and the currently selected raster resolution. Users
  84. have the option of switching back to the default region at any time.
  85. <h2>3. Creating a GRASS database with sample data</h2>
  86. To create the GRASS database:
  87. <ol>
  88. <li> Find a place on your disk where you have write access and that
  89. has enough diskspace to hold your spatial data.</LI>
  90. <li> Create a subdirectory that will hold the general GRASS database
  91. (e.g. using a file manager or with <tt>mkdir /data/grassdata</tt> or
  92. <tt>mkdir /home/yourlogin/grassdata</tt>).</LI>
  93. </ol>
  94. <p>Sample data such as the "Spearfish" or the "North Carolina" sample datasets
  95. may be downloaded from
  96. <a href="http://grass.osgeo.org/download/data.php">http://grass.osgeo.org/download/data.php</a>
  97. and placed in this new database directory.
  98. <p>
  99. <h3>A) Create New Location with wxGUI</h3>
  100. The <a href="wxGUI.html">wxGUI</a> graphical user interface provides a
  101. graphical "Location Wizard" instead which let's you easily create a
  102. new LOCATION. You will be guided through a series of dialogues to
  103. browse and select predefined projections (also via EPSG code) or to
  104. define individual projections. The rules to define the resolution as
  105. described above also apply here.
  106. <h3>B) Create New Location with text screen</h3>
  107. Click on the "Create New Location" button, which will take you to a
  108. text screen on which you can enter a new location name, and then
  109. continue by pressing "ESC"-"RETURN" - i.e. press (NOT hold) the ESC key,
  110. and then press the RETURN key on your keyboard.
  111. <p>Next you will need to assign parameters to the location such
  112. as the coordinate system and datum you want to use, the project area's
  113. boundary coordinates, and the default resolution for raster data:
  114. <UL>
  115. <li> Start by chosing between, X,Y, Latitude-Longitude, UTM, or
  116. "other" coordinate system. This choice depends on your data and the
  117. use you will make of it.</LI>
  118. <li> You are then prompted for a single line of text describing the
  119. project area, for example "Topo Map of the Alps".</LI>
  120. </UL>
  121. <p>Next you are requested for some more information about the projection.
  122. Note that the prompts vary from projection to projection, an example follows:
  123. <UL>
  124. <li> (if you chose "D - Other Projection") "specify projection name":
  125. "list" gives you the list of all available projections, examples are
  126. "tmerc" for Transverse Mercator, "lcc" for Lambert Conformal Conic,
  127. "moll" for Mollweide, etc.
  128. <li> specify datum name: again use "list" to get a list of available
  129. datums, examples are "wgs84", "nad27", "eur79", etc.
  130. <li> Enter Central Parallel: 0 if you want the Equator as the
  131. central parallel
  132. <li> Enter Central Meridian: 0 if you want the Greenwich meridian as
  133. central meridian
  134. <li> Enter Scale Factor at the Central Meridian
  135. <li> Enter plural form of map units: for example, meters
  136. </UL>
  137. <p>The next step is the description of the project area's boundary coordinates
  138. and the definition of the default raster resolution:
  139. <p>The default raster resolution (GRID RESOLUTION) has to be chosen
  140. according to your needs. Generally, it is advisable to work in steps of
  141. 0.25 (0.25, 0.5, 1.75, 2.00, 12.25 etc.). This resolution does not
  142. concern vector and site data since these are stored with their exact
  143. coordinate values. Note that every raster map may have its own
  144. resolution. You can leave this screen with "ESC"-"RETURN" and then
  145. if everything is correct accept the list of parameters that appears.
  146. <p>You will then be back to the startup screen to enter the mapset's
  147. name (if not already entered). Another "ESC"-"RETURN" will finally
  148. let you leave this screen. This mapset is created within the new
  149. location by answering "yes" to the next question. The mapset will
  150. use the parameters of the location (such as the region and resolution
  151. definitions) as its default parameters.
  152. <p>Now the project area, i.e. the location including a mapset, has been
  153. created. You have "arrived" in the GRASS system and can start working
  154. within this new location.
  155. <h2>Further Reading</h2>
  156. Please have a look at the GRASS web site for tutorials and books:
  157. <a href="http://grass.osgeo.org/gdp/index.php">http://grass.osgeo.org/gdp/index.php</a>.
  158. <h2>See also</h2>
  159. <em>
  160. <a href="grass7.html">GRASS startup program</a>
  161. </em>
  162. <p>
  163. <i>Last changed: $Date$</i>