My tracks for the Superior Hiking Trail is in four parts. And I've never gotten the whole thing to merge with an elevation profile. That concurrency is about 268 miles. My Finger Lakes Trail track is merged together, but Google Earth's elevation profile won't read about 100 miles of what it reports as it's length in Rt Click-> Properties-> Measurements. Normally, I don't like to merge anything larger than about 120 miles long because Google Earth is more prone to errors.
He installed the new Bluetooth stereo and got started on the new CB with weatherband radio. Looks like I'm going to have a 19 gallon fuel cell, sending unit and rear in-tank pump to sell on ebay now that he got my 38 gallon stuff working.
I think that we're going to spend most of February doing the interior? I've gone in and out of state parks in the past, so I'm wondering if I should mount some Wi-Fi antennas? I've already got unlimited data on Verizon and it can hotspot to the laptop when needed. But the Wi-Fi might have better reception?
I'd like tile to be put in instead of carpet in case I come back from the trail muddy. Due to water damage, the seams will have to be resealed and the walls will have to be rebuilt.
- ArcGIS Explorer has been discontinued, but I just downloaded ArcGIS Earth on the my laptop. I don't know it's capabilities yet.
- The motorhome's new CB is powered up and one antenna mast is mounted. I just purchased another new mast, splitter cable and 2 more mounts. I also got some more
-Middlebury Land Trust and the Green Mountain Club's NCT route in Vermont mile markers have been re-labeled with their respective mileages.
- Central New York Chapter, an at-large section and Adirondack Mountain Club's mile markers have been re-labeled with their mileages. I'm about 43% done with NCT NYS. Right now, my single track for North Country's concurrency on the Finger Lakes Trail is about 425 miles long. It's the biggest track that I have on record (for any trail). From the way it looks, it has a lot of markers because of how often it comes in and out of dispersed camping. Markers pertaining to dispersed camping are laid at the beginning and end of continuous parcels where it's permitted. I wish I had a solid 6 hours to commit to them, but something tells me that I'll have to do them over a couple of days. I prefer going straight through and finish whole chapter/ partners/ affiliates. But I'm feeling good about getting the Adirondack Mountain Club done.
So far in addition to what I've stated, I've got mile markers from the North Country Trail Association for North Dakota and Michigan. The mile markers are complete for Ohio, including the Buckeye Trail now. That leaves the Finger Lakes concurrency, Minnesota, Wisconsin and Pennsylvania left to re-label. After those, it's on to the final leg of the project.
FYI... I don't think that I can release any data for the Finger Lakes concurrency considering that they are based on it's copyrighted work, which is not open to the public for free. It's data can be purchased in the GPX format for maps M-1 through 22, then O1 & O2. I don't believe that it comes with any mile markers, but it's maps may be of use for that.
The mapping that I'm doing has to be encoded for use on a rudimentary GPS. A campsite might come up as "C - Shelter." Those with more sophisticated units will see the label, but also more appropriate icons. ArcGIS, which makes basemaps, doesn't work on my computer. If it did, I've heard that I could make them there and embed all of the icons on to it and it would probably work on any device?
The motorhome runs. Even better than it ever has and it currently has a broken EGR valve. I already have the replacement, but it's nut is ceased to it's right side breather tube that leads to the cylinders in the engine. My family mechanic friend is waiting to take a hot torch to it to get it off.
Meanwhile, we'll be dismounting the drive axle and taking it to a friend's garage where the U joints can be mounted. Right now, the drive axle is disconnected from the rear one because my old U joint was very corroded and the wrecker (tow truck) had to take it apart in order not to destroy the drive train about 18 months ago.
This state was kinda hard. All the waypoints adding up and the shapes of six MN DNR divisions and 3 national forests, plus their roads and trails was really taxing The Robot. I'm a volunteer. With Wisconsin and Pennsylvania remaining, the worst is over for now. The hardest part now will be backing down the track on the North Country's concurrency with Finger Lakes. That's a 429 mile track with frequent markers. I'm lucky I got 429 miles to merge. You could probably thank Finger Lake's GIS for that. They made it snap together so well.
And for those of you following my progress in trying to write a mock hike written simulation of the NCT, the saga goes on. This is lengthy when you have to compile the data and do the mock hiker. These logs are detailing almost every step of the way.
I'll step out of this log's character and tell you something hypothetical. I've got some people working on something that might permit me to program smartphones and GPS's for other hikers in one sitting. Stay tuned...
All you do is open the properties of one of my chapter/ affiliate tracks with the "measurements" tab showing and backspace from the end of the track until I come upon a campsite, campground, lodging, or a road or trail that leads to those, then record the mileage in the preset placemarks as I go. All measurements that don't show a decimal point, or those that are really close together will need to be read in inches, then divided by 63,360 (inches in a mile) to get a decimal. If the measurement is a double digit number that has a decimal smaller than 0.1, Google Earth doesn't even bother reading it.
I also re-labeled all of the unnamed campsites from the point data issued by the NCTA. So far, it's all for my personal records.
As expected, it was difficult to get an in-tank fuel pump for a 1988 Ford Econoline cut-a-way. The fuel sending unit that sends a reading to the fuel gauge in the cab might need to be replaced. We ended up just getting the fuel pump because from what I was told at the auto parts store, it Ford might not make them anymore. And that coincides with all the searches that I've done for it? But the employee at the auto parts store said that the sender might just be temporarily ceased? He said that I could be like buildup on a toilet flush handle and that my family mechanic friend might be able to manually move it once the unit is out?
When the motorhome was built, Itasca installed a theft alarm. And it's speaker is over where a second battery could be mounted. It doesn't work anymore and my mechanic friend recommend that this be removed and a second cab battery be installed to improve startup. I concur as I've always believed that the starter could use some improvement.
Over the last year and a half, the chassis has taken on more water damage. One of the first things that I need to do when it warms up is seal the roof and windows, then gut the interior one compartment at a time. But I'm going to use a task list on my smartphone to make a schedule of improvements. He recommends that I go with a natural wood ceiling and I want to go with heavy duty rubber truck cab matting on the floor.
For right now, we might go with the old 23 gallons in the gas that's in the tank. He says that it will depend on a test that he'll do to it. If the test comes back positive for too much water condensation, then we'll evacuate and replace it with something fresh. The strategy might be to to use a fuel cleaner and octane booster? And then we'll fill up the rest of the tank with high octane gasoline.
If he can't get the sender working, I'll just keep taking records every time I fill up the tank, writing down the odometer reading and what the pump reports in gallons, then get an average gas mileage from that. Then set two apps on my tablet, one to use the GPS to track my average speed and the other to use as a fuel tank estimator. It's what I've already been doing.
With those conditions in mind, I did not correct my merged tracks for the trail in Michigan because the state has NCTA issued half mile markers, which is all I need for the next phase of my project. But the markers for this state don't always co-inside with the latest tracks. But I have discovered that one of the webpages that I'm writing for Adventurer's Project, which details the length of each chapter and at-large area's span will still need my Michigan tracks to be corrected at some point. So, I'll probably end up revising this total?
The NCTA's point data concerning parking was reorganized into states. At some time in the future, I can be reorganized into chapters. In doing things by chapters, when I give this data to others, they're computers will likely be of lesser design. Breaking things down this way allows me (and possibly them) to only view items that they need at that given point in time.
Speaking of laundry, I know that when the Buckeye Trail map & guides get wet, then folded, they get sticky. But I just accidently put one through the wash on a hot cycle with bleach, then ran it through the drier and ti came out undamaged. These map & guide combination documents are printed on weather/ tear resistant paper and it just went through some harsh conditions.
An Ohio traffic conditions website was linked to the Adventurer's Project's unpublished website. I hope that it will one day show if the trail in the community of Whipple is ever flooded out? It also links to various street web cams in Marietta of Washington County. Sometimes, the north of Ohio is under snow, while the south is clear. I'm hoping that it might convince a hiker that the conditions are better?
On the Whipple Section, we're waiting on the news of some easements. Other that that, it's internal business for now and I'm letting the powers that be take their time with it. As a result, the hikers and myself inherit that situation. We just have to sit back and let it do it's thing. It beyond our control at this point.
My tracks for Central New York Chapter and the Adirondack Park on the North Country Trail have errors. But the merged track is showing me where they are. I think that I still have the tracks that went into the merge and over lay them, find the problem and fix them that way.
I finished altering North Dakota, Minnesota and Pennsylvania. I skipped Michigan. Ohio didn't have any problems. I'm pretty sure that Vermont is in the best shape that it can be. The total corrected lengths by state were written one of Adventurer's Project's webpages.
There's new hope for the motorhome. I'm pretty sure that my family mechanic friend can fix it? The major part is what to do with the in tank low pressure fuel pump? I haven't been able to find one for a 30 year old 38 gallon tank. He might have more luck. If not, I have 19 gallon units standing by.
I'm somewhat optimistic that this thing might be at Buckeye TrailFest this year? If everything works out, I've got 40,000 speedway points saved up on a nearly free 15 gallons of gasoline. I started saving them up as a potential fuel reserve.
The one thing about owning a chassis with 11 fans is that at some point they all have to be cleaned. I usually wrap one of my fingers in an anti static cloth and soak it in 90% rubbing alcohol. Then in the rest for the rest of the computer I use both a compressed can of air and the vacuum cleaner tube and attachment to get some push and pull action on the dust there.
The chassis is made out of aluminum. And often, I have things sitting on top of it. But that's not good because it's built that way to help keep the system cool. With things on top of it, it's very minor, but it's insulating the system and serving to be counterproductive to it's design purpose.
I've got a display in one of the front 5 - 1/4 inch bays that will one day tell me the CPU's temperature is. Well, I haven't gotten to buying the thermal tape yet to install it's sensor to the CPU. But the display goes in and out. My guess is that it's running off of a Molex power connector that's been Y branched over and over again for the chassis fans. As I've stated one of those fans is dead, but I think it's still trying to draw electricity, but even more now. And that may be causing a sag on those wires, who's power is fixed. I want to try plugging in another power cable into my modular power supply unit. I'm not sure if it has another Molex connection available? If not, the other way of powering hard disk, DVD drives and other equipment is with a SATA power connection. I may have to convert one to Molex, but if any of this is possible, the front display could have it's own dedicated power cable?
Yesterday, putting the dispersed camping GPS I's and O's in on the North Country Trail - Minnesota was taxing my newer computer system pretty hard. Under the circumstances, the hard drive light was on solid most of the time. It must have been punishing my CPU? This kind of work is graphical. It's hard to describe when I when I talk to the employees at my local computer store. I'd say that what I do is not as intensive as gaming, but probably up there with architectural design.
My Garmin eTrex 20 dedicated GPS runs for about $200. If you took Buckeye, or North Country Trail's GIS track data and uploaded it to the devices storage, what you'd get is all of the "baby tracks" that it consists of. And they have to be switched from one to another as frequently as every 29 feet.
In order to make it more manageable, I used Google My Maps to overtake the roads and some of the multi-use right-of-ways. Unlike regular Google Maps, My Maps allows me to create, modify routes, save and export them. They were done in the clockwise/ westbound direction because I have the most success merging tracks that way. Overtaking the original GIS reduced the risk of errors on the merging because one track from My Maps usually eliminated 3 or more GIS tracks.
The merging stripped the written GIS data from both agencies, as a result, it's much easier on my system resources to display them. NCTA's has things in there that might be of use, but for The Robot and laptop computer, I just open the original tracks up when I need that information.
I discovered that my polygon for Superior National Forest surface properties was not displaying correctly and I had to reload it. But that was after I started the I's and O's. Right now, I have Superior's trails and roads loaded and I'm using them to determine if Minnesota's miscellaneous forest state lands are accessible. If they're not, those polygons are being coded red. I'd say that at this point, most of them will be. But the rest that remain green will maximize the dispersed camping opportunities, which is the goal.
Minnesota is the last state that I need to do the I's and O's to. The next step is to correct my merged tracks with the latest NCTA data. Then I should be on to the mile markers after that. Once the mile markers are in, I can write the mock hike written simulation and detail either an average hiker's days, or determine what it really takes to thru hike the trail end to end within the window of time alloted.
I have not been keeping track of my hours. This project ultimately benefits Adventurer's Project. When it's all said and done, if I had to guess, I'd say that there would be 200 hours put into it? The plan is to release all of it's data on Adventurer's Project's website. I still have North Dakota and Minnesota to do. I'm going to leave that for tomorrow. Today, I just got a reminder to make a payment on my Buckeye Trail Association Life Membership. I got it in October, so I guess I should get rid of that?
I determined that when I start the mile markers, that I'll use the dispersed "on" and "off" signals that I devised as to where to put down a mile marker. If I have markers there and a dispersed campsite on the mock hiker simulation occurs between them, I won't have measure very much from the last one. In fact, I'll probably add to the markers as I do this.
Google Earth displays the state forest reservation lines, but doesn't have an icon in them telling me what it is. I started the DIS C I's and O's (dispersed camp, on and off), but it's a shot in the dark if I got them right. They will probably have to do?
The state polygons (shapes) for Pennsylvania commonwealth reservations are in. It's state forests are few, but dispersed camping is permitted and they're all colored green. I just finished up Vermont's state reservations. That's it. The ground work is laid for camping. The next thing I'll be doing is lodging and I should probably be done with that quickly?
And of course all this is a continuation of my North Country Trail mapping project.
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.