v0.2.54..v0.2.55 changeset SnapUnconnectedWays.asciidoc
Garret Voltz edited this page Aug 14, 2020
·
1 revision
diff --git a/docs/user/SnapUnconnectedWays.asciidoc b/docs/user/SnapUnconnectedWays.asciidoc
index cbaa40e..3efe828 100644
--- a/docs/user/SnapUnconnectedWays.asciidoc
+++ b/docs/user/SnapUnconnectedWays.asciidoc
@@ -2,10 +2,10 @@
[[SnapUnconnectedWays]]
== Snap Unconnected Ways
-If you merely want to snap unconnected linear features (e.g. roads) within a single dataset or in two different datasets back to neighboring
-linear features without actually conflating them, Hootenanny allows for that.
+If you want to snap unconnected linear features (e.g. roads) within a single dataset or in two different datasets back to neighboring linear
+features without running full conflation, Hootenanny allows for that.
-example:
+basic example:
--------------
# Snap unconnected roads in the second dataset back to neighboring roads in the first dataset
@@ -17,4 +17,18 @@ hoot convert -D convert.ops="hoot::UnconnectedWaySnapper" \
input1.osm input2.osm output.osm
-------------
+See additional examples in the "Command Line Examples" section of the User Documentation.
+
+=== Reviewing
+
+The +snap.unconnected.ways.review.snapped.ways+ option can be enabled to flag any snapped way for review. This allows you to manually correct
+any poorly snapped ways.
+
+The +snap.unconnected.ways.mark.only+ option bypasses way snapping completely, and when used in conjunction with the
++snap.unconnected.ways.review.snapped.ways+ option, marks any ways that would have been snapped withthe current configuration as needing review. This allows you to have complete manual control over way snapping.
+
+=== Configuration
+
+See the snap.unconnected.ways.* configuration options for more information on customization.
+