Select to view content in your preferred language

MOVE A LABEL FOR PLACEMENT

872
6
05-18-2011 11:29 AM
Status: Already Offered
Labels (1)
garyleunis
Occasional Contributor

LABELS THAT CAN BE PLACED (OR ANNOTATION THAT HAS THE FLEXABILITY OF A LABEL).
SPECIFACLY FOR POINTS, BEING ABLE TO STORE AN xy FOR A LABLE PLACEMENT WOULD BE HELPFUL.

6 Comments
CameronWallace
Make points from your annotation class... or live with the labels associated with your features... why do you need to try and muddle the difference between Annotation and Labels?
Marie_Ducharme

I usually convert my labels to graphics, which allows better placement without hassle. I love graphic labels. Just right click on your layer in the Table of Contents pane, and  choose Convert Labels, Convert Lables to Graphics.  

Marie_Ducharme_0-1666116984034.png

 

WendyHarrison
Status changed to: Already Offered

Feature-linked annotation will give you annotation that updates when updates are made to the base feature.

https://pro.arcgis.com/en/pro-app/latest/help/data/annotation/annotation.htm

RoseF
by

As @WendyHarrison mentioned, feature linked annotation is very powerful. And once you have the annotation feature class, you can edit it -- move labels around, change symbology, etc -- as if it was a graphic label.

wayfaringrob

@WendyHarrison  that's not really a perfect solution since feature-linked annotation is required to live in the same .gdb as the layer, which is rarely desirable. If I have a project with labels that is reading data from a source location that is used in many projects, the last thing I want to do is start sticking annotation feature classes in that location or make needless and confusing copies of the data. I don't think the idea being requested is 'already offered.'

RoseF
by

@wayfaringrobI think I'm misunderstanding the idea -- isn't the question whether or not a label will auto-update according to the feature attributes? If this is the case, I would think it would be best to keep the annotation feature class near/with/in the same GDB as the original feature class. I'm sure I'm missing something so please correct me!