B+L

I second everything the jesting one said and the High Divide (7 Lakes Basin) is a good one. I must confess we have not seen the movie, but I believe some scenes were shot around Forks? If so, close to Forks, there is some very beautiful hiking not far from the Mora Campground near La Push. Go North from Rialto Beach, past the Hole-in-the-Wall, a mile or so, and the scenery is hard to beat. Depending on how far you go, beach hiking can be slow going in some places and you may be held up if you don't plan for the tides (please do), but it is possibly the best stretch of coastline in the State(s). Beware: the local fauna has had a lot of contact with careless humans and you need to be pretty cautious with your food, or you will get robbed by the little devils. Even the birds are persistent little rascals. We either take a bear canister, or we sometimes use a 2 1/2 gallon bucket with lid that doubles as a handy stool. In some places bear canisters are required, but you can rent them pretty cheaply at the Wilderness Information Center (WIC) in Port Angeles. Be sure to check with them before you go, they are very helpful with trip planning. Plus, permits may be required for some of the more popular hiking areas. Timing is everything if solitude is what you are seeking.

I'm afraid you are out of luck with the Garmin Communicator plugin. I believe Garmin mentions somewhere that it does not work with usb to serial converters.

You did not say where you obtained the drivers or what you are attempting to use them with, such as what software is reading/writing the device. That information might prove to be helpful. However, if you are using the factory drivers, that might just be your problem. The MacCaching blog states the Prolific drivers do not work and suggests using these. There is also an Open Source driver project for the PL2303 that can be found here, which may or may not be the same drivers as above. I did not look. We have used the factory drivers successfully with our old eTrex Vista, but the connection sometimes failed intermittently or would not connect or be recognized even when it had worked earlier on the same day. The factory Windows drivers did work using Parallels to run Windows XP and since we mostly used the device with GSAK and Windows, we did not try the alternative drivers. Other people have reported they work fine and they are Universal binaries so they should be OK even if you have a PPC MacBook.

My sentiments, exactly. We also wondered about the user fees. No one likes them, but if they keep the parks open... Semi-related, we once returned to our car after backpacking and found a note on our windshield thanking us for having a NW Forest Pass. I guess because we had the only car displaying one, or at least when we arrived (late) no one else did. Fees would not help much if, like the Forest Pass, hardly anyone paid them, or if they went into the General Fund instead of the Parks Dept. Well, at least we can amuse ourselves playing with the old fridges and piles of tires in the unmaintained parks.

Sweet. I got the info second, or maybe third-hand and the source was probably has learned to be pretty cynical.

It's too soon to tell what will happen. Some parks are certainly going to be closed, temporarily or permanently. Permits are required for caches in state parks, so they already know were they all are, but it is not clear if caches will allowed to stay in place in a closed park and what kind a access will be allowed, if any. Tickets and fines are a risk for those who find closed signs to be inadequate barriers to entry. I'm not going to get all political. I merely raised this issue for informational purposes since many, if not all of the parks in question have caches in them. There is an email address where comments are being accepted at the link I posted, above.

From a staff paper presented to the WA Parks and Recreation Commission yesterday, here is a list of state parks that could potentially be closed (mothballed or abandoned). The parks are listed in order of annual visitors (35,860-715,203). PS Jarrell Cove EA Fields Spring PS Federation Forest EA Sacajawea SW Rainbow Falls SW Beacon Rock SW Lewis & Clark SW Fort Columbia EA Alta Lake EA Columbia Plateau Trail NW Wallace Falls PS Lake Easton EA Yakima Sportsman EA Maryhill PS Illahee PS Dash Point SW Potlatch SW Twin Harbors EA Ginkgo/Wanapum PS Flaming Geyser NW Peace Arch PS Saltwater SW Ocean City NW Fort Ebey EA Wenatchee Confluence EA Lake Wenatchee NW Fort Flagler EA Mount Spokane SW Millersylvania Memorial EA Sun Lakes - Dry Falls NW Larrabee NW Fort Casey PS Saint Edward There is an additional list of 13 candidates for transfer to other jurisdictions. Nothing is decided yet, but the proposed budget cuts $23 million from the parks budget and some of the cuts will come from the "park level". More information here (not yet up to date).

Zoom out to 100 miles or so until you can see at least portions of Oregon and Washington on the map. Typing "m" will select the map tool. Click on Oregon and Washington and the selected tiles will get highlighted. You can then copy the map to your Colorado. There should be drop down list that allows you to select the internal memory or an SD card if one is present.

I got a reply today. It was surprising, because their contact form apparently hates me and the two different browsers I tried. They said there is probably not much they can do to help since it is a third-party product they are not aware of and could not find using Google. I guess I left the link out in the copy that made it through, but switchbacks.com is 6th hit returned when googling Northwest Trails and I gave them enough info to make it the first hit. Even so, I don't expect them to have to google the info. I told them where to find the maps and suggested the problem might be with their MapInstall app for the Mac and we'll see if that goes anywhere. I may have to call Garmin to make sure they understand the problem. Unfortunately, using Mapsource is currently out because when I run Windows under Parallels, either the Oregon is not found by Mapsource or my Mac kernel panics when it is. Luckily, I can still use GSAK without any problems. As long as I install something else like Building Footprints along with NW Trails everything works. Although it takes a little longer to install, it is measured in minutes instead of hours like it would be if be if I bundled all the maps I have installed.

We have an Oregon 400t (thanks Santa!). If NW Trails is installed by itself on the unit's internal memory, or an SD card, the map does not appear on the map screen or on the map selection screen. If NW trails is installed with other maps, it works fine. This happens with the two latest beta updates, 2.85 and 2.86. We are not sure if the problem is with the beta updates, or the unit itself. Jon says he has not heard of anyone else having this problem and suggested we ask here. We've also reported the problem to Garmin's beta problems list. Is anyone else running one of the last two Garmin updates and either having or not having the same problem with NW Trails?

Congratulations to Lucy's Ranger for reaching 900 at It's All for the Kids.

The original Starbucks is in the Pike Place Market The nearest cache is Frecky's Architecture and Design Adventure

Apple dumplings.

Did you double click the installer after extracting it? It worked for me.

The expectations in this game are mostly self-imposed. The question of when and what to log really depends on how one defines *logging*. To some people, it might be important to have an accurate accounting, or even an audit trail. Others may prefer to paint in broad strokes, or not at all.

Well, in that case, we might as well add as many counties as we can. King County Parcel Viewer Pierce County Parcel Search

Are they singular, plural, or just omnipresent?

I know what you mean, but instead of ridiculously high, I would have to use at least three or four superlatives to describe FodoB's numbers. He has logged 1034 so far.

I guess you are referring to me when you say "missing the point", if so, you've lost me. What point am I missing? I fail to see the relevance of section easements in Idaho. The OP tried to place a guardrail cache and to his credit, he was upfront about its location. As a result, the cache will now get held up until he manages to get permission for it from the County (and good luck with that). There are, in fact, rights-of-way on public lands, such as when a county road crosses or adjoins state land. The right-of-way itself is often public land, but that does not mean there are no restrictions. The County Code I quoted earlier explicitly denies permission for placing any objects in the right-of-way. Fortunately, there are innumerable locations to hide caches without needing to "grant ourselves permission" because we have already been granted implicit permission to do so. One of the best things about geocaching is the somewhat loosely defined guidelines that leave plenty of room for people to play however they like. But, if geocaching continues to grow as fast as it has over the past couple of years and it remains a common practice to place caches justified by whatever dubious rationale people can conjure up and "adequate permission" is really "I gave myself permission" even though explicit permission was required, will we not inevitably end up with less guidelines and more rules? I do not look forward to the day when all geocachers are licensed, all caches require permits, and the geocaching underground is busy geo-tagging our public places. Oh, wait... we already have drive-by caching. Actually, it is not all that hard to imagine the guidelines requiring proof of permission in writing before a cache will be published. I think very few people actually would want that. Least of all, the reviewers.

Maps are installed as bundles named XXX.gmap (where XXX is the map name) in your Library/Application Support/Garmin/Maps folder. You can move the bundle elsewhere or delete it.

As I said, the County handled the ownership issue very cleverly. Section lines, etc. are not necessarily road rights-of-way and are thus not under discussion. Again, the State (Washington), counties, and various municipalities will all have their own codes either explicitly or by reference. I used Pierce County as an example on purpose. Last time I went to Mt. Rainier during "sign season" one more sign in the right-of-way could possibly have knocked the Earth of its axis.

In this instance, the County Code is very plain in its intent. And yes, the county cleverly addresses ownership in D.2. OT, a story about ownership: During the big pre-Christmas windstorm in 2006, We had some pretty big trees blow down. I spent a couple of days bucking and splitting before I decided I really ought to rent a log splitter. There was still too big of a mess to maneuver the splitter where it would be most useful, so I rolled a bunch of rounds down the bank and split them on the shoulder. I live on a road with very little traffic, mostly just my neighbors, so I figured the wood would be OK sitting on the shoulder until the next morning. In the morning, I looked out and saw one of my neighbor's loading wood into the trunk of his car. When I went out and asked him what he thought he was doing, he had the nerve to tell me the wood was sitting on the public right-of-way and thus free for the taking. I told him that since he often parks his car on the public right-of-way, maybe I'll stop by and "borrow" it next time I need to go uptown. He got in and drove off without another word, taking a few pieces of my wood with him. We haven't spoken since.

We have been somewhat taken aback by the laissez-faire attitude many cachers have about, what to us, are clearly illegal cache placements and I am not referring specifically to this thread. My own common sense tells me that a road right-of-way usually grants me nothing more than the right to use it to travel from one place to another. There are other types of rights-of-way, such as natural gas pipelines which explicitly grant other types of access, such as recreational use, but that is not what we are talking about. I'm sure we would all prefer it if all caches were creatively hidden in places of great natural beauty, or places that are intriguing for other reasons, but just about everyone will make exceptions. I suspect geocaching will eventually go the way of other booms (tennis anyone?) and perhaps issues like this will all blow over without us getting regulated to death. In the meantime, we would be all be better served if we stopped abusing the trust granted to us by the reviewers and took care use our common sense in terms of sound judgment, rather than as a synonym for willful ignorance. I realize some people might take that last bit as a shot at them, but that is not my intention. I could probably find a more artful way to write the above paragraph, but as I stated earlier, I am really more concerned about general attitudes than anything expressed by anyone in this particular thread and this thread has actually been fairly encouraging overall. I've included the relevant law from the Pierce County Code. The State, other counties, and most municipalities will all have all something similar on the books. Be my reading, geocaches placed in the right-of-way require written permission from the County Engineer and there appears to be very little room for interpretation. Before anyone jumps on me for suggesting some type of cache should be banned or claiming I'm playing cache cop, you should know we learned pretty early on how to deal with caches like this -- we ignore them. There are more caches we've ignored than we've found and it will probably always be like that. If more us ignored caches of this type, would they become less popular hiding places? Who knows, but it would be an interesting experiment. Pierce County Code 12.28.010 Permission Required - Removal. A. No person, organization, or agency shall place, erect, or install any object of any nature whatsoever, within a County road right-of-way without the express permission in writing of the County Engineer, and any such object now in place within a County road right-of-way without written permission of the County Engineer is declared illegal; provided, that this Section shall not apply to mailboxes and attached newspaper boxes, placed on the County right-of-way, where these are placed as far removed from the driving portion of the right-of-way as possible, except that said placement shall be subject to approval of the Pierce County Engineer. B. Any person placing any object within a County right-of-way in violation of this Section shall be responsible for the removal of the object within 48 hours of receipt of written notice from Pierce County. If the object is not removed within 48 hours and it unreasonably hampers or prevents the proper use of the right-of-way, it may be summarily removed by the County; provided, that the notice requirement may be waived and the object may be immediately removed by Pierce County if it presents an immediate threat of physical harm to persons or property. C. Abatement of any object or encroachment in Pierce County right-of-way which does not interfere with the proper and legitimate use of such right-of-way may be effected through an injunctive suit by Pierce County authorities. D. Nuisance Cleanup Special Assessment and Lien. 1. For purposes of this Chapter, any object situated on or in a County road right-of-way without permission of the County Engineer and not otherwise permitted by PCC 12.28.010 shall be deemed a nuisance. 2. In addition to any other provision authorized by law, the cost of abating a nuisance shall be a special assessment on the land or premises on which the nuisance is situated. The special assessment shall defray or reimburse the County for the cost of abating the nuisance. This assessment shall constitute a lien against the property that shall be of equal rank with state, county, and municipal taxes. The special assessment and lien shall come into existence and attach upon compliance with the provisions of subsection 3.

VERSION 1.0.1 ...your wish has been granted. Version 1.0.1 now online and including the rest of Vashon, as well as Green River Valley and Umtanum Recreation Area (where I'll be headed later in the week. How self-centered, I know. ). All additional coverage in 20' contours. Any suggestions, or reccomendations for coverage, feel free to weigh in. Also, with the detail of these maps, things will get very large very fast. I believe I'll start dividing the installers into regions (like with Garmin's West/Central/East for 24k maps); any suggestions for natural boundaries? Thanks for the update. We made good use of it today during our nettle-fest. If you were to tile using 7.5 min quad boundaries, I don't think it really matters so much where you divide the installers and it would keep the size of individual tiles reasonable. As far as more coverage, we'd personally be happy with the whole state If you were to standardize on something like the 7.5 min quad grid, it would make it pretty easy for others to assist you with your efforts.

I am really happy you did this. I know what a tedious process retrieving the data can be before you can even get started converting it. Kudos to you. Earlier in the week, we installed your first revision maps and Moun10bike's together on our old grayscale eTrex Vista and explored a ravine we have long been wondering about. The topo and stream data were excellent. The zoom levels were perhaps a little off, but I see you have already made some tweaks. We'll give your latest version a try later today. We eagerly await more coverage, like all of Vashon. <wink>