On the American Discovery Trail (ADT) - Ohio & Kentucky, I know of camping/ lodging amenity gaps in the following places (both are hiking):
Mile 164.67
Ten Mile Per Day
The SE arm independent of the Buckeye Trail
Thru Hike and Ten Miler
In the area of Scioto Trail Section - Buckeye/ North Country/ American Discovery Trail, Point 09 of the current Buckeye Trail map & guide as of this date.
Previously, I wrote about camping/ lodging amenity gaps on the American Discovery trail in Delaware, Maryland and West Virginia. Sometimes, these can be fixed with a new private camp host that could be documented and obtained by the adventurist somehow, or the trail could be re-routed so that it brings the hiker 2 - 4 miles from the amenity depending on the terrain of where such a gap occurs?
All this could be handled by ADT's new state committees. It might be just one of their functions. But as of the date of this log, most them are very new. If you'd like to volunteer for one of these, you should contact the ADT state coordinator for the area your interested in. That directory is linked here.
As of today, this log's had 9,845 pageviews. 914 of those have been in the last 30 days.
This is the adventure and volunteerism log for Matthew Dexter Edmonds, aka "Treeman." Aside from Blogger comments, contact information is listed on Google+. And all places mentioned in this log are in the State of Ohio in United States of America unless otherwise stated. "The Wayne" = the Wayne NF.
Also, the motorhome mentioned is a 25ft, 1988 Itasca Sundancer, Model IF424RC with a Ford Econoline cutaway unless otherwise stated. It runs a 351 Windsor EFI V8 engine.
Search This Blog
Showing posts with label camping/ lodging amenity gap. Show all posts
Showing posts with label camping/ lodging amenity gap. Show all posts
2017/01/06
2017/01/05
Log 2017010501
The American Discovery Trail (ADT) - West Virginia is routed through the Cheat/ Potomac Ranger District of the Monongahela National Forest. Another NFS webpage lists Cheat and Potomac as having two different ranger districts.
I've been working with Google Earth and my ADT - WV GPS track. In the westbound direction for generally 10 mile per day hikers, beginning in Maryland at Segment 4 - Mi 164.67, there is an amenity gap for 66.82 total miles into West Virginia.
Assuming that the thru hike rate in this part of West Virginia is 15 miles per day, with amenity spurs no longer than 3mi, I work with a 3mi reserve, total daily output not to exceed 18.0 total miles, then I am aware of an amenity gap at this rate in the Keyser, WV area. But I'll be going off the bed soon and I might not get back to this project for weeks. That's unless somebody needs logistical assistance, then maybe sooner.
I've been working with Google Earth and my ADT - WV GPS track. In the westbound direction for generally 10 mile per day hikers, beginning in Maryland at Segment 4 - Mi 164.67, there is an amenity gap for 66.82 total miles into West Virginia.
Assuming that the thru hike rate in this part of West Virginia is 15 miles per day, with amenity spurs no longer than 3mi, I work with a 3mi reserve, total daily output not to exceed 18.0 total miles, then I am aware of an amenity gap at this rate in the Keyser, WV area. But I'll be going off the bed soon and I might not get back to this project for weeks. That's unless somebody needs logistical assistance, then maybe sooner.
2015/11/29
Log 2015112901
As I mentioned before, I plan to submit my 10 Mile Continuous Hikes Without Transit data to the Buckeye Trail Association (BTA). While I was routing through the Mogadore Section - Buckeye Trail (BT), I discovered I came along a camping/ lodging amenity gap in the Mantua of Portage County area. The problem was that I had never done a mock hiking route on this scale and without transit before, so taking into account where the last campsite/ lodging amenity was, how do I restart??? There's no rule for this and I have to be contentious of my criticism as this document may be scrutinized someday.
The other 10 mile document uses transit, so it's parameters are a little different. With the non-transit data, I'm going to re-start routing at the nearest public parking area prior to the first campsite if the mock hiker travels in the clockwise (CW) direction. The problem is that my parking area data still doesn't account for any road right-of-way widths yet. More precise parking areas could make a difference in determining the amenity gap's exact parameters.
These areas drive me crazy.
The other 10 mile document uses transit, so it's parameters are a little different. With the non-transit data, I'm going to re-start routing at the nearest public parking area prior to the first campsite if the mock hiker travels in the clockwise (CW) direction. The problem is that my parking area data still doesn't account for any road right-of-way widths yet. More precise parking areas could make a difference in determining the amenity gap's exact parameters.
These areas drive me crazy.
Subscribe to:
Posts (Atom)