Order Tray | Contact Us | Home | SIG Lists

[aprssig] POI engine on APRS-IS

Lynn W. Deffenbaugh (Mr) ldeffenb at homeside.to
Fri Feb 24 14:10:51 UTC 2012


I disagree on multiple destination addresses to talk to the same 
server.  You've now increased it to 3, OBJECT - to define them, KILL - 
to kill them, and QRZ - to query them.  The object server is a single 
server and should respond to a single message destination name, 
OBJECT.   Commands to said server should be in the message content.

Yes, I've done messaging QSOs on a D700, and recently at that.  I'm 
familiar with bringing up the message list to edit it.  It's almost as 
easy to poke the button to move from the OBJECT destination to the 
content field, cursor past the object name, enter *KILL* and then DELete 
the remainder of the message and sent it.  Especially for as 
infrequently as I expect people to (not) kill their objects rather than 
just let them age away and disappear.

And I state again, please don't assume that all APRS messaging RF 
stations are the current crop of radios.  TT4s do messaging with 
displays and keyboards and I don't know if they have message recall.  
Tracker2's do messaging from Garmin Nuvis and I'm pretty sure they don't 
do any message recall.  And the new YagTracker also does messaging (I 
think) but I don't know about recall/edit/resend capabilities there.

This is a single OBJECT server, and I believe it should remain a single 
message target.  Otherwise we're setting a precedent that servers can 
consume any number of message destinations that may be so generic (like 
QRZ/KILL) that their use for one function precludes there use from 
future servers where they may make more sense.  Namespaces are precious 
and limited resourses, let's not squander them unnecessarily.

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

On 2/24/2012 9:03 AM, Bob Bruninga wrote:
> Please use the APRS standard for LAT/LONG.  DEG and decimal minutes...
>
> 00:38:15<  Obj: OBJECT Created at 29.122 / -80.987
>
>> It will even let you kill an object but ONLY IF
>> YOU ARE THE OWNER! By using the "<OBJECT NAME>  *KILL*" command.
> I object strongly. (Pun intended). The proposed format is for the KILL
> function to be implemented by sending the SAME message text that created the
> object to the KILL address.  This is for ease of use of the SENDER.  All he
> has to do is call up the old object message, change the TOADDRESS to KILL
> and it will send the KILL message.
>
> Introducing yet another format is not a good idea in my opinion.
>
> There is a lot of kibitizing on this project and I hope that only those who
> have complete and frequent experience with sending messages from the APRS
> HT's are contributing.  That is the only intent of this function.  So if
> every aspect of this project is not totally committed to simplifying the
> process on these HT's then we are missing the mark.
>
>> ALSO... (just for S&  G's) anyone can query the existence
>> of an object by using the "<OBJECT NAME>  *QTH*" command...
> Same comment.  Send the<objectname>  message to the message address of QRZ
> makes more sense to me.  This way we have a consistent set.
>
> Send to OBJ to create the object.
> Send to KILL to kill the object,
> Send to QRZ to see who owns it.
>
> Bob, WB4APR
>
>
> _______________________________________________
> aprssig mailing list
> aprssig at tapr.org
> https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig
>




More information about the aprssig mailing list