Merge Divided Roads

Summary

Generates single-line road features in place of matched pairs of divided road lanes.

Matched pairs of roads or lanes are merged if they are the same road class, trend generally parallel to one another, and are within the merge distance apart. The road class is specified by the Merge Field parameter. All nonmerged roads from the input collection are copied to the output feature class.

Learn more about how Merge Divided Roads works

Tip:

This tool is generally used to simplify a relatively large-scale road collection at a smaller scale, where it is appropriate to depict divided highways and boulevards as a single line. At medium scales, it may be preferable to retain divided roads as separate features. In this case, you can use the Resolve Road Conflicts tool instead to ensure that symbolized lanes are displayed without symbol conflicts. If both Resolve Road Conflicts and Merge Divided Roads tools will be run on the same collection of roads, it is advisable to run Merge Divided Roads first.

Caution:

A warning is raised if the input features are not in a projected coordinate system. This tool relies on linear distance units, which will create unexpected results in an unprojected coordinate system. It is strongly suggested that you run this tool on data in a projected coordinate system to ensure valid results. An error is raised and the tool will not process if the coordinate system is missing or unknown.

Illustration

The Merge Divided Roads tool creates single-line road features in place of divided roads.

Usage

• The output feature class contains single line features representing merged roads and copies of all unmerged input features. Merged features will inherit the attribution from one of the two input features.

• Input features with Merge Field parameter values equal to zero are "locked" and will not be merged, even if adjacent features are not locked.

• The optional Output Displacement Feature Class parameter creates a feature class of polygons that indicates the amount and direction of displacement that took place. This feature class can be used for visual inspection, for spatial querying, or as an input to the Propagate Displacement tool.

• If the input is a feature layer drawn with a representation, any shape overrides associated with the representation will be used as the input geometry considered by this tool, and the corresponding geometry in the Shape field will be ignored. The output feature class will contain the feature class representation, but all geometry will be stored in the output Shape field, not as representation shape overrides.

• Processing a large road dataset may exceed memory limitations. In this case, consider processing input data by partition by identifying a relevant polygon feature class in the Partition Features environment setting. Portions of the data, defined by partition boundaries, will be processed sequentially. The resulting feature classes will be seamless and consistent at partition edges. See How Merge Divided Roads works for more information about running this tool with partitioning.

Syntax

MergeDividedRoads_cartography (in_features, merge_field, merge_distance, out_features, {out_displacement_features})

Parameter	Explanation	Data Type
in_features	The input linear road features that contain matched pairs of divided road lanes that should be merged together to a single output line feature.	Feature Layer
merge_field	The field that contains road classification information. Only parallel, proximate roads of equal classification will be merged. A value of 0 (zero) locks a feature to prevent it from participating in merging.	Field
merge_distance	The minimum distance apart, in the specified units, for equal-class, relatively parallel road features to be merged. This distance must be greater than zero. If the units are in pt, mm, cm, or in, the value is considered as page units and takes into account the reference scale.	Linear unit
out_features	The output feature class containing single-line merged road features and all unmerged road features.	Feature Class
out_displacement_features (Optional)	The output polygon features containing the degree and direction of road displacement, to be used by the Propagate Displacement tool to preserve spatial relationships.	Feature Class

Code Sample

MergeDividedRoads tool example (Python Window)

The following Python window script demonstrates how to use the MergeDividedRoads tool in immediate mode.

import arcpy
from arcpy import env
env.workspace = "C:/data"
env.referenceScale = "50000"
arcpy.MergeDividedRoads_cartography("roads.lyr", "level", "25 meters",
                                      "C:/data/cartography.gdb/transportation/merged_roads",
                                      "C:/data/cartography.gdb/transportation/displacement")

MergeDividedRoads tool example (stand-alone Python script)

This stand-alone script shows an example of using the MergeDividedRoads tool.

# Name: MergeDividedRoads_standalone_script.py
# Description: Resolves symbology conflicts between roads within a specified distance of each other by snapping them together
# Author: ESRI
 
# Import system modules
import arcpy
from arcpy import env

# Set environment settings
env.workspace = "C:/data"
env.referenceScale = "50000"

# Set local variables
in_features = "roads.lyr"
merge_field = "level"
collapse_distance = "25 meters"
out_features = "C:/data/cartography.gdb/transportation/merged_roads"
out_displacement_features = "C:/data/cartography.gdb/transportation/displacement"

# Execute Merge Divided Roads
arcpy.MergeDividedRoads_cartography(in_features, merge_field, collapse_distance, out_features, out_displacement_features)

Environments

• Cartographic Coordinate System
• Reference Scale

  Note:

  The reference scale is only considered when the Merge Distance parameter is entered in page units. When the reference scale is available, the detection of false dead ends is based on feature separation of 0.5 mm at scale. Otherwise, a value twice the tolerance of the spatial reference is used.

• Cartographic Partitions

Licensing Information

• ArcGIS for Desktop Basic: No
• ArcGIS for Desktop Standard: No
• ArcGIS for Desktop Advanced: Yes

Feedback on this topic?