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; } } }

Exported map missing lines version (Pro V2.7)

JessicaStrauss

Any ideas would be appreciated.

Since updating to Pro Version 2.7 last week all outputs (Jpeg, Png, PDF) are all missing graphic lines (feature ones are fine just those used for borders etc. I have searched but can't work it out.

Example 1: This is on the layout view - this is what we want as the output

Example 2: This is the exported view

Finde mehr Beiträge mit dem Tag

Analysis

Accepted answers

TomBole

Hello Everyone,

We have addressed this issue - BUG-000136364 - and the fix should be available with ArcGIS Pro 2.7.1. We're confident that the fix addresses the scenarios outlined in this thread and provided by those who contacted Support. But just incase, if you have installed this patch and are still seeing issues with graphics being dropped from the output please contact Support.

Thanks to all who participated in this thread. It means a lot to hear from all of you - the good and the bad.

Tom

All comments

JanBurdziej

Thanks Tom for looking into this. I will submit as a bug... Just getting tired with all these little things that are not working in Pro and then you need to spend hours on troubleshooting, reporting etc. I have a feeling that Pro is 2 steps forward comparing to ArcMap and 5 steps backwards... 😕

TomBole

Hi Jan,

It is not the same bug. I suspect that you may be running into an issue where the export is not recognizing the border "feature" in the map view for some reason. My guess is that the export code sees this border as being outside the bounds of the map extent/projection and doesn't draw it. It could be related to the layer that you are using to clip the map frame as well.

Since this is probably a bug can you contact Esri Support? They are better equipped to handle troubleshooting steps and gather bug data. They can be contacted at https://support.esri.com/en/contact-tech-support.

As to a work-around - I haven't run across this so I don't have any good suggestions other than to increase the width of the border or to use the clip features themselves as the border by excluding the clip layer from being clipped. You may have to play around with this, but it may work.

Thanks,

Tom

PS: I can confirm that the clip border does get dropped from the export no matter how thick the line is. This is a bug. The workaround with using the clip feature as a border does work. You just need to include it as an excluded layer (from the clip) in order for the line width to be consistent.

JanBurdziej

Hi Tom,

I have a similar issue working with ArcGIS Pro 2.7.1. I have a layout with a Map Frame that uses "Clip Layers" functionality. The map frame uses Robinson projection and I'd like to have a border clipped to the Robinson projection extent. The "Clip Layers" function works as expected and I've set up a border symbol:

and my layout looks good:

However, when I export the layout (to PDF, JPEG, PNG) the border is not there:

Is this related to the same bug? Any suggestions would be appreciated.

Thanks,

Jan

LindsayRaabe_FPCWA

I can't see the images you've attached to your post, so I'm guessing as to what the error is, but if you're using the python window in ArcGIS Pro, you shouldn't need to include the "import arcpy" line. The only other difference I can see between your script and mine (besides the layout name "TEST" and output pathway) is there is an extra "space" before the lyt.exportToPDF command - dunno if this should impact on it though. Maybe also test a shorter output folder (i.e. f"C:\Temp\{lyt.name}.pdf") and see if that works first.

Also, the latest ArcGIS Pro update (2.7.1) has fixed this issue so you can avoid all this if you update your software (as per the solution post below).

CorbinPeretzki

@LindsayRaabe_FPCWA

Good Morning,

Thank you for posting this! Below is the code that I tried to use in ArcPro 2.7. Could you by chance please help me understand why Im getting the error that I am getting?

import arcpy

aprx = arcpy.mp.ArcGISProject("CURRENT")

aprx.listLayouts()

for lyt in aprx.listLayouts("TEST"):
lyt.exportToPDF(f"C:\Users\cperez2\Documents\ArcGIS\Projects\BMP\{lyt.name}.pdf", 150, "NORMAL", True, "ADAPTIVE", True, "LAYERS_ONLY", True, 80, False, False, False)
print("Done")

Capture.PNG

Capture1.PNG

TomBole

Hello Everyone,

Thanks to all who participated in this thread. It means a lot to hear from all of you - the good and the bad.

Tom

AlBost

Hi, I'm also using 2.7 and have just noticed the lines on my layout missing in my output. After reading the previous suggestion of copying those lines and boxes and repasting them, it worked. That was a big help. Now I also have just seen that a 2.7.1 patch is out (must be very recent) so I will try that.

p.s. Tom, I like your response above 🙂

KevinStarr

Also experiencing pdf export issues after installing 2.7 yesterday when the same project was exporting just fine with 2.5..

Simple legend patches, text, and borders all won't display in exported pdf. No other format like png, jpeg, etc will display items correctly. Print to pdf will also not display items correctly.

I'm a very novice GIS user and Python scripting as a workaround is just not an option for me. Is there a current fix for this bug or can someone please help explain to me how to reinstall my earlier 2.5 version of Pro?

Thanks,

Kevin

EricCreighton

Thanks Tom, I appreciate your response on the matter in several ways

TomBole

Hi Kit,

My name is Tom Bole. I'm a Product Engineer on the Layout team. I'm one of those responsible for testing this area of the software. I'm also a big fan of sarcasm. Ask anyone who knows or works with me. I appreciate the frustration over this issue. I'll use my sarcastic voice here -

"Whose the genius that made all the lines disappear?! When did Penn & Teller start working for esri development? What do they put in the water in Redlands? Dumb-juice? What an evil set of bozos!!!"

That felt good. Now that I've gotten that out of my system...

The key here is not all linework is dropped. Only specific graphics are being dropped. Unfortunately, we did not have any examples in our testing harness. The issue was also not discovered through the beta program where we catch some of the oversights by the testing team (that's me and I'd be glad to go over the dumb mistakes and assumptions I've made over the last 20 years). This was an unknown bug that went out with the release. It happens. We're not omniscient.

Once customers posted the issue on GeoNet and brought to our attention we thought, and I'll paraphrase, "How the heck did we miss this?" Something so basic. We checked our tests. All good. The linework appears in all the supported output types. These lines were created in various versions of Pro and also imported from various versions of ArcMap.

What's going on? We second guessed ourselves and wracked our collective brains trying to get a repro case - much of it over the holidays - to no avail. Then one day we got lucky with a ArcMap file a customer sent to us for a different issue. Lines dropped from the exported file. One of our developers could now reproduce the bug and inspect the code. Seems a change was made deep in the code that had an unintended consequence for specific geometries on a layout.

Unintended consequences of changes in the code. That's what bugs are. They are not something we plan out on a white board or present as bulleted items in a PowerPoint presentation. They are things we have to find, though our automated testing, through manual testing within the team, through functional and holistic testing, and through testing by people outside the team (to get a view from outside the "bubble"). We do not find everything. Sometimes we miss something big like this. But this issue is on our radar now, its a priority, and we are working on it.

Tom

MichaelAugust

Hey Vishal - this may or may not help you, but we've noticed an increase in speed setting Pro to OpenGL vs DirectX graphics. Unrelated to this post but thought I'd throw that out there. Getting a machine with highest possible amounts of Cores/GPU/RAM would help too.

SBrandenburg

Wow ESRI. Well done. You managed to screw up some of the most basic functionality of ArcPro. 3 weeks later this issue still isn't fixed. I am truly in awe. Does the development team ever test anything before releases?

GeraldHeston

I have also had this issue with rectangles and lines not exporting to PDF or JPG from a layout. It started when I upgraded to 2.7. I will try redrawing the graphics.

LindsayRaabe_FPCWA

We too have found this same issue with rectangle and line graphic elements not exporting. We have found the python code works as a work around, but will be telling staff not to upgrade until this is fixed (and reverting other installs to 2.6).

A tip for those unsure about python use, if you only want to export a single layout in your project, enter the layout name between the brackets (and inside " ") on line 4 as per my added instruction below;

##Export to PDF
aprx = arcpy.mp.ArcGISProject("CURRENT")
aprx.listLayouts()
for lyt in aprx.listLayouts(): #**** ENTER THE LAYOUT NAME YOU WANT TO EXPORT INTO THE BRACKETS i.e.     for lyt in aprx.listLayouts("Layout Name"):
#Parameters: output name, resolution, image quality, compress vector graphics, image compression, embed fonts, layer attributes, georeference, jpeg compression, clip to elements, output as image, embed color profile
#Image quality: "BEST", "BETTER", "NORMAL", "FASTER", "FASTEST"
#Image compression: "ADAPTIVE", "DEFLATE", "JPEG", "LZW", "NONE", "RLE"
#Layer attributes: "LAYERS_ONLY", "LAYERS_AND_ATTRIBUTES", "NONE"
    lyt.exportToPDF(f"C:\Temp\{lyt.name}.pdf", 150, "NORMAL", True, "ADAPTIVE", True, "LAYERS_ONLY", True, 80, False, False, False)
print("Done")

TomBole

Hi Logan,

This thread is specifically about line graphics getting dropped in the exported file. I see that you are having a separate issue with legends. I can answer a few questions - however, I think if you want a back and forth a new legend-specific thread should be created.

A new legend fitting type was added at 2.7 - Manual Columns. This type was added because we found that the the legend item option "New Column" created a number of difficult issues with a few of the Legend fitting strategies. Whenever we make changes to the legend we work hard to not change existing legends. Unfortunately, our test suite is but a sample of the vast number of possible legend combinations.

It is possible that your "enlarged" legend is a bug. Not knowing the details of your legend (layers, size, properties, etc...) I can only guess.

You are welcome to log an issue with support. They are better equipped to handle troubleshooting steps and gather bug data. They can be contacted at https://support.esri.com/en/contact-tech-support.

Please refer to https://pro.arcgis.com/en/pro-app/latest/help/layouts/layout-fitting-strategies.htm for more information.

Thanks,

Tom

TomBole

HI Tanya,

You should be able to see the status of a bug on the support site - https://support.esri.com/en/Search-Results#search?q=BUG-000136364

Tom

TanyaOwens

Is there any update on BUG-000136364?

LoganSuhr_PSE

Same issue here as well. Map frame borders are still good though.

We are currently checking other projects side-by-side between 2.6 and 2.7 but what we know for sure is that all projects created from one of our templates and before the upgrade to 2.7 have some gremlins.

Our workaround for missing map elements is to simply cut and paste. No deletion required. But, we do end up needing to shift everything back into it's proper place.

In all, we have noticed the following errors:

Layout lines and polygons not exporting to PDF
Not all legend items have the option for 'New Column' but they did in Pro 2.6

The result is that our legend items are not where they are supposed to be and have run over their frame graphics we drew.

There could be more and I'll edit the post to reflect anything else we find.

Bug status is 'high'

JessicaStrauss

Thanks for the code worked perfectly. I'm not a coder at all (generally can never get these things to work) but this was easy to use and simply just a copy and paste. Just indent the "lyt.exportToPDF(f"C:\Temp\{lyt.name}.pdf", 150, "BEST", True, "ADAPTIVE", True, "LAYERS_ONLY", True, 80, False, False, False)" line.

Copying and pasting the elements works too but it's not really conducive to a larger number of layout views. I often have over 30 maps per project and a time limit due to cost to get these done.

VishalBalraj

In addition to the regular, lethargic performance of ArcGIS Pro, I am having similar issues.

Problem: For me, the problem arises when I duplicate an older layout (prepared with ArcGIS Pro 2.5) in my now updated ArcGIS Pro 2.7. In the duplicated layout, some graphics are "not recognised" by the updated software. However, graphics in the older/original layout displays fine.

Work-around: I opened the older/original layout and copy-pasted the required elements into the newer/"corrupted" duplicate layout.

ArcGIS Pro v.2.7 Layout-Graphic Issues 00.pdf

CarlMorrison

Michael,

I too am having this same issue using older layout templates. Fortunately, I was already using a version of the python code Tom provided and found it worked. May I suggest a shortened version that can be pasted in a Python Notebook and run to get you by?

import arcpy
aprx = arcpy.mp.ArcGISProject (r"CURRENT")
for lyt in aprx.listLayouts():
lyt.exportToPDF(f"C:\Temp\{lyt.name}.pdf", resolution = 300)

ClintonMcComb1

I too ran into this issue and your recommendation worked for me also. I didn't even have to delete the old ones, just pasted the copied elements on top. Thanks!

TomBole

Hi Michael,

Thanks for contacting support. Having an official BUG number help! It also helps track the issue since its status automatically changes as the issue goes through the system.

As of now we don't know the prevalence of this issue. Our testing and certification of Pro 2.7 did not undercover any issues like this and we have many test cases with line work on layouts that get exported to all the supported formats. However, enough people are reporting this issue that we consider this a HIGH PRIORITY item. We "lucked" into a test case that reproduces the issue and that gives the developers something to work with.

Recreating these items is NOT acceptable. We understand this and offer the python work-around as something to work with until we have a solution. Unfortunately, it is the only option at this point. Hopefully, the examples provided at the links can help "code adverse" GISers a little help to overcome any hurdles.

Tom

MichaelAugust

"BUG-000136364" is all I got from support after sending in my template..."case closed", that's sad. I think everyone who's experiencing this should continue to comment on this post, maybe just to see how prevalent the issue is. Copying and pasting these elements and replacing legends on all of our hundreds of existing Pro projects is not really helpful, and is going to cost us a lot of money and time. While the Python solution would work yes, I can't really expect/explain that to our "lighter" GIS users who only occasionally use Pro.

TomBole

All,

Currently, we believe that the lines are getting dropped during the exporting process through the UI. This is being investigated as we have found a single case where this is occurring.

We've also have discovered, with this specific case, that exporting the layout via python (ArcPy.mp) includes the expected lines as expected in the exported file. This may provide a workaround until we have identified the bug and engineered a solution.

You can open the Python window from the View tab on the ribbon.

Screenshot 2020-11-19 053457.png

The following code, when pasted into the Python window and run, will export every layout in the project to a PDF file in C:\temp. For map series in the project, only a single page will be exported.

##Export to PDF
aprx = arcpy.mp.ArcGISProject("CURRENT")
aprx.listLayouts()
for lyt in aprx.listLayouts():
#Parameters: output name, resolution, image quality, compress vector graphics, image compression, embed fonts, layer attributes, georeference, jpeg compression, clip to elements, output as image, embed color profile
#Image quality: "BEST", "BETTER", "NORMAL", "FASTER", "FASTEST"
#Image compression: "ADAPTIVE", "DEFLATE", "JPEG", "LZW", "NONE", "RLE"
#Layer attributes: "LAYERS_ONLY", "LAYERS_AND_ATTRIBUTES", "NONE"
lyt.exportToPDF(f"C:\Temp\{lyt.name}.pdf", 150, "BEST", True, "ADAPTIVE", True, "LAYERS_ONLY", True, 80, False, False, False)
print("Done")

For more information on ArcPy please see - https://pro.arcgis.com/en/pro-app/latest/arcpy/mapping/tutorial-getting-started-with-arcpy-mp.htm

At the bottom of this topic is a section on exporting to PDF.

Sorry for the inconvenience and I hope this work around helps.

Tom

Anonymous User

I am also having this issue.

EricCreighton

I am also having the same issue as stated above. Interested to see what the resolution is.

MichaelAugust

Yes - I'll contact support - my post was mostly to acknowledge that, like the original poster, we are seeing the exact same behavior - thanks!

TomBole

Hi Michael,

Sorry you are running into problems. Before we can do anything about the problem we have to be able to reproduce this issue so a developer can then step through the code to see what exactly is causing the bug.

I mention 2 issues:

1. Some Graphics present in the layout are not displaying in the exported file

As stated earlier we are unaware of any issues with 2.7 and cannot reproduce the stated problem. With our test maps we see all expected graphics on the layout in the exported file.

2. You can no longer drag/drop layers into legends.

I'm not aware of any known issue concerning this functionality in 2.7. I'm able to drag/drop new layers into both the legend on the layout page and into the legend item in the Contents pane.

I'm sure you and others are running into problems, but until we can reproduce (with clear steps & data) either issue there is only guesswork. Can you contact Esri Support? They are better equipped to handle troubleshooting steps and gather bug data. They can be contacted at https://support.esri.com/en/contact-tech-support.

Thanks,

Tom

MichaelAugust

This is indeed happening to us as well, we have some boxes and lines that serve as a title block, on all of our previously created Pro figures now, these graphics are dropped/missing when we export to pdfs. Also our legends don't function correctly either, we seem to lose the ability to drag/drop layers from existing Pro projects, we end up having to recreate all of our legends too.

Can someone look into this? Happened right after Pro upgrade to 2.7 with three of our analysts on 6 different machines.

MichaelStandart2

Our group ran into this today and as a work around we copy and pasted the Rectangle Elements, and deleted the original ones that were not exporting, and that worked.

TomBole

Hi Jessica,

I'm not aware of any outstanding issue regarding the dropping of graphic lines from an exported layout. At the moment I can't think of anything that might cause a problem like this.

Can you contact Esri Support? They are better equipped to handle troubleshooting steps and gather bug data. They can be contacted at https://support.esri.com/en/contact-tech-support.

Thanks,

Tom

Nimm an der Unterhaltung teil

Angemeldete Mitglieder können Beiträge verfassen, Updates folgen und mehr. Neu hier? Registriere ein kostenloses Konto.

Schnellzugriffe

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