helptext.html 7.8 KB

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