GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together. Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community. Already on GitHub? Sign in to your account. Click the Edit Properties button on the Coordinate Conversion pane.
|Published (Last):||18 January 2016|
|PDF File Size:||10.31 Mb|
|ePub File Size:||4.88 Mb|
|Price:||Free* [*Free Regsitration Required]|
Label weights and feature weights are used to assign relative importance to labels and features. This weight is to be used only when there is a conflict, that is, an overlap between a label and a feature. Ultimately, the final positioning of labels on your map is dependent on label and feature weights.
In addition, when working with weights, keep in mind that when you allow labels to overlap some features, generally, more labels will be placed on your map because ArcMap has more room to place them. All of the label classes in the currently active data frame are listed on the Label Weight Ranking dialog box.
Each is listed with the feature layer name, then a dash, and then the label class name. Also listed, because they can act as barriers to label placement, are all of the annotation layers and annotation groups in the currently active data frame.
Both are listed by name. Labels can have a weight of Low, Medium, or High. Features can have a weight of None, Low, Medium, or High. The general rule is that a feature cannot be overlapped by a label with an equal or lesser weight.
By default, features have a label weight of High. In general, you should give more important labels higher label weights. By default, features have a feature weight of None for label classes and High for annotation layers and annotation groups because typically you do not want labels placed on top of annotation text.
Increasing the weight of features will increase the processing time ArcMap needs to place labels. Setting a feature weight of high for point or line features ensures that no labels will be placed on top of these features. Setting a feature weight of high for polygon features ensures that no labels will be placed on the outline of these features.
Do this by increasing feature weight to High. Forces ArcMap to consider alternate positions for labels. Do this by increasing feature weight to Low or Medium. Prevents some labels from being placed on top of some features. Do this by increasing some feature weights and decreasing some label weights. By default, ArcMap automatically resolves conflicts between labels and does not allow them to overlap. You can change this behavior by confirming the layer or label class is at the top of the Label Priority List , has a label weight of High, and has Place Overlapping Labels checked when using the Standard Label Engine and Never Remove checked when using the Maplex Label Engine.
Annotation and graphics properties are accessible by choosing Annotation and Graphics from the list at the bottom of the dialog box. Arc GIS Desktop. Click the Label Weight Ranking button on the Labeling toolbar. Click the label or feature weight you want to change and click the desired weight from the drop-down list. Click OK. Related topics Working with the Standard Label Engine.
ArcMap Tips and Tricks: The 7 Golden Rules
The ArcMap export framework allows developers and third party companies to create and register custom export objects for use within the Export Map dialog box. If the custom export object has defects that cause it to crash, the entire ArcMap application may crash or disappear without warning. Some custom extensions have been known to consistently cause the problem. Versions 3. Uninstall any custom export extensions and try opening the Export Map dialog box again.
Weighting labels and features
Following are some common errors that may occur during editing. When ArcMap encounters problems starting an edit session on the data you chose, a dialog box appears providing additional information. You can receive errors, warnings, or information messages. This error occurs when a coordinate of a feature is beyond the extent of the feature class domain. It can happen when you are creating a new feature or editing the coordinates of an existing one.