ecanderson

I don't know if you play golf, but the description of the web site from the previous poster isn't really all that different from how it's actually done. After playing a round of golf, if the player intends to play with competitive golf with a "real" handicap (not purely recreational golf), the results of the game are entered on the course computer by the player at the end of the round. It is by that system that a player's handicap is computed for competitive purposes. The resulting scores and handicap then available for verification. It's not enough to enter a competition and say "I shoot a 22 handicap". This system is the way we know you're not really an 8 handicapper and trying to sandbag us! For those who prefer their geocaching as a competitive sport, the same honor system applies to both logging caches and posting your round at the end of a golf game. The difference it that the pros rarely get away with anything (too many fans, officials and cameras) ... not even Vijay (1985 Asian Tour). Much of what many geocachers do is done in as much stealth as conditions permit. I could care less whether someone posts a bogus golf score or does a bogus online log of a cache. When caught, it certainly provides information about a person's character, but unless there's money on the line that has been taken out of someone else's pocket (e.g., professional golf), nuts to 'em.

A coordinate error can be either + or - and will create a error in either one direction or the other of a specific distance. The idea of considering distance as +/- in reference to a coordinate system doesn't seem all that peculiar since there is a datum in mind to which the motion is associated (moving north in the northern hemisphere being plus, and moving south in the northern hemisphere being a minus). That a coordinate error is being described as a "possible actual distance from target center" error makes perfect sense to me -- it has more meaning than specifying the error in 0.001 minute increments, especially as many people don't really know what that represents in terms of distance. If your latitudinal error is, for example, +/- 0.002 minutes, that'd give about a +/- 12 foot error radius from center along the N/S axis, and if the longitudinal error is also +/- 0.002 minutes, that'd give about a +/- 9 foot error radius from center (up where I live) along the E/W axis.

Long as you don't slow down the pace of play, and you replace your dadgum divots (gotta figure a baseball bat is going to require some extended turf repair), you'll be fun to watch! I have enough trouble with a 2 iron.

Could be I'm just lucky. Could be I'm just too new to this at a couple of weeks to give a rip -- I don't have the time to even consider playing "catch up" to those with thousands of logs under their belts. I'm logging the finds and signing the logs. As long as those placing caches use decent coordinates and tend to them, and those who are looking for them are having fun finding them, it's enough already. Only the things that detract from one of those two activities really matters to me. People making false claims of finds doesn't impact either one. I try not to even look at the online log entries until I've already returned from the hunt. As they say, "spoilers" can occur. OTOH: If a bogus online entry causes a cache owner unnecessary grief -- and I can see how that could happen, that's not good. Apart from that ... some people taking the numbers game all too seriously.

An update on TT units, NavCore7, and geocaching... I've been communicating with the author of OffRoad Navigator, and it seems that there won't be any 3rd party applications that are really good for geocaching UNLESS/UNTIL TomTom goes open kimono and finally releases an API/SDK to the developers for NavCore7. There are TWO places on your TT that you can get GPS coordinate data. The first is when you press in the lower right corner on the "bars". That takes you to a screen where you can see your unit's firmware version number and some coordinate data in little, tiny print. THAT data is snap to road! If you're near any kind of paved surface that is known to the TT maps, you'll have a bugger of a time getting the coordinates perpendicular to the road to update properly. Unfortunately, it is THAT data that is provided through the old API/SDK to developers (harumph). HOWEVER, if you press on the right side again, you'll get to the page that shows the satellites in their orbital positions, and yet a different set of coordinate data. THAT data is "unsnapped" and pretty raw, and can put you right on top of a cache site. I'm betting that it's beginner's luck, but I'm 5 for 5 on finds that were within 4 feet of the specified coordinates.

I'm starting to wonder whether I've just developed an incredible case of beginner's luck here. I picked up a TT720 for road navigation at Christmas, and after hanging around a geocacher on a regular basis, figured it would be fun to try this unit in that application. It's a SiRF III chipset, and that's all I know about its abilities on the front end. It provides either snapped-to-road coordinate data (not good for geocaching) or, if you go to the right screen, the raw GPS information in your choice of formats -- I use the dd mm.mmm for this purpose since it seems to be the geocaching-preferred notation. It's the screen that shows the satellite orbit positions and individual signal strengths. Granted, I've done a whopping total of 5 caches, and all have been in good weather conditions with clear air above. I know that helps, but ... After allowing the numbers to settle for about 15 seconds, the 720 has put me within no more than 4 feet of the actual location of the hides in each of the 5 cases. That would seem to indicate that not just my unit, but those of the people placing the caches as well, have some serious accuracy going for them. AFAIK, the TT720 doesn't even incorporate WAAS. So should I thank my lucky stars, or has the technology with the advent of the SiRF III really gotten this good?

I picked up a 720, which came with NavCore 7, as did the 1, 3rd edition as I understand it. Consequently, it would seem we have a lot in common at the moment, especially as I don't have a copy of the NavCore6 software to work with. We have the same core system with the same 3rd party options for our units. The 720 was initially a bust for earlier versions of OffRoad Navigator as the screen was pretty well buggered. After the author issued OffRoad Navigator 1.7B, it became usable. Data entry is still a problem, though, so instead of trying to enter a latitude/longitude set in the ORN display, it's FAR easier to set up your destination either using the TT's "itinerary" (load it as a "File" from the ORN main window) or using the TT's "favorite" method (again, load it as a "Favorite" from the ORN main window). Here's the link to the software itself: http://www.webazar.org/tomtom/offroad.php?lang=en With that in mind, I've taken out the 720 and tried a bit of caching, and can advise as follows: You really DO need to make a couple of adjustments to the ORN configuration for caching. Here is my configuration file, including the "tweak" that cleans up the screen a bit for NavCore7. It also accomplishes two other important things... a) it reduces the "at target" distance to 1 meter, and it uses "real" coordinate results, NOT the "snap to road" type results. Without both of those changes, you're toast if trying to use one of these units as a caching device. These are the contents of my config.txt file for ORN, found in the "offroad" folder once you have the software loaded. The "targetdistance 1" sets the 'proximity detector' to 1 meter instead of 100. The "snapping no" avoids on-road snapping by the TT software. Those were changed. Also be aware of the "processperiod 500" which updates every 500 milliseconds (1/2 sec) and the "coordinates degminute" which puts you into degrees and decimal minutes, useful for avoiding conversions when caching. A quick edit of this file with notepad or wordpad can be a lot easier than dealing with the config screen in ORN, but that screen is actually functional on NavCore7 now. [Other parameters] language english.lng units english colorscheme night targetdistance 1 gmtoffset -7 geoidfix no 48 coordinates degminute snapping no mapfile [Manual parameters] processperiod 500 [Colors parameters] topforegroundcolors 0,0,0 255,255,255 204,204,204 bottomforegroundcolors 255,255,255 255,255,255 204,204,204 topbackgroundcolors 255,255,255 0,0,0 bottombackgroundcolors 0,0,128 0,0,128 linescolors 204,204,204 204,204,204 labelcolors 255,0,0 255,255,0 daybackground nightbackground screenadaptation rider2 [End] Once I had ORN tweaked per above for caching, I took the 720 out for a couple of test drives. I have a couple of observations about using the TT in this mode. These observations are made in otherwise "clear sky" conditions. First, I've had instances where the TT itself was balky about updating coordinate position. At first I thought perhaps it was the ORN software, but in going directly to the TT's own direct display of satellite signal and immediate coordinate values, I found it was the TT that was sometimes balky about updating, primarily about the latitude figure. Even with "snap" off, it seemed that the TT would sometimes not trust the data, and give me a bit of a hard time in this regard. It seemed that motion at 2mph or more would often get it off the dime and the display would start to update. ORN can only work with what the TT is providing to it. Second, I've come to learn that even the SIRF3 chipset can be fooled pretty seriously by reflections. In attempt to check out a benchmark near a bridge, we were confounded by the ORN software telling us we were 6 yards from the target, and suddenly having the unit blow us to 38 yards distance within the space of a foot or two. The reflections from the bridge were driving the TT unit nuts. I would imagine that this isn't all that uncommon for other units, but as a newbie in this business, it's a bit disconcerting. Apart from those two caveats, the 720 with NavCore7 and the 1.7B ORN software is certainly adequate for most caching purposes. The lack of a true electronic compass seems to be a real shortcoming, though. I am thinking seriously about soon adding a purpose built unit to my stable just for caching. As this is clearly a TT thread, I won't post my suggestion now, but in practice, it would seem that a unit that includes that feature certainly would have an advantage.