From: Jeff Laughlin <jeff.laughlin@gmail.com>
To: "Curt Mills, WE7U" <archer@eskimo.com>
Cc: Linux-Hams@vger.kernel.org
Subject: Re: Announcing Perl module for parsing APRS packets
Date: Wed, 10 Aug 2005 12:21:31 -0400 [thread overview]
Message-ID: <8ea83f4050810092139d7034c@mail.gmail.com> (raw)
In-Reply-To: <Pine.SUN.4.58.0508100852220.1839@eskimo.com>
Hi Curt,
Thanks for the suggestion. I wasn't aware that it existed.
After thwarting a few broken links I did manage to find a copy. It
targets perl 4, it's not a module, and it outputs formatted text
instead of a data structure, so it doesn't exactly acheive the same
goals that I have. However it is GPL'ed which is good, so I may be
able to re-use some of it's parsing code without tainting my code. I
still have quite a bit left to implement to have a complete
implementation. And it will certainly be nice to have another GPL code
base to reference other than XASTIR.
On 8/10/05, Curt, WE7U <archer@eskimo.com> wrote:
> On Fri, 5 Aug 2005, Jeff Laughlin wrote:
>
> > I've written a Perl module, Ham::APRS::Parser, for parsing APRS
> > packets, and I've released it under the GPL. You can find it here:
> > http://aprs.n1ywb.com/Ham-APRS-Parser-0.01/
> >
> > It takes the packet string, parses it, and returns a hash with the
> > data in a consistent and easy to process format. Currently it reliably
> > returns position, from and to calls, digi-path, symbols, and Mic-E
> > status reports from normal position reports, compressed position
> > reports, and Mic-E position reports. More work is needed to fully
> > implement the APRS protocol.
>
> Have you considered tracking down the Perl code that Ian (the APRS
> spec editor) created which decodes packets? That was quite
> complete and fully decoded everything similar to the "listen"
> command.
>
> --
> 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:[~2005-08-10 16:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-05 21:26 Announcing Perl module for parsing APRS packets Jeff Laughlin
2005-08-09 21:16 ` charlesb
2005-08-10 1:30 ` Nate Bargmann
2005-08-10 11:55 ` charlesb
2005-08-10 15:56 ` Curt, WE7U
2005-08-10 16:14 ` Chuck Hast
2005-08-10 16:33 ` Curt, WE7U
2005-08-10 16:33 ` Jeff Laughlin
2005-08-10 16:38 ` Curt, WE7U
2005-08-10 16:55 ` Chuck Hast
2005-08-11 21:36 ` Bill Vodall
2005-08-11 5:34 ` Wilbert Knol
2005-08-10 16:21 ` Jeff Laughlin [this message]
2005-08-10 16:36 ` 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=8ea83f4050810092139d7034c@mail.gmail.com \
--to=jeff.laughlin@gmail.com \
--cc=Linux-Hams@vger.kernel.org \
--cc=archer@eskimo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.