From: Jeff Laughlin <jeff.laughlin@gmail.com>
To: Chuck Hast <wchast@gmail.com>
Cc: Linux-Hams@vger.kernel.org
Subject: Re: Announcing Perl module for parsing APRS packets
Date: Wed, 10 Aug 2005 12:33:36 -0400 [thread overview]
Message-ID: <8ea83f405081009332564220c@mail.gmail.com> (raw)
In-Reply-To: <620c905705081009143dc3bcb0@mail.gmail.com>
On 8/10/05, Chuck Hast <wchast@gmail.com> wrote:
> 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.
>
> Could this be used to dump APRS data into a db like MySQL? I am interested
> in doing something like that, but have to learn about db. I work with them up
> to a certain point, time to learn the rest and getting APRS data into a db would
> be a neat exersize.
Yes that is certainly a possibility... In fact I am working on that
right now! My next code release will be a complete FOSS findu.com
replacement, with a postgresql backend.
http://www.trackulator.com/
Expect to see it sometime in the next few weeks.
next prev parent reply other threads:[~2005-08-10 16:33 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 [this message]
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
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=8ea83f405081009332564220c@mail.gmail.com \
--to=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