Jump to content

YeOleImposter

+Premium Members
  • Posts

    429
  • Joined

  • Last visited

Posts posted by YeOleImposter

  1. Program has been working well! 2 feature requests I have thought of while using it:

     

    1) Make ignoring destroyed markers the default. I end up editing my ngs.dat file to not include the text at the end so that I don't have to deal with them.

     

    2) could the output of the program go to a file? Not sure it is really needed but it whizzes by so quickly I wonder sometimes if I missed something. I guess I could just pipe the output myself, but others may not know know how to do that.

     

    BTW, I have edited the FindStatGen macro to produce my benchmark statistics. My numbers are not very impressive compared to the veterans here but it is fun to have the statistics.

     

    Here is a link: YeOleImposter BMark Stats

     

    I still want to tweak some stuff, like figuring out a way to add DNF data -- but for now it has the important stuff.

  2. I just was in Kootenai county in northern Idaho and recovered a few benchmarks there. Can't wait to see some color there!

     

    Looks like I need to make some stops also along both sides of the Columbia River between Washington and Oregon, hard to believe there are 8 white counties there!

  3. I can preview the search on the Pocket Query page, and it generated 500 caches which are displayed as 25 pages of 20 caches. I can select all on one of those 25 pages and click 'Download Waypoints', but I havve to repeat that on all 25 pages. How do I get a Pocket query to run and email me a ZIP file immediately? I know I can schedule it, but I want it immediately I have generated the query.

     

    Just a side note. If it generated 500 waypoints then you did not get them all! The PQ will only list 500 -- If there are 600 caches in that vicinity then 100 are missing -- and I have not seen anything saying it is the furthest ones away that are left out -- so random caches will be missing from your list. In other words, always make sure your PQ returns less than 500 caches.

  4. OK, so I downloaded your latest, ran the net frameworks 2.0 when I drop a .dat file on the .exe file I only get this far:

     

    <?xml version="1.0" encoding="utf-8"?>

    ... deleted text ...

    </gpx>

     

    If I double click the .exe I get a standard windows error report.

     

    Any ideas?

     

    Thanks

     

    I probably should have said something earlier about this, but same thing happens to me.

    I thought it was just my windows setup.

    I cannot drag and drop either -- I have to run the program from the dos box --

     

    ngs-gpx.exe county.dat

    (where county.dat is the file I want to convert)

     

    But I have same problem with other programs too -- so just thought it was me.

     

    This is a great program! I have just finished updating about 6 counties in my area (nearly 10,0000 benchmarks) and it is doing a great job. Look forward to a better formula for the projecting the reference marks.

     

    I also added the following lines in long.html so I would have the box score as part of the description:

     

      <tr>
    <td class="tbldataheader">Reference:</td>
    <td class="tbldata"><pre>%%referencebox%%</pre></td>
     </tr>
    

  5.  CK4224|---------------------------------------------------------------------|
    CK4224| PID	Reference Object					 Distance	  Geod. Az  |
    CK4224|														   dddmmss.s |
    CK4224| CK4225 MILLEN MUN TANK					 APPROX. 4.9 KM 1152117.6 |
    CK4224| AB3554 MILLEN LOT						  APPROX. 9.0 KM 1312312.2 |
    CK4224| CK5617 ZOMBIE RM 3						  28.981 METERS 13832	 |
    CK4224| CK5616 ZOMBIE RM 1						  30.017 METERS 14233	 |
    CK4224| CK5615 ZOMBIE AZ MK									   1460148.8 |
    CK4224| CK4240 ZOMBIE RM 2						  33.251 METERS 23609	 |
    CK4224| CK4241 ZOMBIE AZ MK 2					  APPROX. 0.8 KM 2361037.1 |
    CK4224|---------------------------------------------------------------------|

     

    I believe Mike is working on this so that these marks can be added as child waypoints in GSAK, and therefore can be loaded in the GPS at the same time you are loading all the benchmarks.

     

    Question: Which of these PIDs should be created/searched for?

    - Do you ever search for the ones with "Approx" distances? And would the coordinate created be anywhere near close enough to be useful?

    - The AZ Mark never seems to have a distance -- so even though I like to hunt for these, I don't think there is a way to create a coordinate for it.

  6. New release! :rolleyes:

     

    Release: 08/27/07 0.7.0.42

    Changes:

    2. 'short.html' changed to 'long.html', new 'short.html' included. Got one you want to show off? It's

    probably better than mine. Send it my way, and I'll include it with the program!

     

    Looks like the new "short.html" did not get included. The one in the zip file is dated 8/24 and has the same missing "</style>" style statement at the end of that section. Am real curious what the new one was going to look like <_<

  7. I used to transfer from cachemate to my Etrex Legend using the serial port on the legend. I am sure the same could be done on the 60csx -- although I am not sure why would need to. Using GSAK I have all the caches in Washington (and lots in Oregon and Idaho) on my GPS as Points of Interest.

     

    When I was limited to 1000 waypoints I needed to xfer while on the road. Now I have every cache I may ever run across already on my 60csx.

  8. I have been wanting to work on an updated bmgpx program for a long time, someone has beat me to it (thankfully). Foxtrot_xray over at the GSAK forum is working on a great utility that will parse the ngs datasheet files and put them into a gpx file that you can use in whatever program you wish. We are using GSAK but I am sure it could be used by any .gpx program.

     

    I really like that the short description is completely user defined -- you can have it output anyway you want.

     

    Check it out, see if you can use it, give some suggestions to the author. I sure have, and he may tire of me :(

     

    08/20/07 0.5.0.232 Initial Release

    - The Benchmark's URL is pointed to NGS's datasheet, not GC.com.

    - The short description is read from an HTML template file ('short.html', must be in executing directory with ngs-gpx.exe). You can make the HTML file any way you want, and use tags (like "%%latdec%%") that the program will substitute.

    - The full datasheet is included in the Long Description.

    - If available, the "Place Date" is the first listed date in the History section. The "Placed By" and the "Owner" are also the first listed in the History section. (If unavailable, the date is 1/1/1800, and the condition/person is "-Unknown-".)

    - I've had issues with BMGPX dropping certain datasheets. (Dunno why, haven't looked into it. But BMGPX when it reeads my entire state drops about 3k of the 17k that Georgia has.) I made sure that my program can handle it all and not 'lose' records.

    - Support is in place for GPX 1.1 smile.gif It's not used yet, but if it ever is put into use by GSAK, this little bugger's ready.

    - Semi-Support for Destroyed marks. If there's a destroyed mark in your TXT file, it'll get loaded into the GPX with the reason it's unpublishable. (See note below.)

     

    08/24/07 0.6.0.16

    Changes:

    1. Modified HTML to produce a cleaner (and more HTML-correct) file for GSAK to use for the 'short description'

    2. Disabled the 1/1/1800 date, making it the next valid date found. (In case of NO VALID DATES, it will still be 01/01/1800 however.)

    3. The COUNTY from the datasheet is now put into the COUNTRY field in the GPX for importing.

    4. Found descriptions as all put into 'logs'. Long description is still full datasheet for now, and no date/whom/condition is transferred along with each log. (See TODO)

    5. The coordinate type is stored in the "Container" field. GSAK will accept this, however the user will have to note that if editing the waypoint and the 'Container' field is accidently changed, there's no easy way to set it back to it's default. Editing will also show the 'closest match' in it's pre-defined list to what the type is. (i.e. "Scaled" will show "Small" in the drop-down list.) As long as it's not changed, it won't get updated.

    6. The string ALTUTIDE (TYPE) is now put into the USER2 field in GSAK.

     

    Things Todo:

    -------------

    1. The reading and parsing of the History section needs to be redone. Once it is, it will add functionalityto adding the descriptions into the LOG section of the GPX file.

    2. Figure out what to put in the long description. (Options to consider are: First description. All descriptions. Full Datasheet.)

    3. Add options to running program:

    3A. Disable Altitude in User2 field.

    3B. Enable passing of own URL to use.

  9. I would like to see a GSAK macro that reads the dat files and creates a 'real' gsak file. I use bm2gpx but I don't think it would be too hard to create a macro that would put the original description in as the description and all the logs as actual logs. Then all the reference marks can be put in as child waypoints.

     

    then can use the macro that is already out there that can read the logs on gc.com and add them to the ngs logs already parsed.

     

    I have written a rough flow chart for the macro but am not finding the time to put it into real code.e

  10. I have tried a number of different things. Outdoor Navigator worked well while it was available for Topo Maps but they quit selling the product.

     

    I was just going to suggest Mapopolis, but when I go to their site it says that they have discontinued all direct to consumer sales -- so now I don't know what to suggest. Will be watching to see what others suggest

  11. Very cool application! I have bookmarked it for regular use. Nice to be able to get a quick visual of the Adjusted/Scaled Reported/Unreported status of benchmarks in the area.

     

    One addition that would make this even more valuable is if you could incorporate Topo maps into it like http://mapper.acme.com has. I use this map all time out of GSAK.

     

    Thanks again!!

  12. I stand corrected. It would be good if the NGS history showed that it was the original stone that was cut down.

     

    I would not register a disk that replaced a drill hole unless the NGS data sheet showed the history that this is what happened.

     

    Maybe someone can forward Deb the email from the surveyor so that it can be included in the history.

  13. (I just about deleted this post after I put it together because I really am not trying to beat a dead horse (or benchmark) but figured I would go ahead and send it because if a metal disk placed by the park service in 1988 can be called a 'find' of 16-inch tall, 8-inch square stone post then what counts as a "not found"?)

     

    Look close at the disk and you'll see it is set in a "Cut stone" that may or may not be 18" high. With the concrete surrounding both the plaque and stone marker it is hard to say how tall it is.

     

    The marker type is "Stone Monument" and without being there in person the 'disk' is set in stone and not in concrete. How big the cut stone is, is hard to tell from the pictures. If they removed the 'Brass Screw' and replaced it with a 'disk' does it become a reset if the disk is put into the repaired 'stone monument'?

    The 'cut stone' is Zero inches high. I went back and looked at the photos in GC.com and the stone is flush with the ground. And the photo from BeanTeam shows that if nothing else, that 16" of dirt was not mounded up to the top of the monument and a disk placed on the pointy spire of the monument.

     

    Question. If a brass disk marked "benchmark 1903" is lost and a new one marked "benchmark 1908 - 1984" is placed over the same spot, should it be counted as a find of "benchmark 1903"?

     

    You are quite right that this monument is still part of the original stone, the top has been removed, but this is still the original mark.

    I guess I am not sure how we know that the "monument is still part of the original stone" - Nothing I read at the site indicates that anything was saved from the original stone or how they cut it down from 16" to 0" after it was vandalized.

     

    I guess I am just confused since the discussion of a true 'find' here in the forum can get so technical. Here we have no idea if the whole monument was removed by vandals (or state park personnel after it was vandalized) and a flat stone with a shiny commemorative disk was placed by the park service (not any survey crew) and it is considered a find.

     

    <sarcasm>

    If I am looking for a 'chiseled square' and find a disk named 'chiseled square' near the location, would that count as 'found'?

    </sarcasm>

     

    And, BeanTeam - thanks for the photo!

     

    261278709_d55641d21c_o.jpg

×
×
  • Create New...