wildlifewriter

Some possibly useful information for Garmin iQue 3600 owners ONLY... There is empirical evidence that the iQue 3600 will not use the current ESTB signal for differential corrections unless the interim software patch 5.2.1r3 patch1 is installed. This can be downloaded from the Garmin website, HERE. This patch only applies to the iQue 3600 unit. You may THINK that you have already installed the patch, but note that it needs to re-installed after a hard reset. In operation, the unit may "skip" satellite #33 without acquiring enough data for it to be recognised as a (sort of) valid signal. It may be necessary to switch the unit off, and on again, at intervals of about ten minutes before the unit gets the part of the transmission which it recognises as useable. The reason for this behaviour is not known. It is necessary for the iQue to receive the whole of the WAAS-type signal error-free, before all the corrections can be applied. This may take as long as half-an-hour, at first try in real-world operation. Other information: Like many Garmin receivers, the iQue seems to have a preference for corrected satellite data, when not all sats are being corrected. This may mean that the overall accuracy of the solution may be WORSE under this condition. The unit is very conservative about the validity "lifetime" of the corrections it receives. If the WAAS/EGNOS/ESTB signal is lost, an iQue will cease corrections within two minutes - even though the data should be valid for much longer than that. The reason for this behaviour is not known. (Again. ) -Wlw.

I have no doubt that you have put your finger on it. -Wlw.

The mapping is faulty. Mapsource products (Metroguide 6, City Select 6 & 7) all show the island almost exactly 1000 metres west of its true location. -Wlw.

If you asked Garmin about this, they would tell you that your receiver is operating correctly, and in accordance with the agreed industry standard. Which is correct. If you asked them about the EGNOS/ESTB signal, they would tell you that the current signals are NOT compliant with the final agreed standard and that's why some Garmin units don't recognise them. Which is also correct. If you asked the European Space Agency (or their contractor: ESSP), they would tell you that the systems are still under test. They might refer you to this web page. The page is deliberately written in gobbledygook, so that hardly anyone can understand it. They would like you believe that the systems WILL BE compliant with industry standards, one day, but they don't want to talk about it. Both the ESA and Garmin would be happy if you (and I) didn't ask them any more awkward questions about this whole thing... -Wlw.

I claim the June Plonker of the Month Award, for breaking my arm while doing a maintenance visit at one of my own caches. In case this isn't plonkery enough, I then climbed to one of the Six-Peak Challenge caches - GCKAEZ - still with the broken arm, and mild concussion. Only five more weeks in plaster to go, now... -Wlw.

On some receivers, the "signal bar" remains greyed out, and never turns shaded black, even though differential corrections are being received and applied. This is because many models (of Garmin) expect the GEO satellite to be transmitting ranging information, in addition to corrections. Satellite AOR-E (PRN 120, Garmin #33) is currently transmitting corrections without ranging, so the behaviour you see is consistent. -Wlw.

Well done Twiggs! Keep it up....

I've pencilled this one in as a "probable". The plaster cast should be coming off my arm around a week ahead of the SGDO date - but it depends what the physios say, at that time. -Wlw.

Just my 2 euro worth... I wouldn't agree - and that's based on your use of the word "slightly". If this is a mere adjustment, and the cache is close to the original location, with the same terrain and type of hiding place, then I wouldn't log a find twice. Come to think of it... I can't think of any circumstances in which I would log the same physical cache twice. The onus here rests with the cache owner: if the "new" location is some distance away, and the terrain, difficulty, approach - if everything is different, then it should be a brand new cache with a new waypoint identifier. -Wlw.

A correctly-functioning receiver does "know" this. In parts of the far west of Ireland, it's possible to receive signals ftom the WAAS station AOR-W. (PRN122 - Garmin no 35) on a handheld. This satellite provides corrections for part of the North American continent, and the western Atlantic. Ireland is not within its service area. Given how the system works, we would expect our handheld to listen to signals from PRN122 for a moment, (perhaps, several moments) identify that the corrections are not applicable to its current position, and then ignore that satellite and go looking for others. And - in fact - this is exactly what happens. -Wlw.

This is a useful discussion. I have just submitted an earthcache listing for consideration. (It's the first one for Ireland. ) Because the location is very well-known, and attracts large numbers of visitors during the high season, I thought that it WAS appropriate to seek permission before proceeding - even though the land itself is public-access. Interestingly, the agency responsible was very positive and helpful about the idea, but they wanted to see the "finished web page" before formally endorsing it. I guess they want to be sure that we haven't included any misleading or inaccurate information. So... I have sent them the draft text, but assume that I can make any changes asked for, once the earthcache is finally listed. (like an "ordinary" geocache page.) -Wlw.

They should keep their business out of other peoples' noses... -Wlw

Well done M&L... Come back to Ireland soon. -Wlw

Well done the lads, on another milestone reached in this highly dangerous hobby... -Wlw

Sorry Jeremy, but that doesn't make sense. As I understand it, the OP is asking for .gpx. file format to be available instead of (or, as well as) .loc format where the latter is currently the only option. I would support his request. - and if it's a Premium Member-only facility, then so be it. One reason is that Garmin's Mapsource application - in its newest version - no longer supports the import of .loc files directly. (No idea why they made this change.) Even if the .gpx file contained no additional information over .loc, it would still be useful for this reason. -Wlw.

I always try to edit my pages in notepad, and then cut&paste into gc.com - for precisely that reason. No doubt... ... but there's the cutting-and-pasting part, and then there's the trying-to-get-it-all-set-up-evenly part. On gc.com's page layout, this second bit takes half-an-hour.

I had the same problem, at exactly the same time this morning. Was editing an event cache page, and thought I had lost half-an-hour's work. Nasty.... -Wlw.

It looks like you have discovered that the "Quest" is not - and wasn't designed to be - a geocaching/hiking tool. Getting ad hoc waypoints into a Quest is a fiddly business. The unit is really concerned with street addresses and points-of-interest. To enter a waypoint manually, you have to persuade the Quest that it's one of these - and then edit the information. Much easier, is to load the waypoints from a PC, using the "Mapsource" software which came with your unit. The Quest IS capable of displaying a direction pointer (not really a "compass") but you may have to set Route Preferences to "off Road" before it will agree to do this. Once all this is done, you'll find out another reason why people don't use Quests for geocaching - out of the car, its battery only last about two hours.... -Wlw.

Disgraceful. And in a public place, too.

That's the bit that didn't make any sense.

You have no option but to allow the points to count in the June total, since ye put the list up, but didn't make any stipulations about starting dates. It has to be: that anyone making the find as part of a "joint effort", can claim the points, as an individual. There's no way of sorting it out from the log entries, else. A proper "ruling" is essential, because this is going to happen a lot: many of these caches are on islands, or require a significant upland hike to reach them - which people shouldn't be doing on their own. -Wlw.

Congratulations Andy. And your next starter for ten, is... ... who is going to reach 700 first? -Wlw.

Congratulations John, on 1000. (What a show-off) -Wlw.

I like this whole idea, but there's a couple of items in the scoring table that I do have a problem with... This would be a good thing to do (reason in a moment) and ought to carry a higher score. This is OK - but only if it's done at the request of the cache owner. It's the owner's ultimate responsibility to maintain the cache. If the cache needs a new box or logbook - then the implication is: that it isn't being maintained properly. Drawing attention to caches that are (i) missing or (ii) not maintained is a useful service to the hobby as a whole (because the cache could be archived, giving an opportunity for the location to be re-used), and so should carry a higher "score". ... just my 2d worth -Wlw.

Perhaps an extra column for county would be sufficient. I can provide M&L with the counties for the Irish ones. -Wlw.