{"id":1838,"date":"2025-11-12T21:04:58","date_gmt":"2025-11-12T21:04:58","guid":{"rendered":"https:\/\/w6sota.org\/web\/?page_id=1838"},"modified":"2025-11-12T22:17:23","modified_gmt":"2025-11-12T22:17:23","slug":"why-create-a-trip-report","status":"publish","type":"page","link":"https:\/\/w6sota.org\/web\/why-create-a-trip-report\/","title":{"rendered":"Why Create a Trip Report?"},"content":{"rendered":"\n\n\n\n

To answer the question “Why create a Trip Report”, you should understand where the need came from and the value it delivers.<\/span><\/p>\n\n

Trip reports grew out of a need to respond to people that contacted myself and others about which summits they should do when visiting the area.  Some were visiting from other towns, or states, and some were from other countries.  I\u2019ve received a lot of requests from people wanting to do summits in my primary area of operations in California and Arizona.  When building the new web site, I noticed that a similar capability on the PNWsota.org web site with over 2,000 reports is used heavily.  <\/span><\/p>


<\/strong><\/p>

Trip Reports is a way for people to share more in-depth information about their hike, the summit and other pertinent information and make that information searchable.  Using Search, a user can find all the driveups in San Diego (try entering \u201cdiego driveup\u201d).  We add things like points to save the user time of going to another place to look that up and a way to sort on that.  When visiting Los Angeles and being presented with a hundred options, this might help pair down what is doable for the operator.<\/span><\/p>


<\/strong><\/p>

The Trip Reports feature on W6 SOTA provides the following value:<\/span>

<\/span><\/p>

  1. Allows users new to the area who are visiting to <\/span>quickly<\/span> find key info on summits that others have done.  <\/span>Questions like: <\/span>
    <\/span>How long <\/span>is the hike? <\/span>
    <\/span>What is the <\/span>elevation gain<\/span>?<\/span>
    <\/span>Is this a hike, bike, or driveup?<\/span>

    <\/span><\/p><\/li>

  2. Provides ability to quickly search on a known name: For example, they may not be familiar with the region but know to enter \u201cSan Diego\u201d, \u201cLos Angeles, or \u201cYosemite\u201d.  (Summits can be tagged to belong to more than one area in our \u201cFolksonomy\u201d).<\/span>

    <\/span><\/p><\/li>

  3. Next LEVEL<\/span>: Users can search to quickly find all the known driveups in an area.  Or, search on \u201cLos Angeles Bike\u201d and then sort on the Points column.  For hikers who only have a short time after their conference, they can sort on RT Miles for a short hike.  If they are trying to maximize points per mile, they can quickly figure that out.<\/span>

    <\/span><\/p><\/li>

  4. A lot of users want to know what the hike is like.  Is it a trail, road, use trail, or a wicked bushwhack?  Where does the use trail start?  Other info, like bring your climbing gear and be ready for a class 4 climb.  Or warnings, route not recommended if covered in snow. <\/span>If it’s a driveup, does it require high clearance, or a 4X4?<\/span><\/p><\/li><\/ol>


    <\/strong><\/p>

    Should you create a trip report if one already exists?<\/span>  Yes, because everyone has a different perspective, experience and may take a different route or the trail or road conditions change.  For example, a summit near San Diego had an easy use trail to the top if you knew where to go but 3+ years later it was hugely overgrown.<\/span><\/p>


    <\/p>

    Finally, the solution provides an outlet for people that want to share their experience with words and photos in context but don\u2019t have a blog or other media they want to use.  The solution is not perfect but it was the best we could do to get people close to what we envisioned for the lowest cost.  <\/span><\/p>\n\n

    Go HERE for help on creating a Trip Report<\/a><\/h3>\n\n\n\n

    Lorem Ipsum has been the industry’s standard dummy text ever since the 1500s.<\/p>\n\n

    Lorem Ipsum has been the industry’s standard dummy text ever since the 1500s.<\/p>\n\n\n","protected":false},"excerpt":{"rendered":"","protected":false},"author":21,"featured_media":957,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_acf_changed":false,"pagelayer_contact_templates":[],"_pagelayer_content":"","footnotes":""},"class_list":["post-1838","page","type-page","status-publish","has-post-thumbnail","hentry"],"acf":[],"_links":{"self":[{"href":"https:\/\/w6sota.org\/web\/wp-json\/wp\/v2\/pages\/1838","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/w6sota.org\/web\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/w6sota.org\/web\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/w6sota.org\/web\/wp-json\/wp\/v2\/users\/21"}],"replies":[{"embeddable":true,"href":"https:\/\/w6sota.org\/web\/wp-json\/wp\/v2\/comments?post=1838"}],"version-history":[{"count":7,"href":"https:\/\/w6sota.org\/web\/wp-json\/wp\/v2\/pages\/1838\/revisions"}],"predecessor-version":[{"id":1851,"href":"https:\/\/w6sota.org\/web\/wp-json\/wp\/v2\/pages\/1838\/revisions\/1851"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/w6sota.org\/web\/wp-json\/wp\/v2\/media\/957"}],"wp:attachment":[{"href":"https:\/\/w6sota.org\/web\/wp-json\/wp\/v2\/media?parent=1838"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}