4.3 Labels, Annotation, and Graphic Text Compared
Key Takeaways
- ArcGIS Pro holds map text three ways: dynamic labels in layer properties, geodatabase annotation as a feature class, and graphic text inside the project file.
- An annotation feature class is one of the supported geodatabase dataset types, so recognizing it belongs to the Data Management objective on identifying supported ArcGIS data formats.
- Map reference scale is a map property: below it annotation and reference-scaled symbols grow with the map, above it they shrink, keeping text proportional to geometry.
- Standard annotation stands alone, while feature-linked annotation is bound to parent features through a geodatabase relationship class and follows their edits and deletions.
- The EAPF_2025 exam information guide places creating and editing annotation features on the ArcGIS Pro Associate exam, so study the distinctions here rather than the editing mechanics.
4.3 Labels, Annotation, and Graphic Text Compared
Sections 4.1 and 4.2 covered dynamic labels: text that ArcGIS Pro generates on the fly from an attribute field and places according to Maplex rules. Dynamic labels are not the only way text reaches a map, and telling the three mechanisms apart is a recurring Foundation-level question shape. A scenario describes a requirement — "the editor must be able to nudge one street name without changing any others", "the note must live in the geodatabase so a second analyst sees it", "the title only appears on the printed page" — and asks which text mechanism fits.
Scope note: The EAPF_2025 exam information guide lists "Create and edit annotation features" among the tasks beyond the qualified Foundation candidate; it is tested on the ArcGIS Pro Associate exam. This section therefore teaches recognition — what annotation is, where it is stored, and how it behaves — and deliberately stops short of the conversion and editing mechanics. Two published Foundation objectives do reach this material: "Identify supported ArcGIS data formats" (an annotation feature class is a geodatabase dataset type) and "Identify the use and impact of scale on map layers" (reference scale).
The Three Text Mechanisms
1. Dynamic Labels
Dynamic labels are a property of a layer, not data. The text string is read from a label field or label expression each time the map draws, and placement is recalculated by the Maplex engine at every zoom and pan. Nothing about a label is stored as a feature: turn labeling off and the text is simply gone.
- Change the underlying attribute and every affected label updates immediately.
- Placement is governed globally by label classes, priorities, and weights. You cannot drag one individual label to a better spot.
- Labels travel with the layer, so they survive in a layer file (
.lyrx), a layer package, and a published web layer.
2. Geodatabase Annotation
Annotation is stored data. An annotation feature class is a geodatabase dataset type in the same family as point, line, and polygon feature classes, and each annotation feature carries its own geometry, text string, font, point size, rotation angle, and optional leader line. Because the text is a feature, an editor can select it and move, rotate, or reword that one piece of text without touching any other.
The trade is automation for control. Annotation does not follow attribute changes on its own unless it is feature-linked, and it does not regenerate when new features are added. In the Catalog pane an annotation feature class shows its own distinctive icon, which is the recognition cue the Data Management objective is after.
3. Graphic Text
Graphics layers hold text (and shapes, lines, and callout boxes) as graphic elements stored inside the ArcGIS Pro project (.aprx) — either on a map's graphics layer or directly on a layout page. Graphic text is the right answer for a map title, a data-source credit, a north-arrow caption, or a one-off annotation on a single printed sheet. It is not in a geodatabase, so it cannot be shared as data, queried, or edited by a second analyst working from the same database.
Map Reference Scale
Reference scale is a property of the map, set on the Map Properties dialog (General tab) or the Map ribbon tab. It answers the question: at what scale is the text supposed to be exactly the size I specified?
With a reference scale of 1:24,000 and 10-point text:
| Current map scale | Relationship to reference scale | On-screen text size |
|---|---|---|
1:24,000 | equal | exactly 10 pt |
1:12,000 (zoomed in) | larger scale | grows above 10 pt |
1:48,000 (zoomed out) | smaller scale | shrinks below 10 pt |
Setting a reference scale makes text and symbols behave like part of the map — they scale with the geometry, so the ratio of text size to feature size never changes. Leaving reference scale unset (the default, <None>) keeps text at a fixed screen point size at every zoom level, which is usually what you want for interactive browsing and usually wrong for a printed sheet.
Reference scale applies to annotation and to reference-scaled symbology; it is separate from the scale visibility ranges covered in Section 3.4, which turn a layer on and off rather than resize it. Confusing the two is a classic distractor pair.
Standard vs. Feature-Linked Annotation
| Property | Standard (standalone) annotation | Feature-linked annotation |
|---|---|---|
| Storage | Annotation feature class | Annotation feature class |
| Bound to source features | No | Yes, through a geodatabase relationship class |
| Follows attribute edits | No | Yes, the text updates |
| Behavior when the parent feature is deleted | Survives as orphaned text | Deleted with the parent |
| Typical use | One-off cartographic text | Utility, parcel, and cadastral maps |
Feature-linked annotation requires a relationship class and, in ArcGIS Pro, an ArcGIS Desktop Standard or Advanced license — another reason the exam treats its creation as Associate-level material.
Choosing the Right Mechanism
| Requirement in the question stem | Correct mechanism |
|---|---|
| Text must update automatically when attributes change | Dynamic labels |
| Every road with the same name must be labeled consistently and automatically | Dynamic labels |
| One specific label must be nudged, rotated, or reworded individually | Geodatabase annotation |
| Text must live in the geodatabase and be editable by multiple users | Geodatabase annotation |
| Text must delete itself when its parent feature is deleted | Feature-linked annotation |
| A map title, credit line, or note that exists only on this project's layout | Graphic text |
Comparison at a Glance
| Property | Dynamic Labels | Geodatabase Annotation | Graphic Text |
|---|---|---|---|
| Where stored | Layer properties | Geodatabase feature class | Project file (.aprx) / layout |
| Is it data? | No | Yes | No |
| Individually editable | No | Yes | Yes |
| Updates with attribute edits | Yes | Only if feature-linked | No |
| Shareable to another database | With the layer | Yes, as a dataset | No |
| Governed by reference scale | Only if reference-scaled | Yes | No, fixed to page or screen |
Exam traps to watch for. Annotation is data, labels are a display property, and graphics belong to the project — every distractor in this family plays on one of those three lines. Reference scale resizes text; visibility range hides layers. And when a stem asks how to create annotation, remember that the Foundation blueprint does not go there; the question is testing whether you can recognize annotation, not build it.
What happens to text size when viewing Geodatabase Annotation that was created with a Reference Scale of 1:24,000, if the user zooms in to a map scale of 1:12,000?
Which of the following tasks does the EAPF_2025 exam information guide list as beyond the qualified ArcGIS Pro Foundation candidate?
Which text implementation method in ArcGIS Pro is stored directly within the map document (.aprx) rather than inside a geodatabase feature class, making it ideal for quick layout titles and non-spatial callouts?