[aprssig] AVRS Online

[Lynn W. Deffenbaugh (Mr)]

APRSISCE/32 displayed these two items quite well.  But they were 
transmitted as Items, not objects, nor Item-As-Message.  The screen cap 
of the map and station information popups can be seen at:

http://tinyurl.com/AVRS-KG4PID

The raw packets from aprs.fi show:

2011-01-20 23:04:15 UTC: 
AVRS>APZ013,TCPIP*,qAS,AB0OO-D:)EL#523154!3425.92N/08720.69Wn146.960MHz 
T107 EL#523154 22.76 miles
2011-01-20 23:04:15 UTC: 
AVRS>APZ013,TCPIP*,qAS,AB0OO-D:)IRLP#8003!3425.92N/08720.69Wn146.960MHz 
T107.2 IRLP#8003 22.76 miles

These are definitely items (datatype ')'), not objects.  Does anyone 
know if UI-View displays items?  I seem to recall that Objects were the 
recommended repeater format as at least one of the Kenwood APRS radios 
doesn't parse the item packets?

To make these an Item-In-Message 
(http://www.aprs.org/aprs12/item-in-msg.txt) packet, they would have to 
look like the following:

AVRS>APZ013::KG4PID-13:)EL#523154!3425.92N/08720.69Wn146.960MHz T107 
EL#523154 22.76 miles
AVRS>APZ013::KG4PID-13:)IRLP#8003!3425.92N/08720.69Wn146.960MHz T107.2 
IRLP#8003 22.76 miles

Optionally, there could be a trailing {nnnnn at the end of these 
messages if the sender wanted to solicit an acknowlegement.

I'm not commenting on the actual content of the object itself as it 
relates to tunability or compliance with the FreqSpec or LocalInfo 
initiatives.  Just the object vs item vs item-in-message packaging of 
that information.

IMHO, both the objects (items?) AND the Item-In-Message should be issued 
by AVRS. The former for display in all of the legacy clients with 
APRS-IS connections and the latter for automatic transmission by IGates 
to the soliciting station.  If that station doesn't do Item-In-Message, 
they can still read through the text and figure out what it says.  And 
then we can ask the radio vendors to support this format as it's the 
only way to "push" information from the -IS out to RF-based requesting 
stations.

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

PS.  And we still need to assign a ToCall that doesn't collide with 
"Xastir old version" that APZ0xx is assigned to.  I had proposed APAVRS 
but received no response.


Bob Bruninga wrote:
>
> Comment:  The format for the "item" in the message seems to not quite yet
> match the item-in-to format.  For that format the message text would be (I
> think):
>
>    ;146.960*T107 R30m EL#523154 23mi NW{6
>
> Where the R30m is the repeaters own claimed range, and the 23mi NW is the
> AVRS engine's assessment of the range and bearing to it from the users
> position.
>
> If I got that wrong, lemme know.
>