Revision as of 20:26, 18 January 2018

Destinations are points of interest along the hike as well as the final destination. Short hikes may have only one major point of interest; longer hikes may include several. "Destinations" include features that can be seen from somewhere along the trail, including mountains and lakes that the trail doesn't actually reach. Other kinds of destinations include viewpoints, historic buildings, waterfalls, meadows, mines, springs, coastal promontories, campsites, etc.

To begin a new Destination page:

• Log in to the Field Guide with your user name and password.
• Find a destination/point of interest that you can use as a template. Criteria should include: a destination in the same general area; also something that was created in the past four or five years (See the History link to look at the work history).
• Click on the Edit link at the top of the page.
• Copy the entire html content from the dialog box.
• Go back to your hike page, and click on the live link you've created for the destination.
• Paste the html content from your template destination into the blank dialog box and begin working! Save frequently or you might lose content.

The Destination page may have several components and sections:

• Categories
• Hike Ring
• Destination Statistics
• Description
• More Links
• Contributors
• Images

Categories

Destination categories are useful because a user can click on them to find hikes and points of interest in the same area, e.g. Crater Lake National Park. Other categories, e.g. 'Waterfalls' or 'Alpine,' collect a list of similar features.

• Destination categories include the regions and subregions/jurisdictional districts the destination is in.
• Use as many categories as possible that fit the page you are creating. Make sure the categories you use fit the style already being applied in the Field Guide, e.g. '360 Degree Summits' not 'Big Views.'
• A list of all the categories currently being used can be seen on the Categories page.

The categories are listed at the top of your html dialog box. In Page view mode, they are at the bottom of the page. See the categories for Cooks Chasm as an example.

Hike Ring

A complete hike ring links to the hike in question but also relates to the trail log. Since the trail log is optional, and most hikes in the Field Guide do not use trail logs, you do not need to complete a hike ring, just link to the hike using double brackets.

For an example of complete hike rings (Again, this is optional), look at North Lake in View source and Edit modes.

Destination Statistics

The destination statistics appear in the top left of a destination page just below the hike ring(s).

• Latitude coordinate up to four or five decimal points.
• Longitude coordinate up to four or five decimal points.
• Maps This feature gives two links: the first is a map marked with all Oregon Hikers Field Guide waypoints; the second shows the individual waypoint you have marked with the coordinates above. The Maps feature does not show up in your html window.
• Elevation The elevation of the trailhead in feet. Most current trailhead elevations are linked, but they should not be. You can correct this by reconfiguring in html like this: * Elevation: 1150 feet

Notes:

• Coordinates should be retrieved through a GPS device. Alternatively, they can be gotten from an online map like Caltopo or Google Maps.
• Elevation should not be linked even if it is in your template. Reconfigure like this in html: * Elevation: 1150 feet

Example: See the Trailhead Statistics for the Sumpter Dredge Trailhead.

Driving Directions

• Give a line by line account of directions to the trailhead from a specified source, e.g. a numbered freeway exit or a central intersection in a town or city.
• For better readability, write double spaced rather than a single paragraph.
• Each line should be indicative of a turn or intersection in the drive.
• For remote hikes, use your own odometer and take notes while driving.
• For hikes closer to a city, you can use Google Maps for accurate directions.
• Include brief details about road conditions or junction particulars where useful.
• You can give two sets of directions in some instances.

Example: See the Driving Directions section for the North Fork John Day Trailhead.

Alternatives to Driving

This feature gives information on regular public transit that stops at or comes close to the trailhead. This mostly applies to urban hikes. There is usually a link to a specific timetable.

• You will need to note if the bus line is weekdays only (This applies to some commuter routes)
• Give walking directions from the bus stop to the trailhead (You can usually see this on Google Maps or on a transit agency's route map, e.g. TriMet or C-TRAN).

Example: See the Alternatives to Driving section for the Croisan Scenic Trailhead.

Notes/Fees and Regulations

This section gives additional information pertaining to the trailhead itself. It may include:

• Notes about road conditions, including seasonal issues
• Special fees, e.g. Northwest Forest Pass, Discover Pass, State Parks fees, concessionaire fees
• Toll bridge fees on the drive to the trailhead
• Self-issued wilderness permits
• Hours open, e.g. for city parks
• Seasonal closures
• Pet policies, e.g. "Dogs on leash" or "No pets permitted"
• Share the trail situations, e.g. with bicycles or horses
• Facilities at the trailhead, such as restrooms, picnic tables
• Other features, such as visitor centers, interpretive trails

Example: See the Notes section for the Hebo Lake Trailhead.

Contributors

If you have completed a new trailhead page, list yourself as the creator. If you have added significantly to an existing page, you can list yourself under the creator's name.

Example: See the Contributors for the Wahtum Lake Trailhead.

As an editor, you can create a profile page for yourself; for example, see CFM's profile page.

Images

The last item you will probably add to your hike page is a photograph.

• One image is usually enough, but sometimes two are useful.
• Ideally this is a photo taken at the trailhead; you can also post a photo taken near the trailhead.
• If you absolutely don't have a photo, add 'Needs pics' to the categories.
• Save the photo as .jpg or .png
• Upload the photo in a relatively small size, e.g. 40 - 100 KB.
• The first photo, if a horizontal rectangle, will be 400 px in length; if a vertical rectangle, it will be 260 px in width.
• All other photos will be 250 px and 160 px respectively.
• The photos needs to be uploaded with a file name.
• The caption needs to be clear.
• The photographer needs to be credited; use parentheses and italics (two apostrophes before and after the name).
• You can use someone else's photo if they give permission and you give them credit (PM forum users and ask nicely for their pictures).
• Do NOT use a picture without the photographer's permission.

Example: See the photos for the French Creek Ridge East Trailhead.

 Editing the Field Guide  |   Creating a Hike page  |   Creating a Trailhead page  |   Creating a Junction page