0
edits
Changes
→Map Background
Following the guidelines below, information managers can build easy-to-use, sustainable maps for visualising data in IMSMA<sup>NG</sup>:
<center>{| class="wikitable" width="600"|-| align="center" colspan="2" | '''Table 13. Guidelines for Designing Map Backgrounds'''|-| width="300pt" | '''Guideline '''| width="300pt" | '''Explanation'''|-| align="left" | Use only the layers you need || align="left" | When creating or customising maps, include only the layers necessary for map visualisation. Extra layers take up space and present users with unnecessary, confusing options. Consider tailoring specific maps for each user group, for example, building one map for MRE users and a separate map for operations staff.|-| align="left" | Limit raster layers || align="left" | Raster images take up a large amount of space compared to vector layers, causing slower system performance. Limiting the use of raster layers to one or two background images or turning them off by default can improve performance of the map display and IMSMA<sup>NG</sup> overall.|-| align="left" | Tile maps || align="left" | Breaking up a map into multiple images, or tiling them, allows users to turn individual sections on and off as needed, which results in improved performance.|-| align="left" | Back up the .MXD files || align="left" |Keep backups of map(s) in their state prior to importing them into IMSMA<sup>NG</sup>IMSMANG. This makes later map customisation easier and speeds up the process of importing the maps again.|}</center>
{{HowTo's
}}
{{note|Any changes made to IMSMA<sup>NG</sup> maps apply only to the client on which the changes were made. To make system-wide map changes for client-server installations, updated maps must be imported on each client installation}}
==Map Themes and Symbology==