ArcGIS Labeling to Illustrator
Posted 03 March 2008 - 07:02 PM
Posted 03 March 2008 - 07:03 PM
I wouldn't think it would be that much of a problem - resolution shouldn't affect it as should all be vector. I'd go with 7200 to avoid rounding errors. Does the exported PDF look ok in Acrobat?
You don't have a transparency applied to the text do you making it rasterize.
The map is of entire Orange County, California (US) so the small street annotation is huge at 1200. Illy could not barely open it at 300dpi, but then the annotation was worthless anyway.
Yes - I can print the entire map, annotation and all, as a PDF and it looks great, but Illy (CS3) doesn't open it - it REALLY TRIES though
I found a solution though, in case others face this: I clipped the road layer into smaller blocks (in my case 5), then created annotation in a geodatabase. Then I could turn on one annotation group and export at a time. This was small enough for AI to open.
Posted 04 March 2008 - 09:21 AM
Posted 09 April 2008 - 09:05 AM
You need to be careful with just using the term 'Maplex', and it rather depends when (and what) that 'admission' was, and what it applied to.
I used Maplex with very complex rules with much success - however by ESRI's own admission, Maplex breaks down on page sizes greater an E.
The original standalone Maplex product certainly had had limits on the size of internal arrays that limited its usefulness on really big maps. When the heart of the Maplex engine code was spliced into ArcGIS at 9.0 to make the Maplex Label Extension (MLE), then some of those limits went. At 9.0, the engine code was refactored from the original Fortran into C++, and other limits went. At 9.2, the MLE internals were reengineered to be much more modular, and more restrictions disappeared. At 9.2 also, MLE was made available in ArcGIS Server, and hence had to be able to handle bigger datasets. Those processes have continued in 9.3, in which various new placement capabilities have been added to Maplex. In addition, memory sizes and other architectural limits on computer hardware and operating systems have also evolved.
So, I think it's well worth trying Maplex capabilities again.
Caveat: I speak not officially on behalf of ESRI, but based on my personal experience with Maplex and its software development staff over a more than ten-year period.
ESRI Europe (firstname.lastname@example.org)
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users