APRS Common Buletin Board for Situational Awareness 16 Jan 2008 ------------------------------------------------------------------- WB4APR Ev Tupis noted: > APRS is billed as a situational awareness service, > yet... largely barren of situational awareness info... The original APRS concept for displaying this collection of situational information was the MAP display with lots of manually entered objects -and- the COMMON BULLETIN/ANNOUNCEMENT BOARD. Other links address the many missunderstandings about APRS as an information receive and display system, but this file will address the lack of implementation in most follow-on clones of the COMMON BULLETIN/ANNOUNCEMNET BOARD concept. Unfortunately, only the original , XASTIR and an add-on to UIview implemented the original concept of a single COMMON Bulletin board. Just like a MAP display was supposed to let everyone see the same MAP information throughout the network, the BULLETIN BOARD was supposed to act like a BIG DISPLAY board that EVERYONE could see and they ALL SAW THE SAME THING. Think of a big board in the EOC, but now everyone can see the SAME board via APRS everywhere. BUT the VIEW was identical to all observers! The original APRS BULLETIN board had 40 lines. This is not a "limitation" but a forced method of making users condense information to only what is immediately valuable, current and relevant. Think of the public boards in Train stations or Airports. In APRS, anyone can post to the board, can edit their lines or can kill their lines. The board is always sorted on the display. This way, the most important information was always on the display (the same to everyone) and since each source can edit his lines one line at a time, this drastically reduced channel load. Only a changed line had to be retransmitted. If the top 4 lines on the COMMON display board was maintiaing a list of capabilities at each shelter, then to change the second line of that display, an update required only ONE PACKET to re- transmit THAT line! The update was sorted and INSERTED where the old line was! The limitation of 40 lines was arbitrary but was INTENTIONAL to keep the board uncluttered and to make sure that EVERYONE was always seeing the most important and current information and all were seeing it in the same way! If new information came in that made the board go over 40 lines, then the oldest information was overwritten. But more often, the originator of an old post that was no longer valid, could simply OVERWRITE his old lines on the board with new information on the board at the same place. Again, ONLY THE 40 most important lines that were CURRENT would ever be on anyone's display. If you wanted to see a chronology of all bulletins, updates, changes etc, then you could look at the message log. Problem is, only a rare few of the follow-on APRS clones implemented the COMMON bulletin board. They all just show bulletins as items in a sequential LOG of messages. Thus, no one sees the same thing. There is nothing maintaining the currency of the information, there is no system for focusing on what is imporant and what is old, and there is no way of editing or updating information without sending the entire text and context over again plus retries. This is a total failure of these clones to understand the need for COMMON information diplays of situatinal information! The few clones that even considered the COMMON bulletin board display rejected it as being too limited at 40 lines. They could provide a Nulletin display of hundreds or thousands of lines of bulletins as they come in... Well DUH, that is the worst way to present TIMELY, RELEVANT, IMPORTANT information. Humans cannot focus on huge lists of old data, they need to FOCUS only on what is relevant and current. This single COMMON BULLETIN/ANNOUNCEMNT display was supposed to filter out all the old, changed, and updated information and only display to everyone the MOST IMPORTANT and CURRENT 40 lines of info, that EVERYONE SAW everywhere. With a Common Bulletin Board display, all one has to do is look at the BULLETIN BOARD and see what has been posted. If something new has been posted since he last looked, he/she is alerted to "new bulletins" pending. This one screen gaves him the full present, real-time situation (that everyone else is also seeing). With the all the missguided focus on the maps and just vehicle tracking of so many follow-on clones, this concept of a FIXED Single Community Bulletin Board display presenting the full relevant tactical situation has been completely lost to almost all users. This is another reason why the focus on APRS as a vehicle tracking system has caused people to no longer see APRS for its intended purpose of situational awareness. We need this 40 line common Bulletin Board added to all software that omitted it in their rush to vehicle tracking. I believe that an add-on has now been written for UIview. I hope everyone uses it. Using this add-on would be a requirement for participation in an event so everyone sees the same thing. An entire page in the APRS SPEC (p78) was dedicated to presenting this concept of DISPLAY and IMPLEMENTATION of a COMMON bulletin board display, yet it was easier for programmers to just display bulletins as they came in, and keep them in a sequencial log, than to present them as intended. Bummer for APRS... Don't get me started on what else has been glossed over in the rush to put ICONS on maps. APRS was a lot more.... Read about them: http://www.aprs.org/APRS-tactical.html Bob, WB4APR