From: "Chuck Hast" <wchast@gmail.com>
To: "Curt Mills, WE7U" <archer@eskimo.com>
Cc: Jeff Laughlin <jeff.laughlin@gmail.com>, linux-hams@vger.kernel.org
Subject: Re: APRS Parser
Date: Thu, 22 Jun 2006 09:34:05 -0400 [thread overview]
Message-ID: <620c90570606220634i799776bbga8678e1fc6e09360@mail.gmail.com> (raw)
In-Reply-To: <Pine.SUN.4.58.0606220630370.12910@eskimo.com>
On 6/22/06, Curt, WE7U <archer@eskimo.com> wrote:
> On Thu, 22 Jun 2006, Chuck Hast wrote:
>
> > Indeed what I want to do is capture the data from a group of those devices
> > so I can rapidly dispay it locally and graph it, when Alberto went by here I
> > observed some interesting water level changes, and want to capture that
> > data into a db somewhere for later processing, and also want to do so for
> > other such devices.
>
> Are you connected to Firenet? I'm posting thousands of objects
> there for water level. Might be of interest.
>
No though Bob B. contacted firenet for the 'to' field ID that is used in the
FloodAdvisor devices I am using.
How do we go about this?
--
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."
next prev parent reply other threads:[~2006-06-22 13:34 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
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 [this message]
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=620c90570606220634i799776bbga8678e1fc6e09360@mail.gmail.com \
--to=wchast@gmail.com \
--cc=archer@eskimo.com \
--cc=jeff.laughlin@gmail.com \
--cc=linux-hams@vger.kernel.org \
/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