Trip Report request.

My favorite TRs include the starting point:

1. highway
2. trail head
3. drainage/ridge/sumit travelled

I dont really read TRs when I cant figure out where they started (unless pictures are really good or the author is super cool).

I think there is a  great danger in trying to codify trip reports and how they should be presented and laid out. It stifles creativity.
Everybody has their own idea as to how to present them and people have different views and preferences.
Via la differance!

Many people want everything laid out on a plate for them.....personally if a TR has piqued my interest but I need more information I will do the work and research necessary to find out where it is and how to get there...at the last resort I may even contact the poster and ask them direct.

Research and figuring shit out is part of the fun.

This thread makes me sad! :'(

John your too kind. Your edits are detailed and considerate of others. In regards to a balance, I do agree in leaving a bit left for discovery... that's half the fun for me ski touring, exploring. I just want to know the general area and have always been able to stir up an adventure on my own imagination and map session. Just knowing Lanham Lake is based out of Stevens Pass would be enough for me...  but I probably would have had to PM you about parking.

I think there is a  great danger in trying to codify trip reports and how they should be presented and laid out. It stifles creativity.
Everybody has their own idea as to how to present them and people have different views and preferences.

Rest assured that TR presentation will probably not be codified anymore than it currently is -- I like the creativity and layout choices that people can make too, and it's always been up to the poster to decide how much or how little they want to share.

I think as the geographical "spread" of the site's users expands, having a state/region tag (i.e. WA/Blewett) or note could be helpful in the TRs, but it would probably always be an option, not a requirement.

I hope I didn't give any impression that TR's should be "codified" in any way. I was just participating in support of the OP... at the end of the day it doesn't matter, just that the more you leave out the less useful your post is to others. I don't see anything bad in letting others know what's helpful in a TR. The original post request was pretty simple, if you cant share the general location then whats the point of posting?

I hope I didn't give any impression that TR's should be "codified" in any way. I was just participating in support of the OP... at the end of the day it doesn't matter, just that the more you leave out the less useful your post is to others. I don't see anything bad in letting others know what's helpful in a TR. The original post request was pretty simple, if you cant share the general location then whats the point of posting?

Lets see........oh yes..... STOKE!
People post for many reasons .
E-gloating
To give Avy information
To share with others
To boast
To claim a first descent.
Etc,etc.
Sometimes all of the above in the same post. Posting TR's whatever the motivation should be encouraged. If you codify or require that the TR must or is expected to contain information on avy conditions, snow conditions, trailhead information, detailed route plan... ( nice if they do) you are going to stifle them. It should be left to the author to decide.