OpenBCM V1.13 (Linux)

Packet Radio Mailbox

DB0FHN

[JN59NK Nuernberg]

 Login: GUEST





  
ZL3AI  > APRDIG   03.02.03 07:29l 228 Lines 9423 Bytes #999 (0) @ WW
BID : 809-ZL3AI
Read: GUEST
Subj: TAPR Digest, Jan 28, 2/6
Path: DB0FHN<DB0RGB<OK0PPL<RZ6HXA<IK1ZNW<IR0NET<VK3TE<ZL2BAU<ZL3VML
Sent: 030201/0941Z @:ZL3VML.#80.NZL.OC #:58556 [Chch-NZ] FBB7.00i $:809-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To  : APRDIG@WW

Subject: RE: APRS Symbols (versus Windows ICONS)..
From: Alex <kr1st@amsat.org>
Date: Tue, 28 Jan 2003 07:51:32 -0500
X-Message-Number: 7

APRS is just like hamradio, isn't it?

>Please don't blame TAPR.

<snip>

>This is totally false.

<snip>

>Bob, this is a complete lie, and I demand an apology.

Seeing how you "pros" have handled this issue so far I wonder why anyone
developing hardware or software applications would take you guys serious
when you offer them advise or when you try to steer development in a
certain direction. So far there's a great lack of leadership (or at
least the display of it) which may hurt the advancement of APRS much
more than anything that may be lacking in APRS Specifications. No wonder
developers do their "own thing", there's no team to join.

I'll crawl back in my convenient flame resistant cave now.

73,
--Alex KR1ST

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

[commercial content deleted]

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

Subject: RE: APRS Symbols (versus Windows ICONS)..
From: Bob Bruninga <bruninga@usna.edu>
Date: Tue, 28 Jan 2003 09:21:12 -0500 (EST)
X-Message-Number: 9

On Tue, 28 Jan 2003, Steve Dimse wrote:

>On 1/27/03 at 5:05 PM bruninga@usna.edu (Bob Bruninga) sent:
>
>>>Please don't blame TAPR. TAPR was only a facilitator...
>>
>>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 their own way and do it anyway they individually wanted.
>>
>Bob, this is a complete lie, and I demand an apology. I was there, I am
>certain there was no locked door....
>
>Perhaps you felt trapped by the circumstances, but if so, it was the
>combination of your actions and the opinions of others within the APRS
>community that left you with that feeling. In fact you did not have many
>choices at that point, you could have tried to keep APRS proprietary to
>yourself and the few you chose to license, and killed APRS, or you could
>open it up as others wanted. I think you chose the right way, but there
>was a choice.
>
>There was no lock on the door, you could have walked out any time you
>wanted. Admit the truth.
>Steve K4HG

Yes, and if I walked out, we would have a tower of Babble now...
The term "locked" is a figurative term as you well substantiate in your
paragraph above.  I stand by my statement.  Though I will eliminate
any reference to the type of latch mechanism on the door to the room:

>>"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 their own way
>>and do it anyway they individually wanted."

That was the threat posed to me in that room.

And the total inability of that APRS-Working Group (as a group) to agree
to absolutely anything since and make one single formal change to the SPEC
or to document the APRS-IS since, is a testament to the validity of that
last sentence.

Now I certainly don't blame anyone and certainly not any individual
authors,  I can still work with each of them individually.  And I have no
real complaint about the lack of documentation of the APRS-IS.  That is a
horrendous effort and attempting to document it into a be-all-end-all SPEC
would result in the same kind of compromises that are causing us problems
with the APRS SPEC, and cause it to stagnate.

The authors are doing great work.  They are all trying to do their best
and are working to fix things and to move forward.  But many just see
things differently.  Some think APRS is only an AVLS system.  Some think
it is a global COMM system driven only by the internet.  Some think it is
for State-wide networks, Some think it is mostly a mapping and plotting
system.  In Europe, it is a DX system.  To some it is for SAR.  Some think
it is a local comm system.  The opinions of the players are as varied as
the opinions of HAM radio.  THus, the only thing that could be agreed was
the "on-air-protocol" as published in the spec.

Let me make it perfectly clear.  I dont blame any authors!  It is the
nature of the beast and development in HAM radio in an all volunteer
contribution based system that makes agreement difficult.

Changes come gradually or monumentally.  If people put good things into
APRS  or fix past problems, and it is a good idea and it works, others
will incorporate it.

I think there is lots of progress and great movement in APRS.  But I will
continue to fight to see that APRS adheres to a few fundamental
objectives.  I use these concepts to see if new ideas are "good" for APRS
or are "bad" for APRS:

  1) APRS should work, and work well at the local level on RF
  2) Data latency at that level should be minimal
  3) Messaging should work well and rapidly at the local level
  4) All users regardless of who's applications software in that
     same area will "see" the same information displayed as intended
     by the originator of that information..  (Again, I am not saying
     'how', just 'what' should be displayed)...
  5) It will fully integrate the APRS-IS seamlessly
  6) 144.39 will continue to be the USA Nationwide user entry channel
  7) Back bone and long haul traffic will not saturate local areas.
  8) Direction Finding and station location determination are
     fundamental to APRS and should work seamlessly and effortlessly
  9) APRS will deliver information to mobiles that is valuable to
     their immediate needs in HAM radio in their area.
 10) Information injected by a user will not be arbitgrarily filtered
     at the local level.  But in some cases, draconian measures may
     be necessary to block distant information from interfering with
     local throughput.

These are just off my head, but I think I will better formalize them so
that people will understand where I am coming from when I speak of my
frustrations with the current state of APRS and the things I am trying to
improve...

Bob, WB4APR

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

Subject: RE: APRS Symbols (versus Windows ICONS)..
From: Bob Bruninga <bruninga@usna.edu>
Date: Tue, 28 Jan 2003 09:23:41 -0500 (EST)
X-Message-Number: 10

On Tue, 28 Jan 2003, Juergen Frank wrote:

>Bob's initial idea of showing a symbols status (Deadreckoning) is important
>but the way it could be done should be discussed. Bob?

I did a screen capture to show how I did it in APRSdos:

http://www.ew.usna.edu/~bruninga/aprs/symbols.html

Bob

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

Subject: RE: APRS Symbols (versus Windows ICONS)..
From: Juergen Frank <db2fm@jfsattv.de>
Date: Tue, 28 Jan 2003 15:39:35 +0100
X-Message-Number: 11

I followed the link and am now a little bit confused:

>The following table describes the colors used in APRSdos to convey the "type"
>of station that a given SYMBOL is representing:
> 
>*  WHITE:..... A Full-up APRS station that is message capable
>*  GRAY:...... A Tracker or other station without message capability
>*  CYAN:...... A moving station with CSE/SPEED or a Dead Reckoned Station
>*  BLUE:...... The previous position of a MOVED station or object
>*  YELLOW:.... Your own active OBJECTS you are transmitting to the net
>*  VIOLET:.... Objects placed on the map by others
>*  Dark GRAY:. Old Symbols not updated in the last 80 minutes or more
>*  BLACK:..... Old Symbols that have been "killed" by the originator
>*  RED:....... Emergency, Alarmed, or otherwise unknown symbols
> 
>NOTE: Nothing requires anyone to use COLOR like I did in APRSdos to convey
>this information, but no matter how it is presented, it is important
>information about a SYMBOL on an APRS map that should be conveyed somehow
>graphically to the user..

Why can't a station be 'message capable' and 'moving' (with
CSE/speed/(height))? It should be white and cyan at the same time...

So the idea of indicating something at the stations symbol is good, color is
the wrong way to do it IMHO.
What about having small 'icons' directly attached to a station/object's
symbol (small envelope for message capable, small crossed envelope for not
capable, moving station has a moving indicator right now (shorter or longer
line in driving direction) and old symbols will be greyed out also (UI-View
at least), missing is an indicator foor own or foreign objects...)?

Again: don't show it with colors, it's not possible on B&W clients!

73 de Juergen db2fm

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

Subject: RE: APRS Symbols (versus Windows ICONS)..
From: Juergen Frank <db2fm@jfsattv.de>
Date: Tue, 28 Jan 2003 15:49:08 +0100
X-Message-Number: 12

Hello Bob,

I strongly have to disagree to your statement about APRS in Europe!

How do you come to the opinion that it's used as a DX system here?

I encourage everyone I see, sending long pathes in his/her packets, to
shorten them to make the network run better.

Crazy path-definitions like WIDE7-7,TRACE7-7... Can be seen anywhere in the
world, mostly sent by unexperienced users!

73 de Juergen db2fm

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



Read previous mail | Read next mail


 16.11.2026 14:59:52lGo back Go up