| |
ZL3AI > APRDIG 16.11.03 10:50l 80 Lines 3111 Bytes #999 (0) @ WW
BID : 2280-ZL3AI
Read: GUEST
Subj: TAPR Digest, Nov 05, 3/3
Path: DB0FHN<DB0RGB<OK0PPL<DB0RES<ON0AR<7M3TJZ<JE7YGF<LU6DTS<ZL2TZE<ZL3VML
Sent: 031116/0831Z @:ZL3VML.#80.NZL.OC #:12926 [Chch-NZ] FBB7.00i $:2280-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To : APRDIG@WW
Subject: Re: DX cluster spots on APRS (the RIGHT way)
From: Steve Dimse <k4hg@tapr.org>
Date: Wed, 5 Nov 2003 23:11:07 -0500
X-Message-Number: 19
On 11/5/03 at 10:02 PM Bob Bruninga <bruninga@usna.edu> sent:
>On Wed, 5 Nov 2003, Steve Dimse wrote:
>
>>Also, this example has yet another deficiency. The maximum ambiguity
>>possible in APRS is one degree, 60 nm or less in lat and lon. Yet the
>>area covered by, for example the K4 prefix is 400 or 500 miles, so there
>>is no way within APRS to convey the ambiguity. Also, no callsign area
>>has an ambiguity that is a circle, so you cannot get across what you are
>>really aiming for.
>
>Ah, but the definition of the DX SPOT ICON is what includes the 250 mile
>callsign-prefix-plotting ambiguity circle of a DX spot, not the official
>"position ambiguity concept". (which does only go to 60 miles)...
But even 250 miles isn't enough. This guy seems to be using a position for
each number in the US, all 4's are sent with the same position, 5 use
another position, and so on, but as we all know, people move between
callsign areas without getting new calls. Besides, e even if the 250 mile
is radius and not diameter, the 4 call area is nearly double that 500 mile
circle!
Furthermore, as the original post in this thread showed, these are indeed
being sent as APRS objects, and there is no way for an APRS object to have
an ambiguity greater than 60 nm.
>Remember, the concept of "ICON" never entered into APRS until WinAPRS used
>them as a simplistic approach to APRS displays. Thus overlooking the fact
>that APRS "SYMBOLS" also have many ATTRIBUTES. Here are some of the
>ATTRIBUTES of an APRS SYMBOL that are left out of MOST CLIENT PROGRAMS:
>
>1) Message capable or not (White or Gray)
>2) Digipeating or not (Green or not)
>3) Dead reckoned (CYAN or not)
>4) Moving (light Blue or not)
>5) SOmeone elses Object (Purple)
>6) Your own OBJECT (yellow)
>7) Ambiguity circle around it proportional to ambiguity
>8) Emergency or unrecognized symbol (Red)
>9) 250 mile circle if a DX spot symbol
I do understand this is the way you set up APRSdos, but to developers and
users of other systems, it makes no sense. In a windowing environment, it
makes much more sense to be able to point at an object and get all the
details, rather than to try to convey a few of bits of information with
color. Monochrome icons (excuse me, symbols) just won't fly in a windowed
environment. There is a reason no other APRS program implements your color
symbol plan, and I think you need to accept that.
As to plotting ambiguity circles, fortunately virtually no one transmits
ambiguous positions, if they did I can imagine the mess that would make on
your map!
Steve K4HG
----------------------------------------------------------------------
Subject: Kenwood D-700 and KPC-9612
From: Reid Crowe <bigreidous@sbcglobal.net>
Date: Wed, 5 Nov 2003 20:18:53 -0800 (PST)
X-Message-Number: 20
Can i use both 1200 and 9600 baud on the D700 at the same time through the
data port?
73 Reid KC=D8IDI
---
END OF DIGEST
Read previous mail | Read next mail
| |
