OpenBCM V1.13 (Linux)

Packet Radio Mailbox

DB0FHN

[JN59NK Nuernberg]

 Login: GUEST





  
ZL3AI  > APRDIG   03.02.03 14:30l 255 Lines 11652 Bytes #999 (0) @ WW
BID : 796-ZL3AI
Read: GUEST
Subj: TAPR Digest, Jan 27, 1/10
Path: DB0FHN<DB0RGB<OE5XBL<OE3XSR<OK0PCC<OK0NAG<OK0PPL<RZ6HXA<IK1ZNW<IR0NET<
      VK3TE<ZL2BAU<ZL3VML
Sent: 030131/0914Z @:ZL3VML.#80.NZL.OC #:58513 [Chch-NZ] FBB7.00i $:796-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To  : APRDIG@WW

TAPR APRS Special Interest Group Digest for Monday, January 27, 2003.

1. Re: ARRL Public Service Manual regarding RACES
2. RE: APRS Symbols (versus Windows ICONS)..
3. Re: FT-100 operations.
4. RE: Incident Command Post Symbol
5. RE: Skywarn Symbol
6. Re: Proposals, was something else
7. RE: Incident Command Post Symbol
8. RE: Incident Command Post Symbol
9. APRS Look-and-Feel [was: APRS Symbols (versus Windows ICONS)]
10. RE: Incident Command Post Symbol
11. RE: APRS Symbols (versus Windows ICONS)..
12. Re: ARRL Public Service Manual regarding RACES
13. RE: APRS Symbols (versus Windows ICONS)..
14.  Re: ARRL Public Service Manual regarding RACES
15. RE: APRS Symbols (versus Windows ICONS)..
16. RE: APRS Symbols (versus Windows ICONS)..
17. T-238 weather station wind speed...
18. RE: installed infrastructure, WAS: Symbols/Icons wa	s something else
19. APRS TRACKING
20. RE: APRS Symbols (versus Windows ICONS)..
21. RE: Incident Command Post Symbol
22. Re: FT-100 operations.
23. RE: APRS Symbols (versus Windows ICONS)..
24. APRS Presentation
25. Re: APRS TRACKING
26. RE: APRS Symbols (versus Windows ICONS)..
27. RE: APRS Symbols (versus Windows ICONS)..
28. Re: APRS TRACKING
29. RE: APRS Symbols (versus Windows ICONS)..
30. Findu CGIs
31. Re: APRS TRACKING
32. RE:  Re: ARRL Public Service Manual regarding RACES
33. RE: APRS Symbols (versus Windows ICONS)..
34. Re: ARRL Public Service Manual regarding RACES
35. RE: Incident Command Post Symbol
36. RE: APRS Symbols (versus Windows ICONS)..
37. RE: Incident Command Post Symbol
38. RE: APRS Symbols (versus Windows ICONS)..
39. RE: Incident Command Post Symbol
40. RE: Incident Command Post Symbol
41. RE: APRS Symbols (versus Windows ICONS)..
42. RE: Incident Command Post Symbol
43. RE: Incident Command Post Symbol
44. Re: ARRL Public Service Manual regarding RACES
45. RE: Incident Command Post Symbol
46. RE: APRS Symbols (versus Windows ICONS)..
47. RE: APRS Symbols (versus Windows ICONS)..
48. RE: APRS Symbols (versus Windows ICONS)..
49. Fw: RE: Incident Command Post Symbol
50. RE: APRS Symbols (versus Windows ICONS)..
51. RE: Incident Command Post Symbol
52. Re: Fw: RE: Incident Command Post Symbol
53. Re: Fw: RE: Incident Command Post Symbol
54. Re: ARRL Public Service Manual regarding RACES
55. RE: APRS Symbols (versus Windows ICONS)..
56. RE: APRS Symbols (versus Windows ICONS)..
57. Re: ARRL Public Service Manual regarding RACES
58. RE: Incident Command Post Symbol
59. Malfunctioning Vertex VX-150?
60. RE: APRS Symbols (versus Windows ICONS)..
61. RE: APRS Symbols (versus Windows ICONS)..
62. findu2 backup remaining funds

----------------------------------------------------------------------

Subject: Re: ARRL Public Service Manual regarding RACES
From: "Jack Smith" <jrs38801@bellsouth.net>
Date: Sun, 26 Jan 2003 23:08:41 -0600
X-Message-Number: 1

Probably wouldn't apply to present day in any event.  Very few of our radios
will work in the ham bands (except for 6 meters, which is smack in the
middle of our tactical freqs.), and we're going to FHSS (from 30.000 to
75.000MHz), satellite, etc. anyway.  During Vietnam, Grenada, Panama, El
Salvador, Guatemala, Desert Storm, etc. it's not been an issue, and I
suspect it won't be in the future, either.  But, someone does need to bring
it up with the powers that be that APRS has a unique place, and see if an
exception to policy or exemption can't be made in advance.  Just in case...

Jack
KE4LWT

----------------------------------------------------------------------

Subject: RE: APRS Symbols (versus Windows ICONS)..
From: Bob Bruninga <bruninga@usna.edu>
Date: Mon, 27 Jan 2003 00:52:33 -0500 (EST)
X-Message-Number: 2

On Sun, 26 Jan 2003, AE5PL Lists wrote:

>>"SYmbols" in APRS are supposed to convey several layers of
>>information about each "thing" on a map for instant
>>recognition.  Thus APRS, as designed in the original APRSdos,
>>displays each "symbol" on a map using COLOR (and overlays) as
>>variables:
>
>Where was any of this in the Spec?  Overlays and some coloration such as
>for digis and weather are included in the symbol set in the
>specification and implemented by most clients.  But the rest of the
>colorations are not.  And, are those colors background, the symbol
>itself, what?  This is a rhetorical question.  Bottom line is, there is
>no standard answer because there is no specification except for the
>statement "what I do in APRSDos" which does not hold water for those who
>author these other clients.

APRS was invented and totaly specified and defined in the 1992 to 1995
time frame and implemented fully in APRSdos.  In 1995 other authors began
to implement it in Windows and took bits anb pieces of it, and then the
need for a SPEC became very obvious as different authors implemented
things differently.  The SPEC then became a "committee" effort and the
only thing "permitted" in the spec was what was common to APRSdos and
already implemented in Mac/WinAPRS, even though many of the fundamental
principles of the APRS system design were not fully implemented in
Mac/WinAPRS.

Thus the SPEC does not necessarily fully represent what I designed APRS to
do, but represents the lowest common denominator.  To see what APRS is
supposed to do (but without pretty maps) the only baseline is APRSdos.
Although I do not expect anyone to find APRSdos attractive at all in
today's PC environment, it still implements 100% of what was the design
objective of APRS.  An NO OTHER PROGRAM has fully implemented all of the
fundamentals.

>>Thus, a whole layer of visual information was lost in most
>>Windows versions of APRS that took the simplistic "Icon"
>>approach to displaying APRS stations on their maps.
>
>Virtually all graphical environments allow modification of colors in the
>icon.  This was probably not implemented because the authors were
>unaware of the various colorations that you wanted to appear for a
>symbol.

No, They were fully aware, but they had other priorities and that was to
get better maps working. Remember, their objective was to solve the
problem of "good maps" for APRS, and in that excellent effort, a lot of
the fundamental stuff was missed... I am not criticizing at all just
explaining why I think the SPEC is deficient in many areas...

>>So, lack of seeing what an "icon" is, is not the fault of
>>"APRS", it is the fault of many implementations of "APRS"...
>
>And, I submit, the fault of you by not doing a good job in conveying
>these ideas, hence their omission from the Spec.

I find that accusation offensive, arrogant, self richeous and totally
unfounded by someone with no hindsight who was not around during those
painful years.  I did everything in my power to convince, cajole and
otherwise try to influence the proper implementation of APRS in other
programs, but its like hearding cats...

I begged and pleaded the other authors to do it right and to follow all of
my DETAIL specifications in all the APRSdocs.  But That does not happen
when programmers start coding.  They do what they want to do.

Your insinuation that it is my fault is the most outlandish statement I
have ever heard!

>A major problem with your implementation of symbols in APRSDos is the
>lack of uniform symbols

There was never any intention to be uniform!  The EYEBALL and Tornado and
Hurrricane symbols to name a few were intended to be BIG.  Others were
intended to be small.  Others expand to cover the area affected as you
zoom.  SO your insinuation of a "problem" is your lack of understanding of
the intent of such symbols in APRS.  ANd a lazy acceptance of a simplistic
one-size-fits all use of ICONS irregardless of importance of said symbols.

>and a lack, judging from your post, of uniform
>coloration between applications.  Use of pre-created symbols (icons)
>allow multiple applications to use a common way to display objects,
>stations, etc. Changing their color is well within the capabilities of
>most graphical environments.  But those colors may not work well
>depending on what the background is.  All maps do not use black
>backgrounds, or even white backgrounds.  This causes many colors to lose
>their visibility. Something to keep in mind.  Also, some of the color
>recommendations such as green for digis and blue for weather is
>implemented anyway within the symbol set as shown in the specification.
>That factor needs to be taken into account, as well.

Yes, "Taking things into account" is the job of any good programmer.
I do not need to hold anyone's hand (nor would they listen) to tell them
how to convey the SYMBOL type variable.  At their resistance, I left it up
to them to figure out how they wanted to do it, but the fact remains, none
did.

The point is:

Any single APRS symbol on a map can represent many "types" of an entity,
and that "type" should be conveyed within th egraphical user interface
visually without having to selectively query each symbol to determine this
variable.

APRS WAS DESIGNED TO CONVEY THIS BY COLOR.  BUT I NEVER INSISTED THAT ANY
OTHER AUTHOR DISPLAY THOSE VARIABLES IN COLOR.  BUT I DID INSIST THAT
SYMBOLS HAVE THE VARIABLE OF "TYPE" AND THAT THEY SHOULD CONVEY THAT
INFORMATION TO THE USER IN A VISIBLE WAY.

To my knowledge NO one has done this.  THus on most APRS, people see a
"CAR" but they cannot tell if it is:

   1) An Active APRS station with message capability
   2) An Active APRS tracker with no message capability
   3) An object placed by someon else
   4) An object placed by you
   5) An old symbol (more than 80 minutes old)
   6) A deadreckoned symbol
   7) The previous posit when a new posit replaces it
   8) Some kind of object that is also acting as a HIGh digi
   9) Some kind of EMERGENCY or UNKNOWN symbol

Whereas in APRSdos, this is conveyed by the color of the symbol.  But I
would NEVER insist that any other programmer do it in color, but I am very
disappointed that none of the other authors display this SYMBOL TYPE
variable on the map for EASY assessment by people looking at these maps
(without haivng to go dig for it)...

>Can more information be visually represented by the various clients?
>Yes.  Will the same techniques work with all maps and displays?  No.
>Does that make the other applications bad or incomplete?  IMO, No.
>Should a standard set of symbols be used to reduce confusion when
>looking at various client displays?  IMO, Yes.

I absolutely agree to all of the above, except for the one where you
conclude that the omission of this "type" information from the display is
"not" an incomplete application.  I say they are incomplete and can do a
better job at conveying this information to the end user at a glance.

The lack of this information leads to user CONFUSION and that is exactly
what a "TACTICAL REAL TIME" system should NOT do.

If you still do not understand, I say again I am NOT saying to anyone to
"do it like APRSdos" what I am saying is that many "APRS" applications
have left out a lot of critical details of APRS which undermines its
cross-platform effectiveness in "Tactical Real-time" communications
scenarios where a "picture was supposed to be worth a thousand words" at
conveying what is going on. (WITHOUT having to use a MOUSE to find out!)

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.

I'm sorry, but the tone of your condescending emails upsets me.

de WB4APR@amsat.org, Bob

----------------------------------------------------------------------



Read previous mail | Read next mail


 16.11.2026 07:48:57lGo back Go up