My North Country Trail GPS tracks for the State of Michigan are now corrected. The mock hiker written simulation can now continue because the bog just broke. To bring some of you up to speed, the "mock hiker" is a document that details the daily mileages and camping/ lodging of a hiker who will never see the trail. It has rules to keep me in bounds. Buckeye Trail is my "first language," so I'm getting familiar with North Country. And ultimately, I'm trying to predict when their hikers will arrive in SE Ohio. I have mapped out a hiker early warning system, but North Country's end of is imprecise at the moment because I still don't know how it flows.
I'm just really through. This document needs to be done westbound and east bound. But I'll be doing nothing but it from now on.
I want to take this time to write one thing about Adventurer's Project. Starting a chapter in Marietta/ Parkersburg is going to be a different kind of challenge compared to what I believe that we're use to on the BT. That's because unlike other chapters, this area doesn't have a whole lot of existing support in the area. So the members that it gets are probably (and literately) going to have to come right off of the streets as apposed to Buckeye or North Country Trail Association's roster. That's probably more from scratch that it's use to.
Showing posts with label michigan. Show all posts
Showing posts with label michigan. Show all posts
2018/01/07
Dispersed Waypoints - Michigan and Wisconsin on North Country Trail
I finished the dispersed camping waypoints for Michigan and Wisconsin. I went on to try North Dakota, but my Google Earth crashed when I accidentally tried to paste a KML element into a text field. That's the #1 way that I crash this application. It happens when I accidentally click on a colored polygon, or a shape for a government reservation. In this case, these are colored "green" for when dispersed, or backcountry camping is permitted. As I've mentioned in previous articles, I'm putting the "I's" and "O's" in to signal "on" and "off" for more rudimentary GPS's.
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 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?
2018/01/05
Michigan DNR, Pennsylvania DCNR and Vermont ANR Plotted
Michigan DNR parcel GIS data is taxing my computer to it's limits. I have to set my CPU's to "high priority" for Google Earth Pro and it barely runs it. I can't find any shapes of for DNR's reservations. Instead, I'm using the parcels, which has a lot more entries. I'd like to color code them for the camping that's available, but with how I'm throwing everything my computer's go into it and it's running really slow, I don't think that it's worth it.
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.
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.
2016/12/08
Log 2016120801
The Robot was dug out from the clutter in the room and is now on top of a two drawer file cabinet where it should be. It is now ready to have it's new 4 port SATA RAID expansion card and an additional 5.25" drawer installed. The motherboard supports 8 SATA drives, which most of mine are currently mounted to. But I've come to find that four hard disks are probably taking up a lot of it's RAM, or memory. In order to alleviate that, I'm installing an expansion card into one of the motherboard's slots.
The drawer is just for storage. The Robot's chassis is tall and has three CD/DVD drive bays that I'll never use. Two of them already have storage drawers and I currently have the upgrade to install the final one.
My graphics are running off of what's soldered on the motherboard. Unfortunately, to run it, that's also using memory. I don't have the money yet to get another expansion graphics processing unit, but I think I can tell what made the prior one that I had go bad. These days, graphics cards come with their own down facing cooling fans. Well there wasn't much space between it and the card below it, so it's airflow was being blocked. When I was playing movies, it would crash The Robot. My theory was that the card was overheating and had done that so much that it damaged the graphics processing unit (GPU).
Not all of the lower cards are the same size and shape. So, I think that if I reorder the cards from top to bottom, with the thinest being at the top, I can create a space for better air flow should I insert another expansion graphics card into The Robot.
Doing these things might help to allocate more cache memory to Google Earth. And this is essential to working with the North Country Trail Association's GIS Repository. Even when just working with Michigan's tracks as I've recently modified it to do.
The drawer is just for storage. The Robot's chassis is tall and has three CD/DVD drive bays that I'll never use. Two of them already have storage drawers and I currently have the upgrade to install the final one.
My graphics are running off of what's soldered on the motherboard. Unfortunately, to run it, that's also using memory. I don't have the money yet to get another expansion graphics processing unit, but I think I can tell what made the prior one that I had go bad. These days, graphics cards come with their own down facing cooling fans. Well there wasn't much space between it and the card below it, so it's airflow was being blocked. When I was playing movies, it would crash The Robot. My theory was that the card was overheating and had done that so much that it damaged the graphics processing unit (GPU).
Not all of the lower cards are the same size and shape. So, I think that if I reorder the cards from top to bottom, with the thinest being at the top, I can create a space for better air flow should I insert another expansion graphics card into The Robot.
Doing these things might help to allocate more cache memory to Google Earth. And this is essential to working with the North Country Trail Association's GIS Repository. Even when just working with Michigan's tracks as I've recently modified it to do.
2016/11/29
Log 2016112902
All of the GIS and GPS tracks for the North Country Trail in Michigan have been numbered in order in the westbound direction. The next step is to change the color of every other one so I can determine what direction they're in and make sure that the beginnings and terminators barely overlap.
2016/11/27
Log 2016112701
The hard part is over. The majority of the tracks for the North Country Trail in Michigan are now organized by chapter. I made some mistakes in the Upper Peninsula tracks, so I started consulting the chapter spans from their individual web pages.
What's left with Michigan's tracks:
Changing every chapter's track color to NCT blue
Transplanting some missing tracks from my copy of the NCTA GIS Repository. It's tracks are usually red.
After transplanting, turn all tracks in chapter folders to NCT blue
Numbering the tracks in westbound order.
Having Google Earth resort them in numeric order
Changing the track colors so that every other one is red or yellow.
Find smaller tracks and overtake them with a neighboring track (this lowers the track listing)
Adjust the track beginning and terminators to that one is directly on top of the other.
Determine what direction each track is facing and note it (Eb or Wb)
Reverse the eastbound tracks and integrate the new westbound tracks in their place
Merge chapter by chapter
Note each chapters mileage, high and low points
Report my findings to the North Country Trail's Facebook group.
That might seem like a lot, but it's just another day's volunteerism. Right now, about 1,000 miles of trail is organized the way it should be. And for today, that's good enough for me. Wisconsin and Minnesota aren't going to be nearly as hard. North Dakota's modified tracks just need to be cut down, or merged by chapter and reported on.
What's left with Michigan's tracks:
Changing every chapter's track color to NCT blue
Transplanting some missing tracks from my copy of the NCTA GIS Repository. It's tracks are usually red.
After transplanting, turn all tracks in chapter folders to NCT blue
Numbering the tracks in westbound order.
Having Google Earth resort them in numeric order
Changing the track colors so that every other one is red or yellow.
Find smaller tracks and overtake them with a neighboring track (this lowers the track listing)
Adjust the track beginning and terminators to that one is directly on top of the other.
Determine what direction each track is facing and note it (Eb or Wb)
Reverse the eastbound tracks and integrate the new westbound tracks in their place
Merge chapter by chapter
Note each chapters mileage, high and low points
Report my findings to the North Country Trail's Facebook group.
That might seem like a lot, but it's just another day's volunteerism. Right now, about 1,000 miles of trail is organized the way it should be. And for today, that's good enough for me. Wisconsin and Minnesota aren't going to be nearly as hard. North Dakota's modified tracks just need to be cut down, or merged by chapter and reported on.
Subscribe to:
Posts (Atom)