homebrew orienteering

Notes on trail running

2015-05-27T22:29:00.001-07:00

40 SI sticks: 1400 USD.
Measuring wheel: 110 USD.
Banners: 40 USD
Inverter: 50 USD
Deep cycle battery: 100 USD
Monitor for results: 100 USD
1000 Marking flags: 80 USD

Ski to sea

2015-05-25T19:58:00.002-07:00

HBOC was represented in Skitosea as part of Jupiter Mining Corporation, here is the report.

Logistics

Skitosea is a complicated relay: road closures for racers, human transportation class (all equipment to race and from race has to be delivered by human power), safety boats, early waking up, very busy finish line.

I took part in competitive class team Jupiter Mining Corporation for the first running leg: had to wake up at 4:20, then was driven to road bike start place, then drove to downhill runner start, then drove back to alpine run (which was a trail run) start for me.

Usually the first two legs are XC ski and then downhill ski, but for this year they had to replace these with an "alpine run" - a short 5k trail run with some 600 ft of elevation gain. This leg has the least impact on the race - shortest winning time and, most likely, smallest biggest loss.

Race

Some 35 minutes before the start, I get in the toilet queue. Assuming a person takes 1 min, I can barely make it - some 200 folks in front of me, 7 toilets. And I do! 3 minutes before the gun I run out of there and pose at the starting line to the drones flying over heads. Some jokes with bystanders and then BANG. A bit unexpected, but the race is on.

I had tactically chosen the position at the rightmost side of the start line: it worked well since the exit out of the parking lot is in straight and, I believe, shortest line. At the end of the first 300 meters team Jupiter Mining Corporation is 3rd overall. Not bad.

Since then people kept me passing - I had started too fast, but what the hell, I'm still moving.

The rest was miserable: too much of breakfast so I was considering going behind a tree, but it never materialized. Legs are a bit tired and I have trouble breathing - want to take more air, but that breakfast is there.

On the longest climb a girl passes me - but you should hear how organized was her breezing - I let her go. No chance to stay around. Apparently she is some mountain running champion.

I get some time back at the long downhill: catch a guy or 2. Run like you don't care, let the feet find something under. Just before the spectators, another girl - all in pink - is catching up with me. I pass the spectators and a second later they all cheer for her. Great! This time I am up for a fight, but on the pavement I am not finding enough enthusiasm and she passes me with one more guy.

Just before finish I see a guy who clearly has some trouble - he's being walked out and then the finish and I get a chair from Ryota, our downhill runner and I'm done.

I wait a bit around to learn that the second girl was an Olympic XC skier. Then start hiking down the hill with the chair, occasionally offering it to the downhill runners for a small-but-honest payment, but they never take the offer.

Place: 19th, time 25:48.

Next year?

Jupiter Mining Corporation can shave an hour off of our result very easy, so it would be a satisfying experience to do it again - much of the time lost was due to freak accidents that don't happen often. We ended up being around 180th place out of some 350 or so even with quite a lot of bad luck. See results.

However, it is unlikely I will do it again: it is an expensive event, especially from alpine run point of view - 80 dollars means 16 dollars/km + complicated and tiring logistics if Gunta does it as well. On the other hand - I think I could be somewhat of use - maybe even more than this time - in the downhill run, but do I want to hurt my knees? I would not be useful in the bicycle or boat parts, especially not so in the skiing. I also doubt alpine run will be there next year. I will likely stick to a support role if Gunta kayaks in this race again.

Mt Baker area was very nice, I would love to return there - there was too much of fog, but apart from that weather was exceptional - a bit too cold for tshirt, but no wind.

Notes on UAVs, LIDAR, etc.

2015-04-23T22:02:00.001-07:00

Lidar measurement

Velodyne's: Lidar Puck

8k price

Velodyne's: HDL-32E

includes Garmin

Routescene http://www.routescene.com/products/product/routescene-lidarpod-technical-specifications/

contains Velodyne's 35k usd sensor inside. but also spits out reasonable data.
if they used the puck it would be a good e2e solution.
not sure if this is correct since hdl-32E already has much of that.

Autonomoustuff

box with

LIDAR sensor
Inertial Measurement Unit
Processing Unit
Battery
Post processing software

Product good, price too large.

UAVs

Fixed wing

Rotary

DJI, S1000+, http://store.dji.com/spreading-wings/s1000-plus

weighs around 4kg, liftoff weight 11kg.
price - 2.5 - 4.5k USD.

http://www.xactsense.com/products/

this is a running system as it should be.
could be expensive; the puck is 8000USD, comparable DJI is around 3-4k, then that all is put together - unclear what is producing, but it could be .las files that we need. so 2k more. Total - around 14k of price. Then add some margin.

Data

National lidar dataset

"Production of a conterminous US 1-meter dataset will begin in early 2015 and will increase in geographic coverage as new high-resolution data are acquired."

this should satisfy all O' interest.

Google maps/bing maps

2015-04-02T22:37:00.000-07:00

It is hard to improve from simple areal photos. So what do you do? Well, you try to make some 3d picture of various indecency:
google here and bing here.

Not sure if they are using the LIDAR available in Redmond or maybe it is some form of 3d extrapolation from 2d images, but the crippling of images in both cases is quite annoying.

What's that?

2015-03-23T22:23:00.002-07:00

What's that?

Well, this is automatic vegetation (includes housing) from LIDAR data. Streets/fields are easy to be seen.
Formula used is the following: divide fields in 5x5m grid. Count the points that are < 0.5 meters, < 4 meters and rest. Then look at ratio of points between 0.5 and 4 meters divided by all points < 4 meters.
If ratio is > 0.5, all green, if > 0.3 - very green, if > 0.1 - somewhat green. If there are high points (> 4 meters), then make it a forest.

HBOC Winter Champs

2015-01-25T14:29:00.001-08:00

Results are here:
Day 1
Day 2

Route gadgets from Jan:

http://www.5z.com/urban/gadget/rg2/#143

http://www.5z.com/urban/gadget/rg2/#144

and also here (use the interface you like better):

http://www.5z.com/urban/gadget/cgi-bin/reitti.cgi

Thanks to everyone who attended and volunteers:

Jan, who designed the course for second day,

All control pickers, including but not limited to : John, Roman, Ing, Eric.

Especially large thanks goes to Dave Bishop who let us use his campground!

Here are maps:

Some race feedbacks:

Will, Hannah, Hannah 2, Patrick

Trying to find cliffs from point grid

2014-12-17T21:47:00.003-08:00

The ask is simple: you are given vertices on a regular grid and need to return cliffs: lines where steepness gets larger than some given constant.
I tried algorithm like this:

mark all cells for which the borders are steep,
connect 2 steepest sides with cliff segment
join segments where possible

End result is best described by this picture:

The small white lines are my calculated cliffs. The background is OCAD 11 generated steepness where black is 45degree steepness. My lines are calculated in a smaller subregion than the whole picture.

This algorithm does not work without some additional improvements. Something better is needed.

From Python to .OCD files

2014-12-07T22:45:00.001-08:00

I have been experimenting with the OCAD libary from Open Orienteering Mapper and have written a small wrapper for it.
The wrapper is available here.
What can you do with it?
You can import symbols and polygons automagically from python into OCD files for OCAD.
Here is an example:
h_writer=CreateOcadWriter(c_double(1),c_double(1), c_double(10000))

col=AddColor(h_writer, c_char_p("some color"))
sym1=AddAreaSymbol(h_writer,c_char_p("symone"), 4100, col)
sym2=AddAreaSymbol(h_writer,c_char_p("symtwo"), 4010, col)

TYPE=(POINT*3)
t=TYPE()
array=((10,100),(100,10),(100,100))
for i in range(len(array)):
t[i].x=array[i][0]
t[i].y=array[i][1]

re = ExportArea(h_writer, t, 3, 4010)

WriteOcadFile(h_writer, c_char_p("c:\\projekti\\WriteODLL\\a.ocd"))
CleanWriter(h_writer)

What does this do?

Creates a 1:10000 map with offset of (1,1)
Create a color
Creates 2 symbols (4100 is 410.0 and 4010 is 401.0)
Creates a triangle of 401.0 symbol.
Writes to OCAD file.

The color is not a real color and the symbols are neither. To use this one would have to _import_ the OCD file into one which has real symbols.

Why is this useful? If you want to experiment with larger data sets and visualize them in OCAD file, you need to automate it.

Houghton Turkey Sprint: new map!

2014-11-29T20:56:00.001-08:00

Today was an excellent day for O'. Snow covered the Houghton landfill and HBOC held a post Turkey Sprint race. No snow fell on us, but it was cold.

Volunteers: Ing and Will (checkpoints), Gunta (kids), Girts (drinks), Rick and Zarina (food).
Courses: Peteris
RG: Jan

Here is the new map. Ask me for PDF/OCAD version.

You can see splits.
Or you can see route gadget.

Maps and georeferencing

2014-11-02T21:26:00.004-08:00

For a while I have been suggesting that maps geo-referenced should have UTM projection and WGS84 datum. Now I have additional data available: NAD83 should be the datum of choice, with the reason being that LASTOOLS do not approve of WGS84, but they do recognize NAD83...

Maps & courses

2014-03-31T22:28:00.002-07:00

Some maps for everyone to enjoy. And print out if you think you need that. 200 dpi, 1:10000.

Gunta's namesday two days results published / race report

2014-03-30T21:07:00.002-07:00

The Wild horses/Frenchman coulee Gunta's namesday event has successfully finished.

These are the results:

Day1: http://obasen.orientering.se/winsplits/online/en/show_event.asp?id=29835
Day2: http://obasen.orientering.se/winsplits/online/en/show_event.asp?id=29836

Route gadget (non Java!!), here:

http://5z.com/urban/gadget/cgi-bin/reitti.cgi?act=map&id=138&kieli=
http://5z.com/urban/gadget/cgi-bin/reitti.cgi?act=map&id=139&kieli=

Please enter your courses!!

Maps and courses, here:

http://homebrewoc.blogspot.com/2014/03/maps-courses.html

Volunteers:

children watching: Gunta and Tori

rental esticks: Jan, Don, Eileen

control pickup: John, Eric, Girts, Ben, Don

choir: everyone at dinner table

photos and general help all over the place: Atis

RG (and no more Java!!): Jan

Short report:

Overall success with good weather and al-right courses. The only surprise was the environmental lady to whose concern we quickly reacted and steered the courses away from the most vulnerable part of the map by some midnight updates to the printouts. The second day courses decreased in length by 1.2 km because of that. We might have not done it either - I don't think anything would have changed.

The choir by the dinner table was most impressive.

The photos are scattered through the facebook, but I am trying to upload a big set of them into flickr - it is taking lots of time somehow.

We had 32 measured starts on day 2 and 26 on day 1.

Map updates: there were some small issues with the map. If you have some time to do updates, I could share you the map. Please let me know and also the OCAD version you can work with.

Improvements for the next time:

1) I will probably ask someone to do at least one of the two days.

2) I need to organize the emailings better - I have started a facebook group for homebrew OC, but not sure where it will go, please join if you want to - that will probably be a warranty I will not miss you in the next emailings, probably some time in the fall.

3) for the races - I will probably use some eventbrite registration utility next time.

Gunta's namesday event maps done.

2014-03-27T00:08:00.001-07:00

Sent them to the printing shop!!

Lidar data for Tiger Mountain, King County

2013-12-19T23:09:00.000-08:00

An orienteering map is in thinking for Tiger Mountain "middle earth" for homebrew oc, but a major pain is LIDAR/elevation data available for the region. King County does have lidar data which is available to general public in some form, but it is old (like 2001) and for some reason it is extremely horrible, especially when under tree cover. This blog post is to serve as an explanation to what is "unusable lidar data" and why lidar data is not always perfect, especially in King County.

How LIDAR data works

If you know what is LIDAR and how it works, skip over. If you don't, this probably explains it in yet another way and most likely includes some imprecision. Ask in comments if something is unclear.

A plane with extremely precisely known position shoots a laser ray against earth for a tiny impulse. It tries to note when it sees the "red" point on the ground. Sometimes it hits trees, sometimes it hits bushes, sometimes houses, rocks, but sometimes bare earth - these all are called reflections. Sometimes the "red" laser spot is seen on both a tree and on some bushes, these are called first and second reflections.

The machinery notes when it saw the "red" dot on the ground and how it was acquired. It notes its planes position, angle of the laser beam, intensity of reflection. From this data, one can generate - (x,y,z) data - where x, y - coordinate on ground, z - some altitude.

The generated data is LARGE. For example - some data sets contain 1 point per square meter. That yields 1 million points per square kilometer. If described in (x,y,z) in a somewhat efficient format - it would yield 12 bytes per triplet and 12 megabytes or so per 1 square kilometer. In an in-efficient format (like human readable text) - it could be as much as 30 bytes per point and 30 megabytes per square kilometer.

From this cloud of data then by some clever algorithms, different points are picked - for example, bare earth points - ones which represent surface of earth with trees and rocks and houses removed. In some cases this is hard or to do. Especially in data sets where points are few. Another interesting point set is the top surface data. Subtract bare earth from that and you get vegetation, rock and building altitudes. All useful for mapping.

King county LIDAR data

Lidar data in King County can be downloaded in several places, but as far as I can see it is of the same origin. The easiest place to download it is this: http://viewer.nationalmap.gov/viewer/ . Play around a bit with it. It can provide quite a few different data sets. It does not call the most precise LIDAR data, but you can find it by looking for the most dense altitude data.

King county LIDAR data can be also downloaded from Puget Sound LIDAR consortium. They also share full return data (which includes all reflections seen by the plane) and some more.

Tiger mountain data

The area we are interested in is here: http://www.gmap-pedometer.com/?r=6160161
It is a bit less than half a square of a kilometer.
This is the reference of it in the old USGS topomap:

Note the nice 20 feet contours, the road, the shape of the hills. The contours here are questionable a bit - they are acquired by analyzing areal photographs. Did the magician who created them really saw this?

This first "LIDAR data" image shows the individual bare earth points as vertices. The rest are approximations of the points. This data is downloaded from the USGS website mentioned above. The exact file name - ned19_n47x50_w122x00_wa_puget_sound_2000.zip.

You can clearly see the road. The algorithm on the LIDAR original data has identified the points correctly as bare earth and the road is cleanly seen. The rest are some large triangulation planes, which are completely unhelpful. Why? Well, this is how 5 meter contours would look like on it:

OMG. What the hell is that? You can, of course smoothen them or what not, but the hills are gone. There is nothing really that matches to what was seen. The LIDAR data presented here is USELESS for orienteering contours.

Can we get better data?

One solution would be to re-fly this area and probably get better data since the LIDAR technology is 10 years older now than when this data was created. This is unlikely to happen unless someone with money cares. I just don't see it happening.

A solution which I have been thinking of is looking at the original data and trying to get out more information from there. There are two thoughts why it might work:

1) the algorithms were unlikely sophisticated. This was close to the beginning of LIDAR when the data was acquired.

2) When the data was acquired, the projects included both cities and forests. I find it unlikely that an algorithm good for towns is also usable for tree covers.

3) my home computer power probably is a good match to what the company had 10 years ago. Also I have lots of time and somewhat limited data I care about.

Here is a picture of All-returns data (trees, rocks, grass - everything):

There are lots of points there (around half a million)! There are also some holes (and I have no idea why I don't have any data in that square there, but I just did not get it).

The question is how we can get rid of some of them in a way that still gives us something meaningful.

Just for kicks I generated 5 meter contour lines, but I will not share the image - they were way too dense to have any meaningful value. And it makes sense - after all we are looking at individual trees here.

One interesting notice - in the lower part the density of the points is certainly larger. It could be that different original datasets were used (could be the case the LIDAR data was acquired in several steps).

Experiments

The original data is in feet, in State Plane Coordinate System projection, Washington North Zone, NAD83 datum. We will use feet for this chapter.

Experiment 1

Mininum values in 10x10 feet cells. The original data gives as points approximately 1 per 10 square feet, so this is an approximation which will give us 1 point from 10 original ones. Approximately.

Data set for the small rectangle gets some 13 times smaller (15 to 1.2 megabytes)

Does not help. The minimum points with their precise value is not helpful.

Experiment 2

How about 100x100 feet minimums points? Now this translates to 30 meter grid, which is worse than the USGS topo map (which I don't trust too much - we have been in nature there and the small detail in it is close to imaginary).

There are very few points there, but it is extremely likely that the points found there are actually real points that exist in the nature.

Experiment 3

How about we grow from experiment 2 by adding points which belong to the same cells, but do not happen to be much higher than the minimum point. For example, if the point is 100 feet it is unlikely it will be more than some 50 feet higher. So I experiment with ~30% maximum grade. To be pricese - dh*dh*10<dx*dx+dy*dy for all pairs of points in each cell. Note that the lower part starts looking very nice.

How about dh*dh*20<dx*dx+dy*dy?

Not much of difference, but could it be somewhat usable?

I will merge this data with the original data from the place. This will fill holes and probably provide some other points.

Update

Google has started to use some lidar data (some time last year) in the Tiger Mt. region: google maps link. The same horrible source!!!

Crestwoods 2013, Zunguzeng.

2013-09-29T21:19:00.001-07:00

Thanks for volunteering:
Wildwood OC for the cookies.
Ing and Nikolay for control pickup.
Gunta for supporter delivery.
Jan for Route gadget.

Weather was ok, could have been not that wet. Forbes creek was high enough to wet everyone's legs.

2k course (zung):

1	Jan Urban	32.54	0
	HBOC
2	Matthew Knudsen	55.4	22.46
	COC
3	Kathy Forgrave	57.5	24.56
	COC

4k course (zeng):

1	Nikolay Nachev	28.25	0
	COC
2	Rick Breseman	40.42	12.17
	Wildwood
3	Ing Uhlin	45.32	17.07
	COC
4	Rob Knudsen	46.03	17.38
	COC
5	Susan&Berry	53.12	24.47
	DrBlond
6	Richard Staudt	53.58	25.33
	COC
7	Eileen Breseman	57.57	29.32
	Wildwood
8	Bob Forgrave	01:07.3	39.06
	COC
9	Kean Williams	01:07.5	39.21

Route gadget.
Winsplits.

Help needed

2013-07-13T22:47:00.002-07:00

1) We have lidar data for 2 new maps near Quincy.
2) We have some awesome terrain South of Cle Elum (2.5 hours drive time) for at least 2 maps.
3) Two maps close to Seattle in works (one likely to be cancelled).

I need help with field work.

Home-brew field work guidelines

2013-06-23T22:56:00.002-07:00

We are getting ready to do some fieldwork in PNW Cascade foothill forest (think Tiger Mt. and similar).
I have prepared a contour+some trails map.

We will try to split the fieldwork; we are not qualified mappers; the end result is a "race-able" map.
This is the process description:

I will visit the area before hand and try to leave reference markers. Hopefully GPS coverage will be good.

Thus I will have exact reference points on the map

I will distribute the area by giving a proposed trajectory to those participating.
I will print out the maps in twice the scale of the final version (e.g. 1:10000 will be printed as 1:5000)
Information gathering protocol:

GPS is always on

I have means of putting GPS trace on the map very easily.

When on field, follow route on map and add features to it

Use 3 colors

Use 2 usually, use third sometimes.
more colors is messy and takes too much time

Vegetation is encoded by the following number scheme:

0 - open forest (corresponds white map)
0-1 - open forest, bad undergrowth (white map, sparse green stripes)
0-2 - open forest, very bad undergrowth (white map close together green stripes)
1-, 2-, 3- correspond to different runnability of forest.

3 is reserved for blackberries and places you would never go yourself.
1- and 2- are somewhere in between
1- and 2- can be combined with the undergrowth symbol. 3 cannot
In PNW forest 1- and 2- can happen with fallen trees or smaller trees.
-1 and -2 describe the usual undergrowth in different forms of baddness.
2-0 is most likely to be used (and not 2-1). 2-2 is 3, 2-2 is not.
1-0, 2-0 is very unlikely either, there is always some undergrowth
2-1 and 2-2 is questionable.

So the most common are:

0, 0-1, 0-2, 1-0, 1-1,1-2, 2, 3

Please write them down as 0-2 or 0/2

Pointwise features shall be kept as numbers that start with 10 and a list of the features on some side paper.
Linear features:

Distinct vegetation boundaries shall be kept with dotted line with first color
Trails will be drawn as on map with first color
Water features will be drawn with second color
Contour line changes (hopefully not to be done), with third color.

Area features:

mark a region and add an explanation in the features list.

This is a document in making and I expect changes as we go along.

OCAD for Homebrewing

2013-06-22T22:38:00.003-07:00

There are some tips and tricks that make home-brewing OCAD editing much easier. Most of them can be found in the internets, but I have not seen nice sources.

Hiding of symbol

How:

Select an object or symbol
On keyboard: F4.
All of the objects with the given symbol disappear.
Do what you need to do
select the symbol that was hidden.
Click f2.

You can do this also do a group of symbols - select everything and say F4
This is useful for doing work in complicated/dense areas where lots of features are not allowing to draw clean lines. For example, when you are in a steep section with lots of contour lines, you may want to hide them.

Following another line

Why:

there is a road somewhere and you need to have green on one side and yellow on other.
you don't want to get the green on the other side.
and you don't want the green to be away from the road.

How:

start drawing the line.
press control, keep pressing it.
click with mouse (left button) on the line you want to follow and keep holding it
now move the pointer to the place till which you want follow
release mouse
the new line should be following

Sometimes even with this feature you can see tiny white line. OCAD has bugs.
Once you have two lines together and you need to shape them somehow together, you are in bad luck - I do not know how to do that nicely.

Custom shortcuts:

Why:

once by computer, you need to be working fast, don't waste time
use shortcuts!

I use the following:

ctrl+d for duplicate in place (fill, make border, duplicate identically in object menu)
ctrl+f for forcing a different symbol (usually duplicate in place, then choose a symbol and then force a symbol on top)

this is useful when creating borders of sorts or just making some contour line a lake or similar.

ctrl+r - for reverse a feature - if you have a cliff with ticks to one side, this is how you can get them to another
ctrl+t - for removal of vertices

This was mentioned here.

Usage of NW trails/Switchbacks data

2013-04-10T00:16:00.003-07:00

In some of the Homebrew maps I have been using NW Trails data - it has been in most cases used as a reference, but nevertheless, it has been.
So I need to give proper attribution.
From now on, I will make sure this happens better.

Their license, btw:
"Copyright © 2012 Jon Stanley

This software is provided 'as-is', without any express or implied warranty. In no event will the author(s) be held liable for any damages arising from the use of this software.

The accuracy of the data contained in this dataset varies greatly. These maps and data are to be used for reference purposes only. The author(s) are not responsible for any inaccuracies and no responsibility is assumed for damages or other liabilities due to the accuracy, availability, use or misuse of the data presented. Installation and use of this data is at your own risk.

Permission is granted to anyone to use this data for any purpose, including commercial applications, and to alter it and redistribute it freely, subject to the following restrictions:

1. The origin of the data must not be misrepresented; you must not claim that you recorded and compiled the original data.
2. If you use this data in a product, an acknowledgment in the product documentation is required.
3. Altered versions must be plainly marked as such, and must not be misrepresented as being the original data."

For amazing resources see this website:
http://www.switchbacks.com/nwtrails/

Willows training

2013-04-09T21:58:00.003-07:00

Ing, Gunta and Rick participated in Willows training on rainy Sunday, April 7th.
This is the map:

PDF file can be acquired on request.
Note the forbidden and private areas - mostly ones with no trespassing signs.
Posession of the map does not grant you permission to go there.
Use it at your own risk.

Quincy 2 days have finished!

2013-03-24T21:14:00.002-07:00

Excellent racers, excellent volunteers, excellent weather!

Quincy West:

Fast courses with shorter legs.
Some confusion was caused by Finish on first day - "Navigate to finish" says the description sheet.
https://www.5z.com/urban/gadget/cgi-bin/reitti.cgi?act=map&id=130&kieli=
http://www.obasen.nu/winsplits/online/en/default.asp?page=classes&databaseId=24649

Quincy South:

Some longer route choices with a mix of shorter legs.
https://www.5z.com/urban/gadget/cgi-bin/reitti.cgi?act=map&id=131&kieli=
http://www.obasen.nu/winsplits/online/en/default.asp?page=classes&databaseId=24650
* Hannah's results are not recorded.

Special thanks to volunteers:
Help with children - Gunta & everybody else.
Control pickup - Nikolay, Dushka, Peteris, Richard, Andrew, Will, Susan, Barry.
Help with electronic equipment - Debbie, Ing, Don, Jan.
Routegadget - Jan
Cascade OC for renting me their SI stuffs.
Afterrace food - Marianne and Dobby.
(I am missing someone here, sorry about that).

Electronic maps of the race will be shared upon request.

2.5 or 5 meters?

2012-12-30T16:43:00.002-08:00

2.5 or 5 meter contour lines, that is the question.

Thoughts?
I think I will go with 2.5 meter ones.

Homebrew OC Winter 2012 1 results, Mt Tiger

2012-11-11T17:19:00.003-08:00

These are approximate results, they will be corrected.

Place	Orcs	Race Time	Start time	Notes
1	Nikolay	1:07:59	12:20
2	Will	1:24:00	12:17
3	Kean/Rick	1:48:00	12:15
4	Miles	1:57:00	12:07
5	Aaron/Brice	2:07:00	12:09
6	Murray/Christi	2:20:00	12:05
7	Debbie/Ing	2:28:00	12:01

	Hobbits	Time
1	Jan	1:08:32	12:03
2	Ina	1:23	:00?	Course backwards
3	Eileen	2:00:18	12:11
4	Don	1:30:00	12:22	Skipped 1&2
5	Doug/Alan	DNF	12:13	skipped a bunch
6	Sergiy, Valery and Max

Course Setter: Peteris
Start&Finish: Gunta&Emily
Refreshments: Rick&Eileen
Course pickup: Eric Bone
Route gadget: Jan Urban

More information will be provided as it becomes available.

Rules of home-brewing

2012-09-23T21:18:00.005-07:00

When doing homebrew orienteering race there is only one rule:
The map is new or it is updated from the previous bad state to a not-so-bad state (but most likely still pretty bad state). That means that the map will most likely be very far from a good quality map, but we must try hard to make it enjoyable.

Homebrew is looking for...

2012-09-23T21:16:00.001-07:00

We are looking for mapmakers, course setters, controls pickers, anything goes.
The new season is looking exciting...

We are planning on the following events (not all will happen):

Quincy lakes: Quincy south (old map, to be updated), Quincy North, which consists of Quincy middle and Quincy North (two new maps, work under-way, we need to to field work there). The plan would be to have 3 races in a weekend.
Tiger North (new map, first scouting done there - looking for help with map).
Willows fjords (old map, to be updated)
Crestwoods park (old map, to be updated)
Drunken Charlie (old map, to be updated)

Then there is a sprint map of Redmond Triangle in works (also known as our current apartment complex, but very questionable if anything can happen there).