sirclimbsalot

I'm sure that level of thought really means a lot to the cache owners... How about a new log type "FBDCETTYAME" - Found but don't care enough to tell you about my experience. actually, this wasn't what i had in mind. I find that if i have 30 caches to log in a weekend and i'm leaving again in a week and i'm really busy, i just start to cut and paste. if I know someone or its a great cache, then I post something longer. if I could format one file then upload it, then it saves my an hour of logging.

I tend to write my logs in my palm as I do them, but it would really be nice to port it to a standard file for submisson. what I hate is doing a 7-day caching vacation, writing them once, then writting them again. Its not really a question of laziness.

There has been many of time where I've come back from a geocaching weekend and had over 30 caches to log. Could a feature be added for mulitple uploads? something as easy as a tab delimited file with basic headers is all that would be needed. example: GCXXX1 date comment found GCXXX2 date comment DNF GCXXX3 date comment needs maintaince *simple numbers could be used as well (found=1 DNF=2 etc.) a simple confirmation page with errors posted in red would help too.

present

this is a simple perl script written using XML::DOM (which I think is standard now). its makes a text summary of geocaching.com .gpx files. You should be able to figure out which fields are which by the tag names. the html_simple sub is not ideal for all html but seems to work fine for gpx long and short descriptions. ---SCAL ============================================ #!/usr/bin/perl -w # Matthew Ketterling 2005 # mattk470 at hotmail dot com # free to use and edit when proper credit is given. use strict; use warnings; use XML::DOM; my $file = 'c:\perl\infile.gpx'; # .gpx file location and name my $outputfile = 'c:\perl\outfile.txt'; #.txt output file location and name my $parser = XML::DOM::Parser->new(); my $gpx = $parser->parsefile($file); open (OUT, ">".$outputfile) || die "Could not open $outputfile"; my $srtdesc; my $lngdesc; # parses XML file foreach my $waypoint ($gpx->getElementsByTagName('wpt')) { print OUT "-",$waypoint->getElementsByTagName('name')-> item(0) -> getFirstChild->getNodeValue," "; print OUT $waypoint -> getAttribute('lat')," "; print OUT $waypoint -> getAttribute('lon'),"\n"; print OUT $waypoint->getElementsByTagName('Groundspeak:name')-> item(0) -> getFirstChild->getNodeValue," by the "; print OUT $waypoint->getElementsByTagName('Groundspeak:owner')-> item(0) -> getFirstChild->getNodeValue,"\n"; print OUT $waypoint->getElementsByTagName('Groundspeak:container')-> item(0) -> getFirstChild->getNodeValue," "; print OUT $waypoint->getElementsByTagName('Groundspeak:type')-> item(0) -> getFirstChild->getNodeValue," \("; print OUT "D:",$waypoint->getElementsByTagName('Groundspeak:difficulty')-> item(0) -> getFirstChild->getNodeValue,"\/"; print OUT "T:",$waypoint->getElementsByTagName('Groundspeak:terrain')-> item(0) -> getFirstChild->getNodeValue,"\)\n"; print OUT "SD= ",$srtdesc = gpx_remhtml_smpl($waypoint->getElementsByTagName('Groundspeak:short_description')-> item(0) -> getFirstChild->getNodeValue),"\n"; print OUT "LD= ",$lngdesc = gpx_remhtml_smpl($waypoint->getElementsByTagName('Groundspeak:long_description')-> item(0) -> getFirstChild->getNodeValue),"\n"; print OUT "HINT= ",$waypoint->getElementsByTagName('Groundspeak:encoded_hints')-> item(0) -> getFirstChild->getNodeValue,"\n"; print OUT "\n"; } close (OUT); exit(0); sub gpx_remhtml_smpl { my ($text) = @_; ($text = $text) =~ s/<[^>]*>//gs; $text =~ s/\r/\n/gs; $text =~ s/\n/ /gs; while ($text =~ m/ /gs) { $text =~ s/ / /gs; } $text =~ s/ //gs; return $text; }

You mean besides Pocket Queries? or an option in pocket quaries that you can don't need an ebook reader

if there was an option of basic text or even better a xml version of the output in addition of propriatory ebook format or pdf. this would leave things wide open for computer programmers to make custom lists of the data.

first off, I didn't read all the posts. secondly its not that hard to do on a programming standpoint. All you would have to do is give the program a few main waypoints and a distance from the route. using the waypoints you can generate a rough path (this rough path would be broken up into 5 or 10%increments or 10 mile increments if you weren't worried about processing time) and the distance would be enough to report back all the caches within that area. there will be duplicates if you search with each sub-waypoint so a remove duplicates function would have to be included to get a non-redundant list.

looking for someone who's done one or suggestions for fun placements

is there a way to download gpx files in bulk and parse them yourself with perl scripts? I'm tired of downloading 20 .loc files at a time and only having partial info. Am i missing something?