Order Tray | Contact Us | Home | SIG Lists

[aprssig] weigh your toilet paper

canoeman at qnet.com canoeman at qnet.com
Mon Dec 22 03:21:04 UTC 2008


I have actually hiked the AP, and the Pacific Crest Trail.
The people who do this, actually weigh toilet paper or go AU Natural.
The chances of a thru hiker carrying an aprs are zero.
BUT, that's OK.
the more likely scenario is friends of the trail allowing the hikers to check
in
some how.
with out carrying a digi.
Its a sub culture as foreign to ham radio as any other possible sub culture.
So, the best way to make the trail usable to thru hikers is to install a time
clock type of system to allow the hikers to use the system, but not carry it.
This is where the friends of the trail come in.
They will assist in  the placement of the devices to be  used by the hikers and
others, as not to interfere with the spiritual act of hiking the trail.
We must be their enablers. we must not burden their quest.
Technology is not on the  top ten list of thru hikers.
This would make a fantastic project for hams in the west and the east, making
the introduction of the safety of APRS to the thru hiking nation.
This could open up a huge public service project to hams, well allowing them to
spend time out in the woods instead of in front of a glowing screen, eating
cheetos.But we must tread carefully.
Transparency is the goal.We CAN make a DIFFERENCE.
This is a wonderful chance to open up ham radio to  an entirety new audience.
Lets get planning on this now, as  the 09 season is approaching faster then 
lightning.I'm in on the west coast, socal area.

73 de ke6anm

ke6anm at arrl.org


















Quoting aprssig-request at tapr.org:

> Send aprssig mailing list submissions to
> 	aprssig at tapr.org
> 
> To subscribe or unsubscribe via the World Wide Web, visit
> 	https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig
> or, via email, send a message with subject or body 'help' to
> 	aprssig-request at tapr.org
> 
> You can reach the person managing the list at
> 	aprssig-owner at tapr.org
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of aprssig digest..."
> 
> 
> Today's Topics:
> 
>    1. APRS Parser (Bob Bruninga )
>    2. Re: APRS Parser (Andrew Rich)
>    3. Re: APRS Parser (Lynn W. Deffenbaugh (Mr))
>    4. Re: APRS Parser (Andrew Rich)
>    5. Re: APRS Parser (Lynn W. Deffenbaugh (Mr))
>    6. Re: APRS Parser (Andrew Rich)
>    7. Re: APRS Parser (Lynn W. Deffenbaugh (Mr))
>    8. Appalacian TRail and ham radio (Bob Bruninga )
>    9. Re: Appalacian TRail and ham radio (Lynn W. Deffenbaugh (Mr))
>   10. Re: APRS Parser (Andrew Rich)
>   11. Re: APRS Parser (Lynn W. Deffenbaugh (Mr))
>   12. Re: Appalacian TRail and ham radio (Jason KG4WSV)
>   13. Re: Appalacian TRail and ham radio (Jack Spitznagel)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Sat, 20 Dec 2008 10:30:21 -0500 (EST)
> From: "Bob Bruninga " <bruninga at usna.edu>
> Subject: [aprssig] APRS Parser
> To: TAPR APRS Mailing List <aprssig at tapr.org>
> Message-ID: <20081220103021.AIL09437 at mp3.nettest.usna.edu>
> Content-Type: text/plain; charset=us-ascii
> 
> Subject was: Re: [aprssig] Field station  
> 
> >> I'm pretty sure there's a perl APRS 
> >> parser somewhere, 
> 
> The gold standard for APRS parsing in pseudo code English is on the
> www.aprs.org web site:
> 
> http://www.aprs.org/txt/APRS-parser.txt
> 
> This is the full commented parser from the original APRSdos.  It is good up
> through APRS1.1 and much of APRS1.2.  The newest things in APRS1.2 that I
> need to add are:
> 
> 1) The new Mic-E Type definitions so that you can recognize Yaesu, and
> TinyTraks, and other future manufacturers.
> 
> 2) The new ITEM-IN-MESSAGE format
> 
> 3) FREQ-IN-MESSAGE format if your code also has RIG tuning control.
> 
> 4) FREQUNECY parser for tabular display
> 
> 5) OPERATOR PRESENT BIT ("O" overlay on most symbols)
> 
> 6) PRIORITY BIT:  (uses the case of the E/W byte)
> 
> 7) SKY COMMAND Parsing and display of community remotes
> 
> 8) EMERGENCY codes for non Mic-E systems
> 
> 9) The !DAO! high precision parser
> 
> Ill update the parser page above so that it is complete, when I get back from
> travel.
> 
> Bob, Wb4APR
> 
> 
> 
> 
> 
> ------------------------------
> 
> Message: 2
> Date: Sun, 21 Dec 2008 05:29:23 +1000
> From: "Andrew Rich" <vk4tec at tech-software.net>
> Subject: Re: [aprssig] APRS Parser
> To: "TAPR APRS Mailing List" <aprssig at tapr.org>
> Message-ID: <00b701c962d9$44642990$6501a8c0 at Laptop1520>
> Content-Type: text/plain; charset="iso-8859-1"
> 
> DOS
> 
> Will that even work with Windows XP ?
> 
> Bob  i need to bring you into this century
>   ----- Original Message ----- 
>   From: Bob Bruninga 
>   To: TAPR APRS Mailing List 
>   Sent: Sunday, December 21, 2008 1:30 AM
>   Subject: [aprssig] APRS Parser
> 
> 
>   Subject was: Re: [aprssig] Field station  
> 
>   >> I'm pretty sure there's a perl APRS 
>   >> parser somewhere, 
> 
>   The gold standard for APRS parsing in pseudo code English is on the
> www.aprs.org web site:
> 
>   http://www.aprs.org/txt/APRS-parser.txt
> 
>   This is the full commented parser from the original APRSdos.  It is good up
> through APRS1.1 and much of APRS1.2.  The newest things in APRS1.2 that I
> need to add are:
> 
>   1) The new Mic-E Type definitions so that you can recognize Yaesu, and
> TinyTraks, and other future manufacturers.
> 
>   2) The new ITEM-IN-MESSAGE format
> 
>   3) FREQ-IN-MESSAGE format if your code also has RIG tuning control.
> 
>   4) FREQUNECY parser for tabular display
> 
>   5) OPERATOR PRESENT BIT ("O" overlay on most symbols)
> 
>   6) PRIORITY BIT:  (uses the case of the E/W byte)
> 

>   7) SKY COMMAND Parsing and display of community remotes
> 
>   8) EMERGENCY codes for non Mic-E systems
> 
>   9) The !DAO! high precision parser
> 
>   Ill update the parser page above so that it is complete, when I get back
> from travel.
> 
>   Bob, Wb4APR
> 
> 
> 
>   _______________________________________________
>   aprssig mailing list
>   aprssig at tapr.org
>   https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig
> 
> 
>
------------------------------------------------------------------------------
> 
> 
> 
>   No virus found in this incoming message.
>   Checked by AVG - http://www.avg.com 
>   Version: 8.0.176 / Virus Database: 270.9.19/1857 - Release Date: 12/19/2008
> 10:09 AM
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
>
http://www.tapr.org/pipermail/aprssig/attachments/20081221/082f1e0d/attachment.html
> 
> 
> ------------------------------
> 
> Message: 3
> Date: Sat, 20 Dec 2008 14:36:50 -0500
> From: "Lynn W. Deffenbaugh (Mr)" <ldeffenb at homeside.to>
> Subject: Re: [aprssig] APRS Parser
> To: TAPR APRS Mailing List <aprssig at tapr.org>
> Message-ID: <494D4952.9030506 at homeside.to>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> 
> He said it was "pseudo code English" which runs most effectively on this 
> really cool bio-mechanical homo-sapien gray-matter stuff but is readily 
> translated to other languages and operating systems within that native 
> environment.
> 
> Lynn (D) - KJ4ERJ - Professionally employed HSGMS translator
> 
> Andrew Rich wrote:
> > DOS
> >  
> > Will that even work with Windows XP ?
> >  
> > Bob  i need to bring you into this century
> >
> >     ----- Original Message -----
> >     *From:* Bob Bruninga <mailto:bruninga at usna.edu>
> >     *To:* TAPR APRS Mailing List <mailto:aprssig at tapr.org>
> >     *Sent:* Sunday, December 21, 2008 1:30 AM
> >     *Subject:* [aprssig] APRS Parser
> >
> >     Subject was: Re: [aprssig] Field station 
> >
> >     >> I'm pretty sure there's a perl APRS
> >     >> parser somewhere,
> >
> >     The gold standard for APRS parsing in pseudo code English is on
> >     the www.aprs.org <http://www.aprs.org> web site:
> >
> >     http://www.aprs.org/txt/APRS-parser.txt
> >
> >     This is the full commented parser from the original APRSdos.  It
> >     is good up through APRS1.1 and much of APRS1.2.  The newest things
> >     in APRS1.2 that I need to add are:
> >
> >     1) The new Mic-E Type definitions so that you can recognize Yaesu,
> >     and TinyTraks, and other future manufacturers.
> >
> >     2) The new ITEM-IN-MESSAGE format
> >
> >     3) FREQ-IN-MESSAGE format if your code also has RIG tuning control.
> >
> >     4) FREQUNECY parser for tabular display
> >
> >     5) OPERATOR PRESENT BIT ("O" overlay on most symbols)
> >
> >     6) PRIORITY BIT:  (uses the case of the E/W byte)
> >
> >     7) SKY COMMAND Parsing and display of community remotes
> >
> >     8) EMERGENCY codes for non Mic-E systems
> >
> >     9) The !DAO! high precision parser
> >
> >     Ill update the parser page above so that it is complete, when I
> >     get back from travel.
> >
> >     Bob, Wb4APR
> >
> >
> >
> >     _______________________________________________
> >     aprssig mailing list
> >     aprssig at tapr.org <mailto:aprssig at tapr.org>
> >     https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig
> >
> >    
> ------------------------------------------------------------------------
> >
> >     No virus found in this incoming message.
> >     Checked by AVG - http://www.avg.com
> >     Version: 8.0.176 / Virus Database: 270.9.19/1857 - Release Date:
> >     12/19/2008 10:09 AM
> >
> > ------------------------------------------------------------------------
> >
> > _______________________________________________
> > aprssig mailing list
> > aprssig at tapr.org
> > https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig
> >   
> 
> 
> 
> 
> ------------------------------
> 
> Message: 4
> Date: Sun, 21 Dec 2008 05:56:38 +1000
> From: "Andrew Rich" <vk4tec at tech-software.net>
> Subject: Re: [aprssig] APRS Parser
> To: "TAPR APRS Mailing List" <aprssig at tapr.org>
> Message-ID: <00d401c962dd$14d30d00$6501a8c0 at Laptop1520>
> Content-Type: text/plain; charset="iso-8859-1"
> 
> Just having a dig
> 
> Bob does some stuff I have never seen on DOS ;-)
> 
> 
>   ----- Original Message ----- 
>   From: Lynn W. Deffenbaugh (Mr) 
>   To: TAPR APRS Mailing List 
>   Sent: Sunday, December 21, 2008 5:36 AM
>   Subject: Re: [aprssig] APRS Parser
> 
> 
>   He said it was "pseudo code English" which runs most effectively on this 
>   really cool bio-mechanical homo-sapien gray-matter stuff but is readily 
>   translated to other languages and operating systems within that native 
>   environment.
> 
>   Lynn (D) - KJ4ERJ - Professionally employed HSGMS translator
> 
>   Andrew Rich wrote:
>   > DOS
>   >  
>   > Will that even work with Windows XP ?
>   >  
>   > Bob  i need to bring you into this century
>   >
>   >     ----- Original Message -----
>   >     *From:* Bob Bruninga <mailto:bruninga at usna.edu>
>   >     *To:* TAPR APRS Mailing List <mailto:aprssig at tapr.org>
>   >     *Sent:* Sunday, December 21, 2008 1:30 AM
>   >     *Subject:* [aprssig] APRS Parser
>   >
>   >     Subject was: Re: [aprssig] Field station 
>   >
>   >     >> I'm pretty sure there's a perl APRS
>   >     >> parser somewhere,
>   >
>   >     The gold standard for APRS parsing in pseudo code English is on
>   >     the www.aprs.org <http://www.aprs.org> web site:
>   >
>   >     http://www.aprs.org/txt/APRS-parser.txt
>   >
>   >     This is the full commented parser from the original APRSdos.  It
>   >     is good up through APRS1.1 and much of APRS1.2.  The newest things
>   >     in APRS1.2 that I need to add are:
>   >
>   >     1) The new Mic-E Type definitions so that you can recognize Yaesu,
>   >     and TinyTraks, and other future manufacturers.
>   >
>   >     2) The new ITEM-IN-MESSAGE format
>   >
>   >     3) FREQ-IN-MESSAGE format if your code also has RIG tuning control.
>   >
>   >     4) FREQUNECY parser for tabular display
>   >
>   >     5) OPERATOR PRESENT BIT ("O" overlay on most symbols)
>   >
>   >     6) PRIORITY BIT:  (uses the case of the E/W byte)
>   >
>   >     7) SKY COMMAND Parsing and display of community remotes
>   >
>   >     8) EMERGENCY codes for non Mic-E systems
>   >
>   >     9) The !DAO! high precision parser
>   >
>   >     Ill update the parser page above so that it is complete, when I
>   >     get back from travel.
>   >
>   >     Bob, Wb4APR
>   >
>   >
>   >
>   >     _______________________________________________
>   >     aprssig mailing list
>   >     aprssig at tapr.org <mailto:aprssig at tapr.org>
>   >     https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig
>   >
>   >    
> ------------------------------------------------------------------------
>   >
>   >     No virus found in this incoming message.
>   >     Checked by AVG - http://www.avg.com
>   >     Version: 8.0.176 / Virus Database: 270.9.19/1857 - Release Date:
>   >     12/19/2008 10:09 AM
>   >
>   > ------------------------------------------------------------------------
>   >
>   > _______________________________________________
>   > aprssig mailing list
>   > aprssig at tapr.org
>   > https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig
>   >   
> 
> 
>   _______________________________________________
>   aprssig mailing list
>   aprssig at tapr.org
>   https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig
> 
> 
>
------------------------------------------------------------------------------
> 
> 
> 
>   No virus found in this incoming message.
>   Checked by AVG - http://www.avg.com 
>   Version: 8.0.176 / Virus Database: 270.9.19/1857 - Release Date: 12/19/2008
> 10:09 AM
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
>
http://www.tapr.org/pipermail/aprssig/attachments/20081221/0cbbf9c5/attachment-0001.htm
> 
> 
> ------------------------------
> 
> Message: 5
> Date: Sat, 20 Dec 2008 15:06:47 -0500
> From: "Lynn W. Deffenbaugh (Mr)" <ldeffenb at homeside.to>
> Subject: Re: [aprssig] APRS Parser
> To: TAPR APRS Mailing List <aprssig at tapr.org>
> Message-ID: <494D5057.9040106 at homeside.to>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> 
> I couldn't resist throwing a dig right back also.  All in fun.  The best 
> part of the old DOS commands is that most of them still work in Windows 
> Vista's default Command Prompt!
> 
> for %f in (test??x.png) do %f
> 
> Lots faster than trying to identify a bunch of similarly-named PNG files 
> and opening them in the default PNG viewer via a mouse!
> 
> Lynn (D) - KJ4ERJ - Apparently of Bob's vintage!
> 
> Andrew Rich wrote:
> > Just having a dig
> >  
> > Bob does some stuff I have never seen on DOS ;-)
> >  
> >  
> >
> >     ----- Original Message -----
> >     *From:* Lynn W. Deffenbaugh (Mr) <mailto:ldeffenb at homeside.to>
> >     *To:* TAPR APRS Mailing List <mailto:aprssig at tapr.org>
> >     *Sent:* Sunday, December 21, 2008 5:36 AM
> >     *Subject:* Re: [aprssig] APRS Parser
> >
> >     He said it was "pseudo code English" which runs most effectively
> >     on this
> >     really cool bio-mechanical homo-sapien gray-matter stuff but is
> >     readily
> >     translated to other languages and operating systems within that
> >     native
> >     environment.
> >
> >     Lynn (D) - KJ4ERJ - Professionally employed HSGMS translator
> >
> >     Andrew Rich wrote:
> >     > DOS
> >     > 
> >     > Will that even work with Windows XP ?
> >     > 
> >     > Bob  i need to bring you into this century
> >     >
> >     >     ----- Original Message -----
> >     >     *From:* Bob Bruninga <mailto:bruninga at usna.edu>
> >     >     *To:* TAPR APRS Mailing List <mailto:aprssig at tapr.org>
> >     >     *Sent:* Sunday, December 21, 2008 1:30 AM
> >     >     *Subject:* [aprssig] APRS Parser
> >     >
> >     >     Subject was: Re: [aprssig] Field station
> >     >
> >     >     >> I'm pretty sure there's a perl APRS
> >     >     >> parser somewhere,
> >     >
> >     >     The gold standard for APRS parsing in pseudo code English is on
> >     >     the www.aprs.org <http://www.aprs.org> <http://www.aprs.org>
> >     web site:
> >     >
> >     >     http://www.aprs.org/txt/APRS-parser.txt
> >     >
> >     >     This is the full commented parser from the original APRSdos.  It
> >     >     is good up through APRS1.1 and much of APRS1.2.  The newest
> >     things
> >     >     in APRS1.2 that I need to add are:
> >     >
> >     >     1) The new Mic-E Type definitions so that you can recognize
> >     Yaesu,
> >     >     and TinyTraks, and other future manufacturers.
> >     >
> >     >     2) The new ITEM-IN-MESSAGE format
> >     >
> >     >     3) FREQ-IN-MESSAGE format if your code also has RIG tuning
> >     control.
> >     >
> >     >     4) FREQUNECY parser for tabular display
> >     >
> >     >     5) OPERATOR PRESENT BIT ("O" overlay on most symbols)
> >     >
> >     >     6) PRIORITY BIT:  (uses the case of the E/W byte)
> >     >
> >     >     7) SKY COMMAND Parsing and display of community remotes
> >     >
> >     >     8) EMERGENCY codes for non Mic-E systems
> >     >
> >     >     9) The !DAO! high precision parser
> >     >
> >     >     Ill update the parser page above so that it is complete, when I
> >     >     get back from travel.
> >     >
> >     >     Bob, Wb4APR
> >     >
> >     >
> >     >
> >     >     _______________________________________________
> >     >     aprssig mailing list
> >     >     aprssig at tapr.org <mailto:aprssig at tapr.org>
> >     <mailto:aprssig at tapr.org>
> >     >     https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig
> >     >
> >     >    
> >    
> ------------------------------------------------------------------------
> >     >
> >     >     No virus found in this incoming message.
> >     >     Checked by AVG - http://www.avg.com
> >     >     Version: 8.0.176 / Virus Database: 270.9.19/1857 - Release Date:
> >     >     12/19/2008 10:09 AM
> >     >
> >     >
> >    
> ------------------------------------------------------------------------
> >     >
> >     > _______________________________________________
> >     > aprssig mailing list
> >     > aprssig at tapr.org <mailto:aprssig at tapr.org>
> >     > https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig
> >     >  
> >
> >
> >     _______________________________________________
> >     aprssig mailing list
> >     aprssig at tapr.org <mailto:aprssig at tapr.org>
> >     https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig
> >
> >    
> ------------------------------------------------------------------------
> >
> >     No virus found in this incoming message.
> >     Checked by AVG - http://www.avg.com
> >     Version: 8.0.176 / Virus Database: 270.9.19/1857 - Release Date:
> >     12/19/2008 10:09 AM
> >
> > ------------------------------------------------------------------------
> >
> > _______________________________________________
> > aprssig mailing list
> > aprssig at tapr.org
> > https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig
> >   
> 
> 
> 
> 
> ------------------------------
> 
> Message: 6
> Date: Sun, 21 Dec 2008 06:11:37 +1000
> From: "Andrew Rich" <vk4tec at tech-software.net>
> Subject: Re: [aprssig] APRS Parser
> To: "TAPR APRS Mailing List" <aprssig at tapr.org>
> Message-ID: <00f101c962df$2b26ec50$6501a8c0 at Laptop1520>
> Content-Type: text/plain; charset="iso-8859-1"
> 
> I have been playing with perl and GD
> 
> I am able to do the old pixel plots.
> 
> I have managed to hook in my ADS-B (APRS for planes)
> 
> And make my own tracking screens with complete freedom.
> 
> Maps and all !
> 
> Andrew 
>   ----- Original Message ----- 
>   From: Lynn W. Deffenbaugh (Mr) 
>   To: TAPR APRS Mailing List 
>   Sent: Sunday, December 21, 2008 6:06 AM
>   Subject: Re: [aprssig] APRS Parser
> 
> 
>   I couldn't resist throwing a dig right back also.  All in fun.  The best 
>   part of the old DOS commands is that most of them still work in Windows 
>   Vista's default Command Prompt!
> 
>   for %f in (test??x.png) do %f
> 
>   Lots faster than trying to identify a bunch of similarly-named PNG files 
>   and opening them in the default PNG viewer via a mouse!
> 
>   Lynn (D) - KJ4ERJ - Apparently of Bob's vintage!
> 
>   Andrew Rich wrote:
>   > Just having a dig
>   >  
>   > Bob does some stuff I have never seen on DOS ;-)
>   >  
>   >  
>   >
>   >     ----- Original Message -----
>   >     *From:* Lynn W. Deffenbaugh (Mr) <mailto:ldeffenb at homeside.to>
>   >     *To:* TAPR APRS Mailing List <mailto:aprssig at tapr.org>
>   >     *Sent:* Sunday, December 21, 2008 5:36 AM
>   >     *Subject:* Re: [aprssig] APRS Parser
>   >
>   >     He said it was "pseudo code English" which runs most effectively
>   >     on this
>   >     really cool bio-mechanical homo-sapien gray-matter stuff but is
>   >     readily
>   >     translated to other languages and operating systems within that
>   >     native
>   >     environment.
>   >
>   >     Lynn (D) - KJ4ERJ - Professionally employed HSGMS translator
>   >
>   >     Andrew Rich wrote:
>   >     > DOS
>   >     > 
>   >     > Will that even work with Windows XP ?
>   >     > 
>   >     > Bob  i need to bring you into this century
>   >     >
>   >     >     ----- Original Message -----
>   >     >     *From:* Bob Bruninga <mailto:bruninga at usna.edu>
>   >     >     *To:* TAPR APRS Mailing List <mailto:aprssig at tapr.org>
>   >     >     *Sent:* Sunday, December 21, 2008 1:30 AM
>   >     >     *Subject:* [aprssig] APRS Parser
>   >     >
>   >     >     Subject was: Re: [aprssig] Field station
>   >     >
>   >     >     >> I'm pretty sure there's a perl APRS
>   >     >     >> parser somewhere,
>   >     >
>   >     >     The gold standard for APRS parsing in pseudo code English is
> on
>   >     >     the www.aprs.org <http://www.aprs.org> <http://www.aprs.org>
>   >     web site:
>   >     >
>   >     >     http://www.aprs.org/txt/APRS-parser.txt
>   >     >
>   >     >     This is the full commented parser from the original APRSdos. 
> It
>   >     >     is good up through APRS1.1 and much of APRS1.2.  The newest
>   >     things
>   >     >     in APRS1.2 that I need to add are:
>   >     >
>   >     >     1) The new Mic-E Type definitions so that you can recognize
>   >     Yaesu,
>   >     >     and TinyTraks, and other future manufacturers.
>   >     >
>   >     >     2) The new ITEM-IN-MESSAGE format
>   >     >
>   >     >     3) FREQ-IN-MESSAGE format if your code also has RIG tuning
>   >     control.
>   >     >
>   >     >     4) FREQUNECY parser for tabular display
>   >     >
>   >     >     5) OPERATOR PRESENT BIT ("O" overlay on most symbols)
>   >     >
>   >     >     6) PRIORITY BIT:  (uses the case of the E/W byte)
>   >     >
>   >     >     7) SKY COMMAND Parsing and display of community remotes
>   >     >
>   >     >     8) EMERGENCY codes for non Mic-E systems
>   >     >
>   >     >     9) The !DAO! high precision parser
>   >     >
>   >     >     Ill update the parser page above so that it is complete, when
> I
>   >     >     get back from travel.
>   >     >
>   >     >     Bob, Wb4APR
>   >     >
>   >     >
>   >     >
>   >     >     _______________________________________________
>   >     >     aprssig mailing list
>   >     >     aprssig at tapr.org <mailto:aprssig at tapr.org>
>   >     <mailto:aprssig at tapr.org>
>   >     >     https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig
>   >     >
>   >     >    
>   >    
> ------------------------------------------------------------------------
>   >     >
>   >     >     No virus found in this incoming message.
>   >     >     Checked by AVG - http://www.avg.com
>   >     >     Version: 8.0.176 / Virus Database: 270.9.19/1857 - Release
> Date:
>   >     >     12/19/2008 10:09 AM
>   >     >
>   >     >
>   >    
> ------------------------------------------------------------------------
>   >     >
>   >     > _______________________________________________
>   >     > aprssig mailing list
>   >     > aprssig at tapr.org <mailto:aprssig at tapr.org>
>   >     > https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig
>   >     >  
>   >
>   >
>   >     _______________________________________________
>   >     aprssig mailing list
>   >     aprssig at tapr.org <mailto:aprssig at tapr.org>
>   >     https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig
>   >
>   >    
> ------------------------------------------------------------------------
>   >
>   >     No virus found in this incoming message.
>   >     Checked by AVG - http://www.avg.com
>   >     Version: 8.0.176 / Virus Database: 270.9.19/1857 - Release Date:
>   >     12/19/2008 10:09 AM
>   >
>   > ------------------------------------------------------------------------
>   >
>   > _______________________________________________
>   > aprssig mailing list
>   > aprssig at tapr.org
>   > https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig
>   >   
> 
> 
>   _______________________________________________
>   aprssig mailing list
>   aprssig at tapr.org
>   https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig
> 
> 
>
------------------------------------------------------------------------------
> 
> 
> 
>   No virus found in this incoming message.
>   Checked by AVG - http://www.avg.com 
>   Version: 8.0.176 / Virus Database: 270.9.19/1857 - Release Date: 12/19/2008
> 10:09 AM
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
>
http://www.tapr.org/pipermail/aprssig/attachments/20081221/62757d92/attachment-0001.htm
> 
> 
> ------------------------------
> 
> Message: 7
> Date: Sat, 20 Dec 2008 15:54:10 -0500
> From: "Lynn W. Deffenbaugh (Mr)" <ldeffenb at homeside.to>
> Subject: Re: [aprssig] APRS Parser
> To: TAPR APRS Mailing List <aprssig at tapr.org>
> Message-ID: <494D5B72.8070602 at homeside.to>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> 
> Interesting timing!  I've spent the day working with GD and 
> OpenStreetMaps.org to visualize and plot various APRS-IS collected 
> data!  If you've not heard of OpenStreetMaps.org, check them out.  A 
> free map source with tiles of various zoom levels that are stitchable to 
> make any arbitrary map with details.  Of particular programmer interest 
> is http://wiki.openstreetmap.org/index.php/Slippy_map_tilenames
> 
> Lynn (D) - KJ4ERJ - Author of APRS-IS for CE (Windows Mobile actually) - 
> Tracking as KJ4ERJ-12
> 
> Andrew Rich wrote:
> > I have been playing with perl and GD
> >  
> > I am able to do the old pixel plots.
> >  
> > I have managed to hook in my ADS-B (APRS for planes)
> >  
> > And make my own tracking screens with complete freedom.
> >  
> > Maps and all !
> >  
> > Andrew
> >
> >     ----- Original Message -----
> >     *From:* Lynn W. Deffenbaugh (Mr) <mailto:ldeffenb at homeside.to>
> >     *To:* TAPR APRS Mailing List <mailto:aprssig at tapr.org>
> >     *Sent:* Sunday, December 21, 2008 6:06 AM
> >     *Subject:* Re: [aprssig] APRS Parser
> >
> >     I couldn't resist throwing a dig right back also.  All in fun. 
> >     The best
> >     part of the old DOS commands is that most of them still work in
> >     Windows
> >     Vista's default Command Prompt!
> >
> >     for %f in (test??x.png) do %f
> >
> >     Lots faster than trying to identify a bunch of similarly-named PNG
> >     files
> >     and opening them in the default PNG viewer via a mouse!
> >
> >     Lynn (D) - KJ4ERJ - Apparently of Bob's vintage!
> >
> >     Andrew Rich wrote:
> >     > Just having a dig
> >     > 
> >     > Bob does some stuff I have never seen on DOS ;-)
> >     > 
> >     > 
> >     >
> >     >     ----- Original Message -----
> >     >     *From:* Lynn W. Deffenbaugh (Mr) <mailto:ldeffenb at homeside.to>
> >     >     *To:* TAPR APRS Mailing List <mailto:aprssig at tapr.org>
> >     >     *Sent:* Sunday, December 21, 2008 5:36 AM
> >     >     *Subject:* Re: [aprssig] APRS Parser
> >     >
> >     >     He said it was "pseudo code English" which runs most effectively
> >     >     on this
> >     >     really cool bio-mechanical homo-sapien gray-matter stuff but is
> >     >     readily
> >     >     translated to other languages and operating systems within that
> >     >     native
> >     >     environment.
> >     >
> >     >     Lynn (D) - KJ4ERJ - Professionally employed HSGMS translator
> >     >
> >     >     Andrew Rich wrote:
> >     >     > DOS
> >     >     >
> >     >     > Will that even work with Windows XP ?
> >     >     >
> >     >     > Bob  i need to bring you into this century
> >     >     >
> >     >     >     ----- Original Message -----
> >     >     >     *From:* Bob Bruninga <mailto:bruninga at usna.edu>
> >     >     >     *To:* TAPR APRS Mailing List <mailto:aprssig at tapr.org>
> >     >     >     *Sent:* Sunday, December 21, 2008 1:30 AM
> >     >     >     *Subject:* [aprssig] APRS Parser
> >     >     >
> >     >     >     Subject was: Re: [aprssig] Field station
> >     >     >
> >     >     >     >> I'm pretty sure there's a perl APRS
> >     >     >     >> parser somewhere,
> >     >     >
> >     >     >     The gold standard for APRS parsing in pseudo code
> >     English is on
> >     >     >     the www.aprs.org <http://www.aprs.org>
> >     <http://www.aprs.org> <http://www.aprs.org>
> >     >     web site:
> >     >     >
> >     >     >     http://www.aprs.org/txt/APRS-parser.txt
> >     >     >
> >     >     >     This is the full commented parser from the original
> >     APRSdos.  It
> >     >     >     is good up through APRS1.1 and much of APRS1.2.  The
> >     newest
> >     >     things
> >     >     >     in APRS1.2 that I need to add are:
> >     >     >
> >     >     >     1) The new Mic-E Type definitions so that you can
> >     recognize
> >     >     Yaesu,
> >     >     >     and TinyTraks, and other future manufacturers.
> >     >     >
> >     >     >     2) The new ITEM-IN-MESSAGE format
> >     >     >
> >     >     >     3) FREQ-IN-MESSAGE format if your code also has RIG tuning
> >     >     control.
> >     >     >
> >     >     >     4) FREQUNECY parser for tabular display
> >     >     >
> >     >     >     5) OPERATOR PRESENT BIT ("O" overlay on most symbols)
> >     >     >
> >     >     >     6) PRIORITY BIT:  (uses the case of the E/W byte)
> >     >     >
> >     >     >     7) SKY COMMAND Parsing and display of community remotes
> >     >     >
> >     >     >     8) EMERGENCY codes for non Mic-E systems
> >     >     >
> >     >     >     9) The !DAO! high precision parser
> >     >     >
> >     >     >     Ill update the parser page above so that it is
> >     complete, when I
> >     >     >     get back from travel.
> >     >     >
> >     >     >     Bob, Wb4APR
> >     >     >
> >     >     >
> >     >     >
> >     >     >     _______________________________________________
> >     >     >     aprssig mailing list
> >     >     >     aprssig at tapr.org <mailto:aprssig at tapr.org>
> >     <mailto:aprssig at tapr.org>
> >     >     <mailto:aprssig at tapr.org>
> >     >     >     https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig
> >     >     >
> >     >     >   
> >     >    
> >    
> ------------------------------------------------------------------------
> >     >     >
> >     >     >     No virus found in this incoming message.
> >     >     >     Checked by AVG - http://www.avg.com
> >     >     >     Version: 8.0.176 / Virus Database: 270.9.19/1857 -
> >     Release Date:
> >     >     >     12/19/2008 10:09 AM
> >     >     >
> >     >     >
> >     >    
> >    
> ------------------------------------------------------------------------
> >     >     >
> >     >     > _______________________________________________
> >     >     > aprssig mailing list
> >     >     > aprssig at tapr.org <mailto:aprssig at tapr.org>
> >     <mailto:aprssig at tapr.org>
> >     >     > https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig
> >     >     > 
> >     >
> >     >
> >     >     _______________________________________________
> >     >     aprssig mailing list
> >     >     aprssig at tapr.org <mailto:aprssig at tapr.org>
> >     <mailto:aprssig at tapr.org>
> >     >     https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig
> >     >
> >     >    
> >    
> ------------------------------------------------------------------------
> >     >
> >     >     No virus found in this incoming message.
> >     >     Checked by AVG - http://www.avg.com
> >     >     Version: 8.0.176 / Virus Database: 270.9.19/1857 - Release Date:
> >     >     12/19/2008 10:09 AM
> >     >
> >     >
> >    
> ------------------------------------------------------------------------
> >     >
> >     > _______________________________________________
> >     > aprssig mailing list
> >     > aprssig at tapr.org <mailto:aprssig at tapr.org>
> >     > https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig
> >     >  
> >
> >
> >     _______________________________________________
> >     aprssig mailing list
> >     aprssig at tapr.org <mailto:aprssig at tapr.org>
> >     https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig
> >
> >    
> ------------------------------------------------------------------------
> >
> >     No virus found in this incoming message.
> >     Checked by AVG - http://www.avg.com
> >     Version: 8.0.176 / Virus Database: 270.9.19/1857 - Release Date:
> >     12/19/2008 10:09 AM
> >
> > ------------------------------------------------------------------------
> >
> > _______________________________________________
> > aprssig mailing list
> > aprssig at tapr.org
> > https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig
> >   
> 
> 
> 
> 
> ------------------------------
> 
> Message: 8
> Date: Sat, 20 Dec 2008 16:49:21 -0500 (EST)
> From: "Bob Bruninga " <bruninga at usna.edu>
> Subject: [aprssig] Appalacian TRail and ham radio
> To: aprssig at tapr.org
> Cc: peak-2-peak at yahoogroups.com
> Message-ID: <20081220164921.AIL09824 at mp3.nettest.usna.edu>
> Content-Type: text/plain; charset=us-ascii
> 
> TO THE APRS SIG:
> 
> There is a new move afoot to survey the Appalachian Trail for Ham Radio.
> 
> The idea I want to persue is to make a trip-tic or mapquest kind of overlay
> on the AT map to show green, yellow and red overlays along the trail showing
> where APRS tracking is good, fair and poor.
> 
> This would be calibrated to a 5w HT using a stock antenna, or 1W HT using a
> good full size antenna while walking the AT.
> 
> ALso, the map will plot all of those Voice Repeaters that should be
> accessible.  In this case, with a 1W HT and stock antenna but held to the
> face in normal operating style.  These voice repeaters will show where their
> PHG circle intersects the trail.
> 
> The final step is to make sure that those regularly monitoed and mainly
> receommended voice repeaters are included in the APRS local Frequency Object
> for that area, so the AT traveler can SEE on his radio, what freq to use.
> 
> I have  had a web page up on this for many years, but it is no longer
> accessible to the public due to a new firewall at work.  Ill try to remember
> to move it over to APRS.ORG... after seasons travels.
> 
> But I was recently contacted by a group attempting to survey the trail
> (peak-2-peak at yahoogroups.com)(for voice) and so why not also for APRS?
> 
> And maybe some of you may go hiking over the holidays, so why not carry your
> APRS radio.
> 
> HERE IS MY RECOMMENDATION: so that we get a nice data base with the least
> effort and the most fun:
> 
> 1) SET MYCALL TO "ATRAIL" (only on the trail)
> 2) SET your own call in your status text
> 3) SET rate to 3 minutes
> 4) SET PATH to WIDE1-1,WIDE2-1
> 5) Enjoy all the hiking you want ON THE AT
> 
> No matter how many of us do this, every dot will show accessibility, and
> although the "track" will pingpoing, the summation of DOTS will plot the
> accessible trail!
> 
> It is imperative that the MYCALL of "ATRAIL" only be used when actually on
> the trail to avoid dots all over the place, going to and from the trail.
> 
> Does anywone know if FINDU would retain all of these points? and for how
> long?
> 
> Bob, WB4APR
> 
> 
> 
> ------------------------------
> 
> Message: 9
> Date: Sat, 20 Dec 2008 17:09:34 -0500
> From: "Lynn W. Deffenbaugh (Mr)" <ldeffenb at homeside.to>
> Subject: Re: [aprssig] Appalacian TRail and ham radio
> To: TAPR APRS Mailing List <aprssig at tapr.org>
> Message-ID: <494D6D1E.3030506 at homeside.to>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> 
> I would like to add that anyone that DOES hike the trail, please post 
> (or send to the address above) your callsign and approximate hiking 
> times.  Even if you switch to ATRAIL, I'd like to know when to look for 
> data.
> 
> I don't know how long FINDU or APRS.FI buffers data or how they'd handle 
> the ping-ponging of multiple IDs, but I've got my own 7-day buffer 
> running locally from which I'd like to analyze the tracked data.  I can 
> even supply maps of your hike and the APRS infrastructure used by your 
> tracking activities.  This would even apply to road-trips, so please 
> contact me off-list (address above) if you're interested.
> 
> Bob - I suspect using ATRAIL may cause problems with the "speed limits" 
> imposed by the APRS-IS infrastructure.  If two ATRAILs are hiking 
> dramatically separated sections of the trail at the same time, the 
> ping-pong would look like it defies reality and position updates may be 
> rejected as "moving too fast".  Or is that a findu/aprs.fi feature and 
> not the -IS infrastructure itself?
> 
> Lynn (D) - KJ4ERJ - Working on APRS infrastructure utilization visualization
> 
> Bob Bruninga wrote:
> > And maybe some of you may go hiking over the holidays, so why not carry
> your APRS radio.
> >
> > HERE IS MY RECOMMENDATION: so that we get a nice data base with the least
> effort and the most fun:
> >
> > 1) SET MYCALL TO "ATRAIL" (only on the trail)
> > 2) SET your own call in your status text
> > 3) SET rate to 3 minutes
> > 4) SET PATH to WIDE1-1,WIDE2-1
> > 5) Enjoy all the hiking you want ON THE AT
> >
> > No matter how many of us do this, every dot will show accessibility, and
> although the "track" will pingpoing, the summation of DOTS will plot the
> accessible trail!
> >
> > It is imperative that the MYCALL of "ATRAIL" only be used when actually on
> the trail to avoid dots all over the place, going to and from the trail.
> >
> > Does anywone know if FINDU would retain all of these points? and for how
> long?
> >
> > Bob, WB4APR
> >
> > _______________________________________________
> > aprssig mailing list
> > aprssig at tapr.org
> > https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig
> >
> >   
> 
> 
> 
> 
> ------------------------------
> 
> Message: 10
> Date: Sun, 21 Dec 2008 08:23:30 +1000
> From: "Andrew Rich" <vk4tec at tech-software.net>
> Subject: Re: [aprssig] APRS Parser
> To: "TAPR APRS Mailing List" <aprssig at tapr.org>
> Message-ID: <013101c962f1$9e351890$6501a8c0 at Laptop1520>
> Content-Type: text/plain; charset="iso-8859-1"
> 
> Lynn
> 
> Can you help me to work out the GD syntax for a background image please
> 
> I have not had much success so far
> 
> I am working with a blank grey canvas at the moment.
> 
> http://www.tech-software.net/adsb_bn_live.htm
>   ----- Original Message ----- 
>   From: Lynn W. Deffenbaugh (Mr) 
>   To: TAPR APRS Mailing List 
>   Sent: Sunday, December 21, 2008 6:54 AM
>   Subject: Re: [aprssig] APRS Parser
> 
> 
>   Interesting timing!  I've spent the day working with GD and 
>   OpenStreetMaps.org to visualize and plot various APRS-IS collected 
>   data!  If you've not heard of OpenStreetMaps.org, check them out.  A 
>   free map source with tiles of various zoom levels that are stitchable to 
>   make any arbitrary map with details.  Of particular programmer interest 
>   is http://wiki.openstreetmap.org/index.php/Slippy_map_tilenames
> 
>   Lynn (D) - KJ4ERJ - Author of APRS-IS for CE (Windows Mobile actually) - 
>   Tracking as KJ4ERJ-12
> 
>   Andrew Rich wrote:
>   > I have been playing with perl and GD
>   >  
>   > I am able to do the old pixel plots.
>   >  
>   > I have managed to hook in my ADS-B (APRS for planes)
>   >  
>   > And make my own tracking screens with complete freedom.
>   >  
>   > Maps and all !
>   >  
>   > Andrew
>   >
>   >     ----- Original Message -----
>   >     *From:* Lynn W. Deffenbaugh (Mr) <mailto:ldeffenb at homeside.to>
>   >     *To:* TAPR APRS Mailing List <mailto:aprssig at tapr.org>
>   >     *Sent:* Sunday, December 21, 2008 6:06 AM
>   >     *Subject:* Re: [aprssig] APRS Parser
>   >
>   >     I couldn't resist throwing a dig right back also.  All in fun. 
>   >     The best
>   >     part of the old DOS commands is that most of them still work in
>   >     Windows
>   >     Vista's default Command Prompt!
>   >
>   >     for %f in (test??x.png) do %f
>   >
>   >     Lots faster than trying to identify a bunch of similarly-named PNG
>   >     files
>   >     and opening them in the default PNG viewer via a mouse!
>   >
>   >     Lynn (D) - KJ4ERJ - Apparently of Bob's vintage!
>   >
>   >     Andrew Rich wrote:
>   >     > Just having a dig
>   >     > 
>   >     > Bob does some stuff I have never seen on DOS ;-)
>   >     > 
>   >     > 
>   >     >
>   >     >     ----- Original Message -----
>   >     >     *From:* Lynn W. Deffenbaugh (Mr) <mailto:ldeffenb at homeside.to>
>   >     >     *To:* TAPR APRS Mailing List <mailto:aprssig at tapr.org>
>   >     >     *Sent:* Sunday, December 21, 2008 5:36 AM
>   >     >     *Subject:* Re: [aprssig] APRS Parser
>   >     >
>   >     >     He said it was "pseudo code English" which runs most
> effectively
>   >     >     on this
>   >     >     really cool bio-mechanical homo-sapien gray-matter stuff but
> is
>   >     >     readily
>   >     >     translated to other languages and operating systems within
> that
>   >     >     native
>   >     >     environment.
>   >     >
>   >     >     Lynn (D) - KJ4ERJ - Professionally employed HSGMS translator
>   >     >
>   >     >     Andrew Rich wrote:
>   >     >     > DOS
>   >     >     >
>   >     >     > Will that even work with Windows XP ?
>   >     >     >
>   >     >     > Bob  i need to bring you into this century
>   >     >     >
>   >     >     >     ----- Original Message -----
>   >     >     >     *From:* Bob Bruninga <mailto:bruninga at usna.edu>
>   >     >     >     *To:* TAPR APRS Mailing List <mailto:aprssig at tapr.org>
>   >     >     >     *Sent:* Sunday, December 21, 2008 1:30 AM
>   >     >     >     *Subject:* [aprssig] APRS Parser
>   >     >     >
>   >     >     >     Subject was: Re: [aprssig] Field station
>   >     >     >
>   >     >     >     >> I'm pretty sure there's a perl APRS
>   >     >     >     >> parser somewhere,
>   >     >     >
>   >     >     >     The gold standard for APRS parsing in pseudo code
>   >     English is on
>   >     >     >     the www.aprs.org <http://www.aprs.org>
>   >     <http://www.aprs.org> <http://www.aprs.org>
>   >     >     web site:
>   >     >     >
>   >     >     >     http://www.aprs.org/txt/APRS-parser.txt
>   >     >     >
>   >     >     >     This is the full commented parser from the original
>   >     APRSdos.  It
>   >     >     >     is good up through APRS1.1 and much of APRS1.2.  The
>   >     newest
>   >     >     things
>   >     >     >     in APRS1.2 that I need to add are:
>   >     >     >
>   >     >     >     1) The new Mic-E Type definitions so that you can
>   >     recognize
>   >     >     Yaesu,
>   >     >     >     and TinyTraks, and other future manufacturers.
>   >     >     >
>   >     >     >     2) The new ITEM-IN-MESSAGE format
>   >     >     >
>   >     >     >     3) FREQ-IN-MESSAGE format if your code also has RIG
> tuning
>   >     >     control.
>   >     >     >
>   >     >     >     4) FREQUNECY parser for tabular display
>   >     >     >
>   >     >     >     5) OPERATOR PRESENT BIT ("O" overlay on most symbols)
>   >     >     >
>   >     >     >     6) PRIORITY BIT:  (uses the case of the E/W byte)
>   >     >     >
>   >     >     >     7) SKY COMMAND Parsing and display of community remotes
>   >     >     >
>   >     >     >     8) EMERGENCY codes for non Mic-E systems
>   >     >     >
>   >     >     >     9) The !DAO! high precision parser
>   >     >     >
>   >     >     >     Ill update the parser page above so that it is
>   >     complete, when I
>   >     >     >     get back from travel.
>   >     >     >
>   >     >     >     Bob, Wb4APR
>   >     >     >
>   >     >     >
>   >     >     >
>   >     >     >     _______________________________________________
>   >     >     >     aprssig mailing list
>   >     >     >     aprssig at tapr.org <mailto:aprssig at tapr.org>
>   >     <mailto:aprssig at tapr.org>
>   >     >     <mailto:aprssig at tapr.org>
>   >     >     >     https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig
>   >     >     >
>   >     >     >   
>   >     >    
>   >    
> ------------------------------------------------------------------------
>   >     >     >
>   >     >     >     No virus found in this incoming message.
>   >     >     >     Checked by AVG - http://www.avg.com
>   >     >     >     Version: 8.0.176 / Virus Database: 270.9.19/1857 -
>   >     Release Date:
>   >     >     >     12/19/2008 10:09 AM
>   >     >     >
>   >     >     >
>   >     >    
>   >    
> ------------------------------------------------------------------------
>   >     >     >
>   >     >     > _______________________________________________
>   >     >     > aprssig mailing list
>   >     >     > aprssig at tapr.org <mailto:aprssig at tapr.org>
>   >     <mailto:aprssig at tapr.org>
>   >     >     > https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig
>   >     >     > 
>   >     >
>   >     >
>   >     >     _______________________________________________
>   >     >     aprssig mailing list
>   >     >     aprssig at tapr.org <mailto:aprssig at tapr.org>
>   >     <mailto:aprssig at tapr.org>
>   >     >     https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig
>   >     >
>   >     >    
>   >    
> ------------------------------------------------------------------------
>   >     >
>   >     >     No virus found in this incoming message.
>   >     >     Checked by AVG - http://www.avg.com
>   >     >     Version: 8.0.176 / Virus Database: 270.9.19/1857 - Release
> Date:
>   >     >     12/19/2008 10:09 AM
>   >     >
>   >     >
>   >    
> ------------------------------------------------------------------------
>   >     >
>   >     > _______________________________________________
>   >     > aprssig mailing list
>   >     > aprssig at tapr.org <mailto:aprssig at tapr.org>
>   >     > https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig
>   >     >  
>   >
>   >
>   >     _______________________________________________
>   >     aprssig mailing list
>   >     aprssig at tapr.org <mailto:aprssig at tapr.org>
>   >     https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig
>   >
>   >    
> ------------------------------------------------------------------------
>   >
>   >     No virus found in this incoming message.
>   >     Checked by AVG - http://www.avg.com
>   >     Version: 8.0.176 / Virus Database: 270.9.19/1857 - Release Date:
>   >     12/19/2008 10:09 AM
>   >
>   > ------------------------------------------------------------------------
>   >
>   > _______________________________________________
>   > aprssig mailing list
>   > aprssig at tapr.org
>   > https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig
>   >   
> 
> 
>   _______________________________________________
>   aprssig mailing list
>   aprssig at tapr.org
>   https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig
> 
> 
>
------------------------------------------------------------------------------
> 
> 
> 
>   No virus found in this incoming message.
>   Checked by AVG - http://www.avg.com 
>   Version: 8.0.176 / Virus Database: 270.9.19/1857 - Release Date: 12/19/2008
> 10:09 AM
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
>
http://www.tapr.org/pipermail/aprssig/attachments/20081221/e15690c5/attachment-0001.htm
> 
> 
> ------------------------------
> 
> Message: 11
> Date: Sat, 20 Dec 2008 18:01:06 -0500
> From: "Lynn W. Deffenbaugh (Mr)" <ldeffenb at homeside.to>
> Subject: Re: [aprssig] APRS Parser
> To: TAPR APRS Mailing List <aprssig at tapr.org>
> Message-ID: <494D7932.9000405 at homeside.to>
> Content-Type: text/plain; charset="us-ascii"
> 
> An HTML attachment was scrubbed...
> URL:
>
http://www.tapr.org/pipermail/aprssig/attachments/20081220/4c62ea8c/attachment-0001.htm
> 
> 
> ------------------------------
> 
> Message: 12
> Date: Sat, 20 Dec 2008 20:21:43 -0600
> From: "Jason KG4WSV" <kg4wsv at gmail.com>
> Subject: Re: [aprssig] Appalacian TRail and ham radio
> To: "TAPR APRS Mailing List" <aprssig at tapr.org>
> Message-ID:
> 	<fea2d3330812201821k6b409322iceb3bfad4cfbaff0 at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
> 
> On Sat, Dec 20, 2008 at 4:09 PM, Lynn W. Deffenbaugh (Mr)
> <ldeffenb at homeside.to> wrote:
> 
> > Bob - I suspect using ATRAIL may cause problems
> 
> Two at the same time would cause a problem, but only for users and
> clients trying to make sense of the data.
> 
> The APRS-IS only filters exact duplicates, as far as I know. No effort
> is made for sanity checks on speed - after all, those satellite
> objects are moving right along as they go over.
> 
> Why not just put something in the comment indicating they're on the trail?
> 
> Not sure how feasible it is, but something that might be useful is if
> the hiker could carry a packet receiver and a datalogger.  A 1W or 5W
> HT may or may not get out, but a fixed site digi may be more likely to
> get in and give a better indication of coverage.  (No, I am not
> volunteering to carry the batteries. :)
> 
> -Jason
> kg4wsv
> 
> 
> 
> ------------------------------
> 
> Message: 13
> Date: Sat, 20 Dec 2008 23:06:51 -0500
> From: Jack Spitznagel <frawg at frawg.org>
> Subject: Re: [aprssig] Appalacian TRail and ham radio
> To: TAPR APRS Mailing List <aprssig at tapr.org>
> Message-ID: <494DC0DB.2060400 at frawg.org>
> Content-Type: text/plain; charset=ISO-8859-1
> 
> Jason KG4WSV wrote:
> 
> > Not sure how feasible it is, but something that might be useful is if
> > the hiker could carry a packet receiver and a datalogger.  
> Are any of the trackers capable of running off a light weight solar
> panel? Might do that if I was doing a weekender segment.
> 
> The project is a great idea, but there ain't an AT through-hiker I know
> that will carry any weight at all... technical stuff gets left behind if
> you can't wear it on a wrist. The really serious guys won't even talk to
> you if you wear a watch! You'd have to rely on weekenders.
> 
> In the past, I  have hiked parts of the trail in NC and southern VA with
> an HT. Useless unless you are in a rare hilltopping area. OTOH, the
> segment up the Shenandoah from Waynesboro to Front Royal is spectacular
> because you are either on the eastern slope/ridge looking at
> Charlottesville and DC or you are on the west slope looking into the
> valley. From  there to Harrisburg, PA coverage is on and off again...
> Better at the southern end up to Frederick then not good until you are
> near Carlisle and Mechanicsburg.
> 
> VHF is not ideal... I had more luck on one weekend AT hike in southern
> PA using my FT-817 on HF with a slingshot antenna than I did on VHF with
> the telescoping rod 1/4 wave or the duck. I carried two sets of
> rechargables with a trickle charge solar panel and I felt the extra
> weight for the entire 30 mile segment. Have never had the gear to try it
> with APRS. I usually don't even want to carry a GPS unless I am teaching
> the boy scouts how to use one.
> 
> > A 1W or 5W HT may or may not get out, but a fixed site digi may be more
> likely to
> > get in and give a better indication of coverage.  (No, I am not
> > volunteering to carry the batteries. :)
> >   
> You should get in touch with some of the AT Trail Crew groups... they'll
> carry in just about anything with an excuse... the only problem would be
> keeping up with them! Some of those guys run up the trail carrying heavy
> tools, shovels, saws, and axes along with their gear.
> 
> kd4iz
> 
> 
> 
> ------------------------------
> 
> _______________________________________________
> aprssig mailing list
> aprssig at tapr.org
> https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig
> 
> 
> End of aprssig Digest, Vol 54, Issue 24
> ***************************************
> 


a



More information about the aprssig mailing list