Start Anywhere (needs MapRunF 4.8.8 or later)
In addition to any of the other event type parameters, the organiser can designate an event to allow runners to start at any control on the course.
The first control that a runner visits becomes the start and finish control for their run. The course is dynamically reconfigured as soon as the runner visits the first control and the updated course is shown in the main run screen in MapRunF.
The first control that a runner visits becomes the start and finish control for their run. The course is dynamically reconfigured as soon as the runner visits the first control and the updated course is shown in the main run screen in MapRunF.
Where Would this be Used?
When travel to a common start location is restricted, it may be possible to set a course in an urban or park setting that allows people to start from "close to their front door".
Also for some "permanent" courses, the added flexibility may be beneficial.
Types of "Start Anywhere"
Each course still has the characteristics of its main event type:
Details
Organisers of "Start Anywhere" events should be aware of the following points:
Setting the event to be "Start Anywhere" - The controls should be defined in the usual way, including an S1 (Start) and F1 (Finish). Then use the options for MapRunF in the new Admin Tool to set the event to be "Start Anywhere". There is NO defined code for the event name that activates this feature, but you should put something in the name of the event that tells runners that "Start Anywhere" is available. For example: "My Favourite Line Course PXAC Start Anywhere".
MapRunF 4.8.8+ Required - All runners need to be using MapRunF version 4.8.8 or later to be able to start at any control. As there is a normal S1/F1, runners with MapRun or earlier versions of MapRunF can still run the course, but they need to start at S1 and finish at F1 in the normal way.
Co-locate S1 and F1 - It is highly recommended that S1 and F1 be co-located. The reason is explained by considering a line course S1, 31, 32, F1. A runner starting at S1 runs 3 legs (S1-31, 31-32, 32-F1). A runner who starts at 31, has the course re-configured as Start@31, 32, 33@S1, Finish@31. So to make the two runs equivalent, ensure that S1 and F1 are at the same location.
Limitations regarding Pivot Controls on Line Courses - It is recommended that organisers avoid loops in line courses used with "Start Anywhere". If there are loops and the runner attempts to start at a pivot control, that control becomes Start and Finish, and so when they return to that control, they will punch Finish (and end their run).
Limitations regarding HITMO - The "Hey I Think it Missed One" function to add missed controls to a run, does not work with Start Anywhere.
Starting at the Finish - As above, it is highly recommended that S1 and F1 be co-located. If S1 and F1 are NOT co-located, the runner should not start at the Finish as this scenario is invalid.
Splits Results - MapRun does not attempt to re-align legs in the results with what would have been a normal Line Course run (starting at S1). Therefore in comparing splits, it is important to consider which control each runner started from. Similarly comparing splits in a scatter event requires matching end-points.
A new control number: When a runner starts their run from a control other than S1, MapRun immediately re-configures the course as follows:
Tag-based Punching (MapRun6 6.3.9+): If tag-based punching is being used (QR code or NFC tag), even though the course can be dynamically changed on the screen of the phone, the QR codes or NFC tags at each location will remain unchanged. MapRun does the translation of the tag at each site to the reconfigured course as the tag is scanned, and will display the correct punch on the reconfigured course. In particular:
- If the runner approaches 31 first, it will punch and display "S1 punched"
- If the runner then approaches S1 (or F1), it will punch as the new normal control eg "35 punched"
- When 31 is approached again, it will punch as the Finish (F1) .
When travel to a common start location is restricted, it may be possible to set a course in an urban or park setting that allows people to start from "close to their front door".
Also for some "permanent" courses, the added flexibility may be beneficial.
Types of "Start Anywhere"
Each course still has the characteristics of its main event type:
- Line Course - traditional orienteering format, with the winner being the fastest to visit the controls in the defined sequence (Code: PXAC). "Start Anywhere" is most directly applicable to a Line Course format, as no matter where the runner starts, they will run all of the same legs as any other competitor, just not all in the same order.
- Scatter - visit controls in any order, with the winner having the fastest time. (Code: PXAS). The comparability of runs starting at different start locations depends on how homogeneous the layout of the course is. For example if there is a tight cluster of controls in the Northern part of the map, then a runner starting at a control in the North, would have an advantage over someone starting in the South. So although Scatter events are allowed, it is up to the setter to maximise the fairness of a start from any control.
- Scatter (Specific Number) - visit the designated number of controls (from a larger set), with the winner having the fastest time eg any 16 controls out of 20. (Code: PXASxx where xx would be 16 in this example). As per Scatter.
- Score - visit as many controls as possible in a defined time period, gaining points per control, with the winner having the highest points score. (Code: ScoreXyyy - where ScoreX is described at Scoring Schemes and yyy is the time in minutes). As per Scatter.
Details
Organisers of "Start Anywhere" events should be aware of the following points:
Setting the event to be "Start Anywhere" - The controls should be defined in the usual way, including an S1 (Start) and F1 (Finish). Then use the options for MapRunF in the new Admin Tool to set the event to be "Start Anywhere". There is NO defined code for the event name that activates this feature, but you should put something in the name of the event that tells runners that "Start Anywhere" is available. For example: "My Favourite Line Course PXAC Start Anywhere".
MapRunF 4.8.8+ Required - All runners need to be using MapRunF version 4.8.8 or later to be able to start at any control. As there is a normal S1/F1, runners with MapRun or earlier versions of MapRunF can still run the course, but they need to start at S1 and finish at F1 in the normal way.
Co-locate S1 and F1 - It is highly recommended that S1 and F1 be co-located. The reason is explained by considering a line course S1, 31, 32, F1. A runner starting at S1 runs 3 legs (S1-31, 31-32, 32-F1). A runner who starts at 31, has the course re-configured as Start@31, 32, 33@S1, Finish@31. So to make the two runs equivalent, ensure that S1 and F1 are at the same location.
Limitations regarding Pivot Controls on Line Courses - It is recommended that organisers avoid loops in line courses used with "Start Anywhere". If there are loops and the runner attempts to start at a pivot control, that control becomes Start and Finish, and so when they return to that control, they will punch Finish (and end their run).
Limitations regarding HITMO - The "Hey I Think it Missed One" function to add missed controls to a run, does not work with Start Anywhere.
Starting at the Finish - As above, it is highly recommended that S1 and F1 be co-located. If S1 and F1 are NOT co-located, the runner should not start at the Finish as this scenario is invalid.
Splits Results - MapRun does not attempt to re-align legs in the results with what would have been a normal Line Course run (starting at S1). Therefore in comparing splits, it is important to consider which control each runner started from. Similarly comparing splits in a scatter event requires matching end-points.
A new control number: When a runner starts their run from a control other than S1, MapRun immediately re-configures the course as follows:
- The control initially approached becomes S1 and F1
- The following legs are those that followed from this control to last leg of the original course
- Instead of the last leg going to F1, it now goes to the original S1 to connect to the remainder of the course. (So it is important to co-locate S1 and F1 to make this scenario the same as the original last leg being to F1.)
- The original S1 is renumbered to a new control number, being the highest control number on the course plus one.
- The legs after this control, are the legs from the original S1 to the control that is now the new Start.
Tag-based Punching (MapRun6 6.3.9+): If tag-based punching is being used (QR code or NFC tag), even though the course can be dynamically changed on the screen of the phone, the QR codes or NFC tags at each location will remain unchanged. MapRun does the translation of the tag at each site to the reconfigured course as the tag is scanned, and will display the correct punch on the reconfigured course. In particular:
- If the runner approaches 31 first, it will punch and display "S1 punched"
- If the runner then approaches S1 (or F1), it will punch as the new normal control eg "35 punched"
- When 31 is approached again, it will punch as the Finish (F1) .