Changeset 29461


Ignore:
Timestamp:
Dec 17, 2007, 5:45:01 AM (17 years ago)
Author:
neteler
Message:

terminology fix (merge from HEAD)

Location:
grass/branches/releasebranch_6_3/vector
Files:
4 edited

Legend:

Unmodified
Added
Removed

  • grass/branches/releasebranch_6_3/vector/v.lrs/lrs.html

    r24810 r29461  
    22<html>
    33<head>
    4  <title>LRS (Linear Reference System)</title>
     4 <title>LRS (Linear Referencing System)</title>
    55 <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
    66 <meta name="Author" content="Radim Blazek">
    … …  
    1111<img src="grass_logo.png" alt="_\|/_ GRASS logo"><hr align=center size=6 noshade>
    1212
    13 <h2>LRS (Linear Reference System)</h2>
    14 A Linear Reference System (LRS, also called Linear Referencing System) is a system
     13<h2>LRS (Linear Referencing System)</h2>
     14A Linear Referencing System (LRS) is a system
    1515where features (points or segments) are localized by a measure along a linear element.
    1616The LRS can be used to reference events for any network of linear
    … …  
    127127<h3>Available commands</h3>
    128128<ul>
    129 <li><a href="v.lrs.create.html">v.lrs.create</a> to create a linear reference system,
     129<li><a href="v.lrs.create.html">v.lrs.create</a> to create a linear referencing system,
    130130<li><a href="v.lrs.label.html">v.lrs.label</a> to create stationing on the LRS,
    131131<li><a href="v.lrs.segment.html">v.lrs.segment</a> to create points/segments on LRS,
    132132 and
    133133<li><a href="v.lrs.where.html">v.lrs.where</a> to find line id and real km+offset
    134 for given points in vector map using linear reference system.
     134for given points in vector map using linear referencing system.
    135135</ul>
    136136
    … …  
    171171<li>player: vector layer in point map (usually 1; see <a HREF="vectorintro.html">vectorintro</a>
    172172    for "layer" concept)
    173 <li>rsdriver: Driver name for reference system table - DBMI SQL driver (dbf, pg, mysql, sqlite, etc)
    174 <li>rsdatabase: Database name for reference system table - DBMI SQL database name (e.g., "lrsdb")
    175 <li>rstable: Name of the reference system table - DBMI SQL table name (e.g., "streamslrs")
     173<li>rsdriver: Driver name for LRS table - DBMI SQL driver (dbf, pg, mysql, sqlite, etc)
     174<li>rsdatabase: Database name for LRS table - DBMI SQL database name (e.g., "lrsdb")
     175<li>rstable: Name of the LRS table - DBMI SQL table name (e.g., "streamslrs")
    176176</ul>
    177177

  • grass/branches/releasebranch_6_3/vector/v.net/description.html

    r24538 r29461  
    1010If vector editing is required to modify the graph, <em>v.digit</em>
    1111or <em>v.edit</em> can be used. Separately,
    12 <a HREF="lrs.html">Linear Reference System</a> is available
     12<a HREF="lrs.html">Linear Referencing System</a> is available
    1313in GRASS.
    1414

  • grass/branches/releasebranch_6_3/vector/v.segment/description.html

    r23718 r29461  
    114114
    115115<em>
    116 <a href="lrs.html">LRS tutorial</a> (Linear Reference System),<BR>
     116<a href="lrs.html">LRS tutorial</a> (Linear Referencing System),<BR>
    117117<a href="d.vect.html">d.vect</a>,
    118118<a href="v.build.polylines.html">v.build.polylines</a>,

  • grass/branches/releasebranch_6_3/vector/vectorintro.html

    r24890 r29461  
    266266to assign attribute columns to the forward and backward direction.
    267267
    268 <h3>Vector networks: Linear reference system (LRS)</h3>
     268<h3>Vector networks: Linear referencing system (LRS)</h3>
    269269
    270270LRS uses linear features and distance measured along those features to
    … …  
    292292<h3>Lidar data processing</h3>
    293293
    294 Lidar point clouds (first and last ping) are imported with <a
     294Lidar point clouds (first and last return) are imported with <a
    295295href="v.in.ascii.html">v.in.ascii</a> (-b flag to not build the
    296296topology). Outlier detection is done with
    297 <a href="v.outlier.html">v.outlier</a> on both first and last ping data.
     297<a href="v.outlier.html">v.outlier</a> on both first and last return data.
    298298Then, with <a href="v.lidar.edgedetection.html">v.lidar.edgedetection</a>,
    299 edges are detected from last ping data. The building are generated by
     299edges are detected from last return data. The building are generated by
    300300<a href="v.lidar.growing.html">v.lidar.growing</a> from detected
    301301edges.  The resulting data are post-processed with
    302302<a href="v.lidar.correction.html">v.lidar.correction</a>. Finally, the
    303303DTM and DSM are generated with <a href="v.surf.bspline.html">v.surf.bspline</a>
    304 (DTM: uses the 'v.lidar.correction' output; DSM: uses last ping output
     304(DTM: uses the 'v.lidar.correction' output; DSM: uses last return output
    305305from outlier detection).
    306306
Note: See TracChangeset for help on using the changeset viewer.