Categories
Orienteering

Top 10

Okansas is doing a Top 10.

Here’s my Top 10 Areas I ran on in 2006:

10. Hindleap Warren (enjoyable, felt good.)
9. South Ashdown Forest (satisfying battle against the weather.)
8. Hatfield Forest (a breakthrough race for me.)
7. Ilkley Moor – JK Day 1 (moorland but intricate.)
6. Druskininkai – JWOC Spectator Races Day 5 (so fast but so hot!)
5. Leith Hill – Varsity Match (always an interesting area.)
4. Temple Newsam – JK Sprint (fast, scenic.)
3. Trockener Steg – Swiss O Week Day 3 (unique glaciated terrain.)
2. Oxford City Centre – Street Race (home advantage.)
1. Epping Forest North (and not just because I won it!)

Merry Christmas!

East Lothian under Freezing Fog (4722)

Categories
Uncategorized

Ashtead and Epsom Commons MV District Event, 17 December

Brown Course, 9.22k/105m, 70:13, 7.6mpk, 8th/28 finishers.

Categories
Notes

Equipment

Here’s how I’m getting GPS tracks for my recent orienteering races.

I’m using a Navi GPS (£80) bought from Storage Depot, with an SD memory card (£15) to log the route.

I download the data as NMEA sentences via a memory card reader and then convert it to GPX with GPS Babel, and then upload it to RouteGadget. I can also convert it to KML for displaying on Google Earth, or use GPS Visualizer to create altitude-coloured images with dots showing each log point.

I’ve also bought a Holox (£35) off eBay; which, when it arrives, and when Nokia fix a bug in Python S60, I’ll be able to use with my mobile phone recording the data that it sends via Bluetooth. Unlike the Navi GPS, the Holox is ultra-sensitive and very fast at acquiring fixes. I have a Nokia N73 phone, I plan to use NMEA Info to record the data, which a friend has written. I’ve learnt a bit of Python so I’ll be able to hopefully add some orienteering-specific features, e.g. a minimalistic “Sports race” mode, or a “Race start/end” button, to the application.

Categories
Orienteering Events Log

Hindleap Warren SAX Regional Event, 3 December

M21S (Course 3), 7.4k/215m, 58:13, 7.9mpk, 3rd/58 C3 finishers.

Categories
Uncategorized

GPS Tracks and Orienteering Mistakes

I took my GPS on today’s orienteering event, and again it performed generally well.

I’ll write more about the event soon, but for now, here are the “signatures” of three of my mistakes today, as captured by GPS and shown on Google Earth (in an area with low resolution satellite imagery, which is why you can’t see the individual trees.) Note the scale – it’s only about 70m from the left to the right of the photo.

Control 10, approach from North: The Undershoot – Stopping too short, thinking you’re on the wrong line, head away, look back, oh, there it was in front of me after all.

Control 13, approach from East: The Lack of Attack Point – Slightly off line, no plan. Realise I’ve gone too far, double back but don’t know which way to turn, so go the wrong way. Then look at map and realise what’s going on.

Control 23, approach from West: The Overshoot – Misread map, path goes on further past the control approach than I thought – so I just turn off too late. Realise and turn around, there it is, back up the spur.

Here’s a map showing a dot for each second of the race – when the GPS receiver was able to get a fix. The start is the big green blob on the top right, the finish is the yellow blob to its left. (The trail to the north of these points is the walk to/from the assembly.) The general layout of the course is an anticlockwise loop – not a figure of eight.

The only section where there was no signal for a significant amount of time was very near the beginning – there are several gaps here. Once climbed to 170m, the signal remains good for pretty much the whole way round.