| |
ZL3AI > APRDIG 03.02.03 14:30l 266 Lines 9640 Bytes #999 (0) @ WW
BID : 802-ZL3AI
Read: GUEST
Subj: TAPR Digest, Jan 27, 7/10
Path: DB0FHN<DB0RGB<OK0PPL<RZ6HXA<SP7MGD<7M3TJZ<IK6PYS<W4JAX<VK4TUB<ZL2BAU<
ZL3VML
Sent: 030131/0933Z @:ZL3VML.#80.NZL.OC #:58519 [Chch-NZ] FBB7.00i $:802-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To : APRDIG@WW
Subject: RE: Incident Command Post Symbol
From: "Spider" <spider@rivcom.net>
Date: Mon, 27 Jan 2003 17:09:54 -0700
X-Message-Number: 43
----- 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 5:02 PM
Subject: Re: [aprssig] RE: Incident Command Post Symbol
>Looks like you can't create mixed-case/lower-case object names? I
>now have multiples of each object on my screen, some with
>lower/mixed-case (the way I created them), and some with all
>upper-case (the ones you created).
>
>Good thing we're testing this now, instead of when all heck breaks
>loose and we need this capability in a hurry!
I just took control over...did not change anything manually. So it's
software?
Added a Helibase: A location in and around an incident area at which
helicopters may be parked, maintained, fueled and equipped for incident
operations. More than one helibase is possible.
You saving these defs? The test is next week! hehehehe
Jim
----------------------------------------------------------------------
Subject: Re: ARRL Public Service Manual regarding RACES
From: "Ronald Reams" <wa4mjf@worldnet.att.net>
Date: Mon, 27 Jan 2003 19:11:29 -0500
X-Message-Number: 44
I am an Army MARS phone patch station. We run patches for the Green
Beanies in the 'Stan, Africa, etc. They use a 20 watt (That's right 20)
back pack HF Radio with a wire antenna. Sometimes a Whip from the roof of
their hotels in Africa.
I'm sure if you look around y'all will find some HF rigs.
The NCArNG uses Harris equipment like W1AW has for their HF nets and for
contact 3997 kHz.
73 de Ronnie
AAR4LG
----------------------------------------------------------------------
Subject: RE: Incident Command Post Symbol
From: "Curt Mills, WE7U" <hacker@tc.fluke.com>
Date: Mon, 27 Jan 2003 16:13:17 -0800 (PST)
X-Message-Number: 45
On Mon, 27 Jan 2003, Spider wrote:
>From: "Curt Mills, WE7U" <hacker@tc.fluke.com>
>
>>Looks like you can't create mixed-case/lower-case object names? I
>>now have multiples of each object on my screen, some with
>>lower/mixed-case (the way I created them), and some with all
>>upper-case (the ones you created).
>Ijust took control over...did not change anything manually. So it's
>software?
Yep. When you took over "CampTest", you changed it to "CAMPTEST". Same for
"BaseTest" and "StagingT", you converted them to upper-case. The spec
states that for objects and items the names are case-sensitive, so on my
screen, I now have six objects instead of three.
I'll bet Roger could fix this one in a jiffy. Let him know.
While you're at it, find out if he supports Items yet. I'll place one on
the map near the objects. I'll call it "Spider".
--
Curt Mills, WE7U hacker_NO_SPAM_@tc.fluke.com
Senior Methods Engineer/SysAdmin
"Lotto: A tax on people who are bad at math!"
"Windows: Microsoft's tax on computer illiterates!" -- WE7U
"The world DOES revolve around me: I picked the coordinate system!"
----------------------------------------------------------------------
Subject: RE: APRS Symbols (versus Windows ICONS)..
From: "The Hildebrands" <b.hildebrand@verizon.net>
Date: Mon, 27 Jan 2003 16:13:45 -0800
X-Message-Number: 46
----- Original Message -----
From: <BobDonnell@arkalmus.com>
To: "TAPR APRS Special Interest Group" <aprssig@lists.tapr.org>
Sent: Monday, January 27, 2003 3:27 PM
Subject: [aprssig] RE: APRS Symbols (versus Windows ICONS)..
Bob,
I'll bet the intent here may have been tongue-in-cheek, but what about
creating a new 'message type' which would contain sufficient data to
define an icon. An icon tag to be defined, and a representation of a
bit map that would become the icon. An assignment of a sequence (8?
16?) of currently undefined icon's tags for this purpose would one of
the needed steps to achieve this. Limiting the number of colors to be
represented could allow creating ad hoc icons within the constraints of
a single-line packet transmission, and potentially meeting emergent
needs. Ad hoc defined icons should have a defined lifetime, after which
they automatically expire if not renewed. We might potentially also
want to have the main APRS hubs drop ad hoc icon definitions on the
floor, so at most, an ad hoc icon will only be distributed regionally.
At a minimum, ad hoc icon definitions might be limited to RF only
distribution.
73, Bob, KD7NM
>-----Original Message-----
>From: bounce-aprssig-17768@lists.tapr.org
>[mailto:bounce-aprssig-17768@lists.tapr.org]On Behalf Of Bob Bruninga
>Sent: Monday, January 27, 2003 2:14 PM
>To: TAPR APRS Special Interest Group
>Cc: TAPR APRS Special Interest Group
>Subject: [aprssig] RE: APRS Symbols (versus Windows ICONS)..
>
>
>...
>>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,
>
>
>---
<lingua in bucca>
Individual Icons - - everyone has their own unique position, status, wx
data. Icon? hm..
Actually, I played with this idea several years ago in APRS+SA. I
called the user defined Icon, the Tactical Icon. It was a 16 by 16
pixel, mono-color icon, which produced 256 bits of data, which was then
taken 6 bits at a time, and added to 48 to get a text value which was
then transmitted as a text message of 43 characters in length. OK so,
I wasted a couple of bits...
A sample text message would be:
P0500R0440P840@P0T01P0600T0480P@40PP1402P00
This represents a simple, big X, with bits like this:
1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1
0 1 0 0 0 0 0 0 0 0 0 0 0 0 1 0
0 0 1 0 0 0 0 0 0 0 0 0 0 1 0 0
0 0 0 1 0 0 0 0 0 0 0 0 1 0 0 0
0 0 0 0 1 0 0 0 0 0 0 1 0 0 0 0
0 0 0 0 0 1 0 0 0 0 1 0 0 0 0 0
0 0 0 0 0 0 1 0 0 1 0 0 0 0 0 0
0 0 0 0 0 0 0 1 1 0 0 0 0 0 0 0
0 0 0 0 0 0 0 1 1 0 0 0 0 0 0 0
0 0 0 0 0 0 1 0 0 1 0 0 0 0 0 0
0 0 0 0 0 1 0 0 0 0 1 0 0 0 0 0
0 0 0 0 1 0 0 0 0 0 0 1 0 0 0 0
0 0 0 1 0 0 0 0 0 0 0 0 1 0 0 0
0 0 1 0 0 0 0 0 0 0 0 0 0 1 0 0
0 1 0 0 0 0 0 0 0 0 0 0 0 0 1 0
1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
The first 6 bits, are 100000, which represents 32, add 48 yields 80
which is ASCII "P". The next six bits are all 0 which yeilds ASCII 48,
or "0". The next six, 000101 = 5, add 48 yields 53, ASCII "5", etc.
In APRS+SA one can play with this a little using the APRS+SA
"Calculator" function, and no, it does not work over the air, it is not
supported (<devil's advocate> but it could </devil's advocate>). Try
entering this:
N.B. create an icon:
icon #is TacIcon 'Create'
N.B. see the bits:
icon
N.B. Convert the bits to text:
text #is TacIcon 'Icon2Text' icon
N.B see the text:
text
N.B. see the bits in the text string
TacIcon 'Text2Icon' text
N.B. edit the icon
icon #is TacIcon 'Wait' icon
N.B. see the bits again
icon
</lingua in bucca>
Brent KH2Z
----------------------------------------------------------------------
Subject: RE: APRS Symbols (versus Windows ICONS)..
From: "Ronald Reams" <wa4mjf@worldnet.att.net>
Date: Mon, 27 Jan 2003 19:14:36 -0500
X-Message-Number: 47
Always remember and don't forget:
A camel is a horse designed by a committee.
73 de Ronnie
----------------------------------------------------------------------
Subject: RE: APRS Symbols (versus Windows ICONS)..
From: Miller Scott Contr 30SCS/FTI <Scott.Miller@vandenberg.af.mil>
Date: Tue, 28 Jan 2003 00:16:45 -0000
X-Message-Number: 48
Actually, I was thinking of something along those lines, for saving comment
space and allowing Internet-connected clients to provide a website (or
mailto) icon in the station's detail screen.
Basically, you'd go to a central registration site, enter your URL, and get
a short (4 or 5 character) alphanumeric identifier. That identifier would
go into the comment field of your message (see how much easier this would be
if we used a binary, tagged, multipart message format?). When a station
wanted to look it up, it could either simply provide a link to the
registration site, which would then provide an automatic redirect to the
intended destination, or the software could do the lookup itself, by
querying DNS TXT records in a specially defined zone. The redirect would be
trivial to implement for a client (and would work with web forms), and the
DNS implementation would allow fast, lightweight, reliable distribution of
the database.
I've already done a proof-of-concept, with a web interface updating a
back-end database, as well as TXT records, and it works. If anyone's
interested in this functionality, I could have it up and running within a
week.
For those stations that aren't connected to the Internet (mobiles, for
instance), you're not going to be able to view websites anyway, and instead
of seeing http://www.aprsca.net, you'll see something like @gX3r. If you
really want to look up the site, you can write it down and just look it up
in the registration system later.
Thoughts, anyone?
Scott / N6UQE
----------------------------------------------------------------------
Read previous mail | Read next mail
| |