|
POST
|
ok - I'll give it a whirl now. so to be clear you see the anomalous behavior/appearance ONLY in exports, or also in the view when color management is enabled?
... View more
05-23-2022
10:05 AM
|
0
|
0
|
6159
|
|
IDEA
|
Sorry for the confusion @PavelSeemann M4ACC is shorthand we use internally for Maps for Adobe Creative Cloud extension - I should have expanded the acronym.
... View more
05-23-2022
09:25 AM
|
0
|
0
|
3895
|
|
POST
|
What is the data type of the label layer in question - are these actually labeling in Pro or are they just labels that are part of a basemap's "reference" layer?
... View more
05-23-2022
09:23 AM
|
0
|
0
|
6161
|
|
IDEA
|
I've changed the status to _closed_ because M4ACC is the preferred and vendor (Adobe) supported way to get stuff into Adobe Illustrator. Discussion can continue regarding the issue that Pavel surfaced regarding AIX and Annotation workflows, and I'd encourage him to get those logged so M4ACC can work towards resolving them.
... View more
05-20-2022
11:32 AM
|
0
|
0
|
3926
|
|
IDEA
|
@wayfaringrob I'd encourage you to report issues you are having with AIX - my team works with the Maps for Creative Cloud team, and FWIW we fixed the BUG you quoted in the 3.0 release (out soon). You can easily report a bug and provide repro data (such as a Map or Project Package) as well as steps through https://support.esri.com/en/report-bug - no need to make a phone call! As far as opening an AIX without M4ACC - that's unfortunately not gonna work. Adobe were the ones who mandated this workflow using a plug-in, as they previously closed the AI file format many many releases ago. So this is what we have to do to pour Pro content directly into Illustrator. If you have challenges with the login requirement, please report them as bugs through the same form (https://support.esri.com/en/report-bug) so that the appropriate team can address them in a future release. I do know that the team has worked on some login UX issues in the upcoming release of Maps for Creative Cloud as well.
... View more
05-17-2022
03:53 PM
|
0
|
0
|
5946
|
|
POST
|
Magda, The fix I described above does avoid exporting data that's not in the view, so I encourage you to try out 3.0 once it is made publicly available and if you're still having trouble please contact us with more details and a repro case. Regards, Jeremy W.
... View more
05-17-2022
03:44 PM
|
0
|
0
|
2388
|
|
IDEA
|
@PavelSeemann excellent, that provides some clarity as to your motivation in this regard. It seems what you've encountered is a bug in AIX export OR in the M4ACC extension. Since it's a bug, we'd like to investigate further - can you provide us with some information regarding the 'bad experiences with exporting annotations to an AIX file' so that we can potentially fix those bugs? I can share this with the developers on the M4ACC team so we can work to resolve these challenges in the future. I'll contact you via DM to talk about getting the repro case. In the meantime, since AIX _should_ suffice for this case (if we can fix the bug you discovered :)), I would like to close this enhancement request. Is that OK with you? UPDATE: it appears you have DM disabled, can you provide alternative contact info?
... View more
05-17-2022
11:07 AM
|
0
|
0
|
3999
|
|
IDEA
|
@PavelSeemann We are aware of this limitation in Illustrator but it does not exist in other PDF readers. The recommended workflow for moving your ArcGIS content into Adobe Illustrator is to use the Maps for Adobe Creative Cloud extension in Illustrator. The AIX export type from ArcGIS Pro is meant to be opened by Maps For Creative cloud and should provide much nicer UX for you than importing the PDF directly. AIX also does dice the polygons to avoid exceeding the 32k vertex limit. More info on Maps for Creative Cloud is here: https://www.esri.com/en-us/arcgis/products/maps-for-adobecc/overview
... View more
05-17-2022
09:32 AM
|
0
|
0
|
4054
|
|
IDEA
|
@Anonymous User I'm glad the improvements we've implemented over the last couple releases are working out for you - several changes were made to improve file size. We have even more improvements going in to the next release of ArcGIS Pro as well. @BobPlummer can you try the settings Andrea has recommended with the latest release of ArcGIS Pro (currently 2.9.2) and see if these meet your needs? If you have a specific map or layout that proves particularly hard to get comparable exports on, I'd encourage you to try ArcGIS Pro 3.0 when it is released later this year - we have a few enhancements to export file size reduction that may prove very useful for you.
... View more
05-04-2022
04:08 PM
|
0
|
0
|
15691
|
|
IDEA
|
@JLezik curiouser and curiouser! I've contacted the developer of this tool to find out if there is something internally that may be adding this smoothing when creating the TIFF. I'll let you know what we find.
... View more
04-28-2022
10:30 AM
|
0
|
0
|
3474
|
|
POST
|
I will try to address your concerns below, but let me know if I've missed one. I heard the following: 1) when same data is added to default Pro local scenes, it looks sunken (because there is a default elevation source and basemap) - POTENTIAL MITIGATION: you can change Map And Scene Options to remove default elevation and default basemaps from newly added scenes: https://pro.arcgis.com/en/pro-app/latest/help/mapping/properties/default-settings-for-new-maps-and-scenes.htm 2. When same data is added to Pro it is added only as a 2d layer, not as an elevation source. POTENTIAL MITIGATION: we are working on enhancements to the Elevation UX that will make this specific workflow more user-friendly. As you have identified, in current releases you must add the elevation twice (once as 2d layer, once as an elevation source or surface) to get equivalent behavior to ArcScene with the DEM added "on itself". Lastly, vertical exaggeration is available in Pro as well. YOu can adjust it from the Elevation Surface's "appearance" tab: https://pro.arcgis.com/en/pro-app/latest/help/mapping/properties/elevation-surfaces.htm Hope this helps! Please let me know if you have any further questions regarding elevation surfaces in Pro or suggestions for future enhancements.
... View more
04-28-2022
10:02 AM
|
0
|
0
|
4039
|
|
POST
|
Trevis, Unfortunately this appears to be a bug. Blend modes are complicated because _some_ of them are natively supported in PDF, but some are not. Looks like for some reason the combination of Map Series AND blend modes does not work properly. We've logged an issue for our developer to evaluate for next release. In the meantime, have you tried using the "export as image" option? Since this uses rasterized results of rendering, it _may_ retain the effects of blend modes better than trying to use native support in Adobe Acrobat.
... View more
04-27-2022
02:58 PM
|
0
|
0
|
2147
|
|
IDEA
|
thanks for clarifying, Jakub. Let me correspond with the responsible team - this does appear to be some AA applied here which is unexpected. can you verify that AA and hardware antialiasing are both disabled in display options when you add the TIFF to Pro again?
... View more
04-26-2022
10:13 AM
|
0
|
0
|
3488
|
|
POST
|
Hello all, FYI: The upcoming release of ArcGIS Pro (3.0) has a long-awaited fix that will clip content just outside the map frame boundaries, which greatly reduces the amount of data written to vector exports such as PDF and AIX. We also made some improvements to performance during this release. We also made similar performance enhancements in previous releases (2.8 and 2.9) so if you're not on the latest public release, you might consider updating.
... View more
04-25-2022
10:37 AM
|
1
|
2
|
2447
|
|
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
|
3522
|
| 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 |
Offline
|
| Date Last Visited |
3 weeks ago
|