YeOleImposter

Hmmm, the only date I see in the logs on the sheet you reference is "20051218" ??

Actually it is very smart to leave the container. Any cacher looking for the cache will 'find' it and give up. If the container is removed, then every cacher who comes looking for it will spend even more time looking for what, they think, should be there, causing even more traffic at the area.

I looked, and it sure looks like everything is in order. Was really hoping to get a 'free' copy of NGS-GPX! PS. Last time I ran the program, all my heights were '0' but I did not have time to check it out and forgot to send you a note. May be fixed already.

Yes, Yes, Yes. With the import routine created Foxtrot_xray GSAK now displays each log from the NGS datasheet as a seperate entry than can be sorted, etc. Foxtrot_xray does not geocache either but uses GSAK just for benchmarks. I do both, so keep a separate database for each. It also then gives you all the other features that GSAK offers to cachers -- including some incredible macros that can be modified to work with benchmarks including maps, gps exports, and stats. Before going out on a hunt I look on a topo map for possible better coordinates for scaled marks -- GSAK allows be to plug these in as corrected coordinates and will export these instead of the datasheet coordinate. GSAK then allows me to export an unlimited number of benchmarks into my Garmin 60csx since I have it put them in as custom Points-of-Interest instead of waypoints. The intersection stations look like towers on my GPS, the adjusted marks use the regular benchmark icon, and the scaled use an icon that looks like a compass. The reference marks, if any, are just blue dots, but even these show up on my gps since foxtrot_xray creates them as child waypoints inside GSAK. The 'funnest' part is the stats page - My latest update is viewable here: GSAK Benchmark Stats. I wish my stats were more impressive

I have had to send in some corrections too, I don't ever remember getting an email reply, but when I next check the PID it is 'magically' corrected.

I call that 'aggressively getting ready' - which, for me, is just another way to look productive without actually doing anything -YOI-

Wow! version .90 to .128 in 1 day Had my hopes up for a minute with the newest feature that you had figured out some way to pull the logs of others at GC.com into GSAK. Thanks for all your work on this! YOI

I don't think anyone would disagree with you. Before going out to hunt any scaled mark I will look to see if it shows up on the USGS topo map. I usually use ACME Mapper because the crosshair allows me to center it on the benchmark X and then I can copy the lat/lon and paste it into the corrected coordinates for GSAK. -YOI-

I ran the new version (after fixing the backwards slash in your link) and looks like you have a little problem Appears you have accidentally dropped the Negative sign in front of the longitude so all my benchmarks are now in China -YOI-

duplicate

Speaking of meters...... Any way to make it an option to use feet instead? This is being plugging this into UserData2 and honestly it always throws me cause I still think in feet.

Thanks, that was an interesting read. Noticed he was hoping to add coordinate and photo submissions 'in the next couple months' -- that was 4 years ago. Made me think of a new question.... How then are the hand held coordinates submitted? I assumed these were coming from a different source than the NGS recover form since it has no place to submit coordinates (or photos as mentioned in the discussion). YOI UPDATE: I am guessing the HD_HELD1 & 2 have been in the specifications for quite a while -- they are not new -- just had not paid attention to them before this. Guessing there are only a few sheets out there where these show up?

Looking at some of the new sheets trying to figure out why my 'tools' quit working I noticed that the 'cooridinate' line has been changed quite a bit. At first I thought that they had just adjusted it, but now I see that instead of just NAD 83 (19xx) it might have NAD 83 (NSRS2007) -- so the possibility of the NSRS letters caused the realignment. The code section below shows the different possibilities now. Also I noticed that we used to have just 'ADJUSTED' or 'SCALED' at the end of these lines. Now there are 2 more 'Hand Held' possibilities. Will be interesting to get some of you more experienced guys to help me figure out the difference. My first question is, are 'scaled' still 'scaled' and HD_Held1 & 2 the equivalent of the old 'adjusted'? or do we now have gradations in between? Here is from around line 240 of the 'Tell Me More' doc for data sheets: Loading of the National Readjustment data commenced on September 14, 2007. Before this the format of the position and elevation lines appeared as follows: AA3495* NAD 83(CORS)- 39 08 02.34046(N) 077 13 15.51884(W) ADJUSTED AA3495* NAVD 88 - 140.76 (meters) 461.8 (feet) GPS OBS After the readjustment, the position and elevation lines on a datasheet will appear in a slightly modified format to accomodate the larger datum tag field (i.e. NSRS2007) as shown in the below examples. ______________________________________________________________ DF9012* NAD 83(NSRS2007)- 42 56 15.39233(N) 071 26 19.03487(W) ADJUSTED AA3495* NAD 83(CORS) - 39 08 02.34046(N) 077 13 15.51884(W) ADJUSTED RF0849* NAD 83(NSRS2007)- 46 52 08.05186(N) 068 00 53.02328(W) ADJUSTED TA0047* NAD 83(1986) - 48 04 54.20 (N) 090 45 48.42 (W) HD_HELD1 AC3384* NAD 83(1986) - 25 57 14.7 (N) 081 43 29.2 (W) HD_HELD2 HV0454* NAD 83(1986) - 38 20 52. (N) 076 13 39. (W) SCALED DX3756* NAD 83(NSRS2007)- 33 38 08.42412(N) 117 05 10.37961(W) ADJUSTED FQ0856* NAD 83(1986) - 35 47 36. (N) 111 52 56. (W) SCALED DB0356* NAVD 88 - -11.886 (meters) -39.00 (feet) READJUSTED DC2131* NAVD 88 - 1096.93 (meters) 3598.8 (feet) N HEIGHT AI5086* NAVD 88 - 123.68 (meters) 405.8 (feet) GPS OBS GP0162* NAVD 88 - 1456.97 (meters) 4780.1 (feet) RESET DE3069* NAVD 88 - 38.25 (meters) 125.5 (feet) GPS OBS GP0641* NAVD 88 - 1831.8 (meters) 6010. (feet) GPS OBS BW0768* NAVD 88 - 59.70 (+/-2cm) 195.9 (feet) VERTCON BW2469* NAVD 88 - 125. (meters) 410. (feet) SCALED FG1799* NAVD 88 - TV0377* LOCAL TIDAL - 7.2 (meters) 24. (feet) VERT ANG Thanks!

It is interesting that the NGS website has not kept up with the formats. The front page of the data sheets says: Last change to datasheet format was made on 01/01/06 yet the last entry on the NGS version histories page says: The format of the NATIONAL GEODETIC SURVEY Data Sheet was changed on 03/29/05 Version = 7.17. But of course the version that we have been using for quite a while is 7.49 I just looked for the oldest ngs dat file I still had, last year at this time I had version 7.37 DATABASE = Sybase ,PROGRAM = datasheet, VERSION = 7.37 1 National Geodetic Survey, Retrieval Date = AUGUST 1, 2006 Re the ' or " -- it is interesting that the Tell Me More link for datasheets does not use either, leaving just a space between the PID and the text. So it is amazing how this stuff has changed over time, and just like most of the stuff I do, the changes have not been documented. The 'Tell Me More' does seem to have been updated (even though it says nothing about ' or " for histories). This recent change is documented: Loading of the National Readjustment data commenced on September 14, 2007. Before this the format of the position and elevation lines appeared as follows: AA3495* NAD 83(CORS)- 39 08 02.34046(N) 077 13 15.51884(W) ADJUSTED AA3495* NAVD 88 - 140.76 (meters) 461.8 (feet) GPS OBS After the readjustment, the position and elevation lines on a datasheet will appear in a slightly modified format to accomodate the larger datum tag field (i.e. NSRS2007) as shown in the below examples. ______________________________________________________________ DF9012* NAD 83(NSRS2007)- 42 56 15.39233(N) 071 26 19.03487(W) ADJUSTED AA3495* NAD 83(CORS) - 39 08 02.34046(N) 077 13 15.51884(W) ADJUSTED RF0849* NAD 83(NSRS2007)- 46 52 08.05186(N) 068 00 53.02328(W) ADJUSTED TA0047* NAD 83(1986) - 48 04 54.20 (N) 090 45 48.42 (W) HD_HELD1 AC3384* NAD 83(1986) - 25 57 14.7 (N) 081 43 29.2 (W) HD_HELD2 HV0454* NAD 83(1986) - 38 20 52. (N) 076 13 39. (W) SCALED DX3756* NAD 83(NSRS2007)- 33 38 08.42412(N) 117 05 10.37961(W) ADJUSTED FQ0856* NAD 83(1986) - 35 47 36. (N) 111 52 56. (W) SCALED So, looking at this, not only has the 'NAD 83' column been modified, but we now have more than just 'Adjusted' and 'Scaled' at the end of the line.

Well, it appears that the new version of the datasheets has broken your parser. When I pull up a new set of sheets the first line had said version 7.49 but now it shows: DATABASE = Sybase ,PROGRAM = datasheet, VERSION = 7.50 When I run a diff on the files I notice that the 'space'characters have changed on the * NAD line: version 7.49: SA1190* NAD 83(1986)- 46 12 37. (N) 119 45 52. (W) SCALED SA1190* NAVD 88 - 203.929 (meters) 669.06 (feet) ADJUSTED version 7.50 SA1190* NAD 83(1986) - 46 12 37. (N) 119 45 52. (W) SCALED SA1190* NAVD 88 - 203.929 (meters) 669.06 (feet) ADJUSTED Notice the spaces after (1986) and the number of spaces between (N) and the coordinate. When I search and replace these so that the format matches for this line then the data file processes fine again. Looks like you might need to use some regex matching instead of straight column count? I am not sure how often they change the format. Gary UPDATE: It looks like the spacing was changed so that the columns would line up when the date looks like this: SD0042* NAD 83(NSRS2007)- 46 54 28.20193(N) 124 06 42.79448(W) ADJUSTED

I think we will try for this one too after the GH Cache Machine. Thanks for the heads up!

As I get ready for the cache machine I am wondering how to get the route into my 60csx? I already have all the caches in my gps using GSAK. I know I can add them each manually, but there has to be a better way. I really don't want to be searching for each one as we do the machine -- unless that is the best way to do it.

Yes, using GSAK to manage my waypoints I have 17,000 caches and 15,000 benchmarks stored in mine. The nice thing about using the GSAK macro to feed the POI Loader is that I actually have different icons for each cache type, just like the gc.com web page.

Before trying to figure out the problem, where did you find v0.5.0.232 or was that a typo? I believe the current version is 1.0.1.83 and available at http://ngs.tsqmadness.com. There were some early versions that drag and drop did not work, you had to actually use the DOS command line, but that has been fixed.

Congrats Patudles!

Best source/price I have found for the Safety Vest ($18.05)and Hard Hat ($9.55) is Costco.

Sorry so late on getting it posted here, but just in case anyone wants to come where we can guarantee 400 days of sunshine a year.... 2nd Annual GCSEWA Cache-aholics Geo-Picnic 2007 Attention GeoCachers of South Eastern Washington and beyond. It's a Family-Friendly gathering, so bring the kids! Where: Howard Amon Park in Richland, near Sturgeon Cove Playground. When: Saturday, September 15th from 11am-3pm

True but Sluggo is listed as a co-hider and he is still active. The cache does not show signs of distress so at this time I don't see an impending need for it to be adopted. I will try contacting him, but he now lives in Birmingham, Alabama. He had me adopt 2 of his other caches in the area (including Juniper Dunes). But I will check to see if he has the password for Citrix's account so we can change the text. I have run in to 2 cachers here lately who mentioned that they showed up for the monthly meeting mentioned in the cache page -- but we have not had a meeting there for over a year and probably 2.

I would like to adopt Cachers' Clubhouse. The owner has not logged on since August 2005.

No, your reasoning sounds right. I think it was just the number of destroyed markers it listed that I was curious about. BTW, used it again this weekend and it was great to be able to walk to the RMs since your program gives me the coordinates which are automatically loaded in the GPS. Found some that I doubt I would have otherwise.