Latest Contributions by JeremyWright

Next thing to check is the map itself - does it have the color model set to RGB, or CMYK? ... View more

Sorry for the confusion.  Check the layout itself's properties (right-click on the layout node in the Table of Contents, choose properties, go to the Color Management tab).  There you'll find the color model assigned to the layout itself.  This is used to render the layout whether or not color management is enabled (reflecting for example, the color reproduction capabilities of a printer vs. a monitor) ... View more

OK - the "washed out" appearance is perhaps reflecting the effect of the layout being set to CMYK?  Check under the layout properties->color management and see if the Color Model is set to CMYK or RGB. Change it to RGB, and try your export again. ... View more

Can you check the status of the color management setting on your 2.5 machine, as per Jeff Barrette's recommendation below? ... View more

Thomas, What application (and version) are you viewing the export PDF in where it appears washed out? Regards, Jeremy W. ... View more

Ram, Thanks!  I'm aware that we added this feature several releases ago.  2016 was a long time ago! J ... View more

No, that's why I was curious as to other factors.  This type of issue it's better to do troubleshooting interactively with Esri Support - it's not really conducive to forum discussion. ... View more

Not sure what is going on in your case - can you send this to Esri support so we can get a ticket started? ... View more

Oops, sorry for not clarifying.  LOD = Level Of Detail - basically the "resolution" at which the elevation source is triangulated and displayed in a scene.   ... View more

To answer your question here about "on the ground" - this elevation mode draws each vertex of a polygon feature class at the elevation of that location and should update as you change between elevation LODs. However, it appears you're using a procedural symbol layer to make gable-roofed buildings from these features, which might conflict or otherwise counteract this elevation mode.  As an experiment, try using "base heights" extrusion instead and see if the result is more amenable. ... View more

Elevation surfaces in ArcGIS Pro are always multi-LOD, and Pro will display a lower LOD of the elevation surface from greater viewing distances.  This is done to conserve resources as a 3d view with a long camera angle can have quite a bit of terrain data in it (several million triangles).   That said, we do tune the terrain system at each release to attempt to improve the appearance and LOD selection logic to balance between speed, resource consumption, and appearance.  In fact - we're working on enhancements in the next release (2.6) that will improve the resolution in constrained views (such as a case where you only have one DEM for a small area displayed, or when you have your view clipped to a specific extent) such as the one above. One workaround for this in the meantime is to use the Raster to TIN geoprocessing tool to create a TIN Dataset of the same area, and use that instead of the elevation raster.  TIN datasets always display at full resolution, and therefore should give you consistent elevation on which to place your buildings.  The downside of this is that of course you cannot show a much larger area before resource constraints kick in again, but it should get you around this challenge.  Another downside of this is that you can't publish a TIN dataset in a web scene. . ... View more

Here's an FAQ I just wrote up for this issue: WHY DO I NOT SEE THIS ARTIFACT IN ARCMAP? ArcMap does not exhibit this behavior is because the output pipeline in ArcMap DOES NOT support alpha transparency.  All the layers below a partially transparent layer are already flattened and composited together into a single layer called "Image" in the PDF - so you lose the layers. WHY DOES PRO EXPORT HAVE THIS PROBLEM? Pro exports can natively support transparency in any layer, and because of this they run afoul of this display artifact in PDF reader when a raster layer is output that contains transparency in multiple tiles.   I ONLY HAVE ONE RASTER LAYER IN MY MAP, WHY DO I SEE THIS PROBLEM?  Keep in mind that some layers "become" raster layers when some symbology is applied (an example would be the heatmap renderer for points) even if they're not raster layers in your ArcGIS Pro map.  Even a single raster layer can become multiple _tiles_ of raster layer (placed like mosaic tiles together to form the larger image).  We output raster layers in multiple tiles so that we can export higher resolutions without consuming inordinate amounts of resources. WHY DOES OUTPUT AS IMAGE CAUSE THE GRIDLINES TO DISAPPEAR? - Exporting using "Output As Image" gets around this because it performs flattening of the transparency BEFORE we write it to the PDF (very similar to what ArcMap output did). ARE YOU SURE THIS IS AN ISSUE IN THE DISPLAYING APPLICATION, NOT SOME PROBLEM WITH THE PDF? - the gridlines remain the same width regardless of zoom level.  - you can print this from Acrobat and it looks fine (no gridlines).  - You can also use "Optimize PDF" and choose the flatten option (which removes transparency) and no gridlines.  - The gridlines are ONLY visible in the viewing application, and they appear to be an artifact of the way that transparency is applied to adjacent tiles in the viewing application. - We can inspect the coordinates of each of the tiles internal to the PDF written and they are NOT overlapping. WHAT ACTIONS ARE BEING TAKEN TO TRY TO INVESTIGATE OR MITIGATE THIS ISSUE? After a long period of investigation, we contacted Adobe support about this some time ago.  In that contact, Adobe employee Dov Isaacs had acknowledged that it the PDF is written to spec, and therefore should display without these artifacts.  It is currently an open bug in the Adobe Acrobat queue.  WHAT IS THE STATUS OF THE BUG IN ADOBE'S QUEUE? We now are waiting on some analysis or guidance from them.  We have also recently reached out through multiple channels to try and get some response on this issue, but so far have not heard any updates.   ... View more

We are still waiting for a response from Adobe through multiple outreach channels. In the meantime you can use "export as image" to flatten the transparency and remove the grid lines. ... View more

This is logged as BUG-000111662.  We have it up for investigation in the release after 2.5 (which is already in progress), but be aware that the next release of Maps for Adobe Creative Cloud (which will allow you to bring Pro content directly into Adobe Illustrator for post-editing) will also allow similar workflows by going direct from Pro to AI.   ... View more

FWIW - I've just pinged the ArcGIS Maps for Adobe Creative Cloud team to see if they have any alternative contacts we might be able to reach out to at Adobe (even if they're on a different product team) to see how to get some traction from them on this issue.   ... View more