From: "Curt, WE7U" <archer@eskimo.com>
To: Chuck Hast <wchast@gmail.com>
Cc: Jeff Laughlin <jeff.laughlin@gmail.com>, linux-hams@vger.kernel.org
Subject: Re: APRS Parser
Date: Tue, 20 Jun 2006 04:30:58 -0700 (PDT) [thread overview]
Message-ID: <Pine.SUN.4.58.0606200427330.19102@eskimo.com> (raw)
In-Reply-To: <Pine.SUN.4.58.0606200421130.19102@eskimo.com>
On Tue, 20 Jun 2006, Curt, WE7U wrote:
> On Tue, 20 Jun 2006, Chuck Hast wrote:
>
> > Thank you, I will go dig it up too, I am not a coder, but will try anything if
> > I have enough samples!!
>
> Try this in Google:
>
> perl ian aprs parser
>
> Looks like Jeff has a Perl parser already written!
And if I could actually _read_ this morning I wouldn't have had to
say that! Time to go hit the pepsi machine I guess.
This looks to be a description of the newish version of Ian Wade's
packet decoder program, with a link at the bottom to the code which
doesn't work:
http://db0sif.darc.de/cgi-bin/dpcmd?R%20SOFTWARE%203309
Put "aprsdecu.tar" into Google and you'll find sites where it's
available though.
--
Curt, WE7U. APRS Client Comparisons: http://www.eskimo.com/~archer
"Lotto: A tax on people who are bad at math." -- unknown
"Windows: Microsoft's tax on computer illiterates." -- WE7U
"The world DOES revolve around me: I picked the coordinate system!"
next prev parent reply other threads:[~2006-06-20 11:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-20 2:18 APRS Parser Chuck Hast
2006-06-20 4:29 ` Jeff Laughlin
2006-06-20 11:00 ` Curt, WE7U
2006-06-20 11:15 ` Chuck Hast
2006-06-20 11:22 ` Curt, WE7U
2006-06-20 11:30 ` Curt, WE7U [this message]
2006-06-20 11:37 ` Curt, WE7U
2006-06-21 2:34 ` Chuck Hast
2006-06-22 3:52 ` Chuck Hast
2006-06-22 11:41 ` Curt, WE7U
2006-06-22 11:49 ` Chuck Hast
2006-06-22 12:10 ` Curt, WE7U
2006-06-22 13:30 ` Chuck Hast
2006-06-22 13:31 ` Curt, WE7U
2006-06-22 13:34 ` Chuck Hast
2006-06-22 13:41 ` Curt, WE7U
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.SUN.4.58.0606200427330.19102@eskimo.com \
--to=archer@eskimo.com \
--cc=jeff.laughlin@gmail.com \
--cc=linux-hams@vger.kernel.org \
--cc=wchast@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox