<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Big Sur Trails+Maps</title>
	<atom:link href="https://bigsurtrailmap.net/feed/" rel="self" type="application/rss+xml" />
	<link>https://bigsurtrailmap.net/blog</link>
	<description></description>
	<lastBuildDate>Mon, 09 Nov 2026 18:28:36 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1.4</generator>

<image>
	<url>https://bigsurtrailmap.net/blog/wp-content/uploads/2020/02/WindowRidge-MPT-crop3.jpg</url>
	<title>Big Sur Trails+Maps</title>
	<link>https://bigsurtrailmap.net/blog</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Soberanes Fire Reminiscences : ugly,&#160;bad,&#160;and&#160;good</title>
		<link>https://bigsurtrailmap.net/blog/soberanes-fire-reminiscences-ugly-bad-and-good/</link>
					<comments>https://bigsurtrailmap.net/blog/soberanes-fire-reminiscences-ugly-bad-and-good/#respond</comments>
		
		<dc:creator><![CDATA[Jack Glendening]]></dc:creator>
		<pubDate>Sat, 19 Sep 2026 05:16:33 +0000</pubDate>
				<category><![CDATA[hike]]></category>
		<category><![CDATA[report]]></category>
		<guid isPermaLink="false">https://bigsurtrailmap.net/blog/?p=3788</guid>

					<description><![CDATA[The recent Timber and Plaskett wildfires, with the former re-burning some of the area burnt by the 2016 Soberanes Wildfire [July-October], brought back memories of that fire. Contains panorama photosbest viewed on wide screenor in landscape orientation THE UGLY December 2016, two months after end of the Soberanes fire, found Maria Ferdin (as a VWA [&#8230;]]]></description>
										<content:encoded><![CDATA[<div>
<img decoding="async" style="width:178px;height:192px;cursor:pointer;" src="https://bigsurtrailmap.net/blog/wp-content/uploads/2026/09/Soberanes_Fire_Map.356x383.png" alt="Map of Soberanes Fire burn area" onclick="click_404('blog-SoberanesFire-animatedmap');window.open('/MAPS/FIRE/SOBERANES/fireperimeterhistory.googlemaps_display_overlay.html', '_self')"></p>
<div style="padding-top:20px;"><span class="emphasis">T</span>he recent Timber and Plaskett wildfires, with the former re-burning some of the area burnt by the 2016 Soberanes Wildfire <SMALL>[July-October]</SMALL>, brought back memories of that fire.</div>
<div style='height:12px;'></div>
<div class="center" style='font-style:italic;line-height:1.2'>Contains panorama photos<BR>best viewed on wide screen<BR>or in landscape orientation</div>
</div>
<p></p>
<hr style='width:50%;'><span id="more-3788"></span></p>
<p><DIV class='center'>  <!-- START OF POST-WIDE CENTERING DIV --><br />
<DIV style='color:#cc0000;font-size:200%;font-weight:bold;'>THE UGLY</DIV></p>
<p><DIV style="padding-top:20px;"><span class="emphasis">D</span>ecember 2016, two months after end of the Soberanes fire, found Maria Ferdin <SMALL>(as a VWA Volunteer Wilderness Ranger)</SMALL> and myself backpacking to Pat Spring from Bottchers Gap to survey and photograph the fire damage <SMALL>(under USFS auspices since forest closure order was still&nbsp;in&nbsp;effect)</SMALL>.</DIV></p>
<p>It was ugly, disheartening to see places I was familiar with and loved so badly burnt.&nbsp;  The Soberanes burnt &#8216;hot&#8217; in many places &#8211; burning much which had survived all previous fires,<br />
including a favorite of mine, the <a href="/ROUTES/RATTLESNAKE/RattlesnakeCreekTrail-RattlesnakeCamp.html#historic_signpost">historic &#8220;lost Rattlesnake Trail&#8221; signpost</a>.</p>
<p><DIV>Unburnt sign &#8211; with bolt from lost trail signboard<BR><img decoding="async" class="photo landscape" src="https://bigsurtrailmap.net/blog/wp-content/uploads/2026/09/Historic_VDC_Trail_signpost_with_oval.jpg" alt="Unburnt sign - with bolt from lost trail signboard"> <!-- 816x612 --></DIV><br />
<DIV>Burnt signpost &#8211; but bolts remain <BR><img decoding="async" class="photo landscape" src="https://bigsurtrailmap.net/blog/wp-content/uploads/2026/09/Burnt_signpost.jpg" alt="Burnt signpost - but bolts remain"></DIV><br />
<BR><br />
<DIV style='line-height: 1.1'><DIV class='blockhilite'><B>Photos from that hike</B></DIV><BR><SMALL><I>from Maria Ferdin</I></SMALL></DIV></p>
<p>An ugly landscape &#8211; ridgeline to Pat Spring<BR> <img decoding="async" class="photo landscape" src="https://bigsurtrailmap.net/blog/wp-content/uploads/2026/09/Ugly_landscape_ridgeline_to_Pat_Spring.jpg" alt="An ugly landscape - ridgeline to Pat Spring"></p>
<p>Skinner Ridge stubble <img decoding="async" class="photo landscape" src="https://bigsurtrailmap.net/blog/wp-content/uploads/2026/09/Skinner_Ridge_stubble.jpg" alt="Skinner Ridge stubble"></p>
<p><DIV><B>Panorama</B><BR>Little Pines ridge<BR><SMALL><I>(can use mouse to stop/drag)</I></SMALL></p>
<div class="panorama-animated" role="img" aria-label="Panorama: Little Pines ridge" data-width="2512" data-height="800" style="background-image:url('https://bigsurtrailmap.net/blog/wp-content/uploads/2026/09/Little_Pines_ridge_panorama.jpg')"></div>
<p></DIV></p>
<p><DIV><B>Panorama</B>&nbsp;<BR> Big Pines is gone<BR><SMALL><I>(can use mouse to stop/drag)</I></SMALL></p>
<div class="panorama-animated" role="img" aria-label="Panorama: Big Pines is gone" data-width="2560" data-height="556" style="background-image:url('https://bigsurtrailmap.net/blog/wp-content/uploads/2026/09/Big_Pines_is_gone_panorama.jpg')"></div>
<p></DIV></p>
<p><!-- UNUSED 
 maria approaching little pines
  https://lh3.googleusercontent.com/d/0B28FBFYyBh3zQ2RuaFMycDhUcGc=h800?authuser=0
 Skinner ridge rest stop pano:
  https://lh3.googleusercontent.com/d/0B28FBFYyBh3zSmxzSEs5LUNkdTg=h800?authuser=0
--></p>
<p><BR><DIV>I later made a &#8220;photomap&#8221; to display photos taken along the route &#8211; you can view <SMALL>(with LOTS of ugly photos and panoramas)</SMALL> at:<BR><DIV></p>
<p><button  class='basic-button-large' onclick="click_404('blog-SoberanesPatSpringSurvey-photomap');window.open('/MAPS/PHOTOMAP/PatSpringPostfireTrailSurvey.html', '_self')">Pat Spring Post-Fire Survey &#8211; Photomap</button><img class='photo' style='padding:6px;cursor:pointer;' src='https://bigsurtrailmap.net/blog/wp-content/uploads/2026/09/Pat_Spring_Post-Fire_Trail_Survey-photomap-screenshot2.halfsize.png' onclick="click_404('blog-SoberanesPatSpringSurvey-photomap');window.open('/MAPS/PHOTOMAP/PatSpringPostfireTrailSurvey.html', '_self')" alt="Pat Spring post-fire survey - photomap"><DIV style='display:inline-block;padding:6px 4px;border: 1px solid black'><SMALL>Use top-left <IMG style='position:relative;top:1px;width:12px;height:12px;background-color:black;display:inline;margin:0;' SRC='https://bigsurtrailmap.net/blog/wp-content/uploads/2026/09/whitearrow_next_transparentbkg.png' alt="right arrow"> to advance<BR>showing photos along trail</SMALL></DIV></DIV></DIV></p>
<hr>
<p><BR></p>
<p><DIV style='color:#cc0000;font-size:200%;font-weight:bold;'>THE BAD</DIV></p>
<p><DIV style="padding-top:20px;"><span class="emphasis">I</span>n December I also led a Meetup hike from Los Padres Dam along Big Pines Trail to the the serpentine rocks which give that &#8216;Blue Rocks Ridge&#8217; its name.&nbsp;  This area was on the edge of the Soberanes burn so while hiking through the burnt area could see unburnt neighboring areas with their promise of future recovery.</DIV></p>
<p><DIV style='line-height: 1.1'><DIV class='blockhilite'><B>Photos from that hike</B></DIV><BR><SMALL><I>from Jack Glendening</I></SMALL></DIV></p>
<p><DIV>Burnt sign post<BR><img decoding="async" class="photo portrait" src="https://bigsurtrailmap.net/blog/wp-content/uploads/2026/09/IMG_0470.georef.jpg" alt="Burnt sign post"></DIV><br />
<DIV>Burnt brush with regrowth<BR><img decoding="async" class="photo landscape" src="https://bigsurtrailmap.net/blog/wp-content/uploads/2026/09/IMG_0714.georef.jpg" alt="Burnt brush with regrowth"></DIV></p>
<p><DIV><B>Panorama</B>&nbsp;<BR> Blue Rock ridge with serpentine<BR>Cleared by dozer for firebreak<BR><SMALL><I>(can use mouse to stop/drag)</I></SMALL></p>
<div class="panorama-animated" role="img" aria-label="Panorama: Blue Rock ridge with serpentine" data-width="2286" data-height="713" style="background-image:url('https://bigsurtrailmap.net/blog/wp-content/uploads/2026/09/Burn_Serpentine.pano2_.georef.jpg')"></div>
<p></DIV></p>
<p><DIV><B>Panorama</B>&nbsp;<BR> Unburnt areas in the distance<BR><SMALL><I>(can use mouse to stop/drag)</I></SMALL></p>
<div class="panorama-animated" role="img" aria-label="Panorama: unburnt areas" data-width="2560" data-height="400" style="background-image:url('https://bigsurtrailmap.net/blog/wp-content/uploads/2026/09/BigPinesFirebreak.pano_.georef.jpg')"></div>
<p> <!-- 14254x2225 --></DIV></p>
<hr>
<p><BR></p>
<p><DIV style='color:#cc0000;font-size:200%;font-weight:bold;'>THE GOOD</DIV></p>
<p><DIV style="padding-top:20px;"><span class="emphasis">S</span>ome good did result from the Soberanes fire, notably in the explosion of flowers following the fire &#8211; including seldom seen &#8220;fire-folling&#8221; plants.&nbsp;  And in clearing brush from some trails previously nigh-unto-impossible to hike.</DIV></p>
<p>So nineteen months after the Soberanes fire, Maria Ferdin and I took that opportunity to backpack along the Black Cone Trail, which previously had been overgrown with very discouraging <SMALL>(and very few)</SMALL> trail reports but now was very do-able.</p>
<p><DIV style='line-height: 1.1'><DIV class='blockhilite'><B>Photos from that hike</B></DIV><BR><SMALL><I>from Maria Ferdin and Jack Glendening</I></SMALL></DIV></p>
<p>Fire-following Redray Alpengold<BR> <img decoding="async" class="photo landscape" src="https://bigsurtrailmap.net/blog/wp-content/uploads/2026/09/Fire_following_redray_alpengold.jpg" alt="Fire-following redray alpengold"></p>
<p>Harlequin Lupin<BR> <img decoding="async" class="photo landscape" src="https://bigsurtrailmap.net/blog/wp-content/uploads/2026/09/Harlequin_lupin.jpg" alt="Harlequin lupin"></p>
<p>Flowers along Black Cone Trail<BR><img decoding="async" class="photo portrait" src="https://bigsurtrailmap.net/blog/wp-content/uploads/2026/09/Flowers_along_Black_Cone_Trail.jpg" alt="Flowers along black cone trail"></p>
<p><DIV><B>Panorama</B>&nbsp;<BR> Black Cone far ahead, La Ventana far behind<BR><SMALL><I>(can use mouse to stop/drag)</I></SMALL></p>
<div class="panorama-animated" role="img" aria-label="Panorama: Black Cone far ahead, La Ventana far behind" data-width="2560" data-height="582" style="background-image:url('https://bigsurtrailmap.net/blog/wp-content/uploads/2026/09/Black_Cone_La_Ventana_panorama.jpg')"></div>
<p> <!-- 3468 x 788 --></DIV></p>
<p><!-- <DIV><B>Panorama</B>&nbsp;<BR> White Cone <small>(and Black Cone)</small> getting nearer<BR><SMALL><I>(can use mouse to stop/drag)</I></SMALL>

<div class="panorama-animated" role="img" aria-label="panorama: White Cone (and Black Cone) getting nearer" data-width="2560" data-height="582" style="background-image:url('https://bigsurtrailmap.net/blog/wp-content/uploads/2026/09/White_Cone_Black_Cone_panorama.jpg')"></div>

</DIV> --></p>
<p><DIV><B>Panorama</B>&nbsp;<BR> Nearing White Cone<BR><SMALL><I>(can use mouse to stop/drag)</I></SMALL></p>
<div class="panorama-animated" role="img" aria-label="Panorama: Nearing White Cone" data-width="2560" data-height="644" style="background-image:url('https://bigsurtrailmap.net/blog/wp-content/uploads/2026/09/Nearing_White_Cone_panorama.jpg')"></div>
<p></DIV></p>
<p><BR><DIV>I also I made an &#8220;photomap&#8221; <SMALL>(different format from the previous)</SMALL> to display photos taken along that route &#8211; you can view <SMALL>(with lots of flowers and many panoramas)</SMALL> at:<BR><BR><BUTTON class='basic-button-large' onclick="click_404('blog-BlackConeBackpack-photomap');window.open('/MAPS/PHOTOMAP/BlackConeTrailPlusBackpack.photomap.html', '_self')">Black Cone Trail Backpack &#8211; Photomap</BUTTON><img class='photo' style='padding:6px;cursor:pointer;' src='https://bigsurtrailmap.net/blog/wp-content/uploads/2026/09/Black_Cone_Peak_Backpack-photomap_sans_header-screenshot3.halfsize.png' onclick="click_404('blog-BlackConeBackpack-photomap');window.open('/MAPS/PHOTOMAP/BlackConeTrailPlusBackpack.photomap.html', '_self')" alt="Black Cone Trail backpack - photomap"><DIV style='display:inline-block;padding:6px 4px;border: 1px solid black'><SMALL>Hike was in burnt and&nbsp;un-burnt&nbsp;areas<BR>Gray&nbsp;overlay&nbsp;indicates&nbsp;burnt&nbsp;area<BR>Use top-right <IMG style='position:relative;top:1px;width:12px;height:12px;background-color:black;display:inline;margin:0;' SRC='https://bigsurtrailmap.net/blog/wp-content/uploads/2026/09/whitearrow_next_transparentbkg.png' alt="Right arrow"> to advance<BR>showing photos along trail</SMALL></DIV></DIV></p>
<hr>
<p><BR></p>
<p><DIV style='color:#cc0000;font-size:200%;font-weight:bold;'>THE HISTORY</DIV></p>
<p><DIV style="padding-top:20px;"><span class="emphasis">A</span>nimated map of Soberanes Fire burn scar <SMALL>[June&nbsp;24&nbsp;-October&nbsp;13]</SMALL> &#8211; <U>click its <span onclick="click_404('blog-SoberanesFire-animatedmap');window.open('/MAPS/FIRE/SOBERANES/fireperimeterhistory.googlemaps_display_overlay.html', '_self');" style="display:inline-block;padding:0 6px;background:#f2f2f2;border:1px solid #999;border-radius:3px;font-family:Arial,sans-serif;font-size:0.85em;line-height:1.5;color:#000;vertical-align:middle;position:relative;top:-3px;cursor:pointer;">Loop</span> button</U> to start day-by-day time-lapse of burn progression<SMALL>(previous&nbsp;day&nbsp;burn&nbsp;=&nbsp;white&nbsp;line, new&nbsp;day&nbsp;burn&nbsp;=&nbsp;red&nbsp;line)</SMALL>&nbsp;.&nbsp;  Note erratic growth spurts.</DIV></p>
<p><DIV><button class='basic-button-large' onclick="click_404('blog-SoberanesFire-animatedmap');window.open('/MAPS/FIRE/SOBERANES/fireperimeterhistory.googlemaps_display_overlay.html', '_self');">Soberanes Fire Burn &#8211; Animated Map</button><img decoding="async" class='photo' style='padding:6px;cursor:pointer;' src="https://bigsurtrailmap.net/blog/wp-content/uploads/2026/09/Soberanes_Fire_Map.356x383.png" onclick="click_404('blog-SoberanesFire-animatedmap');window.open('/MAPS/FIRE/SOBERANES/fireperimeterhistory.googlemaps_display_overlay.html', '_self')" alt="Soberanes Fire burn - animated map"><DIV style='display:NONE;padding:6px 4px;border: 1px solid black'><SMALL><U>Click its &#8216;Loop&#8217; button</U> to start time-lapse display of burn<BR>Red &#038; white lines = current &#038; previous day perimeters<BR>Orange fill = intense current day burn</SMALL></DIV></DIV><br />
</DIV>  <!-- END OF POST-WIDE CENTERING DIV --></p>
<p><!-- *** JS FOR ANIMATED PANORAMA IMAGE SCRIPT *** --><br />
<script>
//AIo-17-09-26 Size each panorama pan to its actual image width and stop animation when dragged.
//AIo-17-09-26 Apply a shared pixel speed to every panorama.
const PANORAMA_SPEED_PX_PER_SECOND = 100;
const PANORAMA_ELEMENTS = document.querySelectorAll(".panorama-animated");
PANORAMA_ELEMENTS.forEach(panorama => {
  let panoramaDragging = false;
  let panoramaLastX = 0;
  let panoramaPositionX = 0;
  update_panorama_range(panorama);
  panorama.addEventListener("pointerdown", event => {
    const panoramaPositionText = getComputedStyle(panorama).backgroundPositionX;
    panoramaPositionX = parseFloat(panoramaPositionText) || 0;
    panorama.style.animation = "none";
    panorama.style.backgroundPositionX = panoramaPositionText;
    panoramaDragging = true;
    panoramaLastX = event.clientX;
    panorama.classList.add("is-dragging");
    panorama.setPointerCapture(event.pointerId);
  });
  panorama.addEventListener("pointermove", event => {
    if (!panoramaDragging) return;
    const panoramaMaxOffset = Number(panorama.dataset.maxOffset);
    panoramaPositionX += event.clientX - panoramaLastX;
    panoramaPositionX = Math.min(0, Math.max(-panoramaMaxOffset, panoramaPositionX));
    panorama.style.backgroundPositionX = `${panoramaPositionX}px`;
    panoramaLastX = event.clientX;
  });
  panorama.addEventListener("pointerup", () => {
    panoramaDragging = false;
    panorama.classList.remove("is-dragging");
  });
  panorama.addEventListener("pointercancel", () => {
    panoramaDragging = false;
    panorama.classList.remove("is-dragging");
  });
});
window.addEventListener("resize", () => {
  PANORAMA_ELEMENTS.forEach(update_panorama_range);
});
//AIo-17-09-26 Recalculate the end position and travel duration when the viewport width changes.
function update_panorama_range(panorama) {
  const panoramaNaturalWidth = Number(panorama.dataset.width);
  const panoramaNaturalHeight = Number(panorama.dataset.height);
  const panoramaRenderedWidth = panoramaNaturalWidth * panorama.clientHeight / panoramaNaturalHeight;
  //AIo-17-09-26 Limit the viewport to the rendered image width before measuring pan distance.
  panorama.style.maxWidth = `${panoramaRenderedWidth}px`;
  const panoramaMaxOffset = Math.max(0, panoramaRenderedWidth - panorama.clientWidth);
  panorama.dataset.maxOffset = panoramaMaxOffset;
  panorama.style.setProperty("--panorama-end-x", `${-panoramaMaxOffset}px`);
  const panoramaDurationSeconds = panoramaMaxOffset / PANORAMA_SPEED_PX_PER_SECOND;
  panorama.style.setProperty("--panorama-duration", `${panoramaDurationSeconds}s`);
  if (panorama.style.animation === "none") {
    const panoramaCurrentX = parseFloat(panorama.style.backgroundPositionX) || 0;
    panorama.style.backgroundPositionX = `${Math.min(0, Math.max(-panoramaMaxOffset, panoramaCurrentX))}px`;
  }
}
</script></p>
]]></content:encoded>
					
					<wfw:commentRss>https://bigsurtrailmap.net/blog/soberanes-fire-reminiscences-ugly-bad-and-good/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Finding the Mount Manuel Trail &#8211; Hike 3</title>
		<link>https://bigsurtrailmap.net/blog/finding-the-mount-manuel-trail-hike-3/</link>
					<comments>https://bigsurtrailmap.net/blog/finding-the-mount-manuel-trail-hike-3/#respond</comments>
		
		<dc:creator><![CDATA[Jack Glendening]]></dc:creator>
		<pubDate>Wed, 01 Apr 2026 18:42:44 +0000</pubDate>
				<category><![CDATA[hike]]></category>
		<category><![CDATA[mapping]]></category>
		<guid isPermaLink="false">https://bigsurtrailmap.net/blog/?p=3030</guid>

					<description><![CDATA[Trailwork with friends, bypassing the &#8220;Apex of Brushiness&#8221; and lots of photos of brush (with Paul Danielson, Maria Ferdin, and Burke Siedhoff) Hike 3 = Yellow Launtz Creek Camp having been &#8220;found&#8221;, Paul Danielson and I wanted to bring some friends out, to show them the trail and camp &#8211; and to get additional help [&#8230;]]]></description>
										<content:encoded><![CDATA[<div class="center" style="font-size: 20px">
<b>Trailwork with friends,<br />
<span class="nowrap">bypassing the &#8220;Apex of Brushiness&#8221;</span><br />
<span class="nowrap" style="font-size: 16px">and lots of photos of brush</span></b><br />
<span style="font-size: 13px">(with Paul Danielson, Maria Ferdin, and Burke Siedhoff)</span>
</div>
<div class="snippet-only" style="float: left;margin:10px 20px 0 0">
<div style="width: 191px;line-height: 100%;border: 1px solid gray;text-align:center">
<img decoding="async" style="width: 100%" src="https://bigsurtrailmap.net/blog/wp-content/uploads/2024/10/mtmanuel_flagging_history-hike3legend.574x733.png"><b>Hike 3 = Yellow</b>
</div>
</div>
<div style="padding-top:20px"><span class="emphasis">L</span>auntz Creek Camp having been &#8220;found&#8221;, Paul Danielson and I wanted to bring some friends out, to show them the trail and camp &#8211; and to get additional help clearing the trail.&nbsp; So eight months later, January 2013, we arrived at Pico Blanco Scout Reservation along with Maria Ferdin <SMALL>(a founder of Monterey Bay Area Hiking Group and frequent hiking companion of mine)</SMALL> and Burke Siedhoff <SMALL>(a grand old hiker always brimming with enthusiasm)</SMALL>.</div>
<p> </p>
<hr>
<p><span id="more-3030"></span></p>
<div class="post-only">
<div class="center" style="max-width: 574px;line-height: 100%;border: 1px solid gray;text-align:center"><img decoding="async" style="width: 100%" src="https://bigsurtrailmap.net/blog/wp-content/uploads/2024/10/mtmanuel_flagging_history-hike3legend.574x733.png"><b>Hike<br />
3 = Yellow</b> &nbsp;<small>[Outbound=thick Return=thin]</small><br />
<span style="line-height: 50%;font-size: smaller"><i><a href="https://bigsurtrailmap.net/ROUTES/MT_MANUEL/HISTORY/flagginghikehistory.googlemaps_display_overlay.html?i=4&amp;ll=36.3159,-121.7963&amp;z=16" target="_blank" rel="noopener">Above is screenshot &#8211; <b>Click for Interactive map</b></a></i></span> </div>
</p></div>
<p></p>
<p>Again heading up Little Sur Trail,</p>
<p><img fetchpriority="high" decoding="async" class="block center aligncenter" style="max-width: 640px;width:100%;height: auto" src="https://bigsurtrailmap.net/blog/wp-content/uploads/2026/03/LauntzCamp_hike3_0083.jpg" width="800" height="600"></p>
<p><img decoding="async" class="block center aligncenter" style="max-width: 640px;width:100%;height: auto" src="https://bigsurtrailmap.net/blog/wp-content/uploads/2026/03/LauntzCamp_hike3_danielson_1185.georef.jpg" width="800" height="600"></p>
<p><img decoding="async" class="block center aligncenter" style="max-width: 640px;width:100%;height: auto" src="https://bigsurtrailmap.net/blog/wp-content/uploads/2026/03/LauntzCamp_hike3_danielson_1228.georef.jpg" width="800" height="600"></p>
<p>in much better condition than on our first hike in 2012, thanks to some recent VWA trailwork,</p>
<p><img loading="lazy" decoding="async" class="block center aligncenter" style="max-width: 640px;width:100%;height: auto" src="https://bigsurtrailmap.net/blog/wp-content/uploads/2026/03/LauntzCamp_hike3_danielson_1226.georef.jpg" width="800" height="600"></p>
<p><img loading="lazy" decoding="async" class="block center aligncenter" style="max-width: 640px;width:100%;height: auto" src="https://bigsurtrailmap.net/blog/wp-content/uploads/2026/03/LauntzCamp_hike3_danielson_1188.georef.jpg" width="800" height="600"></p>
<p>we reached the northern end of the Mount Manuel Trail.&nbsp;</p>
<p><img loading="lazy" decoding="async" class="block center aligncenter" style="max-width: 640px;width:100%;height: auto" src="https://bigsurtrailmap.net/blog/wp-content/uploads/2026/03/LauntzCamp_hike3_0085.jpg" width="800" height="600"></p>
<p><img loading="lazy" decoding="async" class="block center aligncenter" style="max-width: 640px;width:100%;height: auto" src="https://bigsurtrailmap.net/blog/wp-content/uploads/2026/03/LauntzCamp_hike3_0086.jpg" width="800" height="600"></p>
<p>The change in trail condition was immediately apparent</p>
<p><img loading="lazy" decoding="async" class="block center aligncenter" style="max-width: 640px;width:100%;height: auto" src="https://bigsurtrailmap.net/blog/wp-content/uploads/2026/03/LauntzCamp_hike3_danielson_1191.georef.jpg" width="800" height="600"></p>
<p><img loading="lazy" decoding="async" class="block center aligncenter" style="max-width: 640px;width:100%;height: auto" src="https://bigsurtrailmap.net/blog/wp-content/uploads/2026/03/LauntzCamp_hike3_0092.jpg" width="800" height="600"></p>
<p>bringing out our loppers and saws.</p>
<p><img loading="lazy" decoding="async" class="block center aligncenter" style="max-width: 640px;width:100%;height: auto" src="https://bigsurtrailmap.net/blog/wp-content/uploads/2026/03/LauntzCamp_hike3_0112.jpg" width="800" height="600"></p>
<p>As we crossed over the ridge, we got a view of Pico Blanco </p>
<p><img loading="lazy" decoding="async" class="block center aligncenter" style="max-width: 640px;width:100%;height: auto" src="https://bigsurtrailmap.net/blog/wp-content/uploads/2026/03/LauntzCamp_hike3_0147.jpg" width="800" height="600"></p>
<p>and the trail was much less brushy, though also with less tread to follow</p>
<p><img loading="lazy" decoding="async" class="block center aligncenter" style="max-width: 640px;width:100%;height: auto" src="https://bigsurtrailmap.net/blog/wp-content/uploads/2026/03/LauntzCamp_hike3_danielson_1195.georef.jpg" width="800" height="600"></p>
<p>yet helpfully marked by the noteworthy boundary tree marker.</p>
<p><img loading="lazy" decoding="async" class="block center aligncenter" style="max-width: 640px;width:100%;height: auto" src="https://bigsurtrailmap.net/blog/wp-content/uploads/2026/03/LauntzCamp_hike3_0096.jpg" width="800" height="600"></p>
<p><img loading="lazy" decoding="async" class="block center aligncenter" style="max-width: 640px;width:100%;height: auto" src="https://bigsurtrailmap.net/blog/wp-content/uploads/2026/03/LauntzCamp_hike3_0098.jpg" width="800" height="600"></p>
<p>and again finding the first trail-marking rockwork.</p>
<p><img loading="lazy" decoding="async" class="block center aligncenter" style="max-width: 640px;width:100%;height: auto" src="https://bigsurtrailmap.net/blog/wp-content/uploads/2026/04/LauntzCamp_hike3_0106-rockwork.jpg" width="800" height="600"></p>
<p><B>HOWEVER</B> our past hikes had always been difficult around the &#8220;Apex of Brushiness&#8221; <B>SO</B> this time I wanted to try bypassing it, shortening the route via a bushwhack.&nbsp; Past the trail-identifying rockwork, we headed upslope and over the ridgeline &#8211; giving a good view of the Little Sur River drainage</p>
<p><img loading="lazy" decoding="async" class="block center aligncenter" style="max-width: 640px;width:100%;height: auto" src="https://bigsurtrailmap.net/blog/wp-content/uploads/2026/03/LauntzCamp_hike3_danielson_1196.georef.jpg" width="800" height="600"></p>
<p><img loading="lazy" decoding="async" class="block center aligncenter" style="max-width: 640px;width:100%;height: auto" src="https://bigsurtrailmap.net/blog/wp-content/uploads/2026/03/LauntzCamp_hike3_0110.jpg" width="800" height="600"></p>
<p>then down to the trail again and more brush</p>
<p><img loading="lazy" decoding="async" class="block center aligncenter" style="max-width: 640px;width:100%;height: auto" src="https://bigsurtrailmap.net/blog/wp-content/uploads/2026/03/LauntzCamp_hike3_danielson_1202.georef.jpg" width="800" height="600"></p>
<p><img loading="lazy" decoding="async" class="block center aligncenter" style="max-width: 640px;width:100%;height: auto" src="https://bigsurtrailmap.net/blog/wp-content/uploads/2026/03/LauntzCamp_hike3_danielson_1214.georef.jpg" width="800" height="600"></p>
<p>and finding the second trail-marking rock wall.&nbsp;</p>
<p><img loading="lazy" decoding="async" class="block center aligncenter portrait" style="max-width: 480px;height: auto" src="https://bigsurtrailmap.net/blog/wp-content/uploads/2026/03/LauntzCamp_hike3_0121.jpg" width="600" height="800"></p>
<p>Even resting occasionally.&nbsp;</p>
<p><img loading="lazy" decoding="async" class="block center aligncenter" style="max-width: 640px;width:100%;height: auto" src="https://bigsurtrailmap.net/blog/wp-content/uploads/2026/03/LauntzCamp_hike3_0152.jpg" width="800" height="600"></p>
<p>Then leaving the trail to bushwhack down slope to Launtz Creek</p>
<p><img loading="lazy" decoding="async" class="block center aligncenter" style="max-width: 640px;width:100%;height: auto" src="https://bigsurtrailmap.net/blog/wp-content/uploads/2026/03/LauntzCamp_hike3_0123.jpg" width="800" height="600"></p>
<p>and Launtz Creek Camp</p>
<p><img loading="lazy" decoding="async" class="block center aligncenter" style="max-width: 640px;width:100%;height: auto" src="https://bigsurtrailmap.net/blog/wp-content/uploads/2026/03/LauntzCamp_hike3_danielson_1208.georef.jpg" width="800" height="600"></p>
<p><img loading="lazy" decoding="async" class="block center aligncenter" style="max-width: 640px;width:100%;height: auto" src="https://bigsurtrailmap.net/blog/wp-content/uploads/2026/03/LauntzCamp_hike3_danielson_1204.georef.jpg" width="800" height="600"></p>
<p>where we enjoyed lunch, rest, and conversation.&nbsp;</p>
<p><img loading="lazy" decoding="async" class="block center aligncenter" style="max-width: 640px;width:100%;height: auto" src="https://bigsurtrailmap.net/blog/wp-content/uploads/2026/03/LauntzCamp_hike3_0132.jpg" width="800" height="600"></p>
<p><img loading="lazy" decoding="async" class="block center aligncenter" style="max-width: 640px;width:100%;height: auto" src="https://bigsurtrailmap.net/blog/wp-content/uploads/2026/03/LauntzCamp_hike3_danielson_1205.georef.jpg" width="800" height="600"></p>
<p>Afterward, bushwacking upslope to find the trailbed</p>
<p><img loading="lazy" decoding="async" class="block center aligncenter" style="max-width: 640px;width:100%;height: auto" src="https://bigsurtrailmap.net/blog/wp-content/uploads/2026/03/LauntzCamp_hike3_danielson_1211.georef.jpg" width="800" height="600"></p>
<p><img loading="lazy" decoding="async" class="block center aligncenter" style="max-width: 640px;width:100%;height: auto" src="https://bigsurtrailmap.net/blog/wp-content/uploads/2026/03/LauntzCamp_hike3_danielson_1217.georef.jpg" width="800" height="600"></p>
<p>our trek back was aided by our outward-bound trail clearing (find the<br />
people).&nbsp;</p>
<p><img loading="lazy" decoding="async" class="block center aligncenter" style="max-width: 640px;width:100%;height: auto" src="https://bigsurtrailmap.net/blog/wp-content/uploads/2026/03/LauntzCamp_hike3_danielson_1222.georef.jpg" width="800" height="600"></p>
<p>This this time we <B>DID</B> go through the &#8220;Apex of Brushiness&#8221;, hacking away at it a bit more &#8211; no actual photo, due to too much brush, but two preceding sections are shown below</p>
<p><img loading="lazy" decoding="async" class="block center aligncenter" style="max-width: 640px;width:100%;height: auto" src="https://bigsurtrailmap.net/blog/wp-content/uploads/2026/03/LauntzCamp_hike3_danielson_1214.georef.jpg" width="800" height="600"></p>
<p><img loading="lazy" decoding="async" class="block center aligncenter" style="max-width: 640px;width:100%;height: auto" src="https://bigsurtrailmap.net/blog/wp-content/uploads/2026/03/LauntzCamp_hike3_danielson_1218.georef.jpg" width="800" height="600"></p>
<p>after which we needed a rest&nbsp;</p>
<p><img loading="lazy" decoding="async" class="block center aligncenter" style="max-width: 640px;width:100%;height: auto" src="https://bigsurtrailmap.net/blog/wp-content/uploads/2026/03/LauntzCamp_hike3_danielson_1221.georef.jpg" width="800" height="600"></p>
<p>&lt;!&#8211;OMITTED PHOTO (find the hidden person) <img loading="lazy" decoding="async" class="block center aligncenter" style="max-width: 640px;width:100%;height: auto" src="https://bigsurtrailmap.net/blog/wp-content/uploads/2026/03/LauntzCamp_hike3_0154.jpg" width="800" height="600"> and finally returning just before dark.&nbsp; &#8211;&gt; before continuing and returning just before dark.</p>
<p><img loading="lazy" decoding="async" class="block center aligncenter portrait" style="max-width: 640px;height: auto" src="https://bigsurtrailmap.net/blog/wp-content/uploads/2026/04/LauntzCamp_hike3_danielson_1189.georef.jpg" width="800" height="600"></p>
<p>Total hike time was 9.6&nbsp;hours.&nbsp;  A sense for the roughness of trail and hike difficulty can be seen in our hiking speeds: 1.7&nbsp;mph <small>(steep uphill)</small> and 2.0&nbsp;mph on our outbound and return legs along the Little Sur Trail but slowing to 0.38&nbsp;mph and 0.33&nbsp;mph respectively on the Mount Manuel Trail to the camp.&nbsp;</p>
<p>Hope you have had your fill of brushy photos!&nbsp; Had more photos this time due to presence of Maria Ferdin and more pausing time since trail better cleared than on first two hikes, so wanted to better document the level of overgrowth back in 2013.</p>
<p><SMALL><I>Photos by Maria Ferdin and Paul Danielson</I></SMALL></p>
]]></content:encoded>
					
					<wfw:commentRss>https://bigsurtrailmap.net/blog/finding-the-mount-manuel-trail-hike-3/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Abusive behavior deserves rebuff</title>
		<link>https://bigsurtrailmap.net/blog/abusive-behavior-deserves-rebuff/</link>
					<comments>https://bigsurtrailmap.net/blog/abusive-behavior-deserves-rebuff/#comments</comments>
		
		<dc:creator><![CDATA[Jack Glendening]]></dc:creator>
		<pubDate>Fri, 12 Sep 2025 16:40:59 +0000</pubDate>
				<category><![CDATA[Uncategorized]]></category>
		<guid isPermaLink="false">https://bigsurtrailmap.net/blog/?p=3489</guid>

					<description><![CDATA[A certain Big Sur habitant, having a long history of venomous verbal attacks on others and whom I will call &#8220;JB&#8221; aka BigSurRecCrew, sent me this email Tuesday morning a week after Labor Day: Update the maps old man.&#160; Why you stalling? Come on,you wanted to be the map guy.&#160; You wanted to help Vwa [&#8230;]]]></description>
										<content:encoded><![CDATA[<p><DIV style="height:1px;"></DIV>A certain Big Sur habitant, having a long history of venomous verbal attacks on others and whom I will call &#8220;JB&#8221; aka BigSurRecCrew, sent me this email Tuesday morning a week after Labor Day:</p>
<hr>
<p><span id="more-3489"></span></p>
<p><DIV style="font-size:90%; margin: 0px 30px; font-family: 'Courier New', Courier, monospace">Update the maps old man.&nbsp;  Why you stalling? Come on,you wanted to be the map guy.&nbsp;  You wanted to help Vwa gatekeep the illegal man made hot tub in lost valley.&nbsp;  Come on old man.&nbsp;  Why you shy all of a sudden?<br />
<br />
With no honor or integrity as a man, you should be much ashamed,but it takes honor and integrity to feel shame for false and misleading actions and intents.<br />
<br />
Up date your maps old man.&nbsp;  Dont be shy now.&nbsp;  I thought the whole point was open safe accessible trails for all.. you disingenuous, dishonest, disrespectful, old ass honky cracker piece of shit  its white folks like you that Ive spent my entire life apologizing to everyone else for youre fucking disgusting<br />
</DIV></p>
<p>Hard to believe anyone would think this type of abusive email would get the desired response.&nbsp;  Has throwing a tantrum and calling names ever worked for him  &#8211; would you do as he demands ??  The only people I know who would get abused and then take  orders are slaves &#8211; or wimps.</p>
<p>For me, a push back is my response.&nbsp;  I do expect civility in interactions and will cold shoulder anyone who assaults me verbally &#8211; so will in the future be ignoring JB.  I decided to make these circumstances public since all sorts of stories might circulate in the chatterworld, where people hide behind anonymity. </p>
<p>Ironically, I had planned to honor a request he&#8217;d made in an email four days before <SMALL>(see <I>&#8220;Back story&#8221;</I> below)</SMALL>, as I&#8217;ve honored other trail reports made directly to me in the past.&nbsp;  But not now.</p>
<p>To be clear, this website will continue to use and show all VWA Trail Reports (or civil reports sent privately, on the trailmap forum, &#8230;).&nbsp;  But &#8211; I was the one who had been approving JB&#8217;s previous trail reports there, which I will no longer do.&nbsp;  The VWA relies heavily on volunteers <SMALL>(its Trails program is 100% volunteer-run)</SMALL>.&nbsp;  Volunteers do what they want to do &#8211; if no volunteer wants to do something, it doesn&#8217;t get done.&nbsp;  The VWA Forum is maintained by volunteers and awhile back their number had shrunk to just one who is often away <SMALL>(the displayed &#8216;Moderator&#8217; list is out of date)</SMALL>.  So I&#8217;d stepped in to help and lately have been the one doing most post approvals there from unregistered users.  But in the future some other VWA volunteer must willing to do any JB approvals &#8211; which is questionable, as he has been directing this same kind of venom towards both the VWA and individual volunteers for some time now.  Somehow he expects to do that and still have others do things to benefit him.  I know someone at some time will hike the trail and send in a VWA trail report, so that will suffice.  </p>
<p><!-- Ironically his being so pushy and impatient -- sending an email on Friday, then insulting me on Tuesday -- means he shot himself in the foot.  If he had waited just one more day, the result he wanted would have appeared on the trailmap. --></p>
<p>I thought only children threw tantrums, acted out and called people names.&nbsp;  At least I now know what he really thinks of me! <img src="https://s.w.org/images/core/emoji/17.0.2/72x72/1f642.png" alt="🙂" class="wp-smiley" style="height: 1em; max-height: 1em;" /> Seems to be a lot of hate out there, but life goes on, even for us &#8220;old men&#8221;.</p>
<p><U><I>Back story</I></U></p>
<p>On Labor Day evening my server farm needed to do &#8216;maintenance&#8217; on my server.&nbsp;  The server then rebooted &#8211; but without any connection to its network!  So on Tuesday the website was unreachable and I myself could not reach it as administrator.&nbsp;  Making a long story short, it took three stress-filled days with help from AWS support to find an obscure problem &#8211; the bootup script itself had somehow become corrupted, so would get the server running but without a network connection.   Replacing that script with an uncorrupted file and re-booting, the website was finally back up on the internet on Friday.</p>
<p><!-- So I had to pay AWS support for some help.  
Which turned out to be slow and frustrating.&nbsp;  I did not pay for 'enterprise' support, support was in Indian time zone, and for 'privacy' reasons support refuses to look at a server directly  - all they would do is make suggestions which I would follow, then report back and wait 6-12 hours for a response.&nbsp;  The problem proved resistant to my skills and after much back and forthing the website was still down Thursday.&nbsp;  So Thursday evening they offered to do a screen-sharing, giving immediate feedback on my interactions.  Thankfully the assigned Operating System expert knew much more than I - but it still took 2 hours to discover that the "initialization" script which starts the computer had somehow become corrupted, leaving the network unconnected. --></p>
<p>So I was burnt out and needed to get away for awhile.  Sometime Friday or Saturday, can&#8217;t now remember which, noted I&#8217;d been sent a trail report email by JB and mentally put it into my &#8220;to do later&#8221; bucket.&nbsp;  Then on Tuesday, when I again sat down to do some trailmap work, I first read my email and found the above gem.&nbsp;  If JB had waited one more day before sending, or just send a rational email, the trailmap would have been changed as he desired. </p>
<p>But that is now a what if, in a now different alternative universe. <!-- I cannot un-know what I now know, the bridges have been burnt.--> Trying to be reasonable does not work with unreasonable people.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://bigsurtrailmap.net/blog/abusive-behavior-deserves-rebuff/feed/</wfw:commentRss>
			<slash:comments>2</slash:comments>
		
		
			</item>
		<item>
		<title>Finding the Mount Manuel Trail &#8211; Hike 2</title>
		<link>https://bigsurtrailmap.net/blog/finding-the-mount-manuel-trail-hike-2/</link>
					<comments>https://bigsurtrailmap.net/blog/finding-the-mount-manuel-trail-hike-2/#comments</comments>
		
		<dc:creator><![CDATA[Jack Glendening]]></dc:creator>
		<pubDate>Thu, 09 Jan 2025 18:29:03 +0000</pubDate>
				<category><![CDATA[hike]]></category>
		<category><![CDATA[mapping]]></category>
		<guid isPermaLink="false">https://blog.bigsurtrailmap.net/?p=2582</guid>

					<description><![CDATA[TEST EXCERPT]]></description>
										<content:encoded><![CDATA[<div class="center" style="font-size: 20px"><b>Extravagant flagging, <span class="nowrap">an unhappy couple</span>, <span class="nowrap">Launtz Creek Camp is &#8220;found&#8221;</span><br />
<span style="font-size: 16px">but have to shortcut trail</span></b><br />
<span style="font-size: 13px">(with Paul Danielson)</span></div>
<div class="snippet-only" style="float: left;margin:10px 20px 0 0">
<div style="width: 191px;line-height: 100%;border: 1px solid gray;text-align:center">
  <img decoding="async" style="width: 100%" src="https://bigsurtrailmap.net/blog/wp-content/uploads/2024/10/mtmanuel_flagging_history-hike2legend.574x733.png"/><b>Hike 2 = Orange</b>
  </div>
</div>
<div style="padding-top:20px"><span class="emphasis">O</span>ver a year after our first hike, in March of 2012 Paul Danielson and I decided to re-visit the &#8220;lost&#8221; Mount Manuel Trail &#8211; to go beyond the &#8216;Apex of Brushiness&#8217; which had stopped our last hike and hopefully reach, and so &#8220;find&#8221;, Launtz Creek Camp.&nbsp;  This turned out to be the most interesting hike of my 11 hikes &#8220;finding&#8221; the Mount Manuel trail.
</div>
<p></p>
<hr>
<p><span id="more-2582"></span></p>
<div class="post-only">
<div class="center" style="max-width: 574px;line-height: 100%;border: 1px solid gray;text-align:center">
<img decoding="async" style="width: 100%" src="https://bigsurtrailmap.net/blog/wp-content/uploads/2025/01/mtmanuel_flagging_history-hike2legend-tent.574x733.png"><b>Hike 2 = Orange</b> &nbsp;<small>[Outbound=thick Return=thin]</small><br />
<span style="line-height: 50%;font-size: smaller"><i><a href="https://bigsurtrailmap.net/ROUTES/MT_MANUEL/HISTORY/flagginghikehistory.googlemaps_display_overlay.html?i=3&amp;ll=36.3159,-121.7963&amp;z=16" target="_blank" rel="noopener">Above is screenshot &#8211; <b>Click for Interactive map</b></a></i></span>
</div>
</div>
<p></p>
<p>Learning from our last trip, this time we got to Pico Blanco Boy Scout Camp very early, 7:30 AM.&nbsp;  The hike up the Little Sur Trail to the Mount Manuel Trail trailhead was a bit easier than last time, now being familiar with the route, arriving there at 8:45.</p>
<p>Heading out on the Mount Manuel Trail, we were in for a surprise.&nbsp;  Someone had been out on the trail, clearing some brush and also flagging their route.&nbsp;  The flagging was astounding &#8211; the most profligate flagging I&#8217;ve ever seen! Yards of magenta tape were hanging from branches, wrapped around tree trunks, etc.</p>
<p><img class="block center portrait" src='https://bigsurtrailmap.net/blog/wp-content/uploads/2026/04/FindingMtManuelTrailHike2_6296.georef.jpg'></p>
<p><img class="block center" src='https://bigsurtrailmap.net/blog/wp-content/uploads/2026/04/FindingMtManuelTrailHike2_6343.georef.jpg'></p>
<p><img class="block center portrait" src='https://bigsurtrailmap.net/blog/wp-content/uploads/2026/04/FindingMtManuelTrailHike2_6342.georef.jpg'></p>
<p>In wonder we followed this extravaganza along the north side of the ridge, to see where it would lead.  The clearing allowed easier passage than on our last hike, but its route lay a bit north of what we had then taken.</p>
<p>And then we found a tent with an unhappy couple. </p>
<p><img class="block center" src='https://bigsurtrailmap.net/blog/wp-content/uploads/2026/04/FindingMtManuelTrailHike2_6297.georef.jpg'></p>
<p>We learned they had intended to camp at Pico Blanco Public Camp, which lies along the <u>Little Sur</u> Trail.&nbsp;  Somehow they&#8217;d gotten sidetracked onto the <u>Mount Manuel</u> Trail, possibly allured by the flagging (which had not been on the Little Sur Trail).&nbsp;  What astounded me was the guy had a GPS! But apparently did not know how to use it. </p>
<p><a href="https://bigsurtrailmap.net/blog/wp-content/uploads/2025/01/map-tent2picoblancopubliccamp.png"><img loading="lazy" decoding="async" src="https://bigsurtrailmap.net/blog/wp-content/uploads/2025/01/map-tent2picoblancopubliccamp.png" alt="" width="245" height="525" class="aligncenter size-full wp-image-3383" srcset="https://bigsurtrailmap.net/blog/wp-content/uploads/2025/01/map-tent2picoblancopubliccamp.png 245w, https://bigsurtrailmap.net/blog/wp-content/uploads/2025/01/map-tent2picoblancopubliccamp-215x460.png 215w, https://bigsurtrailmap.net/blog/wp-content/uploads/2025/01/map-tent2picoblancopubliccamp-70x150.png 70w" sizes="auto, (max-width: 245px) 100vw, 245px" /></a></p>
<p>Nightfall found them up on the ridge, where they had to camp without water, having relied on finding water at the camp.&nbsp;  They&#8217;d planned a multi-day outing, so I tried to show the guy on his GPS how to get to Pico Blanco Public Camp.&nbsp;  We then left to continue our trek.</p>
<p>We continued a bit further, finding no more flagging beyond the tent site so that must have been the flagger&#8217;s destination &#8211; later made me wonder if the couple had been the flaggers, but then too late to ask.  Bushwhacking to cross over the ridge, we regained our previous hike&#8217;s route on its south side and the brush lessened </p>
<p><img class="block center portrait" src='https://bigsurtrailmap.net/blog/wp-content/uploads/2026/04/FindingMtManuelTrailHike2_6334.georef.jpg'></p>
<p>After passing a &#8220;Boundary Tree&#8221; sign, </p>
<p><img class="block center" src='https://bigsurtrailmap.net/blog/wp-content/uploads/2026/04/FindingMtManuelTrailHike2_6335.georef.jpg'></p>
<p>and rockwork, familiar from our last hike, the brushiness increased until finally we were stopped by the brush and downed branches wall at the &#8220;Apex of Brushiness&#8221;.  That had defeated us on our last hike, but we attacked with saws and loppers and cleared a passage to squeeze through.  After the &#8220;Apex&#8221; the route changed from southwest to southeast, so from a northerly to southerly exposure and the brushiness lessened &#8211; and tread became a bit more distinct </p>
<p><img class="block center portrait" src='https://bigsurtrailmap.net/blog/wp-content/uploads/2026/04/FindingMtManuelTrailHike2_6329.georef.jpg'></p>
<p><img class="block center" src='https://bigsurtrailmap.net/blog/wp-content/uploads/2026/04/FindingMtManuelTrailHike2_6323.georef.jpg'></p>
<p>Later some new rockwork indicated we were definitely on the trail.<br />
<a href="https://bigsurtrailmap.net/blog/wp-content/uploads/2025/01/IMG_6321rockwork.georef.jpg"><img loading="lazy" decoding="async" src="https://bigsurtrailmap.net/blog/wp-content/uploads/2025/01/IMG_6321rockwork.georef.jpg" alt="" width="800" height="600" class="aligncenter size-full wp-image-3375" srcset="https://bigsurtrailmap.net/blog/wp-content/uploads/2025/01/IMG_6321rockwork.georef.jpg 800w, https://bigsurtrailmap.net/blog/wp-content/uploads/2025/01/IMG_6321rockwork.georef-345x259.jpg 345w, https://bigsurtrailmap.net/blog/wp-content/uploads/2025/01/IMG_6321rockwork.georef-150x113.jpg 150w, https://bigsurtrailmap.net/blog/wp-content/uploads/2025/01/IMG_6321rockwork.georef-768x576.jpg 768w" sizes="auto, (max-width: 800px) 100vw, 800px" /></a></p>
<p>Reaching a point on the steep slope above the Launtz Creek Camp, according to Schaffer&#8217;s map, to save time we decided to simply bushwhack down the slope instead of trying to follow the trail&#8217;s long switchback, skipping its additional 0.4 miles of trail (a good decision, since later hikes found absolutely no tread or trail indicators over much of that section).&nbsp;  After hunting around a bit, at noon we arrived at restful Launtz Creek Camp set amidst the redwoods, with its USFS grate</p>
<p><img class="block center" src='https://bigsurtrailmap.net/blog/wp-content/uploads/2026/04/FindingMtManuelTrailHike2_6310.georef.jpg'></p>
<p>and sign on the ground,</p>
<p><a href="https://bigsurtrailmap.net/blog/wp-content/uploads/2024/10/Launtz_Creek_Camp_sign.jpg"><img loading="lazy" decoding="async" src="https://bigsurtrailmap.net/blog/wp-content/uploads/2024/10/Launtz_Creek_Camp_sign.jpg" alt="" width="800" height="600" class="aligncenter size-full wp-image-3015" srcset="https://bigsurtrailmap.net/blog/wp-content/uploads/2024/10/Launtz_Creek_Camp_sign.jpg 800w, https://bigsurtrailmap.net/blog/wp-content/uploads/2024/10/Launtz_Creek_Camp_sign-345x259.jpg 345w, https://bigsurtrailmap.net/blog/wp-content/uploads/2024/10/Launtz_Creek_Camp_sign-150x113.jpg 150w, https://bigsurtrailmap.net/blog/wp-content/uploads/2024/10/Launtz_Creek_Camp_sign-768x576.jpg 768w" sizes="auto, (max-width: 800px) 100vw, 800px" /></a></p>
<p>and water available from Launtz Creek.</p>
<p><img class="block center" src='https://bigsurtrailmap.net/blog/wp-content/uploads/2026/04/FindingMtManuelTrailHike2_6318.georef.jpg'></p>
<p>Launtz Camp had been &#8220;found&#8221;, 1/8 mile northeast of the USFS location.  And the USFS trail line differed considerably from the old tread we had followed (see map).</p>
<p>While eating lunch, we congratulated ourselves on this time being successful.&nbsp;  Paul decided to commemorate the event by taking a &#8220;Ventana Trails Forever&#8221; campaign card of his, adding the date and my name and placing it under the hinged plate atop the grate <a href="/paul_danielson.html#2016_poignant_find">(a later poignant find)</a>.</p>
<p>But Paul&#8217;s 73 years was telling on him, he felt too tired to go further.&nbsp;  Being a youngster of 66, I went on to investigate the old homestead site along the creek, then decided to see if I could follow the continuing trail.&nbsp;  A bit above the creek I found definite tread and followed it southwesterly.&nbsp;  But it became more brushy as it neared the apex where it would change direction &#8211; so being &#8220;a bit tired&#8221; myself went back to Paul at Launtz Creek Camp.</p>
<div class="center"><i>[Sorry no photo, Paul had the camera]</i></div>
<p></p>
<p>We returned the way we had come.&nbsp;  I wondered what happened to the couple, since the woman had made it clear she was <i>not</i> a happy camper &#8211; I suspected they might just decide to head back to civilization instead of trying for the Public Camp. </p>
<p>Arriving back at my Xterra just at sunset, we left with a feeling of accomplishment and satisfaction.</p>
<p>After the hike, I noted that beyond the &#8220;Apex of Brushiness&#8221; our track was off-set from Schaffer&#8217;s map route by 150-350 feet, indicating the topography of the map Jeff used differed significantly from the actual terrain.&nbsp;  So while his mapping was helpful, it could not be definitive.&nbsp;  The truer latitude/longitude route was stored within in my two GPSes &#8211; and quite different from the official USFS trail route.</p>
<p>Total hike time was 11.2&nbsp;hours.  Our hiking speeds give a sense for the trail roughness and hike difficulty: 1.4&nbsp;mph <small>(steep uphill)</small> and 1.9&nbsp;mph on our outbound and return legs along the Little Sur Trail but slowing to 0.36&nbsp;mph and 0.26&nbsp;mph respectively on the Mount Manuel Trail to the camp &#8211; the slowness of the last reflected our doing some sawing and lopping on the return trip.</p>
<p><SMALL><I>Photos by Paul Danielson</I></SMALL></p>
]]></content:encoded>
					
					<wfw:commentRss>https://bigsurtrailmap.net/blog/finding-the-mount-manuel-trail-hike-2/feed/</wfw:commentRss>
			<slash:comments>6</slash:comments>
		
		
			</item>
		<item>
		<title>Finding the Mount Manuel Trail &#8211; Hike 1</title>
		<link>https://bigsurtrailmap.net/blog/finding-the-mount-manuel-trail-hike-1/</link>
					<comments>https://bigsurtrailmap.net/blog/finding-the-mount-manuel-trail-hike-1/#respond</comments>
		
		<dc:creator><![CDATA[Jack Glendening]]></dc:creator>
		<pubDate>Thu, 24 Oct 2024 06:21:38 +0000</pubDate>
				<category><![CDATA[hike]]></category>
		<category><![CDATA[mapping]]></category>
		<guid isPermaLink="false">https://blog.bigsurtrailmap.net/?p=2554</guid>

					<description><![CDATA[Little tread, much brush, give up at &#8220;Apex of Brushiness&#8221; Find sign and rockwork, Paul follows deer track (with Paul Danielson) Hike 1 = Red February 2011 found myself and Paul Danielson, who had introduced me to the wonders of hiking old trails in the Ventana Wilderness, at Pico Blanco Boy Scout Camp.&#160; We&#8217;d obtained permission and gate access, but were warned the [&#8230;]]]></description>
										<content:encoded><![CDATA[<div class="center">
<div style="font-size: 20px"><b>Little tread, much brush, give up at &#8220;Apex of Brushiness&#8221;</b></div>
<div style="font-size: 16px"><b>Find sign and rockwork, Paul follows deer track</b><br />
<small>(with Paul Danielson)</small></div>
</div>
<div class="snippet-only" style="float: left;margin: 10px 20px 0 0">
<div style="width: 191px;line-height: 100%;border: 1px solid gray;text-align:center">
<figure>
<img decoding="async" style="width: 100%" src="https://bigsurtrailmap.net/blog/wp-content/uploads/2024/10/mtmanuel_flagging_history-hike1legend.574x733.png"><figcaption>Hike 1 = Red<figcaption></figure>
</div>
</div>
<div style="padding-top: 20px"><span class="emphasis">F</span>ebruary 2011 found myself and <a href="/paul_danielson.html">Paul Danielson</a>, who had introduced me to the wonders of hiking old trails in the Ventana Wilderness, at Pico Blanco Boy Scout Camp.&nbsp;  We&#8217;d obtained permission and gate access, but were warned the dirt road was very rough as not worked on since summer.&nbsp;  Indeed it was &#8211; I needed the 4WD of my Xterra, newly bought for just such places.&nbsp;  Being my first time there, the camp&#8217;s setting under tall stately redwood trees with nearby creek was very impressive and peaceful.</div>
<p>&nbsp;</p>
<hr />
<p><span id="more-2554"></span></p>
<div class="smallscreen-show smallscreen-notice">[Larger images shown on larger screens]</div>
<div class="center" style="max-width: 574px;line-height: 100%;border: 1px solid gray;text-align:center">
<figure>
<img decoding="async" style="width: 100%" src="https://bigsurtrailmap.net/blog/wp-content/uploads/2024/10/mtmanuel_flagging_history-hike1legend.574x733.png"><figcaption>
<b>Hike 1 = Red</b>  &nbsp;<small>[Outbound=thick Return=thin]</small><br />
<span style="line-height: 50%;font-size: smaller"><i><a href="https://bigsurtrailmap.net/ROUTES/MT_MANUEL/HISTORY/flagginghikehistory.googlemaps_display_overlay.html?i=2&amp;ll=36.3159,-121.7963&amp;z=16" target="_blank" rel="noopener">Above is screenshot &#8211; <b>Click for Interactive map</b></a></i></span><br />
</figcaption></figure>
</div>
</div>
<p></p>
<p>From the parking lot, the initial route went up a steep water tank access road (the scouts named it &#8220;Cardiac Hill&#8221;) before a sign led to the start of the trail proper.</p>
<p><img decoding="async" class="block center" src="https://bigsurtrailmap.net/blog/wp-content/uploads/2024/09/MtManuelHike1-LittleSurTH-sign.jpg" /></p>
<p>The Little Sur Trail led steadily upward with many switchbacks, under redwoods and oak trees.&nbsp;  It was in rough shape, requiring multiple deviations to avoid downed trees or brush in the trail, but with apparent tread.</p>
<p><img decoding="async" class="block center" src="https://bigsurtrailmap.net/blog/wp-content/uploads/2024/09/MtManuelHike1-LittleSurTrail.jpg" /></p>
<p>After 2 ¼ miles, gaining 1300 feet, the Mount Manuel trailhead sign appeared, on the ground.</p>
<p><img decoding="async" class="block center" src="https://bigsurtrailmap.net/blog/wp-content/uploads/2024/09/MtManuelHike1-MtManuelTH-sign.jpg" /></p>
<p>Heading out, initially some tread was apparent but that soon petered out.</p>
<p><img decoding="async" class="block center" src="https://bigsurtrailmap.net/blog/wp-content/uploads/2026/04/FindingMtManuelTrailHike1_6338.georef.jpg" /></p>
<p><img decoding="async" class="block center portrait" src="https://bigsurtrailmap.net/blog/wp-content/uploads/2026/04/FindingMtManuelTrailHike1_6295.georef.jpg" /></p>
<p>We continued on the same heading, on north side of the ridge, now trying to roughly follow <a href="https://blog.bigsurtrailmap.net/finding-the-mount-manuel-trail-mapping-technique/#jeffery_schaffer">Schaffer&#8217;s map route</a> on my GPS.&nbsp;  Crossing the ridge where Schaffer seemed to indicate, magnificent Pico Blanco came into view as we headed down the slope.</p>
<p><img decoding="async" class="block center" src="https://bigsurtrailmap.net/blog/wp-content/uploads/2024/09/MtManuelHike1-MtManuelTr-PicoBlancoView.jpg" /></p>
<p>This side of the ridge was thankfully less brushy but still without apparent tread or other clues such as cut branches, so we continued to roughly follow Schaffer&#8217;s route on the GPS.&nbsp;  Our &#8220;eureka moment&#8221; came 0.6 miles from the sign &#8211; we found a &#8216;Bearing Tree&#8217; sign posted on a tree! The only such a sign I&#8217;ve found in all my hiking! It was a badly needed confirmation that we were actually on the old trail route.</p>
<p><img decoding="async" class="block center portrait" src="https://bigsurtrailmap.net/blog/wp-content/uploads/2024/09/MtManuelHike1-MtManuelTr-sign1.jpg" /></p>
<p>Then 600 feet later we found some rockwork, more evidence of the old trail.</p>
<p><img decoding="async" class="block center portrait" src="https://bigsurtrailmap.net/blog/wp-content/uploads/2024/10/MtManuelHike1-MtManuelTr-rockwork.jpg" /></p>
<p>To this point the brushiness had been manageable but was worsening.&nbsp;  And ¼ mile later, at a corner where the trail changed its general direction, we hit a thick wall of head high branches and brush.&nbsp;  Not able to see to the other side, hunting for a way through or around on the steep hillside brought no joy &#8211; so we sat to eat a late lunch and talk.&nbsp;  Not being spring chickens, Paul 72 and I 65, we were tired.&nbsp;  We&#8217;d gotten a late start and it was now 2:30, so decided this was good point to stop, to get us back to the car around sunset.&nbsp;  We&#8217;d hoped to reach Launtz Creek Camp, but that clearly was not going to happen.&nbsp;  We started calling that wall the &#8220;Apex of Brushiness&#8221;.</p>
<div class="center"><i>(No photo of &#8220;Apex of Brushiness&#8221; &#8211; not very photogenic.)</i></div>
<p></p>
<p>The return trip took a detour when Paul thought he spied a track differing from where we&#8217;d come down, perhaps a more correct route, so followed it.&nbsp;  But it ended up leading down, just another game track of the many out there.&nbsp;  So we bushwhacked up the slope to get back on our outbound track.&nbsp;  Daylight was short, we had to race down the Little Sur Trail to get back to the parking lot before sunset &#8211; the light faded as we reached Bottchers Gap and drove home in the dark.</p>
<p>Total hike time was 6.0 hours.&nbsp;  Outbound distance along Mt.&nbsp;  Manuel Trail was 1.0 mile <small>(3.2m iles from parking)</small> &#8211; not very far, but a start.&nbsp;  And showing us what we were up against if we pursued this further.&nbsp;  A sense for the roughness of trail and hike difficulty can be seen in our hiking speeds: 1.6 mph <small>(steep uphill)</small> and 3.3 mph on our outbound and return legs along the Little Sur Trail but slowing to 0.62 mph and 0.53 mph respectively on the Mount Manuel Trail route.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://bigsurtrailmap.net/blog/finding-the-mount-manuel-trail-hike-1/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Finding the Mount Manuel Trail &#8211; Mapping technique</title>
		<link>https://bigsurtrailmap.net/blog/finding-the-mount-manuel-trail-mapping-technique/</link>
					<comments>https://bigsurtrailmap.net/blog/finding-the-mount-manuel-trail-mapping-technique/#comments</comments>
		
		<dc:creator><![CDATA[Jack Glendening]]></dc:creator>
		<pubDate>Thu, 01 Aug 2024 18:03:39 +0000</pubDate>
				<category><![CDATA[mapping]]></category>
		<guid isPermaLink="false">https://blog.bigsurtrailmap.net/?p=2529</guid>

					<description><![CDATA[Of the &#8220;lost&#8221; trails I GPS&#8217;d, the north end of the Mount Manuel Trail took more effort than any other.&#160; And in the end, was the one trail not completely mapped when foot problems prevented further work.&#160; In several sections the route went over steep slopes from which all tread had eroded and no trail [&#8230;]]]></description>
										<content:encoded><![CDATA[<p><img decoding="async" class="snippet-only" style="width:190px;;margin-top:20px;margin-right:20px;float:left;border: 1px solid gray" src="https://bigsurtrailmap.net/blog/wp-content/uploads/2024/10/finding_mtmanueltr-legend.webp" alt="All hikes"></p>
<p><span class="emphasis">O</span>f the &#8220;lost&#8221; trails I GPS&#8217;d, the north end of the Mount Manuel Trail took more effort than any other.&nbsp;  And in the end, was the one trail not completely mapped when foot problems prevented further work.&nbsp;  In several sections the route went over steep slopes from which all tread had eroded and no trail clues could be found.  In all, I made 11 hikes there between 2011 and 2016 looking for traces and clues (while aging from 65 to 70).</p>
<hr>
<p><span id="more-2529"></span></p>
<div class="smallscreen-show smallscreen-notice">[Larger images shown on larger screens]</div>
<p>In later posts I&#8217;ll describe those hikes as an example of how a &#8220;lost&#8221; trail becomes &#8220;found&#8221;, but in this post will describe my mapping technique.&nbsp;  FYI below is an animated interactive map of all 11 hikes, plus Schaffer and USFS trail routes.</p>
<div class="center" style="font-size:larger"><b>Map of all 11 hikes</b></div>
<p><a href="https://bigsurtrailmap.net/blog/wp-content/uploads/2024/08/mount-manuel-trail-mapping-technique.topbar.png"><img loading="lazy" decoding="async" src="https://bigsurtrailmap.net/blog/wp-content/uploads/2024/08/mount-manuel-trail-mapping-technique.topbar.png" alt="" width="376" height="168" class="aligncenter size-full wp-image-3477" srcset="https://bigsurtrailmap.net/blog/wp-content/uploads/2024/08/mount-manuel-trail-mapping-technique.topbar.png 376w, https://bigsurtrailmap.net/blog/wp-content/uploads/2024/08/mount-manuel-trail-mapping-technique.topbar-345x154.png 345w, https://bigsurtrailmap.net/blog/wp-content/uploads/2024/08/mount-manuel-trail-mapping-technique.topbar-150x67.png 150w" sizes="auto, (max-width: 376px) 100vw, 376px" /></a><a href="https://bigsurtrailmap.net/blog/wp-content/uploads/2024/08/mount-manuel-trail-mapping-technique.map_canvas.png"><img loading="lazy" decoding="async" src="https://bigsurtrailmap.net/blog/wp-content/uploads/2024/08/mount-manuel-trail-mapping-technique.map_canvas.png" alt="" width="378" height="692" class="aligncenter size-full wp-image-3478" srcset="https://bigsurtrailmap.net/blog/wp-content/uploads/2024/08/mount-manuel-trail-mapping-technique.map_canvas.png 378w, https://bigsurtrailmap.net/blog/wp-content/uploads/2024/08/mount-manuel-trail-mapping-technique.map_canvas-251x460.png 251w, https://bigsurtrailmap.net/blog/wp-content/uploads/2024/08/mount-manuel-trail-mapping-technique.map_canvas-82x150.png 82w" sizes="auto, (max-width: 378px) 100vw, 378px" /></a>
</div>
<div class="center" style="position:relative;top:-20px;"><a class="hoverzoom inlinetxtbutton atag-nofont-button" href="https://bigsurtrailmap.net/ROUTES/MT_MANUEL/HISTORY/flagginghikehistory.googlemaps_display_overlay.html">Animated Interactive Map</a></div>
</div>
<p></p>
<div id="mapping_technique" style='font-size:x-large'><b>Mapping technique</b></div>
<p>Ideally tread exists sufficient to follow and GPS a trail.  But when a trail is overgrown, having had no maintenance and little to no usage, tread disappears.  My trail mapping technique has been to </p>
<p></p>
<div id="gps_device"><span style='font-size:large'><u><b>Use dedicated GPS:</b></u>&nbsp;</span>  When I started, a handheld Garmin GPS <small>(GPSMAP 60)</small> had just come onto the market &#8211; without that availability I could not have attempted this mapping project.&nbsp;  Over the years, newer Garmin units were used, always models with the more capable &#8220;quad&#8221; antenna and with buttons for input with gloves on.&nbsp;  A phone with its questionable ruggedness, less capable antenna, and poor in-daylight-visibility touchscreen was not going to cut it!&nbsp;<br />
<small>[The need to mark frequent trail &#8220;clues&#8221; necessitated outside access to one GPS &#8211; due to the brush encountered, I had to buy a special clip to hold the GPS securely.  And had to eventually replace my first GPS due to brush trashing its buttons.]</small></div>
<p></p>
<div id="multiple_gps"><span style='font-size:large'><u><b>Use multiple GPSes:</b></u>&nbsp;</span> I carried two GPSes &#8211; the second as backup and also, since all individual tracks have error, to allow track averaging.  And if the two GPS tracks differed significantly &#8211; in poor reception conditions a track can suddenly shift, the unshifted one would indicate the &#8220;correct&#8221; track.  </div>
<p></p>
<div id="save_clues"><span style='font-size:large'><u><b>Save clues on GPS and recorder:</b></u>&nbsp;</span> in the absence of tread, one must look for other clues.  Examples of &#8220;definite&#8221; trail indicators are rockwork and sawed trunks.  Also useful are old flags and cut branches.&nbsp;  Sometime &#8220;tread&#8221; seems to be found but can be questionable &#8211; deer and other animal paths abound.  I carried an Olympus voice recorder and if not on obvious tread, upon finding a clue  would put a marker into my GPS and record the type and quality of that evidence &#8211; or if the apparent tread became questionable would mark+note that.  After the hike, I&#8217;d save the tracks and waypoints and transcribe recorder notes &#8211; when the route of the trail was questionable I could piece together the &#8220;good&#8221; points.&nbsp;  Most trails were traversed at least twice, often as in-and-out dayhikes.&nbsp; <small>[The use of separate gps and recorder &#8211; both with buttons &#8211; was important in allowing frequent marking without slowing me down, since button muscle-memory allowed me to mark+record without having to look or stop moving &#8211; two presses on a gps button (automatically increasing the waypoint number), then four on recorder buttons (on-record-stop-off).&nbsp;  I tried a touch-screen gps once but quickly abandoned that due to the time required,  besides its problem with brush touching/scratching the touch-screen.]</small></div>
<p></p>
<div id="preliminary_guess"><span style='font-size:large'><u><b>Have a preliminary guess:</b></u>&nbsp;</span> when available, I put a georeferenced trail route from a map in Jeffrey Schaffer&#8217;s &#8220;Hiking the Big Sur Country&#8221; (1988) into my GPSes.  While I also had track and camp info from the USFS that was often found to be misleading and unhelpful, as was true for the Mt.&nbsp;  Manuel Trail).  Unfortunately even Schaffer&#8217;s routes had enough error <small>(see box below)</small> that they were often not useful for re-finding a trail when tread was lost.&nbsp;  Another example &#8211; once when I could not follow the faint tread after it went into a large area covered with blowdown trees, I luckily found an old satellite image showing a switchback emerging from that area &#8211; so that point was put into the GPS as a &#8220;go-to&#8221; for my next attempt. </div>
<p></p>
<figure class='center'><figcaption class-'center'><i><b>Mapping tools</b> <br /><small>(original voice recorder and later GPS)</small></i></figcaption><img style='max-height:300px;' src='https://bigsurtrailmap.net/blog/wp-content/uploads/2024/10/trail_mapping_tools2.644x714.jpg'></figure>
<div id="jeffery_schaffer"></div>
<p></p>
<div class="center"><a class="hoverzoom inlinetxtbutton atag-nofont-button" href="/HIKES/2012-03-30=LauntzCreekCampHike/LauntzCreekCampHike-Track+Waypoints+Notes.html">Mapping&nbsp;Example:<br />GPX track+waypoints+notes</a></div>
<div style='width: 85%; padding: 20px ; margin-top:60px; border: 1px solid black; margin-left:auto; margin-right:auto; text-align:center;'></p>
<div style='font-size:large'><b>Jeffery Schaffer<br />and his mapping</b></div>
<p></p>
<div style="margin:left; text-align:left;">
Jeff &#8220;Mad Dog&#8221; Schaffer, whom I met twice in person so able to talk for several hours, worked before GPS was available, becoming familiar with mapping techniques during his geological training.  He used compass and step-counting together with topo maps to produce high-quality trail maps.&nbsp;  He emphasized to me that the accuracy of his trail mapping was limited by the accuracy of the topo maps he used &#8211; if actual terrain differs from that, a lat/lon obtained from a georeferenced map will not be accurate, and back then, terrain data was not of today&#8217;s accuracy.  So the changes of direction, twists and turns, of his lines were more significant than their exact location. <small>(BTW the same is true for my mapping, hence I make Big Sur Trailmap trails sequences of short straight lines rather than a smoothed line.)</small><br />
<br />
Jeff&#8217;s initial fame came from mapping the Pacific Coast Trail, authoring several trailblazing guidebooks published by Wilderness Press in the early 1970s.&nbsp;  In the late 1980&#8217;s he mapped the Ventana Wilderness <small>(and Big Sur State Parks, but not the Silver Peak Wilderness)</small> and published them in Wilderness Press&#8217;s <i>&#8220;Hiking the Big Sur County&#8221;</i> &#8211; the first reliable maps of the Ventana Wilderness trail system <small>(though with some omissions, the Black Cone Trail for example)</small>.&nbsp;  How this came about <small>(he did not initially want to do the mapping)</small> and his resulting mixed feelings <small>(for one, he disliked the photo used for the cover)</small> makes an interesting story &#8211; if we should meet, you can ask.
</div>
</div>
<p></p>
]]></content:encoded>
					
					<wfw:commentRss>https://bigsurtrailmap.net/blog/finding-the-mount-manuel-trail-mapping-technique/feed/</wfw:commentRss>
			<slash:comments>2</slash:comments>
		
		
			</item>
		<item>
		<title>Unquestioned ignorance spreads mis-information</title>
		<link>https://bigsurtrailmap.net/blog/unquestioned-ignorance-spreads-mis-information/</link>
					<comments>https://bigsurtrailmap.net/blog/unquestioned-ignorance-spreads-mis-information/#respond</comments>
		
		<dc:creator><![CDATA[Jack Glendening]]></dc:creator>
		<pubDate>Tue, 16 Jul 2024 22:58:25 +0000</pubDate>
				<category><![CDATA[mapping]]></category>
		<guid isPermaLink="false">https://blog.bigsurtrailmap.net/?p=2376</guid>

					<description><![CDATA[Wilderness boundary facts vs. un-facts(after being called &#8220;criminal&#8221;) Everyone knows the internet is full of mis-information.&#160; And that mis-information is often passed on via social media.&#160; Having a gap in one&#8217;s knowledge, &#8220;simple ignorance&#8221;, becomes &#8220;damn ignorance&#8221; when that gap is filled with incorrect assumptions, or even made-up &#8220;facts&#8221;, and posted to the web as [&#8230;]]]></description>
										<content:encoded><![CDATA[<p style="font-size:125%;font-weight:bold;font-style:italic; margin-left:auto; margin-right:auto; text-align:center;">Wilderness boundary facts vs. un-facts<br /><small>(after being called &#8220;criminal&#8221;)</small></p>
<p>Everyone knows the internet is full of mis-information.&nbsp; And that mis-information is often passed on via social media.&nbsp; Having a gap in one&#8217;s knowledge, &#8220;simple ignorance&#8221;, becomes &#8220;damn ignorance&#8221; when that gap is filled with incorrect assumptions, or even made-up &#8220;facts&#8221;, and posted to the web as factual without any attempt to question or verify, spreading still more mis-information.&nbsp;</p>
<hr>
<p><span id="more-2376"></span></p>
<p>A example was recently posted on Instagram, claiming Big Sur Trailmap (and so me) publishes incorrect wilderness boundary lines, calling this &#8220;criminal&#8221;.&nbsp; The &#8220;proof&#8221; was this map (fyi rotated with North on left, without any map attribution)</p>
<p><i>Instagram image 1</i><br />
<img decoding="async" src="https://bigsurtrailmap.net/blog/wp-content/uploads/2024/07/instagram-bigsurreccrew.9jul2024-1.png" /></p>
<p>showing a wilderness boundary along the west edge of Arroyo Seco river, whereas the edge of my &#8220;gold&#8221; (yellow) &#8220;wilderness&#8221; overlay instead follows a narrow wilderness corridor along ArroyoSeco-Indians Road &#8211; see below</p>
<p><i>Instagram image 2</i><br />
<img decoding="async" src="https://bigsurtrailmap.net/blog/wp-content/uploads/2024/07/instagram-bigsurreccrew.9jul2024-2.png" /></p>
<p>Definitely disappointed that no attempt was made to ask me about Big Sur Trailmap&#8217;s boundary lines, to get any clarifying info.&nbsp; Or look at reliable data elsewhere on the web, such such as CalTopo.&nbsp; Instead, without any fact checking, it&#8217;s assumed Big Sur Trailmap is purposely deceiving &#8211; so a post and rant is made about how I am &#8220;criminal&#8221;, with bile, etc.&nbsp; (And these are &#8216;boundaries set by VWA&#8217; <img style='vertical-align:sub' src='https://bigsurtrailmap.net/lib/icons/eyeroll1.16x16.gif'/> &#8211; it&#8217;s a conspiracy!)&nbsp; Bizarre to read that my promulgation of official US wilderness data is &#8220;criminal&#8221; &#8211; when the real problem is the poster&#8217;s own lack of knowledge and and map interpretation failures, not any error on my map.</p>
<p><b><u>THE FACTS</u></b></p>
<p>The Big Sur Trailmap gold (yellow) &#8220;wilderness&#8221; overlay is based on wilderness boundary points taken from current government databases.&nbsp; (See &#8220;DETAILS&#8221; below for details.)</p>
<p><b>FACT #1:  out-of-date map</b><br />
The map used in the post is out-of-date.&nbsp; In the original &#8216;Endangered American Wilderness Act&#8217; of 1978 the boundary did follow Arroyo Seco for awhile, but the &#8216;Big Sur Wilderness and Conservation Act&#8217; of 2002 changed that into a narrow corridor on each side of ArroyoSeco-Indians Road.&nbsp; (Giving wilderness protection to Arroyo Seco, a good thing IMHO.)</p>
<p><b>FACT #2:  believing an &#8220;INDEFINITE&#8221; line</b><br />
The &#8220;wilderness boundary&#8221; on that old map was not even an official line back when the map was made.&nbsp; If you follow it around, you find &#8220;INDEFINITE&#8221; in many places.&nbsp; Two are shown below, with the same region as used in the post:</p>
<p><img decoding="async" src="https://bigsurtrailmap.net/blog/wp-content/uploads/2024/07/usgsquad_arroyoseco_wildernessline4-annotated.490kpx.png" /></p>
<div style='margin-left:auto; margin-right:auto; text-align:center;'>
<figure style='display:inline-block; margin-right:20px'><figcaption><i>Blowup</i></figcaption><img src='https://bigsurtrailmap.net/blog/wp-content/uploads/2024/07/indefinite_north.rotated.png'/><br />
   </figure>
</div>
<p>The &#8220;INDEFINITE&#8221; marking was put there for a reason !</p>
<p><b>FACT #3:  USGS map validates Big Sur Trailmap</b><br />
<em>Instagram image 2</em> above, showing a Big Sur Trailmap with &#8216;USGS Topo + Wilderness&#8217; background, has its own intrinsic validation if you read the map correctly.&nbsp; Note how the edge of my gold overlay matches the green line.&nbsp; That green line does not come from me, it comes from the underlying USGS topo map, marking the wilderness boundary as set by the USGS.&nbsp; (If you use the &#8216;USGS Topo&#8217; background, the gold overlay disappears but the green line remains.)&nbsp; So the USGS wilderness boundary data validates my overlay edge.&nbsp; </p>
<div style='margin-left:auto; margin-right:auto; text-align:center;'>
<figure style='display:inline-block; margin-right:20px;'><figcaption><i><u>Background:</u><br />&nbsp;USGS Topo&nbsp;&plus;&nbsp;wilderness</i></figcaption><img src='https://bigsurtrailmap.net/blog/wp-content/uploads/2024/07/bstm-arroyoseco-usgswilderness.90x169.png'/><br />
  </figure>
<figure style='display:inline-block; margin-left:20px;'><figcaption><i><u>Background:</u><br />USGS Topo</i></figcaption><img src='https://bigsurtrailmap.net/blog/wp-content/uploads/2024/07/bstm-arroyoseco-usgs.90x169.png'/><br />
  </figure>
</div>
<p>(FYI that USGS background map is the current &#8220;National Map&#8221;, not the now out-of-date USGS quadrangle maps.&nbsp; Also, USGS green lines are <i>generic</i> boundary lines, so elsewhere on map can indicate property lines, national forest boundaries, etc.)</p>
<p><b>FACT #4:  other Internet data</b><br />
Other websites also provide wilderness boundary data.&nbsp; You can check out CalTopo&#8217;s default &#8216;Map Builder&#8217; background which uses green wilderness boundaries.&nbsp; You&#8217;ll find agreement with my wilderness lines as a narrow non-wilderness corridor.</p>
<p><img decoding="async" src="https://bigsurtrailmap.net/blog/wp-content/uploads/2024/07/caltopo_arroyoseco_wildernessline-3.png" /></p>
<p>Of course incorrect wilderness maps can also be found on the internet.&nbsp; For example, CalTopo has a &#8220;Forest Service &#8211; 2013&#8221; map which does <i>not</i> have a narrow ArroyoSeco-Indians Road corridor (also with &#8220;INDEFINITE&#8221; along its wilderness boundary lines).&nbsp; A good example of incorrect info appearing on the web, since supposedly dated &#8216;2013&#8217; but with a line invalidated by the 2002 Act.</p>
<p><img decoding="async" src="https://bigsurtrailmap.net/blog/wp-content/uploads/2024/07/usfstopomap_arroyoseco_wildernessline-3-annotated.png" /></p>
<p><b><u>SUMMING UP</u></b></p>
<p>Wilderness boundary lines are certainly incorrect on some maps.&nbsp; But the poster himself was the one using an out-of-date map.&nbsp; And using lines marked on the map as being unofficial (and ultimately incorrect).&nbsp; And not bothering to do any further investigation before spreading mis-information on the web.</p>
<p>Big Sur Trailmap focuses on current info about trails.&nbsp; Inserting new boundary line data is time-consuming and a PITA, with lots of pieces to keep track of &#8211; so done only if I know of a change or error.&nbsp; As of this post, I know of no errors.</p>
<p>If I do learn of a change or error, I will make corrections.&nbsp; But just hearing about a supposed change is not enough &#8211; the trustworthiness of the source and other available info must be considered.&nbsp; Lots of snap judgements and mis-information flying around out there !</p>
<hr style="height: 3px; width: 100%;" />
<p><b>DETAILS &#8211; Big Sur Trailmap wilderness boundaries</b></p>
<p>Wilderness boundaries are set by acts of Congress, which publish the lawful boundaries.&nbsp; The first wilderness boundaries were created by the Endangered American Wilderness Act of 1978.</p>
<p>They are amended from time to time &#8211; for example, the Big Sur Wilderness and Conservation Act of 2002 made several additions to the original Ventana wilderness.&nbsp; (The VWA was instrumental in this process.)</p>
<p>Also, wilderness boundaries can change without a formal act of congress.&nbsp; Notably, inholdings <small>(private ownership inside National Forest)</small> are excluded from wilderness areas &#8211; so if an inholding&#8217;s legal boundary changes, or is transferred to the government, that automatically changes the wilderness boundary.</p>
<p>The congressional bills contain legal descriptions.&nbsp; Turning those into lat/lon points to be used on maps, etc. depends upon government agencies.&nbsp; Wilderness boundaries can be found in both US<b>G</b>S (U.S.&nbsp;  Geological Survey) and US<b>F</b>S (U.S.&nbsp;  Forest Service) databases &#8211; but translating legal descriptions is tricky and the the lines from the different agencies do have some differences, mostly minor.&nbsp;</p>
<p>Big Sur Trailmap uses digital lat/lon boundary data obtained from USGS/USFS servers, which are then converted to lines or shapes displayed on a background map.&nbsp;  I know of two minor errors in the US<b>F</b>S wilderness boundary data, both of which are correct in the US<b>G</b>S data &#8211; so in the main my wilderness boundary lines use the US<b>G</b>S data.&nbsp; However, I also know of one error in the US<b>G</b>S data (an inholding boundary has been formally changed by the US<b>F</b>S and not yet known to US<b>G</b>S), so my wilderness overlay follows the US<b>F</b>S data there.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://bigsurtrailmap.net/blog/unquestioned-ignorance-spreads-mis-information/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Albino redwood dies in fire</title>
		<link>https://bigsurtrailmap.net/blog/albino-redwood-dies-in-fire/</link>
					<comments>https://bigsurtrailmap.net/blog/albino-redwood-dies-in-fire/#comments</comments>
		
		<dc:creator><![CDATA[Jack Glendening]]></dc:creator>
		<pubDate>Sun, 10 Nov 2019 04:48:34 +0000</pubDate>
				<category><![CDATA[report]]></category>
		<guid isPermaLink="false">https://blog.bigsurtrailmap.net/?p=1913</guid>

					<description><![CDATA[I doubt you&#8217;ve seen a white plant. &#8220;Plants&#8221; (here used in the &#8220;strict sense&#8221;, aka Viridiplantae, which excludes fungii among others) use green chlorophyll to produce the energy they need to grow and thrive. Unless they can get their nutrition elsewhere &#8230;   While coast redwoods produce cones and seed, their germination rate is very [&#8230;]]]></description>
										<content:encoded><![CDATA[<p><!-- note image size halved using width+height params --><br />
<a href="https://bigsurtrailmap.net/blog/wp-content/uploads/2019/10/AlbinoRedwood_closeup-NewTimesSanLuisObispo-s.miller.crop_.jpg"><img loading="lazy" decoding="async" class="alignleft size-medium wp-image-2012" src="https://bigsurtrailmap.net/blog/wp-content/uploads/2019/10/AlbinoRedwood_closeup-NewTimesSanLuisObispo-s.miller.crop_-345x424.jpg" alt="" width="172" height="212" srcset="https://bigsurtrailmap.net/blog/wp-content/uploads/2019/10/AlbinoRedwood_closeup-NewTimesSanLuisObispo-s.miller.crop_-345x424.jpg 345w, https://bigsurtrailmap.net/blog/wp-content/uploads/2019/10/AlbinoRedwood_closeup-NewTimesSanLuisObispo-s.miller.crop_-122x150.jpg 122w, https://bigsurtrailmap.net/blog/wp-content/uploads/2019/10/AlbinoRedwood_closeup-NewTimesSanLuisObispo-s.miller.crop_-768x944.jpg 768w, https://bigsurtrailmap.net/blog/wp-content/uploads/2019/10/AlbinoRedwood_closeup-NewTimesSanLuisObispo-s.miller.crop_-833x1024.jpg 833w, https://bigsurtrailmap.net/blog/wp-content/uploads/2019/10/AlbinoRedwood_closeup-NewTimesSanLuisObispo-s.miller.crop_-1200x1476.jpg 1200w, https://bigsurtrailmap.net/blog/wp-content/uploads/2019/10/AlbinoRedwood_closeup-NewTimesSanLuisObispo-s.miller.crop_.jpg 1471w" sizes="auto, (max-width: 172px) 100vw, 172px" /></a></p>
<p><span class="emphasis">I</span> doubt you&#8217;ve seen a white plant. &#8220;Plants&#8221; <small>(here used in the &#8220;strict sense&#8221;, aka Viridiplantae, which excludes fungii among others)</small> use green chlorophyll to produce the energy they need to grow and thrive.</p>
<p>Unless they can get their nutrition elsewhere &#8230;</p>
<hr>
<p><span id="more-1913"></span></p>
<div style="clear: both;"> </div>
<figure id="attachment_1888" aria-describedby="caption-attachment-1888" style="width: 345px" class="wp-caption alignright"><a href="https://bigsurtrailmap.net/blog/wp-content/uploads/2019/10/AlbinoRedwoodsign.490kpx.jpg"><img loading="lazy" decoding="async" class="size-medium wp-image-1888" src="https://bigsurtrailmap.net/blog/wp-content/uploads/2019/10/AlbinoRedwoodsign.490kpx-345x193.jpg" alt="" width="345" height="193" srcset="https://bigsurtrailmap.net/blog/wp-content/uploads/2019/10/AlbinoRedwoodsign.490kpx-345x193.jpg 345w, https://bigsurtrailmap.net/blog/wp-content/uploads/2019/10/AlbinoRedwoodsign.490kpx-150x84.jpg 150w, https://bigsurtrailmap.net/blog/wp-content/uploads/2019/10/AlbinoRedwoodsign.490kpx-768x430.jpg 768w, https://bigsurtrailmap.net/blog/wp-content/uploads/2019/10/AlbinoRedwoodsign.490kpx.jpg 935w" sizes="auto, (max-width: 345px) 100vw, 345px" /></a><figcaption id="caption-attachment-1888" class="wp-caption-text"><i>A &#8220;bushy&#8221; albino redwood <br />
<small>(click for larger image)</small></i></figcaption></figure>
<p>While coast redwoods produce cones and seed, their germination rate is very low.&nbsp;  So most redwood trees have grown from sprouts formed around the base of a parent tree, initially dependent on nutrients from the root of the mature tree.&nbsp;  Although shallow, redwood roots can spread to 100 ft.&nbsp;  Those further from the parent get more sunlight to aid growth, so adult redwoods often form circular &#8220;fairy rings&#8221; created by clonal sprouts from an original parent.</p>
<p>But clones can have still have genetic mutations.&nbsp;  Coast redwoods have six sets of chromosomes, unusual for a tree &#8211; in fact, the only such conifer.&nbsp;  That makes for a wide genetic diversity and higher chance of mutation.&nbsp;  And recent studies have indeed found genetic variations in fairy ring clones.<sup>*</sup></p>
<figure id="attachment_1921" aria-describedby="caption-attachment-1921" style="width: 293px" class="wp-caption alignleft"><a href="https://bigsurtrailmap.net/blog/wp-content/uploads/2019/10/GhostlyAlbinoRedwood-m.ferdin.crop_.lighten.withcredit90.490kpx.jpg"><img loading="lazy" decoding="async" class="size-medium wp-image-1921" src="https://bigsurtrailmap.net/blog/wp-content/uploads/2019/10/GhostlyAlbinoRedwood-m.ferdin.crop_.lighten.withcredit90.490kpx-293x460.jpg" alt="" width="293" height="460" srcset="https://bigsurtrailmap.net/blog/wp-content/uploads/2019/10/GhostlyAlbinoRedwood-m.ferdin.crop_.lighten.withcredit90.490kpx-293x460.jpg 293w, https://bigsurtrailmap.net/blog/wp-content/uploads/2019/10/GhostlyAlbinoRedwood-m.ferdin.crop_.lighten.withcredit90.490kpx-96x150.jpg 96w, https://bigsurtrailmap.net/blog/wp-content/uploads/2019/10/GhostlyAlbinoRedwood-m.ferdin.crop_.lighten.withcredit90.490kpx.jpg 558w" sizes="auto, (max-width: 293px) 100vw, 293px" /></a><figcaption id="caption-attachment-1921" class="wp-caption-text"><i>A unique albino redwood <br />
<small>FYI my feet are 3 ft above base of tree<br />
(click for larger image)</small><br />
</i></figcaption></figure>
<p>And sometimes those mutations produce something unique &#8211; an &#8220;albino redwood&#8221;.&nbsp;  Lacking green chlorophyll, their needles are white.&nbsp;  Since they cannot produce their own nutrition, unlike ordinary &#8220;green&#8221; clones they remain dependent on their root connection with the parent tree.&nbsp;  So their growth is marginal and most albino redwoods remain more bush-like than tree-like.</p>
<p>But there are exceptions &#8211; albino redwoods which <em>are</em> &#8220;tree-like&#8221;.</p>
<hr />
<p>Once while passing a Ventana Wilderness gully, Paul Danielson mentioned an albino redwood grew upstream.&nbsp;  He didn&#8217;t say more, so one day I went out to see what was there.</p>
<p>Was I surprised! I&#8217;d seen a few albino redwoods before &#8211; but all were &#8220;bushes&#8221;, though sometimes large.&nbsp;  This was a truly white &#8220;tree&#8221;, over 20 feet tall.&nbsp;  Reminded me of a flocked Christmas tree.&nbsp;  A wonder of nature.</p>
<p>Afterward, I remained amazed that something so unique existed &#8211; even used its photo on Christmas cards one year.&nbsp;  A fond memory.</p>
<figure id="attachment_1920" aria-describedby="caption-attachment-1920" style="width: 220px" class="wp-caption alignright"><a href="https://bigsurtrailmap.net/blog/wp-content/uploads/2019/10/DeadAlbinoRedwood2-j.glendening.crop_.darken.1561x3264.withcredit90.490kpx.jpg"><img loading="lazy" decoding="async" class="size-medium wp-image-1920" src="https://bigsurtrailmap.net/blog/wp-content/uploads/2019/10/DeadAlbinoRedwood2-j.glendening.crop_.darken.1561x3264.withcredit90.490kpx-220x460.jpg" alt="" width="220" height="460" srcset="https://bigsurtrailmap.net/blog/wp-content/uploads/2019/10/DeadAlbinoRedwood2-j.glendening.crop_.darken.1561x3264.withcredit90.490kpx-220x460.jpg 220w, https://bigsurtrailmap.net/blog/wp-content/uploads/2019/10/DeadAlbinoRedwood2-j.glendening.crop_.darken.1561x3264.withcredit90.490kpx-72x150.jpg 72w, https://bigsurtrailmap.net/blog/wp-content/uploads/2019/10/DeadAlbinoRedwood2-j.glendening.crop_.darken.1561x3264.withcredit90.490kpx.jpg 484w" sizes="auto, (max-width: 220px) 100vw, 220px" /></a><figcaption id="caption-attachment-1920" class="wp-caption-text"><i>Post-fire<br />
<small>(click for larger image)</small></i></figcaption></figure>
<p>So this year I read with alarm reports of a fire in that gully.&nbsp;  Not hearing the extent of the fire or how hot it burned, I held out hope the albino might have survived.&nbsp;  A few weeks after the fire, I went to see for myself with hope and trepidation.</p>
<p>Given the title, you will anticipate what I found.&nbsp;  The albino had been seared rather than burnt &#8211; the heat killed its branches and all were brown.&nbsp;  I remembered reading a plea to not to cut branches for souvenirs since, like a green redwood, they would just turn brown when dead.</p>
<p>Sad, very sad that something so unique was now gone. <img src="https://s.w.org/images/core/emoji/17.0.2/72x72/1f641.png" alt="🙁" class="wp-smiley" style="height: 1em; max-height: 1em;" /> Especially since it resulted from a careless someone&#8217;s campfire.&nbsp;  Others, including college botany classes, have been viewing that albino for decades &#8211; but those opportunities are now lost.</p>
<p><!-- note image size halved using width+height params --></p>
<figure id="attachment_1922" aria-describedby="caption-attachment-1922" style="width: 173px" class="wp-caption alignleft"><a href="https://bigsurtrailmap.net/blog/wp-content/uploads/2019/10/SproutingAlbinoRedwood-j.glendening.490kpx.jpg"><img loading="lazy" decoding="async" class="size-medium wp-image-1922" src="https://bigsurtrailmap.net/blog/wp-content/uploads/2019/10/SproutingAlbinoRedwood-j.glendening.490kpx-345x259.jpg" alt="" width="173" height="130" srcset="https://bigsurtrailmap.net/blog/wp-content/uploads/2019/10/SproutingAlbinoRedwood-j.glendening.490kpx-345x259.jpg 345w, https://bigsurtrailmap.net/blog/wp-content/uploads/2019/10/SproutingAlbinoRedwood-j.glendening.490kpx-150x113.jpg 150w, https://bigsurtrailmap.net/blog/wp-content/uploads/2019/10/SproutingAlbinoRedwood-j.glendening.490kpx-768x576.jpg 768w, https://bigsurtrailmap.net/blog/wp-content/uploads/2019/10/SproutingAlbinoRedwood-j.glendening.490kpx.jpg 808w" sizes="auto, (max-width: 173px) 100vw, 173px" /></a><figcaption id="caption-attachment-1922" class="wp-caption-text"><i>Post-fire albino sprouts <br />
<small>(click for larger image)</small></i></figcaption></figure>
<p>Severely burnt redwoods respond by upping their growth hormones, sprouting green everywhere including their trunks.&nbsp;  At the base of the dead tree I found numerous albino shoots had developed post-fire.&nbsp;  Perhaps another large redwood tree will grow there someday.&nbsp;  Not in my lifetime, but hopefully for future generations.<br />
<br class="clear" />
</p>
<hr style="width: 80%;" />
<p>Below photo of same tree taken by professional from <i>New Times <small>(San Luis Obispo)</small></i></p>
<p><a href="https://bigsurtrailmap.net/blog/wp-content/uploads/2019/10/AlbinoRedwood-NewTimesSanLuisObispo-s.miller.quartersize.jpg"><img loading="lazy" decoding="async" class="size-full wp-image-1999" src="https://bigsurtrailmap.net/blog/wp-content/uploads/2019/10/AlbinoRedwood-NewTimesSanLuisObispo-s.miller.quartersize.jpg" alt="" width="832" height="1248" srcset="https://bigsurtrailmap.net/blog/wp-content/uploads/2019/10/AlbinoRedwood-NewTimesSanLuisObispo-s.miller.quartersize.jpg 832w, https://bigsurtrailmap.net/blog/wp-content/uploads/2019/10/AlbinoRedwood-NewTimesSanLuisObispo-s.miller.quartersize-100x150.jpg 100w, https://bigsurtrailmap.net/blog/wp-content/uploads/2019/10/AlbinoRedwood-NewTimesSanLuisObispo-s.miller.quartersize-307x460.jpg 307w, https://bigsurtrailmap.net/blog/wp-content/uploads/2019/10/AlbinoRedwood-NewTimesSanLuisObispo-s.miller.quartersize-768x1152.jpg 768w, https://bigsurtrailmap.net/blog/wp-content/uploads/2019/10/AlbinoRedwood-NewTimesSanLuisObispo-s.miller.quartersize-683x1024.jpg 683w" sizes="auto, (max-width: 832px) 100vw, 832px" /></a></p>
<div style="float: right; position: relative; bottom: 25px;"><i><small>steve e. miller &#8211; new times, san luis obispo, ca</small></i></div>
<p>&nbsp;</p>
<div style="padding: 8px; border: 2px solid gray; width: 75%; margin: 0 auto; text-align: center; font-style: italic;">For a 2021 article on albino redwood research, including white &amp; green &#8220;chimera&#8221; redwoods:   <a href="https://www.atlasobscura.com/articles/albino-redwoods-chimera">Rare Albino Redwoods &#8230;</a></div>
<p>&nbsp;</p>
<div style="padding: 8px; border: 2px solid gray; width: 75%; margin: 0 auto; text-align: center; font-style: italic;">Some do not consider albino redwoods as parasitic, just exceptional branches of the parent tree.&nbsp;  I can understand this viewpoint for &#8220;bushy&#8221; albinos growing beside the parent trunk, as many are &#8211; but when I see a tall vertical trunk radiating numerous side branches, I call that a tree.&nbsp;  If green, I suspect it would survive without the parent tree &#8211; but the key factor would be whether it had developed its own roots in addition to the parental one.</div>
<p>&nbsp;</p>
<div>
<div style="padding: 8px; border: 2px solid gray; width: 75%; margin: 0 auto; text-align: center; font-style: italic;">in this day of social media, albino redwood tree locations are guarded, to keep them from being inundated by the curious.&nbsp;  So I will not be giving a location.</div>
</div>
<p>&nbsp;</p>
<div>
<div style="float: right;">* <small><i>http://www.genomenewsnetwork.org/articles/08_00/redwood_genome.shtml</i></small></div>
</div>
]]></content:encoded>
					
					<wfw:commentRss>https://bigsurtrailmap.net/blog/albino-redwood-dies-in-fire/feed/</wfw:commentRss>
			<slash:comments>2</slash:comments>
		
		
			</item>
		<item>
		<title>NatGeo creates a Big Sur map(but gets it wrong)</title>
		<link>https://bigsurtrailmap.net/blog/natgeo-creates-a-big-sur-mapbut-gets-it-wrong/</link>
					<comments>https://bigsurtrailmap.net/blog/natgeo-creates-a-big-sur-mapbut-gets-it-wrong/#respond</comments>
		
		<dc:creator><![CDATA[Jack Glendening]]></dc:creator>
		<pubDate>Sat, 12 Oct 2019 03:20:47 +0000</pubDate>
				<category><![CDATA[mapping]]></category>
		<guid isPermaLink="false">https://blog.bigsurtrailmap.net/?p=1843</guid>

					<description><![CDATA[&#160; In 2005 Wilderness Press (&#8220;WP&#8221;) produced the first sheet map available for the backcountry Big Sur trails &#8211; before that, hikers had to depend upon upon quadrangle maps with their many drawbacks.&#160; I first used that WP map when exploring the Ventana Wilderness and always liked its very clean and readable format, with trail [&#8230;]]]></description>
										<content:encoded><![CDATA[<div align="center"><img decoding="async" style="width:650px" src="https://bigsurtrailmap.net/MAPS/BIGSUR/NATGEO/NatGeoBigSurMap-PineRidgeTrail-camps-animate-2.0.gif" width="100%" height="408" /></div>
<p>&nbsp;</p>
<p><span class="emphasis">I</span>n 2005 Wilderness Press <small><i>(&#8220;WP&#8221;)</i></small> produced the first sheet map available for the backcountry Big Sur trails &#8211; before that, hikers had to depend upon upon quadrangle maps with their many drawbacks.&nbsp;  I first used that WP map when exploring the Ventana Wilderness and always liked its very clean and readable format, with trail lines clearly displayed atop contour lines.</p>
<hr>
<p><span id="more-1843"></span></p>
<p>But the WP map did have errors, some egregious.&nbsp;  Notable was a trail line heading west from the Ventana Double Cone.&nbsp;  Such has never existed <small>(though some have bushwhacked that route)</small> &#8211; instead, it is mostly heavy brush.&nbsp;  The WP map also displayed a long overgrown &#8220;lost&#8221; trail west of that &#8211; which almost connected to the false trail, unfortunately leading some to think that with a short bushwhack between then a nice loop hike could be made.&nbsp;  Paul Danielson and I ran into one such backpacker when camped at Hiding Canyon Camp &#8211; he had come in along the Pine Ridge Trail and planned to complete a loop over the false and &#8220;lost&#8221; trail route.&nbsp;  We advised that would be through heavy brush in steep terrain with no followable path &#8211; and suggested he return the way he came.&nbsp;  He was reluctant to accept that, since he&#8217;d already come 2/3 of the way around his loop and had a plane to catch so under time pressure.&nbsp;  We never saw him again and I&#8217;ve wondered what happened, which route he opted to take and the result.</p>
<p>Despite its deficiencies, the WP map was &#8220;better than nothing&#8221; &#8211; since the only alternative was bulky and hard to use USGS quadrangle maps.&nbsp;  And many of the WP map errors became common knowledge, so experienced Big Sur hikers were not misled by them.</p>
<p>Then in 2012, while shopping at REI Marina I spied a new Big Sur map! Created by National Geographic<small><i>(&#8220;NatGeo&#8221;)</i></small> !!  Quite a surprise since there&#8217;d not been any promotion.&nbsp;  Of course I immediately bought one to examine.&nbsp;  You are likely familiar with the NatGeo map format, very colorful with high-quality printing.&nbsp;  That&#8217;s nice, but I wanted to know how it compared to the WP map in coverage and accuracy.&nbsp;  And a first glance quickly found big problems.</p>
<p>In the Ventana Wilderness the most heavily used trail has been the Pine Ridge Trail &#8211; and the most used camp along it, by far because of its hot spring, is Sykes Camp <small>(it&#8217;s hard to explain the extent of Sykes&#8217; legendary/infamous reputation in central California &#8211; but for example, it has a Yelp page!)</small>.&nbsp;  Egregiously, NatGeo&#8217;s map had <u>three</u> camps along the Pine Ridge Trail all mis-located &#8211; including Sykes Camp itself.</p>
<p>And I immediately realized what had happened.&nbsp;  When beginning my own trail mapping in 2009 I first got the latest USFS data from their GIS person in Goleta, the National Forest headquarters, as a basis to start from.&nbsp;  I knew it would have errors, but not the extent nor which trails or camps were problematic.&nbsp;  I quickly found some obvious errors without needing any field checking.&nbsp;  The worst of those were three camps along Pine Ridge Trail incorrectly placed/labeled.&nbsp;  The Sykes Camp misplacement in particular was important, so I sent an email back to Goleta to report those errors.&nbsp;  I never got a response.</p>
<p>So now, in 2012, I realized NatGeo must have gotten that bad camp data from the USFS and used it for their map.&nbsp;  And of course the map also included all the other errors of the USFS data.</p>
<p>I sent an email to National Geographic, to inform them of major errors in their map.&nbsp;  I also suggested they talk to people with local knowledge if they wanted to know where the trails and camps really were.&nbsp;  NatGeo contacted the Ventana Wilderness Alliance <small><i>(&#8220;VWA&#8221;)</i></small>.&nbsp;  They told me that NatGeo wanted to know if I knew what I was talking about! That contact connected two acquaintances who facilitated cooperation and eventually the VWA brought some locals together to examine the NatGeo map and provide corrections.</p>
<div>
<div style="font-style: italic; padding: 8px; border: 2px solid gray; width: 75%; margin: 0 auto; text-align: center;"><b>Aside:</b>  the WP map <i>did</i> have Sykes and the other camps correctly located and I know WP did use USFS data &#8211; and also input from non-USFS sources.&nbsp;  One wonders if someone before me might also have noted and informed the USFS about the Sykes Camp location error &#8211; or whether the errors somehow cropped up after that time.</div>
</div>
<p>&nbsp;</p>
<figure id="attachment_1971" aria-describedby="caption-attachment-1971" style="width: 345px" class="wp-caption alignleft"><a href="https://bigsurtrailmap.net/blog/wp-content/uploads/2019/10/VWA-NatGeo_Exhibit-MarinaREI.490kpx-1.jpg"><img loading="lazy" decoding="async" class="size-medium wp-image-1971" src="https://bigsurtrailmap.net/blog/wp-content/uploads/2019/10/VWA-NatGeo_Exhibit-MarinaREI.490kpx-1-345x454.jpg" alt="" width="345" height="454" srcset="https://bigsurtrailmap.net/blog/wp-content/uploads/2019/10/VWA-NatGeo_Exhibit-MarinaREI.490kpx-1-345x454.jpg 345w, https://bigsurtrailmap.net/blog/wp-content/uploads/2019/10/VWA-NatGeo_Exhibit-MarinaREI.490kpx-1-114x150.jpg 114w, https://bigsurtrailmap.net/blog/wp-content/uploads/2019/10/VWA-NatGeo_Exhibit-MarinaREI.490kpx-1.jpg 610w" sizes="auto, (max-width: 345px) 100vw, 345px" /></a><figcaption id="caption-attachment-1971" class="wp-caption-text"><i>VWA exhibit at Marina REI<br />
<small>(click for larger image)</small></i></figcaption></figure>
<p>To their great credit, NatGeo recalled all their original maps from stores.&nbsp;  Later they send out a revised version, based on the VWA input.&nbsp;  That map <i>is</i> largely accurate in what it presents <small>(a few trails are mislocated, but not too badly &#8211; and &#8220;use&#8221; trails are generally excluded.)</small>.</p>
<p>In return for the help provided, NatGeo produced a nice display promoting the VWA <small>(and their map, of course)</small> which is now on display in the Marina REI store.&nbsp;  Whenever I look at it I am reminded of the shock I felt when seeing the misplaced camps on the original version.</p>
<p>I still have the original map I bought in 2012, as an example of how maps can sometimes be badly inaccurate.&nbsp;  And, in this day of multiple map apps, as a reminder that accuracy of the underlying data is more important than a &#8220;cool&#8221; presentation.</p>
<p><i>[For my review of the four currently available Big Sur sheet hiking maps, see <a href="https://bigsurtrailmap.net/large-printed-maps.html">Printed Maps for Big Sur Hikers</a>]</i></p>
]]></content:encoded>
					
					<wfw:commentRss>https://bigsurtrailmap.net/blog/natgeo-creates-a-big-sur-mapbut-gets-it-wrong/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>State of the trails &#8211; trailcrew vs nature</title>
		<link>https://bigsurtrailmap.net/blog/state-of-the-trails-trailcrews-vs-nature/</link>
					<comments>https://bigsurtrailmap.net/blog/state-of-the-trails-trailcrews-vs-nature/#respond</comments>
		
		<dc:creator><![CDATA[Jack Glendening]]></dc:creator>
		<pubDate>Thu, 08 Mar 2018 08:53:47 +0000</pubDate>
				<category><![CDATA[report]]></category>
		<guid isPermaLink="false">http://blog.bigsurtrailmap.net/?p=1702</guid>

					<description><![CDATA[&#160; Nature is relentlessly degrading the National Forest trails in Big Sur.&#160; And the US Forest Service no longer maintains them.&#160; So volunteer trailcrews have been pushing back &#8211; lopping, sawing, and doing treadwork to keep the trails passable.&#160; But are they rebuilding the trails as fast as nature is destroying them?? Since July 2014 [&#8230;]]]></description>
										<content:encoded><![CDATA[<figure id="attachment_1992" aria-describedby="caption-attachment-1992" style="width: 345px" class="wp-caption alignleft"><a href="https://bigsurtrailmap.net/blog/wp-content/uploads/2019/10/rating_avg_vs_date.oct2019.annotated.png"><img loading="lazy" decoding="async" src="https://bigsurtrailmap.net/blog/wp-content/uploads/2019/10/rating_avg_vs_date.oct2019.annotated-345x254.png" alt="" width="345" height="254" class="size-medium wp-image-1992" srcset="https://bigsurtrailmap.net/blog/wp-content/uploads/2019/10/rating_avg_vs_date.oct2019.annotated-345x254.png 345w, https://bigsurtrailmap.net/blog/wp-content/uploads/2019/10/rating_avg_vs_date.oct2019.annotated-150x110.png 150w, https://bigsurtrailmap.net/blog/wp-content/uploads/2019/10/rating_avg_vs_date.oct2019.annotated-768x565.png 768w, https://bigsurtrailmap.net/blog/wp-content/uploads/2019/10/rating_avg_vs_date.oct2019.annotated.png 800w" sizes="auto, (max-width: 345px) 100vw, 345px" /></a><figcaption id="caption-attachment-1992" class="wp-caption-text">Updated Oct. 2019<br /><i><small>(Click for larger image)</small></i></figcaption></figure>
<p>&nbsp;</p>
<p>Nature is relentlessly degrading the National Forest trails in Big Sur.&nbsp;  And the US Forest Service no longer maintains them.&nbsp;  So volunteer trailcrews have been pushing back &#8211; lopping, sawing, and doing treadwork to keep the trails passable.&nbsp;  But are they rebuilding the trails as fast as nature is destroying them??</p>
<hr />
<p><span id="more-1702"></span></p>
<p>Since July 2014 I&#8217;ve published a <a href="https://bigsurtrailmap.net/trailconditionsmap.html">&#8220;trails conditions&#8221;</a> map, which I updated weekly based on public and private trail reports.&nbsp;  Having kept a history, I decided to see how the overall trail conditions have changed weekly since 2014.</p>
<p>The graphic shows the result.&nbsp;  In &#8220;normal&#8221; <small>(non-fire)</small> years, trailworkers are winning the battle and the overall rating improves.&nbsp;  That&#8217;s good news!  Since there are over 300 miles in the Ventana and Silver Peak wilderness areas, I&#8217;ve wondered whether despite all the trailwork being done we were slowly loosing ground just due to the extensiveness of the trail network.</p>
<p>But nature has a card up her sleeve &#8211; fire, which can undo years of trail maintenance.&nbsp;  Beside the obvious &#8220;natural&#8221; impacts &#8212; both immediate and post-fire of enhanced erosion and tree downing &#8212; there are &#8220;artificial&#8221; <small>(i.e. human-created)</small> impacts such as USFS closure of the forest to hikers and trailworkers, which lengthens the degradation period.</p>
<p>The Soberanes Fire essentially nullified the cumulative trailwork since July 2014 &#8211; the current rating is the same as back then.  Still, its encouraging that the fire did not undo all the work since the previous 2008 fire, so it would seem that progress is being made.</p>
<p>What about the future? That greatly depends upon fire frequency vis-a-vis the effort brought forth by public-spirited trailworkers.&nbsp;  Are you helping? Here is a link for <a href="https://www.meetup.com/Ventana-Wilderness-Alliance-Meetup/">VWA trailcrew events</a>.&nbsp;  Or <a href="https://www.ventanawild.org/donate">join or donate to the VWA</a> to help support paid-crew maintenance.</p>
<p>Since trail degradation should be a concern to all wilderness hikers, I&#8217;m now putting each week&#8217;s &#8220;average trail condition rating&#8221; on my <a href="https://bigsurtrailmap.net">Big Sur Trailmap homepage</a>.&nbsp;  And a link to its weekly-updated time-history.&nbsp;  What sort of trail experiences will future hikers have? Time will tell.</p>
<hr />
<p>
 <b>Whence the metric</b><br />
 My &#8220;average trail condition rating&#8221; is calculated by giving each mile of trail in the Monterey-district Los Padres National Forest a rating from 100% to 0%: 100% for &#8220;Clear&#8221; <small>(or better)</small> conditions and 0% for &#8220;Impassable&#8221; or &#8220;Closed&#8221; trails. <small>(&#8220;Historic&#8221;, i.e. no longer used, trails are not included.)</small> Each trail mile is multiplied by its rating, then summed and divided by the total trail miles.&nbsp;  Of course there are caveats &#8211; in particular, trail conditions should be accurately known but trail reports are infrequent for the less passable trails. <small>&nbsp;(An example is the rating decrease immediately after November 2016, when the National Forest again opened &#8211; overall trail conditions were actually increasing then, since trailwork was again being done, but the post-fire conditions of the less accessable burnt areas were not known until months after the re-opening, as reports trickled in.)&nbsp;</small> Despite the caveats, it&#8217;s better than guessing and/or individual impressions based upon hiking a few trails. </p>
]]></content:encoded>
					
					<wfw:commentRss>https://bigsurtrailmap.net/blog/state-of-the-trails-trailcrews-vs-nature/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
