topic Re: AGO data error? in ArcGIS Maps for Adobe Creative Cloud Questions

AGO data error?

deleted-user-OlpHy1NoMNug — Mon, 22 Jan 2018 16:46:58 GMT

When I add content from our AGO site, the data displays with severe jagged edges. Is this a size restriction? Something in Illustrator? It's not really usable if this is the output from AGO-->Illustrator.

Scott

Re: AGO data error?

Xingdong_Zhang — Mon, 22 Jan 2018 16:58:18 GMT

Hi Scott,

Looks like the geometries of your data got simplified during the export. If you can share us with the data/webmap, we can investigate the problem on our end and provides a solution for it.

Thanks,

Xingdong

Re: AGO data error?

deleted-user-OlpHy1NoMNug — Mon, 22 Jan 2018 17:02:20 GMT

Sure, but it has happened with every layer I try. Does the map scale make a difference? I don't see why it would but I can't think of anything else.

Data layer: http://grvlsc.maps.arcgis.com/home/item.html?id=e2b2d444b98b402988e0a034e5963e27

Re: AGO data error?

deleted-user-OlpHy1NoMNug — Mon, 22 Jan 2018 17:08:58 GMT

If when creating the Mapboard I define a very small map scale, then the geometry looks much better. Is this the intended workflow? Since it's vector data, I'm not understanding why that would matter but it appears it does. Is it converted from raster at some point?

Re: AGO data error?

Xingdong_Zhang — Mon, 22 Jan 2018 20:02:53 GMT

Hi Scott,

Thank you for preparing the data. We are able to reproduce the issue and will be looking for a solution for it. To answer your question, the vector data is not scale dependent and there is no raster to vector conversion during the process.

Thanks,

Xingdong

Re: AGO data error?

deleted-user-OlpHy1NoMNug — Mon, 22 Jan 2018 20:10:20 GMT

Xingdong,

Thanks for taking a look.

Why does setting map a small scale seem to resolve it?

Scott

Re: AGO data error?

deleted-user-OlpHy1NoMNug — Wed, 31 Jan 2018 16:15:07 GMT

xzhang-esristaff,

Any progress on this? Is it registered as a bug? This is holding up production for us.

Scott

Re: AGO data error?

Xingdong_Zhang — Wed, 31 Jan 2018 16:37:39 GMT

Hi Scott,

The issue was logged as a high priority bug in our system. We are working on it and will get back to you as soon as possible.

Thanks,

Xingdong

Re: AGO data error?

Xingdong_Zhang — Wed, 31 Jan 2018 19:42:44 GMT

Hi Scott,

Vector data snaps to display pixel grid during export. So the issue is related to map export dpi setting. Try to bump up your setting to 300 dpi and see if the results meet your production requirements. You can also export the map in a large scale (increased level of detail) to have better results as you already know. If it is still an issue, we can increase the up limit in the incoming release.

Re: AGO data error?

RickBoggs1 — Wed, 11 Apr 2018 20:21:12 GMT

I also have this issue and notice in AGOL - depending on the scale, the polygon will be simplified to a degree. When we pull in the data to illustrator it pulls the simplified polygon at the scale it will fit within the artboard.

It doesn't matter if you up the DPI because it is still pulling the simplified polygon. Only when you zoom way into a feature does it draw without simplification... though this doesn't allow you to download all of the features in the project area.

Re: AGO data error?

ClintLoveman — Thu, 19 Apr 2018 22:45:49 GMT

Bogg2050 can you share a screenshot of the downloaded artwork in Ai of the polygon with the default dpi (96) and another of the polygon at 300 dpi?

Re: AGO data error?

RickBoggs1 — Fri, 20 Apr 2018 15:15:35 GMT

scale: 1:8,656 -

DPI 96

300 DPI

600 DPI

Re: AGO data error?

ClintLoveman — Sat, 21 Apr 2018 00:58:45 GMT

Thanks, where/how did you set the DPI to 600? This was outside of Maps for Adobe, correct? This indeed does look like the same issue as Scott Aulen‌ 's above. We've tracked this to a lower level limitation of ArcGIS Online Printing and Export, and we are looking to resolve this in a future release. Sorry for the inconvenience.

Re: AGO data error?

RickBoggs1 — Mon, 23 Apr 2018 14:35:53 GMT

Hey Clint,

hmm, looks like I didn't realize it reverted to 300 DPI if you try to set it above 300.

Glad you were able to track the issue down.