Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: v.buffer.html minor edits #4744

Merged
merged 1 commit into from
Nov 25, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 10 additions & 9 deletions vector/v.buffer/v.buffer.html
Original file line number Diff line number Diff line change
Expand Up @@ -10,12 +10,13 @@ <h2>NOTES</h2>

Internal buffers for areas can be generated with negative distance
values ("inward buffer" or "negative buffer" or "shrinking").

<p>
<em>v.buffer</em> fusions the geometries of buffers by default.
Categories and attribute table will not be transferred (this would
not make sense as one buffer geometry can be the result of many
different input geometries). To transfer the categories and
attributes the user can set the <b>t</b> flag. This will result in
attributes the user can set the <b>-t</b> flag. This will result in
buffers being cut up where buffers of individual input geometries
overlap. Each part that is the result of overlapping buffers of
multiple geometries will have multiple categories corresponding to
Expand All @@ -29,11 +30,11 @@ <h2>NOTES</h2>
the GEOS library.

<p>
<i>For advanced users:</i> built-in buffer algorithm no longer
desired, we use GEOS: If GRASS is not compiled with GEOS support
or <a href="variables.html">environmental
<i>For advanced users:</i> the built-in buffer algorithm is no longer
used, as we use GEOS instead. If GRASS was not compiled with GEOS support
or the <a href="variables.html">environmental
variable</a> <tt>GRASS_VECTOR_BUFFER</tt> is defined, then GRASS
generates buffers using built-in buffering algorithm (which is still
generates buffers using the built-in buffering algorithm (which is still
buggy for some input data).

<p>
Expand All @@ -56,17 +57,17 @@ <h3>Corner settings</h3>
<img src="v_buffer_line.png">
</center>

Straight corners with caps are created by <b>-s</b> flag (red color on
the figure below), while <b>-c</b> flag doesn't make caps at the ends of
Straight corners with caps are created using the <b>-s</b> flag (red color on
the figure below), while the <b>-c</b> flag doesn't make caps at the ends of
polylines (green color on the figure below):

<center>
<img src="v_buffer_line_s.png">
<img src="v_buffer_line_c.png">
</center>

Using <b>-s</b> with a point vector map as input data, square buffers are
created instead of round buffers.
With a point vector map as input data, square buffers are created instead
of round buffers by using the <b>-s</b> flag.

<center>
<img src="v_buffer_point_s.png">
Expand Down
Loading