blog lan!

4 Augen, 2 Nasen, 1 Blog

blog lan! RSS Feed
 
 
 
 

Found2Log english version

My little application made its way to the non german speaking area. Today I finally found some time to do the translation of the “Found2Log”-application.

Found2Log english version

important: this application needs MS .net-Framework 2.0

Feel free to contact me using the comment form on this site.

4 Kommentare to “Found2Log english version”

  1. Matt Says:

    Thanks for making this app available in English!

    What GPS is it intended for? The .fnd files from my Magellan Explorist 500 are parsed correctly, but the geocache names are only 8 characters long. Clicking the cache name in the list leads to an URL like this:

    http://www.geocaching.com/seek/cache_details.aspx?wp=RiceLake

    In other words, the .fnd file does not seem to contain enough information to build a link to the geocache page on geocaching.com.

    Thanks for any ideas you might have.

  2. tanja Says:

    Hi Matt,

    sorry for the late answer. We don’t have an explorist annymore, but we had an explorist 500 too. I guess the format of the .fnd file changed or we used to name waypoint with GC-Codes. The URL should have an GC-Code like GC01234 at the end.

    Could this help?

  3. Matt Says:

    I figured out the problem!

    The issue was in how I had created the .gs file from the .gpx file. I used GSAK, but I didn’t have it set up right and it did not put the cache’s GC code in the “name” field. Therefore, the wrong name got logged in the .fnd file leading to the broken link in Found2Log.

    Now, I use GPS Babel to convert .gpx to .gs for my Magellan, filtering out logged finds. This puts the GC code in the right field, making the .fnd file formatted properly.

  4. tanja Says:

    Thanks for your solution. We used (and still use) GSAK, so it should be a configuration issue.

Kommentar schreiben