Note that if you have used 0-width lines in your map, they will turn out very thin in the final image. I then take the high res image and reduce it to 1280 in the largest dimension to put it in as the image for the atlas. I always render to the hi-resolution version (which is always 8192 pixels in the largest dimension), rendered with 10% antialias. Many of the atlas maps does not look proper at all if effects are off. I then turn on effects, and enables the 'Effects are on when loaded' setting, so that when people browse atlas maps (the real thing, not the web preview) maps are loaded with effects on.Makes things look a bit nicer if the user access the symbol manager. I then run PURGESYM (Purge symbols) on the map to drop any symbol definition copied into the map that is not in use.Again, the problem with fill style resolutions are mostly an issue if the mapper imported fill styles from other map styles, especially if that style was designed for a completely different detail level. This is also a performance thing, so I need to be carefull not to lower them too much, you generally don't need the VH quality fills to be the ones loaded when the map is zoomed completely out, that is only needed when you zoom in. If this happens, I need to access the fill style resolution settings from the display speed dialog, and reduce the values until the fills stop pixelating. This is something the original mapper wouldn't notice if they were using the wrong style paths (# instead of but once that is fixed, the fill style resolution issue is visible. Once I do this, I often also notice that the fill style resolution in the map is wrong. Running FFIX converts all of the #-style paths to paths (and more) automatically. Proper path is also what people expects from a CC3+ map. Since the #-references only partially work (they generally load the fill, but they don't handle the dynamic resolution system properly, which leads to performance issues), I need to update them. A lot of the maps I get uses old CC3 installation directory style paths (#) instead of the CC3+ data directory style paths ( I notice this is especially prevalent when people add fills styles from other map styles.
I start by running the FFIX command on the map.If this happens, I need to return the map to the mapper for fixing. This means that if I see red X'es, the mapper have used symbols or fills from an invalid source. I load the map up in a dedicated CC3+ installation for the atlas, which only contains the allowed atlas resources.This also contains some observations that may be interesting to those submitting maps, and small stuff you can do to make my job easier. So, I just wanted to talk a little bit of what I do behind the scenes when you submit an atlas map, in case anyone is interested.
0 kommentar(er)
