Detect Graphic Conflict (Cartography) (ArcInfo only)

Usage tips

• The tool works on feature representations only, not feature geometries. The input and conflict feature layers must contain representations; otherwise, the tool will not execute.

• The conflict calculation is based on a reference scale. If you access this tool from ArcMap, the reference scale of the data frame containing the input layers will be used, unless an explicit reference scale has been set in the Cartography Settings under the ArcToolbox Environment Settings. If you access the tool from ArcCatalog, a reference scale must be specified in the Cartography Settings under the ArcToolbox Environment Settings, otherwise the tool will not execute. Learn how to specify environment settings.

• The output feature class stores polygons, each representing an area of graphic conflict between an input representation and a conflict representation. The feature IDs associated to the two conflicting representations are stored with the conflict polygon in the FID_input_representation and FID_conflict_representation fields. If no graphic conflicts are found, the output feature class will be empty.

• Many mapping specifications include a required minimum spacing between certain types of features. Set the conflict distance to this value to detect any areas where representations are closer than this minimum distance. Temporary buffers one-half the size of the conflict distance value are created around feature representation graphics in both the input and conflict layers. Conflict polygons will be generated where buffers overlap. When the conflict distance is zero, no buffers are made, and just the representation footprints are used to detect conflicts.

• The line connection allowance is the radius of a circle, centered where lines join, within which graphic overlaps won't be detected. This parameter is only considered when the input layer and the conflict layer are identical, and contain line representations. Otherwise, this value is ignored when the tool is executed. This is useful if you use end caps to ensure that lines connect visually, but you don't want each instance detected as a conflict. The default value is 1 point. Use a value that is at least one-half the line-width of your line representation symbols to have these connection conflicts skipped. A value of zero means no allowance, and will detect a conflict at each line join in this case.

• You can use the stored feature ObjectIDs to locate conflicting representations. Conflicts can be resolved by reshaping or moving feature representations using the representation editing tools. The output polygons can be used as visual guides while you are editing. Learn about editing feature representations.

• The following environment settings affect this tool: referenceScale, cartographicCoordinateSystem.

Command line syntax
An overview of the Command Line window
DetectGraphicConflict_cartography <in_features> <conflict_features> <out_feature_class> {conflict_distance} {line_connection_allowance}

Command line example

DetectGraphicConflict_cartography c:\workspace.mdb\roads.lyr railroads.lyr ConflictPoly "2 Points"

Scripting syntax
About getting started with writing geoprocessing scripts
DetectGraphicConflict_cartography (in_features, conflict_features, out_feature_class, conflict_distance, line_connection_allowance)

Script example

import arcgisscripting
gp = arcgisscripting.create()

gp.workspace = "c:\Workspace.mdb"
gp.toolbox = "cartography"
gp.DetectGraphicConflict ("roads.lyr", "railroads.lyr", "ConflictPoly", "2 Points")