nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Annotation exporting outside data frame V10

AustinStreetman

Running ArcGIS 10 SP2, when I export to PDF, annotation from a V9.3 file Geodatabase shows up in the margins of the map, outside of the data frame.

Anno_issue.jpg

Find more posts tagged with

Accepted answers

All comments

ShaunConway

Thanks Rachel! Very helpful for those of us still at 10.0.5!

JohnMacdonald1

That's good to know.

We still haven't encountered this bug since uprading to 10.2.

RachelFrischeisen

A few of the previously posted work-arounds seemed to work for some people but not all - just wanted to contribute what we found to be the issue in our case.

We are at 10.0.5 and while labels (not annotation as some have described) appeared to be confined to the data frame while in layout view, printing from ArcGIS and exporting to PDF resulted in the labels beyond the data frame. The issue was occurring only one when labeling one layer in particular and only when the data frame had a rotation applied.

After digging around in the Label Placement Properties dialog box, we found that having the "Never remove (allow overlap)" box checked on will cause the labels to go beyond the data frame. Again, this only happens when rotation is anything other than 0.

TL;DR - Uncheck this box.
[ATTACH=CONFIG]31241[/ATTACH]

Hope this helps.

overlap.JPG

JohnMacdonald1

Just went through the upgrade to 10.2 and it does appear to have solved the problem, for now. I'll keep my fingers crossed!
We are running Windows 7 SP1 also.

I hear what you're saying re: transparency. It's too bad so many people have to go through so much frustration and lost productivity over these issues.

Appreciate all the feed back, hope you enjoy some trouble free ESRI use in the future!

EricPieniak

10.2 has likely addressed this. Print spooling in windows 7 behaves different than XP - could also effect print previews and print to pdf. I bring this up because our IT dept. has finally allowed us to instal service pack 1 - I don't know if SP1 resolves print spool issues. So would be the only other thing I can think of that is different in my machine. I wish I would have checked the issues at each install/update, but it is working fine in 10.2 with Win 7 SP1. It would be nice if ESRI(among other vendors) were more transparent to issues - well..... lets not talk about transperency issues and printing in the same paragraph, lol.

JohnMacdonald1

That's good to know. The computers experiencing these issues are all 10.1. We will upgrade and see if the problem goes away.

Thanks for the reply!

EricPieniak

I have 10.2 now, and I went back to the maps that were giving me trouble when I reported this issue - when I was using 10.1. I turned the labeling back on for the particular layers bleeding out, and no bleed. It appears ESRI has fixed this issue in 10.2 - I cannot recreate the problem.

JohnMacdonald1

SOLUTION (at least for me): I had the same problem with annotations showing up outside the data frame when both exporting to .pdf and when printing the .mxd straight from Arc. Even using a .pdf printer did not fix it. I grouped all my layers into one large group in the data frame and the problem was solved. I have wasted so much time on this.

PLEASE FIX THIS ESRI!

Thanks. We've just run into this problem and this works for us. It's a little cumbersome but it has allowed us to keep going. In our case it's point shape files exporting and/or printing outside the dataframe. The shape files are created by GPSeismic. This is the same workflow we've used for years and we've never run into this until last month. Copying all layers into a new dataframe seemed to work for a while but the problem came back. Neither recreating the shapes or changing their styles works.
At the end of the day the fundamental purpose of this software is to create maps, this bug makes that very difficult. Why is it not getting fixed?

EricPieniak

Using 10.1 on 64 bit win 7 machine, have the same issue. With multiple views on top of main layout view - main view bleeds out past margin and inner views bleed out into main view. I'm too picky for this be in my product. The bleed out to margins was resolved with all layers in one group. the inner views did not get fixed this way. The other masking work-around will not work for these views. I'm graphic texting them, but may try view clipping by graphic, next, if I can find some time.

marieducharme

I' had this issue again last week...(such a waste of time- and it always seems to happen when a deadline is looming.....lol)

Anyway, I frantically tried many different solutions/work-around suggested here. Thanks everyone for sharing your tricks.

I stubbornly did not want to use the "donut-solution"....I wanted to "fix" it!

In this case, I did find a solution...The data frame of the map that I was having trouble with was rotated by -12.5 degrees. When I changed the rotation to 347.5 degrees (same rotation, different way of asking Arcmap to do it) my map exported perfectly. Maybe this work around will help another user out there.

Best of luck all of you fellows!

(and shame on ESRI for not posting anything in the entire, 2 year long thread!) This is a nasty nasty bug, that can really delay production!

ErinNovakovich

The best solution I've found is to remake the map from the beginning. Just drag layers into a blank map and redo the layout and graphics. Unfortunately its time consuming but pretty effective.
Good Luck to you all 🙂

LaurenWinkler2

I found a solution!

Go to Data Frame Properties > Data Frame.

Under Clip Options, choose Clip to Shape, click Specify Shape, and choose the Current Visible Extent.

Be sure to turn off the clipping if you pan to a different area.

LaurenWinkler2

This error is still occurring. I submitted it as an idea on ArcGIS Ideas.

If you're having the same issue, please vote on the idea:
https://c.na9.visual.force.com/apex/ideaView?id=087E00000004T7Z&returnUrl=%2Fapex%2FideaList%3Fc%3D09a300000004xET%26sort%3Drecent

MarkFawkes

The grouping technique worked for me:

ArcGIS 10 (not 10.1) SP5
Map annotation (not gdb)

Now if we could only have an explanation as to why grouping the layers worked!

And I subsequently edited the map and returned to the old problem - grouping and regrouping did not change the behaviour.

CarlTownsend1

OK,

I've found a very quick 'n dirty workaround. The grouping method didn't work for me; in fact it made things worse because annotation that was grouped together also started appearing, and persisted after I ungrouped them.

Here's what you do:

1) Select all the offending labels that are appearing outside the data frame

2) right-click > cut
The labels will be removed

3) Quickly export to pdf/print mxd etc.

4) Edit > Undo Delete Features to put your labels back.

CarlTownsend1

Same freaking problem here, arcmap 10, sp5. I'm wasting so much time on this...arcmap 10 has slowed me down to a crawl - not just with this but with loads of other things... I wasted several hours of my life yesterday updating several hundred field records one by one because the freaking field calculator doesn't work (yes, another arcmap 10 'feature' ) sigh.

Worst release ever.

BillClingman

The grouping did not work for me, but another suggestion further back in this thread did the trick: selecting the anno elements within the map frame, but not selecting the ones right along the edges, and creating a selection layer in the TOC. Use that layer instead of the source anno, and your export will be clean. Not ideal, by any means, but a workaround. I am using gdb annotation with 10.0 SP2

Bill C.
Eugene Oregon

MarkFawkes

The grouping technique worked for me:

ArcGIS 10 (not 10.1) SP5
Map annotation (not gdb)

Now if we could only have an explanation as to why grouping the layers worked!

BretFenster

Thanks for the grouping workaround!
ArcGIS 10 SP5, Server SP5, SDE SP5
Win 7 64 SP 1
Exports and map printing are kind of important to my work flow!

SOLUTION (at least for me): I had the same problem with annotations showing up outside the data frame when both exporting to .pdf and when printing the .mxd straight from Arc. Even using a .pdf printer did not fix it. I grouped all my layers into one large group in the data frame and the problem was solved. I have wasted so much time on this.

PLEASE FIX THIS ESRI!

NolanBecker

Greetings -

I am using ArcGIS 10.1 and this issues still exists. I have tried several work arounds but the text/annotation still bleeds into the margins. Some of the work arounds tried are exporting to various extents. The jpg mentioned in an earlier thread did not work for me. I also tried to print to PDF, that did not work.

Until the bug is fixed the donut solution seems to be it.

We are running ArcGIS 10.1 as well and are also still experiencing this issue. Text/annotation not only bleeds into the margins on pdfs, but also when we print paper copies of the map.

AustinStreetman

What is the donut solution

1.In Layout view, create a graphic rectangle that goes out the edge of the page. (can use guides for this)
2.Create another rectangle the same size as the Data Frame, align to the data frame
Select rectangle 2, then rectangle 1, and choose Drawing --> Graphic Opperations --> Subtract. You will now have a square doughnut graphic that frames your Data Frame.
3.Send the new graphic to the back
4.Send the Data Frame to the back
5.Set the graphic to have the same border you want your Data Frame to have.
Now when you export, the square doughnut graphic will mask anything that hangs out of the Data Frame.

LillianJohnson

What is the donut solution

BarbaraSimpson63

Greetings -

I am using ArcGIS 10.1 and this issues still exists. I have tried several work arounds but the text/annotation still bleeds into the margins. Some of the work arounds tried are exporting to various extents. The jpg mentioned in an earlier thread did not work for me. I also tried to print to PDF, that did not work.

Until the bug is fixed the donut solution seems to be it.

MaximSilin

One of my clients had a similar issue in ArcGIS 10.0 SP5 (see the screenshot). Upon investigation, several inset annotation feature classes have been identified to be causing the problem. The issue was resolved by grouping the faulty layers.

Max

ScreenShot025.jpg

ScottMoyer

I had this problem and resolved it without a workaround. SP 5 was installed for my 10.0 version, but the SDE server was still at SP 4. ESRI installation notes (following) say that the server must be version upgraded also. I uninstalled SP 5, reloaded SP 4, and all is well.

ERSI SP5 installation note says, "If you use ArcIMS 10.0 or the ArcSDE 10.0 application server, you must also install ArcIMS 10.0 Service Pack 5 or ArcSDE 10.0 Service Pack 5. For example, if you use ArcIMS 10.0 and ArcGIS 10.0 Desktop, install both ArcIMS 10.0 Service Pack 5 and ArcGIS 10.0 Service Pack 5 . Since ArcIMS 10.0 Service Pack 5, ArcSDE 10.0 Service Pack 5 and the ArcGIS 10.0 Service Pack 5 products share common DLLs, it is important to keep the software release versions in sync to avoid any software conflicts."

DrewLane

SOLUTION (at least for me): I had the same problem with annotations showing up outside the data frame when both exporting to .pdf and when printing the .mxd straight from Arc. Even using a .pdf printer did not fix it. I grouped all my layers into one large group in the data frame and the problem was solved. I have wasted so much time on this.

PLEASE FIX THIS ESRI!

DianeMcConnaughey

I was having a similar problem with using clip to shape in the Data Frame, ArcGIS 10 Sp4 Windows 7. In the MXD everything is clipped , but when exported to a PDF, a couple of features in one layer, do not get clipped. What worked was converting the problematic shapefile to a FC in a Geodatabase. Using the 2 graphic rectangles described above or grouping everything did not work. Maybe there was a problem with the shapefile that converting to a FC fixed?

BillPatrick

I was having the same trouble with an annotation feature class and a point feature class symbol drawing outside of the data frame extent on my PDF exports. For the two layers which were drawing outside of the extent, I moved them both to the bottom of the TOC and ran an export to PDF and it worked properly. Then one at a time I promoted the layers up from the bottom of the TOC and ran an export each time they were promoted up in the TOC. I was able to identify the layers in conflict with eachother which caused the layers to act up on the export. I'm thinking it has to do with some complex symbology for my line types? Hope this helps.

Tom_De_Smet

Found the cause...

In my case the labels outside the dataframe seem to be coming from a problem with a different layer.
The layer I mentioned before has a character marker symbol, and this seems to give a conflict with the labeled layer.

my solution:
1 change the symbol to a simple symbol
2 drag the pointlayer below the the layer with the lables

as long as there aren't any polygon layers above that your points are still visible and the problem should be solved

greetings

Tom_De_Smet

Hi, I seem to have a similar problem but with labels instead of annotation.

I have discovered 1 layer that is actually causing this problem. There is a layer on top of all the others. When I drag it to the bottom my export to pdf is good. When I turn it off the pdf is good.
It's a point shapefile. The symbol is a character marker symbol of a flag. Switching the symbol doesn't help though.

Have any of you tried turning of layers of dragging them to the bottom?
I don't think there's anything wrong with the shapefile. It seems more like conflict in the layers...

Greetings

ArcGIS 10 SP4 Win7

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.