<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Jakob Perry on Medium]]></title>
        <description><![CDATA[Stories by Jakob Perry on Medium]]></description>
        <link>https://medium.com/@japerry?source=rss-c0f220e4a251------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*r1NO_ireLu_VoEm80KuagQ.jpeg</url>
            <title>Stories by Jakob Perry on Medium</title>
            <link>https://medium.com/@japerry?source=rss-c0f220e4a251------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 20:57:43 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@japerry/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Don’t go making major version changes]]></title>
            <link>https://medium.com/jakob-on-drupal/dont-go-making-major-version-changes-474293dda1d7?source=rss-c0f220e4a251------2</link>
            <guid isPermaLink="false">https://medium.com/p/474293dda1d7</guid>
            <dc:creator><![CDATA[Jakob Perry]]></dc:creator>
            <pubDate>Fri, 12 Aug 2022 16:21:37 GMT</pubDate>
            <atom:updated>2022-08-12T21:09:49.813Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kP_1tI5UyJ8g_P51uMyGyA.jpeg" /><figcaption><em>Please stick to the minor module versions you’re used to. Credit: </em><a href="https://about.sourcegraph.com/blog/nine-circles-of-dependency-hell">https://about.sourcegraph.com/blog/nine-circles-of-dependency-hell</a></figcaption></figure><p>As one of the leads for the Drupal 10 readiness initiative at Acquia, I see a lot of modules. We are looking at the top 165 modules, coupled with another 50 or so modules used by either our products or customers, to ensure they’re ready for Drupal 10.</p><p>One theme I’ve observed some maintainers fall into is the idea of contrib major version bumps to work with the next major version of Drupal. However, as I’ll lay out below, this is a major problem for the community and is making it harder for users to get on the latest version of Drupal.</p><h4>Don’t bump the major unless you <em>a</em>bsolutely need to</h4><p>In general, you want to avoid major version changes. (IE: 1.0.0 to 2.0.0 or 8.x-1.x to 2.0.0) This can cause a cascading dependency problem on any downstream module or customer using your module.</p><h4><strong>Don’t make releases rely on mutually exclusive versions of core</strong></h4><p>The LTS version of Drupal core should closely match the .0 release of the next version. With few exceptions, your module should always require the current/last supported version and the next or current version of Drupal. When you constrain your release to mutually exclusive versions of core, it narrows the upgrade dependency window a customer can use to upgrade their site. When a module has two different<em> major</em> releases supporting two different versions of core, it makes the dependency tree even harder to follow, creating more opportunity for composer conflicts to occur.</p><h3>When should I <strong>not</strong> bump the major version?</h3><p><strong>Major Drupal core changes.</strong> Changing the core version is a major disruption from a dependency standpoint, even if the code doesn’t really change at all. Making your module require a new major version leads to all the dependent modules having to update as well.<br><em>Example: The symfony event handler in Drupal 9 changed, which means any module using symfony events cannot be compatible with 8, 9 and 10. Instead of making a new major version, make a new minor version and increase the minimum supported version of core.</em></p><p><strong>Major PHP changes.</strong> While the new php features are great, its imperative that developers know what the <em>minimum supported</em> version of PHP is for core. If PHP 8.1 comes out, don’t immediately start using 8.1 only features. The only reason you should ever even require a minimum PHP is because of a <em>needed</em> feature or library included in a newer version of PHP. This was more common in the PHP 5 to 5.4 days, but is increasingly rare today.<br>Instead, make sure your module is <em>compatible</em> with PHP 8.1, which should still allow it to work with all other versions of PHP at the time of this writing, which is PHP 7.4 and 8.0. Keep in mind that some sites may still be stuck on 7.3, which is still also supported by core.</p><p><strong>New features</strong><br>Any new features that don’t interrupt the existing functionality should be added to the current version. One alternative is bumping the <em>minor</em> version, which will allow most dependent modules to work with your new minor.</p><p><strong>To get semantic versioning</strong><br>Just getting semantic versioning (ie: 8.x-1.x to 2.x) is not a good reason to bump the version. The composer facade included with drupal.org already removes the 8.x portion. I suspect some smaller Drupal 8 modules may never need to move to semantic versioning, unless core or drupal.org mandates it. While it make look pretty and modern, it causes pain for downstream modules and projects.</p><p><strong>Incompatible tests</strong><br>While its important that code has backwards compatibility, even for EOL versions of Drupal, tests only need to support current versions of core. For example, tests written for Drupal 8.9 won’t work in Drupal 10. If your deprecations are mostly within tests, there isn’t a reason to up the version of your module or even compatibility. Drupal 8.9 is EOL and customers shouldn’t expect new module versions to work with old versions of core. But keeping your module technically compatible with earlier versions of core makes it easier for customers to upgrade.</p><h3>What are some reasons to bump the major version?</h3><p><strong>Your module’s public services have been rewritten and no longer match the current supported version.</strong> This typically occurs when a public method needs to be changed, or the architecture and codeflow of the module is changed significantly that backwards compatibility isn’t feasible. This can also occur if your module extends core classes that become deprecated.<em><br>However: Backwards compatibility should always be the goal. Instead of bumping the version to change a public method call, wrap your new call with the old one and mark it deprecated.</em></p><p><strong>Your module’s data model is rewritten in such a way that running simple update scripts aren’t feasible.</strong> It requires either reinstalling the module (if data is ephemeral), or migration.<br><em>However: Somewhat simple field changes or additions should be done in the same version with code that can interpret the missing change. Dependent modules should never interact directly with data your module owns.</em></p><p><strong>Features are removed or refactored in a way that you <em>want</em> dependent modules to not automatically work with the new version.</strong><br><em>Example: Search API Solr 8.x-1.x to 4.x: This uses a different version of solarium, and required the architecture to be rewritten. By making a new release, the old Search API Solr modules could continue to work on old versions. <br>However: These changes should not be taken lightly, as it requires the maintainer to now maintain two versions of the same module until the dependent modules are updated.</em></p><h3>Major contrib module version timing</h3><p><em>Never release a new major version within 9 months of a new major core release without planning to upgrade the last major version of your module as well.</em></p><p>While it may seem appealing to update your module’s major version around a major core change, <strong>its highly advised not to do that.</strong> Typically it takes at least a year for 80%+ of users to adopt the new version, which means you’ll need to support multiple versions for some time, regardless of whether we’re near a new major core release or not.</p><p>Each major module version release may have multiple downstream dependencies, public or custom, that need to also be updated. When maintainers bump their major version near the release of a major core version, it adds to the workload of end-users. This is especially tough for smaller orgs where they may have one resource or a periodic contractor updating their site.</p><p>If a module plans to have a major release close to a core release, make sure your previous major also supports the new core release as well. This unblocks customers from upgrading core, allowing them to incrementally upgrade their site instead of doing it all at once.</p><h3>Conclusion</h3><p>Upgrading to a major version of core is already a difficult task for users. Adding new features or re-architecting your module at the same time adds exponential complexity to an already difficult task.</p><p>Changing the major version of a module should not be taken lightly. At a minimum, maintainers should make an issue proposing the change and discuss the reasons for it. If there is a way to keep the module backwards compatible, go that route instead of making a new major version.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=474293dda1d7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/jakob-on-drupal/dont-go-making-major-version-changes-474293dda1d7">Don’t go making major version changes</a> was originally published in <a href="https://medium.com/jakob-on-drupal">Jakob on Drupal</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Navigating core_version_requirement]]></title>
            <link>https://japerry.medium.com/the-case-for-drupal-9-dbfa45c52f9e?source=rss-c0f220e4a251------2</link>
            <guid isPermaLink="false">https://medium.com/p/dbfa45c52f9e</guid>
            <category><![CDATA[drupal-8-development]]></category>
            <category><![CDATA[drupal-10]]></category>
            <category><![CDATA[drupal-9]]></category>
            <category><![CDATA[drupal]]></category>
            <dc:creator><![CDATA[Jakob Perry]]></dc:creator>
            <pubDate>Tue, 01 Mar 2022 16:31:51 GMT</pubDate>
            <atom:updated>2024-04-12T20:34:18.478Z</atom:updated>
            <content:encoded><![CDATA[<h3><em>Update (Aug 1 2022):</em></h3><p>At Drupalcon Portland, Nicolas Grekas, Gábor Hojtsy, Ryan Aslett, Matt Glaman, had a discussion which basically led to the creation of the <a href="https://github.com/mglaman/composer-drupal-lenient"><strong>drupal-lenient composer plugin</strong></a>. Developers are encouraged to use this plugin when working to update modules to the next version of Drupal.</p><h4>What should core_version_requirement look like?</h4><p>My personal preference is to work with the next ‘beta’ of a major version. That allows developers to immediately work with a module, but doesn’t allow it to automatically work with the next stable release:</p><p>If your module supports Drupal 8, 9, and 10: <br><em> core_version_requirement: &gt;=8.9 &lt;11.0.0-stable</em></p><p>If your module supports Drupal 9 and 10:<br><em>core_version_requirement: &gt;=9.2 &lt;11.0.0-stable</em></p><h3>Original Post</h3><p>Back when PHP 8 came out, there was some discussion regarding PHP version support with Symfony. <a href="https://twitter.com/nicolasgrekas">Nicolas Grekas</a>, a Symfony core contributor, made this observation:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/601/1*kHUGXf_G_Q41EhUMyXQUgA.png" /><figcaption><a href="https://twitter.com/nicolasgrekas/status/1263023258938548225">https://twitter.com/nicolasgrekas/status/1263023258938548225</a></figcaption></figure><p>The crux of his argument was that by using 7.x, you’re creating planned obsolescence, and by having the ecosystem adopt this system, you’re making it very hard for developers to even experiment with PHP8.</p><p>The other untold part of his argument is around ownership and control. Should composer be a hard-lined traffic cop, putting barriers on where code should be allowed to operate? Or should it be more of a guideline?</p><p>I totally agree with Nicolas here for PHP. In-fact, Drupal 8+ uses his advice and requires PHP &gt;=7.3 instead of ^7.3. But what about Drupal modules? With Drupal 10 coming soon, should modules be adopting the current recommendation: ^9|^10 ? or would &gt;=9.2 be better going into the future? What about Drupal 8 support? Lets discuss.</p><h3>First, a look back at #d9readiness.</h3><p>Drupal 9 was the first version of Drupal to be backwards compatible with Drupal 8, and had minimal changes for sites that were using the latest version. <strong>Drupal 8.9 =Drupal 9</strong>*. Modules also had a similar experience: those that maintained updates with core were pretty simple to upgrade to Drupal 9. <strong>But they had to add/change the core_version_requirement property.</strong> This meant many D8 modules that otherwise worked with Drupal 9 would not even pass composer checks due to the missing version compatibility. This made D9 testing very difficult, especially with dependencies if they weren’t Drupal 9 compatible. Only after modules had defined the core_version_requirement could they even be tested to see if they were truly compatible with Drupal 9.</p><p><em>*There were dependency updates, specifically symfony, that makes them not entirely equal. But in general if your module worked with D8.9 with no deprecations, it worked with D9.</em></p><h3>Minimum vs Maximum version requirements</h3><p>I think everyone can agree that setting minimum versions is a good practice. It allows code to use newer software and not have to be backwards compatible. However, to ensure customer success to newer versions of software, I only increase the minimum requirement if the code requires it. Having a larger window of version compatibility ensures customers can upgrade from older projects to newer ones without your module being a blocker.</p><p>Maximum’s don’t have this problem with deprecated code. Maximum versions aren’t about saying your code <em>won’t</em><strong><em> </em></strong>work with software above a specific version, but more “<em>we don’t know so we will just be safe and say it won’t</em>.” In practice this is unnecessary; either the software will work as-is, or will be broken and require maintainer intervention. The problem is, if you set maximum constraints, contributors can’t even test against the version they’re having a problem with!</p><h3>What about &gt;= 8.9? Drupal 8 is EOL!</h3><p>While the community has stopped supporting Drupal 8, the reality is thousands of Drupal 8 sites are still in use today. And if you support Drupal 9.0, you already support 8.9. Making it easier for customers to upgrade from Drupal 8 to 10 will be important, and it doesn’t help if we set our minimums too high.</p><p>While some will think Drupal 8 is quite outdated, this isn’t really true. Until Drupal 9.3 (November 2021), modules supported 8.9 and 9.2. With 9.3 and certainly D10 there will be new deprecations that will need to be worked around. <strong>But Remember</strong>: Drupal 9.2 is still supported! Its worth the tradeoff to help pull customers into the D10 ecosystem without having to do an intermediate upgrade to Drupal 9.</p><p><strong>If your module supported Drupal 8 until recently, consider keeping the ≥8.9 constraint until after Drupal 10 is released.</strong></p><h3>Remove maximums for Core only</h3><p>We’re lucky that at this point, Drupal core has become a very stable, well planned out software project. Its that trust, coupled with the d8+ major version policy, that allows this to work. <strong>That is not the case for contrib.</strong> The lack of consistency between projects and the fact that different versions may support entirely different dependency paths and data structures means you definitely should use maximum constraints for contrib modules in your own module’s composer file.</p><h3>Which version should I set as a minimum?</h3><p>Whatever minimum you currently have should be the constraint going forward: (^ 8.9 | ^ 9 ) should be rewritten:<em> &gt;=8.9 &lt;11.0.0-stable</em></p><p>If your module supports only Drupal 9 and 10:<em> &gt;=9.2 &lt;11.0.0-stable</em></p><h3>What about deprecations?</h3><p>As we get into deprecations, the following ugly code will be needed:</p><blockquote>//TODO: Remove when support for Drupal 9.2 dropped.<br>if (version_compare(\Drupal::VERSION, ‘9.3’, ‘&gt;=’)) {<br> $rendered = \Drupal::service(‘renderer’)-&gt;render($image); <br>} <br>else {<br> // @phpstan-ignore-next-line<br> $rendered = render($image);<br>}</blockquote><p>The above code will allow earlier versions of Drupal to work with the render function, while supporting the new version in 9.3. If your code only has a few of these programmatic changes, its worth the tradeoff to allow lagging customers to get upgraded without extra hurtles.</p><p><strong>Removing maximum limits to <em>core_version_requirement</em> will help speed up the pace to adopting the next major version of Drupal core.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dbfa45c52f9e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[WA / Oregon ATV Reciprocity]]></title>
            <link>https://japerry.medium.com/wa-oregon-atv-reciprocity-a485bbd9f3d6?source=rss-c0f220e4a251------2</link>
            <guid isPermaLink="false">https://medium.com/p/a485bbd9f3d6</guid>
            <category><![CDATA[oregon]]></category>
            <category><![CDATA[orv]]></category>
            <category><![CDATA[washington]]></category>
            <category><![CDATA[reciprocity]]></category>
            <dc:creator><![CDATA[Jakob Perry]]></dc:creator>
            <pubDate>Mon, 08 Nov 2021 06:00:21 GMT</pubDate>
            <atom:updated>2021-11-08T16:57:00.705Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/256/1*h5TQCRe9ndcCzTRqzC3vOg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*rGZWBzntoYyDP8q7LL-RyQ.jpeg" /></figure><p><em>Editors note: this post (and blog) is my personal opinion and does not necessarily represent that of WOHVA, WSTC, or any other organization I’m a part of.</em></p><p>The 2021 Legislative session brought <a href="https://app.leg.wa.gov/billsummary?BillNumber=1322&amp;Year=2021&amp;Initiative=false">HB1322</a>, a bill that would end reciprocity with any state bordering Washington that doesn’t collect a sales tax. Basically, Oregon. The intent of the bill was to make it harder for WA residents to buy their ORVs down in Oregon, and then title and ‘register’ it in Oregon, thus avoiding WA sales tax. However, as this story will show, not only did that not happen, but it now makes it much harder for Oregonians to recreate legally in Washington, and requires all Washington residents to buy Oregon ATV permits.</p><h3><strong>Wasn’t it already illegal for WA residents to not have WA ORV permits?</strong></h3><p>Yes. The exemption from registration has always been clear that it only applies to out of state residents when recreating in WA. However, the <strong>ORV dealers (WSMDA) </strong>believe just being illegal wasn’t good enough. LEOs couldn’t enforce the law because Oregon ATV tabs were assumed to be an Oregon resident.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xGxqP_BsFEn6eOijMY_rqA.png" /><figcaption>An LEO performs checkpoint stops for ORVs</figcaption></figure><p>However, this thinking is flawed. Due to where ORV tabs are placed on vehicles, mud, etc, the only way LEOs can effectively enforce the law is by doing checkpoint registration stops. This usually occurs at trailheads. In those cases, they stop everyone, and verify their registration is correct.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*viV6umjyFSRWrG5UcoOiBQ.png" /></figure><p>If you were a WA resident on an Oregon ATV, you’d get a ticket because the license wouldn’t match the registration.</p><p>Additionally, DOL <a href="https://www.dol.wa.gov/about/docs/leg-reports/2020-ORV-Legislative-Report.pdf">created a report</a> on those who weren’t properly registering vehicles, and none of the recommendations included eliminating reciprocity. In-fact, despite WSMDA’s claim, to the contrary, out-of-state registrations have been going down since DOL started sending out letters to tax avoiders.</p><h3><strong>How do Oregonians recreate legally in Washington now?</strong></h3><p>Under the bill, out-of-state residents can only recreate legally by obtaining a WA ORV registration. While this permit is free, it requires you to physically visit a Washington DOL office (usually open M-F 9–5pm), fill out <a href="https://www.dol.wa.gov/forms/420428.pdf">this form</a>, bring your Oregon ATV permit, and Drivers License.</p><p><strong>You cannot use a Discover pass in-lieu of registration. </strong>Off-road vehicles are exempt from needing a discover pass, whether they have a valid registration or not. Having a second discover pass but no valid registration would still land you a ticket on DNR land.</p><h3>Can WA residents not Register or title in Oregon?</h3><p>Washington Residents <strong>still can</strong> title their ORVs in Oregon and get an Oregon ATV permit. And if you don’t recreate on Washington Public Lands (DNR, USFS, WDFW), this bill changes absolutely nothing. If you do recreate on public lands, this bill still changes nothing because you weren’t legal in the first place.</p><h3><strong>Oregon ATV permit is NOT a registration or title.</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/160/1*0cnyAQjjaJ5M0A3UxjgO-g.jpeg" /></figure><p>ORS 803.03 exempts Class I, III, and IV ORVs from getting registration and makes getting a title optional. This means that the Oregon ATV permit operates under the same legal framework as the discover pass. More importantly: Its administered by Oregon State Parks (not DMV) and <strong>does not require proof of ownership.</strong></p><h3><strong>Doesn’t that create a massive loophole for registration?</strong></h3><p>It certainly does. Washington residents can just get a friend in Oregon to put their name on the Oregon ATV permit and then go up to Vancouver and get a WA tab. Even better, if you own property (or a drivers license) in Oregon, you can now get a free Washington registration and appear 100% legal to an LEO in the field.</p><h3><strong>Who pushed this?</strong></h3><p>Contrary to many different comments on social media, this was not Democrats or Inslee’s doing. (He actually <a href="https://crmpublicwebservice.des.wa.gov/bats/attachment/vetomessage/bfcbd656-1076-ea11-8181-005056ba1db5#page=1">vetoed it</a> in 2020) It was a bipartisan effort, pushed forward by… <a href="https://lawfilesext.leg.wa.gov/biennium/2021-22/Pdf/Bill%20Reports/House/1322%20HBR%20TR%2021.pdf?q=20211107213421"><strong>the ORV business community</strong></a><strong>, </strong>and had little resistance by any of the ORV groups. <strong>WOHVA</strong> was the only group that publicly opposed the measure, and the business community used the same Lobbyist that NMA and WOHVA used in the past. Because of this, Northwest Motorcycle Association, Washington State Snowmobile Association, nor the Washington ATV Association did not oppose the measure, nor did Ted Jackson, or Tod Petersen, two major heavyweights when it comes to statewide ORV issues. While I pushed hard to oppose it from WOHVA, I’m not a lobbyist, and do not have the same clout. Basically I was told repeatedly: who cares about Oregon residents?</p><h3><strong>Lessons learned</strong></h3><p>This is a major blow to the ORV recreating community. Not only does it cost WA residents more to recreate in Oregon, but defaults Oregonians to illegal use in Washington state unless they jump through a bunch of hoops. Even worse, it barely impacts those who’re avoiding sales tax. Most likely most of these users don’t even use their ATVs on WA public land, which is why they avoided getting a WA ORV permit in the first place.</p><p>Tell the recreation caucus chair how this bill affects recreation for you, and to draft a bill removing the language now present in RCW 46.09.420(4)(b)<br>Andrew Barkis: <a href="/service/mailto:andrew.barkis@leg.wa.gov">andrew.barkis@leg.wa.gov</a><br>Cindy Ryu: <a href="/service/mailto:cindy.ryu@leg.wa.gov">cindy.ryu@leg.wa.gov</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a485bbd9f3d6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Turntable, a love story]]></title>
            <link>https://japerry.medium.com/turntable-a-love-story-fd70fd4c81ca?source=rss-c0f220e4a251------2</link>
            <guid isPermaLink="false">https://medium.com/p/fd70fd4c81ca</guid>
            <dc:creator><![CDATA[Jakob Perry]]></dc:creator>
            <pubDate>Sun, 21 Mar 2021 07:03:32 GMT</pubDate>
            <atom:updated>2021-03-26T16:22:12.339Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/960/0*QTxsiFG_FEPpOXDY" /><figcaption>The day turntable.fm died.</figcaption></figure><p>Its been nearly 10 years since Turntable.fm launched. And when it launched it changed my listening habits entirely. Gone were the days of radio stations playing the same crap over and over again. Gone were pandora or my own playlists which took forever to curate and, again, played the same crap over and over again. Even my most favorite songs get tiring.</p><p>Turntable.fm was my favorite place to discover new music while still injecting some of my own tunes from time to time. It was like being able to listen to the radio and making a request that would <em>actually get played</em>.</p><p>When turntable.fm shutdown in 2013, some of my community in Trance Out moved to Plug.dj. But it wasn’t quite the same, we moved from an average of 20ppl in the room down to 10. And when Plug.dj shutdown (the first time) two years later, we moved to Dubtrack with about 5ppl per room. The ‘discovering new music’ started to wane, and all the issues that brought me to turntable pretty much came back.</p><p>This post will go over some of the pluses and minuses over the years in the different platforms, in hopes that the new turntable.org may actually turn into something sustainable.</p><h3>Plug.dj</h3><p>Plug worked fairly well, but had one big issue: trolls. For some reason people would love to come into your room and ruin a good thing going on. While Turntable had some of these issues, it was really bad on plug. However, moderator tools did help, and a bot was useful for music tracking and auto-banning.</p><p>The best thing about plug.dj was its playlist and queue management. It allowed you to rename tracks, make multiple playlists upto 200 tracks, and shuffle them.</p><p>Plug.dj also had a brand ambassador program, consisting of room owners, extension creators, and others (including myself). Two of these BAs became developers once it was purchased and relaunched in 2016. Having a strong community of super-users help keep the spam down and for the most part we could answer support questions and help rooms advertise events that were being organized.</p><p>While people complained about the avatars, eh, I thought they were fine.</p><h3>Dubtrack / Queup</h3><p>This platform, while similar to plug and turntable, lacked one thing: Avatars. It was essentially a collaborative playlist system. Before I get into its perks (because of the three, imho it was the best), let me talk about Avatars. In retrospect, not having a ‘dance floor’ actually was a problem. Seeing 20 bopping heads is a bit different than seeing an upvote counter. While having fullsize videos was great, the lack of seeing the audience made even a full room seem small.</p><ul><li>++ Playlist Management</li></ul><p>The way playlists were managed in DT was by far the best. Unlimited tracks per playlist, and the ‘queue’ was actually separate from your playlist source.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*klqNAVaCjhebPhNHMAdy3Q.png" /><figcaption>‘My Queue’ was tracks ‘added’ from the 2016 Trance (1) playlist.</figcaption></figure><p>This means that you could create a queue of 1000+ songs from various playlists and run it on autopilot. Unlike plug and turntable, this meant in smaller rooms you wouldn’t end up with repeating tracks because you could easily add hundreds of tracks into your queue and shuffle them independently of your source playlists.</p><p>DT also stored the Youtube/soundcloud ids in their own database. This meant that queing / searching for tracks others have already added was quicker and didn’t run against the dreaded youtube api limit issue plug.dj was hitting.</p><p>Another <strong>huge</strong> advantage was the mod ability to see what <strong>others</strong> queued up to play next.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iVoHSrNF9M4DZTd4W6zaOg.png" /><figcaption>New user entered the room and is about to play a song that doesn’t fit the genre</figcaption></figure><p>This allowed mods and/or a bot to prevent songs that didn’t fit the room to be played. The only real alternative on plug was to restrict DJing to the ‘Resident DJ’ role, and on turntable you could use a bot to kick all but vetted users.</p><h4>Room Moderation</h4><p>Speaking of mods, DT had the best moderation tools as well.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Qf6FMTVl6Le7WB9mSbsNsA.png" /></figure><p>While Plug.dj had some of these roles as well, they weren’t as granular as dubtrack. By having these permissions delegated out, much of the mod code required in Turntable.fm was not needed anymore.</p><p><strong>Live Embeded Sources</strong></p><p>While not used that often, the ability to embed an iframe allowed for live events to be streamed into the channel. You could also stream youtube live, something that doesn’t work on Turntable.fm</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nA4IfwigbeELI0w4_FCuwQ.png" /></figure><h3>The OG Turntable.fm</h3><p>Relaunched in March 2021, we got thrown back to the platform that shutdown in 2013. And man there is a lot to miss about the other platforms.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0DB4f49vZ3jArBFTFwRsYA.png" /><figcaption>You need a chrome extension to change the volume. <strong>THE VOLUME!</strong></figcaption></figure><p>I think our largest concern is how long this iteration of turntable.fm is going to last. The closed beta for turntable.org at the moment is unusable. Our audience do not use Apple music or Spotify.</p><h3>Lets start with the great: Stability and Reunions</h3><p>Since tt.fm was relaunched, the site has been stable and the issues plaguing the late Dubtrack and now Queup (API request limits, socket going down, etc) don’t appear to be an issue here.</p><p>And after a 2 month hiatus, people love to be coming back in. There is momentum to get our bots back up and even the turntable discord appears to have momentum.</p><p><em>Stability cannot be understated. Aside from compatible music services, the ability to actually listen to our music is a basic qualification for any service, full stop.</em></p><h3>Now for the bad: Limited Mod and Playlist tools</h3><p><strong>Moderation? What Moderation?</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/0*kPHOz23VStNh8pRA" /><figcaption>A common occurrence when the room had a bigger audience</figcaption></figure><p>The inability to have good mod tools was a big problem for active rooms. Since there was only one mod role, typically it was reserved for only a handful of people, usually not all online at the same time. With DT, you could give lesser permissions for trusted room members to keep things peaceful.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/0*nUcLfac2bI7nY1EK" /><figcaption>Voting songs down were the only way to mod a room, and that could take time.</figcaption></figure><p><strong>What about custom uploads?</strong></p><p>I’d love to be able to upload custom tracks to these platforms. While using Youtube and Soundcloud certainly has technical (stability) and business/legal benefits, it means that worldwide audiences will end up getting unplayable music. It essentially restricts rooms to specific countries because otherwise every few tracks you get 4–8minutes of silence. Ugh.</p><p>However, there is value in video. Being able to have events with video (twitch streams on Turntable would be <strong>awesome</strong>!) makes them that much better. So while having uploads back on Turntable would be nice, I’d still love to have youtube.</p><p>Also, back in the turntable days of custom uploads, the included music was pretty terrible. I remember many of the included tracks were from cover artists, especially for more well known tracks. I’d much rather source my music from youtube than whatever library the OG turntable was using.</p><h3>Conclusion</h3><p>I really hope one (tt.fm, tt.org, queup) can succeed. While our channel is sticking with tt.fm right now, if these other services can bring the stability and basic requirements along with a sustainability plan, I could see us making a switch.</p><p>By bringing some of the better playlist and moderation tools that Dubtrack had, and giving a live event vibe with avatars, backgrounds, etc, hopefully people will gravitate back here. The idea of streaming twitch or having a new embedded video stream from OBS would be a really cool alternative to twich, allowing scheduled shows to occur in rooms with music played in between.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fd70fd4c81ca" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Yacolt 2016 Construction Plan Feedback]]></title>
            <link>https://medium.com/dnr-trail-policy/yacolt-2016-construction-plan-feedback-72a94f2d4452?source=rss-c0f220e4a251------2</link>
            <guid isPermaLink="false">https://medium.com/p/72a94f2d4452</guid>
            <category><![CDATA[4x4]]></category>
            <category><![CDATA[dnr]]></category>
            <category><![CDATA[orv]]></category>
            <dc:creator><![CDATA[Jakob Perry]]></dc:creator>
            <pubDate>Wed, 06 Dec 2017 20:11:42 GMT</pubDate>
            <atom:updated>2017-12-06T20:11:42.633Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vR3pd53LtzUoRi90CPfM6Q.jpeg" /></figure><p>Below are the slides from DNR regarding trails planned to be built in 2016. I’ve included only slides that merit a response. <a href="https://www.dropbox.com/s/ojia0i9zlb58f6o/6Mile_2016_01_27.pdf?dl=1">To view the entire presentation, click here.</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ycAAcEWbBhAWnQUk0DyupA.jpeg" /></figure><p>I think it goes without saying that quite a monumental feat happened in 2014. However, its disingenuous to talk about only the successes and not have a <a href="http://retrospectivewiki.org/index.php?title=Retrospective_Plans">retrospective plan</a>. Without a frank retrospective between the agency and volunteers, its hard for volunteers to understand why DNR wants to change things, and its hard to figure out what to do better next time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EEJCDVX_7zAdKKQnfTwJqw.jpeg" /></figure><p>DNR has been issued a programmatic permit for grading, clearing, and stormwater. Interestingly, the Salamander study only points out that 25 of 35 crossings contain the species, and mainly focuses on the Hagen Creek trail, not part of this plan.</p><p>DNR is also required to submit an annual plan, including photos, of work done in the previous year.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/689/1*6a0S720_SsQE00Hz2v8z-w.png" /><figcaption>Identified Stream Crossings per the <a href="https://www.dropbox.com/s/egugam45ixrnj6a/DevEngDocs_200173%20Yacolt%20Motorized%20DNR%20Recreation%20Trail_GRD2013-00014_2nd%20review_Appliciant%20Submittals_04%20-%20Habitat%20and%20Mitigation%20Plan.pdf?dl=1">WDFW Wildlife Habitat Assessment</a></figcaption></figure><p>In short, the trails built this year should be fairly simple from a water crossing standpoint. There are three water crossings. Site 13 was already created by the L-1552 road. The trail should be relocated to avoid crossing site 16. Site 18 might be able to be slightly re-routed 50ft to avoid needing a crossing.</p><p><em>Fun fact: DNR ignored WDFW’s recommendations on sites 10 and 9 to relocate the trail down stream 50ft so they wouldn’t need culverts.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dZKcAM3_FeQPt8cCTeOLYg.jpeg" /></figure><p>Read that — <strong>$449,500 ( minus ~$18,000 in volunteer hours)</strong> Over 6 miles of trail. That is roughly $78,000/mile of trail. Trail that is nearly 50% old grades that already exist. <strong>That is insane.</strong></p><p>DNR did not like the fact that volunteers pushed back on 6 miles being just fine. If we only accomplish the 6 miles with this amount of money, <strong>we have failed.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FQnhueF57V6ES_TMyL3zag.jpeg" /></figure><p>You can see the full construction plans <a href="https://www.dropbox.com/s/x0l8yk4f6340f68/DevEngDocs_200173%20Yacolt%20Motorized%20DNR%20Recreation%20Trail_GRD2013-00014_1st%20review_Applicant%20Submittals_04%20-%202013-04-10%20-%20Yacolt%20Motorized%20Trails%20-%20Full%20Plan%20Set.pdf?dl=1">here</a> and <a href="https://www.dropbox.com/s/u6q4tgc54h69qln/DevEngDocs_200173%20Yacolt%20Motorized%20DNR%20Recreation%20Trail_GRD2013-00014_1st%20review_Applicant%20Submittals_03%20-%202013-04-10%20-%20Yacolt%20Motorized%20Trails%20TIR%20Final.pdf?dl=1">technical information here.</a></p><p><strong>DNR keeps reiterating that it maters what the <em>tilt</em> and <em>maximum rise</em> of the rock is. What is crazy is those standards are relatively arbitrary and prone to interpretation. At the same time, DNR in 2014–15 failed to adhere to these minimum trail standards as stated in the construction plan</strong>s:</p><ul><li>5% Minimum slope</li><li>Waterbars installed where slope is over 10%</li><li>“Grading activities are intended to be as minimal as possible to keep the trails challenging to ride or drive”</li><li>Minimum brush and small tree removal. Clearing is limited to the trail dimensions described. No additional vegetation removal, such as shoulders, is required.</li></ul><p>While I disagree with some of the standards (36&quot; Motorcycle trail, what?), and we should file amendments to them, DNR needs to understand how to build trail. <em>The volunteers are not at fault</em>, since they didn’t receive the necessary training and believed they were doing everything to DNR’s liking.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PY1n86JPOxMchjmziW8N0Q.jpeg" /></figure><p>In 2014, most everyone here was new to trail building. This year, DNR is planning on only utilizing Piston’s Wild and JCTRA to build trail, while slowly ramping up other user groups (like Watch This Fourwheelerz and Vancouver 4 Wheelers).</p><ul><li>I understand there is hesitation, especially since the relationship with volunteer groups have been rocky. But instead of denying the ability to work with DNR for summer 2016, I suggest DNR do the following:</li><li>Enter into a cooperative agreement with interested clubs</li><li>Provide training to <strong>all</strong> groups new and old, including DNR staff, before shovels hit the dirt.</li><li>Provide some additional oversight to new groups for the first few weeks. Similar to how PW and JCTRA ramped up in 2014.</li><li>Work on a decommission strategy and partially implement it before construction.</li><li>Start on C-9, C-10, and C-11 trails with new groups. C-9 is basically complete, C-10 and C-11 are small segments that would be a manageable chunk for a new group to grow into.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VG5Ti7E83kEFauqEOM1yjg.jpeg" /></figure><p>DNR has already banked miles of decommissioned trails. We’re about 4 miles in the positive at the moment. New users can get experience with equipment by decommissioning old trails. But again, before any shovels hit the dirt, crews need to be <strong>trained</strong> on abandonment procedure.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6xpfnj6NW424yZaYffKFJg.jpeg" /><figcaption>Proposed trails for abandonment</figcaption></figure><p>Lets be clear about what Phase one contains:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LHypKFqIXLzc5ixEQiszjA.jpeg" /></figure><p><strong><em>Before any decommissioning plan, trails need to be field verified.</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CADHPB7Ai4TiNl0uJTCPSA.jpeg" /></figure><p>After all the trouble with contractors at Reiter. <a href="http://apps.leg.wa.gov/billinfo/summary.aspx?bill=2151&amp;year=2014">After going through a trails policy</a>. After seeing the ballooning costs. Why is this being suggested? The suggestion of contractors left volunteers shaking their heads.</p><p>For ATV trails, this makes absolutely no sense. C-12 and C-13 are shorter than the 2014 trails, and JCTRA have 2 years to complete them. <strong>This should not need contractors.</strong></p><p>For 4x4 trails, this makes less sense if more groups are involved. As a community, we’ve delegated C-14 to Pistons Wild. This will take them most of the summer to complete. But if the suggestions above are followed, <strong>this should not need contractors.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tTbufOaZ_fa8ijFbctBKNA.jpeg" /></figure><p>This slide is, to put it bluntly, rude and undeserved. Read more.</p><h3>What was missing from the DNR plan?</h3><h4>Community/Volunteer Construction Plan</h4><p>In December 2015, stakeholders from Pistons Wild, JCTRA, Watch This Fourwheelerz, and Vancouver 4 Wheelers met and <a href="https://www.dropbox.com/s/hx2e6bee8mmdw0w/2016%20Yacolt%20Construction%20Plan.pdf?dl=0">coordinated a plan.</a> We delivered this plan to DNR staff on January 12th in hopes that we could discuss some merits of the plan at this meeting.</p><p>That did not happen.</p><p>DNR didn’t offer up a time to discuss the plan in detail, and dismissed it as “having some good ideas” but “don’t just send us a plan without talking to us first” — Our hope was that giving DNR two weeks to think about our ideas would help us come to better terms for what we wanted at this meeting. Its unfortunate DNR staff did not see it that way.</p><h4>No Training</h4><p>DNR’s plan discusses tagging the P-line and even kicking off some light brushing before full on construction. Missing here is lack of training. At no point in 2014 did any volunteers have the <a href="https://www.dropbox.com/s/x0l8yk4f6340f68/DevEngDocs_200173%20Yacolt%20Motorized%20DNR%20Recreation%20Trail_GRD2013-00014_1st%20review_Applicant%20Submittals_04%20-%202013-04-10%20-%20Yacolt%20Motorized%20Trails%20-%20Full%20Plan%20Set.pdf?dl=0"><strong>full set</strong></a> of construction plans or <a href="https://www.dropbox.com/s/u6q4tgc54h69qln/DevEngDocs_200173%20Yacolt%20Motorized%20DNR%20Recreation%20Trail_GRD2013-00014_1st%20review_Applicant%20Submittals_03%20-%202013-04-10%20-%20Yacolt%20Motorized%20Trails%20TIR%20Final.pdf?dl=1">technical details</a>. While volunteers were trained on heavy equipment &amp; chainsaw TSA and JSAs, no one was trained on waterbar spacing, side slope, etc.</p><p>I hope DNR schedules a meeting to discuss <strong>how</strong> we will build the trails. This way, perhaps we can get the debate about natural soils out of the way, and point to the standards when DNR staff believe the trail isn’t ‘pretty enough’.</p><p>It is important we discuss the how and get sign-off from all parties so we don’t have any misunderstandings.</p><p>I’m not sure how DNR felt about this kick-off meeting, but from almost every community member who was there the response was fairly unified:</p><ul><li>DNR doesn’t know how to work with the community.</li><li>DNR doesn’t know how to adapt to changing conditions.</li><li>DNR doesn’t know how to learn from its past mistakes.</li><li>We were all deeply frustrated by this meeting.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=72a94f2d4452" width="1" height="1" alt=""><hr><p><a href="https://medium.com/dnr-trail-policy/yacolt-2016-construction-plan-feedback-72a94f2d4452">Yacolt 2016 Construction Plan Feedback</a> was originally published in <a href="https://medium.com/dnr-trail-policy">DNR Trail Policy</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Reflections on Yacolt Burn 4x4 Trails]]></title>
            <link>https://medium.com/dnr-trail-policy/reflections-on-yacolt-burn-4x4-trails-3346247bd84f?source=rss-c0f220e4a251------2</link>
            <guid isPermaLink="false">https://medium.com/p/3346247bd84f</guid>
            <category><![CDATA[running]]></category>
            <category><![CDATA[environment]]></category>
            <dc:creator><![CDATA[Jakob Perry]]></dc:creator>
            <pubDate>Fri, 16 Oct 2015 17:27:05 GMT</pubDate>
            <atom:updated>2015-12-04T19:55:38.436Z</atom:updated>
            <content:encoded><![CDATA[<p>Spring 2015 marked the opening of the first ever DNR designated 4x4 trails in Southwest Washington. It was 8 years in the making and cost over a <strong>quarter million dollars.</strong> While something was accomplished, the sense I received from non-pnw4wda users was that it didn’t meet the minimum needs of the greater 4x4 community.</p><p>What are some of the issues with Yacolt ORV area?</p><ul><li>Lack of diverse public involvement</li><li>Pacific Cascade region’s misunderstanding of 4x4s</li><li>Process from user-built to DNR managed trails</li><li>Multiple Use theory</li><li>Heavy Equipment instead of Volunteers</li><li>Reliance on timber sales and logging roads</li><li>Time Line</li></ul><h3>First: The Good</h3><p>Pistons Wild 4x4 group spent 6000+ hours and over $90,000 in upfront cash (before being reimbursed by DNR) to build the trails at Yacolt Burn. Pacific 4wd Association (PNW4WDA) Region 3 gave another $5000 to get the trails open. It takes a special type of dedication to put forth that effort, and without their hard work, we wouldn’t be where we are today with DNR in Southwest Washington.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*LGipOat7-Z9WowyPf7hCHw.jpeg" /><figcaption>Volunteers helping get the trails open by May 2nd.</figcaption></figure><p>While I may think they could have been more direct about getting better trails (what Scott has been doing at Rieter), I wasn’t here for 7 years and the troubles they were getting with <em>any </em>trail seems to be more difficult in the Pacific Cascade region vs anywhere else in the state. So I understand why they wanted to get something on the ground first.</p><h4>Why not use contractors for building the trail?</h4><p>I’ve heard this question come up time and time again. Road and WCC crews are able to punch in trail faster than what our volunteers. We also see that they could have done it cheaper, when comparing this to Reiter’s cost per mile for trail (excluding obstacles) in 2015. If DNR is not going to change its building standards, this is a legitimate argument. Volunteers <strong>are not</strong> able to build trails <strong>faster or cheaper</strong> than contractors <strong>with current requirements.</strong></p><p>But I’d argue thats not the fault of volunteers. We need a better building process so that we can make volunteers more efficient. More about this later.</p><h3>Pacific Cascade (PC) Region’s approach to motorized recreation</h3><p>Strained would be saying it kindly, in regards to the relationship between DNR and motorized volunteers.</p><p>In the beginning I had hope, after two successful meetings, it seemed like things were looking up in regards to the region. However, as the spring waned, I realized I was mistaken.</p><p>In eight years, Crystal Crowder (Piston’s Wild) and Mike Ames (Jones Creek Trail Riders Association) have worked with a myriad of staff, from the ‘do whatever you want’ to the downright hostile (close everything). But in those 8 years, they haven’t met the region manager for the landscape (06/01/2015). There doesn’t appear to be pressure from upper management to deliver trails (regardless of quality), and there is very little incentive in the job description of the employees on the ground to provide the right type of trails for the users they’re supposed to serve in a timely matter.</p><p>When put to the challenge, boots on the ground lack the experience to build and manage motorized trails correctly. Here are some specific examples.</p><h4>Seasonal Closures</h4><blockquote>The decision to close recreational trails is based several factors: the geology/soils of the trail area, the trails, rain fall, the amount of use, and maintenance including cost and resources. We have found that winter closures have been very helpful in maintaining the quality of the trails and balancing the maintenance and cost and ensuring that resource protection (water quality) is occurring.</blockquote><p>— Mary McDonald, State Lands Assistant, Asset Management</p><p>However, the science does not back her statement. First, rainfall totals are very similar to that of Walker Valley and Reiter (below). Elbe has slightly less annual rainfall.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uyz-x9D_2K5mPBLD2GGmdA.jpeg" /><figcaption>DNR Recreation areas overlaid with annual rainfall totals.</figcaption></figure><p>GIS, permits for the new 4x4 trails, and on the ground soil samples, don’t support the closure. An analysis of two other ORV areas, show very similar soil grades as Yacolt.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XB0b4zxv_QNzMmwFZUiAHA.jpeg" /><figcaption>USDA GIS Web Soil Survey, the same tool DNR uses for its suitability reports and permit requests.</figcaption></figure><p>The only supporting evidence for suitability is soils near the Jones Creek trail-head. But closing the entire landscape because of ~200 acres of potentially wet soil is a bit extreme.</p><p>Walker Valley has a similar issue, and is open year round. In 2010 environmentalists put Walker Valley under the spot light.</p><blockquote>DNR is aware that several of the photos shared with us by Mr.<br>Lider, while illustrating some impacts to trails, may in fact not be<br>causing damage to public resources like streams. We are also aware that<br>several of the areas identified may have real resource damage. While we<br>are committed to providing recreational opportunities, we are also<br>committed to those opportunities being environmentally sustainable. — Peter Goldmark, CPL Public Lands 06/29/2010</blockquote><p>Efforts by volunteers, along with the department of ecology, identified the actual problem spots and repaired them. While some trails were temporarily closed, the ORV area was never shut down.</p><p>In 2002, Walker Valley was headed for seasonal closure. <a href="http://bb.bc4x4.com/showthread.php?9126-Walker-Valley-closed!&amp;p=55890&amp;highlight=#post55890">But the efforts of volunteers stopped that from happening</a>, and in December, only 2 months after the initial closure, the <a href="http://bb.bc4x4.com/showthread.php?13406-Winterized-Trail-quot-in-Walker-Valley-Re-opens-December-28">CPL announced its reopening.</a> We should do the same for Yacolt.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7b5U7kTgw_O2l3MRS4kVXg.jpeg" /><figcaption>Open year round, Walker valley is about half and half for water suitability, according to the Hydrologic Soil Group data.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/573/1*iNHJj6g7OtEEKX7ePFnBIQ.jpeg" /><figcaption>Work Parties happen year-round at Walker Valley, and is mostly open for the winter.</figcaption></figure><p>Elbe foothills, which is known for its mud, is best suited for the wet, according to the data. Only pockets of unsuitable soils exist. These are mitigated by placement of trails and volunteers maintaining the system.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0Nfk_YCcPvIezfin7h7gLw.jpeg" /></figure><p>The data simply doesn’t support a full on closure of Yacolt during the winter months. Nor do the trail conditions on the ground.</p><h4>Trail Design</h4><ul><li>DNR consulted with a landscape architect who essentially copy/paste from the <a href="http://www.dnr.wa.gov/Publications/amp_rec_reiter_4x4_hbb_specs.pdf"><strong>Reiter</strong></a> plan with a <a href="http://fcdnet.org/Yacolt4x4plan.pdf"><strong>few adjustments</strong></a>. They failed to consult and/or listen to the recreation groups, creating Class IV+ USFS equivalent trails in a primitive setting. This isn’t a PC specific issue, this spans new construction on DNR land in regards to motorized recreation.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9dOTf2kD5purOrQ_SVc4sg.png" /><figcaption>Comparison between the Reiter and Yacolt Plans.</figcaption></figure><ul><li>The lead recreation forester has no degrees or experience with trail building, design, or even road building. In-slopes and Out-slopes are not defined. Berms exist on the sides of the trail making it the low point for water flow.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*03VOUMUlzNpyZPoFgsoESQ.jpeg" /><figcaption>This 15% grade has no water bars and is not side sloped correctly. Water will eventually work its way down the left side of this photo.</figcaption></figure><ul><li>At the same time, decision makers in the region have little experience with other 4x4 systems in other DNR regions or adjacent (ODF) land. They didn’t tour the other areas until late into the process. When they did, they did not invite recreationalists to show them which trails at TSF have good user experience and which don’t. This leads to a misunderstanding about the desired trail experience all users want.</li><li>Reiter is working on trails 4 days a week during the winter and summer months. Yacolt stopped construction from November until mid March.</li></ul><p>However, there is some hope: Ryan Schreiner was hired late last year to manage recreation in the PC Region. His previous post was Southwest District Trail Leader of the Washington Trails Association.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*ZXMOtU3gy1A1qSsh3cKMsA.jpeg" /></figure><p><em>“the volunteer program is great for anyone and students are more than welcome to join. I started out as a volunteer. Now I work here and I love it.”</em><br>- Ryan Schreiner regarding working at WTA</p><h3><strong>Lack of public involvement</strong></h3><h4>Planning Meetings</h4><p>Many other regions hold group specific monthly focus group meetings to organize work parties and receive detailed feedback. Yacolt is a bit different. There is an every-other-month meeting for <em>all</em> recreation groups, motorized and non-motorized. These are high level, relatively pointless meetings. Actual decisions are made elsewhere. This lack of openness makes it very hard for new groups to get involved.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/517/1*q8kWhfycQz8t0N_NKt-B3A.jpeg" /><figcaption>6, 2 hour meetings is not enough to plan and manage a trail system.</figcaption></figure><h4>Work Parties</h4><p>User groups had to initiate, organize, and operate work parties. PC DNR rarely sets up work parties on their own, and doesn’t schedule regular work parties, unlike the Northwest and South Puget Sound regions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/993/1*h8LIPfIj0H1ixPEt-vc7Bw.jpeg" /><figcaption>Piston’s Wild was up there on a Monday, coordinating rock and deliveries. Google Earth caught the action! Whats missing? DNR Red trucks.</figcaption></figure><p>At Walker Valley there are monthly work parties. Planning for these parties happen at the meeting beforehand. Reiter has monthly work parties. Elbe usually has monthly work parties (sometimes less in the winter). If there is consistency, people show up. If people show up, trails get maintained. If trails get maintained, they stay open. If they stay open, more users come to help out. Then those users bring their diverse ideas, making for a better trail system all around.</p><h3>User Needs</h3><h4>Defining User Groups/Classifications</h4><p>For those outside of the Motorized community, there are probably two main groups: ATVs and Motorcycles. Within the motorized community, you see ATVs, Motorcycles, and 4x4. But within the 4x4 community there is quite a <a href="https://medium.com/dnr-trail-policy/orv-diversity-8218dc50b70e"><strong>spread of technical skill and need</strong>.</a></p><p>The only obstacle that was allowed to be built was flat &amp; rectangular, which makes it <em>look</em> hard but its actually quite easy. Now for some classes of vehicles, this obstacle is just fine. We just want more, and we want some harder obstacles.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*7XDT_1XrOCNHklIwcpYRPg.jpeg" /><figcaption>Yacolt Rock Pile, horizontal and rectangular. Can be done in 2WD.</figcaption></figure><p>Below are some examples of man made and natural obstacles using rock at other DNR ORV landscapes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*ooNz_nVeeDnREmmA-voNUQ.jpeg" /><figcaption>Typical rock pile at Reiter for a Yellow trail (35&quot; tires). Notice how the rocks are nearly half the size of the buggy. Man made obstacles have to be this large to provide challenge.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tzr9ghNHH-xdgDvCgiRhig.jpeg" /><figcaption>Natural occurring rock at Reiter for extreme, well built 4x4s.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*CKvP1jtveM44DKQHLNZb8Q.jpeg" /><figcaption>Naturally occurring rock at Walker Valley, provides a challenge for mildly built 4x4s</figcaption></figure><h4>Trails are being built like roads</h4><p>The first four trails are being built like roads. Even the gatekeepers provide little challenge for 4x4 vehicles.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2-gMvwKcDMgarRiU_q4emg.jpeg" /></figure><p>The standard says 12&quot; obstacles, but then says “suitable for a vehicle in 4-wheel drive with a rear locker.” At 12&quot; most trucks in 2WD will be able to overcome such obstacles. Despite there being several areas that could have been more difficult, there are <strong>no</strong> challenges on the C-1 or C-2 trails.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mls9hNrSfj88cKeTvpmfug.jpeg" /><figcaption>C1 Trail is a narrow logging road, and in some cases, an actual old logging road.</figcaption></figure><h4>Building intermediate trails</h4><p>Lets be clear:<strong> I’m not arguing for extreme trails.</strong> Instead, I would like to see a diverse trail system, with various opportunities, and at least some that go by DNR’s definition: “Requires 4wd and a rear locker to complete the trail”</p><ul><li>Mild rock and log obstacles across the trail without bypasses</li><li>Gatekeeper/filter that requires 4wd and a locker</li><li>Water bars that are effective for runoff and provide a more primitive trail experience.</li><li>Off-camber sections</li><li>Tight turns</li><li>Steep (&gt; 20%) inclines/declines</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zjDWOs5zaRZ39jTZOYFWEg.jpeg" /><figcaption>At Nicolai Mountain and Elbe the rocks are placed strategically to give hard lines for vehicles w/ 35&quot; tires looking for a challenge.</figcaption></figure><h3>User-built to DNR managed trails</h3><p>We need to change the idea that user-built trails, or user converted orphaned roads are all bad. Trails that are slated to be incorporated into the plan should not just be allowed today, but encouraged.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/829/1*rX7FM1wl6CJ1P7mn-V8rGg.jpeg" /><figcaption>Analysis of the current trail system. Of the roughly 3 miles of trail, only 1.3 miles are not logging roads.</figcaption></figure><p>The C-2 trail is the first orphaned road to be partially adopted to a new trail. But instead of opening the new section and abandoning the unsustainable section, they closed the whole trail first. There was a run-off issue that was slowly working its way towards the logging road. But it wasn’t a dire situation, and should have been adaptively managed and re-routed.</p><p>Phase 2 is supposed to incorporate even more user-built trail and orphaned roads. But instead of closing down these trails first in the forest, we should encourage people to use these trails that are planned to be incorporated to keep them off of trails that DNR doesn’t plan to use. 17 miles of environmentally sustainable, user-built trail, were found at Reiter. There is no reason why we cannot start evaluating similar trails at Yacolt. While we wait to open up sustainable user-built trails, users are recreating on potentially unsustainable trails instead.</p><h3><strong>Waterfall vs Adaptive project management</strong></h3><p>Yacolt underwent a similar planning process as Reiter. The result has been a hardened path through the woods. For example, C1 was connected on both sides June 15th. However, until May 2nd 2015, no vehicle traffic was allowed on it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2eGPjk-FkkRFMOaJf8mV6Q.jpeg" /><figcaption>Taken July 2014, C-1 and C-2 was drivable. It could have been soft opened to test the soil.</figcaption></figure><p>Even with the hardening of the trail, DNR could, and should have opened it up July 1st. This would have allowed DNR to see the trail progression and make changes while it still had grant money. It would have also freed up time to start working on C-3 and C-4 trails.</p><p>Until Reiter, no trails were built entirely with excavators. Its a waste of time and runs counter to the idea of primitive 4x4 trails. Like Reiter, Yacolt is being built entirely from excavators. This means wide 8–10ft road beds, cleared tress, and any obstacles are man-built. The trail as it stands can be ran in 2wd by any vehicle with 6&quot; of clearance and shorter than 20&#39;.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aa_2BfdDif8MvhnXi6TnyA.jpeg" /><figcaption>New 4x4 Trail at Nicolai Mountain. Trail design focuses on strategic placement rather than rock. Agile method allows volunteers to harden areas that could lead to excessive erosion.</figcaption></figure><p>Volunteers should be primarily using their vehicles, chain saws, hand tools, and weed-whackers to establish trail. And this is what happens at other areas around the state and in Oregon.</p><p>When trails are built with vehicles and hand-tools, it allows nature to take them back, avoiding forest floor conversion. It also allows managers to redirect and abandon trails easier if they no longer are suitable. Why spend so much money on a trail when you don’t know its eventual outcome?</p><p>Walker Valley had a trail that was hardened over and over again in an attempt to keep the trail open. Eventually mother nature won when a washout obliterated the trail. Its not the appearance that matters, its the placement.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/604/1*pmyVEF_oSdA09RoItoB1rg.jpeg" /><figcaption>Hardening a trail at Walker Valley. It later closed in 2013 due to a washout. The original trail placement was bad.</figcaption></figure><h3><strong>Multiple Use = Not a 4x4 trail</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/562/1*w-vxQ82yPYWd16mo6dQYng.jpeg" /></figure><p>ATVs, Motorcycles, UTVs, and 4x4s all have different trail and tread requirements, as noted in the USFS trail standards guide. Unfortunately, DNR historically makes 4x4 trail the least common denominator. Not only are all other uses allowed, but must be designed for. This means that the 4x4 trails, cannot be made harder.</p><p>This lesson has been learned at Reiter. There, not only are 4x4 trails designed for 4x4s only, but also designated as such. No ATVs or Motorcycles are allowed on the 4x4 trails.</p><p>The new trails policy also helps clarify that trails can have PMOs that include designation of a particular use, which will help improve the 4x4 user experience.</p><h3>Heavy Equipment instead of vehicles</h3><h4>Lack of Volunteers</h4><p>When using heavy equipment <em>exclusively</em>, it limits the amount of work that can be done simultaneously by volunteers. This reduces the overall need, and drives volunteers away.</p><p>Because vehicles where banned from use during construction, all volunteers could do was hand grub or operate machinery. There were a few tasks around culverts and small rock placement, but not enough to get people excited to come work.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*oe9J7vTi0BIpaor1RcjHFA.jpeg" /><figcaption>A Single Excavator built most of the trail. These rocks were brought in and placed with excavators.</figcaption></figure><p>At Elbe and Walker, vehicles are used extensively in hauling and spreading rock, creating new routes, and winching in trees to close off old ones. At Walker, heavy equipment compliments vehicle use, used for specific spots. Elbe has its own dedicated mini, owned by DNR, and used by volunteers who are certified equipment operators. This builds trails faster and uses less resources, costing less money.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/798/1*5SwyrtopWaDsnJ4v5HlKCw.jpeg" /><figcaption>Buggy running a trail at Walker Valley, delivering rock to a DNR rented excavator operated by a certified volunteer.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lCJLkEFynKUdlObI5PIxyg.jpeg" /><figcaption>Logs are an effective way to water bar and define trail Rigs can also move them, which is much cheaper than heavy equipment. This trail at Reiter was ‘closed’ and still under construction.</figcaption></figure><p>Heavy equipment required removing large obstacles and water bars, then rebuilding them. Disturbed soil, even re-compacted, is not as good as naturally compacted soil.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-0ZyXkW63Wh2t7HKxh3fIQ.jpeg" /><figcaption>Image to the left has water bars that would require 4wd to traverse. Image to right is after water bars were largely flattened.</figcaption></figure><p>While I support the use of heavy equipment in specific areas, especially large rock placement, generally speaking they should be avoided for 4x4 areas. We’re specifically looking for a natural experience, and this really is best when using vehicles and hand/power tools.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Xx6xDcuuZxwWlsVvj42Flg.jpeg" /><figcaption>The initial cost to build this trail is low, and resources can be used to build up specific areas that need rock.</figcaption></figure><h3>Timber Sales and Logging Roads</h3><h4>Harvest trails vs wooded areas</h4><p>There are some advantages to building in harvested areas. There are no trees to disturb. Another harvest won’t happen in another 50 years. Some potential views. But there are also downsides; lack of a tightly defined trail, more water run-off/erosion, experience is not as beautiful. I personally like both, and hope that Yacolt will have more of a mixture of landscape.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*DBxRoQU7QLZVLUW4ejycTA.jpeg" /><figcaption>Trees at Elbe are high marked in Red for a timber sale. Despite the soil compaction here, there is no delivery to streams and the affect to the ecosystem is localized to the trail only (where we don’t want trees growing anyway!)</figcaption></figure><p>When building trail within a wooded area, the easier it is to build, the sooner the area will get logged. If we can create trails 1+ year before harvest and mark the stumps/trees, it will be easier to re-establish the trail after harvest.</p><h4>(Logging) Roads to Trails</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/795/1*9XZdFCbLnWdU4w6hsdYOiA.jpeg" /><figcaption>Humps and Bumps walker valley. Essentially a narrow logging road.</figcaption></figure><p>One of the more serious issues is converting logging roads to trails. The they aren’t rustic enough.</p><p>Roads also require all obstacles to be created. This increases cost and time. I support roads however for trunk and easier trails. But not all trails should be built on old roads and grades.</p><p>There is one benefit to using roads — stream crossings. It is cheaper to use existing roads or take over roads instead of building new bridges. And while its expensive to bring rock in, Reiter shows some successful strategies on building a difficult trail even on existing logging roads.</p><h3>Timeline and Funding</h3><p>Planning at Yacolt started before Reiter, but less has been accomplished since then. With 8 years of planning and over quarter million dollars spent, there was 3 miles of 4x4 trail added and 1.5 miles of new ATV trail.</p><ul><li>2007: Planning process started for Yacolt Burn Rec plan</li><li>2009 July: Planning process complete, plan goes to SEPA</li><li>2009 Fall: Hopeful to open up user-built trails to legitimate use</li><li>2010 August: DNR adopts the Yacolt Burn Rec Plan</li><li>2012: Things come to a halt.</li></ul><blockquote>The SEPA process is complete, public and agency comments have been responded to and we have received our final determination notice. The last piece of red tape we are waiting for is permits from Clark County. Originally, we were not going to need to go through the county, but since the Reiter area project raised such an uproar with the public, we were forced to pursue yet another layer of approval prior to moving forward with our project in the Yacolt Burn.</blockquote><ul><li>2013 Feb: DNR Receives a lawsuit from Gifford Pinchot Task Force on the behalf of a landowner who doesn’t want to see motorized recreation near her house.</li><li>2014 Spring: Lawsuit is settled and phase 1 ORV trails begin construction.</li><li>2014 November: C-1 and C-2 trails complete. C-3 and C-4 not done yet.</li><li>2015 Spring: Completion of C-3 and C-4 trails.</li><li>2016+: With current policies, this is the earliest any new 4x4 trail can be established.</li></ul><h3><strong>What can be done to fix this?</strong></h3><h4>Establish trails with users winter / spring 2016</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YcXhRNtNdqNa3ohRVLfkMg.jpeg" /></figure><p>This map shows a trail system that could be easily completed by the end of summer 2016. A good portion of the trail already exist, making these relatively easy to build.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aFTkQlqe7yp8QVaSkmk0mg.jpeg" /><figcaption>Flat, clear. It wouldn’t take much work to make this an interim parking lot.</figcaption></figure><p>A large bulldozer would be able to grade the abandoned road and reclaim rock for a temporary parking area. While its understood a grading permit would be required, the Clark County Permit office says this is relatively simple and quick to get.</p><p>Alternatively, since this area is planned to be a parking lot anyway, DNR could store its rock here for road maintenance and once the rock is used up, it’d become a de-facto parking area. This strategy has been used by other regions because it falls within forest practices guidelines and solves the problem of a temporary parking area.</p><h4>Other Improvements</h4><p>Scout and plan for more trails using the Mountain View (C1) trail as the trunk trail. There already is an abandoned section of road that could provide for some additional challenge. There is a leave tree section that could provide a tight and twisty area for vehicles. Have users establish the trail naturally, instead of constructing it.</p><p>Want to see the full proposal?<strong> </strong><a href="https://medium.com/@japerry/yacolt-burn-4x4-trails-2015-2016-d183f9cebc08"><strong>Check it out.</strong></a></p><h4>Write to DNR</h4><p>Tell them you want more public input on the Yacolt. Attend the every-other-month TAG meetings. Coordinate a group of friends to volunteer on a section of trail.</p><p>Share your comments and the blog with DNR:</p><p>Commissioner Goldmark: cpl@dnr.wa.gov<br>Lenny Young, Department Supervisor: <a href="/service/mailto:lenny.young@dnr.wa.gov">lenny.young@dnr.wa.gov</a><br>Eric Wisch, Region Manager: eric.wisch@dnr.wa.gov<br>Mary McDonald, Assistant Region Manager: <a href="/service/mailto:mary.mcdonald@dnr.wa.gov">mary.mcdonald@dnr.wa.gov</a><br>Rex Hapala, Recreation District Manager <a href="/service/mailto:rex.hapala@dnr.wa.gov">rex.hapala@dnr.wa.gov</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3346247bd84f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/dnr-trail-policy/reflections-on-yacolt-burn-4x4-trails-3346247bd84f">Reflections on Yacolt Burn 4x4 Trails</a> was originally published in <a href="https://medium.com/dnr-trail-policy">DNR Trail Policy</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Yacolt Burn 4x4 Trails 2015/2016]]></title>
            <link>https://medium.com/dnr-trail-policy/yacolt-burn-4x4-trails-2015-2016-d183f9cebc08?source=rss-c0f220e4a251------2</link>
            <guid isPermaLink="false">https://medium.com/p/d183f9cebc08</guid>
            <category><![CDATA[hiking]]></category>
            <category><![CDATA[travel]]></category>
            <dc:creator><![CDATA[Jakob Perry]]></dc:creator>
            <pubDate>Fri, 16 Oct 2015 17:26:04 GMT</pubDate>
            <atom:updated>2015-10-17T06:31:20.095Z</atom:updated>
            <content:encoded><![CDATA[<p>A plan to build new trail at low cost with volunteers</p><h4>Original Phase 1 — 4x4 Trails</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Rl3_p06y70Yj7uUoCBYswA.jpeg" /></figure><p>Of the phase 1 plan, only a small portion of trail was constructed:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*95K4BcOY7LED8X99Rm96Pw.jpeg" /></figure><p>Our proposal for trails the summer &amp; fall of 2015 is 2.65 miles of new 4x4 trail, .55 miles of new ATV trail, .55 miles of new single-track, and ~1 mile of decommissioned trail.</p><h4>Trail Decommissioning</h4><p>Last year, 4 miles of trail were decommissioned to motorized use. Another 2.67 miles of trail were decommissioned via the Lower Larch and West Hagen Creek timber sales. At least 6.67 miles of user-built trail and old grades were decommissioned in 2014.</p><p>For 2015, the plan is to decommission approximately 1.25 miles of trail. A timber sale planned for 2016 will decommission another 1 mile of trail. This will bring the total miles of decommissioned trail to almost 9 miles, where new built trail from Phase I will be around 7 miles.</p><h4>Blythe Settlement</h4><p>There are three specific areas that the Blythe Settlement calls out:</p><blockquote>1. DNR shall address the Plaintiffs’ concern for the Larch Mountain Trail regarding a portion of the proposed motorized trail providing access to the non-motorized trail near the L-1511 road by removing the portion of the trail that includes the intersection as depicted on the trail plan map.</blockquote><p>There currently exists a user-built trail that goes from the L-1511 road at the cell towers down to the proposed C-9 trail. With Blythe’s permission, we propose that the C-9 trail be constructed to the C-8 trail as proposed, create an access road to C-8 and C-9 trails from L-1511 and install a gate on the L-1511 road, depicted below. Additionally, we would decommission the user-built trail that extends from the L-1511 road to the proposed C-9 trail.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/953/1*kRk7HklryWwUIUr3n_Fg3Q.jpeg" /></figure><blockquote>2. DNR shall address the Plaintiffs’ concern involving the intersection or close proximity to the Tarbell (walking) Trail intersection with a proposed 4x4 trail by increasing the separation of these two trails to locate the walking trail out of the sightline of 4x4 trail. DNR shall move the walking trail downhill, as depicted on the trail plan.</blockquote><p>The area of concern previously had 4x4 trails using a section of user-built trail which intersected with the tarbell trail. This is no longer the case. A new logging road has been built south of the existing intersection, and rerouting the tarbell is most likely not needed anymore. However, an on-site survey is required, and it would be recommended to add woody debris to help delineate where the C-9 trail should be.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/983/1*cjRO3jbUyNgwBzTua3dtng.jpeg" /></figure><blockquote>3. DNR shall not construct, reconstruct, or utilize as part of the designated trail system the north-easternmost segment of the proposed trail near Hagen Creek depicted in red on the map and may relocate a trail length of an equivalent length (~ 1 Mile) in an alternate location outside the circle designated as Hagen Creek.</blockquote><p>In our proposal, the trails planned to be built below won’t occur until the West Hagen Creek timber sale is complete. However, in addition to the settlement, we propose re-allocating an additional .5 mile of trail to the 1 mile given up already. The trail to be traded is mentioned below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/946/1*R1ut6MVUdpDTRarEUlxxUw.jpeg" /></figure><h4>C-8 Trail</h4><p>The C-8 trail is in a recent harvest area. Approved by the Phase I SEPA and Clark County in 2013, this would be the first trail section to build. This area has no water crossings and would not require any heavy equipment to rough the trail in.</p><h4>C-9 Trail</h4><p>The C-9 trail is an old road grade that leads towards grouse vista. Much of this trail already exists. On-site ground surveying would need to occur to verify</p><h4>Blythe Settlement Trail</h4><p>There is an existing road grade that extends from the L-1511 Gate (being removed), past Arrowhead Pit, and down to 4-corners. We propose taking the 1.5 miles of trail from the Blythe Settlement and re-open this trail instead under RCW 79.10.500(2)(d).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*eoVJncfZvwPylK1iBc2VPA.jpeg" /><figcaption>While the trunk trail is not difficult, there are side opportunities for obstacles</figcaption></figure><p>The trail has no water crossings, is built on rocky soil, has water bars from previous abandonment, and has the potential for good natural side obstacles. This trail was last site surveyed on June 9th, 2015.</p><h4>L-1511 Gatekeeper</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/540/1*kQth-cnHNxrslLbwqpEJAg.jpeg" /></figure><p>To provide access to the C-8 and C-9 trails, a gate and gatekeeper should be installed near the gate extending past the Thrillium Trailhead.</p><p>This will allow only vehicles designed for the trails to travel the L-1511 Road.</p><p>Similarly, a gatekeeper of rocks should be added to both sides of the settlement trail.</p><h4>4 Corners Phase 1 Parking Lot</h4><p>There is a need for a temporary parking lot at 4 Corners. An existing road grade can be torn up for rock. Another 60–100 yards would be required to fill an area just under an acre. This would provide parking for around 30 vehicles and trailers. We understand that building an official parking lot is time consuming. Therefore, we propose that if there is a timber sale soon, that state lands stockpile their rock in this area. Other regions have done this under forest practices, which leaves an open gravel area once work is finished.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d183f9cebc08" width="1" height="1" alt=""><hr><p><a href="https://medium.com/dnr-trail-policy/yacolt-burn-4x4-trails-2015-2016-d183f9cebc08">Yacolt Burn 4x4 Trails 2015/2016</a> was originally published in <a href="https://medium.com/dnr-trail-policy">DNR Trail Policy</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Converting Playlists from Plug.dj -> Dubtrack.fm]]></title>
            <link>https://japerry.medium.com/converting-playlists-from-plug-dj-dubtrack-fm-fc62346cbba2?source=rss-c0f220e4a251------2</link>
            <guid isPermaLink="false">https://medium.com/p/fc62346cbba2</guid>
            <category><![CDATA[music]]></category>
            <dc:creator><![CDATA[Jakob Perry]]></dc:creator>
            <pubDate>Sat, 26 Sep 2015 07:58:08 GMT</pubDate>
            <atom:updated>2016-03-22T17:33:12.545Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-sa/4.0/</cc:license>
            <content:encoded><![CDATA[<p>Yes, sadly plug.dj’s days are numbered, and if you’re like me, you have thousands of songs in many different playlists. Luckily there is a way to save -all- of them!</p><p><strong>Note, stg.plug.dj is up for now, this process should work to get your tracks out of plug.</strong></p><h3>Getting your playlists from plug.dj</h3><p>First, go here to get the bookmarklet on plug.dj<br><a href="https://plugdj-playlist.appspot.com/bookmarklet.html">https://plugdj-playlist.appspot.com/bookmarklet.html</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Z3T_Byq7HMDH8gJEnS_jgg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*t5FFkCQ9oG79lnzkjn6RlQ.jpeg" /></figure><p>And thats it! Now you have a zip file of all music. Because Plug.dj is limited to 200 songs per playlist, you may have many of them. Unzip the file, which will give you a bunch of .pdj files, essentially JSON encoded text files.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9rLSFGFTTJ8iMMhErWxpZw.jpeg" /><figcaption>You’ll notice that if you used ‘/’ in the playlist title, they will show as folders. You should find the playlist inside them.</figcaption></figure><h3>Importing your tracks to Dubtrack.fm</h3><p>The import process is similar to the export process. First, get the bookmarklet to the importer:<br><a href="https://dubtrack-playlist.appspot.com/">https://dubtrack-playlist.appspot.com/</a></p><p>Once you have the bookmarklet, you can follow these instructions</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*A7USDAYXR6JqG2jD4cLOCA.jpeg" /></figure><p>Now, go back to the folder in which you unziped the playlists, and open one of the .pdj files up. Depending on your operating system, you may need to open up notepad or wordpad first, and find the file.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZfQoGDfcR-A5u8Cc007xxQ.jpeg" /></figure><p>Simply highlight everything and click copy, and go over the to popup on dubtrack and paste the text in. Make sure to give it a name (in this case I’m copying over Trance 3), and click import!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iTH1wL-ZRJZAdypeJNsJ7w.jpeg" /></figure><p>You should see an ‘importing XXX/YYY’ on the top of dubtrack.fm site and then a new playlist in your playlists!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZE236fRz62QT5AddOVoQ3A.jpeg" /></figure><p>And thats it! Rinse and repeat. And make sure you do it before Monday, or else you may lose your playlists!</p><p>❤ Moodance</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fc62346cbba2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ORV Diversity]]></title>
            <link>https://medium.com/dnr-trail-policy/orv-diversity-8218dc50b70e?source=rss-c0f220e4a251------2</link>
            <guid isPermaLink="false">https://medium.com/p/8218dc50b70e</guid>
            <dc:creator><![CDATA[Jakob Perry]]></dc:creator>
            <pubDate>Tue, 21 Oct 2014 08:45:58 GMT</pubDate>
            <atom:updated>2014-10-23T05:56:40.992Z</atom:updated>
            <content:encoded><![CDATA[<p>The USFS defines three types of Off-Road Vehicles:</p><ul><li>Motorcycle (single-track)</li><li>ATV (3 or 4 wheeled, under 50&quot;)</li><li>Jeep / Buggy (4 wheeled, over 50&quot;)</li></ul><p>But its much more diverse than that, and part of the issue we face with trails today are the inability to see the differences. Below are just some more types of ORV that need to be considered when planning trails standards and policies.</p><h3><strong>Trials bikes</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*YZGlso697Lj7U_ZCY7NxWQ.jpeg" /></figure><p>These are single-track small motorized bikes, a motorized BMX in some respects. They are highly maneuverable and have courses similar to rock buggies</p><h3><strong>Single-track Dirt Bikes</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*O7rOj6U53qyEhKNpwLzLpw.jpeg" /></figure><p>These are your typical dirt bike, built to be off-road and travel fast and through obstacles</p><h3><strong>Dual Use Dirt Bikes</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*hS0IEkyagLLY8XH55SpQQw.jpeg" /></figure><p>These are dual licensed as an on-road and off-road bike. Usually less equipped for hard trails and used on logging roads for speed</p><h3><strong>4x2 and 4x4 ATV</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*Ks_UPR-bBIiVDfczca5EuA.jpeg" /></figure><p>Used often for cross-country travel, fast trails, sand dunes, and some obstacles but less than what a dirt bike would encounter</p><h3><strong>4x4 UTV</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*iDPyepdcNTOUYFjDdet5pw.jpeg" /></figure><p>Larger than an ATV and prohibited on most ATV trails in Washington State. However, they have similar articulation, tires, and engines as ATVs and usually prefer less obstacles and more speed. Popular in sand and for hunting.</p><h3><strong>4x4 Small Wheelbase (Samurai / CJ5 / CJ7)</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*0hKKUmMe4sTQEXaFG4Hvkg.jpeg" /></figure><p>Skinny and short, these vehicles look for smaller obstacles and tighter trails (&lt;74&quot; width). They usually have between 31–37&quot; tires.</p><h3><strong>Modern Jeep / 4x4s (Lightly modified)</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*SpvE2L5uCMOCpob4I-r6WA.jpeg" /></figure><p>Jeep produces a Rubicon model with 32&quot; tires and lockers. Mainly used on logging roads and wider trails (90&quot;+) to reduce body damage. Popular with over-landing, camping, and snow wheeling. Other vehicles in this class include Jeep Cherokee, Toyota Truck/4runner, and other off-road vehicles with a 2&quot; lift and 31–33&quot; tires.</p><h3><strong>4x4 &amp; Truggies (Moderately modified)</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*4N2dIY2-IzsPF1evYfPbLQ.jpeg" /></figure><p>Highway registered vehicles that have been significantly modified with body armor, larger tires (35–39&quot;), lockers, and a winch. Truggies are 80s and early 90s Toyota trucks (and other makes of similar size) that have been partially upgraded to buggy style drive-train components. Also previously highway registered vehicles that have been converted to exclusive off-road use. Can be used on more difficult trails and some most difficult trails.</p><h3><strong>Rock Buggies</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*_OSRW3YW1_FQUvovlJhX_w.jpeg" /></figure><p>ORV registered (non-street legal) vehicles custom built for competition or most difficult trails. Can traverse almost vertical rocks, negotiate tight turns on trails (&lt; 74&quot;), but not usually intended for mud or snow, depending on the skin or tires on the vehicle.</p><p><strong>Full Size Trucks</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*5j3KFfZPSJbp8zc13fVM9w.jpeg" /></figure><p>Lightly lifted street legal vehicles. In the northwest, usually for snow runs and logging roads. Over 90&quot; width, and 33&quot;-38&quot; tires.</p><p><strong>Mud Trucks</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*oDyWvPyym4SqHkSX3mbWfg.jpeg" /></figure><p>Built for traversing deep mud holes, relatively rare in the Northwest due to trail width restrictions and lack of sanctioned mud pits. Large full size trucks on 40&quot;+ Tires and large engines. Over 95&quot; width.</p><h3>Comparison Table</h3><p>While your individual vehicle may vary from the class its usually in, this is historically a comparison table of where different equipment performs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qk9yi9JdrpuNpbKxQTi6nQ.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8218dc50b70e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/dnr-trail-policy/orv-diversity-8218dc50b70e">ORV Diversity</a> was originally published in <a href="https://medium.com/dnr-trail-policy">DNR Trail Policy</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[World Class Parks? We just want to recreate…]]></title>
            <link>https://medium.com/dnr-trail-policy/world-class-orv-parks-we-just-want-to-wheel-b47a143861ad?source=rss-c0f220e4a251------2</link>
            <guid isPermaLink="false">https://medium.com/p/b47a143861ad</guid>
            <dc:creator><![CDATA[Jakob Perry]]></dc:creator>
            <pubDate>Tue, 21 Oct 2014 08:45:45 GMT</pubDate>
            <atom:updated>2014-10-23T06:38:43.044Z</atom:updated>
            <content:encoded><![CDATA[<h2>World Class Parks? We just want to recreate</h2><p><em>“We want to transform Reiter into a World Class recreation area” — </em>Mark Mauren, Ex-DNR Recreation Manager</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/270/1*NWaKk8AjwdOKutdx7ApUvA.jpeg" /><figcaption>DNR Rocking the ATV trunk trail at Reiter Foothills</figcaption></figure><p>Whenever people talk about trails, be that Hiking, Mountain Biking, or ORV, I keep hearing the same generalization about maintenance and making trails bullet-proof.</p><p>But I submit here, not all trails are created or used equally, and making a general policy covering all trails to the same standard will only drive more groups underground.</p><p>We need policies that work with our trail building communities not against them.</p><h3><strong>If a 4x4 makes a mud hole in the middle of the forest and no one is around to see it, does the mud hole cause damage?</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*zbEt_5yl6axje-Aqf7PJ0w.jpeg" /><figcaption>One of many User-Built Trails since the closure of Reiter</figcaption></figure><p>When Reiter was closed in 2009, it was receiving nearly 1500 visitors per weekend, filling all three parking lots with trucks and trailers, and countless more street vehicles. Reiter <em>was </em>overused. Hikers wanted a trail nearby, the Audubon Society and City of Index were worried about water quality, and frankly the landscape wasn’t equipped to handle the amount of people frequenting it.</p><p>But wasn’t always like this.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*DNWGfj0tKdw_kWKze_6OZA.gif" /><figcaption><em>Map of the NW Region over 20 years, how ORV areas have been reduced to 1.5. Circles indicate the relative size of the area based on visits per year.</em></figcaption></figure><p>Before 2005, Reiter was relatively small, frequented mainly by locals (East Snohomish county residents) since the 1970s. There were many other options out there, much easier to get to. But as P-5000, North Fork, and 116th St closed, The options became Walker Valley and Reiter. Since Walker was primarily for Motorcycles and DNR was slow to work with, Reiter exploded in popularity and trails. This growth, coupled with the advancements in ORV technology, caused Reiter to become too large to ignore as a user-built trail system.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*mO8UdEZ_y91mHnfZ3b7o9A.jpeg" /><figcaption>The famous Reiter ‘damage’ photo by Karl Forsgaard. Interestingly, if the water is draining to the forest floor, and the trees were compensated for, is this really damage?</figcaption></figure><p>When Reiter closed, the relatively small Walker Valley saw immediate impact, and became its own mess, requiring more attention than ever to keep up with the new user base. However, even with the surge in use, its not as large as Reiter. Users were finally starting to develop their own areas. Two new secret locations along HWY2 were built, a new area in Whatcom County, two new trails in central Skagit, a new system near D<em>arrington. And those are the ones I know of. </em>It finally became easier to build new trails closer to home than to travel to Canada (for Rock crawling) or deal with lack of trail at Walker.</p><p><strong>Closing Reiter caused ORV impacts to be spread around the region.</strong></p><h3><strong>ORV users aren’t the only builders</strong></h3><p><a href="http://www.pinkbike.com/news/In-Good-Company-A-film-2012.html">Back in 2012, the ‘North Fork’ near Deming was closed down again</a>, due to concerns about unauthorized trail building by mountain bikers. Despite getting a 7–0 resolution from the county council, DNR largely ignored the negative effects of closing down this area.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F42655481&amp;url=http%3A%2F%2Fvimeo.com%2F42655481&amp;image=http%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F296004986_1280.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=vimeo" width="1280" height="720" frameborder="0" scrolling="no"><a href="https://medium.com/media/f4100d89ca35eed4626ab808df276fd1/href">https://medium.com/media/f4100d89ca35eed4626ab808df276fd1/href</a></iframe><p>Similar to the Reiter users, the mountain biking community started setting up new areas in Whatcom County. There are examples all over the state regarding new emerging recreation groups who cannot find a suitable existing place to recreate, and go make their own area.</p><h4>Hikers aren’t immune either</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*iv6Z3hGgG0ixlR07ACMmqA.jpeg" /><figcaption>A badly worn out section of the old mailbox peak trail. Credits: Hikingwithmybrother.com</figcaption></figure><p>Mailbox peak is the most recent hiker version of Reiter. <a href="http://seattletimes.com/html/localnews/2024637990_mailboxpeaknewtrail2xml.html">DNR just completed the process of re-routing the trail.</a></p><ul><li>Popular, exploding with growth.</li><li>Dangerous, with several search and rescue calls being made every year.</li><li>Looked environmentally unsustainable.</li></ul><p>But unlike Reiter, the old trail wasn’t closed when the new trail was open.</p><p>Mailbox peak is a good example of de-facto agile building. A trail was made, it got popular, and the trail was improved. With the new trail, its hoped that original trail can sustain itself. Interestingly, its not abandoned, despite the erosion and environmental issues. But if you look at the photo above, its mainly looks. Mailbox peak, just like mountain bike trails, and most ORV trails, look worse than they really are to the environment. ‘Bad looks’ should not be a criteria to close something down.</p><p>Its understandable that Washington Trails Association (WTA) is concerned about agile methods for building trails. To some, Mailbox peak is a ‘problem needing to be fixed’. To me, Mailbox peak is something awesome in need of preservation, and can do that by adding another easier option.</p><h3>User-built trails are the DNA of Washington’s trail system</h3><p>Did you know DNR had an open unless marked closed trail policy? Yes, while its illegal to build trail (<a href="http://app.leg.wa.gov/wac/default.aspx?cite=332-52-405">WAC 332–52–40</a>5), that trail is open for use as long as it has not been closed pursuant to <a href="http://app.leg.wa.gov/wac/default.aspx?cite=332-52-400">WAC 332–52–400(4)</a> or as long as its not behind a closed gate (<a href="http://app.leg.wa.gov/wac/default.aspx?cite=332-52-400">WAC 332–52–400(5</a>)).</p><p>Per DNR SEPA for Both Reiter and Yacolt Burn:</p><p><em>DNR’s proposed ORV trail system did consider the referenced recommendations when designing ORV trails on DNR-managed land. It is important to note that DNR’s Recreation Rules (WAC 332.52) state that roads and trails are open unless posted closed. DNR’s recreation rules were developed through a public process.</em></p><p>DNR’s Legal response to the GPTF’s lawsuit for Yacolt Phase I building:</p><p><em>“However, Plaintiffs’ specific request to close all motorized recreational trails unless posted open conflicts with a Board of Natural Resources’ policy and a Department rule based upon the statutory concept of allowing for multiple uses on public lands that allow motorized recreational use of trails unless posted closed.”</em></p><p>With over 2 million acres of uplands available and thousands of miles of open roads to explore, you can bet there are hundreds of user-built hiking, biking, ATV, and 4x4 trails out there.</p><h3>Size Matters.</h3><p>The WTA, with over 3 million dollars in assets, is an organization setup to plan, fund, and build trails from the top down. They have paid staff that can lobby the legislature. They have members who work for DNR. They have staff that can build a <a href="http://www.wta.org/about/2013-annual-report">pretty annual report.</a> They also have an order of magnitude more members than any other recreational group in the state.</p><p>No other groups come close. While WOHVA and PNW4WDA are the largest ORV groups in Washington, they are only a fraction of the size of WTA (.04% and 4% in net assets respectively). When you divide into local user groups, you find those building trails are groups of 5 to 30 people. They have no representation.</p><p>What might work for WTA may not be compatible with small niche groups.</p><h3><strong>HB-2151 can help build trails quicker, better, stronger.</strong></h3><p>Washington DNR was required by HB-2151 to create a trail policy. In that law, three criteria were created:</p><ol><li><em>Causes the least impact to the land.</em></li><li><em>Provides environmental and water quality protection.</em></li><li><em>Maintains the lowest maintenance and construction cost reasonable.</em></li></ol><p>DNR has been grouping ORV users into less area, which has created more impact to the land, water quality issues, and caused maintenance and construction costs to be unsustainable. We need to get back to dispersed recreation.</p><h3><strong>An agile plan to manage user-built trails</strong></h3><h4><em>Give user groups the ability to petition an area for limited use</em></h4><p>Many of the unauthorized areas currently in existence see less than 50 visitors a weekend, sometimes none at all. Why spend millions building a trail system for 50 people? Instead of trying to capture trail builders, work with them. Create an annual permit of $500-$2000, depending on desired use and miles of trail, that pays for yearly inspection and other administrative costs.<br><strong>By having small groups of users managing the lands and paying for permits, DNR reduces costs, disperses impact causing less impact to the land, and has regulatory oversight to maintain environmental and water quality protection.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/361/1*GgOPiLNkBLcuH2mtAGCIbg.jpeg" /><figcaption>Many trails are old road grades as seen here. They provide a good rock base for much of the trail mileage</figcaption></figure><h4><em>Create policy that puts responsibility in the user groups to not grow their area of limited use</em></h4><p>Prohibit groups from holding public events and don’t advertise the area as a managed recreation area in DNR materials. Agree upon a trail area based on acreage<strong> OR </strong>mileage, not both. Luckily, many of these user groups have specific types of trails that do not meet the needs of many, naturally limiting the amount of people willing to use the system.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/604/1*LOX_kFG5rW1sXODYEELJtQ.jpeg" /><figcaption>Natural Rock out-cropping suitable only for rock-buggies. This area would never be popular enough to warrant a managed system.</figcaption></figure><h4><em>Create statewide standards and annual inspections</em></h4><p>Having standards that user groups can use to make and maintain trails will help avoid environmental issues. By having DNR work with user groups, these potentially damaging trails can be mitigated.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*YXd29HeNfmMzk0rdYGuk9A.jpeg" /><figcaption>User groups consulting with DNR on a user-built bypass after a timber sale.</figcaption></figure><h4><em>Make these limited use areas pilots for larger recreation plans.</em></h4><p>Consistent with recreational immunity and the multiple use clauses in RCW, the trails must be publicly available for use, and eventually some limited use areas will become popular.<br>This is where creating a recreation plan make sense. By having groups already building trails to standards, DNR can adopt these trails per <a href="http://app.leg.wa.gov/rcw/default.aspx?cite=79.10.500">RCW 79.10.500(1)(d)</a> and improve where needed. By working on existing user-built trails, DNR doesn’t have to guess where the next plan needs to be.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/604/1*aEVcpWtvu7kft_Fv7eJSzA.jpeg" /><figcaption>Users working with hand tools and trucks, most trails do not need heavy equipment.</figcaption></figure><h4>More than the standard USFS type classes exist</h4><p>For ORVs, there are only ATVs, Motorcycles, and 4x4s defined. (<a href="https://medium.com/p/8218dc50b70e">See related article about more ORV classes</a>) Mtn Bikes and Hikers are the other categories, and don’t go into free-ride, cross country, etc. This is why its important to put decisions for trails into the hands of trail builders and not landscape architects. <strong>Unless the person/group building the trail has been involved with the respective recreation activity, they are not qualified to build or design a trail system.</strong></p><h4><em>Close areas that cannot stay in compliance</em></h4><p>Hold groups to the agreement they make with DNR, so any trail closures rest on them, and not DNR. Be proactive on user counts so if an area grows faster than a recreation plan can permit, trails can be converted easily without having to shut down the whole area.</p><h4>Be consistent.</h4><p>DNR needs to be consistent within regions and across user groups when giving access to groups requesting it. Personal bias has long been an issue within DNR, where we see different outcomes in the various regions. By having a fair and equal policy around user-built trails, DNR won’t have to deal with another Reiter or North Fork closure again.</p><p><strong>By working with user groups, DNR turns our best builders into assets instead of criminals, reduces the number of poorly designed trails around the state, and gives better metrics to when a DNR managed trail system is needed.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b47a143861ad" width="1" height="1" alt=""><hr><p><a href="https://medium.com/dnr-trail-policy/world-class-orv-parks-we-just-want-to-wheel-b47a143861ad">World Class Parks? We just want to recreate…</a> was originally published in <a href="https://medium.com/dnr-trail-policy">DNR Trail Policy</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>