MapRun Event Builder

What if we could reduce the amount of work required for Street Orienteering course setting?
If we could eliminate or reduce some of the errors that creep into street
orienteering courses - controls on the wrong side of the road or too far down a long street, 
a course that's missing a control number or one with two control 14's?

What if we could make course setting so easy, even Ian Greenwood could get it right?

Build your Event
using Google Earth

or capture Waypoints
using a Garmin GPS

Define courses
in the 
Event Builder

Import courses
into OCAD and MapRun 


Introducing - the MapRun Event Builder

Mobirise

The MapRun Event Builder - An Overview

How does it work?

  • Create your Control Locations
    The easiest way to do this is to use Google Earth Pro (GEP); anything that is identifiable from the air can be used as a control/checkpoint. A key advantage of GEP is that it allows you specify a control description as you create each control.

    See the Google Earth Page for more information.
  • What if I can't see a feature from the sky?
    Look around in Street-View and find other features that might help you to Add a Placemark accurately (Never use street-view to Add a Placemark - the parallax errors that occur can introduce significant errors in the position recorded). 

    Alternatively, you could use a GPS such as a Garmin eTrex to record locations; many GPS units allow you to find a very accurate position by taking the average of many readings.

    See the Garmin GPS Page for more information.
  • Import your locations into the Event Builder
    The Event Builder can import control locations from Google Earth and from many Garmin GPS Units.

    See the Event Builder Page for information on how to import control locations.
  • Specify the Courses you want                        
    The Event Builder supports most streetO event formats being used in Melbourne - score courses of various durations, scatter courses, rogaines and metrogaines. MapRun is incredibly fussy about the format of the name - if you specify what you want, the Event Builder will build the correct filename for you.

    In addition, the Event Builder carries out basic validation checks for you - it makes sure that you've specified start and finish locations, it checks that all controls from 1 to 20/25 (or whatever) are present and that no controls appear more than once.

    See the Event Builder Page for information on Course Selection, File Naming and validation.
  • Generate the files required
    If your event setup and course information are valid, it's now time to generate the files required by MapRun and OCAD.

    MapRun needs KML files (one for each course) - these contain the locations of the start, finish and all of your controls. If your OCAD map is georeferenced, the GPX gile generated by the Event Builder can be imported into OCAD and will instantly create control circles and control numbers at the locations that you specified. 

    See the Event Builder Pages for information on exporting files to MapRun and OCAD.
  • Import Controls and Control Descriptions into OCAD
    If your OCAD map is georeferenced, the GPX gile generated by the Event Builder can be imported into OCAD and will instantly create control circles and control numbers at the locations that you specified.

    Finally, you can also import Control Descriptions into your OCAD Map. 

    For more information, see the OCAD Pages.

Download the
Event Builder

Please report any issues or suggested improvements to Geoff at [email protected]

Mobirise website builder - See it