Publishing an Event to MapRun
This page describes the steps after you have a KMZ (Map) and a KML (Course) ready to use in the MapRun6 App.
The files can either be published to the MapRun server for general access as described below.
Normally you will want to test your course and maybe experiment with options/settings.
To do this use "CheckSites" - MapRun - CheckSites
Alternatively if you are using an Android device, you can copy the files from your PC/Mac to a particular folder on the device. Generally, CheckSites is a better option.
With CheckSites you can share a confidential 6-digit code with others to test the event, or even to run a simple demonstration event. Remember however, that anyone you send the event to, can change any options/settings so everyone may not be using the event in exactly the same way. (as CheckSites is targeted at checking, testing and experimenting).
Publishing on the MapRun Server
To make an event available publicly for all users of MapRun, it is published to the MapRun server.
This step is normally be undertaken by a local Administrator who has been given access to the MapRun server. If your club/association does not have a local Administrator and you would like to have one, provide details to: [email protected].
If you request to become a local Administrator, normally we ask you to send us a CheckSites code to show that you have successfully been able to create compatible map and course files.
The local Administrator will publish the event either as a draft for your checking or as the final. They will send you back:
More detail on how Administrators publish events is provided in the Administrator section of this website.
Confidentiality Prior to the Event
The event will normally be protected with a 4-digit PIN, which is announced just prior to start time on the day of the event. The setter/organiser will be told this PIN to allow them to do any testing they want to do in advance.
Producing a Printed Map/Course
To reduce the chance of discrepancies between the App and the printed map/course (and the physical placement of SI units if applicable), it is best to derive the printed Map/Course from the Purple Pen files mentioned above.
Options for printing are described below:
1. Purple Pen (Preferred Method)
When your local Administrator publishes the event to the MapRun server, they can download the Purple Pen files that match the files that were uploaded.
Open the Purple Pen file and make any final cosmetic adjustments (eg print area, the position of labels on the controls, control description table if applicable) and print the course.
2. Print from Google Earth (Alternative Method)
To print the map/course directly from Google Earth:
To get the best quality map, expand the display on the screen to as large as possible (on your largest screen) before using a tool such as Windows Snipping Tool or Mac – Shift-Command-4 to select a rectangular area close to the boundaries of the map on the display.
For more information, please email: [email protected]
The files can either be published to the MapRun server for general access as described below.
Normally you will want to test your course and maybe experiment with options/settings.
To do this use "CheckSites" - MapRun - CheckSites
Alternatively if you are using an Android device, you can copy the files from your PC/Mac to a particular folder on the device. Generally, CheckSites is a better option.
With CheckSites you can share a confidential 6-digit code with others to test the event, or even to run a simple demonstration event. Remember however, that anyone you send the event to, can change any options/settings so everyone may not be using the event in exactly the same way. (as CheckSites is targeted at checking, testing and experimenting).
Publishing on the MapRun Server
To make an event available publicly for all users of MapRun, it is published to the MapRun server.
This step is normally be undertaken by a local Administrator who has been given access to the MapRun server. If your club/association does not have a local Administrator and you would like to have one, provide details to: [email protected].
If you request to become a local Administrator, normally we ask you to send us a CheckSites code to show that you have successfully been able to create compatible map and course files.
The local Administrator will publish the event either as a draft for your checking or as the final. They will send you back:
- the PIN for the event (if one was required), and
- the Purple Pen files to allow printing of paper maps.
More detail on how Administrators publish events is provided in the Administrator section of this website.
Confidentiality Prior to the Event
The event will normally be protected with a 4-digit PIN, which is announced just prior to start time on the day of the event. The setter/organiser will be told this PIN to allow them to do any testing they want to do in advance.
Producing a Printed Map/Course
To reduce the chance of discrepancies between the App and the printed map/course (and the physical placement of SI units if applicable), it is best to derive the printed Map/Course from the Purple Pen files mentioned above.
Options for printing are described below:
1. Purple Pen (Preferred Method)
When your local Administrator publishes the event to the MapRun server, they can download the Purple Pen files that match the files that were uploaded.
Open the Purple Pen file and make any final cosmetic adjustments (eg print area, the position of labels on the controls, control description table if applicable) and print the course.
2. Print from Google Earth (Alternative Method)
To print the map/course directly from Google Earth:
- Rotate the map to have Magnetic North vertical and scale it to fill the screen
- Do a screen capture of the map into a jpg file
- Print the jpg file
To get the best quality map, expand the display on the screen to as large as possible (on your largest screen) before using a tool such as Windows Snipping Tool or Mac – Shift-Command-4 to select a rectangular area close to the boundaries of the map on the display.
For more information, please email: [email protected]