Linux HAM/Amateur Radio development
 help / color / mirror / Atom feed
From: "Curt, WE7U" <archer@eskimo.com>
To: Jeff Laughlin <jeff.laughlin@gmail.com>
Cc: Chuck Hast <wchast@gmail.com>, linux-hams@vger.kernel.org
Subject: Re: APRS Parser
Date: Tue, 20 Jun 2006 04:00:00 -0700 (PDT)	[thread overview]
Message-ID: <Pine.SUN.4.58.0606200356580.19102@eskimo.com> (raw)
In-Reply-To: <8ea83f40606192129t28c742y94299329b8548076@mail.gmail.com>

On Mon, 19 Jun 2006, Jeff Laughlin wrote:

> I started on an APRS parser written in perl. It handles most of the
> major bits of the standard and I used it to dump APRS data into
> postgresql and it kept up with the global APRS internet feeds no
> problem, in fact I was suprised at how fast it was. It turned out that
> PostgreSQL consumed vastly more system resources than the parser and
> that was mostly disk IO, CPU load was relatively light. It could
> certainly still use some work but it's functional and well documented
> and I included example code. You can get it from
> http://sourceforge.net/projects/ham-aprs-parser/

There's also the Perl APRS code that Ian wrote (the APRS spec
editor) which validates packets.  I should have a copy of it around
somewhere if you can't find it on the 'net.  That would be excellent
code to have around as an example, just because it was at one time
the most complete Perl decoder implementation.

On SourceForge I believe there are C++ classes and perhaps Java code
for parsing APRS sentences, and of course the Xastir project
(SourceForge again) has a bunch of C code.  It's a _bunch_ of C code
though!

I also have Perl code for authenticating on the 'net if you'd like
that.  It's a direct Perl translation of the C-code that Steve Dimse
published and I use it extensively in my Perl scripts which inject
objects into Firenet.

--
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!"

  reply	other threads:[~2006-06-20 11:00 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 [this message]
2006-06-20 11:15     ` Chuck Hast
2006-06-20 11:22       ` Curt, WE7U
2006-06-20 11:30         ` Curt, WE7U
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.0606200356580.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