Troubleshooting KMZ Files
Background:
The KMZ format is a very broad and flexible format that can hold many different types of content. For example you can zip-up a map, a course and track all in one KMZ file. However, for maps for MapRun, the KMZ content and format needs to be the same as is produced by the leading Orienteering Mapping system (OCAD). Tiling is preferred, but not mandatory. The file size should normally be in the range 1MB to 2MB (and definitely no larger than 5MB).
KMZ files can be produced by a wide variety of tools, but each may have their own nuances.
Troubleshooting Steps:
If you are having problems we suggest:
1. Open your KMZ file in Google Earth and see if there is anything obviously wrong. For example the KMZ should only contain map tiles and NOT have any other content like a course, or pins or tracks.
2. Unzip the KMZ file and check its contents (change .kmz to .zip and use a standard unzip tool). Then compare the contents very carefully with the specification given at: http://maprunners.weebly.com/uploads/6/8/6/6/6866500/technical_overview_-_extract_-_file_formats_v1.pdf (Note that all details including naming of tiles is important ie tile_1_2.jpg)
3. Alternatively, create a simple untiled KMZ, using your preferred tool. Then run it through the tiling routine at: http://www.p.fne.com.au/rg/cgi-bin/o-utils.cgi . This can help get the format aligned.
4. You can create a KMZ file from an image file version of your map (eg jpg). Using: https://console.maprun.net/#/kmz_create . This is like the KMZ Create function in MapRunF and MapRun6, but has more options.
5. Remember that the KMZ doesn’t need to be perfect, as MapRun doesn’t use it except to display on the screen. (Especially if you are providing printed maps created from a separate source).
6. If you are planning to use CheckSites for your event, then you don’t actually need to load a KMZ file into MapRun. (But you do need a KMZ for a published event)
7. If you have a KMZ file that works correctly with CheckSites, but then gives an error when publishing it as the map for a public event (using the Admin Console), check the following. The creation of the RouteGadget “Event” to display results for a published event involves interpreting the geo-referencing info in the KMZ file. This can fail if there are less than 3x3 tiles in the KMZ file. In such cases, either use an un-tiled version of the KMZ file, or increase the dots-per-inch when creating the KMZ (or reduce the tile size to say 256x256 or 128x128),If so that there are more tiles in the KMZ file.
8. If you are printing maps for runners, and are happy to have a simpler map on the screen, and as the background for you are printing tracks in the results, you can meet the MapRun requirements to have a KMZ file using the www.oomap.co.uk site, whilst still using your detailed map for the printed version. If this is the case, in MapRun6 Administrators have the option to not display the map screen at all.
9. Failing that, consider posting a question (and potentially your files) to the MapRun Forum to seek assistance from others.
10. Finally, if you think there is a bug or you are still stuck, send the details (including reference to the above points) to [email protected].
The KMZ format is a very broad and flexible format that can hold many different types of content. For example you can zip-up a map, a course and track all in one KMZ file. However, for maps for MapRun, the KMZ content and format needs to be the same as is produced by the leading Orienteering Mapping system (OCAD). Tiling is preferred, but not mandatory. The file size should normally be in the range 1MB to 2MB (and definitely no larger than 5MB).
KMZ files can be produced by a wide variety of tools, but each may have their own nuances.
Troubleshooting Steps:
If you are having problems we suggest:
1. Open your KMZ file in Google Earth and see if there is anything obviously wrong. For example the KMZ should only contain map tiles and NOT have any other content like a course, or pins or tracks.
2. Unzip the KMZ file and check its contents (change .kmz to .zip and use a standard unzip tool). Then compare the contents very carefully with the specification given at: http://maprunners.weebly.com/uploads/6/8/6/6/6866500/technical_overview_-_extract_-_file_formats_v1.pdf (Note that all details including naming of tiles is important ie tile_1_2.jpg)
3. Alternatively, create a simple untiled KMZ, using your preferred tool. Then run it through the tiling routine at: http://www.p.fne.com.au/rg/cgi-bin/o-utils.cgi . This can help get the format aligned.
4. You can create a KMZ file from an image file version of your map (eg jpg). Using: https://console.maprun.net/#/kmz_create . This is like the KMZ Create function in MapRunF and MapRun6, but has more options.
5. Remember that the KMZ doesn’t need to be perfect, as MapRun doesn’t use it except to display on the screen. (Especially if you are providing printed maps created from a separate source).
6. If you are planning to use CheckSites for your event, then you don’t actually need to load a KMZ file into MapRun. (But you do need a KMZ for a published event)
7. If you have a KMZ file that works correctly with CheckSites, but then gives an error when publishing it as the map for a public event (using the Admin Console), check the following. The creation of the RouteGadget “Event” to display results for a published event involves interpreting the geo-referencing info in the KMZ file. This can fail if there are less than 3x3 tiles in the KMZ file. In such cases, either use an un-tiled version of the KMZ file, or increase the dots-per-inch when creating the KMZ (or reduce the tile size to say 256x256 or 128x128),If so that there are more tiles in the KMZ file.
8. If you are printing maps for runners, and are happy to have a simpler map on the screen, and as the background for you are printing tracks in the results, you can meet the MapRun requirements to have a KMZ file using the www.oomap.co.uk site, whilst still using your detailed map for the printed version. If this is the case, in MapRun6 Administrators have the option to not display the map screen at all.
9. Failing that, consider posting a question (and potentially your files) to the MapRun Forum to seek assistance from others.
10. Finally, if you think there is a bug or you are still stuck, send the details (including reference to the above points) to [email protected].