I spent the day sewing trail patches on my straw cowboy hat. And I repaired a tear in one of my pair of jeans and put a replacement button on another. Right now, the weather report for tomorrow (Monday 04/20/2020) is showing 5 hours of favorable skies for geo photo cataloging the Road Fork Section, Points 26 - 25 (07/2011 BTA map) round trip. It's not as far as I'd like to go, but I can't just stop in the middle of a segment. They have to be photographed whole. But Wednesday is looking like I'll get another 5 hours, but on the Whipple Section? Points 03-W to 05 (10/2010 BTA map) have priority there. I need to see it anyways because I have yet to give it an unofficial, but special segment name.
The purpose of the catalog right now is volunteer procurement. As far as getting new trail adopters, group activities are suspended until further notice. We can get new trail adopters (our primary volunteer maintenance crew), but can't give them the necessary in-person indoctrination until COVID-19 restrictions are relaxed. To sum it up, we can still get them on the record, but not working yet. Anyways, we need those photos for an Adventurer's Project volunteer procurement/ trail promotion campaign that should be had sometime after the COVID-19 restrictions are lifted to a more favorable point.
I didn't jump on the bandwagon and advocate the use of the trail in our region because I thought it would precipitate a public health problem. When cataloged Whipple 06 - 05, it was it's usual, tranquil self out there. The nearest person was 150 yards away from me and they were across a river on a dirt bike.
Our photos for Road Fork 27 - 29 are done and that accounts for the popular Archer's Fork Loop concurrency where I think people are going to be? I've got a good lead on an adopter for Whipple 01 - 02.
New adopters or not, I want to upgrade all of Whipple's off-road blazes myself. It's just to get them up to the Maintenance Guide's recommended standards.
We have permission to move as many North Country Trail NFS tack on markers as needed to our road intersections. They're needed at the intersections because they're shapes and color are what's on NFS's maps. If they see the shapes at the intersections, then Buckeye's blazes can take over from there.
Showing posts with label road fork section. Show all posts
Showing posts with label road fork section. Show all posts
2020/04/19
2020/04/11
Geo Photo Catalog
It might be 9 days before I can continue Adventurer's Project's "Geo Photo Catalog." It has several applications.
Application #1: A photographic record of the trail to educate Buckeye Trail Association volunteers and a reference for future maintenance needs.
Application #2: Produce photos for trail adopter procurement.
Application #3: Social media content. The photos will be released about 3 at a time in between other posts and help with fresh content during the cold days.
Application #4: Photos for Adventurer's Project's website.
Application #5: Pictures for trail promotion and volunteer procurement.
Application #6: Determine where we need to take pictures with better cameras. Those photos can be used for trail promotion, the website and social media.
Adventurer's Project supports the Road Fork and Whipple Sections of the Buckeye Trail (North Country concurrent) in Noble, Monroe, Washington and Morgan Counties of Ohio. The photos are taken about every 50yds or less in both directions. Currently, the photos are being taken at my smartphone's highest possible quality. As this region's off-road total is about 40 miles, it should produce over 2,600 photos. That's far more than Buckeye and North Country's hikers have produced at the moment.
On-road portions have been recorded via video with spoken locations from an automobile. Aside from that, Google Street View covers some of this area. So at this point, it's mostly about photographing about 40 miles of off-road paths on foot. And I'm earning my 2020 North Country Trail 100 Mile Challenge, which I've missed other challenges like this in previous years.
The "geo" part pertains to enabling my smartphone camera's "locator" to produce geotags. This process embeds the location of where the photo was taken into the properties of the file. From there, software can be used to extract their coordinates and then embed them into placemarks into a Google KML/ KMZ file. In terms of the maintenance record, volunteer users can follow the photos, particularly with the GIS/ GPS track of the Road Fork and Whipple Sections. So, this is to see the trail's line with the photos on an application like Google Earth and probably ArcGIS products?
In previous years, the camera locator was on by default. But I like to refer to geotags as "creeper tags." It's unfortunate because people were physically followed by others when they downloaded their pictures and had the geotags extracted. They could tell by the days of the week when they took their kids to karate class for instance.
But recently, to enable the geotag feature, there are two safeties. One is that the phone's locator must be enabled. When it is, this is what enables the smartphone's mapping and navigation. The second step is to enable the locator a second time, but in the camera app's settings. I find it to be a wonderful tool for the trail, but I tend to use it wisely. As of the time of this post, geotags are automatically stripped by Facebook, but not by every social media company. Presently, Adventurer's Project is only on Facebook and no other social media service due to insufficient manpower to admin more.
At last count, it takes about 1 hour to photograph 2 miles of off-road footpath here in what I call "Far SE Ohio," which is in the Appalachian Foothills. That's that's about 4 times faster than it takes to initially blaze (painted navigational markers) one. But still, the "stop and go" is harder on my body and I haven't scheduled this photographing over 7 round trip miles yet.
So, that just about sums up Adventurer's Project's Geo Photo Catalog.
2019/08/18
Passing Up Tomorrow
I work with the weather forecast day by day when it comes to geo photo cataloging the Road Fork and Whipple Sections of the Buckeye Trail (North Country concurrent). For those of you just tuning in, those sections are in SE Ohio, generally east of I-77 and south of I-70 in Ohio. That's one reason why I like to call this region "Far SE Ohio."
I lead Adventurer's Project, which is an effort to try and create a new chapter of the Buckeye Trail Association. It supports these sections and this project is a part of our data collection, which could help in multiple ways.
But getting back to the weather, my camera devices can embed the coordinates of where the pictures are taken. But because these aren't being done with stronger, professional grade equipment, the conditions in the sky have to be good for a more accurate position.
I watch Weatherbug for skies predicted to be "partly sunny" or better. Tomorrow, we're expected to get lightning on the Road Fork Section, but the forecast for the Whipple Section reads sunny and hot. Unfortunately, my van is fuel inefficient, old and the Whipple Section is about a hour away. I'll have to overnight, but my tent needs repairs. I'm afraid I'll have to pass tomorrow up.
2019/08/14
Geo Photo Catalog, A Rough Year, Whole Circuit Challenge
The Geo Photo Catalog is a project for the Road Fork and Whipple Sections that I have already underway. It involves taking pictures with my smartphone and camera app's locators turned on. What does is it embeds the coordinates of where the picture was taken. The idea, is to take them at every blaze, or where they're supposed to be according to the BTA's maintenance guide lines. Because of the weakness of a smartphone's GPS antenna, they have to be taken when the sky is partly sunny or better. And on Weatherbug, there's a difference between "party cloudy" and "partly sunny."
It's multifaceted program as it's purposes are:
1) provide the Buckeye Trail Association with a visual record of the trail
2) provide pictures for a Vacant Segment Showcase
3) to provide Adventurer's Project and the chapter it may become photos to use on it's website and social media, particularly in the winter.
Adventurer's Project covers the Road Fork and Whipple Sections of the Buckeye Trail (North Country concurrent) in Far SE Ohio, or generally east of I-77 and south of I-70. Those sections are off-road at Caldwell Lake and in the Marietta Unit of the Wayne National Forest.
It's been a rough year. Where to start??? The project had about 5 presentations and the public only showed up at one of them. We have two volunteers ready to go, but with both there's some scheduling difficulties. We might have another?
I live in my motorhome in Woodsfield. In December, I started getting physical therapy on my back. That concluded in February, but my abdominals still need tensioned. What I've learned is that I'm not in as good of condition as I once thought and now I'm unable to make the 13 mile one way trip to the nearest off-road portion by way of bicycle because the hills in this county are too much to handle at this time.
The electric warming hose that I was using for water to my motorhome failed and my hot water tank ruptured in a cold snap in February. I had to get a motel for a couple nights, but this is when my car started acting up, The RPM's were jumping.
In April, I finally saved up to get my car's clutch replaced. I then added two bottles of "Guaranteed to Pass" in two tanks of gasoline to try and get the catalytic converters clean.. After the first one, it started to jump less. But part way through the second, I wasn't satisfied it was doing enough.
Sometime afterwards, I started to replace the entire exhaust because in the year prior, a mechanic told me that I was leaking oil and as it was dripping down the back side of the engine, that it could probably clog one of the catalytic converters? Since the header pipe at the engine was bad and it was all practically welded together by this point anyways, I felt it necessitated a full replacement from "stem to stern."
It didn't alleviate the RPM's jumping. I changed the oil valve gasket along with the exhaust, but that didn't do anything. There's got to be something else? Because then it wouldn't start.
I had it hauled to Hilltop Auto Services just outside of Woodsfield to perform a diagnostic. They came back and said that the timing chain had gone and as a result, the valves were warped and the pistons were probably gone as well?
At that point, there was somebody in town who wanted to make my HHR into a jacked up, four wheel drive "Baby Grave Digger." I paid for the tow truck from Hilltop to his house because it was a heck of a lot better than sending it 30 miles north to a junk yard. But on the other hand, he had a old Chevy conversion van that I bought for $800. It use to be a passenger van, but it's interior is stripped down. I only have two seats in it. And the passenger's side needs a seat belt, which is on order.
So, we're back up and running, but there's a few experiments to run with a rear wheel drive only, top heavy vehicle in The Wayne. Most of its parking opportunities occur in a grass strip on the side of narrow, gravel roads. But there's another reason to run these experiments...
The Buckeye Trail Association's board voted in the affirmative to have a "challenge" over the whole circuit in one weekend. Basically, the BTA needs to be able to park cars every 3 miles or less in order to have hikers cover such distances over the 1,454 mile circuit almost virtually simultaneously at once. Some of those vehicles could be RWD only's? I have to come up with the contingency procedures in case it rains and their wheels sink?
Right now, I have 600 - 800lbs over my rear axle. But I'll also be experimenting with a new arrangement of parking boards and a come-a-long, or hand winch. With FWD, I would just place a board under each tire when I park in these places. When I leave, I have about 2 seconds of thrust, the rest is momentum and that better get me out.
But with a rear wheel drive, the drive wheels are further back. So the experiment is to see if four boards placed perpendicular in front of the boards being parked on would be enough traction to make it out? My conversion van has one disadvantage that the HHR didn't and that's it's wheelbase. The HHR could come out of a road side parking place forward, or back, depending on what was more advantageous? The conversion van's wheel base is likely to be not as generous? It probably has to come out in the forward direction only because of how tight the treeline is to the edge of these grass strips? Without knowing more, that's merely speculation at this point.
We have different grass strips. Some are up hill, down hill and some are on flats. We have to anticipate that these vehicles could be parked over night? If so, will front reflectors be needed? And if so, what color?
It's multifaceted program as it's purposes are:
1) provide the Buckeye Trail Association with a visual record of the trail
2) provide pictures for a Vacant Segment Showcase
3) to provide Adventurer's Project and the chapter it may become photos to use on it's website and social media, particularly in the winter.
Adventurer's Project covers the Road Fork and Whipple Sections of the Buckeye Trail (North Country concurrent) in Far SE Ohio, or generally east of I-77 and south of I-70. Those sections are off-road at Caldwell Lake and in the Marietta Unit of the Wayne National Forest.
It's been a rough year. Where to start??? The project had about 5 presentations and the public only showed up at one of them. We have two volunteers ready to go, but with both there's some scheduling difficulties. We might have another?
I live in my motorhome in Woodsfield. In December, I started getting physical therapy on my back. That concluded in February, but my abdominals still need tensioned. What I've learned is that I'm not in as good of condition as I once thought and now I'm unable to make the 13 mile one way trip to the nearest off-road portion by way of bicycle because the hills in this county are too much to handle at this time.
The electric warming hose that I was using for water to my motorhome failed and my hot water tank ruptured in a cold snap in February. I had to get a motel for a couple nights, but this is when my car started acting up, The RPM's were jumping.
In April, I finally saved up to get my car's clutch replaced. I then added two bottles of "Guaranteed to Pass" in two tanks of gasoline to try and get the catalytic converters clean.. After the first one, it started to jump less. But part way through the second, I wasn't satisfied it was doing enough.
Sometime afterwards, I started to replace the entire exhaust because in the year prior, a mechanic told me that I was leaking oil and as it was dripping down the back side of the engine, that it could probably clog one of the catalytic converters? Since the header pipe at the engine was bad and it was all practically welded together by this point anyways, I felt it necessitated a full replacement from "stem to stern."
It didn't alleviate the RPM's jumping. I changed the oil valve gasket along with the exhaust, but that didn't do anything. There's got to be something else? Because then it wouldn't start.
I had it hauled to Hilltop Auto Services just outside of Woodsfield to perform a diagnostic. They came back and said that the timing chain had gone and as a result, the valves were warped and the pistons were probably gone as well?
At that point, there was somebody in town who wanted to make my HHR into a jacked up, four wheel drive "Baby Grave Digger." I paid for the tow truck from Hilltop to his house because it was a heck of a lot better than sending it 30 miles north to a junk yard. But on the other hand, he had a old Chevy conversion van that I bought for $800. It use to be a passenger van, but it's interior is stripped down. I only have two seats in it. And the passenger's side needs a seat belt, which is on order.
So, we're back up and running, but there's a few experiments to run with a rear wheel drive only, top heavy vehicle in The Wayne. Most of its parking opportunities occur in a grass strip on the side of narrow, gravel roads. But there's another reason to run these experiments...
The Buckeye Trail Association's board voted in the affirmative to have a "challenge" over the whole circuit in one weekend. Basically, the BTA needs to be able to park cars every 3 miles or less in order to have hikers cover such distances over the 1,454 mile circuit almost virtually simultaneously at once. Some of those vehicles could be RWD only's? I have to come up with the contingency procedures in case it rains and their wheels sink?
Right now, I have 600 - 800lbs over my rear axle. But I'll also be experimenting with a new arrangement of parking boards and a come-a-long, or hand winch. With FWD, I would just place a board under each tire when I park in these places. When I leave, I have about 2 seconds of thrust, the rest is momentum and that better get me out.
But with a rear wheel drive, the drive wheels are further back. So the experiment is to see if four boards placed perpendicular in front of the boards being parked on would be enough traction to make it out? My conversion van has one disadvantage that the HHR didn't and that's it's wheelbase. The HHR could come out of a road side parking place forward, or back, depending on what was more advantageous? The conversion van's wheel base is likely to be not as generous? It probably has to come out in the forward direction only because of how tight the treeline is to the edge of these grass strips? Without knowing more, that's merely speculation at this point.
We have different grass strips. Some are up hill, down hill and some are on flats. We have to anticipate that these vehicles could be parked over night? If so, will front reflectors be needed? And if so, what color?
2019/06/15
Tried to Move Road Fork/ Whipple Work Week, Dispersed Camping, Timeline, Failure
Three years ago, I was asked to request that the BTA move it's Road Fork/ Whipple Work Week back from July annually to June. I explained that this could be difficult because Buckeye only has one crew to spare for this region. We do it at the height of the growing season and that moving it back to June could entail the Buckeye Trail Association having to field a second crew.
Well, I did it. And all of those were concerns at the BTA, there was another. The BTA expanded to include more work weeks elsewhere. As a result, it was impossible to move Road Fork and Whipple's back. I'm not sure if the outside understands just how big the BT is? I'm certain that National Forest Service's view is deficient with it, however, that's not really their fault because this sort of data only resides currently on my computers.
They think that the forest has truly dispersed camping when it comes to distance hikers, but they're missing a number of factors. They have to do with the balance between Buckeye's very fixed amenities, the terrain in the Marietta Unit and the intent of the hikers, which influences where they disperse camp. And I think that there are these unauthorized campsites on wonderful terrain because the hikers over the decades independently reached the same conclusion and that's what cased them to be well impacted?
The Hiker Hurricane was about 2 years ago (I think). The three year plan for this region entailed stabilizing the Whipple Section. That was done. The second year was supposed to be for maintenance and using my section supervisor credentials to improve the trail adoption numbers for it. But Year 2 was a dud. I'm a Disabled Vet. When my housing situation hit the fan in Year 1, I withdrew back to Painesville. In May of Year 2, I purchased a 29 year old motorhome. But it's expenses and mechanical needs exceeded my abilities. The hiker hurricane hit that year. In Year 3, I can't remember what happened then? But in the winter, my family has a mechanic friend and we spent 4 months working on the motorhome and got me in Far SE Ohio on May 7th. I've been here ever since.
While I was having difficulties, there are certain people who I don't entirely trust around both within and without. And sometimes, some in the BTA can be impressionable to failure. With exceptions, I kept my whereabouts a secret for the most part.
Well, I did it. And all of those were concerns at the BTA, there was another. The BTA expanded to include more work weeks elsewhere. As a result, it was impossible to move Road Fork and Whipple's back. I'm not sure if the outside understands just how big the BT is? I'm certain that National Forest Service's view is deficient with it, however, that's not really their fault because this sort of data only resides currently on my computers.
They think that the forest has truly dispersed camping when it comes to distance hikers, but they're missing a number of factors. They have to do with the balance between Buckeye's very fixed amenities, the terrain in the Marietta Unit and the intent of the hikers, which influences where they disperse camp. And I think that there are these unauthorized campsites on wonderful terrain because the hikers over the decades independently reached the same conclusion and that's what cased them to be well impacted?
The Hiker Hurricane was about 2 years ago (I think). The three year plan for this region entailed stabilizing the Whipple Section. That was done. The second year was supposed to be for maintenance and using my section supervisor credentials to improve the trail adoption numbers for it. But Year 2 was a dud. I'm a Disabled Vet. When my housing situation hit the fan in Year 1, I withdrew back to Painesville. In May of Year 2, I purchased a 29 year old motorhome. But it's expenses and mechanical needs exceeded my abilities. The hiker hurricane hit that year. In Year 3, I can't remember what happened then? But in the winter, my family has a mechanic friend and we spent 4 months working on the motorhome and got me in Far SE Ohio on May 7th. I've been here ever since.
While I was having difficulties, there are certain people who I don't entirely trust around both within and without. And sometimes, some in the BTA can be impressionable to failure. With exceptions, I kept my whereabouts a secret for the most part.
2018/12/26
Website Upgrades 12/26/2018
Campground & lodging mileage from the establishment to the trail was added yesterday. Adventurer's Project's "Hiker Resources" web page had to be practically rebuilt to handle it. Today, I added a mileage chart of the Road Fork and Whipple Section - Buckeye (off-road)/ North Country National Scenic Trail. I won't touch the on-road, but that's much easier to use the "measurement" tool in the BTA's digital mapping on Avenza Maps there.
A link to my Generic Gear Inventory was created on the Hiker Resources web page.
A link to my Generic Gear Inventory was created on the Hiker Resources web page.
2018/10/25
Adventurer's Project's Social Media and USGS Hydrographic GIS Data
I might like to get Adventurer's Project on multiple forms of social media, but we're a little short handed at this point. Many of the posts that I write to its Facebook exceed 280 characters, so, they're not really compatible with each other. But one day, it might be good to diversify our communications over several social media platforms in the event the Facebook goes terminal.
I'm working with the hydrography data for the Road Fork and Whipple Sections - Buckeye/ North Country Trail now. They all came unlabeled from the USGS, but I have the bigger streams along the trail renamed. Unfortunately, somehow, either I or Google Earth stripped its embedded information? Now, I can't tell if the remaining streams are creeks, runs or just some finger in the tree of these watersheds? I'll have to get a new copy of from USGS and try to overlay what I have named and go on from there.
The data needs to be reorganized and merged because that which is issued by USGS it's too demanding on computer systems. And the LoMaps on my Locus Maps apps doesn't display much in the way of hydrogrqphy.
- The Whipple Section approximate to Point 07 (10/2010 map & guide) is 9.73 miles north of the Ohio River on the Little Muskingum River.
- The Little Muskingum River Flats between Whipple Section, Points 05 - 06 falls between miles 12.5 to 13.61 from the Ohip River.
The Road Fork Section between Points 20 - 22 (7/2011 map & guide) is along the Little Muskingum R between Miles 38.87 to 41.02 from the Ohio River.
- The upload of mostly surface streams along the Road Fork and Whipple Sections to the Locus Maps app on my smartphone and tablet is complete. This project has been sitting around in Google Earth for months
2018/08/23
Back Problems 08/23/2018
My back is still giving me problems. This time, I didn't wake up with the pain. I went grocery shopping yesterday and forgot to get some Tylenol. Now, that's going to have to wait about a week. I have to get into a stretching routine twice daily because my issues are muscle related going back to the Night From Hell
The problem from back then was I had no choice but to push myself way beyond my design parameters that day. I wouldn't have ordinarily done this without sufficient testing of my abilities. By way of testing back then, I was only rated for an absolute maximum of 32 miles in one day on flat terrain.
The first test was on a loop using a portion of the Pemberville Section - Buckeye Trail. That was 31 miles in 10 hours, 04 minutes and 28 seconds. I then had to notch it up to 32 when I was on the International Appalachian Trail - Newfoundland and Labrador when I had to make a regional bus stop on time. Normally, I hiked in the ball park of 20 mile days.
On the Night From Hell, I prepositioned my bicycle and scheduled a 24 mile day hiking. The bike ride back was supposed to be about 12 miles. I started late and my hike took me past dusk. Road Fork Section - Buckeye Trail (North Country concurrent, during that time) wasn't maintained well and I didn't trust it. I've had plenty of off-road night hiking experience. And at night, it's slower. There's also optical illusions out there. Even the most powerful flashlights can't display certain depths right (like inside of a rut).
I executed two contingencies that evening that added mileage on foot. For me, it works out to be 1:2 or 3 in hilly terrain and 1:4 on flat terrain. The rear rim on the bike was so out of true that I couldn't ride it much more, so I had to walk it on-foot for about 6 miles. The bike has a drivetrain that spreads out the load on a person's stamina. In total, it turned out to be a 54 mile day, 44 of those were on-foot.
The problem from back then was I had no choice but to push myself way beyond my design parameters that day. I wouldn't have ordinarily done this without sufficient testing of my abilities. By way of testing back then, I was only rated for an absolute maximum of 32 miles in one day on flat terrain.
The first test was on a loop using a portion of the Pemberville Section - Buckeye Trail. That was 31 miles in 10 hours, 04 minutes and 28 seconds. I then had to notch it up to 32 when I was on the International Appalachian Trail - Newfoundland and Labrador when I had to make a regional bus stop on time. Normally, I hiked in the ball park of 20 mile days.
On the Night From Hell, I prepositioned my bicycle and scheduled a 24 mile day hiking. The bike ride back was supposed to be about 12 miles. I started late and my hike took me past dusk. Road Fork Section - Buckeye Trail (North Country concurrent, during that time) wasn't maintained well and I didn't trust it. I've had plenty of off-road night hiking experience. And at night, it's slower. There's also optical illusions out there. Even the most powerful flashlights can't display certain depths right (like inside of a rut).
I executed two contingencies that evening that added mileage on foot. For me, it works out to be 1:2 or 3 in hilly terrain and 1:4 on flat terrain. The rear rim on the bike was so out of true that I couldn't ride it much more, so I had to walk it on-foot for about 6 miles. The bike has a drivetrain that spreads out the load on a person's stamina. In total, it turned out to be a 54 mile day, 44 of those were on-foot.
2018/08/17
Lightning, Event Rescheduled
The Trail Maintenance Day at the Ring Mill in the Marietta Unit of The Wayne (National Forest) in Monroe County, to take place on the Road Fork Section - Buckeye Trail (North Country National Scenic Trail concurrent), Points 21 - 23 that was scheduled for tomorrow (Saturday, August 18th, 2018) has been rescheduled to Saturday, September 1st, 2018 due to lightning in the forecast.
2018/07/21
Great Blue Heron and Rest Day
I saw a Great Blue Heron in the Little Muskingum River Flats on the Whipple Section - Buckeye Trail (North Countey current) yesterday. It was truly a surprise. It's my favorite bird in Ohio because it's so solitary most of the time.
I was down there weed whacking about half of the flat's 1.1 miles. Between that and weed whacking places that are impossible for the DR Mower to reach, I had to take a day off today. Yesterday when I got out of the car to meet the Road Fork/ Whipple Work Week crew, I was light headed and felt a surge to my brain like none before. I didnt eat lunch on both days, so I was probably having low blood sugar mixed with fatigue. Now, I know better.
Those flats once took a crew of 4 about 40 man hours to weed whack. I got half it done in about 6. I'm 6'6 and I think that my swing and the disposition of my weed whacked engine have something to do with it?
2018/07/11
I Know How to Work the Weed Whacker Now
I found out how to work my weed whacker. From reports, most aperatures on the Road Fork and Whipple Sections should be clear now. I did this by car, so there were two aperatures that I couldn't access. Those will have to get done when the DR Mowers, or weed whacker sweep through.
2018/03/24
Trail Manual - Mileage Sheets
Let's recap... I've been writing a mileage sheet for a book that I wish to deploy at two shelters on The Wilderness Loop - Buckeye Trail (North Country partially concurrent). Parts of the book are location specific, including the mileage sheets. The mileage sheets are based on the mile markers that I have for the Buckeye and North Country Trails. They were derived from the merged tracks that I have for them, but accumulative mileages have never been tabulated until I started this project.
There may be inaccuracies in what I'm writing in the books. This thing might need a disclaimer? That's because when North Country chapter spans are larger than 99.9 miles, Google Earth's measurements tab rounds up or down to the nearest whole number. What I wish I would have done was converted them to inches, use a calculator and divide by 63,360 to get the mileages for each section with a decimal place in the ten thousandths.
The first thing that I do on a project like this is accumulate the mileage from one section terminator to another from one of the shelter until the both trails are completed. Then for the mileage sheet, it lists villages, cities and other locations. Having the terminator measurements makes it easier to use the section's mile markers. Mine are done every tenth of a mile. But if I had to do it over again, I'd have them made to every hundredth. I just added, or subtracted (depending on the direction I was working on) the locations mileage to the last reported terminator.
I've worked on the book's minor differences for the Road Fork On-Road Shelter. I found that there are some mileages that I forgot to fill in and I really don't know why? And I'm pretty satisfied that the numbers are in for the other shelter now.
So here's how updating it goes. We don't have the volunteers in Far SE Ohio to stay up with Buckeye and North Country Trails "around the clock..." it's quite impossible right now. Any corrections will have to be done during the cold days when we don't have any maintenance, or trail promotion. Additionally, the roads to access those shelters may be impassable to anything other than 4WD vehicles and we may not be able to issue the books new corrections until the snow thaws and exposes the gravel road surfaces?
But in the end, the hikers can reference these sheets and the next day, they can write their fans and support that they're a certain distance from somewhere, perhaps their ultimate destination? I know Buckeye thru hikers and I believe that they would spend a few minutes studying this sheet?
There may be inaccuracies in what I'm writing in the books. This thing might need a disclaimer? That's because when North Country chapter spans are larger than 99.9 miles, Google Earth's measurements tab rounds up or down to the nearest whole number. What I wish I would have done was converted them to inches, use a calculator and divide by 63,360 to get the mileages for each section with a decimal place in the ten thousandths.
The first thing that I do on a project like this is accumulate the mileage from one section terminator to another from one of the shelter until the both trails are completed. Then for the mileage sheet, it lists villages, cities and other locations. Having the terminator measurements makes it easier to use the section's mile markers. Mine are done every tenth of a mile. But if I had to do it over again, I'd have them made to every hundredth. I just added, or subtracted (depending on the direction I was working on) the locations mileage to the last reported terminator.
I've worked on the book's minor differences for the Road Fork On-Road Shelter. I found that there are some mileages that I forgot to fill in and I really don't know why? And I'm pretty satisfied that the numbers are in for the other shelter now.
So here's how updating it goes. We don't have the volunteers in Far SE Ohio to stay up with Buckeye and North Country Trails "around the clock..." it's quite impossible right now. Any corrections will have to be done during the cold days when we don't have any maintenance, or trail promotion. Additionally, the roads to access those shelters may be impassable to anything other than 4WD vehicles and we may not be able to issue the books new corrections until the snow thaws and exposes the gravel road surfaces?
But in the end, the hikers can reference these sheets and the next day, they can write their fans and support that they're a certain distance from somewhere, perhaps their ultimate destination? I know Buckeye thru hikers and I believe that they would spend a few minutes studying this sheet?
2018/03/22
Milages from the Other Shelter
When I wrote that I had the mileages from The Wilderness Loop done, I discovered that I was incorrect. The mileages for the BT and NCT both away from the loop and beyond are done for the Road Fork On-Road Shelter. This is on the north side of the Today, I was working on doing them from the Jay Stout Shelter, which is on the other side of the loop.
2018/03/20
Trail Manual for RF On-Road Shelter Complete
The trail manual for the Road Fork Section - Buckeye Trail's (North Country concurrent) on-road shelter is written. I now have to compute the mileages from the Stout Shelter on the west end of The Wilderness Loop for various locations around it, the rest of the Buckeye and North Country Trails.
2018/03/11
Highway Mile Markers, Roadside Camping, Caldwell Lake
I just got done writing tracks and getting mile markers for the various state highways on the Road Fork and Whipple Sections - Buckeye Trail (North Country concurrent). I think I remember someone saying that the mile markers on the ground aren't exact, but I think that having a ballpark estimate would help with overlaying Ohio Department of Transportation (ODOT) maps for locations near the trail.
I just crashed Google Earth moving items from Whipple's maintenance folder to Adventurer's project. For you folks who are not familiar with advanced GPS mapping, that means that that folder is very big. Then I did it again, I took my hands off of the keyboard, trackball, waited and again Google Earth crashed. Since this application doesn't have a multiple select option, I had to move the items over one at a time.
-Roadside camping in The Wayne is permitted according to https://www.fs.usda.gov/Internet/FSE_DOCUMENTS/stelprdb5068388.pdf. It's being grouped in with dispersed camping under the heading "Primitive Camping." And the advisory concerning the surface streams is in this document.
- I now have a property polygon (shape) for Caldwell Lake on the Road Fork Section. Trail building there is scheduled for October and camping anytime is not permitted there.
I just crashed Google Earth moving items from Whipple's maintenance folder to Adventurer's project. For you folks who are not familiar with advanced GPS mapping, that means that that folder is very big. Then I did it again, I took my hands off of the keyboard, trackball, waited and again Google Earth crashed. Since this application doesn't have a multiple select option, I had to move the items over one at a time.
-Roadside camping in The Wayne is permitted according to https://www.fs.usda.gov/Internet/FSE_DOCUMENTS/stelprdb5068388.pdf. It's being grouped in with dispersed camping under the heading "Primitive Camping." And the advisory concerning the surface streams is in this document.
- I now have a property polygon (shape) for Caldwell Lake on the Road Fork Section. Trail building there is scheduled for October and camping anytime is not permitted there.
2018/02/22
NOAA - NWS Hydrographic Data
Adventurer's Project's website remains a "works in progress" and is not published yet. But I continue to add things to it. The most recent thing is that I found how to get access to data submitted from five Hydrographic charts from the NOAA - National Weather Service. I'm linking them for the following stations:
- Ohio River at Marietta Pump House
- Duck Creek Near Whipple (approx 320ft W of the Whipple Section between Pts. 11 & 12)
- Duck Creek at Macksburg
- Little Muskingum (River) at Bloomfield [3.8mi NE of Road Fork Section, Point 26 (07/2011 Map & Guide)]
- Muskingum River at Beverly [7.2mi S of Whipple Section, Pt. 22 (10/2010 map & guide]
The Marietta Pump House give a good baseline understanding of what's going on in the area as far as water level is concerned. The station near Whipple might determine in BT's clockwise direction if Whipple 13 is under water?
The station at Macksburg is roughly at 672ft elevation. The ODNR Dam at Whipple 15 is south of that at 644ft. They are approximately 6.82 miles apart from each other. What level would the water on the Duck Creek on Macksburg's hydrograph have to be in order to flood over the ONDR dam near Whipple 15 that is only 3 feet above normal the level of the creek in that location? If we can determine this, then it could alert the hikers traveling in the counter clockwise direction that they'll be on "Dry Boot By-pass," instead of crossing the Duck Creek near Whipple 15 on the concrete ODNR dam.
The Little Muskingum (River) at Bloomfield station could alert hikers that the Road Fork Section near the Ring Mill might be under water? For out of town hikers, this is the kind of information that they would need in order to know whether they should drive at distance to traverse the area. And the Muskingum River at Beverly's levels might somehow indicate the creek and stream levels between Whipple 21 - 23. This area is on higher terrain, but those creeks and streams could bloat? And one of the roads there can have large holes in it?
I have the flood stage data for these stations. But in order to make it a custom fit for these sections, I think that digital photographs are the way to go. They have a time stamp embedded in them that can be accessed with the stock Windows Explorer in Microsoft Windows. If I could roam the area on a very rainy week, take pictures then compare their times to the ones stated in the hydrographs, then I may be able to say based on the Duck Creek in Macksburg's normal level (for instance), that if the hydrograph shows the creek at a certain level, then the Dry Boot By-pass is definitely in effect and we can spare the hiker from having to hike 2.9 miles down to find out, then 2.9 miles back.
- Ohio River at Marietta Pump House
- Duck Creek Near Whipple (approx 320ft W of the Whipple Section between Pts. 11 & 12)
- Duck Creek at Macksburg
- Little Muskingum (River) at Bloomfield [3.8mi NE of Road Fork Section, Point 26 (07/2011 Map & Guide)]
- Muskingum River at Beverly [7.2mi S of Whipple Section, Pt. 22 (10/2010 map & guide]
The Marietta Pump House give a good baseline understanding of what's going on in the area as far as water level is concerned. The station near Whipple might determine in BT's clockwise direction if Whipple 13 is under water?
The station at Macksburg is roughly at 672ft elevation. The ODNR Dam at Whipple 15 is south of that at 644ft. They are approximately 6.82 miles apart from each other. What level would the water on the Duck Creek on Macksburg's hydrograph have to be in order to flood over the ONDR dam near Whipple 15 that is only 3 feet above normal the level of the creek in that location? If we can determine this, then it could alert the hikers traveling in the counter clockwise direction that they'll be on "Dry Boot By-pass," instead of crossing the Duck Creek near Whipple 15 on the concrete ODNR dam.
The Little Muskingum (River) at Bloomfield station could alert hikers that the Road Fork Section near the Ring Mill might be under water? For out of town hikers, this is the kind of information that they would need in order to know whether they should drive at distance to traverse the area. And the Muskingum River at Beverly's levels might somehow indicate the creek and stream levels between Whipple 21 - 23. This area is on higher terrain, but those creeks and streams could bloat? And one of the roads there can have large holes in it?
I have the flood stage data for these stations. But in order to make it a custom fit for these sections, I think that digital photographs are the way to go. They have a time stamp embedded in them that can be accessed with the stock Windows Explorer in Microsoft Windows. If I could roam the area on a very rainy week, take pictures then compare their times to the ones stated in the hydrographs, then I may be able to say based on the Duck Creek in Macksburg's normal level (for instance), that if the hydrograph shows the creek at a certain level, then the Dry Boot By-pass is definitely in effect and we can spare the hiker from having to hike 2.9 miles down to find out, then 2.9 miles back.
2018/02/21
Discount Gas Map
On my end personally, the scenario is that I could be at the Ring Mill Campground, which is at the northern terminator of the Road Fork Section's off-road trail... low on gas. Well, at last count, the motorhome gets 8 MPG with a 38 gallon fuel cell capacity. The nearest gas station from there is about 10 miles away. And the nearest town takes over 20 minutes to get to.
But, I've made an off-line GPS map covering my Speedway Rewards, MySheetz, Giant Eagle Advantage (GetGo) and Plenti (Exxon/ Mobil). But then I got to thinking that Adventurer's Project is coming along and it could use the traffic, so I did all this for the entire State of Ohio (and some). Right now, my Speedway Rewards points are up over 50,000. $0.50 off per gallon is about 8.750 points for a maximum of 15 gallons. The last time that I did this, they're computer system wouldn't let me get free gas and I ended up paying $0.08 a gallon. And at 15 gallons, that's a nearly free 39% of the motorhome's tank.
But, I've made an off-line GPS map covering my Speedway Rewards, MySheetz, Giant Eagle Advantage (GetGo) and Plenti (Exxon/ Mobil). But then I got to thinking that Adventurer's Project is coming along and it could use the traffic, so I did all this for the entire State of Ohio (and some). Right now, my Speedway Rewards points are up over 50,000. $0.50 off per gallon is about 8.750 points for a maximum of 15 gallons. The last time that I did this, they're computer system wouldn't let me get free gas and I ended up paying $0.08 a gallon. And at 15 gallons, that's a nearly free 39% of the motorhome's tank.
2018/01/02
Early Warning System
I've always been good at the BT's maps, it's fixed amenities and generally anticipating where multi-day hikers will be next? So, I've made a map based on an entry level thru hiker's abilities depicting where they'd most likely be 10 days out from the The Wilderness Loop in both directions. And since the Road Fork and Whipple Sections are both North Country Trail (NCT) concurrent, 10 days out had to be tracked on the Great Trail Sandy Beaver Chapter span of that trail when it's independent in NE Ohio.
For my North Country mock hike written simulation, one of the next steps is to devise some mile markers based on campsites, campgrounds, lodging, or the intersections to these. I had to get Great Trail Sandy Beaver's started for what I'm calling my "Early Warning System."
There are ways that I can track a thru hiker. One is that I can follow them on Facebook. Two is that if I get their cell numbers, we can text. Three is that they let me follow their location somehow. The Maps app (which is Google Maps) lets users do this. The early warning map is on Google Earth and is more of a quick reference.
If they're more powerful than entry level thru hikers, I can still anticipate their arrival, it's just done on the pattern of their daily progress instead. That would still give me some idea. This was done for Adventurer's Project and a chapter that may come of it.
For my North Country mock hike written simulation, one of the next steps is to devise some mile markers based on campsites, campgrounds, lodging, or the intersections to these. I had to get Great Trail Sandy Beaver's started for what I'm calling my "Early Warning System."
There are ways that I can track a thru hiker. One is that I can follow them on Facebook. Two is that if I get their cell numbers, we can text. Three is that they let me follow their location somehow. The Maps app (which is Google Maps) lets users do this. The early warning map is on Google Earth and is more of a quick reference.
If they're more powerful than entry level thru hikers, I can still anticipate their arrival, it's just done on the pattern of their daily progress instead. That would still give me some idea. This was done for Adventurer's Project and a chapter that may come of it.
Subscribe to:
Posts (Atom)