David,
The clip region functionality is enabled with three choices that you can find in the Map Options dialog. These are called Windows device clipping, Windows device clipping (no points or text) and Erase Outside (no points or text). They all will have different impacts on the size of data sent to print which in your case is to a PDF file.
The Windows device clipping is the default and simply means that we take your clip region and pass it along to Windows to clip at the device level. This is usually the fastest way to do things. The clipping happens graphically so text, line styles, fills and symbols are clipped wherever they fall. The implementation is out of our hands ;that is Windows or even a particular driver is free to do this as it sees fit.
In general most devices simply remember the clip region and handle the clipping at display time. What this means is that all the data that would have normally been sent to the device is remembered as well as the clip region itself. If the clip region itself is dense, it could easily add to the total . If you had an expectation that the clipped data is not being stored, that would also be wrong.
The Erase Outside option is our oldest method of implementing this feature. It goes back to Version 4 (1995), I believe. This method uses the Erase Outside object processing code to eliminate the actual spatial data outside the clip region. As text glyphs and symbol fonts are graphic and not spatial data, these objects are simply skipped. It was originally felt better to skip them than cut some of them in half. The same also goes for wide line styles! Basically, the clipping is done at the object processing level.
This might solve your problem but depending on the complexity of your data, could be much slower to print to the .PDF and draw on screen. Neither the data outside the region nor the clip region itself is stored. If the clip region is complex, the boundaries that it intersects will inherit the complexity of the clip edge just like in object processing.
The other option is simply a way we added to get the similar behavior to the object processing method but much faster to draw. It uses the same technology as device clipping but purposely skips points and text to be compatible with the old behavior. I have no idea if this is much used but it will not help you reduce the size of the .PDF. It will almost certainly increase it. It is also possible that you are using this option as a default which could be your answer right there! This feature is set in each map window but is initialized by a preference. It is possible that you have this set.
I hope this helps.
Eric Blasenheim
Principal Software Architect
MapInfo Corporation
Mail List:[EMAIL PROTECTED]
| From: | "David Reid" <[EMAIL PROTECTED]> on 06/19/2006 04:32 AM |
| To: | <[email protected]> |
| cc: | |
| Subject: | [MI-L] Clip region bloats PDF |
Greetings List,
I've never really noticed this before until tonight when I needed to email a
PDF to a client. The workspace happens to have a clip region set and I've
found this bloats the otherwise casual 28kb layout PDF to just over 1mb.
Ok, I fell back and punted and just clipped my own region in the cosmetic
layer. Doesn't look quite as pretty and I had to delete several dynamic
labels that still showed.
Is there some setting, or other solution around this PDF bloat when a clip
region is active?
MI v6.5 by the way.
Thanks,
Dave
--
Outgoing mail is certified Virus Free
Checked by AVG Free Edition.
Version: 7.1.394 / Virus Database: 268.9.0/368 - Release Date: 06/16/2006
_______________________________________________
MapInfo-L mailing list
[email protected]
http://www.directionsmag.com/mailman/listinfo/mapinfo-l
_______________________________________________ MapInfo-L mailing list [email protected] http://www.directionsmag.com/mailman/listinfo/mapinfo-l
