The Labeling Summary dialog box presents a general overview of the labeling classes in the data frame for quality assurance and performance checks. It will point out potential problems with your labeling rules that may impact labeling performance, map readability, and the ability to convert labels to annotation. The summary report lists all the layers in the data frame and all the label classes with their properties in each of these layers. Each layer will have a minimum of one label class whether it is currently being labeled or not. Layers that can't be labeled, such as layers referencing raster data, are not listed. To access the Labeling Summary dialog box, click the Summary button on the Label Manager.
The labeling report contains a listing for each layer that provides an overview of the main properties for your label class. Information presented in red text should be checked as it is reporting either an error that is preventing labels from being displayed or an issue that will cause decreased performance in your map labeling. The following items are checked for the report and may be listed for each layer.
- Is the label class turned on or off?
Labeled class—The label class is checked.
Disabled class—The label class is unchecked.
Unlabeled class, but still active due to feature weight. Features will be added to the placement engine as background features—The label class is unchecked, but the labels are working as barriers to other labels being placed due to the feature weight set for the label class.
- Is there an XY Offset applied to the symbol?
Symbol has an XY Offset defined. This is not supported by the placement engine—When placing labels, the placement engine uses the location of the symbol before the x,y offset is applied. This may result in overlapping labels or white spaces on the map once the x,y offset is applied.
- Is there a SQL query for the label class?
A subset of features will be added to the placement engine—Yes, there is a SQL query present for this label class, and only features that satisfy the query will be labeled.
SQL query not defined. All features will be added to the placement engine—No, there is no SQL query, and all labels will be considered for placement.
Identical SQL Query found. Duplicate features will be generated. See [label class name]—The SQL query for this label class is a duplicate of the query for the referenced label class. This will result in features being labeled multiple times. If different attributes are being used to create the label consider concatenating the fields into a label expression.
- Is there a scale range set for the label class?
A scale range has been entered—There has been a scale range set for the label class, and the labels will be displayed only between set scales. If there has been no scale range set, there will be no message.
Are there duplicate label class names?
Duplicate class name. Class names should be unique within a layer—Duplicate label class names exist within the same feature layer. It is recommended that you change one so that all names are unique.
- Is there an advanced labeling expression set?
Advanced label expression defined—There has been an advanced labeling expression created. This could be as simple as concatenating several fields into one label or more complicated and containing programming logic.
Label expression references a field that is not in the feature class. See [Field Name]—There is an error in the advanced labeling expression. Check the field name referenced in the error and change to one that is present in the attributes of the feature layer.
- Click the Label Manager button on the Labeling toolbar.
- Click the Summary button.