Presentation is loading. Please wait.

Presentation is loading. Please wait.

Routegadget analysis By: Matt Radford. Time loss per leg The following graph are taken from winsplit (pro version). They show the average time loss per.

Similar presentations


Presentation on theme: "Routegadget analysis By: Matt Radford. Time loss per leg The following graph are taken from winsplit (pro version). They show the average time loss per."— Presentation transcript:

1 Routegadget analysis By: Matt Radford

2 Time loss per leg The following graph are taken from winsplit (pro version). They show the average time loss per leg. It provides a good overview of what controls people found hard and which was were a bit easier. It is quite interesting to see that it was the shorter controls that seemed to give people the most problems.

3 Red Long

4 Red Medium

5 Red Short

6 Route options I have added a few of the legs where there was major differences in route choice or were difficult for people. Route distance is calculated by taking the shortest distance between controls. Competitors actual distance may vary. On some control the routes are drawn on by me

7 Start to 110 - Red Long #1 - Red medium #1 A -

8 Start to 110 aka “spaghetti junction” A - This control was very tricky to find due to the dense undergrowth. In hindsight I would have taken the orange path (only one person did). It would have been slower but much much less room for getting off course and getting sucked into the undergrowth.

9 Control 132 (clever track-tics) Red long 7

10 Control 132 (clever track-tics) A C B LengthClimb A1253m85m B1200m75m C1025m90m I took me a lot of thinking on the day to decide which way to go and still I am unsure. C is much shorter but the climb at the end was very steep and slow going. The last 250m took me 4 minutes!!

11 Control 131 (Gully-able)

12 Most people seemed to get tricked into the wrong gully to the east. The average time lost was 4:32 for a leg that’s only 170m

13 Control 123 “start-two- ed” - Medium red control 9

14 A B C DistanceClimb A1145m75m B882m45m C930m45m C is slightly longer but much quicker running than B. Therefore overall probably about the same

15 Control 122 “around the hill” - Red short control 5

16 DistanceClimb A951m45m B673m20m A A B A has slightly less climb and longer but quicker running. Overall it's hard to tell which is quicker. Depends on how fast you can run through the forest vs the track.

17 Climb - As a simple rule for every 1m of climb it equals 6m of flat running i.e. 20m climb its equal to 120m flat running. Although obvious a lot of variables will effect this e.g. running ability, terrain etc but it is a good general rule - This data comes from the scientific journal of Orienteering 2005. Yes! There is actually an orienteering journal http://orienteering.org/resources/publications/scie ntific-journal-of-orienteering/

18 Summary Overall the map is very steep and the undergrowth is thick in places and under represented on the map. Taking the tracks was definitely key and even if the distance was much longer it was quicker than struggling through the forest.

19 Quick route http://www.matstroeng.se/quickroute/en/ This is a interesting programme for those people with GPS devices to look at their routes.

20 Here is a snapshot of my run. The colour dipicts speed which is also shown along the bottom graph. You can also look at a lot more stuff. To get the map as a background you can either scan it, take a photo of it or I can send you a computer version of it. Split times can also be added from winsplits (under tools)

21 You can also open your route in google earth. This doesnt really add much but looks cool.

22 Even cooler is a little known tool of google maps, which is flight simulator mode (under tools menu). This is what the Tangoio map looks like at 31000 feet in a F-16 fighter jet.

23 Till next time Please continue to upload your routes to route gadget http://www.routechoice.co.nz/gadget/cgi-bin/reitti.cgi). The more routes the better. Adding comments to your route is a great idea. It adds valuable insight into your route choice If you have any questions, feedback or anything you would like me to add, please email me on mattradford13@gmail.com


Download ppt "Routegadget analysis By: Matt Radford. Time loss per leg The following graph are taken from winsplit (pro version). They show the average time loss per."

Similar presentations


Ads by Google