Hello Paul,

following up a message from Richard Webb to Paul Quinn:

PQ> I would be looking at a system something similar to...

RW> DO that with station logs, but this is for the whole group.
RW> The weekly file is mainly what vessels have used us and
RW> that's already done.

RW> There are a couple of sections that prepend all this
RW> hwoever, and they're built as well to generate this email.
RW> they're a "welcome newcomers" type section, a logistics, who needs
RW> pinch hitters, etc. section, etc.

Meat of this "weekly journal" is made up of info regarding
vessels who file position and weather reports via our
network while offshore.
I'll grab one of those entries from this week and parse it
to explain.  Btw, that code is already written, and working
pretty darned well.  This is year #5 of this journal in fact .

First, the raw entry in my data file ...


01/10/2012 01:13 KC2TIU W1CT 12-38.0n 061-21.0w   SV TSAMAYA 2 POB

FIrst you can see that the entry was posted as of 01/10/2012 at 01:13 utc.

The call sign of the vessel's ham op was kc2tiu.  The guy
who took the data was w1ct.

So, on Sunday mornings a batch (already created and working) parses each entry
in the weekly data file.  IT shows readers the last entry we have for kc2tiu,
and looks in another file for info about the sailing vessel, such as marine
call
signs, communications capabilities, operator's name, marine
service call sign if known, etc.

IN another section of the journal it looks at entries posted by JOhn, w1ct, or
other posters.  IT then tells readers how
many reports JOhn took last week, how many over the month,
how many over the year, and how many since my system started tracking this
data.  So the "next week in history ... "
section is just part of this, and the current one under
development .




Regards,
           Richard
---
 * Origin:  (1:116/901)