v0.2.53..v0.2.54 changeset OldDocs.asciidoc

diff --git a/docs/user/OldDocs.asciidoc b/docs/user/OldDocs.asciidoc
index 8f4745e..c3e95f0 100644
--- a/docs/user/OldDocs.asciidoc
+++ b/docs/user/OldDocs.asciidoc
@@ -178,7 +178,6 @@ are listed the possible solutions where Hootenanny may request a manual review f
 | MultiLineString relations can only contain ways when matching sublines. | A input being conflated of geometry type multiline string contained an OSM feature type other than a way (nodes or relations). | Review this feature manually. This is invalid input data for Hootenanny conflation purposes and cannot be conflated automatically.
 | Multiple overlapping way matches were found within one set of ways. | When attempting to conflate sublines from line inputs, multiple overlapping lines were found. | TODO
 | No valid matching subline found. | When conflating two linear inputs, Hootenanny could not find a corresponding matching subline part in one of the inputs. | Review this feature manually, as Hootenanny can not determine automatically whether it matches any feature in the opposite input dataset.
-| When matching sublines expected a multilinestring relation not a <osm feature type>. | When conflating linear features, Hootenanny expects all relations to be of the type multilinestring. | Review this feature manually. This is invalid input data for Hootenanny conflation purposes and cannot be conflated.
 |======
 
 [[RailwayConflation]]
@@ -201,6 +200,32 @@ this conflation.
 Railway Conflation can further be customized with the railway.* configuration options. See the "Configuration Options" section of User Guide 
 for more detail.
 
+[[ConflationFeatureAccuracyHandling]]
+== Conflation Feature Accuracy Handling
+
+Feature accuracy is measure of the confidence in how accurately a feature's geospatial coordinates are. Feature accuracy values affect the
+accuracy of conflated output data. Feature circular error (accuracy) can be processed in one of two ways: 1) on a feature by feature basis manually or 2) use Hootenanny's default value to assign it to all features. 
+
+For 1), you can manually assign the  either the `circular:error` or `accuracy` tag with your CE value to individual features and Hootenanny will read in the values.
+
+For 2), the default Hootenanny CE value is 15m and is controlled by the `circular.error.default.value` config option. If your feature data has neither the `circular:error` or `accuracy` tags present, hoot will use that value for all features. If you wanted to change the global CE value used for a conflate job to 5.0m, for example, you could do something like this for a conflate job:
+
+`hoot conflate -D conflate.pre.ops++="hoot::SetTagValueVisitor" -D set.tag.value.visitor.keys="error:circular" -D set.tag.value.visitor.values=5.0 input1.osm input2.osm out.osm`
+
+That will assign a CE of 5m to all features just before they are conflated.
+
+If you just wanted to update your data with CE tags without conflating, you could just do something like:
+
+`hoot convert -D convert.ops="hoot::SetTagValueVisitor"  -D set.tag.value.visitor.keys="error:circular" -D set.tag.value.visitor.values=5.0 -D writer.include.circular.error.tags=true input.osm out.osm`
+
+You can also strictly control the search radius of the conflation routines if you don't want to use CE tags, which may be useful if you're not confident in your CE values and don't want to modify the data. The `search.radius.*` configuration options allow for controlling the conflate search radius. For example, if you wanted to conflate all features with a search radius of 25m:
+
+`hoot conflate -D search.radius=25 input1.osm input2.osm out.osm`
+
+Or if you just wanted to conflate buildings at a 25m radius:
+
+`hoot conflate -D search.radius.building=25 -D match.creators="hoot::BuildingMatchCreator" -D merger.creators="hoot::BuildingMergerCreator" input1.osm input2.osm out.osm`
+
 [[Translation]]
 == Translation