Home  •   Field Guide  •   Forums  •    Unread Posts  •   Maps  •   Find a Hike!
| Page | Discussion | View source | History | Print Friendly and PDF

Trail Log Template

From Oregon Hikers Field Guide

"Dad, how much farther is it?"

"Wow, what a view! I wonder if there's a trail to that lake down there?"

"Bill, that's a serious sprain. I wonder if there are any roads closer than the way we came up."

It's always a good idea to research a hike before we go, but sometimes questions come up in the field. The trail logs are our tool for providing information in the field. They're in a concise, easy to read format, perfect for stuffing in a pack.

The trail logs take a little more experience to understand than most of our templates. The easiest way to learn is probably to open an existing log page from the Field Guide and look at it, while you read this.

On the top of the trail log is a link to the hike, and a help note. Next, in the main portion of the trail log, we basically list out the route for the hike. Here, highlighted in blue, is the exact route described on the hike page. Each trail is listed in the same order they occur in the hike and the left column provides a handy mileage log of this hike.

It's important to realize that these are logs of trails with the hike imposed on them. That's why we also have "trail miles" listed, which are basically mile markers that never change, no matter what hike we're on. If you forget your camera at mile 6.2, it's easy to tell your friend where to go to pick it up for you. When the trail continues beyond the hike, we often include the remainder of the trail. This is an easy way to show alternate routes or extensions to hikes. It's easy for us to show water sources, road access and campsites in the logs. There are links to all of destination pages in the Field Guide.

After the trails directly involving the hike are included, there's a section for connecting trails. These can be used for impromptu add-ons in the field. They also provide continuity between the various hikes, showing how the trail system connects together.

At the bottom of each trail log is a key for the icons.

The format is pretty simple to read and use. Unfortunately, it's not nearly as straightforward to produce. Now that we understand what they look like, let's take a look at how we create them.

Copy and paste is your friend here. First copy and paste this into your blank Trail Log page. Then you can copy individual lines as you need them.


{{LogLineYes|0.0|0.0||[[LINKED PAGE ON THE HIKE HERE]]|=y}}
{{LogLineYes|0.2|0.2||NON-LINKED PAGE ON THE HIKE HERE|=y}}
{{LogLineNo|0.4||[[LINKED PAGE NOT ON THE THIS HIKE]]|=y}}

{{LogTrail|NEXT TRAIL}}


The trail log pages use a lot of templates. A wiki template is a piece of code that's already set up, saving a lot of typing and complicated figuring. You use a template by enclosing the name is a double pair of braces. It should look like this: {{Template Name}}. Sometimes we need to pass information into the templates. The things we give it are called parameters. We separate them with a "pipe", which is a "|". On most keyboards, it's a backslash with the shift held down. So these templates look like {{Template Name|parameter|parameter}}.

First, let's look at the things that happen only once on the page.

Obviously, replace "ENTER HIKE NAME HERE" with the name of your hike. The "{{LogHelp}}" template generates the help link on the top of the page, so you don't need to change that. The "{{-}}" template starts us out clean with a new line.

Down on the bottom on the page the "{{LogKey}}" template creates the Log Key and the credit for the icons, so you can ignore that, as well.

For each trail, there's a template at the start and another at the end. You'll need to do this once for each trail in your log.

At the start of each trail is a "{{LogTrail}}" template. This template has one parameter which is the name of the trail. If the trail has a number, you can put that in too. An example would be "{{LogTrail|Pacific Crest Trail #2000}}". This template creates the trail name and the column labels for each trail (For the programmers in the room, the template also sets up the table).

At the end of each trail is a "{{LogTrailEnd}}" template. You don't need to change anything here, but it needs to be there for each trail. (Programmers, this template just closes the table).

Each line in the finished log page is created by a "LogLine" template entry in the code. These templates are "ordered templates", which means that the info needs to be put in the proper order (with one exception below). They come in a few varieties. The first is the "{{LogLineYes}}" template. The syntax is a bit complex, but after you've used it a few times, it will be second nature.

Here's the layout:

  • {{LogLineYes|"Hike Mileage"|"Trail Mileage"|"Elevation"|"Feature"|"Icons"}}

"Hike Mileage" is how far this place is from the start of this hike. When you finish your page these numbers start at zero at the top of the page and get larger.

"Trail Mileage" is the virtual mile markers on the trail. 0.0 is typically the trailhead, or the end of the trail closest to a road. These numbers are always the same no matter what hike we're on. This is a pretty unique feature to Portland Hikers and I feel it's extremely useful. If someone is injured at mile 2.3, that spot is the same, no matter which route the rescuers take to get there.

"Elevation" is simply the elevation of the place. GPS readings are best, but pulling info off a topo map is OK too.

"Feature" is what we're talking about. If it's a destination page, you can create a link using square brackets like [[this]]. Feel free to put all kinds of tiny stuff in here without links. Things like "seasonal creek", "talus slope" and "wilderness boundary" will help hikers figure out exactly where they are.

The "icons" section is what creates the little cars, tents and water drops. The syntax for this is simple, if weird. There are currently seven icons in use. Each one has a single letter code associated with it.

  • b is bathrooms
  • c is a campsite
  • j is a trail junction
  • r is road access
  • v is a viewpoint
  • w is a water source
  • x is a closed area

For each icon you need, you'll type c=y or r=y or w=y. The "y", of course, signifies yes. If you have more than one icon to use, they're separate parameters, so you'll need to separate them with a pipe (c=y|w=y|v=y). The odd part here is that y means yes and everything else means no. "y" means yes, "no" means no, "0" means no, "yes" means no, "you betcha" means no, nothing at all means no. Again this gets easier with practice. (The icons parameters can technically go anywhere in the statement, and you'll see them in nonstandard places on older pages.)

A finished line should look like:

  • {{LogLineYes|0.0|0.0|4600|[[Vista Ridge Trailhead]]|r=y}}

If you don't know some of the information, you can leave it blank, but the pipes need to be there. Here's an example missing the elevation:

  • {{LogLineYes|0.0|0.0||[[Vista Ridge Trailhead]]|r=y}}

There are other variations on the {{LogLineYes}} template. The most common is the {{LogLineNo}} template. It's used for parts of trails that aren't included in the hike. It's also used for connecting trails, since they're not part of the hike by definition. The syntax is very similar, just lacking "Hike Mileage", since it's doesn't have any.

  • {{LogLineNo|"Trail Mileage"|"Elevation"|"Feature"|"Icons"}}

There's also a series of templates for dealing with trails segments that are officially part of two trails. The most well-known example of this is the Timberline Trail, part of which is also the Pacific Crest Trail. The Gorge Trail does this a lot too. Fortunately, this a pretty rare, because it's a pain to deal with. The syntax for these templates is

  • {{LogTrailDual|"Trail Name"}}
  • {{LogLineDualYes|"Hike Mileage"|"Trail Mileage"|"Dual Mileage"|"Elevation"|"Feature"|"Icons"}}
  • {{LogLineDualNo|"Trail Mileage"|"Dual Mileage"|"Elevation"|"Feature"|"Icons"}}

Once you set up a trail with LogTrailDual, all of the lines need to be LogLineDualYes or LogLineDualNo. Otherwise, the columns get thrown off.

The best way to get to know any of these is to play with them.

Here's an example of a finished product. The code looks like this:

[[Elk Cove from Vista Ridge Hike]]
{{LogTrail|Vista Ridge Trail #626}}
{{LogLineYes|0.0|0.0|4600|[[Vista Ridge Trailhead]]|r=y}}
{{LogLineYes|0.4|0.4|4640|[[Vista Ridge-Old Vista Ridge Trail Junction]]|j=y}}
{{LogLineYes|2.5|2.5|5700|[[Vista Ridge-Eden Park Trail Junction]]|j=y}}
{{LogLineYes|2.9|2.9|5800|[[Wy'East Basin|Timberline-Vista Ridge Trail Junction]]|j=y}}

{{LogTrail|Timberline Trail 600 (Partial Log)}}
{{LogLineDualNo|19.0||5600|[[Cairn Basin|Timberline-Eden Park Trail Junction]]|j=y}}
{{LogLineDualNo|19.0||5600|[[Cairn Basin]]}}
{{LogLineDualNo|19.1||5540|[[Ladd Creek Crossing on Timberline Trail]]|w=y}}
{{LogLineDualYes|2.9|20.0||5800|[[Wy'East Basin|Timberline-Vista Ridge Trail Junction]]|j=y}}
{{LogLineDualYes|3.0|20.1||5800|[[Wy'East Basin]]|v=y}}
{{LogLineDualYes|3.2|20.3||5800|[[Timberline-Pinnacle Ridge Trail Junction]]|j=y}}
{{LogLineDualYes|3.5|20.6||5800|[[Timberline-Dollar Lake Trail Junction]]|j=y}}
{{LogLineDualYes|4.3|21.4||5500|[[Elk Cove|Timberline-Elk Cove Trail Junction]]|j=y}}
{{LogLineDualYes|4.4|21.5||5500|[[Elk Cove]]|v=y}}
{{LogLineDualNo|22.2||5150|[[Coe Creek Crossing on Timberline Trail]]|j=y}}
{{LogLineDualNo|23.7||5800|Two campsites|c=y}}
{{LogLineDualNo|25.5||6000|North end of Eliot Detour|j=y}}
{{LogLineDualNo|25.8||6000|[[Eliot Creek Crossing]]|w=y}}
{{LogLineDualNo|26.1||5900|[[Timberline-Cloud Cap Trail Junction]], South end of Eliot Detour|j=y}}

===Connecting Trails===

{{LogTrail|Old Vista Ridge Trail}}
{{LogLineNo|0.0|4640|[[Vista Ridge-Old Vista Ridge Trail Junction]]|j=y}}
{{LogLineNo|1.3|4800|Meadow, Side trail to [[Red Hill]]|j=y}}
{{LogLineNo|1.6|4850|Meadow, Side trail to [[The Rockpile]]|j=y}}
{{LogLineNo|2.4|4400|Site of Red Hill Guard Station}}
{{LogLineNo|2.8|4180|[[Perry Lake]]|w=y}}

{{LogTrail|Pinnacle Ridge Trail #630}}
{{LogLineNo|0.0|3700|[[Pinnacle Ridge Trailhead]]|r=y}}
{{LogLineNo|3.0|5800|[[Timberline-Pinnacle Ridge Trail Junction]]|j=y}}

{{LogTrail|Dollar Lake Trail #600C}}
{{LogLineNo|0.0|5800|[[Timberline-Dollar Lake Trail Junction]]|j=y}}
{{LogLineNo|0.3|5800|[[Dollar Lake]]|w=y}}

{{LogTrail|Elk Cove Trail #631}}
{{LogLineNo|0.0|3600|[[Elk Cove Trailhead]]|r=y}}
{{LogLineNo|1.2|3640|Trail leaves old road}}
{{LogLineNo|3.1|4715|[[Coe Overlook]]|v=y}}
{{LogLineNo|4.2|4040|[[Cove Creek Crossing on Elk Cove Trail]]|w=y}}
{{LogLineNo|5.0|5500|[[Timberline-Elk Cove Trail Junction]]|j=y}}


All of that gibberish create this log page:

Elk Cove from Vista Ridge Hike

This is a trail log page. The hike mile column refers to how many miles you'll have hiked on this particular hike to reach the listed point. Hike miles will be different from one hike to another. The trail mile column is a permanent marker for the trail measuring miles from the start of the trail. Trail miles are a permanent feature of the trail and are the same from hike to hike. Sections of the trail included in this hike are blue. Other trail segments are provided for you to personalize your own hikes.

Vista Ridge Trail #626
Hike Mile Trail Mile Elevation Notes Location
0.0 0.0 4600 Road.JPG Vista Ridge Trailhead
0.4 0.2 4640 Junction.JPG Vista Ridge-Old Vista Ridge Trail Junction
2.5 2.7 5700 Junction.JPG Vista Ridge-Eden Park Trail Junction
2.9 3.0 5800 Junction.JPG Timberline-Vista Ridge Trail Junction

Timberline Trail 600 (Partial Log)
Hike Mile Trail Mile Elevation Notes Location
19.0 5600 Junction.JPG Timberline-Eden Park Trail Junction
19.0 5600 Cairn Basin
19.1 5540 Water.JPG Ladd Creek Crossing on Timberline Trail
2.9 20.0 5800 Junction.JPG Timberline-Vista Ridge Trail Junction
3.0 20.1 5800 View.JPG Wy'East Basin
3.1 20.2 5780 Water.JPG Creek
3.1 20.2 5770 Water.JPG Creek
3.2 20.3 5770 Water.JPG Creek
3.2 20.3 5750 Water.JPG Creek
3.2 20.3 5800 Junction.JPG Timberline-Pinnacle Ridge Trail Junction
3.5 20.6 5800 Junction.JPG Timberline-Dollar Lake Trail Junction
4.3 21.4 5500 Junction.JPG Timberline-Elk Cove Trail Junction
4.4 21.5 5500 View.JPG Elk Cove
22.2 5150 Junction.JPG Coe Creek Crossing on Timberline Trail
23.7 5800 Campsite.JPG Two campsites
25.5 6000 Junction.JPG North end of Eliot Detour
25.8 6000 Water.JPG Eliot Creek Crossing
26.1 5900 Junction.JPG Timberline-Cloud Cap Trail Junction, South end of Eliot Detour

Connecting Trails

Old Vista Ridge Trail
Hike Mile Trail Mile Elevation Notes Location
0.0 4640 Junction.JPG Vista Ridge-Old Vista Ridge Trail Junction
1.3 4800 Junction.JPG Meadow, Side trail to Red Hill
1.6 4850 Junction.JPG Meadow, Side trail to The Rockpile
2.4 4400 Site of Red Hill Guard Station
2.8 4180 Water.JPG Perry Lake

Pinnacle Ridge Trail #630
Hike Mile Trail Mile Elevation Notes Location
0.0 3700 Road.JPG Pinnacle Ridge Trailhead
3.0 5800 Junction.JPG Timberline-Pinnacle Ridge Trail Junction

Dollar Lake Trail #600C
Hike Mile Trail Mile Elevation Notes Location
0.0 5800 Junction.JPG Timberline-Dollar Lake Trail Junction
0.3 5800 Water.JPG Dollar Lake

Elk Cove Trail #631
Hike Mile Trail Mile Elevation Notes Location
0.0 3600 Road.JPG Elk Cove Trailhead
1.2 3640 Trail leaves old road
3.1 4715 View.JPG Coe Overlook
4.2 4040 Water.JPG Cove Creek Crossing on Elk Cove Trail
5.0 5500 Junction.JPG Timberline-Elk Cove Trail Junction

  • Campsite.JPG Campsite
  • Closed.JPG Closed area
  • Bathroom.JPG Restrooms
  • Road.JPG Road access
  • Junction.JPG Trail junction
  • View.JPG View
  • Water.JPG Water source

Icons courtesy of famfamfam.com

Dig in and HAVE FUN!!!

Oregon Hikers Field Guide is built as a collaborative effort by its user community. While we make every effort to fact-check, information found here should be considered anecdotal. You should cross-check against other references before planning a hike. Trail routing and conditions are subject to change. Please contact us if you notice errors on this page.

Hiking is a potentially risky activity, and the entire risk for users of this field guide is assumed by the user, and in no event shall Trailkeepers of Oregon be liable for any injury or damages suffered as a result of relying on content in this field guide. All content posted on the field guide becomes the property of Trailkeepers of Oregon, and may not be used without permission.