| |
ZL3AI > APRDIG 03.02.03 14:30l 274 Lines 10091 Bytes #999 (0) @ WW
BID : 800-ZL3AI
Read: GUEST
Subj: TAPR Digest, Jan 27, 5/10
Path: DB0FHN<DB0RGB<OE5XBL<OE3XSR<OK0PCC<OK0NAG<OK0PPL<RZ6HXA<IK1ZNW<IR0NET<
VK3TE<ZL2BAU<ZL3VML
Sent: 030131/0925Z @:ZL3VML.#80.NZL.OC #:58517 [Chch-NZ] FBB7.00i $:800-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To : APRDIG@WW
Subject: APRS Presentation
From: Reid Crowe <bigreidous@sbcglobal.net>
Date: Mon, 27 Jan 2003 13:29:05 -0800 (PST)
X-Message-Number: 24
Sorry to bug everyone about this presentation again. I was wondering what
the most important points to touch on for an APRS presentation. My
audience is mostly guys that have been in the hobby for a while, what would
catch them? And I have a time limit of about 45 min. (I know, not nearly
enough time! HIHI!) Thanks in advance.
73 Reid KC=D8IDI
----------------------------------------------------------------------
[commercial content deleted]
----------------------------------------------------------------------
Subject: RE: APRS Symbols (versus Windows ICONS)..
From: Bill Vodall - WA7NWP <wa7nwp@yahoo.com>
Date: Mon, 27 Jan 2003 14:03:42 -0800
X-Message-Number: 26
In the good old days, when APRS was young and there was no Spec, folks were
doing neat new stuff on a regular basis. These days some products are
updated annually, if that, and we are hung up if some little icon should be
blue or green.
Lets do something new and implement user defined icons to get past this
artificial limitation on the technology.
73,
Bill WA7NWP
----------------------------------------------------------------------
Subject: RE: APRS Symbols (versus Windows ICONS)..
From: Bob Bruninga <bruninga@usna.edu>
Date: Mon, 27 Jan 2003 17:05:30 -0500 (EST)
X-Message-Number: 27
On Mon, 27 Jan 2003, stan horzepa wrote:
>On 01/27/03, "Bob Bruninga <bruninga@usna.edu>" wrote:
>>
>>And a LOT of these are NOT in the spec, becuase the TAPR guidelines for
>>the SPEC held that nothing could go into the SPEC if it was only in
>>APRSdos (the original APRS)... and not yet implemented by the other
>>authors at the time.
>
>Please don't blame TAPR. TAPR was only a facilitator for the APRS Spec
>Working Group. It provided a forum (the Working Group's e-mail list) and
>Web space for the group. It never specified any guidelines for the spec.
>The Working Group specified the guidelines, not TAPR.
This is totally false. I was locked in a room and not allowed to leave
until I agreed to the terms. Either I agreed to do the spec with all
its shortcomings and without what I considered to be some of the
fundamentals of APRS (how information is displayed) or the other authors
would go there own way and do it anyway they individually wanted.
de WB4APR, BOB
----------------------------------------------------------------------
[commercial content deleted]
----------------------------------------------------------------------
Subject: RE: APRS Symbols (versus Windows ICONS)..
From: Bob Bruninga <bruninga@usna.edu>
Date: Mon, 27 Jan 2003 17:14:11 -0500 (EST)
X-Message-Number: 29
....
>Lets do something new and implement user defined icons to get past this
>artificial limitation on the technology.
I hope that was tongue-in-cheek!
We cannot have multiple applications by different authors having
individual assignments of what an ICON is that is only understood by a
small group on the air.
YES, you can in a closed environment (commercial) where you can force
everyone to use the same software version. But not In HAM radio.
There must be a "standard" definition for what ICON is represented by
the two byte sequence "/-" In APRS, that is a HOUSE.
Imagine the mess if we let every end user define his own icons?
Geeze....
Bob,
----------------------------------------------------------------------
Subject: Findu CGIs
From: "Mark A. Foley" <na4v@cox.net>
Date: Mon, 27 Jan 2003 17:14:41 -0500
X-Message-Number: 30
Steve,
Currently, with the available cgi's from findu, is there a way to
filter/add parameters so I could just grab the information from a posit
like this one:
!19:51:25 !NA4V-1>APU256,TCPIP*,qAC,NA4V-1:>271950zDX: NA4V-2 32.57.84N
83.48.48W 29.0 miles 340=F8 14:38
UI-View has an option to send out as a status text, the best DX heard,
or in this case, the most distant station you have heard direct. I
monitor UI-View stations in my area for this status text to see changes
in propagation...possible holes in the network...etc.... I can grab
this through Alogger...however, a findu cgi maybe better.
Do this require a new cgi to be developed?
Mark A. Foley, NA4V
APRSEast
www.na4v.com
----------------------------------------------------------------------
[commercial content deleted]
----------------------------------------------------------------------
Subject: RE: Re: ARRL Public Service Manual regarding RACES
From: "Jack Smith" <jrs38801@bellsouth.net>
Date: Mon, 27 Jan 2003 16:22:28 -0600
X-Message-Number: 32
Which I think is a little funny. The last time I even saw a military HF
radio was in my own grubby hands in 1986. I know we still have them, but
they're so rare as to almost be on the endangered species list. Every time
we go somewhere now we use Single or Multi-Channel Tactical Satellite.
Seems a little silly to me, but I'm not a retired General now working for
Raytheon, talking my old buddies into buying my product (so they can work
for Raytheon later on).
For there to be a state of emergency to be declared would involve such a
major event that I don't think we want to even think it out loud.
Especially since the military would have no reason to want those frequencies
back. We don't have anything that would work on them anymore! We'd have to
rely on all the amateur radio operators in order to use those frequencies,
or buy a whole bunch of stuff in short order. I just don't think it's an
issue.
But on the other hand, I still think that the ARRL and FCC/EMA should get
together and review the RACES issue. Never hurts to think ahead, just in
case.
Jack
KE4LWT
----------------------------------------------------------------------
Subject: RE: APRS Symbols (versus Windows ICONS)..
From: Bill Vodall - WA7NWP <wa7nwp@yahoo.com>
Date: Mon, 27 Jan 2003 15:16:33 -0800
X-Message-Number: 33
At 05:14 PM 1/27/03 -0500, Bob Bruninga wrote:
>...
>>Lets do something new and implement user defined icons to get past this
>>artificial limitation on the technology.
>
>I hope that was tongue-in-cheek!
Not at all.
>We cannot have multiple applications by different authors having
>individual assignments of what an ICON is that is only understood by a
>small group on the air.
Definitions would be broadcast. This would allow using customized
"pictures" where desired. The "station type" and other information of an
ICON could (emphasis on "could") be separate or not per the "picture".
There is, of course, times when you want to be able to easily look at a
screen and seen a well defined set of icons and know at a glance which each
means.
On the other hand, most times there is no reason that ICON "/-a" can't be a
house displayed as wa7nwp's ICON 'a' which is a bitmap showing a blue, two
story split level with 3 comet verticals in the back. The bitmap image
would be either broadcast on the air or picked up from some Internet data
scheme - or both.
The technology here is not difficulty. It would be fun. It would be
useful. It could be optional. It would be like moving to Color TV while
preserving the basic Black and White signals.
>There must be a "standard" definition for what ICON is represented by
>the two byte sequence "/-" In APRS, that is a HOUSE.
That would not change.
>Imagine the mess if we let every end user define his own icons?
Hasn't the same been said about letting users define their own outgoing
path? I don't think this would be a "mess". I think it would be the
elimination of an artificial limitation on the system.
It would be abused. Heck - I'd be the first to abuse it. Like I'm
usually the first to see just how many transmissions a path with a path of
"RELAY,RELAY,RELAY,RELAY" generates at a hamfest. Then the fun is over and
it's back to the business of building better communication systems.
>Bob,
Bill, WA7NWP
----------------------------------------------------------------------
Subject: Re: ARRL Public Service Manual regarding RACES
From: "Dakota Summerhawk" <dakotas@hotpop.com>
Date: Mon, 27 Jan 2003 16:20:51 -0700
X-Message-Number: 34
The local OEM here does not have a APRS station nor can I get he
communications officer to answer my mail for a possible presentation to
explain the system. Wyoming EM and RACES have yet to get into the whole APRS
scene. There are stations that run upo here but I doubt that they are
registered with RACES or OEM.
Peter "Dakota" Summerhawk
APRS/SSTV/VHF/UHF
N0WRE
----------------------------------------------------------------------
Subject: RE: Incident Command Post Symbol
From: "Spider" <spider@rivcom.net>
Date: Mon, 27 Jan 2003 16:26:08 -0700
X-Message-Number: 35
----- Original Message -----
From: "Curt Mills, WE7U" <hacker@tc.fluke.com>
To: "Spider" <spider@rivcom.net>
Cc: "TAPR APRS Special Interest Group" <aprssig@lists.tapr.org>
Sent: Monday, January 27, 2003 12:11 PM
Subject: Re: [aprssig] RE: Incident Command Post Symbol
>On Mon, 27 Jan 2003, Spider wrote:
>
>>Thanks Curt, I posted the symbols for BASE, CAMP and STAGING areas. Did
>>you see that post? There is also Helibases and Helispots. Although a
>>CASUALTY COLLECTION POINT (CCP) is not official, it has been written about
>>and given serious thought and is followed. A CCP would include areas for
>>triage and can be quite large.... I = Immediate Treatment, D = Delayed
>>Treatment, DECEASED (for the morgue), MINOR = Minor Treatment
>
>Could that be handled nicely with area objects?
Exactly.
I see that! We are making a simulated Incident site!
For those not knowing what the heck we are doing, we are testing symbols
very near 34.11N x 114.27 (thereabouts).
Curt, I see your objects fine...and the ICP view works great there with
UI-VIEW. Others may not see this stuff correctly.....I do not think roger
release this publically. All the firenet guys have it. Please leave your
object up for awhile so others can test.
Jim
----------------------------------------------------------------------
Read previous mail | Read next mail
| |