From: "Jeff Laughlin" <jeff.laughlin@gmail.com>
To: Chuck Hast <wchast@gmail.com>
Cc: linux-hams@vger.kernel.org
Subject: Re: APRS Parser
Date: Mon, 19 Jun 2006 21:29:16 -0700 [thread overview]
Message-ID: <8ea83f40606192129t28c742y94299329b8548076@mail.gmail.com> (raw)
In-Reply-To: <620c90570606191918h7605ecbax20325ecffe1546e2@mail.gmail.com>
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/
On 6/19/06, Chuck Hast <wchast@gmail.com> wrote:
> Folks,
> Was poking around trying to find something to parse aprs data and poke it
> into mysql, thought that I had found something from aprsworld but when I
> went to look at it, it looked like it was only the pieces needed to get the data
> out of the database and into shape files...
>
> I see a lot of comments about such code but the links are dead. Any rec-
> omendations?
>
> --
> Chuck Hast -- KP4DJT --
> To paraphrase my flight instructor;
> "the only dumb question is the one you DID NOT ask resulting in my going
> out and having to identify your bits and pieces in the midst of torn
> and twisted metal."
> -
> To unsubscribe from this list: send the line "unsubscribe linux-hams" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
73 de n1ywb
next prev parent reply other threads:[~2006-06-20 4:29 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 [this message]
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
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=8ea83f40606192129t28c742y94299329b8548076@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