|
IDEA
|
Jakub, There is no antialiasing applied in PDF to TIFF - as you noted it is applied when the PDF is exported _from_ ArcGIS Pro. If you consume a PDF exported from Pro that contains rasterized content that has anti-aliasing, it can only be consumed as it is already written and produce a PDF at the requested DPI. I would suggest posting examples of the artifacts you're trying to avoid, here, so we perhaps can get some better clarity on what you are trying to achieve, or perhaps if the behavior you're reporting is actually a _BUG_ in the PDF to TIFF tool? Regards, Jeremy W.
... View more
04-22-2022
12:48 PM
|
0
|
0
|
3525
|
|
POST
|
the stuff in the background displaying at a lower LOD is by design to control resource consumption of the textures. But it appears the SIZE difference is because they line is set to screen-size (pts). Go into layer properties->Display tab and check the box for "real-world-size" - after that the stuff in the distance should not change _size_ but it may still become blurry.
... View more
04-11-2022
04:09 PM
|
0
|
0
|
2055
|
|
POST
|
Amy, Never seen anything like this before, but here are some ideas to try to troubleshoot before you call support: 1. Update your GPU (Graphics card) driver from the manufacturer. You can find out what kind of GPU you have by running the "Can You Run It?" tool at https://links.esri.com/run-arcgis-pro-29x, it will give you a report that will mention your graphics card name/model. You can post a screenshot here as a reply if you need more guidance. 2. Switch from DirectX to OpenGL in the Options->Display menu - if the problem goes away, then it's likely a GPU driver problem, see item 1. If you can determine what steps cause the boxes to occur (e.g. it only happens when I click and drag a box using selection tool, only occurs when another window is on top of Pro window and then moved, etc.) that would also help troubleshoot.
... View more
02-25-2022
11:43 AM
|
2
|
0
|
2261
|
|
POST
|
Just gonna chime in here and note that Surface NOTEBOOK that Dan provided specs for above is different from the "Surface PRO" series - it actually does have a discrete GPU (GTX1660Ti). The latest Surface Pro (Surface Pro 😎 contains 11th-generation Intel Core processors, which have an upgraded integrated GPU called the Intel Iris Xe, which does provide better performance vs. previous integrated GPUs. Anecdotally: I have a machine (not a Surface Pro) that contains Intel Iris Xe GPU as one of my daily driver machines (working on developing ArcGIS Pro) and in testing it performs admirably for an integrated GPU, but without dedicated video memory you are going to want to configure your system with MORE system memory - because the integrated GPU takes system memory to use as video memory. That means potentially getting the top-end config Surface Pro - which has 32GB memory. Just my 2c! FWIW when we were first developing ArcGIS Pro 1.0, my daily driver was an original Surface Pro, and it worked OK. One last thing to note: if you want to use Deep Learning tools, those require CUDA acceleration, which is only available in NVIDIA GPUs. This requirement is enumerated in https://pro.arcgis.com/en/pro-app/latest/get-started/arcgis-pro-system-requirements.htm
... View more
02-25-2022
09:54 AM
|
0
|
1
|
8968
|
|
IDEA
|
moving to open to allow voting and commentary however as stated before without a specification to write this file format and/or a plug-in API as exists for Adobe products, we cannot directly write to this format .
... View more
02-18-2022
01:07 PM
|
0
|
0
|
3544
|
|
IDEA
|
PDF does not have constructs that would make this (changing symbology at different zoom levels) possible at this time. If you need a fully interactive map, then publishing it as a web map (or a mobile map package for use in one of many ArcGIS Apps) would be a better choice than PDF.
... View more
12-07-2021
09:47 AM
|
0
|
0
|
2166
|
|
POST
|
This difference appears to be due to the lighting applied to the TIN. In Pro, the TIN is always "lit" (based on illumination settings in Map Properties). In ArcMap, you could choose to turn this feature on and off from the Symbology tab of Layer Properties (it's called "show hillshade illumination effect in 2d display"). The mismatch you are seeing is a result of this lighting effect being applied to the TIN based on each face's aspect/angle to light - simulating how it would appear if drawn in 3d. This shading can be helpful to recognize the orientation of the different faces of the TIN dataset, much the same way a hillshade helps understand the shape of a DEM. There's no way to make it match identically to the legend depending on whether one classification of elevation faces multiple directions if the lighting will result in some faces being in "shadow" and some being "in the light". If you want the least difference, you can change lighting to move the altitude to 90 degrees, that means the light is coming from straight up, so no shading should be applied. By default it is set to 30 degrees elevation in Map Properties->Illumination.
... View more
11-15-2021
09:16 PM
|
2
|
1
|
9226
|
|
POST
|
Andy, The important thing to know here (and the thing that is unfortunately not obvious) is that that North Arrow is a character from a font. If you have "embed fonts" checked, then a subset of the font characters are included with the PDF, and any user can open it and see the right symbols. This is actually on by default - but it gets unchecked by other options, or by a user who might be clicking around. This is the option you should be using. If you use "convert marker symbols to polygons" then the fonts are converted at output time to "shapes" and that's why the user can still see the symbols. This option does get around the font problem, but polygonized fonts won't take advantage of other fancy properties of fonts such as hinting, so this should really mostly be used if you have character markers that DON'T have embeddability. If you have _neither_ option checked, then the PDF will "reference" the fonts. If it asks Windows for a font that isn't present, then "fallback" occurs and another font is substituted, which is why you get the rotated colon instead of the north arrow - it's getting Arial or something. People typically leave both unchecked if they're trying to create a smaller PDF or if they don't want to include assets that they KNOW will be on the client machines of the people opening the PDF. This actually isn't a pro-specific problem: same thing can happen in ArcMap too, but most of the default symbols in Esri styles are now vector markers rather than using fonts, so it happens less. BTW, there's more info on all of these settings at https://pro.arcgis.com/en/pro-app/latest/help/sharing/overview/pdf-export.htm tl; dr: this is expected, check the box for embed to fix it is the preferred solution. Hope this helps! Please let me know if you have any further questions regarding this information. Regards, Jeremy W.
... View more
11-12-2021
02:04 PM
|
5
|
1
|
9306
|
|
IDEA
|
Closed: Support of transparency in ArcMap was limited by the architecture's dependency on the Microsoft GDI library, therefore there was not a viable path to resolve this issue in ArcMap. The actively developed desktop application ArcGIS Pro uses a graphics and output engine built by Esri to no longer have this dependency. It is recommended to migrate to ArcGIS Pro if your workflow requires transparency support in page elements.
... View more
11-08-2021
04:30 PM
|
0
|
0
|
785
|
|
IDEA
|
Closed: Win 7 x64 is no longer a supported operating system by Microsoft. If this issue is still impacting users of a supported Microsoft OS and supported ArcMap release, please report it through Esri support.
... View more
11-08-2021
04:25 PM
|
0
|
0
|
2800
|
|
IDEA
|
Unfortunately it appears that the .AFDesign format (which is the extension used by Affinity Designer) is proprietry and closed. As such we have no way of being able to support it in ArcGIS Pro output. This is incidentally the same reason that we no longer support .AI export to Adobe Illustrator - AI format is also closed and proprietary. The plug-in strategy (.AIX out of Pro, into Maps for Adobe plugin in Illustrator) is the one that Adobe recommends to third-party developers, to be able to import their content in Illustrator. Does Affinity Designer offer any kind of plug-in strategy which could be leveraged to import content natively into an .AFDesign? It appears their development team does not want to publicly document the file format: https://forum.affinity.serif.com/index.php?/topic/31716-file-format-specification/
... View more
09-30-2021
10:27 AM
|
0
|
0
|
3792
|
|
POST
|
there are multiple issues going on here, so it'd probably be best to get in contact with Esri support and send them a project package so they can attempt to repro and get it to development for investigation. Barring that here are some basic troubleshooting steps: 1. Lower DPI. If this is a large page size, 150 dpi may still be sufficient quality. 2. If it is always the same map frame that has the reported artifacts, attempt to reduce the complexity of this map frame's map until you no longer see the artifacts. (divide and conquer) 3. If possible try the latest release (2.8) to leverage any bug fixes and performance fixes that are present therein
... View more
06-16-2021
09:39 AM
|
1
|
0
|
1494
|
|
POST
|
@DonKihout you can turn off "atmospheric effects" to get rid of the sun shadow on the earth - the lighting will still be applied to the items in the scene, and they can still cast shadows individually.
... View more
05-04-2021
09:28 AM
|
0
|
1
|
1437
|
|
POST
|
If you continue to have issues, might be good to get in touch with Esri support so they can more interactively troubleshoot.
... View more
05-03-2021
09:56 AM
|
1
|
0
|
1571
|
|
POST
|
OK glad clearing the cache fixed the problem with the excessive drawing popup. Your machine should be more than capable of running Voxel layers, so I'm at a loss at what could be wrong there. One thing to check is that you're using DirectX in display options - early releases that supported Voxel layerse didn't work with OpenGL - the Scene Layers team has fixed that in 2.7. Additionally the upcoming 2.8 release has some fixes for layout display of Voxel layers, and some were back-ported to 2.7.2, so make sure you're on the latest release to pick up these changes.
... View more
05-03-2021
09:19 AM
|
0
|
2
|
1575
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 12-12-2023 11:54 AM | |
| 1 | 12-11-2023 04:07 PM | |
| 1 | 12-13-2023 01:28 PM | |
| 1 | 11-25-2024 03:40 PM | |
| 3 | 03-07-2025 10:29 AM |
| Online Status |
Online
|
| Date Last Visited |
4m ago
|