Course Setting Guidelines for GPS
GPS-based punching of controls is not as precise as SportsIdent or similar physical-touch technologies.
Given the inherent error in GPS positioning, controls will "punch" at slightly different locations for different runners.
This has implications for course setting.
One approach that event organisers can take is to set the requirement that runners physically touch the control feature with their hand, independent of where the beep is received from the App detecting proximity to the control. This removes the variability factor and means that the App is really just confirming a visit to a control... not the precise location.
Following are some course setting guidelines for GPS Orienteering:
For more information, please email: support@maprun.net
Given the inherent error in GPS positioning, controls will "punch" at slightly different locations for different runners.
This has implications for course setting.
One approach that event organisers can take is to set the requirement that runners physically touch the control feature with their hand, independent of where the beep is received from the App detecting proximity to the control. This removes the variability factor and means that the App is really just confirming a visit to a control... not the precise location.
Following are some course setting guidelines for GPS Orienteering:
- Think about orienteers running to the circle – not to the specific control site (ie due to the tolerance factor and the inaccuracy of the GPS location, the runner can register a hit somewhere in the circle –exact spot unknown)
- Avoid controls that you couldn’t see from a satellite – ie down between tall buildings
- Avoid controls where the challenge relies upon fine detail – eg inside/outside an un-crossable fence; top level vs lower level in a multilevel site; inside a wall vs outside
- Avoid “out and back” controls – because some runners will get an early GPS hit and others will not. (unless the organiser adopts the approach of "touch the feature".)
- It is fine to position the Finish at the same location (or near) the Start. The Finish will not punch until at least one other control has been punched. However, the layout of the course/scatter should be that runners are not likely to run past the Finish on the way to another control (except on the way to their first control), as visiting the Finish will end the event for the runner. Accordingly it is best to put the Finish near the edge of the map, or in a location that is not a run-through location.
- It is recommended that controls be at least 50m apart.... or at least two times the tolerance that is set for the event eg 2 x 15m (with some extra for GPS tolerance). This is to avoid MapRun being "within range" of two (or more) controls at the same time. If this occurs, MapRun will rapidly punch the controls it is close to in alternating succession. Although this does not make the run invalid, it does create a large number of unnecessary punches and can cause confusion for the runner.
- For a pivot control in a line course, set the control location pin (eg control 45), then copy this location pin and put it in the sequence order as a duplicate. For example the KML file would have a sequence of pins, as follows: S1, 31, 34, 45, 33, 32, 45, 44, F1. This would give a loop from 45 to 33 to 32 and back to 45. DO NOT put two controls with different numbers at the pivot point, as this will create the issue mentioned above.
For more information, please email: support@maprun.net