diff --git a/vector/v.build/v.build.html b/vector/v.build/v.build.html index c66da69110a..20fd726d44a 100644 --- a/vector/v.build/v.build.html +++ b/vector/v.build/v.build.html @@ -76,7 +76,8 @@

SEE ALSO

v.build.all, v.build.polylines, v.edit, -v.split +v.split, +v.support

See also wxGUI vector digitizer. diff --git a/vector/v.cluster/v.cluster.html b/vector/v.cluster/v.cluster.html index 235e9491b1e..fd70f1ebaa9 100644 --- a/vector/v.cluster/v.cluster.html +++ b/vector/v.cluster/v.cluster.html @@ -20,7 +20,9 @@

DESCRIPTION

distance or method=density if clusters should be created separately for each observed density (distance to the farthest neighbor). -

dbscan

+

Clustering methods

+ +

dbscan method

The Density-Based Spatial Clustering of Applications with Noise is a commonly used clustering algorithm. A new cluster is started for a point with at least @@ -29,12 +31,12 @@

dbscan

least min - 1 neighbors are within the maximum distance for each point already in the cluster. -

dbscan2

+

dbscan2 method

Similar to dbscan, but here it is sufficient if the resultant cluster consists of at least min points, even if no point in the cluster has at least min - 1 neighbors within distance. -

density

+

density method

This method creates clusters according to their point density. The maximum distance is not used. Instead, the points are sorted ascending by the distance to their farthest neighbor (core distance), inspecting @@ -44,7 +46,7 @@

density

own maximum distance. This method can identify clusters with different densities and can create nested clusters. -

optics

+

optics method

This method is Ordering Points to Identify the Clustering Structure. It is controlled by the number @@ -75,7 +77,7 @@

optics

cluster. The order of the input points is arbitrary and can thus influence the resultant clusters. -

optics2

+

optics2 method

EXPERIMENTAL This method is similar to OPTICS, minimizing the reachability of each point. Points are reconnected if their reachability can be reduced. Contrary to OPTICS, a cluster's seed is @@ -176,6 +178,7 @@

EXAMPLE

Generate random points for analysis (100 points per area), use different method for clustering and visualize using color stored the attribute table. + 
 # pick a subregion of the vector urbanarea
 g.region -p n=272950 s=188330 w=574720 e=703090 res=10
diff --git a/vector/v.colors/v.colors.html b/vector/v.colors/v.colors.html
index 440ed5763ec..4b75ceccbd2 100644
--- a/vector/v.colors/v.colors.html
+++ b/vector/v.colors/v.colors.html
@@ -145,7 +145,7 @@ 
SEE ALSO

 page Color
 tables (from GRASS User Wiki)
 
-
ColorBrewer is an online tool designed to
+
ColorBrewer is an online tool designed to
 help people select good color schemes for maps and other graphics.
 
 
AUTHORS

diff --git a/vector/v.delaunay/v.delaunay.html b/vector/v.delaunay/v.delaunay.html
index 2c8b8db4531..de033403816 100644
--- a/vector/v.delaunay/v.delaunay.html
+++ b/vector/v.delaunay/v.delaunay.html
@@ -30,6 +30,8 @@ 
SEE ALSO

 v.voronoi,
 v.hull
 
+

+Delaunay triangulation (Wikipedia)
 
 
AUTHORS

 
diff --git a/vector/v.external.out/v.external.out.html b/vector/v.external.out/v.external.out.html
index f9c3575aa88..ac49365244f 100644
--- a/vector/v.external.out/v.external.out.html
+++ b/vector/v.external.out/v.external.out.html
@@ -24,9 +24,9 @@ 
NOTES

 

 Creation options refer to the output format specified
 by format option. See the list of valid creation options
-at OGR formats
+at OGR formats
 specification page, example
-for ESRI
+for ESRI
 Shapefile
 or PostgreSQL/PostGIS
 format (section "Layer Creation Options"). Options are
@@ -67,7 +67,7 @@ 
PostgreSQL/PostGIS Creation Options

   default: topo
   
  • TOPO_TOLERANCE=<value> - tolerance for PostGIS
   Topology schema,
-  see CreateTopology
+  see CreateTopology
   function for defails, default: 0
    • 
   
  • TOPO_GEO_ONLY=YES|NO - store in PostGIS Topology schema
   only data relevant to Topo-Geo data model, default: NO
    • 
diff --git a/vector/v.external/v.external.html b/vector/v.external/v.external.html
index 200d3726363..1856e78d1a6 100644
--- a/vector/v.external/v.external.html
+++ b/vector/v.external/v.external.html
@@ -47,7 +47,7 @@ 
    Supported OGR vector formats
    For details see -GDAL web site. +GDAL web site.

    EXAMPLES

    @@ -142,7 +142,7 @@

    SEE ALSO

    GDAL Library
    -PostGIS +PostGIS

    See diff --git a/vector/v.in.ascii/v.in.ascii.html b/vector/v.in.ascii/v.in.ascii.html index cd1ab9c7cf1..c0e0490b580 100644 --- a/vector/v.in.ascii/v.in.ascii.html +++ b/vector/v.in.ascii/v.in.ascii.html @@ -280,7 +280,7 @@

    Example 8 - point format mode

    REFERENCES

    -SQL command notes for creating databases +SQL command notes for creating databases,
    GRASS ASCII vector format specification diff --git a/vector/v.in.lidar/v.in.lidar.html b/vector/v.in.lidar/v.in.lidar.html index 72177b9f5ed..3554767c83d 100644 --- a/vector/v.in.lidar/v.in.lidar.html +++ b/vector/v.in.lidar/v.in.lidar.html @@ -1,7 +1,7 @@

    DESCRIPTION

    v.in.lidar converts LiDAR point clouds in LAS format to a GRASS -vector, using the libLAS library. +vector, using the libLAS library. The created vector is true 3D with x, y, z coordinates.

    @@ -107,28 +107,28 @@

    EXAMPLE

    This example is analogous to the example used in the GRASS wiki page for importing LAS as vector points. -

    The sample LAS data are in the file "Serpent Mound Model LAS Data.las", +

    The sample LAS data are in the file "Serpent Mound Model LAS Data.laz", available at -appliedimagery.com +Serpent Mound Model LAS Data.laz 

       # print LAS file info
-  v.in.lidar -p input="Serpent Mound Model LAS Data.las"
+  v.in.lidar -p input="Serpent Mound Model LAS Data.laz"
 
   # create a project with CRS information of the LAS data
-  v.in.lidar -i input="Serpent Mound Model LAS Data.las" project=Serpent_Mound
+  v.in.lidar -i input="Serpent Mound Model LAS Data.laz" project=Serpent_Mound
 
   # quit and restart GRASS in the newly created project "Serpent_Mound"
   # real import of LiDAR LAS data, without topology and without attribute table
-  v.in.lidar -tb input="Serpent Mound Model LAS Data.las" output=Serpent_Mound_Model_pts
+  v.in.lidar -tb input="Serpent Mound Model LAS Data.laz" output=Serpent_Mound_Model_pts

    REFERENCES

    ASPRS LAS format
    -LAS library
    -LAS library C API documentation +LAS library
    +LAS library C API documentation

    SEE ALSO

    diff --git a/vector/v.in.ogr/v.in.ogr.html b/vector/v.in.ogr/v.in.ogr.html index 2ab3ca938a6..d35fb7a315b 100644 --- a/vector/v.in.ogr/v.in.ogr.html +++ b/vector/v.in.ogr/v.in.ogr.html @@ -23,11 +23,11 @@

    Supported Vector Formats

    v.in.ogr uses the OGR library which supports various vector data formats including -ESRI Shapefile, -Mapinfo File, UK .NTF, +ESRI Shapefile, +Mapinfo File, UK .NTF, SDTS, TIGER, IHO S-57 (ENC), DGN, GML, GPX, AVCBin, REC, Memory, OGDI, and PostgreSQL, depending on the local OGR installation. For details -see the OGR format overview. +see the OGR format overview. The -f prints a list of the vector formats supported by the system's OGR (Simple Features Library). The OGR (Simple Features Library) is part of the GDAL library, @@ -257,7 +257,7 @@

    PostGIS tables

    Generally, v.in.ogr just follows the -format-specific +format-specific syntax defined by the OGR library. @@ -301,7 +301,7 @@

    Default connection settings as datasource (PostgreSQL only)

    OpenStreetMap (OSM)

    -OSM data are available in +OSM data are available in .osm (XML based) and .pbf (optimized binary) formats. The .pbf format is recommended because file sizes are smaller. The OSM driver will categorize features into 5 layers : diff --git a/vector/v.in.pdal/v.in.pdal.html b/vector/v.in.pdal/v.in.pdal.html index 1042f8415bf..af1f941eb6d 100644 --- a/vector/v.in.pdal/v.in.pdal.html +++ b/vector/v.in.pdal/v.in.pdal.html @@ -27,7 +27,7 @@

    REFERENCES

    V. Petras, A. Petrasova, J. Jeziorska, H. Mitasova (2016): Processing UAV and lidar point clouds in GRASS GIS. XXIII ISPRS Congress 2016 - [ISPRS Archives, + [ISPRS Archives, ResearchGate] diff --git a/vector/v.lidar.correction/v.lidar.correction.html b/vector/v.lidar.correction/v.lidar.correction.html index 5e45edc02f6..29d1bab645d 100644 --- a/vector/v.lidar.correction/v.lidar.correction.html +++ b/vector/v.lidar.correction/v.lidar.correction.html @@ -90,7 +90,7 @@

    REFERENCES



    Performances of the filter can be seen in the -ISPRS WG III/3 Comparison of Filters +ISPRS WG III/3 Comparison of Filters report by Sithole, G. and Vosselman, G., 2003.

    SEE ALSO

    diff --git a/vector/v.lidar.edgedetection/v.lidar.edgedetection.html b/vector/v.lidar.edgedetection/v.lidar.edgedetection.html index 08fd672d266..77f0efe6e0b 100644 --- a/vector/v.lidar.edgedetection/v.lidar.edgedetection.html +++ b/vector/v.lidar.edgedetection/v.lidar.edgedetection.html @@ -142,7 +142,7 @@

    REFERENCES

  • Brovelli M. A., Cannata M. and Longoni U.M., 2002. DTM LIDAR in area urbana, Bollettino SIFET N.2, pp. 7-26.
  • Performances of the filter can be seen in the -ISPRS WG III/3 Comparison of Filters +ISPRS WG III/3 Comparison of Filters report by Sithole, G. and Vosselman, G., 2003.
    • diff --git a/vector/v.lidar.growing/v.lidar.growing.html b/vector/v.lidar.growing/v.lidar.growing.html index d98309eb59c..58c76c59fb2 100644 --- a/vector/v.lidar.growing/v.lidar.growing.html +++ b/vector/v.lidar.growing/v.lidar.growing.html @@ -68,7 +68,7 @@

    REFERENCES

    Bollettino SIFET N.2, pp. 7-26.

    Performances of the filter can be seen in the -ISPRS WG III/3 Comparison of Filters +ISPRS WG III/3 Comparison of Filters report by Sithole, G. and Vosselman, G., 2003.

    SEE ALSO

    diff --git a/vector/v.lrs/lrs.html b/vector/v.lrs/lrs.html index edc517788cd..8286efd2f7d 100644 --- a/vector/v.lrs/lrs.html +++ b/vector/v.lrs/lrs.html @@ -167,14 +167,16 @@

    NOTES

    SEE ALSO

    -R. Blazek, 2004, Introducing the Linear Reference System in GRASS, Bangkok, GRASS User Conf. Proc.
    -R. Blazek, 2005, Introducing the Linear Reference System in GRASS, International Journal of Geoinformatics, Vol. 1(3), pp. 95-100
    +R. Blazek, 2004, Introducing the Linear Reference System in GRASS, Bangkok, GRASS User Conf. Proc.
    +R. Blazek, 2005, Introducing the Linear Reference System in GRASS, International Journal of Geoinformatics, Vol. 1(3), pp. 95-100

    -v.build.polylines, -v.lrs.create, -v.lrs.segment, -v.lrs.where, -v.lrs.label + +v.build.polylines, +v.lrs.create, +v.lrs.segment, +v.lrs.where, +v.lrs.label +

    AUTHORS

    diff --git a/vector/v.lrs/v.lrs.create/v.lrs.create.html b/vector/v.lrs/v.lrs.create/v.lrs.create.html index 518bb80fedf..266345d651d 100644 --- a/vector/v.lrs/v.lrs.create/v.lrs.create.html +++ b/vector/v.lrs/v.lrs.create/v.lrs.create.html @@ -150,7 +150,7 @@

    SEE ALSO

    LRS tutorial,
    -Introducing the Linear Reference System in GRASS +Introducing the Linear Reference System in GRASS

    AUTHORS

    diff --git a/vector/v.lrs/v.lrs.label/v.lrs.label.html b/vector/v.lrs/v.lrs.label/v.lrs.label.html index dbd2f64ac67..faed971ab15 100644 --- a/vector/v.lrs/v.lrs.label/v.lrs.label.html +++ b/vector/v.lrs/v.lrs.label/v.lrs.label.html @@ -33,7 +33,7 @@

    SEE ALSO

    LRS tutorial,
    -Introducing the Linear Reference System in GRASS +Introducing the Linear Reference System in GRASS

    AUTHORS

    diff --git a/vector/v.lrs/v.lrs.segment/v.lrs.segment.html b/vector/v.lrs/v.lrs.segment/v.lrs.segment.html index 0a2b39dfd1f..b2438e2a88b 100644 --- a/vector/v.lrs/v.lrs.segment/v.lrs.segment.html +++ b/vector/v.lrs/v.lrs.segment/v.lrs.segment.html @@ -56,7 +56,7 @@

    SEE ALSO

    LRS tutorial,
    -Introducing the Linear Reference System in GRASS +Introducing the Linear Reference System in GRASS

    AUTHOR

    diff --git a/vector/v.lrs/v.lrs.where/v.lrs.where.html b/vector/v.lrs/v.lrs.where/v.lrs.where.html index cdf9651f389..962ed0b9b2a 100644 --- a/vector/v.lrs/v.lrs.where/v.lrs.where.html +++ b/vector/v.lrs/v.lrs.where/v.lrs.where.html @@ -45,7 +45,7 @@

    SEE ALSO

    LRS tutorial,
    -Introducing the Linear Reference System in GRASS +Introducing the Linear Reference System in GRASS

    AUTHORS

    diff --git a/vector/v.out.lidar/v.out.lidar.html b/vector/v.out.lidar/v.out.lidar.html index 2d0708d98ae..295812480e0 100644 --- a/vector/v.out.lidar/v.out.lidar.html +++ b/vector/v.out.lidar/v.out.lidar.html @@ -1,7 +1,7 @@

    DESCRIPTION

    v.out.lidar converts GRASS vector map to a LiDAR point clouds -in LAS format using the libLAS library. +in LAS format using the libLAS library.

    The -r flag limits the export to the current computational region @@ -20,7 +20,7 @@

    NOTES

    The typical file extensions for the LAS format are .las and .laz (compressed). The compressed LAS (.laz) format can be exported only if libLAS has been -compiled with LASzip support. +compiled with LASzip support. It is also good when libLAS was compiled with GDAL. This is needed when working with projections. @@ -39,7 +39,7 @@

    REFERENCES

    ASPRS LAS format
    -LAS library
    +LAS library

    SEE ALSO

    diff --git a/vector/v.out.ogr/v.out.ogr.html b/vector/v.out.ogr/v.out.ogr.html index 664a5c35a1a..8373d114687 100644 --- a/vector/v.out.ogr/v.out.ogr.html +++ b/vector/v.out.ogr/v.out.ogr.html @@ -14,13 +14,13 @@

    DESCRIPTION

    @@ -29,7 +29,7 @@

    DESCRIPTION

    For further available other supported formats go -here. +here.

    NOTES

    diff --git a/vector/v.out.postgis/v.out.postgis.html b/vector/v.out.postgis/v.out.postgis.html index 2307ce6a394..423702e7f89 100644 --- a/vector/v.out.postgis/v.out.postgis.html +++ b/vector/v.out.postgis/v.out.postgis.html @@ -6,10 +6,10 @@

    DESCRIPTION

    By default GRASS GIS topological features are converted into simple features -(see OGC Simple +(see OGC Simple Feature Access specification for details). Flag -l allows to export vector features as topological elements stored -in PostGIS +in PostGIS Topology schema. Note that topological export requires PostGIS version 2 or later. @@ -38,7 +38,7 @@

    DESCRIPTION

    default: topo
  • TOPO_TOLERANCE=<value> - tolerance for PostGIS Topology schema, - see CreateTopology + see CreateTopology function for details, default: 0
  • TOPO_GEO_ONLY=YES|NO - store in PostGIS Topology schema only data relevant to Topo-Geo data model, @@ -95,7 +95,7 @@

    NOTES

    v.out.postgis also allows exporting vector features as topological elements -in PostGIS +in PostGIS Topology schema. PostGIS Topology extension uses three tables to store basic topological elements which forms topological objects like areas or isles in GRASS terminology. Nodes (0-dimensional @@ -233,7 +233,7 @@

    Export topological data

    By default v.out.postgis exports data as simple features. Flag -l allows exporting data as topological elements instead of simple features. Export topological elements is stored in -PostGIS +PostGIS Topology schema. 
    @@ -264,8 +264,8 @@ 
    REQUIREMENTS
    
 
    REFERENCES
    
 
 
 
diff --git a/vector/v.proj/v.proj.html b/vector/v.proj/v.proj.html
index 9910b7258b4..8e96d796a6d 100644
--- a/vector/v.proj/v.proj.html
+++ b/vector/v.proj/v.proj.html
@@ -79,7 +79,7 @@ 
    REFERENCES
    
   
  •  ASPRS Grids and Datum
    • 
   
  •  Projections Transform List (PROJ)
    • 
   
  •  Coordinate operations by PROJ (projections, conversions, transformations, pipeline operator)
    • 
-  
  •  MapRef -
+  
  •  MapRef -
       The Collection of Map Projections and Reference Systems for Europe
    • 
   
  •  Information and Service System for European Coordinate Reference Systems - CRS
    • 
 
diff --git a/vector/v.support/v.support.html b/vector/v.support/v.support.html
index 1c81680e1ef..565c4fbfe63 100644
--- a/vector/v.support/v.support.html
+++ b/vector/v.support/v.support.html
@@ -1,6 +1,8 @@
 
    DESCRIPTION
    
 
-v.support is used to set/update vector map metadata.
+v.support is used to set/update vector map metadata. While GRASS
+GIS typically generates these metadata entries automatically, v.support
+allows users to manually edit them when necessary.
 
 
    EXAMPLE
    
 
diff --git a/vector/v.to.rast3/v.to.rast3.html b/vector/v.to.rast3/v.to.rast3.html
index 14bfb0eada0..42a50851491 100644
--- a/vector/v.to.rast3/v.to.rast3.html
+++ b/vector/v.to.rast3/v.to.rast3.html
@@ -14,7 +14,7 @@ 
    NOTES
    
 
    
 
    
 
    
-This screenshot shows the result of the v.to.rast3 test. Visualized
+Fig: This screenshot shows the result of the v.to.rast3 test. Visualized
 are the cube of the GRASS region, the vector points as black dots and
 the voxel cells as wireframe model. Only cells with non-null values are
 shown.
diff --git a/vector/v.voronoi/v.voronoi.html b/vector/v.voronoi/v.voronoi.html
index c058a0587fd..fa79d1507a8 100644
--- a/vector/v.voronoi/v.voronoi.html
+++ b/vector/v.voronoi/v.voronoi.html
@@ -91,6 +91,8 @@ 
    SEE ALSO
    
 v.delaunay,
 v.hull
 
+
    
+Voronoi diagram (Wikipedia)
 
 
    AUTHORS