tiled labels to annotations

[MarcelSt-Germain]

Hi, In arcmap, when you convert labels to annotation in a project, the labels in the layers are deactivated.  When you do it with tiled labels to annotations with geoprocessing, the annotations are created but the layers stay in label mode.

So please, include the same functions in Pro or, at least, make multiple selection available for activating labelling on and off.  When you have 50+ of layers, it's time consuming to each time doing the label on each time.

By the way, can you sort the annotation in A to Z order not Z to A when inserting them in the maps.

[MarcelSt-Germain]

@WendyHarrison 

To answer your question short is because it's time saving and mostly reduce errors.

I think Esri think we only do simple tasks.  Making maps is a complex process.  Doing maps since arc view 3x, Esri make many moves.  Some nice, some a pain in.. for end user.  

For me I can have 45 layout linking to at least 13 maps in a simple project since I have many scale annotations and many sources.

So, to do that, I have templates with all the structure I need for labelling.  I check carefully to see if my layers who need labelling are all activated which take time.  You know, I have more than a few layers to check.  Just now, I have more than 15 in this map and 150 in the main one (easy to make mistakes). That can go up depending on projects.

In the process, I use my template to convert my label to annotations via geoprocessing.

Since I can do this process for the same template but with change in datasource, for now, in my project six sources to parse, having to reflag my labelling is stupid.  In arcmap its work seamlessly leaving my template ready for the next conversion.

Hope this clear.  

Was hoping to see Pro go improving not going back like each change in products improve some task but destroy others.  It takes decades to get Pro finally returning to project we have in arc view by example.

And now, the geoprocessing doesn't work anymore in 3.0.1 since database are empty.  

[MarcelSt-Germain]

Hum, forget to add that not adding to the map is also more time consuming. Since the conversion doesn’t group in the database by scale, having to select the scale we need between few hundred elements is not a choice.

[WendyHarrison]

ok - stepping away from the original question for a moment.

this statement:

"And now, the geoprocessing doesn't work anymore in 3.0.1 since database are empty. "

what are you seeing?  the tiled labels to annotation tool isn't working at 3.0.1?

[MarcelSt-Germain]

@WendyHarrison 

Not sure if it's for 3,0,1 or 3 since I don't remember which version I use the last time.  But it's sure it's wasn't the 3,0,1.

All things being equal in all my project since the availability of tiled labelling in arcmap, this time, all the annotations, in the database, are generated for each scale but, inside, no data.

Robert_LeClair told me to remove the update package but I can't find where to remove the package to return to 3,0.  In Pro, doesn't find a remove update and in window software pane, just one entry.

Hope to also return to the original question.. 

 

[WendyHarrison]

to get to the patch:

open control panel - 

click start and then type control panel > click enter

on the control panel click Programs and Features

on the dialog that opens, click View installed updates

you'll see the patch there and can uninstall it

[WendyHarrison]

I put 3.0.1 onto my machine and was unable to reproduce this issue of empty attribute tables.  Please contact Technical support and an analyst can look into it with you 

I'll get back to looking into your original request now

You can reach our Support Services department at 1-888-377-4575, Monday–Friday, 5:00 a.m.–5:00 p.m. PST, or http://support.esri.com/contact-tech-support.

If you are outside the U.S., use the link above to find the office that supports your country or region.

[WendyHarrison]

back to the original thread

This may be the piece of information that I wasn’t understanding.

"Since I can do this process for the same template but with change in datasource, for now, in my project six sources to parse, having to reflag my labelling is stupid.  In arcmap its work seamlessly leaving my template ready for the next conversion."

Are you converting the labels to annotation for one geographical location and then changing the template data source so that it looks at another geographical location?  And this is why the labels still being on isn’t an issue because there is no annotation in that area as it was converted for a completely different geographical location?

[MarcelSt-Germain]

Hi Wendy,

My layers point to data with scale dependency. To do a map, I point to one them or others depending on my need. I have to generate annotation for all cases. Remember I can have hundred layers in labelling to convert.

Here my current setup for a medium-size project. The project is located between two UTM zone (9 and 10) and are projected on Nad83. A total of 44 main maps and 15 close-up. Exemptionnaly, all map are in only one layout which saves trouble since Pro, like arcmap, doesn’t support mapseries only layout series.

So, for these maps I have choices, this time, of five databases. Since the introduction of tiled labels to annotations, we use this feature to make nicer maps since rotation and scale of adjacent maps was a problem since arcview 3x. Most of maps always overlapping others. So having annotation link to a map almost save the problem.

My labelling map is the same for all sources databases. In arcmap, it was straifoward. Use the template, link to the first database, running the geoprocessing tools. When done, change datasources for the next database, run again and so on until all my sources databases are parse. The only drawback of arcmap was the inability to populate the TileId field correctly. Many times it’s populated some maps but not others. With Pro, at least last time all tiledId was populated correctly.

So next, I only have to copy the group of annotations with a specific scale to the right map and it’s done. It’s simple and straitfoword. Can redo multiple time without having to parse each labelling to be flagged to label and to be sure none is lost in the process. The drawback of arcmap was to make one mxd by map. With the return of arcview 3x capability, Pro save headache when we have to change something in a layer. So my project is reduced from a potential 69 mxd to 26 maps.

It could be easier to maintain if we can join a labelling scale group to a map and not having to duplicate the map for each scale but, it’s a big improvement with the return of arcview way.

If I haven’t forgotten one, maps structure look this way :



Now I hope you understand the need to let the flag on for the next geoprocessing. Since the other solution, not to include them in the map but make a structure directly in the database have been rejected by ESRI, see Craig Williams responds in, Re: Grouping tiled lable in the database - Status changed to: Closed <>, it’s more relevant.

I know I can, each time import the template but, I’m in favour of the way we were before.

Hope this time is more clear.