Map Files

RG2 accepts GIF and JPG formats. There is a balance between the size of the map file (bigger means that it will load slower) and the quality of the display.If you end up with very fine course overprint it is probably because your map file has been generated at too high a resolution.

I generate most maps using OCAD. Recommended settings are to export as a GIF at 150 or 200 dpi. This is OK even for very detailed maps, and gives reasonable file sizes. Nearly all events should be able to get to a file size of under 1Mb without compromising the map quality. Try to avoid files over about 2Mb since these take a long time to load (especially on mobile devices) and offer little benefit.

Other things to consider:

• There is little point in going above 200 dpi. It just increases the file size and makes the course overprint very small, without any useful increase in image quality.
• Maps should never need to be more than about 3500 pixels high or wide. This size is perfectly adequate for A2 mountain marathon maps if the settings are adjusted correctly.
• If you do use JPG then set the quality down to 50% or lower. Again this doesn't have a great impact on image quality, but does reduce the file size.
• Don't forget to generate a world file along with the image if the map is georeferenced. You need to tick a separate box in OCAD to do this.

One of the added benefits of Routegadget is being able to compare a wide range of map layouts and cartographic styles. I am always disappointed when I see a map that has been cropped so that just the area used for the courses is visible. This is almost certainly because of worries about file size. If you follow the guidelines above you should be fine even for A3 maps, so please try to use the whole map if possible.