helptext.html 9.5 KB

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