123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960 |
- <h2>DESCRIPTION</h2>
- A user may access data stored under the other mapsets listed in their
- mapset search path. However, the user may only modify data stored
- under their own current mapset. <em>g.copy</em> allows the user to copy
- existing data files <b>from</b> other mapsets <b>to</b> the user's
- current mapset ($MAPSET). The files to be copied must exist in the
- user's current mapset search path and location; output is sent to the
- relevant data element directory(ies) under the user's current mapset.
- <h2>EXAMPLES</h2>
- If the user wished to copy the existing raster
- file <em>soils</em> to a file called <em>soils.ph</em> and
- to copy an existing vector map <em>roads</em> to a file
- called <em>rds.old</em>, the user could type:
- <div class="code"><pre>
- g.copy raster=soils,soils.ph
- g.copy vector=roads,rds.old
- # or even combined:
- g.copy raster=soils,soils.ph vector=roads,rds.old
- </pre></div>
- <p>
- Data files can also be specified by their mapsets. For
- example, the below command copies the raster map named
- <em>soils</em> from the mapset <em>wilson</em> to a new
- file called <em>soils</em> to be placed under the user's
- current mapset:
- <div class="code"><pre>
- g.copy raster=soils@wilson,soils
- </pre></div>
- If no mapset name is specified, <em>g.copy</em> searches for the
- named <b>from</b> map in each of the mapset directories listed in the
- user's current mapset search path in the order in which mapsets are
- listed there (see <em><a href="g.mapsets.html">g.mapsets</a></em>).
- <h2>SEE ALSO</h2>
- <em>
- <a href="g.access.html">g.access</a>,
- <a href="g.list.html">g.list</a>,
- <a href="g.mapsets.html">g.mapsets</a>,
- <a href="g.remove.html">g.remove</a>,
- <a href="g.rename.html">g.rename</a>
- </em>
- <h2>AUTHOR</h2>
- Michael Shapiro,
- U.S. Army Construction Engineering
- Research Laboratory
- <p>
- <i>Last changed: $Date$</i>
|