vector: various updates

vector/v.build/v.build.html

@@ -76,7 +76,8 @@ <h2>SEE ALSO</h2>
 <a href="v.build.all.html">v.build.all</a>,
 <a href="v.build.polylines.html">v.build.polylines</a>,
 <a href="v.edit.html">v.edit</a>,
-<a href="v.split.html">v.split</a>
+<a href="v.split.html">v.split</a>,
+<a href="v.support.html">v.support</a>
 </em>
 
 <p>See also <em><a href="wxGUI.vdigit.html">wxGUI vector digitizer</a></em>.

vector/v.cluster/v.cluster.html

@@ -20,7 +20,9 @@ <h2>DESCRIPTION</h2>
 <b>distance</b> or <b>method=density</b> if clusters should be created
 separately for each observed density (distance to the farthest neighbor).
 
-<h4>dbscan</h4>
+<h3>Clustering methods</h3>
+
+<h4>dbscan method</h4>
 The <a href="https://en.wikipedia.org/wiki/DBSCAN">Density-Based Spatial
 Clustering of Applications with Noise</a> is a commonly used clustering
 algorithm. A new cluster is started for a point with at least
@@ -29,12 +31,12 @@ <h4>dbscan</h4>
 least <i>min</i> - 1 neighbors are within the maximum distance for each
 point already in the cluster.
 
-<h4>dbscan2</h4>
+<h4>dbscan2 method</h4>
 Similar to <i>dbscan</i>, but here it is sufficient if the resultant
 cluster consists of at least <b>min</b> points, even if no point in the
 cluster has at least <i>min - 1</i> neighbors within <b>distance</b>.
 
-<h4>density</h4>
+<h4>density method</h4>
 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 @@ <h4>density</h4>
 own maximum distance. This method can identify clusters with different
 densities and can create nested clusters.
 
-<h4>optics</h4>
+<h4>optics method</h4>
 This method is
 <a href="https://en.wikipedia.org/wiki/OPTICS_algorithm">Ordering Points to
 Identify the Clustering Structure</a>. It is controlled by the number
@@ -75,7 +77,7 @@ <h4>optics</h4>
 cluster. The order of the input points is arbitrary and can thus
 influence the resultant clusters.
 
-<h4>optics2</h4>
+<h4>optics2 method</h4>
 <b>EXPERIMENTAL</b> 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 @@ <h2>EXAMPLE</h2>
 
 Generate random points for analysis (100 points per area), use different
 method for clustering and visualize using color stored the attribute table.
+
 <div class="code"><pre>
 # pick a subregion of the vector urbanarea
 g.region -p n=272950 s=188330 w=574720 e=703090 res=10

vector/v.colors/v.colors.html

@@ -145,7 +145,7 @@ <h2>SEE ALSO</h2>
 page <a href="https://grasswiki.osgeo.org/wiki/Color_tables">Color
 tables</a> (from GRASS User Wiki)
 
-<p><a href="http://colorbrewer.org">ColorBrewer</a> is an online tool designed to
+<p><a href="https://colorbrewer2.org">ColorBrewer</a> is an online tool designed to
 help people select good color schemes for maps and other graphics.
 
 <h2>AUTHORS</h2>

vector/v.delaunay/v.delaunay.html

@@ -30,6 +30,8 @@ <h2>SEE ALSO</h2>
 <a href="v.voronoi.html">v.voronoi</a>,
 <a href="v.hull.html">v.hull</a>
 </em>
+<p>
+<a href="https://en.wikipedia.org/wiki/Delaunay_triangulation">Delaunay triangulation (Wikipedia)</a>
 
 <h2>AUTHORS</h2>
 

vector/v.external.out/v.external.out.html

@@ -24,9 +24,9 @@ <h2>NOTES</h2>
 <p>
 Creation <b>options</b> refer to the output format specified
 by <b>format</b> option. See the list of valid creation options
-at <a href="https://gdal.org/drivers/vector/">OGR formats
+at <a href="https://gdal.org/en/stable/drivers/vector/">OGR formats
 specification page</a>, example
-for <a href="https://gdal.org/drv_shapefile.html">ESRI
+for <a href="https://gdal.org/en/stable/drivers/vector/shapefile.html">ESRI
 Shapefile</a>
 or <a href="https://gdal.org/drv_pg.html">PostgreSQL/PostGIS</a>
 format (section &quot;Layer Creation Options&quot;). Options are
@@ -67,7 +67,7 @@ <h3>PostgreSQL/PostGIS Creation Options</h3>
   default: <tt>topo</tt></li>
   <li><tt>TOPO_TOLERANCE=&lt;value&gt;</tt> - tolerance for PostGIS
   Topology schema,
-  see <a href="http://www.postgis.net/docs/manual-2.0/CreateTopology.html">CreateTopology</a>
+  see <a href="https://postgis.net/docs/manual-2.0/CreateTopology.html">CreateTopology</a>
   function for defails, default: <tt>0</tt></li>
   <li><tt>TOPO_GEO_ONLY=YES|NO</tt> - store in PostGIS Topology schema
   only data relevant to Topo-Geo data model, default: <tt>NO</tt></li>

vector/v.external/v.external.html

@@ -47,7 +47,7 @@ <h3>Supported OGR vector formats</h3>
 </pre></div>
 
 For details see
-<a href="https://gdal.org/drivers/vector/">GDAL web site</a>.
+<a href="https://gdal.org/en/stable/drivers/vector/">GDAL web site</a>.
 
 <h2>EXAMPLES</h2>
 
@@ -142,7 +142,7 @@ <h2>SEE ALSO</h2>
 <p>
 <a href="https://gdal.org/">GDAL Library</a>
 <br>
-<a href="http://postgis.org/">PostGIS</a>
+<a href="https://postgis.net/">PostGIS</a>
 
 <p>
 See

vector/v.in.ascii/v.in.ascii.html

@@ -280,7 +280,7 @@ <h3>Example 8 - point format mode</h3>
 
 <h2>REFERENCES</h2>
 
-<a href="sql.html">SQL command notes</a> for creating databases
+<a href="sql.html">SQL command notes</a> for creating databases,
 <br>
 <a href="vectorascii.html">GRASS ASCII vector format</a> specification
 

vector/v.in.lidar/v.in.lidar.html

@@ -1,7 +1,7 @@
 <h2>DESCRIPTION</h2>
 
 <em>v.in.lidar</em> converts LiDAR point clouds in LAS format to a GRASS
-vector, using the <a href="http://www.liblas.org">libLAS</a> library.
+vector, using the <a href="https://liblas.org">libLAS</a> library.
 The created vector is true 3D with x, y, z coordinates.
 
 <p>
@@ -107,28 +107,28 @@ <h2>EXAMPLE</h2>
 
 This example is analogous to the example used in the GRASS wiki page for
 <a href="https://grasswiki.osgeo.org/wiki/LIDAR#Import_LAS_as_vector_points">importing LAS as vector points</a>.
-<p>The sample LAS data are in the file "Serpent Mound Model LAS Data.las",
+<p>The sample LAS data are in the file "Serpent Mound Model LAS Data.laz",
 available at
-<a href="http://www.appliedimagery.com/downloads/sampledata/Serpent%20Mound%20Model%20LAS%20Data.las">appliedimagery.com</a>
+<a href="https://github.com/PDAL/data/raw/refs/heads/master/liblas/Serpent%20Mound%20Model%20LAS%20Data.laz">Serpent Mound Model LAS Data.laz</a>
 
 <div class="code"><pre>
   # 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
 </pre></div>
 
 <h2>REFERENCES</h2>
 
 <a href="https://www.asprs.org/committee-general/laser-las-file-format-exchange-activities.html">
 ASPRS LAS format</a><br>
-<a href="http://www.liblas.org/">LAS library</a> <br>
-<a href="http://test.liblas.org/doxygen/liblas_8h.htm">LAS library C API</a> documentation
+<a href="https://liblas.org/">LAS library</a> <br>
+<a href="https://liblas.org/doxygen/liblas_8h.html">LAS library C API</a> documentation
 
 <h2>SEE ALSO</h2>
 

vector/v.in.ogr/v.in.ogr.html

@@ -23,11 +23,11 @@ <h3>Supported Vector Formats</h3>
 
 <em>v.in.ogr</em> uses the OGR library which supports various vector
 data formats including
-<a href="https://gdal.org/drivers/vector/shapefile.html">ESRI Shapefile</a>,
-<a href="https://gdal.org/drivers/vector/mitab.html">Mapinfo File</a>, UK .NTF,
+<a href="https://gdal.org/en/stable/drivers/vector/shapefile.html">ESRI Shapefile</a>,
+<a href="https://gdal.org/en/stable/drivers/vector/mitab.html">Mapinfo File</a>, 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 <a href="https://gdal.org/drivers/vector/">OGR format overview</a>.
+see the <a href="https://gdal.org/en/stable/drivers/vector/">OGR format overview</a>.
 The <b>-f</b> 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 <a href="https://gdal.org">GDAL</a> library,
@@ -257,7 +257,7 @@ <h3>PostGIS tables</h3>
 </pre></div>
 
 Generally, <em>v.in.ogr</em> just follows the
-<a href="https://gdal.org/drivers/vector/">format-specific</a>
+<a href="https://gdal.org/en/stable/drivers/vector/">format-specific</a>
 syntax defined by the OGR library.
 
 
@@ -301,7 +301,7 @@ <h3>Default connection settings as datasource (PostgreSQL only)</h3>
 
 <h3>OpenStreetMap (OSM)</h3>
 
-<a href="https://gdal.org/drivers/vector/osm.html">OSM data</a> are available in
+<a href="https://gdal.org/en/stable/drivers/vector/osm.html">OSM data</a> 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 :

vector/v.in.pdal/v.in.pdal.html

@@ -27,7 +27,7 @@ <h2>REFERENCES</h2>
     V. Petras, A. Petrasova, J. Jeziorska, H. Mitasova (2016):
     <em>Processing UAV and lidar point clouds in GRASS GIS</em>.
     XXIII ISPRS Congress 2016
-    [<a href="http://www.int-arch-photogramm-remote-sens-spatial-inf-sci.net/XLI-B7/945/2016/">ISPRS Archives</a>,
+    [<a href="https://isprs-archives.copernicus.org/articles/XLI-B7/945/2016/">ISPRS Archives</a>,
     <a href="https://www.researchgate.net/publication/304340172_Processing_UAV_and_lidar_point_clouds_in_GRASS_GIS">ResearchGate</a>]</li>
 </ul>
 

vector/v.lidar.correction/v.lidar.correction.html

@@ -90,7 +90,7 @@ <h2>REFERENCES</h2>
 <br>
 <br>
 Performances of the filter can be seen in the
-<a href="http://www.itc.nl/isprswgIII-3/filtertest/MainDoc.htm">ISPRS WG III/3 Comparison of Filters</a>
+<a href="https://www.itc.nl/isprs/wgIII-3/filtertest/">ISPRS WG III/3 Comparison of Filters</a>
 report by Sithole, G. and Vosselman, G., 2003.
 
 <h2>SEE ALSO</h2>

vector/v.lidar.edgedetection/v.lidar.edgedetection.html

@@ -142,7 +142,7 @@ <h2>REFERENCES</h2>
 <li>Brovelli M. A., Cannata M. and Longoni U.M., 2002. DTM LIDAR in area urbana,
 Bollettino SIFET N.2, pp. 7-26.</li>
 <li>Performances of the filter can be seen in the
-<a href="http://www.itc.nl/isprswgIII-3/filtertest/MainDoc.htm">ISPRS WG III/3 Comparison of Filters</a>
+<a href="https://www.itc.nl/isprs/wgIII-3/filtertest/">ISPRS WG III/3 Comparison of Filters</a>
 report by Sithole, G. and Vosselman, G., 2003.</li>
 </ul>
 

vector/v.lidar.growing/v.lidar.growing.html

@@ -68,7 +68,7 @@ <h2>REFERENCES</h2>
 Bollettino SIFET N.2, pp. 7-26.
 <p>
 Performances of the filter can be seen in the
-<a href="http://www.itc.nl/isprswgIII-3/filtertest/MainDoc.htm">ISPRS WG III/3 Comparison of Filters</a>
+<a href="https://www.itc.nl/isprs/wgIII-3/filtertest/">ISPRS WG III/3 Comparison of Filters</a>
 report by Sithole, G. and Vosselman, G., 2003.
 
 <h2>SEE ALSO</h2>

vector/v.lrs/lrs.html

@@ -167,14 +167,16 @@ <h2>NOTES</h2>
 
 <h2>SEE ALSO</h2>
 
-<em>R. Blazek, 2004, <a href="http://gisws.media.osaka-cu.ac.jp/grass04/viewpaper.php?id=50">Introducing the Linear Reference System in GRASS</a>, Bangkok, GRASS User Conf. Proc.</em><br>
-<em>R. Blazek, 2005, <a href="http://creativecity.gscc.osaka-cu.ac.jp/IJG/article/download/320/321">Introducing the Linear Reference System in GRASS</a>, International Journal of Geoinformatics, Vol. 1(3), pp. 95-100</em><br>
+<em>R. Blazek, 2004, <a href="https://web.archive.org/web/20070301130303/http://gisws.media.osaka-cu.ac.jp/grass04/viewpaper.php?id=50">Introducing the Linear Reference System in GRASS</a>, Bangkok, GRASS User Conf. Proc.</em><br>
+<em>R. Blazek, 2005, <a href="https://web.archive.org/web/20240814152234/http://creativecity.gscc.osaka-cu.ac.jp/IJG/article/download/320/321">Introducing the Linear Reference System in GRASS</a>, International Journal of Geoinformatics, Vol. 1(3), pp. 95-100</em><br>
 <p>
-<em><a href="v.build.polylines.html">v.build.polylines</a></em>,
-<em><a href="v.lrs.create.html">v.lrs.create</a></em>,
-<em><a href="v.lrs.segment.html">v.lrs.segment</a></em>,
-<em><a href="v.lrs.where.html">v.lrs.where</a></em>,
-<em><a href="v.lrs.label.html">v.lrs.label</a></em>
+<em>
+<a href="v.build.polylines.html">v.build.polylines</a>,
+<a href="v.lrs.create.html">v.lrs.create</a>,
+<a href="v.lrs.segment.html">v.lrs.segment</a>,
+<a href="v.lrs.where.html">v.lrs.where</a>,
+<a href="v.lrs.label.html">v.lrs.label</a>
+</em>
 
 <h2>AUTHORS</h2>
 

vector/v.lrs/v.lrs.create/v.lrs.create.html

@@ -150,7 +150,7 @@ <h2>SEE ALSO</h2>
 <p>
 <em>
 <a href="lrs.html">LRS tutorial</a>,<br>
-<a href="http://gisws.media.osaka-cu.ac.jp/grass04/viewpaper.php?id=50">Introducing the Linear Reference System in GRASS</a>
+<a href="https://web.archive.org/web/20070301130303/http://gisws.media.osaka-cu.ac.jp/grass04/viewpaper.php?id=50">Introducing the Linear Reference System in GRASS</a>
 </em>
 
 <h2>AUTHORS</h2>

vector/v.lrs/v.lrs.label/v.lrs.label.html

@@ -33,7 +33,7 @@ <h2>SEE ALSO</h2>
 <p>
 <em>
 <a href="lrs.html">LRS tutorial</a>,<br>
-<a href="http://gisws.media.osaka-cu.ac.jp/grass04/viewpaper.php?id=50">Introducing the Linear Reference System in GRASS</a>
+<a href="https://web.archive.org/web/20070301130303/http://gisws.media.osaka-cu.ac.jp/grass04/viewpaper.php?id=50">Introducing the Linear Reference System in GRASS</a>
 </em>
 
 <h2>AUTHORS</h2>

vector/v.lrs/v.lrs.segment/v.lrs.segment.html

@@ -56,7 +56,7 @@ <h2>SEE ALSO</h2>
 <p>
 <em>
 <a href="lrs.html">LRS tutorial</a>,<br>
-<a href="http://gisws.media.osaka-cu.ac.jp/grass04/viewpaper.php?id=50">Introducing the Linear Reference System in GRASS</a>
+<a href="https://web.archive.org/web/20070301130303/http://gisws.media.osaka-cu.ac.jp/grass04/viewpaper.php?id=50">Introducing the Linear Reference System in GRASS</a>
 </em>
 
 <h2>AUTHOR</h2>

vector/v.lrs/v.lrs.where/v.lrs.where.html

@@ -45,7 +45,7 @@ <h2>SEE ALSO</h2>
 <p>
 <em>
 <a href="lrs.html">LRS tutorial</a>,<br>
-<a href="http://gisws.media.osaka-cu.ac.jp/grass04/viewpaper.php?id=50">Introducing the Linear Reference System in GRASS</a>
+<a href="https://web.archive.org/web/20070301130303/http://gisws.media.osaka-cu.ac.jp/grass04/viewpaper.php?id=50">Introducing the Linear Reference System in GRASS</a>
 </em>
 
 <h2>AUTHORS</h2>

vector/v.out.lidar/v.out.lidar.html

@@ -1,7 +1,7 @@
 <h2>DESCRIPTION</h2>
 
 <em>v.out.lidar</em> converts GRASS vector map to a LiDAR point clouds
-in LAS format using the <a href="http://www.liblas.org">libLAS</a> library.
+in LAS format using the <a href="https://liblas.org">libLAS</a> library.
 
 <p>
 The <b>-r</b> flag limits the export to the current computational region
@@ -20,7 +20,7 @@ <h2>NOTES</h2>
 
 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 <a href="http://www.laszip.org/">LASzip</a> support.
+compiled with <a href="https://laszip.org/">LASzip</a> support.
 It is also good when libLAS was compiled with GDAL. This is needed when
 working with projections.
 
@@ -39,7 +39,7 @@ <h2>REFERENCES</h2>
 
 <a href="https://www.asprs.org/committee-general/laser-las-file-format-exchange-activities.html">
 ASPRS LAS format</a><br>
-<a href="http://www.liblas.org/">LAS library</a> <br>
+<a href="https://liblas.org/">LAS library</a> <br>
 
 <h2>SEE ALSO</h2>
 

vector/v.out.ogr/v.out.ogr.html

@@ -14,13 +14,13 @@ <h2>DESCRIPTION</h2>
 
 <ul>
   <li><a href="https://gdal.org/drv_geopackage.html">OGC GeoPackage</a></li>
-  <li><a href="https://gdal.org/drv_shapefile.html">ESRI Shapefile</a></li>
+  <li><a href="https://gdal.org/en/stable/drivers/vector/shapefile.html">ESRI Shapefile</a></li>
   <li><a href="https://gdal.org/drv_pg.html">PostGIS</a></li>
   <li><a href="https://gdal.org/drv_sqlite.html">SpatiaLite</a></li>
-  <li><a href="https://gdal.org/drv_csv.html">CSV</a></li>
+  <li><a href="https://gdal.org/en/stable/drivers/vector/csv.html">CSV</a></li>
   <li><a href="https://gdal.org/drv_gml.html">GML</a></li>
   <li><a href="https://gdal.org/drv_kml.html">KML</a></li>
-  <li><a href="https://gdal.org/drv_mitab.html">Mapinfo File</a></li>
+  <li><a href="https://gdal.org/en/stable/drivers/vector/mitab.html">Mapinfo File</a></li>
   <li><a href="https://gdal.org/drv_tiger.html">TIGER</a></li>
   <li>... and many others</li>
 </ul>
@@ -29,7 +29,7 @@ <h2>DESCRIPTION</h2>
 
 <p>
 For further available other supported formats go
-<a href="https://gdal.org/drivers/vector/">here</a>.
+<a href="https://gdal.org/en/stable/drivers/vector/">here</a>.
 
 <h2>NOTES</h2>